yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] mdaamir1989:
Hi zaclimon ,

Im not sure which of the below are true as to DT2W not working consistently ,

1. As a user reported previously even in r216.2 freqency of 192Mhz is still present inspite of u removing it .

2. Mckael's implementation of DT2W is not precise . The reason i say this because i have been testing semaphore and this kernel back and forth just to see how DT2W behaves , using semaphore kernel DT2W wakes the screen every single time , but thats not the case when i use your r216.2 kernel . The screen wakes up after 4-5 taps.

So not sure which of the above two points are valid . If it helps semaphore uses 384 MHz as the deep sleep frequency ... Doesnt have a 192 MHz frequency step.

I am sorry if i am dragging the topic of DT2W too much . The only thing stopping me from using this kernel is DT2W not working consistently ...

Thank you for your time.
[Nexus 4 Android Development] slipknot31:
perfect this kernel in CM and AOSP, thanks for work
[Nexus 4 Android Development] AndyYan:
"Flash back from stock"? You mean I have to boot with CM's own kernel once, then flash SMF on the next boot?

Sent from Google Nexus 4 @ CM12

[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
[Nexus 4 Android Development] zaclimon:
Yeah stock kernel in this case implies the CM's original kernel before flashing SM-Franco. Also do you have any on-boot tweaks enabled? It could play a role in DT2W not working.
[Nexus 4 Android Development] zakoo2:
flashed this SM franco two days ago and... I must say, I was thinking of getting a new phone because of the horrendous battery life CM had. Now it's like it's been reborn. Thank you very much! :)
[Nexus 4 Android Development] AndyYan:
Nope, everything is stock CM as-is. I'll try reflashing later.

Sent from Google Nexus 4 @ CM12

[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
[Nexus 4 Android Development] coffeecore:
How do I enable init.d support? I want to flash a MOD.
[Nexus 4 Android Development] hypemanisus:
Any hopes for multi rom keh support?

I LOVE MY SLUTTY N4
[Nexus 4 Android Development] zaclimon:
The kernel doesn't have native init.d functionality, though I remember that somebody used term.init to get init.d working.

The Kexec patch is already in the kernel. You're good to go with Multirom.
[Nexus 4 Android Development] Maibol:
from the play store download busybox installer and download universal init.d support and run the script from the app the easy way ;)
[Nexus 4 Android Development] elliot2112:
I just wanted to say thank you. This is the first kernel that I actually can notice a significant improvement in battery life. Great work. I'm running this along with unofficial temasek ROM.
[Nexus 4 Android Development] AndyYan:
Thank you for the heads-up, it enabled me to enable DT2W via the init.d route.

Feels strange to say, but isn't init.d support a norm across most if not all custom ROMs/kernels?

Sent from Google Nexus 4 @ CM12

[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
[Nexus 4 Android Development] ΦDroid:
I think there is a new FK version coming soon :D
[Nexus 4 Android Development] zaclimon:
Yep saw the test build inside the test folder. Get ready because it'll be there really soon. [emoji14]

Envoyé de mon Nexus 7 en utilisant Tapatalk
[Nexus 4 Android Development] rogerstyo:
why spendthat again for only a marginal tech gain.
[Nexus 4 Android Development] BassBlaster:
a bit more detaiL pLs
[Nexus 4 Android Development] migueldbr:
this kernel completely breaks root acess for me (SuperSU). tried flashing SuperSU again, still does not work..any help?im on purity+ rom
[Nexus 4 Android Development] Maibol:
i try it with purity + and everything was fine buddy how did you install it ? give us more info in that way we can help u ;)
[Nexus 4 Android Development] migueldbr:
same thing i always do...flashed awesome kernel cleaning script ( http://xdaforums.com/nexus-4/development/mod-kernel-cleaner-script-superwipe-t2121701 ) and then flashed kernel...dont know why this happened then...had to reflash the rom again(dirty flash) to gain root=/

EDIT: reflashing rom seems to have fix the issue, now this kernel works just fine!

may i request sweep2dim?
[Nexus 4 Android Development] Maibol:
lol great that you fix it buddy and yes is better to dirty flash never fail to me ;) :p
[Nexus 4 Android Development] zaclimon:
Sadly, I won't add any more wake/sleep method than DT2W because it can conflict and cause some unecessary problems.

