Hi, hoping someone can offer some advice/help here. First, my setup:
A500 with the v7 Bootloader, Thor's R169 Rom, Recovery 1.7.3 all of which are working just fine.
The problem I have, is the auto-rotate function does not work. I have tried all the suggested fixes I can find on both here and the Tegra Owners forums (and indeed every other link I can find through Google) and none of them work. I have also checked that the hardware switch is OK and it is functioning as it should. This problem has only appeared since installing ICS and applies to any Rom I try, with the auto-rotate not working in any Rom, or with any bootloader.
I have, of course, tried different bootloaders, different roms, full wipes, full formats of all partitions, factory resets, the pinhole reset and a number of different auto-rotate applications from the market. None of them make the slightest bit of difference and auto-rotate continues to be non-functional. Logcat shows continual "MLUpdateData error (code26)" errors with the hardware switch in the on position, and when I then switch it to the off position, shows "Error: illegal state transition from ML_STAT_SERIAL_CLOSED to ML_STATE_DMP_OPENED", followed by "vendor/3rdparty/Invensense/libservers/mlsdk/mllite/mldmp.c|MLDmpStop|161 returning 25
I am satisified from using a program called AdvancedTools from the market, that the sensors are functioning and responding to restart requests, although restarting the sensors using this app still makes no difference. Auto-rotate remains non-functional and nothing I have tried seems to change that.
To a layman like me, it seems like it may be a driver issue or perhaps a kernel issue. Anyone here able to help at all please ?
Hmmm....
60+ views and not a single response. Is it fair to assume that nobody has any idea what is causing this ? Am I the only person seeing this issue ?
phlashbios said:
60+ views and not a single response. Is it fair to assume that nobody has any idea what is causing this ? Am I the only person seeing this issue ?
Click to expand...
Click to collapse
I have the same issue, I do not know what to
Same issues here...
Take a look here:
http://forum.xda-developers.com/showthread.php?t=1690905
The only way that worked for me so far is:
Turn the auto rotation switch off
Power off
Power on
Put the auto rotation switch on
If I turn off the tablet with the switch ON none of the sensors works and you'll have to try a lot of times to make it work again..
Other users solved the problem:
- installing a HC bootloader
- Installing ICS V4 bootloader
- Performing real format before flashing the rom
Let me know what you've tried, we must find a solution!!!
OK, here's the current situation. I installed a stock HC ROM (Acer_A500_4.010.38_COM_GEN1) but left the v7 Bootloader still in place. ROM booted fine and works, but still no sensors working.
I then reflashed the Bootloader with a stock HC Bootloader and all the sensors work again.
This is clearly a Bootloader issue by the looks of it.
I am currently upgrading the Honeycomb 3.1 ROM as an OTA to 3.2.1 and will then update all apps, check all is working again and if so, install the Acer Update Updater and then do the OTA upgrade to ICS and check if all working again on stock ICS. Will report back later as to how things go.
OK, latest update following on from above.
Installed the Acer Update utility from the Marketplace
Updated OTA to stock 3.2. No issues, all working including sensors.
Updated OTA to stock 3.2.1. No issues, all working including sensors.
Updated existing systems Apps to current versions. No issues, all working including sensors
Updated OTA to stock ICS. Tablet boots, all OK and working, including sensors.
Reboot tablet, get a brief message that says Bootloader updating and then it boots into ICS. Sensors now stop working and no amount of fiddling with the rotation lock or factory resets or pinhole resets will make the sensors work again.
This to me is clearly an ICS Bootloader issue ? Anyone disagree ?
How on earth do I/we get this fixed ?
Well, after many hours of messing about, I have managed to get Thor's R169 ROM working and with the sensors working too. It has however required the use of the HC 3.01 Bootloader to have the sensors still working.
For the benefit of others who are facing similar difficulties, can I suggest the following course of action:
Install the APX drivers if you haven't already got them on your PC.
1. Put Thors ROM and Gapps on your SD card or on the Tab's own internal storage
2. Downgrade your existing setup to the unstable 3.01 Honeycomb
3. Use the AfterOTA v1.7 tool to install CWM on the old Honeycomb setup.
4. Boot into CWM Recovery and do the usual Factory Reset and wipe everything you can, including the Flexrom, Dalvik etc.
5. Install Thors ROM from your SD card/storage
6. Install Gapps from your SD card/storage
7. Reboot the tab into normal mode
Voila ! A working Thor ROM with working sensors.
What all my efforts tell me is that there is an issue with the ICS Bootloader and some tablets. Whether it is causing a race condition and not giving drivers time to start up, I am not sure, but restarting the drivers for the sensors makes no difference once the ICS Bootloader is installed. Any ICS Bootloader, including the stock one and all of Skrilax's from versions 3 through to 8, all result in no sensors working for me. This is clearly nothing to do with Skrilax, it is something inherent in the behaviour of the ICS Bootloaders.
For people using ICS ROM's other than Thor's, you will need to check whether they will behave with a HC Bootloader before installing them.
I can only pray that Thor and others continue to release ICS ROM's that are compatible with HC Bootloaders while someone, hopefully is able to figure out what is causing the ICS Bootloader issue.
Thanks all for those that offered advice and guidance. Your help is and will continue to be appreciated.
I am aware that references to Thor are not welcome in these forums. As I have not provided any links, or posted any attachments, I am hopeful that the mods here will see that I am trying to both seek help and indeed offer help to others rather than cause any issues. It could be any ROM this applies to, it just happens to be Thor's I am using.
use same rom thor169 bootloader v3 never botherd to upgrade to 4-5-6or 7
on mine rotation works with a ics v3 bootloader
Hmmm... that's very interesting, because mine definitely does not. My sensors do not work with the stock ICS Bootloader, or any of Skrillax's from v3 --> v8
I have also recently had some problems in this area. Started out as auto-rotate sticking whenever using an app that forced portrait. Then this morning went to flash v170 after being on flex rf1 v3 and auto-rotate quit completely. Tried twice with no luck. Over the past couple of days I have done multiple complete wipes and data formats. Did this again and did not work. So I restored a v169 backup and everything fine again. Flashed v170 and it's working fine. Possibly restoring to an older backup that worked (even if it was honeycomb) might help you. Oh yah, I was on bootloader v6 through all of this.
Hi all,
i has the same problem, sometimes works and sometimes not. now i have the v8 Bootloader, Recovery 1.7.3 and Tegraowners ICS ROM v170.
any ideas?
If you install a HC 3.01 Bootloader, I am pretty confident that will fix it, however, that's not really the answer to the problem, it's just a workaround. So far, nobody with the necessary skills seems to be interested in sorting out what's causing the problem when using the ICS Bootloader.
phlashbios said:
If you install a HC 3.01 Bootloader, I am pretty confident that will fix it, however, that's not really the answer to the problem, it's just a workaround. So far, nobody with the necessary skills seems to be interested in sorting out what's causing the problem when using the ICS Bootloader.
Click to expand...
Click to collapse
No one with the skills has the problem.. no one with the problem is providing real debugging information. (a logcat + dmesg just after boot might give a hint)
Many experience installing an ICS rom with the unlocked bootloader, and having the rotate fail on the first boot; however ensuring rotate is not locked and rebooting solved it for most users (and it never shows again).. If after this reboot its still failing you need to provide the logs above if you want a dev to have any chance.. and provide info that we are sure you have done this reboot. (and not just blindly downgraded to HC or another rom)
Also it helps to be sure what rom is being run..
ezterry said:
No one with the skills has the problem.. no one with the problem is providing real debugging information. (a logcat + dmesg just after boot might give a hint)
Many experience installing an ICS rom with the unlocked bootloader, and having the rotate fail on the first boot; however ensuring rotate is not locked and rebooting solved it for most users (and it never shows again).. If after this reboot its still failing you need to provide the logs above if you want a dev to have any chance.. and provide info that we are sure you have done this reboot. (and not just blindly downgraded to HC or another rom)
Also it helps to be sure what rom is being run..
Click to expand...
Click to collapse
Reset doesn´t help.
E/Sensors ( 144): MLUpdateData error (code 26)
I/ActivityManager( 144): START {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10000000 pkg=org.jtb.alogcat cmp=org.jtb.alogcat/.LogActivity bnds=[784,52][880,148]} from pid 366
I/dalvikvm( 1348): Turning on JNI app bug workarounds for target SDK version 11...
E/Sensors ( 144): MLUpdateData error (code 26)
I/ActivityManager( 144): Start proc org.jtb.alogcat for activity org.jtb.alogcat/.LogActivity: pid=1348 uid=10108 gids={1007, 1015}
D/OpenGLRenderer( 366): Flushing caches (mode 1)
E/Sensors ( 144): MLUpdateData error (code 26)
D/OpenGLRenderer( 366): Flushing caches (mode 0)
E/Sensors ( 144): MLUpdateData error (code 26)
E/Sensors ( 144): MLUpdateData error (code 26)
E/Sensors ( 144): MLUpdateData error (code 26)
E/Sensors ( 144): MLUpdateData error (code 26)
Related
3rd thread, about 4th rom flashed
constant issues with builds. have gone from stock to:
cm 6.1.3 -apps crashing, random crash notices i.e "phone book has crashed force close" - "the process com.android.phone has stopped unexpectedly"
cm 7 - random reboots, opening browser caused power cycle, wifi issues, lag (thread posted, no solutions at the forefront)
currently on tripnraver pre release. now another issue. no signal what so ever.
original baseband on this xperia x10a is .55. it is suggested to use with bands 52 or 49.
loading either of these basebands. which ive done. doesn't seem to fix the no signal problem. the description states should be backwards compatible even if appropriate bb is not installed on device. yet no luck.
attempting to flash either baseband fails to resolve this problem. currently trying to flash back to stock and try another full reinstall and baseband flash in flashtool.
any ideas would be a great help. having to flash x number of times between roms is getting quite time consuming
thanks everyone.
if you want to stay on the miui rom, you can flash the baseband patch located here and stay on whatever baseband works best for you (I'm on .55 and find it fantastic), then when you load the rom, go to dev tools>bad behaviour>crash the system server.
http://forum.xda-developers.com/showthread.php?t=1011608
Otherwise, I would recommend wolfbreaks cm 6.1.3, as it is the most stable. You must have done something wrong during installation as I never had an issue with his roms.
The only issue I have ever had with any rom is MiUi and thats because I used the wrong baseband. You must be doing something wrong for you to be having problems
if you want, try this flash, it's trips miui pre-final with the baseband patch implemented.
http://www.multiupload.com/KCKE9K2WKN
worked with my .54 baseband
thanks so much for the links to the baseband patches. i remember coming across a thread that posted it but unfortunately forgot to book mark. so im definitely going to go ahead and try with the patch installed. hopefully all works well
each rom ive flashed has been done properly according to instructions. cache wiped, dalvik, and full reset as per menu options in xrecovery.
one way or another i experienced lag for the most part, and as mentioned some random crashes. never had reset on wolfs rom just error messages at times. trips rom worked excellent, smooth and quick. hopefully with the patch implemented everything will work flawlessly
thanks you guys
*Updated
Flashed over rom with baseband patch. signal working. everything running smooth.
except for when using camera zoom. zoom default displays 0x. as soon as the option is selected it spawns an immediate force close
any patches? or similar outcome for anyone else?
i will outline my steps below so everyones up to speed on how i performed this flash.
- flashed back stock in SEUS
- root with one click (success)
- installed busy box (market)
- installed xrecovery apk
- booted into xrec
1. full factory reset
2. wipe cache
3. wipe dalvik cache
4. wipe battery stats
5. install custom zip from sd card
6. selected trips rom with bb patch implemented
5. reboot
Camera zoom doesn't work in most ROMs yet and the lag you were experiencing was likely just the FW "settling" it can take a little bit and a couple reboots sometimes for the phone to calibrate itself properly.
Sent from my X10i using XDA Premium App
thanks cmoney. maybe ill try my luck with cm7. give it a few reboots and hope for the best. great rom. im really loving trips iphonesque style
clean smooth and quick. everythings working great. hoping the zoom may get fixed soon enough. only other inquiry i have with regards to this rom is the apps2sd.
this feature is essential to myself personally. and it is not working as ive noticed on this rom. ive read a thread with regards to a fix for the last release. i checked the settings for an enable option in case the feature requires being manually set as active but nothing listed. within sd settings state reads as unavailable. if anyone has an answer as to whether this fix will function with the current pre release. ill be going ahead with completeling the flash and reporting what i find back on this thread.
thanks again everyone
Try Wolfbreaks rom. It's very very stable for me. It has cam and everything upto date.
im going to flash back to wolfbreaks updated 6.1.3 unless anyone can point me in the direction of a fix for trips rom.
the smooth and fluid feel of trips rom was brilliant. i am hopeful someone has directions for an apps2sd fix as i have flashed the build twice and the same issue has occured.
thesoundofsilence said:
im going to flash back to wolfbreaks updated 6.1.3 unless anyone can point me in the direction of a fix for trips rom.
the smooth and fluid feel of trips rom was brilliant. i am hopeful someone has directions for an apps2sd fix as i have flashed the build twice and the same issue has occured.
Click to expand...
Click to collapse
works for me on trips newest....
i just downloaded the new version 1.0
this is ridiculous. without the baseband patch. crash system server. no signal
now apps to sd is saying "apps2sd is not supported on this device"
this is an xperia x10, so obviously there must be something wrong here.
can anyone elaborate on exactly what to do about this because im going to attempt to flash back the rom, flash the bb patch right after, reboot. i assume this will only solve my signal issue. but this apps to sd is getting extremely frustrating and i can not figure out why it is not showing an enabled status.
- Flashed 1.0 with baseband patch - network signal resolved.
- apps to sd is STILL not working. and i really dont know what to do about this. everything else on this rom is perfect. is there something im missing? i came across a patch for apps2sd fix but this was for a previous version. would it be needed here? is there a setting that must be enabled first in order to start apps to sd as a service.
- as mentioned previously within the main menu, under sd card settings. message states "apps2sd is not supported on device" and on previous build would display "apps2sd unavailable". its simply impossible that the phone doesn't support it. as with every other rom the feature has worked. froyo would support it. the question is how do i go about enabling said feature?
thesoundofsilence said:
i just downloaded the new version 1.0
this is ridiculous. without the baseband patch. crash system server. no signal
now apps to sd is saying "apps2sd is not supported on this device"
this is an xperia x10, so obviously there must be something wrong here.
can anyone elaborate on exactly what to do about this because im going to attempt to flash back the rom, flash the bb patch right after, reboot. i assume this will only solve my signal issue. but this apps to sd is getting extremely frustrating and i can not figure out why it is not showing an enabled status.
- Flashed 1.0 with baseband patch - network signal resolved.
- apps to sd is STILL not working. and i really dont know what to do about this. everything else on this rom is perfect. is there something im missing? i came across a patch for apps2sd fix but this was for a previous version. would it be needed here? is there a setting that must be enabled first in order to start apps to sd as a service.
- as mentioned previously within the main menu, under sd card settings. message states "apps2sd is not supported on device" and on previous build would display "apps2sd unavailable". its simply impossible that the phone doesn't support it. as with every other rom the feature has worked. froyo would support it. the question is how do i go about enabling said feature?
Click to expand...
Click to collapse
I dunno man, it works fine for me, but I copied data from my 0.3.2 xrecovery image, so that might be why. try flashing that apps2sd fix for 0.3.2, should work fine
damn it. i just found that thread. found the links to the fixes. so far ive tried miui32_a2sd_fix.zip. and flashed that over with xrec prior to reboot. which did nothing.
there are two more links so im going to try those two flashes as well and hope that one of them will do the trick. if its working when utilizing .32 patches then ideally the bloody thing would have to work here. thanks for the input though dtox. much appreciated
I don't know what else to suggest man
From the feedback I see in the miui thread, everyone else is reporting it working!
Did you factory wipe, wipe cache partition, and wipe dalvik cache before install? then flash the miui 1.0.zip, and flash immediately the baseband patch then reboot into the rom.
Remember not all apps allow apps2sd so use something like android system info, go into the applications tab click on one, click manage and then see if the option "move to sd" is highlighted. Like I said check a few though, not all apps can be moved
i just replied in the dev section lol but yes i have gone ahead and checked the applications menu. specifically downloaded a file i have moved to sd on a previous occasion from the market.
nothing
the "apps to sd" selection is completely greyed out. no matter what application i click on or download. i did a full wipe, full install, and selected the apps2sd fix immediately after rom and bbpatch flash, prior to rebooting. issue still remains.
we'll see i guess. thanks again dtox
thesoundofsilence said:
i just replied in the dev section lol but yes i have gone ahead and checked the applications menu. specifically downloaded a file i have moved to sd on a previous occasion from the market.
nothing
the "apps to sd" selection is completely greyed out. no matter what application i click on or download. i did a full wipe, full install, and selected the apps2sd fix immediately after rom and bbpatch flash, prior to rebooting. issue still remains.
we'll see i guess. thanks again dtox
Click to expand...
Click to collapse
Try it again but without the fix...
i did that to it doesnt work i get the same message displayed
i tried with fix and without. another thing to note is that the rom itself says it should work with a different baseband as it has elements of unified. (which it doesn't) i had to flash the bb patch to get signal.
im not sure whats up with this but until i figure it out for a certainty ive flashed back over to wolf breaks rom. hopefully something will surface and i can give trips rom another go.
thesoundofsilence said:
i did that to it doesnt work i get the same message displayed
i tried with fix and without. another thing to note is that the rom itself says it should work with a different baseband as it has elements of unified. (which it doesn't) i had to flash the bb patch to get signal.
im not sure whats up with this but until i figure it out for a certainty ive flashed back over to wolf breaks rom. hopefully something will surface and i can give trips rom another go.
Click to expand...
Click to collapse
No idea man, like I said it is fine for everyone else so I'm so no big development will arise that will make it function with your phone....
maybe it has something to do with 10a. i dont know. but the point is it shouldn't even be doing this regardless. hypothetically if its froyo and it has apps2sd built in. it should work. its not the way ive flashed. the phone supports it. so my only conclusion the rom must not be as compatible as stated. and from reading different posts about the prev builds sometimes the patches worked at other times they didnt. and also the fact that the rom is claimed to work without the need for a bbpatch. yet without the patch instaled phone caught no single. i guess certain unexplainable glitches can be bound to happen at times but any how ill give it one last go.
if nothing comes out of that then im giving up on that build because it seems relatively hopeless.
lol I'm using an x10a...
Still man you're the only person reporting this. Don't you find that strange? What baseband are you using anyhow?
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.
The Official OTA 4.0.3 ICS update broke auto rotation. The rest of the thing is running smooth as butter, but no auto rotation and the switch isn't doing anything.
Anyone know of a fix to this? I had this prob with the leak but after rooting and reinstall leak from scratch it cured itself. This one isn't doing that.
Is there an app to set the orientation of the screen manually that i can use in the interim??
------------------------------------------
400+ Views later, i think quite a few people have this issue and are trying to find a solution to this.
So far, thank you networkdawg for your app suggestion for manually rotating the screen, however that is a paid for app with a few too many options for my need. I'm currently using Mantano Reader Free to rotate my screen.
https://play.google.com/store/apps/details?id=nl.fameit.rotate
------------------------------------------
Before i accidentally upgraded to the ICS leak, i had my old HC bootloader and was running Lightspeed flawlessly.
Does anyone know of a way to downgrade the bootloader back to HC so i can run a custom bootloader?
OR
a custom bootloader for ICS?
------------------------------------------
Ok so in the end i used jazzyjames' tutorial and blasted HC + HC Bootloader back onto my tab (accelerometer now working once more), rooted, ran Acer Recovery Installer and loaded Light Speed ICS once more.
Everything is working swimmingly. No issues and i got ICS running like a champ.
When the hardworking devs in the dev section have streamlined the ICS bootloader unlocker and installing of a custom recovery a little further, i may try the ICS bootloader once more. But for now, to just have a functional tab, im sticking with the old stuff a little longer.
Thanks Civato, Blackthund3r and jazzyjames for their excellent tools and tutorials. I could not have done it without their help.
------------------------------------------
Update May 08 2012
Did something new, reverted back to stock 3.2.1 (the Gen 2 that was used in Jazzy's revert tutorial), did an OTA upgrade to ICS Official. On first run everything worked.
The minute i rebooted, the accelerometer stopped working.
Followed Civato's tutorial down to the letter, got the custom ICS bootloader working with recovery. Ran like a charm.
Installed a custom ROM (Lightspeed), accelerometer was still not working.
MY TAKEAWAY ---- The accelerometer issues is not a problem with ICS itself, but related to the new chipset firmware and bootloader included with the ICS update. I could be wrong here.
Anyone have any other insights into this?
Back to HC bootloader once more (accelerometer working again) no dice with ICS bootloader :S
I'm not aware of any apps that will switch orientations, only lock it.
Have you tried switching the lock to off then rebooting to see if that resets it?
I have noticed the orientation check isn't as sensitive as it used to be so sometimes I have to wait a few extra seconds or orient the tablet a little more [than usual] to get it to switch over. But it does work.
I have the rotation problem also. As a workaround, I installed this and it works great, although manually.
https://play.google.com/store/apps/details?id=nl.fameit.rotate
veer01_42 I'd be interested in your review of that app if you use it and/or pay for it.
I have the same issue. I have a couple apps that are orientation locked and I can use them to rotate but it's very annoying. Hope this gets fixed soon
anyone try a factory reset to see if that fixed it
A factory reset fixed it for me
Sent from my PC36100 using XDA
Been factory resetting this thing all night, no beans at all.
With the 4.0.3 leak, after one reset it worked for me, but i never got it to repeat again. So don't go factory resetting your tab in a hurry if you know whats good for you, especially if your rotation is working.
Good app, lots of options, but for what i want, this app is too much and it puts an icon next to the clock for quick access, but you cant preset the orientations there. There are only three, locked, auto and whatever you have it in now.
To get to the other options, tap the notification and it brings up a menu with all the other orientations (over 10 of them) its too much for me. But its an extremely powerful app.
Not worth the money as a workaround to a stupid accelerometer.
Encountered the same issue. I was in Portrait mode, playing Draw Something, and suddenly it just rebooted and went into Landscape mode. After a factory reset, it is not fixed. Not sure where to go, but this is highly disappointing for a tablet I paid close to $500 for...
Try wipe cache, it works for me. All said methods in the forum doesn't work for my tablet though.
qpmzal said:
Try wipe cache, it works for me. All said methods in the forum doesn't work for my tablet though.
Click to expand...
Click to collapse
What cache?
Do you mean Pwr Button + Volume Up while toggling screen lock switch?
Or is it something else?
On some a500 that were rooted and accepted the ics ota, a few things got broken during the upgrade. Flash a stock rooted ice rom, but before you do go into recovery and and select backup an restore,click on toggle backup of internal storage. Then you should see enabled on the screen. Then do full reset in mounts and storage plus your normal wipe. This will fully format everything on your tab but sd . When you reflash the new ics rom everything should work fine.
You miss 100% of the shots you don't take....... ..Wayne Gretzky.......
Flash a stock rooted ice rom
Click to expand...
Click to collapse
You mean the 4.0.3 Leak, install that and then use the one click root tool available in the forum?
but before you do go into recovery and and select backup an restore,click on toggle backup of internal storage.
Click to expand...
Click to collapse
Are you talking about Installing the V3 ICS recovery or the original honeycomb?
Then you should see enabled on the screen. Then do full reset in mounts and storage plus your normal wipe. This will fully format everything on your tab but sd . When you reflash the new ics rom everything should work fine.
Click to expand...
Click to collapse
This is in the ICS V3 custom bootloader/recovery right?
variations on problem for different versions
More pieces to the puzzle.
I just downloaded and installed Acer_AV041_A500_1.041.00_WW_CUS1 (very close to stock OTA, but rooted) from XDA and applied it over the stock OTA I had received from Acer directly, Acer_AV041_A500_RV05RC01_PA_CUS1.
Under Acer_AV041_A500_1.041.00_WW_CUS1 screen rotation (and the error 26's) would not clear. I could not get the rotation to work at all, even with multiple reboots, and hard (pinhole) resets.
I restored to Acer_AV041_A500_RV05RC01_PA_CUS1 and rotation is back to it's unstable self, but at least a pinhole reset will clear it.
Hi guys, i have a problem... After a OTA 4.0.3 update my g-sensor won't work! I did a hard reset no effect... Downgrade to 3.2 - no effect... Guys plz, i really need help!
I had the same problem
After doing the OTA, rotation was down... i've rooted my tablet, and install a custom rom (FLEXREAPER-R14-1.033.00_1.031.00-ICS) but the problem was still there.
After many and many reboot/flash... i've decided to flash a last time the Flexreaper rom. After booting/configuring (problem still there of course), i've flashed with the light :
A500-1.031.00-LIGHT-WITH_ICS_BOOTLOADER 180MB.zip
from there : http://forum.xda-developers.com/showthread.php?t=1622425
But without wipe, by keeping the old configuration from Flexreaper rom. After flash, i've keeped my tablet horizontaly on a table during all the installation to keep the sensor in the same state during all the installation. At the first boot, i've the message "performing update xx/60" from ICS. Wait until update is finished.
Still without mooving the tablet, i've done a reboot ... and it works !
Then I've done again root/bootloader/recovery/kernel
And without wipe, i've flashed again the Flexreaper rom (tablet still on the table)
First boot and again a "perform update xx/68"
Reboot again and still without moving the tablet and it still work now !
To be sure, i've done a full wipe, and reinstall the rom. Rotation was blacked again, i've done alle the stuff below, and it works ...
As i said, i don't know if i'm lucky or not... But on my mind (i'm not a developper... so it's a full noob thinking) when ICS perform the update, it lock the sensor in his actual state...
Sorry for my poor english, but i hope it can help...
Edit : After few more reboot, the accelerometer crash again ...
After lot of more tests, i've found something interessing, that's my methode :
The first steps are maybe useless, i've found a solution after doing that, but i haven't test yet without:
*********************************************
Probably useless
*********************************************
1°) Boot in recovery
2°) Full wipe
3°) Flash rom from here : http://forum.xda-developers.com/showthread.php?t=1633907
4°) Reboot
5°) Configure account / settings
6°) Reboot in recovery
7°) Wipe data
8°) Flash rom from here http://forum.xda-developers.com/showthread.php?t=1517181 (or maybe other custom rom, i don't know yet if it works with others)
9°) reboot
You'll see the "performing optimisation" step and ICS will start.
Normaly, in my case, flip screen doesn't work, and wifi nether.
10°) go to "parameters/backup and restore" and do a factory reset from ICS
11°) Reboot
At this point, wifi is working but no screen rotation.
*********************************************
/Probably useless
*********************************************
Now the points i think usefull
12°) Lock screen with the top switch
13°) Reboot : Do this with your tablet on a table for providing mouvments
14°) when all is started, unlock screen with the top switch
Rotation should work.
Do the step 12->14 on every boot, it works for me.
I've also try (only one time... i've no more time to do more tests) to do steps 12->14 with the tablet in my hands, and it also works.
I've try to reboot normaly without locking screen, rotation was blocked again ...
I'll try tonight by doing a full wipe and flash a new rom without doing the steps 1->11, i'll let you know.
I hope it can help ! please tell me
On another forum I came to a fix that seems really strange but it worked for me and it's quite simple :
Turn off the tablet, then move repeatedly the rotation lock switch to on and off few times. Power the tablet up.
ty
Ty guys, but all ur suggestions won't help me...:-( any more ideas?
After installing DUALBOOT + RECOVERY and ICS 4.0.3/FLEXREAPER-RF1-V5.1 i am unable to turn my wifi on if anyone could please help i would be very grateful thx.
Its ok I just restored my backup and it working now dont know why it didnt work on the rom.
Same issue; tried three different ICS roms and none will allow me to turn wifi on.
Just guessing, but I would say
1. You didn't do complete wipes/formats in Recovery before installing the rom. This is usually the primary reason as sometimes code from the previous rom, is still there.
2. You installed an HC bootloader version? And not the one for ICS (although I heard the devs mostly dropped support for the HC bootloaders and ICS.
But, if you have the ICS patched V8 bootloader, I would go with option 1 And make sure the rom you are installing, is for the bootloader you currently have.
MD