yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] zephiK:
We talked about it earlier and we're planning just to leave the settings discussion in this thread mainly because its the home of the Franco Kernel on the OPO, when new users come here they'll be more likely exposed to the settings that were made by the community.

Maybe we'll make a mini website so everythings all organized with all the latest information would be on that page particularly so things wouldn't be as lost or separated from one another.
[ONE Original Android Development] nneves:
Sorry about this off-topic but which recovery are you using?

I'm having lots of freezes and touch issues with twrp 2.7.1.1.

Thanks
[ONE Original Android Development] fiz:ik:
I can't imagine that your issues are recovery related - or do you mean freezes and touch issues within the recovery? I'm using CWM 6.0.4.9 and have no issues - neither in the recovery nor in CM11S
[ONE Original Android Development] eainyow:
Running r14 with vomer tweaks settings and zephik's smooth scrolling makes this phone so smooth while keeping it at a lower clock rate = awesome battery life ? Loving r14 Franco definitely a winner ;)
[ONE Original Android Development] newellj79:
Tried downloading the flashable 4 or 5 times but it just hangs and eventually stops trying. :(
[ONE Original Android Development] nneves:
Yes, freezes and touch issues when I'm in the recovery, twrp in my case.

Everything is ok when running the rom.
[ONE Original Android Development] kokocabana:
Quick question: Do I just make a backup of /system in twrp before flashing over the stock kernel and restoring it before installing a new OTA?
[ONE Original Android Development] Saythis:
I would just use fastboot to flash the stock boot.img when it comes time to install an OTA.
[ONE Original Android Development] JFK1997:
The New ota installs the stock kernel, came Form 30o Franco r13 gone to 33r and stock was installed, no problems here
[ONE Original Android Development] kokocabana:
He meant if I were to use the OTA from the settings menu because that one won't install with a different kernel.
[ONE Original Android Development] JFK1997:
I installed 33r official as ota from the settings menu with twrp over 30o and Franco r13. If you have Franco, you also have twrp and so there is no problem.
[ONE Original Android Development] kokocabana:
I'm trying to avoid having to plug it into my computer. So the kernel is in /boot and not /system?
[ONE Original Android Development] newellj79:
I received the latest ota while running Franco with Phil recovery. It installed just fine. After I refreshed Franco and super user.
[ONE Original Android Development] dmarden:
The tweaks zip didn't work for me, I'm on the move so I'll post details later. Quick glance at the log seemed like something about the path not existing. I noticed it copied the init.d file and the addons folder didn't exist.
[ONE Original Android Development] SleemLDJ:
Does vomer tweaks need to be reflashed eg., after flashing a new cm11 nightly?
[ONE Original Android Development] zephiK:
No its been reiterated many times in the previous pages. A backup script is included.

Works here for multiple people. What version of Franco are you using? Do you have any kernel tweaking apps causing conflicts?
[ONE Original Android Development] jessesam:
I keep losing gps signal while on navigation. Is it because of francos kernel or madhi rom ??
[ONE Original Android Development] Nomelas:
does anyone have the stock boot img from 33R so I can flash back incase I need to?
[ONE Original Android Development] TjPhysicist:
Non-CM kernel makes root go away

I know this has been said/complained about a couple of times on here, but I'd like to go ahead and bring this to attention:

I'm currently rockin PA-4.5 (stable), whenever i flash this kernel i loose the ability to call root in any way. [Note: PA includes baked in "superuser app" (it's part of the settings menu)]. Of course I flashed and installed supersu as if i were rooting a ROM like usual, but this means that I am no longer able to use the baked in SU app. No biggie I guess, just wondering why this happens.
[ONE Original Android Development] vomer:
Maybe there will be something even better than a thread or a post!!

Lots to come guys ;) stay tuned!
[ONE Original Android Development] MICa.fighter:
Here you go: https://www.dropbox.com/s/3qehrnmeeoldpxx/cyanogenmod-g0ad30e5 #1?dl=0
[ONE Original Android Development] Brembo109:
An App ?

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] vomer:
who knows? :p you will just have to wait and see what it is :angel:
[ONE Original Android Development] Brembo109:
?

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] dmarden:
r14, latest official TWRP:

