yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] capoooro:
Hi my friend, same problem, no log but it happens only after a reboot if I don't put the Sim code in few time. The screen became black and I have to reboot. The rest is smooth like silk

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 Original Android Development] kenshinta:
I still have the ff issue with 187

very often i lose touch control coming from sleep, even though slidetowake function does register, and all hardware buttons function.

hence though i can unlock the phone no touch input registers, and even if i can show the shutdown menu by long pressing powerbutton, i cannot select anything since no touch inpur registers.

this is in combo of semaphore 1.7x-1.8x + touch control 1.8.x

I also observed this with franco pre 1.97, but newer versions after 1.97 seems to not display this bug anymore.
[Nexus 4 Original Android Development] gregorypeg1000:
Does anyone have problem with the touchwake in call?I have set the option "disable touchwake in call" in semaphore manager but it doesnt work.So when i touch the screen with my ear it wakes and then it starts on going on and off and on again every second.
[Nexus 4 Original Android Development] paolocorpo:
is the last version 1.8.7 for N4 good for KOT49H 4.4.2 android ??

Many thanks

Paolo
[Nexus 4 Original Android Development] karanrajpal14:
Yes it's working very well. Using it as we speak. Loving it too!
[Nexus 4 Original Android Development] paolocorpo:
can you suggest me the main setting in order to have a smaller drenage of battery ??

i have rom stock recovery root and at moment kernel franco #199
[Nexus 4 Original Android Development] nithin1992:
Yup, same thing happens with me often as well. :( Just hope this can be solved somehow.

Sent from my Nexus 4
[Nexus 4 Original Android Development] karanrajpal14:
I just flashed it today. I thought I'll check how the stock settings work before I tinker. I suggest you do the same.
[Nexus 4 Original Android Development] carlos67:
Ok I've flashed Joliet 1.8.7-2 to get semaphore and faux sound right? But I'm a bit puzzled why I have not got any sound options/settings within semaphore manager :confused:

Also, on the modules page in SM I only have "logger" visible. Where are the other modules like CIFS/TUN etc etc?

Initial impressions of the kernel are very good though. Seems at least as smooth as Matrix which is where I came from before this kernel (after flashing stock 4.4.2 in between of course).

Sorry for posting this in here but I thought that as it's basically semaphore kernel it would be ok.
[Nexus 4 Original Android Development] thracemerin:
Semaphore manager is for Semaphore not Jolie and since Semaphore doesn't support Faux Sound neither does Semaphore Manager, if you want Faux Sound controls you need to use a tuning app that supports it.
[Nexus 4 Original Android Development] carlos67:
Thanks, I apologise for being too hasty in asking. I see it is on the OP :o
[Nexus 4 Original Android Development] jimyiak:
Try trickster..

neXus⁴ running Purity 4.4.2 with semaphore 1.8.7 kernel ?
[Nexus 4 Original Android Development] RealSlimShadyMC:
All those getting random scaling, is the device hot? Is MPDecision enabled? What settings?
[Nexus 4 Original Android Development] snak3ater:
There's no mpdecision in semaphore :)
[Nexus 4 Original Android Development] stratosk:
Semaphore is not compatible with CM any more. You will have some display issues flashing it on CM

Thanks!

SAI:

- you may handle vibration intensity depending on proximity sensor (near or far).

- you may pick up the phone without touching the screen (just put the phone near your ear).

- Option to disable touchwake during calls (in case you use touchwake feature)

Data works fine on stock ROM here. Does purity uses the latest modem?

Touch control app is unrelated with Semaphore kernel.

Please report any issues in the respective thread.

Please try to disable and enable SAI again (this will restart SAI service - maybe this is the cause of the issue).

Please use default settings. Maybe you can set the min online cores to 1 and use less aggressive ondemand touch settings:

touch load: 65

touch load threshold: 15

touch load duration: 900

These modules are built into the kernel in Semaphore for N4.
[Nexus 4 Original Android Development] paolocorpo:
Thanks i will try it using your suggestion

Do you confirm that the last version runs well with 4.2.2 too ??
[Nexus 4 Original Android Development] stratosk:
If you mean 4.4.2, yes. Latest version works fine on 4.4.1 and 4.4.2 (both roms use the same kernel)
[Nexus 4 Original Android Development] rogers11:
I think the first post should be changed:

Versions >= 1.8.5 are for KK 4.4.1/2 only

to avoid those questions.
[Nexus 4 Original Android Development] paolocorpo:
Yes i mean 4.4.2

May i suggest you to reviews the changelog adding this compatibility ??

using the setting suggested i will loose many reactivity of N4 ??
[Nexus 4 Original Android Development] stratosk:
Thanks! done... :)
[Nexus 4 Original Android Development] stratosk:
It depends on your taste. You may try with different settings and check what is the best for your needs.
[Nexus 4 Original Android Development] paolocorpo:
Ok