Though I could add 192 MHz as it was requested, I don't know if the stock configurations do have 192, (Doesn't look like it) but let's try it to see if it's stable. :)
[Nexus 4 Android Development] migueldbr:
you got it wrong buddy, the sweep2dim is not a wake/sleep method. Check the video from the furnace kernel to see what i am talking about ( http://xdaforums.com/nexus-4/orig-development/kernel-furnace-1-0-0-nexus-4-t2817681 ). if you dont want to add it its fine, no problem=p.But i actually find sweep2dim very useful when using the phone on low light conditions!

btw stock configs dont have the 192 step, but a lot of other kernels have it and it works just fine, never had any issue=)
[Nexus 4 Android Development] zaclimon:
I concur it's not the same thing, my apologizes. Though the same thing remains, Savoca's implementation is based off Stratosk's DT2W/S2W while I use McKael's DT2W. Technically, it could be possible if I "backport" sweep2dim but even then, I would need to ditch McKael's method to include S2W and I don't want to remove it because I find it good enough.
[Nexus 4 Android Development] migueldbr:
oh sorry, i didnt think it was based of dt2w!too bad but i guess i will keep using the screen filter app then=p
[Nexus 4 Android Development] ObihoernchenDE:
Please don't add too many features.

Franco is a clean and solid kernel. Too many features can cause many bugs. I hope this kernel will stay 'minimalistic' as well :)

Btw: R212 released :)
[Nexus 4 Android Development] KcLKcL:
I agree, it's not franco if it has too many features.

Anyways, r212 is out =]
[Nexus 4 Android Development] zaclimon:
Yeah don't worry guys, I know that's the intention of Franco kernel and this is why I won't add too many stuff. (I want to keep it minimalistic as well :p) Probably the only other thing I will add for the time being will be the 192 MHZ step for even more power saving.

As for r212, I'll probably work on it either sunday or monday. (Labor day)
[Nexus 4 Android Development] Maibol:
+1 the 192 mhz is very very stable you can check barome or hellsdog source they have it running great for a while ;)
[Nexus 4 Android Development] Wulfric:
Hello! How can i enable dt2w? The setting in synapse gives me error "SCheckbox has failed"
[Nexus 4 Android Development] marcof93:
There are lots of apps like Trickstermod, PerformanceControl or Semaphore manager.
[Nexus 4 Android Development] zaclimon:
You can also use the dt2w.conf to configure the different options. Here's more information about it

http://lilotux.net/~mikael/pub/android/kernel/N4/README_dt2w.txt

I'll add the infos on the third post later.

Envoyé de mon Nexus 4 en utilisant Tapatalk
[Nexus 4 Android Development] zaclimon:
Hi people, I have a little gift in this labor day :p

r212:

- Upstream updates from Franco (Hotplug driver enhancements, fixes from r211)

- Added the 192 MHZ Freq (384 MHZ is still the default min step, use whatever CPU tweaking app you have to modify it lool)

- Updated fauxsound version to 3.5 (with some new telephony stuff)

- Misc TRIM improvements

- Compiled with up-to-date SM GCC

It's available now in the download folder! As I said before, up to this point, I'll probably won't add new features as we'll derive from the actual franco.Kernel.

Enjoy!! :)
[Nexus 4 Android Development] phadly:
[MENTION=4217103]zaclimon[/MENTION]

I have some request..can you add sweep2wake and sweep2sleep feature on next build?thanks.. :)
[Nexus 4 Android Development] zaclimon:
I literally said it one page ago but I'll say it again here: No sleep / wake method except DT2W.

Envoyé de mon Nexus 7 en utilisant Tapatalk
[Nexus 4 Android Development] _BobsoN_:
[MENTION=4217103]zaclimon[/MENTION]

Can you add swipe2sleep into your mod, please

tapatalked!
[Nexus 4 Android Development] zaclimon:
http://xdaforums.com/showpost.php?p=55053031&postcount=3
[Nexus 4 Android Development] icu64:
OK granted I did read the op I just have one question... Think you can enable the sweep to wake functions that work with vomer tweaks?
[Nexus 4 Android Development] zaclimon:
I won't enable s2w, s2s, dt2s. Only dt2w will be kept. Just wondering, is dt2w working with vomer tweaks?

Envoyé de mon Nexus 7 en utilisant Tapatalk
[Nexus 4 Android Development] icu64:
I'll go check now bro, give me a sec
[Nexus 4 Android Development] emanuele1986:
To use f2fs with cyanogen or other ROM not compatible i have to convert only data partitition?

Example:

Format data to f2fs

Wipe

Install ROM

Install gapps

Install kernel

That's right?
[Nexus 4 Android Development] icu64:
It doesn't work
[Nexus 4 Android Development] zaclimon:
Yeah that method should work without problem.

Ahh Alright, I may have some future project regarding the merge of all SM-Franco features into an app. It could help me with my app learning.

