yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Vintorlok:
Is there any way to enable Fast USB Charging?

Thanks, amazing rom!
[Samsung Galaxy Nexus] poo706:
Don't know if the stock kernel supports it. Looks like Fancy does and I believe DirtyV as well. You'll probably need an app like trickstermod or synapse to enable it.

[poo]
[Samsung Galaxy Nexus] tsiliha:
Poo706, any luck with my problem?
[Samsung Galaxy Nexus] poo706:
Your issue is not in my area of expertise, sorry. You'd probably be better off posting on G+.

[poo]
[Samsung Galaxy Nexus] tsiliha:
Ok, I will post there. Thank you
[Samsung Galaxy Nexus] hardstyle86:
Some problems here with Tapatalk notifications. :eek:

- 23 September + Fancy r57: Tapatalk notifications don't work;

- 24 October + Fancy r60: Tapatalk notifications work;

- 19 October + Fancy r57: Tapatalk notifications don't work.
[Samsung Galaxy Nexus] poo706:
11/4 added to the OP. This is the MileStone 3.2 source with all of my usual mods.

[poo]
[Samsung Galaxy Nexus] hardstyle86:
Hi, thanks for the update!

Are the tinted status bar bugs fixed? :D
[Samsung Galaxy Nexus] poo706:
I believe everything was fixed, or at least it's as fixed as it's going to get.

[poo]
[Samsung Galaxy Nexus] hardstyle86:
Percentage battery doesn't change color when charging.

Icons works well.
[Samsung Galaxy Nexus] poo706:
That still didn't get fixed?! I know they were aware of it, but I have no idea why it's still wonky. Everyone's diving head first into L now, so that's most likely as good as it's going to get.

[poo]
[Samsung Galaxy Nexus] hardstyle86:
Just to let you know. But no problem, just a little bug.

The ROM is very good. :laugh:
[Samsung Galaxy Nexus] Punkiderma:
For me it works (circle battery, no %)
[Samsung Galaxy Nexus] hardstyle86:
Yes, also circle icon with percentage works well.

Only percentage doesn't workk. ;)
[Samsung Galaxy Nexus] GorfDroid:
Does 11-4 fix the camera?
[Samsung Galaxy Nexus] poo706:
Working fine for me.

[poo]
[Samsung Galaxy Nexus] GorfDroid:
Still getting extremely slow frame rate with h264 1080.
[Samsung Galaxy Nexus] poo706:
If that's a deal breaker then you're going to need to go back to an earlier version because there won't be any more development to the KK source.

[poo]
[Samsung Galaxy Nexus] pvkiniyan95:
That's a sign of absolute greatness and incredible sweetness
[Samsung Galaxy Nexus] GorfDroid:
9-29 official is working out for me.

Looking forward to the first lollipop release!
[Samsung Galaxy Nexus] sergialess:
This Rom is working very well. Using Fancy r60. No complaints, just joy :)

Enviado desde mi Galaxy Nexus usando Tapatalk 2
[Samsung Galaxy Nexus] jdcnosse:
Is there a way to change the wallpaper when changing the profile, or would I have to use tasker for this? Basically I want one wallpaper to be displayed under the "home" profile, and a different one to display under the "work" profile.
[Samsung Galaxy Nexus] Culex316:
I'm having a problem where everytime I click on Google Chrome, it opens in a floating window instead of full screen and it's getting annoying.

I have looked everywhere to try to revert it, but haven't found anything.

How could I get it reverted so it opens fullscreen like it used to? I'm using the latest unofficial liquidsmooth by the way.
[Samsung Galaxy Nexus] poo706:
It's an issue with Chrome, not the ROM. You'll need to go back to an earlier version.

[poo]
[Samsung Galaxy Nexus] fauner:
The same here but I use cm browser [emoji6]
[Samsung Galaxy Nexus] mono28aug:
Those of you having problem with chrome opening in windowed mode, do this.

Open chrome then go to recents and click on chrome, it will be in full screen now
[Samsung Galaxy Nexus] Culex316:
Thanks for the tips on opening Google Chrome. Really appreciate it.

By the way, would it be possible to backport Lollipop's ART runtime to this ROM? Could I just drop in the libart.so file from lollipop without any issues?

Reason being is that the ART runtime on Lollipop seems to have improved considerably..
[Samsung Galaxy Nexus] sergialess:
That tip is not working for me. Thanks anyway.
[Samsung Galaxy Nexus] GorfDroid:
I tried copying all files I could find associated with ART (which were 3 files) from lollipop and it didn't work. I switch to ART in developer options and rebooted but it just booted normally and reset to dalvik.

