yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] drmclove69:
When flashing a kernel with cm10.2 you gotta flash supersu 1.50 for now...
[Nexus 4 Original Android Development] kundica:
Okay thanks. I'll give it a shot.

Sent from my Nexus 4

---------- Post added at 05:53 PM ---------- Previous post was at 05:47 PM ----------

Flashing the new supersu worked. Thanks!

Sent from my Nexus 4
[Nexus 4 Original Android Development] Ümit:
I use this:

245	244	240

64	68	118	1	26	0	64	48	1

64	68	118	1	26	0	64	48	1

64	68	118	1	26	0	64	48	1

"2nd rev, 2nd variant: Dark, contrasty, rich colors, brightest whites, sureal, even grays

This is the one you try first, just to see what IPS can really do."
[Nexus 4 Original Android Development] stratosk:
Thanks, my friend!

Kernel development requires extensive test on the target machine.

Unfortunately, I can't afford more than 1 phone per 1-2 years.

More over my main job and family does not leave me more free time (actually I dedicate all my free time in kernel development).

I hope in the future to find a way and work 100% in kernel development. :)
[Nexus 4 Original Android Development] stratosk:
I provide my own initramfs. Maybe they changed something there for su.

Could somebody post CM10.2 boot.img?
[Nexus 4 Original Android Development] faddyie:
Just flashed 1.50. 2 questions..

I got trikster mod, i checked that mp decision is off..thermal throttle is off... I have turned them on.. Does this kernel has ita own provision to cater mp decision and th.throttle. should i on it or off it?

Semaphore app errors in su rights. I have got updated su 1.45. What to do.

4.3 stock.
[Nexus 4 Original Android Development] LOVE ME PLEASE:
Well, you are doing a great job supporting the Nexus 4, and thank you for that. Keep up the great work, and I will be donating soon!
[Nexus 4 Original Android Development] stratosk:
Please use Semaphore Manager(install busybox) to enable hotplug driver. There is no mpdecision anymore.

Please keep stock thermald driver.

Thanks mate!
[Nexus 4 Original Android Development] a g bell:
I stand corrected and learnt something:)just a little confusing when rooting ye olde sgs1 with cfroot kernel via Odin which might leave other former sgs 1 users a little confused

Thankyou:)
[Nexus 4 Original Android Development] akbisw:
Any chance of adding sound control? Would love to get rid of the hiss in my headphone. Driving me crazy lol. Love this kernel so far. I can feel the passion bursting out. First time trying semaphore. Thank you for your work. Now back to my work lol
[Nexus 4 Original Android Development] stratosk:
Maybe. I'm not sure yet. :)
[Nexus 4 Original Android Development] akbisw:
I will take that as a yes :D
[Nexus 4 Original Android Development] stratosk:
As you wish... :)
[Nexus 4 Original Android Development] ashishv:
Semaphore app is showing me no root access in jarjar's rom.Other apps get root access.Any suggestion?
[Nexus 4 Original Android Development] pughie:
[MENTION=4004496]ashishv[/MENTION] Busybox needs to be installed :thumbup:
[Nexus 4 Original Android Development] ashishv:
Tried that doesnt work.
[Nexus 4 Original Android Development] jc monkeyballs:
I had the same issue and flashing SuperSU 1.51 fixes my issue
[Nexus 4 Original Android Development] ashishv:
Hmm im using supersu 1.51 and tried reflashing it too.
[Nexus 4 Original Android Development] Slymobi:
kernel works perfectly on jarjar rom. try.........

uninstall semaphore app and busybox , recovery wipe cache and dalvik. install busy box and normal load binaries then install semaphore app.

worked for me.

