Database Users

[Q] Unable to pull down notification bar after 4.3 update (stock firmware)

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

Big problems after update for Android 7

Hello,
Yesterday i receive the notification for update for android nougat in my phone. The update ends without any problem but right now with this new firmware I have 3 BIG problems:
Back camera don't work > The camera apps open the front camera and i don't have the button to switch for the other camera.
Flash don't work > Flashlight app only controls the screen but do nothing to the flash.
Laser: The app for measure with the laser don´t open.
I already have done a factory reset without any success.
I already enter in safe mode without success.
I already clear all the cache without success.
Any ideas?
Are someone with the same problem?
Thanks!

Hi I updated my Zenfon 3 to Android 7 two wks ago after receive the msg from Asus. After reading your posting, I try all the problems mentioned in your article but it don't exist (maybe I'm lucky), in fact some of the pre exist (problem come with my purchase) problem such as the ear-phone connection problem has resolved. I have yet to find any major bugs in my Zenfon 3 yet. Overall I'm happy with the update.

Try reinstalling the ota. Flash via bootloader. Get the update file via asus site

I have done that but without success

I haven't experienced any issues. I factory reset right after updating though - you may want to give that a try.

DOall said:
I have done that but without success
Click to expand...
Click to collapse
If that is the case it may already be a phone issue. Flashing a device will do a clean install of the software. So any software issues should be resolved.
I suggest trying downgrading to the very first os in the asus site. Make sure you're using the same version though

Overall errors

