I have my new PinePhone Plasma for a short time. I was trying out multi-distro demo image.
I liked the feel of Mobian and I have some experience with Debian.
I did an apt-get dist-upgrade. It worked but after that I get a message, No WWAN Adapter Found.
I do not know how get back the WWAN Adapter and I have not anyone else with this.
Thank you for any help.
Silas

Hello All,

I have a Pinebook Pro running factory Manjaro. Every single time I reboot the system, the brightness is reset to 40%. I have to use the Fn+F2 key to manually adjust the brightness to 70%.

Does anyone have a solution so that the display brightness will be set at 70% every single time the system is started?

I searched online for hours. I didn't find a solution that works.

Thanks

Hi all,

When I got my pinecil, I powered it up to verify it works - it was on for less than a minute.  When I tried to use it tonight, it's completely dead.  It doesn't do anything when power is applied via barrel plug nor USB C.  Went to look into reporting to support, and the link from the page Warranty Policy - PINE STORE (pine64.com) goes to https://support.pine64.org/  - which gives a security cert warning.  Unsure how else to get ahold of Pine support.

I think I may know what the issue is - my power supply is set to 24 volts, which is what I've used with my TS100, and RC charging rig forever.  I've seen several places that say that the barrel plug can take 24v, but others that say 20v or 21v.    The wiki - Pinecil - PINE64 even says "Recommend operating voltage 12-21V, maximum rating at 24V"  right below "12V- 24V DC5525 Barrel Jack"

Anyway - did I overvolt and burn it up?  What specifically would i have burned (didn't open it up yet to look). Repairable?

I know that coherent_pool is a Linux kernel command line parameter, and it "sets the size of memory pool for coherent, atomic DMA allocations". I know it is specific to ARM ISA. I know it is set to 1M (1MiB) in bootloader config in Danielt's unofficial Debian installer script, and likely in most other Linux images/installers for PBP. I know in-kernel it defaults to 256KiB. I know (both from own experience and from some experienced Linux systems engineers) that various "performance tweaks" often times at best give marginal improvements or have a placebo effect, at worst can compromise system performance or stability or both. But at least for tweaks like vm.swappiness or the likes there are pretty clear consequences of changing their value either way. Even CMA (Contiguous Memory Allocator) has reasonably clear consequences of tweaking the value - too little and your device drivers for e.g. webcam may be unable to allocate enough RAM to work properly, too much is just pointless though shouldn't hurt your system (in practice it appears to be "eating" into memory usable by normal applications - e.g. when I experimented with very high CMA numbers my applications at some point started OOMing).

What I'm still puzzled by though through and through is coherent_pool - so far I have been unable to figure out what exact effect changing this value would have. It appears there is some interplay with CMA - e.g. if I set coherent_pool to 1M-8M and CMA at their default 64M things seem to work fine, if I drop CMA to 0 I easily get OOMs if coherent_pool is still set to 1M-8M, but system seems to work fine if I set coherent_pool or both to 0 (admittedly, haven't tried using webcam or any USB devices in that setup). So from that I conclude that coherent_pool actually needs CMA to work correctly, even if from https://lwn.net/Articles/479297/ it seems that CMA is a more recent development than coherent_pool. Some googling around shows that people run into some issues with certain drivers if coherent_pool is not set large enough (and especially if CMA is not enabled/large enough - one source had system complain about insufficiently big coherent_pool, and the issue was fixed by increasing CMA size instead), and some other sources claim issues if coherent_pool is set too large.

AFAIK there are some people working on kernel code around here, I am hoping that maybe some of them would know enough about kernel (as large of a knowledge area it is though) to provide some clarity on coherent_pool - what exactly is this setting for, how does it interact with CMA, why is it set by default to 256KiB if it (supposedly) frequently needs (does it?) to be tweaked to larger amounts, what is the effect of increasing or lowering its value too much?

Hi Everyone,

I have just gone through most of your documentation and I am interested in working with micropython on my PineTime dev kit. However, I seem to be having some difficulty updating the firmware. I currently am using IOS nRF Connect and attempted to update the firmware on my Pinetime. I make a successful connection and upload the micropython.zip  the screen shows a firmware update and it says image loaded ok. At this time it resets and reboots. The PineTime logo shows and it looks like it did when I first opened the package. I have just received this PineTime in Jan 2021 It says the version is PineTime 0.7.1 I'm starting to wonder if I have one that still has the flash protection turned on. Looking forward to learning how to develop for this.

So I've had a little more time today to play around with my BH running Mobian w/ Phosh.

One super irritating thing I'm finding is the frequency of hitting  the Phosh 'minimise' up arrow beneath the space bar of the OSK. I can handle other typos better as I'm watching what I type so can just backspace, minimising things by accident kills the flow.

So:

1. Do others suffer from this UX too?
2. Are there any tweaks currently possible to cirxumvent this short of using another WM?

Thanks,
Matt

Hello all, 
Pine 64 replied when I inquired about ordering that production is scheduled for March. Does that mean I should be pre-ordering right now? The store site doesn't allow me to place an order. Or will pre-ordering be possible in March? I'm confused about how this works. 

My aim for the PineTab is for watching news, podcasts, email, church, listening to online radio etc. 

Thank you.

Does anyone know if there is a solution for autodetecting if the Pine unit is a Pine A64+ or PineA64-LTS.

I would like to create a single (Armbian) image that can run on both units. I guess uboot should
contain a autodetect for knowing which kind of DTB to use on the board. I know the units have
some major differences like memory, network and emmc, but still hope this can be detected
and handled in a single image.

Hi, trying to create an account on Pine64's Zoho instance, as requested by the autoreply to the email I sent to support@pine64.org, however it is *broken* and unable to complete the sign up process as it falsely claims 'cookies are not enabled' when trying to set an initial password.

"Cookie is disabled in your browser. Please enable the cookie to continue."

I've tried with Chrome, Firefox, Safari on Desktop Linux and Windows as well as Ipad - it's just broken and there is now no way to file a support ticket as far as I know.

ps: My original support request is a query about when the Mobian edition Pinephone will be shipping as there is currently no information about this anywhere that I've seen.

Thanks,
Wes

Hello,

I have Pinebook Pro with Kali 2020.1 for ARM. I logs in with kali/kali for a while and I decided that I should change my password to a more secure one. So, I used command "passwd"

kali@kali:~$ passwd
current password:
Enter new password:
Retype new password:
passwd: Your password has been successfully changed.

And I changed it => "Your password has been successfully changed." and when I log in to terminal for recheck it works fine. But when I restarted it, I couldn't log in. Password is too easy. I couldn't forget him. I've tried to find tips on Google but most tips counts the grub and Pinebook Pro doesn't have it.

Thank you in advance for any answers.

PS: I tried to write to official Kali forum but for some reason they didn't post it to me. 
PS 2: Sorry for my english.