AOSP 5.0.2 D2303 Work in Progress

AOSP 5.0.2 D2303 Work in Progress - Sony Xperia M2

AOSP 5.0.2 Barebones for D2303
Hi all.
This is my first run of compiling a barebones AOSP 5.0.2 for our D2303's. I got sick of all the failed ports and wanted to make my own from scratch. Here you have my first launch. You can not get as barebones as this. This ROM was made using the guides on Sony Developer website and should be the same result if anybody else follows the same steps.
I have made ZERO modifications to this ROM. I have changed no code, made no patches or even themed it with a custom name. This ROM is as-is if you built it following the same guides on Sony's site. I just saved you the time.
**This ROM works!**
Data / Calls / SMS / NFC / Bluetooth / GPS/GloNAS / Wifi all work!
Camera does not. It might, but I broke mine and doesn't even work after stock restore!
No lag!
Clean, basic, no-frills, xPosed ready!
Unlock your bootloader!
Be running either a modem from a 4.4.2 ROM or a 4.3 ROM!
This ROM is provided as-is. The sources are freely availble following Sony's guides. You use it purely at you own risk!
Let's clear some confusion with this device, which I am shocked top developers have missed!
* You **have* to be running either 4.3 or 4.4.2 MODEM! If you are running a 4.4.4 ROM, use Flashtool to drop back to 4.4.2 or 4.3 first
* You will not be able to boot ANY 5.x ROM with a 4.4.4 modem, it **HAS** to be 4.4.2 or 4.3 MODEM!
There are guides on how to revert back on this forum and I will not detail that here. But in essence, it is only the modem you need to revert back.
This ROM I would say is usable.
* Camera doesn't work on mine, but I broke it to the point it wont work in stock ROM
* Calls / SMS / Data / Wifi / GPS / NFC / Bluetooth all appear to work as they should
* Sensors appear to all be working as they should (at least compass and light)
* No lag or FCs
This is a totally unmodified ROM using the AOSP & Sony sources provided in Sony guides. I did not develop or make any of the code or scripts. I simply compiled it, flashed it and now using it. All credit to the software that made this ROM goes to all those involved in making, patching and taking the time to make this work.
I do not want any donations. If you wish to donate, donate to FXP/CM12/Omni/PAC/TWRP and the persons that created what I have simply bundled here.
Download via magnet/bittorrent only for now. For trackers, please use OBT trackers. Issue with previous download! I somehow crossed an .img from another project as the boot.img for this. I have recitified this issue and the correct boot.img has been added. Apologies for this & thankyou to all whom spotted it.
Magnet Link
magnet:?xt=urn:btih:44d710f71b92adb9e64475994b5ab905d665af7d&dn=AOSP-5.0.2-D2303.tgz&tr=udp%3A%2F%2Fopen.demonii.com%3A1337
Mega Link
https://mega.co.nz/#!HZUUCCJS!AgjmKr4Nx4NMWPKxVXIGfp72m9JyMMlsF0pvzuGBrg8
Sorry for the bad link effort, since I am new to contributions I'm stuck until I make the relevant posts.
I have no idea if this will work on any of the variants of this device. You are welcome to try, but don't blame me if you break it. This ROM comes as is, is provided under the same licenses as AOSP and Sony Development.
Tricks & Tips:
* Download the .zip for Omni ROM 4.4.4 for our D2303's. Extract the boot.img and keep it safe. This boot.img holds a reliable TWRP which we can use to ''fastboot boot'' instead of flash and even make a reliable backup of a stock ROM. When you put device into fastboot/bootloader (hold power up when plug in data ready cable), execute ''fastboot boot boot.img'' which will boot that kernel w/o modifiying anything. Now keep hitting volume down when you see Sony logo. TWRP should load!
* Use this for all your backing up, flashing zips, ROMs etc. Do NOT flash it. Just fastboot boot it instead. This can even be used AFTER we install Lollipop for the same reasons.
* Flashing this ROM requires you to use the above TWRP to wipe all partitions, System, Data, Cache etc. It's best to start afresh (I actually wiped everything except since I wanted a totally clean slate, wiping external storage isn't necessary but wiping internal is recommended.)
* Extract the tarball with the .img files
* Put the device into fastboot mode again!
* execute the following commands:
* fastboot flash boot boot.img
* fastboot flash system system.img
* fastboot flash userdata userdata.img
Make sure all processes complete successfully!
Unplug cable, wait a second or two and power up your device! (I prefer this to fastboot reboot as the data cable can hang the device in a weird, red led stays on mode that has bootlooped me a few times).
Give it a while to boot. Whalla, Lollipop!
If you want gapps, using the fastboot boot method above with our Omni 4.4.4 boot.img and TWRP.. Download CM's gapps for Lollipop and flash/install it. This does not lag the device. However, you will get a black screen for a while after first boot of installing any system/ZIP flashable (it wont show updating apps, just blank screen). BE PATIENT! The same applies if you do anything that triggers that "Updating App X of X.." Android is updating effort.
xPosed requires you to follow the instructions for flashing the ZIP then installing APK. Use the same method above for installing the ZIP.
To get root, just download the latest SuperSU-2.x.zip and flash the same way as above.
**Issues**
* With a 4.3 Modem, the Bluetooth is slow coming to life. Take about 5 mins when turned on from off. 4.4.2 modem doesn't seem to have this issue
* Location services will forget a change to Accurate on a 4.3 Modem. On 4.4.2 Modem doesn't seem to do this.
* My loudspeaker during calls is tempremental, sometimes it works sometimes it doesn't.
* Some OTG devices work, some dont. I had one or two pendrives that did, some that didn't & a 3G modem (with PPP widget's help) that did & another that didn't!
* Screencasting initially didn't work. Enabling Developer Mode and disable HDCP checks seemed to allow some functionality for me.
* Data icon always said 3G for me, even when on HSPA(+) - I use OSM which showed varying network types. GPRS/EDGE shows as 2G. I do not know for 4G as my carrier isn't 4G enabled yet.
* No hardware accelleration (using VLC & MX Player as guides) for video playback, however it can playback a 1080 MKV over wifi no problem.
* Same applies to screen-recording software. I can't seem to get native Lollipop one to work at all, but SCR Free works.
* 3D Performance is a little smoother than in stock ROM (IMPO playing Ingress).
* GravityBox for Lollipop works. However!! On some instances it can cause a softboot on a boot up (when it goes for PIN entry). For me it comes back after they next cycle. Not pinned it down to what in GB doing it though.
* Compass, proximity & light sensors all work. There is some screen flicker once so often when using dynamic brightness.
* No way to force use of 5Ghz or 2.4Ghz wifi (or leave it to select auto) as there is in stock ROM.
* Battery life when using the device as I do is as the same as stock, the device is however faster in general. I can sit it for 29 hours idling, providing not too many calls. The powersaving modes built-in can extend on this but I haven't properly tested.
I only mention these as some people may care to know. If the camera worked, I would actually be totally happy with this ROM minus it's few pitfalls.
MD5's for the paranoid:
2c053445ab096e813afc2a02079aba85 boot.img
af636c1558e8d6651f211dbd2042443f system.img
adbb0b8d0b5eee98186a71a00d8352a4 userdata.img

Good job, please, compile an AOSP 4.4.4
Sent from my D2303 using XDA Free mobile app

What if I told you I did the same as you and it is EXACTLY the same build you can find on FXP's blog (but files are not straight uploaded, so build can be a little bit outdated). Developers around here are working on sources, and changes are on Xperia Developers Github.
As you can see there are things jerpelea (FXP) has pushed.
https://github.com/sonyxperiadev/device-sony-eagle
Only untouched sources are for Nexus, all other devices need to be patched, and sometimes rewritten from scratch (for example camera wrapper).

If I install this rom, and when I back to stock rom, i won't be able to use camera?
Is that right?

Um ok but why there is no seeding?;/ and why dont u give an alternative link?? haw we supposed to try this rom mate?
who can confirm if camera works or not ?

Update
I will work on a 4.4.4 AOSP eventually. Thanks for the tip, I'd also be curious on this.
I do not doubt that developers that are working on Omni/PAC/CM/FXP have submitted code, that's probably why the barebones is working sweet. I did try FXP but ran into different issues on different versions (all already documented). I built this on a whim as I just got fed up.
With the camera, that is exactly how I killed mine, and I also lost the original backup I made with Flashtool/Companion as well as from TWRP. So I have no hope. If you keep/make a backup upon successful bootloader unlock (companion/flashtool), you should be OK if you do a stock revert that is documented on this forum.
For the download link, sorry about this. I used transmission and it went into meltdown last night from another seed. I believe mega is a method people use here, is there any other suggestions. I will do this when I get back home and check back here.
** I am uploading this to Mega now, I will add the download link to the OP. **

Thank you for uploading this rom Dutch.
I ll test this rom, correct it where i can and send you pm as soon as possible with some fixes plus solution about your camera
cross your fingers to not break mine lol
Best regards
Vampirian

Thanks
If you do make some patches, can you please put them as flashable ZIPs? I really don't want to go and start tampering with a somewhat stable base. I bless whoever made that boot.img for the Omni 4.4.4 - I would like to try and get that working here, but again tampering.. Just means needing a PC or tablet to make mods to your phone each time.
I may have a bash at a custom kernel with a recovery for this, but I'm not rushing into that idea just yet.
** Update **
I got curious about the FOTA partition I saw using Flashtool and see there are already ports of custom recoveries (with custom boot kernels with elf extract support). I am overly curious about this now as I would love to have this TWRP from Omni's boot.img for my internal recovery. I have already made a custom kernel for my device and it seems to not effect anything (not changed a thing mind). I may now start to tinker!!

Has anybody tested this rom?
---------- Post added at 03:37 PM ---------- Previous post was at 02:53 PM ----------
I have the problem with boot.img
It says, failed: this is not a boot image

Bug list same as the omni one

Can You explain that boot.img is over 400MB Large!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Which download did you use? That is so not right!! boot. img should only be about 6/7 mb. are the md5s matching on system and userdata? i will look into this asap
Sent from my Xperia M2 (AOSP) using XDA Free mobile app

