yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] Taxiback:
r27 and r28 aren't test builds they're nightlys just as r23 was, so yes I do expect things to go wrong in the test builds but the nightlys are usually bang on.

It appears that r27 and r28 are just a mixture of the test builds so yes I still expect problems.
[Nexus 4 Original Android Development] UZ7:
They're labeled nightly for a reason :)
[Nexus 4 Original Android Development] Taxiback:
And the difference between a nightly and a test build is?
[Nexus 4 Original Android Development] roblorduk:
By patching the next release that Franco brings out if you find r28 not usable and you drop back to r23. :)
[Nexus 4 Original Android Development] Luigiesin:
R26 fixed my issues... I flashed R28 this morning looking to work out the wakelock issues....

So far I see my data a bit faster with R28, even when signal drops to 2G...

Going to check the battery efficency and report back.... But so far, pretty good!

Lu

BTW, using CM10.1 early December version.

Max 1.2

Min 384

Hi load 65

Hi freq load 810

No lag!
[Nexus 4 Original Android Development] kitch9:
Nightlys are built based on positive user feedback from Test builds, Test builds contain brand new untested experimental patches and settings it appears.
[Nexus 4 Original Android Development] CMNein:
I look at test builds as alphas, nightlies as betas, milestones as stables.

That said between "beta" Franco kernels, and a "beta" rom like a CM nightly, my phone is stable.
[Nexus 4 Original Android Development] drawde40599:
Until he release a milestone there ALL test builds , he added extra word test in front of them cause he didn't test them himself before release and because of this they were not added to app , I've installed 100 Franco kernels on my GNex some work some don't some break **** some fix **** some are great some are no. , thats how he gets his milestone WE test them and help , to say there all going downhill is ridiculous to me , no one said u have to install this kernel or any build ,if u have a issue try to help him fix it not talk **** .

not just my opinion that's how it works ;)
[Nexus 4 Original Android Development] Taxiback:
So where are the test builds between r9 - r23? franco usually does his own testing.

---------- Post added at 07:58 PM ---------- Previous post was at 07:52 PM ----------

Well, ALL is only 3 "test builds" and 2 nightlys.which are just a mix of the test builds. :)

r27

This should be the latest version before the first Milestone labeled release is out

* This release is based on test releases r24-test, r25-test and r26-test which include:

- Interactive governor fixes from Google

- Improvements to the Hotplug driver for bettery battery without sacrificing performance

- Make the thermal control a little more aggressive to prevent heat

- Qualcomm patches which include improvements to the msm_hsic_wakelock etc

I can't see a milestone yet and r28 is already upon us and people are still having troubles.

I don't care how long it takes so long as my mobile signal doesn't disappear again like on the test builds. ;)
[Nexus 4 Original Android Development] iGoogleNexus:
r28 is beast ... Love my phone even more

#Team MiNCO

**G1→N1→NS→GN→N⁴**
[Nexus 4 Original Android Development] ziddey:
"Flash this on a rom that doesn't have the corresponding rom-side commits and you will of course have problems too (and I will laugh at you)."

and you're polluting the wrong thread.
[Nexus 4 Original Android Development] CircuitBug:
Could you ateast tell me how to delete the addon.d script please?
[Nexus 4 Original Android Development] yethz:
File manager that has root capability,

Browse through /system/addon.d/

And delete............

_____________________________

Device: Google Nexus 4 (LG-E960)

ROM: AOKP JB-4.3.1-MR2-(JLS36I) Kecinzer (Oct-18-13)

Kernel: Franco Kernel #190v2-JWR-Prima (Linaro@LaboDJ)

Recovery: PhilZ Touch (CWM) Recovery v5.15.0
[Nexus 4 Original Android Development] sordna:
Aaaaahahahahhaahaha, hilarious!
[Nexus 4 Original Android Development] franciscofranco:
Pushed another Beta/Alpha FKU few minutes ago with bug fixes and Color profiles fully working. I think if I work really hard the app will be Beta status in about a week, maybe less. Last features to re-add is File Manager functionality, finish Kernel Settings and add PerApp Modes :) then after everything is there and working it will take a little while to polish and fix bugs - but I'm currently very happy about how things are progressing!
[Nexus 4 Original Android Development] happiboi:
Love having the color profiles back again :thumbup::thumbup: thanks Franco
[Nexus 4 Original Android Development] franciscofranco:
Did you try to delete one? Just like the gmail app, swipe to delete :)
[Nexus 4 Original Android Development] Bobtehblob:
Are you not allowed to promote your own paid apps in the developer section Franco?
[Nexus 4 Original Android Development] happiboi:
Just did. Lol swipe and it's gone. No confirmation req'd :thumbup::thumbup: Love the little "tutorial notes" the go with each section too. I'm guessing with the color profiles, once set it'll stick even after reboot like the old app right [MENTION=3292224]franciscofranco[/MENTION] ?
[Nexus 4 Original Android Development] Cantacid:
I think he meant for nexus 4! Ill be skipping n5 as well! But only thing i will be sad about is how n4 will take a backseat in the development industry!

