This is a proof of concept working camera for CM9 ICS. I built the sources from TI omapzoom sources and stripped out some stuff not needed in ICS. Also heavily uses the wrapper HAL work that I built for Nexus one compatible Qualcomm cameras
http://forum.xda-developers.com/showthread.php?p=22778026
It is a complete hack for now, but demonstrates that camera works with the tiler memory system, without need for ION. Only camera mode works for now. Video and Panorama mode do not. Also front facing camera does not work either. Preview would be a bit slow, as the decoding of frames is done in software and also there is a lot of debug logging. I have had this device for less than 2 weeks and hope things should improve as I learn more on how things work .
Here is a flashable zip file
http://www.mediafire.com/?r1c2jwchn4sjf9d
The diffs w.r.t TI omapzoom is at
http://www.mediafire.com/?j3zk87qe7uxqg7e
For now, the code is all hacks as you can see in the patch from the URL above. Once I have some more functionality, I will create a github repo for this work.
Credits are due to the CM team, Hashcode and whose ever code is used.
Give it a try and drop a line if camera works for you. Updates are in the second post.
Thank you for your generous donations. Every bit of it is greatly appreciated.
Update: 03/09/2012
Working front facing cam.
Preview and photos now work for both rear and front cams.
Flashable zip file:
http://www.mediafire.com/?48b1xnd84u45fy7
Video recording and the other features do not work yet.
Enjoy!!
rapmv78 said:
Blocking second post for future updates.
Click to expand...
Click to collapse
Gonna try this now thnx
Sent From My Dark Fire DROID3
Heck yes, this works cam works can take pics, front cam nope like you said, but thnx much appreciated
Sent From My Dark Fire DROID3
Stick for futures
Holy crap the camera works! Praise Jebus! Lmao
Awesome work man!
Sent from my D3 w/ ICSCamera Goodness
What ROM do I use?
Sent from my Droid 3?
Rom CM9/ICS for Droid 3 ALPHA #7
Camera Work!
Awesome work!
rapmv78 said:
This is a proof of concept working camera for CM9 ICS. I built the sources from TI omapzoom sources and stripped out some stuff not needed in ICS. Also heavily uses the wrapper HAL work that I built for Nexus one compatible Qualcomm cameras
http://forum.xda-developers.com/showthread.php?p=22778026
It is a complete hack for now, but demonstrates that camera works with the tiler memory system, without need for ION. Only camera mode works for now. Video and Panorama mode do not. Also front facing camera does not work either. Preview would be a bit slow, as the decoding of frames is done in software and also there is a lot of debug logging. I have had this device for less than 2 weeks and hope things should improve as I learn more on how things work .
Here is a flashable zip file
http://www.mediafire.com/?r1c2jwchn4sjf9d
The diffs w.r.t TI omapzoom is at
http://www.mediafire.com/?j3zk87qe7uxqg7e
For now, the code is all hacks as you can see in the patch from the URL above. Once I have some more functionality, I will create a github repo for this work.
Credits are due to the CM team, Hashcode and whose ever code is used.
Give it a try and drop a line if camera works for you.
Click to expand...
Click to collapse
Thank you for the great write up. I see exactly where you comment out the overlay code and let the camera run the buffers through the tiler instead.
Oddly, when I tried this approach I was getting Ducati errors. I must have had something else wrong in my attempts.
Thanks again for the posting. And I hope you don't mind me trying out some different options to speed this up.
It works
great job, thanks
Hashcode said:
Thank you for the great write up. I see exactly where you comment out the overlay code and let the camera run the buffers through the tiler instead.
Oddly, when I tried this approach I was getting Ducati errors. I must have had something else wrong in my attempts.
Thanks again for the posting. And I hope you don't mind me trying out some different options to speed this up.
Click to expand...
Click to collapse
your personal vendetta might just be over sooner than you thought
great great job....i confirm the patch work only in photo mod on cm9 alpha 7 (hash) and don't work on aokp project rom. nice
rapmv78 should be added to the beer money/donate/dev list for this.
for anyone who needs cliff notes of what works:
i have static on the FFC and see the outline of my head a little, should be an easy fix , also camcorder UI pops up just no recording. theres a slight delay with camera movement which i think has to do with the dalvik heap or the codecs. also once a picture is taken the preview/share area works for me and will go to the gallery to edit/delete picture smoothly and VERY fast transitions between camera UI and preview/gallery. this is gonna be very huge once fine tuned!
Awesome! I have been holding out a few days now before flashing back to some GB rom because I need a basic camera for work. I now can stick with CM9! I have to drive a few hours for some family stuff but when I get back tonight I will test this and post any logs. Speaking of that I don't see much of that here. Do people just PM Hash and not post(which I would understand because of the overwhelming posts that incorrectly end up here instead of the users forum)? That is the fastest/easiest way to assist dev instead of just making requests or saying some doesn't work correct?
XT862 CM9A7
CM9 ICS Camera proof of concept
rapmv78 said:
This is a proof of concept working camera for CM9 ICS. I built the sources from TI omapzoom sources and stripped out some stuff not needed in ICS. Also heavily uses the wrapper HAL work that I built for Nexus one compatible Qualcomm cameras
http://forum.xda-developers.com/showthread.php?p=22778026
It is a complete hack for now, but demonstrates that camera works with the tiler memory system, without need for ION. Only camera mode works for now. Video and Panorama mode do not. Also front facing camera does not work either. Preview would be a bit slow, as the decoding of frames is done in software and also there is a lot of debug logging. I have had this device for less than 2 weeks and hope things should improve as I learn more on how things work .
Here is a flashable zip file
http://www.mediafire.com/?r1c2jwchn4sjf9d
The diffs w.r.t TI omapzoom is at
http://www.mediafire.com/?j3zk87qe7uxqg7e
For now, the code is all hacks as you can see in the patch from the URL above. Once I have some more functionality, I will create a github repo for this work.
Credits are due to the CM team, Hashcode and whose ever code is used.
Give it a try and drop a line if camera works for you.
Click to expand...
Click to collapse
Great work!! camera, camera, camera. Nice. I'm so glad I stuck it out, rather than drive myself crazy with how I think this rom should be. Really good work men, really great. Thanks!
atlantanetworkguy said:
Awesome! I have been holding out a few days now before flashing back to some GB rom because I need a basic camera for work. I now can stick with CM9! I have to drive a few hours for some family stuff but when I get back tonight I will test this and post any logs. Speaking of that I don't see much of that here. Do people just PM Hash and not post(which I would understand because of the overwhelming posts that incorrectly end up here instead of the users forum)? That is the fastest/easiest way to assist dev instead of just making requests or saying some doesn't work correct?
XT862 CM9A7
Click to expand...
Click to collapse
twitter.com/hashcode0f
thats the fastest way of getting ahold of him. also he usually wants logs sent to [email protected] or if he is okay with it you could add him on gtalk.
rapmv78
thank you thank you thank you thank you thank you thank you
great job, woks some well
Software cameras work too :] thanks for your hard work !
Sent from my XT862 using Tapatalk
Awesome!!!!!
Sent from my XT862 using XDA App
Related
No, it's not out yet-- but I do have it booting, and with working touchscreen support
Video Link: http://www.youtube.com/watch?v=hnRlyMZzdT0
New video:: http://www.youtube.com/watch?v=2d4pZXyayts
That's about it right now.
Things left:
Mobile Voice
3G Data
4G Data / Voice
Audio
Front Camera
Back Camera
GPS
Bluetooth
Wifi
DSP support for video encode/decode
Vibrate/Notification LED
As I get things working, I'll update this list.
My first priority is wifi, then mobile voice, then 3g data, then vibrate/notification LED.
After that, I'll get GPS working (not hard) then rear camera.
Things that'll probably not happen in CM7 for a while:
Front camera
4G Voice
4G Data
Anything to do with 4G will be VERY tough, since I don't have LG's kernel sources, and I'm no RIL reverse engineer... Any help in this matter is appreciated!
You are the man!
Anxiously awaiting!
Sent from my VS910 4G using XDA Premium App
Uh oh....deciding between 4G and CM7 is going to be rough.
Good work dasgewürfelte (thecubed in German haha)...thanks for everything
Anytime you need a tester Cubed, just let me know. My city is scheduled to get 4G this Thursday so I should be able to test that for you too, soon.
thecubed said:
No, it's not out yet-- but I do have it booting, and with working touchscreen support
That's about it right now.
Things left:
Mobile Voice
3G Data
4G Data / Voice
Audio
Front Camera
Back Camera
GPS
Bluetooth
Wifi
DSP support for video encode/decode
Vibrate/Notification LED
As I get things working, I'll update this list.
My first priority is wifi, then mobile voice, then 3g data, then vibrate/notification LED.
After that, I'll get GPS working (not hard) then rear camera.
Things that'll probably not happen in CM7 for a while:
Front camera
4G Voice
4G Data
Anything to do with 4G will be VERY tough, since I don't have LG's kernel sources, and I'm no RIL reverse engineer... Any help in this matter is appreciated!
Click to expand...
Click to collapse
So, does the release of the kernel change your thoughts on 4G? What about the issues with 3G data lag? Not pressing, just curious. I know with the release of the kernel you aren't going to have a lot of time on your hands to get sidetracked
majorpay said:
So, does the release of the kernel change your thoughts on 4G? What about the issues with 3G data lag? Not pressing, just curious. I know with the release of the kernel you aren't going to have a lot of time on your hands to get sidetracked
Click to expand...
Click to collapse
We were on IRC before when I posted that link. He said 4G data/voice shouldn't be a problem now.
The kernel gives the information on how to communicate with the radio
Pretty much, from what I understand, all of those "not for a while" items. Are now going to be in the first build of CM7 for the REVOLUTIOnnnnn-tionn-tion-tion
nick99wj said:
We were on IRC before when I posted that link. He said 4G data/voice shouldn't be a problem now.
The kernel gives the information on how to communicate with the radio
Pretty much, from what I understand, all of those "not for a while" items. Are now going to be in the first build of CM7 for the REVOLUTIOnnnnn-tionn-tion-tion
Click to expand...
Click to collapse
so did I miss LG releasing the kernal source.. or did we get it another way..?
**edit**
so just a few more clicks and I wouldn't have asked that question.. I am game try whatever you have available!
holy crap i just nutted.
mursepaolo said:
holy crap i just nutted.
Click to expand...
Click to collapse
This.
Awesome!
Hey Thecubed, is there a particular reason you went with ADW Launcher as the... er... Launcher? What would keep you from using HeLauncher as the default? Any chance of getting a Samsung style launcher and icons?
And I think its almost been a week, and the phone is still running smooth. I did the stat bar cleaner, thanks MT. And the battery life is stellar.\
Thanks again. I am working overtime so I can get you a sizeable dony.
nick99wj said:
We were on IRC before when I posted that link. He said 4G data/voice shouldn't be a problem now.
The kernel gives the information on how to communicate with the radio
Pretty much, from what I understand, all of those "not for a while" items. Are now going to be in the first build of CM7 for the REVOLUTIOnnnnn-tionn-tion-tion
Click to expand...
Click to collapse
Very good to hear
Fixing 3G lag will be sooo nice.
markapowell said:
Hey Thecubed, is there a particular reason you went with ADW Launcher as the... er... Launcher? What would keep you from using HeLauncher as the default? Any chance of getting a Samsung style launcher and icons?
And I think its almost been a week, and the phone is still running smooth. I did the stat bar cleaner, thanks MT. And the battery life is stellar.\
Thanks again. I am working overtime so I can get you a sizeable dony.
Click to expand...
Click to collapse
The kingpins of CM7 decided to use ADW.Launcher since its dev open-sourced the launcher. It makes customizations very easy to make. You can always pull it out with TB once you've got your launcher of choice up and running.
Cubed - I was so excited when I saw this thread pop up the other day. I have my Revolution coming in the mail hopefully sometime this afternoon, and I will definitely be on the IRC once it gets in. I won it in a contest, so I won't feel bad if I end up bricking it, especially because I have an upgrade in September.
And as soon as my finances allow, I will most certainly be submitting a donation. Thank you for your support!
I will say though, I just switched to this Fascinate I'm using currently a month ago, and our CM7 code finally got merged upstream, so I'm definitely gonna miss fully-functional GB, but I'm sure you'll have it running smoothly in no time!
Totally double-posting here, but I have my phone activated and running. 4G is friggin' SWEET!
Anywho, if you need any logcats or anything at all that's within my practical ability (I'm willing to flash just about anything since I didn't pay a dime for this phone, and can do any number of logcats/dmesg you need), just let me know. I'll pop onto the IRC from time to time just to check, but if you ever need someone in a hot moment, direct message me and I'll be glad help!
any chance we will see a alpha release to test out for you? would be ballin!
RegnierD said:
The kingpins of CM7 decided to use ADW.Launcher since its dev open-sourced the launcher. It makes customizations very easy to make. You can always pull it out with TB once you've got your launcher of choice up and running.
Cubed - I was so excited when I saw this thread pop up the other day. I have my Revolution coming in the mail hopefully sometime this afternoon, and I will definitely be on the IRC once it gets in. I won it in a contest, so I won't feel bad if I end up bricking it, especially because I have an upgrade in September.
And as soon as my finances allow, I will most certainly be submitting a donation. Thank you for your support!
I will say though, I just switched to this Fascinate I'm using currently a month ago, and our CM7 code finally got merged upstream, so I'm definitely gonna miss fully-functional GB, but I'm sure you'll have it running smoothly in no time!
Click to expand...
Click to collapse
I suspect another reason ADW was incorporated is because it's one of the only open source launchers. That comes without the possible legal ramifications of packaging someone elses work in your creation.
I also wouldn't mind being a testcase, if there is a use for another one.
Right now I'm reworking all the init scripts that LG has written and consolidating them into the cyanogenmod style of a single "init.bryce.rc" initscript.
As I'm doing that, I'm looking for referenced binaries and crossreferencing that list with the list of binaries that cyanogenmod builds (to see what binaries are LG-specific and what are stock Android). After I find the binaries, I am hexdumping each one to find out which libraries they import, and adding those to the cyanogenmod build directory also.
LG really really really needs to write better scripts. Their init process is all over the map, and half of the stuff in the init script isn't even for our device! It references dev platforms and other stuff that really should be trimmed before releasing to the public.
Anyway, in regards to testers, I actually have a device now (my very own device! but no service haha) so I'm able to do testing on my own for intermediate builds. When I release a milestone build (I'd consider wifi and 3d accelerator a milestone build) I'll release it via PM.
I don't want to make the test builds public because I worry that it'd cause problems with people not reading the "WARNING! THIS DOESNT WORK RIGHT!" and coming back saying they bricked their phones.
However, as soon as I have something to show, I'll make a video
Woohoo! That's exciting. I miss stable CM7 so much. It was flawlesson my trusty Incredible, just getting to stable on the Fascinate, and now being started from scratch here.
If you ever need any help, Cubed, I'm game. I would have no qualms with it. I'm available at nearly any moment and always have a computer nearby for logcats and d/kmesg dumps. Plus, I have full services 3/4G and wifi all around me at almost all times.
I'd love to be able to help the community out, even if it's only by flashing and giving error logs.
I noticed when peeking around in the system that things were a little messy too. The build.prop is kinda iffy and their lack of an organized boot animation is annoying. It's like being neat wasn't a concern at all. Seems like they were in a hurry.
RegnierD said:
Woohoo! That's exciting. I miss stable CM7 so much. It was flawlesson my trusty Incredible, just getting to stable on the Fascinate, and now being started from scratch here.
If you ever need any help, Cubed, I'm game. I would have no qualms with it. I'm available at nearly any moment and always have a computer nearby for logcats and d/kmesg dumps. Plus, I have full services 3/4G and wifi all around me at almost all times.
I'd love to be able to help the community out, even if it's only by flashing and giving error logs.
I noticed when peeking around in the system that things were a little messy too. The build.prop is kinda iffy and their lack of an organized boot animation is annoying. It's like being neat wasn't a concern at all. Seems like they were in a hurry.
Click to expand...
Click to collapse
I will need people to test the 3G/4G service once I get the radios initialized, since I only have the phone and no service
Right now I'm still sorting through the binaries and libraries trying to get at a bare minimum wifi and 3d acceleration working.
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
All those able to make use of this information may want to look here.
http://forum.xda-developers.com/showthread.php?t=1609654
Hash said on twitter it was to much work to get this to work with the d3 and ics,unless I missunderstood his tweet the other day..
[email protected]_Carbone
kexec stuff for D3 isnt useful w/o a 3.x kernel. Which would be a ton of work.
@Motorola needs to say what's happening w/D3.
6:39pm - 28 Apr 12 via Plume for Android
Click to expand...
Click to collapse
I saw. Getting kexec itself up and running is one (positive) thing. Then wed need the 3.0 kernel. Kernel source of RAZRs ICS may not be far off and may help.
There are also people (search Kabaldan) who can pull of porting of kernel bits - as with the original Milestone and a similar exploit.
That guy is a genius.
Kabaldan its a great dev with huge skills and enthusiasm, i have milestone #1 so he was my little god.
maybe We should think or not to buy him one piece droid3: D all of us invest a some $$ but benefits will be enormous i thinkg
Get that person who startd the thread in the general section to send one theirs to him lol
Sent from my XT862 using Tapatalk
I think could try hash kindle kernel or even just use the .config from the 2.3.6 posted by moto and fill in the new options. Pretty sure the kernel itself will be easy once kexec is working
Give it a go Willis! we wait with baited breath. If you take on the project id say make a thread for progress updates and donations? Im sure thered be forthcoming donaters.
Ye it wouldn't be fair if D3 was left out
I think it is possible to just cut and paste until we get something solid for us right now.
Sent from my XT862 using XDA
^ joke?
Sent from my XT862 using Tapatalk
MrObvious said:
I think it is possible to just cut and paste until we get something solid for us right now.
Sent from my XT862 using XDA
Click to expand...
Click to collapse
Hmm...no.
Sent from my Galaxy Nexus using xda premium
Lol I'm messing duh.
Sent from my XT862 using XDA
Willis111 said:
I think could try hash kindle kernel or even just use the .config from the 2.3.6 posted by moto and fill in the new options. Pretty sure the kernel itself will be easy once kexec is working
Click to expand...
Click to collapse
I really wish it was that easy. :/ Unfortunately, in many cases kernel changes == userspace binary changes in the OS. And for those, I have no source. So if that item has been customized by Moto.. we're back to some of the hackery that we have now.
Something to keep in mind when checking out how the Kindle works: I was able to drop all of the Amazon custom binaries in favor of generic Texas Instruments alternatives. The Amazon customized android binaries had viable "from source" alternatives in almost every case. There is no way this would be possible for a Moto device. Too much customized hardware/software in the way.
And the Kindle is almost a play toy compared to a phone device. I didn't need to worry about:
Light sensors
Bluetooth
3g Modem
Keyboard
Camera
Etc
And while the base CPU is identical, everything changes from there:
Different charging driver
Battery gauge
LCD driver
Touchscreen driver
Audio driver
Wifi chip is even different and that's supposed to be part of the "system on a chip"
That being said, I know the D3 is probably in the worst looking shape regarding an update from Moto. And, I'm sort of mulling over how to do it right.
While I could probably do a few tweaks to a kexec kernel for:
- graphics drivers which fully support ICS (see: Chrome, RenderScript, etc)
- *maybe* get the backport working for open source hw codecs to support flash, netflix, etc. (I have a good bit of this done as kernel modules from back in January.. just didn't know why they were failing at the time)
But, I'm not sure it's worth the additional effort if we don't get things like camera / video recording working (will probably need custom Moto source for codecs -- open source won't do it). And updating the hw codec engine above would most likely break the current camera hack entirely.
I guess, I would need to see if Moto has any sort of upgrade path for the Droid 3. If they do, then I'd say hang tight and I'll get it integrated once they release something.
Otherwise, we as a community need to decide if a phone which is more ICS friendly but doesn't have a camera is worth it.
Maybe the answer is: finish the CM7 port into something which is more functional and bugfree.
Sent from my XT894 using Tapatalk 2
Hashcode said:
I really wish it was that easy. :/ Unfortunately, in many cases kernel changes == userspace binary changes in the OS. And for those, I have no source. So if that item has been customized by Moto.. we're back to some of the hackery that we have now.
Something to keep in mind when checking out how the Kindle works: I was able to drop all of the Amazon custom binaries in favor of generic Texas Instruments alternatives. The Amazon customized android binaries had viable "from source" alternatives in almost every case. There is no way this would be possible for a Moto device. Too much customized hardware/software in the way.
And the Kindle is almost a play toy compared to a phone device. I didn't need to worry about:
Light sensors
Bluetooth
3g Modem
Keyboard
Camera
Etc
And while the base CPU is identical, everything changes from there:
Different charging driver
Battery gauge
LCD driver
Touchscreen driver
Audio driver
Wifi chip is even different and that's supposed to be part of the "system on a chip"
That being said, I know the D3 is probably in the worst looking shape regarding an update from Moto. And, I'm sort of mulling over how to do it right.
While I could probably do a few tweaks to a kexec kernel for:
- graphics drivers which fully support ICS (see: Chrome, RenderScript, etc)
- *maybe* get the backport working for open source hw codecs to support flash, netflix, etc. (I have a good bit of this done as kernel modules from back in January.. just didn't know why they were failing at the time)
But, I'm not sure it's worth the additional effort if we don't get things like camera / video recording working (will probably need custom Moto source for codecs -- open source won't do it). And updating the hw codec engine above would most likely break the current camera hack entirely.
I guess, I would need to see if Moto has any sort of upgrade path for the Droid 3. If they do, then I'd say hang tight and I'll get it integrated once they release something.
Otherwise, we as a community need to decide if a phone which is more ICS friendly but doesn't have a camera is worth it.
Maybe the answer is: finish the CM7 port into something which is more functional and bugfree.
Sent from my XT894 using Tapatalk 2
Click to expand...
Click to collapse
I personally would love to see cm7 finished. For myself without working video I can't use ics as a daily driver, I need to use skype on my device often. And although its been awhile since I've used ics the battery life was pretty poor compared to gb
Sent from my XT860 using xda premium
If CM9 can be made to work with everything (flash, HW codecs) bar Video that would do me.
Otherwise CM7 completion gets my vote.
Also, how about when Bionic ICS hits? And are RAZR camera/hw codecs of no use?
CM7!
Sent from my DROID3 using XDA
slvrarrow said:
Also, how about when Bionic ICS hits? And are RAZR camera/hw codecs of no use?
Click to expand...
Click to collapse
Turns out the hwcodecs and kernel will be useless for Droid 3. This was something that I learned recently while building the new kernel to the Kindle Fire.
All of the settings in the new 3.0 kernels from TI are hard coded to 1GB RAM. Including the hw codec binary. For the Kindle I had to do quite a bit of rework and dynamic tiler modifications to get ICS running on it correctly.
Can't you use a 2.x Kernel?
slvrarrow said:
Can't you use a 2.x Kernel?
Click to expand...
Click to collapse
I don't think so, I believe ICS depends upon a 3.0 kernel, which is why he's been having such a hard time getting everything to work. He has to rewrite ICS code to work with what we have in our kernel that is meant for Gingerbread.
These are UNOFFICIAL nightlies of CM9 for the Droid Incredible
drk_hd has thrown together an awesome rom here: http://forum.xda-developers.com/showthread.php?t=1558923
But all of the same bugs still exist since its based off the same code.
I've done is scripted his build instructions posted here: https://github.com/drkhd/android_device_htc_inc/blob/ics/README.md
Also have added a few tweaks here and there
Follow the twitter feed here which should link you to the latest successful build after it is done: http://www.twitter.com/invisiblek_cm
Or check out this link to find the latest 'successful' build: http://goo.im/devs/invisiblek/dinc/cm9.unofficial.nightlies
goo.im sometimes take a few minutes (up to a half hour sometimes) to actually replicate the files that are uploaded. Please be patient.
Latest gapps here: http://goo.im/gapps
All the necessary rules apply here: I offer official no support here nor take no responsibility for you, your phone or who you may injure by throwing your phone in a fit of rage.
NANDROID FIRST!!! These are extremely experimental!
Major thanks to:
cyanogen and his awesome team for all their work
the evervolv team (MongooseHelix and drewis) for their device tree and many other things that made this possible
drk_hd for mashing this stuff up and putting together a guide on how to build it
cayniarb for the kernel and all the work he does for our devices
s0up and all the goo.im guys
many others i'm sure i'm missing...
ISSUES
Code:
[SIZE="4"]
- Camcorder doesn't work
(apparently there's a 3rd party market app that will work)
- Some people are experiencing freezes when unplugging
Please track that issue here: [url]http://tinyw.in/JUIb [/url]
- Others??
[/SIZE]
CHANGELOG
Code:
[SIZE="4"]
6-21-12
- back to the inline kernel. compiled with -O3 but using the old toolchain
6-20-12
- using a prebuilt kernel now. built with linaro gcc 4.7
6-18-12
- tweaked sd/emmc read_ahead: [url]http://tinyw.in/czFp[/url]
6-17-12
- MMS fixed upstream: [url]http://review.cyanogenmod.com/#/c/17822/[/url]
5-30-12
- another fix due to an overlay that disabled some pretty effects
commit here: [url]http://bit.ly/L3bFF2[/url] [B](thanks mamarley!)[/B]
5-28-12
- updated adreno drivers from CAF
- notification power widget LED flashlight now enabled
5-27-12
- applied a fix for the gpu regression detailed here: [B](thanks mamarley!)[/B]
[url]http://review.cyanogenmod.com/#/c/16028/[/url]
- enabled torch.apk (still not in notification power widget)
5-26-12
- added a slightly modified kernel that contains several cpu governors
5-24-12
- fixed sensors (prox, brightness, accelerometer, etc)
was using drk.hd's old device tree
- goo'ified the rom so it shows in goo-manager
[/SIZE]
Quick Links
Code:
[SIZE="4"]
Twitter feed for builds: [url]http://www.twitter.com/invisiblekcm9ka[/url]
Links to all nightlies: [url]http://goo.im/devs/invisiblek/dinc/cm9.unofficial.nightlies[/url]
Gapps: [url]http://goo.im/gapps[/url]
My github: [url]http://www.github.com/invisiblek[/url]
Unofficial changelog: [url]http://cm-kang.appspot.com/inc/ics[/url]
[/SIZE]
Thank you! I was hoping someone would do this. Crackflasher's gotta get his fix ya know
nice to see this, Thanks for your contribution .
Crackflashers will be able to leave rehab now, nicely done!
Sounds good I've been eager for a cm9 update, I'm going to flash this soon
Sent from my ADR6300 using Tapatalk 2
Accelerometer doesn't rotate screen on latest.
xport said:
Accelerometer doesn't rotate screen on latest.
Click to expand...
Click to collapse
+1 I can confirm that also.
xport said:
Accelerometer doesn't rotate screen on latest.
Click to expand...
Click to collapse
yep and the LED isn't working here
Can someone clarify - is "official" CM implementation of ICS for DInc being worked on? Or has DInc been dropped from the list of official CM targets for ICS due to some reasons (obsolete/lack of driver binaries/etc)?
It's not supported mostly because there's no maintainer to submit patches to the CM team The same for other older phones like Evo. Now there may be other reasons but this is the primary one.
Woah, let's not start rumors. http://forum.xda-developers.com/showthread.php?p=24081082 read that one, as well as mine on the two pages before that.
In essence, we have one maintainer, CUViper, and he's busy with work. Once it settles down, he'll try and get us up and running. Drk.hd is doing his best to get as much up as possible for CUViper to look at through Gerrit. Meanwhile, I'm just helping out where I can, mainly by troubleshooting and answering questions like these. Not much else I can do with no computer.
Tl;Dr yes it's being worked on. Eta: none. Promises for getting official CM9 on the Inc: see answer for eta.
Editorial side note @invisblek: since you got this at goo.im, why don't you make it Goo Manager compatabile (or ROM Manager compatible)?
Happy to have some sort of Cm9 than none. Weather or not it gets supported.
Sent from my ADR6300 using Tapatalk 2
Looks like proximity sensor (turning screen on and off during calls when moved away and close to face) is not working either.
Great work, glad to see this thread open up and hope that things progress.
new build coming up
sensors fixed (i was using drk.hd's old build method)
prox, brightness, accelerometer, etc
goo-inside.me'ified too
With the builds previous to the one you just mentioned I've been having force restarts. Besides that and the rotation issue, it's beatiful.
Great work!
@invisiblek, you don't have to upload the md5 file at goo, since it automagically creates and displays it. Goo Manager app actually checks and compares them, too.
warpurlgis said:
With the builds previous to the one you just mentioned I've been having force restarts. Besides that and the rotation issue, it's beatiful.
Great work!
Click to expand...
Click to collapse
Does it reboot all the way to your bootloader or just the cm boot screen?
If the former, I'd be interested in seeing your /proc/last_kmsg after one of these reboots. The latter, I'd recommend a data wipe.
PonsAsinorem said:
@invisiblek, you don't have to upload the md5 file at goo, since it automagically creates and displays it. Goo Manager app actually checks and compares them, too.
Click to expand...
Click to collapse
Long gone are the days of doing things manually I suppose.... thanks Pons
Invisiblek my God you have been gone so long that I don't think a lot of people remember you were a legend here when it came to dinc kernel development and a tie for the best with Chad's so let me first say I am stoked to see tour return. Second I just finished downloading your first nightly and I'm gonna report back to you about it after I flash. Lastly a question for ya and I'm sure is on all the minds of anyone that ever uses your gb kernels....any chance of you taking stab at updating your work and making an ics kernel for us dinc users. I mean dude I'd be happy honestly if you just did a couple of betas just to get the bugs out and then made one final release. I'd be like a giddy school boy on the night before Christmas. You shouldn't of seen my eyes when I was reading pons reply and he said your name I was like huh that can't be him and then I went back to op and checked out your profile and long behold it was you. Anyway ty for all your work now and in the past in my eyes your a legend with dinc development.
Sent from my ADR6300 using xda premium
wetbo529 said:
Invisiblek my God you have been gone so long that I don't think a lot of people remember you were a legend here when it came to dinc kernel development and a tie for the best with Chad's so let me first say I am stoked to see tour return. Second I just finished downloading your first nightly and I'm gonna report back to you about it after I flash. Lastly a question for ya and I'm sure is on all the minds of anyone that ever uses your gb kernels....any chance of you taking stab at updating your work and making an ics kernel for us dinc users. I mean dude I'd be happy honestly if you just did a couple of betas just to get the bugs out and then made one final release. I'd be like a giddy school boy on the night before Christmas. You shouldn't of seen my eyes when I was reading pons reply and he said your name I was like huh that can't be him and then I went back to op and checked out your profile and long behold it was you. Anyway ty for all your work now and in the past in my eyes your a legend with dinc development.
Sent from my ADR6300 using xda premium
Click to expand...
Click to collapse
Haha thanks. I'll be honest though, much of the work I did on kernels was kanging other peoples' code though.
I've been planning to roll a kernel one of these days...
Is there a ICS kernel we can run with this? I tried the incredkernel ics and as soon as the boot screen loaded phone went blank.
Sent from my ADR6300 using xda premium
So I've just flashed OmniROM on my LG Optimus 4X HD (p880). Probably this is the first unofficial build, built from Gerrit repos, I'm really proud of myself.
I'm pretty impressed that there were only a few changes needed and almost everything works, only BT doesn't work (easy to fix). I really like the quick settings flipping and how it shows Wi-Fi IP address when flipped. :good: I attach some screenshots.
Adam77Root said:
So I've just flashed OmniROM on my LG Optimus 4X HD (p880). Probably this is the first unofficial build, built from Gerrit repos, I'm really proud of myself.
I'm pretty impressed that there were only a few changes needed and almost everything works, only BT doesn't work (easy to fix). I really like the quick settings flipping and how it shows Wi-Fi IP address when flipped. :good: I attach some screenshots.
Click to expand...
Click to collapse
Is this build available for download? Really eager to try it out
And will you be maintaining for the P880 on a Nightly/Weekly/whenever flexibly based? Sorry for asking that, just curious
penguin449 said:
Is this build available for download? Really eager to try it out
And will you be maintaining for the P880 on a Nightly/Weekly/whenever flexibly based? Sorry for asking that, just curious
Click to expand...
Click to collapse
Not yet. It's not even built from published sources, though there isn't much change in published ones yet.
Yes, probably I will.
Nice to see
In terms of going forward in terms of builds, we will be addressing these issues when we can. For now though, Omni isn't "officially" released in any kind of binary packages.
When the time comes, we will invoke the release processes, which will give nightly builds, with a weekly "tagged build". On Omni, nightly builds are expected to be stable, and encourage bug reports on them. A "weekly" is just a nightly that is tagged as "working fine", for those who don't want to update every day.
pulser_g2 said:
For now though, Omni isn't "officially" released in any kind of binary packages.
Click to expand...
Click to collapse
Not anymore: http://forum.xda-developers.com/showthread.php?t=2481929
When OmniROM is going to be released on Nexus 4?
I hope they will have their own theme going on soon...was hoping it wouldn't look like cm/aokp out of the box lol
mgbotoe said:
I hope they will have their own theme going on soon...was hoping it wouldn't look like cm/aokp out of the box lol
Click to expand...
Click to collapse
I hope it looks like AOSP out of the box, who cares about CM/AOKP?
Testraindrop said:
I hope it looks like AOSP out of the box, who cares about CM/AOKP?
Click to expand...
Click to collapse
Considering cm/aokp look just like aosp...I care it dont look like that o.o
Can somebody who's already built and run the ROM do a hands-on impressions video of it?
mgbotoe said:
I hope they will have their own theme going on soon...was hoping it wouldn't look like cm/aokp out of the box lol
Click to expand...
Click to collapse
The current look is the "AOSP" look. I imagine that longer term, there will be reason to look into modular theming systems. A lot of people want a "pure android" look, and generally the best way to avoid breaking things is to make any themes optional extras.
pulser_g2 said:
The current look is the "AOSP" look. I imagine that longer term, there will be reason to look into modular theming systems. A lot of people want a "pure android" look, and generally the best way to avoid breaking things is to make any themes optional extras.
Click to expand...
Click to collapse
Thank you, you kind sir for the response
Sounds really nice guys!!! Happy to see entropy and xplod working on android roms again after the cm thingy! Also nice to see that maxwen is working on this!
Made a build for the Nexus 10. I installed it breefly and from what i could see is that it is indeed mostly AOSP. Nice touch is the rotating tiles. If you rotate the wifi tile, you will see the ip adres.
Anyway i am still too much used to some CM additions (like the ability to close all apps at once).
It is a good start and will keep an eye on the development.
scanno said:
Made a build for the Nexus 10. I installed it breefly and from what i could see is that it is indeed mostly AOSP. Nice touch is the rotating tiles. If you rotate the wifi tile, you will see the ip adres.
Anyway i am still too much used to some CM additions (like the ability to close all apps at once).
It is a good start and will keep an eye on the development.
Click to expand...
Click to collapse
More features on the way
It's mostly AOSP right now, we are currently in the process of adding a lot of the "useful" parts we know and love. If you want to get involved, feel free to do so on Gerrit.
pulser_g2 said:
More features on the way
It's mostly AOSP right now, we are currently in the process of adding a lot of the "useful" parts we know and love. If you want to get involved, feel free to do so on Gerrit.
Click to expand...
Click to collapse
Already created an account
Sent from my TF300T using Tapatalk 4
So another build for i9500
Everything is working except Bluetooth
Love it ^^
I've installed tilal6991's build on my Xperia T and it works like a charm. No superuser for some reason but otherwise it's perfect! Can't wait for this project to mature
Sent from my Xperia T using Tapatalk now Free
Made a build for HTC Explorer,and it's running great,albeit with a few bugs(most are easy to fix)
The major thing i noticed was that all 4.3 roms for this device have a "lockscreen lag bug",but this doesn't!
sakindia123 said:
Made a build for HTC Explorer,and it's running great,albeit with a few bugs(most are easy to fix)
The major thing i noticed was that all 4.3 roms for this device have a "lockscreen lag bug",but this doesn't!
Click to expand...
Click to collapse
Woah dude, you got this running on an Explorer? That thing is like...ancient. I didn't even think it would be capable of Android 4.1+ Props!