Database Develop

[ROM/AOSP] Cyaonbread - The Best of CM6 and 7 All Rolled in to One - v1 soon

With the buildbots not up yet, I've been working on a little project in secret for a while. I call it Cyanobread. My plan here is to make a CM7 that has all of CM 6.1's bells and whistles before the CM7 team does. Some patches I will probably submit, and some will be only for this ROM as they go against the ideas of what Cyanogen wants. I haven't decided yet if I will keep this updated once the buildbots come back. If it divulges from the CM7 project significantly than probably.... otherwise I will just keep this as a mod for a few patches you can add to CM7.
My philosophy behind doing this ROM is the fact that I love CM6 and have used the nightlies as my daily driver and was very dissapointed 7 wasn't up on the buildbots.
Even though this is mostly a CM7Src ROM, please report any bugs here and I will do my best to either report them to the CM Team or fix them myself if I can. Same thing goes for any features you'd like to see added.
My approach to deving is a very collaborative one. Invisiblek, jladronka and DS36 will be helping me with this project. If any other devs would like to help, please shoot me a PM. The more the merrier, I really want to see a nice group project out of this.
Screenshots :Comming Soon
Version 1: Download Coming Soon!

reserved.... I've always wanted to do that

Sounds swell. Can't wait to give it a whirl! Thanks!
Sent from my Incredible using XDA App

Im all over it

I'm very interested in this.

You let me know if PSX4droid works and I'll be all over this ROM.

Ruggerxpunk said:
You let me know if PSX4droid works and I'll be all over this ROM.
Click to expand...
Click to collapse
You could also, you know, test it out yourself.
Just saying...

Interesting (but then again, I'm a ROM hua), I'm on board.

I'm also interested in Cyanocomb when it's ready. ;-)

sounds interesting, i'll definitely try it

Looking forward to it.....I know I should not ask, but.....ETA?

lol I dont go by the No ETA rule so long as you dont mind if you're wrong.
well this has been an in work project for a few weeks... finally had a full compile this morning but was missing some apps.... so i decidedd to make clean and do it again... first time my laptop blue screened, then it hibernated because I forgot to plug it in.... I'm thinking within a few hours.

I'm looking forward to this.

Back in my Blackberry days we used to call these Hybrids. Some of the most functional, stable BB OSs were patched together from different OSs or even bits and pieces from different phones.
Of course, some hybrids were the biggest train wrecks also...
I have high hopes for this. Good luck!

Heh, FrankenROM.

sorry for not getting this out tonight... I had a few minor setbacks. Teaser installer video coming in a few minutes. Right now, it is completely stock CM, and you can think of the teaser as a .5 of sorts. v1 will be out tomorrow I promise. Very minor tweaks that I am going to do to start out with.

Excuse my ignorance, whats the point? Isn't CM7 the best of 6 and 7 all rolled into one sprinkled over some Gingerbread?

joe3681 said:
Excuse my ignorance, whats the point? Isn't CM7 the best of 6 and 7 all rolled into one sprinkled over some Gingerbread?
Click to expand...
Click to collapse
This ^^ I'm running gridlock's CM 7 latest build and so far, it's got all the mods that CM6.# has, on GB.
What exactly are you planning on adding that it doesn't already have?

n1ghtwish said:
This ^^ I'm running gridlock's CM 7 latest build and so far, it's got all the mods that CM6.# has, on GB.
What exactly are you planning on adding that it doesn't already have?
Click to expand...
Click to collapse
Cause I went from Cm6.1 to to 7 up to the latest 32, and there's nothing at all that has made me say "Oh damn, I miss that from CM6". CM7 has TONS more tweaks, and a pretty bad ass music player.
Glad to see I'm not the only one wondering what the point of this is...

when i started this project that wasn't the case. a lot o the goodies in CM6 were missing... I plan to add my own little touch to it and hopefully diverge from the CM project slightly. Video's not going to happen, having some issue with the touchscreen....will look at it in the morning.
hmmm... no issue with the touch screen... but somehow this compiled lacking a keyboard... blah... i was hopeful... oh well... will deal wiith it in the morning

Yes, please. (Honeycomb)

Honeycomb SDK preview is out
http://www.engadget.com/2011/01/26/android-3-0-honeycomb-sdk-preview-goes-live/

Amen to that. You know - i ahve seen other phones have semi-working rom builds created from the SDK images. I am sure its just a pip dream, but damn it would be sweet if we could be working on honeycomb now....

