Hi,
I recently got my GS4 for Sprint about a month ago, and have it rooted under the ShabbyPenguin 3.4.0 kernel running Android 4.2.2.
I noticed that the Bluetooth is intermittent in my car, many times skipping out back to handset mode, and WiFi is not strong, not picking up my AP from 10-15 feet away.
I was wondering if this could be a software/kernel root issue or a defect in the hardware.
Would Sprint be able to fix this if I unroot the phone? I've had it for about a month now.
Thanks in advanced!
That definitely sounds odd. Was it happening before you rooted? You could also try flashing a different ROM and kernel and see if that makes a difference.
tinkleondabeach said:
Hi,
I recently got my GS4 for Sprint about a month ago, and have it rooted under the ShabbyPenguin 3.4.0 kernel running Android 4.2.2.
I noticed that the Bluetooth is intermittent in my car, many times skipping out back to handset mode, and WiFi is not strong, not picking up my AP from 10-15 feet away.
I was wondering if this could be a software/kernel root issue or a defect in the hardware.
Would Sprint be able to fix this if I unroot the phone? I've had it for about a month now.
Thanks in advanced!
Click to expand...
Click to collapse
NickMachiavelli007 said:
That definitely sounds odd. Was it happening before you rooted? You could also try flashing a different ROM and kernel and see if that makes a difference.
Click to expand...
Click to collapse
Thanks for your reply.
I actually rooted the device a day or two after I got it so I was never able to fully test the BT/WiFi. I haven't used any other roms, I saw that the only working kernel was shabbypenguin's since all the other ones had root lock or something. (i don't really know what I'm talking about) Would taking a backup of the rom restore everything including kernels?
I would think it's a hardware issue since the BT/Wifi is probably on the same chip, but what are the chances of a hardware defect on these mass produced phones? :\
Thanks
Please read forum rules before posting
Questions and help issues go in Q&A and help sections
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
I bet lots of people are running the shabbypenguin kernel, am I the only one having this problem? :'(
tinkleondabeach said:
I bet lots of people are running the shabbypenguin kernel, am I the only one having this problem? :'(
Click to expand...
Click to collapse
Just a solution to this issue: Phone was faulty, the wifi/bt radio antenna was an issue. Had to warranty $50 for a refurb'd replacement, f'ing Sprint
Related
hello guys I have a nexus with one gingerbread 2.3.4 and when I use the 3G network after 2-3 minutes the phone restarts. with this bug I can not use Internet
any ideas? Thanks!
Yes. Me to.
What ROM and/or kernel combo you guys using?
I have the stock rom ota gingerbread 2.3.4, nothing changed, full stock. I recently tried miui 1.5.20 the problem is the same. may be a hardware problem?
Does the phone get hot to the touch on the back? Does the phone still reboot if you turn off 3g data and you go exclusivly Wifi?
Had the same issue with my old Nexus 1. Called HTC support and they immediately said it was a defective board. RMA'd and got refurb, but at least it does not reboot when I use 3g.
Good luck.
thanks jhsiao36, think if I update the radio version 5.12.00.08 can change something or brought it in for service?
poltor said:
thanks jhsiao36, think if I update the radio version 5.12.00.08 can change something or brought it in for service?
Click to expand...
Click to collapse
I didn't help for me. I tried the 5.12.00.08 radio and it suffered from the same 3g reboots. But when I disabled 3g and used Wifi, never suffered from reboots.
If the phone is still under warranty, definitely encourage you to call them. HTC's customer and tech support is the best I've ever seen. They replaced it no questions asked, even though my phone is rooted and bootloader unlocked.
jhsiao36 said:
HTC's customer and tech support is the best I've ever seen. They replaced it no questions asked, even though my phone is rooted and bootloader unlocked.
Click to expand...
Click to collapse
+1 They are awesome to deal with. It really makes me sad that they are starting to lock down their phones, because I won't buy a phone if I can't run custom ROMs on it.
But with the radio, I highly doubt flashing to 5.12 would help. Google released the 5.08 radio with the OTA update to Gingerbread. If 5.12 was any better, I'm sure they would've included it. There had to have been a reason they stuck with 5.08.
If you aren't afraid of losing anything, or already made backups, you could try the passimg method of giving you a completely stock install. See if the problem occurs with that as well. This would rule out software vs hardware.
No one can really solve it?
JetChung said:
No one can really solve it?
Click to expand...
Click to collapse
I really don't think it can be resolve without sending it back to HTC for a replace/repair. As I said in my previous posts, I've tried 3 different ROMs - stock, cyanogenmod 6 and 7 - all exhibit the same issue - reboot when on 3g, but perfect if on Wifi. And yes, it will reboot even on a freshly install ROM (no apps installed).
HTC knows of this issue and they will replace/repair. I got a refurb and it works perfectly - stock, cyanogenmod 6 or 7.
Sorry, probably not the answer you wanted to hear, but search on <insert your favorite search engine> and you will find that this is a fairly widespread problem.
Thank you for your answer! It does not work, had sent a factory repair.
After several tests, on Monday I sent the phone in for service. I think it's a hardware problem, maybe a bad batch of motherboards.
my S / N: HT05... and your?
I will tell you just back from assistance.
Did you ever overheat it? I believe that the N1 has a problem if you really push it that it can overheat. Once it happens once it will happen again and every time it takes less and less to cause the reboot. Eventually it reboots just with 3G.
I was running mine in the car-mount with GPS, Google Maps (3G), screen on brightest, on a hot summer day while charging ... and it rebooted. Didn't think much of it but then it started rebooting every time I used GPS and charging.
In the end it was pretty near useless ... rebooting all the time. I sent it in twice (the first time they couldn't reproduce the problem) and the second time they replaced the board. Problem solved.
Now I am very careful not to overheat it.
I've been waiting a month to ask for help cause i'm stubborn and wanted to fix it on my own, but now i'm over it and accept the fact i need help haha. Basically, I've had this evo running CM7 and Destroyer with savage-zen kernels since january, i updated CM7 from a nightly to a RC and ever since i've been getting random reboots, i've tried everything, restoring my original nandroid, running stock RUU's and a combo of a million different roms and kernels with no luck, also updated radio/prl/NV. I've exhausted my resources now and dont know what else too try, anyone have any suggestions?
TimidRat said:
I've been waiting a month to ask for help cause i'm stubborn and wanted to fix it on my own, but now i'm over it and accept the fact i need help haha. Basically, I've had this evo running CM7 and Destroyer with savage-zen kernels since january, i updated CM7 from a nightly to a RC and ever since i've been getting random reboots, i've tried everything, restoring my original nandroid, running stock RUU's and a combo of a million different roms and kernels with no luck, also updated radio/prl/NV. I've exhausted my resources now and dont know what else too try, anyone have any suggestions?
Click to expand...
Click to collapse
So completely unrooted/returned to stock it STILL random reboots?
If so, sounds like a hardware related issue.
Yeah went all the way back to unrooted s-on, I was starting to think it was hardware related, thanks mattykins
I can confirm that this is a hardware issue. My first EVO had the exact same problem you had, and continued to get worse and worse to the point where it would cycle 10 times before actually staying on for a little bit.
I called Sprint and told them that I thought my phone was defective, and when I explained the problem they said it was a known issue and that it would be replaced free of charge.
A friend of mine is actually dealing with this very thing right now and he said that Sprint is now shuffling people off to HTC for defective phone replacements. If you are within 1 year of buying the phone it should be free, as per the manufacturer's warranty.
I also had this happen and got it replaced. Now I'm without root but at least my phone works. It's definitely hardware related.
Sent from my PC36100 using XDA App
I had the same problem, no matter the rom or kernel, it would reboot and get stuck in bootloop. I finally gave in and went to sprint, turned out it was something with the hardware that would heat up my battery and then when it got to a certain temperature it would cause it to reboot. Definitely take it into sprint.
Sent from my PC36100 using XDA App
Thanks everyone, but if I take it to Sprint I have the feeling ill still have to pay 100 cause the screen has a crack across the bottom.
TimidRat said:
Thanks everyone, but if I take it to Sprint I have the feeling ill still have to pay 100 cause the screen has a crack across the bottom.
Click to expand...
Click to collapse
Try anyway.
Technically you would win legally because the crack has nothing to do with the issue you're having thus the warranty is valid.
(Although I guess they could claim you must have dropped it and that could have damaged something internal)
But the worst case scenario is they say you have to pay the $100 to get a new one and if you don't you still have your phone.
The best case, they fix or replace it.
Either way, its worth a shot.
Greetings my nexus brothers.
I post here today to inquire of a strange phenomenon that has befallen my device.
You see, when I try to make calls... I don't hear anything from the earpiece unless i plug in my headphones.
But before you jump to conclusions, I too thought it was a simple earpiece hardware failure however, when I made calls through the vonage app the sound came through the earpiece like normal.
I am currently running the device on android 4.2.2 with the ParanoidAndroid rom and mako kernel.
Does any of you have a clue as to what might be the issue?
ketonkss4 said:
Greetings my nexus brothers.
I post here today to inquire of a strange phenomenon that has befallen my device.
You see, when I try to make calls... I don't hear anything from the earpiece unless i plug in my headphones.
But before you jump to conclusions, I too thought it was a simple earpiece hardware failure however, when I made calls through the vonage app the sound came through the earpiece like normal.
I am currently running the device on android 4.2.2 with the ParanoidAndroid rom and mako kernel.
Does any of you have a clue as to what might be the issue?
Click to expand...
Click to collapse
what about trying an other kernel...?
regards
did you update your radio? you cant use the old one with 4.2.2 roms. you absolutely must update to the 4.2.2 radio.
molesarecoming said:
did you update your radio? you cant use the old one with 4.2.2 roms. you absolutely must update to the 4.2.2 radio.
Click to expand...
Click to collapse
you are absolutely right when it comes to the older 33 radio. but ive had a few people report that the even older 27 radio is working with 4.2.2 roms. i havent tried, so i cant confirm it myself.
It seems strange however, that a radio problem would cause an earpiece issue... because I am still able to make calls, but I cant hear out of the phones earpiece unless i make internet calls
at any rate im going to try to reflash paranoid android and if this doesnt work I will try the radio suggestion
ketonkss4 said:
It seems strange however, that a radio problem would cause an earpiece issue... because I am still able to make calls, but I cant hear out of the phones earpiece unless i make internet calls
at any rate im going to try to reflash paranoid android and if this doesnt work I will try the radio suggestion
Click to expand...
Click to collapse
i dont think that its as much a radio issue as it is a driver issue. this started happening when the rest of the 4.2.2 drivers were released last week.
simms22 said:
i dont think that its as much a radio issue as it is a driver issue. this started happening when the rest of the 4.2.2 drivers were released last week.
Click to expand...
Click to collapse
You must be right... I tried reflashing Paranoid Android (Latest Version), Tried the Franco kernal, and flashed the 33 radio img.. but its still the same behavior... phone makes calls but earpeice is silent.
Do you think i should reflash the drivers?
ketonkss4 said:
You must be right... I tried reflashing Paranoid Android (Latest Version), Tried the Franco kernal, and flashed the 33 radio img.. but its still the same behavior... phone makes calls but earpeice is silent.
Do you think i should reflash the drivers?
Click to expand...
Click to collapse
no. try the 27 radio, i hear people have luck with it and 4.2.2 roms. if not, then youll need the 48 radio http://forum.xda-developers.com/showthread.php?t=2087227
ketonkss4 said:
It seems strange however, that a radio problem would cause an earpiece issue...
Click to expand...
Click to collapse
those that had old radios all reported they couldnt make calls anymore. they could not hear the other person speaking. sounds awfully familiar, right? when aosp 4.2.2 was released and the kernel was still 4.2.1 the radio even caused stuff like autobrightness to fail - so you never know how deeply it affects your system.
point is, you just cant use your radio anymore, they're obsolete. some people on xda have suggested that google has deliberately made the 4.2.2 compounds mandatory to make you abandon the lte capable radios. so you basically have the choice now, stay for ever on 4.2.1 or update.
molesarecoming said:
those that had old radios all reported they couldnt make calls anymore. they could not hear the other person speaking. sounds awfully familiar, right? when aosp 4.2.2 was released and the kernel was still 4.2.1 the radio even caused stuff like autobrightness to fail - so you never know how deeply it affects your system.
point is, you just cant use your radio anymore, they're obsolete. some people on xda have suggested that google has deliberately made the 4.2.2 compounds mandatory to make you abandon the lte capable radios. so you basically have the choice now, stay for ever on 4.2.1 or update.
Click to expand...
Click to collapse
...Yeah I think you make a good point. Damn, and here I was trying to hold out until t-mobile rolled out their LTE so I could finally make use of the LTE chip.
I suppose ill just have to upgrade the radio... I could always go back right?
Well hopefully Google releases a LTE capable, 32 gig Nexus 4 and stops toying with us... lord knows I would give so many things for that.
Did you find it cleared multi-touch issues or improved it at all? Some people say Cyanogenmod fixed things, but I'd just like more confirmation that it'd make a difference
fedreta said:
Did you find it cleared multi-touch issues or improved it at all? Some people say Cyanogenmod fixed things, but I'd just like more confirmation that it'd make a difference
Click to expand...
Click to collapse
I also have this problem. Tomorrow planning to flash on ParanoidAndroid or Cyanogenmod. Tomorrow otpishus the results.
**Menos** said:
I also have this problem. Tomorrow planning to flash on ParanoidAndroid or Cyanogenmod. Tomorrow otpishus the results.
Click to expand...
Click to collapse
I've never tried flashing a ROM before, my device is already unlocked/rooted. What do you do exactly to flash Cyanogenmod?
Just installed Cyanogenmod and saw that the problem is not solved. I fear starting to appear that the problem is hardware. Now have to wait for an update from Google.
IIRC, the screen issue is due to a firmware config that cannot be addressed by flashing a new ROM. An updated firmware package will have to be pushed via Google.
Tony_YYZ said:
IIRC, the screen issue is due to a firmware config that cannot be addressed by flashing a new ROM. An updated firmware package will have to be pushed via Google.
Click to expand...
Click to collapse
Did Google confirm this was the problem? I just need to make sure it is their problem before I go and swap it out since I have 1 more week to decide
fedreta said:
Did Google confirm this was the problem? I just need to make sure it is their problem before I go and swap it out since I have 1 more week to decide
Click to expand...
Click to collapse
From what I have seen, google is aware of all the big bugs and is working on a big update. Looks like screen flicker, multitouch, overheating, corrupted images on startup, gps, wifi performance etc are going to be fixed in a bugfix update. All the nexus devices start their lives like this, one of the few annoying things about being a nexus fanboy, you get to enjoy the bugs before anyone else gets to.
http://www.engadget.com/2013/08/13/2013-nexus-7-multitouch-bug/
fedreta said:
Did Google confirm this was the problem? I just need to make sure it is their problem before I go and swap it out since I have 1 more week to decide
Click to expand...
Click to collapse
I'm trying to remember the source of my information. But it was stated a few times that the second OTA is what causes the screen issues after powering your device up for the first time.
Tony_YYZ said:
I'm trying to remember the source of my information. But it was stated a few times that the second OTA is what causes the screen issues after powering your device up for the first time.
Click to expand...
Click to collapse
Yeah I remember this too, something about the kernel supplying not enough voltage to the touchscreen in an attempt to improve battery life. This has to be a kernel bug.
Try flashing a different kernel as that is what bridges hardware and software.
Aren't all kernels based on stock?
Sent from my Nexus 7 using xda premium
uprightbass360 said:
From what I have seen, google is aware of all the big bugs and is working on a big update. Looks like screen flicker, multitouch, overheating, corrupted images on startup, gps, wifi performance etc are going to be fixed in a bugfix update.
Click to expand...
Click to collapse
I would love to see that happen, but where do you see Google acknowledged and commited to fix all those problems?
If it is just speculation, that doesn't help folks who are within their return period and can get out instead of playing guinea pig.
sfhub said:
I would love to see that happen, but where do you see Google acknowledged and commited to fix all those problems?
If it is just speculation, that doesn't help folks who are within their return period and can get out instead of playing guinea pig.
Click to expand...
Click to collapse
According to the minions on their google+ "they are working on these issues". I by no means know that google is in fact going to be able to fix all of these issues, nor am I able to guarantee what they do, but I don't see that by repeating what their reps are saying is pure speculation. I think that judging by past examples anyone who has bought a nexus device at launch has either knowingly or unknowingly already agreed to be a guinea pig. In the end I am one of the last people to say that someone shouldn't return a defective piece of hardware, but it seems a lot of the issues people are having are being misdiagnosed as hardware issues when in fact they can (and most likely will) be fixed by an OTA.
I can dare to say that the issue is present in Android 4.3 affecting any device running it even Custom Roms I'm on CyanogenMod 10.2 on my d2spr (S3 Sprint) and the issue is present there too. Also that causes reboots too. I could be wrong too.
Sent from my SPH-L710 using Tapatalk 4
Team SXTP
Also the jss build is giving problems in the nexus 4 thread
Sent 4rm my Nexus 7 FLO... Only thing missing is O.G. N7's development...
uprightbass360 said:
Looks like screen flicker, multitouch, overheating, corrupted images on startup, gps, wifi performance etc are going to be fixed in a bugfix update.
Click to expand...
Click to collapse
uprightbass360 said:
According to the minions on their google+ "they are working on these issues". I by no means know that google is in fact going to be able to fix all of these issues, nor am I able to guarantee what they do, but I don't see that by repeating what their reps are saying is pure speculation.
Click to expand...
Click to collapse
No problem with repeating what they are saying, but you seem to have commited them to more than they are saying in their personal comments, not those as official reps.
IMO everyone should get accurate information so they can evaluate for themselves whether it is worth the risk to keep it or just to return the unit.
Personally I think the random reboots and GPS can be addressed in software and the multi-touch is probably 50/50 something that can be worked around in software, but everyone has their own tolerance levels for these kind of issues and "are looking into it or are working on it" and "going to be fixed" are quite different levels of commitment.
I'm sorry but what issues are you having because I exchanged my first n7 because I was having multitouch stuttering and issues with unresponsiveness which made the device unusable. The new device is okay.
I've been having a bunch of GPS/nav issues. Yesterday I was driving and using the nav, and every time I made a turn, google navigation froze for about a second and thought I was still going straight instead of correctly following me around the turns. This is a REALLY serious problem when there are many successive quick turns - I've missed quite a few turns due to this BS.
On top of that, it frequently takes a long time to lock into a GPS signal...way longer than it should be taking.
I remember there being a GPS mod on my galaxy nexus... is there any similar mod for the note 3?? If that doesn't work some sensor(s) must be faulty because the phone is virtually brand new and this is just unacceptable for phone of this caliber. This has been going on since I got the phone last year.
Has anyone else had similar issues?
I'm still on stock rooted 4.3.
TIA!
siciliano777 said:
I've been having a bunch of GPS/nav issues. Yesterday I was driving and using the nav, and every time I made a turn, google navigation froze for about a second and thought I was still going straight instead of correctly following me around the turns. This is a REALLY serious problem when there are many successive quick turns - I've missed quite a few turns due to this BS.
On top of that, it frequently takes a long time to lock into a GPS signal...way longer than it should be taking.
I remember there being a GPS mod on my galaxy nexus... is there any similar mod for the note 3?? If that doesn't work some sensor(s) must be faulty because the phone is virtually brand new and this is just unacceptable for phone of this caliber. This has been going on since I got the phone last year.
Has anyone else had similar issues?
I'm still on stock rooted 4.3.
TIA!
Click to expand...
Click to collapse
Since you're on stock 4.3 and I don't know of any software mods for that you can try this...http://forum.xda-developers.com/showpost.php?p=51192662&postcount=1
thegamerdarkseid said:
Since you're on stock 4.3 and I don't know of any software mods for that you can try this...http://forum.xda-developers.com/showpost.php?p=51192662&postcount=1
Click to expand...
Click to collapse
Thanks for the reply.. The screws were all already very tight. I installed faster GPS so I'll test it and see if that helped at all.
Are there software mods on 4.4? I'm willing to go through the trouble of updating if it will fix this damn GPS.
siciliano777 said:
Thanks for the reply.. The screws were all already very tight. I installed faster GPS so I'll test it and see if that helped at all.
Are there software mods on 4.4? I'm willing to go through the trouble of updating if it will fix this damn GPS.
Click to expand...
Click to collapse
Baja has a gps fix on his rom but I don't know if it'll work since your screws are already tight. I'd hate to have you upgrade especially if you really don't want to and it's the same problem.
But if you wish to see if that works check out @BeansTown106 thread here to upgrade : http://forum.xda-developers.com/showthread.php?t=2726558
It's not hard but just read and take your time and follow the instructions to a tee.
@bajasur is currently working on the Alliance Rom and I can't find an active link to the last Baja. If you want PM me and I'll upload it for you. Out of respect to Baja I won't put a link in this thread.
thegamerdarkseid said:
Baja has a gps fix on his rom but I don't know if it'll work since your screws are already tight. I'd hate to have you upgrade and it's the same problem.
Click to expand...
Click to collapse
I was googling the issue and there are a bunch of posts regarding GPS issues on the note 3, except none of them are on Verizon. I don't know if the carrier has anything to do with it, but according to the all posts it's some sort of software issue...apparently AT&T released an update regarding the issue.
I haven't updated anything since I got the phone, maybe one of the updates fixed this issue. Has there ever been any Verizon updates?
I'm on Verizon. I'm running stock rooted 4.4.2 and also have GPS issues. I tried tightening the screws which made no difference. Only way I can ever get a lock is by running the app GpsFix. This usually takes 5-10 minutes and doesn't always work.
siciliano777 said:
I was googling the issue and there are a bunch of posts regarding GPS issues on the note 3, except none of them are on Verizon. I don't know if the carrier has anything to do with it, but according to the all posts it's some sort of software issue...apparently AT&T released an update regarding the issue.
I haven't updated anything since I got the phone, maybe one of the updates fixed this issue. Has there ever been any Verizon updates?
Click to expand...
Click to collapse
Yes there has, we have an leak NC2 and the OTA NC4. It's best if you're on 4.3 to do the NC2 leak as you can roll back to MJE if you want. If you go NC4 you're stuck. You can have root and the ability to flash roms on NC4 but no rollback. NC2 for some people have had signal issues. Me personally I'm on NC2 with the NC4 modem and it's been great. There are some people on NC2 with the MJE modem, it depends on where you are and your device I guess. We do have alot of flexibility outside of being able to use custom kernels, they're trying to but nothing yet. There's alot of great guides on here and just read, read and read again before you take the leap and don't skip any steps and you'll be fine. I don't really have any more info I can shed on gps issues and I don't know for sure if upgrading will make it better for you. Maybe someone who knows more will chime in.
I'm on the NC2 leak, using NC4 modem. Nothing has fixed my gps issues. Had problems on 4.3 and hasn't been any better since KitKat.
I know it was spoken in a couple of other threads but tightening the screws under the battery cover improved my GPS tons.
black05x5 said:
I'm on the NC2 leak, using NC4 modem. Nothing has fixed my gps issues. Had problems on 4.3 and hasn't been any better since KitKat.
Click to expand...
Click to collapse
At least I know I'm not alone... It's been less than a year, maybe I can get a replacement, I hope. I'll have to go to Verizon and ***** about it.
I just went on a 2 hour trip and must have lost GPS signal like 15 fkn times. Then when I do have a signal, it lags and/or thinks I'm on an adjacent road. This is UNACCEPTABLE for a phone of this caliber!!!