Develop Bugs

Signal problems after update

Hello all,
I just received my shiny new HOX yesterday and it was working very well at first, however last night I updated it to the latest firmware (with Sense 4.1) and now it will not connect to the mobile network at all (no bars, won't find any networks when I manually search). I have noticed that it seems to be stuck in airplane mode.
Under airplane mode in the settings page it says "off", then a few seconds later it will say "turning off...", then it will go back to saying "off" and then back to "turning off.." and so on. I think it must be a bug in the firmware because I have tested the sim card in another phone (worked fine), and it was working fine before the update.
The only way to see if it is a bug in the firmware (as far as I am aware) would be to install a different ROM. However, I cannot find any way to install a new ROM (custom or stock) without unlocking the bootloader and therefore voiding the warranty (which I don't want to do in case it turns out to be a hardware issue).
I should also add that I could return the phone, but I would like to leave that as a last resort because I live in the middle of nowhere and trying to post stuff if a pain in the ass (and expensive).
I have also tried both a hard and soft reset, with no luck.
This is my first HTC device so I don't really know what I'm doing (although I have plenty of experience rooting and flashing my S2)
Any suggestions would be greatly appreciated

same prob
i've the same problem since the last update. hope it will fixed soon.

ms141289 said:
i've the same problem since the last update. hope it will fixed soon.
Click to expand...
Click to collapse
I'm glad I'm not the person having this problem . Does anyone know if it is definitely a firmware issue? (I might feel more confident about flashing a custom ROM if that's definitely the problem)

Anybody?

Maybe something went wrong with the OTA flash?
First thing HTC will do is flash the RUU to ensure it's back to stock. It will delete all your data, but it's worth a go.
You can use adb backup.

Galaxy S3 Shutdown

Hey guys,
starting last night my Galaxy S3 began to freeze and then randomly shut off. I then had to press the power/home button for a while for it to turn on (around 20-40secs). At first I thought it might be a battery issue, but I used another S3 battery and the issue persisted. I bought the phone in June, and it is currently unrooted but running a leaked Bell Jelly Bean rom which I installed a while ago....
Not sure what the issue could be, and I was wondering if anyone else was experiencing the same issues or if anyone had a fix?

vnsnk said:
Hey guys,
starting last night my Galaxy S3 began to freeze and then randomly shut off. I then had to press the power/home button for a while for it to turn on (around 20-40secs). At first I thought it might be a battery issue, but I used another S3 battery and the issue persisted. I bought the phone in June, and it is currently unrooted but running a leaked Bell Jelly Bean rom which I installed a while ago....
Not sure what the issue could be, and I was wondering if anyone else was experiencing the same issues or if anyone had a fix?
Click to expand...
Click to collapse
I have the same issue, I'm running 4.1.2 XXELL5 firmware, have you found something?

vnsnk said:
Hey guys,
starting last night my Galaxy S3 began to freeze and then randomly shut off. I then had to press the power/home button for a while for it to turn on (around 20-40secs). At first I thought it might be a battery issue, but I used another S3 battery and the issue persisted. I bought the phone in June, and it is currently unrooted but running a leaked Bell Jelly Bean rom which I installed a while ago....
Not sure what the issue could be, and I was wondering if anyone else was experiencing the same issues or if anyone had a fix?
Click to expand...
Click to collapse
What ROM are you running ?

Same here, started last night. I'm not running a ROM just rooted and a few apps removed. In the process of reverting to unrooted stock to see if that helps.

le0nphelps said:
Same here, started last night. I'm not running a ROM just rooted and a few apps removed. In the process of reverting to unrooted stock to see if that helps.
Click to expand...
Click to collapse
It might need a factory reset
EDIT: Ahhh I just noticed you must be on the international version. June didn't ring a bell until I remembered we didn't get carrier models until July
Might want to head over there

hednik said:
It might need a factory reset
EDIT: Ahhh I just noticed you must be on the international version. June didn't ring a bell until I remembered we didn't get carrier models until July
Might want to head over there
Click to expand...
Click to collapse
i agree on the reset. as a matter of fact, i'd suggest a full wipe, flash the appropriate stock firmware in odin and full wipe again. this tends to solve the biggest issues when users update/change android operating systems.
stock firmware thread: http://forum.xda-developers.com/showthread.php?t=1968625

xBeerdroiDx said:
i agree on the reset. as a matter of fact, i'd suggest a full wipe, flash the appropriate stock firmware in odin and full wipe again. this tends to solve the biggest issues when users update/change android operating systems.
stock firmware thread: http://forum.xda-developers.com/showthread.php?t=1968625
Click to expand...
Click to collapse
Do y'all have the i747 or the i9300 international version ? 4.1.2 was never released for north America phones and you quoted a UK version of the OS
Don't flash anything on this site unless you have a i747 or i747m

Music Stops with Screen Off (F460K)

Hey guys I've had this issue where regardless of what music app I use, a few seconds after I turn my screen off (i.e. lock the device) the music will stop playing until I turn it back on.
Anyone have any idea why? I'm on version 10e (latest according to PC Suite and OTA Checker), and I'm stock unrooted.
Other than that the phone's been amazing and blazing fast, even outspeeding my M8 GPE sometimes
Sent from my LG G3 Cat.6 using Tapatalk

Also, when charging, this problem doesn't occur. This further adds to the mystery...
Also, it happens if I have music local or streaming, so that rules out network issues.
Sent from my LG G3 Cat.6 using Tapatalk

UPDATE: OK so after messing with about every single setting on the phone, I tried switching it back to Dalvik. Fixed everything 100%. Whole phone is faster, from opening apps to web pages.
Very strange... Not sure why there would be so much ART incompatibility, but I guess it's 4.4.2 and not .3 or .4. If anyone else has has this problem (including an inability to wake the phone up without a few tries), check your RunTime. I'm hoping it'll be better next update, but for now this'll have to do.
Sent from my LG G3 Cat.6 using Tapatalk

SolarTrans said:
UPDATE: OK so after messing with about every single setting on the phone, I tried switching it back to Dalvik. Fixed everything 100%. Whole phone is faster, from opening apps to web pages.
Very strange... Not sure why there would be so much ART incompatibility, but I guess it's 4.4.2 and not .3 or .4. If anyone else has has this problem (including an inability to wake the phone up without a few tries), check your RunTime. I'm hoping it'll be better next update, but for now this'll have to do.
Sent from my LG G3 Cat.6 using Tapatalk
Click to expand...
Click to collapse
Hi there!
I have exactly the same problem since I updated the phone to Lollipop (D85520A) but before that I didn't have that problem. Firstly I found this when I updated to D85519H and then I performed another update to the current version (D85520A) and it didn't help. The smartphone is way better, but this problem is really ennoying me.
ART is not available on Lollipop and my phone went only for one day to ART mode and it was a pain in the ass (when I still had 4.4.2) and then I switched back to normal.
I am thinking about to a factory reset and reinstall Android 5.0 on CSE mode AGAIN and see what happens, but I think it won't help at all.
Do you have any idea of what could I do in order to solve this problem?
Thank you in advance.

Fixed
Hi there!
Just a short update.
Like I mentioned before, I got this problem when I updated my phone with the new Lollipop FW (D85519H) and then I tried to perform another update using the D85520A but the problem was still there. So I believe that the update didn't fix the issue from the previous update so I performed another clean update using the same last one and the problem disappeared.
Thank you anyway.

juansavage said:
Hi there!
Just a short update.
Like I mentioned before, I got this problem when I updated my phone with the new Lollipop FW (D85519H) and then I tried to perform another update using the D85520A but the problem was still there. So I believe that the update didn't fix the issue from the previous update so I performed another clean update using the same last one and the problem disappeared.
Thank you anyway.
Click to expand...
Click to collapse
I have the same problem. What do you mean by "clean update"?

ZHENURIK said:
I have the same problem. What do you mean by "clean update"?
Click to expand...
Click to collapse
Probably CSE flash with this method: http://forum.xda-developers.com/showthread.php?t=2785089

[Q] Need to downgrade, how?

Greetings, I wonder if somebody can solve the following problem. I'm from Venezuela and I bought this model GT-I9192 in December 2013 when the update came out this year it was updated from 4.2.2 (JellyBean) to 4.4.2 (KitKat). I almost never use the camera of this phone and then I noticed that every time I opened the camera app I would get "Warning: Camera Failed". Thinking it was the update I proceeded to install the Cyanogenmod rom 11 for this model, but continued with the same problem. The flash works every time I turn the flashlight application. I took it to a technician telling me that the problem was not hardware but software. This is where my troubles began. I do not remember which firmware was installed. I tried to install several firmwares 4.2.2. but without success all with flashing failures. However, I could install version 4.4.2 of Trinidad and Tobago but with the same camera error. Hopefully someone can help me with this problem. I would like to know exactly what firmware should download to install? Thank you very much.

nelson2006 said:
Greetings, I wonder if somebody can solve the following problem. I'm from Venezuela and I bought this model GT-I9192 in December 2013 when the update came out this year it was updated from 4.2.2 (JellyBean) to 4.4.2 (KitKat). I almost never use the camera of this phone and then I noticed that every time I opened the camera app I would get "Warning: Camera Failed". Thinking it was the update I proceeded to install the Cyanogenmod rom 11 for this model, but continued with the same problem. The flash works every time I turn the flashlight application. I took it to a technician telling me that the problem was not hardware but software. This is where my troubles began. I do not remember which firmware was installed. I tried to install several firmwares 4.2.2. but without success all with flashing failures. However, I could install version 4.4.2 of Trinidad and Tobago but with the same camera error. Hopefully someone can help me with this problem. I would like to know exactly what firmware should download to install? Thank you very much.
Click to expand...
Click to collapse
I registered here just to answer your question.
My Android expertise is very limited but I try to learn from past experience. If I understand correctly, your want:
1. the camera should work.
2. the phone should function properly.
If you do not remember your original firmware, do not worry as it does not matter. Once your upgraded to KK, Knox (google it) kicked in to prevent you from downgrading to JB. That's why all flashing efforts to downgrade failed. So, you can keep your phone with KK if the phone works except camera. In case you want to downgrade to JB, I am sure that able XDA members can help you with that. I am unaware if such methods exist.
Now, to see if the camera works there are several methods. I encountered the same problem with my wives i727 Skyrocket which has JB 4.1.2 installed. One day the camera suddenly failed with the error "Warning: Camera Failed". The flash-light worked flawlessly so I was a bit perplexed. I researched and found several remedies:
1. From application manager, clear cache/data of the camera app and restart phone - Tried this several times, did not work.
2. Perform factory reset- Thought I'd use it as a last resort as the phone had gigs of data in it.
3. Uninstall apps (last installed app uninstalled first and so on) - I uninstalled the last installed app and restarted the phone. Voila! The camera was back. I have no explanations why but it just worked.
Let us know how it goes, good luck!

On the i9195, it is possible and easy to downgrade to JB since there's a 4.2.2 firmware which is similar to the 4.4.2 firmwares, but I don't know about the i9192.
Be careful with this;
If you know what you are doing, get the CWM recovery, format system/data and flash a 4.4.2 firmware again. If that didn't fix it, I suspect that it's a hardware problem and it's having problems with the software, but there should be something wrong with the hardware, for sure.
Good Luck.

snipar said:
I registered here just to answer your question.
My Android expertise is very limited but I try to learn from past experience. If I understand correctly, your want:
1. the camera should work.
2. the phone should function properly.
If you do not remember your original firmware, do not worry as it does not matter. Once your upgraded to KK, Knox (google it) kicked in to prevent you from downgrading to JB. That's why all flashing efforts to downgrade failed. So, you can keep your phone with KK if the phone works except camera. In case you want to downgrade to JB, I am sure that able XDA members can help you with that. I am unaware if such methods exist.
Now, to see if the camera works there are several methods. I encountered the same problem with my wives i727 Skyrocket which has JB 4.1.2 installed. One day the camera suddenly failed with the error "Warning: Camera Failed". The flash-light worked flawlessly so I was a bit perplexed. I researched and found several remedies:
1. From application manager, clear cache/data of the camera app and restart phone - Tried this several times, did not work.
2. Perform factory reset- Thought I'd use it as a last resort as the phone had gigs of data in it.
3. Uninstall apps (last installed app uninstalled first and so on) - I uninstalled the last installed app and restarted the phone. Voila! The camera was back. I have no explanations why but it just worked.
Let us know how it goes, good luck!
Click to expand...
Click to collapse
I haved tried the first two steps and no luck at all. Maybe this weekend I'll try the third one. Thank you for the reply.

snipar said:
I registered here just to answer your question.
My Android expertise is very limited but I try to learn from past experience. If I understand correctly, your want:
1. the camera should work.
2. the phone should function properly.
If you do not remember your original firmware, do not worry as it does not matter. Once your upgraded to KK, Knox (google it) kicked in to prevent you from downgrading to JB. That's why all flashing efforts to downgrade failed. So, you can keep your phone with KK if the phone works except camera. In case you want to downgrade to JB, I am sure that able XDA members can help you with that. I am unaware if such methods exist.
Now, to see if the camera works there are several methods. I encountered the same problem with my wives i727 Skyrocket which has JB 4.1.2 installed. One day the camera suddenly failed with the error "Warning: Camera Failed". The flash-light worked flawlessly so I was a bit perplexed. I researched and found several remedies:
1. From application manager, clear cache/data of the camera app and restart phone - Tried this several times, did not work.
2. Perform factory reset- Thought I'd use it as a last resort as the phone had gigs of data in it.
3. Uninstall apps (last installed app uninstalled first and so on) - I uninstalled the last installed app and restarted the phone. Voila! The camera was back. I have no explanations why but it just worked.
Let us know how it goes, good luck!
Click to expand...
Click to collapse
RoyaLKurTx3 said:
On the i9195, it is possible and easy to downgrade to JB since there's a 4.2.2 firmware which is similar to the 4.4.2 firmwares, but I don't know about the i9192.
Be careful with this;
If you know what you are doing, get the CWM recovery, format system/data and flash a 4.4.2 firmware again. If that didn't fix it, I suspect that it's a hardware problem and it's having problems with the software, but there should be something wrong with the hardware, for sure.
Good Luck.
Click to expand...
Click to collapse
Tried that too and nothing. I also suspect that the problem is a hardware issue. Thank you for the reply.

nelson2006 said:
Tried that too and nothing. I also suspect that the problem is a hardware issue. Thank you for the reply.
Click to expand...
Click to collapse
The problem, in fact is a fault in the hardware problem. If it's still under warranty, request a new phone.

[Q] Help! What have I done to my Pro 10.1

Here's the story. I purchased a factory refurb'd Tab Pro 10.1 (SM-T520NZKAXAR) on Woot a few weeks back. I live in Canada, but it is a USA tablet, if that matters. It came with a 90-day Samsung warranty. As soon as I got it, I started looking at custom ROMs. I have experience with custom ROMs on my HTC One m8 (and old m7), but not with any Samsung devices. I wish I had kept it stock for a few weeks first to check it out, but here we are.
I created a nandroid backup of the stock firmware, however I quickly deleted it during a wipe when flashing my first custom ROM, which was GraveD's v3.0. It seemed to go OK, but then it would start to freeze up and reboot on it's own. This seemed to happen mostly under load, and especially when trying to install apps from the Play store. I tried going back to the stock kernel, thinking that could be the problem. It stopped the crashing, but then wifi wouldn't work. So I could choose between having a tablet that crashes all the time, and has difficulty installing apps, or one without wifi. Both were basically useless.
I tried installing another custom ROM, GigaWatts Pro. Again, flashing seemed to go well, and the ROM also seemed to work very nicely for a couple of days. No random reboots, and wifi worked great. I spent a few days downloading all of my apps and getting things set up the way I like, when yesterday something went wrong. Perhaps the tablet lost its root (is that possible?). All of a sudden, apps are crashing all over the place (Unfortunately, [insert app name] has stopped). Titanium backup hangs at "Asking for root...". Installing apps is also difficult again. The tab doesn't reboot on it's own, but Play Services crashes constantly. Whenever I try to get into developer options, the Settings app crashes. I'm not even 100% sure USB debugging is enabled right now, although I'm still able to flash using ODIN.
I tried doing a factory reset and re-installing GigaWatts. Same problems. Tried making sure the root was OK. Same problems. I've tried using twrp 2.8.0.0 as well as 2.7.1.0 with no luck.
Right now, I've downloaded the stock firmware for Canada T520UEUANI1 4.4.2 (although the tab was bought from a USA site). I assume this also installs it's own Kernel. It shows Kernel version:
3.4.39-2776001
[email protected] #1
Mon Sep 15 17:44:40 KST 2014
I'm experiencing the same problems. Google Play Newsstand crashes every 10 minutes or so. Settings is almost useless. Installing apps is problematic.
Can anybody tell me if there's something I'm missing? Anything left to try? Does it sound like a hardware/ROM/kernel problem? If it's hardware, can I still utilize the Samsung warranty after trying to flash custom ROMs? I'm going to try to download another Cellular South stock ROM, but it seems like the problems are persisting regardless of which ROM i have installed, so I think it's something else (kernel or hardware-related).
Any help is GREATLY appreciated. My new tablet is basically useless, and I've run out of ideas.

Try this latest firmware since you mentioned your tablet is the XAR model the firmware should be cellular south (wifi)
http://www.sammobile.com/firmwares/download/39630/T520UEUANK1_T520XARANK1_XAR.zip/
If that doesn't help then it could just be a bad tablet .
(btw when you flashed a custom rom you probably tripped the hardware knox flag and voided any warranty it had, I guess you could play dumb if they ask and say it came like that since it was refurbished, and hope they still repair/replace it)

I just tried the USA cellular south firmware. Still experiencing the exact same issues. I'm completely out of ideas. Does anyone else have any ideas? Otherwise I'm going to have to try warranty service and hope for the best. Is there anything I can do to restore the Knox flag before I send it in?
Also, in download mode the tab is recognizing the system as custom. Is this normal after flashing a stock image?

So do a factory reset in recovery, and clear the cache also. Then load the cellular South file thru Odin. Then factory reset again. See if this clears your problems.

k8108 said:
So do a factory reset in recovery, and clear the cache also. Then load the cellular South file thru Odin. Then factory reset again. See if this clears your problems.
Click to expand...
Click to collapse
I've tried the Cellular South firmware to no avail. I'll be trying to warranty the tablet now. Fingers crossed!