Android 4.1 Jelly Bean - Hero, G2 Touch General

Video Preview: http://www.youtube.com/watch?v=iIeFxDfShmY
So ICS on Hero is a reality, despite naysayers. Are there any new features / technical limitations introduced in Jelly Bean that completely rule it out?
The inclusion of Project Butter certainly makes it sound attractive:
Project Butter lets the CPU and graphics run in parallel, rather than crash into each other, and has a big impact on both real and perceived speed: the entire interface runs at 60 frames per second on sufficiently fast hardware. Graphics are now triple-buffered to keep scrolling and transitions humming along, and the processor will swing into full gear the moment you touch the screen to keep input lag to a minimum. - Engadget
Click to expand...
Click to collapse
First up you have improvements across the OS to make sure that the GPU, CPU and display can all work in sync and all at 60fps, which will make everything look just that little bit smoother.
In Android 4.1 Jelly Bean, Google has worked on addressing issues relating to the touch response, improving the way that touches are interpreted, as well as the way in which the power of the device is managed.
When we say power, we mean the CPU rather than battery management. In previous iterations of Android there was the possibility of some lag when the CPU scaled up to perform the tasks requested. In Jelly Bean this response is much faster, reducing possible lag. - Pocket-lint
Click to expand...
Click to collapse
Project Butter Demo: http://www.youtube.com/watch?v=krrLfZjirv8

lost101 said:
http://www.youtube.com/watch?v=iIeFxDfShmY
So ICS on Hero is a reality, despite naysayers. Are there any new features / technical limitations introduced in Jelly Bean that completely rule it out?
The inclusion of Project Butter certainly makes it sound attractive:
http://www.youtube.com/watch?v=krrLfZjirv8
Click to expand...
Click to collapse
Even so, the Project butter is relying on both CPU and GPU. And hero runs CPU as a GPU. Rendering on Hero using GPU is not possible. So project butter will not be applicable on our phone.
Galaxy Nexus has OTA update just today given the fact that the presentation of the Jellybean was made yesterday. I have a One V, and it is possible to run Jellybean on it after someone will port it ofc.

Related

Does 2.2 fully support dual core?

Obviously is does to an extent, but I thought Gingerbread/Honeycomb are the first official OS's to support it?
Anyone know the details around this? When the Atrix gets Gingerbread, will there be processing improvements?
2.3 does... which makes you wonder wtf moto was thinking.
I use SeePU as a CPU monitor and when I swipe the screen and other basic things, the CPU maxes briefly. No lag at all for the most part. However, I'm wondering if Froyo isn't completely optimized for the dual-cores.
As a funny note, I'm wondering if we're all going to see some nice improvements once we get Gingerbread as we did with the 2.1 to 2.2 improvements.
kenyu73 said:
Obviously is does to an extent, but I thought Gingerbread/Honeycomb are the first official OS's to support it?
Anyone know the details around this? When the Atrix gets Gingerbread, will there be processing improvements?
Click to expand...
Click to collapse
Don't believe Froyo was made with dual core in mind. Biggest thing is that apps haven't been optimized for dualcore yet.
kenyu73 said:
Obviously is does to an extent, but I thought Gingerbread/Honeycomb are the first official OS's to support it?
Anyone know the details around this? When the Atrix gets Gingerbread, will there be processing improvements?
Click to expand...
Click to collapse
It seems there is already multi core support on the OS level, but probably not a strong support on the API level. Read, for example, androidnexus [dot] com/android-news/nvidia-tegra-2-review-and-multi-core-support-in-android . That means that the OS will already distribute threads between cores, which for example should eliminate any lag that I sometimes experience in single core when I am playing a game and Android is synching mail in the background. *edit* And generally improve performance while multitasking. *end edit*
I think only Android 3.x will really take advantage of multi core processors (they explicitly stated that as a feature for Honeycomb); I doubt there would be a big difference between Froyo and Gingerbread as far as performance is concerned.
how long do u think Moto will let us update to 2.3? maybe 1 year?
bl0wf1sh said:
It seems there is already multi core support on the OS level, but probably not a strong support on the API level. Read, for example, androidnexus [dot] com/android-news/nvidia-tegra-2-review-and-multi-core-support-in-android . That means that the OS will already distribute threads between cores, which for example should eliminate any lag that I sometimes experience in single core when I am playing a game and Android is synching mail in the background. *edit* And generally improve performance while multitasking. *end edit*
I think only Android 3.x will really take advantage of multi core processors (they explicitly stated that as a feature for Honeycomb); I doubt there would be a big difference between Froyo and Gingerbread as far as performance is concerned.
Click to expand...
Click to collapse
Thanks for the information! However, I believe Gingerbread 2.3 was "canned" and reversioned to 2.4 which includes dual-core support. I've read this in more then a few tech blogs recently.

