Since many people asked what I was doing these days:
The Nook Color running a healthy mix of Android 3.1 Honeycomb from the Xoom and Android 3.1 from Google's SDK.
As can be seen towards the end the Launcher application suffers from some drawing issues. The same issues can be observed in Google's SDK 3.1 emulator. The emulator and the nook both are doing software UI rendering instead of the new in 3.0 hardware accelerated UI rendering. Sadly the PowerVR SGX530 drivers that are (publicly) available right now are lacking some features to activate the hardware UI rendering on the nook. (like support for EGL_SWAP_BEHAVIOUR = EGL_BUFFER_PRESERVED
and the GL_OES_EGL_image_external extension). I started patching around those issues, which is hard without the access to the Android source, and can confirm that the nook's hardware is more than capable of running 3.0/3.1 hardware accelerated even though the source might need some patches if we don't get updated drivers for the SGX530.
So the status right now is: software UI with redraw issues or hardware UI with a working home screen but tons of more issues in other applications.
Other than that sound, wifi and opengl works. (no DSP/video decoding so far)
So who's up for solving the redrawing issues?
Possible solutions are:
getting our hands on a newer SGX530 driver than 1.1.16.4061
unpacking, patching and repacking Launcher2
?
waiting until Google releases the 3.1 AOSP source
-Rafael Brune
It sucks but I feel our best bet is just to wait for source. There are a lot of honeycomb tablets slated for release over the next few months, I think once it becomes more widely available we'll see source.
Since we dont know when will be... all the time, effort, and trouble to get it fully working witout source - will be in vain once the source drop happens.
So unless the people involved don't care, cm7 is more than enough for now. We are lucky to even have that, my phone doesn't even have cm7 working for it.
My .2 anyways
Sent from my SCH-I500 using XDA App
The problem is, Google has stated they won't be releasing Honeycomb source until it's integrated with the phone branch. I personally doubt that we see real source until Ice Cream is out.
honeycomb source will never be released, google said so, we'll get Ice Cream Sandwich source which will be awesome on our nook's i'm sure
ok all of you guys are real downers when you pretty much say "give up, source is the only way" now i know thats not what your literally saying but thats what im getting from your posts
@deeper-blue
good job dude, i would love to see a beta for this if its as stable as honeycomb v4(knowing your work it will be) a side from a few graphical errors(im assuming the same ones from the first SDK port) i think it can and probably will be a daily driver for most people here
Any hope for USB host support with the port or once again not till source
Sent from my Vision using XDA Premium App
deeper-blue said:
Since many people asked what I was doing these days:
http://www.youtube.com/watch?v=RJ_k4kdsaMk
So who's up for solving the redrawing issues?
Possible solutions are:
getting our hands on a newer SGX530 driver than 1.1.16.4061
unpacking, patching and repacking Launcher2
?
waiting until Google releases the 3.1 AOSP source
-Rafael Brune
Click to expand...
Click to collapse
hey THANKS for posting up what you've done and this very cool video... that was just awesome to see how far someone has gotten to get 3.1 running WELL on the nook.
mad props.
Nice work rafael!
Sent from my NookColor using Tapatalk
can't really help you out, but I'd just like to cheer you on
+1 !
Keep up with the excelent work !!!
botossi said:
+1 !
Keep up with the excelent work !!!
Click to expand...
Click to collapse
luigi90210 said:
ok all of you guys are real downers when you pretty much say "give up, source is the only way" now i know thats not what your literally saying but thats what im getting from your posts
@deeper-blue
good job dude, i would love to see a beta for this if its as stable as honeycomb v4(knowing your work it will be) a side from a few graphical errors(im assuming the same ones from the first SDK port) i think it can and probably will be a daily driver for most people here
Click to expand...
Click to collapse
Completely agree, there are a couple of interesting apps in the market that take advantage of HC and would be great in the Nook.
If you ask me waiting for AOSP don't look as such a good idea, since it's release is not so sure.
deeper-blue: Quick question: which HC image are you running in the posted video?
Since the initial SDK image you did, I've not seen any run that smoothly.
arrjaytea said:
deeper-blue: Quick question: which HC image are you running in the posted video?
Since the initial SDK image you did, I've not seen any run that smoothly.
Click to expand...
Click to collapse
He is running 3.1, which he has been working on and has yet to release because of the bugs he demonstrates in the video.
Great work DB, really excited to see the progress on this. I'm just wondering - would it be feasible to run this with ADW or similar as a holdover until the Launcher2 rendering issues are resolved?
Sounds like patching the launcher will be the easiest route. This is why I love you DB ahhaha, your work is amazing.
Hi deeper-blue,
If you want, I can offer you my help. I would be able to try to patch launcher2. I've been able to work out a few stuff in launcher2 when I was doing test builds of HC 3.0 and 3.1.
I'm trying to look if I can find some drivers for the PowerVR SGX530, but I unfortunately can't help by making 3.1 available on AOSP.
Is there a pointer to instructions on how to cook from SDK ? Have been looking around and have not found anything useful.
Wanted to take a crack at the graphics driver portion.
Very nice work deeper-blue.
Don't let the lazy people uninspire your work. If the Android and Open-source community in geral would wait for corporations solutions linux would never have been created. This is the open-source spirit, guys. If you come here to say that open-source hackers should wait, you're on the wrong place doing the wrong stuff.
Back to honeycomb, even before this 3.1 news I was noticing that one of the main limitations we have on honeycomb is the laucher. I suggest that while we can't hack it (but we will keep trying), we use honeycomb with another launcher just for the sake of using the great tablet oriented apps we can't have on cm7.
About the source code, for me Google made clear that they weren't releasing it for a while. So, I think this is more motivation to make a honeycomb daily driver.
Keep up the great work, Good luck everyone and all hail to this awesome community.
--
Marlon Moura
Keep at it man, we appreciate the work.
Unfortunately I lack the technical expertise to help keep this moving forward; however, I think an earlier poster was dead in his argument that waiting for source code is defeatist mentality for the open source "hacking" gurus out there.
I imagine that Deeper-blue could turn this into a truly polished machine....if he had the time to devote endless amounts of hours to this, but who does and that's why he's seeking assistance from other willing and capable hands.
If anything I hope others who are capable find some inspiration in the challenge and ultimately crack this one into something special.
Thanks in advance to Deeper - blue and other who continue to provide users with a cost effective tablet experience.
-Rt
Related
Let me preface this by saying that I have nothing but the utmost respect for the dev community (NC and otherwise) and I really don't mean to step on any toes with this. I'm fairly new at all this and I've got some questions.
Alright, so as we've all heard by now, Google (whether their reasons are benevolent or not) are withholding the AOSP release of Honeycomb and that kind of rains on everyone's nook color parade. We've got a mostly working port of HC that kind of sags in the performance area. Its almost been enough to make me flash Gingerbread but there are a few things - namely the browser, email app, soft keys and notification system - that I'd miss. The new + screen is nice, but I've been using launcher pro as it runs seemingly faster than the stock launcher, so I'm already missing out on that.
Now, from what I understand, and feel free to correct me if I'm wrong, deeperblue's HC port uses parts of Gingerbread to make everything all hunky dory.
My question is this; would a viable solution to slow HC performance be to make a new rom and pump MORE Gingerbread in? i.e. Take HC's notification system replace GB's phone-style notification pane. Make it mostly gingerbread with some tablet friendly nip/tucks here and there.
I realize there are things like softkeys and the bottom taskbar mod, but HC's handling of the android buttons and the new notification system is just so appealing. Its making the choice of which rom to run unduly difficult. And while I can't cook a rom, I'm hoping someone who can sees this and runs with it, if it is feasible, that is.
Truthfully... It's up in the air like everything else, unless a DEV directly comes out of the shadows and saids, hey i'm going to do it... Then we just won't know. Honestly, I'm sad that we won't see HC right around the corner, but CM7 is pretty awesome. And the Xoom is scheduled to drop down to $599 (Wifi only) today, making it a lot more competitive than the 3g.
That's not to say that I personally have $599 to drop and go buy a new tablet, but it does mean that you'll probably see them on craigslist or ebay in a few months for a bit cheaper. =\
The honey comb preview is awsome but to many apps don't work.
Tyfighter said:
My question is this; would a viable solution to slow HC performance be to make a new rom and pump MORE Gingerbread in?
Click to expand...
Click to collapse
That was kinda the plan. CM7 development was going in a way that all the improvements (Bluetooth, partially working DSP, an accelerated interface) were going to be directly ported to Honeycomb once the source released. But without the source, that can't happen.
Basically Google has completely screwed any Nook Color fans wanting Honeycomb.
The only improvement that can be made is that a ROM could be made from the final SDK. That would be just as laggy, and will lack new features (Bluetooth, DSP, etc.), but it would be able to use Android tablet apps.
From the conversation about Google's move on the net, many are saying there won't be a Honeycomb source at all, and the next source dump will come with Ice Cream months from now.
So Honeycomb fans have a choice- either try out the CM7 modification that you talked about to make CM7 more Honeycomb-like, or start saving up for that Xoom...
[email protected] said:
The honey comb preview is awsome but to many apps don't work.
Click to expand...
Click to collapse
what apps dont work? most of the major ones have worked for me so far...
im finding that the hc rom is very usable for a daily driver...although bluetooth and dsp support would be very nice...
nolook said:
what apps dont work? most of the major ones have worked for me so far...
Click to expand...
Click to collapse
Any Tablet app that requires the final SDK version (aka all those Xoom apps) won't work on our preview build.
poofyhairguy said:
Any Tablet app that requires the final SDK version (aka all those Xoom apps) won't work on our preview build.
Click to expand...
Click to collapse
Thank you for your informative reply.
It seems now that my best bet is going to be t see what the cm7 guys cook up. Hopefully this aosp business will spark some of the innovation that the android community is known for. I'd love to help, but its not exactly my forte
With regards to what apps aren't working, my marketplace only seems to intall apps when the stars are right. I often have to attempt an install upwards of five times to have it succeed, if it even does. Otherwise i get insufficient storage errors or indeterminate error 18
sorry if i am hijacking this a bit, but i had thought that android was 'open source'. why the change in the plans to not release hc? is this to protect the hw manufacturers like mot who have hc on the xoom, and freeze out users who want it ported non supported platforms? Otherwise, I can't understand the logic.
I got the nc cause i had thought it had the best $/performance of any android based tablet. For half the price of others, it had great screen, and forgetting bt, etc., nice hw specs. With hc, it would be fantastic!
How else to counter ipads if not to get hc on as many tablets as possible?
I wonder if the fact that the playbook is running our apps has anything to do with it. If so, I don't mind anything that makes it rough for RIM.
Sent from my Desire HD using XDA App
jbinbi said:
sorry if i am hijacking this a bit, but i had thought that android was 'open source'. why the change in the plans to not release hc? is this to protect the hw manufacturers like mot who have hc on the xoom, and freeze out users who want it ported non supported platforms? Otherwise, I can't understand the logic.
Click to expand...
Click to collapse
It is open source and it WILL be released however at this time they don't think it's ready for final release (I've heard of various tweaks they need to make in the xoom) and are working those out prior to releasing it to devs
For those brave souls using Honeycomb daily on their Nooks, what kind of tweaks are you doing to help with performance/compatibility?
Thanks in advance!
Bot
I'd also like to know if there are tweaks you can do to makc HC stable/perfered for the nook, anyone using it full time?
If you already have it installed on the eMMC with an overclocked kernel you have done all you can do.
Honeycomb development pretty much died the day Google said that their was going to be no source code release. We might never see a "stable" Honeycomb for the Nook Color.
With that said, many people has been working on making Froyo and CM7 better in Honeycomb's absence. I personally think the Tablet Tweaks CM7 version is more useable than even the Honeycomb on a Xoom I tried (at least our SD card slots work), and for people who are DYING for Honeycomb there is the NookieComb which is Froyo hacked to act like Honeycomb.
Take a look at the development forum for more information.
you can turn off all transition animations to get a bit of a speed boost...also opera mobile is much faster (but not as nice) as the HC browser
im running it off emmc and its actually very stable for web/reading...video isnt great yet and there is a bit of UI lag but IMO very usable...
I thought Google said they just delayed the 3.0 release. I read into that that 3.0 is a disaster right now and they are still trying to make it a clean product. I think Ipad is scaring them and they are moving into overdrive at Google trying to get ahead (meaning 3.0 came out before it was really ready).
I totally agree. Google doesn't want to let a half baked product out the door when you know the ipad 2 will be stellar.
Sent from my NookColor using Tapatalk
swaaye said:
I thought Google said they just delayed the 3.0 release.
Click to expand...
Click to collapse
The head developer of Android has said that AOSP won't be released until the phone features are merged, which means no code until Ice Cream.
So if the original ETA for Ice Cream was summer 2011, then I guess we see nothing until at least Christmas?
Meaning that Android tablets have been dealt a death blow for <b>another</b> year?
I am so glad for the independent developers working so hard at XDA.
xdabr said:
So if the original ETA for Ice Cream was summer 2011, then I guess we see nothing until at least Christmas?
Meaning that Android tablets have been dealt a death blow for <b>another</b> year?
I am so glad for the independent developers working so hard at XDA.
Click to expand...
Click to collapse
i could be wrong but am pretty sure something will get 'leaked' before then....
I don't think Google minds -too- much that they are slowing down tablet development anyway. They've made it clear they want the "final solution" for tablets to be ChromeOS. Android for tablets is just a stop-gap measure.
P
jahfry said:
I don't think Google minds -too- much that they are slowing down tablet development anyway. They've made it clear they want the "final solution" for tablets to be ChromeOS. Android for tablets is just a stop-gap measure.
Click to expand...
Click to collapse
When did google say this?
Sent from my always stock, EC05 Epic 4G
Is there any advantage to the overclock kernel? I have the regular kernel running at 1100 with CPU Tuner (unless the overclock kernel comes in v2 by default)
already about 5 ics roms not counting the cm9 alpha, why??
they all have the same bugs
they all have the same things working
super ics kangorama?
http://forum.xda-developers.com/showthread.php?t=1360567
koush's + launcher pro added..
nexus mv ics?
http://forum.xda-developers.com/showthread.php?t=1364411
koush's + glados kernel + v6 supercharger
ultimate ics?
http://forum.xda-developers.com/showthread.php?t=1363765
koush's + some extra wall papers + file explorer
all these things are just a completely alpha ics build with some hacks thrown in.. why?? why not just make a post in the ics thread (either by kwiboo or koush) saying "hey guys use launcher pro if you feel its buggy" or "here is link to glados kernel" instead of making "New ultimate sweet fast ICS rom" when all you are doing is downloading one of the actual source built ics roms and opening it with 7zip and dropping in a new boot.img in there then asking for donations :/
/rant
It is no different than the numerous GB/CM based ROMs. Who cares?
Bounced off a tower to a forum near you!
I think that He ( OP ) won't be happy until they say Beta.. its alpha for a reason. so many bugs much more than beta. just sit happy with GB and give it time. I rushed it and lost the ability for Google Wallet, nothing can fix what went wrong with my phone.
xjreyes said:
I think that He ( OP ) won't be happy until they say Beta.. its alpha for a reason. so many bugs much more than beta. just sit happy with GB and give it time. I rushed it and lost the ability for Google Wallet, nothing can fix what went wrong with my phone.
Click to expand...
Click to collapse
What happened? I had wallet set up and ready to go, tried it at rite aid and wouldn't go through...
Sent from my Nexus S using XDA App
these people couldn't be taking part in a hobby for them, could they be just trying to learn the ins and outs of android, heck they couldn't even be kids learning to code and all are getting excited to show off what they complied.
Last time I checked you were not required to flash every rom in the Dev section. So lets take a step back I don't like miui nothing wrong with it but should I be complied to start a thread asking why we have topics about when I don't care for it.
icecoldbong said:
/rant
Click to expand...
Click to collapse
You said it....
Chill out. We have to get AOSP working bug-free in the first place, then they'll start looking different. Even CM9 doesnt have any CMsettings or anything special. We're sorry that something that we're beating Google at (ICS release for NS) currently is not to your standards.
In due time.....in due time.
I see where the OP is coming from, but I disagree. The fact that the devs work hard to bring the OS to our devices is pretty appreciated. They pretty much do Google's work for free by modifying the code.
Sent from my Nexus S using XDA App
icecoldbong said:
already about 5 ics roms not counting the cm9 alpha, why??
they all have the same bugs
they all have the same things working
super ics kangorama?
http://forum.xda-developers.com/showthread.php?t=1360567
koush's + launcher pro added..
nexus mv ics?
http://forum.xda-developers.com/showthread.php?t=1364411
koush's + glados kernel + v6 supercharger
ultimate ics?
http://forum.xda-developers.com/showthread.php?t=1363765
koush's + some extra wall papers + file explorer
all these things are just a completely alpha ics build with some hacks thrown in.. why?? why not just make a post in the ics thread (either by kwiboo or koush) saying "hey guys use launcher pro if you feel its buggy" or "here is link to glados kernel" instead of making "New ultimate sweet fast ICS rom" when all you are doing is downloading one of the actual source built ics roms and opening it with 7zip and dropping in a new boot.img in there then asking for donations :/
/rant
Click to expand...
Click to collapse
you missed these two.. http://goo.gl/bdy4w and http://fitsnugly.euroskank.com/sammich/crespo/
i can probably find you a few more if you would like more variety
simms22 said:
you missed these two.. http://goo.gl/bdy4w and http://fitsnugly.euroskank.com/sammich/crespo/
i can probably find you a few more if you would like more variety
Click to expand...
Click to collapse
lol im not mad that they are all buggy, im mad that people are "deving" with a buggy base and just adding to it. why not be a little patient, if you cant create it/build it from source, wait til the base you will be using to 7zip and copypaste into your rom becomes stable. dont use an alpha build to promote your name
icecoldbong said:
lol im not mad that they are all buggy, im mad that people are "deving" with a buggy base and just adding to it. why not be a little patient, if you cant create it/build it from source, wait til the base you will be using to 7zip and copypaste into your rom becomes stable. dont use an alpha build to promote your name
Click to expand...
Click to collapse
I don't think you quite understand how it works currently. There is no buggy base. They're attempting to adapt AOSP source code to compile and execute correctly on the Nexus S. This is way more complicated than you think. Almost all "bugs" you see are byproducts of tinkering with configurations, compile-ations, etc, in an attempt to get it working properly.
To put things in perspective, ICS development for the Nexus S is light years ahead of all other devices. For that reason alone, we should be grateful. Others are still struggling to either boot, or get somewhere AFTER boot.
If you don't like the way it's done, then wait for the official ROM. You have a choice, after all.
nickmv said:
I don't think you quite understand how it works currently. There is no buggy base. They're attempting to adapt AOSP source code to compile and execute correctly on the Nexus S. This is way more complicated than you think. Almost all "bugs" you see are byproducts of tinkering with configurations, compile-ations, etc, in an attempt to get it working properly.
If you don't like the way it's done, then wait for the official ROM. You have a choice, after all.
Click to expand...
Click to collapse
yes, two roms are getting built from the source on xda; kwiboo and koush. then all the others.
both kwiboo and koush thread is full of bug reports of people using a different rom like brainmaster, ultimate ics, kangorama ics, etc.
all this does is add confusion from the rom chef adding things to the original rom developers work
what im suggesting/ranting is that if a rom chefs should be a little more patient in making more spinoff roms that don't really add much besides to confusion for noob users
Your argument makes a LOT more sense now. I agree, if people are posting bugs in Koush/Kwiboo sections when running brainmaster or other tweaked versions, then that's bad.
Your original argument didn't really point this out.
Not much can be done about that, aside from aggressive moderation. Tweakers will be tweakers.
nickmv said:
Your argument makes a LOT more sense now. I agree, if people are posting bugs in Koush/Kwiboo sections when running brainmaster or other tweaked versions, then that's bad.
Your original argument didn't really point this out.
Not much can be done about that, aside from aggressive moderation. Tweakers will be tweakers.
Click to expand...
Click to collapse
Most of the bugs posted are not even valid. One in particular is known issue even on the GNexus.
The biggest issue I see is code optimization at this point.
One thing I think no one has mentioned is ICS may never be super fast on the NS. I will be much faster on dual core hardware
Bounced off a tower to a forum near you!
RonnieRuff said:
One thing I think no one has mentioned is ICS may never be super fast on the NS. I will be much faster on dual core hardware
Click to expand...
Click to collapse
This is one thing that has been bothering me as well. Every single one of these ROMs are not truly as smooth as Gingerbread. In no way do they even reach the fluidity found in Gingerbread ROMS. The hardware acceleration helps, but even then you can still feel the difference between the two Android releases. I have yet to hear a proper explanation as to why this is happening and I was hoping that the fix for this would be Google releasing the official Ice Cream Sandwich update.
Is it is code optimization as you say? Or is there more to it than that? I want to believe that hardware doesn't play a significant role here.
Eclair~ said:
This is one thing that has been bothering me as well. Every single one of these ROMs are not truly as smooth as Gingerbread. In no way do they even reach the fluidity found in Gingerbread ROMS. The hardware acceleration helps, but even then you can still feel the difference between the two Android releases. I have yet to hear a proper explanation as to why this is happening and I was hoping that the fix for this would be Google releasing the official Ice Cream Sandwich update.
Is it is code optimization as you say? Or is there more to it than that? I want to believe that hardware doesn't play a significant role here.
Click to expand...
Click to collapse
Agree 100% no released rom before ota is even out is worth running.. I ran koush or w/e and it worked but felt like I was holding a brick.. ruff! Brainmasters straight looks like android donut.. but so does cyanogens.. no disrespect to any of the above.. but htcclay is god..
Edit: wasn't brainmaster it was some one else.. sorry
Sent from my iPhone 4S using Siri
BLEEDCOLORYOU said:
Agree 100% no released rom before ota is even out is worth running.. I ran koush or w/e and it worked but felt like I was holding a brick.. ruff! Brainmasters straight looks like android donut.. but so does cyanogens.. no disrespect to any of the above.. but htcclay is god..
Edit: wasn't brainmaster it was some one else.. sorry
Sent from my iPhone 4S using Siri
Click to expand...
Click to collapse
Strange, I've found that Koush's latest (CM9 Alpha 11) is plenty fast, not significantly slower than GB. Definitely Kwiboo v2 was slow as molasses, but then again it came out days ago (a long time when it comes to how fast things are moving). BM v5 is pretty fast but buggy. Also, it seems that adding franco kernel to any of these also speeds things up significantly, but I haven't tried it with CM9 Alpha 11 yet.
oakamil said:
Strange, I've found that Koush's latest (CM9 Alpha 11) is plenty fast, not significantly slower than GB. Definitely Kwiboo v2 was slow as molasses, but then again it came out days ago (a long time when it comes to how fast things are moving). BM v5 is pretty fast but buggy. Also, it seems that adding franco kernel to any of these also speeds things up significantly, but I haven't tried it with CM9 Alpha 11 yet.
Click to expand...
Click to collapse
I found kwiboo's to be a lot more stable than koush's. although koush's had more functionality.. my bluetooth didnt work, and i got many errors.
Understand that we are using old binaries. ICS will run just as good as gingerbread, if not, better. These will make a world of difference
RonnieRuff said:
One thing I think no one has mentioned is ICS may never be super fast on the NS.
Click to expand...
Click to collapse
I'd kind of disagree with this. In its current early state here on the NS, I've gotten it running butter smooth and highly responsive, on a 1.1 OC/UV kernel. This is WITHOUT tweaks to filesystem, etc. If certain apps would just display properly when GPU Rendering is turned on, and some battery stuff worked out, I'd be 100% content.
Now granted, I've seen it running on the SGS2 and Galaxy Nexus and they're clearly speedier, but in my experience, my apps run just as fast as they did in GB.
On a side note....wanna see slow? It's been ported to the T-Mobile G1! HA! The first, original android phone!
I agree. there was actually a recent article on android police about this. There is no problem with people making their own roms but don't clog up the development section with "roms" that really all they do is bundle some easily downloadable market apps and some wallpapers and call it a new rom.
What the SGS2 xda forum actually did was split the dev section into 2 . One for original dev work and one for spin offs.
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
Before any of you say anything negative this isnt to bug other devs this is a thread for people to request/ ask for things me and the other devs to do after they have finished their other projects.
-Firefox OS
-LG UI(fix lockscreen)
-CM7
-Sense 4.1
-cm10.1 WiFi and Bluetooth
-cm10 WiFi authentication issue
-S-OFF
-Roms for cdma version
-Sense 4.1.2
Just pop requests underneath and ill update reguarly.
Shad0wPanda said:
Before any of you say anything negative this isnt to bug other devs this is a thread for people to request/ ask for things me and the other devs to do after they have finished their other projects.
-Firefox OS
-LG UI
-CM7
Just pop requests underneath and ill update reguarly.
Click to expand...
Click to collapse
Sense 4.1 (If possible)
Shad0wPanda said:
Before any of you say anything negative this isnt to bug other devs this is a thread for people to request/ ask for things me and the other devs to do after they have finished their other projects.
-Firefox OS
-LG UI
-CM7
Just pop requests underneath and ill update reguarly.
Click to expand...
Click to collapse
Hahaha, heres an LG UI Rom, iv'e had it for a while, just lockscreen doesnt work at all! so slide down NC and hit settings to unlock, then install a custom locker such as holo locker! I'll post in the dev threads when i can be bothered, but test that out..
http://d-h.st/2V2
Click to expand...
Click to collapse
i think gettin bt and wifi implemented in cm 10.1 should be a good place to begin
lead3r1 said:
i think gettin bt and wifi implemented in cm 10.1 should be a good place to begin
Click to expand...
Click to collapse
+1
but we really need the devs to go back to work
CM7 FTW
CM7 first ... it would be super buttery smooth for us ...
How are you so certain it'd be "buttery smooth"? Cuz I'm not sure, if not totally negative on that matter.
How are you so certain it'd be "buttery smooth"? Cuz I'm not sure, if not totally negative on that matter.
Click to expand...
Click to collapse
Brnt you don't have to flash cm7... What's with all the gingerbread hate??
Sent from my HTC Desire C using xda app-developers app
I suggest we go back to XP then. It's going to run so much better on our new PCs!
It's not hate, you just get overexcited over nothing without even putting some though into it. Go on, prove me gingerbread will run smoother than JB/ICS, but without these facts your words are nothing.
brnt said:
I suggest we go back to XP then. It's going to run so much better on our new PCs!
It's not hate, you just get overexcited over nothing without even putting some though into it. Go on, prove me gingerbread will run smoother than JB/ICS, but without these facts your words are nothing.
Click to expand...
Click to collapse
I think you have your analogy wrong. Going from a newer version of Windows to an older version of Windows is pointless because...well...it's still Windows.
However, if you were to go from Ubuntu to, say, Slackware, you would definitely see a boost in performance because Slackware is far less taxing on the available resources. The same could be said about going from JB to GB. GB requires less resources and can therefore run smoother/faster on hardware designed for a higher version of Android. This is a well known fact throughout the Android community because nearly every JB or ICS based device has GB ROM development in some form or another.
It's still Android. Roughly 90% of the differences between JB/ICS and GB lie in the overall appearence, not the functionality.
IDEA
Or lets make CM10 even better
Like eliminate WiFi problems and hotspot problems etc :fingers-crossed:
What do you think?
S off would be good.
Not first priority though
sent from CM10'd Desire C
Phenziox said:
S off would be good.
Not first priority though
sent from CM10'd Desire C
Click to expand...
Click to collapse
It would be very useful though but it's more HTCs job
Sent from my HTC Desire C using xda premium
@soupmagnet, i agree entirely with that statement, however, where is the desire coming from for having GingerBread Roms? if it was desired so much, then why not buy a gingerbread phone in the first place? Would've been cheaper and there are still devices on the market, some with faster processors then the Desire C, if you wanted GingerBread, should've bought a GB Device, you don't go buy a brand new Windows 8 PC to deliberately downgrade it to a legacy OS like vista and limit the features you have access to. It lacks all logic in all honesty.. You don't go to sell a phone after use being all like, Yeah it has 2.3.5 GB on it, or brag to your mates, yeah my device is android 2.3.5, fact is 4.2.2 is the best android so far, Android has only improved over time, GB on our device is like an i7 with vista, you just don't do that kind of thing..
penguin449 said:
@soupmagnet, i agree entirely with that statement, however, where is the desire coming from for having GingerBread Roms? if it was desired so much, then why not buy a gingerbread phone in the first place? Would've been cheaper and there are still devices on the market, some with faster processors then the Desire C, if you wanted GingerBread, should've bought a GB Device, you don't go buy a brand new Windows 8 PC to deliberately downgrade it to a legacy OS like vista and limit the features you have access to. It lacks all logic in all honesty.. You don't go to sell a phone after use being all like, Yeah it has 2.3.5 GB on it, or brag to your mates, yeah my device is android 2.3.5, fact is 4.2.2 is the best android so far, Android has only improved over time, GB on our device is like an i7 with vista, you just don't do that kind of thing..
Click to expand...
Click to collapse
The problem with your logic is that Gingerbread based devices (with a few exceptions) only have hardware that is capable of meeting the low demands of Gingerbread.
For many people, the worth of their device is in its functionality, not its "bragging rights". I will never have Windows on my computer simply because of the features it provides. I use Linux, because of it's speed, stability and and overall functionality. ICS and JB do have some nice additional features, but at a noticeable cost of available resources and stability, and the overall functionality is still nearly the same. While higher versions of Android do provide some "improvements", they are mostly linked to the user interface (which many people don't necessarily like) and there are very few performance improvements. So for you to say that it "lacks all logic" is, well, illogical in itself.
While you may like what JB and ICS have to offer and prefer that for your daily driver, I don't think it's fair to ridicule others' personal preference in Android versions, considering the majority of changes between these versions are exclusive to the UI and not Android itself.
Off-topic... naughty naughty
Sent from my HTC Desire C using xda premium
Getting back on topic...
It would be nice to see more CDMA support though. I have a shell script, based on bin4ry's exploit, to root the CDMA variants, but it needs to be converted over to Windows' batch scripting language. If anyone wants to have a go at it, just let me know.
As far as ROMs are concerned, we can use the existing GSM ROMs, but a patch will need to be made. It wouldn't be that difficult to implement and would be much easier than creating all new CDMA ROMs.
The biggest problem would be getting a working recovery. I tried unpacking the existing (GSM) recovery and replaced the kernel with the phone's stock kernel but it didn't work out very well. I think a new recovery would need to be built from source, but I'm running into strange compile errors when compiling the stock kernel from source. I don't have experience building custom recovery so it's going to be challenging trying to figure everything out, but I think I can handle it.
Clearly, the need for CDMA support is low, but it's far from non-existent. I'm more than willing to take the reigns on this project, but I may have to take advantage of some of the experience around here, assuming there are those willing to lend a hand.
soupmagnet said:
The problem with your logic is that Gingerbread based devices (with a few exceptions) only have hardware that is capable of meeting the low demands of Gingerbread.
For many people, the worth of their device is in its functionality, not its "bragging rights". I will never have Windows on my computer simply because of the features it provides. I use Linux, because of it's speed, stability and and overall functionality. ICS and JB do have some nice additional features, but at a noticeable cost of available resources and stability, and the overall functionality is still nearly the same. While higher versions of Android do provide some "improvements", they are mostly linked to the user interface (which many people don't necessarily like) and there are very few performance improvements. So for you to say that it "lacks all logic" is, well, illogical in itself.
While you may like what JB and ICS have to offer and prefer that for your daily driver, I don't think it's fair to ridicule others' personal preference in Android versions, considering the majority of changes between these versions are exclusive to the UI and not Android itself.
Click to expand...
Click to collapse
I stand corrected, thankyou for clearing that up for me, i never thought to look at it in this way, however, when you do get a working recovering, i do so believe i added cdma support in SHTD, the rom was both configured for cdma and for gsm, as it is in the build.prop also!, however a cdma aosp kernel would be needed
cm10.1 wifi bluetooth fixed would be a cool rom... Devs plz fix it... We noobs will be greatfull to you......:laugh::laugh::good:
akashgartia said:
cm10.1 wifi bluetooth fixed would be a cool rom... Devs plz fix it... We noobs will be greatfull to you......:laugh::laugh::good:
Click to expand...
Click to collapse
Don't rush them. They have other stuff to do. If you want it done, you could learn and try it yourself.