So I'm loving my EVO running CM 7.1. It runs really well and I love using the sd card partitioned for s2e, but sometimes I receive texts up to 3 days late. That's unacceptable.
Is it worth switching to another sense based rom? If so, I'd like to use one with God Mode for the increase in speeds, so any suggestions would be great.
On a side note, I was able to install Synergy with God Mode once, but wasn't able to have it boot again. I'm not a noob at rom switching, but I have no idea what the heck went wrong. I wiped everything, tried re-flashing, nothing. I gave up and went back to CM7.
Any responses are greatly appreciated, so thank you in advance.
-J
idunnou said:
So I'm loving my EVO running CM 7.1. It runs really well and I love using the sd card partitioned for s2e, but sometimes I receive texts up to 3 days late. That's unacceptable.
Is it worth switching to another sense based rom? If so, I'd like to use one with God Mode for the increase in speeds, so any suggestions would be great.
On a side note, I was able to install Synergy with God Mode once, but wasn't able to have it boot again. I'm not a noob at rom switching, but I have no idea what the heck went wrong. I wiped everything, tried re-flashing, nothing. I gave up and went back to CM7.
Any responses are greatly appreciated, so thank you in advance.
-J
Click to expand...
Click to collapse
Honestly with godmode the only thing I notice different is higher quadrant scores and that's about it it feels the same as the regular version. Also if you do choose godmode make sure your using amon RA recovery since only compatible with it. Also check out some of the roms in my sig I recommended those to everyone
Sent from my PC36100 using XDA App
check it out
idunnou said:
So I'm loving my EVO running CM 7.1. It runs really well and I love using the sd card partitioned for s2e, but sometimes I receive texts up to 3 days late. That's unacceptable.
Is it worth switching to another sense based rom? If so, I'd like to use one with God Mode for the increase in speeds, so any suggestions would be great.
On a side note, I was able to install Synergy with God Mode once, but wasn't able to have it boot again. I'm not a noob at rom switching, but I have no idea what the heck went wrong. I wiped everything, tried re-flashing, nothing. I gave up and went back to CM7.
Any responses are greatly appreciated, so thank you in advance.
-J
Click to expand...
Click to collapse
there is more than cm7, click on the link in my sig to find out about all aosp kernels/roms and feel free to post any questions or anything there. i vote for aosp.
Solutions for Late Texts?
Thanks so much for the quick responses. Would switching to a Sense based rom for PRL updates and such fix the delayed text issue? Is there anything I can do with CM7 to fix it? It occurs randomly when I send and receive texts, but mainly receive.
idunnou said:
Thanks so much for the quick responses. Would switching to a Sense based rom for PRL updates and such fix the delayed text issue? Is there anything I can do with CM7 to fix it? It occurs randomly when I send and receive texts, but mainly receive.
Click to expand...
Click to collapse
re-install your rom and kernel or install the new radios. all of this is in the link in my sig, check it out
Green_Arrow said:
re-install your rom and kernel or install the new radios. all of this is in the link in my sig, check it out
Click to expand...
Click to collapse
I've tried those, but I just switched to Tiamat today, so I should give it a few more days to see if that hasn't solved it.
Godmode tends to be wacky, works for some, not for others. It worked on my phone for about a week, then went to FC city I tried to re-flash to fix it but then it bootlooped, kept doing that over and over til I finally figured I was one it won't work for and moved to non godmode. That ran fine til I switched to The Classic, the only difference I saw in godmode was benchmarks which IMO are worthless, the non godmode and godmode both performed the same in real life conditions. For your text issues try flashing up to date radios, then flash a stock sense Rom and update PRL and profile and flash back to cm7 see if they work better with everything updated. Otherwise you could use a sense Rom like The Classic v 0.0.4 very fast and very stable I've been running it since release from v 0.0.1 to v 0.0.4 which I am currently running with no issues thus far other than if u set autobrightness it is very sensitive in this release, so it adjusts very easily to small light changes. But it is one of the fastest sense roms I've tried and I've tried a lot cuz something about my evo hates AOSP, runs for a short time then random bootloops on all roms I've tried, cm7.1, miui, salvage mod, decks 1.3. So I stick to sense which I run senseless, I like my HTC apps anyways they look and feel more polished than most stock AOSP alternatives to me. But that's just personal preference. I've had text issues and updating PRL and profile always seemed to fix it for me so you could try just flashing a stock sense Rom update those and flash back to cm 7.1, hope that helps.
Sent from my -EViLizED-EVO-
Green_Arrow said:
re-install your rom and kernel or install the new radios. all of this is in the link in my sig, check it out
Click to expand...
Click to collapse
well if you click on the link in my sig there is an aosp GoDm0de kernel and i have the dl zip in my thread. in my opinion it is the best non-sbc kernel
Related
I'm aware of the issues associated with CM6 RC3, but when I installed 6.0.1 today, I booted, the touchscreen was non-responsive, but the scroll wheel allowed me to reboot.
Initially, I forgot to install the stock htc kernel over the hydrakernel I had for Sense (#2), so I put that on. When I rebooted, my screen was responsive, but I noticed a lot of page tearing, and my "SD Card is damaged. May require a format" or some such nonsense.
I'd like to try CyanogenMod but thats a major issue to me. I followed the wiki guide to a T, so its not like it could have been install issue. I reverted to Virtuous 2.2 for the time being, so I find it hard to believe my SD card is damaged, especially since Virtuous doesn't come up with the error.
Any thoughts or ideas that could fix this? Anyone experience similar issues? Thanks in advance.
You should be using the CM6 kernel only. I'd guess that's the source of your woes.
Sent from my Incredible using XDA App
@rmaccr
Only use the kernal that comes with the rom. CM6 is very picky when it comes to custom kernals. I tried to flash hydra and kingx kernals and no go. Just use the original kernal and u should be good.
Sent from my Incredible using XDA App
Make sure you're wiping data/factory reset and wiping the cache partition in Recovery before you install a different ROM.
There's also an alternate kernal you can flash if the stock CM6 kernel is giving you problems - search the RC3 thread to find it.
Thank you for all of your feedback. I'll have to do some thread searching to find that kernel. I assumed that may be the issue.
rmaccamr said:
Thank you for all of your feedback. I'll have to do some thread searching to find that kernel. I assumed that may be the issue.
Click to expand...
Click to collapse
Just reflash the rom and it will include the kernel. Just make sure you have set cpu or some other app to underclock your processor if need be. It's clocked at 1.15 and that gives my phone a bootlooping and crashing party.
Sent from my Incredible using Tapatalk.
rmaccamr said:
I'm aware of the issues associated with CM6 RC3, but when I installed 6.0.1 today, I booted, the touchscreen was non-responsive, but the scroll wheel allowed me to reboot.
Initially, I forgot to install the stock htc kernel over the hydrakernel I had for Sense (#2), so I put that on. When I rebooted, my screen was responsive, but I noticed a lot of page tearing, and my "SD Card is damaged. May require a format" or some such nonsense.
I'd like to try CyanogenMod but thats a major issue to me. I followed the wiki guide to a T, so its not like it could have been install issue. I reverted to Virtuous 2.2 for the time being, so I find it hard to believe my SD card is damaged, especially since Virtuous doesn't come up with the error.
Any thoughts or ideas that could fix this? Anyone experience similar issues? Thanks in advance.
Click to expand...
Click to collapse
Its not the SDCard that requires formatting. It is the internal phone storage. If you view it via Astro, it should appear ok.
whewstoosae said:
Just reflash the rom and it will include the kernel. Just make sure you have set cpu or some other app to underclock your processor if need be. It's clocked at 1.15 and that gives my phone a bootlooping and crashing party.
Sent from my Incredible using Tapatalk.
Click to expand...
Click to collapse
I thought 6.01 was clocked to normal speed and if you wanted the overclocking you just get 6.0 instead.
bippy_b said:
I thought 6.01 was clocked to normal speed and if you wanted the overclocking you just get 6.0 instead.
Click to expand...
Click to collapse
I think that 6.0.1 is defaulted to 1GHz, but you can o/c it if you want to with SetCPU or similar.
The kernel that comes with cm6.0.1 is already great. i get the best battery life i have ever had on my incredible. It can be overclocked to 1.15ghz
When I downloaded it defaulted to 1.15 so I guess YMMV.
Sent from my Incredible using Tapatalk.
rmaccamr said:
Thank you for all of your feedback. I'll have to do some thread searching to find that kernel. I assumed that may be the issue.
Click to expand...
Click to collapse
Slow down and read everything over a bit better.
Hydra and King usually state somewhere SPECIFICALLY that they DON'T work with/support CM6. You don't need to find any kernel, just WIPE your device properly ( wipe data/cache/dalvik) before you flash it. Once flashed don't try any kernels.
Also understand there are known issues with it. One is that BT music streaming doesn't work at all. The other is that the OS doesn't scan the built in 8gb of memory. The third one is that you may experience a random reboot or suddenly get a black screen and unresponsive phone when using wifi. It may happen in 30 minutes, it may take 12 hours. It may not happen at all. It's not even close perfect yet.
The only issue I have seen so far is random reboots and yesterday when I booted up my Phone all my widgets were brown boxes and said they were not compatible, a reboot fixed that.
Android Version 2.2
Model Number - Incredible
Baseband - 2.15.00.07.28
Kernel Version - 2.6.32.15......koush
Mod Version Cyanogen 6.0.1
When you mount your phone via usb mass storage it is mounting more than just the /sdcard/ and /emmc/(internal storage)
It is mounting /data/ and /system
If you're running Windows it will ask you to format these partition's b/c it cannot read them. Do not format them because you will then have issues mounting those partitions and you would have to RUU/PB31IMG.zip
I have already seen this happen to more than two people.
AndroidBruce said:
When you mount your phone via usb mass storage it is mounting more than just the /sdcard/ and /emmc/(internal storage)
It is mounting /data/ and /system
If you're running Windows it will ask you to format these partition's b/c it cannot read them. Do not format them because you will then have issues mounting those partitions and you would have to RUU/PB31IMG.zip
I have already seen this happen to more than two people.
Click to expand...
Click to collapse
Thanks for the pro-tip, I could see myself having done this.
I've had multiple lock ups and reboots but the first day was good.
Sent from my Incredible using XDA App
seanmcd72 said:
third one is that you may experience a random reboot or suddenly get a black screen and unresponsive phone when using wifi.
Click to expand...
Click to collapse
Gah, that's still happening with 6.0.1? I was hoping that would be fixed since the official source drop from HTC.
I'd really like to give an AOSP ROM a good run on my Inc, but that's a deal killer for me.
Thanks for the heads up though.
ardax said:
Gah, that's still happening with 6.0.1? I was hoping that would be fixed since the official source drop from HTC.
I'd really like to give an AOSP ROM a good run on my Inc, but that's a deal killer for me.
Thanks for the heads up though.
Click to expand...
Click to collapse
I have had NO reboots at all since putting 6.0.1 on 2 days ago - and I connect to Wifi at least 50% of the time. Today, I moved toward overclocking, but for the past 2 days I have been running stock speed
ncwildcat said:
I have had NO reboots at all since putting 6.0.1 on 2 days ago - and I connect to Wifi at least 50% of the time. Today, I moved toward overclocking, but for the past 2 days I have been running stock speed
Click to expand...
Click to collapse
I was also fine for over a day. Then today I have had to lockups, where the screen was black and only a bat pull fixed it plus one random reboot.
jratzo said:
I was also fine for over a day. Then today I have had to lockups, where the screen was black and only a bat pull fixed it plus one random reboot.
Click to expand...
Click to collapse
Exactly what I experienced. I went half a day with it seeming perfect, then out of the blue I pick up the phone and it's just off and nothing I do will get it to come on. It's either pull the battery or wait several minutes and suddenly it finally reboots on it's own. It doesn't happen to everyone, but it happens to enough people to say it is a definite unresolved issue. It's very good otherwise, as soon as these little issues are cleared up It will be the ROM for me.
Ok since this the third time typing this here is the condensed version. Running myns rls5 ontop of toastmod kernel listed on same page. Initial flash went ok minus the Flickr screen, distortion lines laterally, horrendous battery life, weird boot process...osmonitor I had to install due to interference with the OS. Myns crashed a lot with in first flash. Also some one dumb down how to use an irc app cuz I'm also lost....also what IM service can I get hold of u guys on cuz I hate forums.... too impatient
Ok no help? Not even some direction for irc where I can get some real help? Well just flashed a diff kernel thanks for the help guys. The Droid community has been a very unhelpful one compared to iPhone....
(irc help would be awesome still since I now have some help with main issue- I enter all the correct info into the app but it shows nothin. I've tried several to no avail. I appreciate the help) second I've ran into more pretentious ppl in these forums for Android then others no offense to the good guys but just my exp. It was brash to say that in this post tho. Thank you guys again for the ones willing.
That's because even the biggest idiot can work an iphone.
Jataadroid said:
Ok no help? Not even some direction for irc where I can get some real help? Well just flashed a diff kernel thanks for the help guys. The Droid community has been a very unhelpful one compared to iPhone....
Click to expand...
Click to collapse
Jataadroid said:
Ok since this the third time typing this here is the condensed version. Running myns rls5 ontop of toastmod kernel listed on same page. Initial flash went ok minus the Flickr screen, distortion lines laterally, horrendous battery life, weird boot process...osmonitor I had to install due to interference with the OS. Myns crashed a lot with in first flash. Also some one dumb down how to use an irc app cuz I'm also lost....also what IM service can I get hold of u guys on cuz I hate forums.... too impatient
Click to expand...
Click to collapse
Patience dude. I didn't catch it, but what exact kernel are you using, net has a lot of em, the one in the OP of myn's thread you mean? What recovery(and version of that recovery, some versions of clockwork floating around that have some bugs i think) did you use to flash the rom? what radio version and pri version do you currently have installed? Which ROM were you coming from, and did you do a full wipe(data, cache, davlik cache) before flashing it? I have never experienced anything like you are describing whilst using Myn's, his ROMs have been solid. Give a little more info and surely we can help you get running smoothly again.
thanks for the reply heres the details...myn's rls5, net toast havs more, ra_superson
Sincerely thanks for your reply. Typing this on my evo as my screen tears on and off. Running ra_supersonic(newest ver.) With Myns rls5 on net havs more smartass as listed on page. Updated to current radio and pri as listed on his post. Only dalvik and cache wiped not data. Flashed
Hulu and data governor hacks...CPU is only overlooked to 1190 in smartass and can't go any higher. This was my first root and flash so came from stock 2.2 on 3.30 ver. Have noticed avg using temp is around 103 off charger, cameras broke, my CPU in system panel says I'm running 100% continuously. Did a fast reboot , norm reboot, and still doin it. I had diminished battery life from the get go, I understand battery life per clockspeed relation but have underclocked profile to try to assist, which only cause frustration when coming back from lock screen and its still tryin to switch profile. Lagged the phone nearly locked out several times cuz it couldn't keep up with my fingers.0003 hw....I think that's it. Thank you again
Looks like we're running nearly the same setup, minus my ra_supersonic 2.2.1 recovery. I have attempted the stock kernel furnished in the Rom zip but since it didn't offer overclock I switched to net havs more smartass. I do the dalvik and cache wipe each time.
Jataadroid said:
Sincerely thanks for your reply. Typing this on my evo as my screen tears on and off. Running ra_supersonic(newest ver.) With Myns rls5 on net havs more smartass as listed on page. Updated to current radio and pri as listed on his post. Only dalvik and cache wiped not data. Flashed
Hulu and data governor hacks...CPU is only overlooked to 1190 in smartass and can't go any higher. This was my first root and flash so came from stock 2.2 on 3.30 ver. Have noticed avg using temp is around 103 off charger, cameras broke, my CPU in system panel says I'm running 100% continuously. Did a fast reboot , norm reboot, and still doin it. I had diminished battery life from the get go, I understand battery life per clockspeed relation but have underclocked profile to try to assist, which only cause frustration when coming back from lock screen and its still tryin to switch profile. Lagged the phone nearly locked out several times cuz it couldn't keep up with my fingers.0003 hw....I think that's it. Thank you again
Click to expand...
Click to collapse
Not trying to be a smart ass but do you realize that by insulting us will not get you any help? Rhetorical question
From reading what you jus stated the obvious problem is you did not do a FULL WIPE as you should do when flashing between roms.
Also next time please be patient as those like myself who browse through this section to help impatient ppl like your self, do actually have a life outside of xda. Its been a big snow storm in the southeast so most like myself included are outside enjoying the snow!
DO A FULL WIPE THEN REPORT BACK!
Gonna ignore the soap box chatter...
Obviously know I didn't do full wipe.....just gonna wait for other poster
gotta do a full wipe if you are switching between roms
Sent from my PC36100 using XDA App
also make sure whatever kernel your using works with the 3.70 based roms, as many dont.
Sent from my PC36100 using XDA App
Ok. Well crap.... thanks guys since that is apparently my only option.
OneStepAhead said:
also make sure whatever kernel your using works with the 3.70 based roms, as many dont.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
The kernel was included in the op and I've seen tags with same setup as mine.
Jataadroid said:
Gonna ignore the soap box chatter...
Obviously know I didn't do full wipe.....just gonna wait for other poster
Click to expand...
Click to collapse
Sorry you feel that way but since i have had the hero, on every thread about a rom says wipe all! This must be a joke for someone as rude as yourself to come on here and disrespect those who are trying to help.
Next time you decide to flash a rom remember to do a full wipe because inside the data partition is files for the particular rom, if you dont wipe, the new files will just over lay but not delete the old one. This will cause conflicting issues within the files as the phone tries to do both at the same time.
Screen tearing and the "jigglies" as I like to call it have always come from kernels - in my experience. And just because someone might have the same set up as you, the way it affects your phone ccan be quite different as you are running different apps, different settings, etc.
First thing I would do if I were you is to freeze any kernel govenor you are using - no setcpu, no secreen off profile, no set on boot, no os monitor govenor, no nothing like that. You don't want want any of that going on when you flash a new rom or kernel.
I know you don't want to do a full data wipe so let's see if we cna get you going without that. I used to HATE doing data wipes, I don't mind so much now because I've learned that trobule shooting can frequently take longer than just doing a data wipe.
I would say #1 make sure you are using AMON RA. Power button-reboot-recovery. Wipe cache at least twice, wipe dalvik at least twice. Now JUST flash the rom (you've already said your radios are updated so you wont have a problem with this). Let the phone boot up and give it time to settle in. You wont have any screan tearing. Now you're running a completely stock Myn's rls5 rom. Check some stuff out, make sure your basic settings are good, make sure your 4g is not scanning, etc.
Make a nandroid of this and keep it.
Now start making changes if you'd like. Flash a different font, flash a different kernel, etc. But leave all the governors OFF until you have a kernel that you KNOW will run ok on your phone. For example - I can run 2 of ziggy's kernels but the others don't work for me. I can run a few of net's kernels, but many don't work for me.
So my basic suggestion is to make sure you get a stable, stock Myn's rls5 on your phone before you mod it. If you can't get that, then yes - you might want to wipe data. Doing a batch backup in Titanium is really easy and it makes restoring very easy as well. It's our own customizing that is time consuming because we are all probably very picky (and proud!) of our beautiful phones.
Thanks for the helpful info from ALL that posted. I understand the risk of the non entire wipe, nandroid is safe of original stock Rom but not of new one. After tinkering with setcpu I've gotten more consistent stability. I know I will reflash with an entire data wipe here soon to see results. Running ra_supersonic 2.2.1 recovery.
I've made list of check point when I test some new Roms and kernels. I have some more question on backing up user info from backed up apps but Im sure ill find it on here.
Now that my system is stable for the time being, some one mind help me setup irc? And also has anyone issues with camera breaking with this Rom or kernel? I should wait to wipe entirely to see if it fixes, but I'd rather not waste my time with this Rom or kernel if the camera won't work. Love everything else about this Rom, need to learn more about the kernel to praise it. Ra_supersonic 2.2.1 recovery i like also.
Jataadroid said:
Sincerely thanks for your reply. Typing this on my evo as my screen tears on and off. Running ra_supersonic(newest ver.) With Myns rls5 on net havs more smartass as listed on page. Updated to current radio and pri as listed on his post. Only dalvik and cache wiped not data. Flashed
Hulu and data governor hacks...CPU is only overlooked to 1190 in smartass and can't go any higher. This was my first root and flash so came from stock 2.2 on 3.30 ver. Have noticed avg using temp is around 103 off charger, cameras broke, my CPU in system panel says I'm running 100% continuously. Did a fast reboot , norm reboot, and still doin it. I had diminished battery life from the get go, I understand battery life per clockspeed relation but have underclocked profile to try to assist, which only cause frustration when coming back from lock screen and its still tryin to switch profile. Lagged the phone nearly locked out several times cuz it couldn't keep up with my fingers.0003 hw....I think that's it. Thank you again
Click to expand...
Click to collapse
You're welcome. I am late at getting back to this post, but yea. Definitely. As everyone else has suggested, you have to do a full wipe when changing ROMS. Only time you could get away with just wiping davlik cache and cache is when upgrading the same rom ( like from rls 3 to rls 4, and rls to rls 5), but even then, it doesn't always work. Full wipe is always recommended. I would also recommend downloading your apps one at a time from the market, and adding your mods one at a time, make sure everything is stable after each flash. Good luck.
QUOTE And also has anyone issues with camera breaking with this Rom or kernel? I should wait to wipe entirely to see if it fixes, but I'd rather not waste my time with this Rom or kernel if the camera won't work. Love everything else about this Rom, need to learn more about the kernel to praise it QUOTE
If your phone is the newer hardware (late 003 or 004), you can only use the stock kernel, or a kernel based off stock for the camera to work. That would be htc #15. I believe Net's 4.3 kernels are based off of that. I am also pretty sure that Net explains that in his kernel thread in the development section.
Thanks guys did the full wipe and reflashed, working ok except SD file permissions are screwed up now. I go to test camera and it says insufficient file permissions when I take a pic. I go to check in astro, I see all the file that are supposed to be there but no editing; it still shows rw. Did not have card in when full wipe was completed would that effect it? Any help? Haven't attempted another SD card. I hope this isn't the second SD card to be trashed during my rooting process. Atleast I can still see that there r files on there. Thanks for the help.
Also any help gettin set with irc? Still having a horrible time trying to work with it....it seems so simple.... so 0003hw are stuck with stock roms or ones based off them...I believe nets kernel on that page was. I will test it out and let you know. I just need to know about the SD card problem. Thanks again guys.
Theres been lots of issues with 3.70 based roms. I always stick to lower versions..usually 3.30 and have no problems.. i also hace seen alot of people having battery problems on 3.70 after updating to 1.90 pri. They usually downgrade to pri 1.77 and there good.....
Evo - Myn 2.2 RLS 3 - Clockwork - HBoot .76
r.storm85 said:
Theres been lots of issues with 3.70 based roms. I always stick to lower versions..usually 3.30 and have no problems.. i also hace seen alot of people having battery problems on 3.70 after updating to 1.90 pri. They usually downgrade to pri 1.77 and there good.....
Evo - Myn 2.2 RLS 3 - Clockwork - HBoot .76
Click to expand...
Click to collapse
This isn't true, the problem is ALWAYS the kernel. I'm running myn rls5 and mikfroyo 4.3 with an SBC #15 v7 kernel (i'll edit post and add the link) and I have had zero issues except I can't download MMS messages on 4g on mikfroyo.
Jataadroid said:
Thanks guys did the full wipe and reflashed, working ok except SD file permissions are screwed up now. I go to test camera and it says insufficient file permissions when I take a pic. I go to check in astro, I see all the file that are supposed to be there but no editing; it still shows rw. Did not have card in when full wipe was completed would that effect it? Any help? Haven't attempted another SD card. I hope this isn't the second SD card to be trashed during my rooting process. Atleast I can still see that there r files on there. Thanks for the help.
Also any help gettin set with irc? Still having a horrible time trying to work with it....it seems so simple.... so 0003hw are stuck with stock roms or ones based off them...I believe nets kernel on that page was. I will test it out and let you know. I just need to know about the SD card problem. Thanks again guys.
Click to expand...
Click to collapse
Okay, this process will 100% work. It's the one I've been using since my lowly mytouch slide oh so many months ago.
*before you do this, make sure you have backups of your nandroid and your rsa keys. I'll edit post and give you links on how to back up your rsa keys*
RSA Key back-up: http://forum.xda-developers.com/showthread.php?t=887900 ...since you're rooted you can go straight to the part where it says "if you're rooted do this.."
1. First you need to fix the sd card. Create a folder on your computer desktop and call it "my sd card". Plug your phone into the computer and select "disk drive". Next you're going to copy EVERYTHING from the sd card and place it in the folder on the desktop (and dude I mean everything! AS IS, DON'T CHANGE ANY NAMES). Then, you're going to unhook your phone, go to settings>sd and phone storage. Then you're going to format your sd card. Yes, do it, but make sure you have EVERYTHING backed up first. After that's done, plug your phone back in, select disk drive and copy everything from your "my sd card" folder on your computer and put it back onto your sd card.
*phew*
Okay now that the sd problem is fixed, here's how you fix the rest. You see, when you upgrade your PRI to 1.90 and your radio, etc etc you gotta update the kernel to a version that's 1.90 supported. I'll edit post and post a link to where you can find one OR you can just use the kernel that's included with myn's rom because it WILL WORK. *edit* the kernel I'm using has been taken down because of the witch hunt against SBC kernels. So for now, just stick with stock. It works just fine.
Anyway.
Steps to getting myn working perfectly.
*before starting, re-download myn rls5 in case the screen flickering was caused by a corrupted download*
1. Download Titanium Back-up from the market. Back up all the apps you want to keep (basically, anything you downloaded from the market as you'll get facebook, sense widgets, etc back). You can do this while you re-download the rom.
2. Make a nandroid back-up in case something goes seriously wrong. A rom that flickers your screen is better than a brick.
3. Once that back-up is done, reboot into recovery. Once there, you're going to WIPE EVERYTHING. Full data, cache and dalvik wipe. Yes, do it. There is no other option.
3. Flash myn's rom. Let it go all the way through. Do NOT flash a new kernel until you've found one that's 3.70 compatible and works with PRI 1.90. Myn rls5 is designed to work with the newest updates (which means a #15 kernel, like the one that came stock).
4. Reboot. If the screen is still flickering, then at this point it's a hardware problem. Flash back to stock, unroot and go get a new one. If it works fine, re-download titanium back-up from the market and restore all your apps. From there it's just putting your widgets back on your home screen.
From here, you can search the forums for a kernel that works with the newest updates. If you read them, they'll tell you what they're compatible with. Remember do NOT use an AOSP kernel with a SENSE rom, that's just spells IDIOCY. Until you find a kernel that works, stick with the one that came with the rom because everyone knows that one works.
I hope this helps. As for the IRC chat, not all the experts are on all the time. If no one is online that can help when you get one, try getting a few hours earlier or a few hours later.
Hello all,
A question as first post. I know, hell of a way to kick off, huh?!
OK, here's the deal...
EVERY single ROM I try to install is giving me the very same three issues:
"SD card unexpectedly removed"
"DRM Notification : License required" (Click and nothing pops up. Never seen that before)
No USB debugging mode upon plugging into PC
When I Nandroid flash back to prior ROM install settings, everything is fine.
I've tried different radios, 5 different Sense ROM's
There is absolutely nothing wrong with the SD card. As soon as I flash back to Sense, it shows, hooks up to the PC, and works perfectly
It's been driving me nuts. I've been screwing with it since 7:00am. I really want to run a different ROM, as the battery on my Evo gets chewed up WAY too fast for my liking.
Any ideas???
Thanks,
Jack
Well try this:
-In recovery, disable signature verification
-Backup all apps using titanium backup
-Wipe factory/data, cache, dalvik in recovery
-Flash CM7 with the latest gapps, reboot.
Let me know what happens.
Signatures were disabled for all ROM installs (verified)
Full backup via Astro
Everything wiped
CM7 and Gapps flashed
Cyanogenmod 7 works fine.
WTF?
zx7rou812 said:
Signatures were disabled for all ROM installs (verified)
Full backup via Astro
Everything wiped
CM7 and Gapps flashed
Cyanogenmod 7 works fine.
WTF?
Click to expand...
Click to collapse
You're welcome.
Now backup CM7, then do a full wipe again, factory/data, cache, dalvik, then try flashing the rom you wanted in the beginning. If its a gingerbread rom, you'll have to flash the gapps with it. If you restore the CM7 backup, you don't need to flash gapps again.
ok, here's the scoop...
Backed up Cyan7
Then:
Flashed to Calkulin's
Flashed to Warm 2.2
Flashed to MikFroYo
Flashed to Fresh
Same 3 problems popped back up.
Flashed back to Cyan7, everything is fine. Thought it wasn't being picked up by the PC, until I hit the setting to enable Disc.
Still confused as to how Cyan is working fantastic, but the others tanked...?
Guess I'm stuck with Cyan?
Also, can I run a different kernel in Cyan7 (say...a more battery conserving one)? Will any kernel work with Cyan, or am I just better off sticking with Cyan and SetCPU?
BTW: I noticed I didn't thank you.
Thanks Roxx.
zx7rou812 said:
ok, here's the scoop...
Backed up Cyan7
Then:
Flashed to Calkulin's
Flashed to Warm 2.2
Flashed to MikFroYo
Flashed to Fresh
Same 3 problems popped back up.
Flashed back to Cyan7, everything is fine. Thought it wasn't being picked up by the PC, until I hit the setting to enable Disc.
Still confused as to how Cyan is working fantastic, but the others tanked...?
Guess I'm stuck with Cyan?
Also, can I run a different kernel in Cyan7 (say...a more battery conserving one)? Will any kernel work with Cyan, or am I just better off sticking with Cyan and SetCPU?
BTW: I noticed I didn't thank you.
Thanks Roxx.
Click to expand...
Click to collapse
aosp kernels will work. that's savaged-zen or tiamat. both are very good.
that is one hell of a problem you got there. where are you downloading roms from? is s-off or on? boot into bootloader and look in the top right corner to find out.
dkdude36 said:
that is one hell of a problem you got there. where are you downloading roms from? is s-off or on? boot into bootloader and look in the top right corner to find out.
Click to expand...
Click to collapse
ROMs were mainly downloaded here, lol. Or off the ROM's dev site. No back door 3rd party sites.
S-OFF on BL screen
zx7rou812 said:
ROMs were mainly downloaded here, lol. Or off the ROM's dev site. No back door 3rd party sites.
S-OFF on BL screen
Click to expand...
Click to collapse
no freaking idea.... newest version of amon-ra?
dkdude36 said:
no freaking idea.... newest version of amon-ra?
Click to expand...
Click to collapse
I'm running ClockworkMod Recovery
Any idea who has the "best battery" kernel?
I don't super gaming level performances from the Evo. I use it mostly as a telephone/text/email device, so I need a nice stable long lasting battery. It usually spends it's life underclocked anway.
zx7rou812 said:
I'm running ClockworkMod Recovery
Any idea who has the "best battery" kernel?
I don't super gaming level performances from the Evo. I use it mostly as a telephone/text/email device, so I need a nice stable long lasting battery. It usually spends it's life underclocked anway.
Click to expand...
Click to collapse
try the newest amon-ra. clockworkmod may be your problem.
savaged zen has better battery life for me, mostly because of the savagedzen governer. it likes to underclock. tiamat supposidly has slightly better performance. i like to run savaged zen.
For best battery, I recommend the Tiamat kernel for CM7. I can get 19hrs at 55% left on the non sbc version. Tiamat is initially undervolted, and allowss additional undervolting thanks to viperboy. And no need to thank me.
This epic reply brought to you by none other than my roxx'd out Evo.
Which kernel should I go with, Roxx?
3.3.7?
And, yeah. I can thank you. If not I'd still be pulling out my hair and rocking the stock ROM, lol!
zx7rou812 said:
Which kernel should I go with, Roxx?
3.3.7?
And, yeah. I can thank you. If not I'd still be pulling out my hair and rocking the stock ROM, lol!
Click to expand...
Click to collapse
Lol anytime, and yes, go for the 3.3.7
So far, I've only used AOSP ROMs (DevNull and Oxygen) since I rooted my phone. Personally, I like it better because I like simplicity, and the idea of a stock ROM appealed to me.
But there seems to be a problem with AOSP ROMs, the call delay issue. Although people say they hardly notice it, I get 3-4 seconds delay every time and I find myself going like "Yes. Hello. Hello? Are you there?" every time I answer a call. I've heard that the problem is AOSP-specific, because of some libs Google uses, and that HTC use their own libs which do not present this issue.
So yesterday I backed everything up and got ready to try LeeDroid. But after installation, I could not get the ROM to boot nor the SD card to mount. I eventually fixed the problem by repartitioning the SD card, and I'm now running DevNull. I'd also like to mention that I'm S-OFFed, was running CWM 3.1.0.1 and had the Oxygen HBOOT before installing the Stock one back.
Now, I'd like to know how I am supposed to correctly switch to a Sense ROM coming from an AOSP one, as well as some opinion as to which is the cleanest, reasonably fast Sense ROM available out there. Perhaps some thoughts on kernels, too.
Thanks in advance!
I am on RcmixS 1.6.2 at the moment and working well.
Do full wipethen flash the rom, that is it. Enjoy.
I did perform a full wipe before installing.
What version are you trying to install? At the start the GB version didn't like the newer versions of CWM, also hboot versions were an issue too. I haven't really been keeping up because I went back to 2.4.1 till an actual GB release. Check it out those might be causing you trouble.
Sent from my HTC Desire using XDA Premium App
I've downloaded InsertCoin and I plan on installing it later today, as now I've got some stuff to finish. If it doesn't work, I'll try downgrading CWM. Thanks!
You need to use the stock 250MB HBOOT - obviously a Sense-based ROM is too large for the Oxygen one
EddyOS said:
You need to use the stock 250MB HBOOT - obviously a Sense-based ROM is too large for the Oxygen one
Click to expand...
Click to collapse
Try AuraxTSense, i have been back and forth between most of the Sense ROMS & this is the one i come back too.
ALWAYS
I've given InsertCoin a try yesterday, but I didn't like it as it was way too laggy (as in I usually had to touch something twice for anything to happen).
I think I'm going to try each one today and see what I'll end up using. I'll post my opinions here.
@EddyOS I did use the stock HBOOT with LeeDroid, but I downloaded the CM7 version of InsertCoin.
@3f1f37 I'll give it a try, thanks!
caen1 said:
I've given InsertCoin a try yesterday, but I didn't like it as it was way too laggy (as in I usually had to touch something twice for anything to happen).
Click to expand...
Click to collapse
???
laggy? twice touching ?
Are you trying to touch things during the first minutes of the first boot after flashing??
Let the ROM settle about 5-10 mins after first boot, your phone will be blazing fast afterwards.
InsertCoin 1.0.7 CM7 (Gongerbread; Sense 2.1 + 3.0; 130MB) is one of the fastest and the most stable Sense ROMs currently available,I use it also.
aaa said:
???
laggy? twice touching ?
Are you trying to touch things during the first minutes of the first boot after flashing??
Let the ROM settle about 5-10 mins after first boot, your phone will be blazing fast afterwards.
InsertCoin 1.0.7 CM7 (Gongerbread; Sense 2.1 + 3.0; 130MB) is one of the fastest and the most stable Sense ROMs currently available,I use it also.
Click to expand...
Click to collapse
I too felt it was very laggy. CM7 version, with CM7 hboot, 1GBext. even the typing was bad, had to retype messages because it would start to lag out and miss letters
i dont know what i could have done wrong to get such a horrible experience. maybe you can enlighten me?
@aaa I've overall had a laggy experience even one day after installing it.
@ringer13 what ROM have you eventually settled to? Thanks!
I'm currently trying CoolD, or something like that, because the ZIP only has 144 MB. I also tried installing HiApk (it has 138 MB), but the download was damaged or something, it didn't pass the verification process in Amon_RA 2. But I will redownload it if I'm dissatisfied with CoolD.
caen1 said:
@ringer13 what ROM have you eventually settled to? Thanks!
Click to expand...
Click to collapse
cyanogenmod7 ive found most gb sense roms way too laggy so went with aosp
I'll have to agree with that. My HiApk ZIP was corrupted and after booting CoolD, all I got was Force Close for all the apps, including the launcher.
I didn't bother anymore, so I went on and installed Oxygen 2.1.3. It works like a charm.
Well it is true that u have to sacrifice speed, but the benefits from the sense are worthing the less smooth response, and mostly it is hardly noticeable...
Sent from my HTC Desire
I know the speed comparison of AOSP and Sense, I have used both.
The only thing I have not used is MIUI...saw it on youtube, and hate it right away...
I know AOSP is always faster than Sense but Sense in generally especially InsertCoin is not so bad so that you had to touch things twice before getting any response.
Moreover, InsertCoin is one of the fastest Sense ROMs you can find.
If you had to touch everything twice until you got any response from your phone, check if you have massive processes on the background caused by any other apps/syncs or some problems with your SD card.
I just got my hands on the dinc. I am coming from a rooted D1. Unforuntulny the dinc has been updated and has s-on..
even searched for s-on Sorry - no matches. Please try some different terms. I love it lol...
Anyways, if i have read correctly if s-on is enabled, I am just SOL in rooting my phone and using custom roms,themes etc till someone finds a workaround , correct?
Also all my game and app data on my d1, anyway to move it over to the dinc?
Updated to GB 2.3.4 and S-On? If so, I found THIS thread a few days ago that seems to be working. Before you do any of that..make sure your SD card is formatted to FAT32.
Apps yes...you can move those over to your Inc. Data would not be a good idea. The data is from a totally different phone so you would cause a lot of issues by doing restoring any app data. My friend who moved on to an Inc from a DX tried to do it and got FC's all over the place.
Good luck and enjoy your new phone!
Marcismo55 said:
Updated to GB 2.3.4 and S-On? If so, I found a thread a few days ago that seems to be working. Before you do any of that..make sure your SD card is formatted to FAT32.
Apps yes...you can move those over to your Inc. Data would not be a good idea. The data is from a totally different phone so you would cause a lot of issues by doing restoring any app data. My friend who moved on to an Inc from a DX tried to do it and got FC's all over the place.
Good luck and enjoy your new phone!
Click to expand...
Click to collapse
Thanks for the link, everything i found was s-off only..
As for backing up info,example, all my game progress will be lost? what would be the process to do this? Guessing the phone would need to be rooted?
bingo6104 said:
Thanks for the link, everything i found was s-off only..
As for backing up info,example, all my game progress will be lost? what would be the process to do this? Guessing the phone would need to be rooted?
Click to expand...
Click to collapse
I looked that over and it looked like it should get you back to s-off, rooted froyo. It's a LOT like the method jcase developed for the Tbolt before Revolutionary. If you can get s-off, you're good to go. Flash a custom recovery and flash a rooted ROM. Should be that simple.
thanks for the info!
Yeah, that thread works.
Thanks again guys, i got it to work last night.. Now i just need to decide on a rom? Any suggestions? I loved chevyNo1 on D1 :/
Your going to love the incredible compared to the og droid, everything is so much snappier, and battery life will increase too.
I'm not a sense guy at all but McD's ROMS are super nice.
I really liked chevy's ROMs too. CM7.1 stable and the latest incredikernel on 10/12 by Tiny will get you started in the right direction if you want to stick with AOSP or if you want something more barebones grab IncDeck 1.3 Final... I just went back to CM7.1 because I felt I got a little better batterylife.
Will give them a try. I did download cm7.1 and on re boot after install it gets stuck on the boot loader. Do I need to do a complete wipe or something ?
bingo6104 said:
Will give them a try. I did download cm7.1 and on re boot after install it gets stuck on the boot loader. Do I need to do a complete wipe or something ?
Click to expand...
Click to collapse
Yeah, complete wipe is recommended if you're not coming from an earlier CM7.
PGleo86 said:
Yeah, complete wipe is recommended if you're not coming from an earlier CM7.
Click to expand...
Click to collapse
Ok I'm a little rusty cause on the d1 I never had to wipe.. in the Rom manager just select clear and wipe and that should do the trick ? I got my games backed up so that isn't a issue. But all settings and such will be lost ,correct?
Thanks
bingo6104 said:
Ok I'm a little rusty cause on the d1 I never had to wipe.. in the Rom manager just select clear and wipe and that should do the trick ? I got my games backed up so that isn't a issue. But all settings and such will be lost ,correct?
Thanks
Click to expand...
Click to collapse
Personally, I never use Rom Manager. I flash through recovery; if you use Rom Manager to reboot into recovery, do a factory reset from there and then flash and you should be good.
Ok cool.. thanks for the quick replies.
McD's ROMS i havent seen any of those. I loaded CM7.1 Very simliar to chevyno1's rom.. Trying something different, miui right now, its not bad, reminds me of the iphone though.. Any other suggestions?
I strongly recommend against ROM manager, too. Any dev worth his salt tends to recommend against flashing through ROM Manager because it doesn't seem to do what it's supposed to. It's been a problem child for a long time now. When performing functions done through recovery, it's best to go directly into recovery to perform them. I think the same can be said for the bootloader.
Sorry i meant clockwork, dont know why i keep on saying rom manager. Can anyone help me with roms or should i post a new post on it?
I kind of dig miui but dont like the sms keyboard layout. Its like cm7 and i really like the stock dinc set up. With my big fingers i get less typos with its set up.. Any suggestions?
Here is a list of Dinc ROMs. I personally recommend CM7, but if you like HTC Sense, go for Runny Revolution 3D. Great Sense ROM.