fair enough, is it more efficient on
the battery?
On 31/08/14 16:38, Migel Wimtore wrote:
In my experience cyanogenmod offers many, many more
configuration options in Settings. Some of those settings I feel
are elementary and conspicuously absent from vanilla android.
For example last time I set up a vanilla nexus 7 (recently:
kitkat 4.4) for a friend, the lack of customisable Quick
Settings toggles was frustrating.
Also you get a reliable update schedule independent of Google,
your phone manufacturer or carrier.
On 31 August 2014 09:12:03 BST, Simon
Robert <simon.robert@xxxxxxxxxxxxxxxxxxxxxx> wrote:
Does cyanogenmod really offer
huge advantages on a nexus? For sure if I had a samsung
device I'd install it as there really is a lot of crapware.
I've thought about cyanogenmod on my nexus, but it really
doesn't seem to offer much over the basic nexus stuff except
cosmetic changes. If there is google supplied stuff you
don't want you can root and install titainium backup which
will allow you to freeze or delete any unwanted apps.
S
On 30/08/14 22:18, Migel Wimtore wrote:
"which is touch enabled like Phillz
so nice and easy to use"
Ironically I turn touch off in Phillz Touch
Recovery. The risk of tapping some destructive option
terrifies me. Much prefer volume up and down for cursor
and power/home for click. I just like being able to make
it look awesome in the customise settings. Lol.
On 30 August 2014 19:20:14 BST, bad
apple <mr.meowski@xxxxxxxx>
wrote:
On 30/08/14 19:04, Migel Wimtore wrote:
And by the way, I always wipe cache and Dalvik after I update
cyanogenmod. It may even be necessary.
AND I use the "wipe to install new ROM", or some such named option, in
Phillz, before installing a new ROM.
Awesome, loads more good advice from someone who has actually done this,
several times by the sound of it.
Just so you know, this is a standard Google Nexus 10 which is
manufactured by Samsung, and is most definitely a tablet rather than a
phone (although from the flashing standpoint, I don't imagine it makes
any difference: it's just an Android device).
Only took me a few moments to get back into recovery mode (using
recovery-clockwork-6.0.4.7-manta.img, which is touch enabled like Phillz
so nice and easy to use) and re-flash with cm-10.2.1-manta.zip which is
the latest stable version from a couple of months back. To my
surprise/annoyance, it has made absolutely zero difference and I'm still
looking at a suspiciously identical cyanogenmod loading screen. I would
have thought that the stable build particularly would have booted no
problem, so I'm suspecting operator error. Your advice about forcibly
wiping caches is jumping out at me, so this time I'll try Pillz and then
the same stable image.
I'm going to be really cross after all this if I end up getting a no-go
on cyanogenmod, and have to reluctantly fall back to a stock google
crapified version... This is actually more tricky than jailbreaking IOS
devices, to my surprise.
Thanks again,
Cheers
--
www.oldhouse-cottage.co.uk
--
The Mailing List for the Devon & Cornwall LUG
http://mailman.dclug.org.uk/listinfo/list
FAQ: http://www.dcglug.org.uk/listfaq
--
www.oldhouse-cottage.co.uk
|
