yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] Ok_Kaleidoscope5109:
Don't get why these noobs always have WiFi issues. What apps do you install? How many Xposed modules do you run? I'm running 8 and I have NEVER had an issue with Franco kernels that was not a known bug. If you've installed a lot of junk apps its time for a factory reset before you blame it all on Franco
[ONE Original Android Development] musashiken:
Are you running a theme? There's a bug that causes WiFi settings to FC if you use a theme. Many themes are facing this problem and it is solved in the latest CM nightlies but not on CM11S. For us on CM11S and wanting to try out some themes, we have to wait for the next OTA from CM to include this bug fix.
[ONE Original Android Development] chr0m:
Since r13 my touchscreen has been much better apart from a few minutes where it felt really unresponsive. It was great before and after
[ONE Original Android Development] ilea94:
Not for 100 % sure, but i think disabling double tap to wake solves the problem.
[ONE Original Android Development] sash89:
Guys are u trying this on 11s or nightlies?
[ONE Original Android Development] kecinzer:
That wery weird. I didn't have any those touchscreen issues on every version I tried. I'm on AOSP.
[ONE Original Android Development] albyXR:
hi everyone,

is there someone that already install the r13 on the latest madhi Rom?

I am tentative to install this kernel but I would like to have some feedback before.

how does this r13 on AOSP works? stable? batterylife under daily stress usage?
[ONE Original Android Development] ilea94:
Stock 11S.

With disabled double tap to wake i don´t have that issue for now.
[ONE Original Android Development] SleemLDJ:
Running AOSP edition CM11 nightly.

Does the TCP congestion algorithm look right?
[ONE Original Android Development] nneves:
I'm using with CM-M9 and it's great, battery life is 0,2%/h and it's very stable.
[ONE Original Android Development] albyXR:
Cm11 is Cm11, madhi is AOSP, or i am wrong?

anyway thats super: 0-2% a hour? unbelieveable! think in 2 or 3 days I will flash this kernel instead of madhi kernel: fro the moment I have 1 positive feedback thanks a lot :D
[ONE Original Android Development] bradm23:
Where is the double two to wake feature in 11s??
[ONE Original Android Development] cyablo:
Madhi also is based on CM: http://xdaforums.com/showpost.php?p=54083308&postcount=6
[ONE Original Android Development] venky716:
Only for CM11S use CM11 Kernel.

Everything else including MAHDI, CM11 use AOSP kernel.
[ONE Original Android Development] franciscofranco:
Nope, that is wrong. Weird bug on my end for sure. Thanks for reporting.
[ONE Original Android Development] fiz:ik:
Everybody complaining about ghost gestures - I'm on CM11S with r12 and now with r13 and I don't have any touchscreen issues, weird
[ONE Original Android Development] Alaris:
Quick noob question can I backup stock kernel with the paid version to the Franco kernel app?
[ONE Original Android Development] shaker2k:
Yup
[ONE Original Android Development] Alaris:
OK has anyone tried restoring a kernel using the app? My phone restarts then hangs at the cynagen mod screen and I can't figure out why.
[ONE Original Android Development] Bajo76:
Same here. Got mine on saturday.
[ONE Original Android Development] shaker2k:
Need more info. Are you stock cm11s, or nightly? Are you sure your flashing the right kernel?
[ONE Original Android Development] ilea94:
Ok I was wrong... Sadly

After some time problems still occur. Best example is SwiftKey which recognizes swipes even when I'm just typing.
[ONE Original Android Development] Alaris:
So I am on stock cm11s and what happens is say I flash Franco kernel. That flashes with no problem but when I try to go back to my stock kernel backup it hangs at the cm boot screen. One thing I was wonder is should I uncheck update cm recover in the developer settings?
[ONE Original Android Development] SleemLDJ:
Same here with SwiftKey. Other than that, all is well.
[ONE Original Android Development] shaker2k:
Have you tried using flashify to flash it? Also a good idea is to nandroid before flashing anything to avoid these problems.
[ONE Original Android Development] Alaris:
Yeah I guess I should install a custom recovery. Kinda wanted to keep it as is so I can install updates as the come out.
[ONE Original Android Development] zephiK:
TWRP can flash OTA updates, just make sure you untick Update CM Recovery in Developer Options.

I've read this in previous pages (way back) and another user had this problem, I don't think FKU Backup/Restore is working properly, I think backup works but when you restore the kernel, the phone would get stuck just like yours.