Envoyé de mon Nexus 4 en utilisant Tapatalk
[Nexus 4 Android Development] icu64:
Ever think about changing the name of the kernel to something else? I mean yea most of your work is based off of Franco's but some of it has to be original. Give it its own identity and name and give yourself some credit to bro... Just don't forget about franco
[Nexus 4 Android Development] AndyYan:
Agreed - just the name of the toolchain doesn't do it justice that well. Especially considering this is one of the best we can have on CAF.

Sent from Google Nexus 4 @ CM12

[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
[Nexus 4 Android Development] emanuele1986:
Can i convert also system and cache or only data?
[Nexus 4 Android Development] zaclimon:
Yeah I did think about changing the the name of the kernel. Though, I never changed it because it would change the "objective" (If I can say so) of the kernel which is only a "Bumped up" version of franco.Kernel.

That said, with the projects I have in mind, it might be nice to change the name. :) (I already have the name thought up)

The most noticable difference will be on the /data partition. I have it converted on /cache also but it's not that useful.

/system won't be noticable as well and it is better to keep it as ext4 because you don't have to re-convert /system everytime as f2fs. (as the rom installer script formats to ext4 everytime you install a rom)
[Nexus 4 Android Development] icu64:
What name do you have in mind? Is it going to have something to do with gundam?
[Nexus 4 Android Development] zaclimon:
LOOOL you already know. Yeah but I didn't chose it's name because I like this particular Gundam, just because I like the name for the context. Actually I've already used it once before but it will be kind of it's "resurrection".
[Nexus 4 Android Development] yochananmarqos:
/offtopic

I can't help it anymore, what in tarnation does "LOOOL" mean? Lots Of Of Of Laughter? Laughing Out Out Out Loud? :p
[Nexus 4 Android Development] TheDarkDefender:
Oh,that's just the Canadian form of "LOL". ?
[Nexus 4 Android Development] prog19:
Hi folks. With 216.2 (euphoria OS 08/03/15) I cant set the minimum cpu frequency to 384 mHz in synapse. It keeps returning to 192 mHz. There is anyone else with this ? Any hint ?

Thanks to the dev for putting this great piece of work together.

I'm a Brazilian without English Course, sorry and be comprehensive :)
[Nexus 4 Android Development] zaclimon:
I use a simple "lol" when the thing isn't all that funny (almost being a sarcastic thing) .

http://xdaforums.com/showthread.php?p=59035946

Hope it works. [emoji14]

Envoyé de mon Nexus 7 en utilisant Tapatalk
[Nexus 4 Android Development] emanuele1986:
I will convert data and cache thanks
[Nexus 4 Android Development] prog19:
Worked like a charm, thank you
[Nexus 4 Android Development] swimma:
Synapse support

I installed 216.2 on Stock ROM 5.0.1. DT2W works perfectly. Thank you!

I wondering some people told here I can activate USB OTG support with Synapse. On my device Synapse app only shows "No UCI support detected". Trickster Mod app works but it has no option for USB OTG.
[Nexus 4 Android Development] yochananmarqos:
You need UKM in order to use Synapse.
[Nexus 4 Android Development] swimma:
Thank you, UKM was missing. Just flashed it, Synapse works.
[Nexus 4 Android Development] TheDarkDefender:
If anyone's wondering, I just tested and the kernel works flawlessly with 5.1 roms.

Cheers,

D
[Nexus 4 Android Development] pompidoi:
Tested the 216 kernel on 5.1 too and working fine (Euphoria with 5.0.2 blobs)
[Nexus 4 Android Development] Csacsifiu:
Deleted
[Nexus 4 Android Development] swimma:
I tried USB OTG with 216.2 Kernel on 5.0.1 original ROM with no luck.