If I've helped you....... Thank yourself for asking the Question :)
[Nexus 4 Original Android Development] kundica:
If you still need it... Here's the boot.img from the build I compiled that gave me the issue.
[Nexus 4 Original Android Development] thracemerin:
Yeah, the CM ramdisk starts the SU daemon, superSU does this with an init.d script. It's easy enough to use an init.d script to start the builtin CM superuser as well.
[Nexus 4 Original Android Development] linezero:
How do I make the touch wake to work?
[Nexus 4 Original Android Development] C4SCA:
how does the new hotplug from semaphore works? always on all 4 cores?
[Nexus 4 Original Android Development] sir*mez:
That explains why I lose root when I flash this kernel. Oh well, time to flash superSU because I want to give this kernel a chance for the first time.
[Nexus 4 Original Android Development] adichandra:
i use aosp 4.3 by jarjar, root is fine with other apps, but the semaphore app keeps asking me for root even though i already granted it. any idea?
[Nexus 4 Original Android Development] thracemerin:
Install busybox.
[Nexus 4 Original Android Development] stratosk:
If you have enabled hotplug driver, you may set minimum number of online cores to 1-4.

You may also set up_threshold (default 25). Over this threshold driver will bring online one more CPU.

Else you may disable completely the driver and have 4 CPUs online always.
[Nexus 4 Original Android Development] soumoks:
First of all,thanks for a great kernel,absolutely love your work!,have a query here

am using your kernel with jarjar124 aosp build,the latest version of the rom has O3 optimizations enabled while the latest version of your kernel has O2 optimizations enabled,will these conflict? don't know much about these optimizations,i would be glad if you or someone could correct me,thanks again! :)
[Nexus 4 Original Android Development] capoooro:
Don't worry it's ok

pizza mandolino pasta
[Nexus 4 Original Android Development] stratosk:
Thanks for your comments.

You will not have any issue with this.

Kernel may be built separately from ROM and may have different build options and flags (optimizations).
[Nexus 4 Original Android Development] Goku80:
Strato mou megale kernel is working great for rasbean 4.3. Many euxaristw:D
[Nexus 4 Original Android Development] MaDInDy:
Hi stratosk

You try merge update dexopt binary from leaked S4 4.3 ?

I use this patch with rasbeanjelly 4.3 stock kernel

Its work fine and smoothness.
[Nexus 4 Original Android Development] stratosk:
Hi,

No, I didn't try it
[Nexus 4 Original Android Development] David_Vaz:
Thanks for all Stratosk, I mentioned the problem via MP has been fixed.

Thank you!! :D :D :D
[Nexus 4 Original Android Development] capoooro:
Very well Your kernel fly on my rasbean... Tnx

pizza mandolino pasta
[Nexus 4 Original Android Development] pitjago74:
Finally works muy gamma colors... Halfbreed:D:D:D

Great work, Stratosk

Enviado desde mi Nexus 4 usando Tapatalk 2
[Nexus 4 Original Android Development] californicated:
Did anyone check if it's working on 4.3?
[Nexus 4 Original Android Development] Midomad:
Deleted.

Envoyé depuis mon Nexus 4 avec Tapatalk
[Nexus 4 Original Android Development] stratosk:
It works.
[Nexus 4 Original Android Development] trillo69:
I see this option but I don't understand it: Higher frequency threshold = 1350000. Can anyone clarify it?

Anyway, [MENTION=3750240]stratosk[/MENTION] I have a question. I see that everytime I touch the screen, core frequencies scale to 1134MHz, similar to what mpdecision does on stock. Is there any way I can tweak that value to another value (1026MHz for example)? Thanks in advance.
[Nexus 4 Original Android Development] Ümit:
Semaphore + Stock rom = more than 4u screen on + good performance.

There is still 19% battery.
[Nexus 4 Original Android Development] stratosk:
When the CPU frequency is equal or greater than this threshold, higher under uV value will be applied. Else lower under uV will be used.

So, you split the frequency table in 2. Lower and higher frequencies that use different undervolting values.

Yes, you may use touch_load tunable in ondemand.

Now, the default value is 75. This leads the CPU to 1134MHz.

