yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] thebuga:
I got that it would be a no for an answer since the first reply. I am just saying that it is a great idea to think about.

As Gmote, Unified Remote is nothing close to the concept of USB Keyboard. Its all about getting physical! :)

I will try to virtualize a Linux machine and give the whole kernel build thing some try.
[Nexus 4 Original Android Development] yochananmarqos:
Ah, I see what you mean now, Since Gmote was previously mentioned I immediately thought of Unified Remote. You could always run Android x86 on a netbook like I do. It's like a tablet with a keyboard attached! :cyclops:
[Nexus 4 Original Android Development] thesupreme85:
will this kernel work with PA rom newest 4.5 version ? ? ?

thanks
[Nexus 4 Original Android Development] buu1152:
I've tried that a million different ways it doesn't work.. I shouldn't have root issues, but it says to check root. :s It still works fine. Until reboot.
[Nexus 4 Original Android Development] BelzIgoh:
Yes, absolutely. :D

And don't forget to buy franco kernel app from playstore to tune the kernel into your usage style.
[Nexus 4 Original Android Development] thesupreme85:
thanks will try it right away

btw i always use FKU with this kernel its a must ! ! !
[Nexus 4 Original Android Development] ken_alpha24:
PA + Franco + PerApp Modes. :D
[Nexus 4 Original Android Development] Galaxyfire:
[MENTION=5189704]ken_alpha24[/MENTION]

WLAN or mobile connection ?
[Nexus 4 Original Android Development] garuhhh:
Anybody having issues with GPS?

After turning off the GPS, it seems to still remain ON. Apps using location consumes battery, but indicates that the GPS keeps it awake.

Edit: I've had this problem even in gNexus with Franco.

I'm running all stock, on ART
[Nexus 4 Original Android Development] RealSlimShadyMC:
Come to think of it, I had an issue with that too

I remember in 4.3, there was a sticky GPS issue where if an app was still using GPS when it was being disabled, it would remain stuck and continue looking for satellite. Perhaps this issue somehow resurfaced with one of Franco's patches?
[Nexus 4 Original Android Development] ken_alpha24:
90% of the time Wifi is on.

10% for Data
[Nexus 4 Original Android Development] AJ06:
I'm not having this GPS issue. My battery stats only show the GPS as on when it is being utilized by Maps.
[Nexus 4 Original Android Development] garuhhh:
My GPS issue doesn't always happen. Sometimes its OK, sometimes "That" happens.
[Nexus 4 Original Android Development] i2k13:
:cyclops:

Turn it off only via the location menu, don't use any kind of toggle.
[Nexus 4 Original Android Development] BigDig:
Hint..
[Nexus 4 Original Android Development] donteo:
Test kernel ...
[Nexus 4 Original Android Development] buu1152:
Get wakelock detector bro, see what apps using the gps then greenify with greenify and it won't be able to use gps, also pay for the donation greenify and you can cut the path that the app uses for the gps.
[Nexus 4 Original Android Development] garuhhh:
Yeah, I also thought of that. But no use, I'm not using any toggle switches recently.

I also checked the wakelocks, all is normal. Its just that GPS seems to be on, and that's what's causing the battery drain, and not the apps themselves.

I don't want to greenify the apps, as I need them to be ON. Besides, all these apps are fine as long as I don't turn on the GPS.
[Nexus 4 Original Android Development] razorsbk:
So this is available for our phone also ? Or its just for Nexus 5 ?
[Nexus 4 Original Android Development] atulclassic:
You are in N4 community hence available for N4
[Nexus 4 Original Android Development] blackbird5308:
Actually, no, that is an extract of a Nexus 5 commit made by franco, hence it's not N4 related ^^

That said, i don't know, must check!
[Nexus 4 Original Android Development] franciscofranco:
That patch is for the 8974, not 8064!
[Nexus 4 Original Android Development] franciscofranco:
Pushed r211! Happy hackings!
[Nexus 4 Original Android Development] Galaxyfire:
[MENTION=3292224]franciscofranco[/MENTION]

