Yes, I also expect that it is far more likely that a defective battery is to blame, plus the batteries should have protection circuitry built-in anyways. Based so far on what I have read (There is some BAD information out there!), there is some handling of this information by Android, so I will figure it out before I reattempt. The Android batterystats.bin information is surviving the flash into UT somehow, because the battery life is in the ballpark of being similar between an Android and UT system. Or maybe it isn't being preserved and it is part of the reason everyone complains about battery life? It would be interesting to hear a battery replacement success story. A possible solution would be to replace the battery and perform a few discharge cycles under Android before reflashing as it is a very infrequent event. Anyway, I have put the original battery back in, and everything is running smoothly now. I plan on reattempting this in the near future, but I will try to buy a more expensive knock-off this time.

I'll post a pic of my device, just need time to stage it and take it I'll do a couple (with and without desktop mode) bare in mind my port isn't complete

@cibersheep Roger that! someone has to approve my PR anyway in case I really get a proper implementation :)

GSettings values: $ gsettings list-recursively com.ubuntu.touch.sound com.ubuntu.touch.sound incoming-call-sound '/usr/share/sounds/ubuntu/ringtones/Ubuntu.ogg' com.ubuntu.touch.sound incoming-message-sound '/usr/share/sounds/ubuntu/notifications/Rhodes.ogg' com.ubuntu.touch.sound silent-mode false

It sounds like maybe there's been an issue with the notification, perhaps due to the staged release nature of the OTAs.

The value you see from /proc/ is the default value, and it is 7200 seconds. Setting it to a much lower value would not solve whatever issue it is you're having. More than likely, the router (or DHCP server rather) is renewing the IP lease, which is probably resulting in a new IP address or other disruption to any active connections. Or there is some other problem.

It is highly unlikely that we would be able to redistribute those apps, @Krille. A good idea, but probably a legal headache. :)

Try "touch frameworks/base/packages/SettingsLib/common.mk" it says that file is missing

I am testing sprint on my Nexus 5 (16.04 RC). I like this desktop very much at least because there is a structure possible and icon packs can be used. Here some suggestions for next steps: It would be nice to swipe left on this desktop to have than browser bookmarks to start directly web pages (like we had it in 15.04 with the bookmark browser). Or maybe something like a double screen. And probably bookmark icons should be smaller than app icons (5 icons in one row). I would like to change text size separately (because they overlap) It would be nice to change the place of the icons on the screen. Actually I can place them only at the first time when adding to the desktop. Is it possible to autostart sprint? (and maybe autohide standard 'Anwendungen'?)

@custello just search for it on open-store.io, but there isn't one I think. anyway, you can easlily make a webapp using webapp creator on Ubuntu Touch for that website

@grepo Same for me.

@ubportsnews also https://tuxdigital.com/2018/12/episode-46-this-week-in-linux/

@davidcolombo Maybe we can even request Twitter verification badges for the Accounts We've been working on this for all of our accounts, but they require official (read: government) documents of ownership. Since the Foundation is still being applied for, we have none of these.

@blandcorporation I have no knowledge of the pro 5 and not seen this before. But, one thing you could try if your not on the dev channel is update to that first and see if that helps. Dev will give you the latest updates for your device just incase it has been fixed already. If you are already or it doesn't we will need help from someone else.