yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 4 Q&A, Help & Troubleshooting] raitchison:
Always assume that any OTA or official update will break root and there is some risk that an update will actually brick your phone.

You should also assume that any OTA or official updates will prevent any known root methods from working in the future.

In short, if you are rooted don't take an OTA and if you think you want to root in the future still don't take an OTA.

One of the first things I do when I root a device is disable the OTA update mechanism so I'll never even see the notification.
[Galaxy Tab 4 Q&A, Help & Troubleshooting] mrdave60:
Yes, the the new firmware update did break my root. I used towelroot. I have a galaxy tab 4 10.1 sm-t530nu.
[Galaxy Tab 4 Q&A, Help & Troubleshooting] 404-Not Found:
Can you guys tell me whats the changelog? I dont want to lose root, but its worth it if its a major update.
[Galaxy Tab 4 Q&A, Help & Troubleshooting] feydakin:
I updated my SM-T335 today. Changelog just said "Stability improvement"
[Galaxy Tab 4 Q&A, Help & Troubleshooting] moonsbabe:
I just bought this tablet today....didn't even think about the update...now I have to wait to root. :(
[Galaxy Tab 4 Q&A, Help & Troubleshooting] billinaz:
Not necessarily.

Im working on reverting my 10.1 to the prior firmware version. I just need to confirm that this is the appropriate firmware

PDA: T530NUUEU1AND4
[Galaxy Tab 4 Q&A, Help & Troubleshooting] billinaz:
OK, I used odin and restored the previous firmware. Ran towelroot again, and all is back to the way it was before the mistake in software update.

I was able to freeze LocalFOTA.apk but these were not there to freeze:

Kies.apk

SyncmIDM.apk

SyncmIDS.apk
[Android Apps and Games] androidarissa:
Hello!

Let me show you my new game:

Make Them Jump : Google Play URL

Your brain is he able to do several things at once ?

Make Them Jump is a funny game, addictive and totally free.

*************************************************

Your goal is to make all the men jump over the obstacles.

*************************************************

You can play with 5 different levels, each one harder than the last :

- Arcade : start with one man and go up to five men to make them jump

- Normal : 2 men to make them jump

- Nightmare : 3 men to make them jump

- Hell : 4 men to make them jump

- Inferno : 5 men to make them jump

Who held the longest ?
[Android Apps and Games] asim.sidz:
Nice!

Good work you have done there!
[Android Apps and Games] paaattinsin:
Good GAME (Y)
[Android Apps and Games] new_challenge:
Good game. The graphics so awesome. Good game to kill time
[T-Mobile Samsung Galaxy S 4] xdm9mm:
I did the same thing, though I came from a i9505 with LTE channels that are not compatible with US channels. I bought a new M919 from amazon for $429. So far the phone works with my Straight talk sim running on ATT network. I get good LTE signal.

Only problem I have noticed is the battery drains a lot faster on the M919 compared to my i9505. They both ran unrooted TW 4.4.2 when I did the test.

How is your battery so far? On my i9505, it drains about .5 to 1% per hour. On my M919 it drains 2.5% and higher. This is with google+ and all other bloatwiz disabled.
[T-Mobile Samsung Galaxy S 4] Frankenscript:
One other thing: Before buying the M919, I compared the frequency bands it is capable of receiving, to ensure it had all the same ones that that were in the I337. Wikipedia has a useful comparison chart, but there are other comparisons out there too. I found this from several sources:

The AT&T variant is model SGH-i337 with the following compatible bands:

GSM850, GSM900, GSM1800, GSM1900, UMTS850 (B5), UMTS1900 (B2), UMTS2100 (B1), LTE700 (B17), LTE1700/2100 (B4)

The T-Mobile variant is model SGH-m919 with the following compatible bands:

GSM850, GSM900, GSM1800, GSM1900, UMTS850 (B5), UMTS900 (B8), UMTS1700/2100 (B4), UMTS1900 (B2), UMTS2100 (B1), LTE700 (B17), LTE850 (B5), LTE1700/2100 (B4), LTE1900 (B2)

So, the T-Mobile has a bit more band range than the ATT version, but contains all the necessary ATT bands.

Regarding battery: On my I337, fully debloated with GoldenEye, I had about 0.3% per hour battery drain (wifi/cell enabled). I hadn't done much customization myself, but GoldenEye was by default pretty battery-thrify in terms of default settings.

