Database Info

[N9005][Beta][Unofficial] - CyanogenMod 11 - Test Build 2014-01-13

Update 2014-01-15
Well, the wait has an end! Official nightlies are out! That means I'm off the hook for building!
I'd like to thank everybody who participated by flashing, and posting in this thread. I really had a great time building CM11 for this device! Obviously, the CM team deserves the credit, they were the ones who gave us this awesome ROM!
Official CM11 nightlies can be downloaded here:
N9005
http://download.cyanogenmod.org/?device=hltexx
To flash the 2014-01-15 nightly on the N9005, you must first remove a device check for hltexx in the update script. You can do this by opening up the .zip, editing the updater-script located under /META-INF/com/google/android/, and removing the assert(...) line at the top.
Other Versions:
http://download.cyanogenmod.org/?device=hltetmo (t-mobile)
http://download.cyanogenmod.org/?device=hltespr (sprint)
http://download.cyanogenmod.org/?device=hltevzw (verizon)
Happy Flashing!!
Last Build: 2014-01-13:
The File:
http://d-h.st/J92
md5: a4bddcec13c97db0ec484f40efccc9d0
mirror: https://mega.co.nz/#!V9xzUBgZ!QGPoHBqWxKcDOuMGwpSVcTjZ2VsxsJw9EXO7tLOthWE
Disclaimer:
You flash at your own risk! I take no responsibility for your device!
Warning/Compatibility:
I have tested this on my N9005 only. I removed the assert line in the update script so it can be flashed directly w/o editing.
Changes:
Check review.cyanogenmod.org for more information.
2014-01-13:
- Anything merged by 6:30PM CET
2014-01-12:
- Anything merged by 5:00PM CET
- Battery drain issues seem to be resolved. Will give it a few days before taking it off the list.
2014-01-11:
- Anything merged by 8:30AM CET
2014-01-09:
- Anything merged by 7:00PM CET
2014-01-08:
- Anything merged by 6:30PM CET
2014-01-07:
- Anything merged by 6:30AM CET
2014-01-05:
- Stylus gestures now supported (via settings -> language & input)
- Stylus hovering icon can now be enabled (via settings -> language & input)
2014-01-03:
- http://review.cyanogenmod.org/#/c/56805/
- Updated the two others (56727 and 56730) which are not yet merged to latest patch sets.
- Touch screen issue is fixed (no more touches registered when screen is off).
- Hopefully battery drain is fixed too.
2014-01-02:
http://review.cyanogenmod.org/#/c/56727/
http://review.cyanogenmod.org/#/c/56728/
http://review.cyanogenmod.org/#/c/56730/
Confirmed Working:
- Sound
- Camera (picture & video)
- Calls/SMS
- Data 2g/3g/4g/wifi
- External SD
- GPS
- BT
- NFC
- USB OTG
- IR
- MHL
- ART
- Proximity sensor
- Light sensor
- Humidity sensor
- Thermometer
- Barometer
Known Issues:
- Touches are registered while in-call even when the screen is off
- Mic does not work in hands-free mode
- Battery drain (probably fixed)
- Compass not functioning in some apps
Installation:
1. Download .zip to external SD.
2. Flash via recovery. (I use chenglu cwm)
- In theory you can dirty flash these updates, I usually do the wipes though.
- Coming from TW you must wipe.
- If you're having issues others are not, wipe!
Gapps:
I personally use an aroma installer found here. You can select which ones you want to install. Alternatively you can find packages at cyanogenmod.org.
Enjoy!
Previous Versions:
2014-01-12: file md5: c2186c357f9c503bd8cfa941834bebfa
2014-01-11: file md5: 88395918a155ff80fe94b5c732bf950a
2014-01-09: file md5: e35b69fbcd5c2711a8595ea078152d5f
2014-01-08: file md5: adc7183daf010285e1f3b3623fe4a62b
2014-01-07: file md5: 45919a2e84e6d6afa69a820ea5449cd1
2014-01-05: file md5: ace79a7843e80f304ef5e23c71d7786f
2014-01-03: file md5: 6a2bbec972bc03623cf907c3aedbac21
2014-01-02: file md5: 9b1140bb1242e62ce78af2165d1c199e
2014-01-01: file md5: 346487b8e9f6e1fdc3b005a604f58c0e
2013-12-31: file md5: db9d51d087f032527371575958d5fad2
2013-12-29: file md5: 1e0c8e160703dabb2fb6b475af26ea55
2013-12-29: file md5: ce5cb1c86077ab1fb9074b7f278eb5c0
2013-12-28: file md5: 3511e57d57b91109329932365501f686
-----------------------------------------------------------------
Original post, 2013-12-31:
Update 2013-12-31:
Just uploaded a new build!
Noticeably, calling now works (both making/receiving)! No word on bt calling, that has yet to be confirmed.
So now it's time to list things that are *not* working rather than things that are working!
NFC --> Could anyone make a statement on that?
The File:
http://d-h.st/Qq4
md5: db9d51d087f032527371575958d5fad2
Enjoy it guys!
A big thank you to the CM team for working out all the major bugs within a few days really, and of course everyone who has contributed by commiting patches, testing, discussing, etc!
I'm not sure I'll do more builds today, as I have a few errands to run before the new years celebration! A celebration it will be indeed with CM on our notes!
-----------------------------------------------------------------
Original post, 2013-12-29 #2:
Update 2013-12-29 #2:
Just uploaded a new build! I have to go out for a few hrs, but wanted to share it quickly.
- External SD is now working
- Audio seems to be working better now (it's not near-muted this time.)
I haven't tested other things though.
The File:
http://d-h.st/ShX
md5: 1e0c8e160703dabb2fb6b475af26ea55
-----------------------------------------------------------------
Original post, 2013-12-29 #1:
Update 2013-12-29:
Just uploaded a new build! It's running better than the first one. Noticeably, the following things have changed:
- Camera works now (FC before)
- Gallery works (FC before)
- Data (3g/4g) works
- Audio works (speakers and headphones, but very quiet.)
- Calls are not working. You can call the phone, but it wont ring on the receiving side.
- External SD is not mounting. (This issue has been reported by the tmo guys already)
The File:
http://d-h.st/QaT
md5: ce5cb1c86077ab1fb9074b7f278eb5c0
Disclaimer:
You flash at your own risk! I take no responsibility for your device!
-----------------------------------------------------------------
Original post, 2013-12-28:
Good news!
I got it built, and it boots to launcher (confirmed on my n9005)! I'm only sharing this for the many flash happy out there waiting to see what cm11 feels like. The build is not a daily driver.
Sources
This is based on the official cm repos:
Code:
<manifest>
<project name="CyanogenMod/android_device_samsung_hltexx" path="device/samsung/hltexx" remote="github" />
<project name="CyanogenMod/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" />
<project name="CyanogenMod/android_device_samsung_msm8960-common" path="device/samsung/msm8960-common" remote="github" />
<project name="CyanogenMod/android_device_samsung_hlte-common" path="device/samsung/hlte-common" remote="github" />
<project name="CyanogenMod/android_kernel_samsung_hlte" path="kernel/samsung/hlte" remote="github" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" revision="cm-11.0" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-11.0" />
</manifest>
Issues:
- Camera FC
- Gallery FC
- No Data / GSM
- Probably alot more
- Model no shows up as n9000 (I flashed on n9005)
Installation:
1. Download the zip
2. Wipe and flash via recovery, (I used chenglu cwm)
The first two boots took forever (10 minutes?) now it boots relatively quickly.
Disclaimer:
You flash at your own risk! I take no responsibility for your device!
The File:
http://d-h.st/JUs
md5: 3511e57d57b91109329932365501f686
The Future
I'm on leave for a couple of days, so if testers want to attach logcats ill take a look at what i can fix.
I guess I'll sync and build daily for the next couple of days, or until a more experienced developer comes along and builds CM11

Great work, It's nice to see I would test, however im having to use my phone as a connection point..so with no data connection it could mean im stuck until I get to another connection
Goodluck and look forward to seeing more from you

SM-N9000? You have the N9005 right?
Did you apply the patch noobnl posted on the tmo thread?
Sent from my SAMSUNG-SGH-I717 using xda app-developers app

CalcProgrammer1 said:
SM-N9000? You have the N9005 right?
Did you apply the patch noobnl posted on the tmo thread?
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
Yes, I have the N9005. I was breakfasting and brunching hltexx. Is hltexx not the 9005?
Did not see that patch, thanks for that! I'll apply it and rebuild tomorrow. Its 2AM now, I'm done for today.
PS: camera likes to hog CPU time on this build. Can kill it via terminal emu or delete the apk from system/app.

LTE working just spiffy here. I didn't need to patch or pull any files. Added muppets repo and it built smoothly.

sturmavik said:
LTE working just spiffy here. I didn't need to patch or pull any files. Added muppets repo and it built smoothly.
Click to expand...
Click to collapse
Very nice! You got the right model number too Can you post your roomservice.xml?
That patch you speak of has been merged:
http://review.cyanogenmod.org/#/c/56103/
How are camera and audio doing in your build? Were you brunching cm_hltexx-eng ? I'm gonna try that now

ponglenis said:
Very nice! You got the right model number too Can you post your roomservice.xml?
Click to expand...
Click to collapse
I just followed the instructions and copied the roomservice.xml from http://forum.xda-developers.com/showthread.php?t=2485033
ponglenis said:
How are camera and audio doing in your build? Were you brunching cm_hltexx-eng ? I'm gonna try that now
Click to expand...
Click to collapse
Yeah. Brunched cm_hltexx-eng. Had to patch updater_script as explained in the thread in order to flash my zip. Audio worked but was pretty quiet. Camera was borked in a big way. I actually nandroided back to TW because in my excitement I forgot to offload my gallery pictures and backup my sms.
But damn that was a wonderful few minutes of CM glory!

Does external sdcard work in your build? It doesn't detect properly on hltetmo and it looks like it's an issue with the hlte common repo that affects all variants.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app

sturmavik said:
Yeah. Brunched cm_hltexx-eng. Had to patch updater_script as explained in the thread in order to flash my zip. Audio worked but was pretty quiet. Camera was borked in a big way. I actually nandroided back to TW because in my excitement I forgot to offload my gallery pictures and backup my sms.
Click to expand...
Click to collapse
Good, i have the same repos (except hltexx instead of hltetmo). I'm building atm, synced at around 09:15 CET. Let's see how it goes
sturmavik said:
But damn that was a wonderful few minutes of CM glory!
Click to expand...
Click to collapse
Oh yes, it's very snappy! Need to get a daily driver asap!

CalcProgrammer1 said:
Does external sdcard work in your build? It doesn't detect properly on hltetmo and it looks like it's an issue with the hlte common repo that affects all variants.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
Can confirm its not working on yesterdays build. Will report back if anything is fixed in the new build!

Psss.
Nice to see any progress.
G00D JOB.
I cant wait for a stable release.
I need the DATA & GALLERY & CAMERA and all other working ..
But it's great news - I had a Xiaomi MI2A and NOTE I and i changed to NOTE III , cant wait for 4.4.2 or CM from any kind.

Managed to get it up and running on my n9005, although it thinks its a n9000. Camera and gallery seem to be working OK, still no external storage and unable to hang up from calls....
https://plus.google.com/105753056745777397846/posts/ihc4BcfKq4z
Sent from my SM-N9000 using XDA Premium 4 mobile app

choppiii said:
Managed to get it up and running on my n9005, although it thinks its a n9000. Camera and gallery seem to be working OK, still no external storage and unable to hang up from calls....
https://plus.google.com/105753056745777397846/posts/ihc4BcfKq4z
Sent from my SM-N9000 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Oh boy, thats more good news! At this pace we'll have a daily driver before 2014!
My build showed up as N9000 too. But my build.prop was a mess. I was brunching hltexx. Now trying cm_hltexx-eng. I'ts almost done.
Anything special you did while building? I'm guessing you're using the same repos as posted here, or?

ponglenis said:
Oh boy, thats more good news! At this pace we'll have a daily driver before 2014!
My build showed up as N9000 too. But my build.prop was a mess. I was brunching hltexx. Now trying cm_hltexx-eng. I'ts almost done.
Anything special you did while building? I'm guessing you're using the same repos as posted here, or?
Click to expand...
Click to collapse
Yeah I brunched hltexx to then couldn't get it to flash so I had to change the update script from hltexx to htle in the .zip
Sent from my SM-N9000 using XDA Premium 4 mobile app
---------- Post added at 08:06 PM ---------- Previous post was at 07:59 PM ----------
Issues aside how nice does it feel to have CyanogenMod running on our phones.... Its going to kill me going back to crap wiz tomorrow when I have to go to work... ?
Sent from my SM-N9000 using XDA Premium 4 mobile app

Well the build from this morning is no good. Stuck on Samsung logo on boot.
Going to clean, sync and try again!

Just finished another build but couldn't get it to flash, I get a status 7 error, this package is for "htlexx" device; this is a "htle" which is the same as before so without changing the update script which I'm not going to do now as I have to be up for work 5 hours it won't flash....
And yes I'm using the same repos posted here to answer your question from earlier...
My first build sat on the Samsung logo for what felt like few minutes before it booted so give it time if it happens again.
Sent from my GT-N7100 using XDA Premium 4 mobile app

ponglenis said:
Good news!
I got it built, and it boots to launcher (confirmed on my n9005)! I'm only sharing this for the many flash happy out there waiting to see what cm11 feels like. The build is not a daily driver.
Sources
This is based on the official cm repos:
Code:
<manifest>
<project name="CyanogenMod/android_device_samsung_hltexx" path="device/samsung/hltexx" remote="github" />
<project name="CyanogenMod/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" />
<project name="CyanogenMod/android_device_samsung_msm8960-common" path="device/samsung/msm8960-common" remote="github" />
<project name="CyanogenMod/android_device_samsung_hlte-common" path="device/samsung/hlte-common" remote="github" />
<project name="CyanogenMod/android_kernel_samsung_hlte" path="kernel/samsung/hlte" remote="github" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" revision="cm-11.0" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-11.0" />
</manifest>
Issues:
- Camera FC
- Gallery FC
- No Data / GSM
- Probably alot more
- Model no shows up as n9000 (I flashed on n9005)
Installation:
1. Download the zip
2. Wipe and flash via recovery, (I used chenglu cwm)
The first two boots took forever (10 minutes?) now it boots relatively quickly.
Disclaimer:
You flash at your own risk! I take no responsibility for your device!
The File:
http://d-h.st/JUs
md5: 3511e57d57b91109329932365501f686
The Future
I'm on leave for a couple of days, so if testers want to attach logcats ill take a look at what i can fix.
I guess I'll sync and build daily for the next couple of days, or until a more experienced developer comes along and builds CM11
Click to expand...
Click to collapse
I think you have either patched something wrong or used some wrong source, because if you have a look in carrier settings, it gives CDMA options in the settings.

wilfredlams said:
I think you have either patched something wrong or used some wrong source, because if you have a look in carrier settings, it gives CDMA options in the settings.
Click to expand...
Click to collapse
Something was borked. Did not patch anything myself, not sure what it was. Uploading a new build now, it's running better. Camera, data (3G/4G) and sound (can't testify on in call sound yet) are working now, but its experiencing a similar issue others have reported regarding hanging up a call.

