I have TnT Lite 3.14 and the Clem 10.9.8 kernel. Since the recent Rockplayer update as well, I can not play vids in accelerated mode. They worked fine before, but either the Rockplayer, TnT or the kernel updates are the issue (or combination).
When I try to play vids in accelerated mode, the app crashes and then the device will freeze up then reboot suddenly to the sparkly splash screen. For that matter, playing higher res WMV files freaks the stock video player out and the device will do the same thing.... I may have just eliminated Rockplayer and the root cause is either TnT Lite 3.14 or the Clem 10.9.8 kernel.
Anybody else having such issues?
rushless said:
I have TnT Lite 3.14 and the Clem 10.9.8 kernel. Since the recent Rockplayer update as well, I can not play vids in accelerated mode. They worked fine before, but either the Rockplayer, TnT or the kernel updates are the issue (or combination).
When I try to play vids in accelerated mode, the app crashes and then the device will freeze up then reboot suddenly to the sparkly splash screen. For that matter, playing higher res WMV files freaks the stock video player out and the device will do the same thing.... I may have just eliminated Rockplayer and the root cause is either TnT Lite 3.14 or the Clem 10.9.8 kernel.
Anybody else having such issues?
Click to expand...
Click to collapse
I am using vegaN with the Clemson 10.9.3 kernel and have not seen it. I know it's not the same but what makes me wonder is you saying you are seeing the sparkle screen. That is from the old Zpad and if it were me I would wonder how much more leftover stuff was floating around in your tablet.. The leftovers may be causing your issues.
Sprdtyf350 said:
I am using vegaN with the Clemson 10.9.3 kernel and have not seen it. I know it's not the same but what makes me wonder is you saying you are seeing the sparkle screen. That is from the old Zpad and if it were me I would wonder how much more leftover stuff was floating around in your tablet.. The leftovers may be causing your issues.
Click to expand...
Click to collapse
The X sparkle screen is not part of TnT?
This is my second G, so no zPad roms installed. Always been stock and then TnT Lite after that. No others tried. The box was sealed so should not be a refurb... Came from Staples, so probably not. Always wipe and clear cache.
rushless said:
The X sparkle screen is not part of TnT?
This is my second G, so no zPad roms installed. Always been stock and then TnT Lite after that. No others tried. The box was sealed so should not be a refurb... Came from Staples, so probably not. Always wipe and clear cache.
Click to expand...
Click to collapse
Thats weird. The sparkle screen that looks like sideways fireworks? Lots of colors? If so, that is from Zpad. Don't know how it would have got there either. Stores can be pretty sneaky though with returns.
Sprdtyf350 said:
Thats weird. The sparkle screen that looks like sideways fireworks? Lots of colors? If so, that is from Zpad. Don't know how it would have got there either. Stores can be pretty sneaky though with returns.
Click to expand...
Click to collapse
Yep, that is the one.
rushless said:
Yep, that is the one.
Click to expand...
Click to collapse
Then you don't have TnT. TnT boots with the big G and some other static thing. vegaN boots with Gtabdevs, and then Android. Only thing I have seen the sparkle thing on is the very first Zpad roms.
If you are up to it I would do the Nvflash restore to get all the way back to stock. Make sure to wipe data, factory restore, and wipe dalvik before doing Nvflash. I have found if I don't I end up with lots of leftover stuff even after Nvflash.
Probably not what you wanted to hear but I remember you saying that about the sparkles for a while now.
That is the boot animation that Roebeet puts in TNT Lite. Been there since version 1.
rayden25 said:
That is the boot animation that Roebeet puts in TNT Lite. Been there since version 1.
Click to expand...
Click to collapse
Nope. Roebeet is not changing the boot animation. It is the Android screen instead of the stock Viewsonic. There is a thread around here somewhere about this same subject. People not clearing data, factory reset, etc. Sparkle screen should not be there.
Sprdtyf350 said:
Nope. Roebeet is not changing the boot animation. It is the Android screen instead of the stock Viewsonic. There is a thread around here somewhere about this same subject. People not clearing data, factory reset, etc. Sparkle screen should not be there.
Click to expand...
Click to collapse
I have run several versions of tnt lite and that boot animation has been in every one of them. it's the animation from the nexus one. It's not exclusive to zpad.
The Sparkle screen does not belong. If you are seeing the sparkle screen then you have stuff on your tablet that does not belong there. If you bought your tablet and it has the sparkle screen then it is not running what everyone else is running.
I run vegaN and have for a while. I remembered no sparkle screen in TnT anything. I just did a backup and loaded TnT 3.1, and then added TnT 3.1.4... Guess what? No sparkle screen. It starts up with the ugly green G Tablet picture with the white background, and then switches to a screen that says Android. Just like I have always seen TnT everything do.. Like I said, this was an issue a while back. It is not supposed to be a sparkle screen and if you see it you have residual crap from somewhere else.
I am not a Psychic so I have no idea how you got it.. Or where you got it. I just know you shouldn't...
I have run every version of tnt lite since 2.2 and they all have had the nexus one boot screen.when I boot my tablet I see the viewsonic birds then the gtablet logo, and finally the nexus one fireworks X.
ETA: roebeet's change log found on the development board states that "tnt boot screen replaced with standard boot screen"
thebrain73 said:
I have run every version of tnt lite since 2.2 and they all have had the nexus one boot screen.when I boot my tablet I see the viewsonic birds then the gtablet logo, and finally the nexus one fireworks X.
Click to expand...
Click to collapse
That's real good.. You are now another member of the you have a screwed up tablet club...
That bootscreen is on the Nexus, Zpad, I'm sure lots of other places. Point I am making is it does not belong in TnTLite.. Or vegaN.
If you like it great. If you believe it is right, great.. If your tablet has other errors from remnant code.. Great..
Sprdtyf350 said:
That's real good.. You are now another member of the you have a screwed up tablet club...
That bootscreen is on the Nexus, Zpad, I'm sure lots of other places. Point I am making is it does not belong in TnTLite.. Or vegaN.
If you like it great. If you believe it is right, great.. If your tablet has other errors from remnant code.. Great..
Click to expand...
Click to collapse
Ok maybe you could tone down your ego a bit and use your vastly superior knowledge to explain how my tablet got a boot screen that is supposedly not in any of the code I or viewsonic loaded on to it.
All I know at this point is that I bought the tablet on december 28 2010. I charged the device, booted it up for the first time and let it do an ota update.i then installed clock work .8, then installed tnt lite 2.2 at which time the nexus boot animation appeared and has been around ever since. With the initial rom change and each change after I have wiped all data. Was the nexus boot animation part of the ota update? And if so why is it not being wiped when I change roms?
Rushless,
To answer your question, when I use hardware decoding I see the lock up and reboot you describe. When I use software decoding everything works fine. I have only played MP4 videos.
thebrain73 said:
Ok maybe you could tone down your ego a bit and use your vastly superior knowledge to explain how my tablet got a boot screen that is supposedly not in any of the code I or viewsonic loaded on to it.
All I know at this point is that I bought the tablet on december 28 2010. I charged the device, booted it up for the first time and let it do an ota update.i then installed clock work .8, then installed tnt lite 2.2 at which time the nexus boot animation appeared and has been around ever since. With the initial rom change and each change after I have wiped all data. Was the nexus boot animation part of the ota update? And if so why is it not being wiped when I change roms?
Click to expand...
Click to collapse
I don't have an ego issue so I don't know what I should be toning down. I responded to your post like that because it came across as another my tablet has it so it's right and yours is wrong post. If your tablet works, and you like the sparkles then great.. Doesn't really matter to me. My tablet works fine.
I don't have an answer for how you, and a few other people have ended up with the sparkle screen. My point is, and always has been that it does not belong in TnT, TnT Lite, or vegaN.
I have only seen that screen on a rom made for the G tab in one place and that is the original Zpad. Who knows what the OEM is loading on these things or how they are doing it. I have wondered if maybe some of these tablets may not have been destined to be Zpads, flashed with Zpad, and then ended up in a G tablet case and flashed with TnT at the factory or somewhere else later on to fill a shortage. If you don't clear data, dalvik, and do an Nvflash there is still stuff left over when I have done it. Who says the factory, or Viewsonic didn't shortcut?
My tablet came from the first batch of 1000 and it has never had the sparkle screen unless I put it there with the original Zpad rom. I don't have any idea if it really matter or not. But if folks are having issues it may be part of the cause and that was really the only purpose for me saying anything about it in the first place..
thebrain73 said:
Rushless,
To answer your question, when I use hardware decoding I see the lock up and reboot you describe. When I use software decoding everything works fine. I have only played MP4 videos.
Click to expand...
Click to collapse
I can use hardware mode, in vegaN, using clemsons kernel, Without it locking up. It should work.
RockPlayer Universal v1.6.0
I am Testing it now ... RockPlayer Universal v1.6.0
Tested and Dont work as good as 1.55
I think the root cause may be Rockplayer 1.6. I am not the only person having the issue and different roms.
Wish I knew that before installing 4.1 now. I had a solid device with 3.14 and the Clem kernel, but now starting from scratch. Bleh. Even with Titanium, the 1gb of apps I have- it takes a while. Smallest violin time.
rushless said:
I think the root cause may be Rockplayer 1.6. I am not the only person having the issue and different roms.
Wish I knew that before installing 4.1 now. I had a solid device with 3.14 and the Clem kernel, but now starting from scratch. Bleh. Even with Titanium, the 1gb of apps I have- it takes a while. Smallest violin time.
Click to expand...
Click to collapse
I wonder what they changed? I have 1.6 right now, admittedly don't use it a lot, but I haven't noticed a difference. Maybe the files you guys want it to play are a lot higher quality than what I use it for? I just watch mp4's that I made with Handbrake and it plays those well.
Sprdtyf350 said:
I wonder what they changed? I have 1.6 right now, admittedly don't use it a lot, but I haven't noticed a difference. Maybe the files you guys want it to play are a lot higher quality than what I use it for? I just watch mp4's that I made with Handbrake and it plays those well.
Click to expand...
Click to collapse
Prioir to 1.6, I could get higher def wmv files to play smooth with hardware decoding. Now it just kicks me out when trying to use it.
Same result with 4.1 and stock kernel as 3.14 with Clem. Only difference is Rockplayer 1.6 vs 1.55.
Need to find 1.55 and install it to confirm.
Related
I've had a weird problem with my phone for the past month where the camera preview shows the colors shifted. For example, my off-white desk is a mustard color transitioning to green, then black, then dark blue instead of what it actually is. If I take a picture, the wrong colors are saved. Sometimes it works correctly but that's pretty rare.
Any ideas? I was using the latest Cyanogen 1.6 rom, then I decided to try moving to CaNNoN202-CompleteEclair-v20 with the same results after wiping everything.
This seems to have started around the time I was messing with the extra RAM patch and JIT hack but wouldn't installing the 2.0 ROM overwrite those? My free memory is 98,196k. The only thing I can think of is maybe the radio image got corrupted? Any ideas would be appreciated!
jcostantino said:
I've had a weird problem with my phone for the past month where the camera preview shows the colors shifted. For example, my off-white desk is a mustard color transitioning to green, then black, then dark blue instead of what it actually is. If I take a picture, the wrong colors are saved. Sometimes it works correctly but that's pretty rare.
Any ideas? I was using the latest Cyanogen 1.6 rom, then I decided to try moving to CaNNoN202-CompleteEclair-v20 with the same results after wiping everything.
This seems to have started around the time I was messing with the extra RAM patch and JIT hack but wouldn't installing the 2.0 ROM overwrite those? My free memory is 98,196k. The only thing I can think of is maybe the radio image got corrupted? Any ideas would be appreciated!
Click to expand...
Click to collapse
Did you have this problem with the Cyanogen rom?
Did you try clearing the data for the camera (Settings>Manage Applications>Camera>Clear data)
Binary100100 said:
Did you have this problem with the Cyanogen rom?
Did you try clearing the data for the camera (Settings>Manage Applications>Camera>Clear data)
Click to expand...
Click to collapse
The Cyanogen rom was working, then something happened around the time I did the RAM and JIT hacks and the camera screwed up. I reversed my changes but it never fixed the camera. Wiping and updating to the 2.0 ROM didn't fix anything either.
jcostantino said:
The Cyanogen rom was working, then something happened around the time I did the RAM and JIT hacks and the camera screwed up. I reversed my changes but it never fixed the camera. Wiping and updating to the 2.0 ROM didn't fix anything either.
Click to expand...
Click to collapse
Well I'm not familiar with the Eclair rom that you used. I would suggest going back to CM and see if that clears it up.
Sounds like hardware issue to me. :/ Lets hope its not.
Agreed - I doubt I have warranty left. The strange thing is that it will work every so often but 95% of the time it won't.
I attached an example picture I just took. Some of it is right but mostly everything is wacky colors.
I vaguely remember this being a problem on the original cooked roms but I don't think it was quite like this.
I reflashed the radio and that didn't do anything - I suppose the next logical step would be to use the drea100.nbf and go back to total bone stock with nothing.
jcostantino said:
Agreed - I doubt I have warranty left. The strange thing is that it will work every so often but 95% of the time it won't.
I attached an example picture I just took. Some of it is right but mostly everything is wacky colors.
I vaguely remember this being a problem on the original cooked roms but I don't think it was quite like this.
I reflashed the radio and that didn't do anything - I suppose the next logical step would be to use the drea100.nbf and go back to total bone stock with nothing.
Click to expand...
Click to collapse
I had exact same thing. I had warranty left so I sent it in. Sorry.
jcostantino said:
Agreed - I doubt I have warranty left. The strange thing is that it will work every so often but 95% of the time it won't.
I attached an example picture I just took. Some of it is right but mostly everything is wacky colors.
I vaguely remember this being a problem on the original cooked roms but I don't think it was quite like this.
I reflashed the radio and that didn't do anything - I suppose the next logical step would be to use the drea100.nbf and go back to total bone stock with nothing.
Click to expand...
Click to collapse
I don't know why, but I kinda like that. It's a nice effect. It reminds me of the Predator movies.
Binary100100 said:
I don't know why, but I kinda like that. It's a nice effect. It reminds me of the Predator movies.
Click to expand...
Click to collapse
Straight trade, my phone for yours then
Binary100100 said:
I don't know why, but I kinda like that. It's a nice effect. It reminds me of the Predator movies.
Click to expand...
Click to collapse
I agree. It looks really cool. Take a picture, submit it into a contest, and when enough money for a new phone.
Kidding, but I'm really sorry you're having this problem. As much as I HATE that ****ty camera HTC gave us, I find myself using it constantly. I would still lean towards hardware, though. =[
jcostantino said:
Straight trade, my phone for yours then
Click to expand...
Click to collapse
LOL! Ummm... no?
I preordered my G1 on the launch in 2008 and I still have warranty until December 2010? WTF?
There was an update and not it supports 2.2 so I went ahead and downloaded it. I am having nothing but issues with it. It plays really choppy. Basically unplayable and it kinda sucks cause it took 20 minutes to download the data so I cant even return it.
Anyone else having issues with this game? I'm running Vegan 5.11
i am having issues with this game too. choppy if it even runs at all, and that's when it's not causing my entire tablet to freeze up.
My advice: wait to download this one until they have fixed the massive amounts of bugs that are floating around in it.
I agree, right now I have waisted $10
Also choppy and crashing. Wouldn't recommend anyone buy this yet.
This makes me sad, I had high hopes for this.
Did any of you try restarting your tablet after downloading? I downloaded and tried to run it and it was very laggy and was no good so I restarted and it works perfectly. I play it all the time with not one issue.
Since the last update, i've had no more problems with this game.
whatsupa said:
Did any of you try restarting your tablet after downloading? I downloaded and tried to run it and it was very laggy and was no good so I restarted and it works perfectly. I play it all the time with not one issue.
Click to expand...
Click to collapse
I did exactly that. In fact, the crappy part is that you can only get it with the supplement for VegAn-TAB 5.11. Otherwise, it is not visible on the market or available through the Tegra App. However, the supplement kept killing my audio and making my device starting hissing out of the blue as if it were possessed.
I have a service emailinto the company to see if I can get a refund or if they can send me an apk.
It sucks. It was nice, but I had to sacrifice audio or video. It never played 100%.
I downloaded an updated version. And now its like butter. Game is ok. I prefer gun bros
All,
We don't have an ICS Bugs thread going on. I wanted to check with some of the people here on XDA to see if they are experiencing what I am. Currently on .213, but most of these bugs I've seen since the begining. Oh, I'm also in Canada running on 3G HSPA+. I'm stock, but rooted with safestrap installed.
1) When placing a phone call, the phone hangs up immediately (you here the disconnected beep), then retries the phone call a few seconds later (it always succeeds). I have tried this on a freshly wiped phone and found the same experience. I have also tried disabling the Assisted Dialing, but have found ikt's the same thing
2) When using Google Chrome, if there is a input box, most of the time my keyboard won't appear (I'm using Swype as my default keyboard)
3) Phone runs hot sometimes, and when it's running hot it slows down to a halt. Usually happens after a day or two without a restart
4) My photo doesn't appear in the text messaging app (worked in AOKP/CM9 on my D3, as well as it works on my gf's Nexus S)
The only bug I noticed was that it initially booted up in global mode, and wouldn't connect to 4G/CDMA. Switching it to CDM+LTE fixed the issue and I haven't seen a bug since (213).:good:
podspi said:
The only bug I noticed was that it initially booted up in global mode, and wouldn't connect to 4G/CDMA. Switching it to CDM+LTE fixed the issue and I haven't seen a bug since (213).:good:
Click to expand...
Click to collapse
Is your chrome working properly? Specifically the bug I mentioned in the OP...?
I didn't comment on that because I use Opera
Just tried the Chrome Beta now just to see, and I can confirm I am seeing the same behavior. I use Swiftkey, so it isn't a Swype-specific bug either.
What exactly is the difference between Chrome and the built-in browser? Aren't they both Webkit-based? Why is Google bothering to work on both?
podspi said:
I didn't comment on that because I use Opera
Just tried the Chrome Beta now just to see, and I can confirm I am seeing the same behavior. I use Swiftkey, so it isn't a Swype-specific bug either.
What exactly is the difference between Chrome and the built-in browser? Aren't they both Webkit-based? Why is Google bothering to work on both?
Click to expand...
Click to collapse
Chrome is way faster at many things since it users hardware acceleration for video. Does text input work properly on opera?
Sent from my XT894 running ICS
I'm in the US also running .213
I haven't noticed any bugs, its working fine for me. I do not use chrome beta so I can't comment on that. The stock is not too bad, I don't use it much anyways.
Sent from my DROID4 using xda app-developers app
danifunker said:
Chrome is way faster at many things since it users hardware acceleration for video. Does text input work properly on opera?
Sent from my XT894 running ICS
Click to expand...
Click to collapse
Text entry works fine in both the stock browser and Opera. BTW, Opera also has hardware acceleration, which is why it never worked in any of the Frankbuilds of ICS based off the GB kernel ... So you can have your teh snappy and type with it too :laugh:
I'm on the 212 build and i can't screencap using power + volume down.
Is this fixed in 213 or am i just doing it wrong?
Also on 212 i can't control the default google music app or winamp from my bluetooth headset when the screen is off. I could do this before with the same version of the winamp app when i was back on gingerbread. I tried upgrading winamp, but that did nothing. Is there any change in 213?
Thanks ahead of time
Edit: just tried it and the volume down + power combo worked. Lol
One question, possible thought to ponder.
Are the bugs being described here really bugs of Android 4 or are they bugs in the individual app itself not being fully compatible with Android 4 yet?
Do similar bugs happen on a non-motorola device with android 4?
I'm considering flashing one of the leaks, so I'm trying to understand how you are sure these are ics bugs before I make the leap and run into issues.
Thanks.
Apologies if this constitutes hijacking the thread, if it does let me know and I"ll edit it to delete the question.
I was able to figure out bug #4, I had to login with my Google+ account again, since the update yesterday everything seems to be working fine.
Bugs 1 through 3 still exist, although I've switched off Global mode for now and put it to GSM only, it seems like the phone runs a lot cooler in this mode.
Even after updating Chrome to the final version, I'm still experiencing that text input bug. Maybe it's a Motorola issue... Can't wait for the next version of the leak!
I have tasker reboot my phone every morning at 6am. The phone doesn't need to be rebooted every day, but it ensures that it is fresh and ready to go every morning :laugh:
Nothing more annoying than trying to do something with your phone and having to reboot it because it is slow for whatever reason.
podspi said:
I have tasker reboot my phone every morning at 6am. The phone doesn't need to be rebooted every day, but it ensures that it is fresh and ready to go every morning :laugh:
Nothing more annoying than trying to do something with your phone and having to reboot it because it is slow for whatever reason.
Click to expand...
Click to collapse
for this reason I think there will be other leaks, ICS is supposed to handle killing processes much better than GB, however the settings seem to not be aggressive enough in 213.
Probably there will be, though I likely won't update again for a while. Don't feel like losing all that data...
podspi said:
Probably there will be, though I likely won't update again for a while. Don't feel like losing all that data...
Click to expand...
Click to collapse
You could just do what I do: once you have root install safestrap and then take a backup of your phone before flashing the upgrade.
Once you're all done upgrading, re-root and re-install safestrap, then do an advanced restore and only restore the data. Voilla, all your apps are back.
podspi said:
Probably there will be, though I likely won't update again for a while. Don't feel like losing all that data...
Click to expand...
Click to collapse
I don't know, just had a random reboot after watching a youtube video in firefox, most likely memory related, not sure who's fault though, Motorola or Firefox. gotta root and use system tuner to change memory mgmt states.
danifunker said:
You could just do what I do: once you have root install safestrap and then take a backup of your phone before flashing the upgrade.
Once you're all done upgrading, re-root and re-install safestrap, then do an advanced restore and only restore the data. Voilla, all your apps are back.
Click to expand...
Click to collapse
That is a great idea. Though there hasn't been another leak since 213, so
Notification Bar Sticking/Wont Pull Down
I am on 212 currently, and I have noticed in 208 and 212 something that has happened only twice so far. Today, I just tried to check my notifications, and the bar will not pull down.
After a reboot it works fine, and it has only happened 2 times in the past couple weeks since the leaks first appeared.
Obviously it is a minor glitch, but just thought I'd throw it out there in case anyone else has seen it and overlooked it. :cyclops:
danifunker said:
You could just do what I do: once you have root install safestrap and then take a backup of your phone before flashing the upgrade.
Once you're all done upgrading, re-root and re-install safestrap, then do an advanced restore and only restore the data. Voilla, all your apps are back.
Click to expand...
Click to collapse
I have heard of a few others using this method successfully. If you are not using safestrap or just don't want to go this route take a look at the post link in my signature. It's a modified version of the original Droid 4 Utility and includes a script to jump from one ICS leak to another without losing data. It also flashes the GB files and the Kernel (boot.img) in one script, thus making it easier to go from one leak to another.
Regarding bugs, my wife got a razr yesterday. It wouldn't pull down the ICS update, so I just sideloaded it. We both run some of the same apps. So this gave me a chance to do side by side comparisons.The issue with some of the icons being small in the left top of the status seems to be a app issue. The chrome issue isn't present on the razr, of course there isn't a physical keyboard. Otherwise my 213 ICS seems to run great.
I found a new bug, it looks like GSM call forwarding doesn't work properly... at least it doesn't with my SIM card, I'm on Rogers in Canada.
Does Verizon support call forwarding? Does it work on there?
I have noticed in Chrome that pressing shift and then one of the symbol keys (like @) will only work if you hold the shift key.
More importantly I don't get notifications of app updates from google play. Check to see if you have any apps that need updating. Superuser had a update on July 1, dropbox yesterday and voodoo rootkeeper on June 28, I think. Anyone else?
Has anyone experienced this? While playing Madden Mobile it lagged quite a bit.
Yep! I have encryption disabled on mine and I have been seeing a lot of stuttering in games. I am not very happy with the performance I am seeing.
could also be that those games are not update to work with 5.0 yet. I haven't got my phone yet but if this is the case with most games, I will be disappointed.
I've been playing Soul Calibur (on sale for $4!!! Go go go!) and I was expecting it to lag. It didn't in fact the overall experience was awesome. That is why I wanted a Nexus phablet!
haven't experienced any game lag with Kingdom Rush Origins.
I'm seeing lag and stutters on Plauge Inc. and Asphalt 8 so far. I haven't tested other games as of yet. It's getting annoying. I might wipe everything and re-flash the stock image to see if it helps at all. What are you guys running right now? I'm rooted and un-encrypted on a 64GB Cloud White.
It could also be the apps themselves like Prod1702 suggested. I'm going to do a comparison with my co-workers N6 before I flash.
Update 1: I'm also seeing the stutters on the boot animation, co-worker is not on his 64GB MB. He is rooted and encrypted and has not changed DPI. I'm going to reflash stock and see if the issue persists.
HowIChrgeLazer said:
I'm seeing lag and stutters on Plauge Inc. and Asphalt 8 so far. I haven't tested other games as of yet. It's getting annoying. I might wipe everything and re-flash the stock image to see if it helps at all. What are you guys running right now? I'm rooted and un-encrypted on a 64GB Cloud White.
It could also be the apps themselves like Prod1702 suggested. I'm going to do a comparison with my co-workers N6 before I flash.
Click to expand...
Click to collapse
Stock 32gb
Okay so another update for you OP. I re-flashed with the stock image and did a (manual) full wipe of the userdata using the Nexus Root Toolkit. Also did root and removed encryption again with some manual flashing.
So far no stuttering in Plague Inc like it was before. Going to re-download Asphalt 8 to make sure. If that tests well, I'm going to slowly add things back to see if I can find what caused the problem.
Update 1: Added all google accounts and exchange accounts back, also re-installed my android wear stuff so far. Still no stutter, even after a power off and power on. Perhaps the image from the factory or the OTA update caused some issues with performance. Flashing the image from google via Nexus Root Toolkit seems to have fixed it so far. I'll post if the stuttering returns. Otherwise, it looks good now.
HowIChrgeLazer said:
Okay so another update for you OP. I re-flashed with the stock image and did a (manual) full wipe of the userdata using the Nexus Root Toolkit. Also did root and removed encryption again with some manual flashing.
So far no stuttering in Plague Inc like it was before. Going to re-download Asphalt 8 to make sure. If that tests well, I'm going to slowly add things back to see if I can find what caused the problem.
Update 1: Added all google accounts and exchange accounts back, also re-installed my android wear stuff so far. Still no stutter, even after a power off and power on. Perhaps the image from the factory or the OTA update caused some issues with performance. Flashing the image from google via Nexus Root Toolkit seems to have fixed it so far. I'll post if the stuttering returns. Otherwise, it looks good now.
Click to expand...
Click to collapse
Ill have to try flashing the stock image again too then. I am still using the encryption as I dont have any performance issues in homescreens and such, but most of my games lag pretty bad. it feels like they are running between 20-24 fps all the time. Rebooting doesnt help, closing all apps doesnt help. I was going to try removing encryption but it looks like people have the problem even with that. Ill just have to try reflashing the stock ROM and see if the lag goes away.
I just made a thread about this. Just purchased the new Gta Chinatown Wars for Android and it lags like crazy while driving around. Yet on my N5 it's perfectly smooth.
I'm starting to get real worried here
OK, so this is an interesting one that's not the end of the world but odd non the less.
My phone 64GB CW bought from GPS. Rooted only, stock recovery still. Lightflow, and carrier tether check disabled are the only two mods I really wanted.
My friend 64GB CW bought from GPS. Stock no root.
His phone will play crossy road just fine, Mine will boot it until it gets to the developer name then crash out.
Anyone else had weird quirks with apps like this after root? I've seen one thread about it and it said to clear the cache in recovery, and that didn't work for everyone. I haven't felt the need to put a 3rd party recovery on yet so I really can't do that quickly.
meest said:
OK, so this is an interesting one that's not the end of the world but odd non the less.
My phone 64GB CW bought from GPS. Rooted only, stock recovery still. Lightflow, and carrier tether check disabled are the only two mods I really wanted.
My friend 64GB CW bought from GPS. Stock no root.
His phone will play crossy road just fine, Mine will boot it until it gets to the developer name then crash out.
Anyone else had weird quirks with apps like this after root? I've seen one thread about it and it said to clear the cache in recovery, and that didn't work for everyone. I haven't felt the need to put a 3rd party recovery on yet so I really can't do that quickly.
Click to expand...
Click to collapse
Doesnt the stock recovery have a wipe cache option? It did on the 5
I've got a rooted 64GB MB and it plays Crossy Road just fine.
rootSU said:
Doesnt the stock recovery have a wipe cache option? It did on the 5
Click to expand...
Click to collapse
If there is I'm not sure how to get to it? I'm assuming a command of some sorts via ADB or Fastboot? This is my first Nexus device since my GNex since i'm on Verizon. So is my Friend though. Both of us still encrypted also. I've uninstalled and installed 4-5 times also. Cleared app cache a few times also.
I find it really strange as well. I download it, closes on developers name screen. Tried on two different roms and both don't work . Maybe just a bug. Not much info to be found on the issue.
jellybsly55 said:
I find it really strange as well. I download it, closes on developers name screen. Tried on two different roms and both don't work . Maybe just a bug. Not much info to be found on the issue.
Click to expand...
Click to collapse
What sort of similar changes have you been making? DPI changes, kernel changes or something else that may be common between the ROMs. Also, I am assuming you wiped in between the ROMs, if so did you restore data. I am just thinking out loud though. Logcats would probably help you find the cause of the problem.
Crossyroads has worked for me on stock, rooted or not, chroma, slimlp, try clearing data on the game, install from playstore and dont restore from TiBu if you are.
Donjuanal said:
Crossyroads has worked for me on stock, rooted or not, chroma, slimlp, try clearing data on the game, install from playstore and dont restore from TiBu if you are.
Click to expand...
Click to collapse
Yeah it's quite weird. (Nexus 5 though, shouldn't really make a difference). I don't even have a cache/date to clear since the game won't boot up enough to make one i think . Quite strange, just wanted to say that the OP isn't only one
It crashed everytime on my N6 so I emailed the developer and he said it doesn't work with ad blockers installed.. So I disabled the adblocker I had running and crossy road loaded just fine with exact same setup.. So if you have adblockers that's probably the issue.
meest said:
OK, so this is an interesting one that's not the end of the world but odd non the less.
My phone 64GB CW bought from GPS. Rooted only, stock recovery still. Lightflow, and carrier tether check disabled are the only two mods I really wanted.
My friend 64GB CW bought from GPS. Stock no root.
His phone will play crossy road just fine, Mine will boot it until it gets to the developer name then crash out.
Anyone else had weird quirks with apps like this after root? I've seen one thread about it and it said to clear the cache in recovery, and that didn't work for everyone. I haven't felt the need to put a 3rd party recovery on yet so I really can't do that quickly.
Click to expand...
Click to collapse
See attached pic
We need min min guard for lollipop or something that let's us choose which apps to block ads.