yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] Ibsonic:
Is it me or is vibration harder now ?:cowboy:
[Nexus 4 Original Android Development] JNewms:
That's what she said. :)
[Nexus 4 Original Android Development] Ibsonic:
hahah, i can allmost use my phone.
[Nexus 4 Original Android Development] Testraindrop:
You need to post those screens in the battery whining threads in general section :D

That would be hilarious to see the reaction there :laugh:
[Nexus 4 Original Android Development] franciscofranco:
You nailed it ;)
[Nexus 4 Original Android Development] Locksmith81:
That's what he said
[Nexus 4 Original Android Development] jhericurls:
I uninstalled my Faux app today, sick of the lag and having to tweak a million options to get the balance of performance and battery life.

Rocking R15 again. It just works, straight out of the box. No need to touch anything, great battery life and no lag.

But I do miss the gamma settings :(
[Nexus 4 Original Android Development] franciscofranco:
Yeah my kernel just works out of the box :)

I dont wanna discredit faux, but I believe he didn't actually add a true GAMMA interface because I saw no code on his repo for that. I believe he played with the color temperature itself to emulate some type of GAMMA. I've been messing with the true GAMMA arrays in the kernel driver and I haven't been 100% successful. It works sometimes but its still not in user production mode. I may be wrong here and I'm sorry to faux if he actually manage to make a true GAMMA interface, but I think its just a trick to emulate GAMMA.

Until then I'll keep digging and try to finish what I started. Me and morfic exchanged a few ideas about this and I'm sure that we'll figure it out completely, either together or one of us.
[Nexus 4 Original Android Development] richteralan:
I think we should stop comparing this kernel dev with another kernel dev. They all do a great job optimizing their kernels.

Let's limit to franco kernel discussion here.
[Nexus 4 Original Android Development] rootuser11:
+1
[Nexus 4 Original Android Development] m0h1t:
Hey, I'm new to your kernel and I really like it. Also, I just bought the updater app to appreciate your hard work.

Where is this hotplug option? It's not in the list of governors. I'm running r15 only.

Also what are the recommended RGB values for the display. I saw someone posted 238/228/240 in the comment section in one of your apps and they look alright. And I know this is subjective and all, but what are you using?

Thanks again
[Nexus 4 Original Android Development] DutchDogg54:
While we're sharing what we think - I think you're silly to tell the OP and creator of the item this thread discusses what he can and can't talk about in his own thread...:confused:
[Nexus 4 Original Android Development] zephiK:
Franco is still working on hotplug and it'll be implemented in a app update soon, be patient.