Installed your kernle and setetd with your suggestions

I will come back after a couple of cycles
[Nexus 4 Original Android Development] ciprianruse88:
[MENTION=3750240]stratosk[/MENTION]

Data connection problem isn't Purity releated.I flashed and used stock factory image for 4 days and same random problem.It might be network problem or kitkat bug.I will flash and use stock kernel for some days to see if the problem is still there and I will let you know my results.
[Nexus 4 Original Android Development] stratosk:
Thanks! Maybe it would be better if someone could try stock rom-kernel.
[Nexus 4 Original Android Development] ciprianruse88:
No problem for me.Tomorrow I will flash again factory image :thumbup:
[Nexus 4 Original Android Development] gregorypeg1000:
Turned touchwake off and then on again and it worked for one call only. after that it behaved like before.it needs to be turned on and off after every call.using purity Rom and the latest semaphore kernel. I will just turn it off completely for now .thanks for the answer strato. :)
[Nexus 4 Original Android Development] twowheeler:
And just ask if you have any questions. This thread is very helpful though, so you will probably find the answer if you search through this thread.

I copied the values stratosk gave you btw. Always fun to see what it does.
[Nexus 4 Original Android Development] KSLevel11:
[MENTION=3750240]stratosk[/MENTION]

Does default color/gamma settings in Semaphore App, are the same as in stock kernel?
[Nexus 4 Original Android Development] Kocai:
It's the same. Stratosk doesn't change anything.
[Nexus 4 Original Android Development] karanrajpal14:
Thanks! I've been facing excessive battery draining lately. Yesterday I was on 28 percent and I was browsing techcrunch through chrome. Suddenly the battery started dropping rapidly. In 1 minute it went down to 26. I thought it was fine since the site has many images. But then again after a minute it went down to 20 and the phone started heating up. Then after almost another minute the phone went down to about 12 and it was really hot. In about 5 minutes the battery dropped by almost 15 percent which I'm sure isn't normal. I turned off Wi-Fi and let the phone cool down for a bit and then put it to charge. Any ideas on what's wrong?
[Nexus 4 Original Android Development] carlos67:
Sleeping like a baby but massive drain.

I'm experiencing a bizzare battery draining issue with this kernel and also Matrix kernel and Purity Rom.

Last night my phone was charged to 99% and I left it with 3g on and wifi off. I also reset CPU spy counters. 10 hours later I wake my phone and the battery has dropped to 66%:eek: however, CPU spy shows that the phone was in deep sleep for 97% of the 10 hours.

I'm baffled, how can the battery drain by 33% in 10 hours when the phone was in deep sleep for 97% of the time??

Can anyone suggest any possible explanations. Like I say, it has now happened on Semaphore 1.8.7 and Matrix v12 both with Purity. All location/GPS disabled. No such drain is happening when on wifi.