Ice Cream Sandwich hardware acceleration?

After looking through engadgets live blog there was no mention of hardware acceleration being added to android 4.0. With that being said that was my hopes of 4.0 bringing true smoothness that both ios and WP7 have been having all along. Now i know there is 3d animation ( i may be wrong ) but i know that isn't the full acceleration. Question asked does it have it?
Yes, Android 4.0 features 2D Hardware Acceleration (as originally added in Honeycomb), with some improvements.
Additionally, applications can take advantage of the GPU (Photos, Video & Gallery, for example) for on-the-fly transform effects. For example, if you perform edits in Gallery to a photo, it's actually loaded as a texture in OpenGL, and the "effects", or transforms, are applied leveraging the GPU to vastly improve performance.
Likewise, the panoramic "stitching" is GPU accelerated, and video capture (compression) and streaming (transformations, such as silly faces) are GPU accelerated.
It remains to be seen if the GPU is being used for other aspects of the OS, for example, being leveraged by the browser to assist in webpage rendering, etc. However, even as it is right now, it's a massive step up in quality and performance, and should facilitate wonderful UI/UX experiences for ICS even on older devices, like the Evo, Nexus One, Droid X, etc.
Shidell said:
It remains to be seen if the GPU is being used for other aspects of the OS, for example, being leveraged by the browser to assist in webpage rendering, etc. However, even as it is right now, it's a massive step up in quality and performance, and should facilitate wonderful UI/UX experiences for ICS even on older devices, like the Evo, Nexus One, Droid X, etc.
Click to expand...
Click to collapse
Oh really! Are we to believe that somehow the Evo's GPU will be ICS supported for hardware acceleration? Will that require a HTC-specific ICS update, or is it workable for AOSP before HTC codes in their hardware acceleration?
thegregbradley said:
Oh really! Are we to believe that somehow the Evo's GPU will be ICS supported for hardware acceleration? Will that require a HTC-specific ICS update, or is it workable for AOSP before HTC codes in their hardware acceleration?
Click to expand...
Click to collapse
Well, it isn't really a device-specific feature.
Hardware acceleration in the UI is akin to playing a 2D game, like Angry Birds. The system is actually leveraging OpenGL to handle 'displaying', or 'rendering', the game. Likewise, the UI is 'displayed', or 'rendered', the same way.
The way this relates to Android 4.0 is like this: Hardware acceleration was added to Android in Honeycomb (3.0), and in order to take advantage of it, requires a GPU that is capable of supporting OpenGL 2.0 with drivers that are compatible with OpenGL 2.0. If you have a capable GPU with capable drivers, the OS will use the GPU to render the UI, and voila, hardware acceleration.
If any of those components are not available (or perhaps not working correctly), Android defaults to "software acceleration", which is what has always been present in Android for phones. 1.0 all the way through 2.3.7 all use software acceleration. That is, all of the UI elements are rendered by the CPU.
You've probably experienced lag thanks to this--scroll through your contacts list quickly, flip between full home screens, or load up an intensive Live Wallpaper and open your Launcher and try scrolling--you'll probably find slowdown, if not stuttering in places. This is because the CPU is doing the heavy lifting not only for the OS, but also to render the display.
By alleviating this pressure on the CPU, we free up the phone to do work it's better at handling--running the OS. Additionally, because GPUs are actually designed for rendering, they are far, far more efficient at doing so than the CPU. The result? A massive overhead reduction overall on Android on devices, that means improved performance across the board as well as a much more pleasing user experience.
This is fantastic news for devices new and old; but a real treat for those of us with older phones, as the reduced CPU overhead coupled with GPU acceleration should mean noticeable performance improvements, as well as a drastic reduction in stuttering, lag, jittery-ness in the UI, etc.
Best of all, it should be very simple to implement. Most hardware supports OpenGL 2.0 (our Evos do, for example), and most drivers for that hardware also support OpenGL 2.0 (as our Evos do), so it should really be as easy as building Android 4.0 with the appropriate drivers, and then experience the bliss of a hardware-accelerated Android for the first time.
(Note that this explanation doesn't touch on using the GPU for additional benefit, like editting photos, videos, offloading work from the CPU as I touched on above, etc.)
man that was a bunch of good info i needed +1 will be glad when our evos have that much needed acceleration
Dude Shidell thank you so much for that in depth explanation! You covered everything I could have possibly wondered about, haha. A king amongst men, and a god amongst kings, you are.
Thanks alot shidell that really helps me out alot. I just have one question, did anyone here about usb host, on 4.0?
Sent from my PC36100 using XDA App
BmW13294 said:
Thanks alot shidell that really helps me out alot. I just have one question, did anyone here about usb host, on 4.0?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
yeah i read that the galaxy nexus was having a usb 2.0? i will check some images to see if its true
Naturally, Ice Cream Sandwich is onboard, with Google finally revealing the version number as 4.0. Other specs include an HD Super AMOLED display (1,280 x 720), a 1.2GHz dual-core processor, 5 megapixel rear camera (with LED flash), a 1.3 megapixel front-facing cam, 1080p video recording and playback, a newfangled panorama mode, a 3.5mm headphone jack and Bluetooth 3.0. You'll also find USB 2.0(right there), 802.11a/b/g/n WiFi, an embedded NFC module, accelerometer, compass, gyro, proximity sensor and even a barometer -- yeah, a barometer. Finishing things out, there's 1GB of RAM, 16 or 32GB of internal storage space and a 1,750mAh battery. info gathered from Engadget listing all the galaxy nexus specs
Happy to share information.
BmW13294 said:
Thanks alot shidell that really helps me out alot. I just have one question, did anyone here about usb host, on 4.0?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Yeah, Android 4.0 builds upon the USB Host support that was integrated in Honeycomb, which means it has native support for a variety of USB devices. Granted, I don't know the depth of devices or support, but it is present.
Nice explanation shi.

Galaxy Note ICS Android 4.0 ETA.....Hardware Acceleration

Who knows when Ice Cream Sandwich will be released officially. What I HAVE heard though is that ICS is fully GPU driven by default, so hopefully when it comes out Samsung will not disable the Hardware acceleration due to their Touchwiz deal. As soon as 4.0 is released and is hardware accelerated I am buying the Note.
You could still buy it before that. ;-)
Sent from my GT-N7000 using xda premium
drgopoos said:
You could still buy it before that. ;-)
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
I could, but I won't because I'm selfish and egotistic and want the GPU to drive the entire O/S which, by the way, will save on battery because the CPU will be freed up. Also, the only carrier to have the Note pass through the FCC so far is Att for HSPA+. I'd like to get a full 4g (LTE) version if released.
I have a SGS Epic 4g and my contract is up in June. That will give them time to release 4.0 and for me to see if any other phones release that are close to the power and amazing screen as this one.
ZenInsight said:
I could, but I won't because I'm selfish and egotistic and want the GPU to drive the entire O/S which, by the way, will save on battery because the CPU will be freed up. Also, the only carrier to have the Note pass through the FCC so far is Att for HSPA+. I'd like to get a full 4g (LTE) version if released.
I have a SGS Epic 4g and my contract is up in June. That will give them time to release 4.0 and for me to see if any other phones release that are close to the power and amazing screen as this one.
Click to expand...
Click to collapse
None of the phone or computer can be fully driven by GPU. CPU is the core component of them but not GPU. GPU will certainly improve the 2D/3D display performance but you still need CPU to response most of the other tasks. ICS is not that kind of magic things. It just an twisted Gingerbread man + Honeycomb.
ZenInsight said:
I could, but I won't because I'm selfish and egotistic and want the GPU to drive the entire O/S which, by the way, will save on battery because the CPU will be freed up. Also, the only carrier to have the Note pass through the FCC so far is Att for HSPA+. I'd like to get a full 4g (LTE) version if released.
I have a SGS Epic 4g and my contract is up in June. That will give them time to release 4.0 and for me to see if any other phones release that are close to the power and amazing screen as this one.
Click to expand...
Click to collapse
and also u never know wat are the glitches coming up with ICS
siamchen said:
None of the phone or computer can be fully driven by GPU. CPU is the core component of them but not GPU. GPU will certainly improve the 2D/3D display performance but you still need CPU to response most of the other tasks. ICS is not that kind of magic things. It just an twisted Gingerbread man + Honeycomb.
Click to expand...
Click to collapse
ICS in fact will be magical, awesome, fantastic
No, seriously, GPU acceleration will make the battery long more, drawers will be fasters and @ 60 fps always even in old devices and all the apps animations will be fluid.
Of course the cpu it is important, but this is like when in windows after a format you don't have the gpu drivers and all of them is laggy with slow drawings on screen.
This will be the most remarcable addition to android so far in a lot of time.
ZenInsight said:
Who knows when Ice Cream Sandwich will be released officially. What I HAVE heard though is that ICS is fully GPU driven by default, so hopefully when it comes out Samsung will not disable the Hardware acceleration due to their Touchwiz deal. As soon as 4.0 is released and is hardware accelerated I am buying the Note.
Click to expand...
Click to collapse
If you have the patience you should wait since you have expectations that are not yet fulfilled.
Also prices won't go higher on waiting, they would only reduce as a new model comes into the circuit.
For people like me (patience-less) I can only hope that disturbances would delay my future electronic purchases so that i can save for the next best thing ;-) then again a person like me would like to dive right into it and see what can be made out if it perhaps rom cooking on my cards ;-)
From Windows to Android here I (try) to Come!~
ZenInsight said:
. . want the GPU to drive the entire O/S which, by the way, will save on battery because the CPU will be freed up. . .
Click to expand...
Click to collapse
Doesn't mean the overall power draw will be less, the GPU will start drawing more power.
The GPU will not drive the OS, only the animations and rendering. The OS will still be driven by the CPU since GPUs are not designed to execute complex instruction sets.
The UI animations and transitions will be faster and smoother and hopefully the hardware acceleration will also be baked into the browser to speed up page rendering and redraws.
But there is no need to wait, since you will have a better phone than you have now which will be able to run ICS when it is available. Samsung will not be shipping the note with ICS anyway, most likely they will always ship it with GB and offer an OTA upgrade.
Sent from my GT-N7000 using XDA App

