yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] Vangelis13:
Welcome to the n4! Great to have a fellow country man developing for us. Looking forward to the development of this! :)
[Nexus 4 Original Android Development] vtec_:
Used your kernel for over a year on the old i9000.

Really pleased to see you here _b
[Nexus 4 Original Android Development] Ibsonic:
Another kernel king.. The n4 has the greatest developers in the world, this is sick.. Welcome !

Verstuurd van mijn Nexus 4 met Tapatalk
[Nexus 4 Original Android Development] eep2378:
This kernel is very smooth and responsive. Most likely due to mpdecision, which I'm a fan of in any case. I remember your kernel for the sgs 1. Nice to see this here. Subscribed :)

Sent from the Nodes of Ranvier
[Nexus 4 Original Android Development] a g bell:
Anyway to increase/change the temp when led comes on 47 is to low for me on all the time when using phone on charge can l change in root explorer or terminal thanks:)
[Nexus 4 Original Android Development] bigeyes0x0:
echoing into the sysfs node during screen and LED on does not turn off the LED, and the LED keeps that state permanently. How can I turn it off in this case?

In my country, it's really hot at the moment so it's easy for the phone to hit the temperature that turns it on which I notice is actually around 40 or so. It starts at low brightness and intensify as the temperature raises.
[Nexus 4 Original Android Development] Elting:
Hey stratosk! I'm a big fan of your work and the idea with the LED is basically not bad I think. However, I am a strong user of Lightflow and the kernel messages about temperature are not interesting for me. Moreover, there seems to be conflicts between Lightflow and semaphore messages.

Can you please make that an option and that you can turn off the function? That would be great! :)
[Nexus 4 Original Android Development] stratosk:
LEDs triggers API is fully configurable. You may disable all triggers:

echo none > /sys/class/leds/red/trigger

echo none > /sys/class/leds/green/trigger

echo none > /sys/class/leds/blue/trigger

I just found a small bug that in thermal trigger that it does not turns off the LED when deactivated. So, please make sure that the LEDs are off before issuing the commands above.
[Nexus 4 Original Android Development] BlueFlame4:
Hi stratosk,

a sound control would be awesome because the mic gain is very low on stock kernel. My call partner hardly understands me when I'm using a kernel without sound control to boost the mic gain.

Could you add this to your to do list? :)

Sent from my Gameboy Color
[Nexus 4 Original Android Development] CerB:
Hey you :cyclops:

Trying this kernel for the first time, seams to be running great, but when my phone sleeps for like 5 min, the it lags like crazy the first 3-4 seconds when i turn it on again, why is that ? running carbon and had matr1x before ?

i am running 0,6 version
[Nexus 4 Original Android Development] siddjazz:
Thanks for this. The red LED is a tricky one :)
[Nexus 4 Original Android Development] grigoris_a:
Also running carbon but no issue here.Flash rom again to reset kernel and then 0.6 kernel

Sent from space...
[Nexus 4 Original Android Development] reginickneo:
Bit frustrating that red light is on... It's awesome that is is brighter when the phone is becoming hotter.

But i don't think is worth the battery. Nearly always on when i'm using the phone.

Edit: that's why i disabled it
[Nexus 4 Original Android Development] iplexus4:
So where we can read about led api? or something in structure triggers?
[Nexus 4 Original Android Development] adil_:
+1.

I'm running PA 26th April build...

Sent from my Nexus 4
[Nexus 4 Original Android Development] stratosk:
I think I will have it disabled by default in next version. I will prepare a new version of Semaphore Manager that will support LED triggers handling.

You may find some basic stuff in Linux documentation https://github.com/stratosk/kernel_msm/blob/jb-4.2/Documentation/leds/leds-class.txt

I have no problem on stock ROM. I can't be sure about the lags on PA.
[Nexus 4 Original Android Development] CerB:
Reinstall your rom, just dirty flash it