My only idea is the radio - it happened while I was on 98 radio so I have changed to 84 radio to see if it still happens.
[Nexus 4 Original Android Development] Arju:
Could you possibly go into your battery option or install better battery stats and check what's causing the drain? might be an app. Anyway, I hope you could give some feedback after you change your radio. Woukd be nice to know if it worked out for you.
[Nexus 4 Original Android Development] apatal:
I wish you took a screenshot of your battery stats. That way, we can see if something keeps waking up your phone. In general, 3G mobile data connection drains a helluva lot more juice than wifi, and if you have a rogue app that keeps updating in the background even when not in use (I'm looking at you, social networking apps), that will explain the battery drain. Have you only experienced this with Semaphore? Have you tried sleeping with the same setup (3G on) and stock kernel? Try it and see how the drain is like. My bet is it would be more or less the same. I think apps are the reason for this, not the kernel.
[Nexus 4 Original Android Development] Holer Togni:
I don't think any app is causing this because your phone was on deep sleep almost all the time. Reasons might be a bad radio signal (constantly switching between 2g/3g, losing signal all time), radio drivers not working well with your setup (try other versions) or even a dying battery.
[Nexus 4 Original Android Development] hachoo:
My advice would be to clean wipe everything if you're coming from a different kernel. In my experience, coming from trinity/matrix/bricked, 'dirty' flash doesn't work well.

I'm experiencing really great speeds with nice undervolts (-100mV) and great battery life. Haven't had such since the 4.2 era. (On Purity ROM)
[Nexus 4 Original Android Development] :
No wipe. Flash Rom, flash kernel.
[Nexus 4 Original Android Development] hachoo:
Jah, sorry, that's what I meant. Reading around these forums, lots of people are not re-flashing to 'stock' and just flashing between kernels, causing these problems.
[Nexus 4 Original Android Development] alcurtis93:
Any kernels version compatible with cm11
[Nexus 4 Original Android Development] elwilson4:
No. They changed to CAF.
[Nexus 4 Original Android Development] themike10452:
too bad CM doesn't support semaphore anymore :P ;)

Sent using my nexus⁴ running Purity ROM 4.4.2 (Dalvik) powered by matr1x v12 Linux 3.4.0 kernel.
[Nexus 4 Original Android Development] twowheeler:
Is the hotplug only active when the screen is on? If it is, does this means that there's only one core online when playing music with the screen off?
[Nexus 4 Original Android Development] themike10452:
If I'm not wrong only 1 core is active during screen off time.

Sent using my nexus⁴ running Purity ROM 4.4.2 (Dalvik) powered by matr1x v12 Linux 3.4.0 kernel.

????????
[Nexus 4 Original Android Development] stratosk:
When the screen goes off, min online core is set to 1.

The hotplug driver is active and it's able to put online more CPUs if it's needed.

When the screen is on again, the min online core is set back to user's selection.
[Nexus 4 Original Android Development] ihancioglu:
Hi [MENTION=3750240]stratosk[/MENTION],

What do you think about this approach?

http://lwn.net/Articles/480055/

Hopefully will get more performance on Semaphore..
[Nexus 4 Original Android Development] thracemerin:
From the article:

Leads me to believe its already in android kernels after 4.0.
[Nexus 4 Original Android Development] ihancioglu:
I am not a developer , just think that Nexus 4 is Qualcomm device and uses PMEM method and will be performance gain If switch to pure ION. Best answer is with [MENTION=3750240]stratosk[/MENTION].

If not in case just forget it :)
[Nexus 4 Original Android Development] stratosk:
Reading kernel configuration, it seems that we currently use both methods.

Though, I don't know details (where each method is used?)

And of course, it's not a piece of cake (at least for me) to do a change like that. :)
[Nexus 4 Original Android Development] Mercado_Negro:
[MENTION=3750240]stratosk[/MENTION]

I think we discussed this a couple of months ago but I can't find it.

I can't seem to make Catlog work at all. In fact, neither using terminal emulator.

Coming from stock SlimKat.
[Nexus 4 Original Android Development] ihancioglu:
You can take a look his repo as he already switched to pure ION.

Hopefully helps.

http://xdaforums.com/showthread.php?t=2485368
[Nexus 4 Original Android Development] Italico:
I'm on SlimKat Beta 1.7 with Semaphore (Jolie) 1.8.7

It seems to me that it cant'handle UV as well as before, don't know if it is because of the ROM or the kernet though...

It sometimes reboots by itself, or it reboots just after switching it on with the power button. Seems soft reboots, it goes back only to the boot animation and carry on from that, not powering completly off.

I'm on a faster binned CPU, -150mV UV from 384MHz to 1,35MHz, Deadline scheduler, Westwood TCP Algorhythm

Before (SlimKAt Betas until 1.6 and Semaphore 1.8.5) it was doing good with -162,5mV UV, No-Op scheduler, CuBIC Algorhythm

[added]

Sometimes, also, when waking it up I can see not only the unlock dots to swipe my pattern, but also the security countdown, like if I tried before to unsuccesfully lock the device

Wonder if someone has similar problems
[Nexus 4 Original Android Development] stratosk:
What do you mean 'before'?

Do you still have issues without UV?

Please try to post your question to the right thread.
[Nexus 4 Original Android Development] Italico:
Thank You for the fast answer, Stratosk.

'Before' is referring to the previous installed combo, Semaphore N4 1.8.5 on SlimKat Beta 1.6. It was great, gave me a record battery life with pretty low and also stable UV at -162,5mV.

Now I lowered the UV values, I'm at -137,5mV at the moment. Everything seems ok, I'll see how it goes and post after some use.

I linked my post into the SlimKat N4 section, too

Thank You for Your support
[Nexus 4 Original Android Development] Italico:
Seems ok with the reduced UV.

At the moment I'm back to -150mV but on the 'stock' Semaphore, not Jolie, and it is stable. I'll see how it goes
[Nexus 4 Original Android Development] ihancioglu:
Hi everybody,

