[ROM] [UNOFFICIAL] CM 12.1 for Kinzie [23/02/2016] - Droid Turbo 2 Android Development

{
"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"
}
Cyanogenmod 12.1 Unofficial Kinzie Port​
Hi, everyone! Here's a little surprise for you: @Xadro and I have been working the last couples of weeks on porting CM12.1 to our Kinzie devices... and we have! So we wanted to share this little present with you, a port of CM12.1 for our brand new X Force device.
SCREENS
Some good old screens for you
COMPATIBILITY
From what we've tested, it works on EU Moto X Force, we don't know if it will work on devices from other zones - China, Brazil... Also, even if you could flash the ROM on US Droid Turbo 2 it probably wouldn't work as it doesn't have the Verizon vendor files on it, sorry .
WHAT WORKS
As far as we know, everything that's not Moto related.
What does that mean? No Moto Voice, Moto Actions or Moto Display, so please think carefully before flashing so you don't have to go back to store Moto later. Moto Gallery and Moto Camera can be flashed, though.
Also, if you see anything that's not working properly, please contact us.
WHAT DOESN'T WORK
As stated before, most Moto Apps will just FC.
Some applications fail to install from Play Store with an SDCard on the device.
Anything else you find while using it.
DOWNLOADS
CM12.1 for Kinzie ROM - [27/02/2016]
23/02/2016 version - works fine with multiSIM
Open GApps - Choose ARM64 and 5.1!
Modems
Lollipop 5.1 EU Modem
Lollipop 5.1 LATAM Modem
INSTRUCTIONS
Please follow these instructions carefully:​
Copy the ROM and the GApps zip to your phone storage - internal or sdcard, it doesn't matter.
Unlock bootloader. CAUTION: this will probably void your warranty AND WIPE ALL YOUR DATA, INCLUDING INTERNAL STORAGE - photos, songs, documents...
Flash TWRP recovery from bootloader. I recommend using @Xadro's. If you are using mine, install this one, since mine won't let you flash the ROM.
Code:
fastboot flash recovery TWRP-3.0.0_kinzie.img
If you were already on Android 6.0, flash the Android 5.1 modem. Otherwise you'll have network issues.
Code:
fastboot flash modem modem.bin
Reboot to recovery.
Do a full backup - you'll probably thank me later .
Wipe data, some settings from stock ROM may lead to bootloops or malfunction.
Install CM from the zip.
Install GApps.
Reboot and enjoy!
SOURCES
Kinzie Porting Github - the repos may be messy, we'll try to tidy them up a bit in the future.
CREDITS
CyanogenMod team for their base source and documentation.
AICP Team for their clark sources, since we used them as a base for kinzie.
Of course, @Arasthel and @Xadro .
​

CHANGELOG​
[27/02/2016]
CPU freqs adjusted to stock ROM ones
Solved charging white screen issue - and probably, overheating while charging
IR sensors working!
[23/02/2016]
Added compatibility with MX and BR devices.
Improved WiFi connection stability by changing the way dhcpcd is started.
[20/02/2016] - Initial upload

Thanks a lot, I'll test it tomorrow!
I have a question : why lollipop?
Inviato dal mio XT1580 utilizzando Tapatalk

Razorbacktrack5535 said:
Thanks a lot, I'll test it tomorrow!
I have a question : why lollipop?
Inviato dal mio XT1580 utilizzando Tapatalk
Click to expand...
Click to collapse
One has to start somewhere.

Xadro said:
One has to start somewhere.
Click to expand...
Click to collapse
Why not with CM14 then?
Edit: Awesome guys!!! Thank you so much for your hard work
Sent from my XT1580

I'm crrying... THANK YOU. Any bug too critical for daily driver?
Edit: Reporting, everything seems BUTTERY SMOOTH, flashed LL modem, and got everything working except sim, i'm getting the only emergency calls. Is a Mexican Moto X Force. Anyone has a clue of how can i get it to work?

MuyKurioso said:
I'm crrying... THANK YOU. Any bug too critical for daily driver?
Edit: Reporting, everything seems BUTTERY SMOOTH, flashed LL modem, and got everything working except sim, i'm getting the only emergency calls. Is a Mexican Moto X Force. Anyone has a clue of how can i get it to work?
Click to expand...
Click to collapse
I also just tried flashing and everything seems to work except for no sim card recognized. I also have mexican moto x Force. If anyone can tell us how to get service that would be great.

mr2sweet said:
I also just tried flashing and everything seems to work except for no sim card recognized. I also have mexican moto x Force. If anyone can tell us how to get service that would be great.
Click to expand...
Click to collapse
I'm going to try to flash UK modem and see if that will fix it, I don't really care if i lose the second sim slot. I don't use the dual sim setup anyway. Downloading right now, will report back if succesfull.
Edit: Nope, no SIM...

I wonder if they can do whatever they did to the eu modem to our mx modem to make it work with the port?

Arasthel said:
IR Sensor won't work as it deeply depends on Motorola framework files to work. Maybe we can port it someday, but it's not likely to happen any time soon.
Click to expand...
Click to collapse
CM dev got the Moto Quark IR sensors to work just fine. (Droid Turbo XT1254, Moto Turbo XT1225, "international" Moto Maxx XT1225, U.S. Moto Maxx XT1250)
So, it's possible.
We have 12.0, 12.1 (Lollipop 5.1.1) and now Preview Build of CM 13 (Marshmallow), all with Motorola IR sensors. Other Quark ROMs are also using CM's code.

mr2sweet said:
I wonder if they can do whatever they did to the eu modem to our mx modem to make it work with the port?
Click to expand...
Click to collapse
Actually, we didn't do anything to the EU modem, it's the stock 5.1 one. If you flash the MX 5.1 one and it doesn't work, that's because build.prop is not configured properly. It would be helpful if you upload your stock build.prop, but it will be difficult to detect your phone region in order to use the configuration you need. Maybe @Xadro can think of a better solution.
ChazzMatt;=65436576 said:
CM dev got the Moto Quark IR sensors to work just fine. (Droid Turbo XT1254, Moto Turbo XT1225, "international" Moto Maxx XT1225, U.S. Moto Maxx XT1250)
It's possible.
Click to expand...
Click to collapse
We're not saying it's not possible, we're saying it's a really difficult task. Quark uses the STM401 sensor device with Moto Sensor Hub to make IR work. Instead, Clark and Kinzie use the STML47X sensor. While there is a library module for STM401 there doesn't seem to be one for STM4L. Maybe the STM401 will partially work, but I wouldn't bet on that...

