yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] franciscofranco:
Nobody really knows what's in those drivers. It's a cluster**** of code I doubt even the QC engineers know much about them.

Anyway I'm not gonna merge that and risk possible derps that I cannot control. Those drivers are for their reference boards and might need new userspace firmware to work properly.
[ONE Original Android Development] omvir:
This is why I love your kernel and threads. You always have a straight up and to the point answer.
[ONE Original Android Development] Kerjifire:
Was there a new touch driver in the kernel? , my touch issues fixed after flashing this latest kernel.... I'm out at the moment can't check.

Edit nope they are still here.
[ONE Original Android Development] j3di:
Was a dodgy download :-/
[ONE Original Android Development] franciscofranco:
Nope.
[ONE Original Android Development] suaverc118:
Not sure if others have this issue with the new kernel, but my apps do open a bit slower. Typing is good and have no issues, but all apps have a slight delay. I was using r22 prior to this. I'll keep testing.

---------- Post added at 08:57 PM ---------- Previous post was at 08:52 PM ----------

Raised max freq to 1958 and same issues. Now if I opened the app earlier it opens quickly, if I open for the first time it takes nearly 2 seconds to open.
[ONE Original Android Development] franciscofranco:
Can't reproduce.
[ONE Original Android Development] akarol:
People on AK claim it reduces wifi wake locks significantly.
[ONE Original Android Development] pandasa123:
Then people here will complain of some bug we can't fix because it won't be diagnosable
[ONE Original Android Development] suaverc118:
I wish I knew a way to show you. Your previous versions had no issues. I haven't changed anything.
[ONE Original Android Development] franciscofranco:
Good for them :)

Try to decrease timer_rate to 20000. If you have FKU it's Governor Control -> timer_rate if you don't, the path is around somewhere.
[ONE Original Android Development] Technecium:
I second this suggestion. I noticed the way some apps respond to scrolling of long lists/websites seems to run out of juice and pause for a moment before continuing to scroll. This makes a tremendous difference.
[ONE Original Android Development] dbaler:
Random reboot on r23. Was just on Reddit is fun. Had USB otg plugged in. https://s3.amazonaws.com/pushbullet-uploads/ujv06B9kIyi-CG5YbllPvDPhR7IN1C0F1kPW7d2wTnK2/last_kmsg
[ONE Original Android Development] toyota86:
Hello [MENTION=3292224]franciscofranco[/MENTION],

You're super awesome. With your kernel, I could calibrate RGB values thru kcal. May I ask a dumb question, how does the kernel pickup a change to the kcal file? I mean, as soon as I do an echo > kcal, the screen reflects this change. Some kind of hardware interrupt?

Edit: Ok, i think it is exported as a sysfs ram-based storage. Ie. when i echo to kcal, i am actually writing to a memory area?
[ONE Original Android Development] Kerjifire:
I feel the touchscreen issue is hardware related. My touchscreen issue has been on and off... Like right now I tried a paint test and no random swipes in between or there is some dodgy code somewhere...

Edit:and it's back.

With my tests I have found that under heat, the phone exhibits ghost like swipe issues leading me to deduce that is due to faulty hardware. Under cooler temperatures there were no issues, but once I ran a game to get the heat up, the touchscreen issues came back.
[ONE Original Android Development] cyablo:
Same for r23, Device gets stuck with Black Screen after entering encryption Code.
[ONE Original Android Development] niffel:
After update to r23 two finger zoom is very buggy. The zoom just moves from left to right or is all over the place. Anyone has the same bug?
[ONE Original Android Development] albyXR:
guys, but The update of the kernel have no sense because the updated are worse then the previous.

Don't understand, if the aim is to make even much more progress with the kernel or only to experiment and have issue during the daily usage?

why are unstable the new release?
[ONE Original Android Development] shadeofgrey:
I haven't had any issues here. All updates have the possibility of side effects, but posts like these don't help solve anything. Try to say what problems you're having and how to reproduce it. [emoji6]
[ONE Original Android Development] wirelezzz:
Thanks Franco I installed 23 kernel on stock ROM and works like charm !

Touch screen and typing finally is smooth !
[ONE Original Android Development] franciscofranco:
You have some ugly ass problem there. It's the same as before, the Wi-Fi chip fails to suspend, then it goes crazy after a while and it crashes the device.

It's something like that yeah, when you input the values we refresh the panel.

It's been confirmed that the touchscreen get's crazy when the ambient temperature is high - yes it's an hardware issue.

