Related
It will be possible?
well froyo is doing some problems to the devs.. i think it would be better to get froyo working since gingerbread will take 4 months
NO!
Minimum hardware requirements for Android 3.0 devices are: 1GHZ CPU, 512MB or RAM, displays from 3.5” and higher. (source)
beat me to it.
yea, considering the minimum system requirements for 3.0 I would have to say no. most Hero users cant even overclock past 695MHz so its a no go.
From what Im reading, theyre killing all custom UI with it too. no more Sense, no more Motoblur, no more nothing. just the new stock google UI that theyre working on.
I kinda see it as a good thing. the one problem with Android phones has been that the customization has been too vast. there needs to be more industry standards just like the iphone or we're going to run into phone wars that dont just involve iphone vs android.
I don't think that we won't be able to get Sense etc because that is the beauty of Android,freedom and customization.If we lose a little of both then...I don't know,I just don't want it to turn iPhoney!I think that they only will give a standard UI for apps so that we avoid the current situation,which is that every app has its own UI and there is no consistency.My opinion though...
If the minimum spec is 1Ghz for gingerbread, then all that news about fragmentation that google going on about is a load of rubbish!
I guess it will soon be the end of the road for the htc hero!
tweedie said:
If the minimum spec is 1Ghz for gingerbread, then all that news about fragmentation that google going on about is a load of rubbish!
I guess it will soon be the end of the road for the htc hero!
Click to expand...
Click to collapse
We will first starve to death and then google might face problems!Anyway...Microsoft gave similar specs for WP7 but I've already seen a ported version running on the Diamond!What I've learned here in XDA-Devs is that we can never say never!My opinion?We will see Gingerbread on the Hero but it will never run well or smooth enough...Unless we can change its chipset!
Sent from my HTC Hero using XDA App
Wouldn't the absence of 'HTC Sense' allow JIT to play an even greater role in boosting performance?
Re: Froyo
There's also a Dalvik JIT compiler that improves overall CPU-bound code performance by two to five times compared to version 2.1.
Click to expand...
Click to collapse
lost101 said:
Wouldn't the absence of 'HTC Sense' allow JIT to play an even greater role in boosting performance?
Re: Froyo
Click to expand...
Click to collapse
Nah...I'm sure they can develop some kind of patch to enable JIT with Sense like the ones here on XDA(right now I can remember Feeyo's and Villain's ones).
Will it be hard...
Hell yeah!!!!
But it isn't impossible just today some developers made ubuntu and Android 2.1 on HTC HD2
tolis626 said:
Nah...I'm sure they can develop some kind of patch to enable JIT with Sense like the ones here on XDA(right now I can remember Feeyo's and Villain's ones).
Click to expand...
Click to collapse
My point was that 'Sense' doesn't seem to benefit from JIT, and that 3.0 will have a superior UI making it unnecessary anyway. If the new UI isn't incredibly demanding (the reason for the 1ghz requirement cited?) and benefits from JIT, chances are that Hero can handle it.
Android 3.0 will also have a completely refreshed user interface. According to UnwiredView, the new UI will resemble the Cooliris-made photo gallery application that's on the Nexus One. It will feature animated transitions between apps and screens.
Google has hired Palm's former webOS user interface designer, Matias Duarte. His new position at Google is with the Android user experience team.
Click to expand...
Click to collapse
h**p://tinyurl.com/39s9e3a
I've heard/read that ONLY honeycomb makes use of the dual core.
So what's the advantage of having a dual core phone running gingerbread?
Nvm I found some information.
Sry for makimg a new useless topic
Where did you find the information?
Please post the Link!
All of the information I've read shows that Ice Cream should be the build with this integrated.
It's somewhat baffling that it's taken this long considering that for the average phone user, how smooth the phone is plays a huge part in whether they like it or not.
iOS has had GPU UI acceleration since its inception, how have the Android team members let this slide? Is it simply because the implementation requires a massive structural re-write?
Tossing the 2D UI acceleration over to the GPU should theoretically increase the speed of the OS as well, since it frees up the CPU to focus on its own tasks.
MustWarnothers said:
iOS has had GPU UI acceleration since its inception, how have the Android team members let this slide? Is it simply because the implementation requires a massive structural re-write?
Tossing the 2D UI acceleration over to the GPU should theoretically increase the speed of the OS as well, since it frees up the CPU to focus on its own tasks.
Click to expand...
Click to collapse
Caching is primarily what makes it so smooth on the iPhone, not GPU acceleration; though that helps a fair amount, also. The lack of heavy use of caching everything in the UI for what seems like all Android UIs is what has baffled me about Android UIs. Home screen launcher replacements like LauncherPro use it, and it makes everything nice and silky smooth. I've honestly been thinking that most UI designers for the hardware companies simply do not know what they are doing.
MustWarnothers said:
All of the information I've read shows that Ice Cream should be the build with this integrated.
It's somewhat baffling that it's taken this long considering that for the average phone user, how smooth the phone is plays a huge part in whether they like it or not.
iOS has had GPU UI acceleration since its inception, how have the Android team members let this slide? Is it simply because the implementation requires a massive structural re-write?
Tossing the 2D UI acceleration over to the GPU should theoretically increase the speed of the OS as well, since it frees up the CPU to focus on its own tasks.
Click to expand...
Click to collapse
it's not that simple...ios is missing a lot of features. i read that it doesn't support java and just object-oriented C++.
Since android was started, phone developers have pushed it in directions that Google didn't originally plan for. That's why the nexus s only had single core, and afaik, all the dual core phones have software on top of android to manage the dual core processing, which doesn't really do much for them. yes they're faster, but i think not as fast as they could/should be.
i'm assuming the next nexus will be a dual core, and with android that has support for them. if so, it'd blow all dual cores away to this point, because processor management is more efficient the lower in the stack it's handled.
however, what with the nexus s 4g being recently released, i'm not expecting the next nexus to be around anytime soon as G focus on tablets.
Since the SGS2 is so fast for web browsing and flash content, as well as UI, what type of magic do they do if they aren't altering the basic Android system? Does it involve using dual-core? How specific are the Samsung optimizations and are they low-level enough for Google to say this would be great in Ice Cream and thus steal that optimization from them? Is TouchWiz actually faster than stock Android? Or is that impossible since it is built on top of Android? Will the browser speed translate to other installed browsers, or is it specific to the stock browser? I really don't know how far Samsung or any other manufacturer can customize the software beyond just superficial skins and whether or not deep customizations change the system fundamentally and possibly break certain apps.
I didn't really investigate this issue deeply, but I think it works out like this:
Right now, the android sdk (2.3) provides no means to use more than one CPU core.
Still, multicore CPUs will increase performance because background processes can use CPU time on the core not being used by the running app.
This also applies to garbage collection (GC) which happens periodically (I guess you can trigger it manually too) whilst an app is running. With more than one core, the GC won't block the app which makes it feel "smoother".
I remember reading about Google's plans to improve multicore-support in android 2.4. It will take some time for existing apps to use it though (like it's happened with desktop applications).
Then just imagine the performance of the SGS II device with hardware acceleration support.
MustWarnothers said:
All of the information I've read shows that Ice Cream should be the build with this integrated.
It's somewhat baffling that it's taken this long considering that for the average phone user, how smooth the phone is plays a huge part in whether they like it or not.
iOS has had GPU UI acceleration since its inception, how have the Android team members let this slide? Is it simply because the implementation requires a massive structural re-write?
Click to expand...
Click to collapse
Since Honeycomb utilizes GPU for UI rendering, I guess it will be available on Ice Cream too.
Android is handicapped by the big range of hardware used by manufacturers. Some GPUs are simply too slow or have other issues which will make GPU acceleration fail. This is not an issue for Apple, because there is no hardware choice on iOS.
silverwolf0 said:
Since the SGS2 is so fast for web browsing and flash content, as well as UI, what type of magic do they do if they aren't altering the basic Android system? Does it involve using dual-core? How specific are the Samsung optimizations and are they low-level enough for Google to say this would be great in Ice Cream and thus steal that optimization from them? Is TouchWiz actually faster than stock Android? Or is that impossible since it is built on top of Android? Will the browser speed translate to other installed browsers, or is it specific to the stock browser? I really don't know how far Samsung or any other manufacturer can customize the software beyond just superficial skins and whether or not deep customizations change the system fundamentally and possibly break certain apps.
Click to expand...
Click to collapse
All parts of android (2.3) are open sourced, so Samsung can customize anything they want. They don't have to release the changed version as open source though (except for the GPLed parts, like the kernel) - so we'll probably never know what they've been doing.
german wikipedia says that gingerbread 2.3.3 features dual-core support ...
Link it please, thats odd.
My German is bad as I only read it for a couple of year but here is the Wikipedia page http://de.wikipedia.org/wiki/Android_(Betriebssystem)
At the bottom you have "Dual-Core-Unterstützung" on 2.3.3 which means it support it.
But as always Wikipedia is never 100% correct so who know
I read that they will re-release a gingerbread version (2.4?) that will take advantage of Dual-core apps. So basically, they add dual-core support and it will also still be gingerbread but version 2.4 of android.
Come to think of it, they did the same thing with Eclair (2.0 and 2.1) already.
Hope this helps
I think they have already done that with "Gingerbread 2.3.3", Instead of calling v 2.4 GINGERBREAD as well, they made the changes in "Gingerbread" and gave it versioning 2.3.3.
Thats what it looks like all on Wikipedia pages. Highlights 2.3.3 as a Major release.
Yes, the wiki says that dual-cores are supported from 2.3.3 and it says too that dual-core-apps are supported on single-core smartphones! --> Thats an indication for real dual-core support!
I'm just waiting for when Android decides to implement GPU UI acceleration.
Even if apps are offered dual core support, if both of those cores are still working on UI animations instead of tossing it to the GPU, it seems like 3 steps forward, 2 steps back.
As I understand it, Gingerbread (2.3) offers limited dual-core support. If your phone has a 2nd core available, then it will move the Garbage Collector onto the 2nd core which means there will be a lot less lag in applications and games when the GC fires off to remove unused resources.
http:/ /developer.android.com/sdk/android-2.3-highlights.html
It's under the 'enhancements to games' section I believe.
Honeycomb (3.0) offers full UI hardware acceleration and makes full use of both cores - so wait for Ice Cream to come to phones and it will be fully supported.
I know that wikipedia isnt always right but if i assume that it is right this time it says that what you just wrote Xailter was integrated in 2.3 and real dual-core support in 2.3.3 :
2.3 features:
Linux-Kernel 2.6.35.7
Unterstützung von WebM
Unterstützung von HTML5 Audio [31]
Unterstützung von Google TV
Unterstützung von Near Field Communication
Parallele Garbage Collection für ruckelfreiere Animationen
verbesserte Integration von sozialen Netzwerken
Unterstützung von Gyroskopen (nicht zu verwechseln mit Bewegungssensoren) und anderen Sensoren (u.a. Barometer, Schwerkraftsensor)[32]
Integrierter SIP-Client für VoIP[33]
Integrierter Downloadmanager[33]
Unterstützung des Ext4-Dateisystems[34]
translated something like "parallel garbage collection for smoother animations"
while 2.3.3 features:
Dual-Core-Unterstützung
Unterstützung von Dual-Core-Apps auf Single-Core-Geräten
verbesserte Unterstützung der NFC-Technik
verbesserte Bluetooth-Unterstützung
kleinere Verbesserungen
which means dual-core support
support for dual-core apps on single-core-devices
improved support of nfc
improved support for bluetooth
minor improvements
if we can believe in what wikipedia says ... 2.3.3 features dual-core support
and i think it is true because it would just make sense to support the hardware that is releasing right now
source: de. wikipedia. org/wiki/Android_%28Betriebssystem%29#Versionsverlauf
sry for the spaces .. but i'm not allowed to post outside links
to the os, browsing and whatever? i don't know much about hardware acceleration but the little i do know methinks the gpu can be tapped more for less cycles on the cpu and less hit on the battery.
I'm not sure, but if it happens, it will be in a custom ROM.
Samsung seems to be doing it on their browsers.
e.g. on my galaxy tab (original 7"), the stock browser FLIES, obviously HW accelerated. Its magnitudes faster than dolphin on the same device, in fact its within touching distance of ipad1 speeds.
i know samsung took it upon themselves to make sure it was there. i'm just wondering if it can be tapped on tegra2's. i'm also think i'm seeing why gsII is a battery hog. the maii-400 gpu is 65nm. that's huge for a mobile phone.
Hardware acceleration really has to be done by the manufacturer. No android phones are hardware accelerated except for the Samsung galaxy phones cause they do a custom job. Ice cream sandwich is when hardware acceleration comes to android.
pukemon said:
i know samsung took it upon themselves to make sure it was there. i'm just wondering if it can be tapped on tegra2's. i'm also think i'm seeing why gsII is a battery hog. the maii-400 gpu is 65nm. that's huge for a mobile phone.
Click to expand...
Click to collapse
Great point I didn't know this till you said it.
I thought it worth opening a discussion on the recent Google engineer's Google+ post on how ICS handles hardware acceleration vs. Honeycomb. That is to say, it doesn't offer "more" hardware acceleration at all.
https://plus.google.com/105051985738280261832/posts/2FXDCz8x93s
Not to say that ICS won't be more highly optimized nor that it might not have better multi-core support (I have no idea if it does or doesn't), but it's not going to offer magically better hardware acceleration than Honeycomb.
Thoughts?
That was an interesting read when I saw it earlier, yes. I can't really say what the consequences of it are, as I haven't used Honeycomb. At least we can take from it that, as Tegra 3 has the most powerful GPU on any Android device, it has the most potential to be the smoothest in operation?
Mithent said:
That was an interesting read when I saw it earlier, yes. I can't really say what the consequences of it are, as I haven't used Honeycomb. At least we can take from it that, as Tegra 3 has the most powerful GPU on any Android device, it has the most potential to be the smoothest in operation?
Click to expand...
Click to collapse
Unlikely.
When it comes to hardware acceleration and multi-core support, then Android 4.0 is pretty much the same as Honeycomb. My only hope is that the UI of Android 4.0 is better, as it is not very laggy on my Galaxy Nexus.
Multi-core will play more role when there are a lot of parallel tasks, it might affect some games, but overall, while it will be the best Android tablet yet, it won't be the best tablet ever. For that we still have to wait at least a year or more.
so they're saying it's just their piss poor optimization for ANYTHING that makes dual core devices with 1GB of ram run like crap on their OS.
dissapointing.
kristovaher said:
Unlikely.
When it comes to hardware acceleration and multi-core support, then Android 4.0 is pretty much the same as Honeycomb. My only hope is that the UI of Android 4.0 is better, as it is not very laggy on my Galaxy Nexus.
Multi-core will play more role when there are a lot of parallel tasks, it might affect some games, but overall, while it will be the best Android tablet yet, it won't be the best tablet ever. For that we still have to wait at least a year or more.
Click to expand...
Click to collapse
It's...a paradox!
Optimization is the name of the game. ICS will help the Tegra 2 tabs, but i suspect it will have an even greater impact on the prime.
kristovaher said:
When it comes to hardware acceleration and multi-core support, then Android 4.0 is pretty much the same as Honeycomb.
Click to expand...
Click to collapse
Indeed. I was really referring to this in the linked article:
As device screen resolution goes up, achieving a 60fps UI is closely related to GPU speed and especially the GPU’s memory bus bandwidth.
Click to expand...
Click to collapse
I think the reality is ...
Google screwed the pooch when it came to having non-native apps (aka framework based) be accelerated *efficiently* in pre-3.0 days. Some operations did go to the GPU then, but the fact was some sub-view getting invalidated caused much more rendering than was needed.
In 3.x they added an option to have apps say "please accelerate me", but that option is an "opt-in". That choice was done for back-compatibility (not *every* operation in the framework is allowed to be accelerated which means some apps could break).
In reality, most of the "OS" level apps did an opt-in, but not everything. I also doubt general "market" apps do the opt-in (unless they are 3.x+ only).
In 4.x, it's going to be an "opt-out" strategy. So, if an app is broken in ICS, then the developer needs to update/fix their code (IFF necessary, since most are likely to "just work").
kristovaher said:
Unlikely.
When it comes to hardware acceleration and multi-core support, then Android 4.0 is pretty much the same as Honeycomb. My only hope is that the UI of Android 4.0 is better, as it is not very laggy on my Galaxy Nexus.
Multi-core will play more role when there are a lot of parallel tasks, it might affect some games, but overall, while it will be the best Android tablet yet, it won't be the best tablet ever. For that we still have to wait at least a year or more.
Click to expand...
Click to collapse
From what I understand, Honeycomb offers dual-core support. ICS offers greater support than only dual-core.
While that whole read was a little bit disappointing, I am still convinced that ICS overall has been cleaned up compared to Honeycomb/Gingerbread and will make better use of the exceptional hardware of Android devices. The Verge gave ICS an absolutely glowing review in their review of the Galaxy Nexus (they notably said that it was the single greatest leap in the Android OS), and for my particular phone (HTC Sensation), the people who have tried a pre-alpha build of ICS have said that it's already a good deal smoother than Gingerbread ROMs, and of course they aren't even using fully fleshed out builds of ICS.
Whether or not ICS offers things a lot of people have been talking about like greater hardware acceleration, I don't care. As long as it's smoother and can finally hold up a torch to the speed of iOS, that's all that matters. I couldn't care less about the means to achieve that.
I think the biggest gain tye dev community (and in turn the userbase) is going to get from ics is that they will finally release source for a tablet branch of android.
The Janitor Mop said:
the people who have tried a pre-alpha build of ICS have said that it's already a good deal smoother than Gingerbread ROMs, and of course they aren't even using fully fleshed out builds of ICS.
Click to expand...
Click to collapse
I've no doubt that ICS significantly improves on Gingerbread on phones. The question is, how significant will the improvement be from Honeycomb on tablets?
Not saying either way, just moving the discussion along.
wynand32 said:
I've no doubt that ICS significantly improves on Gingerbread on phones. The question is, how significant will the improvement be from Honeycomb on tablets?
Not saying either way, just moving the discussion along.
Click to expand...
Click to collapse
Of course, there is no way to say for sure. But Gingerbread has dual-core support just like Honeycomb does. Assuming part of the reason these pre-alpha ICS builds for my phone are so fast is better multi-core support, then I would think there's good evidence ICS would also improve multi-core support over Honeycomb. I don't think there's any reason to doubt that ICS will be faster on tablets than Honeycomb was, though I will admit we really do have no way of knowing how much. Ultimately, I say we give up the whole "in theory" game, wait for our TF Prime's to ship, and then update them to ICS once that update becomes available. Considering that Asus promised a before the end of the year update, I'd assume that means mid-January is the latest we get ICS. That's only about 5-6 weeks from now to wait to personally be able to see what ICS can do.
A great reply to the initial post:
https://plus.google.com/100838276097451809262/posts/VDkV9XaJRGS
If you're into this stuff, it's a pretty interesting read.
I'll read it, but he starts by saying that webOS performs without lag. Um, what?
Sent from my SPH-D710 using Tapatalk
Even Nvidia have confirmed already that software will not matter when it comes to the tegra 3 chipset...
It treats all software the same quad core optimized or not. I dont think ICS will improved anything other than maybe anti-piracy. It will also suck down your 1gb ram alot quicker too because it requires more ram to operate than honeycomb.
Here is a video from nvidia showing how the cores work with software, quad core optimized or not.
http://www.hardwareclips.com/video/5447/NVIDIA-Tegra-3-Fifth-Companion-Core
ModestMuse23 said:
A great reply to the initial post:
https://plus.google.com/100838276097451809262/posts/VDkV9XaJRGS
If you're into this stuff, it's a pretty interesting read.
Click to expand...
Click to collapse
wynand32 said:
I'll read it, but he starts by saying that webOS performs without lag. Um, what?
Click to expand...
Click to collapse
Haha! He's mostly right, but as the owner of a TouchPad he probably should have kept WebOS off his list of those that "do it right".
I've made a thread similar to this before but people assured me it was something i was doing wrong but despite trying everything thats been suggested to me nothing seems to work. ive had this ****ty tablet that i paid £400 for about 3 months now and im sick of it. My galaxy siii is as smooth as i can ask for, its perfect. This tablet however is a different story. the scrolling is truely horrid, i mean its so janky and stuttery and even when it dosent stutter the screen has a sort of deforming effect. I feel like either google really need to spend some time optimising this tablet or the hardware just cannot support this screen resolution. I love android and even back on my older phones with ics and froyo i found their scrolling often smoother than this ****TY TABLET. I've tried about 15 roms, 4 kernels and even tried over-clocking to about 2.0ghz, nothing. made a difference. does anyone know if gooogle is optimising this tablet? because if i see no improvements within the next month im selling this piece of junk. I dont understand how a tablet that can maintain 60 fps on a 3D game can't even manage to scroll a webpage or app drawer page without dropping frames and having janky and stuttery scrolling. I am also very sure this isnt a problem with android. as i said my phone i9300 galaxy siii handles scrolling super smooth on stock and cm10.1 so it can't be an android problem.
My main question is; Does anyone else find this tablets scrolling performance to be stuttery and janky? or do i have a dud?
Another thing i would like to say is that, the animations are perfectly smooth and in terms of app open speed and gaming performance this tablet is great. however i tend to use tablets for mostly web browsing and other 2D applications which is something that this tablet cant handle for some reason. (oh btw i have tried about 5 different browsers and i know chrome is utter **** this isnt chrome that im tlaking about)
My N10 is stock and not rooted, the only application that behaves anything like that is Firefox which can be really bad. No other issues like that at all. If your looking to resolve the problem I'd go back to basics. It's much more likely to be a software issue than anything else.
Sent from my Nexus 10 using XDA Premium HD app
Perhaps checking the Force GPU rendering in the developers options will help remedy the issue you are having with scrolling.
I do not have this issue when scrolling through a website =\ I do have Force GPU rendering enabled as well as Disable HW overlays checked.
before I returned my two through the play store I noticed a horrible amount of scroll "waving" while in portrait. If you have it in portrait and scroll up and down really fast you can see it big time. Even on daily normal scrolling I could see it. It really bothered me. Its too many pixles. I'd rather have uniform scrolling then the last line of pixels be a half second late compared to the first line. It's hard to explain but it is very annoying.
1920 X 1200 is probably the sweet spot right now. Anything over that is overkill and the GPU/CPU cant keep up.
Sorry to disappoint you but if you want a silky smooth performance go check out the iPad.
Android is just not made that way, it cannot be. iOS is always running on a device it is perfectly optimized for whereas Android has to run on no less then 4 different CPU manufacturers, not to even mention the differences within that particular chip set, then GPU, ram and screen. There are thousands of configurations Android has to support. That said, having so much support means you support the lowest and the highest of the bunch, offering a sub par experience on both.
You mention your GS3 often, just recall that the N10 is pushing over twice the resolution on a next-gen chip (read: android isn't optimized for it yet). For every 10 images on a web page loading on your GS3 there are 20 in higher resolution. You can see the issue.
Its no different then the age old battle of Winblows vs OSX. OSX is built for one architecture, one series of chips. Windows has to be run on thousands of configurations. A Windows PC will never be as smooth as a OSX device, even though the OSX device may have lower specs. On a OS level thats what you will always battle against. Windows and Android share the same issue. Also that's why Windows Mobile is so buttery, they only support a small chip set base.
Games are a little different, they can neglect the lower rung of devices and shoot for the Tegra or high end Snapdragons and Exynos. Hence why the N10 is so spectacular on this level.
So to sum it all up, if you want smoothness throughout the OS you need full optimization. Android in its base state cannot offer that and unless Android changes it will never. Samsung optimizes its Touchwiz systems to a large extent and that gives better performance. But in the flip side, the time it takes to optimize it is taken by delaying releases and not being current on the builds of Android.
Sent from my Nexus 10 using Tapatalk HD
altimax98 said:
Sorry to disappoint you but if you want a silky smooth performance go check out the iPad.
Android is just not made that way, it cannot be. iOS is always running on a device it is perfectly optimized for whereas Android has to run on no less then 4 different CPU manufacturers, not to even mention the differences within that particular chip set, then GPU, ram and screen. There are thousands of configurations Android has to support. That said, having so much support means you support the lowest and the highest of the bunch, offering a sub par experience on both.
You mention your GS3 often, just recall that the N10 is pushing over twice the resolution on a next-gen chip (read: android isn't optimized for it yet). For every 10 images on a web page loading on your GS3 there are 20 in higher resolution. You can see the issue.
Its no different then the age old battle of Winblows vs OSX. OSX is built for one architecture, one series of chips. Windows has to be run on thousands of configurations. A Windows PC will never be as smooth as a OSX device, even though the OSX device may have lower specs. On a OS level thats what you will always battle against. Windows and Android share the same issue. Also that's why Windows Mobile is so buttery, they only support a small chip set base.
Games are a little different, they can neglect the lower rung of devices and shoot for the Tegra or high end Snapdragons and Exynos. Hence why the N10 is so spectacular on this level.
So to sum it all up, if you want smoothness throughout the OS you need full optimization. Android in its base state cannot offer that and unless Android changes it will never. Samsung optimizes its Touchwiz systems to a large extent and that gives better performance. But in the flip side, the time it takes to optimize it is taken by delaying releases and not being current on the builds of Android.
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
Except I have a Galaxy Note 2 which is just as smooth as my iPad 3 was. This is nowhere close to as smooth as either device.
try the eos rom, i think it smooth, stable.... it also keeps running smooth after days of use.
http://forum.xda-developers.com/showthread.php?t=2178128
also in developer options there are 3 things i change on every rom down to. 5:
window animation scale
transition animation scale
animation duration scale
only web pg that doesnt seem to be smooth is 9 gag.
i keep my browser in desktop mode always.
bummer u have a bad taste from it, i find it to be a great hardware, but i like to tweak on it alot.
You are not the only one, check this video, N10 is not as smooth as the ipad or surface, go to min 5.00 http://www.youtube.com/watch?v=cI53tTXcPY8&feature=youtube_gdata_player
stock and boat browser made things much better for me, never use chrome.
NickTheMajin said:
Except I have a Galaxy Note 2 which is just as smooth as my iPad 3 was. This is nowhere close to as smooth as either device.
Click to expand...
Click to collapse
Again, this is an A15 w/2x the pixels to push
Sent from my Nexus 10 using Tapatalk HD
altimax98 said:
snip
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
That would be an excuse if this tablet wasn't designed by Google. Google was in charge of optimizing. They had to do it.
Sent from my A100 using xda app-developers app
I'm using the Ocean browser and scrolling is very smooth. So, maybe its inefficient apps?
plznote said:
That would be an excuse if this tablet wasn't designed by Google. Google was in charge of optimizing. They had to do it.
Sent from my A100 using xda app-developers app
Click to expand...
Click to collapse
Thaz the thing about software it can always be edited with new optimization and thus improve it. Its still a work in progress. Android always has been
Sent from my Galaxy Nexus
Settings -> developer options -> ( check ) force GPU rendering
Little more batt life drain I think ...
If you want good browsers :
(Smoothest)
Naked browser
AOKP browser
Sent from my Nexus 10 using xda app-developers app
Like every android device out there you just need to tweak the min free values to make it smoother. A good ROM/kernel combo helps too.
Add these lines to an init.d file:
chmod 775 /sys/module/lowmemorykiller/parameters/minfree
chmod 775 /sys/module/lowmemorykiller/parameters/adj
echo "0,1,3,7,11,15" > /sys/module/lowmemorykiller/parameters/adj;
echo "16384,20480,25600,51200,76800,102400" > /sys/module/lowmemorykiller/parameters/minfree;
chmod 644 /sys/module/lowmemorykiller/parameters/adj
chmod 644 /sys/module/lowmemorykiller/parameters/minfree
Where do I find the init.d file?
Sent from my Nexus 10 using xda premium
215alexdx said:
Where do I find the init.d file?
Sent from my Nexus 10 using xda premium
Click to expand...
Click to collapse
System/etc/init.d
Web browsing mostly also, here's...
the steps which have my n10 scrolling smoothly...
1. Start with tablet stock, locked, and setup complete.
2. Unlock and root tablet by preferred method and create nandroid backup. (May require understanding/knowledge of how to get out of bootloop)
3. Go to Play Store and update SuperSu (if required) and install Quick Boot.
4. Install preferred custom Recovery (TWRP is mine)
5. Download preferred custom ROM, gapps ( I prefer a minimum package like Rascarlo's), and kernel. (See mine in signature).
6. Use Quick Boot to boot into recovery, wipe cache, factory reset, then system. I just do...
7. Install ROM, wipe cache and dalvik, install kernel, then gapps. Again, I just do...
8. Reboot system.
9. Set up tablet then go to Play Store and update SuperSu (if needed).
10. Download and install BusyBox.
11. Update, install, and setup required/preferred apps from Play Store (AdAway and Naked Browser required for my tablet!)
12. Go into Settings and clean/disable everything under each setting I don't require or need for my tablet to web browse.
13. Boot into Recovery and "fix permissions".
14. Reboot system, set governor parameters, and enjoy!
This has worked for me without issue, can't/won't guaranty my results for others so use at own risk! :laugh:
My scrolling is good. I'm just on rooted stock 4.2.2. But then again, I may just not be as picky as other people.
Sent from my Nexus 10 using xda app-developers app
No problem here, my Nexus10 is running fast and smooth. CM10.1 no mods, with Dolphin as browser.
Paranoid Android + KToonsez kernel = silky smooth scrolling.
One flick will scroll top to bottom ANY page I have came across and it is VERY smooth.
Try one of the custom roms / kernels for this device and you will change your mind.