Related
I may be the only one interested in this, and I know its set for froyo 2.2 and not sure if its possible but is there no way to port this back one version? Maybe make it work for us?
I really like the idea and would be disappointed to have to wait the loooooooooong time before 2.2 is ported to G1.
no it uses the new pushy mc jig from froyo
probably could back port the whole framework, but seems like a wast ogf time to me
atantekeier said:
I may be the only one interested in this, and I know its set for froyo 2.2 and not sure if its possible but is there no way to port this back one version? Maybe make it work for us?
I really like the idea and would be disappointed to have to wait the loooooooooong time before 2.2 is ported to G1.
Click to expand...
Click to collapse
How do you know it will be such a long time?
Depending on the code changes between 2.1 and 2.2, it may be little more than trivial to get 2.2 running.
Also, I suggest that the first step required in either backporting or building a whole system would be to actually wait for the availability of the source code. Then we judge what would be a more efficient use of time -- building a whole system or backporting chunks of it.
2.2 will support the ION, so in turn, it will support the Dream. We just have to WAIT for it, people.
Mod edit: not dev related, moved to q&a
Just a thought: during the google io presentation of google TV they make a presentation of this feature with the google box in 2.1. So I don't know if the sdk or the source code is published but can't we use that to make it working with eclair roms?
PS: here at 1:30
Time is relative here, by the time a new update is released from modders porting it to another much older phone version a new version is almost ready to be released.
This is not a bad thing and Im not talking down about it ether. But was simply asking the question if it would take too much effort to get just that .apk to work for even 2.1 that is now very stable on the G1.
2.2 was just released, and it will probably take a while to get it stable, to the point where 2.0 or 2.1 is now for the G1 anyways.
I just really like the chrome to phone and think its a super idea. Maybe I'm a bit impatient too.
Want to dig through 2.3 and see what all the fuss is about for yourself? Well, you're in luck, because Gingerbread has just hit the Android Open Source Project's repository, which means you can set up your machine to download the code. It's great news for hardware companies that don't care to get Google's certification to include Android Market access -- but it's also great news for casual and serious hackers alike who are looking to craft some seriously wild, wacky custom ROMs. So, what are you waiting for? Get to it, folks.
http://www.engadget.com/2010/12/17/android-2-3-gingerbreads-source-code-now-available/
I will be trying to grab a copy and upload it here due to a high server load at Google.
Here is to hoping that dexter comes through and ports this for us, otherwise we can just wait until CyanogenMod upgrades to 2.3 .
With my limited understanding it looks like we [should] be able to get a more usable "ROM" out of 2.3 (with a 2.2.1 kernel) then that of 2.2 (with a 2.1 kernel) as it looks like the only kernel changes are to support hardware that the Milestone doesn't have.
But like I said, I know nothing .
DannyDroid said:
With my limited understanding it looks like we [should] be able to get a more usable "ROM" out of 2.3 (with a 2.2.1 kernel) then that of 2.2 (with a 2.1 kernel) as it looks like the only kernel changes are to support hardware that the Milestone doesn't have.
But like I said, I know nothing .
Click to expand...
Click to collapse
Stop doing conclusions like this one is since we discussed about this in Android 2.3 topic.
Like I said, twice in my post, I have no limited understanding when it comes to Android.
I haven't read the 2.3 topic.
I don't succeed to download the source code 2.3 from the android site can someone help me? have you a direct link?
So CM7 was a stellar success for our tiny lil device called Tattoo.
Now that CM7 is over, we'll are eagerly waiting for CM9. I posted this thread to know if Tattoo is going to be supported in the CM9 builds. If anyone of you has an idea of what is going on, you can reply here. Also you can use this thread for dev purposes.
Others here, you can list out what features you want to see on out Tattoos running CM9. This can come of great help to the devs until the actual thread comes up.
So when many devices have got early CM9 builds, why not us? arco68 and KalimochoAz, you there?
The CyanogenMod team already announced that one phone which will not get the upgrade is the Motorola Droid because of it's outdated hardware. You know, Droid is really similar to Tattoo specwise. Same CPU specs, same RAM amount, same internal memory.....
You draw the conclusions.
pretty bleak future for us indeed. but the hero and the G1 are running early builds of it already. so if G1 can do, why not Tattoo?
sunitknandi said:
pretty bleak future for us indeed. but the hero and the G1 are running early builds of it already. so if G1 can do, why not Tattoo?
Click to expand...
Click to collapse
Any hope for us. Be patient. They only write about Droid1: http://www.cyanogenmod.com/blog/cm9-progress-update
BilboPC said:
Any hope for us. Be patient. They only write about Droid1: http://www.cyanogenmod.com/blog/cm9-progress-update
Click to expand...
Click to collapse
This blog post pretty much confirms that we won't be getting CM9.
Our goal is to provide continued support to all CM7 devices back to the QSD8250 series of devices such as the Nexus One.
Click to expand...
Click to collapse
Our device is MUCH less-powerful than the QSD8250, which is a 1.0-1.2GHz CPU and Adreno 200 GPU System-on-a-Chip.
if that is true, wildfire wont get it too.
My guess it it will run. But should be optimized heavily for a smooth experience.
Sent from my HTC Tattoo using XDA App
I'm afraid the low resolution will be the show stopper there.
Maybe possible but it will be light version of ICS a few of the ingredients may be removed.
The screen is 2.8" n this is maybe the drawback...
I have installed ICS on G1. Its horrible ROM, Very Laggy and still needs lot of development for smoother experience. They haven't fixed the rotation problems yet. It looks to me Tatto0 will have a hard time with CM 9 because of its lower quality hardwares.
Tattoo is a 2 years old phone
Once we made it 2.1/2.2
It great already
And now we even have 2.3
What are we still asking for
As google told before
4.0is for high end
So let's enjoy the extra bonus that we get
Sent from my HTC Sensation XE with Beats Audio Z715e using XDA App
There was a Christmas gift to buzz community from Arco
http://forum.xda-developers.com/showpost.php?p=20639586&postcount=61
which i think is a good news for Tattoo as well in terms of CM9
i still have hope!
it might not be a perfect version of android 4, but at least we can try and have fun a little bit while we wait for next year's christmas for a new phone!!
Look at this
http://www.youtube.com/watch?v=Ym4A82ft5pw
It's ICS running on htc g1, the first android phone! I hope we can run it also on our tattoo
mattia29 said:
Look at this
http://www.youtube.com/watch?v=Ym4A82ft5pw
It's ICS running on htc g1, the first android phone! I hope we can run it also on our tattoo
Click to expand...
Click to collapse
Yes, it's running, but as you can see it's too slow, really.
Yes but tattoo has a little better specs than G1
Hey all,
If no-one is looking at porting CM9 to Tattoo, I could have an indicative look at doing it; no promises though; as I am doing it for HD2 at the moment, where I am spending all my time
I may have a go in a few days.
Although I may need some assistance with drivers and kernel later on
arif-ali said:
Hey all,
If no-one is looking at porting CM9 to Tattoo, I could have an indicative look at doing it; no promises though; as I am doing it for HD2 at the moment, where I am spending all my time
I may have a go in a few days.
Although I may need some assistance with drivers and kernel later on
Click to expand...
Click to collapse
That's awesome, man. I would done it if I had knowlege
arif-ali said:
Hey all,
If no-one is looking at porting CM9 to Tattoo, I could have an indicative look at doing it; no promises though; as I am doing it for HD2 at the moment, where I am spending all my time
I may have a go in a few days.
Although I may need some assistance with drivers and kernel later on
Click to expand...
Click to collapse
Please do it if u have time.
Update on compilation
Hi all,
Everything I do is all open, so you will see what I have done; this also gives others the chance to contribute
If someone wants to see my progress, then you can go to the following git repo
https://github.com/arif-ali/android_device_htc_click
and when I have a build it will be located here
http://cyanogenmod.arif-ali.co.uk/rom/test
So far quite a bit compiles, working on the wpa_supplicant part now. Looks like it may be a hack or need to look somewhere else.
I've had the Tattoo for 2 years now, but don't really know the HW much, so much research will be required. I've just installed nfinityGB, as and when arco built it.
If someone can give any input, it may speed up my work; and it will be appreciated.
Edit 1:
* Got passed the wifi, just got the drivers from gingerbread (for my notes)
Code:
cd system/wlan
git clone git://github.com/CyanogenMod/android_system_wlan_ti.git -b gingerbread
mv android_system_wlan_ti ti
sed -i s/LOCAL_MODULE_TAGS.*/LOCAL_MODULE_TAGS\ :=\ optional/g system/wlan/ti/sta_dk_4_0_4_32/config/Android.mk
* Need http://forum.xda-developers.com/showpost.php?p=20737947&postcount=27 for compilation as well
Code:
unzip ../webrtc.zip -d external/webrtc/
Edit 2:
Good News; first compile done.
Bad News; it's 4am in the morning, and I can't be bothered to test
I have no idea if it is going to work or not, and if someone is really adventurous, then feel free to try flashing the file from the following URL in about 20 mins i.e. better to try 04:30 GMT to be on the safe side
http://cyanogenmod.arif-ali.co.uk/rom/test/update-cm9-click-20120101.zip
system is going to be 162M, and gapps can be downloaded from http://cyanogenmod.arif-ali.co.uk/misc/gapps-ics-20111128.zip
Personally, I won't be able to test until tomorrow now
Edit 3:
NVM, this won't work, our system is only 150M; I will give it another go later
I have been working on porting CM9 to the VS910. So far I have gotten it to boot to the lock screen.
What Works
Boot animation
Lock screen
SurfaceFlinger
logcat/adb shell
3d accel is half working. I have gotten SurfaceFlinger to load up and interface the proprietary drivers (from GB) correctly, but HardwareRenderer (java framework) fails because the drivers don't give up a valid config.
What Doesn't Work
Touch screen
HardwareRenderer (fails because HardwareRenderer.chooseEglConfig() returns null value)
Everything else
Currently this ROM is totally unusuable for anything except for development. At this point, I do believe it is possible to get CM9 running, but it will take a good bit of developer effort. It would be helpful for any other developers around here to give some insight on the errors that come up in the adb logs.
How To Build
Follow Google's instructions for setting up a Linux system or VM for Android AOSP building
Follow CM9 build instructions up to brunch command
git clone git://github.com/andyichr/makerom.git to a location, such as ~/android/makerom
Overlay the files in ~/android/makerom/cm9-system/overlay onto the cm9/system directory (this adds vs910 brunch)
Adjust values in makerom.sh to match your own paths (MAKE SURE TO POINT IT AT A VALID KERNEL --I didn't include instructions for building a kernel)
Adjust values in makecm9.sh to match your own paths
Run ~/android/makerom/makecm9.sh to build cm9 (this takes a long time, depending on your system)
If build is successful, run ~/makerom/makerom.sh which will output a ROM which may be flashed to the device for testing
This is very rough work, but it proves that the basic parts of CM9/ICS do function on the Revolution. The cyanogenmod developers have already added some patches to the android source which allow ICS to run using video drivers from Gingerbread. This means it should be possible to get things working.
The current major problem with this ROM is that the HardwareRenderer does not initialize. Immediately after this, the main trebuchet process is killed and the system reboots itself after a while.
I will be happy to do what I can to support the process of porting CM9 to our phones. I read that a couple of other devs may be looking into porting CM7, but I think focusing on 9 might be more worth the effort, since we already have Gingerbread.
I have also attached a logcat to this post which should give developers some idea about what exactly is broken, which will lead to the first steps of debugging and porting.
Any interested developers should fork my repo on github (git://github.com/andyichr/makerom.git) which has the build scripts and patches.
That's about it for now. I very well may have left out some steps along the way. If you try to follow this process and it doesn't work out, let me know and I'll help you out.
ROM Download (very broken --only use for testing and development)
http://www.multiupload.com/GI0MLQYTE0 - Flash this if you want to see ICS boot to the lock screen or help test/debug. It's not useful for much else at this point.
We're getting there! I've already patched the android egl framework code slightly and built a kernel. CM team already patched frameworks/base for 2.3 video drivers. We'll patch what we have to to get this thing running! I am pretty busy but I will follow this thread and I hope for this to be a collaborative, transparent porting process! Good luck!
Nice, get with Mtmichaelson and Cubed, they are working on Cm9 also!
Sent from my VS910 4G using Tapatalk
Great! I saw in the CM7 thread that thecubed put up a git repo. I'm not sure exactly what his development plan is, but I'd be happy to fork his repo and trade patches, logs, etc. The more devs we have on this, the better... it's not a trivial task and I'm sure my wife hates me by now for spending so many hrs on it so far.
If I read correctly, thecubed just got a master repository set up for the revolution, so maybe the files that are needed could be lurking in there? I'll see if I can find the link and post it here.
Here's the link: https://github.com/thecubed
BLITZ ledded adshot nitro supercharged Gingerlution
I know in irc tonight cubed was talking about it. Guess they have to work on a few things but it's coming along. Wish I knew more so I could help out in this to. Guess I could be the Guinea pig.
Sent from my VS910 4G using Tapatalk
aichrist said:
Great! I saw in the CM7 thread that thecubed put up a git repo. I'm not sure exactly what his development plan is, but I'd be happy to fork his repo and trade patches, logs, etc. The more devs we have on this, the better... it's not a trivial task and I'm sure my wife hates me by now for spending so many hrs on it so far.
Click to expand...
Click to collapse
Awesome job so far! For a lot of things to work correctly, it's my understanding that you'll need a new kernel. For at least the touchscreen issues, you need the "idc" file in the "/system/usr/idc" directory (not sure if you have that or not, I didn't get a chance to check yet)
Either way, if you'd like to get in contact with me, hop on IRC and I'd be happy to answer any questions you may have.
Excellent work!
indyred99 said:
I know in irc tonight cubed was talking about it. Guess they have to work on a few things but it's coming along. Wish I knew more so I could help out in this to. Guess I could be the Guinea pig.
Sent from my VS910 4G using Tapatalk
Click to expand...
Click to collapse
Yeah I see thecube's repo at https://github.com/thecubed/android_device_lge_revolution. His CM files are a lot cleaner than mine... I just copied the crespo config and haven't had time to clean it up yet. I'll do some diffs of his vs mine and see about getting things merged. My github repo has some additional files so what I could do is replace my vs910 device folder with a fork of thecube's repo.
I'm not sure whether his files are for CM7 or CM9 (or if it doesn't matter). I'm new to CM porting, but I'm not new to linux or android app development.
thecubed said:
Awesome job so far! For a lot of things to work correctly, it's my understanding that you'll need a new kernel. For at least the touchscreen issues, you need the "idc" file in the "/system/usr/idc" directory (not sure if you have that or not, I didn't get a chance to check yet)
Either way, if you'd like to get in contact with me, hop on IRC and I'd be happy to answer any questions you may have.
Excellent work!
Click to expand...
Click to collapse
Thanks for the tip. I'll check that out. So far I've mainly been banging my head on getting the adreno205 drivers working, but it sure would be nice to have touch working. That'd be the next priority.
I'm tempted to switch of 3d acceleration but I am focusing on one thing at a time.
I'll hop on IRC. Which channel are you on specifically?
As always guys, I'm happy to assist in testing. Nor very knowledgeable on coding or porting, but I can definitely put my phone at risk
BLITZ ledded adshot nitro supercharged Gingerlution
wish I knew more about this stuff so I could help
keep up the great work!
crossing fingers, hoping I'll get the chance to start making themes for CM9!
aichrist said:
Thanks for the tip. I'll check that out. So far I've mainly been banging my head on getting the adreno205 drivers working, but it sure would be nice to have touch working. That'd be the next priority.
I'm tempted to switch of 3d acceleration but I am focusing on one thing at a time.
I'll hop on IRC. Which channel are you on specifically?
Click to expand...
Click to collapse
Head over to #lgrevolution and I'll be there as IOMonster.
Yep, for ICS we need a lot of work in the KGSL department in kernel for getting proper Adreno support working... Tiamat is working on adding the new KGSL/USB/Genlock support to his MSM7X30 repo here ( http://git.tiamat-dev.com/7x30/htc-kernel-msm7x30/ ) and after that we need to merge our kernel sources with his (boardfiles, includes, configs, etc)
Booting to lockscreen is great, but there's a LOT of work to be done before we can have a "working" ICS by any stretch of the imagination... ICS is a whole new beast, unfortunately...
Cubed beat me to it.
Sent from my VS910 4G using xda premium
thecubed said:
Head over to #lgrevolution and I'll be there as IOMonster.
Yep, for ICS we need a lot of work in the KGSL department in kernel for getting proper Adreno support working... Tiamat is working on adding the new KGSL/USB/Genlock support to his MSM7X30 repo here ( http://git.tiamat-dev.com/7x30/htc-kernel-msm7x30/ ) and after that we need to merge our kernel sources with his (boardfiles, includes, configs, etc)
Booting to lockscreen is great, but there's a LOT of work to be done before we can have a "working" ICS by any stretch of the imagination... ICS is a whole new beast, unfortunately...
Click to expand...
Click to collapse
Great --I'll be on the channel as achristianson or achristi.
Thanks so much for all that info.
I'm sure it is a long road to a fully working ICS. I see it as a challenge and will just keep fixing the next broken thing...
I'd be happy to test this. I got a spare revo cuz I had a warranty and this dent on the outer corner was driving me nuts.
Gingerfused Gingervolt 1.3 + Blitz
It's really awesome to see everyone working on this. I really wish I knew more about this stuff to be able to help. All this is really making me wanna read up on this stuff and learn how to do some of it. Until that happens, I'll be more than happy to help out with any testing or in any other way within my capabilities. I got a Revo just sitting there deactived waiting for that ICS goodness.
Thanks a lot for everyone working on this. Those of us that aren't as gifted really aprreciate the work you guys are putting in.
Grizzy3 said:
It's really awesome to see everyone working on this. I really wish I knew more about this stuff to be able to help. All this is really making me wanna read up on this stuff and learn how to do some of it. Until that happens, I'll be more than happy to help out with any testing or in any other way within my capabilities. I got a Revo just sitting there deactived waiting for that ICS goodness.
Thanks a lot for everyone working on this. Those of us that aren't as gifted really aprreciate the work you guys are putting in.
Click to expand...
Click to collapse
If you've noticed my post in the CM7 Thread, which somehow 'feels' like it's sparked something off here (maybe just timing, lol), I am beginning to work on this stuff.
Anyone can do it, but the problem is motivation and the willingness to learn something new. You will never learn this stuff unless you're willing to fail and fail again. You learn by mistakes and mistakes sometimes turn into innovation for new things and ideas.
There is a lot of Dev's all of a sudden and I do agree, it's great to see. I was almost about to start looking at the Nexus. When I realized I would lose out on the $130 of extra accessories for my Revo (Car Dock, home dock, extra battery, car charge, etc.), And the fact the the Nexus had no External SD Card, I was like... Nah.. Time to step up and see what I can do to make the Revo a well-supported, up to date, kick-ass device. If LG and Verizon wanna sit on their asses, let'em. We make the phone better anyhow, right? MT, Cubed, and anyone else who has already contributed so much, has made this phone 10X's what it ever was out of the box. And, unlike LG and Verizon, Dev's like MT (and others) don't give us the run around on the next release, but a timeline.
-Cybie
Cybie257 said:
If you've noticed my post in the CM7 Thread, which somehow 'feels' like it's sparked something off here (maybe just timing, lol), I am beginning to work on this stuff.
Anyone can do it, but the problem is motivation and the willingness to learn something new. You will never learn this stuff unless you're willing to fail and fail again. You learn by mistakes and mistakes sometimes turn into innovation for new things and ideas.
There is a lot of Dev's all of a sudden and I do agree, it's great to see. I was almost about to start looking at the Nexus. When I realized I would lose out on the $130 of extra accessories for my Revo (Car Dock, home dock, extra battery, car charge, etc.), And the fact the the Nexus had no External SD Card, I was like... Nah.. Time to step up and see what I can do to make the Revo a well-supported, up to date, kick-ass device. If LG and Verizon wanna sit on their asses, let'em. We make the phone better anyhow, right? MT, Cubed, and anyone else who has already contributed so much, has made this phone 10X's what it ever was out of the box. And, unlike LG and Verizon, Dev's like MT (and others) don't give us the run around on the next release, but a timeline.
-Cybie
Click to expand...
Click to collapse
Exactly how i feel. Forget LG and Verizon. You guys are the ones taking these average phones into something great. I definitely gave up on getting any real support from either of them.
I really want to start getting into this. I have a little bit of time on my hands and will definitely be reading up on all this. I think you sparked something with your post lol. I know other people like MT and theCubed were already working on some things but I think you definitely added a little spark lol. Very happy to see other people jumping on board to help out. Hopefully I can too
Grizzy3 said:
Exactly how i feel. Forget LG and Verizon. You guys are the ones taking these average phones into something great. I definitely gave up on getting any real support from either of them.
I really want to start getting into this. I have a little bit of time on my hands and will definitely be reading up on all this. I think you sparked something with your post lol. I know other people like MT and theCubed were already working on some things but I think you definitely added a little spark lol. Very happy to see other people jumping on board to help out. Hopefully I can too
Click to expand...
Click to collapse
Yup! The motivation for me has been that support by LG and VZ is diminishing. This is the beauty of open source, though. Now the community can support it.
I believe the Revolution really is a good phone. It's got a good GPU and CPU. It's not dual-core, no, but with a good ROM on there, it can be much more efficient than a dual-core phone that is loaded with crapware.
Cybie did inspire me to put my work up sooner so that we can all focus on it and not duplicate our efforts as much.
thecubed said:
Head over to #lgrevolution and I'll be there as IOMonster.
Yep, for ICS we need a lot of work in the KGSL department in kernel for getting proper Adreno support working... Tiamat is working on adding the new KGSL/USB/Genlock support to his MSM7X30 repo here ( http://git.tiamat-dev.com/7x30/htc-kernel-msm7x30/ ) and after that we need to merge our kernel sources with his (boardfiles, includes, configs, etc)
Booting to lockscreen is great, but there's a LOT of work to be done before we can have a "working" ICS by any stretch of the imagination... ICS is a whole new beast, unfortunately...
Click to expand...
Click to collapse
OK so I was doing more debugging last night in the EGL/SurfaceFlinger/HardwareRenderer code. I also looked at some of Tiamat's work on the MSM7X30 kernel.
I can see now what you mean with regard to merging parts of that kernel into our own. I am assuming that kernel is being crafted to work with ICS-friendly EGL blobs for the adreno205. Is that correct? If so, then that kernel would have code that would be required to talk to the binary blob EGL drivers for Adreno205 that we would pull from some device that has the same chip and has official proprietary drivers for ICS available. I believe the HTC Droid Incredible 2 is one such device. Is this roughly what you were thinking?
I initially had thought of going down a different path: Instead of using newer ICS proprietary drivers and updating our kernel to support it, I was planning on keeping the kernel we have and the binary drivers we have, which are already made to work with each other. The work then required to get ICS working would be to change parts of the ICS userspace code such that they'd work with our older drivers. I don't have the links on hand, but I believe this is possible because I read about others taking this strategy on other devices that do not have ICS support officially but do have proper GB support. It also makes sense to me logically that the userspace code could be changed to our heart's content to work with older drivers, since we have full access to that source code. One option that I read about that we could potentially do is write a wrapper for the *adreno200*so librares that would implement the newer API that ICS is expecting and would translate the calls into the older API that is supported in our GB proprietary drivers.
It looks to me like we have two possible ways forward with regard to getting hardware acceleration working: upgrading the kernel and drivers to have "proper" ICS support, or patching ICS userspace code to work with GB drivers and kernel. I believe that patching the ICS userspace code would get us up and running faster while upgrading the kernel and adding newer drivers would be the better long-term solution.
Here are a couple of patches that people have already implemented to support older EGL blobs/kernels:
https://github.com/VorkTeam/android_frameworks_base/commit/429e922fb6f2660fc40472e939175688af52b1d2
https://gist.github.com/CyanogenMod...mmit/5d689bd02531f8ff256b3b1eddcaa8040c9f3559
https://gist.github.com/CyanogenMod...mmit/f8e2430be2d6b3e88afd7190f6712f3bc1df0cbf
Let me know what you think.
Also, what do you think about using the BOARD_USES_QCOM_HARDWARE := true directive to our CM board configuration? I noticed references to the QCOM_HARDWARE flags all over the video code. It seems we would want this since we are using a QCOM video chip. The only problem is the build failed for me when I added this flag. There's an issue about it on github: https://github.com/CyanogenMod/android_hardware_qcom_display/issues/3#issuecomment-3457179.
aichrist said:
OK so I was doing more debugging last night in the EGL/SurfaceFlinger/HardwareRenderer code. I also looked at some of Tiamat's work on the MSM7X30 kernel.
I can see now what you mean with regard to merging parts of that kernel into our own. I am assuming that kernel is being crafted to work with ICS-friendly EGL blobs for the adreno205. Is that correct? If so, then that kernel would have code that would be required to talk to the binary blob EGL drivers for Adreno205 that we would pull from some device that has the same chip and has official proprietary drivers for ICS available. I believe the HTC Droid Incredible 2 is one such device. Is this roughly what you were thinking?
I initially had thought of going down a different path: Instead of using newer ICS proprietary drivers and updating our kernel to support it, I was planning on keeping the kernel we have and the binary drivers we have, which are already made to work with each other. The work then required to get ICS working would be to change parts of the ICS userspace code such that they'd work with our older drivers. I don't have the links on hand, but I believe this is possible because I read about others taking this strategy on other devices that do not have ICS support officially but do have proper GB support. It also makes sense to me logically that the userspace code could be changed to our heart's content to work with older drivers, since we have full access to that source code. One option that I read about that we could potentially do is write a wrapper for the *adreno200*so librares that would implement the newer API that ICS is expecting and would translate the calls into the older API that is supported in our GB proprietary drivers.
It looks to me like we have two possible ways forward with regard to getting hardware acceleration working: upgrading the kernel and drivers to have "proper" ICS support, or patching ICS userspace code to work with GB drivers and kernel. I believe that patching the ICS userspace code would get us up and running faster while upgrading the kernel and adding newer drivers would be the better long-term solution.
Here are a couple of patches that people have already implemented to support older EGL blobs/kernels:
https://github.com/VorkTeam/android_frameworks_base/commit/429e922fb6f2660fc40472e939175688af52b1d2
https://gist.github.com/CyanogenMod...mmit/5d689bd02531f8ff256b3b1eddcaa8040c9f3559
https://gist.github.com/CyanogenMod...mmit/f8e2430be2d6b3e88afd7190f6712f3bc1df0cbf
Let me know what you think.
Also, what do you think about using the BOARD_USES_QCOM_HARDWARE := true directive to our CM board configuration? I noticed references to the QCOM_HARDWARE flags all over the video code. It seems we would want this since we are using a QCOM video chip. The only problem is the build failed for me when I added this flag. There's an issue about it on github: https://github.com/CyanogenMod/android_hardware_qcom_display/issues/3#issuecomment-3457179.
Click to expand...
Click to collapse
You guys are great! I hope this is doable, keep up the hard work..
Sent from my Nexus S 4G using XDA App
Now that the ICS build for RAZR has been leaked, has anyone taken a look to see if there's anything in there that would be useful for ICS on our phones?
Also, it seems the new build also includes updated radio firmware. Has anyone checked to see if GSM support is present in the new radio?
highlandsun said:
Now that the ICS build for RAZR has been leaked, has anyone taken a look to see if there's anything in there that would be useful for ICS on our phones?
Also, it seems the new build also includes updated radio firmware. Has anyone checked to see if GSM support is present in the new radio?
Click to expand...
Click to collapse
Dhacker & Hashcode are already looking at it.
According to Hashcode, Dhacker was all over it this weekend, but it's still going to take a bit of time to get it all implemented.
So we should see some stuff coming up, but it is going to be a bit before it trickles down.
Mostly, they're looking at the radio's right now. The other thing that's also being heavily looked at is the HWcodecs for the video.
awesome... i figured they would be on top of it, but its great to have confirmation... also just a straight port of it would be awesome!
it would be great if they are able to port over the radio for 3G/4G since the 3 ICS roms we have so far have issues with data
Yeah, a straight port would pretty much be perfect... What I dont get is why Moto cant release the D4 update along with the RAZR...
Sent from my DROID4 using Tapatalk
Hashcode, you're gonna get 20 bucks from me.