Search results

I have two of these phones, both on T-Mo and no issues whatsoever. I replaced my S7 Edge, in fact, as my daily driver. However, having read this thread, I'll say defective and crappy tech support and agree with the buyer beware notice. Good luck, DHO!

Since I last posted, my screen has been naked and I've incurred one tiny micro scratch that freaked me out. I took one of the extra screen protectors I had lying around (for S7 edge) and cut off the top and bottom in order to avoid the corners being pushed in. So far so good but it is hella ugly...

I'm on the same boat and unless there's a screen protector that only covers the screen and doesn't go up to the four corners, I don't think there are any screen protectors out there right now that won't get pushed in by a case.

As someone who has always had a ZeroLemon on all my phones since the S3, getting this for the S7 edge was a no-brainer. I've also been the type to always get a screen protector for all my gadgets with shiny displays. I always go for glass if available, too. I'm finding out right now, having...

Thanks for this, OP. I've been out of the rooting scene for a while and I completely forgot about gps.conf. It now locks as soon as I start Waze.

trader418, just wanted to report back that the ROM rebooted while running Waze on my way to work.

Which camera do you guys find stable with this ROM? Mine hasn't worked as it should since the 20170111. When I tap on the shutter sometimes it takes a picture, sometimes it doesn't. It doesn't crash/FC, however.

Mine hasn't randomly rebooted so far but my WiFi keeps dropping --getting a little 'x' at the bottom. The airplane mode someone taught me a few posts ago still works, though.

What's in the flashable zip? :)

Phone just randomly rebooted for me, not sure if a certain app triggered it or a notification popped up, since I wasn't really paying attention. I just saw the screen come on after it had already rebooted.

Mine just rebooted from the lock screen. I'm not sure if it was triggered by a notification or what. This didn't happen with the previous release. The rotate seems to be working better for me, though. Actually, I haven't noticed an issue with it yet (hlte here). The reboot doesn't lead to a...

I constantly get an 'x' under LTE now, changed it to 3G preferred and I still get an 'x' under H+. I'm in my office where signal was never bad. Is this a known issue with the 20170111?

I watch a lot of YouTube and use Plex on my phone. Although the auto-rotate doesn't work correctly all the time, it does work when you watch a video or open an app that takes up the whole screen and in landscape. There's really no "fault" that I can think of or found that would prevent this from...

Bluetooth earphones/headphones, car audio, etc. work for me.

Okay. I tried to read a few pages back and didn't see any mention of it. Good to know.

I noticed rebooting turns off my phone and I can't turn it back on unless I take out the battery, replace it and then I can turn it on again. Is this the case or does it just take a while and I'm being impatient.