Sendt fra min Nexus 4 med Tapatalk2
[Nexus 4 Original Android Development] jelle2503:
I like being able to tamper with led triggers.

But it kills the charging led light function on CM10.1

Verstuurd van mijn Nexus 4 met Tapatalk
[Nexus 4 Original Android Development] stratosk:
Did you try to disable them?
[Nexus 4 Original Android Development] TechXero:
Hey !

Am coming from Franco Kernel which was giving me issues with signal resetting every few seconds. I like to try new Kernels. Am flashing it as we speak. I always flash the Kernel reset, prior to flashing new kernels. Dunno, but I feel safer that way.

Also I don't use Kernel managers specific to each kernel, I bought Trickster's MOD ... It works with almost all kernels and is more flexible. Correct me if am wrong ...

Eager to give this baby a whirl. Am on XenonHD of course, best ROM ever ;)
[Nexus 4 Original Android Development] ceejay83:
this kernel and franco haven't had any modifications to wifi/data, so you may get the same results
[Nexus 4 Original Android Development] TechXero:
Well, I dunno what happened but now on every Kernel my Carrier Signal keeps dropping n resetting every few minutes. Getting annoying...

Got no clue what caused this. And yes I did reset to stock kernel to no avail xD

~ Sent Via My XenonHD'ified Nexus 4 ~

| Twitter / Blog : @TechXero / TechXeroBlog |
[Nexus 4 Original Android Development] bustem:
I had the same problem with 01.05 cm and 26. pa. :D

Sent from my Nexus⁴
[Nexus 4 Original Android Development] Elting:
No such problems here... either with PA 04/26 nor with the latest PA Builds.

I'm now on Semaphore 0.6.0.
[Nexus 4 Original Android Development] RealiZms:
So far so good!

I would add ROW scheduler as its most current. Thanks for your work!
[Nexus 4 Original Android Development] apatal:
It's already there. Use Semaphore Manager to set it. :)
[Nexus 4 Original Android Development] stratosk:
Yes, I think these are anything you need.

Hi,

thanks for the log!

I think it's the known issue. I'll check it.

I dropped ROW scheduler some versions ago.

I think we can do without it (Linux kernel maintainers had doubts about it).
[Nexus 4 Original Android Development] apatal:
Oh OK. Noted. I suggest removing it in the feature list in the OP then, just to avoid confusion in the future. :)
[Nexus 4 Original Android Development] emanuele1986:
Hello!

Yesterday i had the same problem. I started my tracks with the 94% of battery, phone in airplane mode, only the gps active, i did only one photosphere and 4 photos. In 4.30h the battery died. I forgot to install cpuspy to see the cpu frequency.

here the statistics

https://www.dropbox.com/s/behteial2qn5a3a/Screenshot_2014-01-05-14-34-14.png

https://www.dropbox.com/s/phi4ney4da0p6ax/Screenshot_2014-01-05-14-34-19.png

https://www.dropbox.com/s/5kp0q2qbwnbmftj/Screenshot_2014-01-05-14-34-29.png
[Nexus 4 Original Android Development] readon1:
Deleted
[Nexus 4 Original Android Development] hulicow:
Are you running on default settings?
[Nexus 4 Original Android Development] twowheeler:
Stratosk could undervolting hurt a device? Even though it doesn't reboot or shows issues?
[Nexus 4 Original Android Development] emanuele1986:
ROM stock e kernel stock setting, only undervolted
[Nexus 4 Original Android Development] stratosk:
AFAIK, undervolting a chip (CPU) can't harm it.

It can only cause instabilities that may crash the system with possible data loss (due to inproper shutdown)
[Nexus 4 Original Android Development] hulicow:
Turn On Hotplug Algorithm change only this settings:

Min Cores: 1

Max Core: 4

Dynamic Hotplug Up Threshold: 95

and just tweak this values on ondemand governor as posted by stratosk:

Touch Load: 65

Touch load threshold: 15