it's possible to extract a image, but then it would be slow as hell.
not worth the trouble porting it

cainhunpi said:
it's possible to extract a image, but then it would be slow as hell.
not worth the trouble porting it
Click to expand...
Click to collapse
I dunno.. doubt it would be slower than Froyo on an SD card.

I made a zombie out of the honeycomb preview and one of the nook kernels.
Touch input doesn't work, no hardware acceleration etc.

Well then get to work dblue.....
From the nookCOLOR

If we can get the Nook Color running gingerbread that would beyond awesome, honeycomb and I might just piss myself.
Sent from my LogicPD Zoom2 using XDA App

deeper-blue said:
I made a zombie out of the honeycomb preview and one of the nook kernels.
Touch input doesn't work, no hardware acceleration etc.
Click to expand...
Click to collapse
I love it (and thanks for trying exactly what i was thinking of)! Sure, it isn't fully working, but it provides a TON of hope that with some work, Honeycomb can be made to work.

Once the source code is on AOSP then getting working ROMs for other platforms should be much easier. I think one of the problems we might see is driver support since the underlying kernel for Honeycomb might be different.

It does indeed run very slow so far.
Touchscreen is working now. I'll try to get the graphics acceleration running over the weekend that should help with performance.
(and I think it's stupid that I can't post or reply in the development forum without having more than 10 posts.)

deeper-blue said:
It does indeed run very slow so far.
Touchscreen is working now. I'll try to get the graphics acceleration running over the weekend that should help with performance.
(and I think it's stupid that I can't post or reply in the development forum without having more than 10 posts.)
Click to expand...
Click to collapse
If you get a bootable SD card out of this, you'd become a legend on these forums (At least in my eyes)
If you don't, you still get huge respect for getting this working on your device.

deeper-blue said:
(and I think it's stupid that I can't post or reply in the development forum without having more than 10 posts.)
Click to expand...
Click to collapse
It is an effort to keep people from finding out about XDA on yahoo or something and then coming here and going into the dev section saying make it work for me...NOW!!
Which sadly happens a great deal. Seen it many times in my years around here.
I'm sure that you will appreciate it when you have less of that to deal with when you hit another few posts and can start your first thread in the dev section.
You obviously have something to contribute so just post replies to a few posts in the general section here and you will be on your way.
Looking forward to the work you have started!!

Agreed - please keep up your work, and hit up the dev section after 10 posts. I would LOVE to see work progress on honeycomb!

Awesome. I may be wrong but isn't this the first HC port?

unknownrebelx said:
Awesome. I may be wrong but isn't this the first HC port?
Click to expand...
Click to collapse
I would call it a port. but yes. first hardware to run it

Congrats! You made Engadget!
http://www.engadget.com/2011/01/28/nook-color-earns-its-very-eary-very-unofficial-android-3-0-hone/

Deeper-Blue. hit up 10 posts and start a post on the Development forum. Gived us the code u got and we can help each other

Divine_Madcat said:
Congrats! You made Engadget!
http://www.engadget.com/2011/01/28/nook-color-earns-its-very-eary-very-unofficial-android-3-0-hone/
Click to expand...
Click to collapse
Job in 3, 2 , 1
Done. He is already working for an OEM

Damn, makes me regret returning my NC. Awesome job!
Sent from my EVO using XDA App

Amazing. The OEM still hasn't released Froyo and there are devs working Froyo, Ubuntu, and now Honeycomb. I didn't see Gingerbread, but I bet that has been done as well! Congrats!

Moderator:please close this thread

My own Project was already in the works for another TEAM:
http://www.aedesign.cn/bbs/forumdisplay.php?fid=6
DOWNLOAD of THEIR work:
http://u.115.com/file/bh5z76gp#AED_Legend_5.0.0.RC3_exp.zip

good to see

Good to see someone else to make something new for the legend comunity. Keep going!
By the way, what is your ROM base? The video is too blury...

ogo2 said:
Good to see someone else to make something new for the legend comunity. Keep going!
By the way, what is your ROM base? The video is too blury...
Click to expand...
Click to collapse
I would say this rom:
http://www.aedesign.cn/bbs/viewthread.php?tid=316&extra=page=1

Looks cool, looking forward to this rom. Gj so far
Sent from my Legend using XDA App

I am glad as well to see someone else step up to the plate. I think this will give the CyanogenMod developers some more motivation to make a stable release.

