Hello forum,

I would like to create a function where i can run a background 'daemon' that listens for incoming calls. Any incoming calls are redirected over the network/internet to another server.

So if my phone is in location A, i can connect to the phone and perform calls, as well as receive calls. SMS Text messages I would also like to be supported. For example a script ./sendsmsmessage "<telephone_nr>" "text message body". But receiving them is just as important. I can then write some web frontend that connects to the phone and allow for telephony over the network / remote location.

How would i best achieve this? Can i do commands on the command line / shell ? Does anything like this exist already?

Hi forum,

I was thinking: new hardware comes out regularly, for example a new Rockchip processor model. Wouldn't it be great to make modular hardware?

Think of a phone: battery module, casing with front screen, camera modules (front+back), modem module, mainboard module with processor, ram and headers for cables that connect to the display, cameras, modem and battery.

Think of a laptop: casing, monitor, battery, mainboard module with processor, ram and headers for various USB ports.


Advantages for users:

- users would have more choice and order their product a la carte. Want a Pinephone? Start designing you own:

1) standard plastic case or more expensive aluminium one, even more expensive aluminium one with custom printed .png or whatever might be an option.
2) select your processor, want RK3288 (PP OG) RK3399 (PPP) or the new RK3588 (PP Ultra i would call it). Perhaps also RAM options. So could be a RK3588 module with 16GiB RAM for power users.
3) modem module could be the default 4G modem or in the future a 5G modem. In some cases the user could use no modem module at all, and would only use wifi and use it as a mini tablet. That is what modular is fun for: more choice.
4) camera modules: some users want no cameras at all, better than a hardware switch for them, they would want better hardware instead like more RAM. Other users might want a simple back camera but good front camera for video calls. Other people don't want front camera because they don't do video calls, but they do like photography, so good back camera. Why not make a back camera module that costs 400 euro? No problem particularly if you can swap it to a newer/modern pinephone model later. Then your 400 euro is modular and can be taken to your daily driver phone that you want the best hardware for. So modular hardware might cause people to spend more, because their products can more universally be used. If i pay for a good camera on a Pinephone Pro and soon RK3588 model comes out, that good camera may be wasted as i will use the older PPP differently. Transferring hardware seems cool to me.
5) WiFi/Bluetooth module: some want cheap model others want wifi 6 with mimo and whatnot, perhaps even external antenna (RP-SMA or that mini connector not sure the name UFL or something)
6) Battery: i would like different modules where the battery grows thicker, so you can choose a very sleek compact thin phone with quite low battery life that lives from charger to charget (Qi i hope) or some users might want a phat brick phone that is heavy and used with bluetooth headsets often and just stays in your bag/purse/whatever most of the time. Make the battery 4 times as big as the standard capacity.

- buying modular hardware might offer users more value for money. Right now if a user wanted a very good camera, it would be attached eternally to one pinephone model. What if soon a new model comes out, the expensive camera is kind of wasted on the older hardware. I like it that people can take with them (upgrade) their modules. So if RK3588 model phone baseboard comes out, then users buy that, and upgrade their phones with it. They can sell off the older baseband.

- modular means easy to repair. Busted your screen? Your baseboard, modem and battery, as well as your cameras may just be fine. Swap them out, order your replacement casing with front screen (those two ought to be one module i think), and you are good to go again without expensive custom repair, but diy repair by just ordering a new module.

- you can make an awesome website where people can design their own pine products with modules, that satisfies many users as they like to have choice, and see visually those modules that stack together. It is cool!

- people may be wanting to spend more money on Pine products. Say you give options for expensive camera modules, people would buy them if those can be used on several phones, allowing the user to take the modules with him/her if newer hardware is bought. So more reason to buy i think.


Advantages for pine developers:

- it breaks new projects down to smaller components. You can just design and release modules instead of entire projects like a new phone model.
- hardware bugs can be mitigated. Bring up a wiki where revisions and changes are kept. Such as: baseboard RK3399 rev 1.1 has bug X but rev 1.2 has that fixed.
- offer some upgrade program for hardware bugs, offering some discount. So if rev 1.1 has a hardware bug and 1.2 has it fixed, allow some discount when user orders the upgrade.
- pine developers can focus more on modules and release often, higher development speed than if you need to finish an entire new phone.
- users getting more interested in pine products means bigger exposure and perhaps more investors/money/growth/opportunities.


I am very excited about pine products, but i feel something is needed to kickstart and accelerate development. The products need to get better, and a software ecosystem is yet to be established. I am hoping to promote this a bit. Any feedback?

Hello forum,

As you might know, Pine uses 4 rockchip models:

RK3288 (4 slow cores)
RK3399 (2 fast cores + 4 slow cores) 4GB RAM max
RK3566 (4 slow cores) 8GB RAM max
RK3588 (4 fast cores + 4 slow cores) 32GB RAM max

The Pinephone Pro is based on RK3399. The new Pine Tablet announced and under development would use RK3566.

