Hello,
I've installed the 1.4 GHZ kernel to my Galaxy Tab 10.1 P7510.
The kernel was working perfectly with SetCPU 1.4.
I've played many games like Asphalt 6 and watching many videos. So, When the charge deceased to 1% I've plugged the charger.
Now, I can see i have fully charged. But when i use my tablet the charging will deceasing very fast (sometimes my tablet will turn off it's self).
I did many things like:
Flashing a new ROM with Odin
Cleaning Battery Stats
Remove the 1.4 Kernel
But no one of them solved my problem.
My battery now deceasing very fast. So, When i have 80% i will lost it within 10 min. But when i reboot the tablet i see there's 80% charging.
What can i do please?
start reading
http://forum.xda-developers.com/showthread.php?t=1215182
This is a know and serious issue caused by 3rd party ROMs and Kernels. Unfortunately Devs refuse to warn people about it in their threads.
Yet another victim of 3rd party ROMs/Kernels......
ArtificialSweetener said:
This is a know and serious issue caused by 3rd party ROMs and Kernels. Unfortunately Devs refuse to warn people about it in their threads.
Yet another victim of 3rd party ROMs/Kernels......
Click to expand...
Click to collapse
I re flashed the OTA ROM. But does not fixed.
web.designer.iq said:
I re flashed the OTA ROM. But does not fixed.
Click to expand...
Click to collapse
Yes, your battery calibrator has been damaged by 3rd party ROM/Kernel you flashed. This is very serious issue for your tablet. Read this thread http://forum.xda-developers.com/show....php?t=1215182
Hopefully you can try to recalibrate the hardware but it does not look like it works for many. You might have to send it in for repair. Remember NEVER flash 3rd party ROM/Kernel. There are simply too many major and serious issues with them that can damage your tablet. Such the case here.
web.designer.iq said:
I re flashed the OTA ROM. But does not fixed.
Click to expand...
Click to collapse
don't panic, you should be fine. Read that thread and you will find explanation and the solution for battery calibration problem.
ArtificialSweetener said:
Yes, your battery calibrator has been damaged by 3rd party ROM/Kernel you flashed. This is very serious issue for your tablet. Read this thread http://forum.xda-developers.com/show....php?t=1215182
Hopefully you can try to recalibrate the hardware but it does not look like it works for many. You might have to send it in for repair. Remember NEVER flash 3rd party ROM/Kernel. There are simply too many major and serious issues with them that can damage your tablet. Such the case here.
Click to expand...
Click to collapse
this is speculatory.
http://forum.xda-developers.com/showpost.php?p=17863797&postcount=17
web.designer.iq,
vlad_z led you in the right direction. if you cannot rectify the issue, then a swap may be in order. i know of one person who had recurring issues (for a while), swapped, and never had an issue again.
5thElement has so many different screen names. geese. what a waste.
---------- Post added at 06:48 PM ---------- Previous post was at 06:47 PM ----------
i would recommend following vlads advice bro. dont listen to Artificial.
ArtificialSweetener said:
This is a know and serious issue caused by 3rd party ROMs and Kernels. Unfortunately Devs refuse to warn people about it in their threads.
Yet another victim of 3rd party ROMs/Kernels......
Click to expand...
Click to collapse
Everyone ignore ArtificialSweetner. this is the user previously known as 5thElement. He was banned so he created a new account with this name.
ArtificialSweetener said:
This is a know and serious issue caused by 3rd party ROMs and Kernels. Unfortunately Devs refuse to warn people about it in their threads.
Yet another victim of 3rd party ROMs/Kernels......
Click to expand...
Click to collapse
I don't think is a 3rd Party ROM issue!!
Because I don't have a custom ROM
Anyway, I'm going to fix it by empty the battery. I don't know if this will be fixed.
web.designer.iq said:
I don't think is a 3rd Party ROM issue!!
Because I don't have a custom ROM
Anyway, I'm going to fix it by empty the battery. I don't know if this will be fixed.
Click to expand...
Click to collapse
Thats funny because it completely contradicts what you said in your original post. You state you flashed 1.4ghz kernel (3rd party kernel), and that you flashed a new ROM with Odin (3rd party)
It does not matter if you return back to stock ROM. Once the damage is done its done.
ArtificialSweetener said:
Thats funny because it completely contradicts what you said in your original post. You state you flashed 1.4ghz kernel (3rd party kernel), and that you flashed a new ROM with Odin (3rd party)
It does not matter if you return back to stock ROM. Once the damage is done its done.
Click to expand...
Click to collapse
you speculated and you were wrong.
he stated he 'flashed a rom'. you assumed a 'custom' rom.
accept that you were incorrect and actually try to help someone.
Related
running latest version of geewiz with leankernel and getting unsupported battery with samsung 1800mah. Im well aware of the reason behind this, but I thought this issue was resolved? I tried searching for a solution and cant come up with anything, and please dont say "run cm7", because I know that it solves the unsupported battery issue. Is there something I can change to fix this
Third party battery issue is not resolved in leankernel. You need to switch to TKSGB kernel. It's not a problem there.
kasmanavt said:
Third party battery issue is not resolved in leankernel. You need to switch to TKSGB kernel. It's not a problem there.
Click to expand...
Click to collapse
nice! Thanks. and would you know what needs to be modified in order to get it to work with lean kernel?
Oh no, I'm not that smart. That's a kernel change. And I tried to request this feature in lenakernel thread but it wasn't done so I assume it isn't that easy.
But comradesven did it in his tksgb kernel so I switched to it. He might give you more details about this change if you need them. I didn't want details. I'm just happy it works
davwman said:
running latest version of geewiz with leankernel and getting unsupported battery with samsung 1800mah. Im well aware of the reason behind this, but I thought this issue was resolved? I tried searching for a solution and cant come up with anything, and please dont say "run cm7", because I know that it solves the unsupported battery issue. Is there something I can change to fix this
Click to expand...
Click to collapse
DJ released a patch for this i believe check the original post
Im pretty sure sirgatez did this a while back. Might be able to find the change on the eclair kernel source on Adrynalyne's github.
Sent from my Incredible 2 using XDA App
I've not seen a specfic thread dedicated to ROMS that people are using that appear to be flawless. I did do a search on here, but honestly, I'm new to Android and don't know exactly what to search for other than maybe CM7.1, UnNamed, and ROMs. of which you get way too many threads to sort through. figured I'd start this and people can add things. I'll keep it updated on this first post with updates as people post them. This may help others who are new find what they need to. If you know of a safe rom, post up. If you also know of a walkthrough of how to install it, post that up as well since other newbs may want help walking through their first flash. Thanks!
considering tomween1 already spent the time to create a thread with all the info you need (here) i think this thread is redundant. just my opinion, though.
nothing is "safe" if you dont know what you're doing or dont do homework, first. On the flip side, most roms are relatively safe if you know what to do. All the info you need to flash, root, whatever ... is usually stickied to the top of the section.
If it isn't from netchip, and you take care to READ all directions and instructions and warnings before flashing - everything here is safe.
(Only thing "unsafe" really is bootloaders - which is why I make sure any bootloader thread has plenty of warnings.)
I think he meant "safe" is the ROM has no error which all the cook ROMs have. Even the Stock ROm sometimes has a bug.
re: Errors
sweetboy02125 said:
I think he meant "safe" is the ROM has no error which all the cook ROMs have. Even the Stock ROm sometimes has a bug.
Click to expand...
Click to collapse
NOTICE:
If anyone wants a custom rom without any bugs or errors please look elsewhere!
(xda is not the right place for you.)
if anyone is looking for:
1) something safe to flash
and
2) doesnt want to read and gain the proper knowledge prior to touching their phone
then they should leave their phone as it is right out of the box. There are a lot of people on this forum that are more than willing to help someone out but dont expect them to do all the work. You need to meet them half way and have some prior knowledge of what you are doing.
I respect this post and would love to see it turn into a rom known bugs thread. For ex unnamed is a battery hog. P8 has Bluetooth issues and cm7 has sub par cam.
Sent from my SAMSUNG-SGH-I777 using Tapatalk
zgr8jakez said:
I respect this post and would love to see it turn into a rom known bugs thread. For ex unnamed is a battery hog. P8 has Bluetooth issues and cm7 has sub par cam.
Sent from my SAMSUNG-SGH-I777 using Tapatalk
Click to expand...
Click to collapse
The problem is, if everyone posted bugs in this thread, you'd have to sift through pages and pages of posts to see if you have a similar problem. Even then, the problem may not be the rom but a bad flash or incompatibility with a app. This would be so cluttered, you wouldn't be able to get anything out of it. What if there was a bug and the dev fixed it in a update? A newb would read the thread and think there's a issue that hasn't been resolved. Bugs are best left to their dev thread where they can be announced and addressed. If you want to see what rom A has to offer, take the time to READ.
zgr8jakez said:
I respect this post and would love to see it turn into a rom known bugs thread. For ex unnamed is a battery hog. P8 has Bluetooth issues and cm7 has sub par cam.
Sent from my SAMSUNG-SGH-I777 using Tapatalk
Click to expand...
Click to collapse
Hmmm.... these "bugs" look more like opinions or might possibly be user error. For me UnNamed is a battery genius and I probably got over 2 days of use on one charge. I'm using Bluetooth just fine on Serendipity right now. And cam on cm7 works better for some then it might work for you bro.
im on uname rom myself but look to make the change to {ROM} MIUI 1.10.21 {Updated on 10-25-11} cuz i love miui so, unmae is a very good fast rom i just miss miui.
task650 said:
Hmmm.... these "bugs" look more like opinions or might possibly be user error. For me UnNamed is a battery genius and I probably got over 2 days of use on one charge. I'm using Bluetooth just fine on Serendipity right now. And cam on cm7 works better for some then it might work for you bro.
Click to expand...
Click to collapse
My thoughts exactly. (Except I never tried CM7)
Sent from my Galaxy S II (i777)
Yup. I've never had battery problems with gtg's ROM. Yes, S8 is slightly better on battery due to being more aggressively debloated, but it's not THAT much better.
Usually, anyone who encounters severe drain has encountered an app bug.
Slight exception: Any ROM that doesn't include my 10/20 kernel is susceptible to the fuel_alerted wakelock bug. Easy enough to flash my kernel over any ROM that hasn't been updated with the 10/20 kernel.
At this point, any user who claims a ROM is a battery drainer is usually at fault themselves. Especially if they haven't posted debugging info collected as documented in my Known Battery Drainers thread.
Most of the issues people have with roms are user errors.
Sent from my SAMSUNG-SGH-I777 using XDA App
One thing I forgot: The UCKJ2 leak that is distributed as a .exe file is an "Odin One-Click" flash package which will flash crippled bootloaders. I would suggest avoiding it.
re: One-Click
Entropy512 said:
One thing I forgot: The UCKJ2 leak that is distributed as a .exe file is an "Odin One-Click" flash package which will flash crippled bootloaders. I would suggest avoiding it.
Click to expand...
Click to collapse
What I am looking for is a complete stock 4 part odin flash rom like
this below but one which is for the SGS2 i777 phone and not the i9100.
OR an Odin One-Click flash for i777.
PIT select u1_02_20110310_emmc_EXT4.pit
PDA select CODE_I9100XXKI3_CL577579_REV02_user_low_ship.tar.md5
PHONE select MODEM_I9100XXKI3_REV_02_CL1062028.tar.md5
CSC select GT-I9100-CSC-MULTI-OXAKI3.tar.md5
So far I could not find a 100% stock package for the i777 here in XDA.
Designgears had a very good odin one-click for the old captivate I used to have.
Either one would be good, one-click or just the complete 4 part odin flash.
Glad I could get the convo going! I'm very conservative when it comes to testing rom's and am a battery nazi as far as processes go. Cm7 is fine with still shots but unless they fixed it lately the fps on it was not perfect. I know I'm alone on the Bluetooth issue with s8 but had just gone from a fresh wipe to clean install
.. there have been allot of mms issues with that rom though..
UnNamed has more bloat so of course it will use more power after I froze the bloat it was where s8 was. The devs are amazing not knocking any at all just putting my 2 cents in. Btw the way I found the easiest way to play around with rom's was to back up in both cwm and titanium, flash one for a week and repeat indefinitely that way you can get the best of all worlds.
Sent from my SAMSUNG-SGH-I777 using Tapatalk
CSC and cache get integrated into the system image on first boot - so you will never see a return-to-stock that includes csc and cache for UCKH7, since the return-to-stock was generated from a dumped phone, and since it's the initial stock firmware, H7 doesn't exist as Odin upgrade leaks anywhere.
Same exact deal as gtg's Ultimate Unbricks for the Infuse - the D5 unbrick (and I think the E3 unbrick too, will check tonight) were created from system dumps, so do not include a separate CSC or Cache file, as those get integrated into the system image on first boot.
Are you guys noticing that a lot of the custom ROMs out now are pretty buggy? I have tried about 10 ROMs in the last two weeks, and usually they seem great at first. Eventually weird things start happening, like sluggish rotation behavior, or random reboots. Sometimes MMS messages will not send, sometimes texts get hung up and I have to delete all my threads... I've had my phone freeze while sleeping, and missed alarms. I find myself flashing a ROM almost every other day, because it seems that I don't notice a huge problem until it has a day to settle on my phone. One problem that really annoys me is that in the Gallery app, on some ROMs, when you rotate the phone, the picture flys off the screen for a second or so, then re-centers itself. In general I've had issues with 3G/1X, and sometimes even calls being sent to voicemail without ringing. I also notice that from one ROM to the next, battery life can be dramatically different, despite having the same exact settings.
When I had my un-rooted Evo 3D, I had barely any of those problems. I definitely never had it freeze during the middle of the night, or overheat, or get wildly-sluggish. Now, with my stock ROM, I never had as SMOOTH as an experience as the fastest custom ROM I've used, and I've also never had as great battery life as the longest-lasting custom ROM out there. I just wish there was a way to take all the good things from every ROM out there, and put it into one, perfect ROM. I have seen the ROMs that claim to do this, but they still tend to have basic flaws. It makes me think that an updated base is to blame for a lot of this. The first round of custom ROMs I had that were based off the original stock seemed rock-solid. Now I've tried just about everything, and there are glaring problems with each of them. Sometimes I am embarassed because my phone has powered off during very important times--like on-call situations at night.
I have multiple wipe APKs, but I was told that the newer superwipe was the end-all be-all of wiping, so that's what I've been using lately. Right now I am using one of the more stable ROMs, Revolution HD 1.1.1, but I still get the random picture movement when rotating in Gallery, I still get really bad 3G/1X problems, where I have to frequently turn off mobile data to get it back... I have had it reboot on me twice in the last 2 days. One thing that really pisses me off, which is not specific to this ROM, is that when I am on WIFI, MMS messages tend not to send or receive... I can't recall if the original stock ROM had this problem or not. I have this issue with stock messaging as well as Handcent. The moment I disable WIFI, my messages appear with images.
Being that I didn't have these issues with truly stock ROMs, I don't believe it is a hardware issue. Am I the only one experiencing these problems, or are others just glossing over these sort of reliability issues, and accounting them to being a flashaholic, or something similar? The only reason I keep flashing is to find one that is rock solid. If I could get the original stock ROM with battery life to get me through an entire day, I'd be happy, but it didn't come close.
What ROMs did you try?
MMS Messages send and receive over WiFi for me just fine (Sense ROM) but on AOSP, they will not.
I suggest you try one of the lesser popular ROMs, as the top ones seem to have the most issues according to my reading and research.
If you want a fast, stable and great battery life that just works check out CleanROM. It is basically stock with the junk pulled out. The dev is very hands. Worth looking at the very least.
well it's a good thing everybody is not having the same issues you are so we know to ignore this useless thread. thanks for the info and cool story bro.
i have two words for you... user. error.
i have never had one issue with cleanrom, steel rom, or WTSB rom... or smokin rom...
all of which would easily be classified as "top roms" as you put it.
and right now i am on virus' eternity 1.4.... been on it, with the same kernel, same settings, etc... for roughly two weeks. zero issues there as well.
sooooooooooo..... either everybody just got lucky, or you are causing the issues you described.
i never have noticed even a blip of lag on eternity.
cobraboy85 said:
well it's a good thing everybody is not having the same issues you are so we know to ignore this useless thread. thanks for the info and cool story bro.
i have two words for you... user. error.
i have never had one issue with cleanrom, steel rom, or WTSB rom... or smokin rom...
all of which would easily be classified as "top roms" as you put it.
and right now i am on virus' eternity 1.4.... been on it, with the same kernel, same settings, etc... for roughly two weeks. zero issues there as well.
sooooooooooo..... either everybody just got lucky, or you are causing the issues you described.
i never have noticed even a blip of lag on eternity.
Click to expand...
Click to collapse
Everyone uses their device differently, has wildly different settings, applications, amount of time per day spent doing one thing or another. In some cases we can consider there to be user error, but this really is unlikely in this case. The problem lies in the fact that we have more ROM"chefs" than developers that actually have the knowledge to code their own ROM from the ground up, instead of pasting other peoples work together and calling it an advancement. You can't provide support or bug fixes for work that isn't your's and you have little to no coding experience. Most of these roms are like some you mentioned; a ROM that just has simple things like "bloat" taken out. Those types of chefs have a purpose here, and their roms are nice for some users but they aren't doing much for the improvement of Android overall, and they don't know enough to be trying to slap features in that they can't debug...
Anyway, rant over. I think your reply was hasty and offensive, not to mention based on what I have seen, inaccurate. I think you have been lucky personally because you are using roms like clean ROM that don't add or change much. Therefore you really wouldn't experience what this user is referring to.
I get random reboots often. The mms over wifi has never been an issue though.
Sent from my PG86100 using XDA App
cobraboy85 said:
well it's a good thing everybody is not having the same issues you are so we know to ignore this useless thread. thanks for the info and cool story bro.
i have two words for you... user. error.
i have never had one issue with cleanrom, steel rom, or WTSB rom... or smokin rom...
all of which would easily be classified as "top roms" as you put it.
and right now i am on virus' eternity 1.4.... been on it, with the same kernel, same settings, etc... for roughly two weeks. zero issues there as well.
sooooooooooo..... either everybody just got lucky, or you are causing the issues you described.
i never have noticed even a blip of lag on eternity.
Click to expand...
Click to collapse
Thanks for the info and cool story bro.
Sent from my PG86100 using Tapatalk
Have you tried to install a ROM and not install any apps to make sure it's not app related. I've heard of lots of apps not playing well with certain roms. Just a thought.
Sent from my PG86100 using xda premium
Two words. ANDROID REVOLUTION! check it out.
Sent from my PG86100 using xda premium
Sad Panda said:
Everyone uses their device differently, has wildly different settings, applications, amount of time per day spent doing one thing or another. In some cases we can consider there to be user error, but this really is unlikely in this case. The problem lies in the fact that we have more ROM"chefs" than developers that actually have the knowledge to code their own ROM from the ground up, instead of pasting other peoples work together and calling it an advancement. You can't provide support or bug fixes for work that isn't your's and you have little to no coding experience. Most of these roms are like some you mentioned; a ROM that just has simple things like "bloat" taken out. Those types of chefs have a purpose here, and their roms are nice for some users but they aren't doing much for the improvement of Android overall, and they don't know enough to be trying to slap features in that they can't debug...
Anyway, rant over. I think your reply was hasty and offensive, not to mention based on what I have seen, inaccurate. I think you have been lucky personally because you are using roms like clean ROM that don't add or change much. Therefore you really wouldn't experience what this user is referring to.
Click to expand...
Click to collapse
Yes to some extent I see your point. Smokin rom is a build based on steel rom... steel rom however, is just steel rom. Clean rom has had little issues with previous builds but scott being a dev has worked everything out and optimized that rom to the max... and it has its own tweaks to it as well. Same thing with steel rom. I'm not sure what wtsb is based off of but I have never had problems with that one either.
And virus rom is damn near flawless. I have never had a problem with... ever. Since day one. Been running 1.4 for over 2 weeks and it is just as fast as it was the day I flashed it. So im confused by the op's post when he says after a few days they have all lagged and become slow
Was I a little harsh? Maybe. But was I right to think this person is simply complaining and wasting my time? Absolutely. This thread is just him complaining, not problem solving, not helping anybody, just knocking people's hard work when the real issues are found on his end obviously.
Yep. I just tried ViperROM Test4...boom! 100% wakelock while charging. Buggy.
epikphone said:
Yep. I just tried ViperROM Test4...boom! 100% wakelock while charging. Buggy.
Click to expand...
Click to collapse
Well ViperROM is actually known for having some problems. Viper is trying to fix that, but any other ROM that is posted (well some but not all) don't have any bugs unless they're posted on the OP. Any other weird hiccups you may experience will most likely be kernel related, such as the random reboots or severe battery drain. I've tried most of the ROMs here, and I have yet to experience any weird quirks unless they are the ones posted on the OP. There are some ROMs that do have weird bugs, but it's not all of the ROMs.
DDiaz007 said:
Well ViperROM is actually known for having some problems. Viper is trying to fix that, but any other ROM that is posted (well some but not all) don't have any bugs unless they're posted on the OP. Any other weird hiccups you may experience will most likely be kernel related, such as the random reboots or severe battery drain. I've tried most of the ROMs here, and I have yet to experience any weird quirks unless they are the ones posted on the OP. There are some ROMs that do have weird bugs, but it's not all of the ROMs.
Click to expand...
Click to collapse
What's your favorite ROM? Fast, long battery life.
epikphone said:
Yep. I just tried ViperROM Test4...boom! 100% wakelock while charging. Buggy.
Click to expand...
Click to collapse
should you be whining about a "test" ROM having bugs? i think not, seeing as how it clearly says "Test" multiple times. what do you think test roms are for? to work out the bugs maybe. and phones are picky. all roms will not work perfectly for you. you "MUST" find the right rom/kernel combination that works best for the way you use your phone. less *****ing and more testing is all you need.
dougstoner said:
Have you tried to install a ROM and not install any apps to make sure it's not app related. I've heard of lots of apps not playing well with certain roms. Just a thought.
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
I'm with this guy.
Try a fresh install.
Only use stock apps for the first couple of days your trying.
The girlfriend used to have a stock unrooted Droid x that she would complain about screwing up but it was usually her using alternative music apps and such .
Also if you use titanium backup never batch restore your apps and data. Manually update each app that you want so your not restoring any nasty app data that might be screwing up your roms
Hope this helps
Sent from my PG86100 using xda premium
Yes, I've noticed it too but you just need to use a dose of caution and ask around. I tried about a half dozen ROM's and I've found that the ones that are more "tricked out" have the most problems. Makes sense, because they are fooling with more stuff in the ROM.
That said, there are some really fast and good ones out there. Deck's ROM never gave me any trouble but it was a little TOO stock for me. I've since switched to CleanROM 2.7 and that's incredibly solid and almost as fast as the tricked out OC'd ones. So try one of those preceded with a full wipe and you should be happy.
Mike
epikphone said:
What's your favorite ROM? Fast, long battery life.
Click to expand...
Click to collapse
Check out CleanROM 2.7 or CleanROM DE 1.2. Both have great battery life. I get easily over 24 hours with light to moderate use and 12+ on moderate to heavy use.
t3project said:
should you be whining about a "test" ROM having bugs? i think not, seeing as how it clearly says "Test" multiple times. what do you think test roms are for? to work out the bugs maybe. and phones are picky. all roms will not work perfectly for you. you "MUST" find the right rom/kernel combination that works best for the way you use your phone. less *****ing and more testing is all you need.
Click to expand...
Click to collapse
Seeing how this is a thread about "Buggy ROMs", I feel justified in my post. Did I ***** and moan and complain about the issue? No. Did I complain about lack of support? No. Did I complain about anything else? No.
I stated the problem...."100% wakelock while charging" and that's it.
Go preach elsewhere.
---------- Post added at 04:55 PM ---------- Previous post was at 04:55 PM ----------
LfnsR said:
Check out CleanROM 2.7 or CleanROM DE 1.2. Both have great battery life. I get easily over 24 hours with light to moderate use and 12+ on moderate to heavy use.
Click to expand...
Click to collapse
Thanks. Your post deserves a thumbs up.
bmtdan said:
Try a fresh install.
Only use stock apps for the first couple of days your trying.
The girlfriend used to have a stock unrooted Droid x that she would complain about screwing up but it was usually her using alternative music apps and such .
Also if you use titanium backup never batch restore your apps and data. Manually update each app that you want so your not restoring any nasty app data that might be screwing up your roms
Hope this helps
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
I was originally coming onto the forum to post about how every rom/kernel combo eventually starts freezing on me after a few days of use (causing me to miss alarms/calls/etc), when I ran into this post.
I do use Titanium backup pro to batch restore and have been doing so on the Hero/Epic/Shift/3vo. This is the first device that I have had any problems with, but it does seem to coincide with titanium backup since the stock rom was butter.
What's the method of manually updating each app? Is it simply downloading from the market and restoring data to that app? And how is that any different with the likelihood of restoring "nasty app data"?
OP, do you use titanium backup to batch restore apps too?
Everyone else, is there a log file that I can look at to discover the process that triggers the freeze?
No problems on the roms I've used at all. Most of these posts do end up being user error, or just a bad phone. As someone else suggested, try Cleanrom. It is bullet proof. Nothing fancy, but it works forever.
If there were more problems, there would be a ton more threads like this. Yet we only see a post like this every week or so...
Hi guys,
Placed some new custom rom on the S3 and not it wont wake up after going on "standby" mode. Any ideas where to look at?
f1enigma said:
Hi guys,
Placed some new custom rom on the S3 and not it wont wake up after going on "standby" mode. Any ideas where to look at?
Click to expand...
Click to collapse
I guess not without more info. But as you're using a custom rom, why not post in the relevant topic? Anyway, did you undervolt or anything?
Nope. I didnt undervolted it. Its just that I have to remove the battery to bring it back to life.
I have tried it with stock roms and different custom roms but the same thing happens. Im not sure if I have to change kernel or something else now.
me too
Mine also does this occasionally and its not been modified in anyway apart from installing apps.
Was considering sending it back but curious as to what would cause this.
I have experienced the same thing with my Verizon S3.
Same
Mine does this aswell ... getting frustrating. Stock rom no mods yet
to the OP - if your on a custom rom then there is a good chance the kernel used has been modified to change cpu speeds or voltages from stock values, if this is the case then this is more than likely the reason for your issues. You don't have to have changed these values yourself for them to already be different from stock (Samsung can only guarantee that everything will work on the stock set up, any differences will depend on each handset, some can take changes perfectly fine, others struggle).
For all the rest of you, it is likely to be one of two issues.
1) some form of corrupt data (not particularly likely) - to fix you will have to try a factory reset
2) a bad app! - this is the most likely reason, you can try to work out which app it is, or remove all apps you have installed and add them back one by one until you realise the issue is gone.
Lennyuk said:
to the OP - if your on a custom rom then there is a good chance the kernel used has been modified to change cpu speeds or voltages from stock values, if this is the case then this is more than likely the reason for your issues. You don't have to have changed these values yourself for them to already be different from stock (Samsung can only guarantee that everything will work on the stock set up, any differences will depend on each handset, some can take changes perfectly fine, others struggle).
For all the rest of you, it is likely to be one of two issues.
1) some form of corrupt data (not particularly likely) - to fix you will have to try a factory reset
2) a bad app! - this is the most likely reason, you can try to work out which app it is, or remove all apps you have installed and add them back one by one until you realise the issue is gone.
Click to expand...
Click to collapse
Did a factory reset and it hasn't done it since. Definitely a bad app. Thanks for the heads up
Sent from my MZ601 using xda app-developers app
Ok ... issue came back ... but only after enabling NFC. Going to see if it occurs again now I've disabled it or if it was coincidence
Sent from my GT-I9300 using xda app-developers app
Hi there.
Following @Tijmen's advice, this thread is for those who have damaged screens (specifically the black lines). There are reports that a reboot triggers this issue. @autoprime had his G2 (never flashed recovery, kernel or ROM) get the black lines after rebooting into Stock Recovery when he was only using ADB with the phone hot.
My device:
Model: LG G2 D805
Current ROM: CloudyStock 2.3 (flashed after the screen panel replacement through RMA)
Panel: $ su -c 'cat /proc/cmdline' -> mdss_dsi_g2_lgd_cmd -> LGD Panel
Damage: Permanent Vertical Black Lines on the right side (borrowed screenshot; even in recovery)
External Links: Reddit 01, Reddit 02
From #[email protected] (irrelevant lines have been removed):
<gitanO0|vs980> hey all, long time since i've been on here
<gitanO0|vs980> anyone experience top to bottm vertical black lines on the right side of their screen after flashing rom?
<gitanO0|vs980> persists through boot and seen in recovery
<gitanO0|vs980> i've seen some other folks have this issue after flashing rom but not seen any solutions
<gitanO0|vs980> right after the flash of the rom, the lg boot screen came on and went all inverted and fading... I booted back to recovery and flashed nandroid and now have these perma lines on the right 1/8" or so of screen
<@autoprime> wat rom? PA?
<gitanO0|vs980> no carbon
<gitanO0|vs980> one of the devs made some 24a bootstack changes for some of the repos
<@autoprime> if it persists thru recovery it might be perm damage
<gitanO0|vs980> yeah, that's what I figurered
<gitanO0|vs980> might have to go the send it back route. any good "back to stock, unrooted" guides out there?
<gitanO0|vs980> autoprime, is there anything I can test or look at to verify if it's permanent?
<@autoprime> if its in recovery its most liekly perm
<@autoprime> if it was rom only then its fixable
<gitanO0|vs980> right
Click to expand...
Click to collapse
IMPORTANT - MUST READ IRC TEXT BELOW IN RED!:
<@autoprime> wah... i has lines on mah g2
<@autoprime> RMA
< Compass_Linux> no worries. the'll be present in the
< Compass_Linux> G3 if LG does it right.
< chachin> lol
< Compass_Linux> i wouldn't cheer to soon when this is fixed though. some regressions come with a vengeance.
< Compass_Linux> s/to/too
<@NookieBot> Compass_Linux meant: "i wouldn't cheer too soon when this is fixed though. some regressions come with a vengeance."
<@autoprime> i wasnt even flashing custom rom
<@autoprime> so its not the roms lol
<@autoprime> wasnt using twrp either
<@autoprime> was messing with adb and stock partitions
<@autoprime> reboot into stock recovery... stock recovery has lines.
< Compass_Linux> autoprime: you serious? :|
<@autoprime> Compass_Linux yup :/
<@autoprime> suxxxxxx
* Compass_Linux needs a hammer for his G2. And quick!
<@autoprime> i think its heat. mine was getting really hot in adb
< Compass_Linux> autoprime: can i add your txt to the OP?
< Compass_Linux> damn LG...
<@autoprime> ok
<@autoprime> 100% stock
<@autoprime> :/
<@autoprime> so based on how mine went down.. its not related to rom/kernel flashing :/
< Compass_Linux> cr*p
< Compass_Linux> i'll update the OP.
<+savoca> autoprime: your g2 just got lines one morning?
<+savoca> autoprime: apperently its a possible defect as well.
<+savoca> however pa's kgsl sh*t bumps the probability by like 200%
<@autoprime> today.. lines on right side
<+Khaytsus> autoprime: So your device has lines now? geez
<@autoprime> Khaytsus indeed
<+Khaytsus> Has anyone positively identified this happening on a device that's always been stock?
< Compass_Linux> Khaytsus: yes, just happened to autoprime right now.
<@autoprime> my g2 was 2nd batch
<+Khaytsus> Has anyone positively identified this happening on a device that's _always_ been stock?
<@autoprime> :/
<+Khaytsus> autoprime: Yours hasn't always been stock, right?
<@autoprime> of course it has :|
<+Khaytsus> really??
<@autoprime> this is public record
<@autoprime> :X
<+Khaytsus> My point being nobody really knows what the failure cause is yet.
<+Khaytsus> But nobody has had it happen on a device that's _always_ been stock that I'm aware of.
<@autoprime> Khaytsus i wanna say heat. but idk
<@autoprime> mine has been getting hot the past few days
<@autoprime> never had issue before
<@autoprime> then was using adb and got hot again.. rebooted into stock recovery.. lines
Click to expand...
Click to collapse
How I saw it happen:
After twrp flashed the files mentioned above, the phone rebooted to a black screen with a vertical non uniform white band in the middle, which rapidly expanded sideways until the screen suddenly went entirely black (that's the moment the screen was damaged), vibrated and turned off. When turned on, permanent vertical black lines on the right side of the screen in recovery, in ParanoidAndroid etc. Flashed a stock D805 ROM, problem persists.
What has been confirmed about the origin(s) of this issue:
@dr87 was kind to clarify this issue here, here, here and here.
@houstonn has some information here and here.
This issue in numbers of LG G2's affected is very low. What is increasing until now are the number of different ROMs affected.
*** Unconfirmed Information (updated 28/07/2014) ***:
It was previously thought that Custom ROMs/Kernel were the cause of this problem, and that Stock ROMs/Kernels were safe to use. This is no longer the case due to @autoprime's experience. I removed the safe and unsafe ROMs list because of this and the Black Lines Survey. The possible reason (and I'm speculating here) Custom ROMs are more prone to this is that modifications done to them or their Kernels accentuated the problem that the phone already has but haven't yet appeared (not all devices due to the still small number of complaints). With the information we have now, it indicates that a hardware failure related to heat is to blame, and using a Custom ROM/Kernel can make the failure appear more quickly than if you keep completely at Stock. In @autoprime's case the simple use of ADB then reboot into Stock Recovery with the phone hot triggered the black lines. And since people are asking what is safe to flash and whatnot, there is unfortunately no answer as of yet.
My device is back from RMA (Return Merchandise Authorization). The panel has been replaced, and after flashing (recovery and ROM) no black lines.
@dr87 has a very interesting post here. He has also built a custom twrp with thermal control. If you use this and it corrupts your /cache partition, do this.
@chillstep1998 has a post about an app that can somehow remove (in his case all of them) the black lines. I'm not sure how it works but if you do chose to use it (if you have no warranty for example), remember that your results will likely vary from others experience.
Which Panel do I have? LGD or JDI?:
Here. Thanks go to @autoprime.
When was my G2 manufactured?:
Here. Thanks go to @jdk2. Once you input the URL, check the generated page source code (you might not have to do it; I did) and read this.
Here is another (and better) way to check the same information. Thanks go to @razrzxcvbnm.
I'll leave both methods just in case one or the other "disappears".
Hints:
@RusherDude has an interesting theory. If the conditions he mentions match yours, please confirm and elaborate the best you can in the thread. Thanks!
In the meantime (considering no permanent way to avoid the black lines):
You're crazy about Custom ROMs as I am and still have some months warranty for your device. I had my screen panel replaced under warranty and it's working fine for now. If I get the black lines again I can take it for repair, as long as I'm under warranty. Once my warranty expires, I'm on my own;
You're crazy about Custom ROMs as I am and no warranty for your device. You fall into two situations basically. Repair the screen now for around USD$80 (parts only), or live with this situation and flash to your hearts content. Repairing the screen hopefully fixes the problem permanently.
Black Lines Survey:
User @NicoC72 created a Black Lines Survey, Graph and Spreadsheet. Thanks!
Contact:
You can find me and lots of nice people in the #lg-g2 IRC Channel at irc.freenode.net (go to Freenode for instructions on how to connect)
To see if I'm away, use /whois Compass_Linux.
Compass.
RIP screens :/
did you try a return to stock method to check if issue survives that?
bachera said:
did you try a return to stock method to check if issue survives that?
Click to expand...
Click to collapse
Few people have reported using tot and kdz, and the issue stayed.
Sent from my Vs980 running Mahdi 2.5
http://forum.xda-developers.com/showthread.php?p=52969597
so after going to stock and using the dialer code ( update firmware) it stayed after a reboot? Dr's suggestions might be handy. I dont have the issue but listing all avenues walked to solve might help.
Is there not a disclosure in every op.. To flash at ur own risk.. I have ran many of houstonns roms and i highly doubt that a rom can cause this.. Closing houstonns thread is little to much dont u think... 4 or 5 out of 1000s of people who flashed this rom. Come on! Bullsheit
Sent from my LG-D800 using XDA Free mobile app
I agree, I've seen this issue pop up in multiple rom threads. It's not just PA. It happened to me after a flash of slimKAT a while back. I don't think it's software related. I think it's faulty hardware that's causing the issue. Quite honestly, I think that while backing up and flashing a new rom in recovery, the device gets hot and stresses the hardware.
I think that houstonn is getting crucified unfairly on this.
bachera said:
did you try a return to stock method to check if issue survives that?
Click to expand...
Click to collapse
Yes, no success.
Thanks for mentioning. I've updated the OP.
Compass.
bachera said:
http://forum.xda-developers.com/showthread.php?p=52969597
so after going to stock and using the dialer code ( update firmware) it stayed after a reboot? Dr's suggestions might be handy. I dont have the issue but listing all avenues walked to solve might help.
Click to expand...
Click to collapse
Doing the Touch Firmware Upgrade also fails, unless you mean something else. Thanks.
Compass.
bps119 said:
I agree, I've seen this issue pop up in multiple rom threads. It's not just PA. It happened to me after a flash of slimKAT a while back. I don't think it's software related. I think it's faulty hardware that's causing the issue. Quite honestly, I think that while backing up and flashing a new rom in recovery, the device gets hot and stresses the hardware.
I think that houstonn is getting crucified unfairly on this.
Click to expand...
Click to collapse
You need to share that this happened to u on another rom with the monitor that closed his thread
Sent from my LG-D800 using XDA Free mobile app
iamtha1 said:
Is there not a disclosure in every op.. To flash at ur own risk.. I have ran many of houstonns roms and i highly doubt that a rom can cause this.. Closing houstonns thread is little to much dont u think... 4 or 5 out of 1000s of people who flashed this rom. Come on! Bullsheit
Sent from my LG-D800 using XDA Free mobile app
Click to expand...
Click to collapse
I don't think closing houstonn's thread is too much. Moderation has tried to contact him to no avail.
As for the 4 or 5 people out of 1000's, those are the ones that have been reported in XDA. If you leave this issue unresolved, you can expect an increase in those numbers.
And so far the damage is permanent.
I mentioned the warranty/liability in my Post 01. If I knew I could damage my hardware permanently like this, I wouldn't have upgraded P.A. and might have changed ROMs (back to stock maybe).
bps119 said:
I agree, I've seen this issue pop up in multiple rom threads. It's not just PA. It happened to me after a flash of slimKAT a while back. I don't think it's software related. I think it's faulty hardware that's causing the issue. Quite honestly, I think that while backing up and flashing a new rom in recovery, the device gets hot and stresses the hardware.
I think that houstonn is getting crucified unfairly on this.
Click to expand...
Click to collapse
It could indeed be a hardware issue, but that doesn't exempt the fact that P.A. (and other ROMs apparently) is triggering this.
Compass.
On the Mahdi thread I saw the ROM author say he avoids commits that change the panel driver code, or something to that effect, and that's why his ROM hasn't had that issue. Have there been reports on his ROM too? Now I'm scared to flash anything.
Compass Linux said:
I don't think closing houstonn's thread is too much. Moderation has tried to contact him to no avail.
As for the 4 or 5 people out of 1000's, those are the ones that have been reported in XDA. If you leave this issue unresolved, you can expect an increase in those numbers.
And so far the damage is permanent.
I mentioned the warranty/liability in my Post 01. If I knew I could damage my hardware permanently like this, I wouldn't have upgraded P.A. and might have changed ROMs (back to stock maybe).
It could indeed be a hardware issue, but that doesn't exempt the fact that P.A. (and other ROMs apparently) is triggering this.
Compass.
Click to expand...
Click to collapse
Dude every dev warns u that flashing roms can damage ur phone.. Come on... Stick to stock if u cant handLe damaging u phone
Sent from my LG-D800 using XDA Free mobile app
I'd like to remind people that flashing a tot or kdz only replaces 12 partitions out of the total 39 partitions on the device.
Partition list here - http://pastebin.com/S5XtQtW3
I can't confirm anything but it seems no one has backed up all partitions and restored them after running into this issue.
so it's still not 100% that it's permanent damage(although it very well could be).
tot/kdz is made to get you booting.. not fix all the things. I have a zip I made to automate the backup of a lot of these partitions... of course you can always do it manually too.
http://forum.xda-developers.com/showthread.php?t=2451390
tbh.. I'm not sure what each and every partition does.. or if it can be shared between users. Example: modemst1 and modemst2 is your EFS and is unique to your phone only.
Only common thing I see between everyone with issues is they all used a custom recovery... maybe we shouldn't use those either
autoprime said:
I'd like to remind people that flashing a tot or kdz only replaces 12 partitions out of the total 39 partitions on the device.
Partition list here - http://pastebin.com/S5XtQtW3
I can't confirm anything.. but it seems no one has backed up all partitions and restored them after running into this issue.. so it's still not 100% that it's permanent damage.
tot/kdz is made to get you booting.. not fix all the things. I have a zip I made to automate the backup of a lot of these partitions... of course you can always do it manually too.
http://forum.xda-developers.com/showthread.php?t=2451390
tbh.. I'm not sure what each and every partition does.. or if it can be shared between users. Example: modemst1 and modemst2 is your EFS and is unique to your phone only.
Only common thing I see between everyone with issues is they all used a custom recovery... maybe we shouldn't use those either
Click to expand...
Click to collapse
Thank u prime!
Sent from my LG-D800 using XDA Free mobile app
iamtha1 said:
You need to share that this happened to u on another rom with the monitor that closed his thread
Sent from my LG-D800 using XDA Free mobile app
Click to expand...
Click to collapse
Done
iamtha1 said:
Dude every dev warns u that flashing roms can damage ur phone.. Come on... Stick to stock if u cant handLe damaging u phone
Sent from my LG-D800 using XDA Free mobile app
Click to expand...
Click to collapse
I assumed the risk of flashing a Custom ROM, as I've mentioned before.
Again, this doesn't exempt the people responsible for the Custom ROM. I'm not seeking damages against them or anything. The only thing I asked for was to remove the P.A. ROMs from when this issue began. And I don't think that's too much to ask for.
Compass.
Compass Linux said:
I assumed the risk of flashing a Custom ROM, as I've mentioned before.
Again, this doesn't exempt the people responsible for the Custom ROM. I'm not seeking damages against them or anything. The only thing I asked for was to remove the P.A. ROMs from when this issue began. And I don't think that's too much to ask for.
Compass.
Click to expand...
Click to collapse
Because u had a problem with pa... Everyone else including myself know cannot run it.. I have ran every beta he has released with no problems what so ever! Now a rom that i love may be in jeopardy of being gone.... Thanx for ur help buddy but it wasnt needed!!
Sent from my LG-D800 using XDA Free mobile app
Flashes on VS980 no problem. You guys had me worried for a minute. Hopefully they fix the issue across all devices. It's a great ROM.
iamtha1 said:
Because u had a problem with pa... Everyone else including myself know cannot run it.. I have ran every beta he has released with no problems what so ever! Now a rom that i love may be in jeopardy of being gone.... Thanx for ur help buddy but it wasnt needed!!
Sent from my LG-D800 using XDA Free mobile app
Click to expand...
Click to collapse
Not only me, if you read the OP. And not only on Paranoid Android either.
I can private message you the Paranoid Android official webpage, where you can download. I cannot post the link here.
You have to contact houstonn to see if it will continue to be developed. I have no influence on the matter, as you suggested the contrary.
I also like Paranoid Android, but this problem cannot persist. It has even spread to other ROMs.
Compass.