![]() |
My list of noticed driver issues - Printable Version +- PINE64 (https://forum.pine64.org) +-- Forum: PinePhone (https://forum.pine64.org/forumdisplay.php?fid=120) +--- Forum: PinePhone Hardware (https://forum.pine64.org/forumdisplay.php?fid=122) +--- Thread: My list of noticed driver issues (/showthread.php?tid=10552) |
My list of noticed driver issues - Subsentient - 07-04-2020 So obviously things aren't complete, but I thought I'd post a list of the bugs I'm seeing with PinePhone drivers right now, since I know some PinePhone kernel developers read this forum, and hopefully some people in ModemManager and Librem5's dev team too, since I use their "Calls" app. This doesn't include stuff like the camera, which just isn't working anymore on recent kernels. I'm using Fedora 32 with XFCE on a 5.7 megous kernel.
RE: My list of noticed driver issues - bcnaz - 07-04-2020 ALL of the OSes are in heavy development still, however I do not think every OS has all the problems you listed. I do see a trend of more modem problems reported on CDMA than on GSM carriers. * (Maybe more developers test with GSM ? ) Charging problems seem to vary with distros, You did mention your Distro, but not your carrier.... RE: My list of noticed driver issues - Subsentient - 07-04-2020 (07-04-2020, 05:14 AM)bcnaz Wrote: ALL of the OSes are in heavy development still, however I do not think every OS has all the problems you listed.I'm on Consumer Cellular, which uses T-Mobile's GSM towers. Yeah, I imagine some of those bugs are in userspace and specific to generic distros, Ubuntu Touch for example might behave better with some stuff. In addition, yeah I'm probably the only one running generic non-phosh, non-rawhide Fedora on a PinePhone right now, so I do expect I'll have to figure a lot of things out for myself, which I have. RE: My list of noticed driver issues - megous - 07-07-2020 - HDMI lag is probably you having GPU enabled. I don't see any lag on Xorg with noaccel option enabled. - 92% capacity max on my kernel may be related to the voltage you choose to charge to (4.35V max, 4.2V default) - charger behavior is normal, it should start charging again after a while by itself, and keeping the battery at 100% all the time is not that good for the battery - modem audio reliability probably depends on which side of the i2s link is the master and some other factors. earlier modem was configured as master, which needs enabling/disabling some audio controls just after call starts and this should be not necessary with SoC being made the i2s clock master (not sure which variant you/your distro uses) - SMS messages loss is just about design decisions in the modem software. Personally I prefer to set up the modem to accept and store messages, and then sync them to some other storage before deleting them, but I think ofono relies on being able to receive messages directly without involving modem storage. So if ofono fails at this one shot to receive the message, it's lost permanently. Maybe ofono has some switch to use the mode of receiving messages with intermediate storage in the modem. I don't use ofono, so I don't know. This is doubly the issue since the signal that tells the modem to hold up messages until SoC wakes up from sleep is only wired up on PP 1.2. I have no idea if any of the distros use this signal (AP_READY). Dunno about the rest. RE: My list of noticed driver issues - wibble - 07-07-2020 Elaboration on the GPS signal strength, and why it might be fixable with driver of devicetree changes: https://forum.pine64.org/showthread.php?tid=10356&pid=70116#pid70116 |