Related
simply said. my phone still reboots
using cm7 2.3.3 #12 and this bastard still reboots.
anyone else?
no.. wrong section
try wiping dalvik/cache/factory
No reboots over here.
Sent from my Nexus S
dudeimgeorge said:
simply said. my phone still reboots
using cm7 2.3.3 #12 and this bastard still reboots.
anyone else?
Click to expand...
Click to collapse
what kernel? And if you're going to ***** about problems with 2.3.3 you should run fully stock to make sure some customization is causing the issue.
Never once had a random reboot related to a call. Why do people tend to only pay attention to half of a bugfix and never specify whether their "problem" is related to it and then post it the completely wrong section about the problem without searching for the older threads relating to their issue?
I encountered this problem too, just 3 hours ago; the first after upgrading to 2.3.3 since Thursday.
Stock (but deodexed) 2.3.3, rooted, dalvik,cache-wiped.
EDIT: And oh, it's not a reboot bug -- it was a shutdown bug for me. Wasn't on a call, phone was just on stand by in my pocket, while my wife and I watched Voyage de la Vie. After the show, phone was dead, power button not working. I had to remove the batteries to jack it up again.
I guess I would be wiping my phone again, oh man that sucks.
But in the end, I still love my Nexus S.
kenvan19 said:
Never once had a random reboot related to a call. Why do people tend to only pay attention to half of a bugfix and never specify whether their "problem" is related to it and then post it the completely wrong section about the problem without searching for the older threads relating to their issue?
Click to expand...
Click to collapse
People don't understand. They just see "reboot bug" and anytime they get a reboot it's "that bug".
Highland3r said:
People don't understand. They just see "reboot bug" and anytime they get a reboot it's "that bug".
Click to expand...
Click to collapse
My G2 (pure stock) rebooted once in a while. In fact I watched it happen while i was in a meeting there day before I got the nexus s. It must be the same bug!
nexus s has not reboot once, though ill give it time its only been three days.
Sent from my Nexus S using Tapatalk
On CM7 build 12 with netarchy 1.2.7... it rebooted once sitting on the desk doing nothing lol. Haven't had a reboot since but it's only been a day. Battery life seems pretty good but 3D performance took a hit on 2.3.3 =\
dinan said:
On CM7 build 12 with netarchy 1.2.7... it rebooted once sitting on the desk doing nothing lol. Haven't had a reboot since but it's only been a day. Battery life seems pretty good but 3D performance took a hit on 2.3.3 =\
Click to expand...
Click to collapse
is this from benchmarks or are you seeing real world performance decrease? I am not trusting benchmarks as my g2 performed better in quadrant, yet real world the ns feels much faster.
Sent from my Nexus S using Tapatalk
Both. Benchmarks are lower and also when playing games like dungeon defenders its noticeably slower than before.
Sent from my Nexus S using XDA App
dinan said:
Both. Benchmarks are lower and also when playing games like dungeon defenders its noticeably slower than before.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
That's strange, the ns has a good gpu..
Sent from my Nexus S using Tapatalk
I'm not saying it's bad, I'm saying the performance is worse than when I was on a 2.3.2 CM7 with the SAME PHONE. Not sure what comparing GPU's has to do with this.
Anyway, just had a reboot while trying to do the pattern unlock to wake my phone. It booted with a little "Safe Mode" thing at the bottom left, never seen that before. Then shortly after that it promptly rebooted itself again and it's back to normal CM7, but all my widgets mysteriously vanished from my home screen... great.
[hfm] said:
That's strange, the ns has a good gpu..
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
dinan said:
I'm not saying it's bad, I'm saying the performance is worse than when I was on a 2.3.2 CM7 with the SAME PHONE. Not sure what comparing GPU's has to do with this.
Click to expand...
Click to collapse
True, that was just my impression switching phones. I suppose it was a stability/compatability play as I hope they wouldn't unknowingly release a build with an unknown gross performance deficiency in the display driver.
Sent from my Nexus S using Tapatalk
prior to 2.3.3 my phone rebooted while in stand by on a daily basis and just once while on a call. i haven't noticed it after 2.3.3, but i'm not holding my breath just yet. i hope it's fixed.
cygnum said:
I encountered this problem too, just 3 hours ago; the first after upgrading to 2.3.3 since Thursday.
Stock (but deodexed) 2.3.3, rooted, dalvik,cache-wiped.
EDIT: And oh, it's not a reboot bug -- it was a shutdown bug for me. Wasn't on a call, phone was just on stand by in my pocket, while my wife and I watched Voyage de la Vie. After the show, phone was dead, power button not working. I had to remove the batteries to jack it up again.
I guess I would be wiping my phone again, oh man that sucks.
But in the end, I still love my Nexus S.
Click to expand...
Click to collapse
My phone is doing the exact same thing.
On 2.3.2, CM7 nightly 2.3.3, and stock 2.3.3.
Wiped or not. Rooted or not. Same damn reboot/shutoff.
It just reboot/shutoff with screen off, and hangs dead there sometimes with LED lights on. Have to remove battery to boot. Sometimes takes a dozen time battery removal to get it pass bootloader.
I am fed up. Now I am using wiped non-root 2.3.3 with a broken CMR, and still reboots!
I am going to flash the stock Recovery back and lock the bootloader before sending back to Samsung for replacement.
But seriously, what would you recommend as my next phone. I am thinking about Tbolt or Atrix.
rocketragz said:
prior to 2.3.3 my phone rebooted while in stand by on a daily basis and just once while on a call. i haven't noticed it after 2.3.3, but i'm not holding my breath just yet. i hope it's fixed.
Click to expand...
Click to collapse
It's not.
I have 2 Nexus S, both of them have spontaneously rebooted on 2.3.3.
It was much worse on 2.3.2, though.
Both are stock, not even rooted. Even most of the apps are different (my wife uses very few).
delete....
dudeimgeorge said:
simply said. my phone still reboots
using cm7 2.3.3 #12 and this bastard still reboots.
anyone else?
Click to expand...
Click to collapse
You do realize the "reboot" bug has nothing to do with just rebooting right? It has to do with rebooting while DURING a call. Also You're running CM7, so any random reboots is an issue with CM7 itself. It's still buggy as heck.
And ummm actually for me. Build 11/12 has been strong, not a single reboot. Used to have random soft-reboots, soft-reboot loops, and can't unwake the phone. All needing battery pulls. Haven't had a single random reboot with CM7 build 12.
nxt said:
You do realize the "reboot" bug has nothing to do with just rebooting right? It has to do with rebooting while DURING a call....
Click to expand...
Click to collapse
Except that it's happening to way too many of us, NOT during a call. I call that a "reboot" bug.
My phones are stock.
im not sure when this started but it seems like every rom, every kernal i use now my phone will close apps to a black screen and freeze up for different lengths of time. was doing it in stock, and now a custom rom. tried different kernals... seems to be worse when the phone first boots up. its almost like a force close but slower and i don't get the force close message. help
Edit: ok i brought up the ram manager and my ram would start around 250 and climb up before my eyes until the screen blacks out.... how do i figure out what is eating up the ram.. and why does it stop?
murso74 said:
im not sure when this started but it seems like every rom, every kernal i use now my phone will close apps to a black screen and freeze up for different lengths of time. was doing it in stock, and now a custom rom. tried different kernals... seems to be worse when the phone first boots up. its almost like a force close but slower and i don't get the force close message. help
Click to expand...
Click to collapse
I assume you already tried Odin to clear out any crap left right?
Sent from my SPH-D700 using XDA Premium App
JohnCorleone said:
I assume you already tried Odin to clear out any crap left right?
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
yeah odined to stock ec05 and it was just as bad. rebooting the phone actually made it worse... seemed like it took forever for everythign to stabilize. phone also seems to get hot but i could be wrong about that. not the battery but above the battery near the camera
Quite often this is caused by restoring old data over a new rom using a program like titanium backup. Sometimes you can get away with it between similar roms but restoring Froyo data on to a gingerbread rom will almost always cause lots of FCs.
poit said:
Quite often this is caused by restoring old data over a new rom using a program like titanium backup. Sometimes you can get away with it between similar roms but restoring Froyo data on to a gingerbread rom will almost always cause lots of FCs.
Click to expand...
Click to collapse
i never restore data from nandroid backups and i reinstall all my apps from the market...
maybe my phone is tired
modem seems to be resetting alot too
murso74 said:
yeah odined to stock ec05 and it was just as bad. rebooting the phone actually made it worse... seemed like it took forever for everythign to stabilize. phone also seems to get hot but i could be wrong about that. not the battery but above the battery near the camera
Click to expand...
Click to collapse
Isn't the spot right above the battery where the chip is located? Have you been overclocking your phone like I have at 1400 everyday? I was wondering if I have been flashing too much. I saw some of these issues myself. Odin started freezing as well but it seems to have smoothed out. I thought I may have wiped out my phone
Sent from my SPH-D700 using XDA Premium App
JohnCorleone said:
Isn't the spot right above the battery where the chip is located? Have you been overclocking your phone like I have at 1400 everyday? I was wondering if I have been flashing too much. I saw some of these issues myself. Odin started freezing as well but it seems to have smoothed out. I thought I may have wiped out my phone
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
no.... set at concervitive 200 - 1000. but i was using drockstars kernal before this without using a governer and it was still doing it. now i'm using TZ 1.1.1
it is that spot.. but its not hot there all the time either. very annoying issue
murso74 said:
no.... set at concervitive 200 - 1000. but i was using drockstars kernal before this without using a governer and it was still doing it. now i'm using TZ 1.1.1
it is that spot.. but its not hot there all the time either. very annoying issue
Click to expand...
Click to collapse
Ummm, I am kind of at a loss here. You don't have any physical damage to your phone? No serious drops? You didn't go swimming with it in your pocket? But seriously, I run at 1400/100 on demand all of the time and that spot gets hot on Gingerbread ROMs but not on Froyo unless I run a lot of video at 1400 max.
Sent from my SPH-D700 using Tapatalk
JohnCorleone said:
Ummm, I am kind of at a loss here. You don't have any physical damage to your phone? No serious drops? You didn't go swimming with it in your pocket? But seriously, I run at 1400/100 on demand all of the time and that spot gets hot on Gingerbread ROMs but not on Froyo unless I run a lot of video at 1400 max.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
yeah i don't know what to think either. i guess when official gb finally drops i'll try one last clean install and if it keeps doing it i'm going to have to go through insurance
murso74 said:
yeah i don't know what to think either. i guess when official gb finally drops i'll try one last clean install and if it keeps doing it i'm going to have to go through insurance
Click to expand...
Click to collapse
When did you purchase your phone? did this start to happen after you started loading custom ROMs or since the start?
What is your current setup right now? Do you use RFS or EXT4?
What hacks have you loaded to your phone, and after what even that you performed on the phone did you start experiencing this issues?
megabiteg said:
When did you purchase your phone? did this start to happen after you started loading custom ROMs or since the start?
What is your current setup right now? Do you use RFS or EXT4?
What hacks have you loaded to your phone, and after what even that you performed on the phone did you start experiencing this issues?
Click to expand...
Click to collapse
i've had the phone for a year. i've been doign roms for at least 6 months.. this only started in the last month on both rfs and ext4. i don't know what i did that could have done this.. honestly i started noticing it when i odined back to EC05 a few weeks ago. then i did an rfs rom, then drockstars kernal, now srf 1.2 and tz kernal. just seems to be getting worse and worse. to be honest it may have started after i flashed back from eh22
Are you on TW4 Launcher? That can cause phone to freeze.
Overstew said:
Are you on TW4 Launcher? That can cause phone to freeze.
Click to expand...
Click to collapse
i am actually.... although this started before the tw4 launcher. i guess i'll remove it for a while and see what happens. dammit i liked the tw4 launcher too
Don't use any CPU programs like setcpu, etc.. if not try wiping your sd card. Could just be your phone too.
Sent from my SPH-D700 using Tapatalk
I had this issue for a while and it caused me to leave to the iPhone, but now after months of waiting I am trying to bring my epic back
I will post my results I am going to try flashing back to stock and see it if can stay on for a day with out crashing....I'll be back with results in a day or 2
Mine does the same thing and it shuts off sometimes at 35% battery left. Just in the past month. Im stock not rooted. One more thing somedays i get 13 hrs of life and others like 6, same usage everyday and same area so service isnt the issue.
Sent from my SPH-D700 using XDA App
I had this same issue. I was to a point of chamging phones.
I decided to watch 5 different tutorials/youtibe videos on how to odin back to stock.
In that process, 3 of the videos had different options checked. Yes, I decided to try each way, restoring apps/data from Titanium, each time.
After the first 2 attempts, and still seeing the freezes, I started to get some kind of com.google.apps process force close errors.
I was really ready to beat my phone up at this point.
So, after deciding, I've had enough, I said I would do it ONE more time. (There was still one more checkbox that another video was showing...)
Sent from my SPH-D700 using XDA Premium App
Sry, my fat fingers pressed submit.
Anyhow, Ive 0 programming experience so, all of this might kust be a lucky fluke. When I odin'd, I checked all three options. Re-Partition, Autoreboot, And F. Reset Time.
Only 1 video of the 4 I watched said to do this.
I then restored my apps and data back w/ Titanium.
I did make sure that any data from OEM apps, was not broight back, as a precaitonary on my part. It was really driving me nuts. Hope this helps....
Sent from my SPH-D700 using XDA Premium App
crap well it wasn't TW4... uninstalled it last night. today rebooted and same thing.... its so strange it only happens the most after i reboot the phone. black screen with the status bar up top. if i touch the screen the button lights will come on ... if i swipe down the status bar it will eventually come down.. but with a ton of lag
i guess i'll nandroid backup and start from scratch with odin again. bone stock no root see what happens.
EDIT: just noticed that the modem seems to reset every time it does this. didn't see that before cause it doesn't always make the no signal sound. but the bars on the status screen go dark and the little x pops up above them before the home screen redraws. so basically whatever i'm doing goes to black screen.. times out for 10 min with just the bar on top, modem resets and goes back to the home screen
ok i brought up the ram manager and my ram would start around 250 and climb up before my eyes until the screen blacks out.... how do i figure out what is eating up the ram.. and why does it stop?
man this is nuts... i've got android system info running and i'm watching the processes tab... all the programs start usign memory, then android starts killing them off until they are almost all gone then i go to black screen... i dont' know what the hell is going on
edit: tasks is showing android.process.acore twice, package com.fede.launcher. both are using 34.89 MB and have cpu at 100... however total CPU usage is only showing 7%
Hello everyone...
I have 2 issues with my Transformer
the first one is that whenever i leave my Transformer for couple hours it shuts down !! doesn't occur when charging but it does when it's not.. even when the battery is around 80% !! i had this problem with ALL kernels except the stock kernel which i don't wanna use !! also had this problem for around 2 months...
the second one happened today when i left my Transformer "Charged" at 100%.. and after couple of hours i found it shut down but when i powered it on again i found the battery 27% !!
i went to the battery stats and found that battery was decreasing slowly and there was a gap (which means that it turned off) and after the gap it shows the battery low !! it happened within 6 hours !!
Please help me if you can... !! I'm using Revolver ROM 3.9.5 and "Blades Kernel 3" that comes in the Revolver Parts...
UPDATE : The problem occurs with the stock kernel !!
This sounds very familiar to the problem I had with my Galaxy S2 a month ago.
It kept shutting down every few hours, and it was driving me mad. Then one day I uninstalled the app greenpower, and it was fine afterwards. You don't have the greenpower app by any chance? If not, maybe it can be caused by some other app you normally use?
The battery might be hosed. Have you ever let it hit 0 before? A lot of batteries never fully recover after being fully depleted once or twice.
Cernunnoz said:
This sounds very familiar to the problem I had with my Galaxy S2 a month ago.
It kept shutting down every few hours, and it was driving me mad. Then one day I uninstalled the app greenpower, and it was fine afterwards. You don't have the greenpower app by any chance? If not, maybe it can be caused by some other app you normally use?
Click to expand...
Click to collapse
I never heard of this app... Just like i said it doesn't happen with the stock kernel !!
But the reason I'm using other kernels is because i wanna Overclock !!
a.mcdear said:
The battery might be hosed. Have you ever let it hit 0 before? A lot of batteries never fully recover after being fully depleted once or twice.
Click to expand...
Click to collapse
No i never let it hit 0%... but i don't think that the problem is in the battery
However I'll try it and see what happens !
sounds like a silly question but i have seen it alot. Are you charging through a computer(USB) or wall?
It could be related to setCPU and the according profiles. Just recently I saw that my profiles were messed up after updating ROM and kernel. Might be worth a shot.
Reinstall stock kernel Issue #1 fixed.
Issue 2 sounds like charger shut off and left TF on not charging.
You've pretty much explained to yourself why the thing is shutting down.. It works fine on the stock kernel but not one that is letting you overclock.. Sounds to me like you are either overclocking more than it can handle or undervolting to much or both.
I can almost bet that its not shutting down completely and its just going into a state that the screen is off but the OS is hung up, so its not responding to you turning the screen on.. This would explain why the battery seems to be dieing when its sitting idle.
Not sure about it dieing while its plugged in other than maybe a fluke.
I don't wanna use the stock kernel.. it's really slow !!
and i over clock to 1.4 ghz only since i can't overclock more than that because it restarts itself endlessly if i overclocked more than 1.4 ghz !! i undervolted about -25 or -50.. not much !!
Yes i charge it on a wall or anything but NOT on my computer...
How can i change profiles in setcpu ??
xMini said:
No i never let it hit 0%... but i don't think that the problem is in the battery
However I'll try it and see what happens !
Click to expand...
Click to collapse
No no you misunderstood! DONT let the battery hit 0.
First, you need to use more exclamation points !!!!
sounds like you are suffering from deep sleep issues. What rom are you running? also, have you tried running a custom kernel and not overclock it? You have several variables that can be influencing your issues, start isolating what may be causing your problems. the kernel seems the must likely of culprits, I would clear the overclock and install setcpu and run it for a but and see if you can replicate your issue.
Sent from my GT-I9000 using XDA App
Just try the non stock kernel, oc it but dont uv it, not all devices can handle uv, even if it is only a little bit. Even take it back too 1000mhz and try to increase the uv and oc by little bits at a time to see exactly what your transformer can handle. I think its the uv thats causing the problems. Experiment a bit and youll find the sweet spot.
I'm using Revolver ROM and i mentioned that...
I've never undervolted till yestersay.. maybe it caused the second problem
I set the clock speed at 1ghz and i'm waiting to see if anything changes..
Yeah... the problem still occurs even after setting the clock speed at 1ghz and default voltage !! using clemsyn kernel ver 22...
Every device is different. Differences in manufacturing etc. You might have a picky device. Plus these are mobile platforms. No fans, just convection cooling. They are not meant to be tweaked and oc'ed they way we do. The stock kernel is very fast. What is it that you cannot do on the stock kernel that the extreme oc let's you do?
Sent from my DROID X2 using Tapatalk
colonel187 said:
Every device is different. Differences in manufacturing etc. You might have a picky device. Plus these are mobile platforms. No fans, just convection cooling. They are not meant to be tweaked and oc'ed they way we do. The stock kernel is very fast. What is it that you cannot do on the stock kernel that the extreme oc let's you do?
Sent from my DROID X2 using Tapatalk
Click to expand...
Click to collapse
I'm guessing my device is bad and it's Asus' problem ! i tried setting the clock speed at normal 1Ghz but the problem still occurs !! the reason i overclock is that because with the stock kernel i get slower web browsing and slower flash playback and slower overall performance!! however I'm back on the stock kernel to check out if the problem is gone or not...
I doubted my device couple months ago... because I've seen everyone overclock their devices at 1.6 GHz Without any issues !! but when i try to overclock a little bit more than 1.4 GHz it restarts itself endlessly !!
Had the same issue a few months ago. Be prepared to wake up to a dead TF.
I sent it back to ASUS and they replaced main board and battery. Under warranty of course. I suggest you unroot and use a stock rom for now.
Sent from my GT-I9100 using XDA App
ropaisoft said:
Had the same issue a few months ago. Be prepared to wake up to a dead TF.
I sent it back to ASUS and they replaced main board and battery. Under warranty of course. I suggest you unroot and use a stock rom for now.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
What do you exactly mean by "for now" ??
and how can i even send it to ASUS ??! i don't live in the USA
xMini said:
I'm guessing my device is bad and it's Asus' problem !!!
Click to expand...
Click to collapse
You stated in an earlier post that the problem does not show up in the stock ASUS setup, but only with a custom ROM and Kernel. How does that make it ASUS' problem. If you buy a car that says it runs on 87 octane fuel and you put 100% nitro methane in the tank and it blows up it is not the manufacturers fault.
i just noticed this morning after unplugging my note that even though my note is going into deep sleep the battery drain is still way too much as compared to the previous day...
i checked cpuspy and at first didn't register anything odd except that it goes into deep sleep.. after a second glance only then i realized that instead of running at 200mhz my note was running at 1000mhz during charge..
has anyone here experienced this before?? although i noticed that it seems to be a lot snappier now
i just can't help but worry what lasting damage it may be doing to the processor... and the fact that even though it goes into deep sleep i'm losing about 5% of juice for every 15-20 mins.
see screenshots below. the first was when i unplugged it from the charger and the second... after going to deep sleep
see screenshots
sorry forgot to attach screenshots
scarlet_sg said:
i just noticed this morning after unplugging my note that even though my note is going into deep sleep the battery drain is still way too much as compared to the previous day...
i checked cpuspy and at first didn't register anything odd except that it goes into deep sleep.. after a second glance only then i realized that instead of running at 200mhz my note was running at 1000mhz during charge..
has anyone here experienced this before?? although i noticed that it seems to be a lot snappier now
i just can't help but worry what lasting damage it may be doing to the processor... and the fact that even though it goes into deep sleep i'm losing about 5% of juice for every 15-20 mins.
see screenshots below. the first was when i unplugged it from the charger and the second... after going to deep sleep
Click to expand...
Click to collapse
Try restarting and see it is softens up
Sent from my GT-N7000 using xda premium
tried it... even did a hard reset by pulling battery out... still the same...
now clueless on what next...
See what processes are running. And kill some unneccessary ones?
Sent from my GT-N7000 using XDA
scarlet_sg said:
tried it... even did a hard reset by pulling battery out... still the same...
now clueless on what next...
Click to expand...
Click to collapse
ANy new apps that u installed recently ?
Normally , rogue process is going to call an abnormal battery drain ,,,download some sort of process,app moniter and see which process is running and taking most of the CPU time......My guess is that it has to be one of the apps that you have installed or started which is causing this
That was what I thought initially but I don't remember installing anything these past few days as I just froze a few bloatware and was monitoring the device for any issues.
The last thing I remember changing was some setting under the development concerning background process.
Hmmmn. Maybe I'll put it back and see.
Really appreciate the help guys. I'll keep you updated.
Sent from my GT-N7000 using XDA
Kernel and rom version pleeez
Sent from my GT-N7000 using Tapatalk 2
scarlet_sg said:
The last thing I remember changing was some setting under the development concerning background process.
Hmmmn. Maybe I'll put it back and see.
Click to expand...
Click to collapse
this may be the reason - afair this setting kills each process after you leave it, so in readily you might have ended with a constant loop of processes being closed and then restarted by system
Sent from my GT-N7000 using xda premium
i unchecked the limiting of background process but still the same... cpu is still running at 1000mhz most of the time
i did a hard reset by turning off and pulling the battery for a few minutes... still the same although the note still goes into deep sleep but hardly uses other cpu speeds except for 1000mhz...
i tried freezing some of my apps and games, those which i suspect might have required 1000mhz to run but still the same...
i guess i'll just have to wait and see for a little while if this changes...
i'm now thinking of reverting back to GB... since the battery drain for ICS is such a let down and with this problem... i'll give it a couple more days
what ROM are you running?
anyway something in the governor seems to have changed ,your case seems to be a performance governor.
try installing set cpu and set minimum to 200 ,max to 1400 ,and the governor to "on demand"
should fix things for you
IM on stock Ics lp9. I haven't root yet after I upgraded ota.
Set CPU requires root ain't it?
Sent from my GT-N7000 using XDA
scarlet_sg said:
IM on stock Ics lp9. I haven't root yet after I upgraded ota.
Set CPU requires root ain't it?
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
yes it does ,but if you're not rooted then the governor couldn't possibly have changed by you !!
could it be a bug in lp9? I heard that ICS have some battery issues
how long were you running LP9 before noticing this issue?
Well, havent heard it from that rom. Bring it back
Sent from my GT-N7000 using Tapatalk 2
it might be the fault of some rogue app running in background, did you check with betterbatterystats?
Sent from my GT-N7000 using xda premium
I was using lp9 for about 2 Weeks after I started noticing the CPU usage
Couldn't find a fix so I reverted back to rooted lc2 GB
With all the issues with Ics - battery drain, fc's and mmc bug and now this CPU overclocking felt it wasn't worth it.
Now the note is sleeping like a baby. Battery is back to its efficient self. I'm getting 3 days on one full charge.
Will just wait for an update on official Ics.
Appreciate all the help guys.
Sent from my GT-N7000 using XDA
My experience with my S4A has been amazingly flawless up until yesterday, when it started experiencing one of the issues that killed my experience with the HTC One- random freezes. And what's strange about it is that they are the same type of freezes that my One experienced, only when browsing the web or using an internet based app like Pulse. It has happened 3 times since yesterday and is so bad that I've had to pull the battery to even get it to reboot. Which brings me to one of my suspicions...
The only thing that has changed between me getting the phone set up originally and when the freezes began was the fact that I started swapping batteries instead of charging the phone. Now, phone batteries nowadays are not just like your average AA cell, it has circuitry in it and NFC stuff... is it possible that a defective battery could be the culprit of my woes? I just put in my original battery and am gonna just wait and see if it happens. The other battery that I've been using is a Samsung OEM battery and not a cheap one. I did root and freeze a bunch of stuff, but nothing exotic, and it was fine until yesterday. I doubt anything I did caused this.
Has anyone else experienced any freezes like this? Help me solve this, I really want to keep this phone (at least until the next latest and greatest comes out). TIA
_MetalHead_ said:
My experience with my S4A has been amazingly flawless up until yesterday, when it started experiencing one of the issues that killed my experience with the HTC One- random freezes. And what's strange about it is that they are the same type of freezes that my One experienced, only when browsing the web or using an internet based app like Pulse. It has happened 3 times since yesterday and is so bad that I've had to pull the battery to even get it to reboot. Which brings me to one of my suspicions...
The only thing that has changed between me getting the phone set up originally and when the freezes began was the fact that I started swapping batteries instead of charging the phone. Now, phone batteries nowadays are not just like your average AA cell, it has circuitry in it and NFC stuff... is it possible that a defective battery could be the culprit of my woes? I just put in my original battery and am gonna just wait and see if it happens. The other battery that I've been using is a Samsung OEM battery and not a cheap one. I did root and freeze a bunch of stuff, but nothing exotic, and it was fine until yesterday. I doubt anything I did caused this.
Has anyone else experienced any freezes like this? Help me solve this, I really want to keep this phone (at least until the next latest and greatest comes out). TIA
Click to expand...
Click to collapse
Mine started Sunday. All it would do is hang at the ATT logo on reboot. I ended up doing a factory reset and it hasn't happened since. Certainly made me suspect the rooting I did...
kbmapper said:
Mine started Sunday. All it would do is hang at the ATT logo on reboot. I ended up doing a factory reset and it hasn't happened since. Certainly made me suspect the rooting I did...
Click to expand...
Click to collapse
What did you do to your phone after rooting?
A couple of times now my active has become unresponsive. The power button doesn't seem to work and the home key doesn't do anything. The led is flashing blue and the battery is still about 35%. The only thing I can do is pull the battery.
Not sure if this is related to your question but I'm going to try to get it replaced...
Sent from my SAMSUNG-SGH-I537 using xda app-developers app
Didn't really do anything drastic- Titanium Backup and froze some att crap. Nothing even remotely close to system apps.
dinglayne said:
A couple of times now my active has become unresponsive. The power button doesn't seem to work and the home key doesn't do anything. The led is flashing blue and the battery is still about 35%. The only thing I can do is pull the battery.
Not sure if this is related to your question but I'm going to try to get it replaced...
Sent from my SAMSUNG-SGH-I537 using xda app-developers app
Click to expand...
Click to collapse
My LED never starts flashing but like yours, none of the buttons respond and I have to do a battery pull. I really don't want to have to get it replaced, and I really don't want to wipe and start over, just don't have the time right now to do either. Did you do anything to yours? Root?
kbmapper said:
Didn't really do anything drastic- Titanium Backup and froze some att crap. Nothing even remotely close to system apps.
Click to expand...
Click to collapse
Same here. Nothing I froze should have any affect on system stability.
I Haven't had any issues since I've had the phone, going on 3 weeks. I've been rooted and have froze apps in TB with no problems since geohot gave us root. Also have done some other root mods, and have not experienced any issues.
Sounds like just some bad hardware circulating.
Sent from my SAMSUNG-SGH-I537 using xda app-developers app
I've modded mine a good amount and haven't had any lock ups. I have just about every root app out there. Xposed with nottach, dark phone and contact apk, and cm10.1 messaging app. Froze a lot of bloat too
Sent from my SAMSUNG-SGH-I537 using Tapatalk 4 Beta
Man I REALLY hope it's not a hardware issue. I'm so tired of doing the repeated exchange thing. I went through 5 One X's before I found a suitable one, saw that pattern emerging with the One (had 2, both with same issues) and was really hoping the S4A was going to be the answer to my woes. I really love this phone but if it ends up being a hardware thing, I will be incredibly disheartened.
Sent from my SAMSUNG-SGH-I537 using xda premium
Any way to tell the build dates of our phones? Maybe we could narrow it down to a certain production date.
Sent from my SAMSUNG-SGH-I537 using xda app-developers app
echonc said:
Any way to tell the build dates of our phones? Maybe we could narrow it down to a certain production date.
Sent from my SAMSUNG-SGH-I537 using xda app-developers app
Click to expand...
Click to collapse
I dunno... My box is in another state so I won't be able to check it for a few weeks. I bought it on the very first day it was available if that helps any. On a side note, I put my original battery in last night and it hasn't locked up on me since. We'll see what happens by the end of the day.
Sent from my SAMSUNG-SGH-I537 using xda premium
I am rooted but that's pretty much it.
The only thing I know I was doing at the time was watching a YouTube video then pressed pause.
Next thing you know I picked it up hit the power... Nothing. Hit menu... Nothing. The blue LED was just the normal notification indicator, so I knew it hadn't powered off... Resulted in a battery pull.
I also know that I didn't get any messages or new notifications while the screen was off.
Sent from my SAMSUNG-SGH-I537 using xda app-developers app
I ALWAYS have issues restoring from titanium backup, esp going from one phone to another. My suggestion is to factory reset and start with a clean slate, cas only then can u verify a hardware issue.
_MetalHead_ said:
I dunno... My box is in another state so I won't be able to check it for a few weeks. I bought it on the very first day it was available if that helps any. On a side note, I put my original battery in last night and it hasn't locked up on me since. We'll see what happens by the end of the day.
Sent from my SAMSUNG-SGH-I537 using xda premium
Click to expand...
Click to collapse
I know on the Captivate the Build Number could be found under the battery (can be found there on the S4A as well) and it was the year/month that the phone was built, or so they say. My S4A Build number is 1306 so I'm guessing it was built the beginning of June...
_MetalHead_ said:
I dunno... My box is in another state so I won't be able to check it for a few weeks. I bought it on the very first day it was available if that helps any. On a side note, I put my original battery in last night and it hasn't locked up on me since. We'll see what happens by the end of the day.
Sent from my SAMSUNG-SGH-I537 using xda premium
Click to expand...
Click to collapse
I would like to know if you have had any more problems since you put your original battery back in? If you could give a update I would really appreciate it. I really think the active is a great phone and I truly like it but if people are having a lot of issues with it, I'll just return it and get something else to save myself a headache down the road. I have a week left on my return date so that's why I was wanting to know.
Sent from my SAMSUNG-SGH-I537 using xda premium
gf has had similar issues; heres what fixed it.
battery pull
factory reset/restore
reboot
battery pull
reboot
root/etc/restore from there. check to make sure you dont have custom CPU voltage/speed mods enabled; i believe this was the initial culprit, though even after resetting them to stock it would still lock up. it only did it 3 times, and usually right after a new mod, but ONLY if CPU values were changed. after the above procedure, she redid all her cpu values but only AFTER all mods were installed, rebooted, and everything works great again.
tmease1 said:
I would like to know if you have had any more problems since you put your original battery back in? If you could give a update I would really appreciate it. I really think the active is a great phone and I truly like it but if people are having a lot of issues with it, I'll just return it and get something else to save myself a headache down the road. I have a week left on my return date so that's why I was wanting to know.
Sent from my SAMSUNG-SGH-I537 using xda premium
Click to expand...
Click to collapse
The only "issue" I've had with mine is that it's too bright when the brightness is set to max
tmease1 said:
I would like to know if you have had any more problems since you put your original battery back in? If you could give a update I would really appreciate it. I really think the active is a great phone and I truly like it but if people are having a lot of issues with it, I'll just return it and get something else to save myself a headache down the road. I have a week left on my return date so that's why I was wanting to know.
Sent from my SAMSUNG-SGH-I537 using xda premium
Click to expand...
Click to collapse
Same problems no matter which battery. It seems to happen most when I'm using Chrome so I deleted the updates but it's still doing it. It happened while playing a game today which it's never done before. Next step is to freeze Chrome and see if that helps. If not, then I'm gonna factory reset and if that doesn't work, I'm gonna have to exchange it. I really did not want to have to deal with this. With my ridiculous work schedule I don't have the time or the energy. I might just start looking for a different phone because I'm sick of having issues like this.
Sent from my SAMSUNG-SGH-I537 using xda premium
_MetalHead_ said:
Same problems no matter which battery. It seems to happen most when I'm using Chrome so I deleted the updates but it's still doing it. It happened while playing a game today which it's never done before. Next step is to freeze Chrome and see if that helps. If not, then I'm gonna factory reset and if that doesn't work, I'm gonna have to exchange it. I really did not want to have to deal with this. With my ridiculous work schedule I don't have the time or the energy. I might just start looking for a different phone because I'm sick of having issues like this.
Sent from my SAMSUNG-SGH-I537 using xda premium
Click to expand...
Click to collapse
I would say if the factory reset does not work than it is the phone itself. I had issues like this in the past with my old infuse and I did a factory reset and it took care of it. Hopefully that will help you out so you can keep your phone. Thanks for replying.
Sent from my SAMSUNG-SGH-I537 using xda premium
tmease1 said:
I would say if the factory reset does not work than it is the phone itself. I had issues like this in the past with my old infuse and I did a factory reset and it took care of it. Hopefully that will help you out so you can keep your phone. Thanks for replying.
Sent from my SAMSUNG-SGH-I537 using xda premium
Click to expand...
Click to collapse
Yeah bud, I really hope a reset works. I might do it tomorrow, I should have enough time. I'm just frustrated that I'm having identical issues with the S4A that I had on my One. I was really hoping to find a phone that just works. I don't think I've had a problem free phone since my Epic 4G Touch. My One X had issues (though my 5th one was near perfect), my iPhone 5 was horrible, both my Ones had problems, and now this. I'm just venting now but I'm seriously tired of it. I've got my eye on that new Sony i1 that's coming out in a couple months, I really love their current design choices and I've never tried a Sony before. Or maybe the next Nexus. Who knows. I just don't want to deal with this crap anymore.
/rant
Sent from my SAMSUNG-SGH-I537 using xda premium