Phone Turns On When Charging Off..... - T-Mobile Samsung Galaxy S 4

Phone turns on when charging off? Is it a faulty battery? I haven't charged my phone while it's off for awhile now and tried just now and am realizing it turns on by itself. Took the battery out for a couple of minutes and tried again, same thing. Anyone have the same issue?

norml said:
Phone turns on when charging off? Is it a faulty battery? I haven't charged my phone while it's off for awhile now and tried just now and am realizing it turns on by itself. Took the battery out for a couple of minutes and tried again, same thing. Anyone have the same issue?
Click to expand...
Click to collapse
Are you on a GPE ROM? If so that's how it is because we don't have the right bootloader.

johnny crapple said:
Are you on a GPE ROM? If so that's how it is because we don't have the right bootloader.
Click to expand...
Click to collapse
No, I'm using Setup A in my sig. Omega v19 4.3 TW JB, on MDL bootloader. Thanks for your help and input.

norml said:
No, I'm using Setup A in my sig. Omega v19 4.3 TW JB, on MDL bootloader. Thanks for your help and input.
Click to expand...
Click to collapse
Oh sorry the SIG didn't show up on tapatalk. I've only heard of this happening on GPE ROMs.

johnny crapple said:
Oh sorry the SIG didn't show up on tapatalk. I've only heard of this happening on GPE ROMs.
Click to expand...
Click to collapse
No biggie, in my sig I have also have a Setup B which is
Setup B
Rom.........• VirginROM v3.1.2 Google Edition 4.4.2 I9505GUEUCML4
Kernel.....• KT GPE v2 Stock 4.4.2
I switch between the two with backups, but I'm on the Omega right now and it's turning on when charging. Is it normal? Thanks in advance.

norml said:
No biggie, in my sig I have also have a Setup B which is
Setup B
Rom.........• VirginROM v3.1.2 Google Edition 4.4.2 I9505GUEUCML4
Kernel.....• KT GPE v2 Stock 4.4.2
I switch between the two with backups, but I'm on the Omega right now and it's turning on when charging. Is it normal? Thanks in advance.
Click to expand...
Click to collapse
I searched the thread with keyword charging and seen someone mentioned it and they said it was kernal related, so yeah I guess its normal.

johnny crapple said:
I searched the thread with keyword charging and seen someone mentioned it and they said it was kernal related, so yeah I guess its normal.
Click to expand...
Click to collapse
Thanks Johnny Man!! I formatted data on my phone and went stock UVUAMDL, rooted with cf-auto-root just in case of OTA, lol, didn't even set up, shut it down. And it's charging, phone off. So I guess it's not hardware, that's what I was worried about. Thanks again for giving a crap, straight up, stay up Man and take it easy!!

Related

Unfortunately settings has been stopped?

