[ROM]Kuroikaze CM10 Discontinued See other ROM threads here - Thrive Android Development

For those who are interested in CM10 for our Thrives, but can't / won't / don't want to build along with us, I will be posting occasional builds here for people to play with. These builds will include my modified kernel (available separate in this forum as well) and include occasionally different source from my Kuroikaze builds, namely a memory bar graph in recent apps. Not all builds may contain this feature, though I like it so I tend to build it in there.
Kernel source is available here:
pio-masaki Github
I attempt to mirror any and all changes by tybar, and implement a few device tree changes myself in attempts to fix issues. My tree is currently private however it will be made public upon mod request OR becomes functional, whichever comes first.
Known issues:
Storage OR paid apps don't work depending on which boot.img you use.
Working:
Boots and runs, and is quite fast
WiFi
Bluetooth (needs more testing)
Sound (mostly, haven't had many issues with it yet). I may implement TinyHal later
Touch Screen
UI acceleration
Video HW Decode
GPS (slow sometimes but does work)
HDMI

Downloads:
Kuroikaze-Thrive Build 4
Kuroikaze-Thrive Build 9
Kuroikaze-Thrive Build 14
Kuroikaze-Thrive Build 14.1
Change Log:
Build 3 = Initial uploaded release.
Build 4 = Cameras working. Gallery opens. Front and rear cameras open view, capture may or may not work at all or correctly. Included a new kernel with GPU OC that should only be used for CM10, NOT ICS.
Build 5 = Failure, kernel changes prevented it's use, another kernel was needed.
Build 6 = New kernel V0.4 implemented.
Build 7 = Sensors and Rotation are now working. GPS should now operate correctly. Minor update to the kernel for rotation lock switch.
Build 8 = Video HW Decode should now be functional. Rotate lock switch should now be functional. Autobrightness may now be functional.
Build 9 = Full UI HW Acceleration (Project Butter). Rotation lock switch should actually be fixed this time. Some kernel changes for Play Store apps issues (may or may not work). Huge thanks to jbettcher for his work on the UI Acceleration, without it we wouldn't be near having it.
Build 14 = Black Bean 6 based build, built from source. Paid apps don't work, storage seems to work correctly (settings>storage will usually crash though)
Build 14.1 = Black Bean 6 based build, built from source. Paid apps work, however storage seems broken for some users, namely it doesn't see an sd card as being mounted, even though it is.
For file specific information, please use this linkHERE. This will list all of the ROMs, and each has it's own changelog available.

this is my boomstick
Thanks:
Tybar for his work on this project!
Godmachine (xda) for helping me out with the kernel work.
ezTerry (xda) for his work on the T20 Kernels, of which this kernel uses bits from.
The rest of the guys throwing in work on this project!
Team Baked for their work that was used for Build 14
diesburg for flashing random fixes chasing the storage bug.
j.anderson for flashing random fixes chasing the storage bug.
bostonbassman78 for flashing random fixes chasing the storage bug.
To everyone who donated to me when my Thrive's audio blew up and got me a replacement!
I'll be adding more, don't worry. If you aren't listed it isn't personal.

Sounds good
Thanks man
Sent from my EVO using xda app-developers app

Any chance of seeing cm9? m running your kernel and it's super fast.. No problems so far

stevie13.xo said:
Any chance of seeing cm9? m running your kernel and it's super fast.. No problems so far?
Click to expand...
Click to collapse
CM9 is something I'm sure could be built, though I'm also sure it'll be just as broken as CM10 is the first time around. I'm diverting among a few projects now, and as I jump between them I keep losing focus, I diverted from the A100 to the Thrive CM10, then to my Galaxy Nexus, which honestly didn't take long to mod to my liking as the source was already modded, just had to change it to work with phone ui. Then I started the Thrive kernel, and I think I'd like to try to get ICS good. Meaning, if the kernel proves to be ok, I'll look at CM9 next. If CM9 gets cleared, then CM10 will be that much easier. I think. Not a whole lot changed from CM9 to CM10 for the iconias, I hope its the same for the Thrive.

Dude you should apply for recognized developer. You definitely deserve it for being the only dev to build custom roms for the thrive.
Sent from my Thunderbolt using Tapatalk 2

Seems my account is not old enough to get a title, not to worried about it, I'm the only dev on the a100 too lol
Tapatalked from my Nexus 7 - Kuroikaze AOSP

Awesome
Following the builds Great work so far!:good: So what is the changes for version 15 i saw in the list?

Its just an update to the boot.IMG for storage and some extra tweaks. 4.2 is taking up my time now but I'll build a fresh one for 16.
Sent from my Galaxy Nexus using Tapatalk 2

Awesome Happy to see development for this tablet...I'm currently running Dalepl's rooted ICS rom and a nice cobalt green theme, but I need some CM goodness Thanks for your work thus far!

D150shorty said:
Awesome Happy to see development for this tablet...I'm currently running Dalepl's rooted ICS rom and a nice cobalt green theme, but I need some CM goodness Thanks for your work thus far!
Click to expand...
Click to collapse
There isn't much dev here, its all on another forum for thrives. Won't mention publicly as per xda rules about such things. But there is a cm10 ROM labeled unified, if you Google it you'll see where I mean.
Sent from my Galaxy Nexus using Tapatalk 2

pio_masaki said:
There isn't much dev here, its all on another forum for thrives. Won't mention publicly as per xda rules about such things. But there is a cm10 ROM labeled unified, if you Google it you'll see where I mean.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Oooo yummy Thanks, and I will continue to watch the development on your ROM as well :good:

pio_masaki said:
Seems my account is not old enough to get a title, not to worried about it, I'm the only dev on the a100 too lol
Tapatalked from my Nexus 7 - Kuroikaze AOSP
Click to expand...
Click to collapse
Well you deserve it man. Thanks for building for us
Sent from my ADR6400L using Tapatalk 2

Related

CM7 vs EagleBlood

I have a big question that is been floating around in my mind.
We have CM7 which is based on ginngerbread and we got Eagle blood 1.03 which is gingerbread as well.
Why does it seems like eagle blood developers seems to develop way faster and have a more stable rom than CM7?
Is it because they had to port gingerbread to the G2x? If that its the case, wouldn't it be easier to grab the gingerbread leak and develop using that as the source?
eagle blood is from gingerbread leak and cyanogen isn't?
Also does it takes longer for CM7 to develop because they are adding more features to the ROM?
The reason I'm asking is because I had this questions and is nothing against CM7 directly at all, I just want to understand how they are doing it and see the benefits.
Thanks
Sent from my LG-P999 using XDA App
Eagle Blood is based on the existing gingerbread leak with added tweaks.
Cyanodenmod is build completely from the ground up using the AOSP source code. It has features not found in ROMs released by manufacturers.
It's like modding an engine vs building an engine.
regP said:
Eagle Blood is based on the existing gingerbread leak.
Cyanodenmod is build from the ground up using the AOSP source code.
It's like modding an engine vs building an engine.
Click to expand...
Click to collapse
That clears up some of my doubts.
So basically they are using a gingerbread AOSP from google?
And what are the advantages of doing it this way instead of just grabbing a leaked ROM and tweak it.
Sent from my LG-P999 using XDA App
Once they get the device-specific stuff ironed out, feature updates can be added easily across multiple devices.
For example, if you look at the CM7 changelog the unlabeled changes are to all GB devices and the entries labeled "p999" are changes specific to this device.
moshe22 said:
That clears up some of my doubts.
So basically they are using a gingerbread AOSP from google?
And what are the advantages of doing it this way instead of just grabbing a leaked ROM and tweak it.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Better performance. Manufactures ROMs often end up with bad coding which results in a device suffering from things such as bad battery life, lower performance, etc. Also with official ROMs you can't do much with it until they release the source code. And even then (at least with samsung) some things like driver source never get released which means the devs cant fully optimize the ROM. AOSP means full control over the ROM to make it do what you want it to do the way you want it to be done. It does take much longer to complete though which is why CM has nightly updates. Makes it easier to put out a nightly than to put out a whole new ROM for every bug they fix. I'm sure someone can explain this better than me.
r4d14n7 said:
For example, if you look at the CM7 changelog the unlabeled changes are to all GB devices and the entries labeled "p999" are changes specific to this device.
Click to expand...
Click to collapse
Oh good to know, thanks
regP said:
Better performance. Manufactures ROMs often end up with bad coding which results in a device suffering from things such as bad battery life, lower performance, etc. Also with official ROMs you can't do much with it until they release the source code. And even then (at least with samsung) some things like driver source never get released which means the devs cant fully optimize the ROM. AOSP means full control over the ROM to make it do what you want it to do the way you want it to be done. It does take much longer to complete though which is why CM has nightly updates. Makes it easier to put out a nightly than to put out a whole new ROM for every bug they fix. I'm sure someone can explain this better than me.
Click to expand...
Click to collapse
Wow, this really answers my question as to why it takes them longer. Thanks
So it means that cyanogen even develop their own drivers?
Sent from my LG-P999 using XDA App
You mentioned that you feel eaglesblood is more stable than CM7. Is this from personal experience or from reading the forums? In my experience, CM7 as of around nightly #11 has every significant bug worked out.
MWBehr said:
You mentioned that you feel eaglesblood is more stable than CM7. Is this from personal experience or from reading the forums? In my experience, CM7 as of around nightly #11 has every significant bug worked out.
Click to expand...
Click to collapse
I must disagree. I LOVE CM 7 and ran build 11 and 13 and found it rather buggy right now. Sometimes the touch screen didn't recognize touches on the right side(I consider this a significant bug). When you call a number and have to punch in numbers (like a VM password or when dialing an extension) did not work for me(which I consider another significant bug). I also heard there are issues with it sticking APN settings(cant comment because I didnt really check that when I had cm 7 installed) I just dont think cm 7 is stable enough at the moment. Eagle Blood is running pretty well right now. I would say a lot better than cm 7 but that will change once CM gets the bugs worked out
MWBehr said:
You mentioned that you feel eaglesblood is more stable than CM7. Is this from personal experience or from reading the forums? In my experience, CM7 as of around nightly #11 has every significant bug worked out.
Click to expand...
Click to collapse
Yes, personal experience. Been running eb 1.02 and is been great.
I Just flashed CM7 #15 just to test it out and is buggy for me
-When i receive a call i don't get any sound from the ringer even though is not muted
-Sensors are like in auto brightness even though they are not
-The performance of the whole system isn't the best.
I am sure it will be the best ROM out there but as for now still only and nightly and is buggy
Sent from my LG-P999 using XDA App
One significant difference for me, which is due to the fact that Cyanogen has built their own rom with their different bluetooth stacks (as opposed to LG's custom ones), is that bluetooth controllers actually work with CM7. Useful for using a wiimote on emulators through HDMI
Just something to consider, no bluetooth controllers on EB.
Sent from my LG-P999 using XDA App
regP said:
Eagle Blood is based on the existing gingerbread leak with added tweaks.
Cyanodenmod is build completely from the ground up using the AOSP source code. It has features not found in ROMs released by manufacturers.
It's like modding an engine vs building an engine.
Click to expand...
Click to collapse
Right, and not only that, cyanogen has many different phones he and his dev team have to work on.
Sent from my LG-P999 using Tapatalk
Build #16 is out today and supposedly the TouchTones in the dialer and the backlight is fixed (thank god!)
But yes. Cyanogen builds their own kernel and drivers, which is why it usually is more compatible with stuff like WiiMotes and stuff. But once they get the Kernel working properly (which they are doing now) it is just a matter of updating the core OS then it can be pushed to all devices pretty seamlessly (I guess).
There are lots of benefits of using CM over standard stock Gingerbread. For one, Stock is 2.3.3 where CM7 is 2.3.4 so it supports lots of Googles new apps like Video in Google Talk and the new Cloud Music player.
Also there are tons of tweaks like Notification menu toggles, System Themes, Sound Profiles, Black-List calling, Several Lockscreen types and Widgets with Gesture support, etc the list goes on and on.
Between the Notification Toggles and Themes which you can install from the market, I'm hooked.
Plus it is the only Gingerbread rom that doesn't cause my phone to lockup/reset/Black Screen of Death/whateveryoucallit
MWBehr said:
You mentioned that you feel eaglesblood is more stable than CM7. Is this from personal experience or from reading the forums? In my experience, CM7 as of around nightly #11 has every significant bug worked out.
Click to expand...
Click to collapse
It has tons of bugs like inaccurate battery readings
Sent from my LG-P999 using Tapatalk
my concern is that is the g2x able to do 1080p video recording and high resolution picture like the stock rom? THis is the only reson why I'm still sticking with the stock rom.
MWBehr said:
CM7 as of around nightly #11 has every significant bug worked out.
Click to expand...
Click to collapse
u must be high
jdaclutch said:
my concern is that is the g2x able to do 1080p video recording and high resolution picture like the stock rom? THis is the only reson why I'm still sticking with the stock rom.
Click to expand...
Click to collapse
+1. I take a lot of photos and videos of my kids and would rather stick with 2.2 than have a gimped camera.
r4d14n7 said:
+1. I take a lot of photos and videos of my kids and would rather stick with 2.2 than have a gimped camera.
Click to expand...
Click to collapse
Yeah, i take alot of pictures and videos too
Sent from my LG-P999 using XDA App

[Q] Different ICS Roms = Confusion | [Poll] Which one are you using? Why?

With the risk of getting banned, flamed or closed down.
It would be cool if someone could clear this up and I think I am not the only one confused here. I might add a FAQ later with all the answers.
So far there seem to be 3 ICS Roms*:
CyanogenMod9 G2X (SelfKANG)
*****EaglesBlood™***** ICS 4.0.3
HellFire Sandwich
*I ignore the (modified) MIUI ICS Roms because they don't seem to have data working according to their threads.
Now what are the real differences?
SelfKANG seems to be the most 'original' a.k.a first one. According to his post "Most visible Known issues [are]:
- No media acceleration: No video decoding, no video encoding
- Apps made for Android 4 with their own specific graphics implementations (Chrome is a good example) will be glitchy."
Then there's HellFire Sandwich which seems to build of one SelfKang version (not really clear), but according to changelog it got media acceleration. Does this mean video decoding & video encoding are working?
Last, but not least, there's ***EaglesBlood™***. According to post it's "BASED OFF CM9 UNRELEASED SOURCE.THIS IS NOT A KANG OF "Arcee's ROM (SelfKANG)" What's the difference? I thought Arcree's is CM9. At least in my understanding, it was...
Do all 3 Roms have the same problems (it doesn't seem to be the case though)? Which ones are the known problems exactly?
Then there's this list I found where more seems to be working. Or at least the problems that are reported sometimes shouldn't happen according to this list.
I went through many pages of the developers threads and no clear answer is to be found. I'm just really confused right now.
Thanks in advance.
Which Rom are you using? Why?
so, ricardo's (arcee's) cm9 build is unsupported by cm team.
Hellfire does not have hardware acceleration/video decoding/video encoding, it is a slightly modded cm9skX; so naturally they have the same issues.
doniqcc is doing his own thing based on the cm teams github sources.
i havent tried eagles blood yet, but i would recommend cm9sk3.
dont forget faux123's kernel. and v6 supercharger if you have the skill.
squallz506 said:
i would recommend cm9sk3.
dont forget faux123's kernel. and v6 supercharger if you have the skill.
Click to expand...
Click to collapse
ty for clearing some things up.
I'll give it a try. I should have the skill.
Any other recommendations for tweaks, scripts, apps?
chrisus246g said:
Last, but not least, **EB ICS**. According to post it's "BASED OFF CM9 UNRELEASED SOURCE.THIS IS NOT A KANG OF "Arcee's ROM (SelfKANG)" What's the difference? I thought Arcree's is CM9. At least in my understanding, it was...
Click to expand...
Click to collapse
EB is based on the straight source code pulled from the Github. From what I understand, this would be like compiling your own "nightly" build from the most up-to-date changes.
everything has a tweaked hardware acceleration..HFS has media acceleration so you can play games from tegra zone. However, this does not have the video encoding to play movies. youtube works though. I haven't used EB so can't comment on that one.
jblah said:
everything has a tweaked hardware acceleration..HFS has media acceleration so you can play games from tegra zone. (...) youtube works though.
Click to expand...
Click to collapse
thy for the answer.
do these work only work on HFS? or also on SelfKANG3?
SK3 can do youtube and just about any game I've tried to play. The only problem I've experienced because of lack of HW acceleration is trouble with Chrome for Android. Arcee said that apps like that which were written for ICS may have problems. Other than that, smooth sailing with SK3
Running sk3 and its damn good..haven't tried eb or Hellfire but reading thru the threads they both seem pretty solid
I think HFS is the most smooth of the 3
To clarify, Hellfire is based on self kang 1, next update should include things from 2 an 3 but there hasn't been an update since before SK2 was released.
Sent from my LG-P999 using xda premium
Just waiting for HFS to get a little farther then it will be the only one I run.
Sent from my LG-P999
CM9.0.0-RC0 SelfKANG3-G2X
Faux CM 49b4 SV ICS
Apex Launcher Beta v0.2
I have used all of them and I feel as though EB ICS feels the least "experimental" and the most like a daily driver IMHO. I use it just like previous EB roms for the most part and it has been a very consistent experience for me
Sent from my LG-P999 using XDA App
I've only tried HFS and while I like it a lot I am going back to 1.9 since it is more stable. I work in the basement of a hospital and don't get a steady signal to my phone unless I use my work's Wifi and enable Phone Wifi. HFS crashes every 15 to 20 seconds whenever I enable to Phone Wifi so I can't use it reliably at work. That said when it becomes stable, I can't wait to enjoy some HFS goodness.
I've been running HFS and I've had only the known issues (wifi calling, ICS apps fc, etc...) I have been running John's roms sine he was kanging EB roms. He responds quick to issues and only releases complete roms ( as complete as possible)
Sent from my LG-P999 using xda premium
squallz506 said:
so, ricardo's (arcee's) cm9 build is unsupported by cm team.
Hellfire does not have hardware acceleration/video decoding/video encoding, it is a slightly modded cm9skX; so naturally they have the same issues.
doniqcc is doing his own thing based on the cm teams github sources.
i havent tried eagles blood yet, but i would recommend cm9sk3.
dont forget faux123's kernel. and v6 supercharger if you have the skill.
Click to expand...
Click to collapse
There is HW acceleration, just not media acceleration. No dev would've released any sort of ICS rom without at least partially working HW acceleration. Faux's kernel is not needed, as all it does is OC/UV, and I would wait for morfic's kernel since there actually is a performance gain.
I'll add my vote for HFS. Started running it yesterday and it has been pretty smooth with almost no issues (except the known ones).
I am really digging ICS!
thanks for all the answers. Added a poll
I've been trying SK3 with faux 049b4 which comes with a minor bug.
If you flash Faux on SK3, it completely removes the "Mobile Data Limit" option which was added in Sk3.
Click to expand...
Click to collapse
So far it seems good/stable. what I've *really* noticed so far:
Fb contact sync won't work. (thanks to ICS, google & fb)
sadly no gestures for launcer nor ability to hide apps in drawer.
Try using apex launcher for hiding apps and gestures. I think it is best of the ics based launchers.
http://forum.xda-developers.com/showthread.php?t=1452663
HFS 1.1 is indeed based on SK1, but for the most part is similar to SK2 after Hell's tweaks. His next build is supposed to be from source (SK3) and we'll probably have some of his personal customizations.
SK3 added in selection options your storage and something else that escapes my memory at the moment that wasn't terribly significant to me.
EB build 1 basically is SK2 built from source. His next build is supposed to be SK3 with more of his customizations from his other EB roms.
Sent from my LG-P999 using XDA App
I'm running cm9 sk3 and its awesome. Flashed hfs but preferred cm9. I keep hearing that hfs has MA working but it didn't work for me. Can someone confirm these statements
Sent from my LG-P999 using xda premium

Any issues or questions regarding CyanogenMod 10 - Please ask here

If anyone has questions or concerns regarding the CyanogenMod 10 please ask here and stay away from the development section for these posts, as it has over 3000 posts.
To start off please read the CM10 faq on the first Page of the CM10 thread before asking any questions here or in the official thread. Thanks
Sent from my HTC One X(L/AT&T)
So, does (or will) the camera app in CM10 have the same burst mode that the Sense camera has? Can you take AS MANY photos AS QUICKLY? Will those photos be similar quality? Will we be able to pull stills from previously recorded video? Or take Hi Res stills while shooting HD video?
I read the last 15 pages of the development thread and didn't see any of this being discussed.
Thanks a bunch!
Billy
Sent from my Nexus 7 using Tapatalk 2
Burst mode is a sense cam feature only, because there is no sense in cm those features will not be there. Your best bet is if you want sense cam but asop feel go with clean rom or tn rom, they can desense the launcher but keep the apps but you will be on ics. But i will say the cm cam is alot faster then it used to be and is still a good camera.
**PLEASE READ IN REGARDS TO CAMERA ISSUES WITH CM10**
The rapid fire camera mode is named Zero Shutter Lag or ZSL and there are plans to implement this in the near future. You will also soon be able to take still pictures while recording video. H8 & the CM10 team are working on getting every feature of the camera to 100% and they say they are nearly there.
However, as of right now the camera, video camera, & panorama mode is still relatively broken. The camera's bare bones features are working but only in the build's that are labeled as EXPERIMENTAL. The regular CM10 nightlies do not contain the WORKAROUND that H8 has come up with because this workaround has not been merged with the offical CM10 nightlies that the One XL is now getting.
Word on the street is the camera will be 100% working very, very soon so please be patient.
If you use and rely on the camera on a daily basis...please only flash the EXPERIMENTAL builds until further notice!!!
PaKMaN787 said:
To start off if you want the video camera and/or audio fixes, please download the experimental build instead of the new nightlies. They will soon be merged.
Sent from my HTC One X(L/AT&T)
Click to expand...
Click to collapse
by audio fixes do you mean caller volume? Im on the 8/22 build. I heard the 8/19 has good caller voice but it kills my battery.
Any idea how we can get native emoji working? It gives the option to download the add on in keyboards settings. Installs. Then refreshes and shows ready to download again. Also, any plans for Google wallet? This ROM is amazing and ridiculously fast!! Thanks for your hard work and help!!
Sent from my One X using xda app-developers app
yungskeeme said:
by audio fixes do you mean caller volume? Im on the 8/22 build. I heard the 8/19 has good caller voice but it kills my battery.
Click to expand...
Click to collapse
Sorry I meant music by audio. Honestly they aren't even fixes for music it just doesn't seem to work sometimes for nightlies... and in call is always a hit or miss
Sent from my HTC One X(L/AT&T)
PaKMaN787 said:
To start off if you want the video camera and/or. music workarounds, please download the experimental build instead of the new nightlies. They will soon be merged.
Sent from my HTC One X(L/AT&T)
Click to expand...
Click to collapse
PaKMaN787 said:
Sorry I meant music by audio. Honestly they aren't even fixes for music it just doesn't seem to work sometimes for nightlies... and in call is always a hit or miss
Sent from my HTC One X(L/AT&T)
Click to expand...
Click to collapse
Definetly hit or miss. Heard it was fixed in the 8/28 but no music so I guess I'll stay on 8/22 and deal with it. Heard someone say they flashed AOKP ICS rom and reflashed CM10 and it was fixed.
bstephens2u said:
Any idea how we can get native emoji working? It gives the option to download the add on in keyboards settings. Installs. Then refreshes and shows ready to download again. Also, any plans for Google wallet? This ROM is amazing and ridiculously fast!! Thanks for your hard work and help!!
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I'll do a little poking around and see if I can get this working (I probably won't) and I'll let you know if I do!
tropazr said:
**PLEASE READ IN REGARDS TO CAMERA ISSUES WITH CM10**
The rapid fire camera mode is named Zero Shutter Lag or ZSL and there are plans to implement this in the near future. You will also soon be able to take still pictures while recording video. H8 & the CM10 team are working on getting every feature of the camera to 100% and they say they are nearly there.
However, as of right now the camera, video camera, & panorama mode is still relatively broken. The camera's bare bones features are working but only in the build's that are labeled as EXPERIMENTAL. The regular CM10 nightlies do not contain the WORKAROUND that H8 has come up with because this workaround has not been merged with the offical CM10 nightlies that the One XL is now getting.
Word on the street is the camera will be 100% working very, very soon so please be patient.
If you use and rely on the camera on a daily basis...please only flash the EXPERIMENTAL builds until further notice!!!
Click to expand...
Click to collapse
This is such great news! I'd like to publicly commit to donating $30 to the team that makes this happen!
Anxiously waiting,
Billy
Sent from my Nexus 7 using Tapatalk 2
I have a couple of general questions.
1. Will the official release of HTC JB drastically and rapidly improve the project? Will lots of things need to be redone/reoptimized? Or it's simply some missing links being filled? What kind of time frame can we expect for a fully working CM10 (equal or close to the quality of CM on the other officially supported devices) following the HTC JB release?
2. Exactly how was the team able to develop this rom so far without official support? And how much farther can this realistically go if we do not get the official JB in the near future (hopefully this doesn't happen). From what I read, I'm under the impression that this rom is already in a much better shape compared to the development phase CM builds on many other non-officially supported devices (for example ICS/JB builds on older devices that received EOL after GB). Is the kernel of the phone somewhat "easier" to crack compared to those devices or is that we have some super talented developers behind this project? And the developer seems confident that even without official HTC JB, this rom can pretty much become a *fully working* one?
Thanks for the awsome work!
Is wake locks an issue with cm10 so far or just a few users isolated type instance? I was getting massive wake lock for alarmmanager that I do not get on CleanRom.
anyone else getting bad battery life with this ROM? currently running the 8/29 nightly.
Right now im at 33% battery with 11h on the battery but only 1h45min screen time. I also have GPS on and brightness around 1/2..which could possibly be the problem.
JeepFreak said:
This is such great news! I'd like to publicly commit to donating $30 to the team that makes this happen!
Anxiously waiting,
Billy
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Well, its done and it should be in the next nightly (20120901)...assuming nightlies are fixed (today's nightly 404's).
toptalent said:
I have a couple of general questions.
1. Will the official release of HTC JB drastically and rapidly improve the project? Will lots of things need to be redone/reoptimized? Or it's simply some missing links being filled? What kind of time frame can we expect for a fully working CM10 (equal or close to the quality of CM on the other officially supported devices) following the HTC JB release?
2. Exactly how was the team able to develop this rom so far without official support? And how much farther can this realistically go if we do not get the official JB in the near future (hopefully this doesn't happen). From what I read, I'm under the impression that this rom is already in a much better shape compared to the development phase CM builds on many other non-officially supported devices (for example ICS/JB builds on older devices that received EOL after GB). Is the kernel of the phone somewhat "easier" to crack compared to those devices or is that we have some super talented developers behind this project? And the developer seems confident that even without official HTC JB, this rom can pretty much become a *fully working* one?
Thanks for the awsome work!
Click to expand...
Click to collapse
1. Nope, didn't help us at all. Didnt need it. As far as I'm concerned, after tonight's nightly (technically...tomorrow morning's nightly) everything is pretty much 100%. a few bugs here or there...but I think the Nexus devices are the only ones ahead of us regarding "working" status.
2. We're magical. *snicker* just kidding. We've pretty much completely beat HTC to Jellybean with CM10. The great part of the kernel work intervigil has provided is that we use the same kernel for ICS and JB. Meaning we can backport all JB stuff to ICS with minimal differences. We are very confident that this will be a fully working one. The last piece we needed was the Camera HAL which we *just* received.
Thank you for the thanks! Enjoy!
h8rift said:
Well, its done and it should be in the next nightly (20120901)...assuming nightlies are fixed (today's nightly 404's).
Click to expand...
Click to collapse
Wooooooooooot!! And would it just be TeamDouche in general that deserves the donation? Or was somebody specific working on this?
Thanks H8!
Billy
Sent from my Nexus 7 using Tapatalk 2
1. Nope, didn't help us at all. Didnt need it. As far as I'm concerned, after tonight's nightly (technically...tomorrow morning's nightly) everything is pretty much 100%. a few bugs here or there...but I think the Nexus devices are the only ones ahead of us regarding "working" status.
2. We're magical. *snicker* just kidding. We've pretty much completely beat HTC to Jellybean with CM10. The great part of the kernel work intervigil has provided is that we use the same kernel for ICS and JB. Meaning we can backport all JB stuff to ICS with minimal differences. We are very confident that this will be a fully working one. The last piece we needed was the Camera HAL which we *just* received.
Thank you for the thanks! Enjoy!
Click to expand...
Click to collapse
That sir, is very impressive. "Beating HTC to jellybean" sounds so satisfying in an ambitious way, and completely changes the way these games used to be played. Hats off to all the "magicians" who made this happen!
One more question: what about LTE? I'm currently on the 4.0.4 based CleanRom 4.5, which is my first custom rom flashed on the phone (only bought it a week ago). Do I have to flash back to a 4.0.3 based ROM (which I have trouble finding) before flashing to CM 10? If the answer is still yes, is a solution being worked out to troubleshoot and solve the problem?
toptalent said:
That sir, is very impressive. "Beating HTC to jellybean" sounds so satisfying in an ambitious way, and completely changes the way these games used to be played. Hats off to all the "magicians" who made this happen!
One more question: what about LTE? I'm currently on the 4.0.4 based CleanRom 4.5, which is my first custom rom flashed on the phone (only bought it a week ago). Do I have to flash back to a 4.0.3 based ROM (which I have trouble finding) before flashing to CM 10? If the answer is still yes, is a solution being worked out to troubleshoot and solve the problem?
Click to expand...
Click to collapse
I'm not entirely sure if something is being worked on but I think you should flash CR4.0 as it is definitely working and is 4.0.3 base which is what h8rift said to flash.
Sent from my HTC One X(L/AT&T)
May I ask what is the right procedure to flash CM10? In the zip there is a boot.img. Do we need to manually extract and flash it with fastboot?
I ask this because some people (including me) can't make LTE to work in CM9/10. Some say by flashing CleanROM 4.0, full reset then flash CM10, LTE will be the default. This trick does not work for me. What is the mechanism of this trick? What stays after full reset? All I can think is the boot image. But even manually flashing CleanROM's boot.img then flash CM10 does not work for me. Changing build.prop (ro.ril.def.preferred.network and ro.telephony.default_network as suggested at code.google.com/p/cyanogenmod/issues/detail?id=1623 , sorry can't link external) of course does not work either.
I know #*#*info*#*# can change the preferred network type, but it does not stick after reboot, which renders this approach useless.
Thanks.

[ROM][Official]MyTouch4G Slide CyanogenMod 10 20130101 (Alpha 3) - 4.1.2

CyanogenMod 10 is a free, community built distribution of Android 4.1.2 (Jelly Bean) which greatly extends the capabilities of your phone.
This is an alpha release, but you should find it stable for everyday use.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
This is an alpha, with most critical functionality working.
TeamDS is working on porting Jellybean to the HTC Doubleshot (CM10 in specific). We have a reasonably well working Alpha we would like to share with the community for testing. Feedback is appreciated. If a timely response is not found here, we can be located on Freenode in #teamds.
INSTRUCTIONS:
1. Unlock/root your device and install Clockwork Recovery via ROM Manager.
2. Do a Nandroid backup!
3. WIPE Data/Cache** (You can try to NOT WIPE, it works for me, but recommended wipe).
4. Install the ROM
5. Optionally install the Google Apps
HOW TO REPORT BUGS OR PROBLEMS?
- Was your problem a hard reboot? Get us the file "/proc/last_kmsg".
- Was your problem a soft reboot or a "boot loop"? Run "adb logcat" and get the full output.
- Pastebin links preferred.
- Join #TeamDS on Freenode to talk to us directly.
Direct download URL: http://www.jeago.com/doubleshot/cm-10-20130101-UNOFFICIAL-doubleshot.zip
20130101 build MD5: b661a782c6f2fed26f9c21f2af39f1de
(hosted by Jeagoss of CyanogenMod, thanks!)
You can find the latest CyanogenMod GAPPS CyanogenMod Wiki. Bottom of page, "CyanogenMod 10" GAPPS.
Thank you to EVERYONE involved in helping with testing, coding, debugging and documenting! Enjoy!
Alpha name explanation.
"Alpha 3" has all the features of Alpha 2 (kernel/device), but the camera works. Also, the vendor blobs have been reduced and some replaced for optimal performance.
"Alpha 2" was the rebased 'common' kernel, rebased device trees. It provided a 3.0.53 kernel. The camera locking was broken.
"Alpha 1" was with a "KANG" kernel that ultimately was not very clean and had a lot of issues to resolve. It was also older (3.0.36 compared to 3.0.53).
----- CHANGES -----
Build 20130101 -- Alpha 3
Changes:
- Kernel rebase found in Alpha 2
- Fixes to the camera preventing the locking issue. Camera should be solid again!
- Contains functional Alt/Shift key LEDS, working www./.com button
- Restructured 'blobs' files, such as mpdecision and htcbatt.
(I have found improved battery statistics and usability with the blob changes.)
Happy New Year!
Bugs
* Chrome and Panorama Camera PREVIEW continues to be a little glitchy graphically, I have been told this is a common MSM8660 issue. They both still work, but it's annoying visually.
* Please report your results, and if you can capture /proc/last_kmsg when it happens, it would be hugely appreciated!
Historical
Build 20121222 -- Alpha 2
Changes:
This build has a somewhat new kernel base, as it's from a more up to date AOSP source which tbalden used when he ported our v2.6 kernel to v3.0 earlier in the year. It is a work in progress, but complete enough to warrant a release and more testing.
Build 20121121 -- Second public alpha (V 1.01)
- Upstream CM10 changes. No other large changes of note from previous 20121103 build pertaining to Doubleshot.
Build 20121121 (Alpha 1):
- Jellybeans!!1
- Updated kernel base to v3.0.48.
- Updated keylayout. NEEDS MORE WORK.
Please note flashing someone else's kernel may ruin your experience with this rom and I advise against it. This rom was a joint effort between kornyone & tbalden. A LOT of core works for msm8660 was put in by many CM Team members, and much of our work is based on their: toastcfh, Kali-, Kmobs, Bumblebee, cretin45, and all of the rest of CM!
A personal shoutout (THANKS!) is due to these individuals for their dedication to the HTC Doubleshot:
Stefan Seidel, Pál Zoltán Illés, and thanks to scverhagen of Github for keeping the kernel maintained!
THANKS to intervillium/intervigil for keeping the common HTC MSM8660 AOSP kernel up to date so many of our HTC MSM8660 phones are based on now in the Open Source community!
You can get all of the Doubleshot source from the following URLs:
TeamDS Github
CyanogenMod source is available from CyanogenMod Github
If you'd like to to contribute to CyanogenMod, checkout our Gerrit instance.
20130101 -- Alpha 3 -- http://www.jeago.com/doubleshot/cm-10-20130101-UNOFFICIAL-doubleshot.zip
20121222 -- Alpha 2 -- http://www.jeago.com/doubleshot/cm-10-20121222-UNOFFICIAL-doubleshot.zip
20121121 -- Alpha 1.01 -- http://www.jeago.com/doubleshot/cm-10-20121121-UNOFFICIAL-doubleshot.zip
20121103 -- Alpha 1.0 -- http://www.jeago.com/doubleshot/cm-10-20121103-UNOFFICIAL-doubleshot.zip
I made a mistake in the URL, the correct one is now posted.
Enjoy!
On it. Thanks again for all of your work! if it weren't for the few devs working on this phone, mine would have an inferiority complex.
Jeff
The webpage cannot be found
HTTP 404
Most likely causes:
•There might be a typing error in the address.
•If you clicked on a link, it may be out of date.
What you can try:
Retype the address.
Go back to the previous page.
Go to and look for the information you want.
More information
So the first post was a bad URL. I have confirmed it works now. Also, I added a mirror server for failback. Let me know if there any more issues, sorry for that.
kornyone said:
I made a mistake in the URL, the correct one is now posted.
Enjoy!
Click to expand...
Click to collapse
Thanks for this amazing upgrade Kornyone and the updated link.:good:
So THAT'S where you've been hiding...
Downloading now.
I never left. I won't be abandoning the Doubleshot anytime soon, even though I have a new daily (Samsung Galaxy Relay 4g) -- because my wife bought a brand new Doubleshot from T-Mobile just before they canceled them about 4 months ago.
I made no noticeable updates in months (about two) due to training for my new gig, which required 6 weeks on site in San Antonio (I live in Austin). Life has been a roller coaster. I also have hacked a few other devices, and I have too many projects now.
I drew a sadface in how the CM ROM thread splintered and fragmented on XDA. I guess I never made a post about CM9 Stable 9.1.0, which was released to http://get.cm (look for Doubleshot). That was 8/29. Also, just this week, I got Doubleshot in the lunch menu for Jenkins auto builds for CM9, so weekly CM9 builds for the Doubleshot are officially official.
Still, I am (almost always) in #teamds on Freenode. Also #cyanogenmod, #cyanogenmod-dev, etc.
Thanks for the support all. I have been hacking the Doubleshot since September last year. I ported CM7 to it, then CM9, and now CM10. tbalden was a monster and really helped us a lot with our v3 kernel most roms are using now.
kornyone said:
I never left. I won't be abandoning the Doubleshot anytime soon, even though I have a new daily (Samsung Galaxy Relay 4g) -- because my wife bought a brand new Doubleshot from T-Mobile just before they canceled them about 4 months ago.
I made no noticeable updates in months (about two) due to training for my new gig, which required 6 weeks on site in San Antonio (I live in Austin). Life has been a roller coaster. I also have hacked a few other devices, and I have too many projects now.
I drew a sadface in how the CM ROM thread splintered and fragmented on XDA. I guess I never made a post about CM9 Stable 9.1.0, which was released to http://get.cm (look for Doubleshot). That was 8/29. Also, just this week, I got Doubleshot in the lunch menu for Jenkins auto builds for CM9, so weekly CM9 builds for the Doubleshot are officially official.
Still, I am (almost always) in #teamds on Freenode. Also #cyanogenmod, #cyanogenmod-dev, etc.
Thanks for the support all. I have been hacking the Doubleshot since September last year. I ported CM7 to it, then CM9, and now CM10. tbalden was a monster and really helped us a lot with our v3 kernel most roms are using now.
Click to expand...
Click to collapse
I was wondering who released that on ROM Manager...
the only thing i could not get to work on the camera was the camcorder facial effects. i got a few fc closes and panarama looks sketchy but works fine
kornyone said:
Also, just this week, I got Doubleshot in the lunch menu for Jenkins auto builds for CM9, so weekly CM9 builds for the Doubleshot are officially official.
Click to expand...
Click to collapse
This is great news. I'll submit fixes for CM9 via gerrit review and encourage everyone to download the nightly builds instead.
I will continue to maintain a kernel for the doubleshot.
Thanks for the hard work!
some bugs
So I just flashed this (full wipe, data, cache, dalvik), and I can confirm some weird stuff with the panorama shot. There's a lot of flickering in panorama mode and while capturing a panoramic shot, but the picture turns out fine (normal pictures seem to look even better than in CM9.1 though.) The main reason I can't keep this ROM right now though is because the ALT key doesn't work in browser fields. It works in the address bar and in apps on the phone (searching contacts, text message fields, etc.), but not on text fields in the browser such as on Google, Youtube, or typing in passwords, so I can't access the secondary functions of the keys. Other than that, it seems very stable. Did not experience a reboot/boot loop, or force close. Wifi and BT tethering seems to be working fine for the brief period I tested it. But I think I'm gonna stick CM9.1 for now.
edit: also, no face unlock? not an issue for me, but I think some people like to have/prefer it.
edit again: the ALT key does work but you have to hold it while typing out your secondary characters. so no two press to lock it in "ALT mode"
The only problem with the hardware keyboard I found on this ROM is the www/com button not working, but I'm used to this one from the CM9 alpha builds. I haven't tested out the camera yet, even though this is the camera I use.
I was thinking of switching to an iphone, but this rom is giving new life to my phone. Thanks!
Sent from my HTC MyTouch 4G Slide using Tapatalk 2
dsp manager seems to be fixed here! thanks for all the hard work kornyone and the rest of teamds!
this is so smooth! and as some people said above, caps/alt is working fine, www/com button acts like a space bar.
can we use ics (especially scverhagen's) kernels with this?
and i know this is probably jumping the gun a bit, but since bruce2728 over on the sensation xda page just fixed 1080p (and many other small bugs the sensation experienced, and therefore we probably will do), is it potentially possible to fix it on ours down the line? not asking for it be actually fixed right now, just seeing if its possible...
thanks again for all the great work!
kornyone said:
I never left. I won't be abandoning the Doubleshot anytime soon, even though I have a new daily (Samsung Galaxy Relay 4g) -- because my wife bought a brand new Doubleshot from T-Mobile just before they canceled them about 4 months ago.
Click to expand...
Click to collapse
I'm doing everything I can to get you guys a forum going for the Relay.I've contacted mods, spammed the new device request thread, and rallied everyone to do the same. If you know any mods or higher ups that can get you guys up and running, I suggest you do so. They have active development going on and they BADLY need a forum
Glad to see the fresh work :good:
blackknightavalon said:
The only problem with the hardware keyboard I found on this ROM is the www/com button not working, but I'm used to this one from the CM9 alpha builds. I haven't tested out the camera yet, even though this is the camera I use.
Click to expand...
Click to collapse
I think they have a JBcamera+ app with more features (additional filters to be exact). ICS+ is what I use as well... best stock-ish one around
wiswis said:
I was thinking of switching to an iphone, but this rom is giving new life to my phone. Thanks!
Sent from my HTC MyTouch 4G Slide using Tapatalk 2
Click to expand...
Click to collapse
Good to hear! Don't make us b*tch slap you back into reality lol! That's a bad word around here... You have way better options like the Samsung Galaxy Relay, Note II, and new Nexuseseses coming!
gtmaster303 said:
I'm doing everything I can to get you guys a forum going for the Relay.I've contacted mods, spammed the new device request thread, and rallied everyone to do the same. If you know any mods or higher ups that can get you guys up and running, I suggest you do so. They have active development going on and they BADLY need a forum
Glad to see the fresh work :good:
Click to expand...
Click to collapse
Nice! They need some support! Alot of 'em are our fellow subforum members (G2/MT4GS) and deserve their own forum. I would have gotten one myself if I wasn't so spoiled by our awesome camera and prettier housing. The Note 2 will probably be my next one when I can get some spare cash. Although, I have to admit.... I am still digging our DS and enjoying having CM9 so stable thanks to kornyone, scverhagen, and others. Makes sense to move on to CM10 once resources were available and am dying to see if project butter makes a true impact as far as performance goes on our device. Will have to check this puppy out shortly!
Awesome! Finally get to try Jelly Bean! Gonna flash in the morning
Wow that's some great news! Thanks. Definitely flashing tonight.
This is perfect timing since I was just about to wipe my rom and reinstall it. I've been sitting on the side lines reading about all the love that JB users received. I may finally get to experience the same, after all.

[ROM] [EVITA] [AOSP] [4.3] [cfX-Toolchain 4.8.y+] codefireXperiment OFFICIAL NIGHTLY

Introducing codefireXperiment for your device! This OP is going to stay slim and bloat free, just like codefireXperiment. No marketing buzzwords either. We take such confidence in the speed and performance of this distribution, we challenge you to find a faster and more stable one!
Warning: we only support anykernel methods of custom kernel installation.
Here's a bit of info you may want on this project for how we do things differently:
CLICK HERE to find out more about the new team working on this project since our TeamEOS merger.
No features you don't need which slow the device down, or put your data at risk of being stolen. If you want to give it away, it should be your decision.
A fast and clean install with no UX decisions made for you. You make the ROM whatever you would like.
A team constantly exploring totally new feature sets and optimizations geared toward you, the user
We utilize a plethora of optimizations in a build system unlike any other:
Each build has a toolchain built for your device at the time of build. No more generic toolchain android builds.
Consistently updated upstream toolchain module source with our custom backports, fixes, and optimizations applied in a patch at build time.
Fully built utilizing Link Time Optimization (another custom ROM first). Feel free to google this one a bit to get an idea of the performance gain.
Many repositories have code fixes, cleanups, and many minor optimizations which are too generous to even speak of here.
Optimizations are toggled on and off based on device for the best experience we can acheive for your device without sacrificing any stability
Many Qcom optimizations and AOSP master (upstream) optimizations and fixes using device specifications to determine usage.
Fully built utilizing strict aliasing and isognu++11 mode.
Full "-O3" build. To those who don't know, this is the highest "optimization level" available in gcc that sets many other flags.
Important Links:
Download Nightlies - We have a very in depth review system, so these should be considered stable.
Download Weeklies - These are built once a week on Monday.
Download GApps
Download SuperSU Zip
Kernel Source
Interactive and Rolling Changelog
Bug Tracker
Instructions:
**This uses the 3.4 cm kernel tweaked for gcc-4.8 builds and as such,
follows all the same requirements as CM-10.2. NEWEST FIRMWARE/HBOOT are required. **
In the same recovery session, flash the following:
Flash rom
Flash GApps
Flash SuperSU zip
Reboot
Thank you for choosing codefireXperiment - See more at: http://www.codefirex.com/index.php?...htc-one-xl-codefirexperiment-nightlies#latest
CHAT on IRC Freenode #codefirex
PHABRICATOR - review system
GITHUB
Thanks to the CM team for all thier work on this family of devices, especiallly h8rift for his work on evita for all of us to enjoy.
Also thanks to my beta testers for experimenting with me.
DISCLAIMER: I will not be held responsible for any damages caused to your device by flashing this ROM. Your warranty is now void.
By proceeding you accept the risks involved with flashing ROMS. While I test everything on my own device, I cannot garauntee yours will not explode into kittens and rainbows.
KNOWN ISSUES:
ROOT ACCESS : On-going disscusion within the team but as of right now root is not available to userspace. Root currently works over adb only. Flash the superSU.zip and carry on if you need root access for apps like TiBu or root file explorers. Otherwise you really don't need it
BOOT ANIMATION : i'ts just full of struggle, it's an old animation made for smaller screens. It freezes and goes blank screen on first boot. Don't be alarmed, it'll be OK. New custom boot ani is being designed now by a fellow team member
BROWSER : Ocassional FC on embedded browser streaming video. You tube and links that open a video player are fine, just embedded video.
ROM is still under construction so i'm sure more will surface but this should be more than ready to be a daily driver.
mine too
Nice! Been testing this. Pretttyyyy smooth. LIKE BUTTAH!
RollTribe said:
Nice! Been testing this. Pretttyyyy smooth. LIKE BUTTAH!
Click to expand...
Click to collapse
Gets better everytime I rebuild it, new optimizations added everyday.
Scozzar said:
So that's where you went!!!! Too many ROMs to choose! :crying:
EDIT: Anyone want to provide some screenshots? I will be grateful if someone did!
Click to expand...
Click to collapse
Yeah this has been my obsession for the last 3-4 weeks.
Think stock nexus, this is AOSP MASTER branch with all the optimization tweaks on top of it and not much else...VERY MINIMAL
Sweet! I've been running this on and off with the new sense rom. Might just be me, but I feel like this gets better battery life.
Working great so far....smooth and fastest ROM I have used ever.
Sent from my One Xl using xda app-developers app
Nice! I'll wait til a more stable version comes about, but I'm looking forward to trying her out. With your success on Vanilla Root I'm sure this will be great as well!
How's the Camera on the One XL in this ROM? That's the only thing that's really ever bugged me about AOSP ROMs on our device, is that the Camera isn't nearly as good as Sense Based ROMs (not devs fault, camera libraries in sense are much different than AOSP). Does it change orientation quickly?
Gonna download and give it a spin. May be the last ROM I flash on my Evita
Got a Nexus 4 on the way to me.
Sent from my One X using Tapatalk 4
pside15 said:
Gonna download and give it a spin. May be the last ROM I flash on my Evita
Got a Nexus 4 on the way to me.
Sent from my One X using Tapatalk 4
Click to expand...
Click to collapse
You'll drive yourself nuts ROM hopping over there.... They've got more aosp ROMs than you could ever flash lol
Sent from my One Xl using Tapatalk 2
jrior001 said:
You'll drive yourself nuts ROM hopping over there.... They've got more aosp ROMs than you could ever flash lol
Sent from my One Xl using Tapatalk 2
Click to expand...
Click to collapse
Yeah, I'm sure I will. I've always wanted a Nexus device and I couldn't pass up the $199 price tag. I'm hoping I will be able to keep both devices but the wife will probably want me to sell my One X to pay for the N4.
I did take a look at the N4 section and it was a little out of control. I was always amazed how much development the DesireHD/Inspire had and the N4 was like 5 times that, lol. I think they have more kernels than we have ROMs, lol.
Sent from my One X using Tapatalk 4
Is there/will there be any way to change the hardware key assignments? I need the recent apps button on the right!
Sent from my One Xl using xda app-developers app
Edit-fixed for now with my launcher
Right now there is not. I played the same trick AOKP does do get recent on long press home. AFAIK aokp still doesn't have remapping either.
It could possibly be added later but I'd have to discuss with the rest of the team. They are far more concerned with getting the rest of their supported devices back up on 4.3 than anything else right now.
Sent from my One Xl using Tapatalk 2
Have this running since the last 12 hours or so and have to say, it is very stable and the battery life so far has been great. Good work!
Sent from my One Xl using xda app-developers app
I'm trying backup my stuff to flash this. Im pretty horrible at that task. Can't wait to run this rom again. I'll report back about how it runs. Thanks so much for this.
Edit: seems to run smoothly although many expected features are not present. Also some root apps take alot of work to get working suck as the latest AdAway. I wish it used Trebuchet and had most of the cm10.2 features especially the keyboard and clock.
Im not sure about this but are the nightlies started? i cant seem to find where to get them
RevolutionHeKz said:
Im not sure about this but are the nightlies started? i cant seem to find where to get them
Click to expand...
Click to collapse
Not yet, last I talked with synergy he was adding us to the nightly build list after I merged our device trees in, but it must not be done yet. Op will be updated as soon as I know something certain. If there's a hold up I'll post newer builds on my own until he catches up.
Sent from my One Xl using Tapatalk 2
DvineLord said:
Edit: seems to run smoothly although many expected features are not present. Also some root apps take alot of work to get working suck as the latest AdAway. I wish it used Trebuchet and had most of the cm10.2 features especially the keyboard and clock.
Click to expand...
Click to collapse
Some "features" will come but the team concentration right now is getting all supported devices caught up to 4.3, and debugging major issues. I didn't have any issues with any root apps but I don't use adaway.
Sent from my One Xl using Tapatalk 2
New nightly is up in OP.
Changlog:
Bluetooth- fixes for 48hz audio & issues with some car connections
Fixes for some issues with games crashing in 4.3
Updated camera proprietaries/kernel code from sense 5 Evita leak.
synergy is on vacay for a week so it will be a few days before we get added to the nightly builds. In the mean time I'll try to kick a few out to hold us over.
Sent from my One Xl using Tapatalk 2

Categories

Resources