I am currently having some data connectivity issues with my E4GT. I have been running the Blu Kuban rom for some time now and have been a huge fan of it, but now my phone is acting really weird (no fault to the rom at all). First my GPS wouldn't lock as I thought this was kernel related I re installed the Blu Kuban rom with both of the other kernels and still couldn't get a GPS lock. Since I use GPS daily for work I went back to my classic Epic Venum rom and the GPS worked albeit poorly, it got me through the day. When on this rom whenever I used data my phone would drop down to zero percent battery and power off, this seems to occur only over 4g/3g and not over wifi. I tried flashing multiple modems from EG30 to FI27 on a multitude of roms (both GB and ICS) and using desktop Odin, but I cannot figure out what is causing my phone to crash (which now occurs consistently). I tried installing new roms (currently on AOKP build 37) which works great until the data is used and then it crashes again. I don't think this is cause from any specific rom, and I am now fearing it is a hardware issue. To summarize GPS now works, using data causes my phone to crash regardless of the rom used. Just thought I would ask the community, any help would be greatly appreciated. Thanks!
Update: I ended up restoring to stock to see if that would fix the problem and it didn't. So I took it to the Sprint store where they discovered I had a defective battery, and it just so happened that I bought the phone a year ago today so the new battery will be covered under warranty . I will update my status upon receiving the new battery, but I am feeling optimistic at this point.
Related
So I've had a VZW Nexus for about 5 months, flashed all kinds of custom ICS stuff on it, never had problems.
When Jelly Bean ROMs come out I flash one built from AOSP, works great, after a while an updated version of the ROM hits Goo.IM, I dirty flash+GApps, and suddenly after a few days my phone seems to be stuck in headset mode, not allowing me to use the mic or make calls without using speakerphone mode.
Do full system wipe, factory reset of radios/system/bootloader back to IMM76K, the issue is still there at first boot, hmm, must not be a software issue then.
I Google, this seems like a known hardware issue with the headphone jack, get a replacement from Verizon, it works fine, no problem.
Until I flash an AOSP JB ROM on this working phone, then, just like before, after dirty flashing a JB AOSP ROM upgrade, a day or so later I get the exact same issue, and again full wipes/factory resets don't fix it.
Verizon sends me a new one. This time, I'm staying on IMM76K.
This seems fishy to me, the odds of getting this kind of hardware failure on two different phones after the same sequence of events and there being no relation is astronomically high.
Again, not running any OC's or anything weird. Never dropped the phone. Don't use it in humid environments. Don't even use actual headsets. Used the first phone for months with no issues. Tried SIM/battery pulls. The AOSP JB ROM in question is used by many without this issue, though I have found what seems to be a few more instances of this that have happened after JB upgrades via Google.
Any explanations? Is there a weird bug in AOSP that's frying stuff? Doesn't seem likely or even possible, but then why?
Hey all,
For a while now ive noticed my phone tends to reboot itself randomly(r800a), usually when waking up, ie, using the slider on the lockscreen after its been asleep.
Outside the house i would be lucky to get an uptime of 5+h, however i have been home sick this week and the phone has been connected to wifi the entire time and ive noticed... no reboots.
I get these reboots on CM9, AOKP, and modded stock roms, whilst hunting for the cause in the last couple of months I have steadily dialed back the use of oc/root and modded firmware altogether, i am currently running bone stock .42 for the r800a and have been for a couple of weeks hoping i could pin down the cause.
Does anyone have any idea what steps I could take to fix this issue, it seems to be related to external data use, a straight firmware flash has not fixed it, is there any more advanced methods i could use to potentially fix the problem?
I've been with this problem since phone was new, I'm in Mexico City in Telcel network, sent my phone several times for the same problem and Sony has never replaced the device, they say it's fine, I 've also noticed the problem is when accessing the carrier' s network, I'm testing gin2jellybean and problems seem to stop, at least for a while.
Hmm, thanks for the reply, at least im not alone with the issue, its been bugging me for a while, I might just keep trying different roms and if im lucky one will fix it, considering prying it open to check the antenna connections as remote as that possibility would probably be.
I ran a couple of searches on Google( and in this forum) to try and find the original thread about this issue, however I didn't find it so I'm posting here in case anyone else can be saved by this fix.
First, some background:
I have been running CM10 Nightlies for almost a month now, also using the leaked Jelly Bean radio version T999UVLI2 with absolutely no problems. Everything was working great, data, ROM, etc. (Prior to that I was on Stock ICS, rooted. Had not run any custom ROMs whatsoever).
I noticed after flashing the latest CM10 Nightly (Oct. 14) that my phone had started acting a little weird - nothing drastic mind you, just a few glitches here and there. The weird thing was, all of the previous nightlies I had flashed pretty much worked flawlessly for me, minus a volume issue when in-call which was a known bug. I had done a clean flash as I always do, so I attributed the glitches to a possible bug or two in the latest Nightly and figured it would probably be resolved in the next release. No big deal.
Yesterday afternoon, after reading a thread that is tracking all available T-Mobile radios by region (to see what works best in your area) I saw someone who posted that the T999UVLI3 radio gave them the best speeds, and they happened to live in the same exact city as I do here in Southern California. So I decided to flash the new radio using Team Sonic's Modem flasher, which I used in the past to flash the LI2 radio that I was currently on. I flashed the T999UVLI3 radio and found that it did indeed provide better data speeds than the LI2 radio, so I was pretty happy about that. Used my phone all day/all night with no problems, everything was great.
I always leave my phone plugged in at night so that I have a fresh charge in the morning - this morning I turned off my phone while it was still plugged in as I leave it off during the drive to work to save a little battery before I start my day. Typically I unplug it first and then turn it off, but not always. So nothing really out of the ordinary there.
I get to work and turn on my phone, and all of the sudden I notice that I have no bars - at all. It doesn't say "T-Mobile" at the bottom of my lock screen. I figured it was just taking it's time booting up, which would be very weird as it never does that, but I waited. And waited. Nothing. Now I'm starting to get a little worried.
Went into settings and checked "About Phone" and it said my Baseband version was "unknown". Oh crap. IMEI, unknown. Serial number, unknown. GREAAAAT
For the life of my I couldn't imagine how this could happen when I didn't even do anything from last night to this morning. I started going over everything I had done recently to my phone.. the power off while plugged in, the nightly update to the Oct 14 build, then it hit me.. the new radio version. Maybe that was it
In a desperate attempt I booted into recovery and ran Team Sonic's Modem Flasher and flashed back to T999UVLI2. Rebooted the phone and... BAM! Back to normal. W...T...F..?
If anyone loses their IMEI, before going through the entire injection fix process, try reflashing a radio. Worked for me!
Any theories on why this happened? Many people have been using the T999UVLI3 radio, I believe without any issues.. but I could be wrong. Anyone flashed that radio and lost their IMEI?
I got a freezing problem with my note2. It's quite a strange behavior, got worse pretty fast since yesterday (tried to reflect the situation exactly below).
The freeze behaves like: system freezes, apps freeze, buttons stop working, sometimes the notification bar pull-down still works for 1-2 seconds, BUT: animated icons in the notification bar are sometimes (not always) still animating up to 2-3 minutes. Can also happen with display off, can't turn on anymore.
Since I'm using a ROM that's safe from the SDS problem, it cant be that. Still I mention that I do have that insane chip (Type: VTU00M, FwRev: 0xf1).
My guess is its a hardware related problem, maybe the internal flash memory(?).
Still, it will be hard to restore back to stock for warranty with the usb not working to use Odin.
Original Baseband: XXALJ2
History of this phone (maybe not 100% accurate, it's hard to recall everything exactly):
Bought on release
rooted some weeks later
flashed CM ~spring, regularly updated
July: stopped showing modem signal strength
July: switched to Asylum CM10.x, updated on new version releases
September: USB stopped working correctly when connecting to computer (charging but no data, different cables, ports, computers)
October: started freezing randomly, approx every second day, getting slighly more often
Since Yesterday:
-did a full wipe/factory reset, reflashed rom. more and faster freezes
-as i was messing around, decided to do a modem update: from XXALJ2 to XXDMF1: radio signal strength working again. Freezing increased.
-reverted to backup, also restored old modem: Crazy fast freezings, withing 30sek after every boot.
-again some full wipes/clean install with different but still recent asylum roms: freezings a little better than with a backup, but still crazy fast.
-full wipe with format internal storage: freezes got better, occur after minutes instead of seconds. They still occur faster when using a backup instead of a new install. Same with CM 10.1.3.
No custom kernels used. Default governors. No TB restores or something that I could think of messing with stuff.
Any help or ideas are very appreciated
I could manage to restore stock via Odin (1 in 100 times it detects the usb connection on my laptop), with 4.1.1 Had a freeze, made the OTR update to 4.1.2. Had another freeze. After that 2 more updates. It also changed the Baseband every time, its now DMF1 (same as i upgraded). No freezes anymore. I mean, what the heck? This makes no sense for me at all. If someone can lighten me up, please, go ahead.
It all sounds like SDS. Don't forget that SDS happens if there is a memory block corrupted. If you were in an insane rom before (and you said you bought it in release so almost sure you did) the memory blocks got corrupted. that happened "a lot" of people in the SDS thread(between commas taking in account that here in xda there is not the whole group of people who bought it and percentatge is low).
I recommend you to use emmc brickbug check app and check the memory blocks(if you are rooted)
then if it is SDS the only thing that we can do is pray or wait to samsung not to give free repairs only to China.
hoping that you'll pass the blocks test and it was only a normal problem..
Sent from my GT-N7100 using xda premium
Thanks for your reply.
SDS was the first thing I thought could be the issue. But it run for months without a single freeze on a SDS-safe rom before it started.
The last thing I have done before reverting to stock was a memory check with emmc brickbug app, and it passed. I forgot to mention it, even it's very interesting: while the memory check was running I had the longest runtime without a freeze.
I'm thinking now of returning the phone for warranty because of the USB problem. It's probably too risky to get back to stock once again. If I even could manage to root it again. But tell them too I had freezes? hmm, it's really not happening now anymore
I have the same problem... no idea what should I do
well... Yesterday I took a try and swtiched the CWM. I had TWRP and I've switch to Phliz Touch, so far... 16 hours without freeze
Amit BL said:
well... Yesterday I took a try and swtiched the CWM. I had TWRP and I've switch to Phliz Touch, so far... 16 hours without freeze
Click to expand...
Click to collapse
hmm, I also switched back to CWM recovery (from TWRP) for the last boot (to restore the nandroid stock backup I did, but could manage to flash with Odin before I had to do it that way), that was the point where I was surprised that the emmc memory check did go through without a freeze. I didn't saw any relation to the problem here, but who knows?
So far 34 hours without a freeze
Sent from my Galaxy Note II using Tapatalk
dedors said:
I got a freezing problem with my note2. It's quite a strange behavior, got worse pretty fast since yesterday (tried to reflect the situation exactly below).
The freeze behaves like: system freezes, apps freeze, buttons stop working, sometimes the notification bar pull-down still works for 1-2 seconds, BUT: animated icons in the notification bar are sometimes (not always) still animating up to 2-3 minutes. Can also happen with display off, can't turn on anymore.
Click to expand...
Click to collapse
Same problem, been suffering with freezes for the last 3 weeks and the last 2 days have been 400% worse, found out about this emmc bug but cannot find any information as to how to fix it, some mention kernals, vodafone will not replace the phone unless their software update does not fix it, Running 3.99 RC2 Paranoid android. Anybody got any ideas?
Seems my phone is one of the effect chips with the emmc issue. Funny thing is i just flashed back to stock in order to take my phone back to the shop and its working fine.... not a single issue all day.
Is there something custom roms are doing that party causes this issue?
Sent from my GT-N7100 using xda app-developers app
Madnessx9 said:
Seems my phone is one of the effect chips with the emmc issue. Funny thing is i just flashed back to stock in order to take my phone back to the shop and its working fine.... not a single issue all day.
Is there something custom roms are doing that party causes this issue?
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
I was having different issues including freezes and WiFi/BT loss when kernels with undervolt installed. Usually from custom ROMs. The effect is prolonged sometimes till hardware reset done.
The only working solution (for me) is to use a kernel with controlled voltages and set all the voltages about 1000mV for frequencies below 800MHz. 100% stable,
These are the two setups I have used thus far (besides full stock), and this issue has occurred on both:
http://imgur.com/EgzxWFI
http://imgur.com/FZWrdwZ
The first is on ktoonsez kernel on stock rom. The second is Slimroms Kitkat. I have been using the first much longer than the second (which I moved over to just a few weeks ago).
Basically this soft reset tends to happen when I'm driving and using the GPS most often (and I notice that's also when the phone is usually the warmest). What happens is the phone just freezes up and sits there for a bit before finally doing a vibration and starting back up to the unlock screen. Kind of like I was restarting, but not quite. If it happened in the middle of calls, somehow it would keep the call going (at least on the stock kernel, I'm not sure about the new one yet). The other person just wouldn't hear what I was saying during the "soft reset"
On the stock kernel it used to happen even when not using the GPS. It was infrequent, but occurred I would say usually when I was using the phone more heavily... mostly just random though. Sometimes it would also not happen while using the GPS. That is to say it's a sporadic issue.
On this new Kitkat kernel it happened while I was navigating recently, but has not occurred when during any other operations (yet) that I can think of. Considering that was one of the first times I tried navigating with the kernel this worries me.
Does anyone know how I could approach this problem? Perhaps some logging I could do to get to the root issue? Some firmware I should perhaps try out?
Thanks.
Sounds hardware related to me. Especially if its happening on different roms.
Then again... I just looked at you image and you are still running 4.0.4 on one. But the other you are running 4.4.4. On one or tge other you most likely have a rather large gap between your firmware build and the rom. Id try flashing full stock firmware with Odin and test for a day or two. Up to you what build you want to use, but if it were me id update to 4.3. If you go to 4.3, keep in mind there is no going back.