yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] TrenchKato:
Yup. I'm on r34 now and I rarely use Bluetooth so it's not an issue. I'm just happy to not have to reboot every 4 hours.
[Nexus 5 Original Android Development] GeekMcLeod:
Best battery life I've ever had. 5 and a half hours SOT and still 11% left. Mainly light gaming and some reading.

Posted from under your bed.
[Nexus 5 Original Android Development] Tzfardaya:
what patch?
[Nexus 5 Original Android Development] Pete182:
I don't know if this is kernel, display setting or room related but my screen has been randomly flickering with a bunch of mixed colours flaking for a split second.

Had anyone else been getting that?
[Nexus 5 Original Android Development] Tzfardaya:
which kernel version? r33? using a custom colour profile? not recycling the screen on then off?

or using auto-brightness on r34 in extremely low light?
[Nexus 5 Original Android Development] floepie:
OK, I can't seem to get this value in /sys/module/lm3660_bl/paratemers/backlight_dimmer changed from Y to N. I've added an init.d script (without extension) using Vomar's script as a template, applied the appropriate permissions, rebooted several times, and that value simply won't change to N (or 0). Shouldn't that value have changed following a reboot to confirm that the script is applied at boot? Thanks for any help.
[Nexus 5 Original Android Development] MrMagic:
Someone just posted this in the CarbonROM thread:

http://xdaforums.com/showpost.php?p=50953164&postcount=1257

(stating that apart from CM other ROMs such as AOKP, PAC and Slim are all switching to CAF)

Apparently CarbonROM has also switched to CAF in the latest nightlies.

This kinda sucks because I've always found Franco and Carbon a really great combination.

Don't want to start a CAF vs. non-CAF war, just a warning that your favorite ROM may not be compatible with Franco anymore.
[Nexus 5 Original Android Development] alanwyl:
Franco does the audio tunneling thing do anything new on this compared to say the nexus 4?
[Nexus 5 Original Android Development] JNewms:
I'm truly impressed at the speed that this kernel took over. Franco has only had the device a few days and it's already giving me insane performance AND battery. Franco just told physics to bugger off.
[Nexus 5 Original Android Development] bloot:
Nice work mate.
[Nexus 5 Original Android Development] Marck527:
Hey Franco, thank you for this kernel it fantastic! :)

Any chance of double tap to wake feature? I use it on my nexus 7 flo and it's very useful especially for nexus devices with no onscreen buttons. Also saves the actual power button. Many thanks.

Sent from my Nexus 5
[Nexus 5 Original Android Development] franciscofranco:
Not that I know off.

That currently not a priority, we'll see about the future.
[Nexus 5 Original Android Development] yoyoz808:
Yes i did that. Don't hear a change.
[Nexus 5 Original Android Development] dazz87:
Change from 0 to 8. There is a somewhat of a boost but im too scare to go any higher.
[Nexus 5 Original Android Development] Damian2013:
Any preset color fixes like the Nexus 4 yet? I like the dark colors preset from the Nexus 4.
[Nexus 5 Original Android Development] PhantomGamers:
Do I have to reflash if I don't use FKU to configure the kernel or was the fix only for changing settings?
[Nexus 5 Original Android Development] davidbar93:
Hi franco. Thank you for this kernel ,I'm a fan of your kernels and was using them on my Nexus 4 too.

Overally it's very smooth ,but gaming it's still not smooth as expected from his device ,and it was like that also with the stock kernel. Maybe you can give us the settings in Trickster to make the gameplay smooth as possible? Thank you a lot. [MENTION=3292224]franciscofranco[/MENTION]
[Nexus 5 Original Android Development] yellowdie:
Psh, yeah? Well, all of the cool kids are using Crespos. Don't see you rockin'

ALL

Nexi, now do we?! ;):p
[Nexus 5 Original Android Development] yoyoz808:
I think you're imagining things. There no change here.

Edit: I stand corrected. I only hear a gain with the play music app.
[Nexus 5 Original Android Development] PresidentMcCain:
Flashed r11 directly from r10 (with thermal-engine-hh renamed back).

It appears that flashing r11 auto-renamed thermal-engine-hh to thermal-engine-hh-bak, but did not solve the phone kernel crash issue. Here's my kmsg log:

http://pastebin.com/UggyXEP8

Now reboots in Antutu at 21% test.
[Nexus 5 Original Android Development] TinTin:
reboot

Reproducable reboot during Antutu test using r11

Governor: performance

CPU freq: 2265

Dalvik

