Related
Hi, I've had a droid x for a few month now and just recently updated it to apex 1.4. Anyway my question is about my phone rebooting randomly. Seems like every day or two my phone will just reboot. I probably wouldn't even notice if it didn't make a sound when it booted up.
I bought the phone second hand and ran it stock for a long time although it was rooted. It has rebooted as long as I can recall. I was hoping upgrading the rom to apex 1.40 might fix that but no luck.
So my question is, is this normal? Does your droid x occasionally reboot itself?
Since mine does this do you think that it might be a hardware problem?
thanks for any help.
ethion said:
Hi, I've had a droid x for a few month now and just recently updated it to apex 1.4. Anyway my question is about my phone rebooting randomly. Seems like every day or two my phone will just reboot. I probably wouldn't even notice if it didn't make a sound when it booted up.
I bought the phone second hand and ran it stock for a long time although it was rooted. It has rebooted as long as I can recall. I was hoping upgrading the rom to apex 1.40 might fix that but no luck.
So my question is, is this normal? Does your droid x occasionally reboot itself?
Since mine does this do you think that it might be a hardware problem?
thanks for any help.
Click to expand...
Click to collapse
It's hard to tell what the cause is of reboots. It could be some many random things. Most running DX’s don’t have a random reboot quirk. Corrupt file/s is normally the culprit. I would back up all your information and apps (nandroid) and try a fresh factory reset. You can SBF or maderstcok if you wanted or, you can use the factory reset option on your phone and see if that helps. If not, a clean slate is what you might need. If after that it still reboots, you will need to SBF with RSD Lite or maderstcok and if it still persists, then I am afraid you will have to rather live with it or use it as a fancy paper weight.
Are you overclocked?
Sent from my DROIDX using XDA App
No I'm not overclocked and I was thinking it might be a bad file or something but after reflashing from stock to apex 1.4 and removing a lot of the blur apps I was having great speed and everything was running real nice. Then this morning it just rebooted...
Before I flashed it when I had it on stock rooted it was doing this reboot thing for awhile. Maybe every couple days. Not a huge deal since it reboots pretty fast and doesn't do it often. Just a pain sometimes.
Only things I think it could be now are bad hardware maybe I got a memory error or something. Or perhaps it is something I have installed that is causing it. I guess I could uninstall all my apps but then I'd have to cry so I guess I'll just live with it. I just wondered if this was just the baseline reliability of the device... Once upon a time I had a palm treo devices and it would crash and reboot all the time. Even when I replaced it it still did that. Friends that had one had similar issues. So for the palm treo it was just the standard that it would crash frequently. The bad thing is it would crash and not reboot
Reboots with Liberty 1.5
I am having the same issue with Liberty 1.5. I first moved from stock to Darkslide, and had no trouble. Then when liberty 1.0 released, I moved to that. I had other issues with liberty 1.0 but not reboots, but now with 1.5 I am getting reboots. I have already reformatted the SD card, restored to factory, and did a fresh install, but even though it seems to be less frequent, it has already happened twice today. I do have the throttle hack installed as I was getting clipped to less than 150k down.
speaker2thedead said:
I am having the same issue with Liberty 1.5. I first moved from stock to Darkslide, and had no trouble. Then when liberty 1.0 released, I moved to that. I had other issues with liberty 1.0 but not reboots, but now with 1.5 I am getting reboots. I have already reformatted the SD card, restored to factory, and did a fresh install, but even though it seems to be less frequent, it has already happened twice today. I do have the throttle hack installed as I was getting clipped to less than 150k down.
Click to expand...
Click to collapse
There's a zip file on droidforums that kejar and jrummy posted that adds back some framework files that will hopefully correct the reboot issues ...take a look at it.
Sent from my DROIDX using XDA App
bigshotrob22 said:
There's a zip file on droidforums that kejar and jrummy posted that adds back some framework files that will hopefully correct the reboot issues ...take a look at it.
Click to expand...
Click to collapse
Do you have a link handy? If not, I'll do some searching.
speaker2thedead said:
Do you have a link handy? If not, I'll do some searching.
Click to expand...
Click to collapse
Sorry I don't im on my phone right now but when I get to the computer I can post it for you.
EDIT: Hers is the link
http://www.droidforums.net/forum/liberty-rom-dx/126295-reboot-freeze-up-issues.html
Sent from my DROIDX using XDA App
Liberty Test Link
Thanks for the link. I was searching thru the known issues thread to no avail.
Thanks again.
speaker2thedead said:
Thanks for the link. I was searching thru the known issues thread to no avail.
Thanks again.
Click to expand...
Click to collapse
No problem. Let me know if that helps you out.
bigshotrob22 said:
No problem. Let me know if that helps you out.
Click to expand...
Click to collapse
It may be placebo, but I feel like the patch has made it more stable, but at the same time I have had three resets and a black screen freeze since I have installed it. My guess is in the throttle hack. Tomorrow I will do a fresh install and try to narrow down the culprit.
It has become quite clear that there is a small unlucky group of us that experience touch screen unresponsiveness at various times, mostly on froyo roms.
http://forum.xda-developers.com/showthread.php?t=1007304
http://forum.xda-developers.com/showthread.php?t=961042
Clearly I realize there are other threads that have discussed this in the past. I would like to find out just how common this problem really is and what we can do to fix it.
My personal experience: My screen works almost flawlessly on any eclair rom. Every froyo rom I have flashed (almost all the super cleans, vanilla AOSP, MIUI etc) I will experience unresponsive spots on the touch screen. Typically it starts in the lower left 1/4 then spreads to the entire screen. A brief lock and unlock of the phone usually gets it working again, only to return a few moments later. When my factory Samsung charger is plugged in the screen is completely useless.
Originally I thought it was a kernel problem but it still happens on the new OE released EC10 kernel as well as on the AOSP built ones. I think it is a hardware problem on certain phones. Why only froro? I have no idea.
Please participate in my survey so we can figure out how bad this really is.
I have also have the screen responsiveness issues. The middle of the screen becomes unresponsive and I have to lock and unlock to get the screen to work. This is only an issue with froyo ROMs. My wife has a fascinate and even though I flashed her phone the same way, she never has had screen responsiveness issues.
Sent from my SCH-I500 using XDA Premium App
johntinman said:
My wife has a fascinate and even though I flashed her phone the same way, she never has had screen responsiveness issues.
Sent from my SCH-I500 using XDA Premium App
Click to expand...
Click to collapse
Excellent information, same method different results. Only difference, the phones themselves.
So far, my Fascinate is running SC 2.9. 2 with absolutely no problems. Did it take a while for those symptoms to start or was it right away?
Sent from my rooted Fascinate running SC 2.9.2 and Tapatalk.
tfotos said:
So far, my Fascinate is running SC 2.9. 2 with absolutely no problems. Did it take a while for those symptoms to start or was it right away?
Sent from my rooted Fascinate running SC 2.9.2 and Tapatalk.
Click to expand...
Click to collapse
Sent from my SCH-I500 using XDA App
It always happened right away (sometimes within a few hours). I should point out this is not developer related. I have the same problems on fully bloated stock roms. I should have mentioned that in the op.
If you Odin back to stock DI01, does it still happen? If so, it sounds like a hardware defect. I, for one, have never seen any screen responsiveness issues at all on my phone, no matter which kernel or rom I'm on.
Sent from XDA Premium on my Super Clean Fascinate
I am having the same issue. Mine is most often around the letters "s" and "k" and it seems intermittent. I was running DJ05 up until a few weeks ago. Then I flashed an EB01 kernel with DarkRevenge, and started to notice this problem. No issues when running DJ05.
ivorycruncher said:
If you Odin back to stock DI01, does it still happen? If so, it sounds like a hardware defect. I, for one, have never seen any screen responsiveness issues at all on my phone, no matter which kernel or rom I'm on.
Sent from XDA Premium on my Super Clean Fascinate
Click to expand...
Click to collapse
Yes, I tried this too. Along with various cocktails of wiping and clearing cache's, no change.
*When I return to any eclair rom it works fine, again why only with froyo??
Just flashed JT's new EC10 kernel and so far no screen responsiveness issues (8+ hours), I'll keep you posted.
Update: my screen responsiveness issues have come back.
Sent from my SCH-I500 using XDA Premium App
I had this problem on some versions of SC 2.8 and at first with 2.9, but now on SC 2.9.2 I haven't had it.
Mine was mostly around letters O, I, N, K, but also sometimes E, R, A, and S. It usually happened after I had already pressed the letter. Take for example this message "I ran into...." I could type the letter I to start, but when I came to it again, it wouldn't register. Same with the letter N.
I had this happen after flashing certain themes. If I ran the ROM themeless, it wouldn't happen.
Factory wiped, ROM (2.9.2) refreshed, and have been running Nitsuj's gb theme with no probs for a few days now.
2.9.2 Voodoo Fascinate
GizmoDroid's CWM fix has stopped my screen resposiveness issues. It's worth a shot. I'm currently running Superclean 2.9.2 voodoo with EB01 radio.
Sent from my Froyonate
I also have the issue. Sometimes it will happen on the lock screen stopping me from unlocking the phone. Same fix though. Had it on all SC roms, AOSP and blackhole.
Sent from my SCH-I500 using XDA App
johntinman said:
GizmoDroid's CWM fix has stopped my screen resposiveness issues. It's worth a shot. I'm currently running Superclean 2.9.2 voodoo with EB01 radio.
Sent from my Froyonate
Click to expand...
Click to collapse
Just did the whole process twice, no change. . . It always seems to be okay at first but a little while later it rears it's ugly head. While in portrait mode if you bisect the phone vertically it is the right hand side that goes dead, the left works fine.
Back to eclair.
Legato525 said:
I also have the issue. Sometimes it will happen on the lock screen stopping me from unlocking the phone. Same fix though. Had it on all SC roms, AOSP and blackhole.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Ditto on mine. After a while it becomes so bad that it happens everytime after it goes to sleep by itself. I would have to reboot to keep it going ok for awhile.
iorikun said:
Ditto on mine. After a while it becomes so bad that it happens everytime after it goes to sleep by itself. I would have to reboot to keep it going ok for awhile.
Click to expand...
Click to collapse
Just tried adryn's EC01 ROM and radio and it still happens....don't bother.
Sent from my SCH-I500 using XDA Premium App
So everyone on here thats had a problem with screen responsiveness has tried a rom/kernel with voodoo lagfix?? If not then give it a try and see if you get the same results.
Keep me Fascinated
SC 2.9.2
EC10 Voodoo Lagfix
Nitro Dark v4
Yes, I've tried Voodoo, nonVoodoo with same issues.
dw77x said:
Just did the whole process twice, no change. . . It always seems to be okay at first but a little while later it rears it's ugly head. While in portrait mode if you bisect the phone vertically it is the right hand side that goes dead, the left works fine.
Back to eclair.
Click to expand...
Click to collapse
Yep same thing here. Not sure when it started but it was most prominent with maybe SC2.8 I think.
It seemed to go away with SC 2.9, but it happens ever now and then.
Always the right side of the screen, simply turn the screen on/off to fix.
Download Advanced Test Card from the market. Give it a try.
Keep me Fascinated
SC 2.9.2
EC10 Voodoo Lagfix
Honeycomb v4 - Animated
I know there are lots of threads about problems with the Atrix including rebooting. What I haven't seen is any consensus on what to do about it. Mine reboots randomly 2 or 3 times a day. Sometimes when I'm on a call or using maps or just sitting idle.
Its happened on and off through all software versions. I'm currently running latest OTA (rooted) but otherwise stock. Is it a software bug to be fixed? Is it bad hardware? Should I seek replacement?
I love my Atrix and am really looking forward to Gingerbread next month. Is it too much to hope that this next update will solve the rebooting issue?
Flame away!
wookiebush said:
I know there are lots of threads about problems with the Atrix including rebooting. What I haven't seen is any consensus on what to do about it. Mine reboots randomly 2 or 3 times a day. Sometimes when I'm on a call or using maps or just sitting idle.
Its happened on and off through all software versions. I'm currently running latest OTA (rooted) but otherwise stock. Is it a software bug to be fixed? Is it bad hardware? Should I seek replacement?
I love my Atrix and am really looking forward to Gingerbread next month. Is it too much to hope that this next update will solve the rebooting issue?
Flame away!
Click to expand...
Click to collapse
What launcher are you using? I ask because Now that I've swapped from LP+ to ADW EX I rarely get a "reboot" anymore. On the other threads you may have read that its possible you are experiencing a graphical shell crash and not a reboot.
I'm currently using apb 3d shell. But also occurred with LP. When the reboot happens, it goes all the way dark and proceeds through the whole boot animation. Seems like a reboot to me.
Sent from my MB860 using Tapatalk
yeah mine randomly reboots too... its happened more lately -- but still only once a week maybe..
It happened once when I had GPS on -- my only guess is there has to be something with incoming/outgoing data where the phone resets itself to clear something out? i dont know jack sh1t about smartphones, but I do know that the times Ive caught it rebooting I noticed the phone being very sluggish and data trickling in even though I'm in a good service area.
wait for the GB update, it is supposed to fix the issue according to the reports. I personally have not had a single reboot using ADW EX.
I had the random reboot issue when I first got my phone in March. The beginning of April I reflashed stock sbf updated to latest version then got gingerblur (currently running gingerblur 4) haven't had a random reboot since I started using gingerblur maybe try that? I don't know that's what fixed it for me I just know it never random reboots since I did this. My two cents take it or leave it
went from leaked gingerbread back to syndicate 1.1.0 and now the autorotate doesn't work, only when i open the keyboard. I did all the fixes, it still doesn't work, any idea how to fix it. I've had 3 epics and never had the problem of it not rotating, always slow rotating or something like that, but never no rotating.
Did autorotate get turned off in the Launcher Pro settings?
Specialksg1 said:
Did autorotate get turned off in the Launcher Pro settings?
Click to expand...
Click to collapse
this is fullyloaded touchwiz and its on.
I wiped data and everything, still doesn't work.
Try this
Did you calibrate the accelerometer first? That might fix it. Mine get kinda wonky after reflashing and especially after using Odin.
i did the calib_yamaha, I calibrated the sensor, nothing did anything, I flashed the gb leak again and it works fine, I flash back to sf 1.1.0 and it doesn't work, so now I'm stuck on the gb leak which is a problem because the phone barely works and keeps dropping calls so I really need to get back to froyo.
robl45 said:
this is fullyloaded touchwiz and its on.
I wiped data and everything, still doesn't work.
Click to expand...
Click to collapse
Are you referring to rotating the home screen, or any and all apps? I might be mistaken, but I don't think TouchWiz rotates the home screen, at least not without sliding out the keyboard...
Also, I would recommend upgrading to SRF 1.2, it's even better than 1.1
Sent from my SPH-D700 using XDA App
styles420 said:
Are you referring to rotating the home screen, or any and all apps? I might be mistaken, but I don't think TouchWiz rotates the home screen, at least not without sliding out the keyboard...
Also, I would recommend upgrading to SRF 1.2, it's even better than 1.1
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
the apps, they don't rotate at all, nothing rotates unless you pop the keyboard out.
This happened to be when I tried a different rom couldn't get it to work for the life of me.
Cleared data, Flashed SR v1.20 and it works now.
fastmikey1969 said:
This happened to be when I tried a different rom couldn't get it to work for the life of me.
Cleared data, Flashed SR v1.20 and it works now.
Click to expand...
Click to collapse
so why would 1.20 be any different that 1.1.0? I actually tried to get 1.20 last night, but the website kept coming up that it could not be found.
robl45 said:
so why would 1.20 be any different that 1.1.0? I actually tried to get 1.20 last night, but the website kept coming up that it could not be found.
Click to expand...
Click to collapse
Well, because 1.2 *is* different than 1.1 - hence the change in version numbers...
Why would you expect the two to be exactly the same? Kind of a silly question
A better question would be, "WHAT is different between the two, that would cause the auto rotate problem in 1.1?"
I don't know that answer, though... I think it may have been tied to the fully loaded version, because I remember experiencing it only once - when I briefly tried fully loaded, before going back to standard
Sent from my SPH-D700 using XDA App
styles420 said:
Well, because 1.2 *is* different than 1.1 - hence the change in version numbers...
Why would you expect the two to be exactly the same? Kind of a silly question
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
why would they be any diferent for rotation?
robl45 said:
why would they be any diferent for rotation?
Click to expand...
Click to collapse
Ok let me clarify my post. Running SR v1.1.1, rotate worked fine. Flashed Revoltion rom, didn't like it, few things didn't work like autorotate.
So I flashed another rom which fixed it, chose SR 1.2 to give it a try. If I flashed v1.1.1 that may have worked also.
so can we get back to the issue, i've tried 1.1.1 and the autorotate doesn't work. it appears to be a froyo issue as it worked fine for months and months and now only gingerbread roms will rotate. could that be because i'm using eh17 modem? i wouldn't think so.
robl45 said:
why would they be any diferent for rotation?
Click to expand...
Click to collapse
Well, one or many of the changes between 1.1 and 1.2 might have affected rotation as a side effect - whatever caused the glitch in 1.1 must have been changed for a completely unrelated reason, and the glitch disappeared...
I think, from what you've reported, that it had something to do with the extras in the fully loaded version - that used a hacked TW, right? 1.2 doesn't have a fully loaded package that I'm aware of... But try the standard version, or just use the most recent version since it *is* better
robl45 said:
so can we get back to the issue, i've tried 1.1.1 and the autorotate doesn't work. it appears to be a froyo issue as it worked fine for months and months and now only gingerbread roms will rotate. could that be because i'm using eh17 modem? i wouldn't think so.
Click to expand...
Click to collapse
It does nut appear to be a froyo issue, because 1.2 is froyo without the issue... In fact, so far the only froyo that appears to have this issue is the fully loaded version of 1.1... Several examples of froyo without the issue vs one with the issue would indicate that froyo is not the problem at all...
Unless I missed the part where you duplicated the issue on several other froyo roms - all I've seen mentioned is SRF 1.1 fully loaded... Have you seen the problem on 1.1 standard edition?
But you are correct about the modem having nothing to do with it
Sent from my SPH-D700 using XDA App
well you could be right, but i've been using the 1.1 for months and months, longer than any other rom and havent had a problem, and I've run many other roms, never had a problem. only time i've ever seen something like this is since running gingerbread leaks, now they work and the old one doesn't, I've flashed that same rom probably 10 times, never had a problem, gone from bonsai to that one and back again, never a problem so I would doubt the rom would have anything to do with it. I'll try the 1.2 if I can get it downloaded. last night the page wasn't coming up.
styles420 said:
Well, one or many of the changes between 1.1 and 1.2 might have affected rotation as a side effect - whatever caused the glitch in 1.1 must have been changed for a completely unrelated reason, and the glitch disappeared...
I think, from what you've reported, that it had something to do with the extras in the fully loaded version - that used a hacked TW, right? 1.2 doesn't have a fully loaded package that I'm aware of... But try the standard version, or just use the most recent version since it *is* better
It does nut appear to be a froyo issue, because 1.2 is froyo without the issue... In fact, so far the only froyo that appears to have this issue is the fully loaded version of 1.1... Several examples of froyo without the issue vs one with the issue would indicate that froyo is not the problem at all...
Unless I missed the part where you duplicated the issue on several other froyo roms - all I've seen mentioned is SRF 1.1 fully loaded... Have you seen the problem on 1.1 standard edition?
But you are correct about the modem having nothing to do with it
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
settings>display>horizontal calibration> place the phone screen upside down on a ledge but with a bit sticking out so you can touch it (like a dresser or desk or counter etc..>calibrate
its sounds strange but it worked for me
Thanks but I did that still didn't work
Perhaps a full odin back to stock froyo, then reinstall everything from there...
I'm wondering if gingerbread updated something that froyo relied on for sensor data (this is a long shot, falling under the category of "I don't see how they're related, but why not?")
Otherwise, it *almost* sounds like a hardware issue - except that you said it works fine on gingerbread... well, unless GB is using a different sensor reading...
Sent from my SPH-D700 using XDA App
styles420 said:
Perhaps a full odin back to stock froyo, then reinstall everything from there...
I'm wondering if gingerbread updated something that froyo relied on for sensor data (this is a long shot, falling under the category of "I don't see how they're related, but why not?")
Otherwise, it *almost* sounds like a hardware issue - except that you said it works fine on gingerbread... well, unless GB is using a different sensor reading...
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
i've only run gb for like 2 weeks, was working fine on froyo, can't understand it. I did download srf 1.2 last night as the site would come up now. so i might play with that this weekend, although the GB is working now and making phone calls without dropping so aside from random reboots its working. kinda makes it hard to sell the thing eventually though if it won't rotate.
well I put on the srf 1.2, autorotate works fine, im perplexed as to why that is since autorotate worked fine for the 6+ months that I ran it and i've never had autorotate stop working on any of the 3 epics i've had and any of the roms. but at least its working now and i have a stable phone.
Howdy,
I've had my tab for a very long time and have always had this issue where when under load the screen would stop responding to touch and I'd have to lock and unlock the device to get it functional again. It didn't matter if it was stock firmware or any of the various roms out there. It always does it. I was hoping that the ICS update would fix whatever the problem was but it does not seem to have done so. Is anyone else seeing this issue on ICS?
This has been an extremely frustrating issue with this device.
Thanks
I have never had any of the issue you described. Are you doing anything in particular that makes the tab freeze like this? So far the ICS custom Rom is just peachy for me. Faster and smoother than the HC versions.
Yes, I also have this problem. I have tried many different roms but problem is more or less the same with all of them (stock, cm9,cm10).
Today I have sent it to Samsung service center, let's hope they can fix it otherwise it goes in the trash.
I only noticed today, first day with official ics. Sometimes the screen is unresponsive, but after I press 2-3 times it works and it doesn't need to lock it.
Sent from my amazing 10.1 galaxy tab
I've has the same issue in starting in Jellybean, where a lock and unlock would fix it.
However, I've had moments where it stopped responding totally, while Android itself was still running fine, and I had to reboot to get it back up. That's happened to me everywhere.
Thanks for the replies. It's happening way more often for me on ICS than it did on HC. It used to happen once or twice a day but it happened 5 times last night. It's almost making the tab unusable. I've talked to a several people around here that have the same tablet and about half mention it happening so it's probably a common issue. As far as I know though no solution.
you can tell when it happens that it's not the os locked up. The volume buttons will show the the volume slider and holding down power will give you the shutdown menu. The screen is just not responding.
Please let me know if Samsung fixes it for you.
L0$t$0ul said:
Thanks for the replies. It's happening way more often for me on ICS than it did on HC. It used to happen once or twice a day but it happened 5 times last night. It's almost making the tab unusable. I've talked to a several people around here that have the same tablet and about half mention it happening so it's probably a common issue. As far as I know though no solution.
you can tell when it happens that it's not the os locked up. The volume buttons will show the the volume slider and holding down power will give you the shutdown menu. The screen is just not responding.
Please let me know if Samsung fixes it for you.
Click to expand...
Click to collapse
Okay, I'll let you know. I´m not very optimistic that they can fix it, but I had to do something. Yesterday I almost break the tab in half when it freeze all the time. After reboot it took about one minute before first lock up and then I had to lock/unlock and after another 30 seconds it freeze again and again and again......
So got pretty pissed and just sent it away.
Will probably take a few weeks to get it back.
Ever since I flashed custom HC and now stock rooted ics, all lag and freezing has disappeared. Before that it was extremely laggy and needed a reboot every day or two as it got extremely slow. And I'm running sslauncher which is generally not a smooth as some others. But now it just flies.
Sometimes a factory reset, wipe and restore of titanium backups helps a great deal.
Sent from my GT-I9300 using xda premium
Kalles Kaviar said:
Okay, I'll let you know. I´m not very optimistic that they can fix it, but I had to do something. Yesterday I almost break the tab in half when it freeze all the time. After reboot it took about one minute before first lock up and then I had to lock/unlock and after another 30 seconds it freeze again and again and again......
So got pretty pissed and just sent it away.
Will probably take a few weeks to get it back.
Click to expand...
Click to collapse
Do you have the 10.1N? I had the exact same issue 2 days ago and I was about to throw the tab outside the window. There are some apps that did the freeze for me...only ones. If this will continue with the stock ics for 10.1N. .. I am going to send it to the service center. I never had such an issue with CM9 or custom roms. Maybe we should all report to Samsung instead of here. They might look into it.
Sent from my GT-P7500 using XDA Premium HD app
Byrana said:
Do you have the 10.1N? I had the exact same issue 2 days ago and I was about to throw the tab outside the window. There are some apps that did the freeze for me...only ones. If this will continue with the stock ics for 10.1N. .. I am going to send it to the service center. I never had such an issue with CM9 or custom roms. Maybe we should all report to Samsung instead of here. They might look into it.
Sent from my GT-P7500 using XDA Premium HD app
Click to expand...
Click to collapse
I have the GT-P7500 and it doesn't matter what rom I have. My problem occur even after a factory reset and no apps installed so I doubt it´s any specific application that makes the freeze.
Will keep you all updated if they do anything about it.
Kalles Kaviar said:
I have the GT-P7500 and it doesn't matter what rom I have. My problem occur even after a factory reset and no apps installed so I doubt it´s any specific application that makes the freeze.
Will keep you all updated if they do anything about it.
Click to expand...
Click to collapse
So, that is even worse than me. Good luck...but still I think we should send the complains towards Samsungs. How else would they know that there's a problem?
I've got the GT-P7510 as well. It's gotten really bad with Jellybean. I always figured it was the touch screen driver being the issue. I know there are ways you can cause it to happen by tweaking driver settings. I really was hoping that the update to the 3.x kernel would cause them to release a new driver and fix it but it looks like in some cases it makes the issues way worse.