Related
Haven't looked at it yet, but found it in my normal scan (I didn't have the build number that high before, so I must have missed it the last few weeks):
http://tapntap.http.internapcdn.net/tapntap/viewsonic/update-smb_a1002-5274-user.zip
EO July build date. USE AT YOUR OWN RISK, as always. I'm going to dissect this tomorrow or Saturday and, if there's anything of importance in there, I'll make a Mountain Laurel update out of it (if the power stays on, of course - Irene, please be kind!).
roebeet said:
Haven't looked at it yet, but found it in my normal scan (I didn't have the build number that high before, so I must have missed it the last few weeks):
http://tapntap.http.internapcdn.net/tapntap/viewsonic/update-smb_a1002-5274-user.zip
EO July build date. USE AT YOUR OWN RISK, as always. I'm going to dissect this tomorrow or Saturday and, if there's anything of importance in there, I'll make a Mountain Laurel update out of it (if the power stays on, of course - Irene, please be kind!).
Click to expand...
Click to collapse
Awesome, looking forward to your findings...
HIGH DEFINITION VIDEO PLAYBACK IS FIXED, with this build (it was broken in all the previous 1.2 stock ROMS -- 3991, 4349 and I believe 4950). I use the same 1080p main profile video for all my baseline tests, and it's working in 5274 stock.
That, in itself, is a good enough reason to deploy this into Mountain Laurel. However, I have to test if I need to use their kernel or not, so more testing would be needed. Worst case, I'd deploy with their kernel, like I used to do with TNT Lite - but of course I still need to check sleep.
This thing also has a newer bootloader, but Mountain Laurel always includes that. Might be related to the video fix, but again not certain without further testing.
As for other changes, probably nothing much - I'm seeing only the usual app and framework files being touched post 4950, the Wifi was touched as well libvodm_query. The camera is still mirrored incorrectly, as it has been on all 1.2 builds.
EDIT: I have a prototype with the pershoot kernel, and video playback is still working. Awesome - good to see that this is finally fixed.
EDIT2: Pulling out the pershoot kernel and testing a "mostly stock" version, like I used to do with TNT Lite. If sleep is working and battery life seems improved, it might be worth going back to that type of release. If someone wants a custom kernel, it's fairly easy to add it on your own.
I think they finally "got it right" with this 5274, going on my testing so far. A worthy successor to 3588 and 4349 stock, imo.
EDIT3: Spoke too soon - sleep issues are cropping up. Might need to keep pershoot's kernel after all -- no worries.
Outstanding work Roe.
When you say new bootloader, do you mean 1.2 or do you mean something else?
It's still 1.2 based - but it's got a newer timestamp, and I have a reliable source that tells me that it's been tweaked. Btw, my ML update is released - I stuck with a 3.0.0 with a stock kernel, as that's what I used to do for TNT Lite. Pershoot / Clem kernels can always be installed by the user, if they wanted. (I had retested sleep on a clean machine, no apps, and had no SOD).
Btw, it seems very obvious to me that the 1.1 branch is now long dead. TapnTap have only done 1.2-based work for the Olipad and Hannspad these last few months, the Adam has been 1.2 since almost Day One, and all the GTAB TapnTap work since March (3991, 4349, 4950 and now 5274) are all 1.2-based.
Sooner or later there will be a stock release, and it will almost certainly be 1.2-based, again. I would argue that this 5274 may very well be their next GA release, it's just a question of when. I hope Cyanagenmod will eventually swing over.
Very awesome Roe. I have been using Vegan 5.1.1 with VTL mainly because it covers *my* basic needs: PvZ, Keyboard/mouse, hardware acceleration, HD video. ANd I dodn't need to bother going to a 1.2 ROM. I think now is the time to go 1.2 and check out a newer ROM.
One question: does Mountain Laurel suffer from the media delete issue? Is .nomedia required? Not being able to access media on Vegan 5.1.1 (after applying the .nomedia fix) is kind of lousy.
roebeet said:
It's still 1.2 based - but it's got a newer timestamp, and I have a reliable source that tells me that it's been tweaked. Btw, my ML update is released - I stuck with a 3.0.0 with a stock kernel, as that's what I used to do for TNT Lite. Pershoot / Clem kernels can always be installed by the user, if they wanted. (I had retested sleep on a clean machine, no apps, and had no SOD).
Btw, it seems very obvious to me that the 1.1 branch is now long dead. TapnTap have only done 1.2-based work for the Olipad and Hannspad these last few months, the Adam has been 1.2 since almost Day One, and all the GTAB TapnTap work since March (3991, 4349, 4950 and now 5274) are all 1.2-based.
Sooner or later there will be a stock release, and it will almost certainly be 1.2-based, again. I would argue that this 5274 may very well be their next GA release, it's just a question of when. I hope Cyanagenmod will eventually swing over.
Click to expand...
Click to collapse
Will you repack as a nvflash package, wait for the GA, or none of these?
Actually, one more question: did you try the stock 5274 ROM and see if it ran any better than before? My biggest complaint with stock was that it was so slow, but I always liked the LOOK of it, especially the weather app.
mike_ekim said:
Very awesome Roe. I have been using Vegan 5.1.1 with VTL mainly because it covers *my* basic needs: PvZ, Keyboard/mouse, hardware acceleration, HD video. ANd I dodn't need to bother going to a 1.2 ROM. I think now is the time to go 1.2 and check out a newer ROM.
One question: does Mountain Laurel suffer from the media delete issue? Is .nomedia required? Not being able to access media on Vegan 5.1.1 (after applying the .nomedia fix) is kind of lousy.
Click to expand...
Click to collapse
From limited testing, I had no issues - for example none of my video test files got wiped. But only time will tell and it is a new kernel.
Btw, good point on PvZ - wish I knew what it was about the old VEGAn build kernel that makes it stable.
mike_ekim said:
Actually, one more question: did you try the stock 5274 ROM and see if it ran any better than before? My biggest complaint with stock was that it was so slow, but I always liked the LOOK of it, especially the weather app.
Click to expand...
Click to collapse
I'd have to go back and test things on builds 3991 / 4249 / 4950, but I would say that it feels snappier than 3588 for sure. And Nenamark / SmartBench scores seem to back that up. So far it really feels like a solid stock Froyo ROM and it's a shame that there are stock users with the ancient 3588 build that still don't have the option to get this ROM the "supported" way.
aabbondanza said:
Will you repack as a nvflash package, wait for the GA, or none of these?
Click to expand...
Click to collapse
I'm going to wait until next week and, assuming the new Mountain Laurel mod I just released doesn't have any serious issues, I'm going to update my 4349-based nvflash to 5274. I probably won't wait for GA, because I could be waiting a long time.
@roebeet awesome work as usual... I'm really really impressed with the speed of your releases... fantastic work... thanks a million for making my GTab well worth the money I spent!!
Hello Roebeet. How was your much deserved break?
Would this happen to have the market included? If not would old methods of getting it on work?
Would you recommend pershoots or clemsyns kernel, what is difference other than 1400 compared to 1500?
Also would you happen to know if than old nvrdaemon file/hack from back in the day than dexter put out would work?
Its been a while seen running stock, always liked it but took honeycomb plunge. Thinking about going back to hassle free stock, flash and hd playback is a plus!
I would think the performance is better than 3588, 4349??? I do miss the back to top of page tab in 3588 browser that 4349 didnt have. Saved a boat of scrolling. Is that option back?
Thanks and hope all is well with weather, I noticed your in western pa, im 20 min from Philadelphia and its not looking all that hot. Need something to do while cooped up. This sounds like it could be fun to tinker with!
Let me answer some questions which I'm sure off...
gkitab said:
Would this happen to have the market included? If not would old methods of getting it on work?
Click to expand...
Click to collapse
Market 3.1.3 (latest Market to date) is included in ML3.0.0... along with the olympus (Motorola Atrix) build props...
gkitab said:
Would you recommend pershoots or clemsyns kernel, what is difference other than 1400 compared to 1500?
Click to expand...
Click to collapse
Honestly, I think pershoot's kernel is better... It is updated more frequently and includes some latest Tegra changes... and OC to 1400 is definitely much more stable than OC to 1500... without any real noticeable difference (maybe some full HD videos might work a bit better at 1500)
gkitab said:
I would think the performance is better than 3588, 4349??? I do miss the back to top of page tab in 3588 browser that 4349 didnt have. Saved a boat of scrolling. Is that option back?
Click to expand...
Click to collapse
It is definitely smoother than the previous versions (3588, 4349, etc.), but no, there is no "scroll to top" option in the browser...
I took the plunge and installed this update to see if it would fix the SOD I have been experiencing on all 1.2bl based roms. Did the following:
Booted to CWM
Cleared user data
Clear dalvik cache
Formatted cache, system, data, sdcard
Copied file to internal memory and renamed to update.zip
Installed from CWM using update.zip
Clear data, cache, dalvik cache
Reboot
Finish setup and make sure everything works.
Downloaded Flashback 7.2 to sdcard
Clear cache, data, dalvik
Reboot and enjoy.
Funny thing is my tablet still has SOD with every honeycomb rom i tried. Only time i dont is on 1.1bl based honeycomb roms. Everything else is working fine.
Sent from my Flashback 7.2 using xda premium
craigacgomez said:
Let me answer some questions which I'm sure off...
Market 3.1.3 (latest Market to date) is included in ML3.0.0... along with the olympus (Motorola Atrix) build props...
Honestly, I think pershoot's kernel is better... It is updated more frequently and includes some latest Tegra changes... and OC to 1400 is definitely much more stable than OC to 1500... without any real noticeable difference (maybe some full HD videos might work a bit better at 1500)
It is definitely smoother than the previous versions (3588, 4349, etc.), but no, there is no "scroll to top" option in the browser...
Click to expand...
Click to collapse
I agree, yes its smoother.
You are correct that pershoots has been updated, did not think about that.
Bummer on the back to top tap. I think its stupid that they removed that. It was mighty convienent.
Now, what are you talking about with the market. It does not have it. What's the atrix talk about?
Sleep of Death?
What does that entail?
For each and every 1.2 bootloader version from TnT (only TnT), I have problems with the home screen crashing unless I change it on 1st boot to Classic. It happended with Mountain Laurel too, yes the new Roebeet version of this week in included in that.
The home screen will crash as soon as I unlock the screen, unless I have changed it in the previous boot. So, I leave it on Classic. I have ML installed, homescreen changed to classic. All my software installed and now its time for a CWM backup.
Am I experiencing the SoD?
Roe,
It's been a looooonng while since I flashed a stock TnT update but if this is stable I would like to update my wife's Gtab to this most current one. Can you point me in the direction of the market and accelerometer fixes along with anything else I might be forgetting? I would just put Mountain Laurel on hers but she likes the stock TnT interface, besides she is not tech minded so I am keeping hers mostly stock with just the necessary fixes. I really do wish there was some way I could talk you into doing a modified stock TnT update.zip (stock with all the fixes already included). Thanks for all that you do and here's to hoping that you and your family made it through Irene OK.
thx -- still picking up the pieces post-Irene (basement was flooded so I'm ripping out the carpeting today).
As for ML, the install actually loads a stock image first, then I layer all the custom changes afterwards. So, if you enjoy a little trial and error, you could look into the update.zip and alter it to your needs. For the TnT apps, I first delete them and, in some cases, overlay them with stock apps - so you'd need to look at both the updater-script and /system folder, for what you want to alter.
roebeet said:
thx -- still picking up the pieces post-Irene (basement was flooded so I'm ripping out the carpeting today).
As for ML, the install actually loads a stock image first, then I layer all the custom changes afterwards. So, if you enjoy a little trial and error, you could look into the update.zip and alter it to your needs. For the TnT apps, I first delete them and, in some cases, overlay them with stock apps - so you'd need to look at both the updater-script and /system folder, for what you want to alter.
Click to expand...
Click to collapse
Hope all is well. Good luck with basement. Near Philly I only lost power about six hours sat night into sun, but being under tornado warning in our county and having one roll down our street last year, the old ladyhad us sleep down basement sat night. Basement floor is not comfy.
Anyways what is the best way to go about getting market on this. Been a long time since running stock. Kinda like it but missing market.
One other thing, remember in 3588, while browsing we had the back to top tab that saved alot of scrolling in browser. Also when you would click something in the browser the top bar would drop down and you would see the progress icon so you would know your press registered. Why they did away with these things I don't get, it made the browser much more user friendly, is there a way to bring those two things back?
Never really noticed those before, but my guess is that the Browser apk could be replaced from the 52xx one to the 3588 one, to see if that functionality returns.
Roebeet, do you make any changes to boot.img except to add the ML image?
Also, is anyone seeing any problems booting with 5274? I can't get my gtab to boot with it. Just sits on the boot animation forever.. like hours.. until the screen jsut goes off. Then you can tap power and it comes right back to the boot animation, almost like sleep mode during the boot.
I am trying to get a rom that doesn't do this, has this issue been resolved? I can lay my device down at random times and I will come back to the device at the Asus screen locked up. Thanks in advanced tried the search filter maybe my keywords weren't correct. Thanks to all.
Found? lol no no one has 'found' one..lmao
We don't 'find' ROMs here, we develop them (or rather THEY do, I don't yet).
The reboot issue seems to be related to the kernel, and all the ROMs use the Asus kernel (with the exception being blades' new kernel, but it still suffers reboots). So there isn't a solution yet. A few workarounds, preventative measures or wive's tales that 'remedy' or make them 'less frequent', but no solutions.
buffalosolja42 said:
I am trying to get a rom that doesn't do this, has this issue been resolved? I can lay my device down at random times and I will come back to the device at the Asus screen locked up. Thanks in advanced tried the search filter maybe my keywords weren't correct. Thanks to all.
Click to expand...
Click to collapse
I'm running revolver 1.3.1 and havne't actually had a single reboot, force close of bad experience, perfect so far and its been running since the release!!!
geenius said:
I'm running revolver 1.3.1 and havne't actually had a single reboot, force close of bad experience, perfect so far and its been running since the release!!!
Click to expand...
Click to collapse
Same here, no instances of any of the reported problems and I even bought my TF101 as a refurb.
b1lk1 said:
Same here, no instances of any of the reported problems and I even bought my TF101 as a refurb.
Click to expand...
Click to collapse
Wonder what applications are running in your TF. The same thing here with my TF. No reboots, no SODs...
However, after posting in several threads about my luck..
here they come... reboot.... reboot... reboot... simply by opening market...
The only thing I like?... no battery drain!
Just accept it until xda devs will figure out the best solution!
Cheers!
Hi
I flashed the Android Revolution 3.1.0 on Friday and have had 1 freeze up and 2 times file manager didnt run after I installed mxvideo player. But otherwise all good.
Sent from my Transformer TF101 using XDA
luna_c666 said:
The reboot issue seems to be related to the kernel, and all the ROMs use the Asus kernel (with the exception being blades' new kernel, but it still suffers reboots). So there isn't a solution yet. A few workarounds, preventative measures or wive's tales that 'remedy' or make them 'less frequent', but no solutions.
Click to expand...
Click to collapse
This is the situation, there is not definitive solution yet, people gets different results with same or different ROMs, its purely luck if you don't have Reboots or freezes, the solution should be something kernel related, most probably tegra2 drivers (as it has been tweeted by gnufabio few weeks ago)
geenius said:
I'm running revolver 1.3.1 and havne't actually had a single reboot, force close of bad experience, perfect so far and its been running since the release!!!
Click to expand...
Click to collapse
This is just an example of users happy with their ROM without issues, but it is just luck.
AOKP and CM9 with cornerstone never rebooted on me. With the Blades kernel I had a few reboots but nothing serious.
Then again I don't have any nvidia tegra gaming stuff installed.
Sent from my Transformer TF101 using Tapatalk
I run a pretty full range of apps. I use the GPS a fair bit, lots of web surfing with flash as well as email. I do lot of games including a handful of Tegra 2 games. Only issues I have right now is Angry Birds Space freezing, but that is common accross all platforms as well. DOes not cause reboot.
I can go from using it all day to leaving it idle for 3-4 days. I never power it down and have left it off the charger for days in a row. I do tend to leave it on the keyboard dock nearly all the time, but it does see some time off dock.
One thing to add, when I first flashed to Revolver ICS, I foolishly flashed an OC kernel for HC. Needless to say I bricked it. Took me 1/2 a day to get it going again after flashing back to stock HC, then stock ICS and finally Revolver ICS. Been up ever since then and that was over 3 weeks ago, more likely 4+. Only time I get a reboot is if I initialize it. No sleep/freezing issues other than the noted single instance.
I call this luck of the draw and likely as to why ASUS can't figure it out since this problem seems like a some have it and some don't thing.
And yet I got a random reboot on a brand new install of pure stock 9.2.1.17 that I had nvflashed within 12 hours, and with blades kernel forget about it.. every hour reboot, and then on pure stock again I got splash screen boot loops..
I have never been experiencing the reboots either, but I only tried Android Revolution HD and CyanogenMod.
For some reason however, I will experience sleeps of death soon as I configure the Wi-Fi to shutdown when the screen is off.
geenius said:
I'm running revolver 1.3.1 and havne't actually had a single reboot, force close of bad experience, perfect so far and its been running since the release!!!
Click to expand...
Click to collapse
Same here. Was running a stock rooted version of ICS with Revolver 4 flashed over the top (I know this wasn't recommended, but I did it one night by accident, and it solved the other issues I was having with Revolver.
I moved on to CodeName Android after the other ICS ROMs pulled ahead. I haven't had the issue there either.
I don't know what the deal is.....but I'm thankful I don't have the issue! And even if I did, I only consume media on my transformer. So I can't say that it'd be a big deal.
1 and 1/2 days without a reboot
Turned off face unlock..... guess I'm not handsome enough to wake up my tablet. But I have wifi on as well. I will report but it seems to be running better.
So. I am a moderately happy owner of a TF101. It was running ICS .17 and I had all sorts of issues with it, from RR to SOD to sound disappearing.
The SOD vanished when I set it to turn wifi off when screen was off, the sound and reboots were "fixed" by turning the device off if I expected to be more than 1 or 2 hours away from it.
However, I still experienced graphics corruption in some games (Angry Birds Space, Anomaly: Warzone Earth) and on the youtube app, to name the ones on the top of my head. I checked Wolf's guide to downgrade, rooted my TF101 and while I was waiting for the blob download to finish, Asus pushed the .21 FOTA on my tab.
I am a regular user who ran the device without root for 2 months, I have no special needs besides stability and no headaches.
So, the question is: was HC all that better? I mean Asus FW, WW 8.6.6.23. Was it really that much better than ICS to justify a downgrade?
EDIT: First milestone passed, 20 hours of uptime, no issues at all. So far, so good. I even noticed better video compatibility with some of my old divx4 and mpeg files
EDIT 2: 50 hours of uptime, no issues at all, games working perfectly (not a single crash or video corruption in Angry Birds Space). I am really really happy with the downgrade
Try one of the threads below.
http://forum.xda-developers.com/showthread.php?t=1622609
http://forum.xda-developers.com/showthread.php?t=1617290
Thanks for the reply
I know how to downgrade. What I really want to know is if it is worth the time.
Is the Asus Honeycomb firmware really much more stable and almost issues free?
Or people are just so pissed with the issues on ICS that they are overpraising HC?
I did not had the tablet with HC long enough to know on my own.
Most people just didn't wipe going to the latest version and think that flashing back to HC will fix all of their problems.
Really, if you are happy with ICS and SOD/RR's are at a minimum, definately stick with it. The features in ICS very much outweigh one or two less RR's a week.
Asked Man said:
I know how to downgrade. What I really want to know is if it is worth the time.
Is the Asus Honeycomb firmware really much more stable and almost issues free?
Or people are just so pissed with the issues on ICS that they are overpraising HC?
I did not had the tablet with HC long enough to know on my own.
Click to expand...
Click to collapse
Yes, Honeycomb was that much more stable. As soon as I'm done testing for Asus, I will be going back to Honeycomb - it's rock solid.
Yu do need to downgrade via NVFlash, or the ICS problems persist, even in Hoenycomb...
Sent from my Transformer TF101 using Tapatalk 2
jtrosky said:
Yu do need to downgrade via NVFlash
Click to expand...
Click to collapse
Then I am out of luck, mine is a B70, not sure of the SBK, but I believe it is incompatible.
Anyway, tried to downgrade using Wolf's method ( http://forum.xda-developers.com/showthread.php?t=1622628 ) and testing now.
Will stick with it for at least a month to draw fair conclusions.
Let's see how that goes.
miketoasty said:
Most people just didn't wipe going to the latest version and think that flashing back to HC will fix all of their problems.
Click to expand...
Click to collapse
That is exactly my belief. I wiped mine before going to ICS that seemed to fix my issues. My two main issues were battery drain & not deep sleeping. I never had a SOD & only a couple of random reboots.
Other people have reported that once they flash back to HC, they are having the same issues. I am with the belief that wiping is the key for some anyway.
jadesse said:
That is exactly my belief. I wiped mine before going to ICS that seemed to fix my issues. My two main issues were battery drain & not deep sleeping. I never had a SOD & only a couple of random reboots.
Other people have reported that once they flash back to HC, they are having the same issues. I am with the belief that wiping is the key for some anyway.
Click to expand...
Click to collapse
Oh, believe me, I have wiped more times that I care to admit - believe me, wiping is NOT the solution!! Unless we are talking about more than one problem...
Sent from my Transformer TF101 using Tapatalk 2
In terms of wiping
I tried:
Factory reset at .17
factory reset, wipe, downgrade to .11 or whatever was before .17, then FOTA
same as above, but doing manual upgrade to .17
Of course I liked ICS and my tab was working, with a few caveats. I had more reboots before the wipe, but the deep sleep remained a problem and I had sound and video issues.
Not many, not frequent, but I definitely had. My son gave up on Angry birds space, as an example. Too many force closes. Not a game issue, since it ran fine on my xperia play. And so far, I got 3 stars on 12 stages, not a single issue, on my recently downgraded tf101.
I don't know, maybe ICS is still green, I heard people used to have issues with Asus HC as well in the beginning. Maybe I just like too much of things that just work. But so far, I haven't seen any of the issues I was having with ICS.
Time will tell.
Reached another milestone
120 hours of uptime, 3 people using the device. However, EA's monopoly stopped working after the 3rd day, so now I rebooted the tab to get it running back again.
It was a success, cleared every single issue I had, but I came to notice that after 3 or 4 days up, the tab starts to run slower than usual, taking longer to open programs, etc.
Anyway, the downgrade was successful and the tab works fine now. So, it was worth for me, since I want stock experience on the tab.
So you are using Wolf's method to downgrade? and to what ROM?
Which Wolf method do you use Root or not root?
If it's not NVFlash method that can solved SOD. I will follow you!!
Guys - you may want to hang on before downgrading - we're testing a new beta release from Asus (.24) and so far, things are looking really good... I have a feeling that the ICS RR/SOD issues will be a thing of the past really soon...
Sent from my Transformer TF101 using Tapatalk 2
jtrosky said:
Guys - you may want to hang on before downgrading - we're testing a new beta release from Asus (.24) and so far, things are looking really good... I have a feeling that the ICS RR/SOD issues will be a thing of the past really soon...
Sent from my Transformer TF101 using Tapatalk 2
Click to expand...
Click to collapse
Hope it will get out soon!!
warlord234 said:
So you are using Wolf's method to downgrade? and to what ROM?
Which Wolf method do you use Root or not root?
If it's not NVFlash method that can solved SOD. I will follow you!!
Click to expand...
Click to collapse
Yes, downgraded using the Method 1 - Rooted.
The ROM I am using is Stock HC WW 8.6.6.23, no modifications.
jtrosky said:
Guys - you may want to hang on before downgrading - we're testing a new beta release from Asus (.24) and so far, things are looking really good... I have a feeling that the ICS RR/SOD issues will be a thing of the past really soon...
Click to expand...
Click to collapse
Maybe. I stuck with ICS from .11 up to .21 and I still had graphic corruption in games (mostly Angry Birds Space) and my touchscreen became less responsive. OTOH, on HC I get zero issues.
Don't get me wrong, I really liked ICS. There are some things that annoys me on HC, like the default browser not open new tabs on background. But I don't like to beta test stuff anymore, so I will stay on HC until the stock ICS has all the issues cleared.
See I'm a sort of flip to this, HC gave me all sorts of HELL, but when I wiped and went to ICS (Keep in mind I did use CWM to flash Rooted stock at the time, so I wiped Dalvik, Cache and Factory reset) from there it's been beautiful, I only got one SOD and the occasional screen tear. When I upgraded to an actual Dev rom (ARHD first, now I'm on AOK/SP) and put a modded kernel on, issues ceased to exist. So I'm really happy with ICS overall, even though my experience is Far from stock..
Thing O Doom said:
So I'm really happy with ICS overall, even though my experience is Far from stock..
Click to expand...
Click to collapse
I came to notice that most people that are fully happy with ICS deviated from stock. I am still not planning to deviate from stock, but I might when I go back to ICS. I got my pad on january, still waiting for the 12 months warranty to expire before unlocking bootloader and flashing custom kernels.
Howdy hello,
I've been on my Nexus S since GB. Ever since I've rooted and been running custom ROMs. I've had some awesome experiences but some crappy ones at the same time, all of which I attributed to my phone running a custom ROM.
Now I've finally got the new, new stock JB on my device, and after running it for a few weeks, I'm a bit disappointed. The features are nice and all, but there are so many issues I face that make it near unusable. To name a few:
Google Now takes way too long to pull up. At least 5 seconds and even while it's loading the cards, it's very laggy. The search button used to be a quick way for me to search for something, but the is effectively ruined with this lag.
Constantly losing data / connectivity. I know this may be at the carrier level, but I've never had this much trouble. ALSO, in these cases, the phone will often be reporting that it has full bars / full 3g connectivity, so either way the phone is acting screwy. I mean seriously, the one thing I need my phone to do is make a damn phone call, yet it semi-frequently fails to do so.
Apps fail left and right. Today my youtube app crashed in the middle of the first video I pulled up on it. I know this isn't really the OS, but it's part of the stock experience, and I think android should be held responsible.
Just a few minor gripes. I'm just wondering: has anyone else experienced this? I did a full wipe before installing the stock JB rom, and I don't think it could just be root permissions making things go wacky. I may consider re-wiping and only installing a few apps, but I really don't have that much crap installed, so I'm not sure if that's the issue as well.
I saw another post recommending to get a new SIM card from AT&T. I have had mine for a few years, so that could be a possible fix for issue #2, but I don't think that's the entire reason.
Any feedback is welcome. Thanks a lot all.
Stock JB was very laggy on my NS for some reason. Even swipping pages in the home screen was laggy. Some apps would instantly crash, too.
I've been running custom JB roms on my Nexus S, and its been running really well. The only thing is im experiencing the same lag that you do with Google Now. It has caused me to open my browser to do a search, which is disappointing, because in GB and ICS, the Google Search bar was so quick and convenient.
shyguyhighfive said:
Howdy hello,
I've been on my Nexus S since GB. Ever since I've rooted and been running custom ROMs. I've had some awesome experiences but some crappy ones at the same time, all of which I attributed to my phone running a custom ROM.
Now I've finally got the new, new stock JB on my device, and after running it for a few weeks, I'm a bit disappointed. The features are nice and all, but there are so many issues I face that make it near unusable. To name a few:
Google Now takes way too long to pull up. At least 5 seconds and even while it's loading the cards, it's very laggy. The search button used to be a quick way for me to search for something, but the is effectively ruined with this lag.
Constantly losing data / connectivity. I know this may be at the carrier level, but I've never had this much trouble. ALSO, in these cases, the phone will often be reporting that it has full bars / full 3g connectivity, so either way the phone is acting screwy. I mean seriously, the one thing I need my phone to do is make a damn phone call, yet it semi-frequently fails to do so.
Apps fail left and right. Today my youtube app crashed in the middle of the first video I pulled up on it. I know this isn't really the OS, but it's part of the stock experience, and I think android should be held responsible.
Just a few minor gripes. I'm just wondering: has anyone else experienced this? I did a full wipe before installing the stock JB rom, and I don't think it could just be root permissions making things go wacky. I may consider re-wiping and only installing a few apps, but I really don't have that much crap installed, so I'm not sure if that's the issue as well.
I saw another post recommending to get a new SIM card from AT&T. I have had mine for a few years, so that could be a possible fix for issue #2, but I don't think that's the entire reason.
Any feedback is welcome. Thanks a lot all.
Click to expand...
Click to collapse
The cards could be taking longer to load because of your flaky connectivity. Can't expect them to load instantly if your data/signal is dying all the time, can you?
Definitely an inferior experience here on stock JB compared to ICS. Really hope Google fix this in an incremental update, as it's a bit silly their second-best phone can't run JB properly.
polobunny said:
The cards could be taking longer to load because of your flaky connectivity. Can't expect them to load instantly if your data/signal is dying all the time, can you?
Click to expand...
Click to collapse
heh, that's a fair point. I'm not so upset with the cards taking a long time to load as I am that, while they are loading, the OS is very unstable. It's difficult for me to bring up the keyboard and search google while it's trying to load those cards. I can't believe it's not butter
Nothijngrad said:
Definitely an inferior experience here on stock JB compared to ICS. Really hope Google fix this in an incremental update, as it's a bit silly their second-best phone can't run JB properly.
Click to expand...
Click to collapse
My thoughts exactly . I was excited to get back on stock so I could have a functional phone without any added bells and whistles. New features are nice, but not at this price.
Try running a custom kernel.. Try the thalamus kernel its very stockish and it's SUPER smooth..
Sent from my Nexus S 4G using xda premium
I'm running stock on [email protected] with a matrix kernel everything smooth for me
Sent from my Nexus S using xda premium
I had problems with JB too. There were a few lags, especially with Google Now. Some apps would crash every time I tried to open them, and the launcher crashed every time I tried to change wall paper.
shyguyhighfive said:
Howdy hello,
I've been on my Nexus S since GB. Ever since I've rooted and been running custom ROMs. I've had some awesome experiences but some crappy ones at the same time, all of which I attributed to my phone running a custom ROM.
Now I've finally got the new, new stock JB on my device, and after running it for a few weeks, I'm a bit disappointed. The features are nice and all, but there are so many issues I face that make it near unusable. To name a few:
Google Now takes way too long to pull up. At least 5 seconds and even while it's loading the cards, it's very laggy. The search button used to be a quick way for me to search for something, but the is effectively ruined with this lag.
Constantly losing data / connectivity. I know this may be at the carrier level, but I've never had this much trouble. ALSO, in these cases, the phone will often be reporting that it has full bars / full 3g connectivity, so either way the phone is acting screwy. I mean seriously, the one thing I need my phone to do is make a damn phone call, yet it semi-frequently fails to do so.
Apps fail left and right. Today my youtube app crashed in the middle of the first video I pulled up on it. I know this isn't really the OS, but it's part of the stock experience, and I think android should be held responsible.
Just a few minor gripes. I'm just wondering: has anyone else experienced this? I did a full wipe before installing the stock JB rom, and I don't think it could just be root permissions making things go wacky. I may consider re-wiping and only installing a few apps, but I really don't have that much crap installed, so I'm not sure if that's the issue as well.
I saw another post recommending to get a new SIM card from AT&T. I have had mine for a few years, so that could be a possible fix for issue #2, but I don't think that's the entire reason.
Any feedback is welcome. Thanks a lot all.
Click to expand...
Click to collapse
Hmm I can say that AOSP JB is WAYYYY better than ICS. Soon I can port my ROM from the NS4G to the NS.
I have to agree with this. I've used stock JB when it was released, I was wowed by it's smoothness and cool animations. But everything felt a little slow and sluggish coming from ICS custom rom. After switching to Jellybro, JB feels both very fast and smooth. If you feel disappointed with JB, try using custom rom.
Sent from my Nexus S using Tapatalk 2
I don't know if you guys with problem tried that yet, but it might be a good idea to do a factory reset. You will lose all your data if not backed up but I'm getting a feeling it could help. JB has only been smoother than ICS for most.
Looking to get an NS soon, but it may help, as others have mentioned to run a custom kernel and bump up the clock speeds a bit.
My N1 is almost perfectly smooth (very little lag and often times none) with JB installed and overclocked.
My GNEX is smooth as butter. (As to be expected). But I guess what I'm saying is, if the N1 can run JB smooth, then the NS should not have any problems.
And while I know AOSP is technically designed to run on multiple devices, only two were in mind when JB was released....the N7 and the GNEX. Everything else is an afterthought in which AOSP may not be fully optimized for the hardware that is pushing it. (Just my opinion).
And another opinion while I'm on my soap box. JB is what ICS should have been.
In my opinion 512 MB of RAM are a tight fit for Jelly Bean. I can just run 3-4 background apps without kill-restart-kill-restart-kill-restart and a constant lag.
I remember some kernels used to have compcache support. Maybe I could try to enable compcache/zram.
got556 said:
Looking to get an NS soon, but it may help, as others have mentioned to run a custom kernel and bump up the clock speeds a bit.
My N1 is almost perfectly smooth (very little lag and often times none) with JB installed and overclocked.
My GNEX is smooth as butter. (As to be expected). But I guess what I'm saying is, if the N1 can run JB smooth, then the NS should not have any problems.
And while I know AOSP is technically designed to run on multiple devices, only two were in mind when JB was released....the N7 and the GNEX. Everything else is an afterthought in which AOSP may not be fully optimized for the hardware that is pushing it. (Just my opinion).
And another opinion while I'm on my soap box. JB is what ICS should have been.
Click to expand...
Click to collapse
I just got my GNex and the difference with JB on this phone is night and day. I didn't think it would be but I'm pleasantly surprised. But yeah. The RAM issue seems to be my biggest gripe with it on the NS. And for some reason, it just dominated my battery. I went through my first cycle on stock with Trinity and managed 3.5 hours of screen time over the course of almost 17 hours and still had a little under 50% remaining. My NS would've been dead long before that with the same usage pattern.....
I run stock JB with Matr1x. It works very very well.
---------- Post added at 01:46 PM ---------- Previous post was at 01:44 PM ----------
ekerazha said:
In my opinion 512 MB of RAM are a tight fit for Jelly Bean. I can just run 3-4 background apps without kill-restart-kill-restart-kill-restart and a constant lag.
I remember some kernels used to have compcache support. Maybe I could try to enable compcache/zram.
Click to expand...
Click to collapse
Not to mention it only uses 368 mb of them. If it used the full 512, it would be pretty nice
I'm running Androxide 3.1 and used to run AdamG's custom ROM. Both ran great, no hiccups what so ever, Google now loads very fast, I guess it depends on your GPS and internet connection. My experience with JB is far better than the fastest ICS ROM out there, I believe given enough time, performance will become exceptional.
Logomotph said:
I run stock JB with Matr1x. It works very very well.
---------- Post added at 01:46 PM ---------- Previous post was at 01:44 PM ----------
Not to mention it only uses 368 mb of them. If it used the full 512, it would be pretty nice
Click to expand...
Click to collapse
That can be tweaked a bit with different kernels.
I am running XenonHD 9 + marmite 4.2 kernel. It's stable and smooth. Worth a try.
I'm getting my tablet Monday and I really don't want to have to flash different roms just to find one that works best.
I prefer Cyanogen stuff, I'm running the nightlies on my Razr Maxx HD, and would like to continue using it on a tablet. HOWEVER, it seems that Cromi has a more developed ROM. Am I wrong? What do you guys think is the best rom and why?
yugendreams said:
I'm getting my tablet Monday and I really don't want to have to flash different roms just to find one that works best.
I prefer Cyanogen stuff, I'm running the nightlies on my Razr Maxx HD, and would like to continue using it on a tablet. HOWEVER, it seems that Cromi has a more developed ROM. Am I wrong? What do you guys think is the best rom and why?
Click to expand...
Click to collapse
CROMi-X obviously
Try a few out though - see what you think.
yugendreams said:
I'm getting my tablet Monday and I really don't want to have to flash different roms just to find one that works best.
I prefer Cyanogen stuff, I'm running the nightlies on my Razr Maxx HD, and would like to continue using it on a tablet. HOWEVER, it seems that Cromi has a more developed ROM. Am I wrong? What do you guys think is the best rom and why?
Click to expand...
Click to collapse
Wait a few weeks and you may not have to decide! sbdags and _that are continuing to work on ROM2SD for CROMi-X! Run his rom on internal and another rom on your microSD. Already works for CROMi-X, miniCROMi-X, but CM is coming - I can feel it
Linux is where the real funs at
JoinTheRealms said:
Linux is where the real funs at
Click to expand...
Click to collapse
If only I had the time to study.....:crying:
yugendreams said:
I'm getting my tablet Monday and I really don't want to have to flash different roms just to find one that works best.
I prefer Cyanogen stuff, I'm running the nightlies on my Razr Maxx HD, and would like to continue using it on a tablet. HOWEVER, it seems that Cromi has a more developed ROM. Am I wrong? What do you guys think is the best rom and why?
Click to expand...
Click to collapse
Cromi-x is highly recommended, but on my tablet it did run well at all. I would recommend going with cyan based rom, I run cyan on all my other android devices and i could not get used to the Asus based roms at all.
Currently running CMB even without data2sd like cromi-x had it way smoother and hasn't crashed yet. Plus has all the cyan features i know and love...
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
sjgieson said:
Cromi-x is highly recommended, but on my tablet it did run well at all. I would recommend going with cyan based rom, I run cyan on all my other android devices and i could not get used to the Asus based roms at all.
Currently running CMB even without data2sd like cromi-x had it way smoother and hasn't crashed yet. Plus has all the cyan features i know and love...
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Click to expand...
Click to collapse
You are the first person to say that so must be something else you did to cause poor performance.
I'd love to get you up and running properly on cromi-x.
sbdags said:
You are the first person to say that so must be something else you did to cause poor performance.
I'd love to get you up and running properly on cromi-x.
Click to expand...
Click to collapse
@sjgieson
His rom, sbdags, is very fast and smooth. I don't know how are we going to accurately measure the speed of the tf700t. According to most of the testers, all the measurement apps are lied and can not be trusted but fast and smooth are even worst because there are no data or numbers associating with the test data to back up the conclusion. Otherwise, we can test them side by side... It is just my opinion and don't kill me if I am saying something wrong...
LetMeKnow said:
@sjgieson
His rom, sbdags, is very fast and smooth. I don't know how are we going to accurately measure the speed of the tf700t. According to most of the testers, all the measurement apps are lied and can not be trusted but fast and smooth are even worst because there are no data or numbers associating with the test data to back up the conclusion. Otherwise, we can test them side by side... It is just my opinion and don't kill me if I am saying something wrong...
Click to expand...
Click to collapse
I have had the TF700 for just a few weeks, but go back Droid1 days with running custom roms. Current devices is a Gnex running experimental KitKat, and Nexus 7 that is the wives DD running 10.1.
My experience with TF is as follows get device, unlock, try to load custom rom find out USB data port is DOA, return device, get new one, take two days to get unlock app to work (just kept trying) rejoiced due to unlocking, download Cromi latests, flashed with DATA2SD and choosing Hunds kernel. Running it that way for about 10 days, getting frustrated and returning to CM based ROM (I have ran CM on GNEX and previous devices 80-90% of the time).
First off, let me say I may be wrong about my Cromi situation and probably should have held off posting my experiences. In the last 24 hours I have spent a lot more time on these forums and have sdbags 1:1 helping me getting Data2SD up and running on CM based 4.3 rom. I have been reading more of the posts instead of just skimming them loooking for what I need to fix something and move on. I have to say I am impressed at folks here (specifically _that and sdbags), their ingenuity and expertise (not mention willingness to contribute) is impressively and rarely seen these days in my opinion.
To answer your question about speed, yes, Cromi-x was fast, by far the fastest 4.2 rom to date on any device I have ran. I am sure this is due to Data2SD and the many many tweaks that have been made. However I know 4.2 is plagued by no trim, and at least on my Gnex 4.3 based roms are more responsive (less times hung with no response) than 4.2 roms. So first off I have bad taste in my mouth with anything related to 4.2 because of my Gnex experiences (probably wrong way to look at things I know). So going in I was little worried about 4.2 based.
Here is a list of annoyances with the rom being based on Asus and not AOSP:
Pulldown menu (pull up in the table interface) not being Googles menu (why change it)
Softkeyboard layout (trying to get the at symbol), no swiping (IIRC)
No cCLOCK widget (I wish I didn't like that CM thing so much...)
None of those were deal breakers, I had planned on addressing those eventually but the following occured:
First boot, confirmed data2sd was working, ran benchmarks, was impressed how well it ran etc. Installed my apps, all was good with the world love at first boot....
Sat it down on table (was in dock) rebooted, came back up to welcome screen, lock tablet was restore to factory. Perplexed, I reinstalled my apps, and went about my merry way (never re-ran benchmarks or really looked into the files system too much, my bad).
Next few days crashed reboots occurred randomly (maybe due to the Hunds OC kernel, should have tried stock kernel i suppose)
Finally one day a reboot occured and I rebooted back into my original environment I had setup in the first few hours of Cromi, my data from the environment I was in appeared lost. At this point the annoyances listed above (related to Asus, not the Cromi-rom) were too much.
I wiped everthing (even formated SD card), and went to CMB (why I didn't go striaght 10.2 I don't know). I have not had one single reboot/crash since the move, it is pretty peppy and I am getting really good benchmarks for not having data2sd installed, which is odd. If I didn't see how fast cromi was, I wouldn't be looking to get data2sd back as of right now i feel like 4.3 AOSP with data2sd has to be faster than 4.2 ASUS w/ data2sd.
Obviously, after writing the above issues I didn't follow good trouble shooting practices and perhaps made emotional not logical decisions.
sbdags - I will give Cromi-X another go
sjgieson said:
I have had the TF700 for just a few weeks, but go back Droid1 days with running custom roms. Current devices is a Gnex running experimental KitKat, and Nexus 7 that is the wives DD running 10.1.
My experience with TF is as follows get device, unlock, try to load custom rom find out USB data port is DOA, return device, get new one, take two days to get unlock app to work (just kept trying) rejoiced due to unlocking, download Cromi latests, flashed with DATA2SD and choosing Hunds kernel. Running it that way for about 10 days, getting frustrated and returning to CM based ROM (I have ran CM on GNEX and previous devices 80-90% of the time).
First off, let me say I may be wrong about my Cromi situation and probably should have held off posting my experiences. In the last 24 hours I have spent a lot more time on these forums and have sdbags 1:1 helping me getting Data2SD up and running on CM based 4.3 rom. I have been reading more of the posts instead of just skimming them loooking for what I need to fix something and move on. I have to say I am impressed at folks here (specifically _that and sdbags), their ingenuity and expertise (not mention willingness to contribute) is impressively and rarely seen these days in my opinion.
To answer your question about speed, yes, Cromi-x was fast, by far the fastest 4.2 rom to date on any device I have ran. I am sure this is due to Data2SD and the many many tweaks that have been made. However I know 4.2 is plagued by no trim, and at least on my Gnex 4.3 based roms are more responsive (less times hung with no response) than 4.2 roms. So first off I have bad taste in my mouth with anything related to 4.2 because of my Gnex experiences (probably wrong way to look at things I know). So going in I was little worried about 4.2 based.
Here is a list of annoyances with the rom being based on Asus and not AOSP:
Pulldown menu (pull up in the table interface) not being Googles menu (why change it)
Softkeyboard layout (trying to get the at symbol), no swiping (IIRC)
No cCLOCK widget (I wish I didn't like that CM thing so much...)
None of those were deal breakers, I had planned on addressing those eventually but the following occured:
First boot, confirmed data2sd was working, ran benchmarks, was impressed how well it ran etc. Installed my apps, all was good with the world love at first boot....
Sat it down on table (was in dock) rebooted, came back up to welcome screen, lock tablet was restore to factory. Perplexed, I reinstalled my apps, and went about my merry way (never re-ran benchmarks or really looked into the files system too much, my bad).
Next few days crashed reboots occurred randomly (maybe due to the Hunds OC kernel, should have tried stock kernel i suppose)
Finally one day a reboot occured and I rebooted back into my original environment I had setup in the first few hours of Cromi, my data from the environment I was in appeared lost. At this point the annoyances listed above (related to Asus, not the Cromi-rom) were too much.
I wiped everthing (even formated SD card), and went to CMB (why I didn't go striaght 10.2 I don't know). I have not had one single reboot/crash since the move, it is pretty peppy and I am getting really good benchmarks for not having data2sd installed, which is odd. If I didn't see how fast cromi was, I wouldn't be looking to get data2sd back as of right now i feel like 4.3 AOSP with data2sd has to be faster than 4.2 ASUS w/ data2sd.
Obviously, after writing the above issues I didn't follow good trouble shooting practices and perhaps made emotional not logical decisions.
sbdags - I will give Cromi-X another go
Click to expand...
Click to collapse
Wow, thanks for the good explanation... What I said was just my opinion, I hope that you are not offended..
Also, there is a trim supported on Cromi X but that would depend on the version of the kernel. You can ask _that or sbdags to help you mount it if it is not currently mounting as an option...
Good luck...:fingers-crossed:
Nope no offense taken! As you had a point .
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
The only time I experience a crashing application is with boat browser. I leave the setting for flash set to always on and flash itself isn't a clean application. That is what causes my tablet to force close the app. I've not experienced the rebooting that I did running pure stock Asus firmware either and it otherwise runs perfect.
Maybe try using one of _that's OC kernals. While not as fast as hunds, they are stable and still offer a greater experience than stock. I haven't found needed to use the 1.8ghz performance mode in his kernals and for my needs the balanced setting at 1.3ghz works fine. The extra boost is there if needed.
Speed doesn't mean you will have the best user experience from the tablet. While hardware specs are meant to be the same for all TF700s, each component is different due to the manufacturing process for each tablet assembled. The CPU/components in your tablet may not play nice with hunds kernal.
a very good one
try cmbroms running 4.3.1 but very close to building 4.4 weekly updates and there great love it. if you have any question there team is very fast to respond http://forum.xda-developers.com/newreply.php?do=newreply&noquote=1&p=47629521:cowboy:
I have been running Cromi-X 5.1 for a few weeks now and it works great.
46584963
were running cmbroms over here and loving it i hear from up the grapevine there getting kitkate soon so will be getting 4.4.1 cant wait the 4.3.1 is solid as a rock and i build them myself on my linix machine loving it
yugendreams said:
I'm getting my tablet Monday and I really don't want to have to flash different roms just to find one that works best.
I prefer Cyanogen stuff, I'm running the nightlies on my Razr Maxx HD, and would like to continue using it on a tablet. HOWEVER, it seems that Cromi has a more developed ROM. Am I wrong? What do you guys think is the best rom and why?
Click to expand...
Click to collapse
Cromi-X will be a good option. I think it give you more freedom to install what you want a bit more flexible.
sbdags said:
You are the first person to say that so must be something else you did to cause poor performance.
I'd love to get you up and running properly on cromi-x.
Click to expand...
Click to collapse
Hello and greetings from new user of TF700T.
I have been using this ROM for 3 days and I can say while the performance of cromi-x is not poor, it's not great either. Certainly better than CM11 (tried that before switching to cromi-x), but navigating the entire Android OS still feels sluggish. Not to say my TF700T is always slow, but tapping home button for instance, could take me 2-3 seconds before it starts reacting. When I open any apps, the transition animation is also sluggish, which is worse if I navigate apps from recent apps button. Lastly and the worst, Google Now and Google Now Launcher are very unpleasant to use, freezes on the opening and lags almost on the entire time.
I wonder if this kind of experience normal in TF700T considering the tablet is 2 years old? Or there are some tweaks I missed? I am currently running CROMi-X 5.4 Xenogenesis DEODEX.
For whatever the reason is, I'm still thankful for such a great ROM. It's the guys like you who make Android different and beautiful
Anggrian said:
Hello and greetings from new user of TF700T.
I have been using this ROM for 3 days and I can say while the performance of cromi-x is not poor, it's not great either. Certainly better than CM11 (tried that before switching to cromi-x), but navigating the entire Android OS still feels sluggish. Not to say my TF700T is always slow, but tapping home button for instance, could take me 2-3 seconds before it starts reacting. When I open any apps, the transition animation is also sluggish, which is worse if I navigate apps from recent apps button.
I wonder if this kind of experience normal in TF700T considering the tablet is 2 years old? Or there are some tweaks I missed? I am currently running CROMi-X 5.4 Xenogenesis DEODEX.
For whatever the reason is, I'm still thankful for such a great ROM. It's the guys like you who make Android different and beautiful
Click to expand...
Click to collapse
Would you like to try my Extreme Tweaks, ET? Give it a shot and tell us what you think...:laugh:
Will hold on to this ROM for a week. If there is no possible improvement could be made, I'll different ROMs, your Extreme Tweaks, and basically anything dangerous
Sent from my Nexus 5 using XDA Free mobile app
Anggrian said:
Will hold on to this ROM for a week. If there is no possible improvement could be made, I'll different ROMs, your Extreme Tweaks, and basically anything dangerous
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Actually, it is a part of the Cromi X v5.4. It is working fine with Cromi X ROM only and never test with other ROMs. It is running perfectly fine with all of my testers except one that he had a weird waking up issue....