Thanks for the update, you are great !
[Nexus 4 Original Android Development] Fenvarien:
Awesome update, thanks! :good: :)
[Nexus 4 Original Android Development] yanleites:
Thank you! The update is great!:good:
[Nexus 4 Original Android Development] RealSlimShadyMC:
Battery life has improved quite a bit with the latest version so far, may be placebo but it drains noticeably slower
[Nexus 4 Original Android Development] Galaxyfire:
It could be because of the interactive patch in r211
[Nexus 4 Original Android Development] alexandreantunez:
Great update! Is it really safe an overclock at 1728 MHz? I know Franco wouldn't put it in dangerous way, but...
[Nexus 4 Original Android Development] RealSlimShadyMC:
Its safe, but kinda pointless.

The way that the S4 Pro works is, if the device only has 2 cores(such as the Moto X) then it will work at 1.7GHz, but if it has 4, then it limits itself to 1.5GHz. There's no harm, but I think he only put it there to stop people from begging for it. Correct me if I'm wrong though
[Nexus 4 Original Android Development] franciscofranco:
No... it will clock all of them to 1.7GHz normally, there's no clock restriction unless you're thermal throttled.
[Nexus 4 Original Android Development] RealSlimShadyMC:
Ah, cheers :)
[Nexus 4 Original Android Development] Hanny:
Saw 1728 and did a pretty quick gaming test, didn't follow the thread much and wow, that OC talk :)

For those unfamiliar with my tests they are done by

- start fps meter (disable hw overlays for necessary games)

- start game, neglect first average fps reading

- record 2nd and 3rd avg reading (updates once per minute)

settings are all default except my input boost being 1350

riptide gp2

1512mhz: 38-39fps

1728mhz: 41fps

minion pro (probably the heaviest game i have installed currently)

1512mhz: 32fps

1728mhz: 31-32fps

I don't know about how things work theoretically, because over the hundreds of prev kernels I only rely on the results of gaming performance.

So at the end of the day I think how the OC works / doesn't work depends on how the app utilises the CPU, and how do you value the fps increases (well, 3 is not small because it is the average fps, which requires a consistent performance increase throughout the game session). Over the past experiences I strongly believe riptide gp2 uses a lot of cpu power to draw the map ahead, so I loved using it to test stuff.

It's simply logical that high freq produces better fps results, but bear in mind that the effects are not universal.

battery life... I never comment on it. I'm running 1728 at 1150mv which is 1512's stock voltage. No overheating or throttling while I was testing. Also in normal usage I don't see them being ramped up to 1728 unnecessarily, thanks to the kernel's magic. In frequent swiping and typing it keeps using my input boost freq, and only uses 1728 for a sec when stuffs load, just like how it used 1512 before OC was available. I like how this works.

I am very happy with it. :) Thanks franco for the mako love!
[Nexus 4 Original Android Development] albundy2010:
Wrong. The moto X has krait 3OO cores among other things. It is simply a dual core version of the snapdragon S600 in layman's terms

Qualcomms naming scheme is a hot mess. But your statement is simply wrong.
[Nexus 4 Original Android Development] RealSlimShadyMC:
I read that on a few forums, but thanks for clearing that up :) I saw other SnapS4Pro devices at 1.5GHz, and then the Moto X and thought it was a core dependent thing
[Nexus 4 Original Android Development] HiM@L:
guys...does anyone change value for audio using fku... if so, can you please provide me the values. thanks in advance.
[Nexus 4 Original Android Development] HiM@L:
sorry if that sounded confusing... i meant these values at the bottom... volume gains
[Nexus 4 Original Android Development] franciscofranco:
Use whatever you want to use, it's not like we have your ears, your headphones, your music sensitivity, your tastes...
[Nexus 4 Original Android Development] Maibol:
hoooo overclocking ....... franco is getting dirty lmaoooo..... i have to ....franco can you add low frequency's ? on the cpu and gpu 192 mhz is completely stable for me and for a lot of people.. 81 mhz is messy for a lot of people 27 mhz on gpu works like charm 2 lol ...... i know .... i know guys but hey i have to try now hes in the mood lmaoooo:p
[Nexus 4 Original Android Development] franciscofranco:
Absolutely not.
[Nexus 4 Original Android Development] borito24:
Headset volume boost 3

Headset gain boost -5 or -7
[Nexus 4 Original Android Development] alanwyl:
My phone crashed after OC.

Spoiler content hidden.
[Nexus 4 Original Android Development] garuhhh:
Mikael also updated his builds. This morning the r211-based has "Not-tested" prefix, now that prefix has been removed. Downloading it now to test it out.
[Nexus 4 Original Android Development] vrolok:
Edit: deleted
[Nexus 4 Original Android Development] mistersixt:
Thanks a lot Franco, from time to time I am testing some other kernels... but at the end your kernel including your franco app is simply the best combination ;) ... and r211 runs flawless on my N4, even when giving oc a try (and giving the people the choice to oc or not is the best solution in my opinion).

Keep up the brilliant work :good: ,

mistersixt.
[Nexus 4 Original Android Development] AJ06:
Brah, hell is upon us.

haha omg r211 is dirty :good:
[Nexus 4 Original Android Development] yanleites:
Mikael's build works great too!
[Nexus 4 Original Android Development] garuhhh:
Yeah! Here too! I can't comment on battery life yet, as I ve just been using it for a few hours.
[Nexus 4 Original Android Development] vampire36:
1 quick query don't you have screen freeze especially when kept in pocket with dt2w enabled ?
[Nexus 4 Original Android Development] garuhhh:
Havent had one. Though I position my phone screen away from thigh to reduce unintentional touches. I was guessing that might reduce batt consumption.
[Nexus 4 Original Android Development] vampire36:
I ll give it a try that way if that help :)

also your dt2w conf...

Mine is...

doubletap_to_wake=Y

doubletap_pwrkey_suspend=Y

doubletap_charger=1

doubletap_area=3 //centre of the screen
[Nexus 4 Original Android Development] garuhhh:
Yes, that's mine as well. I chose center as the double tap area, I accidentally press the EMERGENCY with the default bottom double tap area.
[Nexus 4 Original Android Development] Pac-Man:
Mmm... I did not understand why you were talking about overclocking... I mean, I'll try to explain myself (not stock but franco's kernel):

- Nexus goes to 1.7Ghz automatically.

- If temperature is going too high, it goes to 1.5Ghz because of thermal throttled.

Is that right? I guess I could manage to set default high frequency to 1.5Ghz instead of 1.7Ghz (I hate overclocking).

Thanks in advance :)
[Nexus 4 Original Android Development] underskyzx:
Any chance to add support for brightness linear/exponential?

Screen is to bright imo
[Nexus 4 Original Android Development] fabry90:
Francisco Franco. The best kernel developer in XDA. :good:
[Nexus 4 Original Android Development] blackbird5308:
May i ask you a thing then? why there are the same files for 8974 also in our kernel tree? are they simply discarded? :)

Also, 211 is great :D
[Nexus 4 Original Android Development] Danny.ns:
I'm pretty sure you have to manually enable the 1.7ghz clock.

So if you want to do it, you can head into CPU settings, and set max CPU frequency to 1.7ghz from 1.5ghz.

Big thanks for r211 franco! ^_^
[Nexus 4 Original Android Development] Matteo Mazzu:
Hi! I have some question... Does UV do something like saving battery, or it's just a myth? And, I've been using my N4 as a dual core for a few months, with the input boost at 1512MHz (I love having the phone really speedy, and because I don't play games this setup seem the best for saving some battery and having incredible performance); now I'm using the 1728MHz as input boost ,is it risky this high or doesn't matter for the health of my phone? Thanks for every comment about it! :)
[Nexus 4 Original Android Development] menting:
Depends on your usage

The less your screen is on, or the less you use data or wifi, the more the cpu power usage affects overall battery life. In that case, UV will have more of an effect

Of course, the tradeoff is that if you UV too far such that there is no voltage margin built in, you might start seeing instability under certain cases.
[Nexus 4 Original Android Development] svnhvn:
Sh*t, i really love r211.
[Nexus 4 Original Android Development] Matteo Mazzu:
I UV at - 125 with no side effect at all, now I'll see if does effectly some benefits at battery life.. r211 is awesome I must say! The possibility to OC is something I always wanted because of my dual core phone usage :)
[Nexus 4 Original Android Development] RealSlimShadyMC:
I undervolt to reduce heat, (at -125v) but not much battery improvement
[Nexus 4 Original Android Development] svnhvn:
Usually i go for -50 or -75 max.
[Nexus 4 Original Android Development] ajack2001my:
Thanks Franco for the overclocking options. :)
[Nexus 4 Original Android Development] scissorscrush:
Anyone else having huge battery drains with r211, on mine it's huge. Never happened before with any update.
[Nexus 4 Original Android Development] shakatu:
Nope.
[Nexus 4 Original Android Development] RealSlimShadyMC:
With the latest update, I get a kernel panic after taking a photo with Google Camera. I'll grab a kmsg next time it happens
[Nexus 4 Original Android Development] franciscofranco:
No.

There is a Kernel panic case related to the camera that has been around since the N4 exists. I added a if (x == null) return; in one place, but wasn't enough. Nevertheless, post the log.
[Nexus 4 Original Android Development] RealSlimShadyMC:
I tried to force it by taking multiple photos but my camera crashed and refused to load, rebooted and tried to take a photo and it crashed again. I'm stuck in a loop, however I'll try a cache wipe and come back
[Nexus 4 Original Android Development] scissorscrush:
So that must be my cat then... Hmm
[Nexus 4 Original Android Development] hypemanisus:
Anybody with the color fix I wanna use this kernel got my other cm rom

I LOVE MY SLUTTY N4
[Nexus 4 Original Android Development] olygopoly:
May I know which ROM work best & compatible with latest R211 Franco kernel ?
[Nexus 4 Original Android Development] silvagroup:
If I recall it's developed for stock I use stock and works GREAT. But can be used with several other Roms. Read back through post and you can see which ones work or have a version branched.
[Nexus 4 Original Android Development] olygopoly:
Thanks for the reply. Unfortunately I've not been using Stock ROM since Im using the additional features provided by custom ROM.
[Nexus 4 Original Android Development] dmourao:
Stock rom + xposed + gravity box. :good: :victory:
[Nexus 4 Original Android Development] olygopoly:
Oh totally forgot about x pose. Hurm I might tried it though... Thanks for the feedback
[Nexus 4 Original Android Development] :
+1

I recommend this combo, as well. Gravity Box is amazing.
[Nexus 4 Original Android Development] franciscofranco:
And again, anything that is built from CM won't work, the rest will.
[Nexus 4 Original Android Development] abalam:
Pfff and again again and again.....:what::what:
[Nexus 4 Original Android Development] Flipz77:
I understand your enthusiasm for the xposed project, but not everyone wants to stick with the old stinky dalvik when there's a much *cough*better*cough* runtime out there that's been around for months and makes speed, smoothness, stability and battery awesome, especially on this fantastic kernel! Custom ROMs are still the bomb, and I'm happy Google finally decided to put an end to dalvik. The battery life with stable L + franco kernel is gonna be ossum!
[Nexus 4 Original Android Development] atulclassic:
[MENTION=3292224]franciscofranco[/MENTION]..anyway to keep the cpu temp down..mine is heating upto 62C with 1512Mhz at maximum CPU freq.

running R211 Governer Interactive I/O row

