yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] PeQuEsan:
After 3d12h of running r191, I can say it's rock solid and completely smooth with default governor and values (only -100 UV). Also good battery, achieving over a day and a half if not heavily used, and easily 4h of SoT. Didn't test heavy games, though. Candy Crash.

Really good as a milestone Franco... What do you think? Still place of improve?

Seems as we've got 4.3 mess for other 15 days... :)
[Nexus 4 Original Android Development] adriangb:
You've given up on 4.4/N5 today? Maybe 9AM PST?
[Nexus 4 Original Android Development] Stoozak:
I must say I'm very happy with 191. Best battery life I've had so far.
[Nexus 4 Original Android Development] xFuGiToiDx:
Wats your screen on time?
[Nexus 4 Original Android Development] Stoozak:
Bout 2h20
[Nexus 4 Original Android Development] TestingCharts:
I'm running stock ROM+Franco for a while. I hope 4.4 will change the mind of the CM team, to revert all the CAF mess so I can use Franco again. It's a great project, but isn't essential to me. It's sad to see all the stuff CM is passing through.
[Nexus 4 Original Android Development] droid_legacy:
Hey guys. I already did try to find an answer on my own, but without success, so I decided to ask the crowd. ;)

Might anyone be so Kind and explain to me what the NlpWakelock thing is and what it does. This is always the highest amount of wakelocks/keeping the device up.

Thanks in advance. :)
[Nexus 4 Original Android Development] farris:
NLP=Network Location Provider, so it has to do with location-services (tick off 'use wifi for location and that kind of stuff and try again)
[Nexus 4 Original Android Development] kingofcomedy:
Am I the only one with my two problems (speaker not working and volume buttons switched)? Have I done something wrong? In Fastboot-Mode I entered "fastboot -c "console.ttyHSL0,115200,n8 androidboot.hardware=mako lge.kcal=0|0|0|x" boot boot-r191.img" to boot the new kernel temporary.
[Nexus 4 Original Android Development] David9519:
23% battery left!
[Nexus 4 Original Android Development] blsrbl:
+1. R191 is the best one since 4.3. Smoothness and best battery life so far.
[Nexus 4 Original Android Development] PeQuEsan:
No idea... Last comments I've read sets it for last day of October...
[Nexus 4 Original Android Development] jmudrick:
I'll do you better, two straight sessions, typical usage for me, with 6hr screen times. Great kernel.
[Nexus 4 Original Android Development] Serris:
What os are you two using?
[Nexus 4 Original Android Development] David9519:
Not bad, but I played some games, so I can get 6 hours SoT, too
[Nexus 4 Original Android Development] jmudrick:
Not a contest, just impressed with Franco's work. I've seen 6.5-7.0hr screen times on r111 and r183 but performance not as smooth as this one. On Cataclysm ROM.
[Nexus 4 Original Android Development] xda_emanuel:
Hello guys, i'm on franco r191 android 4.3. Today i got a weird thing. The phone doesnt go in deep sleep anymore ( i saw it on cpu spy) it was run with minimim frequency while screen off but not deep sleep. I was on interactive governor, scheduler row. Now i have rebooteed my phone and deep sleep work fine again. What happened? Maybe some app was creating some conflit?
[Nexus 4 Original Android Development] Deeco7:
Currently not getting enough battery juice, only 3hrs screen on time with 10%, which configuration works best for you on PA?
[Nexus 4 Original Android Development] limeaide:
This is more than likely the problem. Check Google sync and disable the one you do not use.

Sent from my Nexus 4
[Nexus 4 Original Android Development] myweca:
Terrible Battery Life

Hello guys!

I need your help!

I am currently using franco.Kernel r191 with CM10.2 11/10/2013.

I have been experiencing really bad battery life. With moderate use, I must charge my phone twice a day - there is no way I make a day without re-charging!

I want to know if someone is experiencing something like this and if I could post some Logs (for example BetterBatteryStats or Wakelock Detector) so someone could help me! If this is not the right thread, please tell me where to post it!

Thanks!

:):):)
[Nexus 4 Original Android Development] marhensa:
from the navbar icons autohide, and those amazing battery life...

i bet that is CATACLYSM rom.. :)

i could achieve 6 SOT too..

Sent from Android device using Tapatalk 4
[Nexus 4 Original Android Development] Testraindrop:
If you use a wireless charger it might have been the infamous wireless charger detector wakelock.

Android bug.

Gesendet von meinem Nexus 4
[Nexus 4 Original Android Development] rockafellor:
Also using cataclysm rom. Never experienced problems or any problem with battery since then