ponglenis said:
Something was borked. Did not patch anything myself, not sure what it was. Uploading a new build now, it's running better. Camera, data (3G/4G) and sound (can't testify on in call sound yet) are working now, but its experiencing a similar issue others have reported regarding hanging up a call.
Click to expand...
Click to collapse
That's cool, I will test it again when you provide the link.

wilfredlams said:
That's cool, I will test it again when you provide the link.
Click to expand...
Click to collapse
Thanks! Thats perfect! Feel free to attach logcats of bugs in action. A link to the new build can be found in the first post now! I'll be updating that when i upload new builds.
I saw a few more merges on http://review.cyanogenmod.org/ for our device, I'm starting a new build now! Hoping for sd card fixes

[DEV] [sm-t320 == tab pro 8.4] CM-11.0 unofficial bringup for mondrianwifi USA

This thread is for developers only and I will not be posting ROMs here.
I am posting this here in the hope that someone else has time, skills and motivation to help work on this. If so, please PM me and/or send me pull requests.
I am basing this off of the HLTE kernel because it is being very well maintained and has many huge advances from CAF.
Links:
Kernel: https://github.com/crpalmer/android_kernel_samsung_mondrianwifi
Device: https://github.com/crpalmer/android_device_samsung_mondrianwifi
Vendor: https://github.com/crpalmer/android_vendor_samsung_mondrianwifi
I am also using these dependent repositories:
Code:
<project path="device/samsung/msm8960-common"
name="CyanogenMod/android_device_samsung_msm8960-common"
remote="github" revision="cm-11.0"
/>
<project path="device/samsung/qcom-common"
name="CyanogenMod/android_device_samsung_qcom-common"
remote="github" revision="cm-11.0"
/>
<project path="hardware/qcom/display-caf-new"
name="CyanogenMod/android_hardware_qcom_display-caf-new"
groups="caf"
/>
<project path="hardware/qcom/media-caf-new"
name="CyanogenMod/android_hardware_qcom_media-caf-new"
groups="caf"
/>
<remove-project name="CyanogenMod/android_hardware_invensense" />