Sent from my Nexus 4
[Nexus 4 Original Android Development] NYLimited:
I must agree with you. I only got the N4 recently when Google dropped the 16gb to $250 and am not ready for an update yet. Perhaps by the time I am ready the N5 price will be down to $250 also..

Yes, probably too many devs will switch entirely to the N5 as if the old device just became useless.. Oh well.

---

Any clod can have the facts, but having an opinion is an art.
[Nexus 4 Original Android Development] tma24:
Because I translated strings into the Slovak language and all pending approval for some time ( I am Necromander)

While it seems that my work was wasted.
[Nexus 4 Original Android Development] ssbnasa:
6hrs SoT is very very good. :D
[Nexus 4 Original Android Development] Goku80:
From what I can see Franco still supports older devices. Plus many more devs the same. Just cause a new phone will be out development will not stop. Just look at the galaxy nexus. If one dev goes many more show up. N4 is still a beast and with kitkat still many more will develop for it
[Nexus 4 Original Android Development] The Gingerbread Man:
Now you know how it felt for us on galaxy nexus. This year our support will be dropped so you get that to look forward to next year :thumbup:
[Nexus 4 Original Android Development] ki2luminati:
5 stars given and tanks for the app Franco ;)
[Nexus 4 Original Android Development] franciscofranco:
Nope, I can only ask for feedback. Dumbest shít ever if you ask me.

You need to tick the set on boot thingy this time!
[Nexus 4 Original Android Development] devadam1:
I have this weird problem with music players. Occurs with any of them (e.g. Google Music, Poweramp etc.)

When the screen is locked, the sound breaks up intermittently. As if the CPU cannot handle the required processing power.

Just started happening today. Never had it before.

Any ideas? Running the PA ROM. Thanks!
[Nexus 4 Original Android Development] Bill Gamble:
Try raising the Suspend Frequency.
[Nexus 4 Original Android Development] devadam1:
I don't see the Performance tab on the Settings page. Is it a ROM limitation? I used to have CM 10.2 and remember having this setting.
[Nexus 4 Original Android Development] RockBoyEmy:
I've got a problem with the fku app, I know franco that you don't want bug reports, but I think this is a big one. I've been flashing stock rom on my phone, then the recovery and then SuperSU, after that I installed all my apps, of course including your FKU. The problem is that for some reason, now I just can't go on the CPU Manager tab, because it immediatly freezes and pops up message that "Unfortunately Project pringles has stopped". So I just can't change the cpu frequencies now :\ What do you think is the problem?
[Nexus 4 Original Android Development] fozzie:
ROM version? Kernel version? f.Ku version?

Did you flash a ROM update and forget to re-flash the kernel?

Have you tried clearing the app data and rebooting?

Have you tried uninstalling the app, rebooting & re-installing?

Does the problem happen with the normal app?
[Nexus 4 Original Android Development] RockBoyEmy:
Damn now I realize that your app didn't ask for permission from superuser. Maybe that's why it's not working. How can I add it to the list of superSU apps? :/
[Nexus 4 Original Android Development] TestingCharts:
Check if you have root

Remove FKU from the SuperSU list

Clear FKU data

Open FKU
[Nexus 4 Original Android Development] jak3z:
I rather eat the kit kats to be honest :D
[Nexus 4 Original Android Development] cobyman7035:
how's battery know r191¿ I'm on r183 still

Via Google voice Δ |\|€×u$™ 7 FHD on Tapatalk²
[Nexus 4 Original Android Development] hotnikkelz:
Best battery life I've had on my phone. 191 is awesome. It's sorcery

Wifi on blast
[Nexus 4 Original Android Development] :
I'm pushing r191 to the limits, boost duration @ 2000000, touch boost and hispeed freq @ 1512. The phone is too fast, too smooth. But I'm still getting 4 hours SOT for about 11-14 hours of use with full wifi on all the time. Wow! Anyone, please try you'll be amazed.