rest unchanged.
[Nexus 5 Original Android Development] cc16177:
You deserve it dude.
[Nexus 5 Original Android Development] yoyoz808:
Okay so to me the speaker seems to gain in bass and not really volume. I get a lot of distortion when i go to 10 but the actual loudness of the volume doesn't change much.
[Nexus 5 Original Android Development] The Gingerbread Man:
If you were able to find the exact terminal commands needed for each kernel setting you would like to change you could create an init.d script to apply those changes without root as the kernel its self should support init.d unlike stock kernel which would require superuser permission to actually perform the commands you wanted to perform. You might find some help full stuff in francos github https://github.com/franciscofranco/hammerhead/commits/android-msm-hammerhead-3.4-kk-r1 which should allow you to find some of the directories required. It would take a little know how but that way you should get the best of both worlds. Unfortunately I don't have the knowledge to make it for you but I hope that helps you find your way ☺
[Nexus 5 Original Android Development] dazz87:
Same here thats why i didnt want to go higher than 8, i may blow the speaker
[Nexus 5 Original Android Development] zephiK:
Found a bug with per apps mode. If you created a mode and then go to delete tab then back to create or set. The tab for delete still shows, see
[Nexus 5 Original Android Development] franciscofranco:
Both logs say hw_reset:

No errors detected

Boot info:

Last boot reason: hw_reset

I'd say its Antutu that is doing something that it shouldn't.
[Nexus 5 Original Android Development] Tzfardaya:
okay, if you're using stock rom, you'll need a helper app to act as the init.d deamon (as stock android doesn't support it, even though the folder is still there)

this was the one I was playing with the other day while testing.

and if you cut/pasted that path from your script, I can see one problem already...

echo 0 > /sys/module/lm3630_bl/parameters/backlight_dimmer

Double check the spelling and spacing of your script. :P

script should read
[Nexus 5 Original Android Development] PetritH:
I'd reather Change rom than Kernel. Purity is great ROM, you should try out.
[Nexus 5 Original Android Development] nexusmaniac:
Which values 8,11,14? Thanks :)
[Nexus 5 Original Android Development] yorici:
Yes;) Normal order in the app as usual (Left to right is 1 to 5, second row left to right 6 to 10, 15-20, 21-23) Thx bud!
[Nexus 5 Original Android Development] justibasa:
I can confirm slim had not gone caf........ yet. Let's cross our fingers and hope it doesn't on the next nightly.
[Nexus 5 Original Android Development] floepie:
OK thanks. I'm using Cataclysm ROM, and according to its FAQ, init.D is a function of the kernel, so I'm making an educated guess by thinking that init.D support is present with Cataclysm + Franco? As for spelling, everything checks. I simply misspelled in my post, but I've triple checked my script. Still, that value doesn't change.
[Nexus 5 Original Android Development] Tzfardaya:
[MENTION=4809179]yorici[/MENTION], did I just get a bad download or is the background of your png crosshatched?
[Nexus 5 Original Android Development] yorici:
Have you tried opening it with QuickPic? I use QuickPic as the stock gallery app doesn't process it right...

If things are all right the pixels should blend to a half tone. When you zoom in, you shall see that the background is made up out of a grid.
[Nexus 5 Original Android Development] Tzfardaya:
heh, init.d need both kernel and rom support... so if they're saying it depends on the kernel, then the rom should support it...

however, you could grab that init.d app I linked and test for yourself (it has an option in it to test for rom/kernel init.d support... (and as for permissions, user should have read/write/exec, but group and other should only have read/execute.. )

does the value change if you run the echo command manually in a terminal emulator?
[Nexus 5 Original Android Development] aow1980:
In the slimkat thread kufi just addressed this rumor
[Nexus 5 Original Android Development] Tzfardaya:
heh, I was opening it with ristretto on my laptop before even moving it to the phone... :P

edit: still crosshatched on the phone in quickpic... :(

edit 2:nevermind... switching to landscape fixed it...
[Nexus 5 Original Android Development] floepie:
Yes, the value changes using just the terminal, but it doesn't persist of course following reboot.

Your helper app confirmed that init.D is not supported by the kernel. I suspect that it's rather the ROM itself (Cataclysm) that doesn't support init.D. But, that doesn't jive exactly with this popular ROM's FAQ. Or, is there switch that I need to enable with Franco's kernel to turn init.D support to "on"?
[Nexus 5 Original Android Development] FAdrums:
Just a quick update! :)

Tapatalked from my Franco Paranoid ARTified Hammerhead
[Nexus 5 Original Android Development] Tzfardaya:
no, no switch in franco... wonder why the rom dev's say that... just use that app to act as the inid.d daemon...

or, do you use tasker for anything if you do, just set a profile on boot to run that echo... if you don't use tasker, I wouldn't recommend buying it for only this purpose though..
[Nexus 5 Original Android Development] floepie:
Well, thanks for your help. I suspect that what was meant in that FAQ regarding kernel-dependent support is whether or not the kernel's author's update zip adds a module or other script to be inserted in /system (in the ROM itself) somewhere to turn on or enable init.D. Hope this helps the many Cataclysm ROM users here.
[Nexus 5 Original Android Development] KuChar_:
Init.d toggle requires Busybox installed. :) I checked it.

