Everything on home screens disappear only wallpaper on screen - Acer Iconia A500

Hello im have a problem where all my apps,shortcuts and UI randomly disappear or my screen and the only thing left is my wallpaper. The only way i resolve it is to go to settings/apps/launcher and force close it. It restarts but its just a temp fix cause randomly it happens again. I have tried Multiple Flexreaper,Thor, and Cm9 roms Multiple bootloaders and Kernals but it always comes back. I ALWAYS do a full wipe (by wiping everything even data) but after a while it comes back. Anyone know how to fix it or Any info would be great thanks

I can't help with a fix, but I can confirm that you are not the only one with this issue. I have three Acer tabs, One that's stock ICS A500 no root, one A500 with V3 bootloader and Flexreaper, and one stock rooted ICS with the V8 bootloader. All three do this same thing. The only way that I can get rid of the issue is to downgrade to the Honeycomb bootloader. If it was any more annoying I would go back to the Honeycomb bootloader and pretend to be a chicken while enjoying my nice solid user experience. I'm not sure how Acer bugged it up on this one. But as far as I can tell, it is an Acer ICS bootloader problem that carries over even if the bootloader is patched.
I've been trying to find a solution. So far, other than changing back to HCBL, nothing has worked. It's too bad that one of the Dev's can't see a tablet with this issue. Those guys can fix about anything...

Thak you for the info. Its good to know Im not the only one who has this problem. Do you think CM10 will fix it since its Jellybean?

I never experienced that issue...until I moved to Jelly Bean. It happened all the time on the first alpha port, but the latest cm10 is OK. I hasn't happen since. What launcher are you using?

I've tried a ton of launchers and it happens on them all. Also, it happens less frequently if I don't have a email widget on a home screen.

I'v also tried alot of launchers and they all do the same. Thanks for the email widget tip

Has there been any new developments on this issue and how to fix it?

I'm on hc bootloader and never have that problem. I am fully capable of flashing ICS bootloader, but have no interest in doing so. I see no clear advantage and hear nothing but problems. I'm running the newest TO Jelly Bean and it is practically flawless. Call me a chicken if you like, but I'm a happy chicken with a sweet tablet
Sent from my HTC One S using xda app-developers app

It happens to me all the time with all the launchers I 've tried. I am in unlocked ics bootloader and stock rom. The same happened with the locked bootloader. I tried the CM10 Rom same results. I removed all widgets from the homescreen with no luck.
If it's in the ICS Bootloader then all must have the same problem or not?
Any solution except going back to 3.2?

To fix it I had to go full stock to Honey Comb then reinstall CWM then install Thor cm v15 and no problems since. I think the problem is the ICS bootloader

Related

[Q] Tablet boots OK but one issue

I just flashed my tablet with 4.0.3 ICS and now before the android logo and after the acer logo for a couple seconds it looks like an old tv with just multicolored "snow". I have tried every ICS rom here. How would I fix this boot issue?
That is a known issue with the ICS ROMs unless a fix has just been found there isn't one
So it is just a normal thing right now?
It's not normal, for someone not used to it, it could be scary.
the first time a booted up the leaked ICS, i was stressed (was my flash successful ? will the tablet boot and let me use ics ?) about it.
Let me restate that statment. It, currently, is something I have to deal with, for the time being, and is a "normal" bug in the ICS ROMs. Would the this be an accurate statement of my prediciment. So, there is no fix either?
thomasb9511 said:
Let me restate that statment. It, currently, is something I have to deal with, for the time being, and is a "normal" bug in the ICS ROMs. Would the this be an accurate statement of my prediciment. So, there is no fix either?
Click to expand...
Click to collapse
That is correct. At the moment, I don't believe there is a fix (remember, it is just a pre-release leak that the rom is based off of). Don't worry, I'm sure it will be fixed soon enough.
It has to do with the kernel and is a very common problem on devices running Android when the kernel is leaked and no source code is available. The Evo 4g and Evo 3d used to do the same thing when they were first rooted. It is nothing to worry about and should disappear when the kernels start getting cooked.
Sent from my A500 using Tapatalk

How doi I get to ICS?

