yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] ben_pyett:
couldn't have said it better, interactive permits me to turn down the CPU/GPU max when I choose and also configure touch boost, this is especially true when its used in conjunction with franco per app settings.
[Nexus 4 Original Android Development] franciscofranco:
No we're not going to cater for CM at any point starting with 4.4 ;)

No idea, just make sure you don't pull the latest CM nightly changes.

Interactive is not smooth?? That's a first. You can always change back to ondemand if you want.

I didn't count on loss of connectivity when flashing Kernels using FKU. I mean, who would try to auto-flash a Kernel with a flaky internet connection? Smells like trouble to me, but yes I need to treat those in a gracious way in the future.

So THAT's whats causing the repeated SU calls. Thanks a lot, you're the first one that show me a log of the actual command. I'll fix it today and push a FK hotfix.
[Nexus 4 Original Android Development] farris:
Is it normal that I have root issues after flashing the kernel (since 178 or so). TWRP gives me the warning that I lost root en therefor it needs to fix root again. It always works, but I haven't had this untill version 178 (don't know the exact one).
[Nexus 4 Original Android Development] PeQuEsan:
It's not that interactive isn't smooth at all... It's more that it's a little (little) bit slow in reactions to screen touches... at least if you compare it to ondemand. :o That's my observation. If you add to that observation the fact that I can't see big battery drain associated...
[Nexus 4 Original Android Development] zygis10:
Totally agree anyway will try changing some values in interactive maybe that will help.
[Nexus 4 Original Android Development] Bill Gamble:
Update TWRP to the latest version (2.6.3.0, I believe).
[Nexus 4 Original Android Development] PeQuEsan:
We wanna believe Franco! :)
[Nexus 4 Original Android Development] BrandoHD:
This mess with AOSP versions and then with CM doing their own stuff is really crazy, really glad to hear that PA will try to be different
[Nexus 4 Original Android Development] adrok76:
Hi guys,

Anybody have a problem on latest r188 JWR, when in a phone call and the screen goes off, it has difficulty coming back on most of the time?

I'm not sure when it started but I noticed today, I had to call one of those automated lines where you respond to questions by pressing the dialler numbers. When I moved the phone away the screen remained off, I had to press the power button for it to come back on a couple of times, sometimes it did turn on itself, mostly it didn't..
[Nexus 4 Original Android Development] leets4uc3:
PA is amazing. I just wish there was an option to turn off al per app adjustments and change the DPI to what ever I want. This is the only reason I use carbon. (Carbon is wonderful)

BTW no issues using r188 with carbon. (JLS) I can't wait for the n5 and watch the development of FK progress with time as I have done with all my nexuii
[Nexus 4 Original Android Development] jithuelad:
Any idea what is causing this wake lock ?

I never had any while I was on Franco's stable Kernel & Android 4.2.2. But now I am using PA 3.99 with Franco #184. Having this wake lock since last two days. Googled about it but didn't find any useful explanation or what is the culprit ?

Sorry if it is the wrong place to ask
[Nexus 4 Original Android Development] franciscofranco:
PA is also a "no bullshít" project, thats why I joined them.

Thats the proximity sensor playing games with you.

Thats the conjunction of all app wakelocks.
[Nexus 4 Original Android Development] occtec:
[MENTION=3292224]franciscofranco[/MENTION] I seem to be having an issue with display control. I am on PSX v7.1 using your latest jwr kernel. Whenever I reboot super su gives root permission to the app but even on screen of and on again it does not apply my selected profile. Display control does not stick after reboot, any ideas?

Cheers..
[Nexus 4 Original Android Development] adrok76:
Just wandering if there was some more code causing it like last night when it wasn't turning on after sleep?

I'll flash a couple of the previous builds, see if the problem persists...
[Nexus 4 Original Android Development] blsrbl:
Notification sounds seems louder on r188.

Speeking with wakelocks, do task killers cause wakelocks?
[Nexus 4 Original Android Development] adrok76:
You need to screen off/on after reboot..
[Nexus 4 Original Android Development] occtec:
If you read my post I did mention that I have tried screen off/on after reboot BUT it doesn't work :(
[Nexus 4 Original Android Development] adrok76:
Did you wait until your phone had fully booted before trying?
[Nexus 4 Original Android Development] Arstoien:
Does hispeed work properly? I haven't changed the default value (1026 MHz) for several kernel versions and I always see 1.5 GHz, 1.2 GHz (my touch boost freq for a while) and 702 MHz being mainly used. The others as well but I find it strange it's using a lot 702 instead of 1026. To put some numbers here: for the past 2 hours it's used 1:38 min on 702 MHz and just 9s on 1026.
[Nexus 4 Original Android Development] franciscofranco:
That is weird, it should work without any issues. Can you make a profile with ridiculous offset colors, apply, set on boot and then reboot to see if it was applied?

