Hey great guys here at XDA! I'm having an issue lately after I flashed a kernel about a week ago. The kernel was Francos and ever since I flashed it my wireless charging is on the fritz. It will sometimes charge about 30 minutes before it stops recognizing the source and others a few seconds. A lot of the time I will get the charging logo sort of blink because it is constantly going in and out. I have tried every kernel out there and it still does this. Everything was fine when I was on stock so I flashed back both with the zip method and through the actual factory image through ADB by flashing both system.img and boot.img. I can't seem to figure out what went wrong and was looking for someone's advice who might have a better clue. I have been on stock ROM this whole time and am currently on faux kernel using his kernel enhancement app. Any advice is greatly appreciated.
Sent from my Nexus 4 using xda app-developers app
Related
I posted this over at rootz earlier today and didn't get any bites so I figured I'd give it a shot over here.
I may be the only one in the world experiencing this problem. Looked around quite a bit and don't see any sign of others having this issue... Anyway, my N7 doesn't seem to like it when I flash a new kernel. I've tried several different kernels and when ever I flash one my display will not wake up once it times out or if I turn the display off manually. Once the screen goes dark i have to hold the power button down and reboot. I have zero issues with custom kernels as long as they are baked into the rom. I typically wipe cache and dalvic after flashing kernels...
Sent from my Galaxy Nexus using xda app-developers app
Little bump here... 130 views and not a peep... :-/
scram99 said:
Little bump here... 130 views and not a peep... :-/
Click to expand...
Click to collapse
youre experiencing "sod", which is a fairly common problem with android 4.2.1 source code(not as common on the n7 as the gnex, but common enough). do you flash the kernel with the rom or do you flash the kernel separately?
This happens after switching out the kernel on any ROM I've used. Have not flashed a different kernel at the same time I flashed a ROM. I don't think that will make a difference. I can however flash kernels over my stock rooted backup... I don't know. Just weird and bums me out being limited like this...
scram99 said:
This happens after switching out the kernel on any ROM I've used. Have not flashed a different kernel at the same time I flashed a ROM. I don't think that will make a difference. I can however flash kernels over my stock rooted backup... I don't know. Just weird and bums me out being limited like this...
Click to expand...
Click to collapse
I would just factory reset and start from scratch. Do you have any settings set like UV??
Sent from my Nexus 7 using xda premium
I have tried flashing back to stock, relocking and starting from scratch. I do not undervolt...
A few good folks in the android community had experienced similar happenings and suggested lean kernel... Flashed it earlier this evening and working like a charm.
Guys i know nemesis is banned on xda but still i need immediate help.
Guys yesterday i downloaded and flashed Nemesis V2 on my phone then it was working fine it was on stock kernal after that i put my phone on charge and went to sleep when i wake up i saw the phone has not charged a bit rather it has decreased to 17%.
I thought it is a kernel problem and flashed percy gnu#10. But then also the problem persisted rather it was worsened then i switched off the device and put it to charge and it worked well. I tried flashing stock rom via odin but the problem remains same. Guys plz help asap.
DO NOT mention the name of banned roms in xda. BTW, i think it is caused by:
1. Battery itself
2. Internal Hardware
3. Charger adapter
Sent from my little beast using xda-app
Might be hard ware problems,
But you could try deleting battery stats in CWM in might help.
install stock rom twice
or maybe you charge it in electric shutdown lol:silly:
Hardware error for sure, get another charger or get your phones's charging slot tested.
Sent from my **** using xda premium
Look at your charging slot and charger plug.
Maybe it has dust or something in.
Had the same issue few weeks ago, i had some tomato sauce in there, dont ask, i dont know
Anyway i solved this special kind of brick with a simple toothpick and cleaned everything.
Thnx guys changing the charger helped me out.
Requesting moderator to close the thread.
Sent from my room using sgy hyp8.
souroking said:
guys i know nemesis is banned on xda but still i need immediate help.
Guys yesterday i downloaded and flashed nemesis v2 on my phone then it was working fine it was on stock kernal after that i put my phone on charge and went to sleep when i wake up i saw the phone has not charged a bit rather it has decreased to 17%.
I thought it is a kernel problem and flashed percy gnu#10. But then also the problem persisted rather it was worsened then i switched off the device and put it to charge and it worked well. I tried flashing stock rom via odin but the problem remains same. Guys plz help asap.
Click to expand...
Click to collapse
it might be that your battery is no longer usable
buy a new one
You have no choice！install a new Rom and it will work well！helpful to you！
Sent from my V926 using Tapatalk 2
Kernels no longer work for me. I was running _Motley's build 49 kernel and the stock ROM for a few months and never had any issues and had excellent battery life. Then I decided to flash PA and _Motley to give Halo a try and noticed my battery wasn't all too great. I then nandroid back to my previous setup and then my battery life went to ****. Android OS was my biggest drain so I reflashed my stock rooted ROM and kernel and still had the same issue.
Then I flashed Faux's reset kernel and was stuck in a boot loop but was unable to get past the Google logo. Flashed another reset kernel, can't remember who's, and everything was fine. Android OS wasn't an issue anymore but my battery life went back to being mediocre. So I tried flashing other kernels, _Motley's included, and Android OS would still be on top.
So for some reason, only the stock kernel is working for me. Any ideas why? I'm about to just restore the factory image and start over again. I heard PA uses a custom kernel from Franco so could that be why I'm having issues?
Edit: I also fully charged my battery and left it overnight unplugged last night and went from 100%-64% in 8 hours
Sent from my Nexus 4 using xda app-developers app
Hero_Guy said:
Kernels no longer work for me. I was running _Motley's build 49 kernel and the stock ROM for a few months and never had any issues and had excellent battery life. Then I decided to flash PA and _Motley to give Halo a try and noticed my battery wasn't all too great. I then nandroid back to my previous setup and then my battery life went to ****. Android OS was my biggest drain so I reflashed my stock rooted ROM and kernel and still had the same issue.
Then I flashed Faux's reset kernel and was stuck in a boot loop but was unable to get past the Google logo. Flashed another reset kernel, can't remember who's, and everything was fine. Android OS wasn't an issue anymore but my battery life went back to being mediocre. So I tried flashing other kernels, _Motley's included, and Android OS would still be on top.
So for some reason, only the stock kernel is working for me. Any ideas why? I'm about to just restore the factory image and start over again. I heard PA uses a custom kernel from Franco so could that be why I'm having issues?
I also fully charged my battery and left it overnight unplugged last night and went from 100%-64% in about 8 hours.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Here's a logcat
When attempting to wake up device (SPH-L720) from sleep using power or home button, it doesn't wake up, gets blank screen, the menu and back soft buttons LED lights come on, hangs for few secs on the black screen, then reboots by itself. Issue happens randomly and sometimes once a day or multiple times an hour. It seems like the problem existed before rooting and installing custom ROM but I've just noticed it.
I'm using TriForce 3.0 ROM (Android 4.2.2) w/ baseband L720VPUAMDL and kernel 3.4.0-KT-SGS4-ga23d84c. I've tried wiping/reinstall ROM, reflashing back stock ROM, removing microSD card. Nothing helped. The battery charges properly and is usually fully charged. No wear and tear or damage of any kind. Device is 1 month old.
Any ideas what might be causing the problem and suggestions for possible fix?
its because of the kernal, mine does this aswell..
kyledb said:
its because of the kernal, mine does this aswell..
Click to expand...
Click to collapse
Did you find a fix? Does changing the kernel fix the problem? If so, which kernel did you go with? It's driving me crazy lol. Thanks!
I cannot speak to whether or not, as somebody else suggested, the kernal is at fault, but I too am using KT Kernal and have this issue.
beerindex said:
I cannot speak to whether or not, as somebody else suggested, the kernal is at fault, but I too am using KT Kernal and have this issue.
Click to expand...
Click to collapse
Did you notice if you had the issue before rooting and flashing the KT kernel? I'm trying to narrow down the cause. I'm thinking of trying another kernel to test and see if it fixes the problem.
verto8 said:
Did you notice if you had the issue before rooting and flashing the KT kernel? I'm trying to narrow down the cause. I'm thinking of trying another kernel to test and see if it fixes the problem.
Click to expand...
Click to collapse
I don't recall it happening before root, but I rooted fairly soon after getting it. I cannot remember whether it happened while it was stock rooted. As to the kernel, I flashed it immediately after installing my rom, so I would not be able to distinguish between the two as a source.
I switched to the agat kernel and it stopped rebooting until I attempted to watch videos... So I went back to ktoonz..it is most defiantly a kernel issue as this is a known issue with that kernel I deal with it everyday and its absolutely annoying
There is a nice selection to pick from.. Agates..kt...stock....chronic..and faux ..had the same issues on KT but fixed it by UV down 15 across the board ..also for some reason 8/20 worked better for me ..but my fix might not work for anyone else..I really liked chronic..running faux now ..I hated reboots ..my phone was rebooting before I ever rooted it ..who knows my carrier wanted me to bring it in for a replacement ..decided it was time to start reading
beerindex said:
I don't recall it happening before root, but I rooted fairly soon after getting it. I cannot remember whether it happened while it was stock rooted. As to the kernel, I flashed it immediately after installing my rom, so I would not be able to distinguish between the two as a source.
Click to expand...
Click to collapse
Same situation here. I rooted and flash a custom ROM on mine right after I got it. I believe it had the issue pre-root on stock ROM/kernel, but I'm not a 100% sure. I had same issue w/ the Cyanogenmod ROM, not sure what kernel it was using.
kyledb said:
I switched to the agat kernel and it stopped rebooting until I attempted to watch videos... So I went back to ktoonz..it is most defiantly a kernel issue as this is a known issue with that kernel I deal with it everyday and its absolutely annoying
Click to expand...
Click to collapse
Do you remember if you had the issue on stock ROM before rooting? I believe mine has always existed and might be a hardware problem because I tried different ROMs/kernels and issue persisted with all of them.
ParkerParker said:
There is a nice selection to pick from.. Agates..kt...stock....chronic..and faux ..had the same issues on KT but fixed it by UV down 15 across the board ..also for some reason 8/20 worked better for me ..but my fix might not work for anyone else..I really liked chronic..running faux now ..I hated reboots ..my phone was rebooting before I ever rooted it ..who knows my carrier wanted me to bring it in for a replacement ..decided it was time to start reading
Click to expand...
Click to collapse
Is there a comparison thread of different kernels? I'm wondering what the pros/cons of each and maybe some user experience feedback. I believe mine was rebooting as well when it was on stock before rooting. This seems like it might be a hardware problem rather than software (ROM/kernel). Do you think everyone w/ a Sprint Galaxy S4 (SPH-L720) is having this issue? If so, Samsung should do something about it because it's super annoying!
Update: I've been using latest version of KT-SGS4 kernel 3.4.59 (Aug 25 build) for over a day and it's been pretty stable w/ no occurrence of the problem. I'll keep this thread posted w/ updates if I run into any problem. Thanks to everyone for their help!
2nd Update: it still has the problem.
It's still happening but at a slightly lower frequency with the latest KT-SGS4 kernel. For those who have tried a different kernel, did it fix the problem? I'm trying to narrow down the source and convince myself for certain that it's a software rather than a hardware issue.
Same issues
I have been a lurker here for a while, and have found most of the answers that I am looking for without having to ask any questions. For that I say thank you.
I would like to let you know that I am experiencing the same issue with my rooted SGS4. I do not recall having the issue before rooting the phone (I ran it stock for a month or so before rooting it in early July). Today I did a factory reset and re-installed Tri-Force 3.0. Here is some more info if it helps.
SPH-L720
Android 4.2.2
L720VPUAMDL
Hardware Ver. L720.08
Kernel 3.4.0-KT-SGS4-ga23d84c
I am going to try to un-root it this afternoon and go back to out of the box stock to verify it is not a hardware issue.
I am mostly posting here to follow the thread hoping for a fix.
grnerd said:
I have been a lurker here for a while, and have found most of the answers that I am looking for without having to ask any questions. For that I say thank you.
I would like to let you know that I am experiencing the same issue with my rooted SGS4. I do not recall having the issue before rooting the phone (I ran it stock for a month or so before rooting it in early July). Today I did a factory reset and re-installed Tri-Force 3.0. Here is some more info if it helps.
SPH-L720
Android 4.2.2
L720VPUAMDL
Hardware Ver. L720.08
Kernel 3.4.0-KT-SGS4-ga23d84c
I am going to try to un-root it this afternoon and go back to out of the box stock to verify it is not a hardware issue.
I am mostly posting here to follow the thread hoping for a fix.
Click to expand...
Click to collapse
Try that and odin back to stock mf9 not mdl. Tri-force is mf9 based so maybe thats why you get those issues because you need firmware kernel modem and such. Also it could be that kt kernel had been reported to cause some of those issues.
i went to a new rom and new kernal and this is still happening to me, i have no idea what it is now.... any solutions from anyone?
UPDATE: BAD MICRO SD CARD!!!!!!!!!!! REMOVED MY SD CARD AND NO ISSUES IN THE PAST 2 DAYS
NEW UPDATE: SPOKE TO SOON..
Hi,
I hope I made this in the right section but I've got myself into a really nasty problem and I know how to fix it after spending full 10 hours. Maybe this will help anybody.
I re-used my Arc after a while and learned about custom roms and all. I've updated to Stock 2.3.4 - Stock 4.0.4 - Ultrakitkat 2.0.1 - Stock 4.0.4 (back because of trying to compare performances between custom and stock) - Ultimate HD 5.0.1.
When going from Ultrakitkat to Stock 4.0.4, after a day I woke up and found my phone rebooting Android on a loop while in the wall-charger. Went to take a shower and the phone was dead.
Charger didn't work, put it on my laptop USB and went on, only to find the battery at 100%. When disconnecting the phone, it immediately went blank and didn't turned on. I've looked for this problem for so many hours and tried flashing my romand kernel for some time (including phone drops dead WHILE in flashing) and trying out different way's to connect and boot but nothing worked. Installed many battery tools and apps but still nothing.
I;ve searched a lot and didn't found any conclusion anywhere, but combining every information online I've solved it!!
Apperantly there is an error inbetween roms, that when you go from custom rom + certain kernels, back to stock rom, it stops recognizing the battery.
To solve this (for me it worked):
Flashtool stock TFT 4.0.4
Fastboot flash the LUPUSV16 kernel (the magic trick!)
Turn on phone, and put it on a charger for 15 minutes, it should start recharging somewhere and show the correct battery %
I wanted to use the Ultimate HD just for a try and when flashing (I use Advanced Stock Kernel) + Ultimate HD
DO NOT WIPE BATTERY STATS! This will recreate the problem.
This worked for me and I hope this will help someone too who's thinking there is a problem with the battery.
Mostly reflashing the kernel does the job
Sent from my LT18i using xda app-developers app
0 or 100 percent battery
hridayharia said:
Mostly reflashing the kernel does the job
Sent from my LT18i using xda app-developers app
Click to expand...
Click to collapse
Leaving the phone turned off for some hours worked for me!
Thank you!
if you dont want see this problem
do not downgrade to stock kernel
Same issue here.. after fastbooting stock ftf.. Phone not charging and not recognized in fastboot/flashmode
Guys worked for me
Flash rush kernel after downgrading and tada its done.
Its just coz rush recognizes the hardware chip algorithm for battery stats
Sent from my Xperia Arc S using Tapatalk
Swapyyyyy said:
Guys worked for me
Flash rush kernel after downgrading and tada its done.
Its just coz rush recognizes the hardware chip algorithm for battery stats
Sent from my Xperia Arc S using Tapatalk
Click to expand...
Click to collapse
yes, it works flashing other kernel but i encountered a another problem. I lost some of the apps and keep geeting crashing report from diferent sistem apps Does some know how to extract those battery fix from those kernel am apllly it to stock kernel?