Sent from my francofied cataclysmd Nexus 4
[Nexus 4 Original Android Development] yoyosamsam:
What is your setting?
[Nexus 4 Original Android Development] franciscofranco:
Nice screen on times, glad to see people enjoying their phones without worrying about getting out of juice.
[Nexus 4 Original Android Development] rushi1607:
which rom ?
[Nexus 4 Original Android Development] Bobtehblob:
Still liquid smooth with touch boost freq back down to 1026mhz! How's project Pringle going!? Haven't seen any updates yet!
[Nexus 4 Original Android Development] kingofcomedy:
Both problems doesn't exist after I have flashed the kernel permanently.
[Nexus 4 Original Android Development] franciscofranco:
Its going good. Been busy with it and have had some problems here and there that have made me waste some time, but I think Im almost ready for a new alpha/beta soon.
[Nexus 4 Original Android Development] alcurtis93:
What's project Pringle? Are there any kernels that work with cm 10.2 yet?
[Nexus 4 Original Android Development] sNoxious:
You almost have 1,200 forum posts here on XDA, a simple search for "pringle" or "pringles" would easily answer your question.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Pipusz:
1. The codename of the new app.

2. Newer CM ROMs and their derivatives won't be supported until they revert a couple of things.
[Nexus 4 Original Android Development] marhensa:
it's sad CM team are doing such things.. :(

Sent from Android device using Tapatalk Pro
[Nexus 4 Original Android Development] dey2929:
Am on AOKP mr2 nightly 12 oct build android 4.3.1 JLS36I.....does this kernel support it ?
[Nexus 4 Original Android Development] psych2l:
Switched to Paranoid Android and haven't looked back. Hasta la bye bye CM!
[Nexus 4 Original Android Development] devadam1:
Already have the Chainfire Su. I have tried everything I could. Nothing solved the problem. I was told that it has something to do with the CM 10.2 nightlies. They somehow disabled the ability to flash custom kernels. I do not know the details about this change.
[Nexus 4 Original Android Development] pchtc:
the kernel you need is jss

it will work

as long as you use colorfix.zip
[Nexus 4 Original Android Development] drawde40599:
Is it installed as system app ? Like u physically seen it? Chainfire su can be a pain in the ass to install /flash on cm , I had to put his su apk into the system app folder fix the permissions then flash it threw recovery to get damn thing to stick and work right ... I haven't been keeping up with development lately so maybe cm did do something like that , dunno , I went back to 4.2.2 and 165 and I'm happy , I've found there isn't a ROM out that works completly flawless with 4.3 (besides googles ) always one Lil thing screwing up for me , I got sick of it
[Nexus 4 Original Android Development] dey2929:
yeah flashed jss but colors are messed up.....can you provide a link for colorfix.zip please?
[Nexus 4 Original Android Development] Pipusz:
Search for colorfix.zip. It has been a frequently mentioned topic as of late.
[Nexus 4 Original Android Development] Firmino Neto:
r191 rocks!
[Nexus 4 Original Android Development] devadam1:
Yes, it is. I can see it with my naked eyes! :) Unfortunately, I cannot use this great kernel with my room. I guess I will have to stick with the CM's own kernel.
[Nexus 4 Original Android Development] Whyzor:
Apologies for digging up an old post, while googling for the same exact answer, I came to this thread. The only difference in my testing has been I lock the min & max frequencies via scripts:

echo "384000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq

chmod 444 /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq

echo "1026000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

chmod 444 /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

which caused this to appear in stock kernel's logcat. And if I get rid of it the error disappears. So it looks like another resource (possibly MPdecision) trying to reset default frequency values.
[Nexus 4 Original Android Development] blankit:
There are certain flashable files that you can download that will let you flash custom kernels but I think the latest nightlies made them obsolete.
[Nexus 4 Original Android Development] arlenwoot:
Link's in my signature.
[Nexus 4 Original Android Development] frozst:
I haven't seen anyone reporting but I have flashed fk in carbon ROM and I got lots of artifacts, very strange.

On nexus 7 with the same ROM works fine.

Any ideas?
[Nexus 4 Original Android Development] DesertVelo:
Please make sure that you are flashing the JWR version of the kernel (non-JSS file name). Since Oct 3rd, Carbon is now a JWR kernel based ROM. Perform a manual flash of JWR kernel - do not use FKU autoupdate since Carbon may still be reporting JSS variant ROM.
[Nexus 4 Original Android Development] mikeymop:
I keep seeing all these mentions of CAF. Is it Code Aurora fixes? Are they being merged to make a more efficient build?

I was waiting until today because I knew when I change Roms 4.4 would get released and I'd have to flash again.