Sent from my Nexus 4
[Nexus 4 Original Android Development] drawde40599:
Yes, is a custom rom add on , depending on what rom your on if it has that tab its unlocked when u unlock developer options
[Nexus 4 Original Android Development] fuffyk:
Which ROM are u using?
[Nexus 4 Original Android Development] otariq:
What governor are you using? Any changes to hot plug?
[Nexus 4 Original Android Development] hotnikkelz:
Cataclysm
[Nexus 4 Original Android Development] franciscofranco:
Obviously using interactive...
[Nexus 4 Original Android Development] azsl1326:
I am on the latest CM Nightly, 10/19, and no longer able to flash the color.zip along with Franco's Kernel - it just gets stuck at the Google logo. Flashing only Franco's kernel with the nightly causes the the colors to STILL be off. Is there another fix for this issue so that I can use Franco's Kernel?

Thanks, in advance.
[Nexus 4 Original Android Development] franciscofranco:
Yes ditch CM.
[Nexus 4 Original Android Development] Redneck Trash:
The fix would be for CM to quit breaking ****.
[Nexus 4 Original Android Development] JaMeVu:
İ tested double tap screen on for a day ...i can say its totaly useless deadlocks several times so it can be remove from kernel ..

Nexus 4 üzerinde Tapatalk ile gönderildi
[Nexus 4 Original Android Development] franciscofranco:
That's why I'm always saying not to use that feature and that's why its disabled by default.
[Nexus 4 Original Android Development] nexusmaniac:
Franco, do you use a completely stock JWR66Y ROM?
[Nexus 4 Original Android Development] franciscofranco:
Yes, it works, no motivation to change to something else for now. Coming 4.4 we'll see.
[Nexus 4 Original Android Development] wctom:
I found the same thing, though I replaced the lib file manually. I reverted to CM 10/18 + Franco 191, and will just stick with it until KitKat hits in a couple of weeks. At this late stage, I doubt that there is much incremental change in the CM nightlies.
[Nexus 4 Original Android Development] Tennic:
I'm on CM nightly 10/18, and "cm10_colorfix-signed" work perfectly ... You tried with the nightly of 10/18? Or with the nightly 10/18 worked, and with that of the 10/19 does not work anymore? :confused:

(I have not yet tried the CM 10/19)
[Nexus 4 Original Android Development] wctom:
That's what we are saying: the color fix does not work on 10/19, but did worked on earlier builds.
[Nexus 4 Original Android Development] Tennic:
Then work up to 10/18 and from 10/19 does not work anymore? :mad:

