Anyone else have this problem? I just got this phone like not even a week ago and it just stopped working. It will work like 10-15% of the time. Should I send it in or what should I do? would it be a software problem Like the rom I installed? I doubt it but I installed the AokP with franco kernal would that be it?
I have aokp 28 with Franco kernel and I've never experienced this problem. If your power button is giving you issues go to settings in rom control and use volume wake with this feature I never use my power button.
Sent from my Galaxy Nexus using xda premium
beiker44 said:
Anyone else have this problem? I just got this phone like not even a week ago and it just stopped working. It will work like 10-15% of the time. Should I send it in or what should I do? would it be a software problem Like the rom I installed? I doubt it but I installed the AokP with franco kernal would that be it?
Click to expand...
Click to collapse
1) Flash another ROM. Still broken?
a) No?: It was your ROM
b) Yes?: Go to #2
2) Restore to stock. Still broken?
a) No?: Custom ROMs borked it.
b) Yes?: Go to #3
3) Return the phone / warranty claim.
Had this issue. A little different since it was the volume rocker giving me a headache. Volume up suddenly was hit or miss. Then became totally unusable. Brought it back to the store, showed the problem, went home with a brane new Gnex.
Sent from my Galaxy Nexus using Tapatalk
Related
have i got the volume bug if my phone hangs and then reboots every time i touch volume up or down when the screen is on? Samsung insist that its the same thing and i need to wait for the update but i can't see anyone else describing that the problem causes a reboot, and my volume has never actually turned down on it's own as far as i can tell.
That sounds different altogether.
Sent from my Galaxy Nexus using XDA App
matt2053 said:
That sounds different altogether.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Thats what i suspect. Its just a pain to have been waiting for 4 days for something that probably wont fix anything and then to have to start the whole thing over again with samsung. O well
stanleywinston said:
have i got the volume bug if my phone hangs and then reboots every time i touch volume up or down when the screen is on? Samsung insist that its the same thing and i need to wait for the update but i can't see anyone else describing that the problem causes a reboot, and my volume has never actually turned down on it's own as far as i can tell.
Click to expand...
Click to collapse
Deal with the retailer you bought the phone from, and get a replacement from them.
oscillik said:
Deal with the retailer you bought the phone from, and get a replacement from them.
Click to expand...
Click to collapse
I'll give it a go. Im guessing they wont do a doorstep swap like i'd get from t mobile though. Hopefully i wont be without it for long. In our short time together i've grown quite attached to this phone (and almost got used to not touching the volume button)
Couple of questions (you may have already done these -apologies if you have)
Have you tried a factory reset? If not, maybe worth trying it, could be an app doing wierd things.
Also, try running a logcat trace when replicating the issue - see if it helps point in the direction of the issue.
Does the phone still crash when you're in the bootloader? (This _may_ help to rule out application related issues)
I have tried a factory reset. Weird thing is that im pretty sure that it didnt do it for the first few hours that i was playing with it. It was just at the point that i had it all set up that i first noticed it so assumed it was a rouge app and did a factory reset. When it rebooted i signed in and hit volume and it crashed so its definately not an app.
I almost believed that it was the normal volume bug because if i go somewhere more remote in the house, away from all electrical stuff, i can hammer at the buttons for a while before it crashes so maybe ive just got a more extreme version of the bug. Just noone else seems to have anything close. Volume control works fine in a call and when the screen is off but i havent tried in bootloader yet. I'll give it a go
Hey guys,
I don't know whether anyone encounter this before. But my phone sometimes not frequently will just blackout by itself. The saving grace is that, I do not need to pull the battery to get it working again. I just need to hold on power button for it to reboot again.
Anyone facing this issue before?
By the way, I'm on stock rom and kernel. 4.0.2 here.
Thanks in advance.
bryant_16 said:
Hey guys,
I don't know whether anyone encounter this before. But my phone sometimes not frequently will just blackout by itself. The saving grace is that, I do not need to pull the battery to get it working again. I just need to hold on power button for it to reboot again.
Anyone facing this issue before?
By the way, I'm on stock rom and kernel. 4.0.2 here.
Thanks in advance.
Click to expand...
Click to collapse
unlocked and rooted? I would do a factroy reset and see if that would solve your problem. It could be an app you downloaded.
I'm not rooted at all. Stock rom and kernel.
Anyone has any idea on this?
I've had similar problems but i'm rooted any it was a problem with the governor not bringing the phone out of sleep. I think it was the hotplug feature or something.
Not sure what it'd be on stock, sorry!
Sent from my Galaxy Nexus using Tapatalk
i've had my gnex for over 3 weeks and yesterday was the first and only time that i've experienced random shutdowns and reboots. i think i know the culprit.
i was at a location known spotting vzw 3G coverage. no 4G. i had issues getting reception w/ my moto droid phones at this location. this is the first time i've been there w/ my gnex. the gnex shutdown and rebooted twice. a third time, the reboot at stuck at the intro video. had to pull battery.
since i came home to good 4G/3G coverage, my phone has not acted up once.
me thinks random reboots is radio related.
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 just upgraded my old Evo 4G to this phone about 3 weeks ago. On my Evo I was running CM7 and loved it. I tried installing a version of CM7 from a different website and after 5 minutes of running without any issues, my menu button started to glitch out and press itself. I couldn't use any of the other buttons while this was happening. I eventually shut the phone off and restored back to stock. After that I came back to this website and tried flashing Cyanogenmod 9 Alpha 6 and MIUI. Those both had the same issue. I have no issues using stock EL29. Is it just my phone or is this a common E4GT issue? Is there anything I can do to get around this? Thanks in advance.
It's a common problem on some ET4G phones. I'm on my third(bricked 2) and mine does it on every ROM I've tried, even stock. My first two phones didn't do this, but this one was driving me nuts. It was almost unusable. I had to run AOKP that has the option to remove use of the hardware buttons and just use the on screen nav buttons. Since doing that, I've had no more annoying constant menu pop ups. The downside is that I can't use any of the cool TW roms that are available, but at least I can use my phone. You could take it to your local Sprint store and get them to give you a replacement if you can duplicate it while you're there. I decided to keep mine because I've already gotten two replacements and I'm just tired of dealing with it.
Rats! That's not the answer I was hoping to read. I was hoping it was just a kernel issue and not an actual problem with the phone itself
I have d this problem still waiting for a replacement
Sent from my SPH-D710 using Tapatalk 2
Well it's good to know that this issue isn't my fault! I will take it to a Sprint store and see what they can do for me.
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