Anyone know if it is possible to get the lollipop ART in KK at all? Maybe I did something wrong.
[Samsung Galaxy Nexus] 11zeno11:
Would it be possible to add the paranoid android card stack view to the recent panel?

https://plus.google.com/app/basic/s...xu1&sview=25&cid=5&soc-app=115&soc-platform=1

Maybe you can cherry pick from their git. Just an idea.. I really like pa recent panel..
[Samsung Galaxy Nexus] Tolazace:
@ poo706

Are you planning LiquidSmooth 4.0? On LG G2 works fine so on our GNex maybe too ;)
[Samsung Galaxy Nexus] dehein:
I would not recommend adding it. It may look a little bit better. But it is a huge performance hit for our poor Gnex. Also deactivation on PA didn't work, because they had no deactivate or activate button. But still would be possible if added as another menu option.

The best for me on liquid is, that it truely runs liquid smooth.
[Samsung Galaxy Nexus] poo706:
I've been trying for quite a while now. Been using a combo of LS's source and MWisBest's source and I just can't get it to successfully build. Then one and only time I got it to build, it wouldn't boot.

[poo]
[Samsung Galaxy Nexus] Tolazace:
Maybe new version FML solve this problem :)
[Samsung Galaxy Nexus] vladimirhtg:
Mobile Data

Moved post to toro since I dumb.
[Samsung Galaxy Nexus] CoDe LaZaRuS:
[MENTION=3927368]poo706[/MENTION] any chance of getting a liquid smooth lollypop build any time soon
[Samsung Galaxy Nexus] cujo6801:
3 posts above yours.... :eek::D;)

Sent from the "DOG" pound
[Samsung Galaxy Nexus] Culex316:
Exactly.

He was even asking the other Gnex Lollipop devs for help on how to boot it, so don't worry it's coming....just wait patiently (no ETAs) and in the meantime enjoy the awesome Unofficial Liquidsmooth KitKat...:good:...best stable custom ROM for Gnex hands down.
[Samsung Galaxy Nexus] poo706:
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]
[Samsung Galaxy Nexus] cujo6801:
Is it weird that this got me a little worked up ....

O wait maybe it was this..

Sent from the "DOG" pound on my N7 2013
[Samsung Galaxy Nexus] poo706:
Girlie pics in my thread? What an honor!

[poo]
[Samsung Galaxy Nexus] cujo6801:
Lol...^^^^

Just wanna say I love your work I'm still running your unofficial liquidsmooth Toro.

have been for a long time...

Sent from the "DOG" pound
[Samsung Galaxy Nexus] poo706:
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]
[Samsung Galaxy Nexus] cujo6801:
As always bro life first..

Sent from the "DOG" pound
[Samsung Galaxy Nexus] GorfDroid:
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.
[Samsung Galaxy Nexus] trzesickipiotr:
deleted
[Samsung Galaxy Nexus] mdki1996:
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
[Samsung Galaxy Nexus] poo706:
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]
[Samsung Galaxy Nexus] ej8989:
Does this rom have navbar color changer?
[Samsung Galaxy Nexus] mdki1996:
Yes [emoji6]

GN-LiquidKat
[Samsung Galaxy Nexus] ej8989:
Thanks. But what I was trying to find where you can specifically set the color of the navbar regardless of the opened app.
[Samsung Galaxy Nexus] poo706:
Don't think so.

[poo]
[Samsung Galaxy Nexus] zzpianoman:
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.
[Samsung Galaxy Nexus] thelegbra:
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.
[Samsung Galaxy Nexus] elbi14:
on new google search. voice search and other setting force close on this rom, can you fix it?

sorry for my english
[Samsung Galaxy Nexus] poo706:
Sounds like a gapps issue.

[poo]
[Samsung Galaxy Nexus] mdki1996:
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?
[Samsung Galaxy Nexus] thelegbra:
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.
[Samsung Galaxy Nexus] mdki1996:
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.
[Samsung Galaxy Nexus] elbi14:
im using minimal gapps. on other kitkat rom google search working fine. [emoji20]

force close coming from google search 4.2.xxxx version.

Sorry for my English
[Samsung Galaxy Nexus] poo706:
I'm sorry, I really don't know what to tell you. Unfortunately, I don't have the time to spend playing around with Android all the time like I used to.