This was the status but since I got further faster than I was expecting, there is now a build thread which has the status there.

crpalmer said:
Current status:
* clockworkmod recovery: seems to be working fine
* CM 11 boots and the base seems to be generally not horrendously broken
Hardware status:
* display: backlight doesn't work, therefore it also won't turn back on once it turns off
* usb: adb works, nothing else tested
* WiFi: doesn't work
* everything else: haven't even looked at it, and therefore probably doesn't work
Click to expand...
Click to collapse
The source has been published by Samsung.
opensource.samsung.com
Sent from my SM-T320 using XDA Premium HD app

crpalmer said:
Current status:
* clockworkmod recovery: seems to be working fine
Click to expand...
Click to collapse
I'm interested. Do you have a version of CWM recovery that you have compiled that you can share or steps you used to build?
Thanks!

blulite said:
I'm interested. Do you have a version of CWM recovery that you have compiled that you can share or steps you used to build?
Thanks!
Click to expand...
Click to collapse
The cwmr that I am using is the one that gets built by running a full CM build using the repos I pointed toward. If you can build CM then you should be able to build a recovery that works on at least my tablet. However, I am definitely not sharing a build because of the fact that it is based on the hlte kernel and could be causing serious problems.
I'm going to try to merge the official source into the hlte kernel and see if I can get that working. If so, it will be a fair bit less risky (although it is still risky because random people like me are playing with how the hardware gets used including voltages, current, etc.).
If you were trying to build a recovery yourself, yeah, you probably ran into problems because the bootloader requires a boot.img with a device tree and the DT needs to be version 2 format which is quite new.