Installing '/sdcard/Download/vt_zephik_v1.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
Mounting filesystems...
Extracting files...
package_extract_file: can't open /system/addon.d/51-vomertweaks.sh for write: No such file or directory
Setting permissions...
set_perm: chown of /system/addon.d/51-vomertweaks.sh to 0 0 failed: No such file or directory
set_perm: chmod of /system/addon.d/51-vomertweaks.sh to 755 failed: No such file or directory
Unmounting filesystems...
Enjoy VomerTweaks!
script result was [Enjoy VomerTweaks!]
I:Legacy property environment disabled.
Updating partition details...
I:Data backup size is 1764MB, free: 47204MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
I:Set page: 'flash_done'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'filemanagerlist'
I:Set page: 'advanced'
I:Set page: 'confirm_action'
I:Set page: 'action_page'
I:Copying file /tmp/recovery.log to /data/media/0/recovery.log

Should be easy to figure out once I get home.
[ONE Original Android Development] MICa.fighter:
It happens because franco kernel atm doesn't include init.superuser.rc which is required for the built in su.
[ONE Original Android Development] zephiK:
I flashed it yesterday as well as today just to check and I don't have the problem. I think one of your Mounts is not mounted or is mounted that its causing conflicts. It would appear that your TWRP is not properly extracting the .zip, check what is mounted and what is not mounted.
[ONE Original Android Development] badluckclinton:
ZephiK's smooth scrolling is included in the flashable zip he uploaded?
[ONE Original Android Development] zephiK:
My smooth scrolling mod is not included in vt_zephik_v1. My smooth scrolling mod is specific to a ROM so it'd be impossible to package it together.

It could help in cases where you may experience scrolling lag.
[ONE Original Android Development] Tzfardaya:
What roms have you tested your zip on? I haven't ran it but I checked the paths that were failing in that other error report, /system/addon.d is not on my device (cm11s 33r) either.
[ONE Original Android Development] zephiK:
I'm currently using Mahdi. Other people have flashed the zip as well and it worked (I assume they're probably on custom ROMs as well since CM11S apparently doesn't have /system/addon.d?), maybe it doesn't work on CM11S due to lack of addon.d support? Thats weird that CM11S /system/addon.d is missing, on custom ROMs they do come with that folder. Usually used when it comes to backing up gapps, I can modify the zip some more and remove the backup script which will for sure make it work but then users will have to reflash the zip on rom updates.

[MENTION=1314232]dmarden[/MENTION] [MENTION=4860519]Tzfardaya[/MENTION] Can you give this flashable zip a try? https://www.androidfilehost.com/?fid=23622183712461637 CM11S ONLY (well... it should work for non CM11S roms as well, just the backup script won't be there).

You don't have to keep the settings if you don't want to, but just see if it flashes, it should. You can revert it by just deleting 01VomerTweaks from /system/etc/init.d after boot.

Note: you'll have to reflash it again when you do rom updates on cm11s.
[ONE Original Android Development] dmarden:
Will try it tonight. FYI... There was no failure message in TWRP... So I wouldn't count on people not reporting it as a sign that it's working.

I only noticed the issue because one file was there and one wasn't and the path was non existent.
[ONE Original Android Development] zephiK:
Ah so most likely, the flashable zip did work but because CM11S is missing /system/addon.d, it wasn't able to put the backup script in there because CM11S is missing that folder.

If you have FKU, you can use it to verify that the settings indeed loaded. In that case, the zip above should do the same thing as it did before, just removes the /system/addon.d missing.
[ONE Original Android Development] Tzfardaya:
Clean install and working config upon reboot
[ONE Original Android Development] franciscofranco:
Works fine here, but I'll double check again.

:)

without the community = nothing would've happen.

Probably CM's doing it wrong because this cpu cores are async. My app does it correctly.

As I said I need a log of /proc/kmsg when that happens so that I can send it to Steve (cyanogen).

Bug on the Audio stack, I think its gonna be fixed on the next OTA.
[ONE Original Android Development] noobhero:
Hi sir, here is the last kmsg last action I did was to disable pressy app then re-insert the pressy. next i made a call to test the speaker.

hope it helps.
[ONE Original Android Development] omvir:
Thanks for all the work you do, Franco! Flashed the kernel this morning, smooth and very battery friendly.
[ONE Original Android Development] shaker2k:
Have to say. It is awesome to see how far your have come from when I first saw you posting on Franco's n5 thread to now. The one plus community is lucky to be getting you bro.
[ONE Original Android Development] vomer:
Thanks for your kind words buddy :) I'm happy to be here and help out!

