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.
Related
{
"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"
}
Welcome everyone once again to a brand new Android. Here you will find unofficial builds for LiquidSmooth v4.0 running Android 5.0 Lollipop. Bare in mind that these are currently in the ALPHA stage, so expect bugs here and there and things to be a little off. This is early in development and may or may not be daily driver ready yet. And now, on with the show.
Click to expand...
Click to collapse
DISCLAMER
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.
Click to expand...
Click to collapse
LiquidSmooth is an aftermarket firmware based on the Android Open Source Project.
Dedicated to providing users with smooth, stable and fast ROMs. A Lightweight modified AOSP base, and then add the features you crave!
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device.
We ask that you do your part to know your device and know how to recover from problems before you flash!
Code:
[URL="https://github.com/LiquidSmooth"]LiquidSmooth Github[/URL]
Code:
You can download the latest build from [URL="https://www.androidfilehost.com/?fid=95832962473398652"][COLOR="Blue"]]RIGHT HERE[/COLOR][/COLOR][/URL] (Current Build: 12/06 )
Gapps can be found [URL="https://www.androidfilehost.com/?fid=95832962473398367"][COLOR="Blue"]here[/COLOR][/URL] thanks to @rogersb11
INSTALLATION INSTRUCTIONS
1) DO A BACKUP!
2) If you haven't prior to this step, flash the Shift Eternal CM12 kernel, then reboot recovery.
3) Factory Reset, Wipe Cache, Wipe Dalvik.
4) Wipe System
4) Flash ROM then flash Gapps.
5) Reboot and enjoy!
Also note that the initial boot takes a good amount of time. Upwards of 10 minutes in some cases. Just be patient when you get ready to boot into the system. It will eventually start up.
IMPORTANT NOTE:
You must be on a Lollipop compatible kernel and recovery for this to flash. Currently, the only one available is the Shift Eternal CM12 kernel from @rogersb11. You can download it here. This ROM package contains the same kernel so you will not have to reflash it after flashing the ROM. Questions related to the kernel can be directed to this thread.
You will not have a keyboard upon the initial boot. Skip through the initial setup process then do the following:
Go to Settings>Language and Input
Select the current keyboard.
A pop up will then come up and you need to flip the hardware switch in the top right corner to on.
After this you can then go through with signing in with your account, setting up wifi, etc.
Please remember that these are UNOFFICIAL ALPHA BUILDS. This meaning nobody from the LiquidSmooth team should be expected to help you if you run into any issues. Bugs should be reported to THIS THREAD ONLY. I will do my best to address and fix them as I can. I'm not a master developer, just a builder. But I am learning, and I will try my best to track down fixes to relevant bugs.
Click to expand...
Click to collapse
KNOWN ISSUES
As reported by @rogersb11 in his CM12 thread, "If you don't have WiFi on the device will reboot upon going to sleep so LEAVE THE WIFI ON." This is a Lollipop bug in general, and currently has no fix.
SPECIAL THANKS
Special thanks to the entire LiquidSmooth team for building this awesome ROM. I just compile it from source for this device and the ROM would not be here without their dedication and hard work to provide it.
Special thanks also once again to @rogersb11 for his help and guidance and tireless work to bring the device tree up to be ready for Android 5.0 ... Seriously, this dude has coded his fingers to the bone to make this a reality. I wouldn't have this thread up and going already without him. So be sure to let him know how thankful you are for his work to keep this device alive.
XDA:DevDB Information
Unofficial LiquidSmooth v4.0 for the SGH-I777/959G, ROM for the AT&T Samsung Galaxy S II SGH-I777
Contributors
TheGeekyNimrod, rogersb11
Source Code: https://github.com/LiquidSmooth/android
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.0.x
Version Information
Status: Alpha
Current Beta Version: LiquidSmooth v4.0
Beta Release Date: 2014-12-06
Created 2014-12-07
Last Updated 2014-12-07
RESERVED
Reserved one more just because
TheGeekyNimrod said:
Reserved one more just because
Click to expand...
Click to collapse
Thanks for all the hard work. Just a quick question. I assume this isn't happening to everyone, but Google Play Services crashes, not allowing me to create my backup account. Does the same on the cm12 build.
omar71693 said:
Thanks for all the hard work. Just a quick question. I assume this isn't happening to everyone, but Google Play Services crashes, not allowing me to create my backup account. Does the same on the cm12 build.
Click to expand...
Click to collapse
Hmm. I'm not sure. Haven't had that issue. A guess says it could be the Gapps, but I can't say that for sure though because I tested with different Gapps than the ones listed. Have you tried going back and wiping Dalvik and reinstalling Gapps?
Sent from my SAMSUNG-SGH-I747
TheGeekyNimrod said:
Hmm. I'm not sure. Haven't had that issue. A guess says it could be the Gapps, but I can't say that for sure though because I tested with different Gapps than the ones listed. Have you tried going back and wiping Dalvik and reinstalling Gapps?
Sent from my SAMSUNG-SGH-I747
Click to expand...
Click to collapse
Yeah, I actually did. I'm going to try some other things throughout the day and report back.
OMG, I can't believe there is ANOTHER lollipop build for the s2 . Oh BTW where you listed me as a contributer if you remove the @ before my username it will link me correctly. You don't need that on DevDB. Just edit profect at the top and then it automatically links the username without the @ in those contributor boxes
omar71693 said:
Thanks for all the hard work. Just a quick question. I assume this isn't happening to everyone, but Google Play Services crashes, not allowing me to create my backup account. Does the same on the cm12 build.
Click to expand...
Click to collapse
Yah, I'm having the same google play services FCs. I also tried bpear's Lollipop Gapps and that didn't work either . . .
NOTE: I did have the same problem on @rogersb11 Cm12 build too
I tested this with the 5.0 gapps from here. But if you try it, you will have to strip a few unneeded apps out of it for the sake of internal storage space. I can't remember exactly which ones I pulled out of it, but you can pretty much just use Google Play, Play Services, and Google Services Frameworks, and download the rest from the PlayStore
rogersb11 said:
OMG, I can't believe there is ANOTHER lollipop build for the s2 . Oh BTW where you listed me as a contributer if you remove the @ before my username it will link me correctly. You don't need that on DevDB. Just edit profect at the top and then it automatically links the username without the @ in those contributor boxes
Click to expand...
Click to collapse
Got it. I'm really not sure I like how the whole DevDB thing works. Should have just started a regular thread
I may possibly have another build out tomorrow with a few minor tweaks and a little overhaul to the UI. I don't know about everyone else, but I don't like the dark background of, say, the settings app. I'll be working on this and a few minor things tomorrow.
Sent from my SAMSUNG-SGH-I747
I haven't been able to get a working system. It usually hangs on the boot animation (animation freezes). Sometimes it gets to the optimizing apps screen, but it will hang there too. However, if I do NOT flash gapps, it's able to boot, but then hangs on the welcome screen (it freezes and doesn't accept any input). Between failed boot attempts, I'll wipe everything or even go as far as reflashing.
Any ideas?
sciguy125 said:
I haven't been able to get a working system. It usually hangs on the boot animation (animation freezes). Sometimes it gets to the optimizing apps screen, but it will hang there too. However, if I do NOT flash gapps, it's able to boot, but then hangs on the welcome screen (it freezes and doesn't accept any input). Between failed boot attempts, I'll wipe everything or even go as far as reflashing.
Any ideas?
Click to expand...
Click to collapse
Don't bother wiping everything.. Tried that two different times, still having the same results as you. I reverted back to KK and I'm just gonna wait for another build.
Sent from my SGH-I777 using XDA Free mobile app
Remember these are alpha builds. While I haven't had that issue with it yet, doesn't mean it won't happen for others. On mine, once I got to the setup screen I had to reboot the first time, then it allowed me to skip through until I was able to enable the keyboard. And it worked fine after that.
It will stabilize as time goes by for sure.
Sent from my SAMSUNG-SGH-I747
I had hoped to have another build out today, but I had a learning curve to get through first. But now that I have learned, should be late tonight or tomorrow. Mainly UI fixes, maybe a tweak or two elsewhere.
Sent from my SAMSUNG-SGH-I747
Finally! Android L for my GS2! Now to wait for an at&t GS4 custom Lollipop ROM.
[Q] About booting this ROM
When I flash the shift eternal kernel does it give me the right clockwork mod recovery I need to flash the rom? If not,where can I download it?
StoneyJSG said:
When I flash the shift eternal kernel does it give me the right clockwork mod recovery I need to flash the rom? If not,where can I download it?
Click to expand...
Click to collapse
It comes with PhilzTouch which is very a custom recovery based on CWM. It will be the right version for you to flash this and also the version and kernel that the ROM will be running.
Sent from my SAMSUNG-SGH-I747
Was hoping to have a new build posted today, but there are a few too many quirks with it for me to feel comfortable putting it out there. It boots, but there's a few things going crazy. I do believe I can get it worked out though, and will try to get another build done and put out tonight or tomorrow.
Biggest change right now is that I have reverted the Material Dark theme in favor of the Material Light theme that Lollipop is more known for right now. In the future, according to one of LS's lead developers, there will be a switch to go between the two.
Anyhoo, carry on.
My internal storage is not working. Google play services not working. Browser is also not working. Unable to install any app at all. Very nice rom though. Once a stable version is released i will use it as daily driver.
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
MOD EDIT: THREAD CLOSED PER OP REQUEST
Mods: Feel free to lock this thread. I'm done with this. Reasoning below.
Alright well, it was cool. I didn't realize how much went into ROMs [development]. I came into this way over my head and didn't do the proper bug checking before posting it. This was a learning experience for me, and I thought I had this figured out. Oops. I'm going to continue working with ROM source code and expanding my knowledge of this, but it'll be all a personal, private project. Thanks to the community for all of the guides they've posted on this site, and I hope one day I can do something meaningful for this community.
If you really want to run a pure AOSP ROM, you should try @freak97's master branch builds. His has the Verizon call audio issue just as this one does, and neither of us seem to know why that is, but hopefully he figures it out. Fair warning about his builds though, Netflix doesn't work on his ROM (he's probably missing the vendor files which are on this ROM which allow Netflix to work, because DRM), and the package installer will force close if you try to install an APK from outside of the Play Store.
Click to expand...
Click to collapse
{
"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"
}
This is stock AOSP from the Google repos. It contains no extra features, other than the extremely small list below. Any additions to these builds will be purely for compatibility and to make the device easier to use (ex. Enabling tethering). I intend to keep this updated with each of the new releases which appear.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Then cry. Then laugh more.
*/
What is "Clean Whale"?
Clean Whale is a ROM for the Google Nexus 6! Why the name? Because it's essentially pure AOSP running on the Nexus 6. Clean Android, Nexus 6 (shamu). Clean Whale. Why did I make a name for it if it's just AOSP? Because I needed a name for the Github repo. Deal with it.
Features
As stated above, this is pure AOSP with minimal changes. Here's what I've done:
Enabled Tethering
MultiROM support
Encryption isn't forced
Stock AOSP boot animation
Unrooted (also no Busybox. Just install it with an app.)
Yeah, that's literally it.
Kernel
This ROM uses the stock AOSP kernel from Google. The only thing added to it is the kexec-hardboot patch for MultiROM support. Yes, you can use MultiROM with this as a primary or secondary. Enjoy.
Changelog is in second post
Requirements:
Unlocked bootloader
The latest version of TWRP
Install Instructions:
Download the ROM.
Boot into TWRP make backup, and wipe (System, Data, Cache)
Flash the ROM
Flash SuperSU and/or GApps if you wish to use them.
Boot up and enjoy pure AOSP!
NOTE: First boot and signing in (if using GApps) may lag a little bit. Not much I can do about that, sorry. It'll go away pretty quick (if you really don't want to deal with it, reboot immediately after first boot).
Root
As stated above, this doesn't come with root OR Busybox. Why? Becuase neither are included in the source code, and I want this to be as close to the original source as possible. You can get root by flashing SuperSU (I've only tested the latest BETA version) and you can get Busybox by installing it with an app from the Playstore (requires root).
Downloads
Latest - Clean Whale 1.1 (AOSP 6.0.1_r46) [NO LONGER UPDATED]
All releases (my AFH folder) [NO LONGER UPDATED]
I have extremely slow upload speed, so I upload new releases overnight while I'm asleep. If you wish to check if I've updated this to a new revision of 6.0.1, you can view my AFH folder here. It'll appear there before it does in the thread.
Recommend (and tested) GApps
BaNkS Dynamic GApps
SuperSU
SuperSU BETA
SuperSU Stable
Bugs/Issues
Verizon call audio is broken - Currently working on this.
You may get "Error 7: System partition has unexpected contents after OTA update" when flashing. 1.1 should fix it. If you get this error when flashing, please report it here and provide a recovery.log [Fix attempted]
I would just like to take a minute to say thank you to @fhem @Scott for their amazing work with their threads which teach the community about how to download and compile a ROM from source. They're the reason this is here, and they're the reason I've decided to start working with custom ROM source code. This is my first experience working with Android in this way, and I have them to thank. Also, since this is my first experience I may very well get some things wrong and/or manage to break this. If that happens, I'm sorry. I'm still learning.
Thank you all for this wonderful community, and I hope one day I can really get into true ROM development
XDA:DevDB Information
Clean Whale, ROM for the Nexus 6
Contributors
ryanguy426
Source Code: https://github.com/CleanWhale
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Based On: AOSP
Version Information
Status: Abandoned
Current Beta Version: 1.1
Created 2016-06-13
Last Updated 2016-06-18
Changelog
Version 1.1 - June 16, 2016
Call audio is still broken, working on it right now.
Attempted to fix "Error 7" when flashing ROM in recovery
If you encounter "Error 7" when flashing, PLEASE provide a recovery.log when you report it. There's nothing I can do otherwise.
Version 1.0 - June 12, 2016
Initial release
Install may fail if you flash this, try 1.1 instead.
First
Sent from my Nexus 6 using XDA-Developers mobile app
ryanguy426 said:
I would just like to take a minute to say thank you to @fhem and @Scott for their amazing work with their threads which teach the community about how to download and compile a ROM from source. They're the reason this is here, and they're the reason I've decided to start working with custom ROM source code. This is my first experience working with Android in this way, and I have them to thank. Also, since this is my first experience I may very well get some things wrong and/or manage to break this. If that happens, I'm sorry. I'm still learning.
Click to expand...
Click to collapse
Thanks for kind words!!
It's always good to see new work. Welcome aboard and please keep it going.
I'm going to try this. I'm a fan of minimalist roms. Thanks for sharing it
Sent from my Nexus 6 using XDA-Developers mobile app
Count me in.
Sent from my Nexus 6 using XDA-Developers mobile app
I got error 7 when trying to install. Tried twice
Sent from my Nexus 6 using XDA-Developers mobile app
clippy83 said:
I got error 7 when trying to install. Tried twice
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
And what did the error say?
Great job. Everything works except Verizon call audio is broken (similar to Freak97 AOSP version). Very fast and slim. I like it overall :good:
clippy83 said:
I got error 7 when trying to install. Tried twice
Click to expand...
Click to collapse
Take a screenshot in TWRP and post it here please.
HueyT said:
Great job. Everything works except Verizon call audio is broken (similar to Freak97 AOSP version). Very fast and slim. I like it overall :good:
Click to expand...
Click to collapse
Wasn't aware of that, I don't normally get phone calls. I'll see what I can do about it.
I've also downloaded two different times in case of bad download & am also getting the error 7 msg. Also on latest twrp & full wipes both times.
rp076 said:
I've also downloaded two different times in case of bad download & am also getting the error 7 msg. Also on latest twrp & full wipes both times.
Click to expand...
Click to collapse
Same message I got thanks for posting haven't had a chance to post a screenshot
Sent from my Nexus 6 using XDA-Developers mobile app
rp076 said:
I've also downloaded two different times in case of bad download & am also getting the error 7 msg. Also on latest twrp & full wipes both times.
Click to expand...
Click to collapse
Alright, thanks. Looking into it.
I'm booting into Ubuntu now, I'll see if I can figure this out but I'm not experiencing the issue so it might be a while before I find a fix. I'll also see about fixing Verizon call audio as well.
rp076 said:
I've also downloaded two different times in case of bad download & am also getting the error 7 msg. Also on latest twrp & full wipes both times.
Click to expand...
Click to collapse
Upload a log and I'll look at it.
Made some changes which should fix Error 7, building now (gonna be a while... for some reason my ccache reset). As for the lack of call audio, I'm going to see if I can get any useful info from the logcat. I have a feeling I'm missing some libs.
ryanguy426 said:
Made some changes which should fix Error 7, building now (gonna be a while... for some reason my ccache reset). As for the lack of call audio, I'm going to see if I can get any useful info from the logcat. I have a feeling I'm missing some libs.
Click to expand...
Click to collapse
Just a suggestion, why not build from factory images that don't have the AOSP bugs?
ryanguy426 said:
Take a screenshot in TWRP and post it here please.
Click to expand...
Click to collapse
Seems like recovery.log would have had more information than a screen shot.
Yoinx said:
Seems like recovery.log would have had more information than a screen shot.
Click to expand...
Click to collapse
True, didn't think about that. Noob mistake on my part, though you're right. It could definitely give the answer. Although I updated the ota_from_target_files.py in build/tools/releasetools, which should fix the error (in theory).
RatchetPanda said:
Just a suggestion, why not build from factory images that don't have the AOSP bugs?
Click to expand...
Click to collapse
What exactly do you mean by this? Taking the factory images here and just uploading it with changes? Seems kind of pointless since there are multiple ROMs on here which are modded stock. Some people like 100% AOSP, and this is a good learning experience for me. I'm not very interested in modifying Google's factory images. I'll leave that to others
ryanguy426 said:
True, didn't think about that. Noob mistake on my part, though you're right. It could definitely give the answer. Although I updated the ota_from_target_files.py in build/tools/releasetools, which should fix the error (in theory).
What exactly do you mean by this? Taking the factory images here and just uploading it with changes? Seems kind of pointless since there are multiple ROMs on here which are modded stock. Some people like 100% AOSP, and this is a good learning experience for me. I'm not very interested in modifying Google's factory images. I'll leave that to others
Click to expand...
Click to collapse
You say modded stock is pointless but that's what this is :silly:
RatchetPanda said:
You say modded stock is pointless but that's what this is :silly:
Click to expand...
Click to collapse
Like I said, it's a learning experience for me more than anything else.
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?
{
"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.