When I was on M919 4.2.2 stock, not rooted, wifi/cell on, I had drain about 1.0%. After moving to Dirty Unicorns ROM (4.4.4) it's about 0.8% per hour, but I've done NOTHING to improve battery usage, and DU isn't by default as thrifty as GoldenEye was. I'm sure I can review the settings and go through the "Insane battery life" thread and get down to around where I was on the I337/GoldenEye... it's just a matter of taking the time.

For me, I get through the work day with 75% left on my phone most of the time, and top it off overnight, so I'm not that worried about the details enough to spend the time optimizing it.

Marc
[T-Mobile Samsung Galaxy S 4] xdm9mm:
The more LTE bands and the unlocked bootloader were the reasons I bought the M919 against the ATT variant too. I am really happy with my i9505 but I thought I was missing out on the faster LTE signals. I think my faster battery discharge is attributed to poor LTE signal in my bedroom. Thanks for starting the thread. I am sure it will help others trying figure out which one is the better model, and M919 it is.
[T-Mobile Samsung Galaxy S 4] Punkamonk:
I had my phone SIM unlocked from T-Mobile and have been on AT&T for the past 4 months. When I started out I was on 4.3 and had absolutely fantastic service. Until about 2 months ago when I randomly decided to update to 4.4.2 and had that update virtually ruin the phone for me. I became one of the lucky recipients of constant random connection loss that gives no indication that it has happened. The only way to get signal back from this is to reboot the phone. From what I've read it is a network switching issue of some sort and thus far the only way to have the phone work for an extended period of time is to put it in GSM only mode, which basically locks me to EDGE speeds. The phone will not lose connection in GSM mode. I have gotten a new SIM card and also tested the SIM in a Windows phone and have no issues. So it's almost certainly tied to the phone and not specifically AT&T, however I wonder if it has anything to do with having a T-Mobile phone on AT&T. I have links to a couple threads on the issue, but I cannot post outside links yet.

I have researched as much as I can and tried quit a few different things to alleviate the problem. My KNOX flag is tripped, so any warranty service is unlikely. I have tried multiple custom ROMS, from TW to AOSP. One AOSP ROM seems to be able to reconnect to 4G after a few minutes of losing the signal, but the loss of signal is anywhere from 5-10% of the time, which is pretty poor considering I'm within line of sight of the cell tower I'm connected to.

I am currently on a 4.4.4 AOSP ROM, with the NH7 Baseband. I've thought about and tried to research a bit about flashing a different modem, but haven't seen any solid information on if I can do that safely being on 4.4.4. At this point I'm personally out of ideas for what to do about this. I don't have too many options other than AT&T at the moment, so my goal is to continue to stick with them and keep moving forward to resolve this phone's issue.
[T-Mobile Samsung Galaxy S 4] serio22:
Have you tried flashing the full NH7 firmware and making sure you are on NH7 bootloader as well?
[T-Mobile Samsung Galaxy S 4] Punkamonk:
Before I installed a custom recovery I flashed the Official Stock 4.4.4 via ODIN (Downloaded from sammobile) as I had been rooted and couldn't OTA update. I don't recall verifying the boot loader, but I would assume that it was NH7. It honestly got worse in 4.4.4. In 4.4.2 it seemed drop connection every 12-36 hours, whereas on 4.4.4 it will take anywhere from minutes to a few hours, but it's never lasted more than 12.
[T-Mobile Samsung Galaxy S 4] serio22:
Go into terminal emulator and type this: getprop ro.bootloader and make sure you have NH7 if not flash firmware again.. If you do have NH7 I would flash firmware again anyway and use stock for a while to see if the issue persists on stock as well.. Maybe other M919 users on at&t can chime in on this
[T-Mobile Samsung Galaxy S 4] Frankenscript:
[MENTION=6037682]Punkamonk[/MENTION],

Since lots of ATT network users use the M919 version of the phone (because the ATT version has a locked bootloader), and this problem isn't a general thing that affects us all, I'd say it's something with your phone. Once you've ensured you are fully on the NH7 bootloader so that you don't have to worry about mismatched bits and pieces, as serio22 said run stock for a while. Doublecheck your APN settings (see all things att thread and my first post) to make sure they match what is needed for ATT... and be sure your preferred network mode is set to LTE. I'd also be curious to get some signal strength readings (in db) from the status screen.

My M919 is still on the MDL bootloader, and thus the MDL LTE modem (LTE modem is paired to the bootloader), but I use the NB4 GSM modem (baseband). For the record, I didn't see any improvement when I flashed the NB4 GSM modem replacing the MDL GSM modem. So I have no plans to flash the NH7 modem.... everything is working fine for me so I'm not messing with anything.

