Would anyone know of a reason why Plants vs Zombies would not work properly on a rooted thunderbolt?
I played the game last night on a stock Thunderbolt. After I rooted it this morning it continues to go into a loading screen as if i hit the home screen and jumped back into the game.
I'm rooted and it works for me although the game will randomly shut down while I'm in the middle of playing
Sent from my ADR6400L using Tapatalk
I have no problems with it (so far at least).
dionysos803 said:
Would anyone know of a reason why Plants vs Zombies would not work properly on a rooted thunderbolt?
I played the game last night on a stock Thunderbolt. After I rooted it this morning it continues to go into a loading screen as if i hit the home screen and jumped back into the game.
Click to expand...
Click to collapse
Have you tried clearing the data? (yes you will lose your progress I believe, but it might work.) If not maybe reinstall it and see if that may fix the problem. Haven't had any problems with it over here so not sure. What rom/kernel/OC speed (if any) are you running?
das bamf 1.6 (just received a replacement TB). So after i rooted it i jumped back to restore point via clockwork. The whole thing appeared to have no problems, but i know of a few minor things wrong with it that were not like this before the replacement. I've tried over clocking it to see if that could fix the problem but still not success. Also I've tried the das bamf 1.7, i've cleared all the cache and so on. Ive uninstalled and reinstalled the game a few times
Damn, sorry, not sure what is wrong. I'm running BAMF 1.7 Remix, and it's working fine for me. Maybe try redownloading it, I highly doubt it was corrupted when downloading, but then again, stranger things have happened
I'm having no issues on Slayher's latest release of CM7.
me too.
I'm having major problems playing plants vs zombies also.
I start the game up and then I can't set the phone down... I try... but my hands instantly reach down and pick the phone back up.
I have a very similar problem with the game hex defense.
I'm running DAS BAMF 1.6 as is my girl friend and she is experiencing the exact same problems.
I can't get the app to run at all on my TB.
Running Liquid Thundersense. (thinking of switching ROMS.. still looking for that magic combo that won't randomly reboot 4 times a day while i'm at work)
Well I managed to get it going...I guess that since I took one of my backed up roms from ky original TB and restored it on a new one it some how caused a conflict with select apps. I went back, flashed an all new das bamf Rom from scratch and every thing is now working on my phone.
PS what a pain in the ass it was since I didn't have a titanium back up of all my stuff. 4 hours later I finally had everything re-downloaded. The birch is I still haven't had ti3 to re-set up my home screens.
Sent from my ADR6400L using XDA Premium App
Related
Sorry all if this has been touched on but I'm at work right now and the search on the app isn't the same as the full sites. Anyway, I first ran into this issue on listybs nomsensikal 4.6 and now I'm kaosfroyo v32 and when I open gps and type on the address, it begins to load but freezes on the screen where it loads the route but isn't actually navigating..It just keeps searching for gps...after about thirty minutes if finally starts telling me how to get where I am going...i think my issue may stem from TransparentKaos as I used this on both roms and hadn't had issues before flashing it, if anyone has got two cents to throw my way it would be appreciated.
edit- it's definitely not transkaos, which is a relief cause i love the theme but i'm still not sure why this is happening to me, i've done a full wipe and reinstalled the rom but still not picking up the gps signal consistently, randomly it will work right away but mostly waiting for at least 20 minutes before it finds it...not sure whats up
Sent from an Eris running in beast mode aka KaosFroYo v32 using the XDA App
Hey guys, bit of a weekend brain teaser for you guys...
My rotation function just stopped working completely a day or two ago. I dont know if its worth mentioning but I actually never use auto-rotation (I just personally dont like/need it much). However, certain programs; Youtube, games, have usually served their proper rotation function when in use.
I've been running SC 2.9.2 with jt's ec10 kernel for quite some time now without any flaws. No changes were made to the phone before the issue.
Kinda sucks not being able to watch Youtube in full screen...
Any ideas?
Interesting. Mine stopped working a couple of days ago as well, also using SC 2.9.2. I'm using jt's 4/7 kernel. I've tried reinstalling both the rom and kernel with no success. In addition to the rotation my compass also does not work, so both the accelerometer and magnetometer have failed. It happened while using Google Nav in walking mode, where the phone froze and became unresponsive. After about 10 minutes of no response I pulled the battery and afterward noticed the problem. I'm planning to revert to stock to see if it helps tonight.
whereas im relieved to know that someone else is on the same boat, i really hope that it doesnt come.down to doing a full back to stock wipe :/
it would be nice to know what caused the malfunction...
Sent from my SCH-I500 using XDA App
Mine's working again after going back to EB01 briefly before going to EC01. I was planning to try out EC01 anyway and the brief revert to EB01 is part of the procedure.
Today I finally loaded all my PSX and N64 ROMs from my N1 to my GTab, and then started to play.
I first noticed the problem with FPSE when I went into settings. There would be fairly loud "pops" from the tablet, and it seemed to happen at irregular intervals. It continues to happen while I'm in settings, although when I go back to playing it's fine again. The same problem with N64oid: only in settings.
I'm fairly sure it's the speakers (what else could make such a noise?!) but what puzzles me is that even with all volumes muted it doesn't stop.
It wouldn't be such a problem of it weren't so loud, as it almost sounds like the speakers will explode.
Anyone else running VeganTab GE with the same problem? Would you be able to try replicate it if you have either FPSE or N64oid?
I noticed the same thing the other day when I was in connectbot trying to fix my build.prop
I had the same issue running 5.1 and now I am stuck at the viewsonic boot screen after trying to install vegan ge rc-1.
It also seemed to pop with the original viewsonic ui and I had an elocity before this and it did the same thing. I think it is a android issue but I am a noob and know nothing!!
I couldn't get fpse to work on my last Rom will try later today and see if I can replicate.
Sent from my Desire HD using XDA Premium App
Oooo, sounds like your flux capacitor blew.
Hi.
I am about to unroot and go back to otb stock. I am wondering if anyone knows for sure when the random reboots that I, and several others encounter, first started because I need to know whether to do the OTA after I go back to stock.
From my memory....... :
Wasn't there 2 OTA's?
And the random reboots started after installing the 2nd one?
So should I just install the first one.......orrrr......does it automatically only give one OTA direct to the 2nd one released?
Or should I not install any OTA's at all and patiently wait for Gingerbread........
Thanks!
We have MR1, MR2, and MR2.5 but I think only MR1 was an official OTA (dont quote me on it tho since I have been rooted since I got the phone and have never received an OTA). I think the reboot issue has been a problem for a lot of people for the entire time and isnt a new thing. IIRC MR1 caused quite a few reboot issues but not for everyone. I personally ran w/o any reboots until I got to 2.5 and even then I have only ever had 1. Its just what works best for you.
You will be waiting patiently for quite a while for official GB from what I have heard on the boards but you can always try out some of the GB ROMs that we have already.
Beastclaw said:
We have MR1, MR2, and MR2.5 but I think only MR1 was an official OTA (dont quote me on it tho since I have been rooted since I got the phone and have never received an OTA). I think the reboot issue has been a problem for a lot of people for the entire time and isnt a new thing. IIRC MR1 caused quite a few reboot issues but not for everyone. I personally ran w/o any reboots until I got to 2.5 and even then I have only ever had 1. Its just what works best for you.
You will be waiting patiently for quite a while for official GB from what I have heard on the boards but you can always try out some of the GB ROMs that we have already.
Click to expand...
Click to collapse
You are correct Beast there has only been one official OTA. My wife is not rooted but I am
Well I went back to stock because I was gonna try to go to Verizon today and swap it out.....
I find it funny this exactly what I was going to ask today myself. I'm also running bamf remix 1.8, have tried all the radios and even installed bamf 2.0 for GB with the Mr 2.0/2.5 radios. Still got reboots. Now I want to go back to stock and unroot so I can go back to the store and swap it
Just wonder if its worth it, maybe if they let me swap SD cards
I just un-rooted my phone about two days ago. After, I did the OTA update. I hadn't seen any problems until today. I live in a 4G area and work in a (up until Monday) 3G area. Since Monday they have been testing out a 4G tower. I have had 4G until this morning, I just figured that they were still testing it out and had switched it off. Well, about an hour ago I got my first Reboot. When the phone came back up I noticed that the 4G had just came back on. I'm pretty sure that's what triggered my reboot. So in short, as long as they keep the 4G going I don't have any issues.
Just curious is the update worth doing? And if i do it do i go ahead and install the GB bamf rom and radio? or just go back to my current 1.8 remix?
im curious what you guys have your phones overclocked at? I am rooted on the RC3 bamf 3.0 and the only time I have seen reboots is when i had my phone overclocked to high. now that im at 1.42 on the bamf cpu (I disabled my setCPU) and it has been solid.
I am a flashaholic. I flash any new rom on my fassy whenever a new one is released. I recently did TSM Res 2.0. I always flash by the book. I made many mistakes as a rookie and I try not to repeat oopsies. All was well and I found the rom to be stable and well put together. The next day I rebooted for an unrelated issue. After that, as the day progressed my data connection fizzled. By the next day I had lost it completely. I flashed back to stock and nothing. Then Superclean, CM7 and still nothing. Called Verizon and got a replacement. My last day with the phone, day 4, my ability to call also went. I called Verizon. I did an activation and had it authenticated. Rebooted phone and ta-da. All was well.
So WTF? Any ideas folks?
I kept the replacement anyways.
Sent from my SCH-I500 using XDA App