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 !
So here is the situation.
We know our SE Xperia Plays are getting the major update to Ice Cream Sandwhich but Sony is doubting that it will be able to perform and deliver gaming performance like gingerbread does currently. This is because the Play has rather outdated hardware. But they are not looking outside the box. We have great developers here that have excellent skills for exaple DooMlord. These guys could help optimize ICS to give the graphic capabilitys Gingerbread does currently.
So my conclusion? We take the update and then all pull our wait to optimize it like we've done with gingerbread ( WE HAVE A 2GHZ OVERCLOCK)
Whats your view on this topic?
There are already custom ICS roms and kernels that work really well. Check the development section
I'm going to be a bit blunt here. Do you not know the word DEVELOPERS is in the website name? that's what his whole site was based upon. Taking sources and making them work for us so we can use our phones to the potential it was built.. So, in short. There is no situation.
I have a general IT background of 10+ years with basic scripting skills so understand on a general level about drivers but I have been reading for several months trying to understand the EXACT nature of the problem for why i still don't see a ICS rom for the evo4g with working (or semi-working) wimaxx.
Can someone please educate me? Here is my version....
Sprint has retired the evo4g via end of life decision process and so does not have a formal team working on an ICS build of any kind for my phone. I don't agree with this decision, but i understand why Sprint is not providing me with one.
Because Sprint has retired the phone, HTC is not doing any development for the phone and so THEY aren't providing me with any drivers. I'm not sure who of these two made the business decision, Sprint or HTC, probably HTC. Either way, no formal support from either of them. I don't agree, but accept that.
As for developers coming up with their own, this is where I'm expecting magic and so instead of just crying "where are my drivers, where is my rom" i am attempting to learn why they aren't here and am requesting an education on the subject.
From my understanding, AOSP is Googles contribution for free to the world. This is a great operating system for running phones for a variety of reasons. From there, manufacturers take the basic kernel and modify it to work with their equipment. This is where it gets a bit confusing for me.
I think that the manufacturers do two things. One, is that they work with chip manufacturers to obtain proprietary drivers for specific chipsets that integrate into the basic kernel. Two is that phone manufacturers ALSO modify the kernel so as to make a proprietary version of the kernel. So HTC made a propritary version of the kernel and incorporated SENSE (among other things) into that proprietary kernel, and hooked up proprietary drivers that may or may not work with the AOSP kernel to provide services such as video and wimax and sound etc.
I know teamwin some how reverse engineered or manufactured a wimax driver for gingerbread such that the wimax driver was available for the AOSP Gingerbread kernel, but teamwin or nobody else has done that such that a wimax driver is available for the AOSP ICS kernel
I know that HTC has wimax working on some of its phones that have ICS via threads that talk about it being leaked (i.e Nexxus 4g).
So here are some questions... I suspect none of them are accurately asked.
Version1
Does AOSP ICS kernel have the ability to have a wimaxx driver built/interfaced into it?
If so, is it HTC that technically owns this driver or another specific company?
Version2
If AOSP ICS kernel does not, does that mean we currently need both a specific evo4g ICS kernel AND the wimax driver built?
Or are either of these easy to build and we just need one part of them built...meaning the wimax driver is out in the world for developers now and all that needs to happens is for someone to put some "hooks" into a new evo4g kernel such that they would work with the driver.
I apologize in advance if i broke some posting rules. I can't post in developement section yet so i placed in q/a where it says "any question". I did some basic research on the subject so i'm not just whining i don't have my driver. I am trying to get at the specific thing that needs to happen for my evo4g rom to have wimax working on ICS.
My theory is "HTC owns the wimax driver for ICS but won't release the source code as they only want to bring certain wimax devices into the ICS generation. It is proprietary to a specific kernel so if it was released, it would not instantly work with the AOSP kernel and other kernels. It would still need further development (but on which end???). It is illegal and difficult for someone to reverse engineer this ICS WIMAXX driver. It is legal, but still difficult for someone to create a generic ICS WIMAXX driver. Since both are difficult they will not happen soon."
Thanks for your thoughts in advance.
*DISCLAIMER - everything I say below is based on belief and may be wrong.
Believe that the majority of what you said is correct.
Slight thing - nexxus 4g (I believe this is sammy/goog, no?)
While kernel may have specific customizations for sense, believe sense is built on top of OS (ICS) and not IN the kernel itself per se.
(MOST LIKELY SCENARIO): Believe that HTC has to release an update where ICS and Sense crap all play nicely together and sprint has to test it and release it and then xda devs need to fix it to remove bloat, optimize, and ensure no more CIQ-ish kind of crap or htc spy crap or root removal...can't trust any of these bastards. The update will have ICS + Sense + Kernel (including the proprietary or binary blob drivers for things like wimax, camera, screen).
(IDEAL SCENARIO): HTC quit being little Apple-tards, realize that their differentiator is that they ARE NOT a walled garden - that customer enthusiasm is a good thing. They get off their asses and send a working kernel source for ICS AOSP (just the kernel) to team douche/team win/team kang... somebody cool (officially or unofficially) and BAM - everything works great in the AOSP/AOKP world. I mean really - if we are going to be in a walled garden, is not Apple's the best? Why not just buy iphones if HTC's gonna be a giant douche? Turd sandwich or Samsung would be better options.
Please correct me if I'm wrong. This is a learning experience for me too!
Wondering about this as well. It would be nice if the source code for the nexus 4g(wimax) would help us on the EVO front.
One of the biggest problems for the ics rom is its not based on the kernel its supposed to be running. The kernel has been frankenkerneled from tiamats gb kernel with the correct settings to run as ics. While I know that the kernel has been updated to somewhat but its not the true ics kernel some of these other phones are running and also while team douche or team win got the wimax working on aosp gb back in the day...they are no longer working on the evo and also wimax back then wasn't a quick fix. It was on the back burner for the longest time. I commend you on wanting to work on the drivers and learn. I would start by contacting prelude drew via twitter and or atyoung the current dev for the mason ics kernel that hes had great success with. Those two could point you in the right direction or bring on board with them on getting everything working especially with your strong IT background it will come in handy.
Forgive my fading memory, but wikipedia reports Android supports wimax directly.
I thought I read elsewhere that 2.3 GB or 3 and on was supposed to support wimax natively - thereby obviating team win's wimax "fix."
?So ICS doesn't support wimax (or it does?) but we need a driver from the mfg? Is this a broadcom/qualcomm thing? Proprietary driver? Supplied to HTC as a binary blob rather than source?
Will we likely have a first breakthrough when HTC releases the source to ANY ICS kernel?
Will we similarly have a closer breakthrough when HTC releases source to a phone with wimax by same mfg?
What happened to the leaks? Ninja911? Fxck it seems dev has stagnated on these devices. So much hardware and we can't use any of it! GRRRR Why is anyone still buying HTC when they are cxckblocking us so entirely?
Surely if HTC wanted to they could release an ICS AOSP kernel source with little to no effort that works with AOSP roms right? They don't have to do any of their purported excuse for the delay (i.e. get ICS and Sense to play nice, right?)
As it is ICS AOSP can't use 4G, Netflix, Front Camera, HWA...?
On the E3d there's no 4G, no 3D camera, no 3d display, ...
HDMI/MHI surely won't work, will they?
Basically anything that makes the Evo special above a free android type phone?
Along with other issues.
GOD I'd LOVE a 4G working MIUI ICS, CM9, ... but it will never happen - just HTC's corporate culture? I think we have to vote with our $ and support Samsung or a hungry underdog (like HTC used to be) such as Huawei, LG?
Sorry for the vent. Please correct if I've miss-stated above. Learning experience.
My sentiments exactly...
I've been curious about this for the past couple months, I just assumed it was because Sprint felt the Evo4G had run its course, had a good life, etc, and it was time to retire it.
And then since Sprint was no longer supporting HTC followed suit by deciding since Sprint was cutting support for it, HTC realized it was kinda pointless for them to upgrade it. It IS almost 2 years old, so I'm not too irked by it, but I'd like to echo the OP's concern about them not just releasing some ICS compatible drivers for those of us with tinkering hands to play with.
*sigh* Guess I'll just have to wait until the LTEVO is released...
The evo was classified EOL(end of life) before ICS source was even released by Google, therefore HTC has no ICS drivers for them to release because a) they never built anything ICS for the evo and b) alot of the hardware drivers are proprietary and come from the individual hardware manufacturers and not HTC. HTC simply compiles the drivers into a final build to make each specific device function
Sent from my SPH-D710 using xda premium
-EViL-KoNCEPTz- said:
The evo was classified EOL(end of life) before ICS source was even released by Google, therefore HTC has no ICS drivers for them to release because a) they never built anything ICS for the evo and b) alot of the hardware drivers are proprietary and come from the individual hardware manufacturers and not HTC. HTC simply compiles the drivers into a final build to make each specific device function
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Ok, so i understand that HTC and Sprint are out of it, but WHO is the manufacturer of my wimax antenna and is this antenna in any device that has ICS running on it? If so, I'm sensing from this post that even if they release this driver, it still won't help cuz the EVO 4g ICS rom's are actually frankensteined gingerbread code? That seems even weirder. Why wouldn't the EVO 4g ICS roms be frankensteined ICS code massaged for the evo from ICS?
Thanks for the term BLOB. I'll research how that interplays with kernel and OS version and driver and see if i can get a better handle on it. It just annoys me that i'm paying for wimax but in order to use it i have to be on older OS. This phone is totally fine for my basic needs and still has plenty of life left in it. They are accellerating the "planned obselecense" way to fast. Sorry for the typos...its late for me. Thanks everyone.
ittsmith said:
Ok, so i understand that HTC and Sprint are out of it, but WHO is the manufacturer of my wimax antenna and is this antenna in any device that has ICS running on it? If so, I'm sensing from this post that even if they release this driver, it still won't help cuz the EVO 4g ICS rom's are actually frankensteined gingerbread code? That seems even weirder. Why wouldn't the EVO 4g ICS roms be frankensteined ICS code massaged for the evo from ICS?
Thanks for the term BLOB. I'll research how that interplays with kernel and OS version and driver and see if i can get a better handle on it. It just annoys me that i'm paying for wimax but in order to use it i have to be on older OS. This phone is totally fine for my basic needs and still has plenty of life left in it. They are accellerating the "planned obselecense" way to fast. Sorry for the typos...its late for me. Thanks everyone.
Click to expand...
Click to collapse
Its Frankenstein gb code with ics code intertwined cause there are no drivers for ics that'll run the evo so the other kernel was modified to work for ics
I'm no expert on Android but I do understand operating systems pretty well, so here is my best guess as to what is going on:
1) A kernel is pretty hardware generic (maybe architecture dependent only) and provides various functions to the software that runs on top of it (e.g. the Dalvik VM that runs most Android apps and Android/Sense UI) and it is provided by Google. Each kernel will need to have certain features/capabilities that are specific to a given Android release (i.e. you can't just use a GB kernel with ICS since it will be missing some features expected by the ICS UI and Dalvik VM).
2) Individual manufacturers need to add drivers (kernel modules) in with the generic kernel from Google to support the specific chips on a given phone. So, for our Evo 4g there need to be drivers for the WiMax chip, camera, bluetooth, etc.. These drivers need to be updated for each new Android release kernel. Depending on how a release kernel changes, this could be just a re-compile or it might require somebody to rework the code. If the WiMax code needs more than just a recompile, then it is either a lot of work for an amateur dev team to try and refactor the GB WiMax code to work for an ICS kernel OR HTC needs to do the work and release it for us. Since the latter is unlikely to happen, getting WiMax working would require a lot of work from an amateur developer.
3) It is also possible that some drivers are just released as binary blobs that are loaded by the kernel. In this case, a binary driver that was compatible with a GB kernel may no longer be compatible with the ICS kernel. In this case if HTC doesn't release it, it would require a ground up write of an ICS driver for WiMax, which is unlikely to happen.
The above is my best guess as to what is going on as a general field expert on kernels/drivers. Since I'm not as familiar with Android specifically, I could be off on what is happening here. We'd need somebody who has played around with Android kernel development for the Evo 4g to say for sure.
bjohanso said:
I'm no expert on Android but I do understand operating systems pretty well, so here is my best guess as to what is going on:
1) A kernel is pretty hardware generic (maybe architecture dependent only) and provides various functions to the software that runs on top of it (e.g. the Dalvik VM that runs most Android apps and Android/Sense UI) and it is provided by Google. Each kernel will need to have certain features/capabilities that are specific to a given Android release (i.e. you can't just use a GB kernel with ICS since it will be missing some features expected by the ICS UI and Dalvik VM).
2) Individual manufacturers need to add drivers (kernel modules) in with the generic kernel from Google to support the specific chips on a given phone. So, for our Evo 4g there need to be drivers for the WiMax chip, camera, bluetooth, etc.. These drivers need to be updated for each new Android release kernel. Depending on how a release kernel changes, this could be just a re-compile or it might require somebody to rework the code. If the WiMax code needs more than just a recompile, then it is either a lot of work for an amateur dev team to try and refactor the GB WiMax code to work for an ICS kernel OR HTC needs to do the work and release it for us. Since the latter is unlikely to happen, getting WiMax working would require a lot of work from an amateur developer.
3) It is also possible that some drivers are just released as binary blobs that are loaded by the kernel. In this case, a binary driver that was compatible with a GB kernel may no longer be compatible with the ICS kernel. In this case if HTC doesn't release it, it would require a ground up write of an ICS driver for WiMax, which is unlikely to happen.
The above is my best guess as to what is going on as a general field expert on kernels/drivers. Since I'm not as familiar with Android specifically, I could be off on what is happening here. We'd need somebody who has played around with Android kernel development for the Evo 4g to say for sure.
Click to expand...
Click to collapse
You're fairly close, the android kernel is essentially the Linux kernel, HTC doesn't build the wimax driver I believe its qualcomm that makes the radios in our devices but I'm not sure they make the wimax radio or just the cdma radio. They make a good amount of the hardware in the evo from radios to gpu to audio control components. Building the drivers isn't an easy task for any single dev without existing source to modify, even someone who does it for a living would have a long, difficult road to building a driver from the ground up with no preexisting source to use as a map I've been working on drivers for ics for a cpl months and its not easy starting with a blank page and starting code from scratch. Even with the existing aosp wimax drivers available for the evo, so much has changed in ics modifying the drivers is basically like starting from scratch cuz so much code needs to be reworked. It will probably be one of the last things to be added just like it was on gb
Sent from my SPH-D710 using xda premium
What about when they update the EVO3D? Will either the ics update for the 3d or when they release the kernel source for 3d ics help?
sinnedone said:
What about when they update the EVO3D? Will either the ics update for the 3d or when they release the kernel source for 3d ics help?
Click to expand...
Click to collapse
Probably not since the 3d uses a different chipset and the insides look nothing like the evo
sinnedone said:
What about when they update the EVO3D? Will either the ics update for the 3d or when they release the kernel source for 3d ics help?
Click to expand...
Click to collapse
The Evo Design 4G update would help us more than the EVO 3D would since the specs are similar to ours
Sent from my PC36100 using Tapatalk 2 Beta-6
Papa Smurf151 said:
Probably not since the 3d uses a different chipset and the insides look nothing like the evo
Click to expand...
Click to collapse
I was going on the assumption that the only roms with newer versions of sense that have working 4g are ports from the Evo3d.
you guys are nerds and i envy you all...
There is so much awesome going on.. our best bet, would be to grab the EVO design 4g update. That would be as close as we can get.
then someone can port it here
Hopefully HTC will release a source code for the kernel & or RUU. Then we can go from there...
Sent from my PC36100 using xda premium
Thank you, i am learning alot.
Is there a page that discusses the evo 4g specifically and shows what parts are frankensteined and what are not. Ideally, something like
Radio
- wimax - unavailable
- cmda - Use ICS wrapper on Gingerbread kernel driver 2.2. wrapper created by developer abc. Gingerbread kernel driver - HTC Android 2.3 patch - version 12341
Graphics
- something - blob - developer xzy
- something else - blob - developer def
- something else - kernel driver - Standard Android 4.0 patch - version 5.6
Camera
- front - ICS blob - developer pdq
- back - unavailable
Microphone
- standard - ICS Kernel Driver - Standard Android 4.0 patch - version 3.3
etc
I would think that each phone has a "map" of what is available and I would think developers would share. Obviously the first thing I would look at on this map is what did Teamwin do? I can't imagine they created a BLOB, but instead did they use a wrapper on a Froyo wimaxx driver or a wrapper on a gingerbread sense patch or did they write it themselves.
Doing some research I've gotten this data...am I on the right track to build my map of the EVO 4g for ICS. Why isn't this public knowledge somewhere. I am trying and not being lazy...well, not super lazy...
I got this from the cm9 thread for evo, thanks people in there for posting details
mason v14sbc ics kernel (Nonfso nonsbc, hwa kernel)
back camera - system/lib/hw/1sd8k.so
Camcorder
libmediaplayerservice.so
libOmxCore.so
libOmxVdec.so
libOmxVidEnc.so
libstagefright.so
libstagefrighthw.so
@ittsmith, sounds like you are aiming to be the next kernel genius. With this type of info you will be able to develop on kernels for far more devices than just evo...
Anyhow, I am no developer by any means just getting into programming, but I wanted to lay out my train of thought and see if it stands up or has any insight.
Any manufacturer has to start with AOSP source, and then build for their specific device. So, if theoretically HTC was building an ICS kernel they would begin there, with the latest source from Google. Then they would add in the device tree, much like building a ROM from source only here we are talking core drivers and such for proprietary hardware, and finally build a custom kernel for that device.
Now of course these guys have full access to source and drivers and the like of which we may not have... Though htcdev does have kernel source on their site. So, like you said initially why not take the ICS kernel and make it compatible to EVO? That is exactly what HTC would do, and does for the other devices that are receiving updates...
I remember running gingerbread long before there was an update to the evo, and there were gingerbread kernels... So I am just thinking we don't have the tools and know how to get the job done but all the pieces may be there. I would say petition either toastcfh or even Adam Outler, as these two are pretty damn magical when it comes to Android devices and the linux kernel.
http://forum.xda-developers.com/showpost.php?p=29992622&postcount=217
http://forum.xda-developers.com/showthread.php?t=1790721&page=22
He or she said:
Sorry for discontinuing this project. I will start new project in cm10 so i dont have time to continue cm7 . Sorry again
Sent from my GT-I8150 using xda app-developers app
new update: he or she said: Will start to build on this sunday
Not to sound like an ass but honestly CM7 looks and feels really dated now and with a more stable CM9 for our phone and hopefully CM10 on the way I rather more effort is focused on ICS and JB ROMs rather than CM7 since we already have good GB ROMs for the SGW.
Just Another★Gamer said:
Not to sound like an ass but honestly CM7 looks and feels really dated now and with a more stable CM9 for our phone and hopefully CM10 on the way I rather more effort is focused on ICS and JB ROMs rather than CM7 since we already have good GB ROMs for the SGW.
Click to expand...
Click to collapse
Do you mean outdated? :laugh:
FelixAusChina said:
http://forum.xda-developers.com/showpost.php?p=29992622&postcount=217
http://forum.xda-developers.com/showthread.php?t=1790721&page=22
He or she said:
Sorry for discontinuing this project. I will start new project in cm10 so i dont have time to continue cm7 . Sorry again
Sent from my GT-I8150 using xda app-developers app
Click to expand...
Click to collapse
whoaa... really? hope for that become true. can't wait for that.
Just Another★Gamer said:
Not to sound like an ass but honestly CM7 looks and feels really dated now and with a more stable CM9 for our phone and hopefully CM10 on the way I rather more effort is focused on ICS and JB ROMs rather than CM7 since we already have good GB ROMs for the SGW.
Click to expand...
Click to collapse
I'm not agree with you.
First, there is not a finished and stable CM rom and is not so good start with new projects at this point.
Why?
Because gingerbred on galaxy w is simply perfect and there is no reason or features in CM9 or in CM10 that justify porting and waste of resources and time.
I hope that someone will finish CM7 job.
willypt said:
Do you mean outdated? :laugh:
Click to expand...
Click to collapse
Yea, its early in the morning so its a little obvious i'll make mistakes.
kbytek said:
I'm not agree with you.
First, there is not a finished and stable CM rom and is not so good start with new projects at this point.
Why?
Because gingerbred on galaxy w is simply perfect and there is no reason or features in CM9 or in CM10 that justify porting and waste of resources and time.
I hope that someone will finish CM7 job.
Click to expand...
Click to collapse
Well your welcome to disagree, i'm not forcing my opinion on you or anyone just stating what I think.
There is no finished CM ROM but stable I honestly think the latest CM9 build is stable for daily use and not so good, lol CM9 runs graphic heavy games a whole lot better than GB even when its OC.
Oh yes GB is much much smoother and better than ICS and JB, sigh. There are already good GB ROMs for the SGW so is it such a big deal that someone wants to drop making CM7 and start doing the newest CM10 for our phone its their choice and if I had skills I rather take my shot and making CM9 and CM10 for our phone better rather than stick with ye old CM7.
Just Another★Gamer said:
Yea, its early in the morning so its a little obvious i'll make mistakes.
Well your welcome to disagree, i'm not forcing my opinion on you or anyone just stating what I think.
There is no finished CM ROM but stable I honestly think the latest CM9 build is stable for daily use and not so good, lol CM9 runs graphic heavy games a whole lot better than GB even when its OC.
Oh yes GB is much much smoother and better than ICS and JB, sigh. There are already good GB ROMs for the SGW so is it such a big deal that someone wants to drop making CM7 and start doing the newest CM10 for our phone its their choice and if I had skills I rather take my shot and making CM9 and CM10 for our phone better rather than stick with ye old CM7.
Click to expand...
Click to collapse
Agreed. I just can say, " go for the CM10". I want to live the future not the past...
Sent from my GT-I8150 using xda premium
Actually, I'm supporting the development of CM9 and CM10 because 'in case of' the ROM becomes standard, I don't have to learn it.
Take an example of the ye old Win XP
Nowadays, Windows 7 has become the new standard of the computing world (of Windows, obviously).
Yes, you can still make Windows XP compatible program (with more cost and testing) , but can you assure that your program (which is made in .. say Win 7 with .NET Framework 3.5 / 4) could run w/o prob in Windows XP while your program works seamlessly in Win 7?
My point here is that we have to take measure on which ROM has brighter future? Will GB be updated again, with more fantastic feature, or will ICS and JB got them?
The problem is that there will be a hell lot of bugs, maybe even a brick... So when I try a new ROM, best I wait till it has only a few bugs that can be replaced with 3rd party apps (eg. Fm radio)
What do you think?
Sent from my Samsung Galaxy W (GT-I8150) with CM9 Alpha 6.
there will be a hell lot of bugs
Click to expand...
Click to collapse
Yeah, bug may exists but that been always a good news if someone try port rom for us!
at least we have a good starting point, cm9 which can be considered as fully working now :good:
Well, If he's really going to port CM10 for us, I hope he knows that may need to rewrite all the drivers again, like in ICS. And I remember he said in CM7 port topic that he doesn't know very much about kernel and drivers development, Oisis was helping him. I thought he should finish CM7 first, but If he consider better to start CM10, so let's go. I'll try to start studying better of kernel development for helping'em out. Like arco's said before, our community has an lack of kernel developers.
fredamsouza said:
Well, If he's really going to port CM10 for us, I hope he knows that may need to rewrite all the drivers again, like in ICS. And I remember he said in CM7 port topic that he doesn't know very much about kernel and drivers development, Oisis was helping him. I thought he should finish CM7 first, but If he consider better to start CM10, so let's go. I'll try to start studying better of kernel development for helping'em out. Like arco's said before, our community has an lack of kernel developers.
Click to expand...
Click to collapse
Yeah we need all the support we can get (says the guy who doesn't know a thing about kernels and stuff)...
Sent from my Samsung Galaxy W (GT-I8150) with CM9 Alpha 6.
iDelta said:
The problem is that there will be a hell lot of bugs, maybe even a brick... So when I try a new ROM, best I wait till it has only a few bugs that can be replaced with 3rd party apps (eg. Fm radio)
What do you think?
Sent from my Samsung Galaxy W (GT-I8150) with CM9 Alpha 6.
Click to expand...
Click to collapse
Arco encounters 2 hard bricks + several soft bricks when porting CM9
fredamsouza said:
Well, If he's really going to port CM10 for us, I hope he knows that may need to rewrite all the drivers again, like in ICS. And I remember he said in CM7 port topic that he doesn't know very much about kernel and drivers development, Oisis was helping him. I thought he should finish CM7 first, but If he consider better to start CM10, so let's go. I'll try to start studying better of kernel development for helping'em out. Like arco's said before, our community has an lack of kernel developers.
Click to expand...
Click to collapse
It's easier than upgrade from gb to ics. I don't know much about writing driver so i think i will make a bootable cm10 and the rest is for others developer
bangprovn said:
It's easier than upgrade from gb to ics. I don't know much about writing driver so i think i will make a bootable cm10 and the rest is for others developer
Click to expand...
Click to collapse
hope you will success ～
Its the right decision, in my opinion - working on a Gingerbread-ROM does not make any sense at the moment - From features to smoothness, ICS is by far the better choice. Although RAM is a bottleneck for some purposes on the Galaxy W, the device as a whole has enough power to profit from the enhancements that came with ICS and JB.
@bangprovn, would you please release your CM7 source code/repo over github or other repos hosting share with maybe some note howto compile it, I have try it but no luck, stuck on brunch ancora command.
It says there is no ancora device code or sumtim like that
On ur cm7 threat osiris had some patch 4 wifi driver, but I'm sure there are some config on device.mk should be aligned correctly, and I think I could learn easily read ur porting process than I have to start from zero, with your mentoring maybe.
Sorry for my bad english
i am exciting～～ for cm10
I'm really looking forward to this!!
bangprovn said:
It's easier than upgrade from gb to ics. I don't know much about writing driver so i think i will make a bootable cm10 and the rest is for others developer
Click to expand...
Click to collapse
This will be a powerhouse and fast development in CM10 for our phone. A period of 3-4 months, we have a stable CM ROM.
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