Updated the kernel link. It is a merge of the KK_NA source released by samsung into the hlte kernel from cyanogenmod. It builds but the display is still borked (the left hand of the screen now turns back on, but the right does not...).
If anyone was working with these repos, please do not use the original hlte fork any longer.

[Q&A] [OFFICIAL] [NIGHTLY] Cyanogenmod 12 for Motorola Droid MAXX

Q&A for [OFFICIAL] [NIGHTLY] Cyanogenmod 12 for Motorola Droid MAXX
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [OFFICIAL] [NIGHTLY] Cyanogenmod 12 for Motorola Droid MAXX. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Possible daily Driver
Hey been following the offical cm12 for droid maxx for a bit was sad when cm dropped support for my phone but now that its back im happy again. Well anyways i know cm12 being relatively newish i was wondering if this would be able to be run as a daily driver. i know its buggy i dont mind fc's but as long as i got txt, voice, data, and gps ill be happy.
so would this be able to run as a daily driver? i currently do not have another phone to work with
I do have a droid maxx Dev edition
Edit: I Figured it out this can be deleted thanks also yes it can be a daily driver obviously with above statements.

smokyngordo said:
Hey been following the offical cm12 for droid maxx for a bit was sad when cm dropped support for my phone but now that its back im happy again. Well anyways i know cm12 being relatively newish i was wondering if this would be able to be run as a daily driver. i know its buggy i dont mind fc's but as long as i got txt, voice, data, and gps ill be happy.
so would this be able to run as a daily driver? i currently do not have another phone to work with
I do have a droid maxx Dev edition
Edit: I Figured it out this can be deleted thanks also yes it can be a daily driver obviously with above statements.
Click to expand...
Click to collapse
In using a droid ultra and have been running since 1/24 nightly. There is the ear piece bug when making a call (toggle speaker and untoggle to get ear piece to work). The biggest issue is for me is no ambient display. I don't know if they are going to add that in later or not but I have been using acdisplay and that has been working fine for me
CM12 Inside DROID Ultra