Touch load duration: 900
[Nexus 4 Original Android Development] dhruvmalik:
Congratulations to everyone who commented or contributed to make this thread over 600 pages.

Love the Kernel.
[Nexus 4 Original Android Development] stratosk:
New version 2.0.0

- Linux kernel 3.4.76

- lge_touch_core: Implement Double Tap to Wake functionality

- Interactive governor: latest updates from CAF

- lge_touch_core: Remove debug messages

- nefilter: xt_qtaguid: Remove debug messages, fixes from CAF

- sync: Fixes from CAF

- ledtrig-thermal: Fix issue that suspend procedure was blocked during boot (screen remain off)

- touchwake: Fix possible race condition

- Possible fix of kernel panic during update of gamma values

About Double Tap to Wake.

Implemented from scratch and hints from show-p1984 and LG G pad kernels (thanks).

The basic idea is known: touchscreen remains _always_ powered to handle input events

and wake up the device with a double tap.

User have to double tap on the _center_ of the screen (to limit accidentally wake ups).

Double tap is disabled by default. To enable it run the command bellow as su:

echo 1 > /sys/devices/virtual/input/lge_touch/dt_wake_enabled

If you run the above command during screen off, the command will remain pending until

the next power on. Then it will be actually executed.

Touchwake functionality is still implemented and it should be disabled if double tap to wake

is enabled.
[Nexus 4 Original Android Development] svnhvn:
Thank you!!
[Nexus 4 Original Android Development] themike10452:
Thanks man! Will try it soon. Any chance of a CM version?

Sent using my nexus⁴ running crDroid Simple 4.4.2 (Dalvik) powered by Piasek v7 CM Linux 3.4.75 kernel.
[Nexus 4 Original Android Development] GreenSGS:
My Friend, double tap to wake, is working like a charm. Excellent. Thanks a ton. :good:
[Nexus 4 Original Android Development] matthewgwilt:
I was gagging to ask that too! (Sneaky request... Sorry!)
[Nexus 4 Original Android Development] chavocarlos:
Yeah, works well, but how to disable if battery drain faster?.
[Nexus 4 Original Android Development] GreenSGS:
Just echo 0 instead of 1.
[Nexus 4 Original Android Development] themike10452:
if you used terminal command to enable it just use the same command but use 'echo "0" ' instead of "1"

Sent using my nexus⁴ running crDroid Simple 4.4.2 (Dalvik) powered by Piasek v7 CM Linux 3.4.75 kernel.
[Nexus 4 Original Android Development] readon1:
Will the command survive a reboot?
[Nexus 4 Original Android Development] thracemerin:
Nope
[Nexus 4 Original Android Development] stratosk:
No thoughts at the present.
[Nexus 4 Original Android Development] malcho:
Finally dt2w on semaphore.

Great job my friend
[Nexus 4 Original Android Development] themike10452:
it's disabled by default, after reboot it will return to default. So to keep it enabled you have to add this command line to an init.d script and save it.

Sent using my nexus⁴ running crDroid Simple 4.4.2 (Dalvik) powered by Piasek v7 CM Linux 3.4.75 kernel.
[Nexus 4 Original Android Development] Arju:
Woah! DT2W works flawlessly! Much smoother than the way it's been implemented in other kernels. Hope there will be a way to make it stick after a reboot.
[Nexus 4 Original Android Development] thracemerin:
Use an init.d script
[Nexus 4 Original Android Development] Goku80:
Guys would you say on demand is more battery friendly than interactive on this kernel? Many thanks. :)
[Nexus 4 Original Android Development] themike10452:
Ondemand is more aggressive, it ramps up faster than interactive, so it should eat a bit more battery with a boost of performance.

Sent using my nexus⁴ running crDroid Simple 4.4.2 (Dalvik) powered by Piasek v7 CM Linux 3.4.75 kernel.
[Nexus 4 Original Android Development] stratosk:
There will be available soon as an option in Semaphore Manager
[Nexus 4 Original Android Development] Goku80:
I know only reason is cause I know stratos tweaked it that's all.
[Nexus 4 Original Android Development] themike10452:
edit: sorry I didn't see your reply earlier. Too bad :(