I hope it is find a solution soon : (
[Nexus 4 Original Android Development] ziddey:
Come on guys, why are you posting about CM nightlies in here?

You should have noticed that there were no kernel-side changes in the latest nightly.

If you then went to flash just CM and not Franco, you would have found that it doesn't boot either. Lest we forget, remember these are _nightlies_

edit: my derp. see sig for cm compatible kernel
[Nexus 4 Original Android Development] sordna:
It's a highly experimental but VERY PROMISING feature. I would not call it useless. I had it on for a few days, and loved the concept! Yes, it's buggy and needs work, but when Franco is done with it, it will be awesome ! For now I'm conserving my power button by using the Automaton app (which utilizes the proximity sensor).
[Nexus 4 Original Android Development] UgoBoss:
My color settings does not load on boot, I'm on the latest alpha (10/17) is that normal ?

Thank's by advance ! :)

EDIT : My fault ! All is good !
[Nexus 4 Original Android Development] dougiefresh36:
Franco, the color profile section is super clean when you choose a profile. Great work, keep it up!
[Nexus 4 Original Android Development] azsl1326:
Okay...What's your ROM of choice?
[Nexus 4 Original Android Development] The Gingerbread Man:
He's on stock (factory image)
[Nexus 4 Original Android Development] arlenwoot:
Wrong. 10/19 does boot if you don't replace liboverlay and use the kernel it comes with.

If you still want to use franco.Kernel stick with 10/18 for now.
[Nexus 4 Original Android Development] ziddey:
Ha, you're right. I hadn't used the old liboverlay.so for a while now since it results in a constant stream of errors whenever the screen is on (# cat /proc/kmsg). Instead of deleting my addon.d script for liboverlay.so, I stripped it of its execute permissions but didn't account for them being added back on a dirty flash.

Either way, for those who insist on CM or its derivatives, here are two _UNOFFICIAL_ (read: don't bug franco if it kills your cat) builds of Franco r191 with the two relevant commits cherry-picked: http://xdaforums.com/showthread.php?t=2487246

Still working fine with 1019 nightly.
[Nexus 4 Original Android Development] NYLimited:
I could not help but think of you when I saw this one... :D
[Nexus 4 Original Android Development] franciscofranco:
Thank you. I'm thinking of adding the swipe to delete feature to the backup & restore panel, its super clean and super effective.
[Nexus 4 Original Android Development] cobyman7035:
gonna install r191 now!

still can't install fauxsound app :( kernel not supported
[Nexus 4 Original Android Development] :
I'm using interactive. And the only changes are those that I specified earlier. Try it, it's very very fast. Try scrolling buggy apps like the new Quickoffice, the smoothness is very noticeable.
[Nexus 4 Original Android Development] restlesssoul:
I think that could be useful to add the "undo" option to the swipe gesture, just like we have in Gmail... It's pretty much common do that by mistake... Great work by the way!
[Nexus 4 Original Android Development] franciscofranco:
I dunno. Like how often would you completely swipe by mistake? Its not like this data is any important at all, but on the email if you accidentally delete a very important email you can be kind of screwed. I hate defensive programming and I try to avoid it as much as possible. The programmer not always needs to account for every possible error caused by the user. If programmers did that they wouldn't do anything else in their lives. That's what I learned when I took my first C classes in college. Although one cannot simply ignore protection against misuse of the program, but in my opinion it should have a balance - some cases are not really worth adding code protections.
[Nexus 4 Original Android Development] restlesssoul:
Haha! That's right, we can see this defensive programming taken to another level in Windows Vista with its UAC. Sure it can be annoying... And in the worst scenario, all we have to do is create a new profile...
[Nexus 4 Original Android Development] franciscofranco:
Defensive programming isn't exactly that. I'll give you a very simple example:

if (Build.ID.contains("JWR")) downloadJWR();

else if (Build.ID.contains("JSS") || Build.ID.contains("JLC") downloadJSS();

Thats simple defensive programming because I'm defending my program against user mis-usage because in practice everyone should be running the same type of roms. In this case its a bit critical because you know what happens when flashing the wrong Kernel version, but it really isn't my problem to be defending against every type of wrong usage, or better, unintended usage. What I wanted was a simple:

if (user.clicked.download.button) downloadKernel();

and all I got was a lousy double if and an extra function call. :)
[Nexus 4 Original Android Development] fajarlazuarding:
Just updated to the latest version of fku, i love that the color control coming back and also the "000000" thingy gone lol. How it works very clean, as usual very impressive franco :)

I have question here, on voltage control, i scrolled down till the bottom and when pressed +/- button, the screen automatically went to the upper of the screen, is it how it works ? Bcause i think it's a bit annoying to always scroll down when pressing +/- , just my opinion, sorry for my bad English.

Another suggestion, about +/- button, i think its better to place - button in left side rather right one, thanks :)
[Nexus 4 Original Android Development] cobyman7035:
thanks will try those tweaks, whats your max cpu speed? im at u/c to 1.2ghz and undervolted as well, still kinda heats up my phone on LTE usage tho
[Nexus 4 Original Android Development] Cantacid:
LTE generated heat has got nothing to do with your processing speed. It is generated by the radio, which is kind of messed up in N4. It can be coupled with CPU heat depending on what you are doing on LTE, and for that you can UV to a stable level. There is not much you can do to reduce the heat generated by the radio, i may be wrong on that though.
[Nexus 4 Original Android Development] David9519:
I had "random" :D
[Nexus 4 Original Android Development] PINki92:
My n4 sometimes restarts after doing unintense activity such as browsing the web. Is it kernel problem (uv?) or bad hardware? It rarely happens but come on its a nexus, thats why I bought it.
[Nexus 4 Original Android Development] jak3z:
Logs or move along.
[Nexus 4 Original Android Development] yochananmarqos:
You just reminded me of this:

http://i56.tinypic.com/2iu97on.jpg
[Nexus 4 Original Android Development] franciscofranco:
These guys are bastards... Alien bastards.
[Nexus 4 Original Android Development] fozzie:
Why don't you remove the UV and try to eliminate one of the possible causes...
[Nexus 4 Original Android Development] MinatoNamikaze:
how to enable sweeptowake features of franco kernel?? anyone?
[Nexus 4 Original Android Development] fozzie:
If you mean double tap to wake, just search. It's mentioned a few times in the last dozen or so pages.
[Nexus 4 Original Android Development] mara-:
I think I found a bug. Sorry if it is mentioned already. I am trying to use 'cores online on touch input' function. Choosing one core does not work. Two cores still go online according to System Tuner. Choosing 3 or 4 cores works properly. Using jwr build. Please confirm.
[Nexus 4 Original Android Development] :
I think it was mentioned previously that the cores to go online on touch is defaulted at minimum to 2 cores. Thus, you can't change it to one core. If my memory fails me, anyone please correct.

Sent from my Nexus 4
[Nexus 4 Original Android Development] mara-:
No offence, but I dont think you know the meaning of word default. And option of single core would not be offered if it is not supposed to work.

EDIT: My apology to xdarenzzio.
[Nexus 4 Original Android Development] fozzie:
As mentioned in the earlier post, it is 2 cores minimum when the screen is on.
[Nexus 4 Original Android Development] :
Care to explain why you think I don't know the word "default"? I want to know how to use such word. :)

Sent from my Nexus 4
[Nexus 4 Original Android Development] mara-:
Who is mentioning the screen on? When I don't touch my screen I see in System Tuner that two cores are working at 384Mhz. As soon as I touch display, both cores go to 1,13GHz, when only one should go.

Default is a value assigned automatically by developer, but in your post you are basically telling "it's default, can't go lower that that". Default does not mean that.
[Nexus 4 Original Android Development] fozzie:
Mod Edit: Completely unnecessary
[Nexus 4 Original Android Development] RootTheMachine:
The problem is, two cores are always online anyway when the screen is on. Therefore it wouldn't make sense to only online one core on touch when two are already running. What you are observing in system monitor is input boost, not the second core coming online (it's already on). Not really a bug, just an option that is nulled by the default behavior.
[Nexus 4 Original Android Development] mara-:
OK, I agree about online thing. Maybe I expressed myself wrong. When I touch the screen, both cores jump in frequency to 1,13GHz. Shouldn't just one core go to 1,13GHz and other stay at 384MHz?
[Nexus 4 Original Android Development] Mercado_Negro:
No, that's not how it works. Two cores go online on touch by default. It actually depends on the load, as far as I know.