any help is appreciated.
[Nexus 4 Original Android Development] RealSlimShadyMC:
Try undervolting a little. It helps with heat
[Nexus 4 Original Android Development] atulclassic:
already UV-50 for all freq and UV -100 for 384Mhz
[Nexus 4 Original Android Development] RealSlimShadyMC:
WiFi or 3G?
[Nexus 4 Original Android Development] atulclassic:
No WiFi..corporate connection hence 3g not provided..using 2g only
[Nexus 4 Original Android Development] RealSlimShadyMC:
That might explain it, using the wireless radio heats the device up. Should be fine if you don't touch it for a bit or use WiFi later
[Nexus 4 Original Android Development] atulclassic:
ok..but that's not the case with r210 & even r209..both were working fine and i am using 2g since i purchased this device 2 months ago.
[Nexus 4 Original Android Development] migueldbr:
Does this kernel have cpu state C3 enabled?because synapse shows it enable, along with C0...i have cleared data from synapse, cache and reinstalled and it always shows C0 and C3 enabled(im asking this because i saw that franco was against enabling the "power collapse" state (or something like that, i dont really know what im talking about lol)
[Nexus 4 Original Android Development] RootNightmareX:
I had a reboot today after updating to r211, no overclock uv 1075 (1,5ghz)
[Nexus 4 Original Android Development] franciscofranco:
Its summer and the N4 has glass, what were you expecting? Try to use stock Kernel, you'll be able to cook an egg in there.
[Nexus 4 Original Android Development] franciscofranco:
Why are you talking about something that you don't know? When did I say that I wont "enable power collapse"? Leave the power states alone, the N4 chip have some restrictions and you'll end up in problems if you start messing with stuff like that.
[Nexus 4 Original Android Development] migueldbr:
thats exactly the point, i am trying to understand...i think i remember seeing that you wrote in this thread(or another one) that c3 should not be enabled in the nexus 4 because of the chip restrictions, and synapse shows C3 enabled(and i didnt change any settings).

Não leves a mal, estou mesmo só a tentar compreender se é suposto estar ligado ou se foi algum erro do synapse
[Nexus 4 Original Android Development] derking1:
Can anyone screenshot or tell me how much did they undervolt their cpu voltages so I can see good battery life and stuff? I wish this was able to go down to 192mhz like Matrix...
[Nexus 4 Original Android Development] scissorscrush:
I have it UV-150, basically it depends on each phone and you'll have to test it on your own.
[Nexus 4 Original Android Development] zoym:
So, the PA not?
[Nexus 4 Original Android Development] atulclassic:
PA is not CM..its AOSP..so this kernel will work on PA
[Nexus 4 Original Android Development] :
Feeback on r211 Overclocking

Stock settings, battery and performance are good as they've been, very stable and smooth performer. With the CPU overclocked to 1728MHZ, I get random reboots, same thing happened after a factory reset, like every 30 mins or so or many times when in the middle of calls. If I set the clockspeed back to 1512MHZ, no reboots, all is stable. So, maybe my nominal CPU cannot handle overclocking. Do you need a logcat [MENTION=3292224]franciscofranco[/MENTION]? I am not a big fan of overclocking, but testing this out is certainly interesting.
[Nexus 4 Original Android Development] Pac-Man:
Hi! You don't have to gave him a logcat but a log file that is in /proc/last_kmsg.

Cheers :)

==========

tapatalked!
[Nexus 4 Original Android Development] aviz1911:
Chicken 65 is ready Franco. I invite you for dinner :p
[Nexus 4 Original Android Development] derking1:
Any faulty problems running ART with Franco Kernel? Mind that I'm using C-Rom aswell.
[Nexus 4 Original Android Development] RealSlimShadyMC:
Google is your friend...

