Within two days since the release of CM10.1 with hybrid ION/PMEM allocation, I happen to see more and more people asking for the explanation of that ION thing we are all talking about.
In fact, all you need to do is a Google search because lately there's been quite a bit of discussions about Android "ION". What exactly is ION? Is it just some fancy name or is there more to it?
Let's talk about some history of Android first.
Since the very beginning, vendors of Android devices like HTC, Samsung or Motorola all use different System on a Chip (SoC) solutions from Qualcomm (MSM/Snapdragon), Nvidia (Tegra) and TI (OMAP). Each SoC has its own kernel drivers for managing memory buffers (chunks of scratchpad memory) used by Graphic Processing Unit (GPU), Audio processing, and Camera Stills and Video processing.
Every vendor had their own version of memory management, such as PMEM for Qualcomm, NVMAP for Nvidia and CMEM for TI - private memory not shared with anyone else. Each Android graphics, audio and camera libraries had to be customized to work with each of the SoC's own flavour of memory management, which makes it a nightmare for the Android Maintainers to maintain the fragmentation and compatibility issues abound. However, this was the case for all pre-Ice Cream Sandwich OS like Froyo, Gingerbread or even Honeycomb.
For Android 4.0 (aka Ice Cream Sandwich), Google was finally fed up with the private memory manager structure and decreed that all newer devices with Android 4.0 native should use the new, so called "ION" memory manager.
So what is exactly the Android ION?
In a simple words, Android ION removes ARM specific dependencies. The ION memory manager provides a common structure for how memory will be managed and used by GPU, Audio and Camera drivers.
Common functions are:
- Memory allocation / de-allocation
- Direct Memory Access Pools
user-space (Android libraries)
- memory passing to/from kernel space
With these common functions and structures defined, kernel drivers from each SoC manufacturer needed to rewrite their drivers to be compatible with Ice Cream Sandwich.
Once the drivers adopted to the new common structure, the graphics, audio and camera libraries can now be more generic and could care less about the nitty-gritty details of how different SoC vendors' drivers worked.
It was painful at first, but it was a necessary move for Google to impose to all the SoC vendors.
Now looking back, this new ION manager enabled manufactures and third party Android projects (like Cyanogen-mod) to quickly bring up newer Android releases for various devices and also reduce the "hidden" Android fragmentation.
Thanks Google for a powerful Search Tool and the author of this:
Original Article
Sent from my GT-I8150 using Tapatalk
A very good explaination in terms of general basic stuff as my head would be spinning around if you explain it into 'high level wizard' stuff.Hehehe.Thank You.
Sent from my GT-I8150 using Tapatalk
Clearly described. Thank you
Sent from my GT-I9500 using Tapatalk 4 Beta
Very clearly explanation! Thanks
Thanks for the explanation sir, at last, i know what is ION :highfive:
Thanks for the explanation! Been looking for one LOLS! So does it mean ION is better than PMEM?
Sent from my eeepc using xda app-developers app
What's the advantage of ION?
Sent from my GT-I8150 using XDA Premium 4 mobile app
TiTAN-O-One said:
Thanks for the explanation! Been looking for one LOLS! So does it mean ION is better than PMEM?
Sent from my eeepc using xda app-developers app
Click to expand...
Click to collapse
I'm not a dev, but in my understanding the biggest hurdle for porting ROMS is device drivers. It is relatively easy to port a ROM from the AriesVe to the Ancora, because they are made by the same manufacturer, have the same system-on-a-chip manufacturer (Qualcomm) and have a similar stock kernel based.
But porting a ROM from, let's say a HTC One is highly impossible, because it uses a different system-on-a-chip exclusive to HTC phones and its stock kernel is based on it. And even though Android is based on Linux, each of the phone manufacturers have slightly different ways of organizing system files that set the various system options. So a kernel patch that works on one device probably won't work on another. (kernel level features such as GPU overclocking, two-way call recording etc. rely on these system setting files).
Even among phones made by the same company, you may have hardware differences such as different camera technologies, different screen resolutions, etc. that make porting harder.
That's why CyanogenMod, AOKP and MIUI are so valuable and appreciated, because they organize porting of a ROM that, as far as the kernel and GUI are concerned, vary little between devices. However those projects still have to rely on what manufacturers choose to release as open source to develop hardware device drivers to port the ROM to each device.
And then you have the problem of, what level of Android is officially supported by the manufacturer? Our Galaxy W, for example, is still waiting for an official ICS release it may never get, which means running JB/KK as it is meant to be run is that much harder. It's hard enough , where we doesnt have official ICS/JB/KK kernel source.
That's why I give lots of kudos to people who take custom ROMs like Aokp,CM(Mega Kudos to Arco) Paranoid Android and the like that were developed for other devices and port them to the Ancora.We're talking crazy wizard-level stuff like memory management, camera, hardware graphics optimization (Project Butter).
#copypaste ;p
Sent from my GT-I8150 using Tapatalk
BIG thanks for this amazing explanation *thumbsup*
ahaiqali said:
What's the advantage of ION?
Sent from my GT-I8150 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The main advantage for us is the possibility to update Adreno drivers, get rid of some bugs and feel smooth with some sort of better performance.
TiTAN-O-One said:
Thanks for the explanation! Been looking for one LOLS! So does it mean ION is better than PMEM?
Sent from my eeepc using xda app-developers app
Click to expand...
Click to collapse
Surely ION management is better. If it wasn't, it would have already been left out since ICS times by all the manufacturers.
Sent from my Nokia 1100.
LeroViten said:
Surely ION management is better. If it wasn't, it would have already been left out since ICS times by all the manufacturers.
Sent from my Nokia 1100.
Click to expand...
Click to collapse
agree with you.. last time i use CM10.1 that still PMEM, i gave up to stay with it because it is really poor performance when the phone stay up longer... now with ION i feel happy when using this CM10.1 with ION.. well since ICS until KITKAT all should use ION to fully optimize the memory management itself.. if someone could build ION for ICS.. haha.. that would be awesome...
hurtsky said:
agree with you.. last time i use CM10.1 that still PMEM, i gave up to stay with it because it is really poor performance when the phone stay up longer... now with ION i feel happy when using this CM10.1 with ION.. well since ICS until KITKAT all should use ION to fully optimize the memory management itself.. if someone could build ION for ICS.. haha.. that would be awesome...
Click to expand...
Click to collapse
Mates, @hurtsky & @LeroViten
Just want to ask , so for now ONLY cm10.1 b2 custom ROM is compatible with ION kernel? Both ROM and kernel must support ION? Thnx
dec0der said:
Mates, @hurtsky & @LeroViten
Just want to ask , so for now ONLY cm10.1 b2 custom ROM is compatible with ION kernel? Both ROM and kernel must support ION? Thnx
Click to expand...
Click to collapse
Yes
poji94 said:
Yes
Click to expand...
Click to collapse
*sighs
sorry before i noob are "ION" give more life battery to custom rom?
ades47 said:
sorry before i noob are "ION" give more life battery to custom rom?
Click to expand...
Click to collapse
Surely not. It has nothing to do about our battery life. We all have different usage statistics and the variety of apps installed. So we all have different battery stats too. For me one with a heavy usage is more than enough. And two days as a calling and messaging device - is brilliant.
But no... ION has no influence on battery life...
thanks for the topic... best explanation i've read
Maido Ari...
Thank You For The Explanation
LeroViten said:
Surely not. It has nothing to do about our battery life. We all have different usage statistics and the variety of apps installed. So we all have different battery stats too. For me one with a heavy usage is more than enough. And two days as a calling and messaging device - is brilliant.
But no... ION has no influence on battery life...
Click to expand...
Click to collapse
i expecting ION can do better in battery life since bbm to android my galaxy w 100% battery drain in 3 hours and i install greenify
Related
Hi guys,
I know that a lot of users or kernel developers using their SGS like CM7 and/or MIUI on their phone
but the high "battery drain" due to not fully implemented powersaving features [e.g. battery usage of 1-2% per hour in idle and very high consumption during data usage]
and some missing features in the CM7 kernel can be sometimes quite annoying for users that need all or most features of the phone
teamhacksung | cmsgsteam back in April (JVB at that time) had made an attempt to port the Kernel from Samsung's GB sources to get it working with CM7
there were several issues with stability - e.g. rebooting of the phone when activating WIFI, the RIL instability (due to samsung's proprietary RIL/modem driver), don't know about access to the external sd; to only name a few ...
so the majority decided to go the other way around - step by step porting features from the Samsung GB source to the Nexus S port of the SGS
at least the 3 mentioned
can be sort of fixed
- wifi instability (perhaps by force-compiling it via -Os)
- samsung's RIL driver (creating a prebuilt modemctl driver with -Os and stock setting and then using that in optimized kernels; meanwhile the new RIL is used in CM7)
- external SD access (might work with the kernel, the framework might need changes; or the kernel might need some changes that were introduced in the existing CM7 kernel, e.g. 2 luns in devs.c and some changes to the android gadget driver if that's enough)
I used the newer kernel-source from JVH (where deep idle powersaving mode [allowing several days of standby] seems to be working on stock roms and it being enabled in the config)
added the modifications to make it work on CM7 and added some of the newer commits to reflect recent CM7 changes
prerequisites to run it are:
- a Gingerbread bootloader (according to source needed for Deep Idle to work)
- a SGS (GT-i9000), since for the other phones captivate, vibrant there aren't any GB bootloaders yet
- lots of time, commitment and some knowledge to test it & hack on the source
the source can be found in my repo:
jvh_cm7_merge
or if someone feels like hacking on cpuidle/didle stuff on the currently used CM7 kernel:
cpuidle branch
(work mainly done by GuiperPT here; recent didle/cpuidle changes in cm7 kernel were committed/done by coolya (?))
I hope additional devs can be found to attempt to get this kernel working
Thank you for reading this post !
Love the enthusiasm of this guy!
Subscribed !
Zach, Tk.Glitch and Nikademus.. Rock this galaxy! (Y)
EDIT: Don't wanna press you, but can you open a twitter account auto-updated by github to follow all your works? I really like the way teamhacksung adopted
I really love CM7 on my SGS, and I would love to use the phone in the most complete way. So I think a ported Samsung Gingerbread kernel would be a fantastic idea.
Hope some of the kernel developers (maybe hardcore, i have always loved his Speedmod kernel) will spent some time on this.
Had this idea a while back (but would have no idea how to make it) - would this be for CM7/MIUI or GB firmwares? Cheers
Wow. What timing. I have been using CM7 for about 2 months now and I was just thinking that maybe it was time to pop a JVP GB build on to see how it feels. Some CM7 features I would miss for sure, but it seems to me that the speed gap has closed, and battery life on CM7 leaves me wanting (particularly in use, idle consumption has come a long way) and doesn't seem to have any positive prospects. No fault of the devs, who have put an amazing amount of work and progress into it, just a fact.
I was just cruising around to see what was what in the land of customized GB ROM's and stumbled upon this! Wouldn't this rock the casbah!
You rock, Zach! This thread should be sticky / kept alive! And +1 for opening a Twitter account linked to your git repo!
mchud said:
Wow. What timing. I have been using CM7 for about 2 months now and I was just thinking that maybe it was time to pop a JVP GB build on to see how it feels. Some CM7 features I would miss for sure, but it seems to me that the speed gap has closed, and battery life on CM7 leaves me wanting (particularly in use, idle consumption has come a long way) and doesn't seem to have any positive prospects. No fault of the devs, who have put an amazing amount of work and progress into it, just a fact.
Click to expand...
Click to collapse
Funny. I've been thinking the exact same thing. Popped JVP onto my brothers newly acquired SGS and I'm going to monitor it over the coming weeks to see how it performs. I love everything about CM7 except the idle battery usage and perhaps the battery usage during 3G. Damn you Samsung!!!!
EDIT: I wholeheartedly approve of this thread. Although I cannot contribute in any way due to no programming skills whatsoever, I hope some progress can be made
Necrolust said:
Funny. I've been thinking the exact same thing. Popped JVP onto my brothers newly acquired SGS and I'm going to monitor it over the coming weeks to see how it performs. I love everything about CM7 except the idle battery usage and perhaps the battery usage during 3G. Damn you Samsung!!!!
EDIT: I wholeheartedly approve of this thread. Although I cannot contribute in any way due to no programming skills whatsoever, I hope some progress can be made
Click to expand...
Click to collapse
Same for me, miss features in both CM7 and MIUI but the battery life kicked me away. I'm on F1 S2 JVP room now with beautiful UI from galaxy S2, great battery life and stable,been using for few days without any FCs. But Im still looking forward for every updates of CM7 and MIUI
+1 for twitter.
good idea and good luck man!
I completly agree with you zach, and if i can help , i'll try to
This idea is smart ... +10 bacon for you.
Why isn't anybody working on this?...atinm, codework, glitch etc... jump on this...asap
Sent from my GT-I9000 using XDA Premium App
siky_dude said:
This idea is smart ... +10 bacon for you.
Why isn't anybody working on this?...atinm, codework, glitch etc... jump on this...asap
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Wondering too :\
siky_dude said:
This idea is smart ... +10 bacon for you.
Why isn't anybody working on this?...atinm, codework, glitch etc... jump on this...asap
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
they're probably busy with SGSII
and the issue is that GB bootloaders are only available on the SGS right now (and might only be available to the SGS in the future)
so it's hard for atinm, unhelpful and other coders with e.g. captivate, vibrant, etc. to work it
if I were in their position I wouldn't risk irreversibly bricking my device by flashing a SGS (!) bootloader on a non-SGS device
besides that most of the work would have to be started sort of from scratch for the other devices
so in each way it's a win-lose, you never get a win-win for all :\
(would be easier if samsung provided at least GB bootloaders for each device)
zacharias.maladroit said:
they're probably busy with SGSII
and the issue is that GB bootloaders are only available on the SGS right now (and might only be available to the SGS in the future)
so it's hard for atinm, unhelpful and other coders with e.g. captivate, vibrant, etc. to work it
if I were in their position I wouldn't risk irreversibly bricking my device by flashing a SGS (!) bootloader on a non-SGS device
besides that most of the work would have to be started sort of from scratch for the other devices
so in each way it's a win-lose, you never get a win-win for all :\
(would be easier if samsung provided at least GB bootloaders for each device)
Click to expand...
Click to collapse
Yeah..you are right...but even if they would release the bootloaders for vibrant or cappy, it would still not be implemented in cm7 cuz its not cm7 protocol...i think.
But still...you glitch fugu guy(complicated name) and volunteers should get started on this ... i would help if i knew anything more advanced than instaling windows... lol.
Sent from my GT-I9000 using XDA Premium App
Correct me if I an wrong but I believe we have captivate gb boot loaders available through leak from sam firmware. No source though
Sent from my GT-I9000 using XDA Premium App
You're correct. Only vibrant doesn't have gb bootloader available. There is no bootloader source for any device, almost definitely never will be - but that doesn't matter.
Sent from i9000m on cm7, with xda premium.
Great enthusiastic,......now if only I knew what it all meant! Lol +10 from me, and I guess you know why that is mate! Thanks for your posting
Insanity cm017/glitch v10c
Bump! Hopefully this project stays alive!
PaulForde said:
Bump! Hopefully this project stays alive!
Click to expand...
Click to collapse
Doesn't seem so.
Sent from my GT-I9000 using XDA Premium App
Wow if that works it's gonna be awesome !
Anyone know when we are getting 4.0.4 on HTC One X
emahmood87 said:
Anyone know when we are getting 4.0.4 on HTC One X
Click to expand...
Click to collapse
No. We don't even have a 3.0 kernel yet.
HTC already have about 7494643519467 bugs to fix, nevermind 4.0.4
Sent from my HTC One X using XDA
Fokas. said:
HTC already have about 7494643519467 bugs to fix, nevermind 4.0.4
Click to expand...
Click to collapse
And what bugs are these? only problem i have witnessed is an overheat battery which i think i caused my self but got a new phone, everything else seems flawless including battery + external battery !
Fokas. said:
HTC already have about 7494643519467 bugs to fix, nevermind 4.0.4
Click to expand...
Click to collapse
As launches go, other than the Teg3 graphics issues (flickering), it hasn't been that bad. Most of the major issues have been addressed between 1.29.07 and 1.29.11 and supposedly there's another update to follow. Rather than compare the phone to "perfect," compare it to other high-end phone launches. You'll see it's not as bad as a lot of people are making it out to be.
BarryH_GEG said:
No. We don't even have a 3.0 kernel yet.
Click to expand...
Click to collapse
What does this mean ?, do we not have ICS kernel or something ??.
DANOFDANGER said:
What does this mean ?, do we not have ICS kernel or something ??.
Click to expand...
Click to collapse
No we don't. No Teg3 device is on a ICS kernel yet. It's up to Nvidia to do the heavy lifting.
BarryH_GEG said:
No we don't. No Teg3 device is on a ICS kernel yet. It's up to Nvidia to do the heavy lifting.
Click to expand...
Click to collapse
Will they ever do this ?, wouldn't this provide some heavy fixes and peformance boosts ??.
DANOFDANGER said:
Will they ever do this ?, wouldn't this provide some heavy fixes and peformance boosts ??.
Click to expand...
Click to collapse
Probably not.
We have 2.6.39, the first ICS was based on 3.0.1., or if they hadn't had a massive pointless renumbering, would have been called 2.6.41.
I guess the reason people haven't moved up is because in mainline they started moving all the arm specific files around and consolidating features between the different architectures. This will make it easier in the future, but merging changes when all the files have moved is a ballache.
BenPope said:
Probably not.
We have 2.6.39, the first ICS was based on 3.0.1., or if they hadn't had a massive pointless renumbering, would have been called 2.6.41.
I guess the reason people haven't moved up is because in mainline they started moving all the arm specific files around and consolidating features between the different architectures. This will make it easier in the future, but merging changes when all the files have moved is a ballache.
Click to expand...
Click to collapse
The One S and XL are on 3.0 so if Nvidia gets off their lazy asses you can assume Teg3 devices will move up too. All the new Asus, Acer, and Toshiba (some not even released yet) tablets are using Teg3 so I can’t imagine the manufacturers being OK leaving them on an outdated kernel forever. It would make sense though to update the kernel at the same time the OS is updated to 4.0.4 which could be weeks to months away. No one but Nvidia knows for sure what the answer will be.
BarryH_GEG said:
No. We don't even have a 3.0 kernel yet.
Click to expand...
Click to collapse
Nothing to do with the kernel sent from an asus transformer tf101 running android 4.0.4 on 2.6.39.4 kernel
Could have also been sent of my LG GT540 which is a year or more old running 4.0.4 on a 2.6.29 kernel has updated to .35 now but regardless you see my point
Sent from my Transformer TF101 using XDA Premium HD app
So people lets start another petition for HTC and nvidia asking them to update the kernels to 3.0.I think its upto us or else nvidia will not do it themselves as they dont care about developers!
Am I going bonkers, I thought my transformer prime had that kernal and running 4.04?
maxcovergold said:
Am I going bonkers, I thought my transformer prime had that kernal and running 4.04?
Click to expand...
Click to collapse
No check in the settings if you are doubtful i am sure its not running 3.0
rn9215 said:
No check in the settings if you are doubtful i am sure its not running 3.0
Click to expand...
Click to collapse
i thought the first time the one x is also running on 3.0 but it runs at 2.6.39.4 ...i think its not soooo good ...is it so when it runs on 3.0 the hole system would be better?
One-X-master said:
i thought the first time the one x is also running on 3.0 but it runs at 2.6.39.4 ...i think its not soooo good ...is it so when it runs on 3.0 the hole system would be better?
Click to expand...
Click to collapse
Would like to know too, whats our disadvantage from now being on 3.0 ??.
In short.
In details.
And one more for the hope we get upto date kernels!
As already mentioned several times, there are no special landmark
features or incompatibilities related to the version number change,
it's simply a way to drop an inconvenient numbering system in honor of
twenty years of Linux. In fact, the 3.0 merge window was calmer than
most, and apart from some excitement from RCU I'd have called it
really smooth.
Click to expand...
Click to collapse
So no, it is not a huge deal.
Sent from my HTC One X using xda premium
Interesting link here guys wonder if One x can get some of this.
http://liliputing.com/2012/06/android-is-about-to-get-a-lot-faster-thanks-to-linaro.html
shankly1985 said:
Interesting link here guys wonder if One x can get some of this.
http://liliputing.com/2012/06/android-is-about-to-get-a-lot-faster-thanks-to-linaro.html
Click to expand...
Click to collapse
I'm impressed.
shankly1985 said:
Interesting link here guys wonder if One x can get some of this.
http://liliputing.com/2012/06/android-is-about-to-get-a-lot-faster-thanks-to-linaro.html
Click to expand...
Click to collapse
Wow, bring it on!
What i would be interested in is whether battery consumption is therefor increased or if it remains the same? Either way, i hope this gets the attention it deserves. It doubles the fps, this is crazy!
nvidia is not involved in this project according to linaro website
the dev in the video mentioned they were only developing for ARM processors.. .. looks like the wait begins
AndrewJ41 said:
the dev in the video mentioned they were only developing for ARM processors.. .. looks like the wait begins
Click to expand...
Click to collapse
99,99% of all Android devices are ARM. Intel has just ported it to x86 but there has never been a worlwide release of an Intel-Android phone yet, so it makes a lot of sense to keep it on ARM. Needless to say that the HOX is ARM-based too. No need for sad faces...
basically if u use custom rom which is based on AOSP, AOKP & CM9 your in luck because these developers can use this now,
while sense have to wait for htc to update... thus us <---- right?
personally i dont see if happening anytime soon
Not happening on tegra just because Nvidia is a bad company and will not release any source for their drivers and so therefore there's no way to port the timizations over.
thunder07 said:
basically if u use custom rom which is based on AOSP, AOKP & CM9 your in luck because these developers can use this now,
while sense have to wait for htc to update... thus us <---- right?
personally i dont see if happening anytime soon
Click to expand...
Click to collapse
Wouldn't google have to implement this into their source or can this be done via kernel update from htc ?.
shadehh said:
What i would be interested in is whether battery consumption is therefor increased or if it remains the same? Either way, i hope this gets the attention it deserves. It doubles the fps, this is crazy!
Click to expand...
Click to collapse
I would guess less battery usage. It goes faster because the code is better optimised and therefore fewer instructions to achieve the same goal.
Hunt3r.j2 said:
Not happening on tegra just because Nvidia is a bad company and will not release any source for their drivers and so therefore there's no way to port the timizations over.
Click to expand...
Click to collapse
I don't think the ABI is affected by these changes, so it should be possible to build the kernel and still use the prebuilt nVidia binary drivers.
Hunt3r.j2 said:
Not happening on tegra just because Nvidia is a bad company and will not release any source for their drivers and so therefore there's no way to port the timizations over.
Click to expand...
Click to collapse
Aren't this changes made to the google code?
Linaro has been applied to CM9 Domination ROM [JUN14-Build3] today On any CM9 build I tried before this all I could acheive on quadrant was around 4300 now im hitting 5000+ with this build.
http://forum.xda-developers.com/showthread.php?t=1692415
13pointseven said:
Linaro has been applied to CM9 Domination ROM [JUN14-Build3] today On any CM9 build I tried before this all I could acheive on quadrant was around 4300 now im hitting 5000+ with this build.
http://forum.xda-developers.com/showthread.php?t=1692415
Click to expand...
Click to collapse
I'm getting 5000 with stock ROM
Sent from my HTC One X using xda premium
13pointseven said:
Linaro has been applied to CM9 Domination ROM [JUN14-Build3] today On any CM9 build I tried before this all I could acheive on quadrant was around 4300 now im hitting 5000+ with this build.
http://forum.xda-developers.com/showthread.php?t=1692415
Click to expand...
Click to collapse
as you can see in the users feedback opf this ROM lots of GPU acceleration issues
on the linaro website FAQ
its actually said they dont support Nvidia processors since NV didnt join the program
anyway ill keep my eyes on that ROM
To be fair I think nvidia will keep a close eye on this and work that has worth they will use internally, so its not all bad. It does however mean a long wait until users see anything from it though
Hunt3r.j2 said:
Not happening on tegra just because Nvidia is a bad company and will not release any source for their drivers and so therefore there's no way to port the timizations over.
Click to expand...
Click to collapse
Most likely nvidia would like to release the source but can't because of non disclosure agreements with 3rd parties. Anyway acoording to the video most optimization is to the cpu so even on sense we could soon see some of the optimizations on custom roms.
Also a while ago I build custum RPM packages on Mandriva, when building on Mandriva by default it uses strict aliasing and many packages refused to build but adapting the code to compile was relatively easy, even for someone like me with little to no experience in coding.
This would do really, really great on the one x.
How hard is it to port the toolchain to tegra3?
Sent from my HTC One X using XDA
oOzzy` said:
This would do really, really great on the one x.
How hard is it to port the toolchain to tegra3?
Sent from my HTC One X using XDA
Click to expand...
Click to collapse
To get a issue free port I would say it needs Nvidia to do this.
Sent from my HTC One X using xda premium
Hi all, I was wondering why all the kernels we use/flash to our Arc are still version 2.6.32, when other devices had already moved to newer kernels, like 3.0.15/3.0.31 for example, which many Samsung Galaxy phones use. Is it a drivers problem?
Thanks for your time.
This is the reason..
KalleD said:
Hi all devs,
I have seen quite a few comments regarding the kernel version in the ICS alpha release. The reason why we are keeping the 2.6.32-kernel is that we have prioritized time to market. It is rather quick to get a new kernel up and running, but it takes a lot of testing and validation to make it stable and run with the modem, get a good battery performance etc. Quite some effort has been put in to the Sony Ericsson 2.6.32 kernel, to make it as stable and reliable as possible for the 8255 platform, and we do not feel that the user benefit of a new kernel would justify a later release date.
/Karl-Johan “Kalle” Dahlström
Sony Ericsson Developer Program
http://www.sonyericsson.com/developer
Click to expand...
Click to collapse
It very hard to right new drives its eazyer to mod 2.6.32 becouse Sony Ericsson has hack the #### out of most of the drivers and made a mess of them so people
DON'T MAKE IT BETTER THAN THERE NEWEST PHONES THAT THAY RELEASE
it will take time to do it takes a very good dev a eazy month for something good like 2.6.35 but it will come if the tree\source is good for the arc/s just keep you eyes open for someone bringing it ;-)
Sent from my LT18i using xda premium
Thanks for your answers, quite explanatory.
Hope some team will bring in the future Kernel 3.0.X to Arc though.
http://www.gsmarena.com/samsung_gal...786.php?utm_source=dlvr.it&utm_medium=twitter
wat da fak sammy?
that phone have similar hardware configuration like our phone, just 800Mhz dual core cpu and 768Mb ram, I guess its about 500Mb because 268Mb
deserved for system, and mali-400MP GPU. Just a slight improvisation from our i8150.
damn you sammy
wat da fak sammy?
that phone have similar hardware configuration like our phone, just 800Mhz dual core cpu and 768Mb ram, I guess its about 500Mb because 268Mb
deserved for system, and mali-400MP GPU. Just a slight improvisation from our i8150.
damn you sammy[/QUOTE]
what da hell samsung? uour phone spec isn't low enough for ICS, your bull**** touchwiz blows everything down. crappy marketing strategies
Even Samsung Galaxy S Duos http://www.gsmarena.com/samsung_galaxy_s_duos_s7562-4883.php comes with ICS
Speechless as it is much weaker than our SGW, in term of CPU & GPU, the only thing it wins is the amount of RAM
There are a lot of ICS phones with 512MB RAM from HTC & Sony, if Samsung is willing to give us support, we would get ICS without problem for sure since Samsung got a big team to work it out, really quite a bad support from Samsung for our phone, luckily we got Arco and some developers who work hard to bring ICS to us really thankful to them!
MyDeSTiNaTe said:
Even Samsung Galaxy S Duos http://www.gsmarena.com/samsung_galaxy_s_duos_s7562-4883.php comes with ICS
Speechless as it is much weaker than our SGW, in term of CPU & GPU, the only thing it wins is the amount of RAM
There are a lot of ICS phones with 512MB RAM from HTC & Sony, if Samsung is willing to give us support, we would get ICS without problem for sure since Samsung got a big team to work it out, really quite a bad support from Samsung for our phone, luckily we got Arco and some developers who work hard to bring ICS to us really thankful to them!
Click to expand...
Click to collapse
yes this is right. support al the dev!!
I always look at the bright side of this.
If sammy release update ICS or JB, then we will loose the excitement of custom ROM.
What I mean is like the waiting time of new custom ROM version, the moment when devs release new update and we download it and flash it to our beloved SGW. It's so exciting!!!
Here, we have many custom ROMs and every new release is getting better and better. To be honest, I might prefer custom ROM. Because even if sammy release update, I'm sure it will full with sammy's bloatware.
One day, I met other SGW user. He is just a regular user and don't know anything about flashing. He looked at my phone and say: whoaa..!!! how did you do that?? Can you do it to my phone??
My point is: I DON'T CARE if sammy release update or not. As long as there are custom ROMs, that's more than enough for me
maybe we are not worried about this because there are custom rom. but I feel sorry for those who use stock rom and hope about rom upgrade.
hotheabilly said:
http://www.gsmarena.com/samsung_gal...786.php?utm_source=dlvr.it&utm_medium=twitter
wat da fak sammy?
that phone have similar hardware configuration like our phone, just 800Mhz dual core cpu and 768Mb ram, I guess its about 500Mb because 268Mb
deserved for system, and mali-400MP GPU. Just a slight improvisation from our i8150.
damn you sammy
Click to expand...
Click to collapse
Seconded!!!!
And the salt into the wound is that the Galaxy Ace 2 is £70 cheaper on O2 Uk pay as you go than my Galaxy W was 10 months ago
ianfebriyanto said:
maybe we are not worried about this because there are custom rom. .
Click to expand...
Click to collapse
Yes but surely ROMs like Cyanogen 9 would be much further along and have taken less time to develop and debug if an official Sammy ICS ROM for Galaxy W had been available as a starting point for modding/improving.
opexblue said:
I always look at the bright side of this.
If sammy release update ICS or JB, then we will loose the excitement of custom ROM.
What I mean is like the waiting time of new custom ROM version, the moment when devs release new update and we download it and flash it to our beloved SGW. It's so exciting!!!
Here, we have many custom ROMs and every new release is getting better and better. To be honest, I might prefer custom ROM. Because even if sammy release update, I'm sure it will full with sammy's bloatware.
One day, I met other SGW user. He is just a regular user and don't know anything about flashing. He looked at my phone and say: whoaa..!!! how did you do that?? Can you do it to my phone??
My point is: I DON'T CARE if sammy release update or not. As long as there are custom ROMs, that's more than enough for me
Click to expand...
Click to collapse
you're not completely right, for example if we had official ics we would not reverse engineer camera and some other hw, so creating 4.x customs would be easier, but we had just to rely on our devs and huawei u8860 software
Sent from my GT-I8150 using xda premium
opexblue said:
I always look at the bright side of this.
If sammy release update ICS or JB, then we will loose the excitement of custom ROM.
What I mean is like the waiting time of new custom ROM version, the moment when devs release new update and we download it and flash it to our beloved SGW. It's so exciting!!!
Here, we have many custom ROMs and every new release is getting better and better. To be honest, I might prefer custom ROM. Because even if sammy release update, I'm sure it will full with sammy's bloatware.
One day, I met other SGW user. He is just a regular user and don't know anything about flashing. He looked at my phone and say: whoaa..!!! how did you do that?? Can you do it to my phone??
My point is: I DON'T CARE if sammy release update or not. As long as there are custom ROMs, that's more than enough for me
Click to expand...
Click to collapse
Developers would be able to customized ICS if a stock ICS is already available than creating from scratch. ICS is different from GB. Thats why devs are having difficulties in fixing stuffs like camera for phones that do not have ICS. Devs would love to use working libs for ICS phone-related components. Then porting JB would be much faster too since little is different from ICS.
Sent from my GT-I8150 using xda premium
hotheabilly said:
http://www.gsmarena.com/samsung_gal...786.php?utm_source=dlvr.it&utm_medium=twitter
wat da fak sammy?
that phone have similar hardware configuration like our phone, just 800Mhz dual core cpu and 768Mb ram, I guess its about 500Mb because 268Mb
deserved for system, and mali-400MP GPU. Just a slight improvisation from our i8150.
damn you sammy
Click to expand...
Click to collapse
trueeeeeeeeeeeee
dimaka1256 said:
you're not completely right, for example if we had official ics we would not reverse engineer camera and some other hw, so creating 4.x customs would be easier, but we had just to rely on our devs and huawei u8860 software
Sent from my GT-I8150 using xda premium
Click to expand...
Click to collapse
bbmadzky said:
Developers would be able to customized ICS if a stock ICS is already available than creating from scratch. ICS is different from GB. Thats why devs are having difficulties in fixing stuffs like camera for phones that do not have ICS. Devs would love to use working libs for ICS phone-related components. Then porting JB would be much faster too since little is different from ICS.
Sent from my GT-I8150 using xda premium
Click to expand...
Click to collapse
I realize that. But I also know that pissing off to sammy and curse them won't change anything.
What I mean is instead of pissing off to sammy, we should be grateful because we have devs that work very hard porting ICS for our phone.
Sent from my Wonderphone GT-I8150 Ancora
Jelly Bean comes to support phone with NFC device. I think that the cause of the making jelly Bean to Ace 2. Don't worry guys... We have development Forum, we have developers and we have Arco. Not to mention, but ace 2 has no their own thread. You check on search box, no ace 2 comes out. Lol. Probably that's why Sammy feel pity for them and make them a jelly Bean. LMFAO.
Sent from my GT-I8150 using xda premium
azhiekurosaki said:
Jelly Bean comes to support phone with NFC device. I think that the cause of the making jelly Bean to Ace 2. Don't worry guys... We have development Forum, we have developers and we have Arco. Not to mention, but ace 2 has no their own thread. You check on search box, no ace 2 comes out. Lol. Probably that's why Sammy feel pity for them and make them a jelly Bean. LMFAO.
Sent from my GT-I8150 using xda premium
Click to expand...
Click to collapse
+2 saki!!!
u hv d nutz..
azhiekurosaki said:
Jelly Bean comes to support phone with NFC device. I think that the cause of the making jelly Bean to Ace 2. Don't worry guys... We have development Forum, we have developers and we have Arco. Not to mention, but ace 2 has no their own thread. You check on search box, no ace 2 comes out. Lol. Probably that's why Sammy feel pity for them and make them a jelly Bean. LMFAO.
Sent from my GT-I8150 using xda premium
Click to expand...
Click to collapse
Are u trying to bullying ace 2 ? LOL
Sent from My Galaxy Ace 2
hotheabilly said:
http://www.gsmarena.com/samsung_gal...786.php?utm_source=dlvr.it&utm_medium=twitter
wat da fak sammy?
that phone have similar hardware configuration like our phone, just 800Mhz dual core cpu and 768Mb ram, I guess its about 500Mb because 268Mb
deserved for system, and mali-400MP GPU. Just a slight improvisation from our i8150.
damn you sammy
Click to expand...
Click to collapse
I really wish this was true, and I wish Sammy would bring this update out NOW!
Not because I have one of these phones, but because that firmware could be the base for the developers working on our Wonder. That means it's gonna be easier to port, and we'll have a stable CM10 in no time! :highfive: