im a complete beginner with linux,  i bought a pinebook pro with manjaro and i totally forgot the sudo password. any help would be greatly apprecited

Hi,

Just wondering is it worth buying a faster Micro SD card for a PinePhone Community Edition so it may run a bit faster?

The quicker cards tend to be USH-III then USH-II then USH-I:
https://www.androidcentral.com/best-micr...rd-android

If your device is only capable of dealing with USH-I devices then if you plug in a USH-II device then it will run at USH-I speeds.
https://havecamerawilltravel.com/photogr...osd-cards/

Here it says that for the Rock64 it probably supports USH-I but not any higher:
https://forum.pine64.org/showthread.php?tid=4685

Hello!

For privacy reasons I want to keep modem disabled unless I want to make a call or use internet via the modem.

I was expecting operating system on pinephone to find the modem once its powered back by the hardware kill-swich on the back of the device.

Doesn't work: once the modem's hardware kill-switch is "off", the modem does not re-appear in pinephone operating system when the hardware kill-switch is returned to "on" position.

I tried with postmarketOS, ubuntu touch and pure os for pinephone (purism guy says on Librem phone the switches are not requiring re-boot for re-activating the hardware, at least not wifi: https://forums.puri.sm/t/librem-5-pineph...es/8793/12 ). Neither was able to detect modem when its re-enabled by the hardware kill-switch.

Is there any way to bring pinephone modem back to operating mode without system reboot after I flip its hardware kill switch from "off" to "on" position?

Thank you

Spent a good chunk of today attempting to get anbox running under mobian (Linux thalia 5.7-pinetab #1 SMP PREEMPT Fri Sep 11 11:37:38 UTC 2020 aarch64 GNU/Linux) because why not. A log of my progress:

• Nobody's built a snap for arm64 so I can't do that.
  
• Attempted to build anbox from source and actually managed it, but couldn't use it because all the plumbing (e.g. systemd and dbus stuff) is contained in the snapcraft yaml which is used to build systemd units when the snap is built so make install produces roughly one-third of a functioning installation.
  
• Attempted to build a snap myself but it failed because snapcraft builds in a container using multipass but multipass uses qemu's default --machine handling which is unpopulated on arm64 so it complains and bails out. Can't use the --destructive-build option, which skips the containerization, because it just blows up due to a library version mismatch. Also, snaps don't support cross-compilation. Like, at all.
  
• Finally decided to just ignore apt's attempts to tell me that anbox wasn't available for my system and started using curl and dpkg to install random debs from other releases. Eventually found this one that appears to have installed mostly right: http://http.us.debian.org/debian/pool/co..._arm64.deb.
  
• anbox-container-manager.service wouldn't start because it was attempting to modprobe ashmem_linux and binder_linux, which don't exist any more because they're now (respectively) in-tree and obsolete. /proc/config.gz has both CONFIG_ASHMEM=y and CONFIG_ANDROID_BINDER_IPC=y, so I just edited /lib/systemd/system/anbox-container-manager.service to remove the modprobes. That got anbox-container-manager.service enabled and started. However, this doesn't yet prove anything because the container manager doesn't start the container until a request is received from the session manager, so we haven't actually tried talking to lxc yet.
  
•  anbox session-manager also complained about not having ashmem or binder. It turned out that it was looking for binder by just attempting to blindly open /dev/binder, which has been superseded on recent kernels by binderfs. I "fixed" this by manually creating a binderfs and then symlinking the device in where anbox was looking: mkdir -p /dev/binderfs ; mount -t binder binder /dev/binderfs ; ln -s /dev/binderfs/binder /dev/binder. This got the session-manager to at least do something, though it immediately failed out because the container manager can't start a container.
  

Hi all

I was looking at purchasing a Mean Well PSU for my upcoming Rockpro64 build.  However, I don't know the length of the DC barrel.

I was thinking about this one -

Mean Well GST60A12-P1J https://au.element14.com/mean-well/gst60...dp/2815913

Barrel Plug Center Positive 2.1mm x 5.5mm x 11mm

Will this one work with the RockPro64 or do I need a 9.5mm barrel length?

I guess I could just cut off the connector and solder a different barrel, but would like to know before I make the purchase.

Cheers

Wiing

I have a brand new Pinebook Pro and I haven't spent 10 minutes on it yet because some keys are not working. I found a similar report here:

https://forum.pine64.org/showthread.php?tid=9894

I emailed Pinebook support 3 days ago and haven't received a response. I see in the above thread there wasn't any responses either.
Can someone assist? I have a brand new computer that's currently a brick and I would like to understand my options.

Thanks so much!

I know that the Rock64 world is a little sparse on new material, so when I found this updated OS I thought I should share it.
Lakka has a stable version from 2019 here http://le-builds.lakka.tv/Rockchip.ROCK64.arm/
However I found that they have a nightly which is current, and has a rock64 image under http://nightly.builds.lakka.tv/
Choose the date you want, and then R3328.

Hope this is useful to someone.

Couple of weeks ago a seller on Amazon had a bunch of the Rock64 board kits for $7.99 (SBC board, supply case and SD card) i got 4 of em and ive been trying all of the files in the downloads section.

I ran into an issue with one called "Android 9.0 Stock Image [eMMC Boot] using ROCKChip tools method [20190617]" 

The directions says to use the "android tool" put the board into maskrom mode with the jumper then when the tool sees the board pull the jumper off, then flash it. I kept having issues with errors when it went to "check" if the flash was ok it would error out. Then by accedent i downloaded a different version of the tool "2.65" and it actually worked i was trying different eMMc modules, differnt cables, i even thought maybe it was the USB3 and tried USB 2 then by accedent i tried the 2.65 and it worked.

The instructions give a link for version 2.38 and i tried and tried that version with no luck then by accedent i tried the 2.65 because i already had it on my PC from another device and i didnt know it was a different version

I just tried and failed to install foxitreader. Is there anything available?

Also, I get the impression I'm going to have to post on the forum like this for most pieces of software. I was pleased to find https://privacyshark.zero-credibility.net/# earlier as a source of compatible VOIP software. Are there similar places to go for other aarch64 Linux software?

Hello!
This is my first post here so please tell me if I'm breaking any rules.

I bought a PineTab and tried it out for a bit but felt like it wasn't quite for me. I feel like it will be in better use with someone else.

Price ~ 120$ + shipping.
I threw away the original box but everything else is included.
Shipping from Sweden, so I would prefer the buyer to be from Europe.

I think my account is too young to allow private messages so please reply here instead, as I made it to post this post.