tecsironman said:
In using a droid ultra and have been running since 1/24 nightly. There is the ear piece bug when making a call (toggle speaker and untoggle to get ear piece to work).
Click to expand...
Click to collapse
Is there ear piece bug in the last nightly too?

mainbord said:
Is there ear piece bug in the last nightly too?
Click to expand...
Click to collapse
Yes..
CM12 Inside DROID Ultra

I've tried all methods posted and no luck. Guess CM12 isn't for me.
Prior to trying I was stock su6-7 but with ART other than that I was pretty bland.
Best of luck to all. I will try again in the future, but enough of my day has been wasted today. I tried both 01/24 and 01/31 for all the methods listed. Waited a minimum of 20 minutes for boot each time.

cdfjr1975 said:
I've tried all methods posted and no luck. Guess CM12 isn't for me.
Prior to trying I was stock su6-7 but with ART other than that I was pretty bland.
Best of luck to all. I will try again in the future, but enough of my day has been wasted today. I tried both 01/24 and 01/31 for all the methods listed. Waited a minimum of 20 minutes for boot each time.
Click to expand...
Click to collapse
I would dump art and go back to dalvik. Run with that for a couple days and try it again.
CM12 Inside DROID Ultra

cdfjr1975 said:
Waited a minimum of 20 minutes for boot each time.
Click to expand...
Click to collapse
same thing happen to me but i tried installing it at night when i didnt use my phone. i left it on the charger as well. when i woke up the next morning i was greeted with the setup screen.

smokyngordo said:
same thing happen to me but i tried installing it at night when i didnt use my phone. i left it on the charger as well. when i woke up the next morning i was greeted with the setup screen.
Click to expand...
Click to collapse
Thanks for the input, I will try this at work tomorrow.
Which build, nightly and gapps combo did you use? Which recovery and wipe sequence?
Thanks again.
---------- Post added at 05:06 PM ---------- Previous post was at 05:04 PM ----------
tecsironman said:
I would dump art and go back to dalvik. Run with that for a couple days and try it again.
CM12 Inside DROID Ultra
Click to expand...
Click to collapse
Back on Dalvik and no joy so far. Keeping fingers crossed one day it will work. Funny how each phone is a little different.