To save some time, runtime has nothing to do with kernel.
[Nexus 4 Original Android Development] BassBlaster:
I experienced the same thing aswell, random reboots when setting max frequency as 1.7GHZ. However, on 1.5GHZ max no problem at all. Unlike you though, I have undervolted by -175 mV. Also a Nominal CPU here.
[Nexus 4 Original Android Development] benrees21:
A bit red to me. Gonna give it a while to get used to it.

A Nexus Connoisseur!! AOSPA!! Franco Kernel!!
[Nexus 4 Original Android Development] Miragej:
That's absolutely insane! I lose 1% just sending a text message on r28 and minco v6! D:
[Nexus 4 Original Android Development] Nark.GA60:
I'm getting this too. Might not be a kernel thing 'coz I'm still using r14. CM10.1 issue, perhaps? I'm running the nightly from the 5th.
[Nexus 4 Original Android Development] Hrithan2020:
Well firstly it was mostly on wifi . So was expecting a bit more. [there were a few wakelocks, but nothing major]. Plus having a "faster" binned cpu. [Don't think that matters with franco though]

I guess I didn't face much issues with r28. Not going to try r18 as the data speeds are anyway restricted by our ISP here.

Most likely a battery calibration issue. I'm willing to bet my phone that your battery will drain fully, even before you reach 56x50 mins of GPS on and y[the few mins spent playing spotify]x50 mins of spotify. :P
[Nexus 4 Original Android Development] KonstantinKeller:
Not 50 minutes of Spotify, like 5 minutes :P
[Nexus 4 Original Android Development] Hrithan2020:
You didn't get my point. If you lose 1% with 56 minutes of GPS on, then that means that you will lose just 50% with 56x50 mins of GPS on, which I am sure won't happen.[ Or 5% with 56x5 mins of GPS on]

Hence, it is just a battery calibration issue. Cheers.
[Nexus 4 Original Android Development] KonstantinKeller:
I do understand what you mean. I'm pretty sure it's not a calibration issue though. My battery has been running great all week. It's at 82% currently, so it's not as full as before. The GPS was from Endomondo Pro, if that makes any difference.
[Nexus 4 Original Android Development] Fidelator:
Franco, Is it possible to release your display control app for other devices? (Like the Nexus 10, which NEEDS it)
[Nexus 4 Original Android Development] franciscofranco:
Good morning everyone! 2nd day of CES is starting. Good news though, instead of onlining the second core everytime the screen is touched it only does that is the user is interacting by swipping. Works pretty well :) Im very excited to release this build sometime today!
[Nexus 4 Original Android Development] Gaheris:
Almost four days without charging. Thank you Franco ! Of course, only moderate use of the phone with 2.5 hours of screen time but best battery performance so far. Using r28 and cm 10.1
[Nexus 4 Original Android Development] port76:
anxiously waiting for new build thanks Franco ;)
[Nexus 4 Original Android Development] danielvc:
FINALLY!!! I was getting a serious Franco kernel withdrawal!:victory:

Seriously: take your time and enjoy CES, I'm following The Verge's coverage and it looks amazing.
[Nexus 4 Original Android Development] noneabove:
Beautiful!! What's the next item from your list that you're thinking of tackling?
[Nexus 4 Original Android Development] franciscofranco:
I made a list somewhere in the last 50 pages.

And wow XDA doesn't stutter anymore :))
[Nexus 4 Original Android Development] schizophrenia:
deleted. thanks
[Nexus 4 Original Android Development] Hrithan2020:
Wow!! That is great news. I am right now trying out all kernels and it seems all the kernels I tried have issue with tapatalk/xda app.

EDIT:

Found the link you were talking about after page hunting. You were right , it was 43 pages back.

Here is it:

http://xdaforums.com/showpost.php?p=36378598&postcount=5282

And here is your post regarding your thoughts on how onlining the 2nd core will help:

http://xdaforums.com/showpost.php?p=36379161&postcount=5292
[Nexus 4 Original Android Development] CMNein:
I find it a bit hard to read your text colour; black is always a safe bet. Slight red/green colour blindness, curse my inferiour genes :cyclops: