| Welcome, Guest |
You have to register before you can post on our site.
|
| Latest Threads |
Weatherproof case build
Forum: Enclosures
Last Post: ltorsini
Yesterday, 07:01 PM
» Replies: 12
» Views: 38,473
|
Pinephone + Keyboard for ...
Forum: PinePhone Hardware
Last Post: PinePhoneProUser
Yesterday, 04:47 PM
» Replies: 16
» Views: 11,034
|
pinecil v2 dosent negotia...
Forum: General Discussion on Pinecil
Last Post: moses
Yesterday, 07:28 AM
» Replies: 0
» Views: 58
|
Pinephone software
Forum: General Discussion on PinePhone
Last Post: Csanderson0313
07-06-2026, 05:22 PM
» Replies: 2
» Views: 207
|
Rock64 v2.0 u-boot SPI is...
Forum: General Discussion on ROCK64
Last Post: ju0n
07-05-2026, 11:02 AM
» Replies: 0
» Views: 111
|
Libby - ebook reader that...
Forum: PineNote Software
Last Post: kiwigoldfish
07-04-2026, 04:41 PM
» Replies: 6
» Views: 4,059
|
PineNote v1.2 - Charges N...
Forum: General Discussion on Pinebook Pro
Last Post: ttsp
07-02-2026, 02:52 AM
» Replies: 0
» Views: 280
|
How to change the PineNot...
Forum: General Discussion on PineNote
Last Post: cameronharring
07-01-2026, 12:22 PM
» Replies: 0
» Views: 158
|
PinePhone Pro disable Vol...
Forum: PinePhone Pro Hardware
Last Post: FR_IV
07-01-2026, 10:53 AM
» Replies: 1
» Views: 1,618
|
Star64/Starpro64 kernel b...
Forum: General
Last Post: tgbgreen
06-30-2026, 12:17 PM
» Replies: 1
» Views: 2,230
|
|
|
| PBP disappointment |
|
Posted by: fenyo - 09-19-2020, 02:42 PM - Forum: General Discussion on Pinebook Pro
- Replies (22)
|
 |
Hi everyone!
Two days ago I got my loooong awaited PBP machine.
Turned it on, nothing happened. Put it away and did some reading about it. Then tried the second time and it started working. Filled in all the username/password/location, etc. things. Shut it down. Started up and of course asked me for the username and password. The username and password words are displayed on the lines of the boxes. Not in the boxes or outside of the boxes where the username and password supposed to be typed. To make the long story short, I tried every combination of usernames and passwords and obviously I can't go any further.
Downloaded the Manjaro file, etched it on a 32G SD card.
Opened the back of the computer, switched the switch to disable the emmc and plugged in the SD card.
Nothing happened.
I took out the emmc module and tried to boot it up from the SD card; nothing.
I have the usb to emmc module from Pine.
WHY is not available FROM PINE, the SAME file (Manjaro), they install on the emmc in the computer, when they make the computer ready to ship, so anybody could REPROGRAM the emmc if necessary, like I need to do it now?
At least that is my conclusion, to start all over.
So far, the US$199.00 computer cost almost $400.00 Canadian coins. I could of got FOUR Raspberry Pi for that price and I never had any series problem with the Pi, like I have with the PBP.
"High hopes"!
That is what I had when I first heard about the Pine book about two years ago. It was a long wait and now "splash". Great disappointment. Not even heavy enough to use it for boat anchor.
https://www.youtube.com/watch?v=faIeLL_1BeA
If anybody can help, please do so and thank you.
Needless to say, I am a beginner in the linux world. I looked and I couldn't find any file to copy into the emmc module. Is it available?
There are people who know their "stuff" but can't explain and unable to teach what they know to others and there are those who are great (I'll be nice), "explainers" but don't really know their "stuff". Both groups are useless to newbies.
|
|
|
|
| Elementary OS download |
|
Posted by: Paulie420 - 09-19-2020, 02:28 PM - Forum: Linux on Pinebook Pro
- Replies (15)
|
 |
Hey, two questions really...
1. Is there anywhere other than Elementary itself to download the Elementary Pinebook Pro version? Of course doing it this way I'd need to get the SHA signature to make sure its safe... but... Elementary makes you donate $10 per month in order to download the not-stable release versions. I may do this, so my next question:
2. Does anyone use Elementary OS on Pinebook Pro? Manjaro is awesome and I love it - but I do prefer a Ubuntu build. I like Armbian, but I really am just trying all of them out - and I couldn't get regular Ubuntu to unpack yet... must be some issue with my archiver. :/ So, I wanna try Elementary - Before I pay them, tho, as I really just wanted to try it out -- Does anyone use it and could tell me if its worth it to pay for?
Manjaro is really nice - and since its supported its hard to want to go anywhere else, but.... I still want to try.
|
|
|
|
| How to navigate |
|
Posted by: joz_mak - 09-19-2020, 12:27 PM - Forum: Mobian on PinePhone
- Replies (2)
|
 |
Hello,
I can't navigate when I open a file in nano because the on screen keyboard missing up and down arrows in mobian phosh flavor.
I tried several other flavors and I noticed that most of them have this feature.
Is it possible to install a keyboard with navigation arrows?
Thanks.
|
|
|
|
| Only enable modem when needed with kill switches |
|
Posted by: sokolgeo - 09-19-2020, 07:25 AM - Forum: PinePhone Hardware
- Replies (2)
|
 |
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
|
|
|
|
| Anbox on pinetab |
|
Posted by: saulrh - 09-19-2020, 06:36 AM - Forum: PineTab Software
- Replies (3)
|
 |
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.
Current status:
Code: mobian@thalia:~$ anbox session-manager
[ 2020-09-19 12:21:17] [client.cpp:49@start] Failed to start container: Failed to start container: Failed to start container
[ 2020-09-19 12:21:17] [session_manager.cpp:152@operator()] Lost connection to container manager, terminating.
[ 2020-09-19 12:21:17] [daemon.cpp:61@Run] Container is not running
Logs for anbox-session-manager.service are clean, so I have to hunt down the logs for the attempt to actually start the container. Either way, I called it a night there. Probably going to turn out to be an obvious-but-unfixable showstopper in lxc-on-arm64 or something equally obnoxious. Or, like, dbus blowing up for no reason. Maybe I'll keep tearing out attempts to modprobe unnecessary kernel modules until it all works. Or I'll just try arch! Who knows? The me of tomorrow, probably.
|
|
|
|
|