yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] ALI53481:
caf for cm

I have cyanogenmod running on my Nexus 7 device. you stated that caf is for cm of derivatives roms but I can't seem to find and understand what Caf is. could you please explain what it is and give me a link to download it? thanks for your time
[Nexus 7 (2013) Original Android Development] LossyDragon:
Would like to see option #3 come soon. Along with these requests from other users. The nexus 5 has Kexec multi boot patch already.
[Nexus 7 (2013) Original Android Development] Tuckycv:
CM is no longer supported as far as I remember. CM started to do some propetiary coding and everybody seems to be dropping support for it. I don't understand the need for CM, I?m pretty happy with stock and just use this for better battery life.
[Nexus 7 (2013) Original Android Development] cowhow:
When CM became an incorporated business I was skeptical about how that would flesh out and what its impact was going to be. I know they're still pushing out ROMs for a ton of devices, but when you become a business it changes the game. From my perspective the Nexus line from Google already comes with bare bones AOSP. Yes, I know they went overboard with GAPPS, but no Sense Ui, no TouchWiz,etc.
[Nexus 7 (2013) Original Android Development] stfudude:
A few weeks ago I requested a feature to disable or enable magnetic sensor but now there is no need for that.

Download this xposed module to disable magnetic sensor: http://xdaforums.com/showthread.php?t=2621807

With this my request reduced to just two:

1. Kexec multi boot patch

2. Support for 3G usb modem
[Nexus 7 (2013) Original Android Development] CrashTestDroid:
It looks the opposite to me, there's more CAF support now because CAF is rolled out to more devices. Now deb/flo, hammerhead, mako are all on CAF. The reason is because CAF is (IIRC) source available, tuned for performance, and mainly it fixes the deadlock issues that existed on older AOSP codebase. To end users CAF makes no difference when it's working, the Android does well either way. And I think CM Inc is not (yet?) a bad company even if there are issues like with Focal. Many many roms are based on their work, and you can thank them for most device trees including Note 3 etc etc.

That said, it looks like CAF is offered in OP but no download links yet. I can wait patiently. Faux makes many great innovations and even if you don't use his built kernels in 88% cases faux code is still there in scheduler and smp :)
[Nexus 7 (2013) Original Android Development] efect:
Doesn't work for my nexus 7 2013 (clean rom/faux). Widget doesn't add to app drawer either. Please help on install.
[Nexus 7 (2013) Original Android Development] Luca.Brasi:
I'm at 012, device suddenly reboot 4-5 times in a day. I use stock KOT49H and when i was at stock kernel(before flashing faux kernel) there is a no problem like this. I though problem about my fauxclock settings and test it, but no difference with different settings. Any help for that problem? I think my device don't like faux kernel, but i love it :D

Other problem is about control app, i set my settings and set 'set on boot'. But when i reboot device settings come back to default, maybe i do something wrong with app.

And which is prefered one for battery/performance balance(es, m, u)?
[Nexus 7 (2013) Original Android Development] stfudude:
I celebrated too early. The module doesn't work.

Anyway what do you mean by widget? I don't think the module have any widget.

So yeah, in kernel solution is needed. [MENTION=225651]op[/MENTION] Please give us option to disable/enable magnetic sensor in faux clock.
[Nexus 7 (2013) Original Android Development] efect:
It has no icon in app drawer, but I got it to work with xposed. link to how to or google xposed nexus 7 2013

http://nexus7.wonderhowto.com/how-t...our-nexus-7-for-insane-customization-0149150/
[Nexus 7 (2013) Original Android Development] stfudude:
Actually I know how to install xposed framework so thank you very much for that link. I don't need any guide for that.

I think I understand now. You incorrectly thought of app icon as widget that's why you asked me about that in your last post. But all is well now that you know how to open that app (in xposed app) right?

Did that module work as intended? Did your magnetic case trigger screen off or on? As for me, the module doesn't work at all. At first I thought it works but maybe it was placebo (as with any other stuffs from xda excluding Faux kernel of course ROFL)
[Nexus 7 (2013) Original Android Development] efect:
Well it works the way I wanted to. When I close my lid it doesn't turn of the screen. The screen timeout turns it off. If the screen is off and I open the case my Tablet will turn on. I have a nexus 2013 (clean rom/faux kernel) w/ a roocase.

This is what I did step by step. Maybe that can help you.

I install the magnetic on/off like any regular app, but wasn't working so then I copy to the root folder of the apps and install to see if that work. It didn't, then they told me about the xposed, so I install that and then the magnetic and still didn't work. Forgot to install the framework for the xposed and then re-install the magnetic, click to enable it and rebooted and it started working.
[Nexus 7 (2013) Original Android Development] faux123:
kernel 013 is out!