_____

Nexus 5 & SwiftKey_
[Nexus 5 Original Android Development] Tzfardaya:
[MENTION=4809179]yorici[/MENTION]

okay, got the test done, 8 clips out very quickly.. :P (unless I ran the test wrong...)

wp 8/11/14

20 112/82/210

40 255/135/155

60 255/175/115
[Nexus 5 Original Android Development] Shanks:
I think there is a way to use this kernel cm with caf patches, anyone know how?

Please no rude comments, keep those for yourself.
[Nexus 5 Original Android Development] yorici:
Thx bud! 8 appears to run out quicker on other devices. I did this test on 8 and got 197. But you are not the only one, I already got someone else who had that too.

The difference between wp60 and wp20 is for the values 6-18 around 90 for me. It is on yours too. I hope it's a constant and discrepancies are caused by measurement errors, but hitting limits doesn't make it easier.

Constants make the use of formulas more valid and indicate connections (not just a random mesh of numbers ;))
[Nexus 5 Original Android Development] Tzfardaya:
197 for wp 40?

I'll dive back in and check..

my numbers are within 5 of the exact (I think.. :P)

also, I was setting both the red pos and red neg to the same values
[Nexus 5 Original Android Development] yorici:
Nope wp60;) haven't hit a limit yet. Ye i got 90 to 94, but i didn't as precise as I should. But it time costly for 12 values and 2 white points..
[Nexus 5 Original Android Development] Tzfardaya:
what numbers did you get for the test?

for all 3 wp?

I want to see what they do on my device. :P
[Nexus 5 Original Android Development] Moh_Jay:
A little off topic but slim users will not have to worry about anything http://xdaforums.com/showthread.php?p=50957041
[Nexus 5 Original Android Development] dastinger:
I know this will only be another post stating the same but I tried r34 after reverting from r33 to r32.

Definitely, performance and, mainly, battery life are not the same comparing r32 to r33 or r34. The last two versions are amazing when it comes to that. Also, I didn't use r34 enough to know if I liked the new auto brightness values. I think I was getting used to it but I needed more time.. It's not an horrible thing for me like it seems to be for others tbh.

But, I had to revert again to r32. The redraws and some random disconnects from my Nokia Bluetooth headset in the middle of calls are killers, unfortunately. I really hope Google addresses this if the issue is on their side as well.. It's only the fact that none of this happens in r32 that makes me wonder. Oh well, let's just wait and see.

Please, don't take this badly. I'm just a bit disappointed that some issues are making it impossible for me to use the latest versions that are so much better regarding performance vs battery.

--EDIT--

Btw I think the solution to the auto brightness dilemma will be adding an option on FKU to disable it. Or, make 3 profiles for it. Back in the SGS days, Semaphore kernel dev stratosk implemented a different auto brightness on his kernel just like you did and, to please everyone's needs, he added 3 profiles. Dark, normal and bright. What do you think [MENTION=3292224]franciscofranco[/MENTION]?
[Nexus 5 Original Android Development] zllovesuki:
Kernel Panic - r34

Kernel Panic, last below. Stock with xposed, r34.

http://pastebin.com/vCdspB9G
[Nexus 5 Original Android Development] yorici:
Hope you can read it xD R means Register, RO is reversed order. Vs is verschil in Dutch meaning difference.

It has no use though. The values even differ per moment of the day, probably due to screen being warmed up.

The app is called note anytime (wonderful app)
[Nexus 5 Original Android Development] Tzfardaya:
heh, I was just looking for your numbers on 8/11/14 at the 3 wp.. :P

numbers are probably different due to variation in the ambient light... that can throw perceived gamma off on displays...
[Nexus 5 Original Android Development] yorici:
I first did value 11 for each white point, which turns out to behave linearly as well. Then I did it for 20 and 60 for most values, so no 40.