But i am concerned this chip is not powerful enough. For a cool tablet a good single thread performance and good GPU performance is necessary. RK3588 seems to be right chip for that. RK3566 is much less powerful. Also the 3588 is produced on 8nm process node, which is very modern as the latest and greatest is now on 5nm. Not sure what process the other chips are produced on, but i recall they were very old process nodes. RK3588 is the bomb - a super upgrade for those loving libre arm64 hardware. Can boot blobless so privacy-wise this chip is pretty awesome.

So ideally, i would love to see:
- PinePhone Pro 2 or PinePhone Ultra based on RK3588
- PineBook Ultra based on RK3588
- PineTab Ultra based on RK3588.

If you make the product build quality good - use aluminium casing and have good feel quality - then these products could be considered medium/high-end. The RK3399 could be considered low/medium-end i guess. The upgrade will allow for gaming as the RK3588 has great GPU performance. But the drivers are still a WIP for many months i guess? So i am hoping the people behind Pine would consider upgrading to the RK3588 later this year. It would make an excellent laptop and tablet. The phone needs the upgrade less, but it is still a 'killer product' from pine as we have only Librem as competition.

What do you people think?

Hi,

I just wanted to share my first attempt to create a 3D print model of a case for the ROCKPro64 board with a SSD (connected through a 2 port PCI-E to SATA extension) and a 40mm fan.

Hope it can be useful to others

https://www.printables.com/model/380432-...h-40mm-fan

Hello,

I am trying to place shortcuts to some websites on my app drawer, but they don't show up. I created some simple .desktop files like this:

January updates for NemoMobile include:

• Various bug fixes and improvements.
  
• An improved user experience for the time picker component.
  
• Support for USB mode with MTP (Media Transfer Protocol).
  
• Fixes for connecting and disconnecting from the internet.
  
• Improved user experience for notifications and added support for remote actions.
  

I love that Pine offers a wearable watch with health tracking features - I really want a health tracker but I don't at all fancy smart watches. 

In the segment of screenless health trackers, there is currently the Whoop 4 and Amazon Halo band, both designed for discretion, supporting placement on the upper arm, ankle and even being attached via CGM sticker.

This is the Whoop 4 



And this is what it looks like to have a health tracker attached via CGM sticker or bicep band



I was wondering if I could be so bold as to see if there is interest in such a device and perhaps make a hardware request (because I could never make this hardware myself)?

I feel like current generation wearables (fitbit and the like) are too focused on gimmicks, pushing subscription payments while lacking transparency. They have poor data exploration tools, don't offer insight into how they come to the health conclusions they do and you can't export raw data from their services .

Such a device would democratize the collection of health data and put the storage and post processing of that data in the hands of the device owner.

Does Pine64 take hardware requests?

This started a couple months or so ago, trying to open Megapixels just returned the error /dev/video2: No such device
I thought maybe the ribbon cable to to the camera got dislodged after dropping the phone hundreds of times, so I took them out and back in, but still had no luck with it. I could hear the lens or something clicking when trying to start Megapixels, so at least something was connecting, though it's since stopped...
I eventually updated PostmarketOS from 21.something to 22.12 thinking it was just a software issue, but it didn't help; I only got a different error: Could not find camera entity matching 'ov5640'
I also tried taking a picture with ffmpeg using all 3 /dev/videos, but got Not a video capture device and /dev/video2: No such device again.

I haven't gotten around to trying another OS yet, but I doubt this is a software issue considering that 2 other things broke as well, being the internal storage and rear speaker (kinda). Is there any way of narrowing the issue down to a specific component? Or will I have to build I2C prosthetics for my phone, or more realistically just get the Pro?

Hi,

My setup :
- latest arm64 Kali, with kernel 6.0.0-kali5-arm64
- latest tow-boot 2021.10-005 on SPI
- Kingston A2000 M.2 2280 NVME 1 To (one of the best supported drives from wiki list)

My problem : On boot, nvme is detected but I get a rescue console on every boot.

My "ugly" fix : 
modprobe -r nvme
modprobe nvme
exit console
I get a normal boot

On logs (with |grep -i nvme): 
[    7.298134] nvme nvme0: pci function 0000:01:00.0
[    7.298238] nvme 0000:01:00.0: enabling device (0000 -> 0002)
[  68.575114] nvme nvme0: I/O 8 QID 0 timeout, disable controller
[  68.683053] nvme nvme0: Device shutdown incomplete; abort shutdown
[  68.703561] nvme nvme0: Identify Controller failed (-4)
[  68.703769] nvme nvme0: Removing after probe failure status: -5
[  86.189969] nvme nvme0: pci function 0000:01:00.0
[  86.195630] nvme nvme0: missing or invalid SUBNQN field.
[  86.208844] nvme nvme0: 6/0/0 default/read/poll queues
[  86.219019]  nvme0n1: p1 p2


My extlinux section :
label l0
menu label Kali Linux 6.0.0-kali5-arm64

linux /boot/vmlinuz-6.0.0-kali5-arm64

initrd /boot/initrd.img-6.0.0-kali5-arm64

fdtdir /usr/lib/linux-image-6.0.0-kali5-arm64/
append root=UUID=24ac514d-0b32-4e31-9cd1-a2e3ad3c6ead console=tty1 ro rootwait

pine phone pro won't start

link img error : https://postimg.cc/R6F9Hx4Q

Help me