No idea, I can't reproduce because I don't use encryption. Does it work with the stock CM11 nightly Kernel?

For the ****ing 1238927344th time, the touch firmware is the same as on CM, it's been the same since r15 or something. Go to their bug tracker and file a bug report.

What the **** are you talking about?
[ONE Original Android Development] albyXR:
Nice asnwer for a developer, you lost a lot of point in my opinion with these answer.

You dont need to warm you up like a ***** immediatly ;)

I was only asking why I read a lot of issue with the new releases, can I read feedback before flash something or not?? I think we are here for this reason, don't behave so aggressiv :cool:
[ONE Original Android Development] irony17:
Hi,

just bought FKU to thank you for your work !

I couldn't find an answer to this, so if someone could help me find the solution ?

=> impossible to change the values of the vibration (which I find too high)

the option in CM11s seems disabled and doesn't work anymore...
[ONE Original Android Development] shadeofgrey:
Dude, the developers are here to develop.. Without pay mind you. The community is here to report issues and help fix them. Do some reading first and you'll be fine. Demanding things will get you nowhere. There are plenty of choices if you choose not to flash Franco.
[ONE Original Android Development] cyablo:
Im on CM11S 33R, can i use the nightly CM11 Kernel on this Version?
[ONE Original Android Development] franciscofranco:
Uh? This is how I write, I was sincerely confused by your post.

I didn't see any issue with new releases.

The vibration code hasn't changed for months, so I dunno. But I'll be adding it to FKU for the next release ;)
[ONE Original Android Development] franciscofranco:
Nop, you cannot. Does it work with 100% stock firmware?
[ONE Original Android Development] Gamm86:
R23 working great on Vanir.

No issues, no lag, silk smooth!
[ONE Original Android Development] cyablo:
Do you mean fresh nightly or fresh CM11S install? Maybe I have got time to test with fresh & clean installs this evening. Never tried backuping and restoring an encrypted device with twrp, so i need do do a little manual backuping first, just for the case restore fails.
[ONE Original Android Development] albyXR:
What do you use for a manual backup? (which app..)
[ONE Original Android Development] cyablo:
Titanium Backup does a backup every night but i have to pull the backups off my device first. In case restore fails, they're useless inside the TWRP backup of a encrypted storage :)
[ONE Original Android Development] om22:
Finally I will be able to use fk again thank you! The struggle with the non working init.d scripts to change the vibration made me switch back to stock kernel till you add that :P Can't live with that weak vibration like it is on stock franco settings. Didn't want to install tasker for that.

How about defaulting it to stock value of 31 to avoid confusion when you've added the tunable so users can adjust it to their likings?
[ONE Original Android Development] franciscofranco:
31 is horrible, creates a huge vibration sound, can't live with it. But init.d works just fine! Did you try lately?
[ONE Original Android Development] om22:
Tried as of r20 and didn't work. I tried adding the command to the already existing userinit init.d file or creating a new one but it didn't work both ways.

I think I did a

echo 31 > /sys/class/timed_output/vibrator/vtg_level

It worked perfectly in terminal emulator but only with SU privileges
[ONE Original Android Development] BrianAllred:
The new releases aren't unstable. Maybe if you were more specific about your problems, we could help, but it's not Franco's kernel.
[ONE Original Android Development] Tzfardaya:
Have you tried basing your init script off vomer's tweaks? Just edit his config file to what you're wanting...
[ONE Original Android Development] om22:
But I don't want the bunch of other things in vomertweaks. Also trying it yourself is more fun :P
[ONE Original Android Development] Tzfardaya:
So edit out all the stuff you don't want from vomer tweaks... You've tried it yourself, it didn't work, so now try a solution known to work...

