I finally rooted it yesterday and it now is very unresponsive at times. It will get to the point where it's frozen for about 30 seconds before it does anything. I flushed the caches and did a reset, same thing. So I flashed Jedi ROM on it. It's a little better but still has moments where ti freezes for a time. Is there a fix for this?
Rooting does absolutely nothing to the performance of the device. Its comparable to giving yourself admin rights on a windows computer. No performance change just extra features. Might want to check any apps that you installed after rooting
I did not install anything after root.
It works smooth as silk with the stylus. Possible sensitivity adjustment?
Maybe the sdcard needs to be reformatted?
marksm said:
I did not install anything after root.
It works smooth as silk with the stylus. Possible sensitivity adjustment?
Maybe the sdcard needs to be reformatted?
Click to expand...
Click to collapse
ROOT will not brake the phone or cause lag. it changes nothing internally except rights to your phone. no tweaks or files deleted. I can see it being something with the screen since you say the pen works great and using your finger I assume it micro stutters. but even the freezing for 30 sec does not sound screen related. I would wipe and format data, and then try another Rom. I used jedi from the first build all they up to 15 and it ran like a champ. its something you are doing, or have not undone yet.
I would suggest clearing caches. Its got nothing to do with rooting, but neither does rooting have to do with lag.
It sounds like an app was restored with data.
rangercaptain said:
I would suggest clearing caches. Its got nothing to do with rooting, but neither does rooting have to do with lag.
It sounds like an app was restored with data.
Click to expand...
Click to collapse
Agreed....
Excellent point ranger.....TY.....g
Sent from my SAMSUNG-SGH-I317 using XDA Premium HD app
no apps were restored either. When I flashed the new ROM I cleared every cache I could see listed and wiped it clean. All I can think of is the old stuff on the sdcard is causing issues so tomorrow I will reformat it and reset again.
Well then, the only thing I can think of is you flashed an incorrect kernel. What exactly did you flash?
Used the root tool from http://galaxynote2root.com. Odin and cwm6-root-note2.tar.
It still had the bad lag and freezing after I un-rooted it and restored the original ROM.
I have since flashed Jedi, didn't like it and now am on NOTEorious Prime.
What I have noticed is that the lag and freezing go away when I am connected to a wireless network. Maybe it screwed up my modem?
And have you verified the APN settings as being correct ?
Or they may simply be mixed up by default..
It may be set on ATT LTE.....instead of ATT PHONE for example...
Both will work...but one will drop the network speed by about 70%...
Just a thought....g
Sent from my SAMSUNG-SGH-I317 using XDA Premium HD app
Perhaps a factory reset from within recovery --- to make all settings default. By now there's a lot of stuff floating around in there.
Why would the original root change the APN settings.
I have factory reset several times. Even with the factory image applied fresh, it still freezes. The weird thing is, it responds just fine to the stylus.
I am at the point where I restore the stock ROM again and take it to ATT to see if they will swap it out.
Thanks for the help, keep the ideas coming..
Flashing a custom rom or recovery or kernel voids your warranty. Please don't tell us about plans to return the phone to at&t. The phone worked as expected before you began flashing.
It's not the radio or wireless either. It works perfect with the stylus but seems like it doesn't detect my finger to operate normally. Does Samsung have a tool to reset the display sensitivity?
There is a dial code for the touch screen. I don't know it, but I've found those codes by googling 'android secret note 2 dialer codes' or something like that.
Looks like I have it fixed.. It's working right since I followed the instructions here http://android.stackexchange.com/questions/39423/galaxy-note-10-1-does-not-recognize-finger-touch
I had installed swiftkey so I removed that and tried swype beta and it's all good now.
I restored everything back to stock and it is still having problems. The screen is unusable with my finger, I have to use the S Pen for everything.
Would reloading the stock ROM with kies be different than using Odin? Does Samsung put some key piece of code in the areas that get changed with rooting?
I am at a loss..
marksm said:
I restored everything back to stock and it is still having problems. The screen is unusable with my finger, I have to use the S Pen for everything.
Would reloading the stock ROM with kies be different than using Odin? Does Samsung put some key piece of code in the areas that get changed with rooting?
I am at a loss..
Click to expand...
Click to collapse
Ok to test you touch screen etc. type this in code in your dialer *#0*#!!
And don't think Sammy would put something in there, to make there phones not work correctly!
Me 2¢®
Sent from my SAMSUNG-SGH-I317 using Tapatalk 4
Bajanman said:
Ok to test you touch screen etc. type this in code in your dialer *#0*#!!
And don't think Sammy would put something in there, to make there phones not work correctly!
Me 2¢®
Sent from my SAMSUNG-SGH-I317 using Tapatalk 4
Click to expand...
Click to collapse
On the test screen, I have to tap screen many times until it finally registers. Then I drag my finger around for about 30 seconds before it starts picking up and filling in the boxes. It will finally let me fill in all the boxes and say it passes but it takes a lot of effort.
marksm said:
On the test screen, I have to tap screen many times until it finally registers. Then I drag my finger around for about 30 seconds before it starts picking up and filling in the boxes. It will finally let me fill in all the boxes and say it passes but it takes a lot of effort.
Click to expand...
Click to collapse
Yeah it's not suppose to be that difficult honestly. Something is defiantly wrong!!
Me personally if you bought the phone from an AT&T store! I'd reborn it for a replacement! And if it's not used from someone off the street. Then I'll put it back to fully stock, reset flash counter. Then return and replace at one of there local service centers. Especially if it's giving that much problems as it sounds to be doing. Seems as if the screen has some hardware issues inside...
Sent from my SAMSUNG-SGH-I317 using Tapatalk 4
Related
After the ICS update on my non-rooted phone, the phone seems to be freezing
up and becoming unresponsive. After a while it looks like the radio "resets", all
the icons disappear in the top bar (signal, wifi, data) and it shows no service.
Then slowly one by one they all come back and I can use the phone again.
Sometimes I receive the "System is not responding" dialog box, but not always.
There is not one particular program it is doing this in, it can be something as
simple as pulling down the notification bar that will cause the freeze.
Any suggestions are appreciated, I couldn't find anyone else with the same issue.
Thanks.
Try:
Turn off phone
Take out SIM
Put SIM back
Turn on
I've had my phone act weird with respect to signal, wifi and data when this was the issue. Worth a shot, at the very least.
Digital_Buddha said:
Try:
Turn off phone
Take out SIM
Put SIM back
Turn on
I've had my phone act weird with respect to signal, wifi and data when this was the issue. Worth a shot, at the very least.
Click to expand...
Click to collapse
Thank you for the response.
Tried this and had the system is unresponsive issue right on reboot. If I do a
factory reset, does it reset to the current firmware or what was originally on the
phone (probably a really stupid question). I wonder if some other program isn't
ICS compatible and is doing something in the background. Doesn't look like
anyone else is having this same issue.
jdscully said:
Thank you for the response.
Tried this and had the system is unresponsive issue right on reboot. If I do a
factory reset, does it reset to the current firmware or what was originally on the
phone (probably a really stupid question). I wonder if some other program isn't
ICS compatible and is doing something in the background. Doesn't look like
anyone else is having this same issue.
Click to expand...
Click to collapse
If you do a factory reset and it was the standard Kies legit update from Tmo, it won't downgrade your phone - will just re-install a fresh copy of your ICS. Did you do a restore of apps from your last version (gb?) with data? That could cause problems I would think..
VoiD_Dweller said:
If you do a factory reset and it was the standard Kies legit update from Tmo, it won't downgrade your phone - will just re-install a fresh copy of your ICS. Did you do a restore of apps from your last version (gb?) with data? That could cause problems I would think..
Click to expand...
Click to collapse
Yes I did the legit update on Kies, standard stock phone un-rooted.
Do I need to backup pictures before the reset, its been a while since
I had to do this.
At this point, I think its worth a try to wipe it clean and clear out all the
data.
jdscully said:
Yes I did the legit update on Kies, standard stock phone un-rooted.
Do I need to backup pictures before the reset, its been a while since
I had to do this.
At this point, I think its worth a try to wipe it clean and clear out all the
data.
Click to expand...
Click to collapse
wipe the dalvik cache and cache then reboot
I did a factory reset and that solved the issue.
Thanks for all the assistance.
I've done a factory reset and wiped the cache more than once already and i still get a force close or unresponsive, enough that its really irritating me now. Any advice? And also, when texting, the typing responds very slow.
Sent from my SGH-T989 using XDA
itsdamage said:
I've done a factory reset and wiped the cache more than once already and i still get a force close or unresponsive, enough that its really irritating me now. Any advice? And also, when texting, the typing responds very slow.
Sent from my SGH-T989 using XDA
Click to expand...
Click to collapse
Are you letting it sit for like 10 minutes during first boot after factory reset then reboot again before setting up. Its likely that some scripts are running from the initial installation and you need to let it rot until its done..
I did exactly that, thanks for the advice. Hoping that may fix the problem. I wiped the cache and factory reset, then let the phone sit for a good while before going through the play store and re-installing everything.
This issue just resurfaced again. The last 2 days I am getting the freezing, radio reboot and android process not responding.
No one else having this issue?
I think I'm in the same boat. I was stock GB, and just did the mini OTA update (which was great). A few days later ICS became available via Kies from T-Mobile, and I "upgraded".
Since the upgrade my phone is laggy, screen is significantly less responsive and also my battery life is less than before.
I have NOT done a factory reset of my phone yes (plan on doing that today), but even with that I have read that performance does not improve.
Ideally, I would love to return back to the stock tmobile gb firmware. However, even after literally 2 hours of reading I can't find the "how-to" and files I need.
I would appreciate any assistance.
t989 chip lags
ive notice this happen on my tmobile galaxy s2. i think it has to do with the Qualcomm chip on tmobiles stock roms.
When i had sprint i bought my girlfriend a galaxy s2 on the sprint network which runs the samsung exynos chip. She never complained about any lag or freezing whatsoever. I then left sprint because of their garbage network and joined tmobile.
bought 2 galaxy s2s and i noticed the lag almost immediately. The phone has random lag spikes as well as freezing and force closes. It had it on stock gingerbread and it has it on stock ICS too.
My girlfriend complains about freezing all the time so i decided to root her phone too. Right now im testing DarkSides v7 rom and if its pretty good in performance i will flash her phone with it too. So far it has been pretty snappy and everything works.
jdscully said:
This issue just resurfaced again. The last 2 days I am getting the freezing, radio reboot and android process not responding.
No one else having this issue?
Click to expand...
Click to collapse
Yes i have the exact same problem...and the clock goes off too...if i don't reboot then this will keep happening...if you go into settings then development settings and tick off only let 4 process run in the background it should stop...try it and let me know
Sent from my SGH-T989 using xda premium
tonydetroit said:
I think I'm in the same boat. I was stock GB, and just did the mini OTA update (which was great). A few days later ICS became available via Kies from T-Mobile, and I "upgraded".
Since the upgrade my phone is laggy, screen is significantly less responsive and also my battery life is less than before.
I have NOT done a factory reset of my phone yes (plan on doing that today), but even with that I have read that performance does not improve.
Ideally, I would love to return back to the stock tmobile gb firmware. However, even after literally 2 hours of reading I can't find the "how-to" and files I need.
I would appreciate any assistance.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1668502
follow that first post. i went through exactly the same problems and found this guide and am now happy again and running stock GB on my Galaxy S2.
Because you are on stock ics (im guessing you are..), you can just follow that guide and flash the UVLDE update.
Yes clock resets to standard standard time.. I already did a factory reset and worked done for a couple weeks. My wife has same phone and she is getting the freeze ups now.
jdscully said:
Yes clock resets to standard standard time.. I already did a factory reset and worked done for a couple weeks. My wife has same phone and she is getting the freeze ups now.
Click to expand...
Click to collapse
Yeah really sux...it's random..I'm using a custom kernel and still having that problem....
Sent from my SGH-T989 using xda premium
Yup here too. Almost reminds me of XP. Really ticking me off & it never happened on gingerbread. Rooted now & before I'm on rogers 4.0.4. wondering if there's going to be fix? Haven't seen if Google / rogers /at&t have commented?
Sent from, The Eclectic Chair.
I'm getting the freezes as well even after doing a factory reset.
It sucks, I'm waiting for cyanogen to release a stable release and then I'm switching.
djtheraven said:
Yes i have the exact same problem...and the clock goes off too...if i don't reboot then this will keep happening...if you go into settings then development settings and tick off only let 4 process run in the background it should stop...try it and let me know
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Thanks for the suggestion, I'll give it a try. But it really shouldn't be necessary on a phone that's got more going for it than the stock nexus that 1st came out with ics.
There's something else going on.
Sent from, The Eclectic Chair.
So I got the Galaxy Nexus GSM today and it's one hell of a sexy device.
It obviously came with Ice Cream Sandwich out of the box. And errors out of the box. Right when I start the phone, Talk FCs. When I try to start the Camera, it FCs.
I though "What the heck, Jellybean probably fixes that", so I unlocked it and flashed Paranoid Android. Everything is a lot faster now, but I still have the same problems, except now Gallery just crashes, which renders the Camera unusable, because they're apparently linked together in Jellybean.
I tried 3rd party apps (Zoom Camera, Paper Camera and a few others) and none of them work.
So it seems that everything that has something to do with the Camera doesn't work.
I tried everything that I could think of;
Reflashing
returning to stock
force stop Camera
Disable and enable all network related functions in G+ and Gallery
Clearing cache - both for individual apps and the option from the recovery
Trying 3rd party apps
Googling everything I could think of
Installing G+ (that made me able to open Gallery, but Gallery still force closes when I open Camera)
Changing battery
Of course I can't see it being anything but a hardware issue, but some people who have compiled CM10 by themselves have the same errors. I don't know if that helps me.
So before I return it some time this week, does any one have any suggestions to what I could try?
I'll give this thread two days before I return it.
Thanks in advance.
You rooted? If not and you know how to root, root it, replace the app (gallery, camera, whatever is not working) with stock JB version. Hopefully it's just corrupted apps... That's easy to fix
Thanks for the reply. I've already tried the Jellybean version of Paranoid Android and it made no difference.
I though "What the heck, Jellybean probably fixes that", so I unlocked it and flashed Paranoid Android. Everything is a lot faster now, but I still have the same problems, except now Gallery just crashes, which renders the Camera unusable, because they're apparently linked together in Jellybean.
Click to expand...
Click to collapse
mrhaxx1 said:
Thanks for the reply. I've already tried the Jellybean version of Paranoid Android and it made no difference.
Click to expand...
Click to collapse
Might be a long shot, but have you tried fixing permissions in recovery?
Sent from my Galaxy Nexus using xda premium
I have, but I just tried again and it made no difference.
Also, I forgot to mention that it's not a storage issue, as I can save screenshots just fine.
mrhaxx1 said:
I have, but I just tried again and it made no difference.
Also, I forgot to mention that it's not a storage issue, as I can save screenshots just fine.
Click to expand...
Click to collapse
Any solutions for this yet? having the same problem.
Nope, nothing yet.
And to make the bad things worse, I've lost the receipt. So I can't even return it.
Bumpity bump!
mrhaxx1 said:
Bumpity bump!
Click to expand...
Click to collapse
I just went ahead and called verizon.. and they're shipping me a new phone today. I see a lot of posts about this, with no solution. It'll be quicker to do it this way. Except you call whatever your carrier is. Or samsung, if nothing else.
Well, you see, I bought the phone refurbished. There was a guarantee on it, but I lost the receipt, so I can't return it or get a new phone.
I ordered a rear- and front-facing replacement camera. It should arrive in 7-15 days because I'm ordering from the USA.
I looked into it, and disassambling and assembling it should be fairly simple. Nearly the same process as the Nexus S, which I've disassembled before.
If it doesn't work, I've only lost $22 and it's not like I have a valid guarantee on it anyway.
Oh well, replacing the cameras didn't work.
And I even managed to break the volume buttons.
Even if I got hold of the receipt, there would be no way they would repair it now.
I can as well just go buy a new phone. Next month. Maybe. At least everything else still works.
When you flash ROM, do you ensure you completely wipe previous ROM and data? Also, if you use something like Titanium Backup to restore your apps after flashing a new ROM, make sure you don't restore system apps or data. That will definitely screw things up in every ROM as incompatible files are mixed.
Try doing a full wipe of your device it could help
Sent from my Galaxy Nexus using xda app-developers app
It was like that on the stock rom.
And yes, I always ensure to wipe everything. As said in the OP, I even tried returning back to stock.
I got the same problem, I GOT IT FIXED NO HARDWARE FAILLURE!!
Hi,
this is what i did, got it fresh from the box, didn't even bother to set-up, I instantly updated to Jelly Bean..
everything worked perfectly, besides the camera, it crashed instantly.. (gallery did not respond)..
i rebooted it 2 times, then pressed the Power button + volume down.. it went to an system boot thingy.. the i connected it to my pc with an usb (usb debugging enabled).
my win7 pc said the drivers were installed, then i pressed the power button. after loading. the camera worked perfect.. thats REALY everything i DID.. i'll keep you posted if it fails again.
it also worked after unplugging the usb.. Hope I helped you a bit.
I can second this fix!
IvanGrozni87 said:
Hi,
this is what i did, got it fresh from the box, didn't even bother to set-up, I instantly updated to Jelly Bean..
everything worked perfectly, besides the camera, it crashed instantly.. (gallery did not respond)..
i rebooted it 2 times, then pressed the Power button + volume down.. it went to an system boot thingy.. the i connected it to my pc with an usb (usb debugging enabled).
my win7 pc said the drivers were installed, then i pressed the power button. after loading. the camera worked perfect.. thats REALY everything i DID.. i'll keep you posted if it fails again.
it also worked after unplugging the usb.. Hope I helped you a bit.
Click to expand...
Click to collapse
So, I was having this exact same issue and was ready to call Verizon for a replacement, when I tried this as a last resort and VOILA!! IT WORKED! I am still unsure of how this all came about, but for the purpose of hopefully helping someone with the same issue, I will second this quick fix as IT DID WORK FOR ME.
I had this same problem (camera/talk fc'ed on start, whenever opening either app), tried all the fixes I could and nothing worked. I eventually disassembled the phone and used a toothbrush and isopropyl alcohol to clean the main board and the connections for each of the camera modules. After a couple rounds of cleaning, everything started working again.
navjas73 said:
I had this same problem (camera/talk fc'ed on start, whenever opening either app), tried all the fixes I could and nothing worked. I eventually disassembled the phone and used a toothbrush and isopropyl alcohol to clean the main board and the connections for each of the camera modules. After a couple rounds of cleaning, everything started working again.
Click to expand...
Click to collapse
Thanks for this information, I'll try to do it with mine too. Any results I will post here.
I've been having gn2 from at&t for about 2 months. It's awesome in most respects but it sometimes locks up cold. By cold, I mean that the only way to fix it is to pull out battery for some extended time - 5-10 min. Usually it happens when I use some software, typically accessing network. Just now it happened when I used Chrome beta.
Also it happens sometimes after graceful shutdown that it locks up immediatelly on boot.
Seems to happen with any rom that I tried.
Does anyone else have similar problems? I wonder if it's hardware defect.
alexnoalex said:
I've been having gn2 from at&t for about 2 months. It's awesome in most respects but it sometimes locks up cold. By cold, I mean that the only way to fix it is to pull out battery for some extended time - 5-10 min. Usually it happens when I use some software, typically accessing network. Just now it happened when I used Chrome beta.
Also it happens sometimes after graceful shutdown that it locks up immediatelly on boot.
Seems to happen with any rom that I tried.
Does anyone else have similar problems? I wonder if it's hardware defect.
Click to expand...
Click to collapse
I was experiencing lock ups on earlier 7105 ROMs I was using. I thought power cycling was the only way then I discovered if you take out the S-pen (and then put it back) it would unfreeze the device. Maybe give that a shot next time, in case its similar.
Mine would freeze randomly...
Sent from my SGH-I317M using Tapatalk 2
gn2 freeze
xtechx said:
I was experiencing lock ups on earlier 7105 ROMs I was using. I thought power cycling was the only way then I discovered if you take out the S-pen (and then put it back) it would unfreeze the device. Maybe give that a shot next time, in case its similar.
Mine would freeze randomly...
Sent from my SGH-I317M using Tapatalk 2
Click to expand...
Click to collapse
I have never had a problem with mine, but it is still stone stock. That will be changing shortly tho...
I haven't had any lockups per se, but I've had 2 random reboots. I've had the device a week. Rooted, on stock.
I've had this phone for 5 months roughly. It has never locked on stock, Clean ROM, CM 10.1
It really shouldn't be locking up ever
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Bring it back and get a new one. Sounds like a bad device
JDEVIL ZODIAC POWERED ROMS
THIS IS WHY I DONT UNDERVOLT AND DONT RECOMMEND IT http://www.mediafire.com/view/?wdtd8fhletu7lpc
Mine used to do that. Turns out the problem was Superuser. If you have Superuser, and not SuperSU, installed, try switching them and see if it clears up the lock ups.
I would also get weird notifications about "shell" and "radio" trying to get root access.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
I have SuperSU. And I am on international rom. But it did the same thing with CleanRom.
godsmacked4653 said:
Mine used to do that. Turns out the problem was Superuser. If you have Superuser, and not SuperSU, installed, try switching them and see if it clears up the lock ups.
I would also get weird notifications about "shell" and "radio" trying to get root access.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
I had this problem on my SII.
My girl had this problem as well. To remedy it first I wiped the external sd card. Wiped everything off of it incase of some bs data.
Then I wiped and re flashed the rom and only restored mms and the call log with tibu. The rest of the apps she had I manually installed them one by one from the market.
Now doing the above two cleaned up a lot of lockups but it was still happening. Final thing that actually stopped the freezes was getting rid of Chrome. Why was Chrome causing issues, I have no idea but after removal the phone never randomly rebooted and after getting use to the stock browser it's been smooth sailing.
~PsyCl0ne
Edit: sorry just for reference both my phone and hers are running SkyNote 6 with the 6.7 update and the saber 13.4 release.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Chrome definitely may be a culprit. It happened to me often when using it. What is interesting is that it wouldn't reboot unless battery is out for few minutes. It feels like some memory state , perhaps in modem, gets corrupted and isn't cleared during boot.
And it was happening at times with freshly flashed rom with full wipe.
I have this issue too. I know for sure it is ROM or Kernel related as it never does it if I revert back to stock ROM and Kernel. Mine seems to be in a really deep sleep when it happens. I hold the power button for about 15 seconds and the phone reboots and everything is fine for a few days again.
Hi,
History:
I have a problem with my Nexus. It randomly reboots. Nothing seems to help.
It started after a few months after I was rooted on CyanogenMod 10.0. In 3 days, it quickly escalated to a reboot every 10 minutes on average.
A factory reset (without user apps installed on it) on CynogenMod reduced the frequency (every hour?), but didn't eliminate it.
Unrooting to stock Jellybean 4.1.2 seemed fine only in the first week. The problem came back afterwards, and updating to JB 4.2.1 didn't help.
Now, 2 months on stock ROM, I get even more random times. Sometimes it is 2 times a day, sometimes once a week.
Just before it:
I get a metallic screeching noise for 1-2 seconds, and immediately following that, device turns off with a "pang". Although these days I HAVE had situations that the sound came for up to 3 seconds (and the screen freezes), but the phone worked normally afterwards.
What happens:
It randomly reboots. The rebooting is at irregular intervals, whatever i was doing on it (even when not using it).
What happens after:
It takes much, much longer to startup again. It can get stuck at the "Google" logo screen for up to 5min. It doesn't take this long to reboot if I shut it down myself.
Any ideas? What causes this? Is it software or hardware?
Can I even send it for warranty if I cannot reproduce the problem?
I don't want to send it to warranty if I don't have to. I don't want to loose my phone for I don't know how long.
Hi, what's your eMMC version? Maybe buggy memory, try looking at other threads.
Отправлено с моего Galaxy Nexus через Tapatalk
Have you tried different batteries?
GeeNex | Carbon nightlies | Rubiks
I'm new to this eMMC thing, but according to an app my eMMC Type is V3U00M. To check whether it is buggy or not it needs root, which I don't currently have. If it IS buggy, I don't have a choice but to bring it for warranty right?
No, I have not tried to changed batteries. I don't have other batteries. But can the problem really lie with the battery? Btw, my phone is less than 8 months old.
Djalaal said:
I'm new to this eMMC thing, but according to an app my eMMC Type is V3U00M. To check whether it is buggy or not it needs root, which I don't currently have. If it IS buggy, I don't have a choice but to bring it for warranty right?
No, I have not tried to changed batteries. I don't have other batteries. But can the problem really lie with the battery? Btw, my phone is less than 8 months old.
Click to expand...
Click to collapse
Well, try waranty, that chip is buggy. Mine too )) but I just live with it using lagfix app and discard mount options, but things requires root. Good luck.
krugdenis said:
Well, try waranty, that chip is buggy. Mine too )) but I just live with it using lagfix app and discard mount options, but things requires root. Good luck.
Click to expand...
Click to collapse
Well, I am planning to root again. I want to switch back to CyanogenMod 10.1. Lagfix app isn't needed if you can use -discard mount option right? How to use either, if let's say I'm on CyanogenMod. This is also the first time I hear of lagfix and discard mount... :/
Btw, the app i used to check my eMMC Type said that my chip is ok. No brickbug. Are you sure it's buggy?
http://code.google.com/p/android/issues/detail?id=39154
Отправлено с моего Galaxy Nexus через Tapatalk
I might be wrong here, but from what I've read at the link and other xda posts (http://forum.xda-developers.com/showthread.php?t=2029246), the V3U00M chip is not buggy (in the sense that it's stable for rooting and using the -discard command), but it does give slowdowns. I do have horrible slowdowns, so thanks for that solution I didn't know existed. However, this doesn't solve my random reboot problem at all...
No one else got any solid way to find out the source of the problem?
BUMP
Djalaal said:
Hi,
History:
I have a problem with my Nexus. It randomly reboots. Nothing seems to help.
It started after a few months after I was rooted on CyanogenMod 10.0. In 3 days, it quickly escalated to a reboot every 10 minutes on average.
A factory reset (without user apps installed on it) on CynogenMod reduced the frequency (every hour?), but didn't eliminate it.
Unrooting to stock Jellybean 4.1.2 seemed fine only in the first week. The problem came back afterwards, and updating to JB 4.2.1 didn't help.
Now, 2 months on stock ROM, I get even more random times. Sometimes it is 2 times a day, sometimes once a week.
Just before it:
I get a metallic screeching noise for 1-2 seconds, and immediately following that, device turns off with a "pang". Although these days I HAVE had situations that the sound came for up to 3 seconds (and the screen freezes), but the phone worked normally afterwards.
What happens:
It randomly reboots. The rebooting is at irregular intervals, whatever i was doing on it (even when not using it).
What happens after:
It takes much, much longer to startup again. It can get stuck at the "Google" logo screen for up to 5min. It doesn't take this long to reboot if I shut it down myself.
Any ideas? What causes this? Is it software or hardware?
Can I even send it for warranty if I cannot reproduce the problem?
I don't want to send it to warranty if I don't have to. I don't want to loose my phone for I don't know how long.
Click to expand...
Click to collapse
Same as you man...
I'm seriously considering throwing my phone to the garbage. I don't like iPhones, but google is really pushing me into it with this crappy piece of phone. Is so frustrating to have these rebooting issues, I've tried everything, from wipe to factory reset, back to stock, flash custom ROMS and KERNELS, turning location access off, uninstalling all apps/widgets that might interfere, and every single "solution" it's out there, and STILL I'M HAVING THESE DAMN REBOOTS!
Now it's even worse, I can't even transfer files to my phone anymore because, guess what... IT REBOOTS! everytime I transfer ANY KIND of file.
The only thing that seems to work for a while is reformatting and start from scratch. I've done that like 3 times already. But still after a few weeks the issue reapears... i'm really mad about this, and no one seems to care. Not Google and not even Samsung.
The only interesting thing that i found around the internet is this guy's findings
plus.google.com/113601948978986762347/posts/2ALASEC1dG2
I read the log on my phone and matches to his... but now the thing is, what do i do with this information? I'm not a programmer o something like that.
Any ideas?
I think your board is faulty. Even so, have you tried disabling SR and raising voltages across the board? Trimming eMMC? Omapflash?
a manta wrote this.
Hey! Thanks for the reply but I'm just a regular user with just a little bit of computer knowledge... so the things you mentioned are basically Chinese to me
Sent from my Galaxy Nexus using xda app-developers app
elcampeondelrodeo said:
Hey! Thanks for the reply but I'm just a regular user with just a little bit of computer knowledge... so the things you mentioned are basically Chinese to me
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
He is saying that you have root you need to install trickster mod from the play store. Open the app and go to specific. Then disable the smart reflex toggles and click the oké button in the upper right corner see if that works. If it doesnt re enable smart reflex and go tot MPU voltages. Next to the words MPU voltages there is a blue plus/minus button. Click that and click the plus one time. Accept it and push again the oke button. The other two things I dont exactly know..
Sent from my Galaxy Nexus using XDA Premium HD app
Honestly, if you are getting reboots on a clean stock (including stock kernel) , it's probably a hardware issue.
Sent from my Galaxy Nexus using Tapatalk 2
Thanks for the reply guys!
mrgnex said:
He is saying that you have root you need to install trickster mod from the play store. Open the app and go to specific. Then disable the smart reflex toggles and click the oké button in the upper right corner see if that works. If it doesnt re enable smart reflex and go tot MPU voltages. Next to the words MPU voltages there is a blue plus/minus button. Click that and click the plus one time. Accept it and push again the oke button. The other two things I dont exactly know..
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
I tried both things you mentioned with no luck
I'm still searching around for those other things beekay201 mentioned earlier. I found that Omap Flash is a tool for flash roms in binary mode, so that way you can unbrick some phones. Still trying to find out how that can be useful for my case (forum.xda-developers.com/showthread.php?t=1242330)
bpyazel said:
Honestly, if you are getting reboots on a clean stock (including stock kernel) , it's probably a hardware issue.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
The thing is that after a clean stock install everything works fine for a week or two, that means no random reboots, and i can transfer any kind of file of any size with no problem. Then for some estrange reason (even with no crazy apps installed) starts with a random reboot, after that first reboot i know is time and that i wont be able to transfer files anymore, because it WILL reboot while i'm transfering files. Other thing i have noticed is that around where the camera lens is, get really hot. So I think that the reason it reboots is kernel panic caused by overheating, or the other thing is that my sdcard have some issues when writing files.
Right now i'm using CyanogenMod 10.0.0-maguro with jelly bean 4.1.2 and franco.kernel 3.0.51-nightly-512GPU and i have already tried going back to stock.
how can a I check if my hardware is fine? Is there any app out there?
Thanks!
elcampeondelrodeo said:
Thanks for the reply guys!
I tried both things you mentioned with no luck
I'm still searching around for those other things beekay201 mentioned earlier. I found that Omap Flash is a tool for flash roms in binary mode, so that way you can unbrick some phones. Still trying to find out how that can be useful for my case (forum.xda-developers.com/showthread.php?t=1242330)
The thing is that after a clean stock install everything works fine for a week or two, that means no random reboots, and i can transfer any kind of file of any size with no problem. Then for some estrange reason (even with no crazy apps installed) starts with a random reboot, after that first reboot i know is time and that i wont be able to transfer files anymore, because it WILL reboot while i'm transfering files. Other thing i have noticed is that around where the camera lens is, get really hot. So I think that the reason it reboots is kernel panic caused by overheating, or the other thing is that my sdcard have some issues when writing files.
Right now i'm using CyanogenMod 10.0.0-maguro with jelly bean 4.1.2 and franco.kernel 3.0.51-nightly-512GPU and i have already tried going back to stock.
how can a I check if my hardware is fine? Is there any app out there?
Thanks!
Click to expand...
Click to collapse
512GPU? You mean your GPU is overclocked? Maybe try to set your GPU to stock. And if it gets really hot and you have random reboots you can try to over volt with trickster mod.
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
512GPU? You mean your GPU is overclocked? Maybe try to set your GPU to stock. And if it gets really hot and you have random reboots you can try to over volt with trickster mod.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
No, I don't think my GPU is overclocked, that's the full name of the kernel, you say that the kernel automatically puts my GPU to 512?. Anyways i just installed that kernel two days ago just because i thought it might make the reboots go away. I'm having rebooting problems since february (just after upgrading to 4.2.1), so i don't think that the GPU is causing the reboots.
elcampeondelrodeo said:
No, I don't think my GPU is overclocked, that's the full name of the kernel, you say that the kernel automatically puts my GPU to 512?. Anyways i just installed that kernel two days ago just because i thought it might make the reboots go away. I'm having rebooting problems since february (just after upgrading to 4.2.1), so i don't think that the GPU is causing the reboots.
Click to expand...
Click to collapse
Well if it keeps rebooting you can try to over volt. Maybe that helps.
Sent from my Galaxy Nexus using XDA Premium HD app
OK I'll try that! Thanks for your help man!
Sent from my Galaxy Nexus using xda app-developers app
Ive searched everywhere and can't seem to find anyone with a solution. Ive found a post with the same problem but no solution.
So yesterday my s3 started having problems waking up. Meaning when I lock it usually you bring up the lock screen by pressing the power button or home button. Problem is when I press either one, screen doesnt come on. The buttons do. If I tap the screen I can hear the ripple effect but the screen doesnt light up. I have to keep locking and unlocking till it finally works. Averege of about 6 tries. When I get a call most of the time the screen doesnt come on either. I can still answer since I know where the slider is. When I do turn it on everything works perfect. No flickering or any other issues. When it boots it works perfect...never fails. Just when I lock it.
I tried restoring already, thinking its a software issue...still does it. What piece of hardware could cause this? I'm stumped. Please any advice would be great.
I'm not rooted and running 4.1.1 oem rogers software.
Sent from my SGH-I747M using xda app-developers app
felcom said:
Ive searched everywhere and can't seem to find anyone with a solution. Ive found a post with the same problem but no solution.
So yesterday my s3 started having problems waking up. Meaning when I lock it usually you bring up the lock screen by pressing the power button or home button. Problem is when I press either one, screen doesnt come on. The buttons do. If I tap the screen I can hear the ripple effect but the screen doesnt light up. I have to keep locking and unlocking till it finally works. Averege of about 6 tries. When I get a call most of the time the screen doesnt come on either. I can still answer since I know where the slider is. When I do turn it on everything works perfect. No flickering or any other issues. When it boots it works perfect...never fails. Just when I lock it.
I tried restoring already, thinking its a software issue...still does it. What piece of hardware could cause this? I'm stumped. Please any advice would be great.
I'm not rooted and running 4.1.1 oem rogers software.
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
My guess is that you have something draining all your RAM or being hard on your CPU. When you restored, did you factory reset?
You might have to backup your stuff, factory reset. Test it, if it still does it, bring it up with Rogers for a replacement. If it doesn't, reinstall your stuff until you find the culprit.
You could troubleshoot it also by uninstalling the latest apps you installed.
BWolf56 said:
My guess is that you have something draining all your RAM or being hard on your CPU. When you restored, did you factory reset?
You might have to backup your stuff, factory reset. Test it, if it still does it, bring it up with Rogers for a replacement. If it doesn't, reinstall your stuff until you find the culprit.
You could troubleshoot it also by uninstalling the latest apps you installed.
Click to expand...
Click to collapse
Like I said...Already did a factory reset. Meaning All apps were gone. Started fresh. Even without going through the first setup (setting up google account etc etc) if I lock the phone its hard to wakeup.
Phone is out of warranty so no go there....
I'm just not understanding what is causing it. I know the screen is fine...buttons are fine...everything points at a software problem. I found a post from a while back where someone was having the same problem....no solution was posted though. I even took the phone apart last night thinking a bad connection or something...disconnected the screen and reconnected it...didn't do anything.
If the screen was going bad wouldn't I have issues all the time? Once I wakeup the phone it works perfect...no flickering or anything. When it boots (which I've done like 30 times between today and yesterday) the screen has come on every single time perfectly fine. Everything tells me it's software related...but after doing a factory reset and running original firmware it seems as though it must be a hardware issue...but which component.
I know the phone wakes up when I press the buttons...I can see the menu and back buttons light up...and if I tap the screen the ripple sound is there...just the screen doesn't wake up....till I try a few more times....very frustrating.
Thanks Again for trying...if anyone has any ideas....greatly appreciated. I'll try and find original Rogers firmware and install with odin...see if that works....
felcom said:
Like I said...Already did a factory reset. Meaning All apps were gone. Started fresh. Even without going through the first setup (setting up google account etc etc) if I lock the phone its hard to wakeup.
Phone is out of warranty so no go there....
I'm just not understanding what is causing it. I know the screen is fine...buttons are fine...everything points at a software problem. I found a post from a while back where someone was having the same problem....no solution was posted though. I even took the phone apart last night thinking a bad connection or something...disconnected the screen and reconnected it...didn't do anything.
If the screen was going bad wouldn't I have issues all the time? Once I wakeup the phone it works perfect...no flickering or anything. When it boots (which I've done like 30 times between today and yesterday) the screen has come on every single time perfectly fine. Everything tells me it's software related...but after doing a factory reset and running original firmware it seems as though it must be a hardware issue...but which component.
I know the phone wakes up when I press the buttons...I can see the menu and back buttons light up...and if I tap the screen the ripple sound is there...just the screen doesn't wake up....till I try a few more times....very frustrating.
Thanks Again for trying...if anyone has any ideas....greatly appreciated. I'll try and find original Rogers firmware and install with odin...see if that works....
Click to expand...
Click to collapse
Sounds indeed like software issue. I'm not so sure what would cause it on stock rogers though.
Either way, you can find the stock ROM on sammobile.com or on this thread: http://forum.xda-developers.com/showthread.php?t=1822308
You'll need Odin to flash it. (It doesn't trigger the flash counter)
felcom said:
Phone is out of warranty so no go there....
Click to expand...
Click to collapse
Did you buy your phone with a credit card? Some cc's have warranty built in. Mine doubles what the manufacturer offers.
Thanks for the link. I will try it tonight and post the results. Really hoping it works.
Sent from my SGH-I747M using xda app-developers app
I downloaded the newest firmware. 4.1.2 official rogers. Problem persists. Must be a hardware issue. Thing is what could cause this? Is it the screen...is it the gpu? I imagine if its gpu the phone is only good for parts as I imagine its part of the motherboard. Oh well...might be getting the s4 sooner then planned.
Sent from my SGH-I747M using xda app-developers app
felcom said:
I downloaded the newest firmware. 4.1.2 official rogers. Problem persists. Must be a hardware issue. Thing is what could cause this? Is it the screen...is it the gpu? I imagine if its gpu the phone is only good for parts as I imagine its part of the motherboard. Oh well...might be getting the s4 sooner then planned.
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
If you're down for a little test, you could try with a custom ROM.
Use the link I gave you and flash pre-rooted Rogers' ROM. From there, install TWRP (or cwm) using goomanager (from the Play Store) and flash a custom ROM as per their instructions (Don't forget the Gapps).
Before anything though, make a backup
Never know, might save you some time on that S4.
BWolf56 said:
If you're down for a little test, you could try with a custom ROM.
Use the link I gave you and flash pre-rooted Rogers' ROM. From there, install TWRP (or cwm) using goomanager (from the Play Store) and flash a custom ROM as per their instructions (Don't forget the Gapps).
Before anything though, make a backup
Never know, might save you some time on that S4.
Click to expand...
Click to collapse
Thanks. I might try it. Dont think I have too much to lose at this point. I always try and keep my phones nice so that when I get a new one I can sell the old one for good money to help offset the cost. This really messes with that system as the phone isn't worth much now...just bought an extended battery too...was planning to keep it for at least another 6 months.
Sent from my SGH-I747M using xda app-developers app
So just a quick update. For no apparent reason the phone started working fine again. It now turns on and off just fine. I'm not going to mess around with it anymore. That's really bizzare. I'll give it a couple days and will report back if it continuous to work fine or if the problem comes back. Thanks for the input.
Sent from my SGH-I747M using xda app-developers app