My galaxy s3 on tmobile has been overheating, dying fast, charging slow, and randomly rebooting the past week. I'm running AOKP MR1 milestone. I'm thinking maybe AOKP is the issue, but not too sure.
What are some other stable good vanilla 4.2.2 roms I can try? thanks
Probably.
I'm running AOKP without any issue. What have you installed recently? Did you flash custom kernel, overclock cpu, change cpu voltages, etc...? Download OS Monitor app and see which processes are eating cpu and your battery. Maybe it's time to wipe everything clean: factory reset, wipe external sdcard, and reflash the ROM. An sdcard full of stuffs can cause the media scanner process to run long and eat up battery.
S-beamed from my GSIII via xda premium
I wouldnt go as fsr as blaming the rom right away, especially if its a milestone. More kernel related and or user error. Give us more info to help you solve this so you can use your the way you want to.
Sent from my SGH-T999 using xda premium
There have been problems with the new kernel versions that have been merged into the ROMs. Take CM10.1 for example, each nightly is iffy. You never know when it's gonna be buggy or not. So far, my phone has been constantly rebooting.
vx117 said:
There have been problems with the new kernel versions that have been merged into the ROMs. Take CM10.1 for example, each nightly is iffy. You never know when it's gonna be buggy or not. So far, my phone has been constantly rebooting.
Click to expand...
Click to collapse
That's why people use custom kernels. Not just for overclocking, but also for picking up the slack on the CM kernel.
More like kernel related but yes aokp and cm10.1 can mess up your phone at times
Aerowinder said:
That's why people use custom kernels. Not just for overclocking, but also for picking up the slack on the CM kernel.
Click to expand...
Click to collapse
Yes, but even with custom kernels it can get buggy. No kernel is one-size fits all since each chip is unique. You gotta pick and choose which kernel works best for your phone.
Kyle Chen said:
My galaxy s3 on tmobile has been overheating, dying fast, charging slow, and randomly rebooting the past week. I'm running AOKP MR1 milestone. I'm thinking maybe AOKP is the issue, but not too sure.
What are some other stable good vanilla 4.2.2 roms I can try? thanks
Click to expand...
Click to collapse
I was having that issu as well but it was with touch wiz roms and kernels it actually ended up being a dud phone and battery. .. I have done a warranty exchange and it fixed it I also got an anker battery too and its been doing good only gets hot when I have it on charge and use it.. so it would ight not be just the rom. Try a different kernel see if its the battery getting hot and go from there. Isolation is key bud:thumbup:
Sent from my SGH-T999 using Tapatalk 2
This morning my phone was stuck on the AOKP boot logo and it was overheated like crazy. I did a battery pull and waited for the phone to cool down. After that I booted it back up, but the battery drained pretty fast and the phone still heated up.
I did not flash any custom kernals or anything. Just AOKP milestone 1.
Maybe I will wipe the entire phone and reflash aokp.
OR
Are there any roms that are better than AOKP and what is the best kernal to flash?
Thanks.
+1
I've been running AOKP since 2 hours after I got my d2tmo, initially KAsp3rd's unofficial builds, and now the official "nightly" builds... I have been using a very stable build since January, but recent official developments have me flashing regularly again.
Every single build since JB 4.2.2 MR1 has been very unstable on my device, somewhat randomly rebooting quite regularly... I say "somewhat" randomly because there are a certain few actions I can perform which will cause reproducible immediate reboots on demand, including but not limited to trying to DISABLE* USB Debugging. I've noticed that the device is far more likely to reboot itself when attempting to run apps as superuser. I noticed that Koush's Superuser app/infrastructure is embedded/integrated in the ROM and when I installed the latest version from the Google Play Store, it said that my su binary was out of date, so I updated it... It didn't resolve the random reboots, but when the device did reboot next, it performed some additional setup steps, including prompting me for my first & last name which was really odd because the initial setup had, I thought, been completed, and the device had been rebooted (by itself mostly) at least a dozen times prior to this.
I suspect these issues might have something to do with the superuser integration in the ROM and I ask that you who are experiencing similar random reboots take note of any patterns such as whether it occurs more often when attempting to perform superuser privilege escalation.
Currently I'm testing whether setting "Superuser Access" to "Disabled" helps at all. I'll report my findings once a conclusion is established.
*I'm trying to disable it to troubleshoot why the device doesn't show up when I issue `./adb devices` on my PC running Ubuntu 12.10 Linux; it doesn't even show up in the list of connected USB devices when I issue a `lsusb` command which is weird. I've rolled back to my backup of the January AOKP 4.1.2 build and confirmed that the device is visible to adb, so it doesn't seem to be an issue with my hardware...
P.S. I've posted about it in the new official d2tmo AOKP Nightly thread on the RootzWiki Forum (linked above).
---------- Post added at 11:29 AM ---------- Previous post was at 10:50 AM ----------
Disabling Superuser didn't seem to help at all. It has still rebooted itself twice since then.
[KERNEL][4.2.x] dkp - d2tmo - 4/24/13
I installed the following kernel I found here on XDA and I've had 2 crashes in the last 2 days which is acceptable to me.
dkp-3.4-d2att-d2tmo-20130424.zip
[KERNEL][4.2.x] dkp - d2tmo - 4/24/13
PM me for a modified SlimBean build I use if interested. No random reboots and I have had the same issue in the past. Also, you could try wiping 3 times (cache,dalvik, factory reset and system) and then install KT747. Its the most up to date kernel as far as the patches and drivers go.
Sent from my SGH-T999 running Chihuahua v1 ROM
re: acceptable
Ch4m3l30n said:
I installed the following kernel I found here on XDA and I've had 2 crashes in the last 2 days which is acceptable to me.
dkp-3.4-d2att-d2tmo-20130424.zip
[KERNEL][4.2.x] dkp - d2tmo - 4/24/13
Click to expand...
Click to collapse
Why should any amount of crashes or random reboots be "acceptable" to anyone when there are so many
other roms in these xda forums to choose from which do not crash at all and are full of excellent features? LOL
Make a backup. Wipe cache and data. Then try another rom
Sent from my SGH-T999 using xda premium
My phone is actually not overclocked
This morning it was so hot that it literally burned my hands.
I am looking for a rom with similar features as AOKP like virtual buttons etc, no issues.
Kyle Chen said:
My phone is actually not overclocked
This morning it was so hot that it literally burned my hands.
I am looking for a rom with similar features as AOKP like virtual buttons etc, no issues.
Click to expand...
Click to collapse
did you try reformatting your sdcard(s), factory reset, format /system partition (via recovery), and reflash the ROM? maybe just reformat the sdcards first, and see if that helps.
S-beamed from my GSIII via xda premium
Kyle Chen said:
<snip>
Are there any roms that are better than AOKP and what is the best kernal to flash?
Thanks.
Click to expand...
Click to collapse
Kyle, what ROM did you finally settle on? I ask because I'm looking for one, am contemplating AOKP, but came across your complaints/observations here, and am reconsidering.
bwb8771 said:
Kyle, what ROM did you finally settle on? I ask because I'm looking for one, am contemplating AOKP, but came across your complaints/observations here, and am reconsidering.
Click to expand...
Click to collapse
I ended up flashing like a touchwiz galaxy s5 themed kitkat rom, which I have been using since September. Before that I used cyanogenmod 11. Haven't tried AOKP in a long time. When I get time I plan to flash some lolipop rom I guess.
Is there any activity on AOKP any longer, loved rom but it looks like 10/18/14 is the last build i can find.....
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.
I have a Gnex rooted and unlocked - DroidModderX - I'm currently running Android Revolution HD very simple mod, barely has anything changed. This mod is 4.0.2. I have tried installing gummy, AOSP, a bunch of other ones. it always says error installing it. Anybody have any advice. Any way to get my Rogers Gnex to 4.0.3?
Thank you
does the error say something like a word i think its like outset or something (100% sure this is not the word) then alot of numbers after? that happens with mine too, but the rom installs fine.
Do you have the latest Clockwork Recovery Mod installed?
Also are you doing a full wipe before you attempt to flash the ROM?
doublea500 said:
does the error say something like a word i think its like outset or something
Click to expand...
Click to collapse
I have seen it say "offset" when I was using the Codename Android ROM.
I did not wipe my cache and data, I was scared that if I did that and it didn't work... I would have to start over again. Download all my programs. configure
Sometimes it doesn't download any of my programs. I restarted it and installed my old OS three times to get it to download my contacts.
I will see the exact thing it says to me soon. thanks guys
You *must* do a full wipe before going to a 4.0.3 ROM. Since your /system is still there, that is what is causing the issue.
However, use the Backup feature in CWM and you can restore it if anything goes bad.
The wipe will knock out your /system, /cache, and /dalvik but will not touch anything on your SD card which holds you photos, etc.
Wish me luck...
I already did a backup - FULL - in Galaxy Nexus Toolkit.
I'm thinking of going with AOKP M3. Let me know if you have any other suggestions.
I hope that is enough to get my phone back to the way it was...
I would like to change the Kernel too. Do you recommend any? I was thinking about franco kernel.
Thanks guys
Good luck!
I have tried three ROMs now and I greatly prefer AOKP the most. Currently I am on AOKP M3 using Faux's kernel but I was running AOKP M3 with Leankernel 1.9.0 with great results.
My battery drain seems a *little* bit more on Faux's but I have only been running it for one day.
Every kernel I try, the battery life improves over a couple days or more so I am going to let it settle.
I tried doing the change. I wiped everything that you could choose and it still gave me the same error. Didn't do it. I have no idea what the problem is. I have no idea how to get my phone to 4.0.3. F***
How about actually mentioning the error you're seeing as opposed to just winging?
It will work so it has to be something you're doing that's wrong
Was installing this rom via TWRP
http://forum.xda-developers.com/showthread.php?t=1844657
and ended up in a infinite bootloop. Also installed KKO.12 kernel, maybe they didn't play nice together. Currently have the phone in download mode and tried to do a recovery with an older 2.3.6 rom from here
http://galaxys2root.com/t-mobile-ga...ck-t-mobile-galaxy-s2-sgh-t989-android-2-3-6/
Write fails everytime. Odin Mode currently says custom binary download: no, is this why it keeps failing? Any other good recovery roms I can use Odin to flash?
I've just recently got the same phone as you and have been looking for recovery/stock roms before I flashed any new custom rom. Luckily there is a recovery rom for our phone!
Check out this thread. Try flashing the stock Koodo rom with Odin, all the instructions are there and hopefully it will work.
Good luck!
Thanks, was actually already downloading that rom and flashed it. When it finished flashing, I thought it was weird that it didn't automatically reboot, so I powered it off manually, and it rebooted saying there was an error, went back to read the thread, told me not to touch the phone and it'll reboot automatically. Reflashed again, back on stock rom now. Thanks again!
On another note, I was trying different roms to see which would give me the best battery love, and funny enough, it seems like the stock koodo rom has the best battery life. Back to stock and there to stay.
Arkv said:
Thanks, was actually already downloading that rom and flashed it. When it finished flashing, I thought it was weird that it didn't automatically reboot, so I powered it off manually, and it rebooted saying there was an error, went back to read the thread, told me not to touch the phone and it'll reboot automatically. Reflashed again, back on stock rom now. Thanks again!
On another note, I was trying different roms to see which would give me the best battery love, and funny enough, it seems like the stock koodo rom has the best battery life. Back to stock and there to stay.
Click to expand...
Click to collapse
I also am with koodo and experienced the best battery life by far out of any ROM!
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
cwillison94 said:
I also am with koodo and experienced the best battery life by far out of any ROM!
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
What rom's have you guys been trying?
I also have the Koodo version of the SII X. Stock was alright battery wise I guess, but it suffered from lag and such.
I've been running Slimbean 3.0 for about a month now. Very stable, very smooth. I get about 30hrs with 4 to 5 hours screen time. I never even checked on stock, but what kind of times are you guys getting with stock koodo?
I'm in the process now of doing a back up, going to flash the unofficial build of Slimbean 3.1. Supposed to be just as good battery wise.
OnlineDiscord said:
What rom's have you guys been trying?
I also have the Koodo version of the SII X. Stock was alright battery wise I guess, but it suffered from lag and such.
I've been running Slimbean 3.0 for about a month now. Very stable, very smooth. I get about 30hrs with 4 to 5 hours screen time. I never even checked on stock, but what kind of times are you guys getting with stock koodo?
I'm in the process now of doing a back up, going to flash the unofficial build of Slimbean 3.1. Supposed to be just as good battery wise.
Click to expand...
Click to collapse
Since you seem to be liking the SB ROMs, check out the All-Star Team SB Rom variant. It's basically the same as the original, but with more features. I've been running it for several days now and it's been performing smoothly. You'll also be getting updates more often as the team is constantly releasing updates. Cheers!
I have searched via various keywords for days and have not found an answer to my problem yet. I have only run across one other post (on another forum) that describes exactly my issue and they are asking the exact same question I have with no response.
I am using the AT&T Samsung Galaxy S3. I have downloaded CM 10.0.0 stable d2att on several occasions (different computers even), verified the md5, and installed on my phone. I have used CWM, CWM Touch, and TWRP to install hoping it was an issue there. Regardless of what I have done, I have the same issue addressed below:
I make or receive a phone call. No problems answering a phone call when it comes in. However when I hang up, the screen immediately goes back to sleep (which seems to be normal for the Nexus after researching). However, if I press the power button after the call is ended, the screen does not turn on at all. The hardware buttons (menu and back) do light up however and they remain lit. Regardless of what I do my phone stays stuck in this mode unless I hold the power button for about 10 seconds or so and force it to reboot, at which point it operates normal with no issues until my next phone call.
Has anyone experienced this issue and if so did you find a way to resolve it that does not require rebooting the phone? Right now this is the only thing keeping me from using the ROM as my daily driver.
Imo, AOSP-based ROMs run best when coming from stock. I flash back to touchwiz the before flashing them. Not sure if you've tried this.
Also, I had some small issues with the exact same rom that kept me from making it my daily driver. If you want stability, I can vouch for AOKP 4.1.2. I'm in no hurry for 4.2 with this rom running so well with no bugs or glitches
xBeerdroiDx said:
Imo, AOSP-based ROMs run best when coming from stock. I flash back to touchwiz the before flashing them. Not sure if you've tried this.
Also, I had some small issues with the exact same rom that kept me from making it my daily driver. If you want stability, I can vouch for AOKP 4.1.2. I'm in no hurry for 4.2 with this rom running so well with no bugs or glitches
Click to expand...
Click to collapse
Thanks. Seems that it was destined not to work. Oh well. I was on TW nearly everytime. I will give AOKP a shot. Should like it equally as well because I prefer AOSP roms. I am assuming you restore nandroid stock...or do you odin flash?
aybarrap1 said:
Thanks. Seems that it was destined not to work. Oh well. I was on TW nearly everytime. I will give AOKP a shot. Should like it equally as well because I prefer AOSP roms. I am assuming you restore nandroid stock...or do you odin flash?
Click to expand...
Click to collapse
I don't think it matters but I usually restore my tw/stock nandroid because it's right there and I don't lose root.
When I flashed the rom im currently running, I formatted /system /data and battery. Not sure if you care or need that info, just passing it on as this device has run really well for me on this OS.
I also flashed the Nexus 4 camera/gallery and the TW clock. The aokp camera is lame-o, and controlling the alarms is easier on the TW clock.
If you can't find them on the forum here (where I got them), PM me your email and I will send you the zips if you are interested. I believe I flashed them both in cwm, wiped cache/dalvik and then adjusted permissions in root browser to rw-r-r
AOKP's 4.1.2 jellybean milestone 1 is still on goo.im
xBeerdroiDx said:
I don't think it matters but I usually restore my tw/stock nandroid because it's right there and I don't lose root.
When I flashed the rom im currently running, I formatted /system /data and battery. Not sure if you care or need that info, just passing it on as this device has run really well for me on this OS.
I also flashed the Nexus 4 camera/gallery and the TW clock. The aokp camera is lame-o, and controlling the alarms is easier on the TW clock.
If you can't find them on the forum here (where I got them), PM me your email and I will send you the zips if you are interested. I believe I flashed them both in cwm, wiped cache/dalvik and then adjusted permissions in root browser to rw-r-r
AOKP's 4.1.2 jellybean milestone 1 is still on goo.im
Click to expand...
Click to collapse
I actually downloaded the camera/gallery apk for 4.2 as well as the keyboard. Already installed and running. Prefer both over the 4.1.2 versions installed on AOKP and CM10. Thanks for the info.
Hey all -
I have a T-Mobile Galaxy SIII with TWRP, AOKP JB Milestone 5 and GooManager. I got a pop-up for AOKP JB Milestone 6 this morning, so I downloaded it and added that file, Lean Kernel 2.9 and gapps (latest that could be downloaded) to the flash list. I set my Dalvik cache to clear before flashing anything, then rebooted the phone to flash everything. Immediately after the flash, the phone seemed to reboot, but with a blank screen. After a while, the capacitive buttons on the front started working and when I plugged the phone into my computer the file transfer program popped up.
However ... at no point can I ever get anything to display on the screen. I've tried rebooting into recovery (volume up, home button, power button) and nothing. I don't really care about the data on my phone, I have proper backups of everything. But what I can't seem to do is get it to a point where I can recover it. What are my options here if rebooting into recovery doesn't work?
Thanks!
As an addendum, the phone is clearly booted into the OS. I have a blinking notification LED that indicates a new e-mail, and calls placed to the phone cause it to ring. I just can't see .... anything on it.
I was able to get into TWRP, somehow. I took out my T-Mobile SIM card and had it plugged into USB. I held down the recovery combo and then it booted up into recovery. It also displayed the Galaxy SIII white splash screen for the first time since the bad flash. What the hell.
chuffykow said:
I was able to get into TWRP, somehow. I took out my T-Mobile SIM card and had it plugged into USB. I held down the recovery combo and then it booted up into recovery. It also displayed the Galaxy SIII white splash screen for the first time since the bad flash. What the hell.
Click to expand...
Click to collapse
so was you able to use your phone again i say go back to a nandroid you have or flash a rom that you know works good on your phone without that white screen and trouble shoot from there that it very strange indeed if you get success with the other just try posting in the ROM thread that you flashed you could possibly get more help where it happened :good:
I went back to AOKP Milestone 5 after doing a full wipe. I saw a number of graphics changes in the Milestone 6 code review, so it's possible that had something to do with it. In any case, I'm no longer panicing
Does mr6 use the 3.4 kernel? If yes, then you were using the wrong version of leankernel.
Ya its all kernel related and user error.
Aerowinder said:
Does mr6 use the 3.4 kernel? If yes, then you were using the wrong version of leankernel.
Click to expand...
Click to collapse
mt3g said:
Ya its all kernel related and user error.
Click to expand...
Click to collapse
I assumed it was user error. I just wanted to lay out the steps I took, so I could get some help on a recovery path. I thought that a JB based ROM would work with any kernel that supports JB. Looks like I was wrong.
chuffykow said:
I assumed it was user error. I just wanted to lay out the steps I took, so I could get some help on a recovery path. I thought that a JB based ROM would work with any kernel that supports JB. Looks like I was wrong.
Click to expand...
Click to collapse
Nope, JB can be AOSP, TouchWiz, 4.1, 4.2, 4.2.2, 3.0 kernel, 3.4 kernel. Just need to read and make sure you know what you're doing before just doing it. That's why I frown at people being lazy (not just you) and not reading the forums and such, and just using apps to update and flash.
mt3g said:
Nope, JB can be AOSP, TouchWiz, 4.1, 4.2, 4.2.2, 3.0 kernel, 3.4 kernel. Just need to read and make sure you know what you're doing before just doing it. That's why I frown at people being lazy (not just you) and not reading the forums and such, and just using apps to update and flash.
Click to expand...
Click to collapse
Thank's for the condescension, I appreciate being called lazy. I might not have an encyclopedic knowledge of Everything Android, but between the knowledge I do have and the details I read on the AOKP release page, I saw nothing that indicated I _couldn't_ run LeanKernel, especially when it was only a point release on the same ROM I was previously using.
I had a look at the changelog that's available on their page. It's pretty lame. http://gerrit.sudoservers.com/#/q/status:merged,n,z that one will probably have the kernel info. A good rule of thumb is when you flash a new rom, wait until the kernel is up to date (release date). For instance, don't flash a 3/01 kernel on a 4/24 rom - wait for kernel update.
I don't recommend flashing anything with the 3.4 kernel right now. Even if you manage to pull off stability, it's still laggy and eating about 3x the battery it should. This goes for the custom kernels, too. I'll put up with stability issues, but can't deal with bad battery. Already bad enough as it is. Need my phone during the day and not near a charger.
chuffykow said:
Thank's for the condescension, I appreciate being called lazy. I might not have an encyclopedic knowledge of Everything Android, but between the knowledge I do have and the details I read on the AOKP release page, I saw nothing that indicated I _couldn't_ run LeanKernel, especially when it was only a point release on the same ROM I was previously using.
Click to expand...
Click to collapse
calm down lol, you could have read up any of the kernel threads that there are some compatible issues with kernels and roms right now.
Aerowinder said:
I had a look at the changelog that's available on their page. It's pretty lame. http://gerrit.sudoservers.com/#/q/status:merged,n,z that one will probably have the kernel info. A good rule of thumb is when you flash a new rom, wait until the kernel is up to date (release date). For instance, don't flash a 3/01 kernel on a 4/24 rom - wait for kernel update.
I don't recommend flashing anything with the 3.4 kernel right now. Even if you manage to pull off stability, it's still laggy and eating about 3x the battery it should. This goes for the custom kernels, too. I'll put up with stability issues, but can't deal with bad battery. Already bad enough as it is. Need my phone during the day and not near a charger.
Click to expand...
Click to collapse
Thanks for the tip! I appreciate it.