LiViD said:
I am glad as well to see someone else step up to the place. I think this will give the CyanogenMod developers some more motivation to make a stable release.
Click to expand...
Click to collapse
Yeah, I know we are idiots. All of our releases have been unstable, full of bugs and missing nearly every feature one could wish for. Please excuse us, but we really can't do any better. The fact that all ROMs that are not based off RUUs are CyanogenMod rip-offs should clearly tell you that we just can't get anything right at all.

Very MIUI like.. Looks pretty much like my new Desire... Great job seeing similar running on the Legend..
Sent from my HTC Desire using XDA Premium App

great job!

LiViD said:
I am glad as well to see someone else step up to the plate. I think this will give the CyanogenMod developers some more motivation to make a stable release.
Click to expand...
Click to collapse
i suggust u say sorry for your arrogance to the CyanogenMod tea
btw awsome work!

dilip007 said:
i suggust u say sorry for your arrogance to the CyanogenMod tea
btw awsome work!
Click to expand...
Click to collapse
You guys don't pay attention to the experimental thread do you? Seriously, over 160 attempts at a nightly build and still nothing that performs up to par with ogo2's 2.3.3 Sense UI ROM. Sure his is lacking WiFi AP functionality, but I can live with that.
I love how you call everyone elses' ROM a rip-off of a CM ROM. Get a life guys, no one would attempt to use your builds unless said person was extremely lazy.

LiViD said:
You guys don't pay attention to the experimental thread do you? Seriously, over 160 attempts at a nightly build and still nothing that performs up to par with ogo2's 2.3.3 Sense UI ROM. Sure his is lacking WiFi AP functionality, but I can live with that.
I love how you call everyone elses' ROM a rip-off of a CM ROM. Get a life guys, no one would attempt to use your builds unless said person was extremely lazy.
Click to expand...
Click to collapse
Damn.. Where have you lived your life? 2 versions of stable ROMS is what we have.. original from HTC is 1 - CM is 2.. All roms worth mention is variations of one of those.. (for Legend that is)
Sent from my HTC Desire using XDA Premium App

LiViD said:
I love how you call everyone elses' ROM a rip-off of a CM ROM.
Click to expand...
Click to collapse
I know I'm wasting my time here and I really don't care anyway.
Still I think I have to clarify that I'm not talking about people using some "builds". I'm talking about the source code.
If you want to build a ROM for the Legend (and nearly every other device out there) you've got two choices: Push some files from official releases (RUUs) around and zip them, or compile from source.
As a matter of fact there's no project out there that releases working source code (for anything but Google's official devices) except for CyanogenMod.
Video encoding or decoding? msm* support? Backported code for ancient libcamera, libril and framework support for said ancient libraries? GPS backport or implementation? Kernel backports for Gingerbread? Yeah, good luck finding that somewhere else (no, I don't mean the CAF repositories where we are copying from and giving credit of course).
LiViD said:
Get a life guys, no one would attempt to use your builds unless said person was extremely lazy.
Click to expand...
Click to collapse
"Get a life"? Come on, don't be ridiculous.
MD5-sums can be quite revealing by the way. Or boot messages (like "Welcome to CyanogeMod" in MIUI). Some people were even charging for shady rip-offs – that's why the CM team ultimately decided to close down development and switch to "release when it's done".
LiViD said:
Seriously, over 160 attempts at a nightly build...
Click to expand...
Click to collapse
Sorry, but you didn't understand the concept of a nightly build? There are no "attempts at a nightly build" and they are not even meant for users. Nightly builds are there to see if current code in the repositories still compiles. Nothing else.
whitetigerdk said:
All roms worth mention is variations of one of those.. (for Legend that is)
Click to expand...
Click to collapse
Unfortunately not only for the Legend but for most other devices too.
Android was said to be open but in fact it's just proprietary crap again. No developer wants to spend months doing the work of forty CM devs, so they either join CM – or sometimes steal their work declaring it as their own – or use (or combine) binaries from official releases.

If you didn't care, you would be in other developers threads attacking their attempts at making something that just may work better than what you're pushing out.
Face the facts; People want more choices other than CM. I am willing to admit that CM 6.1 was a damn good ROM when it came out, but I can't for life of me figure out why you guys can't live up to the same expectations with CM7.
I have been testing the NewSense 1.0 RC's (HTC Salsa ROM) for some time, and I as I said; Without the lack of AP support, it works well and does not have the crash prone problems that I have seen with 7.0.3, and 7.1 RC1.

ali ba said:
Unfortunately not only for the Legend but for most other devices too.
Android was said to be open but in fact it's just proprietary crap again. No developer wants to spend months doing the work of forty CM devs, so they either join CM – or sometimes steal their work declaring it as their own – or use (or combine) binaries from official releases.
Click to expand...
Click to collapse
Oh Sorry.. Didn't know much of other devices.. Recently bought the Desire and currently using MIUI. Must admit that I believed the MIUI to be a completely rewrite of the Android framework..
Sent from my HTC Desire using XDA Premium App

LiViD said:
I have been testing the NewSense 1.0 RC's (HTC Salsa ROM) for some time, and I as I said; Without the lack of AP support, it works well and does not have the crash prone problems that I have seen with 7.0.3, and 7.1 RC1.
Click to expand...
Click to collapse
You can thanks for that to HTC, because i haven't written a single line of code in NewSense. Only some crappy hacks.
Really, our community is too small and we have a lack of devs, but that's not all. HTC provide to us just ****ty sources. It just sucks!

Btw: this rom here is based on cm7...

Edit: I commented on the wrong ROM. My bad.

I still think Blayo's rom's are the best for Legend!
Been using them for quite a while and I never have had any complain!

whitetigerdk said:
Must admit that I believed the MIUI to be a completely rewrite of the Android framework..
Click to expand...
Click to collapse
Their earlier releases certainly used CM sources with modified framework and apps. I don't know what they are doing now – but as they don't release their sources I can accuse them of using modified CM source code as much as I want without ever being able to prove it so I refrain from doing that.
If you are interested, the UltimateDroid soap opera is a good read by the way.
ogo2 said:
You can thanks for that to HTC, because i haven't written a single line of code in NewSense. Only some crappy hacks.
Click to expand...
Click to collapse
That doesn't make your work worth less than anyone else's and certainly not "crappy".
ogo2 said:
HTC provide to us just ****ty sources.
Click to expand...
Click to collapse
I'd be happy if they provided the real sources for the binaries they are releasing but as a matter of fact HTC continuously violates the GPL and we can't do anything about that.
LiViD said:
If you didn't care, you would be in other developers threads attacking their attempts at making something that just may work better than what you're pushing out.
Click to expand...
Click to collapse
Where exactly did I attack emiliano7's work? I'm actually very glad that someone is developing for the Legend and I never stated anything else.
You obviously on the other hand couldn't resist showing your arrogant attitude by addressing the CM team in this thread making false accusations. You can't take a discussion off-topic and then blame others for taking the same train.
LiViD said:
...the crash prone problems that I have seen with 7.0.3, and 7.1 RC1.
Click to expand...
Click to collapse
Instead of making vague accusations you could have filed bug reports a long time ago. CM is a community project and nothing without its community.
It sometimes still makes me sad that for some people whining doesn't seem to be a problem but as soon as it comes to writing a good bug report they come up with various excuses.

[DEV][WIP] CM9/Ice Cream Sandwich

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

The future of the Dell Streak 7

Okay, I wanted to take a moment to talk about the development for our device.
Recently CM decided to no longer support Tegra 2 devices as they are starting to get dated. So basically that boils down to the fact that the CM10.1 will be the last one for our device that I do.
Currently I'm trying to jump start the process of putting out our updated kernel from 2.6.36.4 -> 3.1. This will hopefully put our device at a point where everything should work.
DerArtem is the lead developer on the kernel, but has been busy because he just got married and works a full time job, which puts a damper on his time (which is understandable).
I am putting in an 1-2 hours every morning on this, trying to fix those bugs and was just tipped on a possible way to minimize the overload of the log with the USB error. This will be a hold off till we get the kernel done as these issues should go away after the update.
I am sad to see this tablet come to an end (though not yet). We all have to admit that its time we all start moving on. I am going to push to get these last bit done and call it quits. This can take anywhere from 2-5 months to finish up, maybe a bit longer and then our device will be done.
I have had an amazing time learning about Android under DJ_Steve and DerArtem, and thank them for taking the time to teach me.

I thank you what you done so far and in the future. Can blame you one bit for your decisions.

I think setting an "end game" is respectable, and is a good goal. The kernel work is the key to smoothing things over on what has been wonderful development thus far.
The fact you've taken us this far sir is very commendable and you and the crew deserve many thanks. For your time and efforts, you have my gratitude, and my tablet serves as a hobby rather than a shelved device.
4.2.x has been flawed since release by Google, and with the way android has evolved, future versions will undoubtedly require more current hardware and OEM support. The latest tablet releases have as much computing power as a 2 year old laptop! Thanks to you, we've managed to play with JB, and I look forward to what comes before a final release.:thumbup:
Sent from my Galaxy Nexus using xda premium

Wow, I hate doing this, but I may have to close up shop on all this. Severe lack of any real work is getting done as I am looking for jobs and trying to have some game time as well.
The time to do this isn't worth it. I may ask for payments for my next ROM ($1 per download). Seriously, I hate doing it but this just isn't worth it anymore. Currently working on a AOKP release, to see if this may resolve any bugs I am having.

Hi giveen,
first of all thank you for all the time you spent on our old device. I already donated you some time ago and always had an eye on your progesses. I really understand your decision to ask for some payment for all the work and that is absolutely ok for me.
I use my DS7 (wifi only) on a daily base to check my mails, surf the net and stream some TV and video from my HTPC. Until now I use a HC 3.2 mod (514 mod by dreamer) together with V6 Supercharger script and am so far quite ok with that. So far I see no need to buy me a new tablet as long as the DS7 fits my few needs
But before I collect all my courage and update my DS7 in the near future to your CM10 build I want to ask a few things:
1. Is your build already stable and usable enough for the things I do with my device?
2. Any news from DerArtem about the kernel work? Will there be a new kernel for our device in the future?
THX,
Michael

Montezuma10 said:
Hi giveen,
first of all thank you for all the time you spent on our old device. I already donated you some time ago and always had an eye on your progesses. I really understand your decision to ask for some payment for all the work and that is absolutely ok for me.
I use my DS7 (wifi only) on a daily base to check my mails, surf the net and stream some TV and video from my HTPC. Until now I use a HC 3.2 mod (514 mod by dreamer) together with V6 Supercharger script and am so far quite ok with that. So far I see no need to buy me a new tablet as long as the DS7 fits my few needs
But before I collect all my courage and update my DS7 in the near future to your CM10 build I want to ask a few things:
1. Is your build already stable and usable enough for the things I do with my device?
2. Any news from DerArtem about the kernel work? Will there be a new kernel for our device in the future?
THX,
Michael
Click to expand...
Click to collapse
If its from your HTPC, I honestly don't know as I have never tried it before. This latest build is much more stable, though it still has the gmail keyboard crash that I am tracking down. If you are happy with what you have, don't do anything. I would hate for you to make a purchase and not be happy.
I haven't heard from DerArtem in several weeks because he is in another country (Russia) doing a job. (He lives in Germany). To be honest, I don't think a new kernel is going to happen and I'm really upset by it.

giveen said:
If its from your HTPC, I honestly don't know as I have never tried it before. This latest build is much more stable, though it still has the gmail keyboard crash that I am tracking down. If you are happy with what you have, don't do anything. I would hate for you to make a purchase and not be happy.
I haven't heard from DerArtem in several weeks because he is in another country (Russia) doing a job. (He lives in Germany). To be honest, I don't think a new kernel is going to happen and I'm really upset by it.
Click to expand...
Click to collapse
One issue I see here is that when you start charging, a person paying for it like a app from the Play Store, they expect things to work. This "might" cause you to spend more time than you have been on it. Just my $0.02!
Didn't somebody donate an unused DS7 for DerArtem for this kernel project?

wptski said:
One issue I see here is that when you start charging, a person paying for it like a app from the Play Store, they expect things to work. This "might" cause you to spend more time than you have been on it. Just my $0.02!
Didn't somebody donate an unused DS7 for DerArtem for this kernel project?
Click to expand...
Click to collapse
They can contact me if they are having an issue. I appreciate the concern though.
Yes, someone did give their DS7 to him.

giveen said:
They can contact me if they are having an issue. I appreciate the concern though.
Yes, someone did give their DS7 to him.
Click to expand...
Click to collapse
I'll be downloading it later after some usage and a charge.

I'm working on sensors now. The old sensor drivers we used were for something we dont even have. I found the correct Android drivers but they are for qualcomm devices, so I need to modify them to work.

giveen said:
I'm working on sensors now. The old sensor drivers we used were for something we dont even have. I found the correct Android drivers but they are for qualcomm devices, so I need to modify them to work.
Click to expand...
Click to collapse
after several attempts and research I was still not the sound from my headphones with android android 2 and 3 sound going normally but not with 4.2.1 and 4.2.2.