In December, when I picked up my TF101, I used Razorclaw + CWM to root it. I also found some kind of an update here that I applied that allowed me to overlock the device .. I believe it was a form of kernel patch?
I would like to go to ICS. I need to be rooted after ICS though, we have a VPN client for our SonicWall firewall that requires the OS to be rooted. I would also prefer an ICS port that supports overclocking like my current build .. it's been incredibly useful to clock up in to the 1400s as it makes everything run so much better.
Is it possible to upgrade to the stock ICS, root it easily and patch it to allow for overclocking at this time? If so, could someone direct me to a guide that shows what the easiest way to do this is, since I already have CWM in (although can't remember how to get it to come up on boot .. doh)?
Thanks =)
Wait till Asus fix the problems.
Yea dont install ICS, it would be like pouring water over your PC
It might seem fun at the time, but its really not a good idea
I would say it is a very bad idea. Avoid it. I did it and literally my tablet is unusable now because of
Slow response
Random rebooted
Random no message crash of apps like gmail.
Dead slow,app response
white screen on app loading
It is now embarrassing infront of ipad users.
Sent from my Transformer TF101 using Tapatalk
spinaldex said:
In December, when I picked up my TF101, I used Razorclaw + CWM to root it. I also found some kind of an update here that I applied that allowed me to overlock the device .. I believe it was a form of kernel patch?
I would like to go to ICS. I need to be rooted after ICS though, we have a VPN client for our SonicWall firewall that requires the OS to be rooted. I would also prefer an ICS port that supports overclocking like my current build .. it's been incredibly useful to clock up in to the 1400s as it makes everything run so much better.
Is it possible to upgrade to the stock ICS, root it easily and patch it to allow for overclocking at this time? If so, could someone direct me to a guide that shows what the easiest way to do this is, since I already have CWM in (although can't remember how to get it to come up on boot .. doh)?
Thanks =)
Click to expand...
Click to collapse
Ignore the fear mongering posters.
Tons of people are using ICS without issues. But yes, some do experience issues.
Since you have CWM, you can directly flash the pre-rooted stock ICS. http://forum.xda-developers.com/showthread.php?t=1552303 This is the latest 9.2.1.17 version.
If you want to overclock, you can flash custom ICS ROMs that support overclocking. There's only 2 at the moment, Team EOS and Codename Android.
Frequently updated custom ICS roms such as Team EOS and CM9 tend to be very stable and have fixes that stock ICS doesn't have, so flash a custom ROM instead of the stock ROM if you are concerned about possible issues.
As always, do factory reset + clear cache + clear dalvik cache within CWM before flashing the stock ROM or any custom ROM.
To be safe, I would update your CWM to the latest version here http://forum.xda-developers.com/showthread.php?t=1213723 before flashing anything.
horndroid said:
Ignore the fear mongering posters.
Tons of people are using ICS without issues. But yes, some do experience issues.
Since you have CWM, you can directly flash the pre-rooted stock ICS. http://forum.xda-developers.com/showthread.php?t=1552303 This is the latest 9.2.1.17 version.
If you want to overclock, you can flash custom ICS ROMs that support overclocking. There's only 2 at the moment, Team EOS and Codename Android.
Frequently updated custom ICS roms such as Team EOS and CM9 tend to be very stable and have fixes that stock ICS doesn't have, so flash a custom ROM instead of the stock ROM if you are concerned about possible issues.
As always, do factory reset + clear cache + clear dalvik cache within CWM before flashing the stock ROM or any custom ROM.
To be safe, I would update your CWM to the latest version here http://forum.xda-developers.com/showthread.php?t=1213723 before flashing anything.
Click to expand...
Click to collapse
Terrible advise.
Why tell someone to update to an OS that has literally flooded XDA and other forums, and ASUS's facebook page with people saying their TF is no longer usable ?
For the sake of waiting for a working update, why suggest doing something that could very well turn their TF into a buggy POS ?
There is nothing in ICS that is worth the risk
*Detection* said:
Terrible advise.
Why tell someone to update to an OS that has literally flooded XDA and other forums, and ASUS's facebook page with people saying their TF is no longer usable ?
For the sake of waiting for a working update, why suggest doing something that could very well turn their TF into a buggy POS ?
There is nothing in ICS that is worth the risk
Click to expand...
Click to collapse
There are just as many people, probably much much more, who aren't having problems.
Besides, have you tried any custom ROMs? If not, stfu.
I would no say my TF is unusable under ICS.
It works fine, apart from not so random reboots, as it reboots mainly in the morning when I wake it up form the night...
maybe the Sleeping Beauty requires a kiss from the Prince ...
By the way, it used to be really better under HoneyComb, I wish i could have refused that damned firmware upgrade ...
If I were you I'd rather wait as an other poster said for a really proven Stable version from Asus
Nickola
horndroid said:
There are just as many people, probably much much more, who aren't having problems.
Besides, have you tried any custom ROMs? If not, stfu.
Click to expand...
Click to collapse
Who the F are you telling to stfu ?
Of course I have tried custom ROMs you doosh, I just prefer to have a stock TF, well, I did until ASUS decided to send out buggy sh**
*Detection* said:
Who the F are you telling to stfu ?
Of course I have tried custom ROMs you doosh, I just prefer to have a stock TF, well, I did until ASUS decided to send out buggy sh**
Click to expand...
Click to collapse
If you are using one of the better custom ICS roms and still having such bad issues, the problem is you and your apps since those AOSP roms aren't even based on Asus's ICS.
The OP has root and CWM, and wants to overclock. So how was it a bad advice to recommend a custom ICS rom?
Just because you are having issues, doesn't mean everyone else will.
I've never had any issues at all and I just got done testing like 5 different ROMs. No issues whatsoever. Probably because I do it correctly and do a full wipe including format /system before I flash anything.
I've got issues on Stock and I did a full wipe using voldn+power method and this was before I rooted. I also lost sound randomly on Stock, and the custom kernels I still get reboots but my sound for the main part does work.
So, if the OP needs their tablet to work correctly then wait, if it's not that important to them and they don't need for day to day tasks then take a chance, you might get lucky or you might be causing yourself a headache, up to you.
horndroid said:
If you are using one of the better custom ICS roms and still having such bad issues, the problem is you and your apps since those AOSP roms aren't even based on Asus's ICS.
The OP has root and CWM, and wants to overclock. So how was it a bad advice to recommend a custom ICS rom?
Just because you are having issues, doesn't mean everyone else will.
I've never had any issues at all and I just got done testing like 5 different ROMs. No issues whatsoever. Probably because I do it correctly and do a full wipe including format /system before I flash anything.
Click to expand...
Click to collapse
How is the problem me when I am doing everything the "ASUS way" ?
The problem is ASUS and their code.
If you read the OP's actual post, you will see this line
"Is it possible to upgrade to the stock ICS"
And if you want to go even further into it, your line "Probably because I do it correctly and do a full wipe including format /system before I flash anything"
I don't think you can get a cleaner flash than NVFLASH, which is how I always flash my ROMs