Sent using my nexus⁴ running crDroid Simple 4.4.2 (Dalvik) powered by Piasek v7 CM Linux 3.4.75 kernel.
[Nexus 4 Original Android Development] stratosk:
Forgive me, but I think this is not a correct assumption. A faster ramp up does not guarantee more power consumption.

I don't know if ondemand ramp up faster and I didn't see any scientific measurements and comparison between 2 governors.
[Nexus 4 Original Android Development] Arju:
Woah, I definitely learned something new today. I googled init.d and found a tutorial on how to do it. I did it and it works! Thank you for pointing me in the right direction. This kernel is awesome!
[Nexus 4 Original Android Development] themike10452:
I guess you're right, but I've using both governors since my Xperia Arc S and it "feels" like Ondemand is a little more heavy on the battery.

Sent using my nexus⁴ running crDroid Simple 4.4.2 (Dalvik) powered by Piasek v7 CM Linux 3.4.75 kernel.
[Nexus 4 Original Android Development] Goku80:
Higher the ramp the quicker the process hence less battery load if I am not mistaken
[Nexus 4 Original Android Development] thracemerin:
That depends 100% on the use case, if you are talking about screen off operations then the race to idle principle probably applies, but in other use cases it may not.
[Nexus 4 Original Android Development] Goku80:
True forgot about that. You maybe correcf
[Nexus 4 Original Android Development] themike10452:
That's the way Paul (Faux123) sees it. He calls it race to idle, the process is finished faster and the cpu goes to idle faster. But I'm not convinced with this theory, as long as you are using your phone the phone will be processing data, and it won't go to idle. Here comes the work of the governor which decides when to push frequencies and online idle cores.

Sent using my nexus⁴ running crDroid Simple 4.4.2 (Dalvik) powered by Piasek v7 CM Linux 3.4.75 kernel.
[Nexus 4 Original Android Development] Slymobi:
[MENTION=278972]stratos[/MENTION]

How will this double tap to wake effect deep sleep ?

does this now mean that the device will never deep sleep ?

Cheers

we are all just evolved organism's
[Nexus 4 Original Android Development] thracemerin:
The phone will still deep sleep, but a small amount of power will be used to keep the touchscreen active in order to listen for the doubletap.
[Nexus 4 Original Android Development] Slymobi:
OK, and what about power button off, will this disable the double tap? for example is double tap to wake only a working feature as of when screen times out or is it a working feature under all circumstances.

we are all just evolved organism's
[Nexus 4 Original Android Development] thracemerin:
all circumstances, it's not the same as touchwake.
[Nexus 4 Original Android Development] Slymobi:
1 more ....... lol

upcoming feature to disable in semaphore app also means its getting the easy to enable option too then ? ;)

I don't have terminal nor a PC to enable this at present also not comfortable to attempt a script eeeeek

cheers

we are all just evolved organism's
[Nexus 4 Original Android Development] themike10452:
There's a feature that disables DT2W and S2W if you lock the screen by yourself using power button or any other method.

Sent using my nexus⁴ running crDroid Simple 4.4.2 (Dalvik) powered by Piasek v7 CM Linux 3.4.75 kernel.
[Nexus 4 Original Android Development] stratosk:
This is true only for touchwake. If double tap is enabled it won't be disabled even after using power button
[Nexus 4 Original Android Development] Slymobi:
Cool, thanks.

p.s I bit the bullet and added the line to an existing init.d and rebooted.

working great here ;)

I overcame my fear and got a success lol. A lesson learnt and very happy.

Not too sure on this feature yet but I know you just made a lot of users very very happy.

You are a one of a kind Stratos :)

we are all just evolved organism's
[Nexus 4 Original Android Development] Midomad:
Yes.