A value of 65 will push the CPU to 1026MHz when you touch the screen.

Of course you may use any threshold, according to your needs for performance/battery.
[Nexus 4 Original Android Development] Vangelis13:
Kernel running very nicely on Rasbeanjelly 4.3. Μπράβο Στράτο!
[Nexus 4 Original Android Development] snak3ater:
Right now you get 1134Mhz because the touch load value is set to 75..Lower it down if you want the cpu to jump to a specific freq on touching the screen..setting touch load to 65 as stratosk said will leads to 1026Mhz. Value of 55 will lead the cpu to 918Mhz..Similarly reduce the touch load & you will notice decrease in Cpu Freq jump as well.But decreasing touch load will effect the performance as well..
[Nexus 4 Original Android Development] flaviocc:
Stratosk,

Great kernel, smooth and excellent battery.

Running J version with jarjar rom.

Thank you.
[Nexus 4 Original Android Development] kelah:
Hi stratosk.

Franco said that stock behavior of GPU is go to sleep at 320mhz frequensy and he changed it to 128. http://xdaforums.com/showpost.php?p=44048233&postcount=41163

If i'm not mistaken it's latest lines at this commit: https://github.com/franciscofranco/mako/commit/3f4458c489fe538fe23b8da518a78852c9f55603

I looked using trikstermod (it can show current GPU freq) on 1.5.1 kernel - and stock behavior is weird: when you swiping tabs GPU freq is 128 but after 1-2 sec it becomes 320.

What do you think of it? Maybe it save some battery when reading ebook?
[Nexus 4 Original Android Development] californicated:
I enabled it in your Semaphore App, but it doesn't seem to work. Is there something more to do?
[Nexus 4 Original Android Development] Kitch16:
Sorry if this has already been mentioned, but when I use v1.5.1 on Latest rasbeanjelly I get weird graphical issues, almost like lag. This issue wasn't there prior to the kernel flash. Anyone else having this issue and is there a way to fix it?
[Nexus 4 Original Android Development] capoooro:
Try to leave it switch off without interventions. Don't click power button, I mean. Then try to tap. It should work

pizza mandolino pasta
[Nexus 4 Original Android Development] kelah:
Works for me.

It works when screen goes off due timeout not by power button.
[Nexus 4 Original Android Development] spr33:
I asked about doing this the other day but had no response..
[Nexus 4 Original Android Development] kelah:
Use 1.5.1j.
[Nexus 4 Original Android Development] stratosk:
I didn't study the code.

But, as far as I know, if the GPU go to sleep the clock will be 0 and almost no power will be consumed.

I think that changing the frequency before the GPU go to sleep will do nothing.

EDIT: about the trikstermod app. How frequently does the app poll the GPU frequency? I mean if it polls the GPU freq every 1 or 2 sec, it's normal that you will see later the frequency increase
[Nexus 4 Original Android Development] californicated:
Ah, ok. I thought it would be working like s2w. I assume there is no way to lock the screen with a touch, slide, etc. ?
[Nexus 4 Original Android Development] Kitch16:
Yeah, I just realised that I was using the wrong version. I'll leave my stupidity at home from now on :')
[Nexus 4 Original Android Development] trillo69:
Thank you very much for the explanation, seems a great solution to me. :)
[Nexus 4 Original Android Development] kelah:
Every 1sec I think. When I don't touching sceen for some period of time (about 2sec) it shows 320.

I just don't know if GPU really can go to sleep when screen on. If it goes, yep, there is no point to change it before.
[Nexus 4 Original Android Development] stratosk:
The tz_sleep function in the code is used when the GPU goes to sleep.

When the screen is on obviously the GPU is not in sleep mode. Maybe it's in idle but not in sleep.
[Nexus 4 Original Android Development] kelah:
Then this doesn't make any sense for me.

