http://www.androidcentral.com/android-403-source-code-being-pushed-aosp#comments
how does this affect the build of ics for the g2x?
Motorola Xoom was in their. Tegra 2 device... interested for sure.
Android 4.0.3 kernel sources pushed
https://groups.google.com/group/android-building/msg/ff4e97808535b396?pli=1
all this could be old news. the devs might be one step ahead on this. i just want to help out as much as i can. i hate not having any news on the devs work. i still love what you guys done so far. dont give up and dont let it die.
Xoom has a 4.0.3 port.
Xoom hw is not the same. Not the same board
Sent from my LG-P999 using Tapatalk
well if this post has nothing to offer to the build of ics for the g2x can the mod. please delete this post. i dont need this to take up space. thanks
i was under the impression that the source code for the tegra 2 kernel, and not the source code for ics itself was the issue.
Thats not entirely correct. ICS changed the way certain interfaces behaved especially HW accelerated graphics. Under Gingerbread, the system expected round peg and the nVidia blob provided round peg.
The problem is now ICS wants square peg. The blob we have only ever provides round peg.
There were three potential solutions to this problem:
1) nVidia releases source code and developers update as needed. This is how development works on the Qualcomm and TI driven devices which are basically fully open. This is also why you see old as dirt devices like the G1 updated far beyond their last "official" ROM.
2) nVidia releases an ICS compatible blob. This is what we can hopefully pull from the Xoom tree. It leaves us dependent on nVidia for "substantial" updates, like when interfaces change but would probably allow for a number of updates. There are Gingerbread ROMs that use Froyo kernels as an example.
3) Developers rewrite the interfaces in question to accept round peg. In the case of HW acceleration, this would mean back-porting the Gingerbread method of HW acceleration. It would work but would be labor intensive to maintain and may introduce instability or comparability issues in apps that specifically expect the ICS method. Think, for example, Swype talking about having to rewrite the keyboard to accomidate the way the screen is presented to programs.
I am not a ROM developer but I have college level programming experience and a pretty decent understanding of the technical issues here.
nVidia was never going to release their source. They have always maintained their source code as confidential and proprietary and as far as I know they've not released source for anything as far back as the Riva TNT.
In other product lines, the reason for this is that they differentiate some features through software. In essence the HW is capable of more and the software locks it away. Back in the day there was a GeForce to Quadro softmod that drastically increased performance in some programs.
I don't really know if thats the case here, nobody does. nVidia only wants you to access what they sell you not what the HW is capable of.
Personally, I hope the blob for the Xoom helps the CM team. I imagine we will know shortly.
rayman2k1 said:
i was under the impression that the source code for the tegra 2 kernel, and not the source code for ics itself was the issue.
Click to expand...
Click to collapse
Sent from my LG-P999 using Tapatalk
That was the most intelligent and courteous explanation I have ever read here on xda. Now watch all the omniscient people strike it down.
Sent from my LG-P999 using xda premium
TerryMathews said:
Thats not entirely correct. ICS changed the way certain interfaces behaved especially HW accelerated graphics. Under Gingerbread, the system expected round peg and the nVidia blob provided round peg.
The problem is now ICS wants square peg. The blob we have only ever provides round peg.
There were three potential solutions to this problem:
1) nVidia releases source code and developers update as needed. This is how development works on the Qualcomm and TI driven devices which are basically fully open. This is also why you see old as dirt devices like the G1 updated far beyond their last "official" ROM.
2) nVidia releases an ICS compatible blob. This is what we can hopefully pull from the Xoom tree. It leaves us dependent on nVidia for "substantial" updates, like when interfaces change but would probably allow for a number of updates. There are Gingerbread ROMs that use Froyo kernels as an example.
3) Developers rewrite the interfaces in question to accept round peg. In the case of HW acceleration, this would mean back-porting the Gingerbread method of HW acceleration. It would work but would be labor intensive to maintain and may introduce instability or comparability issues in apps that specifically expect the ICS method. Think, for example, Swype talking about having to rewrite the keyboard to accomidate the way the screen is presented to programs.
I am not a ROM developer but I have college level programming experience and a pretty decent understanding of the technical issues here.
nVidia was never going to release their source. They have always maintained their source code as confidential and proprietary and as far as I know they've not released source for anything as far back as the Riva TNT.
In other product lines, the reason for this is that they differentiate some features through software. In essence the HW is capable of more and the software locks it away. Back in the day there was a GeForce to Quadro softmod that drastically increased performance in some programs.
I don't really know if thats the case here, nobody does. nVidia only wants you to access what they sell you not what the HW is capable of.
Personally, I hope the blob for the Xoom helps the CM team. I imagine we will know shortly.
Sent from my LG-P999 using Tapatalk
Click to expand...
Click to collapse
Absolutely right. I don't have any hope at all regarding the Xoom blobs though, as they are not the same board type, and thus likely will not be compatible.
Sent from my LG-P999 using Tapatalk
You are totally right but nvidia is planning to release the drivers for tegra 2 platform in Q1 of 2012, if you haven't heard it yet. Here is the link:
http://forums.developer.nvidia.com/devforum/discussion/comment/3236?Sort=popular
Regards
Sent from my Optimus 2X using Tapatalk
Missing Dateline
ironman159 said:
You are totally right but nvidia is planning to release the drivers for tegra 2 platform in Q1 of 2012, if you haven't heard it yet. Here is the link:
http://forums.developer.nvidia.com/devforum/discussion/comment/3236?Sort=popular
Regards
Sent from my Optimus 2X using Tapatalk
Click to expand...
Click to collapse
I dont see any dateline regarding nVidia will release tegra2 drivers in Q1 of 2012 here (http://forums.developer.nvidia.com/devforum/discussion/comment/3236?Sort=popular). Am I missing sth?
It says early next year.
Sent from my Optimus 2X using Tapatalk
ironman159 said:
It says early next year.
Sent from my Optimus 2X using Tapatalk
Click to expand...
Click to collapse
+1 early could mean the first half of 2012.
NVIDIA NEVER AGAIN!
By Summer.
We will have cm9 and other ICS roms probaly by the end of January-mid February. LG and Nvidia could learn much from our talented devs that do all this for free and the joy of it.
Drivers Release?
IF Nvidia is going to release the necessary drivers, does this mean we might see our camera features back again on future ICS roms?
Chinese281 said:
IF Nvidia is going to release the necessary drivers, does this mean we might see our camera features back again on future ICS roms?
Click to expand...
Click to collapse
This might mean nothing unless lg releases there stuff too. Lg changed some things for this device. I'm not sure but I think lg did something weird to get the tegra 2 to work with the board they designed. nvidia said lg needs to release there changes too for what we are trying to do.
Sent from my CM 7.1.0 G2x using XDA app
Hey guys, I might be hopping over to the $29 monthly WIND Mobile plan pretty soon, so I'm looking at the handsets they have and I pretty much narrowed it down to the G2X and the Nexus S. I'm currently using a Samsung Galaxy S GT-I9000 which is really similar to the Nexus S in terms of hardware, so I'm hoping that you folks could shed some light on some of the questions I have about WIND and the G2X
1. How are the custom ROMS for the G2X? I love being able to flash custom ROMS like MIUI and CM7, so I'm wondering if there are custom ROMS out there for the G2X that provides full functionality (ie. smooth video recording, etc)?
2. On my GT-I9000, 512 MB of RAM on 2.3.x Gingerbread seems to hinder the home screen smoothness and performance unless tweaks (scripts, LMK kernels, etc) are applied and even then, it's not always 100% smooth. Does the G2X suffer from the same issue?
3. Some of most impressive specs on paper for the G2X are the camera and the dual core processor, do they live up to the initial hype?
4. If anyone's has/had a Samsung Galaxy S GT-I9000 (and used the custom ROM or stock ROM with lag fix), how does the G2X compare with the SGS?
5. Are there any phone-specific precautions I should keep in mind when rooting/flashing this phone (eg. bootloader locks, etc)?
I'd appreciate any advice/input from owners of the G2X, thanks!
To answer some of your questions..
1. Eaglesblood,latest cm7 nightlies using faux latest cm ds kernel are BOSS! I am using latest 2.3.7 eaglesblood rom and everything just works perfect! I have tried miui roms and they are great also(thanks whitehawx for all the ports)
2. Compared to the i9000 the g2x smokes it even tho it has the same ammount of ram, let me just say this... i have 600+ apps/games and dont experience any lag whatsoever! No scripts needed!
3. Yes!
5. Just make sure you install lg drivers/ apx drivers first, install CWM thru tgagunmans excellent nvflash guide(never thru rom manager since it's a fake flash) Then just flash a rooted rom thru recovery, or you can also oneclick root. G2x doesnt have a bootloader like htc devices(wish it did tho because it would make flashing radio/baseband soo much easier compared to using lg's crappy software/kdz method).
Also..
Since the nexus s already has ICS it might also be an attractive option but since it seems your wanting input on g2x, once cm9 is publicly released for our phones it will be an even more amazing device since it is the OS our G2x's should have started with from the beginning(hw acceleration,multicore support, improved ui,etc)
Sent from my LG-P999 using xda premium
The camera software was changed in Gingerbread. There are a few options gone from the Froyo LG Cam. Also added more compression to the pics taken. Not as sharp and clear.
Wait until ICS is available fo the G2X then decide. If it's the G2X, buy a 2nd hand one, they,re a lot cheaper.
I love the phone but to be honest, the camera sucks ever since LG removed the new camera and the modded ones don't work the same. Not a problem for me though, I don't use it.
Sent from my LG-P999 using xda premium
Thanks for the input guys,
Is the stock firmware from LG really as bad as everyone says it is?
adslee said:
Thanks for the input guys,
Is the stock firmware from LG really as bad as everyone says it is?
Click to expand...
Click to collapse
It wasn't too bad on Wind mobile. But it's a lot more enjoyable once I rooted and upgraded to Gingerbread on EaglesBlood rom.
Hi everyone,
Today I was just reading about Android 5.0 Key Lime Pie, and I couldn't help but wonder if it will be ported to Sensation XE.
An upgrade from Gingerbread (2.3.4) to Ice Cream Sandwich/Jelly Bean required a corresponding firmware upgrade, which was "conveniently" released by HTC. As far as I know, nobody is invloved in firmware development for Sensation XE (for obvious reasons, I suppose), and the next K release on Android will most likely require new firmware which, let's be honest, HTC is quite unlikely to release.
So, what are your thoughts on Key Lime Pie being ported to Sensation XE?
More reading!
Well there was no firmware release for jb on the sensation. So ur using ICS firmware on jb. The same will follow, correct me if wrong.
Sent from my T-Mobile myTouch 4G using xda premium
mymeatb18 said:
Well there was no firmware release for jb on the sensation. So ur using ICS firmware on jb. The same will follow, correct me if wrong.
Sent from my T-Mobile myTouch 4G using xda premium
Click to expand...
Click to collapse
Well, JB could run on the same firmware as ICS. I'm guessing it was because it was in some ways similar to ics (ics (4.0) to(4.1/2/3)).
However ics cannot run on gingerbread firmware. Isn't it likely that Key Lime Pie will need need a new firmware too. I mean it's supposed to be a major upgrade.
Yeah I guess I see what u mean. But I still don't think ICS and jb are similar enough to justify the use of the same firmware. Then again I don't know that much detail about the developmental level so u could very much be right.
All we can do is wait and see I guess. Hopefully there is no extra firmware needed though.
Honeycomb and ICS look similar and are 3.0 and 4.0
Froyo and GB look similar as well and are 2.2 and 2.3
So hard to say really
Sent from my T-Mobile myTouch 4G using xda premium[/QUOTE]
Sent from my T-Mobile myTouch 4G using xda premium
mymeatb18 said:
Yeah I guess I see what u mean. But I still don't think ICS and jb are similar enough to justify the use of the same firmware. Then again I don't know that much detail about the developmental level so u could very much be right.
All we can do is wait and see I guess. Hopefully there is no extra firmware needed though.
Sent from my T-Mobile myTouch 4G using xda premium
---------- Post added at 12:50 PM ---------- Previous post was at 12:46 PM ----------
Sent from my T-Mobile myTouch 4G using xda premium
Click to expand...
Click to collapse
Well I really hope Sensation gets Key Lime Pie. Fingers Crossed
Huh... tough one.
We just recently got the working JB (Sense) rom thanx to SebastianFM's kernel (Search for Revelation rom) which is great for th efirst release.
and as far as I know it was a preatty tough task to accomplish.
So, I belive, that IF we get the Key Lime Pie we'll get it firs in AOKP or CM rom's... not that sure about the Sense based roms.
But like you said... fingers crossed. :fingers-crossed:
As far as I know, it's possible, as devices which did not get official ICS upgrades were upgraded and are working well (for example, the i9000 Galaxy S, and many even older devices (My sister's old Optimus One runs JB, albeit it has it's own bugs)). The fact HTC released a new firmware for ICS certainly helped, but it was not necessary, because when you port a ROM to your device, you build it to run on a certain firmware. If we wouldn't have a new firmware, devs would probably port it to the older firmware version.
What's happening with JB and SebastianFM's kernel is that since ICS, Google began transition to ION memory management and drivers, instead of PMEM (which was used on Qualcomm devices, and each chip manufacturer had it's own tech). Since JB, ION became the preffered solution, and that's why AOSP based roms such as cyanogenmod and AOKP could run, but Sense 4+ (android 4.1) couldn't, as it requires ION drivers on the Kernel level.
So what I believe, it will be possible. newer firmware isn't necessary, as when a ROM is ported, it's made to work with the existing firmware. And for the kernel related, I wan't to believe that once we have full ION drivers, problems will be easier to solve, but that is for the future.
I'm not a dev, that's just my understanding of things.
astar26 said:
As far as I know, it's possible, as devices which did not get official ICS upgrades were upgraded and are working well (for example, the i9000 Galaxy S, and many even older devices (My sister's old Optimus One runs JB, albeit it has it's own bugs)). The fact HTC released a new firmware for ICS certainly helped, but it was not necessary, because when you port a ROM to your device, you build it to run on a certain firmware. If we wouldn't have a new firmware, devs would probably port it to the older firmware version.
What's happening with JB and SebastianFM's kernel is that since ICS, Google began transition to ION memory management and drivers, instead of PMEM (which was used on Qualcomm devices, and each chip manufacturer had it's own tech). Since JB, ION became the preffered solution, and that's why AOSP based roms such as cyanogenmod and AOKP could run, but Sense 4+ (android 4.1) couldn't, as it requires ION drivers on the Kernel level.
So what I believe, it will be possible. newer firmware isn't necessary, as when a ROM is ported, it's made to work with the existing firmware. And for the kernel related, I wan't to believe that once we have full ION drivers, problems will be easier to solve, but that is for the future.
I'm not a dev, that's just my understanding of things.
Click to expand...
Click to collapse
Yes, if the sensation does indeed get android 5.0 key like pie, then it is pretty much going to be AOSP first, no sense version. Also, I don't know anything about key lime pie, but we probably need that 3.4 kernel with ION to work on AOSP based ROMs first.
Not to be skeptical, but I think there's not really a chance that key lime pie could run on a pmem kernel. Plus, the Sensation's ram is only 768 megabytes, so some type of more advanced memory allocator is probably required.
Sent from my Ouya
AndroidSupporter318 said:
Yes, if the sensation does indeed get android 5.0 key like pie, then it is pretty much going to be AOSP first, no sense version. Also, I don't know anything about key lime pie, but we probably need that 3.4 kernel with ION to work on AOSP based ROMs first.
Not to be skeptical, but I think there's not really a chance that key lime pie could run on a pmem kernel. Plus, the Sensation's ram is only 768 megabytes, so some type of more advanced memory allocator is probably required.
Sent from my Ouya
Click to expand...
Click to collapse
As things are going now, the chances of having a Sense KLP ROM on our Sensation are low, as the One S currently won't get any more updates, and ROMs are ported from a version of it (ville c2).
And for the low RAM, I don't think it's a problem yet, as devices with 512MB run JB quite well. but a better memory management is always good.
astar26 said:
As things are going now, the chances of having a Sense KLP ROM on our Sensation are low, as the One S currently won't get any more updates, and ROMs are ported from a version of it (ville c2).
And for the low RAM, I don't think it's a problem yet, as devices with 512MB run JB quite well. but a better memory management is always good.
Click to expand...
Click to collapse
I don't think that RAM requirements are going to be a problem at all.
Google has already said that it wants android to run equally well on smartphones tablets as well as low end phones, and though Sensation XE may not be high end, it sure as hell isn't low end. So hardware wise, KLP shouldn't have any issued on Sensation.
For example read http://au.ibtimes.com/articles/486414/20130704/android-5-0-key-lime-pie-k.htm
Andoir KLP for a wider set of devices
Far_SighT said:
Hi everyone,
Today I was just reading about Android 5.0 Key Lime Pie, and I couldn't help but wonder if it will be ported to Sensation XE.
An upgrade from Gingerbread (2.3.4) to Ice Cream Sandwich/Jelly Bean required a corresponding firmware upgrade, which was "conveniently" released by HTC. As far as I know, nobody is invloved in firmware development for Sensation XE (for obvious reasons, I suppose), and the next K release on Android will most likely require new firmware which, let's be honest, HTC is quite unlikely to release.
So, what are your thoughts on Key Lime Pie being ported to Sensation XE?
More reading!
Click to expand...
Click to collapse
a while ago i was researching about Android KLP..it just came out of my mind..and i have read that this version will support a wider range of devices, including even low-end smartphones and those with 512MB of RAM. So it's most likely our Senny can cope up to it, as it is said that Android 5 will be optimized to be lighter and built for performance and battery efficiency. it is rumored that this version will make the device smoother, and consume less RAM to make it more quick in performance. i dunno how google will do it but i hopethat said features will materialize and our Senny can taste the new android..it will be a huge leap from 4.0.3 to 5.0. so flashaholics like me, keep a backup of your stock roms! let's just hope HTC won't deny us old phone users this major update.
ichigo_kurosaki said:
a while ago i was researching about Android KLP..it just came out of my mind..and i have read that this version will support a wider range of devices, including even low-end smartphones and those with 512MB of RAM. So it's most likely our Senny can cope up to it, as it is said that Android 5 will be optimized to be lighter and built for performance and battery efficiency. it is rumored that this version will make the device smoother, and consume less RAM to make it more quick in performance. i dunno how google will do it but i hopethat said features will materialize and our Senny can taste the new android..it will be a huge leap from 4.0.3 to 5.0. so flashaholics like me, keep a backup of your stock roms! let's just hope HTC won't deny us old phone users this major update.
Click to expand...
Click to collapse
HTC isn't going to update the Sensation XE. Hell, they only agreed to update the One S after so much protest.
But it would be nice if KLP comes to Sensation XE.
Happy to help.
ichigo_kurosaki said:
a while ago i was researching about Android KLP..it just came out of my mind..and i have read that this version will support a wider range of devices, including even low-end smartphones and those with 512MB of RAM. So it's most likely our Senny can cope up to it, as it is said that Android 5 will be optimized to be lighter and built for performance and battery efficiency. it is rumored that this version will make the device smoother, and consume less RAM to make it more quick in performance. i dunno how google will do it but i hopethat said features will materialize and our Senny can taste the new android..it will be a huge leap from 4.0.3 to 5.0. so flashaholics like me, keep a backup of your stock roms! let's just hope HTC won't deny us old phone users this major update.
Click to expand...
Click to collapse
HTC already did deny us, after stopping updates, they won't update a 2-year old device. I didn't find any official confirmation for the One S Sense 5 update, but from what I found, it was explained that only the S4 powered One S will be updated, due to lack of software support from Qualcomm to the S3 platform. It's quite hard to believe HTC would make that effort of updating such old device. After all, their interest is to sell new phones, and 2 years are about the average time for an upgrade (personally I'm probably keeping my device for at least the next year before even considering an upgrade).
Maybe as an AOSP port or CM, but I don't think we will get Sensed KLP, and I don't think we'll even get it ported.
astar26 said:
HTC already did deny us, after stopping updates, they won't update a 2-year old device. I didn't find any official confirmation for the One S Sense 5 update, but from what I found, it was explained that only the S4 powered One S will be updated, due to lack of software support from Qualcomm to the S3 platform. It's quite hard to believe HTC would make that effort of updating such old device. After all, their interest is to sell new phones, and 2 years are about the average time for an upgrade (personally I'm probably keeping my device for at least the next year before even considering an upgrade).
Maybe as an AOSP port or CM, but I don't think we will get Sensed KLP, and I don't think we'll even get it ported.
Click to expand...
Click to collapse
Too bad that even the One S HTC release wouldn't do us any good. But I really hope that at least KLP AOSP roms can run on current firmware.
Happy to help.
My previous device (HTC WILDFIRE) last official relase was Froyo but it runned gb ics and jb (very slow because lack of gpu and very very bad processor) but i hope we can enjoy KLP on our sensation
Sent from my HTC Sensation Z710e with Tapatalk 4
Press that thanks button if i helped?
---------- Post added at 06:36 PM ---------- Previous post was at 06:29 PM ----------
AndroidSupporter318 said:
Yes, if the sensation does indeed get android 5.0 key like pie, then it is pretty much going to be AOSP first, no sense version. Also, I don't know anything about key lime pie, but we probably need that 3.4 kernel with ION to work on AOSP based ROMs first.
Not to be skeptical, but I think there's not really a chance that key lime pie could run on a pmem kernel. Plus, the Sensation's ram is only 768 megabytes, so some type of more advanced memory allocator is probably required.
Sent from my Ouya
Click to expand...
Click to collapse
KLP Will be able to run good on devices with 512mb ram
"Officials Said, to run Android 5.0 Key Lime Pie your device must have minimum 512MB ram and 1GB for smooth running. "
( http://www.techcodez.com/android-5-0-key-lime-pie/ )
Sent from my HTC Sensation Z710e with Tapatalk 4
Press that thanks button if i helped?
Sensation are not supported now so... in my opinion they are not in future
vito.exe said:
Sensation are not supported now so... in my opinion they are not in future
Click to expand...
Click to collapse
Buddy, you needn't say that. (Everybody's ) Sensation XE might be old, but that doesn't mean it's useless.
If you have any doubts see http://forum.xda-developers.com/showthread.php?t=2391968.
Besides KLP requirements have been confirmed. Sensation can definately run KLP. I just have concerns if the current ics/jb firmware can support it, because firmware updates come from htc only.
Far_SighT said:
Buddy, you needn't say that. (Everybody's ) Sensation XE might be old, but that doesn't mean it's useless.
If you have any doubts see http://forum.xda-developers.com/showthread.php?t=2391968.
Besides KLP requirements have been confirmed. Sensation can definately run KLP. I just have concerns if the current ics/jb firmware can support it, because firmware updates come from htc only.
Click to expand...
Click to collapse
agree :good:
Check out the specs for an upcoming phone, the htc Zara. Lots of similar specs to the sensation. It comes with jelly bean but since htc usually gives at least one os update, it's not hard to imagine that phone with key lime pie some day.
Sent from my Nexus 7 using xda app-developers app
funkymonkey_01 said:
Check out the specs for an upcoming phone, the htc Zara. Lots of similar specs to the sensation. It comes with jelly bean but since htc usually gives at least one os update, it's not hard to imagine that phone with key lime pie some day.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
but it has different emmc and gpu chip