After receiving my PBP and tinkering with Manjaro (including fully updating the system) I decided I'd rather try out a more familiar distro so flashed @mrjay 's Ubuntu image; details here: https://forum.pine64.org/showthread.php?...0#pid68220
The battery was showing 20% when flashing completed however once the system powered down it will no longer power up. The power button does not appear to have any effect at all.
I've tried searching the forums here for similar issues and so far have tried:
Booting with / without A/C adapter plugged in
Booting with / without SD card inserted
Verified that A/C adapter is charging (light comes on, charges then turns off)
Verified the A/C adapters are working by charging a 2nd PBP that is still working
Removed the battery, connected the power bypass cable and attempted to power on with A/C adapter
Reseated the eMMC
Booting with / without eMMC hardware switch toggled
Nothing appears to have had any effect and I'm not sure what else I can do; any advice would be much appreciated
After dd my working Manjaro KDE 20.04 from SD card (mounted with an SD card reader at USB) to the emmc (by booting from a 2. SD card from card slot) the pinebook pro do not boot from SD card any more. I cant even mount SD cards from the SD card slot. Any idea how to get the card slot to work again (and then with booting SD cards first, before emmc)? Thx in advance!
Addendum:
The only SD card which mount is the SD card i did the dd from - this is also the only sd card the pinebook do boot from if inserted.
Hi,
as the pre-orders are sold out, I would like to buy a pine single board computer to get a feeling on how useable (or not useable) a pinetab would be.
Could please someone tell me which pine single-board computer I should buy to get the exact same performance as with the pinetab?
The reason behind this is that I am a school teacher and would like to try if the pinetab could be suitable foor school use.
In Germany, students are required to buy a very expensive graphic calculator for math. So firstly I would like to try how GeoGebra runs on pine Hardware.
So I've been fiddling with my phone, trying to get GPS working. From ModemManager, this is what I get after enabling NMEA.
Anyone else seeing this?
What exactly is required to get the GPS to actually work, since some people claim it works for them?
Used 'mmcli -m 0 --location-get' to produce output, after using --location-enable-gps-nmea.
Machine arrived yesterday. Very pleased with quality. Manjero set up with absolutely no problems. KDE seems unrefined compared to cinnamon, but I think it's safest to stay with what's known to work for now. Next step is figuring out how to make the M.2/NGFF adapter work. Need a bit more storage to make this thing a daily driver.
my PinePhone sets the current date/time to august 2115. Thats terribly annoying because you can't even surf the web without trouble with such an issue (cause TLS-certificates seem to be to old).
And I can't set a new date/time because the internal clock seems to stay with the old and wrong time. Sometimes rebooting helps, but not everytime. Sometimes I'll have to wait...
I had this problem 4 times since yesterday.
Do you know this issue?
Together with stability and heat issues I have I don't know if I got a faulty device. (I know sotware is under heavy development).
Been doing some basic testing on the battery.
Using dev 53 UBports and the battery life is indeed 13+ hours with near to zero screentime.
With crust, looking at a simple ping sequence the phone seems to enter sleepmode instantly when switching off.
Me testing the batterytime when off, but 'receiving' quasi push messages (a la GCM) ended here.
question:
Is there (on the middle long term) any idea how the system will provide a GCM alike TCP channel to have our own push messages ?
Maybe triggering the wifi modem the same way as the phonemodem, or with a on/off sequence.....
Unpacked , and wrote the img file to a Sandisk Ultra 32GB card w. etcher , no errors.
Inserted the SD in the PP , and did a started the phone.
When it booted, it asked for my "screen lock code" , and it was connected to my WiFi
Now i'm in doubt if it has booted from the SD card at all, if it doesn't use the eMMC , how does it know my Screenlock code & wifi passwd ??
I somewhat expected it to boot up as "Factory reset" , or ??
My SIM card was not working, i had to go to Cellular settings and select my "provider number" 23xxxx (Telia)
It was set to Auto , and 23xxx was listed below. Once i chose the 23xxx it connected to GSM , and showed Telia.
When i went into update settings - , and had a look it now shows stable, so something has happened.
And there was actually an update waiting, even though i just downloaded "latest" - Where's the SHA-Sum of the file !!!!
The update is named Ubuntu Touch Version 3 , and i think that's the old Dev 53 , that @Luke promoted to Stable 2 days ago.
I guess my question is does the OS/PP have some persistent storage where it saves Screen & WiFi pwd's ? Or does it "sneak read" from the eMMC, even if it is booted from the SD ?
Right now i'm updating my PP with the Stable 3 , that update said it found OTA.
More to come
/Bingo
Wutt !!
After updating with the OTA , and reboot.
It now seems to be Factory reset.
The first thing i'm asked after the reboot is to set Language
Yupp , i just went through a "Factory reset setup" , Lang,TZ,Screen-pwd, WiFi-pwd".
Strange !!! , is this intended behaviour , or just a "Quirk" ??
I downloaded Teleport (telegram) , and gets the verification code via sms , but it wont accept it.
I didn't see that issue on the eMMC install , but it could be app related.
Edit: On 2'nd try & SMS , it registered , even if it still said the sms code was too long
Well giving stable 3 a go today, and prob switch to Devel in the afternoon.
Once again thank you for your efforts
/Bingo
Hmm ....
Code:
root@ubuntu-phablet:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
mmcblk2 179:32 0 14,7G 0 disk
├─mmcblk2p8 179:40 0 2,4G 0 part
├─mmcblk2p6 179:38 0 63,9M 0 part
├─mmcblk2p4 179:36 0 64M 0 part
├─mmcblk2p2 179:34 0 1M 0 part
├─mmcblk2p10 179:42 0 8,6G 0 part
├─mmcblk2p9 179:41 0 2,4G 0 part
├─mmcblk2p7 179:39 0 63,9M 0 part
├─mmcblk2p5 179:37 0 64,3M 0 part
├─mmcblk2p3 179:35 0 8M 0 part
└─mmcblk2p1 179:33 0 1,9M 0 part
mmcblk0 179:0 0 29,7G 0 disk
├─mmcblk0p9 179:9 0 2,4G 0 part /
├─mmcblk0p10 179:10 0 8,6G 0 part /userdata
├─mmcblk0p7 179:7 0 63,9M 0 part
├─mmcblk0p5 179:5 0 64,3M 0 part
├─mmcblk0p3 179:3 0 8M 0 part /android/persist
├─mmcblk0p1 179:1 0 1,9M 0 part
├─mmcblk0p8 179:8 0 2,4G 0 part /android/cache
├─mmcblk0p6 179:6 0 63,9M 0 part
├─mmcblk0p4 179:4 0 64M 0 part /android/boot
└─mmcblk0p2 179:2 0 1M 0 part
mmcblk2boot1 179:96 0 4M 1 disk
mmcblk2boot0 179:64 0