[poo]
[Samsung Galaxy Nexus] sergialess:
Hi!. I re-flashed this rom yesterday, but I have the SystemUpdateService wakelock. Anyone with same problem?. Any method for fixing it?. Thanks!
[Samsung Galaxy Nexus] mdki1996:
Here is a flashable zip and it works great! ;) http://xdaforums.com/showpost.php?p=61268254&postcount=915
[Samsung Galaxy Nexus] sergialess:
Woah! thanks mate. I'm running latest build 11/04 and the patch worked like a charm.

My battery is back!
[Samsung Galaxy Nexus] christianpeso:
This is funny because I just went back to this ROM yesterday, the 11/4 version and woke up this morning and looked at Greenify that I had installed and see two different Google Play Services that have been running since my phone last powered on. My question is, would this flash-able zip work on the Toro version as well?
[Samsung Galaxy Nexus] mdki1996:
I don't know, you should ask to [MENTION=4362212]thelegbra[/MENTION] ;)
[Samsung Galaxy Nexus] Punkiderma:
Anyone still using this rom, does profile wifi triggers works for you?
[Samsung Galaxy Nexus] poo706:
Even though I moved on to a S4 months ago and don't do any deving anymore, it makes me really happy to see the occasional activity on my threads. Even more so knowing that people are still installing and using my roms. You guys are the best!

[poo]
[Samsung Galaxy Nexus] Punkiderma:
After using lollipop for a while, I went back to this rom: the difference is incredible. This rom is very fast, and also multitasking is perfect!

Anyway, I'm having some issues with Feedly: after reading some articles, it gets stuck. Anyone have the same problems? Never had them in the past!
[Samsung Galaxy Nexus] hardstyle86:
In my opinion, the best KitKat ROM for maguro.
[Samsung Galaxy Nexus] knopper84:
ok...i' ll try this one too.

Anyone knows whether latest Fancy Kernel works on this ROM? und if, how does it perform?

Or is franco more recommended on this one??
[Samsung Galaxy Nexus] christianpeso:
Latest Fancy does work. I think it is version R60. Ran just fine for me on Toro version. I am currently using the latest DirtyV kernel and it works great.

I too went back to this ROM after trying several Lollipop ROMS. None of them worked as good as I want them to and I attribute that to the age of our device. Went back to this ROM because it has pretty much every feature/customization a phone can have. Difference is night and day in performance over any Lollipop ROM. Like I stated, using DirtyV kernel with Nepehilim settings. Also just installed Killjoys scripts and this phone is flying! Running Greenify as well using Boost mode(xposed) and also Bootmanager from xposed. Only thing I need now is a new battery and this phone is just as good as some newer phones.
[Samsung Galaxy Nexus] dante197:
Skype keeps force closing when i try to start it. Is only my problem?
[Samsung Galaxy Nexus] mdki1996:
Just tried: same problem...
[Samsung Galaxy Nexus] Spraite25:
I think I'll move to this ROM, latest Cyanogen is crappy

Luckily I don't use Skype!
[Samsung Galaxy Nexus] poo706:
You shan't be disappointed.

[poo]
[Samsung Galaxy Nexus] djkk16:
does anyone know of nephilim like settings for fancy kernel r60 as i couldnt find one. if someone has their own personalized settings of fancy kernel do tell. gonna be shifting to ls in the weekend hopefully :)
[Samsung Galaxy Nexus] knopper84:
So whats with the lattest security-fixes (Stagefright)? Could they be integrated into this ROM?

Or do i have to switch to a 5.x ROM if i need them?
[Samsung Galaxy Nexus] poo706:
I'm really not familiar with the stagefright patch, although I think you're right that they are for 5.0+. You should be able to add these build.prop edits: http://xdaforums.com/showpost.php?p=62069940&postcount=8 . I haven't tried them myself.

[poo]
[Samsung Galaxy Nexus] musical_chairs:
The patches have been backported at least to kitkat, by CyanogenMod and probably others. Just for fun, I picked the backported patches from CM and did a stagefright-safe build of kitkat (using Evervolv) for my oldest Android device, the venerable HTC Droid Incredible. Not that video playback really works on kitkat on that old phone anyway, but hey, it passes the 'stagefright detector' tests now.
[Samsung Galaxy Nexus] poo706:
Too bad I didn't hang on to my build environment and the source as I last left it, I would have put out another round of builds with the patch.

[poo]
[Samsung Galaxy Nexus] bamtan2:
It would be a shame if the internet of open source projects became implicitly closed like this because of such technical quirks :P
[Samsung Galaxy Nexus] irondog:
I'm using this ROM and it's for sure the best kitkat!