cdfjr1975 said:
Thanks for the input, I will try this at work tomorrow.
Which build, nightly and gapps combo did you use? Which recovery and wipe sequence?
Thanks again.
---------- Post added at 05:06 PM ---------- Previous post was at 05:04 PM ----------
Back on Dalvik and no joy so far. Keeping fingers crossed one day it will work. Funny how each phone is a little different.
Click to expand...
Click to collapse
Yes very different. I have been unlocked since last year so I have used other recoveries but I always fxz back for an update.
CM12 Inside DROID Ultra

cdfjr1975 said:
Thanks for the input, I will try this at work tomorrow.
Which build, nightly and gapps combo did you use? Which recovery and wipe sequence?
Click to expand...
Click to collapse
im used the 20150128 nightly and i cant recall the gapps i used. i do remember that i used one that was put together in November.
sorry for the late response hope you are/were able to figure it out

No worries @smokyngordo I used the below to get CM12 since a clean install wasn't working for me
CM12 didn't work for me either I had to go through CM11 and upgrade<br />
<br />
Started with stock su6-7<br />
<br />
CM11<br />
Used instructions from this post<br />
<br />
http://forum.xda-developers.com/showthread.php?t=2911626<br />
<br />
I used the snapshot version of cm11<br />
<br />
I had to change my<br />
ro.product.device and ro.build.product to ghost in the build prop prior to flashing since I was getting status 7 errors<br />
<br />
I needed a factory reset since I also received incompatible data errors <br />
<br />
CM12<br />
<br />
After install and initial boot of cm11<br />
Used rashr to flash back twrp 2.8.4.0 recovery<br />
Factory reset<br />
<br />
I flashed cm12 01/24 build with these gapps <br />
<br />
https://s.basketbuild.com/filedl/gapps?dl=gapps-lp-20141109-signed.zip<br />
<br />
Haven't taken other nightlies due to errors being reported<br />
<br />
All good from there so far(only one day in though)<br />
<br />
Hope this helps.<br/>

having issues with the gapps cm12.1?
Have a Droid Maxx Dev Edition
i started with a wiped device.(wiped all the partitions) flashed cm12.1 and the gapps on the cm wiki.
i keep getting this error " unknown issue with google play services"
any help would be greatly appreciated.

smokyngordo said:
Have a Droid Maxx Dev Edition
i started with a wiped device.(wiped all the partitions) flashed cm12.1 and the gapps on the cm wiki.
i keep getting this error " unknown issue with google play services"
any help would be greatly appreciated.
Click to expand...
Click to collapse
Try 5.1 gapps from here
http://forum.xda-developers.com/android/software/gapps-google-apps-minimal-edition-t2943330

SnipeR_TT said:
Try 5.1 gapps from here
http://forum.xda-developers.com/android/software/gapps-google-apps-minimal-edition-t2943330
Click to expand...
Click to collapse
hey thanks for the link. it worked kinda. For some reason i have to flash both that one and the cm wiki one for mine to work.

This is working well... Thank you very much!

Anyone having an issue with adaptive brightness?
Sent from my DROID Ultra using Tapatalk

[WIP]CyanogenMod 12.1 for Xiaomi Mi 4i

SOURCES
I've worked on this in the last 4-5 days... Unfortunately, i've no too much spare time, so I've published my sources, because I'm stucked on several areas...
I'm asking every Developer to collaborate.
This source is very experimental. I'm not responsible if you transform your phone into a brick!
kernel: https://github.com/dh-harald/android_kernel_xiaomi_ferrari
device: https://github.com/dh-harald/android_device_xiaomi_ferrari
optional:
vendor: https://github.com/dh-harald/android_vendor_xiaomi_ferrari
so your local_manifest must be something like this:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="kernel/xiaomi/ferrari" name="dh-harald/android_kernel_xiaomi_ferrari" />
<project path="device/xiaomi/ferrari" name="dh-harald/android_device_xiaomi_ferrari" />
<project path="vendor/xiaomi/ferrari" name="dh-harald/android_vendor_xiaomi_ferrari" />
<project path="device/qcom/common" name="CyanogenMod/android_device_qcom_common" />
<project path="external/mm-dash" name="CyanogenMod/android_external_mm-dash" />
<project path="hardware/qcom/fm" name="CyanogenMod/android_hardware_qcom_fm" />
</manifest>
Quick compile guide:
Code:
cd <your source>
. build/envsetup.sh
brunch cm_ferrari-userdebug
This topic is strictly for developers, so it will be enough for help