Intelliactive added!
[Nexus 7 (2013) Original Android Development] dickenam:
Thanks Faux! Hot Reboot at about 25 seconds uptime on 13ES/13M attached is last_kmsg. Weird that it says it's not your kernel in the first line or 2, I can assure you that it was just flashed in recovery.

PA b5

http://pastebin.com/aepPqfgd
[Nexus 7 (2013) Original Android Development] faux123:
No errors detected

Boot info:

Last boot reason: Reboot

Weird, it was told to reboot.. not a kernel bug :(
[Nexus 7 (2013) Original Android Development] stab244:
I had the same thing with both 13u and 13m. Same reason given. What would happen is I would turn off screen and then it won't turn on anymore so I had to reboot manually. Thought the clocks were too high but it was far after boot and so long as it stayed awake it was running fine.
[Nexus 7 (2013) Original Android Development] Steady Hawkin:
I'm having the exact same issue as well.
[Nexus 7 (2013) Original Android Development] faux123:
are you using fauxclock? if so please wait for 179 update. there was a slight bug with the new kernel and fauxclock.
[Nexus 7 (2013) Original Android Development] stab244:
Yeah I am. I sure hope that is it.
[Nexus 7 (2013) Original Android Development] dickenam:
Faux clock update fixed me up! Thx!!!!!!
[Nexus 7 (2013) Original Android Development] wildestpixel:
I have to say Faux, I had long been a Franco user on N4 and N7 2013.

Recently I gave the Moto G a whirl and in the main none of the usual suspects for nexis devices are sporting it with kernels except y your kind self. So I bought faux clock and installed my first ever faux kernel on Moto G. Thoroughly impressed with release 4 and 5 ultras on that device I have now removed Franco from my N7 2013 and fully embraced the faux experience on here. Points to make :

More tunable

Features the user wants not what the dev can be bothered to do

Polite and helpful dev who doesn't need to constantly swear ;)
[Nexus 7 (2013) Original Android Development] stab244:
Double confirmed. Now to see how well battery life is with intelliactive. Seems smoother already though. Can't wait for N4 to get it too.
[Nexus 7 (2013) Original Android Development] vagelis:
Would v. 13 run with the ART runtime?
[Nexus 7 (2013) Original Android Development] stfudude:
+1

Intelliactive is smoother than intellidemand! Lag is minimal.

BTW does anyone know what are kernel neon mode and futex?
[Nexus 7 (2013) Original Android Development] tibere86:
+1

---------- Post added at 09:26 AM ---------- Previous post was at 09:24 AM ----------

Loving intelliactive too. Can't wait for the HTC One GPE 4.4.2 update ;)
[Nexus 7 (2013) Original Android Development] Krowbarr:
Not seeing that problem here. Running great,I had already updated faux clock though.

☞"And on the eight day the Lord made a backup"☜
[Nexus 7 (2013) Original Android Development] dickenam:
Yes, ART 4 life.
[Nexus 7 (2013) Original Android Development] manfio:
guys

how can i disable performence control to avoid conflicts with fauxclock app?
[Nexus 7 (2013) Original Android Development] faux123:
Kernel 014 is out! Minor bug fixes!!!! :D Enjoy!
[Nexus 7 (2013) Original Android Development] stfudude:
I think there is something wrong with 014.

I have made a few tasker tasks and profiles to change kernel values (cpu gov, gpu gov, etc) according to certain rules that I made.

On 014, after that task launched, the screen will immediately goes black. Only thing I can do is hard reboot.

I'm sure there are others who use init.d to set kernel values at boot or use terminal shell emulator to change the value on the fly. Can you guys confirm this issue with me? It's driving me crazy..

P/S: import this tasker project to help understand what is the issue I'm having. https://www.dropbox.com/s/dkqngxvwqlgl9it/Faux_Kernel.prj.xml
[Nexus 7 (2013) Original Android Development] seschaum:
Hi!

I can't find any kernels with "CAF" in it, does it run with CM11 Nightlies?

Thanks!
[Nexus 7 (2013) Original Android Development] dark2099:
No, not any more.
[Nexus 7 (2013) Original Android Development] Crythar:
Does this kernel work with latest paranoid android beta?
[Nexus 7 (2013) Original Android Development] El Nino1977:
I haven't tried myself but I'm sure it will work fine. PA try to keep their builds aosp with minimal cm/caf commits
[Nexus 7 (2013) Original Android Development] Crythar:
You are right. Works fine. Thank you!
[Nexus 7 (2013) Original Android Development] vengence_angels:
this kernel works with deb right?..

cause the download page has no files which starts with deb..

all the file names start with flo
[Nexus 7 (2013) Original Android Development] Brembo109:
Hey Paul can you update your recommended settings for the last changes and especially intelliactive or is it just the same as interactive?

Gesendet von meinem Nexus 7 mit Tapatalk
[Nexus 7 (2013) Original Android Development] dickenam:
Yes, plz!
[Nexus 7 (2013) Original Android Development] Crythar:
Yes, running on deb since yesterday. Works fine (mobile works)
[Nexus 7 (2013) Original Android Development] Crythar:
https://plus.google.com/app/basic/stream/z13ye5n5nrnlhhf24225edernyneht15b04

This is for nexus 5. Does not seem like you have to change anything, as he says: 'it's been pre-tweaked already. just switch to intelliactive and leave the settings default'
[Nexus 7 (2013) Original Android Development] Brembo109:
Hey Thank you. I missed that on g+:)