If stock, with ATT APN, and you keep losing network, I would start to suspect a problem with the phone hardware.

Good luck. Let us know how it goes!

Marc
[T-Mobile Samsung Galaxy S 4] Punkamonk:
I am on the NH7 Bootloader.

I was stock 4.4.4. for about a week before I flashed a custom recovery for the first time and started trying custom ROMs . I had rooted 4.4.2 only after having major issues with losing connection. When I upgraded to 4.4.4, with hopes that the issue would be fixed, I left it completely unrooted and stock and lost connection within a few hours. APN settings have been check and rechecked quite a few times, as well as being re-setup with AT&T Customer support.

During the time that the phone actually works and connects properly, it works great. I had installed stock 4.4.4, confirmed it working at home, traveled to work, had it work there for an hour or so, and eventually have it lose connection and have to reboot to restore it. The phone will also work consistently in GSM only mode, but being locked to 2G speeds is almost pointless. There are AT&T cell towers directly next to my home and my work, so lack of reception isn't the issue.

I'm almost tempted to transfer to T-Mobile again and see if I still have the issue on their network. However, T-Mobile doesn't have service inside my home OR at my job, so being able to identify an issue with reception would be extremely difficult. I feel like it's not specifically a hardware issue as there are enough near exact reports of the same issue with the same bandaid solution (GSM only mode) remedying the problem.
[T-Mobile Samsung Galaxy S 4] Frankenscript:
Sounds to me like a glitch in the LTE modem that could be either hardware or firmware related. It may seem extreme, but you could always buy another m919 off swappa, use for a while (stock), and see if the problem follows. Recoup most of cost by selling one of the phones after sorting the problem out. If it does, you've ruled out the phone a hardware and software and can then start fighting with ATT over an LTE service issue in your area.

This kind of thing would drive me insane... Spending some $ to figure it out conclusively would be worth it to me, but I'm not sure how many would similarly prioritize this kind of troubleshooting.

Marc
[T-Mobile Samsung Galaxy S 4] Frankenscript:
I thought of another test you could do. It is known that mismatching the LTE modem (non-hlos.bin) with the rest of the firmware causes problems with sound / WiFi.

As a short term test, what if you flashed the full MDL LTE / GSM modem package (non-hlos.bin and modem.bin) to your phone. This would cause the problems above but would let you test LTE signal retention on the older firmware. If the problem is solved you will eliminate hardware and network issues from consideration.

Once test is complete you can Odin back.

Marc
[T-Mobile Samsung Galaxy S 4] xdm9mm:
Try to do a NV Rebuild ... you can find info in the unlocking thread: http://xdaforums.com/showthread.php?t=2283068
[T-Mobile Samsung Galaxy S 4] Punkamonk:
I hadn't tried this yet since I thought that it might cause more problems than it would help. But, since it might be able to rule out the hardware, I'll give it a shot. Thanks for the advice!
[T-Mobile Samsung Galaxy S 4] Punkamonk:
So, I hadn't gotten the chance to try this until today. I had been using a AOSP ROM and just left it in WCDMA mode and it worked fine for the time being. Now I am trying to do this, however I'm not completely sure of how to do it. I've used ODIN before, but none of the guides I've been able to find dictate exactly what I'm supposed to do having both files. I have downloaded the MDL firmware and have extracted modem.bin and NON-HLOS.bin from it. Do I flash both of them the same way, one right after the other? Or do I have to do something else?
[T-Mobile Samsung Galaxy S 4] Frankenscript:
I believe the right way to do it is find the modem package in flashable form, then flash using ODIN in one of the slots ODIN has for doing it... Someone likely has a link handy...
[T-Mobile Samsung Galaxy S 4] Punkamonk:
I ended up setting up a new T-Mobile account with their $30 prepaid plan to test if there are any issues with LTE on T-Mobile. I learned that T-Mobile has deployed LTE service in my neighborhood now and that I have very good reception if I'm not inside of my metal house. Using T-Mobile, I had been away from home all yesterday and over 12 hours, I have 0% time without signal. So, from that test I'm going to say that my issue most likely isn't an issue with the phone alone.

I put in my AT&T SIM last night and was delighted to see that it connected with LTE immediately. I've left Wifi off and have now used the phone for about 18 hours without any interruptions. I'm honestly confused as to what is going on since right before I put the T-Mobile SIM in I had tested it and lost the LTE connection within an hour. I'm home and charging the phone and everything seems to be working great. I'm stumped.
[T-Mobile Samsung Galaxy S 4] Frankenscript:
Very good troubleshooting. Your problem is a very strange one. I've never quite heard the like of it. But I'm glad that things are going well for the moment, though I don't want to jinx you.

Marc
[T-Mobile Samsung Galaxy S 4] Punkamonk:
About 36 hours into using the phone on AT&T, it went back to its same old ways. LTE stopped working and regular WCDMA worked perfectly.

However, I've been using the phone exclusively with T-Mobile for a week now and aside from actual T-Mobile coverage issues, the phone is working flawlessly. I have been traveling over a roughly 80 mile area this week and it switches modes without issue.

So, is it possible there's some sort of an issue with my account setup with AT&T? I tried to call them and explain the issue but they gave me nothing but "we don't guarantee LTE on non-AT&T branded phones". I tried to get the rep to escalate me, but she just kept reading from her script telling me more random things about how it's probably my phone's issue or an APN issue, which I'm fairly sure it isn't since it will connect to LTE and have everything working for some amount of time.

I'm kinda baffled what to do other than try and argue my way up the ladder again.
[8525, TyTN, MDA Vario II, JasJam General] nolovelust:
is screen aligment and 3g issue sorted with new ones?
[8525, TyTN, MDA Vario II, JasJam General] MikeChannon:
Well, I'd say from screen alignment problems with over 50% we're now down to less than 10% (and I don't have figures to back this up!!) just a feeling based on problems appearing on this board.

As regards 3g it depends which problem you refer to, but I believe there are work arounds for the dropped calls issues related to auto swapping of band selection.

Mike
[8525, TyTN, MDA Vario II, JasJam General] nolovelust:
i had t-mobile's one and was having problem with 3 g and/or HSPDA ( it wasnt receiving data althoug there was connection to the internet)
[8525, TyTN, MDA Vario II, JasJam General] shogunmark:
i havent had any real issues with my cingular 8525, well except the first one had excessive bad memory blocks
[Moto 360] wethead4:
It is my understanding that the display is supposed to dim, but never shutoff when ambient mode is selected. Is this true? if so, since mine does shutoff, could the fact that I have a screen protector be impacting this?
[Moto 360] kpjimmy:
No it will still shut off after a certain amount of time. It's normal from what I heard.
[Moto 360] Bob Smith42:
Also, if you want to turn it off....

There is an Ambient setting in the Android Wear application on your phone/tablet.

If you wait for the watch to dim, and then uncheck the Ambient setting box the screen will turn off.

Good luck!
[Moto 360] SilentAce07:
It has to do with orientation and motion. It dims most of the time but is able to turn off if not in use or held down at your side.
[Moto 360] wethead4:
Thanks all. All the reviews online indicate that when ambient screen is enabled,the face would never shutoff, but enter a dimmed state. This clears it up. so the only difference between ambient and ambient mode off is that it would shutoff immedietely instead of entering a dimmed state prior to fully shutting off?
[Moto 360] SilentAce07:
Basically. Ambient mode is on and dimmed quite a bit. Not always. Just a lot.

Ambient mode off basically dims the screen briefly before turning it off completely.

While ambient mode off seems like it would be bad, it's not. The gesture to turn it on is pretty sensitive and responsive. Also, you can just touch the screen or the button to turn it on as well.
[Moto 360] OrionNE:
?

Anyone know if you can turn off the gesture motion and only turn it on by pushing button. I believe this would save a ton of battery.

Just driving into work this morning the screen turned on 20+ times on a 45min commute.
[Moto 360] v3ngence:
Yeah just about everyone wants that feature so I would expect it to be included in a future update sometime, it's mentioned on basically every page of this thread:

http://xdaforums.com/moto-360/general/battery-life-discussion-t2806528
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] buckinfuzzard:
Can't seem to find an answer to my question, and I've been at this since 9:00 this morning.

Tried to OTA 4.4 update my AT&T SGS3 last night, and the update soft bricked the phone. Initially I could get it to the spinning Death Star logo, but would freeze up at that point. After hours of trying almost anything, I installed clockwork custom recovery. Had it wipe all data, and now it hangs at the Samsung Galaxy SIII boot screen. Trying to install Cyanogenmod from sideload (since I can't get a 4.3 ROM to work because Kies won't recognize the device), but that errors off telling me "assert failed: getprop ("ro.product.device"). I followed the suggestion to remove the first line from the updater-script file, but now I just get "assert failed: getprop ("ro bootloader") for multiple bootloaders. When I tried to load an updated bootloader, I get the above error, which shows no device (it just says "this is a " and leaves it at that).