MuyKurioso said:
flashed LL modem, got everything working except sim, i'm getting the only emergency calls. Is a Mexican Moto X Force. Anyone has a clue of how can i get it to work?
Click to expand...
Click to collapse
Not clear which modem you flashed...
Re-flash your stock modem for YOUR phone.
If you already did that, sorry.

Ok, so here's my Build.prop, I don't know if that would help. Anyway, thanks a lot.
https://drive.google.com/file/d/0B14IVKIVgBZWOTdJU01qaW5YdHM/view?usp=docslist_api
Edit: it's the lollipop stock Build.prop

MuyKurioso said:
Ok, so here's my Build.prop, I don't know if that would help. Anyway, thanks a lot.
https://drive.google.com/file/d/0B14IVKIVgBZWOTdJU01qaW5YdHM/view?usp=docslist_api
Edit: it's the lollipop stock Build.prop
Click to expand...
Click to collapse
Thanks for the build.prop, I was able to make a new configuration for LATAM Kinzie. Can you try this version? Also, remember to flash the right modem (LATAM for 5.1). It's the "NON-HLOS.bin" file that comes on the stock ROM zip, or at least it was on EU.

Arasthel said:
Thanks for the build.prop, I was able to make a new configuration for LATAM Kinzie. Can you try this version? Also, remember to flash the right modem (LATAM for 5.1). It's the "NON-HLOS.bin" file that comes on the stock ROM zip, or at least it was on EU.
Click to expand...
Click to collapse
Yeah, i've already flashed the right módem, in fact i downgraded to stock 5.1.1 to be ready for your ROM cause CM or AOSP is what I was craving for the X Force since i've found the stock to be solid, but sluggish at times. Will try this Build in a few hours, when I can get some WiFi coverage, and then report back. Thank you for your hard work.

Arasthel said:
Thanks for the build.prop, I was able to make a new configuration for LATAM Kinzie. Can you try this version? Also, remember to flash the right modem (LATAM for 5.1). It's the "NON-HLOS.bin" file that comes on the stock ROM zip, or at least it was on EU.
Click to expand...
Click to collapse
So, still no SIM... Luckily I made a backup this time...

Could you tell me what's the result of using:
Code:
adb shell getprop ro.boot.carrier

Arasthel said:
Could you tell me what's the result of using:
Code:
adb shell getprop ro.boot.carrier
Click to expand...
Click to collapse
in the stock firmware, or in your rom?

It should give the same result on both of them.

Arasthel said:
It should give the same result on both of them.
Click to expand...
Click to collapse
oh, ok. give me a sec, i can't seem to get my pc to recognize my moto x force in the ADB devices list with your rom. Will restore backup and try on the stock one.
---------- Post added at 10:18 PM ---------- Previous post was at 10:09 PM ----------
Arasthel said:
Could you tell me what's the result of using:
Code:
adb shell getprop ro.boot.carrier
Click to expand...
Click to collapse
retmx

Related