IMPORTANT
The binary base of my rom is 5.6.11.
If you have unexcepted behaviours, try to install developer edition 5.6.11, before you install CM
Latest alpha builds:
From: @dh.harald
cm-12.1-20151015-UNOFFICIAL-ferrari.zip - 348.13 MB
Sensor patch:
patch-sensors.zip - 204.43 KB (only libsensorservice.so needs)
I'm currently testing this build as a daily driver
From: @smoki3
Sensors patch already applied:
cm-12.1-20150722-UNOFFICIAL-ferrari.zip
WORKING
2D acceleration
Touchscreen
HW/SW buttons
RIL/multisim
+ mobile data (big thanks for @smoki3 & @k2wl)
Wifi
Bluetooth
internal SD
MTP
vibrate
gps
camera ( @smoki3)
audio (with proprietary drivers)
fm radio @k2wl
notification lights (see limitations: http://forum.xda-developers.com/showpost.php?p=61954224&postcount=434)
ant +
+ you tell me
NOT WORKING
sensors (use this patch: http://d-h.st/S5m)
+ everything else...
CHANGELOG
+ doze (limited)
If you want buy us a beer, here are the donation links:
dh.harald
smoki3
k2wl

can you add a list of working/non working parts?

have you tried
AUDIO_FEATURE_LOW_LATENCY_PRIMARY := true
on boardconfig?

smoki3 said:
have you tried
AUDIO_FEATURE_LOW_LATENCY_PRIMARY := true
on boardconfig?
Click to expand...
Click to collapse
Nope
Please fork it, and if your modification is working, make a pull request
Maybe I'll try it in the evening... we will see
Thanks!

Wow.. You are the man.
Thank you so much
Sent from my Mi 4i using XDA Free mobile app

dh.harald said:
Nope
Please fork it, and if your modification is working, make a pull request
Maybe I'll try it in the evening... we will see
Thanks!
Click to expand...
Click to collapse
have forked already. building now

dh.harald said:
Nope
Please fork it, and if your modification is working, make a pull request
Maybe I'll try it in the evening... we will see
Thanks!
Click to expand...
Click to collapse
can you do the following:
1. install this app: https://play.google.com/store/apps/details?id=com.tortel.syslog&hl=de
2. reboot
3. start and stop camera app
3. run the app from 1. and upload the generated zip file here

vibration is working for me on your build. it only is weak

Thank you very much for your work dh.harald! Give this man some beer for his work

You didn't define msm8916 audio files in your device.mk like inhttps://github.com/CyanogenMod/android_device_cyanogen_msm8939-common/blob/cm-12.1/msm8939.mk

k2wl said:
You didn't define msm8916 audio files in your device.mk like inhttps://github.com/CyanogenMod/android_device_cyanogen_msm8939-common/blob/cm-12.1/msm8939.mk
Click to expand...
Click to collapse
You mean, like here?
https://github.com/dh-harald/android_device_xiaomi_ferrari/blob/cm-12.1/full_ferrari.mk#L52

Bitti09 said:
can you do the following:
1. install this app: https://play.google.com/store/apps/details?id=com.tortel.syslog&hl=de
2. reboot
3. start and stop camera app
3. run the app from 1. and upload the generated zip file here
Click to expand...
Click to collapse
camera is not built in until now

smoki3 said:
camera is not built in until now
Click to expand...
Click to collapse
can you upload a zip of the logfiles directly after booting the mi4i ?

dh.harald said:
You mean, like here?
https://github.com/dh-harald/android_device_xiaomi_ferrari/blob/cm-12.1/full_ferrari.mk#L52
Click to expand...
Click to collapse
yes those...but why you put them in full.mk insetad of device.mk
are those building during compilation...check that too..
you must be missing something in your blobs...
and if those are building fine then just put
/system/vendor/lib/hw/sound_trigger.primary.msm8916.so
/system/vendor/lib/libhwdaphal.so
/system/vendor/lib64/libhwdaphal.so
in your vendor tree.
these are vendor files and are not open source files...like
https://github.com/AICP/device_htc_...c21f098ea9e883e156/proprietary-files.txt#L182
https://github.com/AICP/device_htc_...c21f098ea9e883e156/proprietary-files.txt#L400
https://github.com/AICP/device_htc_...c21f098ea9e883e156/proprietary-files.txt#L715
build everything else as open source like audio.primary.msm8916

Bitti09 said:
can you upload a zip of the logfiles directly after booting the mi4i ?
Click to expand...
Click to collapse
Here

dh.harald said:
Here
Click to expand...
Click to collapse
add DATA is not working.
No mobile data and no LTE option

smoki3 said:
add DATA is not working.
No mobile data and no LTE option
Click to expand...
Click to collapse
Thanks... I try to check it, but my mobile provider is not too healthy nowadays... (and I have no LTE subscription)
That's pretty sure, that the following proprietary files are missing for mobile data:
bin/netmgrd
lib/libcnefeatureconfig.so
lib64/libcnefeatureconfig.so

dh.harald said:
Thanks... I try to check it, but my mobile provider is not too healthy nowadays... (and I have no LTE subscription)
Click to expand...
Click to collapse
there is no lte option in settings until now. only 2g 3g there. but not working
---------- Post added at 08:18 PM ---------- Previous post was at 07:58 PM ----------
dh.harald said:
Thanks... I try to check it, but my mobile provider is not too healthy nowadays... (and I have no LTE subscription)
That's pretty sure, that the following proprietary files are missing for mobile data:
bin/netmgrd
lib/libcnefeatureconfig.so
lib64/libcnefeatureconfig.so
Click to expand...
Click to collapse
Have you tried to add them? does it work?

smoki3 said:
there is no lte option in settings until now. only 2g 3g there. but not working
---------- Post added at 08:18 PM ---------- Previous post was at 07:58 PM ----------
Have you tried to add them? does it work?
Click to expand...
Click to collapse
Not for me Maybe it's Vectone, but unfortunately, maybe something more is missing

[ROM][UNOFFICIAL] LiquidRemix-8.1 (181104)

LiquidRemix-8.1-difrED for Xiaomi Redmi 3S/Prime/3X
Download:​
https://www.androidfilehost.com/?w=files&flid=247274
Sources:
https://github.com/LiquidRemix
https://github.com/difr
Special thanks to:
- @nichcream
- @HridayHS
- @nathanchance
- LiquidRemix Team
- LineageOS Team
- All developers
- and to all involved
XDA:DevDB Information
LiquidRemix-8.1-difrED, ROM for the Xiaomi Redmi 3S
Contributors
difr
ROM OS Version: 8.x Oreo
Version Information
Status: Nightly
Created 2018-09-24
Last Updated 2018-09-24

main builds feature is battery and performance tuning
use statusbar "Profile" tile to switch between (its "Spectrum" app, mostly rewrited and adapted)
base (kernel-vendor-device) is the same as in crDroidAndroid-8.1-difrED

Umm there's still no 24 sep build on the link you given(?) Or its the 21 sep one?

faatihf said:
Umm there's still no 24 sep build on the link you given(?) Or its the 21 sep one?
Click to expand...
Click to collapse
21 still. just want to move discussion in new thread

Thanks for this rom

Yayyyy..

ROM is smooth, stable and very battery efficient. one of the best oreo roms! loved your crdroid but this is better because there are many more customizations options. i hope you keep working on developing this. great work comrade!

I noticed that this ROM has no high volume problem during call, which is very good because most ROMs have same problem.:good:

krishna_jm said:
battery efficient
Click to expand...
Click to collapse
if you use gapps, i would recommend to install "Enable Doze for GMS Magisk Module" by otonieru
it will save some additional percents.

thank you very much!

Downloading speed is very slow and unreliable. Damn

Trilokpati said:
Downloading speed is very slow and unreliable. Damn
Click to expand...
Click to collapse
Use other mirrors or use any VPN app

After installing the ROM calendar and clock apps were not present. Is this normal? I flashed Pico as usual, rom was clean flashed. Tried many rom, this happened first time.

Trilokpati said:
After installing the ROM calendar and clock apps were not present. Is this normal? I flashed Pico as usual, rom was clean flashed. Tried many rom, this happened first time.
Click to expand...
Click to collapse
same here. just install the calendar and clock apps from play store or F-droid Calendar and Clock (if you want the opensource non google ones). Works fine.

Trilokpati said:
After installing the ROM calendar and clock apps were not present. Is this normal? I flashed Pico as usual, rom was clean flashed. Tried many rom, this happened first time.
Click to expand...
Click to collapse
yes, these apps are not there. was surprised also
will try to add some in next release (October)

Battery Performance
Here is battery Performance, though I don't use many battery hungry app still result is very good. Battery was fully charged since uses, 10H+ SOT

The Gps sometimes stops working.. I have to restart the device and switch on and off the gps several time to get it work. Please fix that

foreverlaxmikanta said:
The Gps sometimes stops working.. I have to restart the device and switch on and off the gps several time to get it work. Please fix that
Click to expand...
Click to collapse
need confirmation from other users. you are along with such report. this part (gps) is not changed since spring.
you can try to install magisk module "Global Optimized GPS File Replacer". write back

GPS working fine for me.
ROM is perfect , no bugs encountered till now
Battery backup is looking too good for light users

difr said:
need confirmation from other users. you are along with such report. this part (gps) is not changed since spring.
you can try to install magisk module "Global Optimized GPS File Replacer". write back
Click to expand...
Click to collapse
Yes boss