And you are aware that the kernel has no effect on init.d? Init.d is very much romspace
[ONE Original Android Development] zephiK:
Just take vomer tweaks and then remove all the echos with the exception of vibrator and there you go. You can make it set to 31 on every boot with that script.
[ONE Original Android Development] Tzfardaya:
/me thinks.oO( isn't that what I said... Twice?)
[ONE Original Android Development] om22:
I know that my error must be ROM dependant. Maybe I forgot a very minor thing I will take a look into vomer tweals and see if there is anything different from my script.
[ONE Original Android Development] franciscofranco:
Just do what they said, take vomer tweaks file, remove whatever entries you don't want and add your vibration line, save it, push to the device, profit.

But hey, I just added it to FKU beta, pushing it in a couple minutes to get feedback on the File Manager.
[ONE Original Android Development] zephiK:
I just quickly glanced at the post and didn't read all of them, sorry.
[ONE Original Android Development] Tzfardaya:
No worries... Franciscofranco has said that, you've said it, and I've said it twice.... Hopefully he will read at least one of them... :p

/me starts harassing Google play for the beta update
[ONE Original Android Development] Tzfardaya:
Still no beta update... :(
[ONE Original Android Development] franciscofranco:
I'm just done testing the vibration code, will push to the store in about 15m :)
[ONE Original Android Development] franciscofranco:
I think I found the bug. There was a change in the ramdisk that I didn't merge: https://github.com/CyanogenMod/andr...mmit/4124e2327cd7faf551f6160b3ebb85221fe5626c

I'll merge this and hopefully next release you should be fine. Sorry!
[ONE Original Android Development] cyablo:
No need to apologize, i'll wait for the next release, THX :)
[ONE Original Android Development] Tzfardaya:
Dude, take that apology... Do you know how rare it is that franciscofranco actually apologies?
[ONE Original Android Development] SleemLDJ:
Lol. I was about to say that. Screenshot it and print it out as a wallpaper for your living room.
[ONE Original Android Development] franciscofranco:
Eheh I apologise when I **** up :)
[ONE Original Android Development] Tzfardaya:
That's kinda our point... :p
[ONE Original Android Development] cyablo:
Yeah, but Franco and many others here are doing great work for free, this is often not honored and people are even disrespectful. So if he left something out, and it's in the next Release, i'll be fine, nothing to apologize about :)
[ONE Original Android Development] Tzfardaya:
Well, we never said he should or shouldn't have apologized... We are saying it's a rare event and you should accept it.. :P
[ONE Original Android Development] cyablo:
No Question, accepted from the bottom of my heart :)
[ONE Original Android Development] shaker2k:
Yeah. Even when he does, mods edit it out! He has a reputation to uphold..
[ONE Original Android Development] ghul21:
Uuu love it :)

Sent from my A0001
[ONE Original Android Development] Tzfardaya:
Ummmm ... Franciscofranco...

I think I broke it already...
[ONE Original Android Development] Tunasty:
I hate this!!! Can't find anything to complain about... Lol

Running r23 on Mahdi, and it's running smooth as hell. Thanks [MENTION=3292224]franciscofranco[/MENTION]

-Tunasty
[ONE Original Android Development] franciscofranco:
That's because it's fetching the server and it hasn't received any response back yet. I haven't got around to add some kind of indication of what's happening, but I will :)
[ONE Original Android Development] Tzfardaya:
That's what I thought, but it was still there after 5 minutes.... So I hit up your server in Chrome to make sure I could connect.... I could.... I think beta hung....

And you should check out the guy complaining that the beta is buggy in your n5 thread....
[ONE Original Android Development] omvir:
I noticed under-volt settings do not set after boot, on your beta release.
[ONE Original Android Development] franciscofranco:
Beta is buggy, no kiddin'. He wins the Sherlock award.

Not hung, but it only retries a couple times before giving up. It's more fine tuning than anything else, but yes, it needs it.
[ONE Original Android Development] franciscofranco:
Indeed, I haven't implemented that code properly yet. I still have a long list of tiny things that need attention but can't be arsed until all the features are up and running.
[ONE Original Android Development] Rene_ajax:
what are best settings for this kernel using the FKU app?? For best battery / performance
[ONE Original Android Development] zephiK:
There is no best settings. If you want a balance of the two, check out vomer tweaks and you can input them into fku.
[ONE Original Android Development] geowolf1000:
kernel expirience

The first time i installed fk was with r19

The batterry was beetter than stock and also touchscreen was smoother

Then update to r21 and the only problem was of charing

animation

After to r22 i had some drain battery but the same time chrome update and i notice that now new chrope has option to stay or wake device with all the problems you describe to above posts

So i fix with app ops i turn off option that chrome stay wake device

Results my device to r23 is great with huge batterry life no warm smoother than ever

I have stock R33 with twrp2.8.0.1 unofficial full xposed with hard modules like appsettings

I am hard tester an i am satisfied with kernel

Huge thank to the dev

And to his thread can speak as he like