[NEW][ROM][AOSPA][4.4.2] - Paranoid Android - 4.1 Beta 2 - 12th of March (Post #2).

I own an N7105 LTE on Telstra, Australia. Works Perfectly FINE... Follow Installation Steps Bellow:
{
"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"
}
Okay ladies and gentlemen, we have a new player in town cooking the latest Paranoid Android ROMS. So I have removed the older links from the Original Post and the details are bellow:​
Send your 'thank you' messages to our new hero Mr. Shingers5​
Installation:
NOTE #1:
Download LINKS are available by going to the latest pages and finding "shingers5" who will be posting his latest builds here. Once he has released a Stable Version, I will post his links on the main thread. For now though his Beta's have been tested and stable for everyday use from what I am hearing.
NOTE #2:
If you don't need the installation directions, follow Note #1 and go find yourself the latest 'Beta' posted by the aforementioned user.
NOTE #3:
Paranoid Android GApps can be found in POST #2. As well as any other links for future reference.
1)
GET THE LATEST TWRP FROM THE OFFICIAL SITE:
- Check POST TWO Bellow FOR LINKS.
Wipe Caches + Data / Factory Reset
Install Rom
Install Gapps (Check POST TWO)
Reboot
2)
[OPTIONAL]
Download a KERNEL of your choice (Used generally to improve Battery Life and/or Performance). Giving you certain tweaks and modification that don't generally come with Stock Kernels.
I recommend the one bellow, I have tested it myself on multiple ROMS; always get the latest version. Have a read through the thread and see the advantages yourself.
AGNi pureCM:
http://forum.xda-developers.com/showthread.php?t=2316648
[MUST READ]
I am not responsible or liable in any way to anything which might happen directly or indirectly to your device. Everything worked perfectly fine for me, I just have to put this, and please you should know what you're doing before you do it.
I am not involved in any of the teams I have linked above. The Image at the TOP belongs to the Paranoid Android TEAM.
PLEASE:
If you use and like this ROM or any of the KERNELS I have linked above. You do not need to thank me, I did not do anything other than write this piece. GO AND THANK the aforementioned developers for their hard-work and dedication to the community.
STABLE & BETA RELEASES WILL BE POSTED HERE
NO Stable Release YET
shingers5 said:
Fresh off the press guys recently released 4.1 Beta 2 so enjoy
https://docs.google.com/file/d/0B029oIGmuWyfV1owak1fX1BBZDg/edit
Click to expand...
Click to collapse
GET THE LATEST TWRP FROM THE OFFICIAL SITE:
Flash the Latest ZIP Formatted TWRP using your current Recovery and restart back into recovery; you should now see the latest TWRP you downloaded from the link bellow. (Make sure you get the .ZIP format).
http://goo.im/devs/OpenRecovery/t0lte
Paranoid Android GApps LINK:
http://forum.xda-developers.com/showthread.php?t=2397942
Camera Issue
Hi,
I have recently installed the PA rom and so far I liked it a lot.
However I noticed there is a bug with the camera.
Stock camera app: Function fine
Other camera apps (LINE camera, Instagram): Buggy, always come up with a message "cannot connect to the camera"
Please see if there is a fix on it?
Deleted Post : Irrelevant.
Absolutely brilliant! I tried porting PA to my N7105 (on Telstra as well, actually) but only got part of it to work. Do you plan to keep this updated at all?
screamworks said:
Absolutely brilliant! I tried porting PA to my N7105 (on Telstra as well, actually) but only got part of it to work. Do you plan to keep this updated at all?
Click to expand...
Click to collapse
Thank you, but as I've mentioned in the original post I don't deserve the thanks, so go thank the original developers. I've linked them in the OP.
It seems there is a new update (in the link available on the Original Post). Anyone facing any issues should definitely update their ROM.
i realised i can find the camera app in the app manager. whenever i take photo with the camera app, it doesnt save the photo. any help here?
listenlily said:
i realised i can find the camera app in the app manager. whenever i take photo with the camera app, it doesnt save the photo. any help here?
Click to expand...
Click to collapse
What version of Paranoid Android are you running? The latest one?
Hi, can I just confirm that pa_t0lte-3.65-20130705.zip is the latest version? Thread title says 07/07.
Im running 3.65
Sent from my GT-N7105 using XDA Premium HD app
listenlily said:
i realised i can find the camera app in the app manager. whenever i take photo with the camera app, it doesnt save the photo. any help here?
Click to expand...
Click to collapse
Check the location of the save folder
Sent from my GT-N7105 using Tapatalk 4 Beta
Pondy said:
Hi, can I just confirm that pa_t0lte-3.65-20130705.zip is the latest version? Thread title says 07/07.
Click to expand...
Click to collapse
Yes it is the latest version. Also sorry it should say the 05/07/2013. I will fix it when I get home.
listenlily said:
Im running 3.65
Click to expand...
Click to collapse
I have a link to the AT&T post in the Third or Fourth comment. Please ask your question over there, as I mentioned in the OP, I am not the original developer.
NOTE: For all those who are not aware, all AT&T ROMS run on the international version of the NOTE 2 (n7105). I am also running Jedi ROM, that is the smoothest ROM running android 4.1.2
electroking said:
Yes it is the latest version. Also sorry it should say the 05/07/2013. I will fix it when I get home.
I have a link to the AT&T post in the Third or Fourth comment. Please ask your question over there, as I mentioned in the OP, I am not the original developer.
NOTE: For all those who are not aware, all AT&T ROMS run on the international version of the NOTE 2 (n7105). I am also running Jedi ROM, that is the smoothest ROM running android 4.1.2
Click to expand...
Click to collapse
Thanks for your efforts mate, do you suggest installing this version of PA or the one from the AT&T thread? I have the N7105T model.
Cheers.
-P3P- said:
Thanks for your efforts mate, do you suggest installing this version of PA or the one from the AT&T thread? I have the N7105T model.
Cheers.
Click to expand...
Click to collapse
You're welcome, do not forget to thank the original developers.
I interchange between them, depending on which one is running the later version (between the download link I provided, and the one in the AT&T section). Because the porting of this ROM is not done by the official developer you will find that sometimes one updates their "download link" prior to the other.
what filesystems are supported on the microSD? thanks
Hi, I am from singapore, is this for at&t phones or can I stil use this rom with the starhub/singapore modem?
Hi, it should be okay since both phones shares the same hardware and OP uses the same model as us. Although the only problem is whether the future builds will be compatible with our model. There are some roms out there that aren't made for our model but works fine when its flashes but things got all wonky when a new build comes out. If you're looking for a rom that has the hybrid mode, Rootbox has that, along with Halo.
Sent from my GT-N7105 using xda app-developers app
Hi, I have no other problems on this Rom except for one. The sound replay and stuffs like that. Like when I'm trying to hear out some tones for my notifications, it doesn't play out any sounds. When I'm using zedge as well. Any idea what might be the cause and fix? Only sometimes I try closing and opening the app again or the system settings then it would work out somehow but most of the time the replay sounds just doesn't work. Please help
Does this ROM support the "One-Handed use" feature from stock as well as the s-pen?
electroking said:
I own an N7105 LTE on Telstra, Australia. Works Perfectly FINE... Follow Installation Steps
2) Install your relevant MODEM. I got mine from here:
http://forum.xda-developers.com/showthread.php?t=2031575
Click to expand...
Click to collapse
which specific modem do you use?
also, what version of JB-apps do you use. is it "pa_gapps-full-4.2-20130710-signed.zip"?
i'm using TWRP too, backing up my stock ROM now. downloading "pa_grouper-3.67-20130713.zip" atm.
thanks.

[ROM][UNOFFICIAL][CM12.1][5.1.1][VirginMobileUS][A5][single sim][6/1/2016 security]