I open trickster and leave it on info tab. After 1-2 sec gpu freq becomes 320. Info on screen is changing (cpu load/freqs) so gpu isn't sleeping but obviously there is no load - so why 320mhz? When I touch screen (scrolling info tab for example) it becomes 128, after I leave it - it's becomes 320 again...
[Nexus 4 Original Android Development] stratosk:
I didn't touch GPU code.

So, there are 2 possibilities.

Either stock kernel or trickster app has a bug.

Since, I have no regression regarding GPU, I trust Google. :)
[Nexus 4 Original Android Development] Corintio:
I'm on stock 4.3 and loving this kernel, BUT... I have a problem. I can't switch on the flash when recording a video, and I honestly believe I could do it before, when I was on the stock kernel. Could anyone else try, please?

Enviado desde mi Nexus 4 usando Tapatalk 4 Beta
[Nexus 4 Original Android Development] stratosk:
I'm afraid it's not kernel related.
[Nexus 4 Original Android Development] ScumDroid:
Works fine for me. What ROM are you on? Im on rasbean and this kernel. [MENTION=3750240]stratosk[/MENTION] did you implement faux gamma? Great work on the kernel btw. Thanks :good:
[Nexus 4 Original Android Development] zephiK:
He mentioned stock 4.3. Works fine here too, on CM 10.2 Jellybro
[Nexus 4 Original Android Development] ScumDroid:
lol im blind :eek:
[Nexus 4 Original Android Development] stratosk:
New version 1.5.2

- Linux kernel 3.4.55

- mach-msm: acpuclock-krait: Fix PVS bin information in cputable info

- Add service in init.rc about SuperSU daemon (recommended by Chainfire)

- Add CM10.2 support for su (untested)

Please find the download links in the new XDA menu on top of the screen (or in www.semaphore.gr)
[Nexus 4 Original Android Development] Corintio:
Sorry for the false alarm, guys. I rebooted and it works! :confused::silly:

As you were, gentlemen, nothing to see here.
[Nexus 4 Original Android Development] flaviocc:
One question... You turn on the flash when the camera record or before you begin the record?

Here I just turn on /off before starting record.

Tks
[Nexus 4 Original Android Development] Corintio:
Before I begin recording, of course; if you touch the screen when recording what you get is a frame of the video saved as a picture.

It's just that the flash wouldn't turn on, no matter what I did, until I rebooted. Strange.
[Nexus 4 Original Android Development] flaviocc:
If you used the frontal camera and didn't switch to the back the flash don't turn on. Happens with me.
[Nexus 4 Original Android Development] franciscofranco:
You are wrong :) Just cat the gpuclk while idling and you'll see it at 320MHz ;) I will explain better when I get back home.
[Nexus 4 Original Android Development] kundica:
I can confirm it's working with CM10.2 Superuser. Thanks!
[Nexus 4 Original Android Development] ghul21:
Yup. Works great with cm ;) akso semaphore manager :D

Wysyłane z mojego Nexus 4 za pomocą Tapatalk 2
[Nexus 4 Original Android Development] LOVE ME PLEASE:
1.5.2 already! Can I say I love you? Wow, happy flashing!!!
[Nexus 4 Original Android Development] adichandra:
great kernel, but im confused about manually undervolting each step. do i need to enter the command in terminal emulator or what?
[Nexus 4 Original Android Development] zephiK:
use his app. semaphore manager from play store.
[Nexus 4 Original Android Development] adichandra:
i cant manually uv each clock with the app.
[Nexus 4 Original Android Development] stratosk:
You can't undervolt each step.

You may only undervolt frequencies in 2 groups. Lower and higher freqs.
[Nexus 4 Original Android Development] jcmaddox1:
Really wish i understood the gamma settings for this kernel as im tired of looking at the stock colors...
[Nexus 4 Original Android Development] adichandra:
is it possible to use trickster mod so i can undervolt each step?
[Nexus 4 Original Android Development] zephiK:
I agree. Its very unorganized and not sure what the