If your are virgins change school!!!!
[ONE Original Android Development] Tzfardaya:
Defaults...
[ONE Original Android Development] gpelekanos1:
I find r23 a bit problematic with keyboard. Sometimes i press a letter and it wont respond. I am back on r22 and everything seems better. Just commenting if any other got this as well :)
[ONE Original Android Development] Rene_ajax:
ok thanks and how about fast charging? I read somewhere that you can enable that feature for charging the phone in a faster time.
[ONE Original Android Development] Tzfardaya:
Haven't seen it on the opo yet, someone correct me if I'm wrong.

But fast charge only works if the USB port you're plugging into supports non-standard currents.... Has no effect on ac charging.
[ONE Original Android Development] shuweee:
My apology if this has bee asked before. I'm on R22 right now and if I flash the r33 zip over the top, does it reset anything? I know it's not a wipe but was just wondering. Thanks

Sent via Oneplus One + CM11S + franco r22
[ONE Original Android Development] Tunasty:
What do you mean by reset? Like reset FKU settings? Reset your apps?

Either way, nothing will change. Sometimes FKU settings change which is a good thing that way you can configure your new settings for the new version

-Tunasty
[ONE Original Android Development] DerRomtester:
Placebo. None of these commits affect touchscreen sensitivity.
[ONE Original Android Development] Rene_ajax:
Ok currently phone is on charger and the FKU app says that it is charging with a speed of 13% per hour? I think thats too slow and not even possible on this device. Is this kernel related bug?
[ONE Original Android Development] Tzfardaya:
What charger?
[ONE Original Android Development] Rene_ajax:
just stock usb charger. charging via usb 2.0 connection on PC
[ONE Original Android Development] zephiK:
Your charging via USB. It charges slower via USB to the computer. Use the wall charger
[ONE Original Android Development] Tzfardaya:
So between 500 and 900 maH (USB spec)... To charge a 3100 maH battery... 3000/500=6 100/6=16.7.. Allow for conversion loss and operational needs, 13% per hour makes sense...
[ONE Original Android Development] Chikko:
I have too! And it is not placebo... Revert back to r22
[ONE Original Android Development] krxz:
I have 14.7% / h atm.

Gesendet von meinem A0001
[ONE Original Android Development] Tzfardaya:
USB 3 port? :p
[ONE Original Android Development] krxz:
3.5 xD

Gesendet von meinem A0001
[ONE Original Android Development] Rene_ajax:
omg, you guys are so smart! where do u get such information, I really dont know?
[ONE Original Android Development] Tzfardaya:
Research, study, paying attention in class...

Charge times for electronic devices depend on the output current of the charger... USB is 500-900maH, the Wall blister shipped with the opo is 1.8aH (1800maH)

Its good for the battery to be charged slower (lower maH) as this stressed the battery less while generating less heat...
[ONE Original Android Development] shuweee:
While user experiences may vary from people to people but I just flashed r33 and have not who experienced keyboard issues. Will continue to test though. [emoji1]

Sent via Oneplus One + CM11S + franco r22
[ONE Original Android Development] Tzfardaya:
I want r33 too... Share the link you downloaded it from... All I can find on Franco's server is r23... :(
[ONE Original Android Development] DerRomtester:
There is no r33. r23 is the latest version. I think he made a typo mistake.
[ONE Original Android Development] Tzfardaya:
But, but, but.....
[ONE Original Android Development] nikzDHD:
I thought r33 was a mystical version for the dreamers....

Anyway no issues to report with r23 no touch screen issues keyboard working as it should and nothing going crazy as reported.
[ONE Original Android Development] Tunasty:
I see what you did here :P

-Tunasty
[ONE Original Android Development] Ok_Kaleidoscope5109:
Hi Franco, the reason I suggest using 31 is not because its better than your setting but because there's vibration control in CM already meaning one can adjust using that interface without having to use the fk utilities or an init.d script. I personally feel that having a 0-100 slider in the ROM gives you far more precise control than 0-31.

---------- Post added at 04:24 PM ---------- Previous post was at 03:50 PM ----------

Also any ideas why my init.d script doesn't work? Permissions are set 755 as required

#!/system/bin/sh

echo 31 > /sys/devices/virtual/timed_output/vibrator/vtg_level

I would think that having done this for the N4, N5, that I should know how to do this properly. And last I checked CM11 does support init.d scripts....
[ONE Original Android Development] Manholas:
I've been watching you, you are a very funny boy. Dear me .... can any saint.
[ONE Original Android Development] alk770:
Is there a working version for mahdi rom 2.8?
[ONE Original Android Development] Tunasty:
Hmm a working version huh?

Define working.

