Related
Way back in the 30's I was getting fantastic results with CM7 and tiamets kernel. I recently wanted to go back to it until the Sense 2.1 guys ironed out a few more bugs for me to comfortably daily drive them. I installed n63....had issues 7.0.3.1.... had issues.... n65.... had issues.
By issues I mean random restarts, force closes, 3g won't stick, overall signal for 1x was horrible, no amount of gps fixing would keep my gps locked in or lock better than 20 meters and mms won't work.
I tried stock kernel, tiamets, SZ ect.... clean install, clean wipe, reinstall apps from market vs restore from TB. Tried the mms fix, gps status app, msl reset trick, you name it I have tried it. My phone does not like CM7 right now at all. It's like feeding a baby strained carrots.
I was just curious if anyone else is having similar "no amount of tweaking will fix it" issues. I had to go back to Konis just for some sanity after 3days of this. I know all these Roms that are not based on actual Evo source are experimental but can a guy get some CM love?! lol
I am having pretty much the same issues on my evo. Tried just about the same tweaks to try to rectify them. Right now I'm going to under clock and see if it helps. I noticed a lot more things residing in memory after a restart than usual, including fota kill which is a cm product. All I think I can do now is fire up catlog and see if anything is obvious. I'm no genius so likely I'll just send it in and hope for the best. I was almost sure my hardware was failing, but now not so much.
Haven't had any issues gonna try the latest stable build of cm7 I always use amon 2.3 for a full wipe a lot of the time that fixes issues for people .
ginjeet said:
I am having pretty much the same issues on my evo. Tried just about the same tweaks to try to rectify them. Right now I'm going to under clock and see if it helps. I noticed a lot more things residing in memory after a restart than usual, including fota kill which is a cm product. All I think I can do now is fire up catlog and see if anything is obvious. I'm no genius so likely I'll just send it in and hope for the best. I was almost sure my hardware was failing, but now not so much.
Click to expand...
Click to collapse
Well, n66 after a day on tiamets 4.0.1 kernel seems stable. Let me know how the undervolting goes. I tried vipers v2 and it started freezing after about 20 minutes. The -50 script did the same thing. -25 actually worked out pretty well right up until this morning. My alarm went off and I hit snooze and it threw it into constant reboot.
I'm going to run just n66 with 4.0.1 all day no script and see what I get. I dunno what has changed for my phone but it seems to have leveled out. *knocks on wood*
Sent from my PC36100 using XDA Premium App
So far on the 7.0.3.1 build GPS works like a champ market mms and everything camera and such you tube app plays everything on hq. Picky at time at times tho on HQ.
blizzard1017 said:
Way back in the 30's I was getting fantastic results with CM7 and tiamets kernel. I recently wanted to go back to it until the Sense 2.1 guys ironed out a few more bugs for me to comfortably daily drive them. I installed n63....had issues 7.0.3.1.... had issues.... n65.... had issues.
By issues I mean random restarts, force closes, 3g won't stick, overall signal for 1x was horrible, no amount of gps fixing would keep my gps locked in or lock better than 20 meters and mms won't work.
I tried stock kernel, tiamets, SZ ect.... clean install, clean wipe, reinstall apps from market vs restore from TB. Tried the mms fix, gps status app, msl reset trick, you name it I have tried it. My phone does not like CM7 right now at all. It's like feeding a baby strained carrots.
I was just curious if anyone else is having similar "no amount of tweaking will fix it" issues. I had to go back to Konis just for some sanity after 3days of this. I know all these Roms that are not based on actual Evo source are experimental but can a guy get some CM love?! lol
Click to expand...
Click to collapse
Are you u using amon 2.3
Cm7 is running great for me. Used nightly 65 for a week with no problems. Flashed 7.0.3.1 2 days ago and it is running like a champ with sz 2.1.0 cfs. Did GPS fix back on nightly 30 something and it has been fine ever since. Maybe you just made your phone mad and its retaliating lol. I do have the receive mms problem though . Tried multiple fixes for it with no luck.
Update* just received an mms with 7.0.3.1 and it worked
A1Lonestar said:
Cm7 is running great for me. Used nightly 65 for a week with no problems. Flashed 7.0.3.1 2 days ago and it is running like a champ with sz 2.1.0 cfs. Did GPS fix back on nightly 30 something and it has been fine ever since. Maybe you just made your phone mad and its retaliating lol. I do have the receive mms problem though . Tried multiple fixes for it with no luck.
Click to expand...
Click to collapse
What recovery are you using man? Anything better using nightly 66 advantage wise?
reaper24 said:
What recovery are you using man? Anything better using nightly 66 advantage wise?
Click to expand...
Click to collapse
Well 66 plays nicely, but I think the mms bug where you can't receive, but using 3.3.7/4.0.1 with bsm v2 and it plays nicely.
teh roxxorz said:
Well 66 plays nicely, but I think the mms bug where you can't receive, but using 3.3.7/4.0.1 with bsm v2 and it plays nicely.
Click to expand...
Click to collapse
Well, I just went back to Koni's..............again. I was running 66 all morning with 4.0.1 and no script and while everything was working ok the battery was draining somewhat fast. It wasn't a wake issue and I even tested an hour or so on PRI177 with the same results. The battery was tolerable because Mondays are really busy for me so I know on a normal day I wouldn't complain but my data connection still drops to 1x a lot and I think the drain might have something to do with the connection searching constantly.
If I can get that Viper script moving along and figure out the data and signal drop I think I am getting somewhere.
@reaper, yes I am using Amon Ra latest and greatest.
Off topic, I love the Nand backup option. My Vibrant only uses Clockwork and even then it was not fully functional. Some of the basic options would brick the phone.
The latest cm7 stable works great.
Sent from my PC36100 using XDA App
flashing back to sense after "GPS FIX"
I have a few issues with CM7 and I keep switching back to Sense roms because they have been stable. If I do the GPS fix and stay on CM7 will my GPS still work when and if I go back to a Sense ROM?
So this started happening back when I was using CM 7.1 before the new year, one day I wanted to use my camera and it would not load, just gave me a blank screen with no camera controls or anything nor would any apps that required the camera would work either. The only button I could push was the home button to go back to the home screen, if I waited long enough the camera would force close or say something about connecting to the camera. I flashed to a few other aosp roms, don't remember which ones, but the same thing happened, except when I tried the 4.0 evolvr rom, so fed up with having no camera I went back to multiple sense roms where my camera worked on all of them without any issue. Now I'm on the Evo Classic rom and my camera again isn't working, my guess would be due to it being a sense/aosp hybrid.
I had looked up solutions to this problem and the only thing I had found was to hard reset the phone by pulling the batter out for a minute and then putting it back in. I tried this but instead of having to have the batter out for a minute I needed to have the battery out for about an hour, too long or too short and the camera still wouldn't work. I've tried fix permissions, wiping camera data, redownloading and reflashing but nothing has worked.
My current setup is Classic Evo 0.0.6 preview with anthrax test 009 kernel.
My question to you guys is there anything I can do about this or will i just have to stick with pure sense roms in order to have a working camera?
Thanks again for all your help.
I'm no professional, but if you are having issues with using AOSP ROM's, and NOT Sense ROM's, then the logical choice would be to use only Sense ROM's since there seems to be an issue between those types of ROM's and your hardware. It may not be ideal since you obviously seem to prefer the AOSP ROM's, but unfortunately in order to get the functionality you desire you may have to suck it up and go back to Sense. I would suggest the Express ROM by Outerdepth...I'm using it right now and it BAMF! Still in Beta, but most bugs are worked out and everything works, like 4G. It's got good battery life and its really fast. Just a thought.
Try a full wipe of your phone, like data wipe, cache, dalvik, system, etc. Flash a stock ROM then data wipe/factory reset and flash whatever ROM you desire. I've had the same problem and that worked.
Thanks Supreme, it worked, I think I figured out what the problem was too, I kept using a superwipe before flashing roms but this time I didn't and it works.
Frostbiter said:
Thanks Supreme, it worked, I think I figured out what the problem was too, I kept using a superwipe before flashing roms but this time I didn't and it works.
Click to expand...
Click to collapse
No problem man, glad it worked.
I've done loads of searching here, heard about the *#0011# and switching Power Saving mode off, which doesn't apply to AOSP/CM based ROMs, and tons of beating my head against the wall for the past few weeks. I have "keep WiFi awake when screen off" set to "Always." I tried setting my frequency to both 2.4ghz and 5ghz only with no luck. I have tried the stock CM kernel, ktoonsez's Kernel, Lean Kernel with none of them changing anything. I have tried an array of ROMs, including CM10 stable, CM10 nightlies, Task's AOKP, Slim, LiquidSmooth, ... the list goes on.
Long story short: my WiFi will occasionally drop connection to the network and not come back up until I turn off and turn on the WiFi again. If it drops and I go into the list of signals I get, it seems to pick up the network and have decent strength, but it will not reconnect and just says "Saved" underneath the record. How long it takes before it drops ranges anywhere from a few hours to a few seconds. It does seem to happen more often than not with low signals to the router, but I've been in the same room as a router with full bars and it will still happen. I've tried different routers, different router configurations, and different networks entirely, same deal. It does not affect my cell data, just my WiFi.
I am currently trying a stock ROM to see if it happens on stock, and so far it has not occurred. I have done full wipes of all data and clean installing a new ROM, I have tried installing stock and then dirty installing to a new ROM. Nothing seems to solve the problem. I ran a logcat when the problem occurred (lost the log, sorry) and the entry from wpa_supplicant was "AP scan failed". I am at my wits end here. Has anyone had the same problem and found a solution? None of the solutions I've found so far have seemed to work.
Edit:
Stock ROM seemed to have stable WiFi.
Completely formatted phone back to virgin stock, rerooted, installed CWM instead of TWRP (really don't think this would have a difference), factory reset, wiped data, wiped system AGAIN, wiped cache, wiped davlik, installed Task650's AOKP. WiFi seems stable again. Maybe his kernel? Maybe something during wipe? Maybe CWM vs TWRP (unlikely)? I'm unsure if the problem is even solved, honestly, but so far it seems stable. Will keep this updated. I'm going to start installing apps (not from Titanium backup this time) one at a time...
oscooter said:
I've done loads of searching here, heard about the *#0011# and switching Power Saving mode off, which doesn't apply to AOSP/CM based ROMs, and tons of beating my head against the wall for the past few weeks. I have "keep WiFi awake when screen off" set to "Always." I tried setting my frequency to both 2.4ghz and 5ghz only with no luck. I have tried the stock CM kernel, ktoonsez's Kernel, Lean Kernel with none of them changing anything. I have tried an array of ROMs, including CM10 stable, CM10 nightlies, Task's AOKP, Slim, LiquidSmooth, ... the list goes on.
Long story short: my WiFi will occasionally drop connection to the network and not come back up until I turn off and turn on the WiFi again. If it drops and I go into the list of signals I get, it seems to pick up the network and have decent strength, but it will not reconnect and just says "Saved" underneath the record. How long it takes before it drops ranges anywhere from a few hours to a few seconds. It does seem to happen more often than not with low signals to the router, but I've been in the same room as a router with full bars and it will still happen. I've tried different routers, different router configurations, and different networks entirely, same deal. It does not affect my cell data, just my WiFi.
I am currently trying a stock ROM to see if it happens on stock, and so far it has not occurred. I have done full wipes of all data and clean installing a new ROM, I have tried installing stock and then dirty installing to a new ROM. Nothing seems to solve the problem. I ran a logcat when the problem occurred (lost the log, sorry) and the entry from wpa_supplicant was "AP scan failed". I am at my wits end here. Has anyone had the same problem and found a solution? None of the solutions I've found so far have seemed to work.
Edit:
Stock ROM seemed to have stable WiFi.
Completely formatted phone back to virgin stock, rerooted, installed CWM instead of TWRP (really don't think this would have a difference), factory reset, wiped data, wiped system AGAIN, wiped cache, wiped davlik, installed Task650's AOKP. WiFi seems stable again. Maybe his kernel? Maybe something during wipe? Maybe CWM vs TWRP (unlikely)? I'm unsure if the problem is even solved, honestly, but so far it seems stable. Will keep this updated. I'm going to start installing apps (not from Titanium backup this time) one at a time...
Click to expand...
Click to collapse
I've had the same issue with all AOSP based roms. There seems to be an issue with cm 10 which is the base for all AOSP and aokp roms. The touch wiz roms I've tried have no issues and you can go into settings and disable wifi sleep with them.
ak29 said:
I've had the same issue with all AOSP based roms. There seems to be an issue with cm 10 which is the base for all AOSP and aokp roms. The touch wiz roms I've tried have no issues and you can go into settings and disable wifi sleep with them.
Click to expand...
Click to collapse
That's a shame, but I suppose at least I'm not an isolated case. I didn't figure I was considering I could find other people posting about it, but all the posts seem old and never got much attention. So far task650's AOKP seems fairly stable. I haven't had it drop out on me at home yet, though the WiFi does seem to have difficulty coming up after a boot. I suppose worst case scenario I could switch to a TW ROM, but I really like the AOSP experience better :\ (minus TW's camera)
oscooter said:
That's a shame, but I suppose at least I'm not an isolated case. I didn't figure I was considering I could find other people posting about it, but all the posts seem old and never got much attention. So far task650's AOKP seems fairly stable. I haven't had it drop out on me at home yet, though the WiFi does seem to have difficulty coming up after a boot. I suppose worst case scenario I could switch to a TW ROM, but I really like the AOSP experience better :\ (minus TW's camera)
Click to expand...
Click to collapse
In addition to having wifi issues I found all the AOSP/AOKP based roms to have screen wake issues. The camera on non touch wiz based roms is also considerably slower. For now I'm sticking with the stock virgin rom - rooted with toggle mod installed. Wifi on the AOSP/AOKP based roms seems to disable when I go to bed. Then I have disable and enable for it to reconnect. I've tried 10+ roms still haven't found that was stable with the features I want. The only I didn't try was flashing a new kernel. Maybe that will solve both the wifi and screen wake issues. I would rather the rom be stable than have tons of features and being buggy.
ak29 said:
In addition to having wifi issues I found all the AOSP/AOKP based roms to have screen wake issues. The camera on non touch wiz based roms is also considerably slower. For now I'm sticking with the stock virgin rom - rooted with toggle mod installed. Wifi on the AOSP/AOKP based roms seems to disable when I go to bed. Then I have disable and enable for it to reconnect. I've tried 10+ roms still haven't found that was stable with the features I want. The only I didn't try was flashing a new kernel. Maybe that will solve both the wifi and screen wake issues. I would rather the rom be stable than have tons of features and being buggy.
Click to expand...
Click to collapse
If you are interested in running an AOSP/AOKP ROM still, give Task650's AOKP a try. After a fresh wipe, to virgin stock, to rooted stock, wipe, and then to his ROM, it seems stable. I haven't had a WiFi drop for about 24 hrs, and it seems stable. I did have some WiFi problems on the first boot or two (WiFi wouldn't be on at boot and a tad stubborn to come on, stable after it came on), but that seems to have solved itself now... I say seem though, because like I said in my OP it can sometimes take hours to drop WiFi. He does use a kernel that isn't the CM10 kernel, so maybe that has something to do with it?
I'm loading my apps back on in waves to try and see if maybe it's an app. So far it's still stable.. I'm about to start downloading all my Spotify playlists which it typically would **** out on, so we'll see. If it starts again I'll be going back to stock.
oscooter said:
If you are interested in running an AOSP/AOKP ROM still, give Task650's AOKP a try. After a fresh wipe, to virgin stock, to rooted stock, wipe, and then to his ROM, it seems stable. I haven't had a WiFi drop for about 24 hrs, and it seems stable. I did have some WiFi problems on the first boot or two (WiFi wouldn't be on at boot and a tad stubborn to come on, stable after it came on), but that seems to have solved itself now... I say seem though, because like I said in my OP it can sometimes take hours to drop WiFi. He does use a kernel that isn't the CM10 kernel, so maybe that has something to do with it?
I'm loading my apps back on in waves to try and see if maybe it's an app. So far it's still stable.. I'm about to start downloading all my Spotify playlists which it typically would **** out on, so we'll see. If it starts again I'll be going back to stock.
Click to expand...
Click to collapse
I did give that rom a try. I had the same wifi issue when I went to bed. It also happens after the phone is rebooted. In addition I was getting the screen wake issue. Task's rom is still based on cm 10 so will have the same bugs. Maybe changing the kernel to task's own kernel or the other AOSP kernel. I'll give a try one of these days. Let me know how that works out for you.
Do you guys having this problem have "Avoid poor connections" checked in the Wifi advanced settings? I don't remember if CM10 has this, but AOKP does. I expected that this setting would cause the phone to switch to a better AP if the signal was low but it seems like it just stops Wifi data completely. After disabling this setting I haven't had any issues.
I've been running CM10 nightlies with the CM10 kernel since late November and haven't had any issues with WiFi. I am on my 2nd GS3, first one returned due to phone speaker (not the speakerphone on the back) and on that one my WiFi was sketchy. Not sure if it was a hardware problem, or CM10 merged a fix close to when I swapped out devices. Either way, I use the latest twrp recovery flashed from GooManager and Formula84 10/12 Gapps. I update daily with the CM Updater, and haven't had any issues other than what is already reported to be a bug on CM (which in all reality is, nothing, since I NEVER use Bluetooth)
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
I'm only asking for reference, this happened to me somewhat on CM10, and my roommate on his Stock GS3. Anyone with these issues using a Netgear router? We dumped ours for an Asus and haven't seen a problem since. I hate netgear so much...
goodtimes50 said:
Do you guys having this problem have "Avoid poor connections" checked in the Wifi advanced settings? I don't remember if CM10 has this, but AOKP does. I expected that this setting would cause the phone to switch to a better AP if the signal was low but it seems like it just stops Wifi data completely. After disabling this setting I haven't had any issues.
Click to expand...
Click to collapse
Avoid poor connections is always unchecked for me. I also make sure wifi is set to never sleep.
---------- Post added at 11:35 PM ---------- Previous post was at 11:33 PM ----------
thacounty said:
I'm only asking for reference, this happened to me somewhat on CM10, and my roommate on his Stock GS3. Anyone with these issues using a Netgear router? We dumped ours for an Asus and haven't seen a problem since. I hate netgear so much...
Click to expand...
Click to collapse
I'm using the linksys e4200v2 router. Never had any issues with any of my devices except after I flash AOSP/AOKP based roms. I have 8 devices connected wirelessly with no issues.
My router at home is a Netgear. Not sure about work. The weird part for me is that I didn't use to have these problems with AOSP ROMs, not that I remember anyways. It seems like a recent development in the past few weeks.
Still having decent luck with task650's ROM. It did happen to me once last night at home but it's been stable as a rock otherwise. If it starts happening more I'm gonna flash stock. If it continues to happen from there I'll consider it a hardware defect and go ***** to AT&T.
Sent from my SGH-I747 using xda app-developers app
oscooter said:
My router at home is a Netgear. Not sure about work. The weird part for me is that I didn't use to have these problems with AOSP ROMs, not that I remember anyways. It seems like a recent development in the past few weeks.
Still having decent luck with task650's ROM. It did happen to me once last night at home but it's been stable as a rock otherwise. If it starts happening more I'm gonna flash stock. If it continues to happen from there I'll consider it a hardware defect and go ***** to AT&T.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I just tried two roms (liquid smooth and tasks aokp). Had wifi issues with both of them after reboot. I decided to try two custom kernels (underwear and ktoonsez). Still experienced wifi saying not in range. The issue seems to be with the latest cm base which is used in all AOSP and AOKP roms. I hope this issue is fixed with the new cm 10.1 base. I guess I'll be stuck using only touch wiz roms now.
Found a great app that solves the wifi issue. It's called smart wifi toggler. Wifi reconnects after reboot now and remains connected when I go to sleep.
ak29 said:
I did give that rom a try. I had the same wifi issue when I went to bed. It also happens after the phone is rebooted. In addition I was getting the screen wake issue. Task's rom is still based on cm 10 so will have the same bugs. Maybe changing the kernel to task's own kernel or the other AOSP kernel. I'll give a try one of these days. Let me know how that works out for you.
Click to expand...
Click to collapse
It sounds like something is going wrong when you flashed the ROM. Task's AOKP isn't CM based (he cherry-picks from it, but builds from source), and I've never had a Wi-Fi issue with it.
Sent from my SGH-I747 using xda app-developers app
ak29 said:
Found a great app that solves the wifi issue. It's called smart wifi toggler. Wifi reconnects after reboot now and remains connected when I go to sleep.
Click to expand...
Click to collapse
Thanks for the heads up! I still have been having good luck with task650's ROM, but I will try this out on other ROMs!
guitarpunk8403 said:
It sounds like something is going wrong when you flashed the ROM. Task's AOKP isn't CM based (he cherry-picks from it, but builds from source), and I've never had a Wi-Fi issue with it.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I've been having good luck as well with tasks, but I don't know what could be going wrong when flashing a CM based ROM that is so consistent, unless it's either a hardware issue or something in their code base.
Sent from my SGH-I747 using xda app-developers app
oscooter said:
Thanks for the heads up! I still have been having good luck with task650's ROM, but I will try this out on other ROMs!
I've been having good luck as well with tasks, but I don't know what could be going wrong when flashing a CM based ROM that is so consistent, unless it's either a hardware issue or something in their code base.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
No prob. I'm finally able to enjoy tasks aokp now that I got the wifi issue solved with using smart wifi toggler. It's a great rom, with tons of features and customizations.
I've been ignoring custom roms for about 6 months after I tried one previously and found the bluetooth bug. Just curious if this has found a fix at this point? I'd love to run a CM10.1 rom, but bluetooth audio is a must have for me.
cegna09 said:
I've been ignoring custom roms for about 6 months after I tried one previously and found the bluetooth bug. Just curious if this has found a fix at this point? I'd love to run a CM10.1 rom, but bluetooth audio is a must have for me.
Click to expand...
Click to collapse
the issues from 6 months ago have been gone for sometime now.
fantastic, thank you.
Life's been pretty crazy so i'm out of the loop on where everything has progressed. Once i get AT&T to warranty my phone for the GPS issues i'm having i'll try out one of the new builds.
Bluetooth audio has been working fine
But from my experience there have been problems with Bluetooth dialing.
A recent update of slimbean (version 6) seems to have corrected the problem.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I don't know that the issue really is fixed in 4.2.2. Doesn't seem to matter what ROM I run (I've tried CM, Carbon, AOKP), I can't get Bluetooth to work at all. It won't scan/find any of my devices or even turn on. I've resorted going back to stock rooted.
Has anyone found a work around or fix?
If bluetooth worked, it wont be 4.2.2. Best to go back to 4.1.x.
Sent from my SAMSUNG-SGH-I747 using xda premium
kt314 said:
I don't know that the issue really is fixed in 4.2.2. Doesn't seem to matter what ROM I run (I've tried CM, Carbon, AOKP), I can't get Bluetooth to work at all. It won't scan/find any of my devices or even turn on. I've resorted going back to stock rooted.
Has anyone found a work around or fix?
Click to expand...
Click to collapse
once in the past, when the CM roms were having bluetooth problems, I tried a different kernel and that fixed issues. The BMS Kernel is pretty stable and great performance/battery. you might give that a try.
So I've been having a bit of trouble with my t989 lately, when I try unlocking the phone I will either get a black screen (the lock screen will appear for a split second before going blank if I hit the lock button again) or it won't track my finger movements on the screen. If I manage to unlock the device I end up seeing numerous graphic glitches ranging from the bar at the top w/ the clock/battery meter just gone and the keyboard not working.
I'm runing CM9.0.0 because I had issues with 10.2 (battery wouldn't charge) and 10.1.3 (similar to my lock screen issues but not as severe, still agitating) and also 9.1 which had the same exact issues as I'm having now. I've tried installing with different gapps but the same thing happens. The phone will work for a day or two, then the glitches come. After resetting, everything is normal for a day or so, then it's normal a few hours, etc. The time is getting narrower between reboots and it's a bit frustrating.
Does anyone know what I could be doing wrong, if anything? I flash via twrp and wipe, then install the rom, then install gapps, then reboot, wait 20min, reboot, and go about my business w/ the setup and such. I would be fine going back to 10.1.3 but jellybean roms and snapchat don't really like to work together on this phone for some reason. It's really the only app I use because it seems like the only way my friends want to communicate nowadays, so I'd prefer to stay on ics if possible...
If anyone can give any insight I'd really appreciate it
greenghoul said:
If anyone can give any insight I'd really appreciate it
Click to expand...
Click to collapse
Have you tried using Odin to flash back to stock? That is usually the recommended step if you are having problems with custom ROMs.
And the newest stock is 4.1.2, so at least you wouldn't have to be on ICS.
meekrawb said:
Have you tried using Odin to flash back to stock? That is usually the recommended step if you are having problems with custom ROMs.
And the newest stock is 4.1.2, so at least you wouldn't have to be on ICS.
Click to expand...
Click to collapse
I'll give that a try. Odin is just the program used to root originally, correct? Also, I want to stay on ICS if possible. So after doing that I'm going to try CM9 again and see how that works.
Anyway, the past few days I've been using AOKP mr2 milestone 1 and it's been okay. For some reason the battery life is bad even with juice defender and a task killer taking care of things. In a matter of minutes after clearing tasks I'm down from ~350mb of ram free to 60. Is that normal with that rom?
I'm not sure what to do at this point. I'm not the best with technology but i figured i was smart enough to figure this out...
bump.
I still haven't tried flashing w/ odin yet. Does anyone know where I can find a gingerbread stock rom? I've been looking for a while and can only find the jellybean one. Since I want to stay on ICS what I want to do is go from gingerbread and up to that rather than downgrading from the jellybean stock rom if that makes sense.