Try this, use Flashify and try flashing your "backed" up image file from FKU. If it boots, then restore is not working.
[ONE Original Android Development] franciscofranco:
Just tried and it works fine here. I dunno what you're doing to be honest. Maybe you backed up 25R stock Kernel...
[ONE Original Android Development] damastax68:
I flashed Franco r13 and still notice touch screen issues. Did this fix the typing issue where it misses key presses for anyone else?
[ONE Original Android Development] hellfire666:
Disabling tap to wake fixed the SOD issues and intermittent touch not working issues. desent fix the ghost touches sadly

Ive been testing for sometime now seems to be fine..

I enabled the capacitive buttons to see if that will cause issues like it did with 30O update+ hotfix

will update if i run in to any problems

CM11S - XNPH30o + hotfix

franco.Kernel - r13
[ONE Original Android Development] Alaris:
No I backup using the newest version. That's so weird I can't figure this out, I run into the same problem with flashify also.
[ONE Original Android Development] franciscofranco:
Are you sure you're backing up the latest 30O Kernel? I don't know then, sorry.
[ONE Original Android Development] Alaris:
Yeah I'm sure. Its the weirdest thing, I can flash new kernels but when I restore both in FKU and Flashify it hangs on reboot.
[ONE Original Android Development] FuzeLearner:
I had the same problem this morning. Went to restore the backup I made of stock 30O and it hung on reboot. It is weird.
[ONE Original Android Development] Alaris:
Did you find out why or fix it?
[ONE Original Android Development] FuzeLearner:
I got into TWRP with the power and volume down combo, connected it to my computer (when home during lunch....) adb pushed the r13.zip to my sdcard. Flashed it and I'm back up and running much to my relief.
[ONE Original Android Development] Alaris:
Yeah I can restore kernels and flash things fine through twrp. But it seems if I do any type of restores with flashify or fku I get hanging on reboots and need to use twrp.
[ONE Original Android Development] lilnev:
mine also hangs. i'm on 25r stock rooted. when i double tab it wakes up to the "one+ powered by android" boot screen. it hangs on using auto flash option in franco kernel updater app or through twrp. to fix it i flash 25r again and supersu.
[ONE Original Android Development] MICa.fighter:
Try restoring the kernel backup with fastboot.
[ONE Original Android Development] Alaris:
I've been using the restore option in twrp to just restore boot from a backup. This is the only thing that works for me and fastboot. I just very weird, almost as if the apps aren't making good backups.
[ONE Original Android Development] MICa.fighter:
Maybe, thats why you should try to restore the backup you made with those apps.
[ONE Original Android Development] paychex:
it's a probably with an individual hardware component maker's software. I believe they have said they are waiting for an update to the touchscreen software
[ONE Original Android Development] dayanandgp:
Hi Franco, At the risk of irritating you, I have installed r13 but still see a drain of 16% of battery loss in flight mode due to " Phone Idle " activity.

Should i still wait for CM11S incremental OTA or is something wrong with my wakelocks and should dig deep into wakelock consumption (did once but will dig deeper based on your answer)?

Love your kernel but couldnt get a confirmed answer for the above question when i asked it few pages back :(

forgive the noob question ,if it indeed is ;)
[ONE Original Android Development] Ok_Kaleidoscope5109:
Is [MENTION=3292224]franciscofranco[/MENTION] considering putting init.superuser.rc in the ramdisk so we can use built in SU? It's a leaner option than a 3rd party app having to run at startup IMO.

Also, is the lack of init.superuser.rc also why I cannot use init.d scripts?
[ONE Original Android Development] omino323:
So I was told that to get the feature of call recording built into my phone such as I had it with my GS4 that it is something that is built into the kernel...is this right??...if so is there anyway you could incorporate this into a future build? I dont think Im alone in wanting this feature built in instead of using some app that dosent work half the time. Sorry if this ends up not having to do with the kernel but I thought Id ask in hopes...:fingers-crossed:
[ONE Original Android Development] hellfire666:
Well looks like enabling the capacituve buttons still bring up the touch screen issues

With

Double tap to wake - disabled

Capacitive buttons - disabled (they are useless during the day time anyway)

