Related
I cant charge my phone after flashing the speedmod RAGEMOD kernel and undervolting it. I already tried reverting back to stock voltages, even tried flashing over jeffery's speedmod kernel and finally back to the original T27 speedmod. None of them could make my battery charge via the phone using the wall charger or via USB. Instead when it plug it in it keeps telling me "Battery Disconnected" and battery status is shown as "AC" but "not charging". What gives? Wiping cache partition and recalibrating the battery doesnt help!
EDIT: Help please! Factory wipe didnt work either! Is there such a thing as a charging brick?
Flashing new ROM doesnt help either! Am i doomed?
Firstly, that's not Speedmod kernel by Hardcore, because Speedmod doesn't do OC and UV.
RAGEmod by RAvenGEr is based on Speedmod, however has OC + UV and extras added to it.
I wouldn't recommend using any kernels that has OC and UV, reason is, it's a phone, why are you even overclocking it? As for UV, the power savings might be worth it, but for a phone that might not receive calls or might freeze during heavy load doesn't appeal to me. (MIGHT is the keyword).
Which is probably why Hardcore doesn't include OC+UV in his kernels.
Anyways... In order to remove the settings, you will have to wipe the userdata partition. You can also flash to another kernel that ignores OC+UV settings. Ignoring the settings doesn't mean that settings are not there, so if you use another kernel that has OC+UV, that settings might cause you some grief. If wiping the settings still doesn't work, that means the RAGEmod might have modified charging current and it is time to claim warranty at the nearest Samsung Service Center.
LiFE1688 said:
Firstly, that's not Speedmod kernel by Hardcore, because Speedmod doesn't do OC and UV.
RAGEmod by RAvenGEr is based on Speedmod, however has OC + UV and extras added to it.
I wouldn't recommend using any kernels that has OC and UV, reason is, it's a phone, why are you even overclocking it? As for UV, the power savings might be worth it, but for a phone that might not receive calls or might freeze during heavy load doesn't appeal to me. (MIGHT is the keyword).
Which is probably why Hardcore doesn't include OC+UV in his kernels.
Anyways... In order to remove the settings, you will have to wipe the userdata partition. You can also flash to another kernel that ignores OC+UV settings. Ignoring the settings doesn't mean that settings are not there, so if you use another kernel that has OC+UV, that settings might cause you some grief.
Click to expand...
Click to collapse
Thanks for the reply.
Like i said, already flashed 2 other kernels (including the original speedmod by hardcore) and i did not touch any of the settings after that. And i have NEVER overclocked this phone before, only undervolt. I did a full wipe of my phone, but it didnt work, i am running TOUCH X KG5. So i did another full wipe and flashed Cognition 1.5 which comes with his own kernel i suppose. It worked at first, at least for a few minutes before the battery disconnected notification popped up again. To my disappointment, i tried plugging the phone in while it was turned off. And to my horror it showed the battery logo with a yellow triangle and exclamation mark on it. Meaning the phone is unable to charge even while its turned off. Ive no idea why and i have never heard of a "charge brick" on any phone before, and definitely not on the SGS2. Anyway isnt a full wipe and a flash of a new ROM supposed to erase and overwrite any previous OS files? Which means my old corrupted settings should have been gone by then.
I ended up using the USB jig i bought some weeks back, and it works fine. Right now im charging my phone via USB (not wall charger) and it seems to be charging like normal. Strangely enough, my phone seems to charge fine AT LEAST for now...
cr0wnest said:
Thanks for the reply.
Like i said, already flashed 2 other kernels (including the original speedmod by hardcore) and i did not touch any of the settings after that. And i have NEVER overclocked this phone before, only undervolt. I did a full wipe of my phone, but it didnt work, i am running TOUCH X KG5. So i did another full wipe and flashed Cognition 1.5 which comes with his own kernel i suppose. It worked at first, at least for a few minutes before the battery disconnected notification popped up again. To my disappointment, i tried plugging the phone in while it was turned off. And to my horror it showed the battery logo with a yellow triangle and exclamation mark on it. Meaning the phone is unable to charge even while its turned off. Ive no idea why and i have never heard of a "charge brick" on any phone before, and definitely not on the SGS2. Anyway isnt a full wipe and a flash of a new ROM supposed to erase and overwrite any previous OS files? Which means my old corrupted settings should have been gone by then.
I ended up using the USB jig i bought some weeks back, and it works fine. Right now im charging my phone via USB (not wall charger) and it seems to be charging like normal. Strangely enough, my phone seems to charge fine AT LEAST for now...
Click to expand...
Click to collapse
You could try flashing back to stock using odin and staring afresh before root, if you got it charging.
Otherwise this just sounds like your battery is fubar.
mynamesteve said:
You could try flashing back to stock using odin and staring afresh before root, if you got it charging.
Otherwise this just sounds like your battery is fubar.
Click to expand...
Click to collapse
I tried both the stock original battery and a third party one I bought and they're both behaving the same way. I charged it a bit with the wall charger just before I left the house this morning, and all seems well though. Maybe the jig resets something else other than just the flash counter?
I'll try flashing back to stock tonight and see what happens. Thanks!
Sent from my GT-I9100 using XDA App
cr0wnest said:
To my disappointment, i tried plugging the phone in while it was turned off. And to my horror it showed the battery logo with a yellow triangle and exclamation mark on it. Meaning the phone is unable to charge even while its turned off.
Click to expand...
Click to collapse
dude the yellow triangle just means the battery is low....it always happens with me when I turn my phone off and plug the charger in....did you leave the phone plugged in for a while ? it should charge...
Sent from my GT-I9100 using Tapatalk
beaver2233 said:
dude the yellow triangle just means the battery is low....it always happens with me when I turn my phone off and plug the charger in....did you leave the phone plugged in for a while ? it should charge...
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
Really? I've no idea cos I don't charge the phone with drained battery while its off. I'll be sure to take note of that now.
Sent from my GT-I9100 using XDA App
cr0wnest said:
Really? I've no idea cos I don't charge the phone with drained battery while its off. I'll be sure to take note of that now.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
yeah its a bit worrying when you see the yellow triangle and exclamation, but yeah it means the phones battery is 'critically' low...and also the fact you turned the phone off and connected it to the charger and the phones screen turned on that's a hint its getting power from the charger
Sent from my GT-I9100 using Tapatalk
beaver2233 said:
yeah its a bit worrying when you see the yellow triangle and exclamation, but yeah it means the phones battery is 'critically' low...and also the fact you turned the phone off and connected it to the charger and the phones screen turned on that's a hint its getting power from the charger
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
Hmm I should check it again tonight.. When I get the battery disconnected message, the phone power status is recognized as "AC" however the battery status shows "not charging". Very unusual indeed..
Sent from my GT-I9100 using XDA App
My s2 some time half way will stop charging and power drain fast but status show battery on charging.phone getting hot.and than I power off phone to charge everything is ok. This happen after flash custom rom.
After I switch back original rom everything back to normal.but if I use other kernels the problem back again even use original rom. Not sure usb jig can solve this problem not.
rolandyip said:
My s2 some time half way will stop charging and power drain fast but status show battery on charging.phone getting hot.and than I power off phone to charge everything is ok. This happen after flash custom rom.
After I switch back original rom everything back to normal.but if I use other kernels the problem back again even use original rom. Not sure usb jig can solve this problem not.
Click to expand...
Click to collapse
The jig seems to have solved my problem. I guess it also resets the battery charge settings when you plug it into the phone. Which is a good thing. fairly inexpensive too, its worth a try.
Sent from my non-Apple device via XDA App
cr0wnest said:
The jig seems to have solved my problem. I guess it also resets the battery charge settings when you plug it into the phone. Which is a good thing. fairly inexpensive too, its worth a try.
Sent from my non-Apple device via XDA App
Click to expand...
Click to collapse
just get a usb jig and try to solve it. still the same.
i think i have to flash back default rom and bring back samsung and check.
May be only singapore S2 got this type charging probem
I'm hoping someone can shed some light on this problem.
I've been using my X10 Mini running CM7-2.2.0 for internet access (both USB tethered and Wi-Fi hotspot) for the past couple weeks while traveling. About a week ago I started having problems with the phone randomly shutting off during an internet session (usually preceded by a single vibrate). It's gotten progressively worse. Whereas at first it was only happening after surfing the internet for awhile, now it's at the point where I can power on the phone in airplane mode and use it for awhile, but as soon as I turn on the GSM or 3G radio, the screen simply goes dark and the phone is off.
I suspect it's one of two problems: either there's a power issue, or the phone (particularly the GSM/3G radio) has become defective. To back up the theory that it's a power issue, I've noticed some strange things with the battery and it's reported charge level. Today I left the phone plugged in while off (charging from the USB charger for my Kindle, which outputs 850mAh). After a few hours the screen showed it as being fully charged. Then I turned on the phone and it said the charge was 33% percent. Still, even if it was only 33%, as soon as I turned on the 3G radio, it died.
I've tried charged with 2 different microUSB cables, one supplied with my Amazon Kindle, one from a Nokia phone, so both are quality cables. I don't have the original charger and cable with me to try those, but it seems like I should be able to get a charge between 2 decent cables, 1 wall charger and the USB ports on my Thinkpad laptop.
I did try doing a wipe and factory restore of the MiniCM7 ROM just in case, and also tried reverting to a previous MiniCM7 version just in case that one would be problem free, but it's no different.
I guess there's a 3rd option: could it be an issue with the nAa kernel?
Any help or input is appreciated.
Something similar happened to me when i was on MiniCM7-2.2.0
It's definitely an issue with the ROM, not the kernel.
I went back to stock with xrecovery and did a couple of battery-calibrations (drain the battery, charge it on the wall-charger and do a battery-stat wipe when starting up the phone again)
I still can't get a 100% full charge and when the batterylevel sinks below roughly 30 percent getting and making calls results in the same behaviour as your phone (forced shutdowns), but i have a half-decent batteryperformance again.
I have a strong feeling that MiniCM7-2.2.0 doesn't like usb-charging very much, but i don't have any hard evidence to back that up, but i know some other people have the same sort of issues.
It's definitely not the kernel itself, becaue i'm using it now with a different rom for testing and the battery behaves roughly the same as on stock firmware. If you get your battery back to decent performance (don't think it will ever be completely good again), earlier versions of MiniCM7 don't seem to have this particular issue, so stay away from MiniCM7-2.2.0.
That's about all i could advice you, it seems to be the only rom that displays this particular behaviour.
Great to hear at least someone has had this problem. Have you tried other Gingerbread ROMs, such as GingerDX?
Thanks very much for your input.
Yes, i've tried GingerDX, quite like that one too, and i've tried MiniCM7-2.1.9, which is one version older than the 2.2.0, I'm testing a new one now GIngerZaraki, and none of those seem to have this particular issue.
Did you post in the MiniCM7 thread regarding the issue? Just wondering if I should pos there about this. This seems like a very serious issue if it is to do with the ROM. I just tried restoring MiniCM7 2.1.7 and I'm having the same problem though (although ometimes the phone just shows no signal rather than crashing). I also tried reflashing the kernel, but no luck. Right now I'm thinking stock ROM is my best bet.
It needs some time to get it back up working well, let the battery drain till about 10% and then charge it in one go until 100, that will probably take a short time because your battery won't accept full charge yet. Turn the phone on and reset the battery-stats in recovery, if you boot into the rom you can see the percentage, you can charge it again to 100 and repest the process, it took me about a week.
And i think there are posts about battery-issues in the MiniCM7 thread, but i'm not sure how much work still goes into that, since nAa is busy with MiniCM9 and the new kernel for ICS.
I've restored it back to original 2.1 ROM in factory restored state and thankfully the GSM/3G radios are working again. Only problem now is that Wi-Fi won't turn on, giving me an "unable to start Wi-Fi" error when I try to turn it on. Did this happen for you, SmG, in that first week of battery recovery?
kentchristopher said:
I'm hoping someone can shed some light on this problem.
I've been using my X10 Mini .........Any help or input is appreciated.
Click to expand...
Click to collapse
Well i think you are totally new to using this ROM so this issue is raised i have been using this ROM since the release.
There is no such Issue.
The actual issue that might happen (also happened in your case) is Flashing error, that means Bootloader is cracked, Kernel is flashed and rom is flashed but there was some minor glitch which got skipped and Flashing got successful, so you will have the problem even after factory resetting.
Here is what you should do Download Bootloader, kernel, ROM again. Delete old Files and use new ones to Unlock BootLoader Reflash the MiniCM Kernel and Flash The ROM, then go to recovery Wipe dalvik Cache,Battery Stats and then factory reset via recovery, after doing that everything should work fine.
also Xperia X10 Mini is not made for Tethering so if you use it you might get those problems again, try to avoid it.
if the problem persists install SEUS factory reset your mobile and update it by the SEUS or PC companion even if it says you have latest version, it will make your mobile factory reset.
I've been using CM7 since last year and 2.2.0 since its release. I have tethered before without problem though that was probably 2.1.7 and with less extensive use.
I ca say that the problem persists even though I am now back on stock 2.1 ROM. Wiped system before restore, wiped Dalvik cache, wiped battery stats, restored 2.1 and flashed stock kernel. I guess this means the problem has to be the bootloader?
As for repair with SEUS or PC Companion, I tried both and there is no way to force repair -- at least with CURRENT versions, and the versions I have won't run without an internet connection and you are forced to update. When run, both said I have the most curent version of the software on my phone and no option to repair anyway. I think this is a change from previous versions, but if you don't believe me, please try it yourself. Maybe I need to relock the bootloader?
Thanks for your input.
To follow up on this, the underlying issue seems to have been a my battery. Having just swapped out the original battery for my own self-built replacement, it seems to be working absolutely fine.
My battery life was fine before this issue. My theory right now is that the extensive tethering and internet use I was doing on the CM7 2.2.0 ROM and, most importantly, the heat that it was creating (I remember the phone getting hot) brought about a rather sudden death to my battery (heat being a known killer of battery health).
Download the battery calibration app,charge to max and leave it plugged in. Enter the app and see how many mv the battery is emitting. It should be 4200 at full charge.
Sent from my E10i using xda app-developers app
aloy99 said:
Download the battery calibration app,charge to max and leave it plugged in.
Click to expand...
Click to collapse
I assume you mean that I should do this with the old battery? Not really an option anymore since I clipped its cable to use on my new DIY replacement battery. However, back when trying to solve this problem, I did wipe the battery stats both from Battery Monitor (app) and from CWM recovery (separate occasions) and did full discharge/recharge cycles to calibrate. Obviously it didn't help, and I think it may have actually made the problem worse.
Same problem here, wifi Not working after relocking bootloader on my x10mini.
:crying:
Alright so my Vibrant won't charge. I JUST recovered my phone from a brick, (I was having issues with the battery life on Slim Roms 4.0 compared to 3.9--in the middle of flashing back I accidently wiped my internal memory. As I was recovering it using Odin, my fat cat jumped on my bed and caught on my phone cord bricking it.) Flashed using Heimdall and was able to get my phone into working order.
Now, I placed Slim Roms 4.0 back on my phone initially after the unbricking to have something working on it, even though the battery life less than impressed me.
So I charged it like normal yesterday, got it to 100% and was fine and dandy with it working. (Still sucking up battery life like a vampire in a fat camp.)
So the update 4.1 went live yesterday, I flashed it immediately to that. The battery life was amazing! So I do the normal thing when I flash to a new ROM. Let it die completely before charging it completely. It's now dead and will not charge.
Symptoms;
I plugged in my normal cable for work (a cheap cable I purchased off of Ebay.) And up comes the round loading symbol. Followed by a darkening of the screen, followed by nothing.
One thing to note, is while it has it's loading circle on, the bottom buttons light up when I touch them.
My Steps;
-I attempted different USB ports since I charge through my work computer. No luck.
-I "borrowed" my co-workers USB cord and USB to wall plug. Attempted the new cable in the computer first. No luck.
-Plugged the borrowed USB into the wall charger. Same thing happens.
-Used my own cheapy cable in wall charger. Same thing.
-Took co-workers complete set and plugged it in in a different room. Nothing.
-Took out my battery, plugged in USB, placed battery back in. Nothing.
-Hold down the Vibrant buttons to get into Bootloader, it resets the loading circle and nothing more.
So now I'm sitting here wondering what to do. I do not have rubbing alcohol readily available, however since it charged to 100% yesterday I do not believe that is the issue, but I'd be willing to try if I had access.
Something you should know, I am using a Samsung Epic 4G battery in my phone.
-For those who might judge saying it is dumb, I have gotten 54 hours out of that battery on one ROM before, that is with texting, talking on the phone and installing apps. I'm fond of this thing, however I have my stock battery at home still.-
Any suggestions you guys have would be appreciated. I have tried things that I found on this forum and basic tech support to no avail. (I am at work so the things I can use are fairly limited. However cords are of no shortage.)
Alright, I unplugged my phone from being plugged into the wall charger for an hour and 3 minutes later it decides to turn itself on.. Not sure what's going on but I'm not going to complain.
So my question now is, can anyone explain this or help prevent this in the future?
From what I've heard draining a battery until it dies can damage it. But, I'm not an expert on that. It's possible that the battery needed more time to recover from the drain.
rmelendez3 said:
From what I've heard draining a battery until it dies can damage it. But, I'm not an expert on that. It's possible that the battery needed more time to recover from the drain.
Click to expand...
Click to collapse
Really? I was always told it prolongs battery life. Now I need to research this! Thank you.
knoka said:
Really? I was always told it prolongs battery life. Now I need to research this! Thank you.
Click to expand...
Click to collapse
I had something similar happen when running lithium volt ROM. My battery completely died and the phone cut off (obviously.) I plugged it in the charger and it immediately tried to boot the phone up but it was bootlooping at the startup screen. I let it sit there for 20 minutes or so thinking maybe it is charging but as soon as i unplug the charger the phone cut off. Luckily I have an extra battery, popped it in, flashed a new ROM thinking that was the problem, turns out it was something to do with the ROM(maybe it needed a certain amount of battery power to boot up). My completely dead battery worked on the cm7 ROM I flashed, plugged in the charger and it booted up normally and started charging.
Sent from my SGH-T959 using XDA Premium App
iTz KeeFy said:
I had something similar happen when running lithium volt ROM. My battery completely died and the phone cut off (obviously.) I plugged it in the charger and it immediately tried to boot the phone up but it was bootlooping at the startup screen. I let it sit there for 20 minutes or so thinking maybe it is charging but as soon as i unplug the charger the phone cut off. Luckily I have an extra battery, popped it in, flashed a new ROM thinking that was the problem, turns out it was something to do with the ROM(maybe it needed a certain amount of battery power to boot up). My completely dead battery worked on the cm7 ROM I flashed, plugged in the charger and it booted up normally and started charging.
Sent from my SGH-T959 using XDA Premium App
Click to expand...
Click to collapse
Oh so it could be ROM related? :/ That makes sense considering I just installed a brand new ROM. Thank you!
knoka said:
Oh so it could be ROM related? :/ That makes sense considering I just installed a brand new ROM. Thank you!
Click to expand...
Click to collapse
Yea it could be ROM related but it also could be a number of other things. Hopefully flashing a new ROM will fix the issue.
Sent from my SGH-T959 using XDA Premium App
iTz KeeFy said:
Yea it could be ROM related but it also could be a number of other things. Hopefully flashing a new ROM will fix the issue.
Sent from my SGH-T959 using XDA Premium App
Click to expand...
Click to collapse
Thank you. I might just have to downgrade back to 3.9. It's almost a shame. xD
I'm going to test my old battery in this ROM just to make sure before I downgrade.
You need to use your Samsung usb charger, and wall adapter only. These two are the only ones that will actually work. I had this same problem and realized it was because I wasn't using the Samsung stuff. Even when pugging into the computer, use the Samsung USB cabe only. As for the battery your using... I wouldn't recommend it, no matter the fantastic battery life you must be getting.
whatiznt said:
You need to use your Samsung usb charger, and wall adapter only. These two are the only ones that will actually work. I had this same problem and realized it was because I wasn't using the Samsung stuff. Even when pugging into the computer, use the Samsung USB cabe only. As for the battery your using... I wouldn't recommend it, no matter the fantastic battery life you must be getting.
Click to expand...
Click to collapse
Daw it's a fellow Samsung battery.
Thank you about the cable, I need to purchase another one anyways, mine at home seems to not be connecting very well. :/
ROM. some roms do that. it will not let you power up while charging if the battery is very low. you will get the circle and the battery symbol after. sometimes you still cant unless you pull the battery. happened to me many times
My problem is kind of strange.. when I turn off the phone, it thinks it's being charged (no cable plugged in).. and i'm unable to boot the OS as per usual. The only way for me to do it is to load CWM and choose the reboot option, which does work but only with 1 battery (a spare hyperion one). The stock battery and my other hyperion aftermarket battery does not work. Instead, it takes me to the stock recovery system.
I tried remedying this problem by doing wiping battery stats, but it doesn't help any. I also decided to make the jump from unnamed ROM (gingerbread) to an ICS rom (AOKP)
On top of that, the phone no longer makes a beeping sound when i plug the cable in, but it does charge the battery.
Another thing: the boot screen (when turning phone on) shows "samsung i9100" when i'm pretty sure my phone is an i777.. i might have done something to this phone when i got it about 10 months ago, but i don't remember. All i remember was rooting the phone and flashing it to unnamed ROM.
It seems like this might be a hardware issue, but i'm no expert.
mistabeo said:
My problem is kind of strange.. when I turn off the phone, it thinks it's being charged (no cable plugged in).. and i'm unable to boot the OS as per usual. The only way for me to do it is to load CWM and choose the reboot option, which does work but only with 1 battery (a spare hyperion one). The stock battery and my other hyperion aftermarket battery does not work. Instead, it takes me to the stock recovery system.
I tried remedying this problem by doing wiping battery stats, but it doesn't help any. I also decided to make the jump from unnamed ROM (gingerbread) to an ICS rom (AOKP)
On top of that, the phone no longer makes a beeping sound when i plug the cable in, but it does charge the battery.
Another thing: the boot screen (when turning phone on) shows "samsung i9100" when i'm pretty sure my phone is an i777.. i might have done something to this phone when i got it about 10 months ago, but i don't remember. All i remember was rooting the phone and flashing it to unnamed ROM.
It seems like this might be a hardware issue, but i'm no expert.
Click to expand...
Click to collapse
I would try wiping cache and dalvik cache in cwm. Also, fix permissions in cwm. If that does nothing, I would try a different kernel. However, this may be an internal issue of the phone.
Sent from my GT-I9100 using xda premium
mistabeo said:
My problem is kind of strange.. when I turn off the phone, it thinks it's being charged (no cable plugged in).. and i'm unable to boot the OS as per usual. The only way for me to do it is to load CWM and choose the reboot option, which does work but only with 1 battery (a spare hyperion one). The stock battery and my other hyperion aftermarket battery does not work. Instead, it takes me to the stock recovery system.
I tried remedying this problem by doing wiping battery stats, but it doesn't help any. I also decided to make the jump from unnamed ROM (gingerbread) to an ICS rom (AOKP)
On top of that, the phone no longer makes a beeping sound when i plug the cable in, but it does charge the battery.
Another thing: the boot screen (when turning phone on) shows "samsung i9100" when i'm pretty sure my phone is an i777.. i might have done something to this phone when i got it about 10 months ago, but i don't remember. All i remember was rooting the phone and flashing it to unnamed ROM.
It seems like this might be a hardware issue, but i'm no expert.
Click to expand...
Click to collapse
Well you fixed your charging issue by itself It says that because the flash counter has been tripped. Just use any triangle away app from the play store.
jt.61 said:
I would try wiping cache and dalvik cache in cwm. Also, fix permissions in cwm. If that does nothing, I would try a different kernel. However, this may be an internal issue of the phone.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
i just flashed to AOKP ics rom yesterday from unnamed ROM, so i doubt it's a a kernel issue. just tried wiping cache, dalvik cache, and fixed permissions. still the same issue. im afraid of shutting the phone off or changing the batteries now, which is a pain since the new ICS rom burns battery power like crazy.
122ninjas said:
Well you fixed your charging issue by itself It says that because the flash counter has been tripped. Just use any triangle away app from the play store.
Click to expand...
Click to collapse
the flash counter isn't a big issue for me; thought i had circumvented it when i flashed the ROM 10 months ago, but i guess not. the phone still thinks it's being charged when it's turned off though. that's my main problem.
mistabeo said:
i just flashed to AOKP ics rom yesterday from unnamed ROM, so i doubt it's a a kernel issue. just tried wiping cache, dalvik cache, and fixed permissions. still the same issue. im afraid of shutting the phone off or changing the batteries now, which is a pain since the new ICS rom burns battery power like crazy.
the flash counter isn't a big issue for me; thought i had circumvented it when i flashed the ROM 10 months ago, but i guess not. the phone still thinks it's being charged when it's turned off though. that's my main problem.
Click to expand...
Click to collapse
Try to go to stock and see if the problem persists. If it does obviously a hardware issue
ultimately, if i really want to confirm, i'd probably have to do that. but i've already installed 2 different ROMs and the issue is still persistent, so i'm just going to assume it's a hardware issue. it also seems now that the phone no longer turns off. if i choose to turn it off, it'll just reboot the phone. this phone will have to last me another 9-10 months, i just hope it doesn't die out on me.
but yeah, i tried ICS for about a day and didn't like it. bad battery life, seems slower, and less user intuitive UI.. so i'm going back to gingerbread.
mistabeo said:
ultimately, if i really want to confirm, i'd probably have to do that. but i've already installed 2 different ROMs and the issue is still persistent, so i'm just going to assume it's a hardware issue. it also seems now that the phone no longer turns off. if i choose to turn it off, it'll just reboot the phone. this phone will have to last me another 9-10 months, i just hope it doesn't die out on me.
but yeah, i tried ICS for about a day and didn't like it. bad battery life, seems slower, and less user intuitive UI.. so i'm going back to gingerbread.
Click to expand...
Click to collapse
you know samsung has factory warranty for that kind of stuff.
i got my phone refurbished, about 9 or so months ago.. it only came with 3 months for the warranty. i guess getting a returned phone ended up biting me in the ass.
now the phone is overheating when im charging it.. looks like it's going to crap out on me soon.
Download the stock 2.3.4 firmware from the download repository. Do a full wipe including system data cache and dalvik. Boot into download mode hook up Odin and flash the stock firmware. If its a hardware issue your problems will persist in which case u could sell it on eBay for parts. If its a software issue that will fix it.
Sent from my SGH-I777 using xda premium
that's what i'll probably have to do tomorrow. if i remember correct, rooting the phone on 2.3.4 wasn't that straight forward, so i'd have to read up on how to do that again. but im just gonna leave it as is right now.
the phone acts really weird. when i took out the battery and replaced it with another one, it would keep doing the same thing. so then i plugged the phone into the USB charger and tried turning it on - that worked.
if it's a hardware thing, it's got to be something to do with the battery sensor. the phone is simple to remove, so i wonder if i can replace it myself.
i believe my phone is now semi-FUBAR.. it still runs, but seems like the battery sensor issue is a hardware one. i just tried doing a stock flash/odin thingy, and it still has the same issues... also, the phone is now permanently showing as MTP connected. i am also seeing decreased battery life.. only lasts about 1/2 a day now.
i guess i learned my lesson.. don't switch out the batteries too often, or your phone will die.
Another thing: the boot screen (when turning phone on) shows "samsung i9100" when i'm pretty sure my phone is an i777.. i might have done something to this phone when i got it about 10 months ago, but i don't remember. All i remember was rooting the phone and flashing it to unnamed ROM.
Click to expand...
Click to collapse
is this a big deal? i'm also having samsung i9100? im using ucle5 AJ's rom/kernel.
i'm also having issues with charging the phone. it seems to charge forever, i have to unplug and plug the charger again to properly charge it.
When it says i9100 it means you tripped the flash counter. If you want to reset it use a triangle away app.
Sent from my SGH-I777
i see thanks.
i'll try to run this app and see what will happen.
do wiping battery stat needs to be in full charged? i used to do that on my tab so i guess same principle applies.
bubuty said:
i see thanks.
i'll try to run this app and see what will happen.
do wiping battery stat needs to be in full charged? i used to do that on my tab so i guess same principle applies.
Click to expand...
Click to collapse
No the same principle does not apply. Battery state wiping has no effect on this phone.
Sent from team Pirate! Using Tapatalk 2
Hi guys,
I'm having some problems with my S2's USB port. I've been combing the forums to see if I can find something, but no luck. Let me describe the symptoms and everything I tried.
Whenever I plug my phone in, it doesn't show that it's charging, but the battery is getting filled. USB also doesn't work. Rebooting the phone with the power cable plugged in shows that the phone is charging. Doing the same with the USB only made it charge but not work in USB mode. The battery life is also crappy, as the phone never goes into deep sleep (not even with the Deep Sleep app).
First I thought that the USB board might be faulty. I exchanged that (yes, the revision matches). The problem still persisted. I then tried to reflash the device with different versions of stock ROMs (ICS and JB). Same thing. I then tried flashing the Siyah kernel. That solved a small part of it. Restarting the phone while connected to the PC will make the phone be recognized as a USB device. I also installed CM 10.1. Tried it out with the Dorimanx kernel, still nothing.
My next plans are to use the NukeROM script (tried it before, but nothing) and try fiddling with different ROMs. If anyone has any more ideas, I'd really appreciate it.
Thanks,
Tudor
tudor.timi said:
Hi guys,
I'm having some problems with my S2's USB port. I've been combing the forums to see if I can find something, but no luck. Let me describe the symptoms and everything I tried.
Whenever I plug my phone in, it doesn't show that it's charging, but the battery is getting filled. USB also doesn't work. Rebooting the phone with the power cable plugged in shows that the phone is charging. Doing the same with the USB only made it charge but not work in USB mode. The battery life is also crappy, as the phone never goes into deep sleep (not even with the Deep Sleep app).
First I thought that the USB board might be faulty. I exchanged that (yes, the revision matches). The problem still persisted. I then tried to reflash the device with different versions of stock ROMs (ICS and JB). Same thing. I then tried flashing the Siyah kernel. That solved a small part of it. Restarting the phone while connected to the PC will make the phone be recognized as a USB device. I also installed CM 10.1. Tried it out with the Dorimanx kernel, still nothing.
My next plans are to use the NukeROM script (tried it before, but nothing) and try fiddling with different ROMs. If anyone has any more ideas, I'd really appreciate it.
Thanks,
Tudor
Click to expand...
Click to collapse
Did you ever try to use another, USB cable, USB port or even computer to connect your phone? If not, try this first. It is just to make sure you are not trying to fix the problem on the wrong side of the USB cable
Oh yeah, forgot to mention. Tried multiple ports with multiple cables on multiple PCs.
Sent from my GT-I9100 using xda app-developers app
Awkward, in this case likely to be a hardware problem, but you mentioned it isnt. I never seen something like this.
Sent from my GT-I9100 using xda premium
I could live with the USB thing, but the not going to deep sleep is really a phone killer. The battery only lasts a few hours on idle.
tudor.timi said:
I could live with the USB thing, but the not going to deep sleep is really a phone killer. The battery only lasts a few hours on idle.
Click to expand...
Click to collapse
Use BetterBatteryStats then. It will help you find the problem.
over Lioyr
I've been using it (even got the paid version). Doesn't really show anything useful. Also, correct me if I'm wrong, it should show me any problematic apps I have installed. Seeing as how I've been wiping like crazy, I don't think it's an issue due to some app.
tudor.timi said:
Doesn't really show anything useful.
Click to expand...
Click to collapse
Wow... That definitely depends on the observer
tudor.timi said:
Seeing as how I've been wiping like crazy, I don't think it's an issue due to some app.
Click to expand...
Click to collapse
If you think it's a hardware issue It would probably be best to bring the phone to a Samsung repair center.
Might just buy a new phone. I just wanted to see if anybody ever had the problem before.