What caused this error message and how do I get rid of it? When I did something related to the settings, like turning on/off airplane mode, the error message "Unfortunately Settings has been stopped" popped up and I had to click OK for it to go away. However, it did not seem to affect anything else...
It also came up right after my Note 2 finished reboot.
Anybody knows why it happened? It just happened in the last couple of days and nothing was changed.
My Note 2 is running stock JB 4.1.2, rooted with CF Autoroot.
Thank you very much in advance.
I'm sure I'm not the first one and only one who got this message. Could anybody please help?
Thank you very much!
testrider said:
What caused this error message and how do I get rid of it? When I did something related to the settings, like turning on/off airplane mode, the error message "Unfortunately Settings has been stopped" popped up and I had to click OK for it to go away. However, it did not seem to affect anything else...
It also came up right after my Note 2 finished reboot.
Anybody knows why it happened? It just happened in the last couple of days and nothing was changed.
My Note 2 is running stock JB 4.1.2, rooted with CF Autoroot.
Thank you very much in advance.
Click to expand...
Click to collapse
I don't know about stock, but flashing a custom ROM should fix it. (Try reflashing stock 4.1.2)
Smack that thanks button If I helped!
Note 2 LTE powered by Illusion ROM and Plasma Kernel.
Sent from dat small country called Singapore.
P.S. Quote my post for replies ASAP.
Irwenzhao said:
I don't know about stock, but flashing a custom ROM should fix it. (Try reflashing stock 4.1.2)
Smack that thanks button If I helped!
Note 2 LTE powered by Illusion ROM and Plasma Kernel.
Sent from dat small country called Singapore.
P.S. Quote my post for replies ASAP.
Click to expand...
Click to collapse
I don't know why flashing a custom ROM would fix it, as I did not have this before and I did not change
my ROM...
testrider said:
I don't know why flashing a custom ROM would fix it, as I did not have this before and I did not change
my ROM...
Click to expand...
Click to collapse
U could try reflashing stock rom if u don't want a custom one.
Smack that thanks button if I helped!
Note 2 LTE powered by Illusion ROM and Plasma Kernel.
Sent from dat small country called Singapore.
P.S. replies with quotes will be replied to faster.
testrider said:
What caused this error message and how do I get rid of it? When I did something related to the settings, like turning on/off airplane mode, the error message "Unfortunately Settings has been stopped" popped up and I had to click OK for it to go away. However, it did not seem to affect anything else...
It also came up right after my Note 2 finished reboot.
Anybody knows why it happened? It just happened in the last couple of days and nothing was changed.
My Note 2 is running stock JB 4.1.2, rooted with CF Autoroot.
Thank you very much in advance.
Click to expand...
Click to collapse
I would just re-flash a stock rom. Maybe stock+root. Sorry I've rooted many times and never had that issue on a stock rom.
0.o said:
I would just re-flash a stock rom. Maybe stock+root. Sorry I've rooted many times and never had that issue on a stock rom.
Click to expand...
Click to collapse
Thanks for the reply. It'll be great if I can find out why then I can fix the root cause. We really don't want every time we have a problem we just do factory reset/wipe all/reflash and pray for the best?
It really seemed that there was no answer. I googled it and saw lots of people having the same problem but no solution.
I may have to flash the stock rom but I don't think that will fix the problem. Mine is running a stock ROM
testrider said:
Thanks for the reply. It'll be great if I can find out why then I can fix the root cause. We really don't want every time we have a problem we just do factory reset/wipe all/reflash and pray for the best?
It really seemed that there was no answer. I googled it and saw lots of people having the same problem but no solution.
I may have to flash the stock rom but I don't think that will fix the problem. Mine is running a stock ROM
Click to expand...
Click to collapse
The only way to get to the root problem is run a logcat of the error. We could guess all day long. I mean did you freeze anything, delete anything, flash a mod, use an xposed module? There are hundreds of things that could be wrong, but without a logcat it would take a long time to guess your specific error.
Sent from my SGH-T889 using xda app-developers app
kintwofan said:
The only way to get to the root problem is run a logcat of the error. We could guess all day long. I mean did you freeze anything, delete anything, flash a mod, use an xposed module? There are hundreds of things that could be wrong, but without a logcat it would take a long time to guess your specific error.
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Thanks. I'll remember to get a logcat next time. Right after the message popped up, correct?
testrider said:
Thanks. I'll remember to get a logcat next time. Right after the message popped up, correct?
Click to expand...
Click to collapse
Yep right after it happens. If there is something that triggers it. Reboot, to clear the log, then trigger the fc and pull log
Sent from my SGH-T889 using xda app-developers app

Constantly losing cell service

This problem suddenly came out of nowhere.
I've had the same rom (paranoid android 3.99 RC2) running on my phone for 6 months and everything works perfectly until one day as I'm driving home the GPS goes wonky.
I restart my phone and then boom, no cell service on my phone.
I tried to:
wipe cache, dalvik
shutdown and reboot multiple times,
install a fresh copy of the rom,
tried other roms,
made sure i wiped system and storage when flashing new rom,
and tried to insert, reinsert sim card multiple times.
Strangely enough when this problem happens, the home button laso seems to act like its unlocking the device...
What do you guys think?
I'm thinking maybe I got some water on my device and ended up having it seep into the home button and the back of the device.
Sounds like a modem issue, might just need updating to the latest for you device...
Sent from my SAMSUNG-SGH-I317 using Tapatalk
MiuKing said:
This problem suddenly came out of nowhere.
I've had the same rom (paranoid android 3.99 RC2) running on my phone for 6 months and everything works perfectly until one day as I'm driving home the GPS goes wonky.
I restart my phone and then boom, no cell service on my phone.
I tried to:
wipe cache, dalvik
shutdown and reboot multiple times,
install a fresh copy of the rom,
tried other roms,
made sure i wiped system and storage when flashing new rom,
and tried to insert, reinsert sim card multiple times.
Strangely enough when this problem happens, the home button laso seems to act like its unlocking the device...
What do you guys think?
I'm thinking maybe I got some water on my device and ended up having it seep into the home button and the back of the device.
Click to expand...
Click to collapse
Agree with the updating modem?
Have you popped open the phone and checked the water indicators ? Check for water invasion, that would answer whether it's a factor or not.
dicksteele said:
Agree with the updating modem?
Have you popped open the phone and checked the water indicators ? Check for water invasion, that would answer whether it's a factor or not.
Click to expand...
Click to collapse
I flashed to the stock rom and unrooted, which flashed the UCALJ2 Modem. It's working fine now on Paranoid 3.60.
I downgraded to that one since I never had any troubles with that rom, I kinda liked that version anyway,
but if I get any issues I will post here again.
MiuKing said:
I flashed to the stock rom and unrooted, which flashed the UCALJ2 Modem. It's working fine now on Paranoid 3.60.
I downgraded to that one since I never had any troubles with that rom, I kinda liked that version anyway,
but if I get any issues I will post here again.
Click to expand...
Click to collapse
Good deal.. I didn't mean to have a ? after Agree with flashing modem......
BTW, Baja has a great thread here....
http://forum.xda-developers.com/showthread.php?t=1987541
It has just the flashable modem zip's in there also.
dicksteele said:
Good deal.. I didn't mean to have a ? after Agree with flashing modem......
BTW, Baja has a great thread here....
http://forum.xda-developers.com/showthread.php?t=1987541
It has just the flashable modem zip's in there also.
Click to expand...
Click to collapse
That thread doesn't get updated often these days,
I317UCAMH3 , is the latest right?
MiuKing said:
That thread doesn't get updated often these days,
I317UCAMH3 , is the latest right?
Click to expand...
Click to collapse
That part is. MK6 is latest from ATT 4.3 OTA
Sent from my GT-N7105 using XDA Premium 4 mobile app
MiuKing said:
That thread doesn't get updated often these days,
I317UCAMH3 , is the latest right?
Click to expand...
Click to collapse
That's possibly because I have a lot going on. And I try my best to have it UPDATED with the latest stuff.
You wanna know when the last time I updated, then look at the top of the OP page. Updated yesterday btw
Modems are updated to the latest one....
dicksteele said:
That part is. MK6 is latest from ATT 4.3 OTA
Sent from my GT-N7105 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
+1:thumbup:
Sometimes we all ASSUME
Sent from my SAMSUNG-SGH-I317 using Tapatalk

broken wifi

ok im flashing back to touch wiz from a miui rom and my wifi seems to be broken..it doesnt matter what touch wiz rom it is ive even gone full stock. wifi turns on connects the hot boots? i think the word is . it goes to the logo and then starts back with the wifi turned off any suggestions?
im really trying to go back to hyper rom its what i had before miui and i wish i woulda never left......srry hyper rom gods forgive me!:crying:
Hrlmbtz said:
ok im flashing back to touch wiz from a miui rom and my wifi seems to be broken..it doesnt matter what touch wiz rom it is ive even gone full stock. wifi turns on connects the hot boots? i think the word is . it goes to the logo and then starts back with the wifi turned off any suggestions?
im really trying to go back to hyper rom its what i had before miui and i wish i woulda never left......srry hyper rom gods forgive me!:crying:
Click to expand...
Click to collapse
20 views and nothing?! i might have to go back to miui smh i use wifi on a daily this is a killer
Hrlmbtz said:
20 views and nothing?! i might have to go back to miui smh i use wifi on a daily this is a killer
Click to expand...
Click to collapse
if this is anything like the S3 was, then the bootloader must match the radio. Make sure you are on the latest. Not much I can go on since I am new to the Note 3.
Chr0nicDreamz said:
if this is anything like the S3 was, then the bootloader must match the radio. Make sure you are on the latest. Not much I can go on since I am new to the Note 3.
Click to expand...
Click to collapse
ima check and see if those match...i hope i can get this fixed
thanks for the reply
Chr0nicDreamz said:
if this is anything like the S3 was, then the bootloader must match the radio. Make sure you are on the latest. Not much I can go on since I am new to the Note 3.
Click to expand...
Click to collapse
Hrlmbtz said:
ima check and see if those match...i hope i can get this fixed
thanks for the reply
Click to expand...
Click to collapse
ok bootloader nk3 baseband nk3 but pda is nf9 and csc is nf9 should i flash down to nf9?
Hrlmbtz said:
ok bootloader nk3 baseband nk3 but pda is nf9 and csc is nf9 should i flash down to nf9?
Click to expand...
Click to collapse
F9 all the way through still loops ..guess im going back to miui
not that anyone seems to care but
Hrlmbtz said:
F9 all the way through still loops ..guess im going back to miui
Click to expand...
Click to collapse
i flashed jedi elite wich is a nb4 rom and everything works fine i dont get it every thing at the moment is nk3 other than pda and csc which displat nb4 anything else seems to crash on wifi any idea what the issue could be? if i flash say an older version of hyper rom and update on through should it work?

