Related
Really hoping someone can help me. I have had my Defy for a few months and have always been on a custom SBF but continue to experience problems with the Defy working amazingly for hours and then sometimes I turn the screen on and the Defy is working in some kind of super slow mode and opening anything takes ages, everything does eventually open so it’s not crashed but just going super slow!
I am currently on SBF 3.4.2-177 Nordic but have had the same problem on different SBF’s so either my phone has a hardware issue or its some software I have on my phone, I am currently on Beta 6 of CM7 and have had this issue on other betas of CM7 but have never heard of anyone else with this issue. The phone will sometimes go a whole day without the issue also which is weird. It is not overclocked either. When it goes into what I now call superslow mode I have checked to see what the processor and memory usage are and both are around 60% used not being topped out at all. I have even used StabiltyTest to test the memory and CPU when the problem is occurring and both run through fine.
I really would love to know if anyone else had a similar problem or if they know what is causing it or how I can find out what is causing it without removing every bit of software I use. The only piece of software I use regularly that runs in the background is Juicedefender so I am going to remove this now and see what happens over a few days.
Any help would be amazing
Many Thanks
Bob
Did you install the latest patch for the auto-brightness issue? or Did you turn off the auto-brightness?
Thanks for the fast reply I have already installed the latest patch for auto-brightness issue but still have the problem
Was the phone slow in the stock ROM? I mean that's really wired that the problem appears on each SBF
Hi mys_721x, I only had the stock ROM for a matter of days when I first had the phone so really cant remember but I am thinking I may have to go back to see if I do still have problems if no one else can suggest anything else. Cheers
I have this same problem. Only fix seems to be a reboot whenever it happens
bobdigby said:
Hi mys_721x, I only had the stock ROM for a matter of days when I first had the phone so really cant remember but I am thinking I may have to go back to see if I do still have problems if no one else can suggest anything else. Cheers
Click to expand...
Click to collapse
Same here, my phone suddenly becomes sluggish and unusable. Yesterday it was stuck on 100% cpu usage, I entered the task manager to see what was wrong and there wasn't any application that was using the cpu.
Only solution is to reboot everyday.
Glad to see I am not the only one, yea a reboot does the job sometimes it can be twice a day sometimes I don't see it for a few days, do you guys have juice defender installed by any chance as thats the only real program which stays running in my background which is extra to the roms I have used, cheers for your input, lets hope we can figure out whats going on.
Bob
Sent from my MB525 using XDA Premium App
I had it to in the past. When i tried to lock the phone it took long time and it wouldn't unlock for a wile 1-2min what is verry long if your waiting and afterwards scrolling was lame.
Don't know what I did, but it's gone now. Now only when out of memory(dhuu!)
I think I wiped it cleen, went to a 2.2 and didn't have it again, now on CM.
Do you see in spare parts any apps using mutch cpu?
Weirdest thing that happens to me..
Every hour/day the phone loads up some applications prepared to start when I turn on the phone..
That means that if I close say, tigertext or Skype, the following day, without turning off the phone, hey are running again.. wtf?
EDIT: A way of checking what's using the CPU, if you're on Froyo, is check the application manager to check for services CPU usage
Yea I have no idea what is causing it but little to no cpu usage when it happens, when I lock on cm7 the tv effect for screen off is super slow motion its really strange, did a clean wipe yesterday and did its first slow down today just before post, cheers
Sent from my MB525 using XDA Premium App
Anyone have any luck with this? Mine just seems to be getting worse and worse on CM7.
Update: I've opened a issue for this on Github. You can go there to post new information / symptoms so that hopefully it can be fixed: https://github.com/Quarx2k/android_device_motorola_umts_jordan/issues/204
Hi dasbin,
Since uninstalling Juicedefender from my phone I have not had this issue once, it has now been 3 days which is probably a record for me so I would say that it was causing me the issue, do you have juicedefender installed? I am now using green power it is much better so far.
Cheers
Hi everyone,
I've looked for a solution all over the net, but seems like no one had this problem before (guess i'm a special girl...):
The vibrate feedback when touching the screen just stopped working, in spite of the settings under "settings -> sounds -> vibrate on touch".
It started after an update to AOKP rom - milestone 5 (based on ICS 4.0.4) + Franco kernel nightly r151, but effects all the other roms. Maybe one untouched system file damaged.
I've tried everything: restore from previous nandroid backup, another rom (CM9), another kernel, another launcher, I even wiped everything and flashed new and clean rom-stock from google developers' page. And yet - no vibrate feedback.
The wired thing is that the haptic feedback is working in few specific applications, like the build-in ICS keyboard and the dialer Dialer-One, so it probably not some hardware failure.
All this time there are five softkeys that still have haptic feedback: the buttons of the nav-bar, the button that opens the applications drawer and the google-search widget.
I've tried using "KickBack" instead, but it's too aggressive and very uncomfortable.
PLEASE, PLEASE - Help me!
Same thing happened to me. I had the exact same setup and the haptic feedback went away after I flashed the kernel. Since I've had lots of issues when trying custom kernels, I just restored a nandroid and went back to the kernel included with aokp.
Sent from my Galaxy Nexus using XDA
Restore fixed my issue, so I'm not sure exactly what to tell you.
Sent from my Galaxy Nexus using XDA
taappel said:
Restore fixed my issue, so I'm not sure exactly what to tell you.
Click to expand...
Click to collapse
I've seen some ppl's msgs that even simple reboot fixed their vibrate problem.
Didn't work for me, unfortunately
Some kernels have haptic adjustment, see pic for kernel does.
I'm running Franco 152 and mines fine.
I know trinity kernels lower it
Sent from my Galaxy Nexus using XDA
Sveke said:
Some kernels have haptic adjustment, see pic for kernel does.
I'm running Franco 152 and mines fine.
I know trinity kernels lower it
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
I'm also using Franco kernel, but I don't think this is the problem because i've tried some other kernels and none of them fixed my haptic.
Hi TaliKa
I've just had this problem myself but it happens long after I flashed aokp m5 + franco r152 (too) so I'm not exactly sure what caused it. However after I went to clear my cache and dalvik cache, everything seems fine again.
nich0145 said:
Hi TaliKa
I've just had this problem myself but it happens long after I flashed aokp m5 + franco r152 (too) so I'm not exactly sure what caused it. However after I went to clear my cache and dalvik cache, everything seems fine again.
Click to expand...
Click to collapse
Thanks guys, but as I wrote in the first msg, those actions didn't help.
Is there any pro here who can offer a profound solution that I didn't tried before?
Which system file responsible for the haptic feedback?
Guess I'll have to stuck without haptic feedback...
Sveke said:
Some kernels have haptic adjustment, see pic for kernel does.
I'm running Franco 152 and mines fine.
I know trinity kernels lower it
Click to expand...
Click to collapse
How can I adjust the haptic feedback feature in Trinity kernel?
+1
just wanted to say...exactly the same thing happened to me (started with aokp milestone 5 and vibration gone afterwards...)
im trying several things to get it back...i use it alot (at work and most of the time..its on vibrate)
hopefully we'll find a solution
Yeah this just happened to me too. It was working fine for awhile on AOKP and then all of a sudden it stopped. No idea what happened exactly. I tried whiping everything and restoring CM9 but that didn't work either. I thought maybe hardware but the phone vibrated on boot so it isn't that. Hopefully we find a fix...
takomar said:
+1
just wanted to say...exactly the same thing happened to me (started with aokp milestone 5 and vibration gone afterwards...)
im trying several things to get it back...i use it alot (at work and most of the time..its on vibrate)
hopefully we'll find a solution
Click to expand...
Click to collapse
Dacian said:
Yeah this just happened to me too. It was working fine for awhile on AOKP and then all of a sudden it stopped. No idea what happened exactly. I tried whiping everything and restoring CM9 but that didn't work either. I thought maybe hardware but the phone vibrated on boot so it isn't that. Hopefully we find a fix...
Click to expand...
Click to collapse
unfortunately I didn't get any solution yet. Realy depressing.
I promise to update about any progress, and hope you'll both do the same...
Just don't give up! it isn't hardware thing, so there must be solution somewhere.
TaliKa said:
unfortunately I didn't get any solution yet. Realy depressing.
I promise to update about any progress, and hope you'll both do the same...
Just don't give up! it isn't hardware thing, so there must be solution somewhere.
Click to expand...
Click to collapse
im starting to believe its a hardware issue (well at least for me) i mean i dont even get a vibration upon booting or turning off the phone...and i even went back to full stock...same thing
maybe it might have been some software issue that led to the overburning of the motor(doubt that though)
what is weird though is that the same scenario happened to us so im lost...
maybe i should start talking to samsung for my replacement
meanwhile...im very open to suggestions that might help my case
hope we find something soon...u guys, does it vibrate at all?when u turn on ur phone?turn off? unlock ?
takomar said:
hope we find something soon...u guys, does it vibrate at all?when u turn on ur phone?turn off? unlock ?
Click to expand...
Click to collapse
Yes, it vibrates at boot and also when using application with it's own vibrate settings, like "dialer one" for example.
Did you try using KickBack just to check the hardware?
if it's some hardware issue, maybe you can apply to your warranty supplier about that, just flash stock rom and relock your device before.
TaliKa said:
Yes, it vibrates at boot and also when using application with it's own vibrate settings, like "dialer one" for example.
Did you try using KickBack just to check the hardware?
if it's some hardware issue, maybe you can apply to your warranty supplier about that, just flash stock rom and relock your device before.
Click to expand...
Click to collapse
thats what im gonna do i guess...such a sad day...
i couldnt find KickBack, its not available in my accessibility menu nor in my market (i live in France)
i tried googling an apk but nothing for android 4.0
do you have a link for it?
takomar said:
thats what im gonna do i guess...such a sad day...
i couldnt find KickBack, its not available in my accessibility menu nor in my market (i live in France)
i tried googling an apk but nothing for android 4.0
do you have a link for it?
Click to expand...
Click to collapse
I couldn't find it in play store either, but i download it from here:
http://code.google.com/p/eyes-free/downloads/detail?name=kickback-v1.1.1.apk
works fine for me.
TaliKa said:
unfortunately I didn't get any solution yet. Realy depressing.
I promise to update about any progress, and hope you'll both do the same...
Just don't give up! it isn't hardware thing, so there must be solution somewhere.
Click to expand...
Click to collapse
Good to know. I went ahead and flashed the base image and it restored vibration, then I rooted and flashed AOKP again. It worked for about that day and then this morning when I woke up the vibration is gone again. I'm almost positive it's AOKP's software. I'll test another ROM (Android Revolution) for a day and see if it happens again.
Dacian said:
I'm almost positive it's AOKP's software. I'll test another ROM (Android Revolution) for a day and see if it happens again.
Click to expand...
Click to collapse
Which kernel do you use? and did you set the quite hours on?
If you succeed to restore the vibrate, i'd like to hear exact instructions how to do that, including links to download the boot image, if you plesae...
I have tried searching for this problem but I must be using the wrong terms... so sorry in advance if I missed a post that addressed this issue.
My sprint S3 does this twitchy/glitching thing on every touchwhiz based jellybean rom (does not do it on TW ICS ROMS) I have tried. It basically makes it nearly impossible to do sliding animations, IE it can actually get stuck and start flashing halfway between screens, or when pulling down the top menu, however you can open new programs just fine if you are already on the right screen for them. Luckily it does not do this all the time, but when it happens it keeps doing for 10 minutes or so and its annoying as hell.
I figured this must be a rare issue even though it effects both my wifes phone and mine, since I have never read anything about it, however I just got a new replacement phone and it does the exact same thing, even on dead stock TW JB ROM.
Oddly enough I discovered last night that if I turn on my screen filter app it stops completely, but it starts right back up when I turn off screen filter..... any ideas how to fix this?
Try grabbing cache clear from the play store and set it to run every 12 hours. It helped my phone a good bit.
Sent from my SPH-L710 using xda premium
No one else ever has this issue?
joelespinoza said:
No one else ever has this issue?
Click to expand...
Click to collapse
I had it dude, but it was just on the CleanBean ROM, it was annoying as hell!
So I changed the ROM, Its weird that its happening on a Stock ROM, any suspicious app?
Im new in this nexus section...i'm asking why my galaxy nexus sometimes reboots? It has the latest 4.2.2 android version stock...it isnt the update, i think, because also before this happen...and when it reboots there's like a opened locket under the google logo....who can help.me? I tried also the nexus toolkit...but when i try to do something with fastboot the program says WAITING DEVICE forever...
Guys, please help!! Its really urgent!
Hi,
I think there are two reasons for random reboots:
1- overheating
2-lack of ram (many running proceses, so ram gets full, so it reboots.
Press the thanks button if I helped
blakstar said:
Hi,
I think there are two reasons for random reboots:
1- overheating
2-lack of ram (many running proceses, so ram gets full, so it reboots.
Press the thanks button if I helped
Click to expand...
Click to collapse
No, even when the battery isnt hot it reboots!!
and it is without any apps installed, only stock apps!! I did also a factory reset from settings..but nothing happened...
Searching on net, i read that the opened locket is the bootloader....is that causing random reboots? If yes, how to relock with toolkit? Beacause it says me WAITING DEVICE
isko95 said:
No, even when the battery isnt hot it reboots!!
and it is without any apps installed, only stock apps!! I did also a factory reset from settings..but nothing happened...
Searching on net, i read that the opened locket is the bootloader....is that causing random reboots? If yes, how to relock with toolkit? Beacause it says me WAITING DEVICE
Click to expand...
Click to collapse
No, unlocking the bootloader shouldn't do this. I have an unlocked bootloader, and I have this phone(xperia arc) for 5 months and I only had one random reboot and it was definitely because of lack of ram
blakstar said:
No, unlocking the bootloader shouldn't do this. I have an unlocked bootloader, and I have this phone(xperia arc) for 5 months and I only had one random reboot and it was definitely because of lack of ram
Click to expand...
Click to collapse
Yes but im talking about NEXUS and maybe its different!!
I used to have that happen all the time. I used to think that the phone sucked but my husband never had that happen with his. I compared the apps and wiped my phone, only installed what he had on there. It still happened. I was really beginning to get mad but I wiped it again. I Installed things one by one only allowing myself to install a new app only after it had gone a week with no nonsense. Yes, this was a painful process but I found the cause of my random reboots. I use Handcent. That alone isn't the cause. When I would get new sounds for my GN, I would have the option of making them a ringtone or a Handcent notification among other things. If I made Handcent notifications, that seemed to cause the problem. If I move a sound into the notifications folder and assign it to contacts in Handcent, everything has been fine.
I don't know if this helps your problem but some settings could affect unexpected things. Good luck!
Sent from my Xoom using xda premium
3devious said:
I used to have that happen all the time. I used to think that the phone sucked but my husband never had that happen with his. I compared the apps and wiped my phone, only installed what he had on there. It still happened. I was really beginning to get mad but I wiped it again. I Installed things one by one only allowing myself to install a new app only after it had gone a week with no nonsense. Yes, this was a painful process but I found the cause of my random reboots. I use Handcent. That alone isn't the cause. When I would get new sounds for my GN, I would have the option of making them a ringtone or a Handcent notification among other things. If I made Handcent notifications, that seemed to cause the problem. If I move a sound into the notifications folder and assign it to contacts in Handcent, everything has been fine.
I don't know if this helps your problem but some settings could affect unexpected things. Good luck!
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
I did factory reset twice from device's settings, but nothing.
no one who can help? wow!!
I had random reboots on my Verizon GN running the OTA 4.1.1. I got so fed up with it that I went back to 4.0.4. I have had no problems or reboots since doing this.
Are you running Chrome or the stock browser? I've always had the random restarts on my N10, but only started seeing them on my GN after I started using Chrome around the time 4.2.2 came out.
gforce1963 said:
I had random reboots on my Verizon GN running the OTA 4.1.1. I got so fed up with it that I went back to 4.0.4. I have had no problems or reboots since doing this.
Click to expand...
Click to collapse
Reaally? How did you get back to 4.0 ics?
OP, read the return to stickied thread on general forum by efrant, if your problems still happen after restoring back to stock through fastboot, then you may have faulty hw.
Sent from my Nexus
bk201doesntexist said:
OP, read the return to stickied thread on general forum by efrant, if your problems still happen after restoring back to stock through fastboot, then you may have faulty hw.
Sent from my Nexus
Click to expand...
Click to collapse
why when i try to do something with nexus toolkit it says waiting for device?
Heeeeeeeeelp heeeeeeeeeeelp!
why no one can help in here?!?!?!
Do dmesg or logcat, maybe we can help resolving your problem or you can ask your phone service.
Sent from my MT27i using my finger
ahlulnugraha said:
Do dmesg or logcat, maybe we can help resolving your problem or you can ask your phone service.
Sent from my MT27i using my finger
Click to expand...
Click to collapse
How to make logcat??
Really a few people answers!
Bk201 handled it as always. Follow his suggestion. If that can't help you it must be PEBKAC.
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