As far as Mahdi rom, this is not the thread to ask for.

Secondly all roms have working versions lol?

-Tunasty
[ONE Original Android Development] ravearamashi:
You guys just gave those people at Jira headache :P
[ONE Original Android Development] franciscofranco:
Of course it updates the Kernel without a custom recovery...

I didnt say anywhere that r7 would magically work with non-stock firmware... I at this point I dont really care about anything other than stock.
[ONE Original Android Development] mike9055:
Hello Franco, i'm using your kernel on all my devices and it's great

I'd like to flash it on my OPO but i get a warning i'm using CM11, but as far as i know it should be 11S

It says CyanogenMod version 11.0-XNPH25R, phone came with an earlier version and i upgraded through settings

Thank you
[ONE Original Android Development] zephiK:
Ignore the warning and go with it. You are indeed using cm 11s
[ONE Original Android Development] mike9055:
do i need root or unlocked bootloader? my phone is still locked

i tried unlocking it 1st thing when i unpacked but couldn't get win 8.1 to recognize the phone as a fastboot device, think i nedd one of those tools to clear drivers, like the one in nexus 5/7 toolkits

---------- Post added at 10:13 AM ---------- Previous post was at 10:06 AM ----------

replying to myself, think i need a custom recovery... so i need to unlock
[ONE Original Android Development] franciscofranco:
Ignore the warning, I've disabled it before for this device, but somehow they changed something in the build.prop and now it thinks you're not an OPO anymore for that check. Don't worry I'll have that fixed in the next FKU update.

You don't need an unlocked bootloader. Just flash from the app.
[ONE Original Android Development] mike9055:
Thank you for the reply, i tried but it doesn't work, r7 downloads but device doesn't autoflash, doesn't reboot automatically

Given i have no custom recovery i guess the zip is not an option

I'm running on ART if it matters
[ONE Original Android Development] ChesterZZ:
Thanks for the update, but the phone still rebooted after 5 mins of playing...
[ONE Original Android Development] franciscofranco:
No errors detected

I can't reproduce, and the log is empty of crashes.
[ONE Original Android Development] franciscofranco:
You need root - sorry for the erroneous answer in my previous post, I was waking up. Not to self, don't post on XDA before having coffee.
[ONE Original Android Development] Dzhedaj:
And in order to root you need to have the unlocked bootloader, right?
[ONE Original Android Development] mike9055:
ok unlocked, rooted, flashed and it's working ok!

Strange thing (?) nothing was deleted after unlocking bootloader... i thought my phone was about to be wiped
[ONE Original Android Development] ChesterZZ:
Tried again and it doesn't seem to be rebooting anymore. Thanks. I'll keep testing though.
[ONE Original Android Development] Dzhedaj:
If you bought it off Aliexpress or Oppomart, they unlocked the bootloader when flashing the CM11S. Which is a good thing for us, means we don't have to wipe ;)
[ONE Original Android Development] :
[MENTION=3292224]franciscofranco[/MENTION] My OPO just shipped. Can't wait to flash FK on it :)
[ONE Original Android Development] joeg6217:
Everything has been good so far until yesterday when I was driving.

I was using Google Maps navigation and listening to Google Music via the car's bluetooth sound system.

Got 2-3 random reboots - not great when navigating and not sure where you are going :eek:.

Hopefully - r7 sorts out the reboots.
[ONE Original Android Development] franciscofranco:
Random reboots with r6?
[ONE Original Android Development] joeg6217:
Yes, r6.

---------- Post added at 03:03 PM ---------- Previous post was at 03:00 PM ----------

Not sure what the procedure is for identifying the cause of random reboots?
[ONE Original Android Development] Tzfardaya:
Submitting last_kmesg log via pastie/pastebin
[ONE Original Android Development] franciscofranco:
Flash r7.
[ONE Original Android Development] alk770:
Yes I tried it twice but neither cell service or wifi would work..
[ONE Original Android Development] Tunasty:
Post in Mahdi thread.

-Tunasty
[ONE Original Android Development] paychex:
Franco, been getting some random reboots. Here's the last_kmsg https://s3.amazonaws.com/pushbullet-uploads/ucsZ-wGBf3nyKEyLqHHKFOlzegig2SrZx2NSf/last_kmsg

I might get one every couple days in previous versions. Nothing I was gonna worry about. But on r23. I had about 5 between 6 and 8 am. Cleared Cache and Dalvik and haven't had one since. Probably anecdotal, don't know if there's anything to it.