Related
Hi all, I was wondering if you could help with an annoying issue I'm having.
I made a big mistake by updating to an ICS Rom, it worked fine apart from the accelerometer which stopped 100%. I did a backup, but system crashed and that's the end of that backup
1: I've since downgraded to Honey Comb Acer_A500_7.14.14_COM_GEN1, but Accelerometer still won't work, I don't know why, is there some fix or file to replace or anything like that.
2: Second question, because I updated to ICS the boot loader got updated also, is there a way to revert the boot loader back to the original so the end product would be a 100% original
This is a 16GB UK version of the A500, so any help would really be grateful. Even if I can get both the boot loader and OS to original I can then send it off to Acer for repair.
Kindest Regards to all
Garret
Man, I don't have an Acer iconia, but I have a Samsung galaxy player 5.0 and I just experienced the same issue after trying an ICS ROM.
When I searched for a way to solve my problem, I've seen many many users (increasingly, indeed) with the same kind of problem. It's hard to think that so many users are having accelerometer hardware fail. I believe it's not physical problem, mostly because this kind of issue happens after ppl try modding their phones/tabs or changing roms. I've seen some users talking about removing a sensorfile yamaha.cfg and trying to reboot the device. That didn't solve my problem, or executing:
"sensorcalibutil_yamaha"
It is under /system/bin/, you can see that with root explore.
Unfortunately, didn't work for me. Hope it works for you.
Best regards.
Thanks for your reply, I found a way of down grading the bootloader and OS to 3.0.2 which fixed it, then updated the odds to the latest and back working 100%.
Hello, same issue for me, accelerometer doesn't work anymore! I had yesterday the official ICS fota. Is there a patch somewhere for this problem?
after official Acer ICS update - Accelerometer quit?
My A500 pad just quit doing auto-rotate just about 30 mins after I applied the "official" ICS update to my device. I haven't done anything different, I did lock the pad into portrait to read some stuff, but unlocked it (manual switch) and it was fine then all of a sudden - it stopped rotating between portrait and landscape. The switch now has no effect on it. Of course there's not a setting to change the rotation either. Argh? I was so excited to get ICS - not this goofs on me? I see quite a lot of posts about people who experience this from hacking around on their tablet or phone - I haven't hacked on this one at all - its the "official" stuff... Reset didn't help.
bthorsberg said:
My A500 pad just quit doing auto-rotate just about 30 mins after I applied the "official" ICS update to my device. I haven't done anything different, I did lock the pad into portrait to read some stuff, but unlocked it (manual switch) and it was fine then all of a sudden - it stopped rotating between portrait and landscape. The switch now has no effect on it. Of course there's not a setting to change the rotation either. Argh? I was so excited to get ICS - not this goofs on me? I see quite a lot of posts about people who experience this from hacking around on their tablet or phone - I haven't hacked on this one at all - its the "official" stuff... Reset didn't help.
Click to expand...
Click to collapse
This is the same issue I have on the leak version.
Sent from my PC36100 using XDA
gbyrne2011 said:
Thanks for your reply, I found a way of down grading the bootloader and OS to 3.0.2 which fixed it, then updated the odds to the latest and back working 100%.
Click to expand...
Click to collapse
I need to do the exact same thing. Could you please let me know what you did to start all over and get all the OTAs?
Thanks!
One could conjecture that if the accelerometer is stuffed, so would the orientation detection be.
Cause and effect?
Z.
Sent from my A501 using Tapatalk 2
Same here but a reboot cured it.
anyone find a fix for this ? im on the official with no root ics update and mine has also stopped auto rotating.
What did you use to do the downgrade back to 3.0.2?
gr8buddha said:
anyone find a fix for this ? im on the official with no root ics update and mine has also stopped auto rotating.
Click to expand...
Click to collapse
The only solution I found so far is keepin rebooting, eventually at some point accelerometer starts to work.
Best regards.
Sent from my GT-I9000 using XDA
If any off you had a leak and altered boot loader prior to install, it may have caused that. You should have had a 2 step optimizing process in the update, when I tested it on a leaked/flashed back version the bootloader was wrogn and that issue resulted. The stock had no issue and went through the full hardware optimizing process.
Also you shoudl have applied the market place update first, it has a pre fix to prepare it for patching.
Hey guys, i also have the same issue with accelerometer. I downgraded the a500 to Honeycomb and it fixed now.
I followed this guide: http://forum.xda-developers.com/showthread.php?t=1516012
Rollback OS + Bootloader back to Rooted HC 3.2.1
Use this to Rollback OS + Bootloader back to Rooted HC 3.2.1
WARNING EXTREMELY DANGEROUS | YMMV | WARNING EXTREMELY DANGEROUS
http://forum.xda-developers.com/showthread.php?t=1516012
WARNING EXTREMELY DANGEROUS | YMMV | WARNING EXTREMELY DANGEROUS
the guides to rollback posted above can be used on an official pad , with no hack or root stuffs ?
No, it rolls you back to rooted 3.2.1. with stock bootloader. Once ur back, you can load your official 3.2 rom on an SD, use Pwr + Volume down to update to it. Then OTA to ICS.
Just saw a guy posted a system of methods to completely wipe all the system files (not just most) and clean install ICS which supposedly fixes the accelerometer problem.
Accelerometer / ICS
I sent my tab back to Acer for repair, they say they replaced the "motherboard" and it did work fine on stock ICS as returned for a while. Periodically it would stick in orientation and not auto-rotate, but a power cycle with a few minutes in between seemed to always bring it back ok. NOW - nothing I do brings it back - its working the very same way it was when it originally experienced this issue. I don't want to send this slab back to Acer every couple of months and deal with setting it back up when they ship it to me a week or so later. This is rediculous or am I just being picky?
Anyhow - How bout a reference or link for the info on downgrading, wiping ICS and re-installing from scratch as mentioned above? That would be helpful if I knew where to look.
UPDATE: This morning, based on another post about finding errors in the bootlog, I downloaded the bootlog capture app, ran it, and poof - the auto-rotate function came back to life - like magic. I'm sure it was NOT the app, but rather the fact that I had powered down the unit and let it sit all night long without touching it or powering it on/off, etc. so at least for now, I won't be sending it back to Acer for Warranty repair (AGAIN). BUT I might be listing it rather quickly on ebay and shopping for another tab that doesn't have this issue....
I have had this issue and normally a power cycle fixes it. I did have one time where it did not but I found an article that said to do a hard reset. You do this with a paper clip pushed into the very small hole. I did not lose any data.
Marc
Sent from my A500 using xda app-developers app
take a look at this. It work for me.
http://androidforums.com/acer-iconi...veral-a500-ics-related-symptoms-problems.html........
delete the last dots.
Hello folks,
I've been using a few builds of ParanoidAndroid on my 16gb N7 (grouper) for quite some time.
Last update, thou, has broken my tab's NFC. Whatever NFC signal I try to use (tag, N4, Gnex), nothing happens, not even an error message. I tried several restoration and full wipes with no success and then decided I might as well go back to stock since 4.2.2 seems to fix most issues I had with it.
So I flashed the latest factory image, with a clean install (manually erased boot, system, userdata, etc. thru fastboot) and the problem is still here ! I performed 2 more factory reset without any success.
So before I return my tab (and that will be annoying cause it's probably gonna take them a month before it comes back), is there a way that would help me check if the problem is hardware or sofware related ? If it's software, there has to be a way I can fix it myself, so I won't bother send it to be repaired.
Any help would be appreciated, thanks a lot to anyone.
(and sorry if this question already exists, I couldn't find a thread about it).
You've already eliminated the probability of it being software.
Sent from my Nexus 7 using Tapatalk HD
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 everyone.
I have encountered a problem on my phone's rear camera with the latest ROM upgrade, which upgraded my android version fom 4.2.2 to 4.3:
I9505XXUEMJ7_I9505BTUEMJ8_BTU
The problem is that I get a dark display (black screen, see the attached screenshot) and the whole phone gets stucked and its performance is slowed down due to that. After about a minute or to of freezing phone I Finally get a warning - Camera Failed.
I tried to wipe twice (both cache partition and user data), prior to and after flashing, and also tried to reflash the same rom again. Didn't work out for me, or at least works once right after wiping and then fails again. Seems like a heavy bug in 4.3, unstables the camera due to the new firmware.
Has anyone had that same problem or reported on it or it's just me? What should I do now?
Thanks.
When you open the camera, did you get a camera firmware update?
Crauze said:
When you open the camera, did you get a camera firmware update?
Click to expand...
Click to collapse
Yes, that was in the first time that opened the built-in camera app after flashing the newest firmware. I proceeded with the update and then all that mess started. But since then I have reflashed and didn't get that message once more to confirm/approve.
Is there a way to downgrade the camera's firmware to the one used in 4.2.2? It really worked really well for me prior to that so called "upgrade"...
Another question: When (roughly) should I9505 models recieve the 4.3.1 update? Is it scheduled to be soon?
Having the same issue (also with other Camera apps like Barcode Scanner, Paper Camera & Optical Reader). If I wait I end up with a "camera fail" message.
UPDATE: Just upgraded to MK8 version using Kies - and the problem persists!
This month's (november) update implies that Samsung are yet to resolve this bug. Does someone know how should I report them about the problem? Is there a website or a social network page that they actually check up on a regular basis?
Thank you.
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