No touch issues for the past few hours...smooth sailing over here
[ONE Original Android Development] chr0m:
I can confirm that restoring a backed up stock kernel through the paid app hangs on boot. It happened to be the first time I tried it a few weeks ago when I didn't have an unlocked bootloader. I'm an android noob and unlocked the bootloader not knowing it wiped my phone. Had to do this before fastboot would let me flash the kernel. I haven't been game to try the app again since. I only use fastboot or twrp for flashing now. Which is probably for the best. Also the RGB settings don't get saved by the app and persist on a reboot.
[ONE Original Android Development] LiquidSolstice:
This is currently a native feature of CM11 but can't be enabled easily because they are concerned about country restrictions and laws. It's not legal for you to record a conversation in many countries, and in the US, the laws vary from state-to-state.

http://review.cyanogenmod.org/#/c/70497/
[ONE Original Android Development] bigdog_nick:
I can confirm this. Paid app, restoring from Franco to stock, never boots into TWRP (latest), hangs at the splash screen. Had to fastboot flash the boot img.
[ONE Original Android Development] insestito:
What is the best cpu governor generally?
[ONE Original Android Development] hughfollett:
Interactive is optimized to death by Franco for his kernel
[ONE Original Android Development] omino323:
Why was is so easy to get on almost every custom rom for my Galaxy S4? Is there a zip anywhere I could flash to get this feature??
[ONE Original Android Development] LiquidSolstice:
Didn't say it was hard, just saying that call recording also has a lot to do with CM, and if CM is concerned about the legality of it, you're not going to be able to just "flash a zip" and make it happen.

Simply put, I don't think it's something Franco will do.
[ONE Original Android Development] 7ewis:
Is the vibration still set to lower the default?

It definitely feels weaker to me, I think I prefer it at the default strength. Is there a way I can change I back, there isn't a vibration amp option like there is on the Nexus 5?

Where can I change it, and what is default?

Brilliant job with the kernel Franco. I really don't know why Google hasn't hired you yet!
[ONE Original Android Development] cchant:
Just had a sleep of death on CM11s all stock settings

http://pastebin.com/eThiG03C
[ONE Original Android Development] Ixtilion:
Hello, I'm sorry to bother you but im running the latest CM11S nightly and decided to try and flash franco kernel r12 and r13, but Im stuck at the boot image even though the computer detects the phone.

I wiped dalvik cache after flashing the kernel just in case, is there anything that im missing?
[ONE Original Android Development] zephiK:
Wiping dalvik cache does nothing to a kernel. CM11S nightlies do not exist. You're either on CM11S or CM11 nightlies.

You most likely flashed the wrong kernel, if you're on CM11S, you must be on XNPH30O to flash r12-r13, otherwise use r11 or update your stock ROM to XNPH30O to use r12-r13.

If you're on CM11 nightlies, use AOSP.

Shhh, if Google hires him then we lose him :p
[ONE Original Android Development] franciscofranco:
As far as I know there is a bug in the modem firmware which can cause that. Looks like some sort of race condition.

Yeah I'll work on that soon.

I don't know anything about that, I'm not gonna help anyone asking for call recording, I think it's disgusting and I would be very pissed if anyone recorded calls with me. You're on your own.

Interactive.

It's lower than the default yes. I've put the path somewhere in this thread, I don't remember from the top of my head. I'll add it to FKU sometime too.

I've had an interview with Google, passed it, but then didn't want to go through any longer, not my thing, hate work in big companies.
[ONE Original Android Development] hughfollett:
You man are a mad scientist. You were about to work at Google and you refused..! That would be a dream work!
[ONE Original Android Development] shaker2k:
Have you seen how many times Franco's paid apps have been downloaded? If he worked for Google it might be a pay cut lol.
[ONE Original Android Development] zephiK:
sys/devices/virtual/timed_output/vibrator/vtg_level

min: 12

max: 31

(just a heads up for those changing it manually, values dont stick after reboot)
[ONE Original Android Development] nintendolinky:
Have we got optimised settings for this kernel yet, awesome by the way.
[ONE Original Android Development] chr0m:
Anyone experienced the phone turning itself off? This morning I pulled my phone out of my pocket and it was off. Now I'm not suggesting it has anything to do with this kernel, it just so happens I was using it both times it happened :) It's only happened twice in the 4 weeks I've had the phone. I wanted to see if logcat showed anything, but it only showed me logs from since I powered it back on.
[ONE Original Android Development] jcpq:
Someone has already tested in the liquidsmooth rom?
[ONE Original Android Development] zephiK:
Most optimized settings are default. If you're curious you can try the 0 hotplug config that has been popular on other devices using Franco Kernel. Check http://xdaforums.com/showpost.php?p=54291066&postcount=396
[ONE Original Android Development] jarjar124:
What I've been running for the past week is change bootpulse duration to 0 and increase go high-speed load to 95. Works wonders for me
[ONE Original Android Development] rlex:
r13 on 30O killed vibration in my 1+1, now it only works in recovery and on boot. Looks like now i'm forced to reflash whole phone. Dammit.
[ONE Original Android Development] franciscofranco:
Coincidence.
[ONE Original Android Development] evil_pro:
Dear [MENTION=3292224]franciscofranco[/MENTION]