Colors: https://docs.google.com/spreadsheet/ccc?key=0AoDp2qRui0u0dGE4T2gtSDBTRHVFSldPS2RrX1Rya0E#gid=0 (as linked previously)
[Nexus 4 Original Android Development] m0h1t:
Oh okay, I misunderstood and thought he had already implemented that. Thanks
[Nexus 4 Original Android Development] gee2012:
Just flashed r100 and i don`t see the adviced color setting option in color adjustments ,i only see the rgb scales in the franco kernel updater and not the extended settings.

-Edit- reflashed r97 and the extended gamma settings are back, r100 is also not listed as latest available kernel.
[Nexus 4 Original Android Development] franciscofranco:
I didn't change any color setting in r100.

Read the changelog, I beg you.
[Nexus 4 Original Android Development] schmitzekater:
AW: [KERNEL][GPL][N4] franco.Kernel - r100

Same here. I was using the recommended values before and I hope someone finds the settings for those.

The default values look like the ones from visceralpsyche some time ago. They are better with brightness set to 50%.

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] Koraboros:
I'm using the app that someone wrote about a month ago that switched between PA Halfbred colors and stock color... It doens't work any more, presumably because of the new options layout. Is there anyone who has an updated program to change it on the fly?

Thanks.
[Nexus 4 Original Android Development] kaiowas82:
Re: [KERNEL][GPL][N4] franco.Kernel - r100

Back to 97...i can't stand the Display not calibrated... :)
[Nexus 4 Original Android Development] Whosdaman:
Re: [KERNEL][GPL][N4] franco.Kernel - r100

Everyone who is complaining about the default color settings. Set the RGB to 180-185 for the meantime. It'll give you at least a decent looking display.
[Nexus 4 Original Android Development] franciscofranco:
But I didn't change anything in the default colors/gamma !!!
[Nexus 4 Original Android Development] ben_pyett:
Re: [KERNEL][GPL][N4] franco.Kernel - r100

Afraid that i may have to agree 100 is seriously dark and the preset gamma settings are no longer in application to change it. As you're aware missing fast charge option.
[Nexus 4 Original Android Development] Redneck Trash:
Re: [KERNEL][GPL][N4] franco.Kernel - r100

You should know better than to bring reality into the discussion.
[Nexus 4 Original Android Development] fizfaka:
can i use this kernel with aokp rom?
[Nexus 4 Original Android Development] schmitzekater:
AW: [KERNEL][GPL][N4] franco.Kernel - r100

Yeah, nobody doubts that I guess. But not everyone was running default values. :cool:

As soon as the value can be changed within the app the crowd will shut up. :D

Just relax, only 1st world kernel problems.

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] I2IEAILiiTY:
I think what's going on is since you added more options within the gamma controls, it's making the colors set previously go funky.

Just a thought. I haven't flashed r100 myself b/c I thought this was going to happen.
[Nexus 4 Original Android Development] Whosdaman:
Re: [KERNEL][GPL][N4] franco.Kernel - r100

I've always wanted to ask this, but is there any reason why Westwood is set as the tcp congestion avoidance algorithm? I only ask because from what I know, Vegas was the best. Just curious, thanks again!
[Nexus 4 Original Android Development] GIKE:
Re: [KERNEL][GPL][N4] franco.Kernel - r100

For those with colour calibration problems, un install franco app, reboot and install again.

Did the trick for me.
[Nexus 4 Original Android Development] alcurtis93:
Re: [KERNEL][GPL][N4] franco.Kernel - r100

Why is there no changelog for r100 and why is there no update to r100 in the app?
[Nexus 4 Original Android Development] albundy2010:
Re: [KERNEL][GPL][N4] franco.Kernel - r100

Y u no read franco's posts?
[Nexus 4 Original Android Development] cassius_20:
Re: [KERNEL][GPL][N4] franco.Kernel - r100

Come on man, read up a bit....
[Nexus 4 Original Android Development] trueblueram:
Re: [KERNEL][GPL][N4] franco.Kernel - r100

R100 is alien ware.
[Nexus 4 Original Android Development] blackdub370:
Re: [KERNEL][GPL][N4] franco.Kernel - r100

Wait to developer

They will be available from the app when I code the new gamma interface + sound boost interface + accuracy filter interface, which might happen today, tomorrow or the day after depending on my mood and predisposition to code.

The changes are:

* Reverted all Google patches for interactive and merge Codeaurora's code. This will get rid of the timer_rate bug in the previous interactive code and possibly maintain some better stability. Also made interactive back the default governor.

* Governors not sticking on boot - fixed

* Increased Conservative up_threshold to 95 and freq_step to 25 (using less freqs to scale to/from)

* Add Sound Control - for starters possibility to increase the headphones volume. The path is /sys/class/misc/soundcontrol/volume_boost. Maximum value is 20 to prevent big troubles on your ears. PAY ATTENTION: when changing this value you need to stop any media, change the value, wait 3-5 seconds, then resume your media. If you don't do this either the new volume won't apply or you will ear some microsecond long noise that will hurt your ears. You're on your own, read the **** up before complaining.

* Add improved Gamma Control code. So now instead of having whites, greys, blacks and mids for RGB arrays they are now separate. whites for red, green and blue, greys for red, green and blue... etc you get the picture. Same path as before /sys/class/misc/gammacontrol/ but new tunables. App will be updated later for this. For now you need to adjust your init.d scripts

Enviado desde mi Nexus 4 usando Tapatalk 2
[Nexus 4 Original Android Development] schmitzekater:
AW: [KERNEL][GPL][N4] franco.Kernel - r100

So I did some Tests.

Flashed r96 over r100 and colors were good again for me (recommended values). Set gamma to default in FKU and rebooted. Colors were washed out compared to recommended, but that seems to be default.

Flashed r100 again, and colors were the same as default in r96.

So I guess that if you were running custom gamma settings you get not the default values after flashing r100. Delete data in FKU before flashing r100 and you'll be fine.

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] billclay1988:
Is it by design that the max CPU frequency is locked at 1512? I'm using r100 with the latest CM 10.1, but I had the same problem with r96 and r97.
[Nexus 4 Original Android Development] franciscofranco:
Locked? I'm not following.
[Nexus 4 Original Android Development] Luigiesin:
Re: [KERNEL][GPL][N4] franco.Kernel - r100

I had no issues with colors... Flashed r100... Then just loaded one of my color presets and done...

Sent from my Rock & Roll Nexus 4 \m/

ROM: PA 3.0 (Feb25)

Kernel: Franco r100

T-Mobile
[Nexus 4 Original Android Development] alcurtis93:
Re: [KERNEL][GPL][N4] franco.Kernel - r100

You can't change it using the performance section of settings. Use the Franco kernel app

---------- Post added at 09:09 AM ---------- Previous post was at 09:08 AM ----------

The colors have definitely changed on r100
[Nexus 4 Original Android Development] franciscofranco:
Whatever. I already wrote that I did not change a single ****ing color/gamma parameter in r100. If they changed on your eyes is because you should have an app (probably mine) setting the values and it only sets up contrast, brightness and saturation successfully, the rest isn't there anymore so it won't apply.
[Nexus 4 Original Android Development] i860:
Default colors in r100 look fine for me, looking forward for fk update.

ps

This time no demands.
[Nexus 4 Original Android Development] billclay1988:
I mean that I can't set it any lower than 1512.
[Nexus 4 Original Android Development] alcurtis93:
Re: [KERNEL][GPL][N4] franco.Kernel - r100

You can't if your using the cm10.1 performance menu. Get the Franco kernel app
[Nexus 4 Original Android Development] tanjiajun_34:
Anyone managed to get the headphone boost working? I tried using Root Explorer to edit the file but it has no different :(( And it reverts to 0 after I reboot.
[Nexus 4 Original Android Development] billclay1988:
Ok, missed that. Thanks for the help.
[Nexus 4 Original Android Development] I2IEAILiiTY:
Re: [KERNEL][GPL][N4] franco.Kernel - r100

What I do to catch up on important posts, especially from an OP, is I click on that user's profile and view all their posts. And you can't say that you're using tapatalk as an excuse, because it works on here as well.

I always do this before I post, and sometimes I *gasp* do a search if I find my question to be fairly simple.

I'm not singling you out, as this could benefit more than a few handfuls of users I see posting here and in other threads.

I know the threads move fast, that's why I'm mentioning my technique for catching up. Like when I want to know what Franco's been up to, I click on his profile and view his posts. It makes things much easier.
[Nexus 4 Original Android Development] Koraboros:
Does anyone have an APK that changes the gamma values to a pre-set value like someone made before? It was a zip with 2 APKs, one to change to custom one and one to change to stock. With the updated interface I don't think those old APKs work anymore and it would be nice to get an update.
[Nexus 4 Original Android Development] benrees21:
Re: [KERNEL][GPL][N4] franco.Kernel - r100

Waiting patiently for the app update! Gotta try r100. People need to chill out and read through before asking questions that have already been answered.

Sent from my Nexus4™
[Nexus 4 Original Android Development] Haomuch:
Re: [KERNEL][GPL][N4] franco.Kernel - r100

No it's not because the color can't be changed in the app. I always used the recommended (not the mako default) color and gamma setting without doing any endless tuning. But the default color/gamma or display effect now is completely different now. I am now even doubting if it is because I didn't sleep well last night so my eyes are very tried.
[Nexus 4 Original Android Development] schmitzekater:
AW: [KERNEL][GPL][N4] franco.Kernel - r100

Clear data from FKU and reboot. The default values are a little but washed out, but better than recommended from r97 adapted to r100 default.

I'm missing the recommended values as well, but in a few days I bet they'll be back.

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] Haomuch:
Re: [KERNEL][GPL][N4] franco.Kernel - r100

The recommended in r97 is as good as previous builds. But the r100 default changed.
[Nexus 4 Original Android Development] derPianist:
AW: [KERNEL][GPL][N4] franco.Kernel - r100

Nooo! THEY DID

NOT

CHANGE !
[Nexus 4 Original Android Development] Haomuch:
Re: [KERNEL][GPL][N4] franco.Kernel - r100

So I believe it's my eyes' problem.
[Nexus 4 Original Android Development] franciscofranco:
Nop, clear the apps data, it will be back to normal.
[Nexus 4 Original Android Development] Haomuch:
Re: [KERNEL][GPL][N4] franco.Kernel - r100

Yes I did. And it returns to the washed out mako default. Anyway, just a little issue. And the headphone sound boost is awesome.
[Nexus 4 Original Android Development] franciscofranco:
Ah yes, it will return to my stock values ;) Great to know!
[Nexus 4 Original Android Development] gianton:
Re: [KERNEL][GPL][N4] franco.Kernel - r100

Amazing battery life! 2nd full discharge on r97 with CM10.1 Linaro. Stock settings only UV -150mV (faster binned chip). This is the best battery life since I got my N4

Will flash r100 now, thanks Franco.
[Nexus 4 Original Android Development] Haomuch:
Re: [KERNEL][GPL][N4] franco.Kernel - r100

What governor are you using? And what apps do you have or disable?
[Nexus 4 Original Android Development] Vangelis13:
Re: [KERNEL][GPL][N4] franco.Kernel - r100

I know what we need to get you for your next birthday Francisco; a soft pad like those mouse pads used to have for resting the palm. A bigger one of those so that it doesn't hurt every time you bang your head on your desk..

Pic: Francisco every 10 minutes after the release of a new kernel.
[Nexus 4 Original Android Development] gianton:
As I wrote I'm using stock settings only UV (stock governor for r97 was consrvative). I have 130 apps in total and have 25 apps greenified, I was using WiFi mostly for these values and have sync off most of the time.
[Nexus 4 Original Android Development] Dan53:
To anyone requesting an init.d file with new gamma interface + old colours. Here's a few. Will add more requested colour settings

To use:

1. Download

2. Remove .txt extension

3. Move file to system/etc/init.d/

4.Set permissions as rwxr-x-r-x

5. Reboot

6. Done

Settings that do not have the same value for all RGB (visceral) will now look slightly different

Read the post below http://xdaforums.com/showpost.php?p=38934661&postcount=18442) to find out how to make colours survive flashing a new rom
[Nexus 4 Original Android Development] jan.ringas:
If you put it into /data/local/userinit.d (you might need to create the folder userinit.d) it will survive flashing a new rom (at least when running Cyanogen Mod). Permissions will have to be the same as you told.

Edit: If your rom has a script in /system/etc/init.d containing these lines:

#!/system/bin/sh
# call userinit.sh and/or userinit.d/* scripts if present in /data/local

if [ -e /data/local/userinit.sh ];
then
log -p i -t userinit "Executing /data/local/userinit.sh";
logwrapper /system/bin/sh /data/local/userinit.sh;
setprop cm.userinit.active 1;
fi;

if [ -d /data/local/userinit.d ];
then
logwrapper busybox run-parts /data/local/userinit.d;
setprop cm.userinit.active 1;
fi;

you should be able to store scripts in /data/local/userinit.d and have them survive flashing of a rom.
[Nexus 4 Original Android Development] Dan53:
Thanks. I'm not sure if all ROMs have this system/etc/init.d file (I know PA does). But yeah nice idea, would be nice to confirm that
[Nexus 4 Original Android Development] Software Guru:
Thanks man

Works perfectly with Touch Control 1.5e
[Nexus 4 Original Android Development] johann2204:
Nice to hear. i try to Flash later.
[Nexus 4 Original Android Development] steviewevie:
Re: [KERNEL][GPL][N4] franco.Kernel - r100

Wow, I had forgotten how washed-out the default colours were. Looking forward to the app update and seeing what calibrated profiles the colour experts can come up with.

Sent from my Nexus 4
[Nexus 4 Original Android Development] jak3z:
Thats what I actually thought when the homescreen came up, who are you and what you have done to my colours!!!

Kernel feels amazing though.

BTW Franco you can poke on github in case you want translations for the new app before release. I will do asap.
[Nexus 4 Original Android Development] banny7000:
Re: [KERNEL][GPL][N4] franco.Kernel - r100

Do I delete the other file in init d
[Nexus 4 Original Android Development] Dan53:
Re: [KERNEL][GPL][N4] franco.Kernel - r100

Nope, not unless its other gamma settings. (If you haven't been in init.d before then no)
[Nexus 4 Original Android Development] PhoenixTank:
Appreciate the effort here, but the PA settings look awful now.

I was using this before, that some kind fellow converted for franco (cannot remember the name)

I see what you've done to convert old style to new and have no idea why it wouldn't work correctly.

It makes sense and should, right?

Booting up with that makes the nexus boot animation look terrible here.

Any ideas?
[Nexus 4 Original Android Development] johann2204:
is there any difference between boot-r100.img and franco.Kernel-nightly-r100.zip ? i know one is image the other zip. And i know how to flash them. I mean is the same code inside? for me its more easy to flash zip.
[Nexus 4 Original Android Development] tr1cky1:
It's the same
[Nexus 4 Original Android Development] johann2204:
Yes you can. See first post

franco: 2. This kernel works on Y or X rom?

A: This is one of the worse questions you can ask on my threads. This is a Nexus, it works on every rom you can possibly imagine.

---------- Post added at 02:24 PM ---------- Previous post was at 02:23 PM ----------

i wonder because the one is nightly. will flash now.
[Nexus 4 Original Android Development] steviewevie:
Re: [KERNEL][GPL][N4] franco.Kernel - r100

I appreciate your efforts, but sorry to ask whether it's possible to do a conversion like this at all? E.g. do we know for sure that the previous greys/mids etc were being applied to all the RGB colours and not just, say, one of them?

Not trying to say that what you've done is wrong, just wanting to check that it's definitely correct.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Hanny:
Google Play Music Volume Bomb

WARNING

BEWARE OF GOOGLE PLAY MUSIC

IF YOU USE EQUALIZERS​

This is NOT a kernel bug

This is a bug from Google Play Music app

So why do I post here? To protect your ears.

It is always there. Normally we don't encounter it (tell you why later)

But most probably we are going to experience it as we test out franco's volume_boost function

Because to use volume_boost function, we need to PAUSE -> SET -> PLAY

and this bug is exactly about pause and play.

Reproduction Procedures

1. Wear your headphone, keep a small distance between it and your ears to prevent ears damage.

2. Turn ON any kind of equalizer in Google Play Music. It is also confirmed for the equalizer in DSP Manager.

3. Play any song.

4. Use the back button to return to homescreen.

5. Pull down notification bar. Press the X that stops music + closes the notification. Do not plug out headphone.

[Normally, we do this when we finish listening to songs. Then we plug out our headphones. Plugging out and in resets something and the bug would be gone. Therefore we don't experience the bug in most normal usage. However, we do not plug our headphones off and in, while testing the volume_boost function.]

6. Open Google Play Music. Press the PLAY button at the bottom right corner.

7. Now there is a loud volume bomb in the headphone for 0.5 second. After that the song just plays normal.

That 0.5 second is enough to damage our ears, because the sudden burst of volume is terrible.

We probably will do the same procedure when we are pausing/playing frequently, while testing out the new function.

Workaround

1. Uninstall Google Play Music. Use an alternative. I have tested various other players (Player Pro, MusicXmatch, PowerAMP, Zplayer, n7player, Fusion player, Cubed) and there are no such volume burst issue.

If it is your song database and you cannot leave it:

2. Turn OFF the equalizers. I confirm the bug cannot be reproduced after the equalizer is OFF.

If you cannot live without the equalizers:

3. Press the PAUSE button in the notification bar before pressing X to close the notification.

Though, I cannot guarantee it if you leave the equalizers on. The bug may appear at anytime if you have them turned ON. So please combine with:

4. Before start playing the song, plug out/in the headphones for once. Something is reset and there will be no volume bomb.

This bug is always there. It is not related to the kernel or what kind of headphones you use. I did, but very rarely noticed this bug before. Because we never frequently pause play pause play pause play. But during testings we do, so no matter you are using Google Play Music or not, becareful of your ears when testing stuffs!

I cannot access any website about Google Play Music here in Hong Kong. If you find a way to report the bug, simply forward my post to them.

This bug, is also confirmed on kernels other than franco.

However it may be device specific for the Nexus 4. Because it does not happen on my Galaxy Nexus with 4.2.2.

Sorry for the technical OT but just my best regards to everybody here. ;)
[Nexus 4 Original Android Development] Dave778:
Thanks Franco for everything u do!

Anyone know why the gamma settings from R96 were removed?

I will stickstick w R96 for Obsanity's deep color settings & as well as me personally feeling that 96 was more responsive & less lag, even on conservative. I'll live w the small bugs lol.

I hope Obsanity's deep color settings find their way back to the newer releases :)

R96 was excellent on battery life too... At least on Rogers/Fido.
[Nexus 4 Original Android Development] rocklee80:
AW: [KERNEL][GPL][N4] franco.Kernel - r100

+1 have massive color banding on blacks and greys
[Nexus 4 Original Android Development] i860:
I will wait for franco to update fk. I will not try to fix any thing my self.
[Nexus 4 Original Android Development] TRSolebum:
AW: [KERNEL][GPL][N4] franco.Kernel - r100

The 3D-Effect in the Equalizer seems to be the problem. I tried to reproduce the described bug with my settings and it didn't work, the I put the 3D-Effect to the max and tried again *Boom*

So we should be fine using the equalizer as long as 3D-Effect is off ;)

Disclaimer: I tried it about 10 times, but no guarantee
[Nexus 4 Original Android Development] banny7000:
Re: [KERNEL][GPL][N4] franco.Kernel - r100

No I haven't been in initd before. I have a file called 90userinit should I leave it or felete