Hacker Read top | best | new | newcomments | leaders | about | bookmarklet login

Can this problem be solved by installing a custom ROM, such as CyanogenMod? I've only used Nexus Android phones, so am curious how to stay updated if using a phone from an OEM.


sort by: page size:

It's not an Android problem, as you only have the issue if you buy from a shitty oem.

Get a device with stock Android ROM and there is no issue


Use CyanogenMod. They detected this bug and issue updates all the time to phones no longer supported by their manufacturer.

As a OnePlus user, what can I do about this? Is there a well supported third party ROM (?) I can use?

Actually, lots of Android phones, including Nexus phones, have this problem, but none of them had a software fix shipped.

I've never had that issue with a Nexus line phone. I got OS updates the day they dropped from Google.

This is why I use Cyanogenmod. I get better support from a bunch of unpaid yahoos who like to dork around with phones than from the carriers and handset manufactures.

I am willing to bet Cyanogenmod will have a fix out in days, if not hours.

This goes for other ROMs like Paranoid too.

I refuse to buy hardware which isn't supported by the open-source community, such as Cyanogen.

If I don't 0wn it, I don't own it.


I've found I need to do a factory refresh every time there is an Android OS upgrade, because my battery life goes in the tank. ADB shows processes going crazy, trying and retrying to access things that are no longer there.

I've never had such issues with any of my Android phones, but it might be because i don't buy flagships and always run custom ROM

Funny that, my experience is quite the opposite.

Nexus 6P (Marshmallow); any time I lost phone signal the messaging app would get itself stuck in a tight loop until it had to be force stopped. You'd think they would have tested that on a brand new device..

Cyanogen Mod has been great in the past, as you say, to extend the life of old phones. Quite stable too.


I encountered this recently. Really exceptionally poor engineering for a communication device.

My solution: flash Cyanogen ROM, force all apps to install to the SD card. No more concerns about running out of internal memory.


TL;DR: not Android is the problem, but the vendor crapware. As a rule, always only buy Nexus phones.

Are you sure this is not only due to the fact that you've flashed a new rom (you say flash so it's not OTA, I suppose) so the system is freshly installed?

I should try it on my Nexus S that has become sluggish as hell (and I've tried different custom roms)


Have you tried clearing the cache from the debug screen? I had a similar problem with my old Nexus 5 that got fixed by doing that.

I have experienced that as well, but I feel it can usually be remedied by doing a factory reset. I also typically never do in-place upgrades for Android updates. I will download the full OS images (or the RUU/whatever updater is required for that brand phone) and do a full reset and restore. I will say for some reason this seems to be less of a problem on Sony Xperias that I have owned versus LG, HTC, Motorola, and others. But I for sure know what you're talking about.

I had that problem with my Moto G 4G. Found out that it wasn't the 1G of RAM causing this issue but the firmware. This was fixed in an update and seemingly broken again in another update.

I have the same problem and no real solution. FWIW I've been able to make my (mid-range android) phone last for 7+ years now by uninstalling some apps whenever memory becomes an issue. Also I update apps only when forced.

Interesting you blame Android that all your apps crash, when it is most likely CyanogenMod. I'm still running stock on my Nexus 7 and I don't get any crashes.

CyanogenMod's quality has gone down in the past few months. I'm running CM 10.1 on a Nexus 4. The home screen crashes occasionally and, after the most recent update, my ringer doesn't ring. Community QA is a tough problem.

You need to factory reset your device or maybe even reinstall the OS. I had the same issue with my Nexus 5 and Nexus 7 (2nd gen) and after doing factory resets after the update to 5.1.x, it was like I had a new device.
next

Legal | privacy