Related
I recently updated my Galaxy S4 (i9500) to Android 4.3 [MJ5] using Kies. The phone is completly stock and non-rooted. After the update, I'm unable to pull down notification bar. However, after I restart the device, it works well for some time and then again refuses to be pulled down.
Has anyone else experienced the same problem? I have lot of data on the device that will be difficult to restore and hence and donot want to format the phone. Any suggestions/solutions that might resolve the problem?
Also, after the 4.3 update, when I check for OTA, a popup shows saying "Your device has been modified. Software updates are not available." Pulling out and reinserting SD card didn't solve the issue.
Same problem. .. No solution yet.
arpit88 said:
I recently updated my Galaxy S4 (i9500) to Android 4.3 [MJ5] using Kies. The phone is completly stock and non-rooted. After the update, I'm unable to pull down notification bar. However, after I restart the device, it works well for some time and then again refuses to be pulled down.
Has anyone else experienced the same problem? I have lot of data on the device that will be difficult to restore and hence and donot want to format the phone. Any suggestions/solutions that might resolve the problem?
Also, after the 4.3 update, when I check for OTA, a popup shows saying "Your device has been modified. Software updates are not available." Pulling out and reinserting SD card didn't solve the issue.
Click to expand...
Click to collapse
I am going mentally insane trying to figure this out. I have refreshed and wiped my phone 5 times for the same issue, but to nothing good. The notification bar simply wouldn't want to respond.
What's getting to my nerves is that in one of my experiments with solving this issue, I kept my phone as stock with no third party apps, and still faced the issue. I kept knox uninstalled thinking that's what is causing the issue, but that's didn't help. I did lots of these kind of attempts, but to no avail. I'm concluding that is a serious Bug that Samsung is not going to address to soon. And we're simply screwed until.
Same problem.. DEAL BREAKER
I am facing the same problem after update to 4.3 Andrew this is a deal breaker if Samsung does not fix immediately. Thinking of rooting Andrew moving to cyanogen mod beta.. This is crazy. Nobody tested this for sure.
4.3 official update notification panel drop down problem
I have same problem with this update.can anybody solve this problem ?
kish0007 said:
I am going mentally insane trying to figure this out. I have refreshed and wiped my phone 5 times for the same issue, but to nothing good. The notification bar simply wouldn't want to respond.
What's getting to my nerves is that in one of my experiments with solving this issue, I kept my phone as stock with no third party apps, and still faced the issue. I kept knox uninstalled thinking that's what is causing the issue, but that's didn't help. I did lots of these kind of attempts, but to no avail. I'm concluding that is a serious Bug that Samsung is not going to address to soon. And we're simply screwed until.
Click to expand...
Click to collapse
Is your device status showing as "CUSTOM" or "ORIGINAL"?
figured out temporary solution
After a lot of playing around, I seem to know what's causing the problem. It's the Phone (Dialer) application that is creating an issue.
when the problem arises again, try making a call, and while the call is being placed, pull down the notification bar....It begins working.
obv I Ousby this is no permanent solution, but will help you from needing to restart.
If anyone with deeper knowledge can PLEASE look at what from the inside is causing it, and how can we make a permanent fix, much appreciated.
let me know if it works for you, the temp fix.
---------- Post added at 09:03 AM ---------- Previous post was at 08:55 AM ----------
[/QUOTE=arpit88;46809031]Is your device status showing as "CUSTOM" or "ORIGINAL"?[/QUOTE]
Mine says official, for you, I'd suggesting finding the correct 4.3 version with the correct region for your i9500 / i9505, and redo the firmware. Download the firmware off Sammobile, and use Odin 1.85 whilst your phone is in download mode. If you don't know any of these terms used, Google it. It'll be helpful.
Basically, the notification bar problem and device modified problem are separate issues.
Did u install the indian firmware or the unknown one?
yes boys same issue here after 4.3 installed
also my notification bar when its stacked works when you try it on a call but its a temporary solution. mine is official also. anybody find a permanent solution? should we again root 4.3 on 4.3? I think it must be that the 4.3 was installed over 4.2.2 maybe if we make hard reset it will be fixed?
It's the Indian firmware, that I downloaded using Kies but still it started showing as "custom".
I took the phone to samsung care, they said Official 4.3 isn't released for s4 in India yet. Lolz. However, then one of there geeky employees reinstalled the 4.3 update and now my both issues have been fixed. Notification bar is now working perfectly fine and Device status is now Official.
official 4.3 also problem task bar
mine is official because in germany 4.3 is released on samsungs update and my phone is from germany. sould I take it to samsung service and they reinstalling again 4.3 is finally fixed?
xxuemj8
I got an ota update xxuemj8 just now that seemingly has solved the problem. My test so far hasn't given complaints, but.let's see what's the situation in long term.
Indian version i9500 currently updated from xxuemj5 to xxuemj8
Should solve all your problems too if you refresh your phone with Odin. Meaning reinstall from fresh by downloading from sammobile and.installing.through Odin
UPDATE XXUEMJ8 doesnt help
Update: XXUEMJ8 doesnt solve any problem. The bug still exists, notification bar stops working.
Also, another issue is that under Settings > Battery, even if Wi-Fi is switched off, the wifi blue bar shows full all the time as if it were ON.
This confuses me to if this is only a software bug in displaying the battery status of settings where wifi is truly off, and it thinks it is on.
OR
Wifi remains on throughout, and switching it off in the software doesnt actually switch it off, eventually taking more battery.
kish0007 said:
I got an ota update xxuemj8 just now that seemingly has solved the problem. My test so far hasn't given complaints, but.let's see what's the situation in long term.
Indian version i9500 currently updated from xxuemj5 to xxuemj8
Should solve all your problems too if you refresh your phone with Odin. Meaning reinstall from fresh by downloading from sammobile and.installing.through Odin
Click to expand...
Click to collapse
Android 4.3 Update
I DEFINITELY AGREE with the earlier post by Kish0007. The bug is related to the PHONE (Dialer) App. The problem always occurs after receiving a phone call.
I changed from German Android 4.3 to Unknown Android 4.3 as posted on Sammobile hoping for the problem to disappear. But it did not !
Mich
The possible solution is to format your phone after installing 4.3 upgrade.
Goto Hard reset by pressing your Volume Key+Power key+Home Key......
Then goto Wipe data/Factory reset.........Don't worry your android Upgrade will not be reset, it will be as it is (4.3)....just it will format your data
and cache.
Do not forget to take backup of apps and your other data......!!
It worked for me & hope it will work for you as well........!!
I try format several times but problem still exist
update the firmware before format.
After upgrading your OS , please update the firmware from PDA:MJ5 to PDA:MJ8 also,
then try formatting.
Same problem after updating on my Samsung S4
Same problem after updating on my Samsung S4.
I have the Middle east version UAE. MJ5 build number currently.
i noticed the dialor was started this issue.
i hope there is a solution for this soon.
still issue after hard reset
Sid0406 said:
The possible solution is to format your phone after installing 4.3 upgrade.
Goto Hard reset by pressing your Volume Key+Power key+Home Key......
Then goto Wipe data/Factory reset.........Don't worry your android Upgrade will not be reset, it will be as it is (4.3)....just it will format your data
and cache.
Do not forget to take backup of apps and your other data......!!
It worked for me & hope it will work for you as well........!!
Click to expand...
Click to collapse
I made hard reset on my phone and tha issue still exists. from samsung service they told me its possible the viber on 4.3 that makes the problem so I unistall it I made hard reset but I still have stacked tool bar sometimes after receiving or making calls but no so often.
notification bar problem
I updated my s4 i9500 to 4.3 indian ver. INU mj5 via kies and recently MJ8.. and same problem happening to me... notification bar would not pull down on call ends... calling again fixes the problem but thats kind of annoying every time for fix..... even transition animation scale resets on opening camera app.... then I thought to give a clean install via odin on same firmware from sammobile... ie. INU MJ8 21 oct build.... but this even did not solve the above problems. .. I also uninstalled viber thinking it might be the cause.... factory reset... cache wipe ... everything but to no avail.... any permanent fix would be appreciated. ...
Phone Settings
Guys,
Do you have the phone setting answer call using the power button selected ? Please, let me know. My notification bar never crashed today after I un-selected this option.
Thanks,
Mich
Hi! I recently updated my i9505 to the xugng8 firmware via kies. Ever since, my phone has been randomly rebooting itself. The reboots are quick enough, so it doesn't look like the phone is completely rebooting, more like a half reboot. I have tried formating, but that didn't help. I have the phone rooted but using stock firmware.
Any ideas what could be causing this? Thanks
juzzy16 said:
Hi! I recently updated my i9505 to the xugng8 firmware via kies. Ever since, my phone has been randomly rebooting itself. The reboots are quick enough, so it doesn't look like the phone is completely rebooting, more like a half reboot. I have tried formating, but that didn't help. I have the phone rooted but using stock firmware.
Any ideas what could be causing this? Thanks
Click to expand...
Click to collapse
You have to uninstall every Knox app, that will stop the reboots
Sent from my Galaxy S4 using Tapatalk
juzzy16 said:
Hi! I recently updated my i9505 to the xugng8 firmware via kies. Ever since, my phone has been randomly rebooting itself. The reboots are quick enough, so it doesn't look like the phone is completely rebooting, more like a half reboot. I have tried formating, but that didn't help. I have the phone rooted but using stock firmware.
Any ideas what could be causing this? Thanks
Click to expand...
Click to collapse
Remove all Knox related apps via "Titanium Backup" and you are good to go. :good:
there is also an xposed module that deals with these random reboots, but personally i think the best way is to revert to an earlier firmware. fnb8 is rock solid.
I have just upgraded my firmware to NG8 (UK) and my phone reboots randomly, no matter what I am doing. After receiving a call, using gmaps, etc..
I will try the suggested solution with removing the knox sh*t and report back.
Yes
juzzy16 said:
Hi! I recently updated my i9505 to the xugng8 firmware via kies. Ever since, my phone has been randomly rebooting itself. The reboots are quick enough, so it doesn't look like the phone is completely rebooting, more like a half reboot. I have tried formating, but that didn't help. I have the phone rooted but using stock firmware.
Any ideas what could be causing this? Thanks
Click to expand...
Click to collapse
Yes, same problem here exactly. Any solution to fix this WITHOUT ROOT or reverting back to xxufnb9 ?
I found that uninstalling all knox apps and resetting a private app fixed my problem. I have been restart free for the last 2 days! I suggest using BBS to find out what app is causing wakes and reset them.
nm8 said:
I have just upgraded my firmware to NG8 (UK) and my phone reboots randomly, no matter what I am doing. After receiving a call, using gmaps, etc..
I will try the suggested solution with removing the knox sh*t and report back.
Click to expand...
Click to collapse
wuwinso said:
Yes, same problem here exactly. Any solution to fix this WITHOUT ROOT or reverting back to UGNF ?
Click to expand...
Click to collapse
juzzy16 said:
I found that uninstalling all knox apps and resetting a private app fixed my problem. I have been restart free for the last 2 days! I suggest using BBS to find out what app is causing wakes and reset them.
Click to expand...
Click to collapse
yup same here after reading this thread and removing all knox crap.... phone has not had a self reboot reboot for the day...
Revert
Had to reflash the old XXUFNB9, it was useless with all those restarts. Downgrade went okey, however need to delete the Media Storage `s cache because it will keep crashing. Testing now if it solved the problem.
Update 1: after 2 hours later no restart so far..
I recommend this solution who doesn`t want to loose everything and risking if a factory reset will solve this issue. There is a problem with the KNOX 2.0 update (XXUGNG8) ...
Update 2: Link for the firmware, for whoever choose to do this way: http://www.sammobile.com/firmwares/3/?download=31852
Ok, just a quick update, I have used googlemaps for 2 hours, and tomtom navigator for 1 hour on my S4, made and received a few calls without issue. No REBOOTS.. I think it was definitely the knox crap...
juzzy16 said:
I found that uninstalling all knox apps and resetting a private app fixed my problem. I have been restart free for the last 2 days! I suggest using BBS to find out what app is causing wakes and reset them.
Click to expand...
Click to collapse
nm8 said:
Ok, just a quick update, I have used googlemaps for 2 hours, and tomtom navigator for 1 hour on my S4, made and received a few calls without issue. No REBOOTS.. I think it was definitely the knox crap...
Click to expand...
Click to collapse
Stabil for 3 hours or 2 days - well that's for sure great ....
You both must be joking - take older NB8 and you can have an uptime of > 1 month without any problem,
All newer version are worse -
As s.o. mentioned, there is an Xposed Modul made by Thomas Hofmann that tries to solve this. This is not a Knox problem but seems to be in AOSP itself - although might mainly be triggered by Knox 2.0 (NB8 is still Knox 1.0). In general situation goes worse the more processes are started, i.e. with heavy load. It is said to happen not only with S4 but e.g. also with N3.
As Thomas Hofmann stated: "I figured out that actually the system server process crashed due to an ArrayIndexOutOfBoundsException"
If you want to know details plz have a look at Thomas's blog. With his modul he mainly catches a faulty parameter value that would otherwise cause a certain method to crash. As a result he manages to avoid the reboot but of course the real problem goes deeper, so to fix this for real Google / Samsung are needed.
=> I want a 4.4.4 rom with towelroot fixed, without those ArrayIndexOutOfBoundsExceptions and as solid as NB8 - but I doubt Samsung is able or willing to do this.
I am using STOCK i9505 4.4.2 ROM which is rooted. I don't use towelroot because I don't have to. I also try to stay away from premade Roms and Kernels beause i don't have time to test and tinker with eveything.
After a few days of removing knoxcrap, I can conclude, that it is the issue with my phone. My i9505 is now working perfectly......
Have to agree with you. Since removing all the knox stuff, Haven't had a reboot since! Been over a week now at this stage!
nm8 said:
I am using STOCK i9505 4.4.2 ROM which is rooted. I don't use towelroot because I don't have to. I also try to stay away from premade Roms and Kernels beause i don't have time to test and tinker with eveything.
After a few days of removing knoxcrap, I can conclude, that it is the issue with my phone. My i9505 is now working perfectly......
Click to expand...
Click to collapse
no random rebooting anymore xugng8 firmware
juzzy16 said:
Hi! I recently updated my i9505 to the xugng8 firmware via kies. Ever since, my phone has been randomly rebooting itself. The reboots are quick enough, so it doesn't look like the phone is completely rebooting, more like a half reboot. I have tried formating, but that didn't help. I have the phone rooted but using stock firmware.
Any ideas what could be causing this? Thanks
Click to expand...
Click to collapse
i have sorted my i9505 to the xugng8 firmware by re-installing with latest odin...download fresh stock firmware xugng8 firmware and i re-installed 2 weeks now no reboot ,but make sure before you do these steps usb debuging mode is selected ,rest you all know
nm8 said:
I don't use towelroot because I don't have to.
Click to expand...
Click to collapse
Yes, many think this to be a nice 'feature' to get root, but that rediculous. Towelroot (plus the older Exynos bug - but that was Samsung specific) is the biggest bug in Android since many years. Using a kernel that is not hardened against this (this unfortunately includes the otherwise almost perfect NB8 rom) could mean you couldn't be save anymore from someone taking over your phone unnoticed using root authorization.
---------- Post added at 02:20 PM ---------- Previous post was at 02:08 PM ----------
juzzy16 said:
Have to agree with you. Since removing all the knox stuff, Haven't had a reboot since! Been over a week now at this stage!
Click to expand...
Click to collapse
As said those reboots most certaintly are caused by a bug in AOSP code itself - but in fact they seem to be mainly triggered by Knox 2.0. Otherwise a lot more phones other than S4 or N3 should be involved.
As we will never know fpr sure if and when Google/Samsung will solve the real reason of this problem and "removing" Knox 2.0 seems to help, it would be very nice of you (juzzy16, nm8, sneazy) to perhaps add another comment in 2-3 weeks about reboot behaviour again including the rom version you are using and what exactly of Knox you had removed.:good:
Volume is absolutely up, I don't have it on silent mode or priority mode only or anything, plus alarm doesn't make sound and some other things, just to clarify I'm not being dumb.
Any app that tries to produce sound crashes, like if I play a video on YouTube or in Chrome, if I open anything like AudioFX or what have you.
I think the most important thing is that this is occurring on every ROM, and I don't know what to do. I just fixed my data issue that was persistent on every ROM, but this is more important to me because I need my phone for an alarm clock among other things.
I have wiped, wiped, and wiped again. I flashed stock Touchwiz, tried older nightlies of CM12 I know were fine, tried other ROMs, etc. It doesn't make a difference, the effect is still the same no matter what.
I have tried pluggging in and unplugging headphones over and over. There isn't even an indication it's plugged in. There's also no way in hell I damaged the speaker or anything, and that wouldn't really explain crashes on YouTube and so forth anyway.
I have reset, without a charger plugged in over 10 times. Powered off and on 10 times. This was apparently a solution to a similar issue with the Nexus 5 on Lollipop. But do note that this issue isn't even restricted to Lollipop.
Please, if anyone has any ideas, even if they probably won't work, I'm pretty desperate to get this working again.
I solved it. It's caused by the NAE modem for some reason. Flashing any previous modem has working audio, and flashing NAE again breaks it again (just to verify that was the cause).
I don't know much about it, but how does the modem have any effect on audio?
PwnCloud said:
I solved it. It's caused by the NAE modem for some reason. Flashing any previous modem has working audio, and flashing NAE again breaks it again (just to verify that was the cause).
I don't know much about it, but how does the modem have any effect on audio?
Click to expand...
Click to collapse
Dang had I seen this earlier I would a told you exactly what you found. I had same issue going from MF9 modem to NAE. Trick is to flash MK(whatever number) boot up normally, then reboot and flash NAE modem and boot. Cheers!
Sent from my SPH-L720 using XDA Free mobile app
I had similar problem...had tried everything and then some. Was about to flash odin that revererted everything to stock unrooted. Was going to take in to sprint. Noticed files to download mismatched mine so odin back to mk2 and had sound so moved on up to NAE and still had sound. Then on to 4.4.2 rom and NG2 and all good. Go figure...was coming on here to tell you Glad u got it.
I have an extremely persistent set of problems:
1. Unable to record video
- stock camera freezes and the phone restarts (no matter the resolution or storage)
- other camera apps (mx, open, google..) either freezes or acts like its recording but it doesn't
2. While playing some videos, the phone freezes and restarts (in 90% its instagram videos, but sometimes it plays them fine)
What i tried:
- a bunch of roms. The problems probably started with some of them.
- returned to a stock lolipop
- several custom and stock kernels
- a bunch of camera apps
Currently i'm on Audax rom v26.1 with its audax kernel.
Does anyone have idea what could i try?
Could it be a hardware problem? (other than that, camera works fine)
Thanks in advance.
So I solved it by:
Using Odin 3.11.1
I have already tried Factory reset, wipe cache, wipe dalvik, flashed the latest stock Lolipop or older lollipop with ODin and nothing solved the problem.
So I tried to flash the latest stock lolipop with Odin and marking checked (Auto Reboot , F. Reset Time , Phone EFS clear, Phone Bootloader update).
I suspect that the Phone EFS clear did the trick. It's function is related to the modem and radio of the phone. And clearly the modem has a problem here.
I hope this will help anybody out there having this issue.
This problem happened after trying to flash lollipop using FlashFire app to reserve the root that I had in my previos Android KK 4.4.2.
Phone: Galaxy Note3 N9005 Malaysian
hayder78 said:
So I solved it by:
Using Odin 3.11.1
I have already tried Factory reset, wipe cache, wipe dalvik, flashed the latest stock Lolipop or older lollipop with ODin and nothing solved the problem.
So I tried to flash the latest stock lolipop with Odin and marking checked (Auto Reboot , F. Reset Time , Phone EFS clear, Phone Bootloader update).
I suspect that the Phone EFS clear did the trick. It's function is related to the modem and radio of the phone. And clearly the modem has a problem here.
I hope this will help anybody out there having this issue.
This problem happened after trying to flash lollipop using FlashFire app to reserve the root that I had in my previos Android KK 4.4.2.
Phone: Galaxy Note3 N9005 Malaysian
Click to expand...
Click to collapse
Hi Bro,
I have same kind of issue posted here.
https://forum.xda-developers.com/htc-explorer/help/sound-speaker-mic-headphones-hardware-t3608070
Can you help me on this or give some idea?
jmsrajkumar said:
Hi Bro,
I have same kind of issue posted here.
https://forum.xda-developers.com/htc-explorer/help/sound-speaker-mic-headphones-hardware-t3608070
Can you help me on this or give some idea?
Click to expand...
Click to collapse
Hi there,
Sorry, but did not face any issue like that before.
If you have searched a lot for a solution and could not solve it, I suggest that you install this ROM:
https://forum.xda-developers.com/galaxy-note-3/development/purify-cm-13-hlte-n9005-unofficial-cm13-t3337234
This happened to me once after a terrible mistake , which is not related to my above issue. Then I installed this ROM and never looked back. Much snappier phone, lower battery usage and less heated device. I just love it. The only thing that I missed, the better camera app in the stock ROM, and the TouchWiz ability to show multiple apps at the same time.
I strongly suggest that you do a Nandroid backup then give this ROM a try. If you did not like it, you can always return to the Nandroid backup again.
You are frustrated now, like I was. Take a deep breath, and remember that we all went through such bad times with our phone, not just you. This is part of the experience of using such complicated devices. You will solve it eventually, believe me!
Hello everybody!
Not quite sure if it fits here... If it doesn't, please move it to the correct forum.
I tried to upgrade to Oreo from a rooted phone, it got softbricked and I somehow made it work again. I'm now on OOS 5.1.3, unrooted. Ever since my phone worked again, I experience issues with jetAudio.
No matter what file I play, I hear occasional crackling and interruptions, sometimes only on one channel, sometimes on both. I didn't experience the audio issues with any other audio playing app. Clearing cache or reinstalling didn't help. I somehow get the feeling Oreo messed with permissions or something.
Any idea how I can make the app work again? Would it help to reset the device? Thanks for reading!