I have an Evo and I've used 4g in about 4 major cities across the country and had a horrible experience every single time. It doesnt stay connected, it's got huge packet loss making streaming nearly impossible, huge latency, etc. where someone else I talked to had the most excellent experience even in one of the areas I had a hard time. Difference is, I'm rooted and was running a custom rom, and he wasn't.
Anyone got any clues on this? Is this a byproduct of not accepting updates from Sprint?
Difference is, I'm rooted and was running a custom rom, and he wasn't.
Anyone got any clues on this? Is this a byproduct of not accepting updates from Sprint?
Click to expand...
Click to collapse
Well, since that is the only difference between the two phones, I would say that is the problem. Update your radios and see if that helps.
Fellow XDA users,
My friend has an absolutely stock Galaxy Nexus (chic white) which is on 4.2.2.
Ever since the last few months, he is facing a specific issue where-in his phone just reboots halfway through a call.
This happens on voice calls, as well as while using Skype, Viber, etc.
He does not have any reboots while using his phone otherwise, just while calling.
He is not very tech savvy and primarily uses his phone for calling people (surprise!! surprise!!) and he is really frustrated by this behavior.
Can anyone suggest anything that he could try to stop this unexpected behavior or can identify possible causes for this?
Thanks in advance for your responses.
You could get it rooted for him and see if that resolves the issue. If it doesn't I would suspect defective hardware is the problem. Does it get hot during a call?
Sent from my Galaxy Nexus.
Pierceye said:
You could get it rooted for him and see if that resolves the issue. If it doesn't I would suspect defective hardware is the problem. Does it get hot during a call?
Sent from my Galaxy Nexus.
Click to expand...
Click to collapse
@Pierceye Yep that was going to be my next step, however, I wanted to investigate to see if this was a (fixable) software defect on 4.2.2.
Later I will root and install a custom ROM and see if it disappears. If not, them I am afraid it's an hardware an issue and I hope he can get it replaced via warranty.
Pierceye said:
You could get it rooted for him and see if that resolves the issue. If it doesn't I would suspect defective hardware is the problem. Does it get hot during a call?
Sent from my Galaxy Nexus.
Click to expand...
Click to collapse
@Pierceye Yep that was going to be my next step, however, I wanted to investigate to see if this was a (fixable) software defect on 4.2.2.
Later I will root and install a custom ROM and see if it disappears. If not, them I am afraid it's an hardware an issue and I hope he can get it replaced via warranty.
Samsung's warranty department is pretty good. I have read a few complaints here and there but no worse than any other big corporation. I haven't seen any significant number of complaints about the issue your friend is having with any of the 4.2.2 ROMs. Mostly battery life and BlueTooth issues. Hope you can get it sorted out soon though. :thumbup:
Sent from my Galaxy Nexus
Hi! I'm planning to buy the LTE version of this phone tom. I wanna ask what are the common issues that I need to check and or common issue after months of using like screen unreponsiveness or not accurate touch screen deadpixels so I can think for other options or I can live with the issues if there is a work around.. Thabks in advance!
kimdarrel said:
Hi! I'm planning to buy the LTE version of this phone tom. I wanna ask what are the common issues that I need to check and or common issue after months of using like screen unreponsiveness or not accurate touch screen deadpixels so I can think for other options or I can live with the issues if there is a work around.. Thabks in advance!
Click to expand...
Click to collapse
All the 'potential' problem you list may or may not happen to you/anyone with any phones...
The only real problem with the S4 mini is the KNOX protection. Which prevent you modding your phone, as a triggered knox voids warranty.
Got this for about two months now, only issue that I couldn't fix is GPS... Gps is very unstable as for me. Also there is not that many roms with this device. I wouldn't buy this now... In general no samsung devices for me...
kodyro said:
Got this for about two months now, only issue that I couldn't fix is GPS... Gps is very unstable as for me. Also there is not that many roms with this device. I wouldn't buy this now... In general no samsung devices for me...
Click to expand...
Click to collapse
There's at least 8 ROMs if not more for the S4 mini... How many more you want? I have Sygic on mine, and it works perfectly.
However I may agree with the idea with no Samsung, but all the reason you given is not a valid one.
well i have to say, i don't really have any issues
Battery issue is a big problem. People talking around of it:
http://forum.xda-developers.com/showthread.php?t=2775477&page=2
http://forum.xda-developers.com/showthread.php?t=2779448
in certain circumstances the battery drains very quickly.
Other than that, there is a custom roms, mine GPS working fine.
And i do not undurstand the fuss about KNOX, because if you want to replace it you can electrically shock the device, and no one can tell what rom did you had on it...
daywalker1914 said:
Battery issue is a big problem. People talking around of it:
http://forum.xda-developers.com/showthread.php?t=2775477&page=2
http://forum.xda-developers.com/showthread.php?t=2779448
in certain circumstances the battery drains very quickly.
Other than that, there is a custom roms, mine GPS working fine.
And i do not undurstand the fuss about KNOX, because if you want to replace it you can electrically shock the device, and no one can tell what rom did you had on it...
Click to expand...
Click to collapse
That a software problem... particularly a kernel one. It not the phone itself. And if you want to talk about software problem, I want to know which phone doesn't have one? Even Google Edition phones that uses AOSP has problems.
Yes, all smart phones has software misgivings in one or another way, but all phones are comprised both of software and hardware, and for me, i cannot give hardware disadvantage to this one, i can only share my opinion on the problem with the battery (no one actuality confirmed 100% where the problem is, almost everybody suspects that it is a software - kernel, problem), because for me, the battery drains some times fast, some times slow, and this is really awful. I cannot relay on this phone.
TNCS said:
There's at least 8 ROMs if not more for the S4 mini... How many more you want? I have Sygic on mine, and it works perfectly.
However I may agree with the idea with no Samsung, but all the reason you given is not a valid one.
Click to expand...
Click to collapse
basicly i've tried most of them, however it was device fault.
I have some thumb rule, never update to the newest firmware, and reed the comments. Also at home I have a router, that the manufacture update the firmware from time to time, but I used to run one firmware before the last one. It just an example, but since all the Lollipop, people complain, so why bother? Can't you wait for a while, till Google resolve all the issues? Do you consider Kitkat was perfect then? Or does Lollipop runs perfect on Nexus 6 & 9? I'm starting to think, it intentionally, like iOS 7 on iCrap 4, on iOS 6 it was fine, just think of it, maybe Google do it intentionally, to make us buy a new device? Or they just do a bad optimization job for older devices, and put all effort toward new devices? Any thoughts? I know we all nexus user, are a free beta testers, but if running latest firmware, means it brick out devices, it's hard to thrust Google like that, so I think it's better to stay on Kitkat till better times.
Sent from my hammerhead using Tapatalk
The people who's tablets work fine (the vast majority I'd guess) don't complain. You only here from the people who have problems.
I've been on lollipop since the preview and it's been great. I'll be flashing 5.1.1 the second it's out. Kitkat is dead to me, and very ugly looking back. It certainly was not perfect.
If my device gets the brick people are talking about it would suck but I really, really doubt it has anything to do with the firmware. Some hardware failure most likely. No reason to stay on an old release.
5.0.2 was horrible. While I disregard majority of users complaining of battery life, some of them weren't spewing nonsense.
5.1 is an improvement. I'm one of the guys who do not post every complaint or dissatisfaction I encounter with the Nexus 7. I know what the problem is, I know where to ask for help to pinpoint the cause, now it's my turn to make a decision, stay on Lollipop? or revert to KitKat? Or remove the cause, in other words the app itself.
Back to the OP, there is no risk updating to 5.x. Your device won't magically break. If you like to play it safe, maybe it's better for you to wait for user feedback and ignore the OTA.
OTA you say...
All I hear ate 2 things "Memory leak" & "Bad battery life", be it Nexus 4, 5 or 7, all after the "Lollipop", ...mostly the "Memory leak thing, that told to be solved after each update
Is it safer to flash from ADB? or the "dead" devices dyed in both ways? be it ADB on clean device, after reset, or just OTA? I personally, never thrust OTA updates, I wish there was an easy way, to make a full backup, like a "Norton Ghost" for PC's, I know it can be done with ADB, the question is, if there's any difference, between flashing "with wipe" or without? or maybe the "dead" devices was : 1. rooted, 2. bootloader unlocked, 3. encrypted, or something else? I mean, Google do test all new FW on real devices? don't they?
I wouldn't take an ota myself. Not because of "the brick," I think thats a hardware problem, I feel it's a cleaner update with fastboot and if something fails I'll know what.
And you can (and should) make full nandroid backups in a custom recovery (cwm, twrp etc.).
But to the poster aboves comment it just goes to show you people are having different experiences. 5.0.2 was fantastic for me, great battery life, best it's ever been actually (still as good on 5.1 ~8 hours screen time over two days.)
The memory leak was/is a problem. Oh no I had to reboot once a week. Huge headache. On 5.1 I'm at 270 hours uptime and system ram's at 479. It is creeping up slooowly but better than 5.0.2
I guess it depends what you do with the tablet and especially what apps you have installed. I use my **** pretty heavily though so I don't know why I'v had no problems.
donisan969 said:
OTA you say...
All I hear ate 2 things "Memory leak" & "Bad battery life", be it Nexus 4, 5 or 7, all after the "Lollipop", ...mostly the "Memory leak thing, that told to be solved after each update
Is it safer to flash from ADB? or the "dead" devices dyed in both ways? be it ADB on clean device, after reset, or just OTA? I personally, never thrust OTA updates, I wish there was an easy way, to make a full backup, like a "Norton Ghost" for PC's, I know it can be done with ADB, the question is, if there's any difference, between flashing "with wipe" or without? or maybe the "dead" devices was : 1. rooted, 2. bootloader unlocked, 3. encrypted, or something else? I mean, Google do test all new FW on real devices? don't they?
Click to expand...
Click to collapse
Hard bricks have been reported from both OTA and ADB updates, but very seldom from users of custom ROMs... Most likely cause is eMMC failure due to faulty hardware, though the issue is present on nexus 4 and 5 as well... Possibly faulty bootloader software too.
^Bootloader faults could be possible.. that has pretty low level access. I don't know low enough to corrupt the chip. I don't know. Asus/google probably does but guaranteed you'll never hear a word from them.
I hope it's not something like the infamous s2 brickbug. Then you're just playing russian roulette. Maybe entropy can help lol.
What emmc chips are the 4 and 5 using? I'll have to look.
I'm not sure this is true but if you use Greenify I think the memory is kept in check better, although it requires root. I still see the occasional launcher redraw but not nearly as bad as it was in 5.0. I was on 5.0.2 for several weeks and wouldn't have updated if I hadn't read about the hardware failures.
Well if you don't update your tab, than you don't need a Nexus, buy some cheap chinese tabs for 70-100$, almost all of them are on kitkat, most of them vanila android, no updates, and they all work fine.
This is Nexus.It's a developers tab, for testig, trying, people who like the freshest system on their device, who like clean android....if something's not working, there's always an image of the old system or a bunch of ROMs to test and use...
I know, I myself for now test windows 10 on work PC, and a server 10 preview, but computers and tablets are different things, because you not have that much control for both. All I say, is, that I see same threads for any nexus device, I had a Galaxy nexus before, so I know. About s2, there was a rumor about some other Samsung devices back than.
Sent from my iPhone 4 using Tapatalk
donisan969 said:
I know, I myself for now test windows 10 on work PC, and a server 10 preview, but computers and tablets are different things, because you not have that much control for both. All I say, is, that I see same threads for any nexus device, I had a Galaxy nexus before, so I know. About s2, there was a rumor about some other Samsung devices back than.
Sent from my iPhone 4 using Tapatalk
Click to expand...
Click to collapse
Device OEM is irrelevant in that regard, the quality of internal components is really the crux of understanding hardware failure IMO. of the major android OEMs, all of them have in the past put forth devices that were predisposed to early hardware failure, mostly due to choices of components used during the manufacturing process. Hardware revisions on individual devices of the same model is also a valid form of comparison.