i'm running cm7 nightly with latest radio, wimax, 1.90 pri and nv. everytime i flash a kernel my phone gets stuck at white screen and will not allow a nand restore whatsoever. my battery life is terrible even if i try pri 1.7 and nv 1.7.. wiping never helps.. why is this happening? any ideas???
Probably because you are doing something wrong. Just like this thread you felt compelled to start. You know you could ask this question in the CM7 thread or even the question and answer forum...
Ok now that that has been said what kernel are you trying to flash?
Sent from my PC36100 using XDA App
i placed the same question over on cyanogen forums and got no help. i was using cm7 nightly build 8. I wiped then flashed sz 0.0.9 no sbc kernel and 30 minutes later froze, rebooted and still stuck at white screen. Booted into recovery and only got amon_ra_1.8 never loaded. So i had to put the pc36 file on my sd card via laptop and managed to go into hboot that way. Let it update itself then reflashed cm7 nightly #8. Was working smoothly except for battery life which is why i did a back up and tried netatchy_toast_4.2.3. That worked a few hours and landed me back at frozen white screen with a nand backup that kept giving me a flash error. After 3 tries the backup loaded and thats where i'm stuck at. I think i'm about to flash cm7 build 12, the latest, see how it works, then give a shot to another kernel. Any ideas?
Yes. It's a nightly build. It's unstable, and no one is going to help because it's almost impossible to troubleshoot.
also netatch's kernels are for sense roms. Use an AOSP kernel.
Try the kernel in my sig. Seems to work pretty well.
tried to post in cm7 thread but got a "new user" warning saying i dont have enough posts to post in that area. so i had to start at the noob level..
HipKat said:
Try the kernel in my sig. Seems to work pretty well.
Click to expand...
Click to collapse
Im gonna give that kernel a shot if nightly 12 still sucks up my battery. Only thing is, thats the same kernel that got me frozen the first time lol. Maybe it will run better with nightly 12?
Do a full wipe of system, boot, data, and cache, then flash just the ROM and GApps package. If you still have issues, get a logcat, and post in the CM7 Nightly thread here.
sounds like a plan. just got done flashing #12. Colors in notification bar stay white sometimes now lol. I wiped first then flashed. Read somewhere you didnt have to wipe if flashing 12 over another nightly. Wiped regardless, just throwing it out there..
oh, do i need to reflash pri and nv or are they not an option for nightly builds? tried them once before and pri never showed up.
cm7 nightly #12 seems to have helped battery life alot. Taught my daughter to ride her bike, went to movies and saw "Rango", stopped by walmart, came home, battery remained strong. On nightly #8 it was dead in 3 hours. #12 seems like a winner so far!! Not sure what pri and nv come in #12 or if they need to be reflashed or which one i should flash if they remain old etc... etc... Thanks in advance for any help!!
quickstang1 said:
Not sure what pri and nv come in #12 or if they need to be reflashed or which one i should flash if they remain old etc... etc... Thanks in advance for any help!!
Click to expand...
Click to collapse
There are NO PRIs / PRLs/ NVs, or any of those things. Those are never part of any rom flash. Those are either flashed separately, or obtained through a sense ROM via profile or prl updates.
Also, even though you are thinking things are fine with your current build, I am curious what recovery you are using... and what is your HBOOT. are you forever S-OFF?
using amon_ra 1.8, unrevoked forever. Cm7 nightly #12 is kickin a$$!!! No reboots, no battery drain, no weird glitches.. Stock kernel, cpu set at "performance", unplugged from 8am to 4 pm, using internet all day, wimax on, 3 weather widgets running, made it all that time and still had 15% battery left... Not sure what was changed in 12, but its a definite keeper!!!
Related
Weird issue...
Doesn't matter which rom, when I'm not on stock, my phone will freeze...
I have used odin and flashed one click root, clockwork mod then installed different kernels, roms and with same result. It will freeze eventually until I pull the battery... am I doing something wrong here?
I mean, I completely wiped using Odin so I don't see the residual thing here.
And in case there are, I wiped data, cache, dalvic prior to flash or followed chefs instructions to the T.
Am I the only one that's experiencing this? (probably am T_T)
Any inputs would be appreciated.
Same here. I've found that its the custon kernels that cause it. I just flash the rom I want and then flash the stock kernel back.
Sent from my Epic 4G using the power of the Holy Spirit
Hey, thanks for writing to confirm. good to hear that I'm not the only one but sucks to be one of the few...
I have done multiple wipes, cache clearing (both cache and dalvik)
Gone fresh from di18 fresh install, rooted and unrooted (I heard that old 1 click conflicts with genius dog's kernel) I have come to conclusion that it's the under voltaging that's the culprit here... I may be wrong but what kinda grinds my gears is that why is that only you and me are having these issues?
I'm using Andromeda kernel and it seems to be stable for me.
Any ways around this ??
I just recently started having this problem. I never had it until the day I flashed bakedsnack 1.3. The ROM is wonderful besides the occasional freezing. I usually freeze up about 2 times a day and have to pull the battery. This ROM does use a custom kernel though and I was OC'd to 1.3ghz but reflashed and went to 1ghz and still freezing.
Have you tried OC kernel before? i.e. genius dog's kernel. (not dogging Genius dog or anything. I'm naming his because his kernel is most widely used and I'm dying to use it.)
Just want to try to eliminate the culprit here lol.
Also try flashing andromeda kernel and see if your problems persists because I'm having no problems however my mflops will never go over 8.5 T_T
I've tried Myns, Cjs nonsense, and now MikFroyo and all 3 have had awake time and up time be exactly the same. I check it before I install any apps so I know it's nothing I've installed that's keeping it up. I can literally see the battery drain as I look at it. The last 2 things I can remember doing that might have caused this are flashing HTC kernel #15 and flashing the alternate #15 kernel by netarchy. But shouldn't flashing a new rom flash it to whatever kernel it's using? I really need to figure this out
EDIT: I've tried wakelocks on titanium before anyone suggests that. And I was debating between this and Q&A, but my pleas in Q&A usually go unanswered so I went here
Since you flashed HTC #15 I am going to assume you are using 3.70 based roms.
I'm assuming because you failed to mention this bit of info. You also failed to mention your radio/pri versions.
Based on my assumptions you probably flashed a 3.70 based rom and then flashed the updated radios/pri.
If this is the case try this:
1. Boot into recovery (I use amon and my instructions pertain to it)
2. Wipe everything (sd card is up to you) - cache/data/dalvik
3. Then do a factory data reset wipe (again this option is in amon)
4. Flash the most recent radio combo from calkulins thread (pri 1.90)
---DO NOT REBOOT AFTER FLASHING THE RADIO COMBO--
5. After the radio is flashed, install a 3.70 based rom that has HTC #15 as its kernel
6. When the rom is installed have it boot up
7. Ensure all radios are off (wifi, wimax, mobile data) and check your up/awake time after letting it sleep for about 5 - 10 minutes.
8. If your up/awake time does not match THEN you can flash another kernel provided you are on hardware version 003 or earlier WITH the old camera chip.
These are the steps I took to fix this issue. YMMV.
Zori said:
I've tried Myns, Cjs nonsense, and now MikFroyo and all 3 have had awake time and up time be exactly the same. I check it before I install any apps so I know it's nothing I've installed that's keeping it up. I can literally see the battery drain as I look at it. The last 2 things I can remember doing that might have caused this are flashing HTC kernel #15 and flashing the alternate #15 kernel by netarchy. But shouldn't flashing a new rom flash it to whatever kernel it's using? I really need to figure this out
EDIT: I've tried wakelocks on titanium before anyone suggests that. And I was debating between this and Q&A, but my pleas in Q&A usually go unanswered so I went here
Click to expand...
Click to collapse
This issue if you are on 3.70 Rom is a known issue. There is no direct solution as not all have experienced it. I can't concur with what's said above my comment because I have not had the issue but I can say all devs have said to do is after a charge take it off the charger and reboot..
Sent from my PC36100 using XDA App
Uninstall Wireless Tether. Reboot. Let the phone sleep. I have 370 and my phone sleeps perfectly.
What PRI are you running? Try going back to 1.77_003 and see if that fixes it. At least with some ROMs, the current version of the PRI is causing this. You can leave everything else as is.
lovethyEVO said:
Since you flashed HTC #15 I am going to assume you are using 3.70 based roms.
I'm assuming because you failed to mention this bit of info. You also failed to mention your radio/pri versions.
Based on my assumptions you probably flashed a 3.70 based rom and then flashed the updated radios/pri.
If this is the case try this:
1. Boot into recovery (I use amon and my instructions pertain to it)
2. Wipe everything (sd card is up to you) - cache/data/dalvik
3. Then do a factory data reset wipe (again this option is in amon)
4. Flash the most recent radio combo from calkulins thread (pri 1.90)
---DO NOT REBOOT AFTER FLASHING THE RADIO COMBO--
5. After the radio is flashed, install a 3.70 based rom that has HTC #15 as its kernel
6. When the rom is installed have it boot up
7. Ensure all radios are off (wifi, wimax, mobile data) and check your up/awake time after letting it sleep for about 5 - 10 minutes.
8. If your up/awake time does not match THEN you can flash another kernel provided you are on hardware version 003 or earlier WITH the old camera chip.
These are the steps I took to fix this issue. YMMV.
Click to expand...
Click to collapse
Wow! This worked like a charm man, thank you so much!
lovethyEVO said:
1. Boot into recovery (I use amon and my instructions pertain to it)
2. Wipe everything (sd card is up to you) - cache/data/dalvik
3. Then do a factory data reset wipe (again this option is in amon)
4. Flash the most recent radio combo from calkulins thread (pri 1.90)
---DO NOT REBOOT AFTER FLASHING THE RADIO COMBO--
5. After the radio is flashed, install a 3.70 based rom that has HTC #15 as its kernel
6. When the rom is installed have it boot up
7. Ensure all radios are off (wifi, wimax, mobile data) and check your up/awake time after letting it sleep for about 5 - 10 minutes.
8. If your up/awake time does not match THEN you can flash another kernel provided you are on hardware version 003 or earlier WITH the old camera chip.
These are the steps I took to fix this issue. YMMV.
Click to expand...
Click to collapse
Very interesting... I have ready many people with similar problems, and most everyone who went back to 1.77 PRI also fixed the problem. Is this the same issue that can be resolved by your information?
From what I can see in your post, the key is not to reboot after flashing the PRI/radio, immediately flash the ROM, and have everything boot together?
Thanks. I have high hopes for this...
Try running a rom that is based on the 3.70 OTA, i've had an issue where there is 100% awake time when it's on either an AOSP rom or lower than 3.70
mrono said:
Try running a rom that is based on the 3.70 OTA, i've had an issue where there is 100% awake time when it's on either an AOSP rom or lower than 3.70
Click to expand...
Click to collapse
I, like many others, are seeing 100% wake with 3.70 OTA-based ROM and kernel 15. For every post that I have read, including myself, reverting to PRI (only) to 1.77 solves the problem.
I even remember reading a case where the person got 3.70 via OTA and had the same problem, which is truly puzzling.
From my last post in this thread, I am now curious wether the load order (radio/PRI/ROM) makes a difference. At the same time, I have read others where they load things out of order (ROM first, boot, then PRI/radio) and do not have any problems.
snovvman said:
Very interesting... I have ready many people with similar problems, and most everyone who went back to 1.77 PRI also fixed the problem. Is this the same issue that can be resolved by your information?
From what I can see in your post, the key is not to reboot after flashing the PRI/radio, immediately flash the ROM, and have everything boot together?
Thanks. I have high hopes for this...
Click to expand...
Click to collapse
snovvman said:
I, like many others, are seeing 100% wake with 3.70 OTA-based ROM and kernel 15. For every post that I have read, including myself, reverting to PRI (only) to 1.77 solves the problem.
I even remember reading a case where the person got 3.70 via OTA and had the same problem, which is truly puzzling.
From my last post in this thread, I am now curious wether the load order (radio/PRI/ROM) makes a difference. At the same time, I have read others where they load things out of order (ROM first, boot, then PRI/radio) and do not have any problems.
Click to expand...
Click to collapse
I was actually the one who suggested to revert to pri 1.77 as that fixed my issue at the time.
I had set out to find how to have all the updated radios and not have a wake issue. I went through the trouble of flashing each radio independantly on a fresh 3.70 installed over all old radios.
So in one instance I had all old radios, installed 3.70, after boot install new baseband radio but keep everything old (wimax,pri, etc).
I did thus for each radio (install 3.70 over old radios and update one radio) so I had one install with old wimax and pri but new baseband, old baseband and pri but new wimax, etc.
It would always have the wake issue when I would flash all the new radios and pri AFTER the install.
I found the method I posted above to work for me after wanting ti have all my radios updated and not have a sleep issue. It worked for me so ymmv.
lovethyEVO said:
I found the method I posted above to work for me after wanting ti have all my radios updated and not have a sleep issue. It worked for me so ymmv.
Click to expand...
Click to collapse
I will try this when I'm ready to wipe the current ROM and report back. I do hope it works. Thanks.
Besides running a rom based off 3.70, before u go to the extreme, boot your phone, give it like five minutes for everything to load up all the background apps etc. screen off for like a min and then check battery and see if its sleeping. If not, update profile, then screen off for another minute. I've been flashing roms like crazy for the past week and would get the same problem. I noticed after flashing a new rom, it takes a couple minutes for your phone to settle down, sometimes it requires a profile update. If that still don't work, reboot (just in case the profile update requires it.) And then check.
This only fixes the problem for a day or so. I followed your instructions to the letter, downloaded zero apps, and the issue just comes back.
Still having this problem (Awake Time is 100% alive time), Please help, I have tried everything!
Currently I have tried PRI 1.77 003 and 1.90
My ROM is rooted OMJ's EVO 2.2 FroYo v4.6 Deodexed w/ Stock Kernel
Android Version 2.2
Baseband Ver 2.15.00.09.01
Kernel Ver 2.6.32.17-gee557fd [email protected] #15
Build # v4.6 Deoxed
Browser Ver Webkit 3.1
PRL 01115
I have removed WIFI Tether, no luck, updated Profile, No Luck
PLEASE Help
I hope that this isn't a repost, I've searched quite a bit but nothing is exactly like what i'm experiencing.
Here's what happened, i'll try and make this short and to the point.
Got my new evo, rooted it using unrevoked 3 and got root access.
Loaded a few custom roms, no problem, finally settled on Calkulin's EViO rom. Everything was working great, 4G was perfect, blah blah blah, buddy with an evo told me that Cyanogen was the poo and that I had to flash to that as it was the best ever.
I download Cyanogen 6.1.2 from cyanogen's forum and proceeded to flash it to my phone after doing a nand backup on my current rom. I forgot to back up my RSA keys (didn't even know i had to in the first place) and after cyanogen loaded, I read the thread that states that flashing cyanogen make screw up your wimp key and that you should backup your RSA keys (crap!) before loading cyanogen. Well after reading this and freaking out, I went back into recovery, wiped everything, and loaded the recovery img of the last rom I was running on my evo.
Now my 4G doesn't work in calkulin (posted a thread about that a couple days ago), and I'm not able to load any rooms except for backups, a fresh copy of calkulin, and a fresh copy of cyanogen 6.1.2.
When i try to load a new rom (warm 2.2 for example), it'll load, but when i go and reboot, it'll sit at the white HTC EVO screen forever .. nothing will change until I pull the battery out and start the phone back into recovery. I can reload one of my old backup images and everything works fine again.
I've cleared all the memory, delvik cache, everything. I even formatted my SD card after backing it up and loading just the roms on there. that didn't help either.
Any help would be fantastic .. I'm completely floored as to why I can't load anymore rooms.
Also, i want my wimax back!
wow.. sorry.. i hope someone can help you.
but I would think, you have to call sprint. they may have the wimax info for your phone.. and how to put it back.
for my knownledge... how do you get the information RSA keys and wimax info.. so I can backup mine?
Here's how to backup your RSA keys
http://androidforums.com/evo-4g-all-things-root/248586-question-how-backup-wimax-rsa-keys.html
And issue is resolved.
amon recover > clockwork
4G is working now too. wewt.
thanks..
that is great you got it done.
I dont use clockwork.
dizzle247 said:
I hope that this isn't a repost, I've searched quite a bit but nothing is exactly like what i'm experiencing.
Here's what happened, i'll try and make this short and to the point.
Got my new evo, rooted it using unrevoked 3 and got root access.
Loaded a few custom roms, no problem, finally settled on Calkulin's EViO rom. Everything was working great, 4G was perfect, blah blah blah, buddy with an evo told me that Cyanogen was the poo and that I had to flash to that as it was the best ever.
I download Cyanogen 6.1.2 from cyanogen's forum and proceeded to flash it to my phone after doing a nand backup on my current rom. I forgot to back up my RSA keys (didn't even know i had to in the first place) and after cyanogen loaded, I read the thread that states that flashing cyanogen make screw up your wimp key and that you should backup your RSA keys (crap!) before loading cyanogen. Well after reading this and freaking out, I went back into recovery, wiped everything, and loaded the recovery img of the last rom I was running on my evo.
Now my 4G doesn't work in calkulin (posted a thread about that a couple days ago), and I'm not able to load any rooms except for backups, a fresh copy of calkulin, and a fresh copy of cyanogen 6.1.2.
When i try to load a new rom (warm 2.2 for example), it'll load, but when i go and reboot, it'll sit at the white HTC EVO screen forever .. nothing will change until I pull the battery out and start the phone back into recovery. I can reload one of my old backup images and everything works fine again.
I've cleared all the memory, delvik cache, everything. I even formatted my SD card after backing it up and loading just the roms on there. that didn't help either.
Any help would be fantastic .. I'm completely floored as to why I can't load anymore rooms.
Also, i want my wimax back!
Click to expand...
Click to collapse
dizzle247 said:
Here's how to backup your RSA keys
http://androidforums.com/evo-4g-all-things-root/248586-question-how-backup-wimax-rsa-keys.html
And issue is resolved.
amon recover > clockwork
4G is working now too. wewt.
Click to expand...
Click to collapse
Glad you got it working bro. Just for everyone that is new who may read this thread Cyanogen DOES NOT break your 4G keys. Older versions of Clockworkmod Recovery will. Follow the how to backup your RSA keys before doing Anything with the EVO.
Just because 4G is not yet included in Cyanogen Rom's does not mean it breaks your 4g. In fact, thanks to some of our dedicated and smart devs there is an actual Alpha of CM 6.1.2 with 4g and from what I hear it works pretty damn good.
Anyway I just wanted to clear that up because I would not want anyone to think that CM Rom's break your 4G. I am sure the OP meant Clockworkmod Recovery, but said CM in a rush to try to figure out his problem.
housry23 said:
Glad you got it working bro. Just for everyone that is new who may read this thread Cyanogen DOES NOT break your 4G keys. Older versions of Clockworkmod Recovery will. Follow the how to backup your RSA keys before doing Anything with the EVO.
Just because 4G is not yet included in Cyanogen Rom's does not mean it breaks your 4g. In fact, thanks to some of our dedicated and smart devs there is an actual Alpha of CM 6.1.2 with 4g and from what I hear it works pretty damn good.
Anyway I just wanted to clear that up because I would not want anyone to think that CM Rom's break your 4G. I am sure the OP meant Clockworkmod Recovery, but said CM in a rush to try to figure out his problem.
Click to expand...
Click to collapse
thanks for clearing that up .. I'm not sure exactly what I read as I glanced over it and freaked out because I didn't want to ruin my wimax keys .. so thanks for the clarification.
I've been trying to install the 6.1.2 with wimax but I keep getting hung up on the white evo screen, as well as others .. I'm tempted to install CM7 and forget about 4G for the time being as I know toast will get it up and running in the upcoming months.
Hopefully someone can figure out the reason as to why the wimax alpha is hanging at the htc evo screen after installing the kernal.
Hey I would have posted this on a different thread but i cant because i just made this account they want atleast 10 posts...
heres the deal... i have a rooted evo and running cm7 which i like, but i was dropping calls and where i live i should have good service. so i got the updated radio/wifi/ ect package and flashed it... it installed but did not help with the call issue... i heard many other having the same problem.
so i flashed the ota root update... which seemed like it did it really fast (wasnt watching the whole time) and the phone rebooted but gets stuck at the white htc evo screen, i let it sit there for 20 mins nothing, so right now i am recovering my old cm7... just wondering if anyone has that same problem or can help with getting better voice reception on cm7.. like i said i have tried the package for radio ect... and my prl was updated before i flashed to stable of cm7 so that should be in good standing i would imagine... thanks..
The obvious first question is, did you do a full and complete wipe of everything before you flashed the ROM?
As far as your signal, it may have been just in my area, but I know a few people that had problems texting and making calls, getting a "Network Is busy" error.
yea i did the wipe data/cache i wasnt dropping calls before the cm7 so im not sure right now im shootin to myns seeing how that is... cm7 was first flash i did
well as im trying to flash to the myns its looking like the samething... ill go through the steps...
have zip file in root of sd card
open up rom manager, have the newest clockwork thing installed
i goto flash from sd wipe data and cache are checked... i already have a backup so i skip that part
it installs.... says install is done and reboots itself... but seems to stay on that white bootscreen
if i take the battery out then i can reboot with recovery from the save file i have
blah i dont know... i got the ota installed... looked like it got a bit better reception.. i updated prl and came back to cm7 same probs... i dunno maybe ill just have to let go of cm7... really dont want to though its so sexy lol
I had the same weak signal issue with cm7 and had dropped calls and data dropping to 1x. I am on stock rooted 2.3.3 and reception is good again. Liked cm7 but need a phone I can use in the boonies.
Sent from my PC36100 using XDA Premium App
Dude, please, don't use ROM Manger.
Just boot to recovery, hopefully, you have Amon Ra, if not, search how to get it on your phone, it's not hard, do a FULL WIPE, full, wipe everything in recovery, then flash the ROM in recovery.
No offense to the Dev, I know he's a great guy, a smart guy, hard worker that makes a contribution, but Rom Manager is not the best way to do this.
Yea had to do it manually but nymph works now liking it so far
ok now i have different problem.... got the myn working liking it, but my market is completely different, not just the theme, but the apps i usually download... so tried to flash new market but it just open/closes quickly... any ideas for that?
Not sure by what you mean by the apps you usually d/l.
One thing about the Market in these newer ROMS is that sometimes, you just need to give it some time to fully sync before all your apps so up...
You should pull the market out of the zip file for the ROM and re-install that one, but you'll have to delete the one you have installed now, first.
umm usually download ninjump cant find that just some games that are usually on my phone the market on cm7 had them... ill give it a try though
look on the android market website
This is my first post in XDA.I hope this is the right spot for this questions.
I have searched everywhere for the answers to this question before posting. I flashed to CM7 with the tiamat kernel awhile back. I love CM7 but was curious to see what other rom developers are doing.
I ALWAYS do a back up before doing any flashes. I backed up my CM7 and my base rooted HTC downgraded 2.2 through RM. I was able to flash to synergy with no problems and restore to CM7. I decided to check out MIUI over the weekend. I flashed it with no problem. Last night I wanted to try mikshifted-g and Supreme Sense . I could not install either of them . The both stalled once CWM started to install. It was stuck on updating. There were no errors. I took the battery out and tried to restore CM7 backup through CWM. The restore went as expect but when I went to reboot it was only the HTC logo. I took the battery out and went back to MIUI through CWM and the phone booted. I then did a restore of my original rooted 2.2 the phone booted. I tried to install the above again on a fresh HTC stock rooted phone through RM and still had the same thing happen.
My question, is why I am not able to flash any other roms successfully other than restoring to MIUI and stock rooted htc 2.2 ? Installing Synergy works !
I do a full flash of system,data, cache and dalvik cache. I am not sure what I am missing.
If I understand correctly MIUI is a GB kernel as well as the others so there should not be a problem of compatibility ? I am assuming I still have root ? My HBOOT does say S off and PG 06001. I will try downloading CM7 through MIUI again to see if it works through RM. Sorry for the long post. I wanted to give as much detail as possible. Thanks in advance for any help
Richard
My suggestion would be don't use ROM Manager to flash, wipe or make nands. Do everything manually through recovery. I've seen too many people have the same type problems when using ROM manager.
what I have noticed is the progress bar in cwm doesn't work with sense roms, at least it never did in the mikshifted roms i tried and they take a LOT longer to install than cm7. How long did you let them sit at the install screen with that blank progress bar? Try clearing all your data/caches then install a sense based rom but leave your phone alone for like 10 minutes while it sits at that screen with the blank progress bar that says mikroms or whatever it says (been awhile since i used one). It shouldn't take 10 minutes but if your phone sits at that screen for that long then you know for sure it isn't working. I pulled my battery a couple times before i realized that's what was happening. I read about it somewhere online.
I have tried both RM and CWM. Both have the same results. 99% of the time I prefer the manual CWM method. Sorry I did not make it more clear.
I did re-flash CM7 with no problem. I do let the rom flash sit for a while but I will try longer since you say it takes longer with the roms in question. I let it sit for a few minutes. That seems like it should be more than enough. CM7 is pretty quick to install as well MIUI like you said. I love the layout and features of MIUI but since I am in a 4G area seems to defeat the purpose of having 4G if you can't use it. To be realistic though 4G is spotty in Atlanta and I mostly end up for 3G or using my wireless at home. I will probably end up with CM7 again since I like it equally as much as MIUI. If I wait longer for it to install and it does not work is there anything I should be looking at as the culprit other than myself
you were right, it just took a LONG time to install. I thought I was losing it. It took over 5 minutes. I am used to the install times of the MIUI and CM7 . Thanks for telling me to wait a little long. It's always the simple overlooked things like patients
My advice is just make sure you do a FULL Wipe before flashing a Rom. Like on THIS GUIDE, saves headaches later. Aslo, as you've learned Sense Roms usually take quite a bit longer than MIUI ,ASOP, or most others. But yes patience is important .
I definitely do a full wipe . I used all the guides here to make sure I did everything correct. I did not realize that the sense roms took longer than the CM or MIUI. I love the layout of MIUI. I wished it at some point 4G was going to be a part of it but I understand why it will not be .
4G in Atlanta, GA is not reliable, at least on my shift with sprint. I hate to pay for a feature that I am not able to use on regular basis. It's so spotty here I have gotten used to it.
I was never a big sense fan but it seems like if you want to have the 4G feature you use either use CM or another Sense rom right ? I got the shift because of how solid it's built and many reviews favor the EVOs or Galaxy S on Sprint
Thanks for all the feedback
Richard
Well you might want to give [AOSP ROM] S.O.A.P. ROM (sense-ish on android phones) a try. Sounds more like what your looking for. It's by one of the Shift members here.