Stop the bleeding, downgrade to HC

!!! Attention !!!
.24 seems to be even more imminent, so if you have any patience left, wait for it, otherwise keep on reading
#########
Couldn't take the infant ICS anymore, the RR & SOD, broken sound, gmail freezing etc. Waited a while for fixes but my patience ran out.
If you decide to downgrade via flashing stock images, you will quickly discover yourself in a maze of inter dependencies, missing downloads etc, conflicting & not working root methods.
Instead, flash the Revolver 3.11 (fetch one from Dev Thread) - doable via CW or NVFlash. You will get up-to-date HC distro, rooted & all, with barely any effort at all.
rashid11 said:
Instead, flash the Revolver 3.11 (fetch one from Dev Thread) - doable via CW or NVFlash. You will get up-to-date HC distro, rooted & all, with barely any effort at all.
Click to expand...
Click to collapse
If you're flashing a custom ROM, why not try one of the ICS custom ROM? I don't have RR or SOD with Megatron ROM or any of the ICS ROM I've tried
baseballfanz said:
If you're flashing a custom ROM, why not try one of the ICS custom ROM? I don't have RR or SOD with Megatron ROM or any of the ICS ROM I've tried
Click to expand...
Click to collapse
Same here, other than the latest ICS test Kernel I have seen little to no problems since upgrading to ICS.
glad to hear that ICS's been trouble-free for some folx here, and God knows I tried too, but simply had to back off and wait till 100% stable ICS is released - ASUS or custom ROMs.
I think most of us wuz caught by surprise with ICS instability, we were used so much to how rock stable HC had become around late fall of 2011, ASUS or custom ROMs.
Or save your self the pain, since it isn't going to help much, refurting back to HC. and read Gary's last update:
5/14/2012 Update -
The .24 release should go to FOTA later today or early tomorrow. Please shutdown and perform a cold boot after updating.
Click to expand...
Click to collapse
gkillerx said:
Or save your self the pain, since it isn't going to help much, refurting back to HC. and read Gary's last update:
Click to expand...
Click to collapse
Where did you get this from?
hey, if that .24 thing works (as in proven) and we have a nice pre-rooted NVFlash or CW image out, I won't hesitate going back to HC ... but for now I need something I could rely on
baseballfanz said:
If you're flashing a custom ROM, why not try one of the ICS custom ROM? I don't have RR or SOD with Megatron ROM or any of the ICS ROM I've tried
Click to expand...
Click to collapse
I Was on Megatron and had daily (sometimes multiple per day) SOD's. The problem is at the kernel level, with something that is common to *any* ICS ROM, stock or custom.
Even with guevor's kernel I still had the SOD's. I stopped trying when he was at the 17c version, I think, and nvflashed prime (I posted a quick guide somewhere).
If you want stock, there are guides to go from custom HC ROM's to stock which are simpler than going from ICS to stock HC.
I don't know what you guys are doing to have such bad luck on ICS, but my experience with Team Eos ICS has been absolutely pleasant. Absolutely every minor shortcoming that the tf101 had on HC (like video playback, stuttery transitions, "white boxing" in the browser, etc) is improved or fixed completely in ICS.
The ONLY problem I have with ICS is that the one single app I depend on every day for work is incompatible with ICS - not a fault of ICS, but the developer of that app. Thats why of my two tf101s, one of them is still running HC (Prime 2.1.1)
None of us doubt the evolutionary nature of ICS and we all will gladly upgrade to ICS when the issues are fixed. For now, some require tablets that are good enough to be relied on.
The "wait a for a full moon, have 23 ml of blood of virgin male chicken handy, face North (do account for magnetic field) at exactly 12:34, wipe 7 times, wait 50 minutes between, upgrade to 18.1, immediately downgrade to 17c ... etc" recipes are a bit more than I could handle .
Seriously, I was so used to how solid stock HC was, I was totally shocked by ICS ... should've never allowed auto-update ... wait, ASUS gave us non-rooted users no choice in the matter
rashid11 said:
None of us doubt the evolutionary nature of ICS and we all will gladly upgrade to ICS when the issues are fixed. For now, some require tablets that are good enough to be relied on.
The "wait a for a full moon, have 23 ml of blood of virgin male chicken handy, face North (do account for magnetic field) at exactly 12:34, wipe 7 times, wait 50 minutes between, upgrade to 18.1, immediately downgrade to 17c ... etc" recipes are a bit more than I could handle .
Seriously, I was so used to how solid stock HC was, I was totally shocked by ICS ... should've never allowed auto-update ... wait, ASUS gave us non-rooted users no choice in the matter
Click to expand...
Click to collapse
I haven't seen anyone post anything like that to get ICS to work. It seems like it either does or doesn't, I would call it user error but I would probably be beheaded by all the people who have these issues. All I know is that along with other people I am running ICS and can go days, if not longer, without a single SOD or RR.
If you need to go back to HC, go right ahead, but try not to be too harsh as from what I can tell, 90 % of the community isn't having major issues.
rashid11 said:
None of us doubt the evolutionary nature of ICS and we all will gladly upgrade to ICS when the issues are fixed. For now, some require tablets that are good enough to be relied on.
The "wait a for a full moon, have 23 ml of blood of virgin male chicken handy, face North (do account for magnetic field) at exactly 12:34, wipe 7 times, wait 50 minutes between, upgrade to 18.1, immediately downgrade to 17c ... etc" recipes are a bit more than I could handle .
Seriously, I was so used to how solid stock HC was, I was totally shocked by ICS ... should've never allowed auto-update ... wait, ASUS gave us non-rooted users no choice in the matter
Click to expand...
Click to collapse
I have no idea what you're talking about, dude...
ICS works fine. I didn't do any weird dance or ritual involving blood from a chicken. I simply installed Eos ICS and haven't had a single issue. Its better, faster, more stable than Honeycomb in every measurable metric. If you are having a different experience, I don't know what to tell you..
No sleep issues, no random reboots, all features work correctly. I don't know how else to put it other than saying there are ZERO problems with my tablet running ICS.
I agree, Ics is amazing IMO. I had freezing and reboot problems with HC, but I havn't really been on stock ICS, only AOKP/Megatron/ARHD with Testymehics/test kernels. No sod problems here.
Stock ICS
Sorry guys, no problems here at all and I am running stock ICS. No issues what so ever.
a.mcdear said:
I don't know what you guys are doing to have such bad luck on ICS, but my experience with Team Eos ICS has been absolutely pleasant.
Click to expand...
Click to collapse
I've no doubt whatsoever that you have a great experience with ICS on your tablet. TBH, other than the SOD's, I liked ICS better than HC: Faster, snappier, more intuitive UI, etc. This isn't about the the OS or UI in general, it's a problem with the kernel and it is very inconsistent. While maybe the majority of people with a TF don't have a problem there is still a large group who do have problems. And these are also all over the place:
- SOD
- Random Reboot
- SOD + Random Reboot
- Screen glitching (or something like that)
- other weird stuff, less critical.
Nobody is doing *anything* to have such bad luck. It's just, well, bad luck. I love ICS and have it on my SGS, which ironically, wasn't even supposed to have been running ICS in the first place. And it's rock solid, fast, dependable and I love it tons more than the iPhone 4S they gave me at the office
miketoasty said:
Where did you get this from?
Click to expand...
Click to collapse
Like i said from gary :
http://forum.xda-developers.com/showthread.php?t=1556914
Does anyone have access to NVFlash version of Revolver 3.11? (all links I've found are dead)
Apparently SOD and RR still exist in ICS .24
I downgraded using CWM .zip of 3.11 , that one was still available 2 days ago.
kermitdefroghere said:
Apparently SOD and RR still exist in ICS .24
Click to expand...
Click to collapse
How do you sure about this? Have you updated to ICS.24???
My stock ICS.21 is doing great with a little mod.. flashed guever's custom kernel and those SOD or RR are gone.. Everything else is stock with all those ICS greatness.
farsight73 said:
How do you sure about this? Have you updated to ICS.24???
My stock ICS.21 is doing great with a little mod.. flashed guever's custom kernel and those SOD or RR are gone.. Everything else is stock with all those ICS greatness.
Click to expand...
Click to collapse
Check jtroskys posts in the official ics thread (stickied).
He was a beta tester for. 21 and .24.
Though stable initially .24 has receded back to the regular sods and Reboots many of us have been struggling with.
I've officially stopped waiting and went to Revolver.
Edit: Just to be clear... that's Revolver 3.11.1 (Honeycomb) with Blades kernel 3.
Very impressed.
Funny how an overclocked 3.2.1 build can be more stable than ICS (at least so far).
VERY impressed with Revolvers 3.11.1
Enjoying my Transformer again.
Sent from my XT910 using Tapatalk 2

Unlocked Bootloader v8 / ICS - SoDs

I had zero issues with SoD running HC roms and HC bootloader. I have serious issues with ICS roms and the unlocked bootloaders. Here is what i have tried:
First tried v3 unlocked bootloader with Thors recovery and CM9 alpha rom. I had many issues with SoDs everytime the screen went off it seems like it SoD. That was the original issue. I recently just tried 3 different recoveries including twrp/ezterry/thors and used all 3 to do full wipes. I installed ezterrys ICS rom. I am getting less SoD..maybe 1 per day but they still persist. Does anyone have any ideas what im doing wrong? Am i the only one with these issues? Its not an app causing this either as I have run with both roms on the base w/o installing any apps and the SoD still persists. Anyone have any experience with this and can enlighten me?
droidroidz said:
I had zero issues with SoD running HC roms and HC bootloader. I have serious issues with ICS roms and the unlocked bootloaders. Here is what i have tried:
First tried v3 unlocked bootloader with Thors recovery and CM9 alpha rom. I had many issues with SoDs everytime the screen went off it seems like it SoD. That was the original issue. I recently just tried 3 different recoveries including twrp/ezterry/thors and used all 3 to do full wipes. I installed ezterrys ICS rom. I am getting less SoD..maybe 1 per day but they still persist. Does anyone have any ideas what im doing wrong? Am i the only one with these issues? Its not an app causing this either as I have run with both roms on the base w/o installing any apps and the SoD still persists. Anyone have any experience with this and can enlighten me?
Click to expand...
Click to collapse
Had sod on any rom (and stock) with changed bootloader (and other problems). Went back to ota stock without root. No problems
I have SoD since going from thors rom back to taboonay and then to V8 bootloader, still trying to solve the issue but no luck. I can't even connect to pc to root it again as I've lost that too
Any of you running a 501?
If so, it's an issue with the kernel.
MD
a500 here
Moscow Desire said:
Any of you running a 501?
If so, it's an issue with the kernel.
MD
Click to expand...
Click to collapse
Using A500
I see so many others with success which is why its killing me that this is not more common issue. There must be something we are doing slightly wrong or forgot to do causing this.
Ok, here is the real deal.
1. ICS Bootloader. Mandatory. Check it when you boot, it should say in the left corner.
2. Recovery version has no effect on SOD. However, you should have the correct one for ICS. Currently I use 1.7.3.
3. The kernel. Now, most of the ICS Roms in the forum for the 500 have a "tweaked kernel". These are the ones you want to use. MAKE SURE the rom you are using is for the patched ICS Bootloader. This includes EZTerry's and Civatos. You have to pay attention with Civ's as he may still have some designed for HC bootloader. YOU DO NOT WANT THESE. I believe Smaury's and Vache's are ok also, but check first.
4. This is probably where the problem is. Wipes and Formats. Sometimes, leftover code from a previous kernel or modules could still possibly be in the tab. This can cause strange issues.
Wipe
Data/factory reset
Cache
Dalvik Cache
(depending on recovery version)
Format System
Format Flexrom
Do this 2 or 3 times, then install the rom.
I use CWM 1.7.3 recovery (too lazy now to change but will in the future)
Also, if you have any doubt which bootloader you currently have, download AcerRecoveryInstaller and it should tell you. After OTA in the Dev forum will also tell you. You don't have to do anything with the app, just start it to get information.
This should get you going.
MD
I have two A500's, both with V8 bootloader and the latest flexreaper rom. One doesn't SOD, the other has constant SOD's. I'm beginning to think it's the hardware. Mine were purchased about 6 months apart, maybe different hardware revisions?
riot1031 said:
I have two A500's, both with V8 bootloader and the latest flexreaper rom. One doesn't SOD, the other has constant SOD's. I'm beginning to think it's the hardware. Mine were purchased about 6 months apart, maybe different hardware revisions?
Click to expand...
Click to collapse
This is some good info! I am pulling my hair our here! As far as what MD suggested I have done all those steps...multiple times with 3 different recoveries wiping everything i can. Do you happen to remember when you purchased them? I bought mine from newegg 8.16.2011
riot1031 said:
I have two A500's, both with V8 bootloader and the latest flexreaper rom. One doesn't SOD, the other has constant SOD's. I'm beginning to think it's the hardware. Mine were purchased about 6 months apart, maybe different hardware revisions?
Click to expand...
Click to collapse
You know, you just added some insight into a theory I've been tossing in my head. Although I thought this was only a51x and a70x based. I didn't know it might be effecting the 50x as well.
Let me run this at you. With the 51x and 70x, the bootloaders seem to be matched to the specific version of ICS installed from factory. (COMGen, version number, etc). We know this, as the bootloaders on several tabs have different naming conventions. It's why certain root methods will not work on some tabs. Currently we have 3 methods, but 1 requires CWM (and our current version will brick the tab if you use the restore option..../data is what bricks).
It's possible, that with ICS, certain kernels are required to function properly on the 500 also. We all know with ICS, the kernel communicated a lot with the bootloader. This "may" be associated with some obscure part of the hardware as well. This I don't know. But with the newer tabs, it definately seems to be hardware software related. Some Roms just WILL NOT run on some tabs.
Now for you guys, here is what I might try. Different kernels. Try running a stock kernel for that specific build number. Or if you haven't tried it yet, try running EZ_Terry's OC kernel built form source. See if you still get SOD.
Just something to try.
MD
Moscow Desire said:
You know, you just added some insight into a theory I've been tossing in my head. Although I thought this was only a51x and a70x based. I didn't know it might be effecting the 50x as well.
Let me run this at you. With the 51x and 70x, the bootloaders seem to be matched to the specific version of ICS installed from factory. (COMGen, version number, etc). We know this, as the bootloaders on several tabs have different naming conventions. It's why certain root methods will not work on some tabs. Currently we have 3 methods, but 1 requires CWM (and our current version will brick the tab if you use the restore option..../data is what bricks).
It's possible, that with ICS, certain kernels are required to function properly on the 500 also. We all know with ICS, the kernel communicated a lot with the bootloader. This "may" be associated with some obscure part of the hardware as well. This I don't know. But with the newer tabs, it definately seems to be hardware software related. Some Roms just WILL NOT run on some tabs.
Now for you guys, here is what I might try. Different kernels. Try running a stock kernel for that specific build number. Or if you haven't tried it yet, try running EZ_Terry's OC kernel built form source. See if you still get SOD.
Just something to try.
MD
Click to expand...
Click to collapse
This is an interesting theory and makes sense. In my case with CM9 and Ezterry's rom I have tried the stock kernel for each and ezterry's OC kernel on both...and still SoDs although ezterrys rom/kernel seems to be far less frequest SoDs. We don't have much options for kernels around here.
Progress?
Has anyone made any progress with figuring this out?
My tablet was running fine on a stock, rooted ICS. Then I installed custom recovery, different kernel, and bootloader when I tried JellyBean (ROM | WIP | CM10 JellyBean 4.1.2 Unofficial for acer a500 [Build 3]) from the Developers forum on here. I started getting SoDs and some of my games weren't running, so I went back to the ICS rom, but the SoDs are still happening. At that point, I was pretty sure it was related to the kernel or the bootloader.
On the "ROM | WIP | CM10 JellyBean 4.1.2 Unofficial for acer a500 [Build 3]" thread in the developers section they are questioning if the SoD is related to CyanogenMod (which I don't believe it is). I wanted to post there about what this thread is hypothesizing, but am unable to post to that thread (too new to XDA).
Update
I went ahead and went back to full stock ICS (bootloader, kernel, etc). Then rooted it again.
The disappearing icon issues have gone away.
Now I'm not sure if I should just stick with it like that or venture out into Jelly Bean land again...
Waleslie said:
I went ahead and went back to full stock ICS (bootloader, kernel, etc). Then rooted it again.
The disappearing icon issues have gone away.
Now I'm not sure if I should just stick with it like that or venture out into Jelly Bean land again...
Click to expand...
Click to collapse
Venturing out to JB land is a choice.
Although CM does a pretty good job of doing things, I always have to remember, they lean toward mainstream devices.
We 50x owners, have some pretty good guys. But, we only have a few, compared to the mainstream devices, which have a whole lot more. Welcome to the tablet world.
If it were a samsung or Asus, would probably have a ton more.
But, my ICS on my 501 runs pretty darn good. And I'm thankful to each and every dev and cook who strive to make it better. It's a pity there are not more for our device.
SOD will always plague us it seems. A lot seems to depend on the revision hardware. Seems the earlier versions don't get it much.
MD
droidroidz said:
This is some good info! I am pulling my hair our here! As far as what MD suggested I have done all those steps...multiple times with 3 different recoveries wiping everything i can. Do you happen to remember when you purchased them? I bought mine from newegg 8.16.2011
Click to expand...
Click to collapse
same problem as you and 8/10/2011 is when I got mine. I have had some version of hc to work with no sod, but tried everthing and every combination out there (with the mod bootloader) and still have sod, so just went back to stock.

[Q] Should I update?

Hello,
Got my N7 yesterday, I unlocked it and its rooted.
now its running 4.1.1 I want to update to 4.1.2 im still on the stock rom(rooted+touch recovery).
I heard that there is some issue if you update through the stoke recovery, so I have a custom recovery. I flashed a rom named smooth 4.0 through both the touch recovery(TWP) and CMW and non of them work I just see the boot up thats all.
so should I update or flash a different rom ?
im sorry if this question has been asked before.
thanks
anyone?
Why Not?
It's up to you if you want to update. 4.1.2 has a few new things, including screen rotation (finally), and a camera app If you can't choose, why don't you do both?
Saturny said:
It's up to you if you want to update. 4.1.2 has a few new things, including screen rotation (finally), and a camera app If you can't choose, why don't you do both?
Click to expand...
Click to collapse
try both to see for yourself. i always get the latest and the greatest because of bug fixes stability improvements and things like that.
Maybe this is a placebo effect, but since I've updated I have yet to have some of the intermittent touchscreen issues that I was experiencing on 4.1.1... On that premise alone, and the fact I've had zero new issues crop up on 4.1.2, I'd say go for it.
Sent from my Nexus 7 using xda app-developers app
..
I really would like to update and get rid of the annoying pop up message but isnt if im rooted and I have custom recovery will it update?, and if it did will I see app crashing?

Categories

Resources