Does your Kernel support Kexec Hardboot? It is needed for MultiROM.

If you haven't already, could you please merge this from the MutliROM for OnePlus One dev? It's just three lines that were changed.

https://github.com/KINGbabasula/and...mmit/96be9ef51bedaed3f5dfeaecfa3584d2f9fa10b9

Thanks in advance!
[ONE Original Android Development] zephiK:
http://xdaforums.com/oneplus-one/or...-kernel-r1-t2800871/post54909156#post54909156
[ONE Original Android Development] evil_pro:
Awesome. Thanks guys! :)
[ONE Original Android Development] Shadow Samurai:
I'm having a problem of mulitouch not working right. Is this a cm11s issue or something with the new firmware.

Edit: reflashed the kernel and it's gone. Had the same problem before on my amaze, don't know what caused it, I'll see if it returns.

Sent from the one and only Oneplus One
[ONE Original Android Development] sharp2G:
My phone seems to stutter a little with this config (using Dalvik and -75 under volt). Could I raise the maximum CPU and GPU to achieve better performance and leave the rest of the settlings alone in the 0 hot plug config?
[ONE Original Android Development] nicholaschum:
Google Bacon55.
[ONE Original Android Development] Shadow Samurai:
Yeah I did. Tested it out with a multi touch tester. It registered one touch and then the others were jerking all over the place. Again reflash fixed the issue. Had to see I'm not the only one with the strange issue

Sent from the one and only Oneplus One
[ONE Original Android Development] zephiK:
Tweak around the settings with what you just said, maximium CPU/GPU. Leave everything else the same, you can tweak around the highspeed_freq and sync_freq as well by boosting them up. Or you can just boost it up by using Per-App-Modes on apps/games that need higher CPU/GPU. But yeah for me, 1.2GHz was fine for me and I had a PAM that boosted it to 1.5GHz if needed.

1.5 GHz and 389 MHz should be a sweet spot. Although 330 does its job for me too.
[ONE Original Android Development] Tzfardaya:
Dude, it's your phone, play with the settings all you want, just reset back to defaults if you encounter issues...
[ONE Original Android Development] N.Tesla:
Thank you so much for the info. I'll try to read more. :good:

Hi [MENTION=3292224]franciscofranco[/MENTION] . Sorry to get this back to the previous pages, your answer is always clear, I totally respect and understand exactly what it says. ;)

However, I would like to add something personal, I recently search this function because my father has a peculiar habit of retiring and change position the mic, even have the ability to vary the tone of voice. lol

I have tried to explain this problem to many times unsuccessfully, record the conversation is not going to guarantee a significant change, but if he is able to understand how frustrating it is keep a conversation under these conditions, it is good for me. We talk every day because 6-7 days he's working away from home. :rolleyes:

Sorry to bore you with the adventures of my life, my intention is to show a nice face of this function.

Add also that although it is disgusting private calls recorder, the most important is that it is a significant lack of respect, even illegal according to region.

However this means leaving out many protective situations are unfortunately now the order of the day, cases of threats, extortion etc, situations that lead to depression, psychological problems or even irreversible problems much worse, better not to mention more examples. :(

A camera can do the same or worse yet here we have this Sony sensor completely legal and good quality. Clearly, something happens and it is not to our benefit. Perhaps much to lose and little to gain from an extra function that only needs software, privacy in 2014 is not sufficient reason to prohibit record your own calls. ;)

Many of our tools are used to commit crimes, however that does not make all of us criminals, I think of the function calls recorder and I see no differences.

I want to make clear that my intention is only to show a different view and nothing else. The thread is so entertaining that I was forced to comment, sorry Francisco. :D