I was thinking of switching to a hybrid ROM like AOSPA and flashing Franco's kernel. I don't really care what ROM or 4.3 version but I can't deal with the deadlocks.

I'm on Gnome Project right now which is great, but I miss T-Mobile themes.

Can anyone else vouch for the 10/1 nightly? I know every phone/setup is different so I'd love to hear others' opinions.
[Nexus 4 Original Android Development] David9519:
Default settings, but voltage : -100mv
[Nexus 4 Original Android Development] lotherius:
Same problem here. Latest pro app, and it sends you off to JSS-land for paranoid which calls for a JWR kernel.
[Nexus 4 Original Android Development] frozst:
Thanks!

I didn't notice that carbon was JWR, I was so used to CM... Runs perfect now.

And it's true, fku downloads the JSS version ;)
[Nexus 4 Original Android Development] jmudrick:
All my 6hr SOT sessions achieved with stock settings, no UV, no per app settings.
[Nexus 4 Original Android Development] spider623:
Try PSX, PA or any other JWR+JSS hybrid Rom
[Nexus 4 Original Android Development] Dimatchka:
I remember reading a while back about a double tap to Wake up feature. How do I enable it? Do I need to use a terminal or I can do it through the app?
[Nexus 4 Original Android Development] noobiekins:
on an root explorer, open /sys/module/lge_touch_core/parameters/doubletap_to_wake and change it to 1 or Y
[Nexus 4 Original Android Development] arlenwoot:
To enable from terminal

su

echo 1 > /sys/module/lge_touch_core/parameters/doubletap_to_wake
[Nexus 4 Original Android Development] franciscofranco:
Don't use that feature, its not finished, its semi-broken and needs work, but its not my priority right now.
[Nexus 4 Original Android Development] Arstoien:
Here's something for you and possibly others interested, taken mostly from my bookmarks but all should be in the changelog in the op:

USB Fast Charge – to enable: echo 1 > /sys/module/msm_otg/parameters/fast_charge

The path for the gamma values is: /sys/class/misc/gammacontrol/

Sound Control (volume boost, headset boost, mic gain) – The path is /sys/class/misc/soundcontrol/

Hotplug driver settings (cores_on_touch, first level, suspend frequency): /sys/class/misc/mako_hotplug_control/

Governor settings (above hispeed delay, boostpulse duration, go hispeed load, hispeed freq, input boost freq, min sample time, target loads, timer rate, timer slack: /sys/devices/system/cpu/cpufreq/interactive/

CPU's max freq file path: /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

Note that you need to change the file permissions for this, unlike the other files. I'm sure that there's more efficient way to do this but here's what works for me: If you want to change the max freq to 1026 MHz, do these three lines:

chmod 666 /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

echo 1026000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

chmod 444 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

GPU parameters (down threshold, up threshold, sample time): /sys/module/msm_kgsl_core/parameters/

And the newly exposed audio settings: /sys/devices/i2c-0/0-0058/

PS: Would be useful to know how to change the gpu max frequency, so if anyone knows the path, drop a comment :)
[Nexus 4 Original Android Development] _artem_:
I was always wondering why you can't use latest linux kernel? All drivers are available so why is it impossible to use 3.11 kernel?
[Nexus 4 Original Android Development] ronac:
Hello I am new to the forum, just don't know whether I should ask the question here.

I am using PA3.99r2 w/ franco r191.

I've got occasional hang when charging overnight (cannot wake up, need to press power button long to reboot).

Not so sure whether it is correlated to charging but I did got hang in daytime as well.

How do I troubleshoot the problem myself (such as reading logs), I tried to dump a report from "report bug", but it only logs record since the device is rebooted.

Thanks for the nice work here guys.
[Nexus 4 Original Android Development] hooliganx:
[MENTION=4928198]Arstoien[/MENTION]...

and the franco app is for....?

N4*Slim.b.1.8.JLS.4.3.1*Hells.b40-t3.JWR*TWRP.2.6*Radio.0.84
[Nexus 4 Original Android Development] devadam1:
I am switching to PA. Enough of CM. Thanks for the suggestions.
[Nexus 4 Original Android Development] sordna:
Nice! What does the stock kernel give you in comparison?
[Nexus 4 Original Android Development] CrimsonSmear:
#echo X > /sys/class/kgsl/kgsl-3d0/max_gpuclk; # 128000000, 200000000, 325000000(4.2)/320000000(4.3), 400000000

Most franco.Kernel specific paths/values can be found in my init.d script, as some of the paths/instruction you have happen to be specific to other kernels.