But the real starting points don't matter that much for structure and logic. They are bound to display characteristics. I still need to find a way to incorporate the register in my formulas I have now.

The formulas apply to the gamma images. I have 4 of them, but the bottom three are derived from the top one.

The terms perfect and max are a bit misleading. Max is actually difference between the colours used in the background. As you want to have 0;255 most of the time, you should maintain max at 255. Perfect should be called output value. It the RGB value of the rectangle in all the gamma images.

Edit: You are right about ambient light. That's a factor too. But you should also warm your display up for 30 minutes by leaving it on, or using your phone. (That's what I read from calibration guides)
[Nexus 5 Original Android Development] Nucleotide:
Is anyone able to tell me if Gingerbreadman colour profile in the Franco Kernel updater app are the same as the ones found in the Display Control app?

If they aren't the same, can anyone post the settings from the FKU app for Gingerbreadman profile - or point me in the direction where I might find them?

Would be greatly appreciated.

Thanks. :)
[Nexus 5 Original Android Development] Tzfardaya:
Vomer has a collection of all the colour profiles in a zip file in his signature.

or, it's here
[Nexus 5 Original Android Development] imablackhat:
Vomer3 Is niceeee
[Nexus 5 Original Android Development] Nucleotide:
Thanks a lot. I will try out both. :)
[Nexus 5 Original Android Development] Tzfardaya:
both? That link I gave has a zip of all the colour profiles for you to play with.. :P
[Nexus 5 Original Android Development] Nucleotide:
The_Gingerbread_Man_2.3_Gamma was the one I was after. Looks awesome. Thanks a lot. :)

---------- Post added at 01:22 PM ---------- Previous post was at 01:21 PM ----------

imablackhat mentioned vomer3 was nice. I was referring to both as in trying The_Gingerbread_Man_2.3_Gamma and vomer3 profiles. :)
[Nexus 5 Original Android Development] krolla03:
Ever since I flashed r34 hangouts keeps FCing
[Nexus 5 Original Android Development] occtec:
No problems here, on r34 using Mahdi ROM.
[Nexus 5 Original Android Development] towelboy:
After flashing r34 my autobrightness is really finicky, it changes often from low-high in a dark room

Sent from my Nexus 5
[Nexus 5 Original Android Development] blueren:
Cuz you're justin bieber. And your phone hates you

Sent from my Nexus 5
[Nexus 5 Original Android Development] Enddo:
i really enjoy the new brightness setting. please don't revert back
[Nexus 5 Original Android Development] inscythe:
Does your Bluetooth headset uses the latest Bluetooth 4.0 LE standard? My Pebble also suffers from the same disconnection issue. Perhaps you can also try to get the last_kmsg when the disconnection happens, we might find something in common in our logs and help [MENTION=3292224]franciscofranco[/MENTION] in solving the issue.

I am currently in r32 as well due to this Bluetooth issue.
[Nexus 5 Original Android Development] Nucleotide:
I would love to help you, but with a name like that, as well as the profile picture to boot, I'll leave you to search for the answer yourself.

Hint: this issue(?) has been mentioned heaps of time already. Perhaps searching the thread will reveal the answer. :good:
[Nexus 5 Original Android Development] m57:
Had the same thing happen to me on r34. It was taking a little bit longer to wake the screen too.

Around that time I noticed that "mm-qcamera-daemon" was keeping the device awake and it had lost over 25% battery in 2hours.

Have since flashed back to r33
[Nexus 5 Original Android Development] nirmalsudharjanan:
Same problem here..reflashed r34 test.
[Nexus 5 Original Android Development] lesp4ul:
are you sure that were kernel prob?

http://gadgets.ndtv.com/mobiles/new...acknowledged-by-google-fix-coming-soon-492667
[Nexus 5 Original Android Development] m57:
The flickering was a kernel problem maybe, but the "mm-qcamera-daemon" seems to be an android issue.
[Nexus 5 Original Android Development] tuncan:
I don't have enough time to read all those pages, but with R34 I have problems with brightness (like many others). Now I have to wait when I get phone call, because at first display is to dark to see. The same is after the phone call - I have to wait until brightness goes up to see stop button.
[Nexus 5 Original Android Development] Enddo:
the flickering is a hardware issue. your display just can't handle the low brightness. much like some chips can't handle undervolting like others can. it doesn't mean the display is defective. it just can't handle that low of a brightness. think of it like headphones/speakers that bottom out when you crank the volume too loudly. just down bring the brightness that low
[Nexus 5 Original Android Development] Nucleotide:
That's what the search functionality is for - so you don't have to read pages and pages or unnecessary crap.

