I looked everywhere I could for insight into this, but found nothing conclusive.
I am running (see screenshots) the 2013/01/23 build of the AOSP rom found here. I am using the 10-point touchscreen firmware, and the kernel, etc., as shown in the screenshot.
Ever since I "traded up" to this rom, I have not been able to "fast charge" my Nook using the stock AC adapter, as I was once able to running (rooted) stock 1.4.1. No matter what combination of charger, cable, wall-wart, etc., it thinks I'm charging via USB. (See other screenshot - that's AC folks.) I've tried rebooting while it's plugged in, tried two different B&N chargers, a Kindle cable, and another 2-3 micro USB cables. No dice. So it trickle charges all the time. I have to either shut it off or near-sleep everything, and it still takes 4+ hours to fully charge. I miss the 1-2 hour fast charges I used to get.
Would a newer kernel address this? And if so, how do I go about obtaining one? Or does anyone else have any suggestions? I'm stumped.
johnseeking said:
I looked everywhere I could for insight into this, but found nothing conclusive.
I am running (see screenshots) the 2013/01/23 build of the AOSP rom found here. I am using the 10-point touchscreen firmware, and the kernel, etc., as shown in the screenshot.
Ever since I "traded up" to this rom, I have not been able to "fast charge" my Nook using the stock AC adapter, as I was once able to running (rooted) stock 1.4.1. No matter what combination of charger, cable, wall-wart, etc., it thinks I'm charging via USB. (See other screenshot - that's AC folks.) I've tried rebooting while it's plugged in, tried two different B&N chargers, a Kindle cable, and another 2-3 micro USB cables. No dice. So it trickle charges all the time. I have to either shut it off or near-sleep everything, and it still takes 4+ hours to fully charge. I miss the 1-2 hour fast charges I used to get.
Would a newer kernel address this? And if so, how do I go about obtaining one? Or does anyone else have any suggestions? I'm stumped.
Click to expand...
Click to collapse
If I were you I would make an SDC version of the ROM and have stock on your internal. You could charge your nook on the stock os and run your ROM off the SD card.
Does anybody ELSE have any suggestions? Is this an issue that anyone else is seeing on this or any other 4.1.x rom or this or other kernels?
johnseeking said:
Does anybody ELSE have any suggestions? Is this an issue that anyone else is seeing on this or any other 4.1.x rom or this or other kernels?
Click to expand...
Click to collapse
I'd suggest you try a different 4.1 build such as CM10.0 build dated 12/31 by Succulent which is posted at http://iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet/.
*sigh* Thanks for the suggestion. I think since the charging speed isn't really a deal-breaker for me, and since I'm loath to re-redo all the tweaks I've put into my tab on this rom, I will probably just wait 6-12 months for a phenomenally stable (official CM?) 4.2 rom (or higher??) to come along before I make any more big moves. 1st world problems, amirite? :crying:
Edit: noob question. For the sake of argument, since they are both built on 4.1, would the world explode if I tried dirty-flashing said CM 12/31 over what I'm running now? Would all my apps and other crapola still be there? I.E., would Android just see it as an "upgrade" like the other AOSP builds I have dirty-flashed in the past?
When you dirty-flash a different build (i.e. not wiping /data), your downloaded apps should be intact but some might not work properly with the new build, in which case an option could be to un-install and re-install those apps that ill-behave. With a clean flash, if you use Google Backup/Restore your downloaded apps should be automatically re-downloaded following first boot and Google account setup, but you will have to re-enter your apps personal settings. To preserve the apps and personal settings you can try to use a Backup/Restore app such as Titanium Backup.
So, a potential course of action for you would be to first try out a different build on SD to see if it fixes your charging problem; if the new build does fix your problem then you can proceed to flashing it internally on emmc:
Do a full back up of your current ROM using CWM Recovery's backup feature (see http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31).
Do a Titanium backup of your apps & settings
Try a dirty flash and see you can get away with it and use Titanium to restore any ill-behaving apps
If the results from previous step are not satisfactory, do a clean flash and use Titanium to restore apps and/or their settings as needed.
If you don't like the new build for any reason, use CWM Recovery's restore feature and the full-backup dataset (that gets created in the first step above) to fully restore your NT to your previous build.
You make it sound so easy. Thanks again. I will give it a go sometime in the next few weeks and report back here.
Try downloading the BatteryCalibration app from the Play Store, charge your device to 100%, and click the button (assuming you're rooted because you're running a custom ROM).
Related
Hello,
I downloaded the official rom from the official HTC website.
It is the WWE East Europe version - suited for my device because the SN is confirmed.
The download finished OK from the Europe 2 server.
I flashed by placing the extracted leoimg.nbh on the root of the SD Card.
I confirmed that the flash was successful - it shows the correct version number of Manilla, radio, etc. Additionally, the ROM is still only 448 MB.
However, the phone freezes all the time and/or restarts itself complely randomly - I have observed this 22 times in the past hour. Is anyone experiencing something similar?
I have redone the flash again, but the same issue occurs.
This is happening with no programs installed, no HSPL, etc. Everything is completely clean.
What can I do to stop this?
may i know why you flashed the latest stock rom using your sd card. would it not be easier to flash through your pc using a usb cable?
you might want to check the meaning of "bricking the phone"...........
then remove it from the title of the thread........
As Rurph mentioned, flash it via your pc, still following the instructions from theHTC site
I now tried flashing through PC, same freezing occurs.
To reiterate:
I have an original HTC HD2 bought from the official HTC shop in Czech republic.
I downloaded the latest official ROM for HTC HD2 from the official htc.com/cz website using my original serial number.
The download finished successfully every time (I tried it 5 times from all the different servers), and the SHA-1 hash of the files was identical every time.
I now flashed it using the normal PC method - everything appeared successful.
I also tried extracting the nbh file from the downloaded file - both by running the .exe file, and by extracting it using winrar - both methods gave me the same nbh file with the same SHA-1 hash. Then I moved the leoimg.nbh to the root of SD card and flashed using the SD-Card method. Everything appeared successful.
Both of the above methods give me a system that freezes completely at random. For example when starting the phone, it can just freeze (left it for 8 hours over night, it remained frozed), when moving from 1 tab to another (freezes in the middle of the animation), when opening the start menu, when going into settings, when making phone call, when opening SMS, and most importantly when NOT DOING ANYTHING AT ALL.
What can I do?
Try to flash an older Version.
I don't know if its possible, but maybe that solves your problem.
Did you have SPL 3.03? If no... Install HSPL and use a custom ROM like the one from NRGZ28 (EnergyROM)
If you an't flash the older version via RUU (Rom Update Utility) try to flash it from SD card. You can also perform a "task 29" with MTTY (before you flash)
But be careful, you can brick your phone...
I have always only used official ROMs from HTC, so I never needed HSPL so I never installed it. I also always prefer the official ROMs so I would rather not use a cooked one.
I think flashing an older version would solve the problem, however I would rather like to find out what the cause is...
So far, I managed to get my phone to a useable state by running Android from the SD card - it works flawlessly for all my purposes. The only problem was to start Android through Windows before windows manages to freeze...
Given that android does not freeze, I believe that the freezing problem must be a windows mobile issue.
Any suggestions for tracking down this freezing problem? Could it be a hardware issue?
hard reset. and if no better flash the rom again followed by hard reset.always hard reset straight away as soon as you see a glitch in a freshly flashed rom. don't ask me why, cos i don't know, but it does seem to help when a flash doesn't "take".
oh and you didn't leave the old application data folder on your sd card did you? or try to restore registry settings?
samsamuel said:
hard reset. and if no better flash the rom again followed by hard reset.always hard reset straight away as soon as you see a glitch in a freshly flashed rom. don't ask me why, cos i don't know, but it does seem to help when a flash doesn't "take".
Click to expand...
Click to collapse
I always hard reset before and after a flash. No change - freezing still occurs.
Even when I did multiple hard resets, the freezing persisted.
The SD card is freshly formatted, checked for no filesystem errors.
I did not restore any settings or anything else - the problem occurs on a completely fresh clean flash.
Additionally, the problem occurs even with no SIM card or SD card inserted into the phone.
Overheating?
I concur with rr5678, seems more like overheating than ROM problems, esp. that I've had the same ROM for a week with no problems whatsoever
hence kind request to OP: check overheating threads and please change the thread subject to a more accurate one so it does not spread misinformation and panic
as for the overheating - 1st thing to do is installing BattClock and monitoring correlation between freezes and battery temperature
rr5678 said:
Overheating?
Click to expand...
Click to collapse
The phone is definitely not overheating. It is very cold to touch and it runs Android without a problem.
OK I did some more testing - going back to any previous ROM fixes the freezing. Then installing the newest ROM reintroduces the freezing.
Given that it is definitely not a hardware issue (works on previous ROM, works on Android, no overheating), it looks like a Windows mobile issue.
I am surprised that nobody else is experiencing this. How come I am the only one? What is so special about my phone?
And the new firmware can "brick" the phone - a less skilled user would not be able to do anything with a frozen phone...
Anyone know why I get no ringtones or alarm sounds when using 1.8?
Deliberate?
Edit: Weird, seems first time a check a ringtone or alarm sound list it's empy. I leave then go back, it's populated again. So self-fixing issue.
Edit 2: Yeah.. tabs got mixed up, completely wrong thread, sorry!
Anyone help?
HTC Support is as always useless - their advice was to take out the battery and put it back in...
Additionally, I think this is a similar problem:
http://forum.xda-developers.com/showthread.php?t=818169
b2206015 said:
Anyone help?
HTC Support is as always useless - their advice was to take out the battery and put it back in...
Additionally, I think this is a similar problem:
http://forum.xda-developers.com/showthread.php?t=818169
Click to expand...
Click to collapse
Try another sim card if you can. I know it sounds crazy but...
wardh said:
Try another sim card if you can. I know it sounds crazy but...
Click to expand...
Click to collapse
Thanks for the advice - but given that the phone freezes even with no SIM card inserted, I do not think that it is the case...
I have however tested inserting a different SIM card anyway, and the freezing occured again...
I too faced constant freezing problems with the official ROM but then I used HSPL and flashed a different radio (2.12 in my case) and ever since never faced any freezing problems..worth a try I guess...
epic fail
not being picky, but "bricking" is, as far I know, by definition an irreversible problem? Hanging and freezing and re-booting are not bricking.
That said, sorry to hear about your troubles.
Sounds like going back to your old ROM is the only solution right now.
b2206015 said:
Hello,
I downloaded the official rom from the official HTC website.
It is the WWE East Europe version - suited for my device because the SN is confirmed.
The download finished OK from the Europe 2 server.
I flashed by placing the extracted leoimg.nbh on the root of the SD Card.
I confirmed that the flash was successful - it shows the correct version number of Manilla, radio, etc. Additionally, the ROM is still only 448 MB.
However, the phone freezes all the time and/or restarts itself complely randomly - I have observed this 22 times in the past hour. Is anyone experiencing something similar?
I have redone the flash again, but the same issue occurs.
This is happening with no programs installed, no HSPL, etc. Everything is completely clean.
What can I do to stop this?
Click to expand...
Click to collapse
Psaldorn said:
Anyone know why I get no ringtones or alarm sounds when using 1.8?
Deliberate?
Edit: Weird, seems first time a check a ringtone or alarm sound list it's empy. I leave then go back, it's populated again. So self-fixing issue.
Edit 2: Yeah.. tabs got mixed up, completely wrong thread, sorry!
Click to expand...
Click to collapse
Well, to me it seems your phone just doesn't like custom ROMs.
Hi
I have tried many ICS roms and they seem to have wireless problems.
at times it takes time for them to connect or at times they are not able to connect. sometime there is no error message but at times i get authentication error (btw authentication credentials are correct). Is something wrong with ICS. Si anyone else have these problems. Is there any fix for it. i have tried many ics roms with different combination of kernels, mostly its the same issue.
i always have to revert back to GB rom and wireless is fine.connects instantly
any help will be appreciated.
thanks
Hi,
Same here. But I can't decide if it is because of juice defender or ICS. In GB worked ok even with Juice defender.
Sent from my GT-I9100 using Tapatalk
xinfinityoO said:
Hi
I have tried many ICS roms and they seem to have wireless problems.
at times it takes time for them to connect or at times they are not able to connect. sometime there is no error message but at times i get authentication error (btw authentication credentials are correct). Is something wrong with ICS. Si anyone else have these problems. Is there any fix for it. i have tried many ics roms with different combination of kernels, mostly its the same issue.
i always have to revert back to GB rom and wireless is fine.connects instantly
any help will be appreciated.
thanks
Click to expand...
Click to collapse
I've had the same problem. Tried many different ICS roms over the last 2 weeks or so.
The last one I tried - HyDrOG3N-ICS was horrible...
Wireless would not connect at all, even though I was standing right next to the router.
After reading through the forums etc I decided to start from scratch.
I reloaded stock Samsung rom with odin, hard reset the phone, formatted my external sdcard and deleted everything on the int sdcard.
I then loaded latest siyah GB kernel.
After this, I install HyDrOG3N-ICS 23.03
Installed GApps
Rebooted and waited 20 minutes (read it somewhere on the forums)
Rebooted and changed to SiyahKernel v3.0beta6 kernel
And finally installed DXLP7 modem.
I then reloaded all my apps from Market (Not apps restored from backups)
After all this, everything seems to work very well... Wireless is connected and working well.
I do have a problem with mobile data disconnecting every now and then, but it returns after a minute or so - might even be a problem with my provider.
I dont know which one of these steps was actually required - but this sorted it out for me.
It's almost like I had 'leftover' bits and pieces of all the different roms I tried... If it makes sense?
I dont know enough to confirm if this was the case - perhaps its not possible.
Perhaps it was just a happy shot that it all worked for me.
If you have a couple of hours spare - give it a bash...
Cheers
jakezpeenz said:
I've had the same problem. Tried many different ICS roms over the last 2 weeks or so.
The last one I tried - HyDrOG3N-ICS was horrible...
Wireless would not connect at all, even though I was standing right next to the router.
After reading through the forums etc I decided to start from scratch.
I reloaded stock Samsung rom with odin, hard reset the phone, formatted my external sdcard and deleted everything on the int sdcard.
I then loaded latest siyah GB kernel.
After this, I install HyDrOG3N-ICS 23.03
Installed GApps
Rebooted and waited 20 minutes (read it somewhere on the forums)
Rebooted and changed to SiyahKernel v3.0beta6 kernel
And finally installed DXLP7 modem.
I then reloaded all my apps from Market (Not apps restored from backups)
After all this, everything seems to work very well... Wireless is connected and working well.
I do have a problem with mobile data disconnecting every now and then, but it returns after a minute or so - might even be a problem with my provider.
I dont know which one of these steps was actually required - but this sorted it out for me.
It's almost like I had 'leftover' bits and pieces of all the different roms I tried... If it makes sense?
I dont know enough to confirm if this was the case - perhaps its not possible.
Perhaps it was just a happy shot that it all worked for me.
If you have a couple of hours spare - give it a bash...
Cheers
Click to expand...
Click to collapse
i have read many ppl have some issues with wireless on ICS. i was thinking about doing a factory reset , wipe both my internal and external storage.. but seems like quite a big job getting everything back..oh wellif i am really tempted i will go ahead and do it..but will wait for a while for more ICS build to come out.could be a bug in the official roms itself
Hi everyone,
My apologies if these issues can be solved by searching, I have tried and have spent many days already trying to sort out these issues then more keep arising.
Issue #1: Battery drain
I have the dreaded Android OS/kworker/wakelock bug - I'm losing 100% battery life within 6 hours and there seems to be nothing I can do about it. I'm planning on doing a full wipe of the phone and trying a reinstall of the OS to see if this solves the issue - but that brings me to issue #2
Issue #2 - Phone is not connecting to PC via USB
I am trying to do a backup and obviously flash my phone once the backup is done with the stock ROM for my phone (I am running a stock ROM at the moment but a clean version rather than the one from my provider loaded with rubbish) - http://forum.xda-developers.com/showthread.php?t=1602579 - the phone will not connect to the PC via Kies USB, it is charging via the USB but Windows reports "Driver installation failed" when it attempts to install the USB drivers to use the phone in mass storage mode.
I have tried in debug mode (it's on right now) if anyone was going to ask that.
Currently running 4.0.3 Official
Download mode DOES work and drivers install fine (Odin gives yellow box)
I have tried uninstalling and reinstalling KIES
Going to see if I can connect it via Wifi now to try and get all my stuff off - even if it is slowly :/
Thank you everyone for any help - I am rather upset that my phone which has worked perfectly up until now has suddenly gained 2 major issues at once - one of which cancels out me sorting out the other :<
i had similar issue,
uninstall kies, install USB drivers ONLY... restart
try different usb cables, make sure MTP is enabled if ur using a custom rom, on resurrection before 1.5 you had to run a few commands in terminal, thats what made it work for me!
Thank you for the information - I'm uninstalling KIES now - how do I just install the USB driver without installing KIES? I just tried reinstalling KIES again and had the same problem. Windows just fails to find any drivers and reports a failure to install the device. Which makes no sense because Samsung drivers are installed - Windows seems to be insistent on looking on Windows update, in preconfigured folders and then giving it a big red cross
http://dl.dropbox.com/u/34590193/SAMSUNG_USB_Driver_for_Mobile_Phones.exe
Hope this helps.
Thank you for that - I'm about to try a full wipe and see if that does anything for me.
Also on your PC go to Computer/Properties/device manager. Connect your samsung phone via USB. uninstall the samsung driver.Unplug your usb then plug it back in.
reinstall the drivers.
I was having these issues on the official Rom so I flashed resurrection Remix v1.5 (ics 4.0.4) and problem solved... If you have charged only one cycle I recommend you try some more...
Sent from my GT-I9100 using Tapatalk 2
Sent from my GT-I9100 using Tapatalk 2
Doing the full wipe did seem to solve the Android OS bug - until I unplugged it from the charger this morning and after 13 minutes I'm sitting on 88% battery CPU Total is 33m 19s and Keep awake is 12m 25s so once again kernel wakelocks are keeping it from deep sleep and draining the hell out of the battery.
I have just uninstalled ANY app on the phone that says "Able to prevent phone from sleeping" that I can uninstall in the hope that it's something simple.
Going by the fact I just did a reboot and already Android OS is using 83% battery - I don't think so.
The strange thing is that for about 2 weeks ICS was working perfectly - then with no warning at all it started draining the hell out of the battery with kernel wakelocks and for the life of me I can't figure out why.
Maybe I'll downgrade to GB and see if it helps.
Did you solve issue 2 so that issue 1 can be resolved. If you did then from recovery do a full wlpe, ie data/factory reset, delvik cache, battery stats. Then format system in mounts & storage. Install original gb firmware from Odin.
Sent from my GT-I9100 using xda premium
Hi all - thank you for the help thus far. I have an update:
I have downgraded the phone to my carrier's official 2.3.6
Neither issue is solved, Odin will see the phone if I boot it in download mode but Windows will not see it at all. I did a backup of all my data over Kies Air though and have done several wipes which were needed in order to downgrade to 2.3.6
The phone is still draining within 3-4 hours from a 100% reported charge. If I plug the phone into USB on the computer it reports as Charging (AC) which I found odd - since it used to say Charging (USB). I'm wondering if the battery is not getting a full charge since it's not being charged at full voltage but thinks it is?
I now have a new issue I didn't have when I previously ran 2.3.6 - the screen turns itself on and if I try to turn it off by pressing the power button it freezes, reboots and then repeats the same again.
I have done about 15 wipes so far, I've used 6 different MicroUSB cables and reflashed 2.3.6 7 times already - at this point I'm really over it since the phone is just unusable and I'm assuming there MUST be a hardware fault somewhere so I'm thinking I'll have to send it in for service and be without it for at least 2 weeks.
I'm rather frustrated by this whole thing because none of it makes sense. I've been told by the service guys to reflash right back to the branded 2.3.3 that shipped with the phone to see if that solves the problem and if not, to send it in.
If anyone else has any idea what I can do to fix this please let me know - it would be very much appreciated so I don't have to be without it for a minimum of 2 weeks :<
Phone is currently sitting next to me charging off USB - I just pressed the power adapter since again the screen was stuck on and it shut itself off. It now has the usual picture of the battery on the screen with the white dots moving underneath.
Another update:
Just did yet another wipe and for some reason this time the CSC comes up instead of coming up as unknown, and initially Windows detected it when I plugged it in via USB - then promptly said the device was unplugged a second later.
Got it charging now, but so far haven't seen the screen turn on randomly so it could just be that the problem of battery usage is solved, by downgrading from ICS to GB
I still suspect the USB port may be faulty since it's still not working within Windows (it does say MTP Connected though) but it still says "Charging (AC)" in the Settings -> About menu.
You need to try another PC or laptop. Also have you tried downgrading to 2.3.3.
Do a full wipe. If downloading the 2.3.3 firmware from Samfirmware, download the flash program too. Then try putting the recomended .pit file into odin.
Sent from my GT-I9100P using Tapatalk 2
Edit: Scratch all that - I just downgraded completely to 100% stock original shipped 2.3.3 carrier branded bloatware firmware and it appears in Windows straight away without any issues. This is really quite annoying >_< but I guess I'm stuck on 2.3.3 for now since it works or risking the ICS upgrade to 4.0.3 again and just downgrading again if the poop hits the proverbial fan.
Thank you everyone for your help - I still suspect the USB port may be bad but at least it's working for now. Please feel free to close the thread mods.
Update: For those that are interested - I have now upgraded to ICS again and it's working perfectly. Which is really odd and makes no sense. But for those interested:
I was running 4.0.3 unbranded (OPS but with XEU CSC) XXLP8 - USB not working, battery draining in 4-5 hours, USB detects as AC for some reason
Downgraded to 2.3.6 Unbranded (XSA) - USB detecting on phone and saying connected, CSC coming up as unknown but format fixed this. Drivers not installing in Windows for Kies or MTP - suspected USB port
Downgraded to 2.3.3 Branded (OPS) - This was what shipped with my phone, USB started working with MTP, pops up in Windows no problem - CSC working
Upgraded to 4.0.3 unbranded (XSA) - Still working with MTP in Windows without issue. Battery drain seems to be solved as well but we'll see.
USB when plugged in is now detecting in settings -> about phone as Charging (USB) again as well.
I have no idea what the hell happened, I've done so many wipes the last few days and everything else it just all makes no sense (speaking of which I haven't done a wipe since I upgraded from 2.3.3 to 4.0.3... I should probably do that) and for whatever reason downgrading all the way back has solved it. Thank you again everyone for trying to help, I guess it's just one of those weird issues that noone can explain :/
Hey guys,
been reading here a lot. However, I always found help to my problems. Except for this one:
All happened after I finally decided to move over to CM11m7 from Stock and rootet JB4.1.2. I also repartitioned the phone to have 4 GB for apps, which I did in the process of switching to CM. When my phone is plugged into the wall charger, it reboots after some time. I am presented then with the screen to enter my PIN. When I enter it (and leave it connected), then after some time, it will reboot again. This does NOT happen when charging over USB from the computer. Only wall charger affected (tried also two different ones, one being the original that came with the device, the other one from Nexus 4).
Here is what I've done so far:
* Switched off WiFi while on charger
* Switched off GSM/Mobile data while on charger
* Installed Gustavo_s' kernel (21.06.2014)
* Factory reset/wipe cache/wipe dalvik cache
Still, the problem persists. Luckily, the alarm is not affected and still works when PIN is asked for. With rootet stock rom I never experienced anything like this.
Has anyone had this before? Are there somewhere some log files that I could investigate? You help is very much appreciated. I have no idea what else to do. Eventually I would have to switch back to stock, if I cannot get this sorted out (but I love CM!)
EDIT: Maybe some info on my device:
GT-I9100 international version (CSC is from Swiss carrier, however, I used unbranded German stock rom before)
Hello Devs,
I have problem charging my s3 international version.
My phone is rooted and running custom rom s5 sensation v4.0 kitkat 4.4.2 with boeffla kernel v6.0 and latest CWM touch recovery.
I have flashed many custom roms before and all was working good before. The phone was also charging properly before.
But after some time when 4.3 was released I have flashed s4 revolution.
After flashing that rom my problem started.
1st problem was the phone was not gettin connected to my cell tower. Later after searching soo many hours on google I found out that it changed the efs version from v1 to v2. So I found out a rescue zip file which include only modem of xxemg4. I flashed it and then all was working good.
After some time I faced a problem of reverse charging means the phone is kept on charge but instead of charging the battery decrease. So again I searched on google about my problem and found out an app called galaxy charging current which show the power that is getting the phone while its connected to the charger. when I installed it and saw the current it was only showing max 100 min 999 and avg 100. I saw some where that the default current the phone should get is 1000 in max.
I searched alot on google on how to solve this problem, tried many diffrent rom , tried changing my charger, tried to flash back the previous rom which I was using in which I was not having any problem but after doing all this the result was same.
when I connect to the charger it shows 700 In max n after some time it keeps going down like 500 then 300 then last 100.
So after searching on google I have found out a solution of flashing custom kernel. I flashed googymax kernel in which using sTweak we can configure the battery power and ignore safety measures and unstable power.
After doing that my phone gets max 1000 min 1000 and avg 999.
My problem is that when ever I flash new rom I hav to flash custom kernel to ignore the unstable power and safety measures to properly charge my phone.
is there any way I can get back as before I was charging my phone without flashing custom kernel...???
Any answer will be appreciated.
Note :- I was using the original charger which I got in the box while purchasing.
First replace your battery, charger and lead, then flash full stock firmware with Odin.
What happens when you attempt to charge the phone completely off. Do you see the charging graphic?
If something is wrong with the micro-USB port then a wireless charging solution might be your only option.
You could try reloading the firmware using the Kies software on your PC - here's an overview of what to do:
- if you don't already have the Kies software installed on your PC, download it (just search Google) and install it. The first time it runs it'll update itself to the latest version so make sure you run it once before proceeding.
- put your phone in Download mode: with the phone completely off, press and hold the Volume Down and Home and Power buttons simultaneously, and release them all when you see the Samsung splash screen
- connect the phone to your PC with the USB cable that came with the phone
-- if you've never had the phone connected to your Windows-based computer before, you'll see messages about installing drivers, etc - just wait until this is done (may take 5 or 10 minutes) [I don't know what happens if you have a Mac - it probably just works]
- in the Kies software, select the second item in the Tools menu and just follow the prompts to enter the model number (in CAPS) and IMEI/Serial Number (both found under the battery - it's ok to remove the battery at this point)
- the Kies software should start downloading the correct firmware for your phone from the Internet; once that's done (depending on your Internet connection speed) it'll begin downloading that to the phone (this probably takes 10 minutes or so)
Thnaks for your rply
boomboomer said:
First replace your battery, charger and lead, then flash full stock firmware with Odin.
Click to expand...
Click to collapse
1st of all thanks for replying on my query.
As u stated to change the battery, Charger, Lead and to full flash stock firmware.
I already did that.
I have tried my friends battery with his charger ( not the 1 which come in box ).
but then also its the same.
Whats the problem in it.
Is it a software fault or hardware fault....???
Hermosa said:
What happens when you attempt to charge the phone completely off. Do you see the charging graphic?
If something is wrong with the micro-USB port then a wireless charging solution might be your only option.
You could try reloading the firmware using the Kies software on your PC - here's an overview of what to do:
- if you don't already have the Kies software installed on your PC, download it (just search Google) and install it. The first time it runs it'll update itself to the latest version so make sure you run it once before proceeding.
- put your phone in Download mode: with the phone completely off, press and hold the Volume Down and Home and Power buttons simultaneously, and release them all when you see the Samsung splash screen
- connect the phone to your PC with the USB cable that came with the phone
-- if you've never had the phone connected to your Windows-based computer before, you'll see messages about installing drivers, etc - just wait until this is done (may take 5 or 10 minutes) [I don't know what happens if you have a Mac - it probably just works]
- in the Kies software, select the second item in the Tools menu and just follow the prompts to enter the model number (in CAPS) and IMEI/Serial Number (both found under the battery - it's ok to remove the battery at this point)
- the Kies software should start downloading the correct firmware for your phone from the Internet; once that's done (depending on your Internet connection speed) it'll begin downloading that to the phone (this probably takes 10 minutes or so)
Click to expand...
Click to collapse
Thanks for the reply.
When I try to charge my phone when completely off, 1st it was showing me the graphics of battery charging when I was using 4.3 Custom Rom. But since I flashed my phone with 4.4 Custom Rom, I can't see the graphics of charging battery now.
As per your overview above I have tried all the possible ways to get back charging work properly ( your overview was also included in it ) but I dont get any success in it.
Now I have to compulsory flash custom kernel which supports the options of ignoring unstable power and safety measures.
But then also I will try to do what you told me.
Once again thanks.