I'm working towards a big project that I think you guys will like! Its a lot of work but should be interesting once done :)

Sent from my Nexus 7
[ONE Original Android Development] mbudden:
What a tease. :D
[ONE Original Android Development] prstorero:
Do we get any hints? [emoji2]
[ONE Original Android Development] GreggoryD502:
Flash through TWRP or fastboot?
[ONE Original Android Development] MICa.fighter:
Its a .img file, so flash through fastboot or use flashify app.
[ONE Original Android Development] dayanandgp:
[MENTION=3292224]franciscofranco[/MENTION] , [MENTION=1978554]zephiK[/MENTION] I am currently using r14 release (AOSP based) with Mahdi ROM (Build 23082014) . Is the touch screen firmware fix present in the kernel or ROM ? If in kernel , does r14 already contains it ?

Reason for asking is , in the change log it was mentioned as " OTA 30O only " and then about all the fixes viz. touch screen, battery etc etc

PS: big thanks to franco for updating the FKU app :) I screwed up 2 times by using old FKU and then yesterday i downloaded r14 via app and it chose correct version for mahdi :)
[ONE Original Android Development] MICa.fighter:
Franco r14 has the new touch firmware.
[ONE Original Android Development] RealLordK1:
Well.

I've sideloaded the 33R update, flashed R14, and installed FKU to get the per app module.

THAT is battery life.

Now all I have to do is going deeper in the FKU use.

Thanks a lot to all the contributors here.
[ONE Original Android Development] jlevy73:
Yes the FKU app has a lot going on. You might want to find the thread that [MENTION=3097025]The G[/MENTION]inger bread man started in the N5 section. Has a lot of really good info to get you started.
[ONE Original Android Development] badluckclinton:
Did you undervolt your OPO? And by how much... Just wanna use this as a reference :fingers-crossed:
[ONE Original Android Development] SleemLDJ:
I've tried to install vomer tweaks but I got an abort error in Cwm..... Have I done something wrong?
[ONE Original Android Development] Sheeezy:
Altough I'm on R33 and r14 my touchscreen sometimes gets a bit crazy.

When I'm gently sliding my finger across the screen it will be recognized as a single touch ...

Also zooming with pinch to zoom in gallery acts very wierd and jumps forth and back.

Yesterday I installed the tempered glas protector from casebase, maybe that has something to do with it ?
[ONE Original Android Development] spacemanvt:
I am sure this has been asked before but can i run r14 with the CM11 nightlies??

thanks!
[ONE Original Android Development] hughfollett:
Yes, download the aosp version in the op!
[ONE Original Android Development] spacemanvt:
Is anyone able to get greenify and Franco to work together? I am getting an error that auto hibernation is blocked by a 3rd party tool or system settings in greenify.

I am running the latest CM11 nightly with the latest (r14) franco kernel on my OPO.

When i re flash the stock kennel i don't get that error...Any ideas for me?
[ONE Original Android Development] MICa.fighter:
Guys you can find a collection of stock kernel images if you need them: http://xdaforums.com/oneplus-one/general/cm11s-official-untouched-image-t2857110
[ONE Original Android Development] noobhero:
I think it's the per app mode in the performance settings in android's setting

I unchecked it and the warning is gone
[ONE Original Android Development] zephiK:
You have to find the cpu bin to your snapdragon. Google on about this. Either that or Undervolt - 25 on every interval and test it. It's more or less trial and error until you find the sweet spot.

What's the error? What rom?
[ONE Original Android Development] sui81:
Has anyone tried the Vomertweak for CM11s only ?

[MENTION=1978554]zephiK[/MENTION]

I flashed the old Version (vt_zephik_v1p.zip) yesterday and saw that the CPU is undervolted to 1267MHz and the I/O Scheduler changed to DEADLINE, so i think it works without the addon.d Folder.
[ONE Original Android Development] Dzhedaj:
As franco's kernel has got the latest commits merged, what idle battery mA do you guys get on it in Battery Monitor Widget?
[ONE Original Android Development] zephiK:
My script does not touch voltages what so ever. Any modifications of the voltages were done on your part either by a kernel tweaker app that already had Undervolt your phone. That line of code is commented out.