Envoyé depuis mon Nexus 4 avec Tapatalk
[Nexus 4 Original Android Development] Broooooook:
The new DT2W works really great! With other kernels which also have this feature, sometimes the screen fails to respond at first attempt and this makes it less appealing. But with Semaphore, I've got instant respond every time I double tap so far. Gonna see how it affects the battery. It would be perfect to have such a feature at reasonable cost of power.
[Nexus 4 Original Android Development] themike10452:
how about this:

echo "Y" > /sys/module/input_core/parameters/pwrkey_suspend ?

Doesn't work with Semaphore?

Sent using my nexus⁴ running crDroid Simple 4.4.2 (Dalvik) powered by Piasek v7 CM Linux 3.4.75 kernel.
[Nexus 4 Original Android Development] zorginho:
Hey stratosk can u take a look on your gamma mod implementation? Seems that the calibration is applied only partially, I'm comparing the same color profile ( bundi22 iphone5) with your kernel and _mplus and on _mplus the colors are correct, on yours are still washed.

Hope I helped :)

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 Original Android Development] Swords.Grizzlebee:
Thanks for the update!

For anyone who is interested, these are the new Bundi22 Iphone5 colors that have been implemented in a few kernels recently, (Matrix, for example), converted for Semaphore manager. Not sure where these values actually came from, as I haven't seen them on the shared gamma spreadsheet, but for what it's worth, here you go:

18 66 116 0 2 2 7 0 1

for red, green, and blue
[Nexus 4 Original Android Development] themike10452:
Here's an excel file that has the color profiles in both Franco and Semaphore formats. It should be a great help. (bundi22 iphone5 is on line 46)

http://www.mediafire.com/?nxx0fwad732kcos

Sent using my nexus⁴ running crDroid Simple 4.4.2 (Dalvik) powered by Piasek v7 CM Linux 3.4.75 kernel.

---------- Post added at 01:07 AM ---------- Previous post was at 01:06 AM ----------

this is because mplus uses franco gamma hack, semaphore is different, thus it has different settings.

Sent using my nexus⁴ running crDroid Simple 4.4.2 (Dalvik) powered by Piasek v7 CM Linux 3.4.75 kernel.
[Nexus 4 Original Android Development] stratosk:
I don't know. I haven't test it.

Sure I will double check it.
[Nexus 4 Original Android Development] themike10452:
We'll have to ask him what app did he use to set the gamma settings. I think the error is on his side and not yours :P

Sent using my nexus⁴ running crDroid Simple 4.4.2 (Dalvik) powered by Piasek v7 CM Linux 3.4.75 kernel.
[Nexus 4 Original Android Development] mati1414:
How to use it?
[Nexus 4 Original Android Development] zorginho:
Using faux clock for _mplus and semaphore manager in semaphore and I'm not so stupid I know how to apply a profile -.-

And values of spreadsheet for semaphore

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 Original Android Development] Swords.Grizzlebee:
Thanks for the link, but the values I posted are different than the original Iphone5 Bundi22 color profile, even thought they are still attributed to him. That's why I was posting them for anyone that wanted to try them out. It is the profile that Matrix 12.5 uses by default now.
[Nexus 4 Original Android Development] zorginho:
Deleted
[Nexus 4 Original Android Development] themike10452:
matr1x has a different gamma controller. Faux gamma.

Sent using my nexus⁴ running crDroid Simple 4.4.2 (Dalvik) powered by Piasek v7 CM Linux 3.4.75 kernel.
[Nexus 4 Original Android Development] Swords.Grizzlebee:
I used Trickster to determine the default Matrix colors, wrote them down, flashed Semaphore, used trickster to set the gamma values I'd saved from Matrix, then installed semaphore manager and copied the values under "gamma control". That's what I shared. I've seen people do this before. I don't understand your point. Does this result in an incorrect translation of the color settings?
[Nexus 4 Original Android Development] MameTozhio:
Oh my god I've been waiting for DT2W for so long thank you =D
[Nexus 4 Original Android Development] oxxshadow:
Anyone recommed a governor and or settings for good battery and performance. Great kernel BTW! Love the DTP2Wake
[Nexus 4 Original Android Development] snak3ater:
Double tap in semaphore.. It's like a dream come true.. Thanks a lot :)
[Nexus 4 Original Android Development] Broooooook:
I think this is the right approach.