PD: r13 works very well here. :victory: I appreciate your work.:good:
[ONE Original Android Development] LiquidSolstice:
Maybe you misunderstood. In many countries and certain American States, it is flat out illegal to record a phone call. Period.
[ONE Original Android Development] Tzfardaya:
Caveat. Those regions where it's "flat out illegal", it's only illegal to secretly record.. So long as both parties are aware of the recording, it's legal (which is why most tech support calls have the leader "this call may be recorded for quality assurance and training purposes")

In my locale, it is legal to record calls so long as one party (minimum) is aware of the recording. (so I can record a call I'm part of, but I can't record a call my GF is making to her friend, unless either my GF or her friend is aware)
[ONE Original Android Development] N.Tesla:
I understood well, maybe a little juice google.translate my comment. Or maybe not explain well. :laugh:

In my country Spain is legal in some situations.;)
[ONE Original Android Development] jlevy73:
Additional Caveat :D

In California not only does the party being recorded have to consent but there must be a beep tone throughout the duration of the call to demonstrate consent. Failure of consent and beep-tone is considered a crime and carries a maximum penalty of a year in jail. That being said, California has the strictest privacy laws in the US. I have no idea what the laws are in different states or countries but nowadays, most developers don't include in-call recording. But there's an app for that :)
[ONE Original Android Development] Tzfardaya:
Most U. S. States just require informed consent... But yeah, fines and jail terms are common for most private infractions... My province is very lenient wrt call recording...
[ONE Original Android Development] jlevy73:
Yeah Canada is cool like that, universal health care, beautiful country, nice people...
[ONE Original Android Development] kecinzer:
I still have weird battery drain. 10% over night. But I also had 3% with this kernel. Already tried furnace kernel and it's give me also 3% over night. Weird. Btw. I'm on AOSP.
[ONE Original Android Development] zephiK:
Apparently theres a bug in the modem

http://xdaforums.com/showpost.php?p=54930126&postcount=1838
[ONE Original Android Development] paychex:
Works all the time https://play.google.com/store/apps/details?id=com.skvalex.callrecorder

---------- Post added at 12:59 AM ---------- Previous post was at 12:56 AM ----------

No need to undervolt that much
[ONE Original Android Development] wp7chris:
excuse my ignorance

I am coming from the nexus 5 where cm11 was caf based and other roms like paranoid android and slimroms was AOSP. Now on the oneplus one i see that for cm11 nightlies we flash the aosp kernel and the cm11s kernel is of course, for cm11s....So is cm11s caf based and did cyanogen change the nightlies for the oneplus one to aosp instead of caf? this is all blowing my mind lol someone please clarify for me haha. Thanks.
[ONE Original Android Development] zephiK:
If you're using CM 11S... flash CM11S version.

Everything else flash the "AOSP" variant of the kernel.

No more of the CAF talk on OPO. Its either stock ROM or non-stock ROM :)
[ONE Original Android Development] kecinzer:
One is only CAF based :).
[ONE Original Android Development] LiquidSolstice:
This. Pay attention to this. It makes a hell of a lot more sense than CAF v AOSP.
[ONE Original Android Development] benzso63:
I am using Mahdi-Rom 2.7 , should I download For AOSP roms ?
[ONE Original Android Development] Bajo76:
Yes, Mahdi = AOSP
[ONE Original Android Development] wp7chris:
Haha wow thanks everyone :p
[ONE Original Android Development] sash89:
Guys why root does not work with this kernel?
[ONE Original Android Development] bernard134:
Nope, mine is working fine. I rooted it yesterday and flash this kernel this morning, everything is running fine until now. Maybe you can try re-rooting it? Because i dont think the kernel will affect anything.
[ONE Original Android Development] chr0m:
Root working fine here
[ONE Original Android Development] hellfire666:
Sometimes SU breaks when flashing kernels, just reflash SU binary it you should be good
[ONE Original Android Development] unavix:
After installing the kernel stopped working wifi and gsm. How to fix it?
[ONE Original Android Development] rlex:
Looks like. Planned to reflash at morning, grabbed phone, vibration works. WTF.
[ONE Original Android Development] bernard134:
Did you flash the correct version of franco.Kernel on your phone?
[ONE Original Android Development] nneves:
Do you have any wakelocks?

I'm using CM11-M9 with franco r13 and I don't see any drain problems:

Have you check PlayServices drain bug?
[ONE Original Android Development] nazfalas:
Had this once. Simple reboot did the trick for me.

He wouldn't have been able to boot using the wrong version.