Hi,

Although I've managed to boot a custom kernel and recovery image using a combination of rkdeveloptool and fastboot, I noticed that on the 'stock' android firmware adb has been configured in 'production mode' and won't let you run 'adb root' to gain root access to android - this is an accident, right?  The dev documentation seems to expect the device to not be in production mode and for 'adb root' to work.

Can we get an 'update' to the stock image that turns off 'production mode' so we can tinker with that environment?

Thanks

Edit: Never mind I managed to get the stock android rooted using magisk - after realizing my boot.img I fed it initially was incomplete, leading me to think magisk was to blame for making android unbootable. All good now

On the wiki ( https://wiki.pine64.org/wiki/Quartz64 ) it mentions installing Debian testing userland.

Is it possible to do this without touching an existing 4.19 based boot partition (so keep the existing working kernel and dtb file)?

How do I actually do it?

Would anyone be kind enough to let me know what version of Mobian i need to make the keyboard work?  i have done an update and an upgrade, but the keyboard is still just a hockey puck.

This article explains how I created a Linux script to flash and test Apache NuttX OS automatically on PineCone BL602...

https://lupyuen.github.io/articles/auto

Since everything tried so on my PinePhone was working and I had just completed my weekly update to Mobian I thought it might be useful to check out the dip switches and disable the front-facing camera. Clicked down switch 5, which should have disabled the front-facing camera, only. Rebooted the phone and when I brought up the camera app nothing happened except showing the background wallpaper. It appeared as if the camera app was totally disabled. The good news was that when I returned the switch to the off position and rebooted the phone the cameras both worked perfectly. This was contrary to some reports I had read which had described a total reinstall of the OS to make the return settings work. Yaaa.

Am I missing something on setting the dip switches or is there still work in progress? Any comments or assistance is always appreciated. Thanks

Hi,

I received the fingerprint scanner. So now the first task is to get this working

I haven't found many information, apart a demo that was based on https://github.com/zschroeder6212/tiny-i2c-spi  (which does not build, see https://github.com/zschroeder6212/tiny-i2c-spi/issues/1 ).

Any way to go further ?

Hello,

the last time I installed updates (from the Terminal), my pine phone froze after a couple of minutes.
I waited a really long time, was using wifi and connected to power.
I finally made a hard reset (pressed the power button for 20-some seconds), started it again and got -- nothing. Just a black screen and the LED constantly on in green.

I have arch installed on the eMMC.

So, I made a full backup months ago. My bad, I know.

I still would like to know if/how I can access my data that is (hopefully) still on the phone.
Can I access some kind of boot manager during startup?
Could I make a backup of the broken phone and get my data from that backup?
Could I roll-back to some kind of restore point (this would be ideal)?

Any help is appreciated!


   lacriz

Hi,

I was looking in the store and can't find the pinepower 120W desktop charger anymore.
It was already out of stock but now it seams to eb disapeared?

Does any one know if it will be back?

Regards Paul

Finally saw my pine64 keyboard battery. Inserted phone (without battery) in keyboard. Pinched across the screen/rear cover pogo pin area and the phone started under keyboard battery power - great, my battery works Released my pinch and the phone (of course) lost all power.

Come on #Luke, many of us have already subsidized the pinephone by buying second motherboards without complaint. Please could you explain why the keyboard case lid is so poor? I have inserted/removed my phone carefully a couple of times and the case around the volume up/down button is already warped. A snap on rear phone case is OK but the keyboard case obviously needs mechanical connection/retention.

pine64 == guinipig64???
   

I realize that there is no way that shutting off the modem via software can be as definitive as the hardware kill switch. However the switch is a bit of a pain to get to and I don't know how many on/off cycles it can take.

By tapping the cellular icon in Phosh's control area at top of the screen it disables the modem, but how effective is that? Does it actually turn the modem off and prevent it from connecting with the carrier, or does it just prevent messaging at the user level? If left turned off when powering the phone down the modem indicator will stay off the next time the phone is powered up - but until Phosh loads does the modem become active for a short time?

I'm just wondering how functional that software switch is.