The mega download is shot. It has become corrupted and I will remove the link from the OP. DO NOT USE IT!
The magnet link is still fine and extracts properly.. Just be patient as there are only 3 peers at present.
I am still using this ROM and there are some issues.
I failed to get Wifi tethering to actually route. It would run, give dhcp and even resolve DNS, but it is as-if the the nat forwarding rule has been missed and everything blackholes.
Camera is a total no go for me, I fooked mine in other ways though.
For how I use my phone (calls/sms/Ingress/HO/G+/Whatsapp/Maps/Wifi location mapping (OSM/Mozilla stumbler/Wigle) / Skymaps) it does just fine. Battery life isnt impressive vs. stock overall (doing same as above). xPosed allows tweaking, but this is where instability occurs.
GB works quite well, but avoid things that dont have direct L support (xPrivacy/Lightningwall etc.).
What I want to do is submit my phone into submission and try to get my camera working in a stock again, then give this another bash. It is a usable ROM if you just want a clean fast phone with no thrills (or camera).
Sent from my Xperia M2 (AOSP) using XDA Free mobile app

Magnet link not working
The magnet link you posted doesn't seem to work for me. I get "unable to parse magnet URI!" error

There is a space in the magnet part of the URI when you C&P. The forum did this. I should be able to post proper links soon.
Sent from my Xperia M2 (AOSP) using XDA Free mobile app

Nice for giving so much info on AOSP experiences and "prerequisites" (like 4.4.2).
I'm using a AOSP 5.1 build I made myself, and have to say the only issue with the latest build/kernel is battery drain (and camera, but "they" are working on it).
I Hope nobody will call you a troll because you share your builds and experiences with everybody

I got a massive lag when using browser or while using a few apps at once, also installing apps and turning on bluetooth take alot more time.
The things I do like is that it is pretty stable....

Thanks to all that have and are testing.
The tether issue was my tablets fault and does actually work. As does BT tethering.
All of the sensors work (i went out of my way to try each one (magnet sensors are always fun)).
The slow Bluetooth I found only happens when using a 4.3 modem. I dont get it now using a 4.4.2 modem.
There is no call record ability in this ROM. CM11/12 have enabled this feature, I believe its a small. xml patch, can anyone confirm please?
I do experience slowness with lots of open apps, i also notice if you have a lot in frequents its a pain to clear all (fixed with gravitybox mind). They also seem to come back even after a reboot. I do find myself regularly clearing the frequents which does sort it.
And thanks for the tips. I find trolls arent entirely too common here. Ive been reading from XDA for years and my sole idea was to demonstrate that its is doable and quite easy. I am still using this ROM everyday and Im quite happy with it. I do still prefer Kitkat though
I do want to play with 5.1.x (and nicer the camera works) - but i went 5.0.2 simply because of xposed support. Nothing else
There is a battery drain which I noticed "out-of-the-box" so to speak. This happens when there are issues with "qdoverlay" which i noticed sometimes occurs on bootup, then will savage your cpu. I spotted this in logcat and didnt find a direct fix (other than sleep the screen when the phone starts lagging, wait a second or two then wake it back up. Location type also counts, oddly high precision seems to give me more life. However, there is an "Over-Counted" cropping up in battery stats, which I cant pin is for what, as its usually a high figure at the bottom.
Can anyone confirm a working camera on this ROM? Opencamera or Googles should work if one doesnt show up.
Thanks again everyone
Sent from my Xperia M2 (AOSP) using XDA Free mobile app

Dutch Burdock said:
Thanks to all that have and are testing.
The tether issue was my tablets fault and does actually work. As does BT tethering.
All of the sensors work (i went out of my way to try each one (magnet sensors are always fun)).
The slow Bluetooth I found only happens when using a 4.3 modem. I dont get it now using a 4.4.2 modem.
There is no call record ability in this ROM. CM11/12 have enabled this feature, I believe its a small. xml patch, can anyone confirm please?
I do experience slowness with lots of open apps, i also notice if you have a lot in frequents its a pain to clear all (fixed with gravitybox mind). They also seem to come back even after a reboot. I do find myself regularly clearing the frequents which does sort it.
And thanks for the tips. I find trolls arent entirely too common here. Ive been reading from XDA for years and my sole idea was to demonstrate that its is doable and quite easy. I am still using this ROM everyday and Im quite happy with it. I do still prefer Kitkat though
I do want to play with 5.1.x (and nicer the camera works) - but i went 5.0.2 simply because of xposed support. Nothing else
There is a battery drain which I noticed "out-of-the-box" so to speak. This happens when there are issues with "qdoverlay" which i noticed sometimes occurs on bootup, then will savage your cpu. I spotted this in logcat and didnt find a direct fix (other than sleep the screen when the phone starts lagging, wait a second or two then wake it back up. Location type also counts, oddly high precision seems to give me more life. However, there is an "Over-Counted" cropping up in battery stats, which I cant pin is for what, as its usually a high figure at the bottom.
Can anyone confirm a working camera on this ROM? Opencamera or Googles should work if one doesnt show up.
Thanks again everyone
Sent from my Xperia M2 (AOSP) using XDA Free mobile app
Click to expand...
Click to collapse
Camera is not working

Dang. Thank you.
Sent from my Xperia M2 (AOSP) using XDA Free mobile app

Related

[FIX] Wake Issue (Android OS) - Combination of Radio/PRI/NV/Wimax/GPS !Solved!

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thread has shed some light on new issues and some other fantastic developers have chimed in with a lot more insight into this issue than I had originally anticipated when I started this thread. Please read the below post in FULL, and skip to page 31 for where this discussion picks up. ~> http://forum.xda-developers.com/showthread.php?t=1128135&page=31
DaKlown said:
First I would like the thank the OP for bringing some attention to the issue. This thread seems to have started going in the wrong direction so I will make an attempt to clear some things up and shed some light on the situation with my findings. In my tests so far I cannot really find a combination of radios and pri to solve any of the problems mentioned in this thread. All my findings are using and testing aosp roms. Cm7 really but most aosp roms are based off of cm so this post should be helpful if you use an aosp rom and are having a unreleased pokelock caused by the dialer and/or high android system in the battery usage after phone calls. If you use a sense rom I do not recommend any of these fixes for you. If you use these on a sense rom you will probably mess something up and/or experience boot loops and lots of other problems. That being said lets get started:
Problem 1: The pokelock not being released after a phone call is made or received. This problem comes from the phone app and not the radios as far as I can tell from my tests.
Solution: http://www.mediafire.com/?xzw0zhonmnjw1xs
This file is a flashable zip of a new phone app that releases the wakelock after making a phone call the way its supposed to. I take no credit for this new phone app. It was made by Scott Brady (The same dev that fixed the mms problems on the evo in the cm nightlies about a month ago). I just got this from him. We haven't thoroughly tested it yet so please FLASH AT YOUR OWN RISK. Make a nandroid. I will say this though. In my current tests I have made about 40 calls with no pokelock and it seems to work wonderfully. The only reason I'm posting it early is because if you're like me and you know something is wrong then you want an immediate fix. Also using the killall command in terminal emulator or adb after every call can get tiresome... I have also tested with multiple radios In case anyone was wondering.
Problem 2: Android system spikes in the battery use in settings after a phone call is made or received.
Solution: I'm close but not finished yet...
Please read what I am about to say all the way through. What I have found is that the current proximity drivers for the evo are causing the android system in the battery use to go bonkers. I'm not really sure how much it affects your battery because it seems that it causes all your apps to not even show up in your battery stats. Proof? I have supplied two files in a zip:
http://www.mediafire.com/?mxks9k60shlckk5
THIS IS NOT A FLASHABLE ZIP. USE AT YOUR OWN RISK. One file is "sensors.supersonic.so" where I edited it so that android cannot find the drivers for your proximity sensor so it never comes on. The second file is "sensors.supersonic.so.bak" which is a backup of the original .so file that you can use if you want to turn your proximity back on. When I edited my sensors.supersonic.so file so the proximity wouldn't come on android system no longer spiked in my battery stats after a phone call!!! Also I tried to add a command to the build.prop first to disable the proximity sensor which would have been better practice but the command didn't work. Not sure if that's because cm overrides it or what. I can pretty much guarantee that this is an aosp problem and not a sense problem so if you use a sense rom you don't even need to worry about this. I doubt HTC has faulty proximity drivers on a stock rom... I could be wrong but I doubt it, they have screwed up in the past...
So what now? Well if you're on an aosp rom and the current proximity drivers work for you then you know what they say, "If it ain't broke don't try to fix it." For the rest of us I am in the process of trying to find some proximity drivers that don't make battery stats go haywire. Lets try to keep the thread relevant to findings so that we as a community can come closer to a fix instead of all the repetitive questions and things that don't help us get closer to a true fix... Don't forget the thanks button if you found this useful =P
Thanks for your time.
Edit: I would also like to add that I am on the most current radios, nv, and pri with no wakelock or spike in my android stats. And If you flashed the combo from the Calkulin thread you are probably missing the newest NV file because its not in there.
Click to expand...
Click to collapse
I have left the previous OP in-tact so if you would like to follow from the beginning you may. At this time, I can no longer recommend the below steps!!!, but I can still let you know that the GPS driver files below are pretty damned awesome.
~J
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
I believe I have FINALLY figured out how to solve the infamous "Wake-Lock" or "Keep Awake" of Android OS that seems to drain the battery on end. It took several hours of reading forum posts, several DAYS of testing on 5 different EVO's (I work at Sprint) and have tested the fix across a multitude of ROM's, including Sense.
I will post a short history of the issue as I know it here for those of you hitting this thread for the first time, skip below for the solution I have found.
Requirements:
-Radio S-OFF
-AmonRA Custom Recovery
-Android System always at or near the top in your battery usage
History
To the best of my knowledge the issue first started to appear in AOSP ROMS when the Cyanogen team stopped using HTC Blobs to control the driver for the GPS, As a great many custom roms utilize cyanogen for many of their own enhancements and fixes the problem began to propagate out to the community at an alarming rate. Restoring your system back was a hit or miss on if it actually solved the issue or not, and more RADIO files were getting leaked/posted online and many people were flashing a multitude of firmwares to their handset making the issue confusing and seemingly with no correlation on handsets with the people having issues.
I came across ViRuS Kingdom ROM and read about 1000 pages of posts and the conclusion from their team was that the PRI needed to be downgraded to 1.77 and behold, it worked......(mostly)......
I wondered how the PRI had anything to do with the fix, and mixed that with many, many other forums I have read on the issue realized myself that there was a correlative cause and that we all did indeed have something in common. Everyone was on a different radio/pri/nv/wimax combination. I decided to run some tests myself as I have access to ****loads of handsets being a Sprint employee and here is what I have found.
I have found exactly 1 combination that has fixed the issue on every single handset I have tried it on, hands down across the board on a great cross-section of ROMS.
-Cyanogen
-Kingdom
-MIUI
-SavagedZen
-Synergy
-Mik's
-Sense 3.7 build
-Sense 4.22 build
-FreshEVO 3.5
-FreshEVO 4.1
______________________________________________________________
THE FIX!
The fix is a combination of...
Radio: 2.15.00.05.02
PRI: 1.77_003
NV: 1.90_003
WiMAX: 27243
GPS: HTC VISION GPS ".so" file
-Download the below PC36IMG.zip It is a custom Combo Radio installation I created that will set your Radio/Pri/NV/WiMAX to the above settings
-Move the PC36IMG.zip file to the root of your SD-Card and reboot the phone into bootloader. It will load the file and prompt you for an update, you will see on the left 3 items that will be upgraded on your handset. Hit volume up to accept
-Reboot the phone after the Radio update, go ahead and remove the PC36IMG.zip file from the sd-card and put it in a safe place
-Download "GPS_FIX_Flashable_Vision.zip" and put on your SD-Card
-Reboot into Recovery (I highly recommend AmonRA 2.3)
-Wipe Cache & Dalvik Cache. Now wipe them again just to be safe
-Choose "Install zip file from SDCard"
-Navigate to GPS_FIX_Flashable_Vision.zip and choose install
-Once installed go down to "Other" and "Fix UID mismatches"
-Reboot the phone
______________________________________________________________
Now heres the weird and tricky part so listen closely. At this time you will still see the Android System in your battery stats. This is normal. To see the fix, you need to charge your phone fully to 100%.... and honestly give it an extra 10-15m on the charger after it says its full. Now..... REBOOT the phone when you pull it off the charger. Use the phone a little bit, make a phone call... it may still pop up around 5%.... again this is normal..... after 2-3 hours however it will be gone, completely and utterly gone... it will never show up again.
I have tested this on 5 handsets hardware revision 0002 0003 & 0004, and about 6-7 ROMS both AOSP & Sense and have yet to see Android OS re-appear. This is not to say that it will work for everyone, but I think that after my testing, there's an excellent chance that this will work for you.
Please leave feedback if this works or does not work for you please so that everyone can benefit from your experience, either good or bad. Please, please please, follow the final instructions carefully, it does literally take a few hours to test and get the old stat to wipe from the battery history, that is why I started this, literally 2 weeks ago, and am just posting now. I tried TONS of combination's and this is the one that struck gold, then I needed to test this combination on all of the phones I had sitting in the back for this. If mirrors are needed please let me know, and I will upload.
Good Luck!
PC36IMG.zip
Radio: 2.15.00.05.02
PRI: 1.77_003
NV: 1.90_003
WiMAX: 27243
http://www.multiupload.com/HJOWHOLW4G
Qualcomm Vision GPS Driver
Sense GPS Driver File from Qualcomm Vision
http://www.multiupload.com/11IWQ99VKH
EDIT:
A few reports on certain ROMS of excessive CPU usage after Android OS has dropped off the list
Please use one of the two below GPS drivers if you experience 100% CPU usage (Source: http://forum.xda-developers.com/showthread.php?t=1132412 )
~>AOSP<~
CyanogenMOD 7 Nightly 39 GPS Driver (HTC Blob File Compiled)
http://www.multiupload.com/NIJEKWGDEQ
~>SENSE<~
KingdomROM GPS Driver FIX
Sense GPS Driver File from EVO 3D aka "Kingdom"
http://www.multiupload.com/ZMOXSDJBOE
EDIT: It has come to my attention from a few members in PM, that the issue doesn't always "take" right away. People have reported that it can take 2 or 3 attempts, and 9 different people have reported that they have run the 1.77_003 NV after flashing the radio, and then running the GPS to resolve the issue.
---------------If the above fails for you after a 2nd attempt. Please follow these Modified Instructions
-Download the below PC36IMG.zip It is a custom Combo Radio installation I created that will set your Radio/Pri/NV/WiMAX to the above settings
-Move the PC36IMG.zip file to the root of your SD-Card and reboot the phone into bootloader. It will load the file and prompt you for an update, you will see on the left 3 items that will be upgraded on your handset. Hit volume up to accept
-Reboot the phone after the Radio update, go ahead and remove the PC36IMG.zip file from the sd-card and put it in a safe place
-Download "GPS_FIX_Flashable_Vision.zip" and put on your SD-Card
--MODIFIED STEP-- Download "EVO_NV_1.77_003" ~> http://www.mediafire.com/file/i1p436188iw0iqb/EVO_NV_1.77_003.zip (source: http://forum.xda-developers.com/showthread.php?t=715485) & put the file on your SD-Card
-Reboot into Recovery (I highly recommend AmonRA 2.3)
-Wipe Cache & Dalvik Cache. Now wipe them again just to be safe
-Choose "Install zip file from SDCard"
--MODIFIED STEP-- Navigate to EVO_NV_1.77_003.zip and choose install, once installed you will see a note at the bottom to reboot the phone. Choose the "Reboot Phone" option in AmonRA and let the phone reboot
-You will see the screen blink, go into recovery and hang, this is completely normal, just wait about 30 seconds and the phone will Automatically put you back into your recovery
-Choose option Flash zip file from SD-Card
-Navigate to GPS_FIX_Flashable_Vision.zip and choose install
-Once installed go down to "Other" and "Fix UID mismatches"
-Reboot the phone
Pickup the rest of the steps from above. PLEASE REPORT back your experience!
++++++++++++++++++++++++++++

wow sounds like it could work but im too busy with work...hopefully this thread will get more people to try this fix and see if it works for them....my fingers are definitely crossed!

thanks for this.. i will try it out.. i currently allready have the 1.77 on my phone.. dont know bout the radios.. last time i tried to flash radios i had net closing issues..

dgrobe2112 said:
thanks for this.. i will try it out.. i currently allready have the 1.77 on my phone.. dont know bout the radios.. last time i tried to flash radios i had net closing issues..
Click to expand...
Click to collapse
I have had issues like this as well, but only when I do the radio's through the recovery partition. That is why I enclosed it as a PC36IMG.zip file so that it could be done by the "official" HTC update method. I have had no issues doing it this way. Good luck, looking forward to hearing that your issue is resolved.

Fails to install Can't find update script... any ideas??
CM7.0.3.1

JBabey said:
I have had issues like this as well, but only when I do the radio's through the recovery partition. That is why I enclosed it as a PC36IMG.zip file so that it could be done by the "official" HTC update method. I have had no issues doing it this way. Good luck, looking forward to hearing that your issue is resolved.
Click to expand...
Click to collapse
i dont have to reflash my rom do i?

downloading now, should i clear battery stats?

glennpettit said:
Fails to install Can't find update script... any ideas??
CM7.0.3.1
Click to expand...
Click to collapse
Use AmonRA, the update script is not in EDIFY (I may have to fix that later)
downloading now, should i clear battery stats?
Click to expand...
Click to collapse
You shouldn't need to. If you are clearing your battery stats, do that for the reasons its intended, and make sure you follow the top off/drain instructions when doing so or it could lead to false readings.
i dont have to reflash my rom do i?
Click to expand...
Click to collapse
No, you are only updating your radio and thus will not lose your data or have to reflash your ROM. Please remember to follow the short instructions at the end for charging/reboot/2 hours before reporting back here please.

flash the virus gps fix even if your not on the kingdom rom ?

I am using RA.

might give this a shot later, don't have high android OS, but might be interesting none the less

glennpettit said:
I am using RA.
Click to expand...
Click to collapse
I re-uploaded the zip file, please redownload and lemme know if this one works for you.
Thanks!
might give this a shot later, don't have high android OS, but might be interesting none the less
Click to expand...
Click to collapse
If it aint broke..... lol (granted this will put you on the latest radio)
And.. I have found my GPS locks to be instantaneous on this driver.
flash the virus gps fix even if your not on the kingdom rom ?
Click to expand...
Click to collapse
I personally use CyanogenMOD Nightly 100 at the moment and it works like gangbusters on this ROM.

CheesyNutz said:
flash the virus gps fix even if your not on the kingdom rom ?
Click to expand...
Click to collapse
I used the GPS drivers provided by Vaelpak...and it worked! I'm using Salvage-Mod v1.2.1 GB 2.3.3 and my GPS pickup is now instant!
And to the OP, I haven't had this issue...but great work!!!

What is acceptable for Android System usage? I'm at 23% right now and it's third on my list behind Cell Standby and Phone Idle. Is 23% high? I know I've seen it higher before. I am interested to hear more feedback on this fix.

I assume when flashing a new nightly, I would need to reflash the GPS driver again?

That's not even the problem for me, I'm on hardware 4 and with any of the 2.3.3 Roms the highest thing draining my battery is the display any ideas on how to reduce that. It's between 50%-right now at 86%. I have turned off auto display and notifications. Thanks in advance for any help.
Sent from my PC36100 using XDA Premium App

I had major issues with bat life and wake (android system) after flashing calkulins radiosfrom the ota 4.2.2 release. I downgraded radios to
Baseband 11.19
Pri 1.77
NV 1.77
Wimax 27167
Still have issues though. Is it safe to flash radios that many times. I have heard it can scree stuff up so should I flash your combo. Also my GPS works fine using cm 7.0.3.1 do I stool need to flash your GPS fix.
Cm 7.0.3.1
Sz 2.1.0 Cfs havs sbc
V0003

I did this for the hell of it even though I wasn't having too many issues on Virus revo 1.3 however this fixed my intermittent wifi issue and seems to have improved my battery too. Thanks a lot

Flashing it now while I'm at work (its slow today)

i am finished with the install of the zips, and rebooting now.. you said 2 hours.. i will post back my findings.. to let you know what is going on..
also.. as others have mentioned.. i havent been having any issues with the kingdom revo 1.3 rom.. other than battery drainage.. i dont have wake issues.. but wanted to see if this fixes anything.. will give updates..

[ROM][HYBRID][Jellybean] PARANOIDANDROID v1.991 - Non-kexec only!

no
20120819v1.991
Maintenance update, bugfixes and patches.
20120810v1.9.8alpha
Project butter recents in tabUI (2/2)
Quick access hybrid properties by longpressing a recent app
More refined hybrid algorithm to reveal more layout containers
TabletUI toggles
All recent cm merges (Trebuchet, googles 4.1.1 r4 with a whole bunch of fixes for memory leaks, etc)
20120806v1.9.7alpha
New option: "large" to trick an app thinking the device has a real big screen. some need it, like amazon kindle to jump into tabUI. some even react on it, gdrive will slightly adapt its layout - makes only sense if you give it a small dpi though.
The algorithm to extract the actual layout containers from apk files works more precise and can reveal more than before. there will still be a few apps left who do that layout stuff in java - we will add an override button for that, but in the meantime you can edit /system/etc/paranoid/properties.conf .layout=360 for phone-like UI, 600 for phablet, 720 = tablet, 1280 = super huge tablet
Several bugfixes from us and cm
CDMA SIM
20120723v1.9.5a - On Page 23
Finally hardware accelerated recents in TabUI, as fluid as ever. The ugly gradient is gone aswell
A clean backup properties file is shipped, you can make a full reset in the panel in case you lost it with all the settings you made
Force option can be activated in the panel, good for widget scaling
The DPI sliders in the panel read min/max props from properties.conf, define them as you like
TabUI Recents are back to a bigger size, this is temporary, i'll look for ways to port the phone implementation as project butter skipped the tabUI code
Cyanogenmod fixes
New GApps
20120723v1.9a / 1.9.1a - My edits are in RED
Newest CM10 patches (powertoggles for phoneUI, lockscreen options, etc,)
Definable number of notifications for navbar shaping
Hide clock wont cut it out of the notification center aswell
Lockscreen tutorial overlap *should* be fixed
Notificationcenter in TabUI has a draghandle like phablet and phone have
New GApps
Camera (very rough fix)
Panorama
Video Recording
Video Playback
YouTube (very rough fix) - I suggest starting out in landscape mode
Phone number

Do I flash this using ODIN?
No. Use the custom recovery that's linked.
I still don't know how to install the ROM
Download the ROM, GApps, and recovery.img from the OP
Download and open the EZ recovery app from HERE
Select custom, then select the box with 3 dots... find the d2vzw_recovery.img you downloaded in step 1 part B., select flash, then Reboot Recovery
From CWM recovery, Perform a nandroid backup from the backup/restore menu
Wipe data/factory reset
Select install .zip from sd and install the rom you downloaded in step 1 part A.
Select install .zip from sd and install the gapps package you downloaded in step 1 part B.
Reboot
Thanks droidstyle
I'm in a bootloop. Help!
This is normal for now. The phone will reboot multiple times, but will get to the bootanimation and eventually boot up. Do not freak out.
Something went wrong! Can you help me?
I'd love to help you, but I need a little more information about your issue. You should provide us with information regarding what your issue causes and what you did before the issue started. However, before asking me and the community, ask yourself two simple questions:
Can I reproduce the error?
Have I looked for a solution?
If you answered "yes" to both of these questions and came up empty handed, then post it in the thread and it will be addressed. Even more helpful would be if you got a logcat. Like so:
Code:
adb logcat > logcat.txt
OR (the better way so we dont have to keep downloading logs)
Code:
adb logcat
Paste the terminal output here (you don't need to register): http://pastebin.com/
Click "submit"
Share your link/logcat
When I use the camera the phone freezes and I have to do a battery pull...I thought it was fixed? (1.9.1a)
It is fixed. It's just a pretty hacky fix. To take a picture, you will have to tap the screen to focus the camera BEFORE taking the picture. If you just press the camera button, the phone will freeze.
Can you add *this* to the ROM?
Although I'm not obligated to add anything and everything to the ROM, I will do our best to supply your desires and live up to your expectations. Do not mistake this for a guarantee. I would like to do everything, but I may not be able to.
I'm experiencing some force closes, what gives?
Boot into recovery and fix permissions. Reboot.
Where can I go for information about the latest updates?
You can follow me on Twitter

Omgz, on-screen buttons! Can't wait to ditch this physical home key.

This Rom looks Awesome!!! Thank you for all the hard work. I am a noob when it comes to ADB , does anyone have a video that shows how to install this recovery and rom. Thanks in advance.

drbveb88 said:
This Rom looks Awesome!!! Thank you for all the hard work. I am a noob when it comes to ADB , does anyone have a video that shows how to install this recovery and rom. Thanks in advance.
Click to expand...
Click to collapse
Hopefully you already have adb installed (I'm assuming you do). You are going to want to download the recovery.img beanstown106/Team Epic has provided us with and then move it into the directory where you have adb installed (usually in "platform-tools" or "tools" in the android-sdk). Then cd to that directory using terminal or cmd (depending on your OS).
It should look something like:
Code:
cd .../Desktop/android-sdk/platform-tools
Once you do that, then enter each of the above commands (in the OP) in descending order. When it finishes, you're done.
:highfive:

Im guessing we will have the same issues we are having with cm9/cm10? like camera and possible imei disappearing?

drbveb88 said:
This Rom looks Awesome!!! Thank you for all the hard work. I am a noob when it comes to ADB , does anyone have a video that shows how to install this recovery and rom. Thanks in advance.
Click to expand...
Click to collapse
Use section 5 of my guide in sig...just replace links with this rom and gapps.
PureMotive, thanks alot for this! If you like copy my section 5 instructions to your op...it uses mmmeff's EZ recovery app to install recovery. I believe this will keep the "how do i install this" questions at bay since most dont understand adb. Thanks again for your work!!

suzook said:
Im guessing we will have the same issues we are having with cm9/cm10? like camera and possible imei disappearing?
Click to expand...
Click to collapse
Normal camera doesn't work, but panorama and the video recorder do.
droidstyle said:
Use section 5 of my guide in sig...just replace links with this rom and gapps.
PureMotive, thanks alot for this! If you like copy my section 5 instructions to your op...it uses mmmeff's EZ recovery app to install recovery. I believe this will keep the "how do i install this" questions at bay since most dont understand adb. Thanks again for your work!!
Click to expand...
Click to collapse
Will do

looks ok, noticed that ex-sdcard doesnt show and data keeps cutting out..other than that looks pretty cool

I am so excited to see this here! Thanks for developing.
For more exposure, shouldn't this be in the original android development section? Just a suggestion.
Sent from my SCH-I535 using Tapatalk 2

Holy crap, this looks AMAZING! Thanks for what looks like amazing work on this. Downloading and and preparing to make a Nandoid.

Ran this on my nexus and loved it. Can't wait to give it a shot. I'm going to wait till I have time to learn more about the IMEI deal before I flash but I can't wait. Nice work.
Sent from my SCH-I535 using xda app-developers app

This looks really cool. On my todo list. Also, :good: on the logo

Nevermind

Very cool boot animation. 4G is working really well for me. Very smooth rom. I have not experienced any bugs as of yet, but then again I've only been up for less than a hour.

Rom is running awsome so far!!

can someone check the camera and also wifi tether.

Basically this Rom will try to convert your phone into tablet and ended up getting tiny fonts!
Sent from my S3 using xda premium

The fonts are not really small on this by default. I kept the default setup and the fonts are close to stock size.
The camera froze on me after one picture. I got an "gallery not responding" error. I thought I read there was a fix if the gallery.apk was replaced.

[ROM] Jelly Bean / CyanogenMod 10 on HTC ChaCha

Hello everyone,
This thread contains the developing/porting stages for the Jelly Bean / CyanogenMod 10 ROM, brought to you by adlx.xda. Therefore all the credits regarding this should go to him. Thanks man for making this device better for each one of us!
Please note that the 2nd post is reserved by adlx for future use. Keep an eye out there. In the meantime I will manage the QA and provide assistance as much as possible.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Disclaimer: Any complaints about "damaging your phone", "stuff X doesn't work and I haven't put in it the known issues list and now my phone doesn't work as I want it to work and I'm crying like a little girl", and similar observations will not be tolerated. Flash this ROM at your own risk, you have been warned.
NOTE: This ROM is far from stable, it's still under high development by the CM team. Please report all of your findings in the thread as suggested below.
2nd NOTE: Please keep the thread clean of off-topic. Questions like "when is the next release?","When is the front camera fixed?" and so on will not be tolerated.
Release: DOWNLOAD
Google Apps: DOWNLOAD
Release notes:
relnotes in progress.
Reboot Into CWM Recovery
Wipe data, wipe cache
Flash ROM .zip file
Flash Google Apps
Google Apps seem not have enough space to flash correctly - Under investigation.
Text messages do not give notifications(even after going into the settings of the messaging application and making sure that "Notifications" is checked) - Reflash ROM with data/cache wipe.
Home button does not bring you home. - Under investigation.
Search button does not seem to do work.
Camera crashes.
Web Browser seems to just flash white on the screen for a second, then disappears and nothing happens. - Reflash ROM with data/cache wipe.
Dial pad in Phone application needs slight resizing, the left side of each number is slightly cut off.
During a call, the screen is rotated counter-clockwise 90 degrees.
Apollo is rotated counter-clockwise 90 degrees, except it's settings menu.
Calculator crashes on startup.
Movie Studio crashes on startup.
Lock screen isn't showing when locking - Reflash ROM with data/cache wipe.

OP+1
Useful Stuff that apply to that rom
Trim CM10 of not so useful apks and install Google Apps Lite, by Atrix4g18
lgCamera, free from the Market work! (pictures & videos). Only back camera
Install Google Now on this Rom by ethancottier
Wifi-Tethering, by ethancottier
Help to avoid lost wifi connections: Use the WiFix-Manager to set the correct country (tip by Flexmaen)
Int2Ext+ works great:
http://forum.xda-developers.com/showthread.php?t=1716124
Some apps still have orientation issues (Apollo...), try the app named Ultimate Rotation Control v 4.8.2 (works fine for Apollo for example), Tip by GragonV
Click to expand...
Click to collapse
ASN/Modpunk from the Wildfire S development, as I massively kanged his JB sources as a starting point and I xalso use his msm-7x27 common sources.
Recognized Contributor Alex C. for this official thread OP maintenance
CyanogenMod and all the people contributing to it for the main sources
SuperTeam for their help
Click to expand...
Click to collapse
Sources:
Linux Kernel (GPL): https://github.com/adumont/htc-kernel-msm7227/
Device tree: https://github.com/adumont/android_device_htc_chacha/
Vendor tree: https://github.com/adumont/android_vendor_htc_chacha/
Click to expand...
Click to collapse

Deleted, Sorry all.

I realize that there are going to be bugs, and that you likely know of many, but I thought I should contribute with a list of bugs I've found so far.
-First of all, I can't seem to get gapps(google apps) to install. in CWM it says that it completes, but none of the applications show up, I did try a few of the latest builds, so perhaps we need to use a specific older one.
-Text messages do not give notifications(even after going into the settings of the messaging application and making sure that "Notifications" is checked)
-Home button does not bring you home(or do much of anything) even if you go and set up what it's actions do in the settings.
-Search button does not seem to do anything either.
-Camera crashes(however it says "Gallery has stopped." so I imagine it's the usual top right image preview that's the culprit, although gallery itself works fine)
-Web Browser seems to just flash white on the screen for a second, then disappears and nothing happens.(assuming crash, but it's not actually saying anything)
-Dial pad in Phone application needs slight resizing(this was also present in CM9) the left side of each number is slightly cut off.
-During a call, the screen is rotated counter-clockwise 90 degrees.
-Apollo is rotated counter-clockwise 90 degrees, except it's settings menu(this was also present in CM9)
-Calculator crashes on startup
-Movie Studio crashes on startup
-Lock screen isn't showing when locking
(some of these may be just me, because I did change a few settings. I'll have to reinstall the rom and test all of these issues again. but at least it's something to go on in the meantime. I'll also try and get a logcat when I do.)
In general, the rom is -very- fast. The first boot was extremely slow/long, but after that, rebooting is much faster. The freezing is seemingly totally gone.

GAPPS doesn't install fully because the System space is to small for gapps. I removed a load of system apps to fit all of the Gapps in. Made about 30MB free to install.

kronflux said:
I realize that there are going to be bugs, and that you likely know of many, but I thought I should contribute with a list of bugs I've found so far.
-...
(some of these may be just me, because I did change a few settings. I'll have to reinstall the rom and test all of these issues again. but at least it's something to go on in the meantime. I'll also try and get a logcat when I do.)
In general, the rom is -very- fast. The first boot was extremely slow/long, but after that, rebooting is much faster. The freezing is seemingly totally gone.
Click to expand...
Click to collapse
Thanks a lot for the testing. Although I have been able to reproduce some of them, there are some of them that won't happen to me.
For example, home button is working fine for me, as the stock Web browser (tested on wifi). Also, when I lock the phone, it does go to the lock screen fine (with some delay though).
Cam is crashing also here, as well as Calc.
Sent from my Galaxy Nexus

adlx.xda said:
Thanks a lot for the testing. Although I have been able to reproduce some of them, there are some of them that won't happen to me.
For example, home button is working fine for me, as the stock Web browser (tested on wifi). Also, when I lock the phone, it does go to the lock screen fine (with some delay though).
Cam is crashing also here, as well as Calc.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Naturally after changing most settings(as I usually do when I install a new rom, I go through every setting and get a custom experience from the start), things are bound to be different. I'm going to PM you the logcat(I warn you, it's long, but I stuck it on pastebin) hopefully it will help out a bit. if I can help in any other way, let me know.
I'll reinstall the rom in a few hours and make sure everything works properly with "out of the box" settings, and post my results.

kronflux said:
Naturally after changing most settings(as I usually do when I install a new rom, I go through every setting and get a custom experience from the start), things are bound to be different. I'm going to PM you the logcat(I warn you, it's long, but I stuck it on pastebin) hopefully it will help out a bit. if I can help in any other way, let me know.
I'll reinstall the rom in a few hours and make sure everything works properly with "out of the box" settings, and post my results.
Click to expand...
Click to collapse
thanks, but what bug did you reproduce in this particular logcat?
Some hints about capturing a logcat per bug:
You can clean the logcat with:
adb logcat -c
Then, reproduce a bug, and then dump only that to file:
adb logcat -d > bug_ANameSoWeCanUnderstand.txt
Pastebin that .txt file, with a description of the bug .
Logcat isn't very intuitive (to me at least), so imagine reviewing a logcat with a lot of posibly unrelated bug, and no idea of what bug is supposed to be reproduced in it

adlx.xda said:
thanks, but what bug did you reproduce in this particular logcat?
Some hints about capturing a logcat per bug:
You can clean the logcat with:
adb logcat -c
Then, reproduce a bug, and then dump only that to file:
adb logcat -d > bug_ANameSoWeCanUnderstand.txt
Pastebin that .txt file, with a description of the bug .
Logcat isn't very intuitive (to me at least), so imagine reviewing a logcat with a lot of posibly unrelated bug, and no idea of what bug is supposed to be reproduced in it
Click to expand...
Click to collapse
terribly sorry that was literally just a logcat from the time I installed the rom, till the time I sent it - I'm kind of new to this xD
I'll see if I encounter any major issues during my next install and if I do, I'll send you more clean, specific logcats
---------- Post added at 12:26 AM ---------- Previous post was at 12:07 AM ----------
lucasarran said:
GAPPS doesn't install fully because the System space is to small for gapps. I removed a load of system apps to fit all of the Gapps in. Made about 30MB free to install.
Click to expand...
Click to collapse
any chance you could make a list of what you removed from where?
I'd like to try myself, but I don't want to delete anything needed.

System folder issue
Just on side note: I have quick question on how CWM install works.
Why do we see difference in behavior, like here some people see Home key not working, while others are fine. Seems like after flashing some partitions have different data. While flashing in CWM we take care of erasing /data and /cache. So I think those partitions should not differ from person to person. What about /system ? What is done while installing zip? Is the /system cleaned first and then zip contains is copied? Or just copied straight away?
This question is in my mind for some time now. I have seen fresh installs of OS also showing different behavior on my Phone. So please help with answer. Thanks.
Sorry for diversion from topic. But I thought it is just relevant at this juncture. Thanks a lot.

mobilepgk said:
Just on side note: I have quick question on how CWM install works.
Why do we see difference in behavior, like here some people see Home key not working, while others are fine. Seems like after flashing some partitions have different data. While flashing in CWM we take care of erasing /data and /cache. So I think those partitions should not differ from person to person. What about /system ? What is done while installing zip? Is the /system cleaned first and then zip contains is copied? Or just copied straight away?
This question is in my mind for some time now. I have seen fresh installs of OS also showing different behavior on my Phone. So please help with answer. Thanks.
Sorry for diversion from topic. But I thought it is just relevant at this juncture. Thanks a lot.
Click to expand...
Click to collapse
This isn't really the right thread for asking generic CWM or Android questions. There are "General" forums on XDA, and google is your friend.
On that note, I can't tell you what does what(because I don't know a lot of it myself), but if you search google for "/system /boot /cache android" or similar, I'm sure you'll find a list of what's stored where.
Personally, everytime I install a new Rom, I double check to make sure it has a boot.img, then upon using CWM to install it, I first do the following(some of them are redundant, but I do so for good measure):
wipe data/factory reset
wipe cache partition
advanced > Wipe Dalvik Cache
advanced > Wipe Battery Stats
mounts and storage > unmount cache
(If the rom had a boot.img) mounts and storage > format /boot
mounts and storage > format /cache
mounts and storage > format /data
mounts and storage > format /system
-then- I install the rom zip, and if I want gapps, I flash those afterward. then reboot.
This ensures that -all- data is gone, and it will not allow for unique bugs caused by remaining data from a previous rom.
In my case with the home key not working, I think I figured out what was causing most of the problems that I had, but adlx didn't have - After trying to flash GApps, and it not installing properly, it seems to have broken something.
After flashing the rom again(after clearing all those things) I'm now not experiencing those.
Notifications are working again, home key works, lock screen works, browser works, etc.

kronflux said:
In my case with the home key not working, I think I figured out what was causing most of the problems that I had, but adlx didn't have - After trying to flash GApps, and it not installing properly, it seems to have broken something.
After flashing the rom again(after clearing all those things) I'm now not experiencing those.
Notifications are working again, home key works, lock screen works, browser works, etc.
Click to expand...
Click to collapse
Confirming the lock screen issue. At first install it did not work. Now I reflashed, booted the ROM, restarted to CWM and afterwards flashed gapps. Now it works properly.
What we need to focus on at the moment, which is very important:
- gapps flashing 100%.
- camera working 50%.
- keyboard buttons and softkeys availability.
This is my high prio list, anything else is currently not that important; I have yet to find a person that will tell me he cannot live without the calculator app for example.

Alex C. said:
Confirming the lock screen issue. At first install it did not work. Now I reflashed, booted the ROM, restarted to CWM and afterwards flashed gapps. Now it works properly.
What we need to focus on at the moment, which is very important:
- gapps flashing 100%.
- camera working 50%.
- keyboard buttons and softkeys availability.
This is my high prio list, anything else is currently not that important; I have yet to find a person that will tell me he cannot live without the calculator app for example.
Click to expand...
Click to collapse
No Calculator?! We're all going to die! D:
but on a more serious note - something that struck my high interest when exploring this rom is that there is a Hardware Keys section under System in the Settings.
Granted, the only ones that are in there currently are Menu, Home and Search(screen "buttons"), but I wonder if we can maybe add a new one in there, and have it configurable so we can open apps with it.
It might be difficult, but it also might be worth pursuing for the Facebook button.

more n00b questions
First, I too look forward to getting the list/method of uninstalling some of the bundled apps to make way for gapps.
When I flashed JB, I had no unexpected problems (ie camera wasn't working, but pretty much everything else was). I downloaded titanium and deleted calculator only, then was getting bugs with TB, where it was getting stuck in some sort of superuser loop (I had told it to sort apps by total size, in readiness for deleting the biggest non-essential ones).
I rebooted, then tried flashing the gapps zip, and did not see any errors - but when I rebooted, I could only see the gmail app - no google play app. Could it be that gapps silently failed to fully flash, or is gmail the only extra app I should see?
Last, is there a recommended / confirmed working app for moving apps/data to the SD card? With CM7 I am using link2sd and there are a multitude of others. Is JB pretty much the same, or are some apps going to work better with JB?
I am very impressed with the smoothness of the system, particularly the browser. Really great work. It is so close to being usable already.

lucasarran said:
Made about 30MB free to install.
Click to expand...
Click to collapse
30MB free only?
Hmm... is it possible to integrate some features from SuperOSR? When I had SuperOSR based on CM7 I didn't have any problems with the RAM, but with CM9 and Link2SD the RAM fills up mach faster than with SuperOSR. Don't know why but I guess CM10 with SuperOSR features would be great!

Flexmaen said:
30MB free only?
Hmm... is it possible to integrate some features from SuperOSR? When I had SuperOSR based on CM7 I didn't have any problems with the RAM, but with CM9 and Link2SD the RAM fills up mach faster than with SuperOSR. Don't know why but I guess CM10 with SuperOSR features would be great!
Click to expand...
Click to collapse
It's because Link2SD will only move apks to Sdcard, but all app data, and dalvik cache will stay on /data, AFAIK.
You would need to use another mechanism of App ti SD that moves everything, like App2SD. I haven't tried it in CM9 nor CM10 though. Anyone?
Sent from my Galaxy Nexus

adlx.xda said:
It's because Link2SD will only move apks to Sdcard, but all app data, and dalvik cache will stay on /data, AFAIK.
Click to expand...
Click to collapse
No, it can move the dalvik cache as well as app data. However for some reason it will leave more garbage behind than the version of App2SD included in SuperOSR. Also the function "relink all application files" won't really help. Sometimes I even found installation files left on /data.

adlx.xda said:
You would need to use another mechanism of App ti SD that moves everything, like App2SD. I haven't tried it in CM9 nor CM10 though. Anyone?
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
i use INT2EXT with CM9 it works great!

adlx.xda said:
Reserved for future use.
In the meantime, go to http://goo.im/devs/adlx/chacha/cm10/
Click to expand...
Click to collapse
Alex C. said:
Hello everyone,
Click to expand...
Click to collapse
Thanks guys. This is really cracking.
In the meanwhile, I had a question about the CM7/9 ROMs you guys had uploaded earlier.
In the OEM ROM / StockPlus by Hexgore, the moment I type anything, it opens up the dialer. However, in CMROMS, any words I type open up the google universal search box - which is pathetically slow and doesnt solve my purpose. Often its just a number I am entering to call, not a string!
How can we remind android that its a phone first and a smart device later?
Many thanks in advance!!
PS: Why do CM ROMs have the CM camera and not the OEM one? the OEM camera is quite decent in and of itself, no?

phone search tool
hitanshu said:
In the OEM ROM / StockPlus by Hexgore, the moment I type anything, it opens up the dialer.
Click to expand...
Click to collapse
yes, I liked that quick fast dialer too. If you just flash CM10 without Gapps, you will see that there is nice Search tool, which searches your phone contacts, apps, web (I disable this anyway). It looks neat and tidy.
So after installing Gapps, we have to somehow disable google search/google now and enable this old search tool.
[UPDATE]:
In order to get default phone search working.
- Uninstall Google Search. Alternately remove/rename system/app/QuickSearchBox.apk. Check this file is about 4MB in size.
- From CM10 zip package, extract and install the QuickSearchBox.apk. Note this is just less than 1MB in size.
This search just works for Web/Contacts/Apps and can serve as temporary fix till we get the Google Search/Now FC issue fixed.

CM²ROM Beta-16 Lollipop 5.1.1 by CMahendra & Antariksh for iBerry Auxus Note

CM²Rom Beta-16 Lollipop 5.1.1 by CMahendra & Antariksh
for iBerry Auxus Note 5.5
[Lollipop] [CyanogenMod]
(***NOT FOR ELEPHONE P2000, Do not try, else you'll brick your phone)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Features in current version:
All CM 12.1 features
USBOTG working perfect both on Android
Perfect Mounting of Partitions on PC Connection in MTP and Mass-Storage Mode.
Enable 3G Network in Any Sim without swapping sims.
Magic Happened with Proximity Sensor. Now works even on 1 and half inch away
Super Smooth Performance with necessary Tweaks
Camera (8MP) & Video Recording working
1080P Video playback working
PHONE Radio & USSD working
FM Radio working
BlueTooth Working
Back Key Swapped on Navigation Bar for Auxus Users
Battery Tweaks for less Battery Drain
ZERO BATTERY DRAIN in Standby Mode. 0% drain in overnight time.
No network drops
And so much more, everything which you expect to get working in your stock ROM is working in this build of CM 12.1 for MT6592
Fully Rooted
ZipAligned & Optimized
Only essentials apps
Loud Sound
Ported Improved and Better Stock Camera with frameworks (No Grains in camera)
All apps tested ok and perfect.
Google Now Fix with Microphone
Google Sync problem solved (read FAQ)
New Boot Animation and Boot Logo
Buttery Smooth
Full Tweaking init.d Support enabled
Deep Sleep Tweak Enabled
Ram Optimization
Auto Cache Management
Wifi performance improved
Faster UI rendering via GPU
Improved photo and video recording quality
Fixed!!! Rare Network drop. (Enable Airplane mode and disable if still experienced!)
Many tiny things I don't remember now
Whats wrong/missing? Remember this is Beta Version.
There could be some minor annoying bugs, Please help yourself and inform me with details in comments below. Private Messages are not allowed.
GPS not working, Still under development
Fingerprint Not available in CM (will not be added)
NFC removed due to bug and will not be added.
*Important: Do not send pm (private messages) for any rom related issues, obviously it will be ignored and pm will be bluntly deleted without reading. Post here in thread only, which I will try to reply asap.
Installation Instructions:
Warnings:
Do at your own risk. I am not responsible for any damages.
Do not forget this is BETA VERSION!
Electric Supply failure or disconnection due to poor cable while flashing may still brick your phone. So inform your electric company that you are flashing. ha ha
Take Full Backup of all your personal files from storage partitions. Don't complain of lost data.
GET READY WITH FILES
VERY IMPORTANT: Read Frequently Asked Question below in Second Post
DOWNLOAD Main CM2Rom Full Version and also Google Apps (5.1.x Nano Version) and keep in the root folder of SDCARD.
***Download Links are in Download Section in Post#3
***Do not flash other versions of Google apps.
Are you Ready? Let's start Flashing Rom Now in proper steps ....
CLEAN PHONE: Open phone in Recovery mode (TWRP 2.7.1.0) and do FACTORY RESET.
.
FLASH MAIN ROM: Flash CM² Rom (Do not exit)
.
GPAPPS: Flash Google Apps Nano Edition (DO NOT USE Pico edition).
Done! Now reboot to System and Enjoy
Press thanks if you liked my work.
.
You are also advised to Disable "Vibrate on Touch" option, to fix occasional hanging problem.
Credits and Project Information:
Credits
CyanogenMod Team: For CM
Fire855 : For this Amazing CM 12.1 Lollipop ROM Developement for MediaTek Devices .
www.mtkroms.com : For Fire855
Ajit Guraya: For further Developement and Improvements
Antariksh: For Storage Partition Fix, Battery Drain Fix, USBOTG Integration, Mass-Storage Fix.
CMahendra: For everything else
XDA:DevDB Information
CM²ROM Lollipop 5.1.1 based on CM12.1 for iBerry Auxus Note, ROM for all devices (see above for details)
Contributors
cmahendra
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Beta
Current Stable Version: Beta 11
Stable Release Date: 2016-01-05
Current Beta Version: Beta 11
Beta Release Date: 2016-01-05
Created 2016-01-05
Last Updated 2016-01-05

Frequently asked questions
FREQUENTLY ASKED QUESTIONS
Question 1) Is this Rom Rooted? I do not see SuperSU icon.
Answer: This ROM comes with another Super User software called "KINGROOT" and you will find KingUser icon in rom
Question 2) Icons Missing. After installing new Apps, I do not see new shortcut icons in Application Drawer. How to see them?
Answer: This is known minor issue of Trebuchet (The included Lollipop Launcher) The simple resolution is as follows.
Go to Settings >> All Apps >> Trebuchet >> Force Stop.
Now go back to Launcher and you will see all missing icons appeared.
Question 3) WhatsApp and other apps are not restoring data backup from previous rom. What to do?
This rom does not come with Swapped Memory Partitions. Hence copy WhatsApp folder from External SDCard to Phone Storage. Clear Data of Whatsapp from All Manager. Now it will recognize backup and will restore.
Question 4) Why Gmail and other Google apps are not syncing data?
This rom lacks GPS fix at this moment hence Google fails to get location. Just go in Settings and disable Location (GPS). Now GMail and other Google apps will start syncing
Question 5) Rarely or Occasionally Phone Network drops for few seconds.
Inherited Issue from CM 12.1. If this is just after Flashing rom then, simply Disable Location and Reboot. Otherwise just enable Airplane Mode and disable it. Network will be stable.
Question 6) GPS / NFC / FingerPrint is not working!
Yes I know! Wait for some time for the fix.
Question 6) NFC and FingerPrint Features are not working!
The port version of CM 12.1 I selected for Auxus Note does not have FingerPrint scanner feature. Hence it can not be added. NFC is disabled for some technical issues but I am sure you do not need both features for the sake of CyanogenMod 12.1 Porting CM for Dual Sim MediaTek devices is not easy task. It takes months of work hence I thought these are not worth wasting time which may delay project for another 2/3 months. Hope you understand. Thanks !
Question 7) After flashing your rom my IMEI numbers are lost and phone lost its network. How to restore my IMEI numbers of phone?
Due to mismatch in Radio files mismatched between the roms of two different chipsets, you may lose IMEI on some roms after flashing. Do not panic or worry, it can be restored easily. Remember for DUAL SIM phone you need to restore both IMEI numbers, which are found on your Invoice (Bill), Product Box or below Battery)
METHOD 1) Restore your own IMEI numbers with this amazing APP. Read warning carefully.
WARNING: DO NOT SHARE YOUR IMEI WITH ANYONE ELSE. Remember, using FALSE IMEI numbers is illegal in any country and it can put you in JAIL. These days they are tracing culprits for terrorism threats. So please use this app to restore your own IMEI only.
https://play.google.com/store/apps/details?id=com.cryptotel.chamelephon&hl=en
METHOD 2)
Restoring NVRAM BACKUP taken with MTKDROID TOOLS which you can flash with SPFT Flashing tool.
a) Watch this video to know how to take backup of NVRAM of a working STOCK ROM with the help of MTKDROID Tools. You must know that NVRAM backup file stores your own IMEI Number. Do Not share it with anyone else. They will restore their phone with your IMEI number and will put you in trouble.
_____ https://www.youtube.com/watch?v=3tttvKlWTwc
.
b) When IMEI is lost flash this only single entry of NVRAM with SPFlash tools
WARNING: DO NOT SHARE YOUR NVRAM FILE WITH ANYONE ELSE. It stores your IMEI Number.
Separate XDA Link:
Question 8) Can I play heavy Games on this Rom? (Why some games run slow on this rom?)
The rom in optimized for less battery drain hence CPU is generally in PowerSave mode or Balanced Mode.
This setting is in Settings >>> Battery >>> Battery Mode >>> ???
Gamers should change Battery Mode to PERFORMANCE mode while playing games to get full power of CPU.
After playing games changing battery mode back to BALANCED mode or POWERSAVE mode will be best idea.
Question 9) Sometimes phone lags.
This is a known issue in Beta 12 (first release) still WIP. The quick workaround is reboot the phone in Recovery Mode and clear Dalvik Cache and Cache one a day in middle of a day.
Question 10) Sometime rare camera do not work. Camera keeps showing front camera and no option to change back to rare.
This is known issue and quick workaround is as follows.
Settings >>> Apps >>> All >>> Camera >>> Clear Data and Remove Battery then switch on. Camera should work now.
One more workaround is restart the phone but if still does not work then reboot the phone in Recovery Mode and clear Dalvik Cache and Cache one a day in middle of a day.
Question 11) Flash icon disappeared in camera and can not use flash.
Settings >>> Apps >>> All >>> Camera >>> Clear Data and Remove Battery then switch on. Camera should work now.
Question 12) Sometimes Network is dropped and does not comes back.
This is fixed in BETA 15 but if you still experience it just enable Airplace mode and again disable it. This may happen frequently in remote locations (rural areas or areas with weak network)
Question 13) Battery 1% problem . Battery was charged a lot, but after rebooting or returning from Recovery mode the battery started showing 1%.
This is known battery synchronization bug in previous version of Recovery. If you are on Version 2 of my TWRP 2.7.1.0 you may not have this problem.
But even if you are on latest recovery and you get this 1% battery issue, then do a simple solution.
Workaround (a) Connect Charging cable to charge phone, Power Off and Power On Normally without removing power cable. Works!
Workaround (b) If above does not work, then Start phone in recovery (twrp) mode, plug in power cable and keeping the power cable connected, restart the phone in normal mode (also called system mode, Reboot to System).
The phone will again show normal charged count. Usually doing this only one time should solve problem.
.
===============================================.
More questions and answers will come in next few days, until development is over.
===============================================
Good Night!

Download links
Download links
2016-02-08 : Beta Version 16 --- Full Rom
CM2Rom Update 16. (Full Rom. Clean Install recommended, though you can try dirty flash.)
IMPORTANT: Always take full BACKUP in Recovery mode as precaution, before flashing any UPDATE PATCH or FULL ROM.
Download : https://www.androidfilehost.com/?fid=673368273298965024
MD5: 6c3323e46997fa28727331c144d597a7
Changelog:
Some important fixes and updates from previous build.
Click to expand...
Click to collapse
2016-02-08 : Beta Version 15 --- Small Update Patch
CM2Rom Update from Beta 14 to Beta 15. (To be flashed after full rom beta 14)
IMPORTANT: Always take full BACKUP in Recovery mode as precaution, before flashing any UPDATE PATCH.
Download : New version released. check above
Changelog:
Memory Leak is fixed. Now Phone works smooth without any reboot required. Keep as many as apps in recent apps and still phone is faster and smoother.
Some minor fixes not worth discussing
Press only this blue Button on download page.
Click to expand...
Click to collapse
2016-01-11 : Beta Version 14 --- Full Rom
CM2Rom Full Rom Beta Version 14
Download : New version released. check above
Google Apps: Nano version
Download: Download from OpenGapps website
Changelog:
Different method used for enabling init.d support. Works great
Added many scripts to reduce memory leak and ram optimization
Battery saving script
CPU performance increased via kernel settings.
Wifi Connect Speed optimization
Google DNS servers added.
Click to expand...
Click to collapse
2016-01-05 : Beta Version 12 --- Full Rom
CM2Rom Full Rom Beta Version 12
Download Beta Version 11 : New version released. check above
Click to expand...
Click to collapse

PATCHES AND MODS
---- coming soon

Thank u sir

baskye said:
Thank u sir
Click to expand...
Click to collapse
u r welcome! Did you try this one?

Will try and get back sir.

First feel wow. Our waiting and belief in you had not been wasted. Lollipop soooo. sweet....

baskye said:
Will try and get back sir.
Click to expand...
Click to collapse
Sure! Take your own time
baskye said:
First feel wow. Our waiting and belief in you had not been wasted. Lollipop soooo. sweet....
Click to expand...
Click to collapse
Thanks

Hi CMahendra,
thanks much for your work and efforts with this ROM. I do not mind NFC and fingerprint missing but GPS fix is a vital feature. When are you planning to fix GPS as for the moment this is a showstopper for this ROM?
Thanks in advance!

barev said:
Hi CMahendra,
thanks much for your work and efforts with this ROM. I do not mind NFC and fingerprint missing but GPS fix is a vital feature. When are you planning to fix GPS as for the moment this is a showstopper for this ROM?
Thanks in advance!
Click to expand...
Click to collapse
Thanks a lot for your reply. GPS is important for me too. I am working on it. This is Beta Version and may have some minor bugs. Things will be all perfect when I will release final version.
BTW I am using it for business use and there is no other problem for me while using it. If it lags for some time, just restart and within 30 seconds phone will behave normal Could not work on it for few days due to main job. BTW I do not believe in declaring ETA. Thanks