I have only one question about the stock FW on it, why it does not go into deep sleep? I read only 350mhz minimum but no deep sleep... by the way battery is good...
[Samsung Galaxy Nexus] Punkiderma:
Could be the Google Play services issue.

If you search this topic for "play services", you should find a flashable zip that will solve the issue [emoji6]
[Samsung Galaxy Nexus] irondog:
Thanks I've seen the zip but I'm a bit scared of messing up mu setup... the think I have noticed is that it goes into deep sleep only when wifi/3g is connected while during the night when I tur off all the connections it doesn't go into deel sleep.

My previous setup was PA latest beta, Fancy r60 and the same PA Gapps but everything was fine.... could it be a kernel issue or a ROM issue?
[Samsung Galaxy Nexus] mdki1996:
90% you solve with the zip, however install Wakelock Detector to see where is the issue ;)
[Samsung Galaxy Nexus] irondog:
Ok I solved the issue installing the ZIP but then I had to restart Google Play Services service "systemupdateservice". Now he is sleeping like a baby! thank you
[Samsung Galaxy Nexus] knopper84:
So where can i exactly find the zip-file?
[Samsung Galaxy Nexus] mdki1996:
Here bro: http://xdaforums.com/showpost.php?p=61268254&postcount=915 ;)
[Samsung Galaxy Nexus] irondog:
I've another last (I hope) problem... bluetooth.

My Pebble Time connects correctly the first time but then it doesn't connects any more.

It seems that it is connected on the phone (it says connected) but it is not. The same thing happens with the car bluetooth. Any fix available?
[Samsung Galaxy Nexus] KiD3991:
I don't know. The fastest rom I know to date odexes its files. N5 Velocity. I'll pm you if you want to see because the dev left xda and is working on a private community.

Well I'll be using the 30/6 build since people said its the most badass. Hopefully Z2bionic works too. It broke camera but made the phone fly. Small price to pay IMO.
[Samsung Galaxy Nexus] Alkemix:
Thanks :victory:

7/8 maguro release

1) After conversion to F2FS (by Your tool also)

sometimes

rom stopped at boot "Google" and Android system OS doesn't start. 30/6 release

never

stop at boot on "Google"

2) Battery percentage on status bar indicates values ​​totally incorrect

I remain on 30/6 release,.. for now... no issues at all by It.. also 24/6 release... they are the best releases for me...
[Samsung Galaxy Nexus] alboz83:
I have problem with 7/8 maguro release also, after one reboot the screen turns off by itself and will not turn on, i must remove the battery
[Samsung Galaxy Nexus] thenemis:
some issue with other rom. kernel related

LINK

http://xdaforums.com/galaxy-nexus/development/kernel-dirtyv-6-9-14-t2613655/page1103
[Samsung Galaxy Nexus] poo706:
What the hey, I'll put out an odex build with the sabermod 4.9 toolchain and see what happens.

By the way, I have nothing but good things to say about the 7/7 for toroplus.

[poo]
[Samsung Galaxy Nexus] poo706:
Getting stuck at the google logo sounds like a kernel issue to me. The converter uses dirtyv which, if you keep up with that thread, you can see a lot of people are having that issue. I can't imagine why 6/30 would be good, but not 7/8, but if that works for you, then more power to you.

I don't know what to say about the battery percentage, everything's been all good on 7/7 on my toroplus. Maybe wipe battery stats?

[poo]
[Samsung Galaxy Nexus] poo706:
EXT4 or converted to F2FS? Kernel?

[poo]
[Samsung Galaxy Nexus] Alkemix:
Yes.. I think ramdisk issue... I assume "fstab.tuna" issue with F2FS file system... I don't know because 30/6 release start always.. then is still a rom issue..rom+ ramdisk kernel issue+ F2FS I guess. the phenomenon occurs with various roms and is linked to these 3 factors: ROM+kernel ramdisk (fstab I guess)+F2FS

I will do various tests ... I hope to find a solution ...
[Samsung Galaxy Nexus] poo706:
I would focus on this: https://github.com/LiquidSmooth-Dev...mmit/c4ed156b6f63a6f3075b724f4c1a208c8b20c354 . Looks like that didn't make it into the 6/30 build.

[poo]
[Samsung Galaxy Nexus] Alkemix:
Uhmmm then... Rketerson uses dirty-V kernel... He has applied all commits from dirty-V adapt to F2FS... and entire osmosis kernel ramdisk (hybrid for ext4 and F2FS ) ... here is what he meant by "added support to F2FS" into changelog...

