Thanks man, that means a lot. I really love being part of this great community. I wish I had more time to dedicate to L, but I started a new job recently that's much more demanding of my time.
[poo]
[ROM] [4.4.4 KK] [EXT4/F2FS] [DeltaJen] LiquidSmooth-UNOFFICIAL v3.2 maguro
- Thread starter poo706
- Start date
-
- Tags
- development
[poo]
True say.
After trying all the other ROM's this one is the most flawless.
I will hold out on L until it is just as flawless.
Thought you all might like an update on LP. The best luck I've had is using the LS source, with MWisBest's device_toroplus, and Ziyan's device_tuna, kernel, and vendor_samsung. I've successfully compiled this combo a few times, neither will get past the Google logo. I've pulled a dmesg and Ziyan confirmed the kernel is not at fault. I now also have a logcat, but I really don't know what I should be focusing on. I invite everyone to take a look at this, let's see if we can figure this out and enjoy some sweet Liquid Lollipop! http://pastebin.com/W5CrdtpR
[poo]
[poo]
I made this maguro build last night, but I don't have a maguro, so I can't test it: http://www.mediafire.com/download/eh4i1sf2l2xxh4j/LS-LP-v4.0-2014-12-18-liquid_maguro.zip
Don't know if it'll boot, I still can't get my toroplus builds to boot. Same kernel as Ziyan's cm12, so whatever goes for that (like f2fs) goes for this. If it won't boot, I'd appreciate if someone could grab me a dmesg and logcat.
[poo]
Don't know if it'll boot, I still can't get my toroplus builds to boot. Same kernel as Ziyan's cm12, so whatever goes for that (like f2fs) goes for this. If it won't boot, I'd appreciate if someone could grab me a dmesg and logcat.
[poo]
I made a separate thread for lollipop, in case you haven't seen it. http://xdaforums.com/galaxy-nexus/development/rom-liquidsmooth-unofficial-v4-0-maguro-t2979895
[poo]
[poo]
Hi all [emoji2] thanks to the developer for this fantastic rom! I found a bug related to brightness: if I set brightness manually to medium (example) from low (example) and than switch off the display, when I switch on display the brightness is back to low value but the brightness bar is set to medium. After 10 time screen on/off and manually setting to medium brightness the bug disappears but if I change an other time brightness (example to low or high) we are back with the bug [emoji17] anybody has the same issue?
GN-LiquidKat
GN-LiquidKat
I've never had such a problem personally and don't remember anyone reporting anything like that. You might look through the display options and disable anything that makes adjustments based on ambient light. There's also content adaptive brightness (CAB) that could be part of the kernel, which you can disable with TricksterMod.
[poo]
Thanks. But what I was trying to find where you can specifically set the color of the navbar regardless of the opened app.
This was a part of the Xposed module GravityBox, if I remember correctly. Not sure if this was ever implemented in any of the KitKat custom ROMs.
if there is anyone else like me using this rom and plagued with the google play services' wakelocks (systemupdateservice), i have applied a patch to framework-res.apk and got rid of the wakelocks without any init scripts or disabling services.
here's a flashable zip for people who has the same problem.
warning: only use if you have the 11/04 build.
here's a flashable zip for people who has the same problem.
warning: only use if you have the 11/04 build.
on new google search. voice search and other setting force close on this rom, can you fix it?
sorry for my english
Sent from my Galaxy Nexus using Tapatalk
sorry for my english
Sent from my Galaxy Nexus using Tapatalk
Great job man, thanks!
During the last month I used myandroidtools to disable systemupdate at every boot, but the wakelocks in my case are connected also with *NET_scheduler*. Is it only a my problem or what?
Great job man, thanks!
I don't have those kind of problems, could be an app causing it. After applying the framework patch I have uploaded, you can enable the services and remove those service disablers.
Oh, and you have to clear catch and dalvik as well.
I take the opportunity to ask if you have this bug (i paste what i wrote months ago in this thread): if I set brightness manually to medium (example) from low (example) and than switch off the display, when I switch on display the brightness is back to low value but the brightness bar is set to medium. After 10 time screen on/off and manually setting to medium brightness the bug disappears but if I change an other time brightness (example to low or high) we are back with the bug.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
40poo706 presents... LIQUIDSMOOTH - UNOFFICIAL
Question
What, no snazzy name for your ROM?
Answer
It's virtually identical to LiquidSmooth. You can usually dirty flash back and forth between official and unofficial.
Question
Virtually identical? So what's different?
Answer
- Unified EXT4/F2FS (INCLUDED STOCK LS KERNEL IS EXT4 ONLY, IT'S UP TO YOU TO FLASH A F2FS KERNEL IF NEEDED)
- DeltaJen ROM update patches
- Advanced Backup/Restore (details)
- CyanogenMod Calculator
- Heads up notifications for system apps
- Scrolling cache disabled
- Navigation bar can be disabled without enabling PIE
- Launcher icon for Viper4Android
- Removed Dash Clock, cLock, Apollo, Sound Recorder, Kernel Tweaker, and Liquid Updater
What's DeltaJen?
Answer
ROM upgrade patches that are usually less than 10 MB. The /system partition will not be wiped. Unchanged files, files you changed, files you added, and files you removed will be all be ignored.
NOTE: You MUST be on a specific UNOFFICIAL LIQUIDSMOOTH build to use DeltaJen. For example, 10/24 to go to 10/29. You CAN'T use DeltaJen to go from 10/19 to 10/29, but you CAN go from 10/19 to 10/24, then to 10/29.
Question
What gapps should I use?
Answer
I don't think it matters. I recommend Google Apps Minimal Edition: http://xdaforums.com/showthread.php?t=2779598
Google Drive mirrors: maguro, maguro DeltaJens
LiquidSmooth changelogs: https://drive.google.com/folderview?id=0B_Yk7pLJ4-VhVFVSN0JkNmJlOTQ&usp=sharing
Unofficial-specific changelogs:
11/4: No new unofficial-specific changes
10/29: Tinted Statusbar/Navbar still not officially merged, but several bugs have been fixed
10/24: Fixed "Always On" LED, early implementation of Tinted Statusbar/Navbar (as of 10/26, official LS fixed LED & using beta tinted bars)
10/19: No new unofficial-specific changes
10/11:
- Unified EXT4/F2FS
- Stock LS kernel (EXT4 ONLY!) built with Sabermod 4.9 toolchain
- Advanced Backup/Restore
- CM Calculator instead of Slim's
- Launcher icon for Viper
- Removed apps: Dash Clock, cLock, Apollo, Sound Recorder, Kernel Tweaker, and Liquid Updater
- Removed "Clock Widget" from Interface Settings
- Removed "Performance" from Liquid Settings
- Enabled heads up notification checkbox for system apps
- Scrolling cache disabled
- Nav bar can be turned off without enabling PIE
Credits:
LiquidSmooth team: https://github.com/LiquidSmooth
@rkpeterson for his work on the LS source for the gnex
@cybojenix for DeltaJen: http://xdaforums.com/android/development/tool-deltajen-t2839999
@EnricoD for the method of disabling scrolling cache: http://xdaforums.com/google-nexus-5...roll-stock-t2617050/post49582206#post49582206
Motorola Mobility for the method of unified /system formatting: https://github.com/MotorolaMobilityLLC
@bamafan39 for the logo
[poo]18Ok guys, here's my latest thoughts on the kernel situation with my unofficial LiquidSmooth ROMs. My intention of including Fancy or DirtyV with the ROM was so that it would be totally EXT4/F2FS universal right out of the box. However, it's become clear lately that there are issues with the inclusion of 3rd party kernels, namely:
- When I include Fancy, wifi tethering is broken when people switch to DirtyV
- When I include Fancy, there are CPU frequency issues when people switch to DirtyV and use Synapse
- When I include DirtyV, tethering is still broken
- Seemingly, when I include DirtyV, some people have stability issues
- Everyone has their own preference for kernels and versions of those kernels
I think the most elegant and correct solution is to simply include the stock LiquidSmooth kernel with my ROMs, and leave the burden of installing your kernel of choice to you. I have verified that DirtyV installs as it should when the stock kernel is included instead of Fancy. Of course this means that if you have any partitions as F2FS, you're going to HAVE to also install an F2FS compatible kernel after installing the ROM. But we're all big boys here (no offense to any girls that may be present). I've 99% made up my mind on this, but I welcome any opinions.
[poo]1510/4 added to the OP.
- Switched optimizations from metalspring to optimizations from JustArchi
- Switched toolchain from 4.8 Linaro to 4.8 Sabermod
- Switched kernel from Fancy r54 to DirtyV Pre-Final
A few notes regarding the 9/30 -> 10/4 DeltaJen:
- It's about 31 MB because of the toolchain switch
- It will NOT touch the kernel. For some reason the DeltaJen creation failed due to the switch to DirtyV, so I had to exclude the kernel from this DeltaJen. If you're on 9/30 with Fancy r54 and want to go to 10/4 with DirtyV, either install the full ROM or use the DeltaJen and follow that up with the attached DirtyV flashable ZIP.
Special thanks to @Nautilus74 for creating the boot.img to allow me to include DirtyV with my ROM: http://xdaforums.com/showpost.php?p=55799653&postcount=608
[poo]1110/11 added to the OP.
- Included kernel is stock LS built with Sabermod 4.9 (EXT4 ONLY, IT'S UP TO YOU TO FLASH A F2FS KERNEL IF NEEDED)
- Lots of tuna commits were merged in the official LS source a few days ago
- Once again, DeltaJen won't touch the kernel because it just did not like that DirtyV boot.img from the last build
As you may have seen, I recently came to the conclusion that there are a lot of issues when trying to include 3rd party kernels with the ROM. I would encourage you to use the full ROM zip this time instead of DeltaJen.
[poo]10
I have problems with my build machine right now. I hope to get that fixed this weekend and then, without going into specifics, I have high hopes that I'll be able to make a bootable LP LS this weekend.
[poo]