Gesendet von meinem HTC One mit Tapatalk
[Nexus 7 (2013) Original Android Development] creeve4:
[MENTION=3332811]faux123[/MENTION] I came across this post of yours and it got me wondering about possible interferences when using intellidemand with Showp's msm_mpdecision hotplug driver (or even your intelliplug driver) and Input-Boost, what are your thoughts?

Specifically this part of the post:
[Nexus 7 (2013) Original Android Development] faux123:
that's the older version of intellidemand. the newer versions have no issues which is been running on N7 from day 1.

Intellidemand is OLD ;) It's was invented since 2010... I may retire it in favor of the new intelliactive governor.
[Nexus 7 (2013) Original Android Development] Crythar:
Saying this, it would be even more useful if you could update the recommended settings for fauxclock. Are they still the same (replace intellidemand with intelliactive?)
[Nexus 7 (2013) Original Android Development] faux123:
intelliactive is pre-tweaked. no need to tweak it further
[Nexus 7 (2013) Original Android Development] MandoH:
Just got my N7 LTE... Can't wait to customize it with Faux123 Apps and Kernels..!! Thanks Faux123:D:thumbup:
[Nexus 7 (2013) Original Android Development] creeve4:
[MENTION=3332811]faux123[/MENTION]

I just noticed that your updater-script says: "faux123 Nexus 4 Kernel..." not a big deal, but thought I'd mention it.
[Nexus 7 (2013) Original Android Development] faux123:
:D copy and paste error. Flo/Deb is VERY VERY similar to Mako :D They are fishes from Google ;)
[Nexus 7 (2013) Original Android Development] DroidIt!:
Lol! Gotta quit doing that. :D
[Nexus 7 (2013) Original Android Development] creeve4:
[MENTION=3332811]faux123[/MENTION] is it possible to set gamma values via an init.d script?
[Nexus 7 (2013) Original Android Development] faux123:
No. The gamma is done in fauxclock. The kernel driver is just a bridge interface (it just pass the data from app to display directly. All the smarts are in the app itself).
[Nexus 7 (2013) Original Android Development] wildestpixel:
You are at exactly the same as me - all the 125's.
[Nexus 7 (2013) Original Android Development] tibere86:
What are you guys using as RGB values?
[Nexus 7 (2013) Original Android Development] creeve4:
I'm using 255 for all the RGB and 120 for all gamma channels
[Nexus 7 (2013) Original Android Development] SuperSmashedBro:
Any reason why the "stop mpdecision" toggle disappears in the Faux123 app? I can't enable intelliplug because of that
[Nexus 7 (2013) Original Android Development] stfudude:
Flash your rom again. (if custom rom: dirty flash of rom zip, if stock rom: fastboot flash update but without wipe data partition) then flash the kernel.
[Nexus 7 (2013) Original Android Development] k3mik4l:
Tried searching must be blind but can I flash this right over Franco? or if not can someone point me to a stock kernel flash zip. Thanks
[Nexus 7 (2013) Original Android Development] SuperSmashedBro:
You can
[Nexus 7 (2013) Original Android Development] stfudude:
To turn off magnetic sensor :

1. With root enabled file explorer, go to /sys/module/lid/parameters/enable_lid edit that file from 1 to 0.

2. Make a tasker task to run this command at boot: "echo 0 > /sys/module/lid/parameters/enable_lid"

P/S:

1. method 1 would not stick after each reboot.