The reason why Undervolt is not included in the script is because the Undervolt values are different based on the phone.

And yes it does work without the folder, I've said this before. The only difference is that you won't have the script backed up and will need to flash the zip again if you do any rom updates. Since you're on stock, it'll be when the next Ota comes out. For others on custom roms, use the other version and it'll be backed up on every rom update.

You can verify the changed values by looking in fku. Give it a good minute or two so the changes can be made as they aren't done instanteously on boot.

But yeah I don't think the cm11s.zip is needed. If add-on d is missing then it just won't copy the file but the tweak script file will still copy so just ignore the error.
[ONE Original Android Development] Brembo109:
I'm running the first version of the script that was posted first on CM11s. Everything worked. I manually undervolted and set up PAM's afterwards

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] Ky0sHiR0:
After flashing Franco r14 (aosp) and vomertweaks on slimsaber my Phone is not responsible with Double tap to Wake. I need to do it two, three times before my phone wake up... Should i install fku and check that option?
[ONE Original Android Development] zephiK:
FKU doesn't have a option to enable/disable gestures. They're already on, maybe your phone doesn't like the lower frequencies or its your ROM. Try bumping up the minimum cpu frequency higher to 1.5 GHz and see if it still happens. I don't have any problems though, its definitely not a kernel problem though.
[ONE Original Android Development] spacemanvt:
That fixed it!
[ONE Original Android Development] Ky0sHiR0:
It happen only when i dont use phone for a while... How Can i bump it? At your script level?
[ONE Original Android Development] jlevy73:
Mine's the same, the touchscreen is still being worked on by the Cyanogen team. What was fixed in the last update was the issue where the screen would become completely unresponsive. In the bug reports, touchscreen is still unresolved and is being worked on with the vendor of the driver to figure out a work around for this. For me this issue makes any launcher not completely smooth as swipes will often time be registered as a touch. Nova seems to be the best but Google Now and stock Trebuchet are almost unusable.
[ONE Original Android Development] paychex:
The stock voltage tables are already pretty low. If anything modestly drop only the 300mhz slot

---------- Post added at 11:27 AM ---------- Previous post was at 11:25 AM ----------

Doubt it. Touchscreen is definitely different now. Not sure if for the better yet

---------- Post added at 11:27 AM ---------- Previous post was at 11:27 AM ----------

Is Greenify even necessary?
[ONE Original Android Development] zephiK:
Use FKU or any other kernel app and just change the frequency up to 1.5GHz.

Do note that it won't stick once a reboot occurs. But the problem more or less resides on ROM or you undervolted too much.

I use Greenify for Google Maps, Facebook. Other than that I don't use it all that much.
[ONE Original Android Development] Red5:
*breathes heavily*
[ONE Original Android Development] Ky0sHiR0:
Its nova launcher fault. I dont have prime version where Double tap to Wake is available. Everything is Okay on Google launcher... Its rly weird. ROM Got this functionality but launcher in free version not. I will buy prime version and See what happen i think
[ONE Original Android Development] zephiK:
Wow really? O_o I wouldn't think that a launcher would have the ability to enable/disable double tap to wake. Are you sure?

I can't really say much though as I do have Nova Launcher Prime. I've never seen a double tap to wake option in the launcher.
[ONE Original Android Development] fiz:ik:
Nova can do many things with root access, but I've never seen an option to enable/disable tap2wake, too.
[ONE Original Android Development] Nomelas:
Thanks! do i have to flash it in recovery or can I use the FKU app to "restore" it?
[ONE Original Android Development] Ky0sHiR0:
Look at this. Maybe im wrong but dont know what is hiding there before i buy it.
[ONE Original Android Development] zephiK:
That isn't it.... double tap to wake is not a feature controlled by software. It could be if it correlates with hardware which requires root access. Nova Launcher doesn't even ask for root access. Double tap on there is gestures for:

App Drawer, Show Previews, Toggle Notification Bar, Expand Notifications, etc.... (I have Prime), apps, or shortcuts.

It has nothing to do with Nova disabling the ability to double tap to wake your screen. Simply put it, Nova lacks the permission to do so.
[ONE Original Android Development] Ky0sHiR0:
So... I really dont know what is happening...maybe i will try reflash kernel without ur vomertweaks ?
[ONE Original Android Development] MICa.fighter:
Its a .img file. You may try restoring with FKU, or you can use Flashify app to restore, or flash it through fastboot. Since it is a .img it cannot be flashed through a recovery as a recovery flashable .zip file.
[ONE Original Android Development] zephiK:
Does your ROM have gestures enabled? This is surely not a kernel problem. So check the options, depending what ROM you're on such as Settings -> Display.