I flashed lollipop os bt ma cel too heated & sometimes runnings very slow plzz halp me Mahendra Chavan sir i like too much this os bt sometimes faced this problem plz help

Rear camera is not working even after trying your workarounds... Also, what's up with home key? (I am talking about the one bellow the screen, not the onscreen one) It's not working, when u touch it, it vibrates, but doesn't do anything. Another thing is that when u reboot the phone, battery shows 1%, even when it's fully charged. Other than these things, the ROM is quite nice, but wouldn't recommend using it on daily bases.. At least until these bugs are fixed.

Thank you for the awesome rom and for your endless efforts. Downloaded the latest Beta 14 build and will report bug if any shows up.
14/2/16. Updated to latest Beta 15 build which is working great and memory leak isn't an issue anymore.

CMahendra Sir first of all i want to thank you for this great ROM. But i am facing RAM leak issue after 3-4 hours phone become hang and only restarting (remove battery) is only solution. please short-out this problem

Jtig said:
Rear camera is not working even after trying your workarounds... Also, what's up with home key? (I am talking about the one bellow the screen, not the onscreen one) It's not working, when u touch it, it vibrates, but doesn't do anything. Another thing is that when u reboot the phone, battery shows 1%, even when it's fully charged. Other than these things, the ROM is quite nice, but wouldn't recommend using it on daily bases.. At least until these bugs are fixed.
Click to expand...
Click to collapse
Thanks for reply.
Camera works fine but sometimes it changes to front camera for which workaround is given.
Home key on navigation screen works perfect and homekey on phone is not working but both do same task so you can ignore all keys on phone hardware below.
Phone battery shows 1% because you have wrong version of Recovery installed. Read Thread and FAQ carefully.
I already mentioned rom is in beta stage and still work in progress. But I am using it as daily driver. Though Memory Leak (hangs after 4 hours) and GPS are only two known bugs with this rom. So wait for some time if you can not stay with these two.
No need to recommend this rom to anyone. If any courageous person want to try, he/she will do so on their own
balamurali24 said:
Thank you for the awesome rom and for your endless efforts. Downloaded the latest Beta 14 build and will report bug if any shows up.
Click to expand...
Click to collapse
MPGANGWAR said:
CMahendra Sir first of all i want to thank you for this great ROM. But i am facing RAM leak issue after 3-4 hours phone become hang and only restarting (remove battery) is only solution. please short-out this problem
Click to expand...
Click to collapse
Thanks a lot for response to this rom. I am using this rom as daily driver. Memory Leak (hangs after 4 hours) and GPS are only two known bugs with this rom and I am trying it to resolve asap. So please wait for some time. Thanks :good:

siddlv25 said:
I flashed lollipop os bt ma cel too heated & sometimes runnings very slow plzz halp me Mahendra Chavan sir i like too much this os bt sometimes faced this problem plz help
Click to expand...
Click to collapse
Heating while flashing is common issue and you can ignore it. Running slow sometimes is called Memory Leak and it happens after 3/5 hours of use. I am working on the issue. You can restart phone to make it smooth again. Please wait until next update.

Isn't there a way to fix the hardware home key? I mean, since we're all used to the resolution, the software keys are a bit annoying and personally i just disable them (why would u want buttons, that take extra screen space, when u have hardware buttons that do the same exact thing). Also, camera does not work even when given workarounds are used. Also, I forgot to mention, that I came from Elephone P2000 community, maybe that is causing the weird bugs?

cmahendra said:
Heating while flashing is common issue and you can ignore it. Running slow sometimes is called Memory Leak and it happens after 3/5 hours of use. I am working on the issue. You can restart phone to make it smooth again. Please wait until next update.
Click to expand...
Click to collapse
Ok sir i am waiting

UPDATE: CM2ROM LOLLIPOP: I think the memory leak problem is almost solved. Now phone is not hanging and much more faster , responsive all the time and no reboot required. No slowdown so no reboot Still will do test for a day and will release a small patch, if successful.
EDIT: Real good results. Changes Confirmed. After 8 hrs of new changes in framework files and new init.d scripts, phone is super smooth and I have at least 25 apps in recent app. I am Not even deliberately trying to clear them .
*Using heavy apps alike FB , Messenger , WA Lollipop version, etc and no lags at all Releasing patch tonight or tomorrow morning

