I will be downgrading from PA 2.99 to PA 2.54 in hopes Jellybean 4.1.2 will play better with wifi. Does anyone know which Gapps should be flashed with it? And will I have to do a full wipe or will clearing cache and dalvik suffice? Thanks!
pottersam said:
I will be downgrading from PA 2.99 to PA 2.54 in hopes Jellybean 4.1.2 will play better with wifi. Does anyone know which Gapps should be flashed with it? And will I have to do a full wipe or will clearing cache and dalvik suffice? Thanks!
Click to expand...
Click to collapse
Go back from 4.2.x to 4.1.2 - unless I'm mistaken & stand corrected, it is necessary to do a full wipe, factory reset, wipe system , wipe cache partition and wipe dalvik cache before switching to PA 2.54, after making a (CWM) backup first.
I ran PA 2.54 myself briefly and used the recommended one: gapps-jb-20121011-signed
And, yes - PA and Kaos Droid under 4.1.2 have no issues with WiFi whatsoever, but - I'm back running rooted stock Rom with franco kernel, with a few tweaks, no lags and the added bonus of excellent standby battery life.
Letitride said:
Go back from 4.2.x to 4.1.2 - unless I'm mistaken & stand corrected, it is necessary to do a full wipe, factory reset, wipe system , wipe cache partition and wipe dalvik cache before switching to PA 2.54, after making a (CWM) backup first.
I ran PA 2.54 myself briefly and used the recommended one: gapps-jb-20121011-signed
And, yes - PA and Kaos Droid under 4.1.2 have no issues with WiFi whatsoever, but - I'm back running rooted stock Rom with franco kernel, with a few tweaks, no lags and the added bonus of excellent standby battery life.
Click to expand...
Click to collapse
Excellent info! I really wish I read this before bootlooping my device, looks like I'll be forced to full wipe . Luckily nothing really important was on the device.
What made you switch away from PA back to stock?
pottersam said:
... nothing really important was on the device. What made you switch away from PA back to stock?
Click to expand...
Click to collapse
Backing up is the key to flashing Android roms & kernels, we've all paid our "dues" in hard lessons on skipping or rushing without doing a proper safe.
I've flashed majority of the roms & kernels, some briefly and others ran for a while, more than a quick test drive or spin to get a real feel for whether it's for my device to meet my objectives - stability, reliability and good battery life/standby time without pushing it for speed/gaming, all of them are fast for Angry Birds. Tablet UI and landscape views are important, as long as the icons & fonts are "readable" - even with progressive lens at my age. PA is nice, and like several others, great with tablet UI but - except that it's not "easy" on the eyes for long period of time.
BAMF's Paradigm's 2.4.1 grouper rom is also great if you wanted to try it out, solid on 4.1.2 with many nice features - rooted stock rom with a custom kernel is a nice compromise, and best on battery life for my usage - down the road, when the 4.2.1 bugs are worked out in a future update, I would switch & upgrade to have the option of taking full advantage of all the Google Apps preloaded on the device.
Related
I'm on CM7 RC7.1 right now, thinking of flashing nightly 252. Can I just flash it right over, should I do a full wipe before flashing?
I've always done full wipes when flashing a new nightly or RC. Not sure if this is necessary and it's a pain to do the full setup everytime. Basically, wondering when it's okay to just flash a new nightly right over my current ROM.
TIA
You should be able to flash the nightly without a problem. As long as you're sticking to CM7 it SHOULD all work.
But, as always, make a backup of you ROM using Clockwork and your data using Titanium (Or whatever Apps you prefer) before you flash.
If it gets borked with the update, you can always just revert to the saved backup and start over with wiping the second time. Then you can reinstall everything easily using the data backup.
poprocks01 said:
I'm on CM7 RC7.1 right now, thinking of flashing nightly 252. Can I just flash it right over, should I do a full wipe before flashing?
I've always done full wipes when flashing a new nightly or RC. Not sure if this is necessary and it's a pain to do the full setup everytime. Basically, wondering when it's okay to just flash a new nightly right over my current ROM.
TIA
Click to expand...
Click to collapse
I was always told that if you are staying in the like OS you can just update. However if you are going from from one [format] to another you need to wipe.
meaning
RC --> RC : no wipe
Nightly --> Nightly : no wipe
Stable --> Stable : no wipe
rc --> nightly : wipe
nightly -- > official : wipe
and around the circle we go.
but the poster above me is 100% always do a back up before flashing anything.
neidlinger said:
RC --> RC : no wipe
Nightly --> Nightly : no wipe
Stable --> Stable : no wipe
rc --> nightly : wipe
nightly -- > official : wipe
and around the circle we go.
Click to expand...
Click to collapse
Interesting .....
According to this logic I would need to wipe since I'm going from RC to nightly. Irt appears the nightlies have stopped for the time being. Maybe something big is coming soon. I may wait to see ... Thanks guys!
I went from CM7.1 RC1 to various nightly builds, then back and forth between nightlies and gigglebread builds without doing any wipe at all, and everything seems to be working fine.
Of course, I am not sure if it will work for everyone and there may be issues hiding for me which I haven't yet had the chance to discover but most things that I use on daily basis (phone, messaging, e/gmail, 3G, Wifi, BT, cameras etc etc) are operational, and the only fc I ever had is waze (gps application) force closing immediately after booting (although it is definitely not on auto start list)- afterwards it just behaves normally.
I do nand backup and check its md5 (and of course for the rom I'm about to install).
a) Random reboots. We've all experienced them; Mine seem to come up quite often, no matter what rom I have installed. Whether it be CM7, CM9, MIUI, etc... it usually happens after returning from "sleep mode" (locking the screen)
b) Also, is there a way to make the nook run SMOOTH (for christ's sake...)??
I've tried V6 supercharger, and I haven't felt that much of a difference.
As for specs, I have my nook overclocked to 1200mhz, with the governor on "interactivex".
c) BATTERY LIFE. I've heard people using there nooks for quite a long period of time before needing to recharge.. is there any trick to this? I'm getting 3-5 hours of use on a normal day. It's supposed to have the same battery as the Nook Tablet... and same screen resolution.. sigh..
solutions anyone?
Thanks in advance.
Well, I'm currently running the MiRage rom and it runs fine. No random reboots. Do you use a time/weather widget? Sometimes these can cause occasional problems. I wouuld think it might be an app that is causing these problems, as I've used many roms on my nook, including MIUI, without the problems you are describing.
As for low battery, how high is your display brightness set? I have found that to be a big battery hog. Or again, it could be due to certain apps.
I would also suggest doing a clean install of your rom - wipe and reformat. If you are not sure of the procedure, please post.
My nook gets very heavy use on a daily basis and I get a full day after a nightly charge. Look for a thread in the general section for the nook by mr72 - a guide for CM 7.10 setup. Lots of useful info there.
Sent from my NookColor using xda premium
How many updates have you installed on your nook color? I have found that you should only update a few times before you will start seeing problems with your cyanogenMod builds.
CyanogenMod uses modified kernels so you should wipe both your data and your caches after a few updates to keep from corrupting your kernel base. Make sure to backup first with a nandroid backup so you can restore your apps and settings afterwards. Constantly re-flashing and updating your cyanogenmod builds just leads to problems without doing a full data wipe once and awhile. ALWAYS wipe your dalvik caches on each update.
The easiest way to wipe both your data and caches is to use clockworkmod in your included ROM manager.
~~~~~~~~~~~~~~~~
I have not experienced any of the issues you are claiming with the latest stable of cyanogenMod 7.2 on the nook color, but I make it a issue with myself to wipe both the data and the caches on the eMMC of my nook color , which is the way I am using cyanogenMod, after a couple of updates. YOU will especially will have to wipe both the data and caches when you upgrade from gingerbread ported versions of cyanogenMod to the ICS versions, those kernels are way modified. I have worked on some through the github.
I tried many CM7 nightlies and newer CM9 also.
Very rarely to have a restart (freeze up are bit more often) and battery lasts for 9–10 hours with full use.
Something might be wrong with your hardware or no good install of Roms.
How long do you have it? Did you get it new or used?
Produced by NookColor at ICS 4.0.4
Hello Friends,
I am having Red Lens Defy with 24/09 CM10 running on it. ROM is quite stable and working fie but I am facing Battery drops issues as well as heating issue for my handset. This is my only handset which i use for day to day usage.
I would like to go ahead with 2ndinit ROM by almighty Quarx but i am not willing to wipe my data for it. I have some concerns regarding ROM. I would appreciate if you can help me out...
1. Is it possible moving to 2nd Init ROM from 24/09 CM10 without wiping the Data? Have anyone tried? Are there any consequences doing so?
2. Is it recommended to Daily usage as this is my only phone. Anyone Tried with Airtel India(preferably Mumbai)?
3. Are there any issues noticed in 3G connnection(i use it daily)?
4. Can someone help me with steps to install this ROM without wiping data? Or is it same as upgrading nightlies?
Thanks & Regards,
Sameer
I try to change ROM s without wipe, for me it ends with a never ending reboot. u can try it, but the chance that it worked is not that good I think, just make a full backup before and if it fail restore it.
there is a free program on the PlayStore (appextractor) with that u can restore ur apps from a nand backup with there data.
Jelly powered.Defy
i went from 24.09 to 18.10 just wiping cache and dalvik cache without any problem, make sure to make a backup just in case and try it
So is it a daily usable ROM?
yes
Jelly powered.Defy
Hello all-
I've been bouncing around ROMs lately trying to find a fast and stable ROM to use as my daily driver, but the TW roms seem to all lag, and CM10.2 isn't giving me a reliable connection to my car's bluetooth. The most promising ROM has been a 4.3 Google Edition ROM (http://forum.xda-developers.com/showthread.php?t=2370205) except I keep getting a message when I try and use Google maps saying I need to enable GPS, although GPS is enabled. A quick reboot solves the issue and I am then able to use Maps. Does anyone else get this issue, or know if there is a solution?
Many thanks,
Jacob
edit: the problem also happens on CM10.2. The only common denominator I see is 4.3, but that is still just a guess.
when you're moving around ROMs, what wipe procedures are you performing? more specifically when transitioning between 4.2.2 and 4.3. what you're saying in your post is that a reboot generally fixes the issue which means it's not technically being caused by the ROM (code) but by an action before or after the install. cheers
xBeerdroiDx said:
when you're moving around ROMs, what wipe procedures are you performing? more specifically when transitioning between 4.2.2 and 4.3. what you're saying in your post is that a reboot generally fixes the issue which means it's not technically being caused by the ROM (code) but by an action before or after the install. cheers
Click to expand...
Click to collapse
Always the same process. In TWRP 2.5.0.2: Wipe Data, System, Dalvik Cache and Cache in Advanced Wipe. Then install the zip (and gapps if necessary) and reboot. Never had the problem with TW 4.2.2 Roms, and after posting, decided to give CM10.1.3 a whirl and see what happens.
Thanks for the help.
Hi, I have installed CM10.1.3 stable on my US Cellular XT901 electrify M. The ROM is same as for XT907. everything works fine until after few days my some of the apps specifically games starts freezing giving error ' process.system not responding' and game also force closes. After that every other game or browser like chrome start to Force close giving same error. I reflashed the ROM in clean way.
wipe data/factory reset
wipe cache
manual format system
mount system(tried without this step also, nothing changes)
flashed ROM zip
wipe dalvik cache
after activation reboot
flashed Gapps
Tried slim bean ROM build 7.1......having issues with musicFX and poweramp compatibility.
tried different 4.3 ROMS they all feel somewhat laggy.
So can anyone suggest me any solution for CM10.1.3? or suggest another 4.2.2 based stable custom rom.
Back up whatever you need to and reflash back to stock 4.1 using Matts Utility ( Look in Developement Section). Then download and read the instructions on how to flash Liquid Smooth. Its by far the smoothest and astest rom ive used on my Droid M. Except i cant get my bloody Whatsapp contacts to sink. Good luck.
I used liquid smooth and loved it... except batery life which sucked really bad!... it made my M's batery life feel as bad as my Galaxy Nexus was... Terribad!
..
I've tried AOKP and never looked back, batery life is awesome!
Also, big part of Liquid Smooth's slickness is due to the launcher it comes with => Nova Launcher.
Thanks for the reply.
can you provide the link for Liquid Smooth V2.9 because i have v2.8 and it is not working fine. Not able access quick settings menu!!
Does making Nandroid restore to stock 4.1 will help?