I use osmosis ramdisk also into my custom kernel with different scripts... I don't know if issues on 7/8 rom are due to It or to rkpeterson's commits from dirty-V kernel.

I've rebooted my Nexus and always starts (no stop at "Google") ... It's sure: on 30/6 release no issues !!! Try to ask to Rkpeterson about those commits and about this problem. :(

I'm thinking... If We remove fstab check and made ramdisk only for F2fS (not universal) ?
[Samsung Galaxy Nexus] poo706:
I'm not sure what to make of those commits I linked you to. I built for my toroplus sometime around 7/3 and installed it without also installing dirtyv under the expectation that drityv was now included. But when I booted up, it wasn't dirtyv. In the about phone section, the kernel information had something about cyanogenmod in it and touch control didn't work.

Have you tried installing dirtyv immediately after installing the ROM instead on relying on my tool to handle it for you?

[poo]
[Samsung Galaxy Nexus] Alkemix:
Liquid ext4 uses custom cyanogenmod kernel... F2FS tool install dirty-V because, rightly, is the first kernel that has supported F2FS; otherwise the rom converted to F2FS doesn't boot .. and so far we..

Yes I've tried to "force" flash dirty-V or others F2FS kernels (all built by osmosis' ramdisk) after flash rom converted by Your tool..but issue remains... so there is something in the ramdisk that conflict with ROM converted to F2FS.

Rom starts on the first time.. but when You restart Your Nexus boot stops at "Google" ... this issue by severals roms ...
[Samsung Galaxy Nexus] poo706:
If it's happening on several ROMs then it definitely sounds like a kernel issue. I think you should take it up on the drityv thread.

[poo]
[Samsung Galaxy Nexus] alboz83:
Converted with your tool in F2FS and used dirty v kernel, inside your tool
[Samsung Galaxy Nexus] Alkemix:
;

Ok I've solved all issues. I've changed ramdisk.. erased some simply string into updaterscript and update busybox to last Stericsson release.. I've done various tests and System Android always starts correctly.

I'm testing Liquid unofficial on 7/8 now... converted into F2FS with my custom kernel.

1) Battery issue disappeared by full wipes...

2) Annoying issue of official release on 7/4 disappeared by Your last unofficial release !

For now... all run rock solid and smooth..

I've found a special sabermod toolchain 4.9 (Is the same that I use for build my kernel, but this is for ROMs ;) )... I'll give It to You by private message... so You can use this toolchain for build new release.. I''ll wait It for my maguro :cool: :good: ;)
[Samsung Galaxy Nexus] KiD3991:
Tell me when its out for maguro. Crackhead here. But i have too much device to flash with recently. :laugh:
[Samsung Galaxy Nexus] poo706:
Could you go into specifics on the ram disk and updater-script changes?

[poo]
[Samsung Galaxy Nexus] Alkemix:
- updated busybox to last Stericsson's release

- set right busybox path into kernel script:

[B]bb[/B]=/system/xbin/busybox;

- deleted:

run_program("/sbin/sh", "-c", "mkdir /system/etc/init.d");
set_perm_recursive(0, 0, 0755, 0755, "/system/etc/init.d");
run_program("/sbin/sh", "-c", "mkdir /system/etc/init.d");

- added from dirty-V:

assert(getprop("ro.product.device") == "maguro" || getprop("ro.build.product") == "maguro" ||
getprop("ro.product.device") == "toro" || getprop("ro.build.product") == "toro" ||
getprop("ro.product.device") == "toroplus" || getprop("ro.build.product") == "toroplus");

- erased:

run_program("/sbin/busybox", "mount", "/cache");
...
unmount("/cache");

- add from dirty-V into script kernel:

# workaround for hung boots with nodiratime+noatime or barrier=0+data=writeback
# which occur when used as ext4 mount options for userdata via the tuna fstab
$bb [ `getprop ro.fs.data` == "ext4" ] && $bb mount -o remount,nosuid,nodev,noatime,nodiratime,barrier=0 -t auto /data;

4.9 toolchain uploading... I'll send You between 2 hours about :eek:
[Samsung Galaxy Nexus] poo706:
So were all these changes to file(s) extracted from boot.img? And if so, what boot.img did you start with?

[poo]
[Samsung Galaxy Nexus] Alkemix:
I use only osmosis' ramdisk so boot.img example model is that into dirty-V kernel.. if You look into your focus link https://github.com/LiquidSmooth-Dev...mmit/c4ed156b6f63a6f3075b724f4c1a208c8b20c354 You find them. If You want to look better.. extract files from last dirty-V boot.img, so You'll get whole osmosis' ramdisk