That bug that was present on last night r186 and r187 was caused by a race condition on the thermal throttle driver and the Hotplug driver only when the device was under throttling period. I removed that code on r188 until I can work more on it. Nothing else can possibly mess with the proximity sensor since thats on the Android side and the Kernel has no idea about that sensor existence.

Yes, speaker volume is louder on r188, I boosted it.

If the task killer holds a wakelock then yes. If it doesn't then it doesn't.

Not sure if hispeed_freq is being used at this point. I can definitely check for that, thanks!
[Nexus 4 Original Android Development] baza14:
It must be on your side. I'm too on PSX v7 and it's working as it should.
[Nexus 4 Original Android Development] ben_pyett:
he said he was on v7.1? whats the difference? and don't sat .1 :)
[Nexus 4 Original Android Development] occtec:
So you are using Franco display control? I do not see any option to set on boot??
[Nexus 4 Original Android Development] Testraindrop:
Franco any thoughts on that, do you think it can be true (in a Nexus)?

http://www.phonearena.com/news/Nexu...t-on-a-phone-Lytro-like-functionality_id47900
[Nexus 4 Original Android Development] adrok76:
Delete
[Nexus 4 Original Android Development] occtec:
[MENTION=3292224]franciscofranco[/MENTION] I did as you suggested setup a profile with ridiculous offset colors, screen off/on to apply reboot and my profile was different not even like default but more like it was in between profiles. I wonder if psx gamma values are taking over after reboot? By the way I am using your display control app NOT fku, should I be or will you be updating display control app soon?
[Nexus 4 Original Android Development] adrok76:
OK Mr Smarty Pants! :D Get your butt on RR3, Then we'll see who is stupid!

Seriously though, is this Hardware, 4.3 or ROM issue? Sorry to go OT but I've never had an issue with it before, but I have read in various forums people with proximity issues with no real explanations (not recently).

Everything seems good on r188, however in FKU, If I have a per app power mode, even if I check the box for them to be disabled, I still get a toast saying they have been applied when I enter the app.

Edit: Sorry if you are getting tired of the same - ish questions about FKU, I know you are working on a complete overhaul. I just thought I'd let you know in case you weren't aware of it, I haven't seen it posted before..
[Nexus 4 Original Android Development] Mercado_Negro:
Here's a script you can run with ROM Toolbox to modify the gain in the latest r188:

https://db.tt/5FiXyVu1

You can "set it on boot" to avoid running this command every time you reboot your device.

The default value set by Franco is 20 but I lowered it to 15 because it was distorting a bit without the compressor. You can modify this, though. Just edit the script and change the value from 15 to anything you may want.
[Nexus 4 Original Android Development] Waveblade:
Search is down and for latest Paranoid Android I use JWR kernel right? And that franco kernel can't detect the kernel correctly?
[Nexus 4 Original Android Development] drawde40599:
Read there OP? And if there build prop maches the kernel your sposed to use then FKU works just fine far as i can tell
[Nexus 4 Original Android Development] 3thman:
Nope
[Nexus 4 Original Android Development] yokuyuki:
Haven't had any more wifi drops and the battery life on it is phenomenal. I'm getting about 0.7% per hour idle drain with almost everything syncing, latitude on, and google now on.

You can tell when I'm idling on r23 and when I'm idling on r27.
[Nexus 4 Original Android Development] squadz:
Reverted back to r23. r27 was causing reboots.
[Nexus 4 Original Android Development] stormtroopercs:
Any logs? What you just said was pretty useless.
[Nexus 4 Original Android Development] Stadsport:
Data drops on 27, just like I saw with 24-test. Back to 23 for me!
[Nexus 4 Original Android Development] shamu11:
I finally getting wonders with r27! Thanks a ton Franco!
[Nexus 4 Original Android Development] Globespy:
Wi-fi sleep issues

I posted this in the Q&A section, but after close to 100 views and zero replies, i wondered if it could be kernel related?

I'm on stock 4.2.1 ROM and Franco r23.

I have my Wi-Fi policy set to "never", which should turn it off when the screen is off and the phone is sleeping.

But it's not doing that and I don't know why?

I use Better Battery Stats and an attaching a couple of screens so that someone can suggest why the Wi-Fi refuses to shut off and allow the phone to truly enter deep sleep. The second screen shot shows that Gmail is the top process in terms of battery usage, so I'm wondering if that's the culprit as gmail sync is always set on push, and can't be changed to any other schedule?