2. I'm quite sad that Faux would not add this feature (disable or enable magnetic sensor) in faux clock app considering it is very simple and many kernel devs have already introduce it to their kernels long ago.
[Nexus 7 (2013) Original Android Development] DroidIt!:
Hey stf :) Well, as you know because you've been around awhile faux is a very busy dude. I'm sure if he see's a useful feature that he thinks is worth it, he will add it. Seriously, just out of curiosity, why do you want to be able to disable it? I mean, I have a magnetic case too and when I open my case to use the tablet the screen automatically turns on. So I think it's a really nice feature. No button presses, just bam the screen is on. So again was just wondering what would make you want to disable it.

from my N5
[Nexus 7 (2013) Original Android Development] stfudude:
I have a habit of opening and closing the cover quickly. Sometimes the tablet went dead (SOD) and only a hard reboot can bring it to life. That's why I really need the switch to disable magnetic sensor. I'm not exactly sure if it's a problem of nexus 7 or Faux kernel in particular. Most probably the former.
[Nexus 7 (2013) Original Android Development] DroidIt!:
So does the tablet get SOD you think from opening and closing the case quick or no? If no might wanna try a different rom. I'll take a look at my tab though in a bit and open and close the case a few times quick and see what happens. I'm running the latest SlimKat (3.2 released yesterday) and faux 014U. I'll let you know what I see though. :good: ;)
[Nexus 7 (2013) Original Android Development] stfudude:
I'm not interested in trying other rom. Stock rom is the best for me.
[Nexus 7 (2013) Original Android Development] DroidIt!:
Well, just tried my tab in a bunch of different ways and I couldn't replicate it. I would say either rom or case. When I was looking for a case on Amazon I did see in some reviews that people were reporting in that the magnets might have been too strong. They were saying when they had the case OPEN the tab turned off when they had the case flipped back to where the magnets were against the backside of their N7"s. Only other thing I can think from my tests is ROM. I'd maybe do a nand though and just try a different rom to see if it still does it. I'd suggest SlimKat because I know I don't get SOD"s on that rom. So, I would say to just try a different one and see if it does it still and if not then you can either choose to stay on a different rom or a different kernel or get a different case. Hope that helps. :)

---------- Post added at 12:55 PM ---------- Previous post was at 12:53 PM ----------

Oh, and this is the case I have that works good http://www.amazon.com/Devicewear-Go...1393354455&sr=8-2&keywords=devicewear+nexus+7 I'd be really surprised though if it were your N7.
[Nexus 7 (2013) Original Android Development] stfudude:
Thanks for trying to help. Actually I already found a way to disable magnetic sensor so I don't need to change kernel or rom. (Refer to my earlier post.)

Thanks again.
[Nexus 7 (2013) Original Android Development] DroidIt!:
Ah ok. Yeah I know you said you're not interested in a different rom. I was just suggesting a try just to see if it is rom related or something else. Thinking about it, it would be strange too if it were the rom. I'd almost think it would have to be something with the case. Just my thoughts :)
[Nexus 7 (2013) Original Android Development] stfudude:
Yup maybe. But there is one guy in mahdi rom thread who mentioned about this SOD problem too. He was using Faux kernel before, but now he's using mahdi's kernel. He could recall this exact problem I'm having back when he's using Faux kernel.

come to think of it, starting from version 13, the SOD frequency has significantly decreased. Maybe I already gotten used to it or maybe Faux has already fixed the bug. But just to save myself from the headache, I figure that it'd be nice to just disable the feature totally. I can still wake the tablet with doubletap2wake and it can go to sleep automatically so yeah, don't think I need the feature.
[Nexus 7 (2013) Original Android Development] DroidIt!:
Yeah I do remember getting SOD's with Faux too, but for me I haven't had probably since about 006 or 007. So, could be your rom/kernel combo. :) So yeah, after trying everything I tried though I think it boils down to either kernel/rom combo or the case. If it were me though, I'd just try loading a different rom with faux and see if it does it becuse then I'd know for sure if it were the case or not. I think that'd be a good way to narrow down your issue. Only other thing is it might be some kind of mod.

So just for my 2 cents personally I'd go in this order :) :do a nand and go back to stock w/faux and no mods and see if it does it. If yes, different rom w/faux and no mods and see if it does it. If it still did it go completely stock and see if it still does it. If it still did it, it would cost money but I"d try a different case. If it still did it...then might be the tab. If it were me, that's what I'd do anyways. ;)
[Nexus 7 (2013) Original Android Development] stfudude:
That is actually a good plan but to be honest I don't have time or motivation to do that experiment. I'd rather disable magnetic sensor and just stop worrying about this problem.

Can't afford to waste time making nandroid backup (about 20 minutes to finish) and titanium backup of all user apps (take about 1 hour). Restoring and testing the app whether it data (game progress) were restored or not would take 2 hours of my time. I have about 300 apps installed.