Official nightlies aren't happening anymore,
so here's a more up to date build. Vanilla cm12.1 except for eri.xml/apn tweaks and binfmt_misc enabled in kernel.
Special for the a5_chl Virgin Mobile US Desire 816,
may work ok on other a5's too.
Note: a5_dug, a5_dwg dual sim telephony are not working correctly. buyer beware.
Flashes fine with official TWRP.
Official HTC firmware here:
http://www.htc.com/us/support/htc-desire-816-virgin-mobile/news/
I strongly suggest updating your firmware to htc lollipop with an official ruu or you may have hardware issues like touchscreen, wifi, and/or bluetooth problems. It might work with kitkat firmware though, and you are free to try if you want. Post results if you do.
It appears kitkat firmware can cause not only touch issues but wifi issues.
xXminiWHOOPERxX said:
Okay ,
Rom and firmware are two different things... inside OTA's it contains a firmware.zip at which updates bootloader, radio, etc.... so without taking firmware upgrades and just installing what's released on XDA will lead you to bugs other users don't have ..
For Example :
4.4.4 firmware will work with 5.0.2 fine for some users and some have to update too 5.0.2 for Wi-Fi to work...
But any Android version past 5.0.2 you need to have either lollipop firmware or marshmallow firmware in order for Wi-Fi to work...
Sent from my 831C using Tapatalk
Click to expand...
Click to collapse
Wipe cache, data, and system for clean flash.
Dirty flash not recommended. 5.0 gapps crash on 5.1
If you wanna try a dirty flash I recommend wiping system, cache, and dalvik cache, then your apps and some settings may survive.
Disclaimer: Void warranty, not responsible for anything, you know flashing is your choice and any damage is your own problem.
issues:
mobile data sometimes needs toggled to activate, using airplane mode on/off.
apparently the livedisplay function isn't working well ( maybe not at all)
as mentioned above, dual sim devices not fully functional.
I'm afraid that since I have a mostly working marshmallow build, that needs TLC and attention paid to it, that I can't justify putting any more time into cm12. So unless there security patches released or something, the 12/25 is the last cm12 build I'm releasing.
Download folder:
https://androidfilehost.com/?w=files&flid=45601
visual voicemail see here: http://forum.xda-developers.com/showpost.php?p=64395211&postcount=38
sultanxda's SnapdragonCamera is included as of 12/25 build. it seems to freeze on the first picture after installation but works ok after that once rebooted.
I'm leaving the link to the source built from the ROM standalone camera zip in case anyone needs it. Flash in recovery. If you flashed the one I ripped from the Yureka forum, flash this one over it.
You may have to clear its app data if flashing over, and it may freeze. The 12/25 ROM seems to get along OK with the camera after the first picture and a reboot if you really want the camera.
https://www.androidfilehost.com/?w=files&flid=46051
Source: official CM repo with these changes:
https://github.com/bigsupersquid/android_device_htc_a5
https://github.com/TheMuppets/proprietary_vendor_htc
https://github.com/bigsupersquid/kernel_htc_msm8974_arch_arm_configs_cm_a5_defconfig
https://github.com/bigsupersquid/frameworks_base_core_res_res_xml_eri.xml
https://github.com/bigsupersquid/vendor_cm_prebuilt_common_etc_apns-conf.xml
https://github.com/bigsupersquid/android_packages_apps_SnapdragonCamera
screenshot of interesting format of app drawer:
{
"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"
}
Thanks for continuing the builds! I'm flashing right now and will let you know how it works.
(Flashing on HTC A5_CHL Sprint Prepaid)
EDIT:
Everything seems to be running smoothly, and I haven't found any bugs. (I haven't tested cellular or data, just wifi)
Even though it is said it's for CHL, I would appreciate if someone would try it on UL version and post the results.
bonczas said:
Even though it is said it's for CHL, I would appreciate if someone would try it on UL version and post the results.
Click to expand...
Click to collapse
it's tweaked for chl, but the device code detects several varieties.
according to the zip updater script:
This package is for device: a5,a5tl,a5dug,a5dwg,a5chl,a5ul;
as people test them I can add to the OP.
I only have a chl myself.
How usable is this build? Would you recommend it for daily smartphone use? Or is this just a preview / proof of concept?
Thanks!
Is the dual sim problem on a5dug will ever be fixed on our phone or is just a cyanogenmod 12 problem that will never be fixed. I searched hours on google and didn`t find anything useful...
Shedal said:
How usable is this build? Would you recommend it for daily smartphone use? Or is this just a preview / proof of concept?
Thanks!
Click to expand...
Click to collapse
It works as well as any other CM 12.1 build I've run on a device. I haven't found any bugs yet, besides the wifi cutting out briefly once.
I had flashed on 816W dual sim ,Both sim couldn't be detected
@bigsupersquid is 320 DPI the standard for the HTC Desire 816, or is that just the default that CM applies? Just curious, because the UI elements seem much bigger in CM than stock.
Thanks.
@bigsupersquid
Thanks man! I've been running it for about 3 hours with no problems, and its nice to have a up to date secure version of CM. Thanks a bunch for your work!
Flashed it on a5dug and could not detect both sims. I really hope u could make it work for all variants. I have been using 5.1.1 as my daily driver for 2 months now and i love it.
Do MMS and Bluetooth work well on this? Every other version of CM I've tried, bluetooth turns off after an hour or two and not even a reboot will turn it on again.
@Icelus I can try turning on BT and seeing how long it will stay on if you want. Is there a better way to test?
Icelus said:
Do MMS and Bluetooth work well on this? Every other version of CM I've tried, bluetooth turns off after an hour or two and not even a reboot will turn it on again.
Click to expand...
Click to collapse
my mms is OK on virgin mobile, and bt seems OK. I'll leave it on a while, then try to pair stuff and toggle it on and off to let you know.
over two hours, bt still on, pairs/forgets/pairs again/ fine, toggles off/on and reconnects automatically.
anyone with hardware issues:
I had another user update their firmware to lollipop to get around touchscreen problems with this rom and it worked.
I will add that to the OP with more info from users to verify the firmware needs to be updated. My htc evo 3d is certainly picky about its firmware and rom combinations.
Bandit Development said:
@bigsupersquid is 320 DPI the standard for the HTC Desire 816, or is that just the default that CM applies? Just curious, because the UI elements seem much bigger in CM than stock.
Thanks.
Click to expand...
Click to collapse
according to pdadb.net,
Pixel density (dot pitch): 266.4 pixel/inch (0.09533 millimetre/pixel)
I haven't checked the original build.prop to see what htc set it at.
qaliza said:
Flashed it on a5dug and could not detect both sims. I really hope u could make it work for all variants. I have been using 5.1.1 as my daily driver for 2 months now and i love it.
Click to expand...
Click to collapse
crazybasss said:
Is the dual sim problem on a5dug will ever be fixed on our phone or is just a cyanogenmod 12 problem that will never be fixed. I searched hours on google and didn`t find anything useful...
Click to expand...
Click to collapse
while I'd like to help with that, but I don't have the hardware to test on; without that there's too much guesswork. Google isn't much help, implies RIL patch based on other phones with same issue. Sorry. I'll add the info to the OP though.
Shedal said:
How usable is this build? Would you recommend it for daily smartphone use? Or is this just a preview / proof of concept?
Thanks!
Click to expand...
Click to collapse
This seems stable to me, actually haven't had one random reboot yet, or other noticable hiccup. Way better than the kitkat I daily drivered on my old optimus v.
Now if I decide to play with marshmallow, and actually get it booting, that would be proof of concept/alpha most likely.
Does this have the issue where Bluetooth turns off randomly while on and it becomes unable to be reenable until reboot? Cuz that's my only issue with cm12 so far
Icelus said:
Do MMS and Bluetooth work well on this? Every other version of CM I've tried, bluetooth turns off after an hour or two and not even a reboot will turn it on again.
Click to expand...
Click to collapse
bigsupersquid said:
my mms is OK on virgin mobile, and bt seems OK. I'll leave it on a while, then try to pair stuff and toggle it on and off to let you know.
over two hours, bt still on, pairs/forgets/pairs again/ fine, toggles off/on and reconnects automatically.
anyone with hardware issues:
I had another user update their firmware to lollipop to get around touchscreen problems with this rom and it worked.
I will add that to the OP with more info from users to verify the firmware needs to be updated. My htc evo 3d is certainly picky about its firmware and rom combinations.
Click to expand...
Click to collapse
exProphecy said:
Does this have the issue where Bluetooth turns off randomly while on and it becomes unable to be reenable until reboot? Cuz that's my only issue with cm12 so far
Click to expand...
Click to collapse
I'm not having any bluetooth problems at all. but I haven't done much more than test it to be sure it works, either. I'll leave it on longer and see if it drops out.
bigsupersquid said:
I'm not having any bluetooth problems at all. but I haven't done much more than test it to be sure it works, either. I'll leave it on longer and see if it drops out.
Click to expand...
Click to collapse
I can't keep mobile data going...I'm on VM but apparently where I'm at the switching between 3G and 4G makes it angry...
Sent from my 710C using Tapatalk