Hi, I'm fairly new to XDA so please forgive me for my newbieness.
I recently purchased the Axon 7 but I got a lot of problems with it to which I can't find solutions here or elsewhere on the internet:
- I can't update my device, I have now A2017GV1.0.0B06 but whenever I try to update, it fails
- I can't open photos/videos in Whatsapp (crash), can't send photos/videos in Facebook messenger (just won't do it without explanation). I checked the permisions which all seem to be fine
- I got random app crashes all the time, sometimes it even uninstalls them.
- The device itself reboots every so often randomly, once or twice a day
For the most part the device works okay, but these problems just drive me insane sometimes.
Would it be a software related error, which I can maybe solve by whiping it clean all again (I had problems since the start so I doubt this would work), or by maybe rooting it?
I must say that I bought the device second hand, but it barely had been used before (everything without any scratches and fairly new in the box). So maybe that's the reason?
Many thanks,
~Pr0fviktorie

I would do a factory wrote and that the system firmware. That should solve the issues as it definitely sounds software related.
Sent from my ZTE A2017 using Tapatalk

May very well be why it was sold lol.
Regarding updating firmware, the official advice is to update to B10 MM before diving straight to Nougat.
I assume the update zip file is at least detected by system updater?

Pr0fviktorie said:
Hi, I'm fairly new to XDA so please forgive me for my newbieness.
I recently purchased the Axon 7 but I got a lot of problems with it to which I can't find solutions here or elsewhere on the internet:
- I can't update my device, I have now A2017GV1.0.0B06 but whenever I try to update, it fails
- I can't open photos/videos in Whatsapp (crash), can't send photos/videos in Facebook messenger (just won't do it without explanation). I checked the permisions which all seem to be fine
- I got random app crashes all the time, sometimes it even uninstalls them.
- The device itself reboots every so often randomly, once or twice a day
For the most part the device works okay, but these problems just drive me insane sometimes.
Would it be a software related error, which I can maybe solve by whiping it clean all again (I had problems since the start so I doubt this would work), or by maybe rooting it?
I must say that I bought the device second hand, but it barely had been used before (everything without any scratches and fairly new in the box). So maybe that's the reason?
Many thanks,
~Pr0fviktorie
Click to expand...
Click to collapse
I had the random reboot stuff too. Tried reflashing but what really fixed it was going to a custom ROM for a couple of months then flashing the stock recovery and installing the update from there
But if you don't wanna go the warranty voiding route do this:
Download Marshmallow B11 (I think it's 1.0.0B11)
Download Nougat B02 (I think it's 1.2.0B02 or 1.1.0B02, don't remember)
Update to Marshmallow B11
Now try updating to Nougat B02
---------- Post added at 04:33 PM ---------- Previous post was at 04:32 PM ----------
Hamburgle4 said:
May very well be why it was sold lol.
Regarding updating firmware, the official advice is to update to B10 MM before diving straight to Nougat.
Click to expand...
Click to collapse
wasn't B11 for that?

Choose an username... said:
wasn't B11 for that?
Click to expand...
Click to collapse
Probably. I'm just reading off the Aus firmware instructions page! Only making sure they aren't trying to jump directly to Nougat from B06 MM.

Hamburgle4 said:
Probably. I'm just reading off the Aus firmware instructions page! Only making sure they aren't trying to jump directly to Nougat from B06 MM.
Click to expand...
Click to collapse
Yeah I guess it fails because he's trying to update from B06. I'll delete the recovery part on my post just to be sure

Thanks for the suggestions, I suppose I have to do it manually?
The OTA update I am getting is MM B11, but that doesn't work. When installing it fails at around 40% and when I check why, it says that 'The system update package did not match the phone'. Would it work if I try it manually?

Pr0fviktorie said:
Thanks for the suggestions, I suppose I have to do it manually?
The OTA update I am getting is MM B11, but that doesn't work. When installing it fails at around 40% and when I check why, it says that 'The system update package did not match the phone'. Would it work if I try it manually?
Click to expand...
Click to collapse
Yeah I'd try what Choose suggested.
You can find the full update files in this thread: https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547

GPS not working after downgrade to Nougat.

Hi
My phone is LG V20 F800K and i wasn't getting oreo update via OTA, so i manually downloaded the files from LG Firmware and installed oreo but then faced horrible battery timing issues so i reverted back to android 7.0 after testing one week on oreo. I did all this using LG UP tool via Uppercut.
Now that i am on stock nougat again, everything else is fine even the battery timing is perfect now as before but now the GPS is not working at all. It displays that it is searching for my location and it never shows it. I tried it in Google find my device app, then Google maps and then thought there might be some else issue, so i tried installing GPS check and fix apps from play store, but all of them just keep searching but nothing happens.
I flashed the stock 7.0 from above mentioned site and even the software version is same which was before i.e. F800K 10E. What is wrong with my phone? Can anyone please help?

Hi
I came back to reply because the problem resolved with a little tweak.
I found this thread on reddit and i tried doing that as a hope of making this happen myself and not spend money for this. I tried cleaning the top points shown in the picture of the reddit link and screwed back in. When i tried it didn't work. Then i just tightened the screws and it worked. So if anyone else is also facing same issues, this might resolve.
https://www.reddit.com/r/lgv20/comments/7fx2gz/becareful_buying_the_top_plastic_bezel_of_the_v20/

Flashlight being used by another app. Camera doesn't work

After flashing the unbranded firmware and rooting the phone, I'm not able to use the camera app. Opening it just says "Camera Failed. In the slide down menu, the flashlight icon is turned on even though I'm not actually using the flashlight. and I cant turn it off either. How do I fix this?
I've tried: clearing data & cache of camera app, clearing the cache partition, setting default settings of the camera app, changed camera storage from SD card to internal & vice versa

TommyQuid said:
After flashing the unbranded firmware and rooting the phone, I'm not able to use the camera app. Opening it just says "Camera Failed. In the slide down menu, the flashlight icon is turned on even though I'm not actually using the flashlight. and I cant turn it off either. How do I fix this?
I've tried: clearing data & cache of camera app, clearing the cache partition, setting default settings of the camera app, changed camera storage from SD card to internal & vice versa
Click to expand...
Click to collapse
Sucks no one responded to your post. I rooted my sons S7 Edge and sometime after it acquired the same issue yours has/has. I had another S7 Edge phone so I ended up rooting that one and giving it to him. I still have his old one with the camera fail issue but I've yet to try to figure out what caused it to happen. I know my response doesn't help with info or duration from OP post to reply, I just wanted to let you know that your post wasn't ignored by everyone. Unfortunately I have nothing substantial to contribute.

kanesglove said:
Sucks no one responded to your post. I rooted my sons S7 Edge and sometime after it acquired the same issue yours has/has. I had another S7 Edge phone so I ended up rooting that one and giving it to him. I still have his old one with the camera fail issue but I've yet to try to figure out what caused it to happen. I know my response doesn't help with info or duration from OP post to reply, I just wanted to let you know that your post wasn't ignored by everyone. Unfortunately I have nothing substantial to contribute.
Click to expand...
Click to collapse
So I ended up putting that phone back to stock then rooting it again and it had the exact same issue yours has. I did a clean root too and the issue is still present. From there I decided to again run it back to stock and this time do a nand erase all and repartition the device. After all was finished I checked the device and I'll be goddamned... it still has the same issue. So if the problem persists after all that reformatting is it safe to say that it's a hardware issue? I'm out of ideas. Sorry I couldn't help you.

kanesglove said:
So I ended up putting that phone back to stock then rooting it again and it had the exact same issue yours has. I did a clean root too and the issue is still present. From there I decided to again run it back to stock and this time do a nand erase all and repartition the device. After all was finished I checked the device and I'll be goddamned... it still has the same issue. So if the problem persists after all that reformatting is it safe to say that it's a hardware issue? I'm out of ideas. Sorry I couldn't help you.
Click to expand...
Click to collapse
you guys offer little information at all so this is why no one helps you. Maybe tell what firmware version you flashed what root version you did etc. There is a big difference between bootloader revB/11 and the others

Holy ****. Did I just get constructive suggestions from jrkruse?! Dude if you told me I could fix my phone by sucking a fart out of a wallaby's ass I'd do it cuz the advice came from you, and if there's one thing I know it's that you know your ****. You're ****in' awesome. I feel so special now. Ok sorry about that...
Well, I'm not too sure about the OP but I can tell you about the phone I have that seems to have the same issue.
My S7 Edge is a SM-G935V on android 7.0 on update 4BQK2. Prior to rooting I put everything to stock then I did a NAND erase and repartition. No issues with any of that.
I rooted my phone from this post
G935V Root Method. No Lag! No Heat!
G935V Root Method. No Lag! No Heat!
I AM NOT RESPONSIBLE FOR ANY OF YOUR ISSUES! ALL I CAN DO IS RECOMMEND A GOOD PSYCHOLOGIST! Hey guys. Stumbled on this by accident. I HAVE ABSOLUTELY NO IDEA WHY IT WORKS, BUT IT DOES. THE METHOD HAS BEEN TESTED BY ME AND A FEW OTHER PEOPLE HERE...
forum.xda-developers.com
which directs to your older method for gaining root privileges.
[DISCONTINUED] ROOT Method For Nougat
DISCONTINUED New Thread Found Here This Root Method For S7 Nougat Nougat_S7_Root_2_82_All_Carriers_V2.zip Includes Fingerprint Fix [Latest Verison] Nougat_S7_Root_2_81_All_Carriers_V2.zip Includes Fingerprint Fix Nougat_S7_Root_2_79_All.zip...
forum.xda-developers.com
I also flashed Unzip the Nougat_S7_Root_2_82_All_Carriers_V2.
Then I flashed the BL file in the BL slot from the G935U firmware with odin checking "Phone Bootloader Update". I used the BL file from G935UUES4BRA1 since it's the closest update for the U brand to the firmware this phone is on (G935VVRU4BQK2)
I'm aware that there are newer methods for gaining root access but I chose this method cuz I used it back in 2017-2018, I had read all the posts in the thread, and I knew it worked.
I currently have 3 S7 Edge phones all on the same firmware and build and are all rooted with the same combo method I just explained. The other 2 phones also have xposed installed and they both work well.. expect mine says weird stuff instead of the callers information. I think it only does it if they're a contact but in the notification tab it says an example like this 5556661234;verstat=No-TN-Validation. No clue how to fix that.
The phone that is having the same issue as the OP still had access to the private/secure folder when it was rooted; which I thought was weird cuz mine doesn't and from what I understood private mode gets disabled if the phone's rooted. Maybe it only gets disabled if you install xposed? I don't know. My son had the phone with the issue and it was his first smart phone and he dropped it a few times (with a case) so I was thinking it's an effect from something he downloaded from the play store (he's 20 now but pretty still very ignorant with android). Now I'm not sure if it's a software or hardware issue since the problem persisted after the NAND erase.
Something to note about my sons old phone also is that it has 2 thin pink lines running down one side of the screen (defective/dead pixels) and when the screen turns off it it flashes once before actually turning off. One time over the phone I tried troubleshooting the issue with him and he ended up being able to use his camera immediately after rebooting the phone though once he exited the camera app it wouldn't open again. We were trying a bunch of things, force closing any app I thought would be related to the issue. Not sure what allowed it work when it did, but even now right after a reboot the camera app still crashes.

This was long ago, I've since lost the phone. But, I was on the A bootloader and on OREO rooted using @/billa's method using an ENGboot file. I tried everything possible to get the camera to work including flashing back to stock but nothing helped. I just gave up finally. @kanesglove maybe try safely updating the firmware. Hope it helps