Hi there, I have an i9505 currently on cm12 - 20150304 Nightly.
I replaced the screen a few months ago and since then I have never been able to connect to 4g. I have flashed many roms include a return to pure stock but no software intervention has ever gotten a peep of LTE out of it.
I really don't know what else to try and I don't know what physical component could be causing the issue. H/H+ works fine and LTE was fine before I replaced the screen/digitizer. Has anyone got any ideas/suggestions?
Thank you for your time.
Related
hi there,
i have a s4 i9505 which has been rooted and is running davdh's pure nexus rom.
i've got a bit of a problem with the gps - it locks when i first turn on maps but loses signal subsequently. signal stays lost for a few mintutes (maybe 2-5, it depends) and locks for a second or two before the signal is lost again.
i've had a look at several forums and it seems like its a common problem for the S4 Active, S3 and Note II. those problems were fixed when some users flashed a different modem - there seems to be a consensus that the problem is caused by overheating caused by the radio.
I was wondering if anyone here had a similar problem with their i9505, and if so, did you manage to fix it?
also, might anyone recommend a fix/modem version that might fix this?
Cheers
Hello all,
It appears my NFC sensor has quit working on my T-Mobile Galaxy S5. To provide some back story in hopes of finding a solution, here's what's going on:
A few days back, everything was running fine. I flashed an unofficial CM12 ROM (Albinoman887's) to my phone, which at the time had broken hotspot and no Netflix support. NFC worked for me at that point, as I used it to 'Tap n Go' when setting up my account to transfer everything to my S5 from my N7.
The next build that was released fixed Netflix for me, but since then I haven't been able to get any functionality out of NFC. According to the ROM developer, NFC works on his device, as it also does for several other T-Mobile S5 owners. I definitely believe that it works for them, but it's super frustrating to me that it won't for me -- even though I rarely use NFC. I'm just irritated at the thought that my sensor may have died and I have no idea why/how. The phone has never been dropped, so it shouldn't be shock damage.
It's also worth noting that I Odin'd back to my stock firmware, just to test NFC, and I couldn't get any NFC functions to work once I started fresh.
I'm not sure what my options are at this point, but I was hoping someone might have some input to help steer me in the right direction.
Quick update: I flashed a CM 11 ROM (Bliss Stalk, to be exact), and my NFC sensors now work like normal. I'm glad to see it's not dead, but I'm completely baffled as to why it doesn't work on CM 12, when the ROM developer is running the same device and it works for him.
Ahh, the perils of Android development. I'm still glad Lollipop is coming along so smoothly, and I apologize to @albinoman887 for being such a pain in his butt!
Hi All,
I'm wondering if anyone else has encountered this problem?
Basically, I was having wifi issues connecting to an enterprise WLAN with PEAP/MSCHAPV2, so I (stupidly) upgraded to the OTA 4.4.2 ROM, which would have been fine if it didn't kill battery life and randomly restart. I wasn't on this version long enough to know if it had the same issue that I will describe below.
So I threw caution and my warranty to the wind and went with the 4.4.4 Pacman ROM, which was great, but whenever I had a phone call, the phone screen freezes and won't wake up to allow me to hang up a call. The same thing would occur if I called someone and had to use their automated system - I'd put the screen on loudspeaker, open up the dialpad, and when I want to hit the numbers - nothing. Locked up. Can't hang up either.
I had the same issue on the 4.4.4 Cyanhacker ROM, so I believe that it is fully related to some sort of incompatibility between KitKat and the i9505, and not the ROMs themselves.
At this point I was successful in switching to the Darthstalker 4.3 ROM, which is running beautifully and I'm really liking it so far. It's also nice having the old phone and contacts apps back, because I really hated the Kitkat one anyway...
Hey all. I just got my Note 3 two weeks ago and I love it. The battery life is great, great specs, unlocked bootloader, and I find it easier to use in terms of size compared to the Galaxy S5. There is only ONE problem with this device.
The mic stops working during skype calls after random periods and the only solution is to hang up the call and call again. This lingers even after restarts of the app and phone.
Being a Nexus user since the Galaxy Nexus, the first thing I did was install TWRP and the latest CM nightly. I personally can't stand Touchwiz, which is why I sold my bootloader-locked GS5 to get this bad boy.
Has anyone else encountered this issue? Is it a Skype problem? Is it CM? Lollipop? My mic is fine, it works perfectly in every other application.
Also, I've noticed that USB 3.0 mode doesn't show up in the Connection type selection menu. Is USB 3.0 file transfer only supported in the stock kernel?
Hi all,
I recently upgraded from 4.4.2 stock rom to 6.0.1 stock rom and everything worked fine except the GPS. I tried a few different fixes like changing the gps.conf, and a few different apps and could see there was some signal but it could never seem to get a lock. Sometimes it seemed to get a lock for a split second then drop it again.
I ended up going back to my 4.4.2 and GPS works fine again. So the simple conclusion is this is firmware based. I'm no expert but would be willing to help if someone wants to investigate this further. There has to be some GPS related files from the KK firmware that can be exported to MM to make it work
Keliuss
GPS has always been kinda weak and slow due to the module itself. Did you experience the auto brightness bug as well?
kom-pakt said:
GPS has always been kinda weak and slow due to the module itself. Did you experience the auto brightness bug as well?
Click to expand...
Click to collapse
Auto-brightness was working fine for me. Just the GPS issue noted.