It lost root somehow but I managed to backup the important stuff. A clean wipe did it. I could have sworn (I haven't done this in a VERY loooong time) that upgrading from the same ROM didn't require data wipe, but I guess it does when it's from different versions. Especially one from so old.

I just tried to update my wife's phone from CM 10 and I just get errors upon errors. I'm on the latest TWRP.

I'm sorry. My TF201 has been bricked for a long time now and I don't recall what we did to fix my friend's TF201.

It's definitely stuck. I already tried reflashing, wiping, etc. No go.

Mine, too. How long did you wait? I'm wondering if it's stuck there or if I should wait longer.

Did you do a complete wipe or just dirty flashed it? And thanks.

Has anyone tried the 1/16 build? Any carrier/data signal issues? Thanks.

Will do! Thanks! UPDATE: No data or carrier signal. SystemUI errors are gone, though.

Whoops. I thought your post earlier alluded to that build. My mistake.

I just flashed 1/5 build and SystemUI crashes non-stop.

I went back to the previous build and the carrier signal came back but no data. When I flashed back to the 1/3 build again, the SystemUI error was gone but there was no carrier signal. Now I'm back to the previous build again and still no data. I might have to do a complete wipe and go back to...

Thanks! Testing it out now! UPDATE: I don't seem to be getting carrier signal, just WiFi. UPDATE #2: Also getting SystemUI error.

I was shocked to find that this is much more stable than CM11. Thanks for bringing PA back to d2tmo again. I loved 3.99.

Whenever I play a video (doesn't matter if its .mkv, .avi, .mp4, etc. and played on MX, Dice, Mobo, etc.), either the sound doesn't work or the video just freezes. Has anyone else experienced something like this?

Where did you get 8/15 GApps?

Skip to the last pages of the official thread and read the last pages of this thread. That's what I did and I saw some complains of FC's in the official thread and not so much of any complaining here. I decided to go with the unofficial found in this thread for my 4.3 fix. :)

I don't know how this rom is better than the official, but I love it! Lol. Thanks, OP.

What will happen to this thread now that official CM 10.2 is out? http://get.cm/?device=d2tmo Can the mods let us keep it for discussions and in case something doesn't work on the official but works in the unofficial build? EDIT: GApps here.

I actually did that already. The first thing I did when it booted up. I still can't get TiBu to work. Thanks, though. UPDATE: Ha! I rebooted and it worked. Lesson learned. When in doubt, reboot.

Which superuser app is recommended for these builds? UPDATE: I can't seem to gain root access.

It's definitely out of warranty --both the limited time and the fact it was hacked to the teeth. I'm not as upset anymore about losing that tablet. It barely had any XDA love anyway. Lol. My Xoom is at least still heavily supported by Team EOS and Steady Hawkin. The reason why I suspect the...

No, this belongs here for those who were as confused when trying to flash 2.4 official. Although flashing to a newer bootloader has been widely discussed by Cyanogen, many didn't notice it. And for some reason, I assumed the bootloader and the radio were packaged together. That's my fault...

I agree. My bootloader was from older JB. It's no wonder I kept getting the ro.bootloader error from the flashing script. Thanks to the OP for this once again!

Gah. I'd hate to wipe and do this all over again but I guess it'll have to be that. I wonder if there's a thread somewhere that just lets us update the bootloader? Oh, man. The thought of flashing back to stock... LOL. ---------- Post added at 11:30 PM ---------- Previous post was at 11:26 PM...

Sorry! Too much distractions! I meant to say My bootloader is NOW on the latest. Lol. Yeah. I'm on the latest and I still get the error. UPDATE: Just rebooted and flashed the rom in recovery again (TWRP 2.5.0.0) and it worked!!! Thanks to the OP for sharing this sweet little flashable bootloader.

I ran this and it worked fine. My bootloader is now on the latest. When I tried flashing the latest Liquid Smooth 2.4 official rom however, it claims that my bootloader isn't one of the three choices required to flash the rom. Weird.

No worries! I appreciate you trying to help. Which rom did you come from? I'm already on MD5 and it's still giving me an error. I am certain it isn't a bad download either. If I can only figure out what else it is besides the radio, I'm sure this is an easy fix.

Do we have to flash back to stock TW through ODIN then flash LS 2.4?

Thanks! Going to try this with Liquid Smooth. I seem to be getting an error while flashing the latest rom with a UVDLJC modem. UPDATE: Bah! Something else is causing the error. Nonetheless, I'm on UVDMD5. Thanks, OP!

You may be right. The last time I flashed OTA firmware was T999_UVDLJA. The rest of the flashing (UVDLJC) I did was just zips through recovery. No, you don't understand. The error in the script halts the flashing completely. I would have to resort to older versions of Liquid Smooth. I have...

Edited my typos. When I flash the latest 2.4 OFFICIAL, the script checks which modem I have and if it not UVDLJC or UVDMD5 or something else, the script stops the whole thing. I do have UVDLJC but the script doesn't seem to think so.

Which modem do you have? I have UVLJC and when I flash it acts like it doesn't. Weird.

Okay, so my prime was on the latest CM10.1 offered here: http://forum.xda-developers.com/showthread.php?t=2053269 I had TWRP 2.5.0.0 on it as well as the corresponding GApps. I did nvflash and everything on my Prime and it was working flawlessly since the day I bought it. I have had ZERO issues...

Note that I'm talking about "Liquid-JB-v2.3-OFFICIAL-d2tmo.zip" released "2013-05-03 19:37:27 PDT" and you're talking about a completely different release of LS. So yes, of course you have no issues because as I stated above only the latest official release and the second to the latest/last...