If so, this is a huge oversight by Google.

http://db.tt/4029wI0A

http://db.tt/0jN1hVhd

Any ideas?

Thanks!

---------- Post added at 10:00 PM ---------- Previous post was at 09:57 PM ----------

Are you saying r27 is significantly better battery than r23?
[Nexus 4 Original Android Development] direwolf1:
It's not turning off because you have it set to never turn off during sleep. Set it to always or only when plugged in

Sent from my Nexus 4
[Nexus 4 Original Android Development] Ranguvar:
Two hours of idle on WiFi (cell off at home), 0% drop.

r27 checks out for me.
[Nexus 4 Original Android Development] knnhzx:
Hi, so should i flash r23 or 27? which one is more stable?

not required to wipe anything when flashing new kernel is that correct?
[Nexus 4 Original Android Development] yokuyuki:
Yes, it made the biggest difference in battery life than all the other kernel updates at least for addressing the msm_hsic_host wakelock for me.
[Nexus 4 Original Android Development] spaceman860:
Franco r27 is amazing battery life and performance :thumbup::thumbup::thumbup:

Sent from my Nexus 4
[Nexus 4 Original Android Development] yokuyuki:
They both seem just as stable. Some people seem to be running into data drop issues with r27, but it's up to you to try. You don't have to wipe anything when you flash the new kernel though.
[Nexus 4 Original Android Development] siscim23:
Probably too early to tell if 27 can be considered stable, but correct you don't have to wipe anything
[Nexus 4 Original Android Development] jack1984:
Hmmm, I'm having trouble connecting to 3g after being on Wi-Fi with r27. I need to reboot to fix this, though I assume disabling then enabling radio will fix this. Can anyone reproduce this? I had to head out so I flashed back to r23 but will post logs if I'm the only one experiencing this.
[Nexus 4 Original Android Development] scream4cheese:
You're not the only one. Unfortunately, it's happening to other users as well.
[Nexus 4 Original Android Development] mobilehavoc:
Well its obviously not just the kernel if not everyone is experiencing it. Maybe a combination of kernel, rom and an app or something. My point is if its purely the kernel I would have at least one. I ran 24-25-26-27 on 3G for a long time and never had an issue. The bits in my boot partition are the same as yours and you had the issue so perhaps its some other factor. Smh
[Nexus 4 Original Android Development] yokuyuki:
Didn't have any issue getting back on 3g here after being on wifi all day.
[Nexus 4 Original Android Development] tx3kgtman:
Data issues here also. On at&t. Have to reboot my phone constantly to regain data. I'm running the latest cm 10.1 nightly if that matters.
[Nexus 4 Original Android Development] knnhzx:
which is a safer choice? r23 or r27?

what is the difference between them? and between stock kernel.

able to return to stock kernel if i do not like the r 23 or r 27?
[Nexus 4 Original Android Development] gpvecchi:
So, which ROMs do add the FLO code? Just the CyanogenMod? I decided to abandon CM as it's too "closed", but I'd not like to full wipe for another incompatible ROM...
[Nexus 4 Original Android Development] rxmxsh:
Carbon and AOKP have it as well.
[Nexus 4 Original Android Development] gpvecchi:
ParanoidAndroid?
[Nexus 4 Original Android Development] rxmxsh:
Based on Franco's comment above, I think they are good to go.
[Nexus 4 Original Android Development] ensboarder:
What is FLO?
[Nexus 4 Original Android Development] UgoBoss:
Does anyone knows which kernel do I have to flash with a JLS build please ?

Thank's ! :)
[Nexus 4 Original Android Development] GriffenD:
The one with the JSS tag
[Nexus 4 Original Android Development] Bill Gamble:
http://wiki.cyanogenmod.org/w/Flo_Info
[Nexus 4 Original Android Development] rxmxsh:
Carbon has an unofficial JWR kernel compatible build now.

http://xdaforums.com/showpost.php?p=46117395&postcount=9004
[Nexus 4 Original Android Development] gpvecchi:
A part of code which is not AOSP, I assume to correct deadlocks, but which make s incompatible all custom kernels...
[Nexus 4 Original Android Development] Marreboy:
Are you sure about that? Isn't Flo the code name for Nexus 7 (2013)? Just like Mako is the code name for Nexus 4.
[Nexus 4 Original Android Development] gpvecchi:
Probably they merged some code from new Nexus 7... I don't know; but for sure, custom kernels don't work...
[Nexus 4 Original Android Development] fozzie:
C'mon, you just made that up (or you like spreading disinformation). It's the codename for the new Nexus 7 2013.
[Nexus 4 Original Android Development] gpvecchi:
I was sure I read it...
[Nexus 4 Original Android Development] TheDarkDefender:
Flo is nothing but the new nexus 7s codename