"## ## ## ## ## ##" means.
[Nexus 4 Original Android Development] jcmaddox1:
As far as i can tell it doesn't match up with any numbers on the colorsheets, There's too many numbers for that. So it'd be nice for a little bit of explanation. OR to implement Franco gamma controls instead - Since it's all sliders, and thus easier to most if not all people to adjust.
[Nexus 4 Original Android Development] :
Here's a little explanation
[Nexus 4 Original Android Development] jcmaddox1:
That seems to be extremely complicated considering the easier ways of doing it, but thanks.

Thought I understood it, but I don't.
[Nexus 4 Original Android Development] stratosk:
From Semaphore change log (there is also an excel that convers other kernel values to Semaphore):

You may tune gamma through sysfs using the following path:

/sys/devices/virtual/misc/gamma_control/gamma_r

/sys/devices/virtual/misc/gamma_control/gamma_g

/sys/devices/virtual/misc/gamma_control/gamma_b

You have to pass 9 values for each file (r, g, b). For example:

echo "64 68 118 1 0 0 48 32 1" > /sys/devices/virtual/misc/gamma_control/gamma_r

For your convinience, franciscofranco uses the terminology below for array's positions

"greys, mids, black, XX, contrast, brightness, saturation, white, XX"

So, he leaves positions 4 and 9 with hardcoded values. (You may also leave them untouched)
[Nexus 4 Original Android Development] stratosk:
No, you can't.
[Nexus 4 Original Android Development] twowheeler:
I recommend using the semaphore app for settings on this particular kernel. Although it misses some features from trickster everything you need is in the app. And it gives you a chart about how your voltages are set.
[Nexus 4 Original Android Development] pughie:
1.5.2j is running beautifully with the latest rasbean, the battery life is particularly impressive, great work stratos :)
[Nexus 4 Original Android Development] Goku80:
Strato file mou signomi gia tin erotisi but I tried the kernel with the latest jellybro ROM that is based on cm10.2. Now the stock kernel that comes with it has superuser by koush working fine. Is there a way to make your kernel to be compatible please or is it just playing around with boot.img
[Nexus 4 Original Android Development] KingKonga:
Did you change the wifi drivers in your Kernel version stratosk? Been using CM10.2 from euroskank with stock Kernel and it was only connecting very badly with my router. After installing your kernel everything works perfectly. :good:
[Nexus 4 Original Android Development] stratosk:
You mean that you tried 1.5.2 and it didn't work for you?

Because I made changes for koush's superuser.

No changes in Semaphore regarding WiFi.
[Nexus 4 Original Android Development] Goku80:
I will try again

---------- Post added at 11:41 AM ---------- Previous post was at 11:30 AM ----------

works great now :victory:
[Nexus 4 Original Android Development] gpvecchi:
Hallo, are the default gamma of this kernel, the same of stock one? Thanks!
[Nexus 4 Original Android Development] X DoZ3R:
Can someone describe in ondemand settings values mean?

From Nexus 4
[Nexus 4 Original Android Development] stratosk:
Yes, stock.

touch_load: (default 75) when you touch the screen, this pseudo load will be 'appeared' to governor. Practivally means that the CPU will go to 1134MHz (at minimum).

touch_load_threshold (default 10): over this real threshold, the touch load will be applied. This means that if the real CPU load is greater than 10 then touch_load will be applied.

touch_load_duration: (default 1100ms) the above calculations will be applied for 1100ms if you touch the screen. After this period, ondemand works as usual.
[Nexus 4 Original Android Development] Tortel:
Testing CM 10.2 (20130731 release) with Koush's superuser 4.3 beta 2 and your 1.5.2 kernel. So far seems to work fine til now ;)
[Nexus 4 Original Android Development] linezero:
how to make it work? :S
[Nexus 4 Original Android Development] stratosk:
Just enable the option in semaphore manager. The if the device is switched off due to inactivity you may turn it on touching the screen.
[Nexus 4 Original Android Development] snorfu:
Hey stratosk, i got 10 to 12% hsic wakelock...any change of fixing this? Except this your kernel is amazing fast :)