On a rare occasion where I got the time to do that, I would just flash the rom as a secondary rom in multirom configuration. After finish testing (satisfied or not) I'll just delete the rom and went back to stock rom.

Oh yeah forgot to mention: custom rom can't attract me anymore after I installed gravity box. Hahaha
[Nexus 7 (2013) Original Android Development] sneakerhead27:
[MENTION=3332811]faux123[/MENTION] you've been speeding up my devices since the HTC glacier lol thank you for all your hard work!
[Nexus 7 (2013) Original Android Development] edios123:
This kernel is just awesome. Not to mention the app.

But I've two questions, please answer these:

I've increased the speaker volume by 5, will my speaker go bad?

Ive changed the charge speed to 2a to use with my iPad's charger. Will it affect the battery?
[Nexus 7 (2013) Original Android Development] animania260:
I've had my speakers turned up to 9 for a good few months now and no issues. 5 shouldn't cause really any harm at all.

The battery question someone else should probably answer. But I've heard different charging rates do effect battery life-span overtime.
[Nexus 7 (2013) Original Android Development] k2thec:
I think you are safe as long as you are charging below 1xcapacity for lithium cells, seems .8 or less is recommended. so for 1000mah 1000ma, 2000mah 2000ma, and so on. the cell in our n72s is 3970 mah so I would not go over 3970ma charge rate. check out http://batteryuniversity.com/learn/article/charging_lithium_ion_batteries

google is actively working to make android functionally less open with each new release.
[Nexus 7 (2013) Original Android Development] edios123:
Thank you for the replies. I think I'll lower the charge speed to default.

And for the speaker, I'm very happy now. The sound output was really low on stock.
[Nexus 7 (2013) Original Android Development] stfudude:
[MENTION=3332811]faux123[/MENTION]

can this somehow be integrated with the kernel: https://developer.qualcomm.com/download/adreno200-nexus-kot49h.zip
[Nexus 7 (2013) Original Android Development] 77kdv77:
no. this patch is for ROM, not for kernel. just flash it via TWRP or CWM
[Nexus 7 (2013) Original Android Development] stfudude:
Have you tried it?
[Nexus 7 (2013) Original Android Development] 77kdv77:
no. I'm on 4.3 JSS15R, but this update is for 4.4.2 KOT49H and I don't think that it will be compatible the ROM I use…
[Nexus 7 (2013) Original Android Development] El Nino1977:
Either update your rom (needed as it's long overdue) :P or stick with v7 of fauxs kernel
[Nexus 7 (2013) Original Android Development] Cuzz1369:
If caf is no longer supported the OP needs to be edited...
[Nexus 7 (2013) Original Android Development] habylab:
Where is the reset needed for Franco's kernel? I only ask as per the Franco warning in the app you have!
[Nexus 7 (2013) Original Android Development] faux123:
simply flash the stock boot.img then flash my kernel afterwards. This guarantees the RAMDISK is reverted back to stock version. Many custom kernels have altered their RAMDISK settings, and I often ONLY test my kernels with stock RAMDISK settings, so this is a wise precaution in case of compatibility issues from altered RAMDISK.
[Nexus 7 (2013) Original Android Development] 77kdv77:
I will not update ROM. and I don't use faux kernel. I use my own kernel. but we were talking about adreno drivers update, not about kernel…
[Nexus 7 (2013) Original Android Development] faux123:
sometimes you need to update the matching kernel driver as well for userspace driver updates. I doubt my kernel will work out of the box with the latest Adreno drivers as is.
[Nexus 7 (2013) Original Android Development] 77kdv77:
well, QC didn't give kernel updates, only libraries for paticular ROM. it's easy to find out whether this patch is working or not. recovery backup rules :)
[Nexus 7 (2013) Original Android Development] stfudude:
Thank you for that info. I won't flash the updated drivers.
[Nexus 7 (2013) Original Android Development] 77kdv77:
on CM 11.0 and stock 4.4.2 kot49h this gpu driver update works without kernel modification. two friends of mine tested it. so I see no reason why it shouldn't work with faux kernel…
[Nexus 7 (2013) Original Android Development] faux123:
Cool thanks for the feedback
[Nexus 7 (2013) Original Android Development] ReX83:
Is this the only way to restore the missing mpdecision feature in Fauxclock?

Can you explain exactly how to proceed (I've the stock ROM with Qualcom GPU driver)?

Thanks!
[Nexus 7 (2013) Original Android Development] squeeish:
Is this the same way to return to stock kernel? (I'm on 14m.)