sábado, 8 de fevereiro de 2014

Galaxy S3 Mini storage and battery drain issues [solved]

by Ricardo Goldbach


Revisiting the Android scene after a sabbatical year, I replaced my dust gathering Xperia X10 Mini Pro (a nano device when compared to the name length) by a Samsung Galaxy S3 Mini. For starters, rooting a stock rom is nowadays a breeze. Among plenty of kits available out there I picked Mark Skipper's (includes Odin for ADB and an interactive shell script), well worth the donation.

Next step was to find out who "the man" was when it comes to porting CyanogenMod versions to particular devices (I miss Paul, a whiz-kid in the Sony Ericsson scene). Browsing XDA-Developers, I opted-in for Maclaw's porting shop. Older versions of Jelly Bean available, I took the memory lane up to the present, beginning with the Jelly Bean 4.1.2 (CM 10.0). Among a few bugs, some battery drain issues and the vicious "insufficient storage available" message after installing a few apps.

The S3 Mini doesn't allow moving apps to the external card, as the internal 8GB memory space is split in two halves, one of them being an emulated external memory card (go figure why...). Traditional apps (Link2SD and it's likes) can't do their tricks here: they don't know how to handle this anomalous external slot.

No remedy came out from browsing some forums; lots of naive suggestions as "get yourself a 32GB card", "wipe Dalvik cache" or "uninstall some apps" are there. The ubiquitous "reformat and reinstall everything" silver bullet also has lots of fans, but... no can do.

Good thing is both battery drain and insufficient storage issues have workarounds. Roy True posted an ingenious solution here as for the storage problem, and I solved my particular battery drain issue by myself, through managing a surfaceflinger service side effect, and also by some fine grain tuning provided by System Tuner. More on this later.

PS: I'll stick to the stable and responsive Maclaw's KitKat 4.4.2 (CM 11.0) despite the ever growing Google agenda on disregarding privacy issues. But... yes can do.

Edit:

A step by step solution for the storage issue can be found here.

Nenhum comentário:

Postar um comentário