I've tried multiple bootloaders and multiple Cyanogen packages (both stable and nightly). What am I missing? Or am I out of luck? Any help is appreciated.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
I'm assuming you are on 4.3 since you tried to update via Ota. Try flashing this from recovery. 4.3 custom stock rom I found in development section.

https://www.androidfilehost.com/?fid=23212708291681250

Or verify your current firmware build using adb or the built in terminal emulator in recovery.

Enter this:

getprop ro.bootloader

If it returns a 4.3 build you can flash the MJB firmware found in the general section. Flash with Odin.
[Nexus 5 General] lzyllp:
please vote nexus5

http://en.miui.com/forum.php?mod=viewthread&tid=42294
[Nexus 5 General] fiffan86:
Commmme onnnn people!!! The LG G2 is beating us!
[Nexus 5 General] DummyPLUG:
xiaomi phone with miui will steal user data, will this miui port do the same?
[Nexus 5 General] shhbz:
Well seem people are loosing interest in miui as the willingness to flash a miui rom and make it a daily driver never succeed and moreover they concentrate on fixing bugs for mi3 and 4 so all end up sticking to the aosp or cm rom out here where dev are doing excellent job.

Maybe it will be great when someday they release the source as promised and people out here could do the magic
[Nexus 5 General] jirez62:
come on......
[Nexus 5 General] doctor_droid:
May be they have no source at all :p

All they do is to decompile ..make changes...recompile...lol ...kidding
[Nexus 5 General] ps000000:
Yes I am always thinking about this.

If it count on Xiaomi device & all phone that using offical & custom MIUI ROM. :silly:
[Nexus 5 General] sonnhy:
Voted!
[Nexus 5 General] Stocco:
by the way we will not have for 5 Nexus soon :crying:
[Nexus 5 General] MidnightDevil:
Voted, but we're a little off behind. Maybe they will open an exception for us :/
[Nexus 5 General] badboy47:
Looking at the poll I agree. I can see why G2 users are dying to have MIUI; they barely have any good custom roms comparing it to Nexus 5.
[Themer General Discussion] davseu:
Is it possible to allow the app drawer to auto rotate and also a better range of size selection for app icons in favourites and app drawer
[Themer General Discussion] ThemerSupport:
We are working on a landscape mode, however due to the complexity of Themer, this may take some time. Sorry about that!
[Themer General Discussion] rigattoni:
Any news on landscape?

Would be glad to use it with my AppRadio...
[Themer General Discussion] ThemerSupport:
Hi!

Unfortunately this feature may only arrive in the future :( It's going to require a huge amount of time and resources in order to create themes that can work both ways. Sorry about that! It is still on our to-do list though!

- Marco
[Galaxy S III Q&A, Help & Troubleshooting] BMXnotFIX:
I have a d2tmo t999 and I've recently tried out Slimkat 4.4.4, C-ROM 4.4.4, CM11, and Pacman ROM . All work fine, even the camera, until I start SnapChat. After that no camera, in app or just plain camera, will work. I get the "error opening camera, please restart device" error. Anyone have any clue what's going on? I've flashed and reflashed but the problem remains consistent.
[Galaxy S III Q&A, Help & Troubleshooting] BMXnotFIX:
Quick update. Restarting the device allows the camera to work again. Starting Snapchat causes the problem again though. I didn't have this problem on the stock rooted firmware.
[Galaxy S III Q&A, Help & Troubleshooting] AMLB:
This forum is for i9300 only. :)
[Galaxy S III Q&A, Help & Troubleshooting] BMXnotFIX:
Mods, could you move this thread? Sorry, I'm new.
[Galaxy S III Q&A, Help & Troubleshooting] BMXnotFIX:
Installed a new superuser binary and it seems to have fixed it for now.
[G3 Q&A, Help & Troubleshooting] denimourson:
Has anyone tried this? To circumvent AT&T using PMA instead of Qi or add wireless charging to any other LG G3 variant.

Can't post Amazon link showcasing the product for I am new here but here is how it works. It' uses the phone's USB port and you have the receiver connected to a wire and when the receiver touches the back of the phone you get wireless charging.

Do simple Amazon search for wireless charging receiver and you will find it.
[G3 Q&A, Help & Troubleshooting] meyerweb:
Is it this one?

http://www.amazon.com/DigiYes®-Wide...11&sr=1-1&keywords=wireless+charging+receiver

I don't think you have how it works quite right. This plugs into the microUSB port and then sticks permanently to the back of the phone. You then need to put your phone, with this device stuck to the back, on a Qi charger. Just touching this to the back of the phone does nothing by itself.