[off topic]Linaro Android Puts Stock Android To Shame !!!!!!!!!!!!!!!!!

Linaro is a second NEON optimization !
You can check Galaxy Nexus forums....already working with cyanogen
"-Both hardware, android version and benchmark software (oxBench) are the same, and the results are quite amazing with Android Linaro achieving about 60 fps in all 0xBenchmark tests (OpenGL Cube, OpenGL Blending, OpenGL Fog and Flying Teapot) whereas Android stock achieving 30 fps."
Also:
or this
So what do you think people?
Some one still have it Nexus phone ? Any feedback's?
Please use the Android General Section Thread
Would be so sick if we could use that on S4 processors
Every little bit helps, but before you get too excited. Android is double buffered, so frame rates are some multiple of 60. So some of this 30/60 benchmarks are likely to be more like 57 and 63fps if rendered off screen. However, every bit helps and a code cleanup is always welcome! I also look forward to it.

Not smooth as I expected!

The Nexus 7 should be very "powerful" as promised by Google!
Quad-core 1.3 GHz Tegra 3 processor vs Dual-core 1.2 GHz Cortex-A9... the Nexus is a Giant in CPU performance, but the UI isn't smoother than Galaxy S2, indeed it seems that the UI hardship to drag from one screen to another, is not at all fluid! in some case this is irritating!
At this point the Mali GPU of the Galaxy S2 it's a big point over the perfmance!
Anyone have the same observation about the UI smoothness of the S2 vs the Nexus 7?
Naamah said:
The Nexus 7 should be very "powerful" as promised by Google!
Quad-core 1.3 GHz Tegra 3 processor vs Dual-core 1.2 GHz Cortex-A9... the Nexus is a Giant in CPU performance, but the UI isn't smoother than Galaxy S2, indeed it seems that the UI hardship to drag from one screen to another, is not at all fluid! in some case this is irritating!
At this point the Mali GPU of the Galaxy S2 it's a big point over the perfmance!
Anyone have the same observation about the UI smoothness of the S2 vs the Nexus 7?
Click to expand...
Click to collapse
Are you comparing stock with stock? Personally, I find both stock and most roms very smooth. I don't have a GS2 but its definitely a lot smoother than the phones I have played on, including the GS2 on ICS stock.
What did you do to it? I use a SGS3 at work (I'm a software engineer currently developing a proprietary android app for my company) and the Nexus 7 is just as "smooth" if not smoother. You realize as soon as you install apps or modify it in any way the comparison to another device is not fair because it's not on even footing, right? Take it and the S2 back to stock with a factory reset and then compare them. It's entirely possible that apps that you choose to install will affect the performance of the device, even when they are not running.
CHollman82 said:
What did you do to it? I use a SGS3 at work (I'm a software engineer currently developing a proprietary android app for my company) and the Nexus 7 is just as "smooth" if not smoother. You realize as soon as you install apps or modify it in any way the comparison to another device is not fair because it's not on even footing, right? Take it and the S2 back to stock with a factory reset and then compare them. It's entirely possible that apps that you choose to install will affect the performance of the device, even when they are not running.
Click to expand...
Click to collapse
The Nexus7 and the S2 have the same Apex Launcher, the same LWP, and around the same software installed, the kernel is about to stock (excepted for the rooting) on both device, and the software installed is pretty the same (maybe the S2 have some apps plus rather the N7).
The Stock S2 is not AOSP (is Samsung full of bloatware) as in N7, so compairing the stock isn't to right... so I've installed in my S2 the SuperNexus (AOSP JB) to compare with N7 (AOSP JB).
Exist a benchmark to test the smoothness of the UI? instead of the CPU benchmark?
The difference of smoothness I've found maybe can be imputed to the different screen resolution? (1280x800 vs 480x800)
I don't know what you've done to your N7 but that just sounds ridiculous. I have a Galaxy S2 and have used that many ROMs & Kernels on it I care not to mention.
But still it has never even come close to the N7's stock experience, in fact the only thing I use my S2 for now is phone calls. This bad boy goes everywhere with me now tethered to my phone when I'm not at home.
Sent from my........
RockNrolling said:
Magnetised banana
Click to expand...
Click to collapse
After a lot of trying I've found that my LWP scrool smooth on S2 but not on N7... maybe it's a code related question (about Mali driver?).
Comparing the speed of the excution of the various apps the N7 is greater, but regarding the smoothness of the UI the S2 is equal to N7 (maybe a little bit greater).
At this point I must say thanks to the developer of the S2 ROM and the "optimized Mali driver for project butter"?
Naamah said:
After a lot of trying I've found that my LWP scrool smooth on S2 but not on N7... maybe it's a code related question (about Mali driver?).
Comparing the speed of the excution of the various apps the N7 is greater, but regarding the smoothness of the UI the S2 is equal to N7 (maybe a little bit greater).
At this point I must say thanks to the developer of the S2 ROM and the "optimized Mali driver for project butter"?
Click to expand...
Click to collapse
Is this an AOSP or touchwiz rom?
Because I remember codeworkx himself saying that the exynos S2 will never have full project butter and JB stuff because of all the closed source drivers and stuff samsung uses. He said that the OMAP version had a smoother UI, so I doubt it comes close to the N7. Unless you're using the omap version
markj338 said:
Is this an AOSP or touchwiz rom?
Because I remember codeworkx himself saying that the exynos S2 will never have full project butter and JB stuff because of all the closed source drivers and stuff samsung uses. He said that the OMAP version had a smoother UI, so I doubt it comes close to the N7. Unless you're using the omap version
Click to expand...
Click to collapse
Mine is an AOSP ROM (based on CM10) so... I've been heard about OMAP, but I don't know what is on details...

Categories

Resources