Related
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
hey, i was just trying to get some feed back on what differences are there in gb that would be a good reason to leave froyo. the reason i ask is because i put a gingerbread rom on my vibrant for about a day and did not see a deference. everything pretty much looks the same. maybe someone can give me a strong argument for switching because at this point i just don't get it.
I was on GB for a couple weeks to try it out but with all of the bugs and non working GPS its just not worth it til there are more stable roms. People will argue that the GB roms are stable but I've had several problems on GB roms, nothing big but little bugs that just get annoying after a while. I would stick with froyo
Dont switch. They just drain your battery and have loads of bugs, like not beeing able to charge when off.(CM7)
Sent from my SGH-T959 using XDA App
New user interface design with new themes (Black themes save power)
Extra Large Screen Size supported
SIP Communication Supported (SIP Video and Audio Calling, In an operator point of view, this is feature will decrease their voice calling revenue where as user can call each other for lower rates or even free if they have good data connection)
Supports for NFC (High Frequency High Speech Data Transfer in short range)
Support for WebM/VP8 video playback, and AAC audio encoding
New audio effects such as reverb, equalization, headphone virtualization, and bass boost
Improved Copy and Paste functionality
Redesigned Multi Touch Software Keyboard
Audio, graphical, and input enhancements for game developers
New sensors support (i.e gyroscope)
Download manager for long running HTTP downloads
Enhanced support for native code
Improved power management and application control
Support for multiple cameras
there's your list of differences from froyo to GB
I switched because cm7 is just lightyears faster than froyo or anything eelse on our phones ... games that wouldnt work on other roms in n64oid now run smoothly
Sent from a cell tower to the XDA server to you.
It is definitely not worth switching until we get an official leak, although at this point it may be worth facing up to the fact that there will not ever be an official GB rom. The ports are too buggy and unstable to make it worth your time.. you will just uninstall it.
I think it is matter of opinion. Some will highlight the builds being buggy and others on it being faster.
vicky_ag said:
I think it is matter of opinion. Some will highlight the builds being buggy and others on it being faster.
Click to expand...
Click to collapse
+1 to that! ive been running cm7 since nightly #4 and there up past #65 so ive been on it awhile. Havent gone back since and im loving it! I like the Built in theme chooser any day i feel like changing my mood just change theme and built in theme chooser does the rest, 10 sec process. Its way so much faster then Froyo thats like comparing apples to oranges of course its faster it should be if it wasnt google wouldnt be doing a very good job! I could go on with all the cool features and specs but theres no use everyone has there own opinion. Heres the true fact of the matter it says in CM7 op cm7 isnt for the noob rom flasher so it may be buggy on ur phone due a bad flash or not wiping data or wiping dalvik. But with cm7 now having gps its as stable as its ever gonna get. Plus make sure ur reading the instructions carefully!!!
Heres what atinm from cm7 has said about vibrant running cm7 and this is so very true!!
All releases are planned to be free of all bugs. Reality forces us to accept what we can do and our hands are tied on things that we don't have code for, nor documentation for and so no, it will not be free of all bugs/limitations. If the code is stable, if the release is usable as a daily driver for most people, it will get the "stable" designation. We will continue to fix bugs that we can fix.
so its wht it is
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".
Anyone here testing CM10 Preview Edition?
What works:
Wifi
Bluetooth
Sound
Camera (Photos + recording + panorama)
Video Acceleration (720p youtube ftw!)
Basic dock functionality (keyboard works -- second battery doesn’t show up)
3D Games
Sensors
What doesn’t work:
GPS
Lightsensor is funky
here is the link
Code:
http://androidroot.mobi/2012/07/18/cyanogenmod-10-preview-edition/
There's a thread on it in development already... Tried it briefly but non-working sd is a dealbreaker for me atm. Other then that there are some keyboard issues when docked (on screen keyboard popping up all the time) and no camera (but that's a generic issue).
Right now I'm on the EOS build, which has sd-card working but no HD youtube vid. So something broken there in hardware acceleration or something (antutu bench can't finish either).
Was hoping for an improvement in IO but the few benchmarks I've been able to run don't show much of that in that area. But hey, it's a first build so can't expect too much (hell, it's pretty awesome for such an early build). RL Benchmark finishes in 74secs now btw, which is quite a bit better compared to ICS.
dagrim1 said:
There's a thread on it in development already... Tried it briefly but non-working sd is a dealbreaker for me atm. Other then that there are some keyboard issues when docked (on screen keyboard popping up all the time) and no camera (but that's a generic issue).
Right now I'm on the EOS build, which has sd-card working but no HD youtube vid. So something broken there in hardware acceleration or something (antutu bench can't finish either).
Was hoping for an improvement in IO but the few benchmarks I've been able to run don't show much of that in that area. But hey, it's a first build so can't expect too much (hell, it's pretty awesome for such an early build). RL Benchmark finishes in 74secs now btw, which is quite a bit better compared to ICS.
Click to expand...
Click to collapse
i was on another aosp build last week and indeed sqlite performance is WAY better! unfortunally not yet an official kernel for jellybean so some performance benches stay the same or worse.
however i did not have ANR and lockups in browser, installation of apps went fast without lockups.
thats pretty nice to me and as long as i dont have problems i dont care about benches too much (benches arw good to pinpoint problems, but dont always reflect user experience)
I've been using team EOS JB, it seems to have a few more things working right now.
smooth as butter.
We already have a thread for this.
Please continue here: http://forum.xda-developers.com/showthread.php?t=1781853
Closed.
So why don't we have this?
http://www.phonearena.com/news/Alwa...standard-with-Qualcomm-Snapdragon-800_id46105
http://www.engadget.com/2013/02/20/...k-charge-2-0-and-snapdragon-voice-activation/
Sony? Google? Maybe in Kitkat?
Btw I'm really impressed how fast the Snapdragon 800 processor is. Feels like a major step forwards. The Ultra is so freaking snappy (and no I'm not talking about the weird homescreen swiping tests you see in reviews. I'm talking about launching stuff, rendering graphics etc)
Never ever experienced such an incredible improvement in speed.
There is a similar app available but I don't think it uses the S800 passive listening ability (and its associated battery life benefits)
http://forum.xda-developers.com/showthread.php?p=45723436
Open mic+
Sent from my C6802 using Tapatalk 2
I agree with liqn7, don't think that Open Mic will use the low power voice recognition module on the snapdragon 800. Did a search on the Qualcomm site, but there aren't any Android API's. In a press release they are talking about the possibility for OEMs to define there own "hotword " so maybe it's only possible to implement it on a low level in the kernel. Don't think Android will add special API's for a specific processor either.