Gesendet von meinem Nexus 4 mit Tapatalk 4 Beta
[Nexus 4 Original Android Development] franciscofranco:
Just a FYI, TouchWake has nothing to do with Slide2Wake or Touch Control. The first one is just a tap to wake up the display if it times out naturally. The other two are to wakeup the display anytime just by sliding the finger in the screen, same effect as the power button.
[Nexus 4 Original Android Development] -iNSiGhT-:
I can share the script for Moles Halfbreed and Moles Brighter (than halfbreed)... But my scripts only work with Harsh...

Another question : can we undervolt (I saw 0.3.0 add init.d script) with Semaphore?

Paranoid mako
[Nexus 4 Original Android Development] franciscofranco:
Sorry for this, stupid XDA timed-out.
[Nexus 4 Original Android Development] franciscofranco:
Sorry for this, stupid XDA timed-out... twice.
[Nexus 4 Original Android Development] Sad56:
No, I don't have any issues for the moment :)

It works like you describe it should be.

I've just made a navring shortcuts to screen of my phone. With this it works (I never let the screen timeout itself, it's a reflex) ;)

Thanks francisco.franco I don't know this and that's why I don't understand :)

N4 - Xenon HD - Semaphore Kernel
[Nexus 4 Original Android Development] stratosk:
No, you can't undervolt. Maybe in the future.
[Nexus 4 Original Android Development] stratosk:
Thanks for the clarification.

BTW, since you are longer on this device, any idea how to get a feedback from proximity sensor?

I don't know why they made these proprietary stupid drivers. Thanks in advance.
[Nexus 4 Original Android Development] sorcio46:
I Had some troubles while trying to use this kernel on the CM10.1

After a simple flash from recovery, I rebooted the phone and when Android booted everything (from android.phone to the entire UI) was crashing and sending messages about "process xxx has stopped".

Then I went into recovery and I did:

- Wipe Cache

- Wipe Dalvik Cache

So I rebooted the phone and I got a bootloop on the CM10.1 boot animation

I restored the phone by flashing my current ROM

Version of CM: 10.1-20130411-EXPERIMENTAL-mako-M3
[Nexus 4 Original Android Development] stratosk:
Did you have a clean cm installation?

Anyway I will try it myself tonight or tomorrow.

Thanks for testing and reporting
[Nexus 4 Original Android Development] simorangkir_dcs:
Franco is still developing n4 kernel, btw.
[Nexus 4 Original Android Development] 3dawg:
Did Franco sell his N4 or something?
[Nexus 4 Original Android Development] stratosk:
I know that, I didn't say the opposite. :)
[Nexus 4 Original Android Development] Mahdi786:
No, read stratosk's post again.
[Nexus 4 Original Android Development] 3dawg:
"BTW, since you are longer on this device, any idea how to get a feedback from proximity sensor?

I don't know why they made these proprietary stupid drivers. Thanks in advance."

So what does that mean then?
[Nexus 4 Original Android Development] sorcio46:
No, it's my daily device so it was full of apps and everthing, and there I hadn't troubles in fashing Franco Kernel and coming back to the CM one when I wanted.
[Nexus 4 Original Android Development] Vangelis13:
Seriously..?

Franco has more experience on the device, Stratos is asking for advice.

Kappisch..?
[Nexus 4 Original Android Development] 3dawg:
AH, I was reading it wrong the whole time. I read it as "Since you're no longer on this device".
[Nexus 4 Original Android Development] simorangkir_dcs:
****, my mind read it exactly like yours. How the hell?
[Nexus 4 Original Android Development] reginickneo:
I'm curious about the CM compatibility. I'm using franco's kernel and it is great, but everyone raves about this kernel, how good it is and so on.

I don't wanna lose date.