Database Develop

[DISCONTINUED][ROM] Unofficial CM 7 Nightlies [Android 2.3.7/GWK74]

Introduction
Welcome to the Unofficial CyanogenMod Nightlies for the HTC Tattoo
The build is compiled from the latest cyanogen/github repos using the slightly tweaked device files.
Notes
This build is Unofficial work, not related to arco, kalim or CyanogenMod nightlies. Please do not report bugs to CyanogenMod for anything that is provided as part of this thread. I created this so that we all can updates to anything that CyanogenMod updates, bug fixes or enhancements.
Use this at your own risk. I will not be accountable if this causes you phone to fail, or you lose your data. The backup of your data is your responsibility.
General Info
The releases will co-inside and the build start time is at 02:01 GMT, and by 03:00 GMT the builds should be uploaded. If at anytime the builds are not there, then there was a problem building the ROM, and I will have a look at it ASAP.
I use this as my daily driver, so I will know if it didn't compile; so please don't add another post to mention the fact it isn't compiled.
Below You will find Download Links for Each Build and Instructions on how to install it.
Download
ROM: download (Download the lastest zip for click from the list)
GAPPS: Google Apps
Known Issues:
* Auto-Rotate doesn't work
Pre-requisites
* Rooted phone
* CWM 5
ChangeLog
* http://review.cyanogenmod.com/#q,status:merged+branch:gingerbread,n,z
* http://github.com/arif-ali/android_device_htc_click
Thanks/Credits
arco68 - original Development on Tattoo
KalimochoAz - original Development on Tattoo
CyanogenMod - For starting this great project
Google - This wouldn't have happened without the releases of Android from you
All comments/suggestions are welcome

another post just-incase

2 different builds?
Hi.
Why two men makes the same builds?
This build works fine: http://forum.xda-developers.com/showpost.php?p=21489211&postcount=135
Screen rotation works too.

OK, back again

arif-ali said:
no problem thread closed
I will stop building
sorry to cause inconvenience
Thread will be deleted
Click to expand...
Click to collapse
Arif, what's about CM9 for Tattoo?

brooklyn2001 said:
Arif, what's about CM9 for Tattoo?
Click to expand...
Click to collapse
Been busy with personal stuff and work.
I am hoping that this week will probably be productive on this end, and also trying to fix any bugs with CM7 with my build wrt to proprietary libs.

arif-ali said:
Been busy with personal stuff and work.
I am hoping that this week will probably be productive on this end, and also trying to fix any bugs with CM7 with my build wrt to proprietary libs.
Click to expand...
Click to collapse
You can ask furious anger what settings he's using while compiling the builds.

sunitknandi said:
You can ask furious anger what settings he's using while compiling the builds.
Click to expand...
Click to collapse
I use a different method, where my proprietary libs are extracted and public on http://github.com/arif-ali/android_vendor_htc_click
I don't use extract-files.sh, even then, there is a problem with that as well, as that is trying to extract akm8973, which doesn't exist. So I am presuming it is the akmd service that I may be needing.
Although I've had my Tattoo for more than 2 years now, I haven't really developed for it, so now I am getting into it, and trying to find out all the nitty gritty stuff to get everything to compile correctly for the Tattoo

arif-ali said:
I use a different method, where my proprietary libs are extracted and public on http://github.com/arif-ali/android_vendor_htc_click
I don't use extract-files.sh, even then, there is a problem with that as well, as that is trying to extract akm8973, which doesn't exist. So I am presuming it is the akmd service that I may be needing.
Although I've had my Tattoo for more than 2 years now, I haven't really developed for it, so now I am getting into it, and trying to find out all the nitty gritty stuff to get everything to compile correctly for the Tattoo
Click to expand...
Click to collapse
Here are proprietary libs of tattoo including akm since the script is impossible to pull of the phone.

Do you think it's worth the trouble porting ice cream sandwich to our tattoo?
I saw some vidoes on youtube about ics on the htc desire (!!).. they are slow as our tattoo with gingerbread. or even more.
So i don't think ics is usable on the tattoo.
Maybe it's better investing more time in fixing bugs, improving cm7 for our tattoo (like better battery time or make it faster with some kernelhacks) or adding some new features than wasting time on ics.

