Leaderboard

Well though I'm personally happy with my Pro1 (still waiting for the Pro1X), but that does not mean that everybody has to feel the same. So I don't see anything wrong in someone trying to find a new owner for it, that hopefully like it better. Though I had considered moving them into one thread.

Found the below on the Mobian wiki, if you have the same files it's probably the same fix in Droidian 🙂

I want to sell mine, too. 8/256GB, QWERTY. The box is unopened. Anyone interested?

Dewit! 😉

You keep posting these "selling it" threads. Are you expecting a positive response, or what? Wouldn't be surprised if the mods lose patience, this is practically the opposite of constructive discussion.

This was happening to me on the PinePhone with Phosh. I found instructions for editing the Phoc.ini file to change the default number. I would imagine there is probably some similar ini file for Droidian, but don't know.

Hi. We(me+Ichernev) are currently messing around mainline kernel on Snapdragon 662. We are going to submit some base stuff pretty soon depending how maintainers will go on merging simple compatibles. However we are working on other devices, Redmi 9T(me) and Oneplus N100(Ichernev). While progress is going to be slow we will get there at some point, one of harder things will be Adreno 610 support due to no GMU but i hope this will be done by SoMainline for 665 SoC so we just can pick it.

If you want to run mainline Linux out of principle, I totally respect that. 👍 But, on the practical side: what do you think you would miss if you ran your favourite GNU distro in a container of Android, Sailfish or UBTouch, as proposed by @matf-kabouik or @Rob. S.? Many think of an Android/Lineage chroot or an UBTouch/Sailfish LXC as an "emulator" or a "virtual machine", and therefore have the gut feeling that any software installed in such environments would not be "really" running on their phone. That its speed of execution would be slower compared to the "host OS". That it would s

Got a response back, apparently it's something they are aware of and looking to come up with a patch very soon. So looks like it's a firmware issue, rather than a hardware issue thankfully.