Sent from my Nexus 4
[Nexus 4 Original Android Development] fozzie:
Read what? Mako is the codename for the original Nexus -7- 4 and Flo the codename for the new Nexus 7 2013. It has nothing to do with parts of code, AOSP, CM or anything related. It is just a device codename.

Edit: as pointed out, my 7 was meant to be a 4
[Nexus 4 Original Android Development] Mantulis:
I see and what codename is for nexus 4 ? :rolleyes:
[Nexus 4 Original Android Development] krazeecracker:
Grouper is the original Nexus 7, Flo is the 2013 Nexus 7, and Mako is for us.
[Nexus 4 Original Android Development] daivee:
Mako = nexus 4
[Nexus 4 Original Android Development] Mantulis:
I know. Just look at his post. What was joke :p
[Nexus 4 Original Android Development] fozzie:
Now that was a bad typo. It comes from having too many devices.... but the point still stands. I'll refrain from the yaaaawn eye rolling thing though :)

---------- Post added at 10:46 PM ---------- Previous post was at 10:40 PM ----------

Thanks for the clarification after my fishy typo. I couldn't have put it better myself :)

(Let's all keep our skirts on here; the actual point being that Flo is a device, not code.)
[Nexus 4 Original Android Development] dagansta24:
Hi sorry if this question have already been asked but have the sound drivers been fixed on 4.3 roms the music with headphones nothing like 4.2 roms with sound control
[Nexus 4 Original Android Development] sordna:
Um, for a 63 byte file, you have could used code tags and/or just pasted it instead of dropbox :)

Here it is for people just reading the posts.

#!/system/bin/sh
echo 15 > /sys/devices/i2c-0/0-0058/fixed_gain

EDIT: I use this free app called SH Script Runner, it's WONDERFUL for writing scripts, keeping them in one place, and running them all from the GUI either with root or without:

https://play.google.com/store/apps/details?id=com.adamioan.scriptrunner
[Nexus 4 Original Android Development] santeana:
Sorry if this has been mentioned, but I see a lot of people wondering what Flo is, what caf is and just wtf CyanogenMod is doing lately. Well, it is explained a little better here. http://xdaforums.com/showpost.php?p=46098546&postcount=15393

Hope it helps. It helped me! :)
[Nexus 4 Original Android Development] Floydfire:
[MENTION=3292224]franciscofranco[/MENTION] i know is an offtopic but in your opinion is worth to update pa to latest nightly or is less bugged the rc2? Or you didn't know and don't like my question?

Inviato dal mio Nexus 4 con Tapatalk 4
[Nexus 4 Original Android Development] Mercado_Negro:
You're welcome :thumbup:
[Nexus 4 Original Android Development] limeaide:
Francisco how can I lower the notification volume? Even turning it down via sound makes it sound distorted and really loud haha.

Sent from my Nexus 4
[Nexus 4 Original Android Development] justibasa:
I'm loving Franco's kernel. Therefore looking to get away from using cm. Looking for another rom like cm. I'm not into a lot of features. I can't stand pa or carbon. Liking for something that includes the theme chooser and has pie. Any recommendations would be great. Thanks!

Don't like me.........BITE ME!!!
[Nexus 4 Original Android Development] Mercado_Negro:
SlimBean
[Nexus 4 Original Android Development] justibasa:
So it has pie and the theme chooser? Guess I'll try it thanks.

Don't like me.........BITE ME!!!
[Nexus 4 Original Android Development] occtec:
[MENTION=3292224]franciscofranco[/MENTION] I purchased your fku app which has resolved my display control profiles from not sticking after reboot. Your display control app no longer works for me anyway after reboot BUT fku has done the job. Thanks again Franco for another awesome app :thumbup:
[Nexus 4 Original Android Development] michelemascia7:
[MENTION=3292224]franciscofranco[/MENTION] Thanks for your work :) but the franco.kernel app(donate version) don't save my personal color profile, and i can t load it :/

Inviato dal mio Nexus 4 con Tapatalk 4
[Nexus 4 Original Android Development] occtec:
Make sure to screen off/on again to apply settings ;)
[Nexus 4 Original Android Development] drawde40599:
Make sure your SU working correctly, if your not useing chainfire SU i highly recommed it
[Nexus 4 Original Android Development] CM Wave:
I thought SlimBean didn't support franco's kernels anymore? Has this changed? I sure hope so.
[Nexus 4 Original Android Development] Testraindrop:
Ok guys as it seems its time to move away from CM, can anyone help me find the right Rom that works with franco kernel?