I know that the script is not fully current to the 4.3 (steaming turd) kernel, as I have preferred the consistency/stability of 4.2.2. I am willing to update my script if anyone is willing to share the missing paths and corresponding values.
[Nexus 4 Original Android Development] jmudrick:
Haven't tested vs. R191. With r183 I was getting up to 60 min over stock. R184 not so good. Even if battery was the same I'd stick with Franco for other considerations.
[Nexus 4 Original Android Development] hooliganx:
try slim too... excellent rom :D

N4*Slim.b.1.8.JLS.4.3.1*Hells.b38-JWR*TWRP.2.6*Radio.0.84
[Nexus 4 Original Android Development] franciscofranco:
Because OEM's fork the internal Google common tree (which is currently 3.4). When SoC makers have specific Kernel trees OEM's also tend to work on top of it. We just cannot simply push things to 3.11 just like that because of too many code differences and possibly many broken crap.

Are you undervolting? Are you using stock charger?

r191 is good to go :)

Btw your sig makes me giggle every time I see it.
[Nexus 4 Original Android Development] dapsANDpoundz:
Off topic but, for those who use the Feedly app check out the "What's New" section. It says "Kit Kat Optimizations". How can you optimize for something that hasn't been released? Unless the release date is within the next few days and devs received an early update.
[Nexus 4 Original Android Development] krazeecracker:
Hmm
[Nexus 4 Original Android Development] franciscofranco:
Google shares SDK's and PDK's to partners and selected companies, I wouldn't be surprised if they shared with Feedly team so that they could get their app up and running for KitKat.
[Nexus 4 Original Android Development] raziruelas:
Franco Kernal + Bam Rom

I flashed Bam Rom rc-1 to my LGE Nexus 4.

On JSS my device gets this blue messed up bootanimation then boot with the colors really messed up.

On JWR it does not boot.

Does any body have a fix or know what is going on with my device?

thank you.
[Nexus 4 Original Android Development] dapsANDpoundz:
So would this imply that we'd probably see a release soon? I'm pretty patient with these things normally but the changes look substantial in some areas so can't wait to try it out. Sorry for the off topic.
[Nexus 4 Original Android Development] franciscofranco:
Search colorfix, don't be lazy.

No one knows.
[Nexus 4 Original Android Development] Mercado_Negro:
Hopefully this JLS/JSS/JWR mess will end soon. That's all I care tbh
[Nexus 4 Original Android Development] franciscofranco:
Feedback needed: https://plus.google.com/u/0/106873500108976028532/posts/iuKKsaXhWvc
[Nexus 4 Original Android Development] myfluxi:
CAF startend working on 3.10 in early September. Guess we receive it with 5.0.
[Nexus 4 Original Android Development] Mercado_Negro:
Did you just push the new alpha? I just want to know if I should wait for Google servers as usual (I'm running the stable version).
[Nexus 4 Original Android Development] arlenwoot:
Flash the colorfix linked in my sig after you flash your rom and kernel.
[Nexus 4 Original Android Development] lizaq:
I updated today FKU and I can't get rid of this screen with help info. I tryed swipe, click, clear cache and data, reinstall app. Nothing helped.

Wysłane z mojego Nexus 4 przy użyciu Tapatalk
[Nexus 4 Original Android Development] Rohit02:
Try clicking on the clue button in the right corner. that might be the OK button. :good:

lemme know if it worked
[Nexus 4 Original Android Development] lizaq:
It helped. I was trying this before, but IT is so thin, so I must missed it.

Wysłane z mojego Nexus 4 przy użyciu Tapatalk
[Nexus 4 Original Android Development] franciscofranco:
That's weird, on my device the OK button is 100% visible. I'm running stock.
[Nexus 4 Original Android Development] franciscofranco:
Alpha is live :)
[Nexus 4 Original Android Development] Mercado_Negro:
I like the way Color Control works now, paged. Very intuitive.

There are a few bugs here and there in that section but I'm sure you know them by now.

Nice work, Franco. It's getting there...
[Nexus 4 Original Android Development] franciscofranco:
Bugs? Which ones? Not aware of any bug in there but maybe I didnt stress it enough.
[Nexus 4 Original Android Development] Godaemon:
Great 3 hours unplugged 4.3 min hsic wakelock
[Nexus 4 Original Android Development] zaki67:
The problem is that after making a call 3g is not restored until I restart, I tried turning airplane mode on then off but didn't work.
[Nexus 4 Original Android Development] Taxiback:
What apps?

The play store is instant, Maps is instant, you tube takes about a second. What are you having difficulty with?

---------- Post added at 05:09 PM ---------- Previous post was at 05:06 PM ----------

Not happening here, works as it should.