If all comes to worse, use another ROM. I'm sure you mistakenly disabled the gestures for double tap to wake or your phone just is not responding properly.
[ONE Original Android Development] Ky0sHiR0:
I bet that its nova launcher fine. On Google Launcher its okay. My gestures are on...
[ONE Original Android Development] zephiK:
Shrug, I have no idea... use another launcher then or clear nova cache. Works fine here on Nova Launcher.
[ONE Original Android Development] Ky0sHiR0:
SlimSaber coming with pre-installed nova. Now i deleted apk and installed it from Google Play Store. Let's see how it works : )

Not working : ( or working with very big delay :(
[ONE Original Android Development] franciscofranco:
Why are we even discussing launchers. Makes no bloody sense.
[ONE Original Android Development] Red5:
Thank you. Trying to see what awesome goodies are being done today and instead I have to sort through random launcher chitchat. I'd rather read about what Franco is doing today, or the status of vomers teams and phone delivery.
[ONE Original Android Development] zephiK:
Originally it was about vomertweaks where he thought the problem was associated with fk or vomertweaks. So far everybody seems pretty happy with the settings, next step is possibly make some pre-configured Per-App-Modes (PAM) setups. If anyone has made any PAM settings, feel free to share them.
[ONE Original Android Development] MICa.fighter:
I was thinking about it. Guess its the way of every good kernel topic. People just start to talk about random stuff (or nonsense) because there is nothing to complain about.
[ONE Original Android Development] Nomelas:
used the flashify app, it's hanging at boot.... had to restore...
[ONE Original Android Development] MICa.fighter:
Try again, make sure you get the matching kernel for your ROM version: link. If restoring doesn't work with flashify, try other means: FKU or fastboot.
[ONE Original Android Development] Sheeezy:
Exactly the same issue right here. I just recognized it after playing with my phone a bit. Sudden zoom in/out in chrome when reading here on xda or when browsing through a list the swipes are recognized as a input. But yes I've also read on AndroidPolice, that the next OTA should look into this problem. As far as I read Synaptics is working on a possible fix for the touchscreen.

Maybe you can answer me this one too:

Do you use the "V" for the torch in the lockscreen ? It's so unreliable for me that it drives me crazy !
[ONE Original Android Development] jlevy73:
I don't use the V in the lockscreen, but just tried it out a few times and it worked ok.
[ONE Original Android Development] vomer:
Not yet! :)

*breathing intensifies* lol

Sent from my Nexus 7
[ONE Original Android Development] ChefChaudart:
Always at 100%

Hi,

For 4 hours now, my battery remains at 100 % :silly::confused:

What's this ?

Cheers
[ONE Original Android Development] MICa.fighter:
Bug. I got it on full stock cm11s so its not franco. Just do a Reboot.
[ONE Original Android Development] Nomelas:
still not working even with fastboot... it's "cyanogenmod-g0ad30e5" should I rename it? it also isn't .img.....

EDIT: renamed it to boot.img and still it's not working....

Also my ROM version is 33R (From OTA)
[ONE Original Android Development] vomer:
That's Franco's new nuclear reactor governor ;) 1yr battery life per charge!

Sent from my Nexus 7

---------- Post added at 04:57 PM ---------- Previous post was at 04:56 PM ----------

The name is not relevant. What's the error message?

Sent from my Nexus 7
[ONE Original Android Development] ChefChaudart:
I rebooted twice, still 100% ...
[ONE Original Android Development] MICa.fighter:
Interesting.. A reboot fixed for me. Then maybe the nuclear reactor thing vomer mentioned :D
[ONE Original Android Development] ChefChaudart:
Well I go to sleep, let's see tomorrow ...
[ONE Original Android Development] extream87:
True the reboot has worked for me too.

But im gonna report the bug in cyanogen site.
[ONE Original Android Development] Sheeezy:
can someone check for me if their notification LED is working this way:

activate the notification LED and set for standard behaviour always on.

Do this work for you ? On my end the LED lights up and goes off immediately and that's it.

No always on as I set in settings.