I need just quiet hours, advanced autobrightness, custom LED colors and quick toggles like on CM, no such feature overflow like PA.
[Nexus 4 Original Android Development] sordna:
Best ROM for franco.kenel and piece of mind is stock 4.3 (soon 4.4) with apps to do what you need:

Llama, Lux, Light Flow, Power Toggles, and optionally a good launcher like Apex or Nova.

Seriously, I tried CM and went back to stock. I also like my updates to be small, and over the air.
[Nexus 4 Original Android Development] sNoxious:
Try Purity. Haven't missed CM ever since I tried that Rom. :good:

Sent from my Nexus 4
[Nexus 4 Original Android Development] Mercado_Negro:
Yes, it has.

franco.Kernel is supported in SlimBean since r184. You need the JWR version.

SlimBean has all that

I'd strongly suggest you to visit www.slimroms.net . These devs are very organized and they actually care about their users, unlike CM.
[Nexus 4 Original Android Development] swirly05:
Question: The "tick" sound when pressing home, menu, etc...

I like the sound on but my question is, "how do I turn it down from tick'n so loud, what setting it that under in the Trickstermod sound control app?? Thanks
[Nexus 4 Original Android Development] joni_strokes:
did anyone has the same problem on 188jss? everytime browsing with chrome (stable version) it will closed automatically (carbon rom build 1st october), went back to version 184, chrome works normally.
[Nexus 4 Original Android Development] swirly05:
Edit
[Nexus 4 Original Android Development] drawde40599:
U cant do just the tick but u can lower volume, Read threw last changlogs to find the code to do it through terminal or someone made a skript few pages back u could modify, Your not going be able to turn it down with trickster
[Nexus 4 Original Android Development] jimbohurt:
I do not want to high-jack the thread, sorry, I just trust you guys and this is like the only thread I really chill in. Just real quick, what is the most lightweight ROM out there but that has theme engine? I would use purity or psx but I love theming too much. Thanks :)
[Nexus 4 Original Android Development] sordna:
screen became unresponsive

My screen became unresponsive this evening, I used tap to wake feature all day (running r188 on stock 4.3 rom) but this evening after interacting with the phone and putting it down so the screen turned off, it would no longer tap to wake. I woke the phone with the bower button, but discovered the screen would not respond, only the physical buttons would. I was able to change the volume, even take a screenshot, so the phone worked except the digitizer was dead and my phone would not respond to touch.

But I couldn't reboot the phone, because you have to tap the screen after you press the power button that pops up the shutdown menu. I had no ssh server running at the time, and usb debugging was off. So I was forced to restart the phone ungracefully by holding down hte power button for several seconds.

Francisco, any idea why the digitizer would stop working? Other people reported it on earlier pages too, starting with the 185 test builds.
[Nexus 4 Original Android Development] Cantacid:
Hey [MENTION=3292224]franciscofranco[/MENTION]

I remember you had plans to fix the mic on this phone, id just like to know if its still in the pipeline or has the whole idea been scrapped?

---------- Post added at 11:01 AM ---------- Previous post was at 10:59 AM ----------

Closest to stock, stable as hell and works brilliant with franco
[Nexus 4 Original Android Development] davidbar93:
Purity and PXS are the most powerful roms I've tried so far... Both of them are very stable and super smooth.
[Nexus 4 Original Android Development] :
Whoa! I'm literally doing the exact same thing. :D

The SAME set of apps & Stock 4.3 + franco.kernel. :good::laugh:
[Nexus 4 Original Android Development] Mercado_Negro:
Yes, stock is a safe bet as well. I'm kinda tired of all these problems and that's why I switched yesterday to stock. I really like SlimBean and AOKP but there are still some rough edges I want to avoid. I just like stability.

Right now I'm on stock + franco.kernel r188 + Xposed with a module called GravityBox which seems to work well so far.
[Nexus 4 Original Android Development] Goku80:
you should try crdroid.....actually really fast and freaking stable...

to everyone else i have a question and apologies if this has been asked before...does anyone find that Touch control drain battery? what i mean is would TC drain more battery than the normal doubletap to wake of Franco's?

and for some reason colour profiles do not seem to stick after reboot....first time i had this happen
[Nexus 4 Original Android Development] aldyu:
Well, the safest would be on all stock. ;) but then it would be boring...

Sent from my Nexus 4
[Nexus 4 Original Android Development] TheDarkDefender:
Lol. I'd rather get a Nokia :p

Sent from my Nexus 4