Did you try the test kernels r24 - r26 I kept loosing my signal after flashing them even after going back to r23. I did a nandroid restore back to stock then went to r28 and all is fine now.
[Nexus 4 Original Android Development] zaki67:
Can I just install the reset kernel and the try the r28 again?
[Nexus 4 Original Android Development] jack1984:
Just flash r28 over it
[Nexus 4 Original Android Development] mosd:
Play store, Facebook, fotbolls manager instagram and so on, all apps actually
[Nexus 4 Original Android Development] Taxiback:
That didn't work for me, I had to restore back to stock to cure the problem.
[Nexus 4 Original Android Development] jack1984:
R28 is so far so good, no problems getting on 3g from Wi-Fi and vice versa.
[Nexus 4 Original Android Development] tanjiajun_34:
Anyone feels performance drop from r23?

Just feel slightly.... My Nexus 4 never seem to lags on r23 but starting to do so on r28... :(
[Nexus 4 Original Android Development] Sim-1:
Do you have a link to the reset kernel? Thanks! :good:
[Nexus 4 Original Android Development] syncopy:
Just flash the stock kernel and flash Franco's. There is no need for a reset kernel, really.
[Nexus 4 Original Android Development] kyokeun1234:
That's because he decreased hi speed freq from 1ghz to 900mhz. You can change that back using his update app
[Nexus 4 Original Android Development] Taxiback:
http://faux.androidro.ms/mako/mako_421_reset_kernel.zip
[Nexus 4 Original Android Development] drawde40599:
28

28 --- absolutely !!! No lag , very fast ( faster than stock for sure ) no data drops anymore , no issues opening any apps or the market or anything else , no heat !! I installed 28 fell asleep at 2% woke up 6 hours later i was still at 2% ( for real ;) ) so battery seems pretty legit !!

Thanks Franco
[Nexus 4 Original Android Development] spinkick:
Hey Franco, how hard would it be to get your kernel on the HTC droid dna? I know it's the same chip, but I'm sure there is more to it than that! Thanks!
[Nexus 4 Original Android Development] mobilehavoc:
I'm on r27 and still not a single data drop. Even in low signal areas. Works great. Only difference left between me and other people having issues is I'm not rooted and flashed via fast boot. That's it.
[Nexus 4 Original Android Development] DaX05:
All is good on r28.

Beamed via Nexus 4
[Nexus 4 Original Android Development] Fr4gg0r:
franciscofranco, could you tell us the configure and make command for building your kernel?
[Nexus 4 Original Android Development] roblorduk:
Run WiFi and 2g at home, have weak signal (about 2 bars normally) but never drops off. Mobile network dropped off completely before and then came back itself. Logs attached. I'm on r28, upgraded about 4 hours ago from r23.

All good apart from that.

Thanks in advance.
[Nexus 4 Original Android Development] Taxiback:
Personally I think r23 was perfect, never had any problems what so ever, it's been slowly going downhill since then. :(
[Nexus 4 Original Android Development] Mercado_Negro:
The first time I pressed and held the minus symbol to decrease the Red value it just got stuck after I raised my finger and it kept lowering it by itself. I actually thought it was the way it worked like press, hold, release: it keeps moving until you press that button again but no, it didn't happen again after I tried it a second time. Also, sometimes it's hard to press those buttons and make them work. It takes a few tries before it actually changes the values. Also, if you go back by pressing the back key the top panel still reads "gamma..." instead of the name of the current section you just came back in.
[Nexus 4 Original Android Development] myfluxi:
"we" as "nexus users", not users of a specific google device.
[Nexus 4 Original Android Development] getaceres:
There isn't any mess. Look at the device it was released for:

JWR is for Nexus phones

JSS/JLS is for Nexus tablets

There isn't any mess, it's very clear from the point of view of Google, two products, two branches. The only mess is that ROM developers want to build phone ROMs based on the tablets code. Then problems arise (like deadlocks) and everyone blame Google for doing what's natural for them. If you own a Nexus phone, use JWR code. Period.
[Nexus 4 Original Android Development] :
Makes sense.

Sent from my Nexus 4
[Nexus 4 Original Android Development] ronac:
I am not undervolting and using stock charger. (but not stock cable, I guess it shouldnt matters), and it did hangs yesterday even it is not charging.

I've touch control installed but disabled.

Seems there should be some bad program running which cause the problem, my ideal plan was to check the log and see what it happens just before it restart. Anything I can do to find out more information?

I was thinking whether I should do a factory reset or not, but I am reluctant to do so as I'd need to install everything again.
[Nexus 4 Original Android Development] dey2929:
Am experiencing deadlocks on r191...am on AOKP mr2 nighly....is there any fix for it ?