I have one off-topic question,

I just switched ART runtime but all .odex files and /dalvik-cache/*.dex files are in place and not translated .oat files. Is this normal behavior? As I read from documents all of the .dex files should translate to .oat files.

Sorry it is not Semaphore related but most responsible people in here :)
[Nexus 4 Original Android Development] Giox96:
I changed some of the values ​​of the colors of the screen, but I notice that a few times on the white becomes less and sometimes more intense. Why?
[Nexus 4 Original Android Development] fajarlazuarding:
Try to change according to the available presets out there, i believe someone has posted before :)
[Nexus 4 Original Android Development] Barbatos19:
Try this. Obsanity amoled, credits to the one who discover it
[Nexus 4 Original Android Development] Sir_gpm:
Using this lovely kernel. From time to time tap2wake does not work, using slimrom 4.3, since uptaded the manager.

Enviado desde mi Nexus 4 usando Tapatalk 4
[Nexus 4 Original Android Development] autoradio78:
Tap to wake work for few second after you lock your device..

If you want wake your phone you must download app as touch control for wake it with slide screen, double tap etc..

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 Original Android Development] JaqaL06:
is this kernel have a incoming call lag like franco kernel? if anybody confirm it would be perfect :)
[Nexus 4 Original Android Development] xda_emanuel:
Nope, this kernel is perfect, best combination for battery and performance. Im using it combined with purity :)
[Nexus 4 Original Android Development] Barbatos19:
Here I go again. While I'm on 1.8.5 I charged my phone for 3hrs only and after updating to 1.8.7 max of 5hrs per charge
[Nexus 4 Original Android Development] apatal:
Hi guys, has anyone experienced using 1.8.7 and having your 2nd core (core 1) stuck at maximum frequency (1512 MHz)? I observed this while using PerfMon by Chainfire and confirmed it with the Info tab in Trickster? The thing is I wanted to use the kernel as is and hadn't messed around with it until I saw the behavior using PerfMon.
[Nexus 4 Original Android Development] yarisd4dturbo:
Yes, for me the solution is to switch off the overvolt in trickster option ;)

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 Original Android Development] droid_legacy:
overvolt means boost-voltages in semaphore app?
[Nexus 4 Original Android Development] lalo20:
S

For me too. Just switch to interactive and then to ondemand.

Enviado desde mi Nexus 4 mediante Tapatalk
[Nexus 4 Original Android Development] droid_legacy:
+1 confirmed. Second CPU stuck at 1,5 GHz. After changing governor to interactive and back to ondemand, problem is solved.

Sempahore 1.8.7, Purity (latest), clean install, Sempahore App, :D
[Nexus 4 Original Android Development] TheNerd:]:
Thanks guys no wonder my phone was getting so hot
[Nexus 4 Original Android Development] paolocorpo:
Hi

I tried your kernel 4 days using tyhe above setting on my N4 4.4.2 rom stock

All is ok but ... i have not a bigger life of battery: it is always the same

have you others suggestions for me ?
[Nexus 4 Original Android Development] RealSlimShadyMC:
What apps do you use? Stock play apps, Facebook, viber e.t.c are really bad for battery life.
[Nexus 4 Original Android Development] ihancioglu:
Hi [MENTION=3750240]stratosk[/MENTION],

Second core is stuck 1.5Ghz If Semaphore manager is not installed.

I tried to flash stock kernel and Semaphore 1.8.7 again for double check. No change.

Switch between interactive and ondemand on Semaphore app solves the issue, but stuck again 1.5Ghz as soon as uninstall the Semaphore manager and reboot.
[Nexus 4 Original Android Development] ciprianruse88:
I have 76h up time without reboot and still didn't experienced this issue.Might be an app on your side or location or sync.
[Nexus 4 Original Android Development] alen1901:
I am using trickster and no core is stuck at 1.5ghz. All good.

Sent from Pure Nexus⁴
[Nexus 4 Original Android Development] ihancioglu:
I don't even use trickstermod. Just Semaphore kernel.

---------- Post added at 12:47 AM ---------- Previous post was at 12:45 AM ----------

No problem with stock my friend. I don't think the issue app or sync related..

So If anyone want to test exactly the same scenario, please uninstall Semaphore manager , trickster and clean flash Semaphore kernel and reboot.
[Nexus 4 Original Android Development] ciprianruse88:
The kernel is meant to run aside with semaphore manager.Why should anyone use a custom kernel without a kernel control app?
[Nexus 4 Original Android Development] clockworkstop:
Well, if you use PSK you don't need it...

Sent speedily from my scurrying Nexus 4
[Nexus 4 Original Android Development] ciprianruse88:
Semaphore manager is recommended by the OP.
[Nexus 4 Original Android Development] thracemerin:
Ok, clearly the issue isn't happening to everyone and there is no point in arguing about whether it's a bug or something else. What would be worthwhile is for those who are experiencing the issue to do what they should have done in the first place and provide logcats and dmesg for stratosk to look at so that he can see what's causing the issue in case it isn't happening to him.
[Nexus 4 Original Android Development] apatal:
Because sometimes I'd like to use a kernel as is, as the developer wants it, after all, he already made it so that the default settings are the perfect balance between battery life and performance. :)
[Nexus 4 Original Android Development] ciprianruse88:
I am using as it is...I am using semaphore manager just to keep track on things and change gamma settings because stock gamma is super ugly :).Oh...and btw...the developer made a kernel control app for his kernel to play with it for your best settings(UV,gamma and stuff)...The developer releases the kernel with the most stable settings for everyone...Remember : not all devices are the same...even stratosk playes with UV from what I seen and he doesn't releases the kernel with his UV settings. ;)
[Nexus 4 Original Android Development] apatal:
I understand...and I don't begrudge you that option. I'm just stating what I experienced using it: flashed the kernel, used it as is, no kernel app installed (so I know it wasn't caused by any apps), decided to open PerfMon one day and saw core 1 stuck at 1512 MHz. (By the way. I observed the same thing with Jolie kernel, which was built from Semaphore source. ) I'm saying this not to just put down the kernel. I like Semaphore and have nothing but respect for stratosk. Just stating my observation as an aid to development. :)
[Nexus 4 Original Android Development] ciprianruse88:
As thracemerin said, please provide logs. Thanks a lot ! :thumbup:
[Nexus 4 Original Android Development] apatal:
Good idea. Logs coming soon. :)
[Nexus 4 Original Android Development] ihancioglu:
May be they are pleased with default values and there is no need to change anything. I just realized that bests are the default and IMHO under volt causes some instabilities for me. Everybody is free to use kernel control app or not.

That's the point, it is not required , just recommended for control anything.

I will provide logs in a few minutes...

EDIT : Here is the last_kmsg.
[Nexus 4 Original Android Development] stratosk:
Thanks for logs but I don't think last_kmsg will help.

My guess is that an app is set max_scaling_freq to max.

I'm on stock ROM and I've never faced this issue (205 hours uptime).

Can you please confirm the following after this happens (using terminal emulator)?

su

cat /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq

ls -l /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq

cat /sys/module/dyn_hotplug/parameters/enabled

cat /sys/module/dyn_hotplug/parameters/min_online

cat /sys/module/dyn_hotplug/parameters/max_online

ps | grep mpd

Also, do you use stock ROM?
[Nexus 4 Original Android Development] ciprianruse88:
I don't thinks it's rom releated.I have 87h up time with Purity and the kernel works perfectly.My guess is that there is an app messing with the kernel.
[Nexus 4 Original Android Development] wozn:
my input

Mine also has the issue with the maxed out core. Purity ROM + Tickster setup.
[Nexus 4 Original Android Development] ciprianruse88:
Try semaphore manager instead of trickster.

---------- Post added at 11:43 AM ---------- Previous post was at 11:40 AM ----------

Install semaphore manager and change the lcd calibration settings to the ones from the screenshot...maybe after you see the changes you will understand my point and the point of a custom kernel :)

---------- Post added at 12:35 PM ---------- Previous post was at 11:43 AM ----------

[MENTION=3750240]stratosk[/MENTION]

I think I found how to reproduce the issue with core stock at max freq. I have unistalled semaphore manager,dirty flashed rom+kernel and after reboot I saw the issue.Then I installed semaphore manager,opened it,rebooted and the issue is fixed.Maybe this can help.
[Nexus 4 Original Android Development] thracemerin:
last_kmsg is only really useful after an unexpected reboot or hard freeze, logcat and dmesg (see !y signature for a link on how to get logs) would be much more useful in this situation, you should also get the information requested by stratosk. This goes for everyone with the issue, '+1' or 'me too' posts are diagnostically useless when looking for bugs.
[Nexus 4 Original Android Development] Tylog:
You need no numbers, you need the app rom tool box, I will post a short how to when at home, to much text with the phone :) in two hours I post it :)

Tapatalk
[Nexus 4 Original Android Development] TheeWolf:
BM? Do you mean a big memory version like there was for the i9000?