[DISCONTINUED][ROM][STABLE] LineageOS 16.0 (unofficial) for ZTE Axon 7 Mini (aka tulip)

Unfortunately the hoster where my build server is located raised the fees and i had no way to download a backup of my data... As i can't afford it now i had to delete everything. With a heavy heart I have to discontinue this great ROM for a great phone..
- first of all, thanks to @tdm for his tremendous effort to have us all enjoy LineageOS in the first place, without his contribution this thread would never exist. Also thanks for tdm's Lineage 14.1 where I took this post's layout from -
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Gentlemen,
The time has come to share what's due to be shared.
Supported devices
* US model running 7.1.1 b14 firmware
* EU model running 7.1.1 b12 firmware
Pre-requisites
Make sure to have at least this TWRP version installed
Patience as first start takes a while
First time install Instructions
Use these instructions when coming from any other ROM (stock, AOKP, LineageOS 15.1, etc.)
Download ROM.
Download GAPPS if desired.
Boot into recovery.
Backup your current data.
Format/Wipe 'Dalvik/ART Cache', 'System', 'Data' and 'Cache'
Flash ROM.
Flash GAPPS if desired.
Reboot.
Upgrade instructions
Use these instructions when upgrading from a previous Lineage 16.0 build.
Download ROM.
Boot into recovery.
Backup your current data.
Flash ROM.
Reboot.
Flashing instructions
There are two main ways to flash files onto your phone: local and sideload. Most people are only familiar with local, but sideload is much quicker and easier if you are at a PC.
Sideload
Download the ZIP file(s) to your PC. In TWRP, select advanced and then sideload. Swipe the slider to begin, then on your PC run "adb sideload <filename>".
Local
Download and/or copy the ZIP file(s) to your phone. Note whether they are on internal storage (the default) or the sdcard. In TWRP, select install, find your file, and select it.
Status
This is currently stable quality
Known issues
Very minor graphical glitches
sometimes videos don't play, you have to remove the relevant all from your recent app list and restart (e.g. WhatsApp)
AKM DAC is not supported
Selinux permissive
To Do list
Implement Camera2 API Thanks for customizing libraries and not sharing any code or insight ZTE
Get DSP to kick in for high quality audio again
Download
Google Drive
* works well with open gapps
Sources
Device tree
Kernel
Vendor
Note: please refrain from requesting other Android distributions from me, like AOKP, AOSP, etc - this is most likely not going to happen from my end. As I provided all my sources you can fork the stuff yourself and try to build
Special thanks
@R3bornD4rth for having provided me an axon 7 mini for my testing/debugging, which is heavily in use and doing great so far
@tdm for his original work on this
@armandop_ for his ZMAX Pro Repo and help getting LiveDisplay to work (flawlessly, thanks mate)
intervigilium aka Ethan Chen for his work on HTC One A9 (hiae) (which shares the same chipset as our phones)

Thanks for this rom, there's a way to make work the camera API 2 (in the future)?

jose_777.mx said:
Thanks for this rom, there's a way to make work the camera API 2 (in the future)?
Click to expand...
Click to collapse
Good question, no clue if I will be making it to work somehow I can try to get some pointers if there are just some drivers to be altered or whatever is needed to have this done

I installed magisc 19.1, and dolby for better sound.Now it is my dayly driver,
Thanks Man!

bius88 said:
I installed magisc 19.1, and dolby for better sound.Now it is my dayly driver,
Thanks Man!
Click to expand...
Click to collapse
Cool!
Would be better if GPS and Cam would work though I am working on GPS right now, will soon test my latest build, so fingers crossed

Working well with open gapps 9 micro.
Play store works
Pixel launcher fc.
Camera works. The app doesn't. Download any other camera and you're good.
Looking great so far
Thanks

Holyoblation said:
Working well with open gapps 9 micro.
Play store works
Pixel launcher fc.
Camera works. The app doesn't. Download any other camera and you're good.
Looking great so far
Thanks
Click to expand...
Click to collapse
What? The camera really works? Then I shall replace the camera app with another one maybe ?

Works great with opengapps pico too i am using this for a day and there is not a big issue i will share if any unexpected issue happens. Thx for your effort
EDIT: I think there is still a problem with camera. i tried it with 2 applications and one game.
I have problem with instagram videos i cant play them.
Cant open flashlight from quick settings.

koktey14 said:
Works great with opengapps pico too i am using this for a day and there is not a big issue i will share if any unexpected issue happens. Thx for your effort
EDIT: I think there is still a problem with camera. i tried it with 2 applications and one game.
I have problem with instagram videos i cant play them.
Cant open flashlight from quick settings.
Click to expand...
Click to collapse
I see 2 issues here to be fixed. first with the video playing will be added to my known bugs post, the flashlight thing is related to the camera not working (pretty sure at least)

Small update: unfortunately I can't find a reason why GPS is not working on LOS16, but worked in LOS15.1, even just taking the files from 15.1 and placing them in 16 didn't help. The error messages in the log are not disclosing enough information what exactly the issue could be, just getting loads of invalid handle errors. Comparing with other msm8952 chipsets I don't really see any differences, so I am clueless now

TheSSJ said:
Small update: unfortunately I can't find a reason why GPS is not working on LOS16, but worked in LOS15.1, even just taking the files from 15.1 and placing them in 16 didn't help. The error messages in the log are not disclosing enough information what exactly the issue could be, just getting loads of invalid handle errors. Comparing with other msm8952 chipsets I don't really see any differences, so I am clueless now
Click to expand...
Click to collapse
Can there be a chain problem with sim card, graphics or camera maybe

koktey14 said:
Can there be a chain problem with sim card, graphics or camera maybe
Click to expand...
Click to collapse
Well, this really looks like it - I reverted back to the state where I took over from tdm and applied just the modifications to make nfc, wifi, bt, radio to work. Now GPS works, but wifi went back to sometimes fail to start where you have to reboot to make it actually work again.. it seems something I added along the lines fixed the issue with wifi and another one broke GPS
I am trying to fix wifi now somehow to make it behave stable again, then we can enjoy even a fixed GPS phone
Next stop is camera (after I repaired wifi)

TheSSJ said:
Well, this really looks like it - I reverted back to the state where I took over from tdm and applied just the modifications to make nfc, wifi, bt, radio to work. Now GPS works, but wifi went back to sometimes fail to start where you have to reboot to make it actually work again.. it seems something I added along the lines fixed the issue with wifi and another one broke GPS
I am trying to fix wifi now somehow to make it behave stable again, then we can enjoy even a fixed GPS phone
Next stop is camera (after I repaired wifi)
Click to expand...
Click to collapse
Apparently I fixed wifi I rebooted 15 times to be sure and it always turned on, GPS still functioning as well!
I will update the OP and proceed with cam (which is so broken that not even 3rd party apps work at the moment)
EDIT: Notification lights fixed as well

@TheSSJ -Great Work man!
Will try it out as soon as I get a chance
edit - is the TWRP version the same as Oreo or a newer one ?
edit 2 - Are you building an Aokp version ?

Hi, thanks for the hard work. Does the firmware support fast charging?

BAPK said:
Hi, thanks for the hard work. Does the firmware support fast charging?
Click to expand...
Click to collapse
Yes, as this is setup on kernel side the stock settings have been just kept

k500zm;79544339 [user=2388665 said:
@TheSSJ[/user] -Great Work man!
Will try it out as soon as I get a chance
edit - is the TWRP version the same as Oreo or a newer one ?
edit 2 - Are you building an Aokp version ?
Click to expand...
Click to collapse
Twrp is the same with oreo i installed it.
I was thinking about aokp too but didnt want to put pressure on you. you are already busy. @TheSSJ what do you think about this?

Once I fixed all issues with LOS16, compiling aokp should not be too hard, but I can't promise it

Now i installed the new build but i have a problem. First i made an update but i wasnt able to open get through lock screen after that i made a clean install but now it is too laggy always freezing. Its too difficult to use this build.

koktey14 said:
Now i installed the new build but i have a problem. First i made an update but i wasnt able to open get through lock screen after that i made a clean install but now it is too laggy always freezing. Its too difficult to use this build.
Click to expand...
Click to collapse
Strange,i just clean installed and it is working really fast
Can you provide dmesg and logcat please, then I can check

Database Info

welcome