OTG activated by Synapse. The file /sys/module/msm_otg/parameters/otg_hack_enable contains 1. But the USB cardreader seems not to be activated when I plug it. Yes I use an Y-cable and additional power source and OTG used to work with Android 4.3 and Ziddey Kernel with this hardware. :(
[Nexus 4 Android Development] Csacsifiu:
Install stickmount app https://play.google.com/store/apps/details?id=eu.chainfire.stickmount
[Nexus 4 Android Development] swimma:
Thank you. OTG works fine with Stickmount. However I have to mount the USB drive manually in Stickmount. It doesn't mount it automatically when I plug in the card reader.
[Nexus 4 Android Development] yochananmarqos:
Also install USB Host Diagnostics. . Run the test & follow the instructions. It will install a few things & prompt you to reboot.
[Nexus 4 Android Development] zaclimon:
New project teaser...

Without any kernel updates these days, the thread became near dead. Meanwhile below is what I've been working on.

[MENTION=4467696]AndyYan[/MENTION] I'm pretty sure you were waiting for that one. XD

I'm currently searching for a themer. (Because I struggle at everything design related...) PM me if you're interested.
[Nexus 4 Android Development] AndyYan:
"Yay" is not enough to express my excitement :D

And this simple Material style looks appealing enough to me... It's a simple app anyway, isn't it?

(or maybe I'm simply trying to cover the fact that I don't know anything about theming :D)
[Nexus 4 Android Development] zaclimon:
Yeah it is a simple app, and the theme isn't that really much of a problem. I'm more searching for somebody who can do the icons and some drawables for the app. XD

Envoyé de mon Nexus 7 en utilisant Tapatalk
[Nexus 4 Android Development] aviz1911:
PM Franco :p

He is an all-in-one developer/themer.
[Nexus 4 Android Development] zaclimon:
Mehhh that might be asking too much loool. :p
[Nexus 4 Android Development] sd3993:
can/should i flash this on 5.1? :p

I know the original can't be flashed since the ram disk differs from 5.1
[Nexus 4 Android Development] gharrrrrr:
5.1 hasn't even officially been released yet for N4. So all 5.1 ROMs are still using older 5.0 blobs so any kernel for those should also work still on any of the "5.1" ROMs around for N4.
[Nexus 4 Android Development] sd3993:
yeah i jumped it. works fine :)
[Nexus 4 Android Development] icu64:
Hope the app is coming along well
[Nexus 4 Android Development] zaclimon:
I'm almost done, I just need to finish the about section and do some cleanups and the app should be ready. ;)

EDIT: Below are some screenshots about the final design of the app. Hmm looks like my phone colors are too saturated compared to the screenshots. On my device, the blue is closer to the banner's than to the one in the screenshots.
[Nexus 4 Android Development] synace:
First: [MENTION=4217103]zaclimon[/MENTION] thanks for the Franco kernel for CM12 & mako. You're helping to keep an older device alive & well.

I enabled encryption and switched to this kernel to hope to realize a performance gain. I think it's snappier now. Thanks!! But, there's a few things happening in logcat I wanted to ask about.

From what I understand this is benign and can be ignored. Is that correct?

E/PowerHAL( 1793): touch_boost: failed to send: Connection refused

At complete idle: the MPDecision is starting and closing over & over w/ an error. I thought, in relation to the previous item, MPDecision was disabled?

I/ANDR-PERF-LOCK(28278): Listener starting
I/MP-Decision(28278): MPDecision server starting
I/MP-Decision(28278): OPTION ENABLED: Control sleep modes
I/MP-Decision(28278): OPTION ENABLED: Adjusting average
I/MP-Decision(28278): Decision parameters CPU 0: Nw=0.000000, Tw=0, Ns=0.000000, Ts=0
I/MP-Decision(28278): util_h_and=0, util_h_or=0, util_low=0
I/MP-Decision(28278): Decision parameters CPU 1: Nw=1.900000, Tw=140, Ns=1.100000, Ts=190
I/MP-Decision(28278): util_h_and=35, util_h_or=75, util_low=20
I/MP-Decision(28278): Decision parameters CPU 2: Nw=2.700000, Tw=90, Ns=2.100000, Ts=240
I/MP-Decision(28278): util_h_and=0, util_h_or=400, util_low=0
I/MP-Decision(28278): Decision parameters CPU 3: Nw=3.500000, Tw=90, Ns=3.100000, Ts=240
I/MP-Decision(28278): util_h_and=0, util_h_or=400, util_low=0
I/MP-Decision(28278): Decision parameters: poll_ms: 9 decision_ms: 50
E/MP-Decision(28278): Unable to open rq_depth file

And last, I've enabled encryption and I get a boat load of these. But I think it's from the ROM, not the kernel, is that correct?

D/VoldCmdListener( 172): cryptfs getpwtype

Thanks in advance!

Edit: For now, since I'm on CM (which has /etc/init.d/90userinit), I've added: /data/local/userinit.d/99sabremod as:

#!/system/bin/sh
# place script in /data/local/userinit.d/*
# called by /etc/init.d/90userinit.sh

unameStr=`uname -r`;
if [[ "$unameStr" == "3.4.106-franco.Kernel-SaberMod-r216.2-CM" ]];
then
stop mpdecision;
fi;
[Nexus 4 Android Development] zaclimon:
Hmm it shouldn't be enabled but it looks like the power hal is still enabled. (related to the encryption maybe?)

You can rename the /system/lib/hw/power.msm8960.so to power.msm8960.so.bak and the issue should be gone. You should receive an error saying that the powerhal doesn't exist but it doesn't matter.

Envoyé de mon Nexus 7 en utilisant Tapatalk
[Nexus 4 Android Development] synace:
Thanks, I'll give that a shot. Could it also be disabled in the kernel?

https://github.com/omnirom/android_...mmit/e482834de0d5da00d61d104341e131b3bf7d6d42

Edit: I have the following files: power.default.so and power.mako.so

http://xdaforums.com/showpost.php?p=46507552&postcount=2 says to rename the .mako one. I'll report back in a minute.

---------- Post added at 08:47 PM ---------- Previous post was at 08:21 PM ----------

This worked! Thanks, I renamed /system/lib/hw/power.mako.so to /system/lib/hw/power.mako.so.bak

My strategy for mpdecision didn't work however. Any thoughts on how to make this work? Is it something that should be in the MOD or is it something you can do on the kernel level?

#!/system/bin/sh
# place script in /data/local/userinit.d/*
# called by /etc/init.d/90userinit.sh

unameStr=`uname -r`;
if [[ "$unameStr" == "3.4.106-franco.Kernel-SaberMod-r216.2-CM" ]];
then
stop mpdecision;
fi;
[Nexus 4 Android Development] zaclimon:
[MENTION=2713164]synace[/MENTION] Well the renaming of the power.msm8960.so is present the init scripts of the kernel. That said, it may be possible that like I said either your encryption can't make file change it's name or, only the power.mako.so is acting up as mpdecision. That said after you renamed it, you should have a spam in your logcat related to touch_boost not finding anything. This is normal and won't cause any issue.

I don't quite understand what happened after you renamed the power.msm8960.so because you copied 2 times your script over. Is the issue fixed or it still remains?
[Nexus 4 Android Development] synace:
Sorry typo: I renamed /system/lib/hw/power.mako.so to /system/lib/hw/power.mako.so.bak

With regard to "stop mpdecision", My attempt didn't work, and it wakes the device from sleep briefly. Is there a change you could apply at the kernel level to prevent mpdecision daemon entirely?
[Nexus 4 Android Development] zaclimon:
The thing I don't understand is how mpdecision can even run if it's daemon in /system isn't supposed to run. I can't really force something that's not even present. (mpdecision is completely disabled at kernel side) I'll try CM12 on my side and I'll come back at you whether if I have the same issue.

EDIT: [MENTION=2713164]synace[/MENTION] I've found the issue. mpdecision on CM acts now as a service instead of a driver module. Looks like it is needed for their performance profiles stuff. What you can do is either rename the file /system/bin/mpdecision to mpdecision.bak or delete it completely. I'll fix this up in the next kernel release.
[Nexus 4 Android Development] synace:
Good to hear. You can possibly just "STOP" the service, instead of renaming the file. I thought the userinit.sh strategy would work, but maybe you can figure it out better than I. I'll rename the file for now. Thanks!

Edit 2: renaming it worked for now, no errors in log related to the filename or "[Dd]ecision"

Edit: log of trying to stop the service (I added a log message to the userinit I wrote).

So, the userinit runs and it stops, but then it starts up again later.

adb logcat | grep --line-buffered -E "(userinit|decision)"

I/MP-Decision( 1781): Decision parameters: poll_ms: 9 decision_ms: 50
I/MP-Decision( 1787): Decision parameters: poll_ms: 9 decision_ms: 50
I/MP-Decision( 1793): Decision parameters: poll_ms: 9 decision_ms: 50
I/Sabremod( 1898): Applying 99sabremod via /etc/init.d/90userinit.sh
....
I/MP-Decision( 2270): Decision parameters: poll_ms: 9 decision_ms: 50
I/MP-Decision( 3033): Decision parameters: poll_ms: 9 decision_ms: 50
I/MP-Decision( 3295): Decision parameters: poll_ms: 9 decision_ms: 50
[Nexus 4 Android Development] zaclimon:
Renaming the file isn't a "clean" stop the service I concur. That said, another alternative would be to remove everything mpdecision related to the init.mako.rc. Honestly I would say that's just too much if there's no problem with only Renaming mpdecision.

I reverted too fast to my current rom so I didn't see what was the consequences kernel side. Can I get a dmesg when you'll have tried this out?

EDIT: Regarding your log, I said previously that it was needed for performance profiles stuff so even if you disable it, if (in theory) the performance profiles are activated, it will start mpdecision depending on the situation.

Envoyé de mon Nexus 7 en utilisant Tapatalk