Sammobile SM-G925T Android 7 Firmware

Hooray....It's up and posted. Just Downloaded
Here fast download link for all: https://www.androidfilehost.com/?fid=889764386195905698
Docmjldds said:
Hooray....It's up and posted. Just Downloaded
Click to expand...
Click to collapse
Can I root after this update
dunbar28205 said:
Can I root after this update
Click to expand...
Click to collapse
Yes. Just reinstall TWRP from ODIN, then Magisk or SU.
Docmjldds said:
Hooray....It's up and posted. Just Downloaded
Click to expand...
Click to collapse
Docmjldds said:
Yes. Just reinstall TWRP from ODIN, then Magisk or SU.
Click to expand...
Click to collapse
Yes!Thank you
dunbar28205 said:
Yes!Thank you
Click to expand...
Click to collapse
So far everything running really snappy. Did the *#0228# battery reset suggestion and initially my Battery went from 100% to 82%. Really a large recalibrate. Let it charge up from powered off state and it took two hours to get it back to 100% which was rather slow, but then again, proof will be running now to see how it fairs vs MM.
BTW...sorry for thread drift here Will respect thread etiquette in future.
EDIT: my bad...just realized this was in the TMob section
Docmjldds said:
So far everything running really snappy. Did the *#0228# battery reset suggestion and initially my Battery went from 100% to 82%. Really a large recalibrate. Let it charge up from powered off state and it took two hours to get it back to 100% which was rather slow, but then again, proof will be running now to see how it fairs vs MM.
BTW...sorry for thread drift here Will respect thread etiquette in future.
EDIT: my bad...just realized this was in the TMob section
Click to expand...
Click to collapse
ok will do
dunbar28205 said:
ok will do
Click to expand...
Click to collapse
Battery looks great so far. Reading 99% now after 1 hour 15 min idle. Says 33H left. Can't complain. CPU Plus showing Deep Sleep at 74% too.
dunbar28205 said:
ok will do
Click to expand...
Click to collapse
im stuck on the t mobile splash screen
dunbar28205 said:
im stuck on the t mobile splash screen
Click to expand...
Click to collapse
nevermind lol
dunbar28205 said:
nevermind lol
Click to expand...
Click to collapse
LOL.... I only dropped 5 % battery overnight. Have 15 hours now and show 94%. Today will be a good test since I am out and about all day. I decided to NOT charge it overnight to see how it will go today.
When rooting should I just flash the regular Magisk V12 zip for systemless?
ketwi15 said:
When rooting should I just flash the regular Magisk V12 zip for systemless?
Click to expand...
Click to collapse
Yes....
How long were you guys stuck at the splash screen? After flashing Magisk I've been stuck on T-mobile splash screen for about 20 mins.
Thanks
Thanks
ketwi15 said:
How long were you guys stuck at the splash screen? After flashing Magisk I've been stuck on T-mobile splash screen for about 20 mins.
Click to expand...
Click to collapse
Did you first install the stock firmware and setup NON rooted. Start over with a clean wipe using TWRP which will of course reinstall stock recovery. Set your phone up. Reinstall TWRP. then flash magisk. Only 5 min or so of the TMobile splash for me.
Got it working.
Received the 7.0 update OTA today. Just throwing it out there.
kpeezy said:
Received the 7.0 update OTA today. Just throwing it out there.
Click to expand...
Click to collapse
One advantage of NOT being rooted
Has anyone figured out how to get Viper for this?

Turns on automatically as soon as connected to charger...

Hey, I just bought a z2 plus and unlocked bootloader and started messing around. I installed viper rom and was going good but when I turned my cell down and connected it to charge, it starts itself. I tried a lot but no help. Finally I thought it maybe something to do with the rom so I flashed AOSP extended and now the same problem . I am just not able to make my cell charge while being switched off; it keeps on restarting. I don't think I was having this problem on stock rom as I used to put my cell on charge but turning it off at night. If anyone can help me with this it would be great..
Prince Mohit said:
it keeps on restarting
Click to expand...
Click to collapse
on every custom ROM and you will not face with
Prince Mohit said:
this problem on stock rom
Click to expand...
Click to collapse
sergsinger said:
on every custom ROM and you will not face with
Click to expand...
Click to collapse
Isn't there any workaround to solve this.. I want to charge my phone while it's off..
Prince Mohit said:
Is there any workaround to solve this
Click to expand...
Click to collapse
Don't know.
Short answer - no

Categories

Resources