Actually when I was using matrix, I set bundi22 manually using the general spread sheet with Trickster Mod and saved that profile. Then changed to semaphore, loaded and applied the profile with trickster, installed semaphore manager, and the color sequence is the same as the one from the semaphore sheet.

So I guess the default color setting Mathkid applied in Matrix is not THE "bundi" from the sheet. Maybe another version, whatever. Thanks for sharing that anyway :good:.
[Nexus 4 Original Android Development] sean222:
Thanks for the update and DT2W...hoping this new approach/implementation is more reliable than other kernels :)
[Nexus 4 Original Android Development] Broooooook:
I used bundi22 with Matrix (set with trickster mod) and am using it now with semaphore (set with semaphore manager). I can't say I notice a big difference, or maybe just because my eyes are not sensitive enough:D
[Nexus 4 Original Android Development] Mercado_Negro:
From Semaphore website:
[Nexus 4 Original Android Development] artifex21:
I cant find the option to turn on double tap to wake. Do i have to install bponury's app or what ? Would appreciate the help :)
[Nexus 4 Original Android Development] thracemerin:
The instructions are in stratosk's release post, it's not in semaphore manager yet, he said soon.
[Nexus 4 Original Android Development] llevo3:
i sent you pm
[Nexus 4 Original Android Development] ihancioglu:
Hi [MENTION=3750240]stratosk[/MENTION],

I would like share first impressions about double tap to wake.

Overnight battery consumption was % 0-1 on my setup in previous versions. That was %6 last night. I don't know about consumption of dt2w functions generally as I am just using that feature first time. I will try showp's dt2w and get back to you about battery drain.

I think there are some bugs still in there. For example I just tried to wake the device with double tap - does not work. Then wake up with power button. Touch screen was not working, then I do screen off and on again with power button a few times. Touch Screen is back to work but navigation buttons are not function. Then a few seconds later that buttons back to work..

I think my logs are useless as that problem was a few hours ago. Which logs are useful for this issues? Logcat, dmesg or both? I will gather the logs as soon as I face again.

Thanks,
[Nexus 4 Original Android Development] zorginho:
With sema I notice the color change but seems incomplete dunno how to tell better. I have to try to use faux clock to apply the bundy22 profile also with sema!

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 Original Android Development] schmitzekater:
I was facing a similar issue today maybe it's kernel related.

Woke the device via double tap and LMT quit working after a few hours. Soft buttons still worked.

happened again a second time after reboot but this time the soft buttons did not work as well.

I'm trying now without double tap to wake to see if it's my birthday is my configuration.

Using latest purity with LMT 2.0 RC7

Gesendet von meinem Nexus 4 mit Tapatalk
[Nexus 4 Original Android Development] stratosk:
Hi,

The power consumption seems OK to me.

About the issue you faced. Please send both logs (dmesg is most important to me)

If you can reproduce the issue it's even better.

So far, I didn't face similar issues.
[Nexus 4 Original Android Development] Goku80:
i have not faced such issues since last night when i flashed the kernel..the only thing that i faced regarding the d2tw is that sometimes when the phone sleeps like a baby the feature does not work and i need to switch the phone on by power button..not a big issue though...i have enabled the feature through rootexplorer though i am not using a script
[Nexus 4 Original Android Development] TheDarkDefender:
+1,

Same here. The functions ( both touch wake and dtw) seem to get disabled after the phone goes into deep sleep.

Sent from my Nexus 4