Here's an explanation by Franco himself:

[EDIT] I was wrong about the load part.
[Nexus 4 Original Android Development] mara-:
Maybe it's like that then. Franco should probably then remove the option to choose one core.
[Nexus 4 Original Android Development] Mercado_Negro:
Please read my edit and the quote I added from Franco. I think you were replying when I added/edited my post.
[Nexus 4 Original Android Development] Tex99:
Purity + franco kernel r191

I m very happy for results and for performance on my phone. Once my keyboard was been all green but after a reboot all normal.

The only thing that i don t like so much is the sound from speaker, it s too strong.

For the rest is perfect !! Thank you franco :)

PS: i can t upload the other battery image, by the way 1day and 13hours with battery , airplain mode only during the first night for about 7 hours

Inviato dal mio Nexus 4 con Tapatalk
[Nexus 4 Original Android Development] mara-:
Yes, I was replying. Thanks for finding the quote. And it explains about cores staying always online, which I noticed it didn't happen on stock kernel, but I don't mind. And I see now the problem. This option controls how many cores go online, not the frequency jump of cores. Maybe Franco should make an exception when we select one core, so that only one jumps in frequency and other stays at 384Mhz until needed.
[Nexus 4 Original Android Development] Savant:
Does anyone have great Io settings they'll share for deadline ?
[Nexus 4 Original Android Development] Lebo-Wog:
Hello people, first a stupid question i know, but bare with me, i have no root and no recovery, so no way i can know, what is the default governor used ?

Second, with latest r191 version, on complete stock settings, Performance is great, especially with gaming, i have spent 3 hours today on Real racing 3 (not simultaneously) and not a single glitch....

Here are the numbers, all with 12 to 14 hours of moderate usage :

On 3g only, i get 3 to 3.25 hours of screen on time.

On mostly 3g and little wifi i get around 3.5 hours of screen on time.

On mostly wifi i get 4 hours of screen on time.

On Wifi only, and no gaming i get 5 to 5.5 hours of screen on time.

Kudos to Franco, these number are amazing...