.dot said:
Do you think it's worth the trouble porting ice cream sandwich to our tattoo?
I saw some vidoes on youtube about ics on the htc desire (!!).. they are slow as our tattoo with gingerbread. or even more.
So i don't think ics is usable on the tattoo.
Maybe it's better investing more time in fixing bugs, improving cm7 for our tattoo (like better battery time or make it faster with some kernelhacks) or adding some new features than wasting time on ics.
Click to expand...
Click to collapse
Well, a stripped down ICS will also suffice.

Can anyone confirm that GPS is not working?

arif-ali said:
Introduction
Welcome to the Unofficial CyanogenMod Nightlies for the HTC Tattoo
The build is compiled from the latest cyanogen/github repos using the slightly tweaked device files.
Notes
This build is Unofficial work, not related to arco, kalim or CyanogenMod nightlies. Please do not report bugs to CyanogenMod for anything that is provided as part of this thread. I created this so that we all can updates to anything that CyanogenMod updates, bug fixes or enhancements.
Use this at your own risk. I will not be accountable if this causes you phone to fail, or you lose your data. The backup of your data is your responsibility.
General Info
The releases will co-inside and the build start time is at 02:01 GMT, and by 03:00 GMT the builds should be uploaded. If at anytime the builds are not there, then there was a problem building the ROM, and I will have a look at it ASAP.
I use this as my daily driver, so I will know if it didn't compile; so please don't add another post to mention the fact it isn't compiled.
Below You will find Download Links for Each Build and Instructions on how to install it.
Download
ROM: download (Download the lastest zip for click from the list)
GAPPS: Google Apps
Known Issues:
* Auto-Rotate doesn't work
Pre-requisites
* Rooted phone
* CWM 5
ChangeLog
* http://review.cyanogenmod.com/#q,status:merged+branch:gingerbread,n,z
* http://github.com/arif-ali/android_device_htc_click
Thanks/Credits
arco68 - original Development on Tattoo
KalimochoAz - original Development on Tattoo
CyanogenMod - For starting this great project
Google - This wouldn't have happened without the releases of Android from you
All comments/suggestions are welcome
Click to expand...
Click to collapse
Sorry to inform that the GPS is not working in update-cm7-click-20120218.
Please someone try to fix this bug.
I love this rom, it's fast but ...
I use the GPS function every day.
Sorry for my english.
---------- Post added at 12:33 AM ---------- Previous post was at 12:31 AM ----------
Vieira said:
Can anyone confirm that GPS is not working?
Click to expand...
Click to collapse
Yes, i confirm that it isn't working.
Viera, Sim eu confirmo que não está a funcionar.

GPS should be fixed now. update-cm7-click-20120220.zip; as of now
It was missing the gps.bahamas.so, This is was a typo from one of the gps repos that I was using.
regards,
Arif

arif-ali said:
GPS should be fixed now. update-cm7-click-20120220.zip; as of now
It was missing the gps.bahamas.so, This is was a typo from one of the gps repos that I was using.
regards,
Arif
Click to expand...
Click to collapse
With this nightly gps works perfectly.
Thank's.

I'm calling it a day with my Android hackery for now. RL and work is much more important than this. And this started affecting it.
So apologies for being able to do much with CM9.
I have seen that the buildbot from CM is now up and running, I presume they will start click as well.
I am sorry if I have wronged, or stolen any work without any credit given
Sent from my GT-I9100 using Tapatalk

Is there any new way how to get CM7 nightlies for our Tattoo? The buildbot isn't making any for our model and I can't find any other place where to get the nightlies and updated CM7.

bladez said:
Is there any new way how to get CM7 nightlies for our Tattoo? The buildbot isn't making any for our model and I can't find any other place where to get the nightlies and updated CM7.
Click to expand...
Click to collapse
My buildbot is down at the moment, and will start again, when I am back from my business trip later in a week or so. If I have time today, I might do it today
The latest on my webserver is http://cyanogenmod.arif-ali.co.uk/rom/update-cm7-click-2012-04-12_02-00-37.zip, from 2 weeks ago

.dot said:
Do you think it's worth the trouble porting ice cream sandwich to our tattoo?
I saw some vidoes on youtube about ics on the htc desire (!!).. they are slow as our tattoo with gingerbread. or even more.
So i don't think ics is usable on the tattoo.
Maybe it's better investing more time in fixing bugs, improving cm7 for our tattoo (like better battery time or make it faster with some kernelhacks) or adding some new features than wasting time on ics.
Click to expand...
Click to collapse
... or addidng a stable camera, fix that bug with .android_secure and other things that would make a complete and stable cm7 ROM.

my build bot is rebuilding again, check out http://cyanogenmod.arif-ali.co.uk/rom

CM10 or CM9?

Hey guys, I'm thinking of compiling a CM ROM from source next month (have to wait for data cap to reset) and was wondering what you guys would prefer, a significantly more stable CM9, or a more buggy (and more headaches for me) CM10 ROM? I personally would prefer to do a CM9 ROM since it would be easier to support and fix bugs on, since we already have relatively stable, working builds of AOSP ICS. CM10 would be great as well, but it would be much harder for me to support, since I would be the second dev for the Inc S to build a JB ROM from source for us. I just don't think I have the know-how to be the only one working on it, and the only one fixing bugs and whatnot, without any already working source code to view and compare.
So I could compile CM9.2 stable, and we would have the latest CM9 code using kaijura's IceColdSandwich as a reference. I would have an easier time supporting the ICS ROM since I would have working source code to compare and review. Also, it would be significantly more stable simply due to the fact that multiple devs for our device have already worked on it. I'm sure I'd be able to fix bugs and support it fairly easily, other devs are the best resource around
Or I could compile a CM10 ROM. I would have to take device proprietary files from nik's JB ROM's, which would mean my compiled ROM would share a lot of the same bugs our current JB ROM's already have. I could support and fix bugs in CM10, it would just take longer and be harder to do. Nothing's impossible though, so if that's what the community wants, then that's what I'll build!
So what do you guys think? CM10 or CM9?

It's your time and effort you do what Rom you want to do. Any Rom would be great!
Sent from my HTC Incredible S using Tapatalk 2

vizzy said:
It's your time and effort you do what Rom you want to do. Any Rom would be great!
Sent from my HTC Incredible S using Tapatalk 2
Click to expand...
Click to collapse
I'm torn between the two! On the one hand, I want a stable ROM which would be CM9, but I also love that JellyBean goodness. I've also seen some people here that simply want a stable CM9 that's up to date, and other's that want the latest CM10 despite bugs. That's the point of this thread

I would tell u is that first for cm9 when we get a stable awesome cm9 for sure it will be easy to get a cm10... btw are u going to build a kernel?

My vote goes towards CM9! been using codename for the past couple months and although i'm enjoying all the new features, i still find myself yearning for a rock solid & stable ASOP based build.
Sent from my Incredible S using Tapatalk 2

linezero said:
I would tell u is that first for cm9 when we get a stable awesome cm9 for sure it will be easy to get a cm10... btw are u going to build a kernel?
Click to expand...
Click to collapse
I could give it a try, but if nik and others couldn't get a 3.0 kernel up and running for AOSP, then I'll have a damn hard time. I'd prefer to have someone else make the new kernel, I don't know much about compiling them. Till then, I would just use X-ICS4.0 for the kernel.

Make a CM9, CM10 would have in the end too much bugs and they would just chance again. I'm waiting for a stable cm9 anyway
Sent from my HTC Incredible S using xda app-developers app

Kernel 3, Cm10 got my vote
sent from my jellybean device

ZaySk said:
Hey guys, I'm thinking of compiling a CM ROM from source next month (have to wait for data cap to reset) and was wondering what you guys would prefer, a significantly more stable CM9, or a more buggy (and more headaches for me) CM10 ROM? I personally would prefer to do a CM9 ROM since it would be easier to support and fix bugs on, since we already have relatively stable, working builds of AOSP ICS. CM10 would be great as well, but it would be much harder for me to support, since I would be the second dev for the Inc S to build a JB ROM from source for us. I just don't think I have the know-how to be the only one working on it, and the only one fixing bugs and whatnot, without any already working source code to view and compare.
So I could compile CM9.2 stable, and we would have the latest CM9 code using kaijura's IceColdSandwich as a reference. I would have an easier time supporting the ICS ROM since I would have working source code to compare and review. Also, it would be significantly more stable simply due to the fact that multiple devs for our device have already worked on it. I'm sure I'd be able to fix bugs and support it fairly easily, other devs are the best resource around
Or I could compile a CM10 ROM. I would have to take device proprietary files from nik's JB ROM's, which would mean my compiled ROM would share a lot of the same bugs our current JB ROM's already have. I could support and fix bugs in CM10, it would just take longer and be harder to do. Nothing's impossible though, so if that's what the community wants, then that's what I'll build!
So what do you guys think? CM10 or CM9?
Click to expand...
Click to collapse
cm9 bro! because ics kernel source is out and bugs can be fixed!

Yeah. CM9 would be OK for me too. I can help with testing if needed.
But what would be those great JB features we would be missing out? Sry I haven't been following the differences between 4.0 and 4.1.

IncS community is desperate for at least one fully functional, bugless AOSP ROM, so my vote goes for CM9

CM9 bro..wishing for bugless one.. gud luck..
Sent from my HTC Incredible S using xda app-developers app

My 2 cents.
CM9. Kernel sources for ICS has been release by HTC and ANY AOSP rom that is stable would be very welcome in our community.
(I know there is gingerbread roms.. But.. Its ginger bread..)
Jelly Bean is nice and all,
But the odds of getting a stable AOSP rom are much higher with cm9.

CM9 I would say. I hope you can fix data problems for Vodafone NL users. We always have problems with data connection on AOSP ROMs.

CM9 would be great....!!
Its great to see devs are enthusiasticaly working on Roms..!!
You are the one dude...
Jst for info u might already aware of
This thread
http://forum.xda-developers.com/showthread.php?t=1914015
CM10 test build
Sent from my HTC Incredible S using xda app-developers app

my vote a CM9 ASOP rom and bugless
Sent from my Incredible S using xda premium

naathaanb96 said:
cm9 bro! because ics kernel source is out and bugs can be fixed!
Click to expand...
Click to collapse
Totally agree. I don't like much sense ROMs, CM9 with working camera and camcorder would be perfect!
Thanks ZaySk

CM9!!!!

ZaySk said:
Hey guys, I'm thinking of compiling a CM ROM from source next month (have to wait for data cap to reset) and was wondering what you guys would prefer, a significantly more stable CM9, or a more buggy (and more headaches for me) CM10 ROM? I personally would prefer to do a CM9 ROM since it would be easier to support and fix bugs on, since we already have relatively stable, working builds of AOSP ICS. CM10 would be great as well, but it would be much harder for me to support, since I would be the second dev for the Inc S to build a JB ROM from source for us. I just don't think I have the know-how to be the only one working on it, and the only one fixing bugs and whatnot, without any already working source code to view and compare.
So I could compile CM9.2 stable, and we would have the latest CM9 code using kaijura's IceColdSandwich as a reference. I would have an easier time supporting the ICS ROM since I would have working source code to compare and review. Also, it would be significantly more stable simply due to the fact that multiple devs for our device have already worked on it. I'm sure I'd be able to fix bugs and support it fairly easily, other devs are the best resource around
Or I could compile a CM10 ROM. I would have to take device proprietary files from nik's JB ROM's, which would mean my compiled ROM would share a lot of the same bugs our current JB ROM's already have. I could support and fix bugs in CM10, it would just take longer and be harder to do. Nothing's impossible though, so if that's what the community wants, then that's what I'll build!
So what do you guys think? CM10 or CM9?
Click to expand...
Click to collapse
My request would be neither CM9 nor CM 10.... it will be great if you can work on Kernel Version 3.... Becz that is the only roadblock for us for Jelly Bean and would open doors for may developers to come up with fresh and exciting jelly bean ROMs.....Why stay behind the world guys... lets target Jelly bean step by step.....who knows if you start working on kernel it may really turn out to be good.....Try for kernel bro......all the best.. try to compile it from source....

A rock solid cm9 would be great!
Sent from my Incredible S using xda app-developers app

Different versions CyanogenMod

hey guys, do not know much about the CyanogenMod roms, I wonder what the difference between the versions and nightly snapshot?
Sorry for my bad English.

elderap said:
hey guys, do not know much about the CyanogenMod roms, I wonder what the difference between the versions and nightly snapshot?
Sorry for my bad English.
Click to expand...
Click to collapse
The Snapshot is a stable point where almost everything worked 100%. A couple of bugs that most people will miss and a few that is annoying but doesn't make it unstable.
The nightlies are not so well tested and receive commits from the main CM branch. They include the latest bugfixes and features but it might not be as stable.

elderap said:
hey guys, do not know much about the CyanogenMod roms, I wonder what the difference between the versions and nightly snapshot?
Sorry for my bad English.
Click to expand...
Click to collapse
First correct me if I'm wrong, other ppl like xonar_ definitly know more about it.
CM 7 is GB
CM 9 is ICS
CM 10 is JB
nighlys are done everyday and not much tested, I heard there are done automaticaly by a build robot
M snapshots are more tested and seem to come out every month
RC is tested a lot and the CM ppl think it is stable, if they find errors in it there will be another RC that corrects the errors, if not it will be declared stable

SaschaKH said:
First correct me if I'm wrong, other ppl like xonar_ definitly know more about it.
CM 7 is GB
CM 9 is ICS
CM 10 is JB
nighlys are done everyday and not much tested, I heard there are done automaticaly by a build robot
M snapshots are more tested and seem to come out every month
RC is tested a lot and the CM ppl think it is stable, if they find errors in it there will be another RC that corrects the errors, if not it will be declared stable
Click to expand...
Click to collapse
Everything is correct except nightly. Nightlys are only built when there are commits. Everyday means that the dev of the phone for CM has done a commit. That's why this week its everyday.
Sent from my LG-P970 using Tapatalk 2

SoulExertz said:
Everything is correct except nightly. Nightlys are only built when there are commits. Everyday means that the dev of the phone for CM has done a commit. That's why this week its everyday.
Sent from my LG-P970 using Tapatalk 2
Click to expand...
Click to collapse
Not just the develeoper of the phone. We also receive commits from the main CM10 branch. If you look at the device specific and kernel commits then you'll see that new nightlys are sometimes being released without there being any changes too them. CM10 still has bugs on the main branch and those bugs can be fixed by any person at CM not just our awesome phone developer rmcc.
Sent from my LG-P970

In this case, they are automatically released, this is why a later version "nightly" can not contain an adjustment that had been made in the last version (as in the case of video recording in our CM10 that worked in past releases and the latest does not work), leaving only when another snapshot version is that everything was done correctly should not it contain?

Snapshot or Release Candidates
Thanks for you wonderful explanation guys, but this might be a noobish question, if I were to choose or you are, would you pick snapshot or RC's?
Thanks! :good:

StanceMitchell said:
Thanks for you wonderful explanation guys, but this might be a noobish question, if I were to choose or you are, would you pick snapshot or RC's?
Thanks! :good:
Click to expand...
Click to collapse
Depends on how close to the RC the snapshot is....
A snapshot from the day after a RC should be almost identical to the RC, plus (hopefully) fixes.
A snapshot far after a release could be introducing a bunch of new features (and bugs to go with them).
I'd be more interested in reading snapshot changelogs, relative to the last release or release candidate.

[AOSP] Who should I be following as the better AOSP. CM or FreeXperia?

Hey so I love that we have AOSP for my Sony = Sony Nexus!!
But who should I be following as the cutting edge of AOSP. I know Sony releases some sources but not the proprietary ones so I know most of it comes from there. I myself have just installed the latest RC3 of CM 10.1. And the bugs I used to have like Lockscreen delay and No audio on Hangouts seem to have gone. But why should I install FreeXperia over CM?
Is CM the base that everyone bases their AOSP on? Is Free Xperia more focused on the Sony Specific Issues?
And what about Linaro? Carbon? AOKP? Are they all based off the same source (they all seem to have the same bugs)
Thoughts? Direction?
Thanks in advance!

First of all, CM roms are made by the FXP team as they are official CM maintainers for Sony devices.
Secondly, Sony's AOSP sources are different from that of CM sources. AOSP implies pure android with stock customizations. CM sources is heavily customizable (think of all the settings you can do in CM10.1) they are based on Google's open source as well as the device specific source code released by Sony.
Sent from my C6602 using xda app-developers app

CM10.1 vs. Free Xperia
What is the difference between the regular CM and the one you can download from FreeXperia project?
E.g. for Xperia Z (the latest releases at the moment):
FXP222a-cm-10.1-20130604-UNOFFICIAL-yuga.zip
Click to expand...
Click to collapse
vs.
cm-10.1-20130608-NIGHTLY-yuga.zip
Click to expand...
Click to collapse

80mercury said:
What is the difference between the regular CM and the one you can download from FreeXperia project? ...
Click to expand...
Click to collapse
I too would like to know this - obviously, they're very close, but there must be something different there.
I spent an hour trying to find this out the other night - got slightly excited when I saw a message from some poor sucker who explained he was a noob, etc, blah, blah, and would someone please explain the difference. The only reply he got was a terse demand that he go read the FreeXperia dev thread and work it out for himself ...
If someone can write an explanatory sentence or two about the difference between the builds on the official Cyanogen Mod site and the FXP* builds from freexperiaproject.com, I would appreciate it.

ratworks said:
I too would like to know this - obviously, they're very close, but there must be something different there.
I spent an hour trying to find this out the other night - got slightly excited when I saw a message from some poor sucker who explained he was a noob, etc, blah, blah, and would someone please explain the difference. The only reply he got was a terse demand that he go read the FreeXperia dev thread and work it out for himself ...
If someone can write an explanatory sentence or two about the difference between the builds on the official Cyanogen Mod site and the FXP* builds from freexperiaproject.com, I would appreciate it.
Click to expand...
Click to collapse
hey man, I had forgotten that I had made this thread but long story short FXP and CM are the same. CM has their own schedule, standards and code they develop and CM work towards AOSP for all their devices. FXP are SONY only, They use the code by CM and are responsible for both the Sony releases via CM and FXP. How FXP differs is that they can go ahead and release a lot of versions without any established "stable" or milestones they just release updates as they go. CM take those Sony specific changes that are made and combine them standard CM code are release Milestones, RC's and Nightlies with varying results
TLDR: They are the same, All the Sony specific code in CM is FROM FXP, FXP has no interest in making a stable version they just release new code in an almost "nightly" fashion. Their is no guarantee that the newest FXP will be more stable then the previous, its the same risk you take when you go with CM nightlies.
Personally I prefer CM Nightlies. If you want stable (with established bugs) go with CM, if you want to be running the latest CM code go with CM but if you want the latest sony fixes (unstable at times) go FXP, who updates about 1 every 1-2 weeks

Great explanation mate, thanks for that.

[Q] CM 10.2

Hi All,
I remember that we will not be receiving next major version of Android by CM becoz of lack of NEON instructions. I only wonder, if we will still get CM 10.2 or our last version will be CM 10.1.
Can anybody with CM insider knowledge answer?
I can only see that there was not created CM10.2 branches in our P990 github related repositories, which is bad sign to me.
Edit: Answer is Yes, CM10.1 is last version.

CM 10.1 seems to be the latest official version of cyanogenmod. But just look at all the gifted developers in the development thread. I guess someone will get it working on our device .
I think even some time ago pengus or tonyp mentioned that they like the challenge ....:thumbup:
Sent from my LG-P990 using xda app-developers app

Yes, I have read tonyp's thread and there was mentioned that CM team officially won't support 10.2 for our phone. But I hope Pengus and Tonyp will make something But it's quite possible that it will be a little bit unstable and glitchy...

p.valenta said:
Hi All,
I remember that we will not be receiving next major version of Android by CM becoz of lack of NEON instructions. I only wonder, if we will still get CM 10.2 or our last version will be CM 10.1.
Can anybody with CM insider knowledge answer?
I can only see that there was not created CM10.2 branches in our P990 github related repositories, which is bad sign to me.
Edit: Answer is Yes, CM10.1 is last version.
Click to expand...
Click to collapse
nope it isn't if you watch the developer thread you see cm10.2 only camera doesn't work yet but further it is smooth and stable i am posting this cause you may didn't see it

winstonxl2 said:
nope it isn't if you watch the developer thread you see cm10.2 only camera doesn't work yet but further it is smooth and stable i am posting this cause you may didn't see it
Click to expand...
Click to collapse
Thanks, I know about it. But unfortunately it will not be official CM, only experimental.
It's great that there are still developers who want to keep our device up to date :fingers-crossed: , but looks like it's time to look around for next future device.

p.valenta said:
Thanks, I know about it. But unfortunately it will not be official CM, only experimental.
It's great that there are still developers who want to keep our device up to date :fingers-crossed: , but looks like it's time to look around for next future device.
Click to expand...
Click to collapse
it isn't really experimental only the camera doesn't work and all cm10.1 bugs are included but cm10.2 is smoother and hdmi is partly fixed