I just flashed my A500 with the new ICS Taboonay 3.0.1 build. I have Flashed the main ROM and have also flashed the WiFi fix along with the Acer lock screen.
For some reason I get SOD every time my tablet goes to sleep. I have wiped the system, data, cache, dalvik, and flexrom multiple times. I have tried it with just the Taboonay ROM, Taboonay ROM with WiFi fix, and with just the acer lock screen.
I've read that someone was able to uninstall their google maps and street view, I tried that and still getting a SOD when it goes to sleep. I have also seen references to a SOD-Fix.zip file, however I'm unable to find it on the forums, or in google searches...
Anyone have an idea what I might be doing wrong?
What bootloader did you flash, if any?
I believe I'm using CWM... I have a feeling that is not what you are looking for though. I was running the Taboonay 2.3 (I think that was the version) prior to installing this ROM.
I've always had lots of luck with Taboonay ROMs in regards to stability and performance.
Weird. Try freezing your apps one by one using TB. The way I discovered the map thing on mine was to make a full nand backup, then restore to defaults, adding only one program or updated apk at a time. It was the updates that did it. Maps was fine as it comes from Acer, when I applied the market Update was when it started causing SOD.
Kabish said:
I just flashed my A500 with the new ICS Taboonay 3.0.1 build. I have Flashed the main ROM and have also flashed the WiFi fix along with the Acer lock screen.
For some reason I get SOD every time my tablet goes to sleep. I have wiped the system, data, cache, dalvik, and flexrom multiple times. I have tried it with just the Taboonay ROM, Taboonay ROM with WiFi fix, and with just the acer lock screen.
I've read that someone was able to uninstall their google maps and street view, I tried that and still getting a SOD when it goes to sleep. I have also seen references to a SOD-Fix.zip file, however I'm unable to find it on the forums, or in google searches...
Anyone have an idea what I might be doing wrong?
Click to expand...
Click to collapse
yu
So you wipe data/cache/dalvik/ factory reset-> flash 3.0->3.1->wifi-fix->maybe acer ring
And here link to sod fix http://http://forum.xda-developers.com/showpost.php?p=23070364&postcount=2265
greetz
have you tried turning off crt animation when screen off??
Related
Hi all, i have been having a very bazaar problem lately...When my phone boots up i get a pop-up message indicating that the gapps process shutdown unexpectedly...and sometimes i may even get a acore crash too. Applications from the market do not download...when i select my download i will end up getting a gapps crash and then the supposed download just sits there saying "starting...". Google talk doesn't even open! It will just say that the process quit unexpectedly. Even after a fresh install with factory data reset all these problems will continue. The initial boot up screen/tutorial will even show a gapps crash. I have tried with 3 different versions of cyanogenmod all with the exact same problem..Each version i've tried with a2sd enabled and disabled, formatting the partition each time before a new install to ensure no data carry-over issues. I don't know what to do. To me it seems like it make be something on googles side...but i can't for the life of me figure out whats causing these wild problems. Help would be very much appreciated.
ANDROID Market problems
I've recently had the same problem with the market getting stuck on "starting download". I thought it was something I modified as I'm putting together a STARGATE theme of my own based on kron2's work with this site and the theme for "Open Home" for DWANG's newest ROM. What worked for me was going back 1 restore point at a time till I found one that didn't have the problem (NANDROID backup). I also had luck with flashing DWANG's original unmodified ROM 1.17.1. I had the same problem when I flashed 1.16 ..weird. Up till 2 days ago I didn't have any problems changing anything in it. Others have said that they tried opening G-Talk at the same time and some how going between the 2 the problem would right itself. If you find out anything definite about what the exact problem is let me know as I'm going to keep looking for the answer myself.
six6star said:
I've recently had the same problem with the market getting stuck on "starting download". I thought it was something I modified as I'm putting together a STARGATE theme of my own based on kron2's work with this site and the theme for "Open Home" for DWANG's newest ROM. What worked for me was going back 1 restore point at a time till I found one that didn't have the problem (NANDROID backup). I also had luck with flashing DWANG's original unmodified ROM 1.17.1. I had the same problem when I flashed 1.16 ..weird. Up till 2 days ago I didn't have any problems changing anything in it. Others have said that they tried opening G-Talk at the same time and some how going between the 2 the problem would right itself. If you find out anything definite about what the exact problem is let me know as I'm going to keep looking for the answer myself.
Click to expand...
Click to collapse
I have searched and it seems many people have the Market/Gtalk problem.
I have the same problem (with an Eclair 2.1 Cyanogenmod rom) and I've not been able to find a solution. Wiping the cache makes nothing.
Anyone knows how to solve it?
Huh. I had a problem with the market at first with cyan 5.0.8 . I went in the terminal and ran fix_permissions after su and haven't had any problems since. Might try that
Sent from my HTC Magic using XDA App
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?
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.
Hey guys, I've had my transformer for just under a year and love it to death, but for the last couple of days it has been giving me hell! I was running ARHD 3.4.1 with Guevor's ICS kernel (can't remember version, either 19.4, 20 or 21). Anyway, all was well until I changed to ARHD 3.5.1 and switched to raymanfx's harmony kernel to try it out. I couldn't get my videos to play on mxplayer, FC's on apps, random freezes and tablet kept randomly rebooting. So I reflashed ARHD 3.5.1 again, same, reflashed guevor kernel, same, updated CWM to Rogue XM Touch Recovery v1.5.0-R1, same. Finally used this method: http://www.theandroidsoul.com/update-and-restore-eee-pad-transformer-to-stock-ice-cream-sandwich/ to flash back to stock, no root, no nothing annnnnd... same! Same issues no matter what I try. So my question is, with a few weeks of ASUS global warranty left (bought it in HK so I can't take it back to 'shop') can/should I send it back now that it's flashed back to stock without them finding out I rooted it? Or is there something I'm missing that you guys can think of. Please let me know asap in case I do need to send it back. Thanks in advance. Oh and let me know if you need more info
Maybe a stupid question...
Did you do a factory reset in between flashing the different roms and kernels? Full factory reset, wipe cache and dalvik?
Not a stupid question at all, but yes, I tried all three
Sent from my R800i using Tapatalk 2
I can't think of anything else causing that behaviour. Restoring apps, data and system data with Titanium has been a source of trouble for me in he past. Restoring setCPU with profiles that don't work well with the new kernel for example. But I guess that's not the case here. At least stock ROM should be working.
Sorry, maybe someone else has another idea.
Hey guys,
I have a Galaxy S4 (i9500). I installed Omega ROM v22 on it and everything went smoothly, Wifi & BT working perfectly.
After a few hours of using the device (nothing special at all, texts and stuff like that) - I noticed my wifi isn't working and by not working I mean that I click the wi-fi button and it changes from gray to the mid-state between gray to green for around 20 seconds before it goes back to green ago.
If I open the menu to see my networks it just says "Enabling" without any networks there.
I had to drive somewhere so I went to my car and tried to enable Bluetooth, and same thing happens there - Bluetooth will not turn on and will stay stuck on mid-state between gray and green for a while and go back to green.
I flashed omega rom v22 again and the problem was gone, or so I thought. I went back to the car for another drive and realized the bluetooth issue is back - and when I got home I realized the wifi issue is back as well.
I figured I need to reset everything so I tried the following:
Full wipe (including dalvik and even including "internal SD card") and then flashing stock rom (from the official website, stock rom of my country).
The issue was back after a few hours. I do not have BT or Wifi access. Yesterday Wifi suddenly started working for a few hours but then it stopped working again.
I really need help! I have no idea what to do with this issue!
Well rule number one when you have problems after flashing without wipe.
1. perform a full wipe and see if the problem persists.
Lennyz1988 said:
Well rule number one when you have problems after flashing without wipe.
1. perform a full wipe and see if the problem persists.
Click to expand...
Click to collapse
Tried that, no luck.
What else would you try?
In some places when people had problems with Wi-Fi they said to flash a different kernel but I don't see why I would have this specific issue with Omega Rom and why the default kernel with it wont work well?
Maybe this could be a root issue? My root works fine but I have this weird gut feeling like this is some permissions thing that's going on.
I'm trying to think why it would work right after the wipe but then stop working shortly after.
Another symptom: It randomly started working for a few minutes and then stopped again (around three hours ago).
Any idea what's going on?
Well, if you fully wiped and didn't restore any apps and settings then it can be two other things.
Or it's a bug in the rom or a hardware failure in your phone.
I would suggest trying a different rom first. Do not restore anything, not even your google account.
wi-fi fix?
Do you actually have an i9505? or is it a canadian or att version? if its the latter sometimes the devs offer some wifi-fixes, also try a different kernel. otherwise it could be that your radio/modem are not compatible with the version of the ROM you are flashing.
Tried arrow ROM and this issue doesn't seem to happen in this rom. Hope it stays like that...
morhsn said:
Tried arrow ROM and this issue doesn't seem to happen in this rom. Hope it stays like that...
Click to expand...
Click to collapse
Sadly, it did happen with this rom, after just a few hours.
I'm now using stock rom and still suffering from the issue.
Does anyone have ANY idea what I can do to fix this?
Thanks in advance!