[ROM][SM-G313HU] AOSP 5.1.1 and CM12.1 for Galaxy Ace 4

Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
General:
AOSP 5.1 and CM12.1 for Samsung Galaxy Ace 4 (SM-G313HU). Note that Google apps are not included.
What works:
Pretty much everything
What does not:
FM Radio (removed from the firmware)
Download:
Downloads moved.
CM12.1
AOSP
Google Apps
Screenies:
{
"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"
}
Sources:
Device tree
Kernel repo
Please report any bugs to this thread.
Thanks alot to TheNikiz for a device tree and helping me with some thingies.
Did you figure out the codec issues? For example the Facebook video playback?
Nikiz said:
Did you figure out the codec issues? For example the Facebook video playback?
Click to expand...
Click to collapse
Yeah, you need to patch frameworks_av like in cm12 to add YcbYCr color format, and add proper media_codecs.xml. Haven't tested facebook tho, but video recording/playing and apps like youtube work. Check out git repo.
Tho that routing still annoys crap outta me, it tries to add route to gateway, but fails, cause gw is in another network, we need to add static route to rmnet0 address instead, i tested adding it manually and it worked.
@itigr Thanks for the ROM but isn't there any possibility of getting the mobile data thing fixed permanently?
Also,ROM with pretty much everything working with tiltle[Experimental].
weird. @Nikiz how did you unlock the bootloader of the almost dead Trend 2 or it wasn't locked?
Edwin Hamal said:
@itigr Thanks for the ROM but isn't there any possibility of getting the mobile data thing fixed permanently?
Also,ROM with pretty much everything working with tiltle[Experimental].
weird.
Click to expand...
Click to collapse
No, at least not now. And i don't want to spend one more week figuring out why it doesn't work, i will probably pause dev for indefinite period 'coz i'm tired of this.
Yep, cause i messed with sources alot
Edwin Hamal said:
@Nikiz how did you unlock the bootloader of the almost dead Trend 2 or it wasn't locked?
Click to expand...
Click to collapse
Umm, what? The Trend 2 bootloader was never locked. (Well, it shows the invalid signature check, but still allows booting) I think you mixed it up with the Huawei Y5-project I have now. (Got the bootloader unlocked and a custom recovery running on it within 24 hours of owning it.. )
@itigr ok... but...
First of all AOSP sucks(It doesn't even have a file manager)
There's alot more bugs i.e
Wifi does't work (always shows exclamation even though the wifi is working good)
Calls doesn't end(mention about the work around for this too)
Last thing isn't there anyway that I can flash both ROM's by @Nikiz and you without editing things?
Coz having to switch recovery is really a hard task!
Edwin Hamal said:
@itigr ok... but...
First of all AOSP sucks(It doesn't even have a file manager)
There's alot more bugs i.e
Wifi does't work (always shows exclamation even though the wifi is working good)
Calls doesn't end(mention about the work around for this too)
Last thing isn't there anyway that I can flash both ROM's by @Nikiz and you without editing things?
Coz having to switch recovery is really a hard task!
Click to expand...
Click to collapse
Got the bootloader unlocked by just typing "fastboot oem unlock-go" into the terminal. I just made a minimal device tree for this phone, with the partition information, TWRP settings and the fstab-file. I just built it and I was surprised that it booted on the first try. All I had to do was to fix the fstab-file, change the pixel format and add couple of recovery settings to make it fully working. Building CM12.1 now. (Luckily there was couple of officially supported, similar Huawei devices, so I just copied bunch of code from there.. )
Nikiz said:
Got the bootloader unlocked by just typing "fastboot oem unlock-go" into the terminal. I just made a minimal device tree for this phone, with the partition information, TWRP settings and the fstab-file. I just built it and I was surprised that it booted on the first try. All I had to do was to fix the fstab-file, change the pixel format and add couple of recovery settings to make it fully working. Building CM12.1 now. (Luckily there was couple of officially supported, similar Huawei devices, so I just copied bunch of code from there.. )
Click to expand...
Click to collapse
Lucky for you that almost all Huawei are Snapdragon.
doesntexits said:
Lucky for you that almost all Huawei are Snapdragon.
Click to expand...
Click to collapse
Yeah, this processor is supported by AOSP too, so no patching needs to be done, which is nice. Currently I have only got to the boot animation. ADB doesn't work for some reason. (eng-build and insecure ADB)
Nikiz said:
Yeah, this processor is supported by AOSP too, so no patching needs to be done, which is nice. Currently I have only got to the boot animation. ADB doesn't work for some reason. (eng-build and insecure ADB)
Click to expand...
Click to collapse
Welcome to my world Now i'm still stuck at Samsung logo. adb shell works fine but logcat gives me a blinking cursor, ueventd.scx15.rc is included in out/target/vivalto3gvn/root. Idk the reason why it doesn't even gives me a boot animation. Tried stock init but it reboots straight to recovery mode. Now i wish i have a buddy to work with this phone.
Edwin Hamal said:
@itigr ok... but...
First of all AOSP sucks(It doesn't even have a file manager)
There's alot more bugs i.e
Wifi does't work (always shows exclamation even though the wifi is working good)
Calls doesn't end(mention about the work around for this too)
Last thing isn't there anyway that I can flash both ROM's by @Nikiz and you without editing things?
Coz having to switch recovery is really a hard task!
Click to expand...
Click to collapse
Welp aosp still isn't as bad, i used to use it with xposed on my old xperia Maybe at some time i will compile cm12.1 or AOSPA (or it's still dead?).
Wifi and calls work, maybe i uploaded an old zip, i was drunk as hell and can't recall it really lol. Reuploading right now, ETA: 40 mins.
Idk how do you want to flash two roms, i've heard it only supported on nexus and still has bugs..
Front camera video recording doesn't work....
Why is this faster than CM12.1?
I wonder why you prefer AOSP over CM though?
 @itigr
Codec issues has gone too.(I guess coz fb videos play now)
Edwin Hamal said:
Front camera video recording doesn't work....
Why is this faster than CM12.1?
I wonder why you prefer AOSP over CM though?
@itigr
Codec issues has gone too.(I guess coz fb videos play now)
Click to expand...
Click to collapse
No idea, i just kinda like pure android lol. Dunno how to fix front camera tho. I'm compilling cm12 now and omni 6.0 tomorrow.
Great but CyanogenMod is also stock android isn't it? with added features which stock lacks.
By the way you're compiling CM12 or CM12.1?
Omni?! Guess you're die heart fan of stock Android! Pure Stock Android rather! @itigr
Edwin Hamal said:
Great but CyanogenMod is also stock android isn't it? with added features which stock lacks.
By the way you're compiling CM12 or CM12.1?
Omni?! Guess you're die heart fan of stock Android! Pure Stock Android rather! @itigr
Click to expand...
Click to collapse
Yeah. CM12.1, i already compiled it and "fixed" mobile data (not really but now you don't have to mess with scripter since workaround is added to boot image). Uploading it now, 50 minutes left. Only thing is left to fix is offline charger but i got no idea how.
Not really
The reason i am compiling omni because i already had it downloaded, i would compile cm13.0 but i'm on my 2nd house now and internet here is crappy + i also heard it's not complete yet and compilinig can fail sometimes. It took me around 2 days to download cm12.1 source with a lot of disconnects.
Added cm12.1 and pushed data fix and patches to github.
itigr said:
Added cm12.1 and pushed data fix and patches to github.
Click to expand...
Click to collapse
Installed CM12.1 and there's one more problem.
Don't known if I'm only one who has this issue
but after some time device doesn't detect any
Sim cards till a reboot.(Faced this in the AOSP as well)
Has it happend to you?
Edwin Hamal said:
Installed CM12.1 and there's one more problem.
Don't known if I'm only one who has this issue
but after some time device doesn't detect any
Sim cards till a reboot.(Faced this in the AOSP as well)
Has it happend to you?
Click to expand...
Click to collapse
I was testing it for 2 days and have never noticed it.
Did you wipe data/cache/system after flashing?
itigr said:
I was testing it for 2 days and have never noticed it.
Did you wipe data/cache/system after flashing?
Click to expand...
Click to collapse
Nah,just did wipe to install new ROM! using
philz.I think it does wipe everything required...
Edit:After flashing???
Edit:Figured out that decive doesn't detect sim card when I soft reboot.

[Unofficial] Cyanogenmod 14.1

CM14.1 is here for the LS990, aka the Sprint LG G3.
This is unofficial until one framework change gets merged in for fixing LteOnCdma support. Once that merge happens, we'll get nighties.
This should have fully working modem, nfc and all the things you've come to enjoy. World phone mode is enabled, but I do not have an activated GSM sim to fully test the GSM side.
Instructions
This has only be validated on ZVC or newer firmware.
Download cm-14.1, and gapps. Put them on your sdcard, reboot to recovery. Flash, and enjoy!
The latest will be available at:
http://downloads.codefi.re/shelnutt2/g3/ls990/cm14_1/
Gapps:
OpenGapps:
http://opengapps.org/?api=7.1&variant=nano
Click to expand...
Click to collapse
Known Issue
None!
Click to expand...
Click to collapse
Change Log
Click to expand...
Click to collapse
Special Thanks To!
None of this would be possible without the following people:
invisiblek
Kasual52e
rashed
Click to expand...
Click to collapse
Source
http://github.com/CyanogenMod
Click to expand...
Click to collapse
Is the speakerphone Echo fixed?
There is a setting in stock phone "call settings" that has to be changed in order to keep it from happening.
In the stock "call settings" you have to turn off noise suppression and turn on voice enhancement:
{
"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"
}
I think all of the source built Roms are built with this setting set to it's default settings which causes the echo even in the stock Roms until it's changed to the above. (The pic is from MM but it's prevalent in the Nougat Roms as well).
People do a lot to try to fix the problem, change: mixer_paths.xml to no avail. turning the volume down, changing the Mic settings doesn't take the problem away.
I would love to see this fixed. I can't use any of the source built Roms because of it. (I can't stand to put the phone to my head, I have to have speakerphone).
Anyway hope this gives the right people the insight to fix the problem.
Thanks for taking the time to bring us these awesome builds.
? Sent from DjRobBlaze's VS985 ? Rockin' ? Fulmics 6.6 ? using Tapatalk. ? ®
Shelnutt2 said:
CM14.1 is here for the LS990, aka the Sprint LG G3.
This is unofficial until one framework change gets merged in for fixing LteOnCdma support. Once that merge happens, we'll get nighties.
This should have fully working modem, nfc and all the things you've come to enjoy. World phone mode is enabled, but I do not have an activated GSM sim to fully test the GSM side.
Click to expand...
Click to collapse
That framework change you mentioned to fix LteOnCdma support, is that in this release and you are waiting for it to be merged with CM official?
Just wanted to thank the OP, this rom is working perfectly (dec 15 build). It's actually more stable than the cm14.1 nightlies for the d851 G3 (T-Mobile). I've had no sim card or data issues of any kind. Miracast works great as well.
bavarianblessed said:
That framework change you mentioned to fix LteOnCdma support, is that in this release and you are waiting for it to be merged with CM official?
Click to expand...
Click to collapse
It is included in these unofficial builds. It is awaiting merge upstream, https://review.cyanogenmod.org/#/c/176865/
in light of the news today, I'm guessing the ls990 is never getting merged into the nightlies, and we might be looking at a whole new rom in the future (lineage).
its hard to believe really... cyanogenmod seemed like it was poised to take over... its been my favorite rom for about 3 years now, and was really starting to get good in this 14.1 build (miracast finally works!)
i guess just thanks for building these, not sure where we all go from here...
Whatever happens there will continue to be unofficial builds of either cm or lineage until we are able to get the necessary changes merged to make stable official builds
Engineers running businesses get owned by business people running businesses. From 10k km, it seems the cyanogen Corp got edged out by 'partners' with less then admirable ethics and motives. The code is still ours, thanks to GPL. Our community will continue to build and rebuild. Kondik has learned to play hardball the hard way, and will hopefully dust himself off and come back even stronger. The hope for a mainstream android fork continues... and it's likely to keep on that way just like 2017 is going to finally be the year of desktop Linux. In the mean time, thank and donate to our developers, their blood oils the machinery of free software.
Rooted ZVC Firmware?
Where can I find rooted ZVC Firmware? I tried this with the rooted ZVB firmware at https://forum.xda-developers.com/sp...990-zvb-root-method-zvb-rooted-stock-t3211878, but after rebooting, it doesn't look like I have root privileges.
rogerdc said:
Where can I find rooted ZVC Firmware? I tried this with the rooted ZVB firmware at https://forum.xda-developers.com/sp...90-zvb-root-method-zvb-rooted-stock-t3211878, but after rebooting, it doesn't look like I have root privileges.
Click to expand...
Click to collapse
Rooted ZVC:
http://forum.xda-developers.com/sprint-lg-g3/development/barecee-zvc-t3257826
Straight stock partitions http://downloads.codefi.re/autoprime/LG/LG_G3/LS990/stock_partitions/ZVC
There's a nice little modem/rpm/tz flasher zip in the ZVB folder there that can be commandeered to flash the relevant ZVC partitions with a little zip hacking.
just flashed this after failing at the Resurection and Cypher N roms. I couldnt get data, cell, text or any networks to work.
This worked fine out of the box. Awesome! Nice and smooth. No force closes. Bluetooth appears to be nice and stable at least on my headphones which are a foot away from me. Havent tried my car yet.
On a side note, the whole reason I was trying to upgrade to something nougat based was to get the google assistant working. There appears to be a workaround if you are not a pixel phone listed here. https://forum.xda-developers.com/android/software/guide-how-to-enable-google-assistant-t3477879
Then I started reading and it doesnt appear the g3 is on its list of supported phones for this. Has anyone tried it yet? Does it work, and if so, what technique did you use?
CMILD561 said:
On a side note, the whole reason I was trying to upgrade to something nougat based was to get the google assistant working. There appears to be a workaround if you are not a pixel phone listed here. https://forum.xda-developers.com/android/software/guide-how-to-enable-google-assistant-t3477879
Then I started reading and it doesnt appear the g3 is on its list of supported phones for this. Has anyone tried it yet? Does it work, and if so, what technique did you use?
Click to expand...
Click to collapse
You can get Assistant working on the G3... I had it working with AICP and I'm sure it will work with CM but I haven't reinstalled it. The big issue for me was loosing "OK Google" Hotword. I followed the instructions here... https://forum.xda-developers.com/android/apps-games/google-pixel-experience-launcher-dialer-t3478907
Also, if anyone is interested, CrazySuperKernel is working very well with this ROM.... https://forum.xda-developers.com/lg-g3/development/kernel-crazysuperkernel-v1-t3521121
Matteo1219 said:
Also, if anyone is interested, CrazySuperKernel is working very well with this ROM.... https://forum.xda-developers.com/lg-g3/development/kernel-crazysuperkernel-v1-t3521121
Click to expand...
Click to collapse
Thanks, i will give this ROM and Kernel a try once i get my replacement battery
Installed this ROM and so far it is pretty good! Thanks to the dev for the time and effort to put out a good system unlike some of the others who are posting N ROMs that do not work with the phone (ie data, mms, etc). I hope to see further development of this ROM but that might be difficult with CM getting out of the custom OS business.... Great work and thanks again!
len207 said:
Installed this ROM and so far it is pretty good! Thanks to the dev for the time and effort to put out a good system unlike some of the others who are posting N ROMs that do not work with the phone (ie data, mms, etc). I hope to see further development of this ROM but that might be difficult with CM getting out of the custom OS business.... Great work and thanks again!
Click to expand...
Click to collapse
keep an eye on this page, we're supposed to start seeing official builds this weekend (hopefully today)
https://download.lineageos.org/
chat:
https://webchat.freenode.net/?channels=lineageos
The great @Shelnutt2 has continued posting updates for the ls990.... http://downloads.codefi.re/shelnutt2/g3/ls990/laos14_1
I got stuck on "Tap & Go" during setup... Don't have another device to try this and it's not letting me skip it
Matteo1219 said:
The great @Shelnutt2 has continued posting updates for the ls990.... http://downloads.codefi.re/shelnutt2/g3/ls990/laos14_1
Click to expand...
Click to collapse
Is data texting mms working on sprint?? Still domestic roaming issue??
Matteo1219 said:
The great @Shelnutt2 has continued posting updates for the ls990.... http://downloads.codefi.re/shelnutt2/g3/ls990/laos14_1
Click to expand...
Click to collapse
latest vesion of that rom still switches from digital roaming to sprint. i get lte texting on digital roaming and calls on sprint (
erik077 said:
I got stuck on "Tap & Go" during setup... Don't have another device to try this and it's not letting me skip it
Click to expand...
Click to collapse
With a clean install? Which GApps package are you using?

[Discontinued]Dirty Unicorns[UNOFFICIAL][09.12.2018][S9/S9+/N9]

{
"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"
}
Dirty Unicorns Semi GSI for Samsung Devices
By CodeFox & OpenSauce9810​
What is this?
This is a Semi Generic System Image. That means it's a generic system image that's been optimized as much as possible for our Samsung Devices.
How the heck do I flash this?
It's slightly different than flashing a zip, so here's what you need to do.
Download the image file
UNCOMPRESS IT .xz is a compressed file. So you can uncompress it with zarchiver from the playstore or 7zip/winrar.
Flash the ARH6 Vendor Image to your Vendor Partion from TWRP (Press the Install Image button at the bottom right of where you usually select a flashable zip)
Flash the System Image to your System Partition
Optional if you want root (but reccomended): Reboot to recovery again then flash your choice of Magisk. I use 17.1 as I can get galaxy wear to work with that version.
Reboot your device and you should be good to go! No need to flash gapps as they're included.
03.12.2018
Initial Release
05.12.2018
Updated sources to 9.0 r21 release. (December Security Patch)
Gapps included, (dialer and messenger also included so you won't start without a phone or sms app)
Bootanimation changed to reduce boot times
Tweaks to ambient play ticker so it clears when you clear media notifications
Further performance tweaks thanks to @malinathani animations transition smoother now.
09.12.2018
Keystore fixed - You can now use fingerprint within apps (once you've passed safetynet with hideprops module)
Screenshots
[/YOUTUBE]
Video Review Thanks to @vmb265
Click here to view video review
Downloads:
System Image GDrive
Vendor Image
Support & Feedback
I'm happy to provide as much support as possible. Through XDA here or you can get in touch with me and the rest of OpenSauce9810 + our community at our Telegram group here
Our telegram also has a bot which will provide you with the latest builds.
If you're happy with the work I've put into this (endless amounts of hours trying to perfect GSI building) then a simple thanks here or clicking the thanks button below is very appreciated!
Credits and Thanks
Dirty Unicorns (The best ROM ever)
Ivan - Thank you for helping me out every now and then when I'm being stoopid.
Rainbow_Dash - Pointing me in the right direction with regards to fixing the errors.
malinathani- For the UI Jank Fix (Used widely in other GSI's now)
GRaf - best tester
The guys in telegram as a whole, thank you for the feedback and support.
phhusson - thank you for your work on project treble.
XDA:DevDB Information
[Discontinued]Dirty Unicorns[UNOFFICIAL][09.12.2018][S9/S9+/N9], ROM for the Samsung Galaxy Note 9
Contributors
CodeFox, Rainbow_Dash, malinathani, phhusson, Dirty Unicorns, Ivanmeler,
Source Code: https://github.com/DirtyUnicorns/android_manifest
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Vendor ARH6
Based On: Dirty Unicorns
Version Information
Status: Stable
Current Stable Version: 1
Stable Release Date: 2018-12-03
Created 2018-12-03
Last Updated 2019-01-07
First! lol
Still on stock ROM but i'd love to flash some Dirty Unicorn goodness.
Any bugs to be aware of?
PieceofSlice said:
First! lol
Still on stock ROM but i'd love to flash some Dirty Unicorn goodness.
Any bugs to be aware of?
Click to expand...
Click to collapse
Fingerprint doesn't worth within apps. Other than that though everything's pretty much good I think.
@CodeFox Thanks for this rom. I used to make my own Du builds for nexus device. It was sucha an amazing experience.
Would love to try DU for note 9.
Just a couple of questions -
- Does any of the Touch wiz features like, pen related features ( bluetooth control work ) ?
- Phone related features by flashing csc files for specific network still doable ?
Techvir said:
@CodeFox Thanks for this rom. I used to make my own Du builds for nexus device. It was sucha an amazing experience.
Would love to try DU for note 9.
Just a couple of questions -
- Does any of the Touch wiz features like, pen related features ( bluetooth control work ) ?
- Phone related features by flashing csc files for specific network still doable ?
Click to expand...
Click to collapse
Pretty much all Samsung features are lost on AOSP however there are a lot of alternative apps that can "revive" the Spen.
PieceofSlice said:
Pretty much all Samsung features are lost on AOSP however there are a lot of alternative apps that can "revive" the Spen.
Click to expand...
Click to collapse
That is what I thought... Thanks for answering
I flashed this twice. Both times I couldn't get the setup wizard to show up. There are no gapps in the app drawer either.
Can someone confirm? I'm pretty sure I did everything right with the flashing process..
Nasty_z said:
I flashed this twice. Both times I couldn't get the setup wizard to show up. There are no gapps in the app drawer either.
Can someone confirm? I'm pretty sure I did everything right with the flashing process..
Click to expand...
Click to collapse
Gapps aren't included. You'll need to download a package from opengapps. Arm64 9.0. I recommend nano.
Don't forget to download a phone and SMS app too.
I copied and pasted from my PE thread so I need to take out the gapps included part. My bad, sorry about that.
CodeFox said:
Gapps aren't included. You'll need to download a package from opengapps. Arm64 9.0. I recommend nano.
Don't forget to download a phone and SMS app too.
I copied and pasted from my PE thread so I need to take out the gapps included part. My bad, sorry about that.
Click to expand...
Click to collapse
No problem. Also, the .xz file needs to be extracted and the IMG file in it needs to be flashed to the system partition. I noticed you haven't included this in the flashing instructions
Thank you for the ROM btw
Nasty_z said:
No problem. Also, the .xz file needs to be extracted and the IMG file in it needs to be flashed to the system partition. I noticed you haven't included this in the flashing instructions
Thank you for the ROM btw
Click to expand...
Click to collapse
I'll update the posts tomorrow. I'm looking after 4 threads at the minute as there's 2 more in the s9 forum ? it's proving to be challenging haha.
You're welcome. This one is a lot smoother than pixel experience.
CodeFox said:
I'll update the posts tomorrow. I'm looking after 4 threads at the minute as there's 2 more in the s9 forum ? it's proving to be challenging haha.
You're welcome. This one is a lot smoother than pixel experience.
Click to expand...
Click to collapse
Haha I can understand. Btw I just restored the galaxy wearable, Samsung accessory service, gear s plugin and Samsung health using titanium backup and I didn't have to reset my gear. It just connected right away and it's working fine now. The backup I made using titanium backup was on Pixel Experience right before I flashed this rom.
I hope it doesn't do a freak reset later.. Too good to be true? :silly:
Nasty_z said:
Haha I can understand. Btw I just restored the galaxy wearable, Samsung accessory service, gear s plugin and Samsung health using titanium backup and I didn't have to reset my gear. It just connected right away and it's working fine now. The backup I made using titanium backup was on Pixel Experience right before I flashed this rom.
I hope it doesn't do a freak reset later.. Too good to be true? :silly:
Click to expand...
Click to collapse
Hmm thanks for letting me know. I'll give it a go. I really do need to start using titanium backup more often. I usually have problems with apps not notifying me of new posts anymore or them being stuck in the past though.
CodeFox said:
Hmm thanks for letting me know. I'll give it a go. I really do need to start using titanium backup more often. I usually have problems with apps not notifying me of new posts anymore or them being stuck in the past though.
Click to expand...
Click to collapse
I agree with you on those issues. Apps like whatsapp are affected with the delayed notifications so I avoid backing it up with titanium backup. Still, the fact that Gear doesn't need to be reset is a big thing. I even toggled Bluetooth on and off multiple times and it still connects to it without any prompt for reset
CodeFox said:
I'll update the posts tomorrow. I'm looking after 4 threads at the minute as there's 2 more in the s9 forum it's proving to be challenging haha.
You're welcome. This one is a lot smoother than pixel experience.
Click to expand...
Click to collapse
Damn just Flased PixelExperience last night. Will definitely be installing this. I found pe was smooth enough so the fact that this is a lot smoother is really nice. Thanks mate
Nasty_z said:
I agree with you on those issues. Apps like whatsapp are affected with the delayed notifications so I avoid backing it up with titanium backup. Still, the fact that Gear doesn't need to be reset is a big thing. I even toggled Bluetooth on and off multiple times and it still connects to it without any prompt for reset
Click to expand...
Click to collapse
The ability to restore gear with titanium is something new ... I could not do that till very recently but last week when I did a restore, there was no need to reset the watch and I was amazed..
Techvir said:
The ability to restore gear with titanium is something new ... I could not do that till very recently but last week when I did a restore, there was no need to reset the watch and I was amazed..
Click to expand...
Click to collapse
Glad to know it's not just me
New build released. see OP for details.
CodeFox said:
New build released. see OP for details.
Click to expand...
Click to collapse
You're on fire! Thanks
i love dirty so much
great to see this
Hello there. Iam new to. Gsi roms. Needed to ask the flashing steps. Iam on light rom right now with dual sim model.
1. In twrp clear everything. Cache data system
2. Flash vendor image
3. Flash system image
So i was able to boot this rom and everything was working included dual sim. then i downloaded viper for android ,flashed in magisk, restarted and kept in boot loop since.

Categories

Resources