I'll do the hard (easy) work for you this time. :good:

Open up a terminal emulator and type in su to gain root.

Then type in echo 0 > /sys/module/lm3630_bl/parameters/backlight_dimmer

Fixed. :good:
[Nexus 5 Original Android Development] tuncan:
Thank you, I saw this.

I just want to confirm this problem ...
[Nexus 5 Original Android Development] Technecium:
:banghead:

koeASOP 4.4.2 w/ Franco kernel + F2FS
[Nexus 5 Original Android Development] omvir:
I wonder what's changed in latest fku beta
[Nexus 5 Original Android Development] thloe:
Hello franco,

at first thanks for your great work!!! hope this has been ask not yet been; i´ve seached some pages but found nothing:

i´ve had r34 beta for about two weeks and with this kernel i had no connection to BT-Car Speaker. Do you know about this and is this problem solved?
[Nexus 5 Original Android Development] dannyella:
Backlight dimmer is too low to see anything. How to increase this??
[Nexus 5 Original Android Development] dastinger:
I'm not sure. Will have to check later. I think the headset is an old model but, as soon as I'm able to do it, I'll check. Also, I'm back on r32 but I may try flashing r34 in order to provide some logs if that helps.
[Nexus 5 Original Android Development] Nucleotide:
Are you for real?????

Go back just one page. :rolleyes:
[Nexus 5 Original Android Development] momomok:
same question

too bad Google doesn't allow dev to mark What's New for Beta version in Play Store page
[Nexus 5 Original Android Development] fbf2201:
I don't think that all these Bluetooth disconnections are only related to Bluetooth LE. The low energy protocol stack was introduced with Bluetooth specification 4.0 in 12/2009.

My car is from 12/2005 and I also have such disconnections together with Kernel r33 and r34.
[Nexus 5 Original Android Development] djmcnz:
I hate to have to say but auto brightness control is terrible with r34. Yes I've read the previous pages but this is a serious regression. On the same hardware there shouldn't be such an obvious decrease in usability.

My auto brightness now seems to be both slow and have massive steps. Credit for the kernel work but r34 performs poorly in this regard and I hope a quick update to r35 recovers lost capability.

Also the XDA support links in FK Updater don't work at all.
[Nexus 5 Original Android Development] @wells:
I am usually on the other kernel or cm, but installed to see what's the fuss about auto brightness and I see no problem, works pretty good..

only issue I have is when I set brightness manually to lowest level (settings -> brightness) left side of screen is darker than right side of screen. is it know issue or just me?

thanks!
[Nexus 5 Original Android Development] djmcnz:
Until you've used it for a while, and compared it to previous releases, you opinion is unfortunately of no value. A single data point can't be extrapolated to a trend and all that.
[Nexus 5 Original Android Development] @wells:
my post was not directed to you directly.. and I have no need for my opinion to be valued as you stated correctly. peace!
[Nexus 5 Original Android Development] Enddo:
there's nothing wrong with the new brightness feature. move along
[Nexus 5 Original Android Development] djmcnz:
You are incorrect so try not to be so righteous.

I politely pointed out an *obvious* regression, something I infrequently do but nevertheless based on many years of experience.

There is no explanation for the significant regression in auto brightness behaviour and this needs to be addressed.

Expressing your opinion is fine but in the face of obvious evidence it's not necessarily correct.

Rational, logical feedback to all developers, myself included, is critical and necessary for ongoing enhancement. Don't try and quash it because you don't agree with it.
[Nexus 5 Original Android Development] Nucleotide:
There is nothing wrong hey? That's why every second person is reporting issues with it I suppose.

Whether by design or not, it is way to harsh. In a dark room, I can barely see my screen.

Agree! ^^ :good:
[Nexus 5 Original Android Development] Enddo:
did you just see how you talked to someone else expressing their opinion? pot meet kettle

guess what, millions of people have differing opinions than you. get used to it. they're all valid
[Nexus 5 Original Android Development] djmcnz:
I was honest and polite, I trust you recognised that. Valid != Correct, I'm sure you understand.

You're lucky, you're happy. Many aren't, accept that and move on because the feedback was not intended for you and your opinion, valid or not, accurate or not, does not matter.
[Nexus 5 Original Android Development] @wells:
well this then should be a solution, right?

echo 0 > /sys/module/lm3630_bl/parameters/backlight_dimmer

:)