Related
Just wanted to get some opinions on what people are running on their G Tablets, and feel is the best performing ROM?
Also do most/all ROMs support and utilize the dual core of the Tegra?
Any opinions and suggestions on getting the best performing G Tablet would be greatly appreciated!
Thanks much.
Anything on the 1.2 bootloader is going to perform better. The kernels activate the second core at 60% of core ones capacity where kernels for 1.1 activate core 2 at redline of core 1.
Thanks Mantara. Any personal preferences on ROMS? I've tried TNT Lite, and like it, but seem to still have some sluggishness with WIFI, and would like to try something newer based on an Android 2.3 or 3.0 core.
Hold off on any 3.0 roms for now. Still lots of brick issues.
Are you on bootloader 1.1 or 1.2?
If your on 1.1 try calculins+clemsyns version 5. Its got cool tweeks that block adds and control CPU speed based on battery level. It is my personal favorite.
If your on 1.2 I would use cm7 mod for 1.2 in the development section. You can easily get Netflix working, its stable and it has that cyanogen charm that has really made android shine.
You can use cm7 on bootloader 1.1 and C+C on 1.2 (version 6) but through my use I have found them faster and more stable running on the BLs I stated above.
All this is just personal preference though. The whole reason we are on this site is trying things out to find out exactly what we personally like.
Happy flashing,
Ive only had my gtab for a week. Ive tried cm7 based on the. 1.1 then i went to vegan based on 1.2. The vegan is much faster but im not sure if its vegan itself or the different build that is making such a big difference
Vegan 7 has some good tweeks. It just isn't being supported any more.
Kernel makes a big difference. Did you flash a new kernel over cm7?
Also with 1.2 vegan the stock kernel (made by pershoot) is optomized and overclocked to 1.4ghz.
Cm7 for 1.2 has more optimization and than vegan simply for the fact vegan is based off of cm7 7.0.0
And the 1.2 cm7 is 7.0.3. That's about a thousand changes to the rom.
Mantara said:
Hold off on any 3.0 roms for now. Still lots of brick issues.
Click to expand...
Click to collapse
Respectfully disagree with this statement. I have been running Roebeet's HC ROMs since the very beginning and, except for a couple of brief problematic versions, have thoroughly enjoyed them all with no bricking along the way.
Currently on Bottle of Smoke 5.2 alpha and have yet to see issues when I flash to a new one. (IMHO) the vast majority of people who are soft-bricking are not following the correct instructions in some way. I did read about a bunch of issues with the illuminate version (modded copy of Roebeet's older ROM). If you stick with Roebeet's stuff and his directions (exactly) you should not have problems. Also GoodIntentions has his G-tab for Dummies site with even more simplified steps.
Before this I ran VEGAnTab (latest) and the only thing I had with that one that I don't now is the camera (no big loss) and flash videos (again, not a big deal). This is my daily driver - I have way over 200 apps installed and every single one that I have tried works fine so far. Overclocked to 1.4 with no FCs yet. At work I stream music with TuneIn Pro and have News360 running all day long and still have 30+% of battery left at day's end. My Quadrant scores are usually 1800-2200 and that is with a pile of stuff being loaded at boot.
For me, it all basically boils down to the interface. I really like the HC one and could not go back to a FroYo or GB-based one now.
Plus, there is the "wow" factor. When someone says "you're running Honeycomb on that?" I just smile and say, "aren't you?"
@ mantra, i borked my tab on my first try going from cm7(1.1) to vegan(1.2) so i ended up nvflashing 1.2 stock then loaded vegan- not sure what exactly that mean on the state of my kernel. (first time paying with roms this week)
Mantara said:
Anything on the 1.2 bootloader is going to perform better. The kernels activate the second core at 60% of core ones capacity where kernels for 1.1 activate core 2 at redline of core 1.
Click to expand...
Click to collapse
I saw this comment last week, as well - do we have any evidence of this? Did someone test this and document or is this some third-party boast? I'm just curious because, if it's true, it's the first true improvement over 1.1. The other things like Adam compatibility are important, but it doesn't necessarily make 1.2 BETTER than 1.1, just a little more convenient for things like HC development.
Mantara said:
....Plus, there is the "wow" factor. When someone says "you're running Honeycomb on that?" I just smile and say, "aren't you?"
Click to expand...
Click to collapse
I love reading stuff like this - THAT makes modding worth doing. People have assumptions on the GTAB on what it can or can't do, so mods like this show them that it's not impossible if the vendor just pushed for it.
Btw, I agree about the interface over the 2.2/2.3 ROMs. The latter still feels like a big phone interface, even with the UI changes of things like CM7 or EDEN. HC really makes a tablet feel like a tablet, imo - and once they catch up with things like Netflix support, I think HC will eventually dominate.
Mantara said:
Hold off on any 3.0 roms for now. Still lots of brick issues.
Are you on bootloader 1.1 or 1.2?
If your on 1.1 try calculins+clemsyns version 5. Its got cool tweeks that block adds and control CPU speed based on battery level. It is my personal favorite.
If your on 1.2 I would use cm7 mod for 1.2 in the development section. You can easily get Netflix working, its stable and it has that cyanogen charm that has really made android shine.
You can use cm7 on bootloader 1.1 and C+C on 1.2 (version 6) but through my use I have found them faster and more stable running on the BLs I stated above.
All this is just personal preference though. The whole reason we are on this site is trying things out to find out exactly what we personally like.
Happy flashing,
Click to expand...
Click to collapse
Thanks much! That's exactly what I was looking for, some personal preferences as a starting point.
I'm not sure if I have 1.1 or 1.2 on the boot loader - would love to get NetFlix going on it; so that's prob. going to be my starting point.
Bells and Whistles are nice lol
nunjabusiness said:
...
For me, it all basically boils down to the interface. I really like the HC one and could not go back to a FroYo or GB-based one now.
Plus, there is the "wow" factor. When someone says "you're running Honeycomb on that?" I just smile and say, "aren't you?"
Click to expand...
Click to collapse
Thanks Nun. I definitely would love to have a better interface than the typical phone feel; and NetFlix would be great.
tmx2112 said:
Just wanted to get some opinions on what people are running on their G Tablets, and feel is the best performing ROM?
Also do most/all ROMs support and utilize the dual core of the Tegra?
Any opinions and suggestions on getting the best performing G Tablet would be greatly appreciated!
Thanks much.
Click to expand...
Click to collapse
well so far. i haven noticed much difference in 1.1 and 1.2 roms. both variations have the plus and minus
best performing
Click to expand...
Click to collapse
i think it would be froyo, since everything is supported. FULL hw acceleration (of what ive been told). gb roms were pretty good too. But still have issues. and hc have many issues.
so froyo roms. now which one. ive tried the beastly one, and that was the best for me. Im currently on b corners but too many problems that i might go back to beastlys if i cant figure out this damn wifi bug
cheers
After a couple weeks venturing in the honeycomb world, I'm back to froyo. Specifically, I'm back to calk+clem combo.
VTL launcher + ripple lock + scrollable widgets + full hardware acceleration + OC + full stability = me happy.
roebeet said:
I saw this comment last week, as well - do we have any evidence of this? Did someone test this and document or is this some third-party boast? I'm just curious because, if it's true, it's the first true improvement over 1.1. The other things like Adam compatibility are important, but it doesn't necessarily make 1.2 BETTER than 1.1, just a little more convenient for things like HC development.
.
Click to expand...
Click to collapse
As far as I know neither clemsyn and pershoot have made 1.1 versions of their alterations to the 1.2 kernels that change the power step in the second cores activation.
From his 1.2 kernel thread,
clemsyn said:
In 1.1 cpu1 runs onlywhen cpu0 is running 1000 and above. In 1.2 I changed it to run when cpu0 is 600 and above. I can also make one for 1.1 but I'm moving forward to 1.2.
Click to expand...
Click to collapse
I have not read pershoots change log in a two weeks-ish so that may have changed but clemsyn has stated that he will Not make a 1.1 version with the change in power step as he is looking towards the future (1.2) and not the past (1.1). I'm just going off of what I have read on here and SLD. If I am reading this wrong I would appreciate a correction. I don't want to be spreading fallacy all over xda and misleading people.
As far as HC, once its in beta, I will shout it rom the rooftops that people flash it. Until then recommending it to flash as one of your first roms I can't recommend. HC will dominate the tablet world, it is beauty and functionality in motion. But to a person just wanting stability and full functionality it doesn't hit the mark yet. I believe to understand the present and to grasp the future you must know your history. This is why I will always recommend flashing a froyo or GB varient the first time, at least until HC is at least the state that GB is with hardware accell and flash.
As stated earlier, this is just my preference and that is the reason we are all on this site, its all about personal preference.
Thanks - so it's not that it's not possible, it's just that at least one of the kernel devs (Clem) isn't planning to backport his 1.2 changes to 1.1.
I'm a very big supporter of 1.2, but it's important to make that distinction, imo. I'm really not sure WHY there's a 1.2 to begin with (yes, we know that the voltage levels were changed, but not why it was done). All I know is that the Adam is 1.2 based, and Notion Ink is our best chance right now for an HC port with full acceleration. So 1.2 is where I'm staying.
Agreed on you assessment of the current HC port, btw. I call it an alpha for a reason - some things work really well, but a few important things are broken so it's more for advanced users who don't mind the caveats.
I just got my tablet about a month ago, so I'm new to a lot of this stuff. I've learned quite a lot so far. I'm using VEGAn-Tab Ginger edition. I thought about trying some of the other roms, but everything I need works fine on this one. Flash,Videos,web browsing,slingplayer, and others. Maybe when a beta version of honeycomb becomes available I'll upgrade.
just a follow up on this question- i have tried about 8 of the roms so far i love the "feel of the ginger and honey comb roms better but so far nothing beats the calk+clem combo for functionality and speed. i currently run it at 1.4 using cpu master to dial it back a bit. i had a bit of instability running it at 1.5
Try them all....I have yet to hear of a hard brick
Sent from my HERO200 using Tapatalk
tmx2112 said:
I'm not sure if I have 1.1 or 1.2 on the boot loader - would love to get NetFlix going on it; so that's prob. going to be my starting point.
Click to expand...
Click to collapse
roebeet said:
Btw, I agree about the interface over the 2.2/2.3 ROMs. The latter still feels like a big phone interface, even with the UI changes of things like CM7 or EDEN. HC really makes a tablet feel like a tablet, imo - and once they catch up with things like Netflix support, I think HC will eventually dominate.
Click to expand...
Click to collapse
One of the most exciting things I wanted to do on a tablet was run Netflix. Dare I say, once I saw a youtube video showing a G-tablet hacked to run Netflix properly (as well as Hulu directly off the site), it was my inspiration to bite the bullet and say I wanted one.
Little did I realize that Netflix currently only works on one rom, CM7, and that rom is not exactly the best option for this thing.
I just came back from a Digital Experience media event in NYC (I have a press pass), where I got to play with the new BB playbook, Samsung 10" tab, and the new webOS tablet. Made me realize how slow and laggy CM7 appears to have made my Gtablet! The tegra chip is capable of more, I've seen it fly through other roms, but I picked CM7 which lacks just about any kind of HW acceleration.
Meanwhile, there are all these little things that irk me- the camera doesn't work in apps like oovoo or yahoo messenger, there's a weird microSD/MMC bug that hides either your internal memory or your SD card (you can at least switch by flashing a zip that renames thins, but you still have to pick one to be invisible to most apps), and the mouse cursor doesn't work if you plug in a USB mouse.
That last one is an issue because I have one of these keyboard/mouse combo mini USB things:
http://gadgetynews.com/wp-content/uploads/2010/02/LenovoMiniWirelessKeyboard.jpg
And on other roms (like the stock one), it gives a mouse pointer I can move around and click where I want to pretend I'm touching the screen (pretty cool!). On CM7, it treats it like a track ball that moves the cursor around. So while I'm typing, if it shakes, the cursor moves to the left or right of where I'm trying to type. SUPER ANNOYING. I actually took some duct tape to hold the track ball down.
All this... so I can watch netflix in bed without a laptop. Worth it? I'm still doing it so I guess so. I mean, it was part of why I wanted a tablet. But I can't wait for more roms to work with netflix, I don't care if its Froyo. Just something fast that supports it and doesn't have all these little troublesome quirks!
I mean, someone is bound to figure out what makes it work on netflix and apply it to other roms, right? Or heck, maybe netflix will release an update that works with more devices soon? This is getting ridiculous, IMO!
Whew. Sorry for the rant, that's something I've been needing to say for a while!
Thanks Dishe ... they were some of the same little quirks I was reading about; actually one of the reasons I posted - I appreciate the feedback. I'm sure these guys out here busting it on all the cool ROMs will eventually hit one out of the park - provided all the vendors, i.e. Netflix, etc. get their act together, with DRM, etc.
-T
I'm a fairly new Galaxy Tab 10.1 user (had it for a few weeks, from the woot deal). I'm not new to android, however. I'm currently running the Task 7 ROM, but this issue seems to be present in all ROMs I've tried so far (including stock). Transition screens (when it zooms to launch an app), panning between home screens, scrolling in emails, etc. are all jerky.
I've seen threads about jerky video playback (movies), but I haven't seen much about this. I have to figure this either isn't happening to anyone else, or it's happening to everyone and people have just accepted it by now. Is there a fix for this? A kernel, or ROM, perhaps? Coming from an iPad, the jerkiness is very apparent, and it is really bothering me.
Thanks in advance...
dodgeboy said:
I'm a fairly new Galaxy Tab 10.1 user (had it for a few weeks, from the woot deal). I'm not new to android, however. I'm currently running the Task 7 ROM, but this issue seems to be present in all ROMs I've tried so far (including stock). Transition screens (when it zooms to launch an app), panning between home screens, scrolling in emails, etc. are all jerky.
I've seen threads about jerky video playback (movies), but I haven't seen much about this. I have to figure this either isn't happening to anyone else, or it's happening to everyone and people have just accepted it by now. Is there a fix for this? A kernel, or ROM, perhaps? Coming from an iPad, the jerkiness is very apparent, and it is really bothering me.
Thanks in advance...
Click to expand...
Click to collapse
I recommend getting a home screen replacement, like adw ex. That will get you silky smooth homescreen transitions. As far as any other lag, it can probably be fixed by overclocking. Tasks newest rom includes pershoots OC kernel, but make sure you do your homework before delving into overclocking.
At the moment my tab is running at 1.4 GHz and I haven't seen any lag, although you are correct that the device can be pretty jerky without using some of the great mods available here.
Sent from my Samsung Galaxy Tab 10.1
sendan said:
I recommend getting a home screen replacement, like adw ex. That will get you silky smooth homescreen transitions. As far as any other lag, it can probably be fixed by overclocking. Tasks newest rom includes pershoots OC kernel, but make sure you do your homework before delving into overclocking.
At the moment my tab is running at 1.4 GHz and I haven't seen any lag, although you are correct that the device can be pretty jerky without using some of the great mods available here.
Sent from my Samsung Galaxy Tab 10.1
Click to expand...
Click to collapse
I am running ADW EX. It dramatically improved the jerkiness, but it's still there. I mainly notice it when launching apps. The swiping between homescreens is not as noticeable.
I was hoping to not have to OC to fix the issue. In my experience (with phones) it usually leads to some other kind of instability...
Any other ideas? Could it be that the clock speed is dropping too low when nothing on the screen is moving, and doesn't spool back up fast enough?
dodgeboy said:
I am running ADW EX. It dramatically improved the jerkiness, but it's still there. I mainly notice it when launching apps. The swiping between homescreens is not as noticeable.
I was hoping to not have to OC to fix the issue. In my experience (with phones) it usually leads to some other kind of instability...
Any other ideas? Could it be that the clock speed is dropping too low when nothing on the screen is moving, and doesn't spool back up fast enough?
Click to expand...
Click to collapse
Yeah you could play around with different governors, although pershoot's kernels generally have optimal default settings.
As for your choice to not overclock, I can understand why you don't want to, (as I have a fascinate and it's all to easy to cause instability) however pershoot did a ridiculously good job. Paired with setcpu you really only have to move the slider to your desired clock and your good to go, I've never actually had a random reboot or sleep of death with this tablet at 1.4 GHz. If you only did a slight overclock I really don't think you will regret it...
Edit: Also keep in mind that this tablet allows widgets on the homescreen, and by default it uses non uniform icons. For this reason you should not be comparing it to an iPad. At the moment I'm running with the suave hd icon pack (uniform icons) with minimal widgets and it's just as smooth as an iPad. (but also more useful).
Also a small tip, turn off wallpaper scrolling in ADW, it makes it seem so much more laggy than it really is.
Sent from my Samsung Galaxy Tab 10.1
It will never be the same as an iOS device. Post 64 of the thread about ICS removing lag is helpful in shedding light on why. http://forum.xda-developers.com/showpost.php?p=20458845&postcount=64
Either overclock and live with a bit of it or get a plain uncustomizable iPad (talking homescreens).
That being said with pershoots kernel and supercharger/kernelizer/zipalign scripts the performance is noticably improved over stock and more than acceptable for many of us.
muzzy996 said:
It will never be the same as an iOS device. Post 64 of the thread about ICS removing lag is helpful in shedding light on why. http://forum.xda-developers.com/showpost.php?p=20458845&postcount=64
Either overclock and live with a bit of it or get a plain uncustomizable iPad (talking homescreens).
That being said with pershoots kernel and supercharger/kernelizer/zipalign scripts the performance is noticably improved over stock and more than acceptable for many of us.
Click to expand...
Click to collapse
+1 this. If smooth homescreen performance is your #1 priority in a tablet, get an ipad. It's lower resolution and doesn't have widgets so it's sort of a no-brainer why homescreen performance is generally better.
Thanks for your input, everyone. It turns out that my issue is almost nonexistent when the screen is oriented in landscape mode. All transitions are smoother, scrolling is smoother, etc. Seems silly, but that's the case. Unfortunately, I use the tablet primarily in portrait mode, for magazine reading and puzzle games.
Dave
It's been said that this is a Honeycomb issue (portrait vs landscape scrolling lag) and that ICS should improve upon this. Many such as myself use our tablets primarily in landscape mode so we tend to overlook the issue but those who need to use the device in portrait do have to suffer with it for now.
i have a valid question for you guys. every ice cream rom ive tried has given me significant lag/choppiness and heats up my rezound. now today i played with both a gnexus at verizon and a htc one x at at&t and it was smooth as butter. is our issues because of no ota or kernel source? just curious as to what you guys think?
thanks!
fix-this! said:
i have a valid question for you guys. every ice cream rom ive tried has given me significant lag/choppiness and heats up my rezound. now today i played with both a gnexus at verizon and a htc one x at at&t and it was smooth as butter. is our issues because of no ota or kernel source? just curious as to what you guys think?
thanks!
Click to expand...
Click to collapse
Both I would take a very educated guess in saying. no OTA means it is a work in progress and no kernel source means that the kernels aren't really tweaked out for the ROMs they are running....
my guess is sense bogs us down a good bit. also ics is coded for the gnex.
Without kernel source, we're stuck with what the leak has. From what I've read, that is not good.
I'm sticking with GB until we have source...GB flies for me!
Sent from my ADR6425LVW using Tapatalk 2 Beta-5
tspderek said:
my guess is sense bogs us down a good bit. also ics is coded for the gnex.
Click to expand...
Click to collapse
Yeah, Sense 3.5/.6 are steaming piles of laggy crap, but 4.0 seems really nice.
I have official ics on my unrooted galaxy tab 2. It has the touchwiz overlay but is still superfast. I was worried too that ICS was slow until I got this. I think the omap processor is a better performer on average than a qualcomm too, but not by much.
If you are running the gb kernel and firmware it is hit or miss with ics roms for the rezound. GB will always be faster if running gb firmware and kernel. I hope that the ics kernel is fixed when we get the official ics update and that sense doesnt bog things down. We really need htc to release kernel source and firmware in order to have a solid base for ics roms imo. I love Rez Rom Sense 3.6 ICS though, runs pretty good even on old firmware.
sent from my galaxy tab 2
LunaticSerenade said:
I'm sticking with GB until we have source...GB flies for me!
-5
Click to expand...
Click to collapse
GB flies for me too, even running a sense ROM.
I always chuckle when people post how "slow and laggy" sense is.
I get absolutely zero lag running sense 3.5 and figure those posters are probably clueless on how to correctly set up their system.......
tekhna said:
Yeah, Sense 3.5/.6 are steaming piles of laggy crap, but 4.0 seems really nice.
Click to expand...
Click to collapse
Actually for me all of the sense 4.0 ports were super laggy. I can say gb seems more fluid but the battery life still stinks on my rezound. That one x is really a nice device but im thinking this may be my last htc. I havent had good luck with the brand.
Thanks for the responses guys.
ICS doesn't lag for me ever, but I dig the Senseless roms for the looks, and indeed, Sense 4.0 isn't optimized for us yet.
jmorton10 said:
GB flies for me too, even running a sense ROM.
I always chuckle when people post how "slow and laggy" sense is.
I get absolutely zero lag running sense 3.5 and figure those posters are probably clueless on how to correctly set up their system.......
Click to expand...
Click to collapse
when i went from a sense rom to an aosp rom on my inc2 i noticed a big difference in speed. sense definitely affects things.
ics runs great for me on 3.5/3.6 and on 4.0 its great as well... i have no problems at all
I don't get all these people who have all the battery and heating problems. I think it is user error. I have better battery and better signal since I upgraded to ICS CleanROM.
GrayTheWolf said:
I don't get all these people who have all the battery and heating problems. I think it is user error. I have better battery and better signal since I upgraded to ICS CleanROM.
Click to expand...
Click to collapse
Agreed, if there were such a range in hardware that some overheated while others were great, I'd expect that HTC's quality control was so bad that half the units that were produced wouldn't even power up. Always get a kick out reading about someone who has warrantied a couple of phones then in the next breath says "I'm running "xyz" kernel and OC'd...
Anyway, would you mind sharing your setup Gray? It might help others to know what a working ICS setup is. What Kernel, Radios and other specifics are you running.
What I find is interesting is that with my first rezound I had a horrible experience when I flashed the ICS leak. Extreme overheating, even worse battery life, but it was nothing that I could have done. It was the radios on some hardware that cause this issue. I sent it back, got another, and reran the leak. Haven't looked back since. It's also worth noting that I have a way better experience with ICS then I did with GB. GB scrolling was always choppy and just overall sluggish. ICS fixed all that along with giving me a battery life ranging from 11-17 hours depending on usage.
nolimit78 said:
What I find is interesting is that with my first rezound I had a horrible experience when I flashed the ICS leak. Extreme overheating, even worse battery life, but it was nothing that I could have done. It was the radios on some hardware that cause this issue. I sent it back, got another, and reran the leak. Haven't looked back since. It's also worth noting that I have a way better experience with ICS then I did with GB. GB scrolling was always choppy and just overall sluggish. ICS fixed all that along with giving me a battery life ranging from 11-17 hours depending on usage.
Click to expand...
Click to collapse
I also have a better user experience, as in runs faster, smoother, and less lag along with better battery life on ice cream sandwich than I did on gingerbread. I think a lot of it has to do with how it's set up and configured. And I understand that some people have genuine hardware problems but it seems that it's causing a lot of people to quickly attribute their issues to hardware and not spend the time to chase down the problem and solve it. Regardless another leaked kernel or an official OTA base will definitely be welcomed and help this beast run even better.
bwthor20 said:
Agreed, if there were such a range in hardware that some overheated while others were great, I'd expect that HTC's quality control was so bad that half the units that were produced wouldn't even power up. Always get a kick out reading about someone who has warrantied a couple of phones then in the next breath says "I'm running "xyz" kernel and OC'd...
Anyway, would you mind sharing your setup Gray? It might help others to know what a working ICS setup is. What Kernel, Radios and other specifics are you running.
Click to expand...
Click to collapse
CleanROM Developer 1.2, overclocked 1.8ghz kernel, AmonRa recovery, new ICS radio, juopuntbear boot, S-Off.
Extremely smooth and no problems at all.
Ill put it in my sig too.
jmorton10 said:
GB flies for me too, even running a sense ROM.
I always chuckle when people post how "slow and laggy" sense is.
I get absolutely zero lag running sense 3.5 and figure those posters are probably clueless on how to correctly set up their system.......
Click to expand...
Click to collapse
I don't get any "lag" persay with any Rom I've used. What drives me a little nuts is the stuttery and choppy scrolling in a LOT of apps I use daily. The text and the pictures chop, even though the scrolling motion is smooth. Facebook, zynga apps, internet (if its more than text) messaging app, contacts, reddit news... There are some that don't stutter though. Twicca, tapatalk, menu scrolling, root explorer...
platinumrims said:
I don't get any "lag" persay with any Rom I've used. What drives me a little nuts is the stuttery and choppy scrolling in a LOT of apps I use daily. The text and the pictures chop, even though the scrolling motion is smooth. Facebook, zynga apps, internet (if its more than text) messaging app, contacts, reddit news... There are some that don't stutter though. Twicca, tapatalk, menu scrolling, root explorer...
Click to expand...
Click to collapse
That annoyed me about GB (stock and CleanROM 1.7.5). Even on ICS, Facebook scrolling is choppy, unless you enable Force GPU rendering. Running ICS with Force GPU rendering is an incredibly smooth experience, and I haven't run into any bugs. I'm surprised it's not enabled by default in all ROMs.
I think that people having a better experience on a hacked(nicely mind you), sense 4.0 rom must have set up Gingerbread wrong. See how easy it is to make a statement like that. I have experienced both ics, and gb, and have always had a smoother experience on gb. I hated how ics scrolling in the browser, xda app, tapatalk, and others was jittery at best. I love some of the elements of ics, but the trade off was too much for me. My phone ran about 11 degrees different between ics, and gb. Also, if you go back to around Christmas, overheating was an issue then. On stock. So apparently, this phone can have heat issues. Don't get me wrong, I love this phone, and I appreciate all the work that goes into making roms. I have been following these developers for quite a while. They are all really good. We are blessed to have them.
Sent from my ADR6425LVW using XDA
destro158 said:
That annoyed me about GB (stock and CleanROM 1.7.5). Even on ICS, Facebook scrolling is choppy, unless you enable Force GPU rendering. Running ICS with Force GPU rendering is an incredibly smooth experience, and I haven't run into any bugs. I'm surprised it's not enabled by default in all ROMs.
Click to expand...
Click to collapse
So it is the GPU that's the problem as I thought.... But thankfully it isnt because its not good enough. Lol. It's just because its more limited c
This is my fifth prime bought the first when it was first released and bought and sold a few more since then I picked one up a few days ago for a crazy price i am now running virtuous prime and performance mode at 1.8 ghz and my galaxy note is still much faster with everything i don't understand this, i think the prime is the best 10 inch tablet i guess i just thought it would be faster when overclocked with a custom rom
for starters wrong section, should've been in QnA section. Second, you could've just posted that in one of the many existing complaint threads.
Not complaining just wondering why and how to make the prime faster
golfinggino said:
Not complaining just wondering why and how to make the prime faster
Click to expand...
Click to collapse
if you running a custom rom and overclocked it should easily run faster than what you claim. you must not of did something right. I'm stock, rooted, and overclocked n my prime runs circles around my Ipad n phone.
try a different rom and make sure its flashed correctly. virtuous is more of a stock base rom built for stability. you want performance, use AOKP or WSG rom or maybe even new gummy one. lots of different roms to try out. even still, virtuous overclocked should be running great.
OK thanks I will try another room btw my note is rooted running rocket rom lpy so it is not not stock, but it is faster then my current set up on my prime but i will take your advice and try another room thanks
Also remember that different chip setups use different speed tweaks. Are you running a third-party launcher? Any monitoring apps? What kind of widgets? What background services are running? I had virtuous with OC and it was great, but I changed to AOKP with OC and is much faster running the same apps.
Sent from my ADR6425LVW using xda premium
golfinggino said:
This is my fifth prime bought the first when it was first released and bought and sold a few more since then I picked one up a few days ago for a crazy price i am now running virtuous prime and performance mode at 1.8 ghz and my galaxy note is still much faster with everything i don't understand this, i think the prime is the best 10 inch tablet i guess i just thought it would be faster when overclocked with a custom rom
Click to expand...
Click to collapse
Im runnin a custom ICS Rom on my Galaxy S2...Its overclocked at 1.5...And its pretty damn close side by side when I bring up stuff...I too am runnin the Gummy on performance 1.8...But its fast enuff for me...
And I just luv the view of a 10.1 compared to my 4.6 screen on the Epic 4 Touch...
why is my honda civic faster than a 18 wheeler? the 18 wheeler has a much larger engine and a lot more power!
The prime easialy outpowers the note however other things have to come into consideration: What kernel / rom is running on both devices, what device specific optimizations have been made for the specific hardware. What different chipsets, GPU's, screen resolutions, animations, versions of android, etc are there?
There are so many problems with this thread i dont even know where to start. As far as tablets go, the prime has the best HARDWARE. This does not mean, by default, the software will run faster. The same way that 18 wheeler has a much larger and more powerfull engine does not mean it will go faster than my honda civic with its 4 cylinder engine.
My suggestion is go on google and do some research on how android actually works. Learn about the hardware you complain about and maybe you might learn your answer for yourself.
Both are running ics 4.0.3. Both are running adw ex launcher and the same apps don't get me wrong the prime is great I am just surprised that my note loads webpages twice as fast on the same wifi network even on demand at 1400 MHz on the note vs 1800mhz performance on the prime - anyway I was just curious no big deal
lol im not surprised, wifi on the tablet sucks. try loading up some graphic intense games and see which has the fastest loading times. Its no secret the primes wifi sucks try a test that compares other things like the GPU or CPU.
And even if both devices have android 4.0.3 unless its stock google 4.0.3 they have been tweaked in one way or another. load AOSP on each and give er another shot.
just loaded up the gummy v1.2.3 and now it is as about as fast as my note on the internet - of course the prime has more power and gpu but i was more concerned with everyday apps like internet, etc. i currently dont play any games on the prime
i think i wil put an aosp rom on the note and see how it compares - thanks to everyone for their advice
btw i picked up this prime to test out the unlocked bootloader / customs roms, it was pretty scratched up when i bought it used but i put on a zagg screen protector and it covers up all the scratches on the screen and then i bought a nice leather case as well not bad for $100 total !!
**DISCLAIMERS**
This thread has no intention of attempting to complain, diminish, degrade, or criticize any developers on this forum or any of their work, as all of us are nothing but grateful for the amount of free, altruistic, and superior quality code that they provide us with. :good:
This thread has no intention of trying to reiterate the content of the "Butery Smoothness" thread found at http://forum.xda-developers.com/showthread.php?t=1814010 nor to define what "Buttery Smoothness" is, as the previous thread defines it well enough already through the posts and insight of multiple users.
This thread has been created with full knowledge and consideration of the alpha development stage that Android 4.1.1 is currently in and all content discussed in this thread is stated with regard to said knowledge and should only be perceived as an attempt to contribute to at least one of multiple bug fixes to further improve the state of Android 4.1.1 on the SGH-i717 for the good of all users
Purpose
The purpose of this thread is to solve the perceived lack of graphical smoothness and fluidity inside of Android 4.1.1 (Jelly Bean) on the SGH-i717 which has been noticed and reported by many users in multiple ROM's through the collaboration of information, ideas, and solutions between all users and developers.
Background
Many users have reported a significant lack of graphical performance in multiple Jelly Bean ROM's for the SGH-i717 in various scenarios such as home screen navigation, UI animations, and in-app scrolling where there is not only a user-noticeable drop in performance but a quantifiable drop in frame-rate. With Google's Project Butter being a highlight of Jelly Bean, the lack of smoothness in its current state for our device brings not only dismay but logical confusion as other, older devices with lower specifications (such as the Galaxy Nexus for example) perform better graphically than the SGH-i717 with higher specifications. The higher graphical performance in the older Ice Cream Sandwich indicates that the highlighted performance issue in Jelly Bean is not related to hardware incapability but to software utilization of the hardware.
I want to leave as little of my insight in this thread as possible because I want to hear from other users but I'll post some initial information and questions to provoke some response.
Ever since Jelly Bean development began, I've noticed this issue on my device and have even had a replacement device with the same experience so hardware isn't a likely culprit in my opinion. h0tw1r3 was one of the first developers to bring a Jelly Bean ROM to SGH-i717 users and other ROM's were formed briefly after his using it as a base. Until about the third or fourth build ( 8-21 I believe), the performance was sluggishly the same. After this build though, there was a noticeable increase in graphical performance, although still significantly behind ICS. That new standard hasn't changed much since until the latest CM10 nightly builds where I've noticed quite an increase in graphical performance putting it a little closer to ICS performance but still painfully behind such that Dolphin is the only browser that feels smooth enough to use efficiently.
I have also noticed an odd phenomenon where the performance varies from build to build without a noticeably significant change. For example, I remember using DaGr8's AOKP port for a while and finding it smoother than other ROM's at the time but once installing his next build (that only mentioned minor unrelated changes, although some could have been unlisted) the performance was back down again. I have experienced this with multiple different ROM's though which is what is most peculiar that there is so much inconsistency.
Helpful Questions
Have you noticed any of these issues before? If so, which ones?
Do you think the issue is hardware or software/driver related?
How would you compare your best JB experience to stable ICS builds?
Which processes/applications perform the best and the worst for you graphically?
Which ROM's run smooth for you and which ones don't?
Which browsers have you tried in Jelly Bean and which ones do you prefer the most?
Have you noticed graphical performance issues in Chrome consistently at all? If so, in which ROM's or instances have you experienced such?
Do you have any ideas/suggestions as to what is causing or what could fix this issue?
And regardless of the inevitable bugs we are experiencing in alpha software, are you extremely grateful for the developers who have provided us with them? (SAY YES!!)
If any of you would like to add more content or questions to this list (and PLEASE do), just ask them and I'll add them to this OP.
Suggestions and Modifications for Improvement (list will grow over time as new information is presented)
1) Verify that the "debug.mdpcomp.maxlayer" parameter in build.prop is set to the value of 3 and not 2 when you first install a ROM (thanks to NYConex for the tip!). Some developers/ROM chefs (lol) will customize this setting based on their preference. This setting disables (value 2) and enables (value 3) GPU acceleration taking the load off of the CPU. Disabling has fixed the flicker issue that has developed in Jelly Bean for many people but will severely impact performance and graphical smoothness as well as battery life potentially. For flickering, I instead recommend using a live wallpaper which will force the GPU to refresh the screen much more often disabling flicker (in the homescreen at least).
2)**ESSENTIAL FIX FOR SIGNIFICANT IMPROVEMENT** Change the debug.composition.type in /system/build.prop from "dyn" to "gpu" and reboot. This makes a MAJOR difference in ALL areas of performance. The existing string that is entered by default is a "dynamic" setting which alternates putting the graphical load on either the GPU or CPU depending upon resource allocation. Changing the setting to "gpu" will force Android to constantly use the GPU for graphics so you won't notice stutter and lag as Android switches the load from the CPU and GPU. Using this setting also increases overall system speed IMMENSELY as it allows the CPU to do more central tasks like launching applications and communicating with hardware instead of handling the graphics. This "constant GPU setting" plays very nicely with Project Butter in the sense that it uses a constant component of hardware to render graphics along with the constant frame rate that VSync provides. I may try to learn how to make my first ROM sometime soon and when I do, I'll be sure and integrate this into the ROM. Either thank the post or let everyone know if this has helped you!
I have noticed that the liquid ROM as well as the most recent nightly (2 SEP) have been pretty smooth. Nova launcher works great and I don't really see a lot of lag outside the launchers. One thing that kinda brothers me is the lag that is introduced when you enable the nav bar. I don't know exactly what happens behind the scenes (other than it disable the hw keys and enables the soft keys) but it adds a lot of lag. Is there a way to monitor exactly what happens when doing things to your phone? When I use liquid it changes without a reboot but with cm10 I have to manually disable the hw keys so it requires a reboot. Anyone know what's going on with it?
NYConex said:
I have noticed that the liquid ROM as well as the most recent nightly (2 SEP) have been pretty smooth. Nova launcher works great and I don't really see a lot of lag outside the launchers. One thing that kinda brothers me is the lag that is introduced when you enable the nav bar. I don't know exactly what happens behind the scenes (other than it disable the hw keys and enables the soft keys) but it adds a lot of lag. Is there a way to monitor exactly what happens when doing things to your phone? When I use liquid it changes without a reboot but with cm10 I have to manually disable the hw keys so it requires a reboot. Anyone know what's going on with it?
Click to expand...
Click to collapse
Good question. I know there are settings in Developer options that allow you to show GPU status and updates which may provide some insight into GPU/CPU utilization. I don't have an immediate answer for you though. I'll do some research and report back.
With the Liquid ROM, I noticed it to be of the poorest performance as others. Was your experience smooth out of the box or did you have to change the debug.mdcomp.maxlayer from 2 back to 3 first?
**EDIT**
I just tried the Liquid ROM again and realized the debug.mdpcomp.maxlayer setting was set to 2 by default in that ROM and after the changing it, the performance was much better, though about the same as CM10 nightlies.
The mdcomp.maxlayer is always the first thing I check after flashing a ROM. I always set it to 3. But if you go back to liquid try the navbar and you will see what I mean. In not home right now but when I get back I'll mess with it a little.
I'm on the Liquid ROM and I don't notice any lag. So i don't think anything needs fixed...since I dont have the problems u describe.
I use almost all aspects of the Note except little music and games.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Try pulling down the notification drawer. Now sit there and tell me to my face its 60fps. No its not... its really choppy.
Fasty12 said:
Try pulling down the notification drawer. Now sit there and tell me to my face its 60fps. No its not... its really choppy.
Click to expand...
Click to collapse
Lol damn right. I'd say its between 14-21 FPS variably.
Which ROM's have worked the best for you so far?
On mobile, had 2 scroll forever to read topic
SayWhat10 said:
On mobile, had 2 scroll forever to read topic
Click to expand...
Click to collapse
Are you saying that my OP is too long which made you scroll forever or are you saying that the lag in Jelly Bean cause you to scroll forever?
andrawer said:
I'm on the Liquid ROM and I don't notice any lag. So i don't think anything needs fixed...since I dont have the problems u describe.
I use almost all aspects of the Note except little music and games.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
Do you use Google Chrome? If so, how would you describe its performance in comparison to Ice Cream Sandwich?
The CM10 nightly has been the smoothest this far. So going by experience heres the rankings ATM.
1) Nightly... Smooth but constant flicker.
2) Liquid
2) Paranoid
3) Aokp
4) manualscout4life's rom.
Fasty12 said:
Try pulling down the notification drawer. Now sit there and tell me to my face its 60fps. No its not... its really choppy.
Click to expand...
Click to collapse
not sure if i understand.
I use my thumb to initiate the notification bar/drawer pulling down and it's immediate and smooth?? Up/down/up/down/up/down...smooth...just tried it. Not even a hint of lag...and that's with 4 notifications waiting for me to do something.
The mentioned lag on jellybean compared to anything previous doesn't come from anything done by Google or issues with software but comes from the lack of hardware acceleration which we don't get to use with jellybean, so our device is not being used to the fullest, is known like previous versions of android when it comes out and ported , is not going to performed like it's supposed to until HWA becomes available. This is the performance drop in fps compared to ICS. Some think because is a newer version of android is going to be better performing out of the box, but that won't happen unless an official version with HWA becomes available or a developer figures out how to implement it into a ROM.
I think JB is amazing and smooth in the little time it has been out.
RoloRacer Paranoid on JellyBean
I agree about the sluggishness of JB at its current state, its normal since we don't have HW acceleration, I'm on Paranoid and flashed Flaps Hot kernel, OC'ed to 1.7Ghz and its performing really well, you should try it out
Sent from my Nexus 7 using xda premium
egomezmorales said:
I agree about the sluggishness of JB at its current state, its normal since we don't have HW acceleration, I'm on Paranoid and flashed Flaps Hot kernel, OC'ed to 1.7Ghz and its performing really well, you should try it out
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
So when will we get hardware acceleration? When jb officially comes out for the note?
roloracer said:
The mentioned lag on jellybean compared to anything previous doesn't come from anything done by Google or issues with software but comes from the lack of hardware acceleration which we don't get to use with jellybean, so our device is not being used to the fullest, is known like previous versions of android when it comes out and ported , is not going to performed like it's supposed to until HWA becomes available. This is the performance drop in fps compared to ICS. Some think because is a newer version of android is going to be better performing out of the box, but that won't happen unless an official version with HWA becomes available or a developer figures out how to implement it into a ROM.
I think JB is amazing and smooth in the little time it has been out.
RoloRacer Paranoid on JellyBean
Click to expand...
Click to collapse
This has been my thought and awareness all along and what I've wanted to work on repairing. Perhaps it's everyone's use of the term "smooth" that is making everything amiss. When people boast that their JB experiences are "incredibly smooth!" and even more specifically "smoother than ICS!" I think they are making very fallible statements because I don't think that my perception of JB being behind ICS in smoothness can be interpreted as just a "difference in opinion or interpretation". It's definitely factual and quantifiable when testing frame rates and comparing them to ICS. Perhaps it's safe to say that "Jelly Bean is remarkably usable right now considering its alpha state", but to say that it is smooth is quite a fallacy. It's really not much better than Gingerbread and Gingerbread lacked HW acceleration altogether.
But if JB lacks hardware acceleration completely, then how is toggling the maxlayer setting and HW overlay setting in developer options clearly affecting performance if HW acceleration isn't even supported at all in the first place? Some sort of acceleration is clearly being enabled for the evident difference in performance to occur.
I am grateful that you recognize JB's current state to be behind and also attribute it to HW acceleration as I initially did. Now we can hopefully gain some momentum on finding the hindrance of bringing HW acceleration to JB!
If there's anything we've learned thus far, it's not to label a ROM officially "smooth" unless you can prove it greater than or equal to stable ICS builds with quantifiable means!
The word "smooth" is beginning to become a profanity for me, which is rather extreme, as there aren't many words I don't say! Lol...
Everyone should read this.
http://www.androidpolice.com/2012/0...roject-butter-how-it-works-and-what-it-added/
Jb runs exceptionally well for me with just the 2 buffers. Are all the animations perfect every single time? No, but it's perfectly usable, and slick enough for my dd. I'm sure it will be sorted in time.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
So far the smoothest jb rom for me has been dagr8's aokp Sept 1 build.
HW overlays are disabled and cpu at stock frequencies. Running Nova 1.2.2 and have fluid home screen transitions and overall smoothness.
If I were to nitpick, the notification bar is the only thing that seems somewhat sluggish but only when I pull it down on the home screen (I am running a live wallpaper.)
No reboots or sleep of deaths so far, loving this rom at the moment.
yollasho said:
Everyone should read this.
http://www.androidpolice.com/2012/0...roject-butter-how-it-works-and-what-it-added/
Jb runs exceptionally well for me with just the 2 buffers. Are all the animations perfect every single time? No, but it's perfectly usable, and slick enough for my dd. I'm sure it will be sorted in time.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
Really interesting read, thanks for sharing!
Sent from my Nexus 7 using xda premium
---------- Post added at 01:04 PM ---------- Previous post was at 01:04 PM ----------
Fasty12 said:
So when will we get hardware acceleration? When jb officially comes out for the note?
Click to expand...
Click to collapse
Yep, or that a developer taps on how to get HW acceleration
Sent from my Nexus 7 using xda premium
We've had hardware acceleration.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app