Related
Hey guys!
Got a little problem here!
Here's the situation, I'm perfectly able to flash CM6.10 (? - The latest stable for Wildfire anyway), but I've had no luck when trying to flash CM7. Either, it gets stuck at the white HTC splash after flashing and rebooting, or it gets stuck at the CM splash screen. The arrow just stops moving around in circles and freezes!
Not completely sure what this could be, I clear everything before I flash CM7 so ... And I ofc admit that I'm no sort of expert in this area, as almost every single flash has been perfectly fine to me, so I thought that you guys could figure this one out .
Regards
Try flashing kernel v4.1 from the HCDR.Kernel thread from the Wildfire Android Development Zone. Since you say you have cleared everything as stated by the first post in CM7, guess I wont be going into that.
I actually tried that as a last resort before going to bed yesterday, and that solved the problem! So thanks anyway, you were right !
Later on I installed the Gapps for CM7, but then when i booted my phone, i got the "Low Memory"-warning that wants you to remove some apps, and all the apps started to crash all the time. Especially the browser, not entirely sure of what's causing all this!
Hi,
I had the same boot problem and 4.1 also fixed it for me. I've not had any low memory issues but I only really have the google applications... One problem I do have is that I don't seem to be able to pair with any Bluetooth devices, I just don't get long enough to type in the PIN!
Can't post a report on the dev thread as I'm new here...
Andy
PS Which 6.10 have you been using? Did you have any Bluetooth issues?
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.
Installed ICS fine using Acer_AV041_A500_1.031.00_WW_GEN1.zip from here: http://vache-android.com/v1/index.php?site=files&file=151 , renamed to update.zip, stick it on the root of the SD and powered up with vol down.
Have struck an issue though: following the update my a500 reboots back to the android boot animation as soon as it has established a wifi connection. As long as I leave wifi turned off it runs fine. I don't think it's related to this particular package though, a bit of googling has revealed others who updated using the OTA and encountered the same issue. The only way they've found to resolve it is a factory reset. Ugh!
Anyone have any brighter ideas before I take the plunge and spend the rest of the weekend downloading apps and re-configuring my tab?
I am having the exact same problem. Did the upgrade the the update.zip that was released and worked fine for others. Mine runs fine until wifi is turned on, then it reboots. I am only able to stop the reboots is by turning off wifi, obviously not suitable for. Anyone find a solution yet? Glad to see I am not the Lone Stranger here.
+1 here... strange issue. Got the OTA btw.
Did a search but have not seen any thread on this, so apologies if I have missed something.
I've just encountered this today and not sure what to make of it. i9000 been on CM9 nightly without issues until I woke up this morning, backlight was on (nothing unusual, just emails overnight), but it will not wake up no matter what I pressed (home button, power button etc.). So ended popping the battery out and start it up again.
This is when the strangest thing happen, loaded the usual Galaxy logo screen, then into the CyanogenMod screen, seconds later, it restarted. This boot loop went on forever. Doing VOL UP + HOME + POWER does not get me back into recovery. At this stage, I am on CM9 nightly 20120707, with CWM 6.0.0.3 (I think).
I ended up having to Odin flash back to GB 2.3.6 (XXJVU) and start over again. And I thought that was the end of it. Picked up the latest nightly 20120728 and RC2, and I ended up with the same symptom. I.e. post WIPE (Data / System / Cache) and loaded CM9 of both version (plus Gapps loaded), all ended in the aforementioned bootloop. Have also tried fixed permission as well in between tries to load CM9.
Spent a bit more time on this and I am now on the unofficial CM10 (not that I am complaining ), but this is very strange to me. Has anyone ever experienced this? It seems that I have no way of getting back in CM9.
I was running cm9 nightlies until I flashed cm10 (which is amazing ) and had no issues with it what so ever :S
I don't think I've heard of any cases of what happened to you, happening elsewhere
I'd just stick with cm10
Happened to me, too. I solved the problem flashing a previous build of CM9 and a previous build of Gapps - it seems like Gapps was the problem.
After popping out battery, insert batt., start download mode, Odin flash Semaphore ICS kernel as PDA, re-partition unticked.
Enjoy
The Semaphore dev has a thread about this. A number of people have experienced what you say with a combination of different ROMs and kernels. Check it out on development thread
Sent from my GT-I9000 using xda premium
Cheers for the reply fellas. Will check out Semaphore. Interesting though as I've always thought "stock" CM9 was just easy as.
Hello all,
My apologies if this is a common issue. I have searched but the only old thread about it is the following:
http://forum.xda-developers.com/showthread.php?t=2190960
and no real answer was suggested there, which is why I am asking it again.
So the issue is the same as in that previous thread: quite often, when I longpress the power button, the menu (to shut down, put it on vibrate mode, ...) does not pop up. The only way to get it back is to hold the power button until the phone shuts down, and then reboot the phone, after which it works again (for god knows how long).
I was rooted (with stock rom) before 4.3, but lost my root when updating to 4.3, so I was on stock ROM without root when the problem first appeared. Now yesterday I rooted again and flashed paranoid android ROM (first factory reset, clearing cache and dalvik cache), but the problem remains.
In that old thread one member solved the problem by flashing the stock kernel, however I have never flashed another kernel so I doubt the kernel is the problem?
If anybody knows the issue and a way to solve it, please let me know, it would be greatly appreciated.
Thanks,
Maarten
You did flash a kernel when you flashed the rom
Wayne Tech Nexus
Hey there
No, as in the first post, I have never flashed another kernel on the nexus. Neither did I flash a new radio.
I had not flashed anything yet when the problem started, I only unlocked the bootloader and rooted my phone when I first got it (but it worked a long time without any problems)
Delete this post
Nobody had this issue ?
Found a solution at last!!
wolfway said:
Nobody had this issue ?
Click to expand...
Click to collapse
After quite a long search and a lot of worries, I finally found THE solution...
https://www.youtube.com/watch?v=d8dbrerUacw
how to get out of factory mode for a s4 but it worked on my N7105
- efs/factoryApp/factorymode/ouvrir avec/editeur de texte/ON
- efs/factoryApp/keystr/ouvrir avec/editeur de texte/ON
I have this issue too. I'm using paranoid Android beta 4 with franco kernel and since The moment o rooted my phone this issue started
Sent from my Nexus 4 using XDA Free mobile app