yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] dsmpampis:
I just flashed Semaphore! So far so good!

But I have one issue. How I can change the colours settings? For example on LCD calibration they are 9 different values for gama controls and not 7! (gray, mids, blacks, whites, contrast, brightness, saturation).

And how can I untervolt all steps by-125mv?

Thanks in advance!

Tapatalked with my ΝΕΞΟΥΣ⁴ powered by ParanoidAndroid 3+
[Nexus 4 Original Android Development] snak3ater:
Yes there are 2 extra values in semaphore.. Search franco to semaphore spread sheet in general forum..you'll find it there.. you will find it from this thread as well..

There you go...

http://xdaforums.com/showthread.php?p=41461508
[Nexus 4 Original Android Development] stratosk:
New version 1.5.6

- Linux kernel 3.4.60

- Rework touchwake code for compatibility with TouchControl (thanks [MENTION=2538253]bponury[/MENTION])

- mach-msm: board-mako-display: Use default values for LCD color temperature (should fix stock issue with 'fastboot boot' command. Thanks [MENTION=894259]mskip[/MENTION] for reporting)

- mach-msm: subsystem_restart: Fix CPU detection (should fix issue that the subsystem_restart could not detect the CPU and panic_handler could not restart susbystems properly)

At the moment only available on www.semaphore.gr due to issues in XDA devdb.

CM compatibility under development. I hope I will have something shortly.
[Nexus 4 Original Android Development] stratosk:
Hi [MENTION=2538253]bponury[/MENTION]

Final code is here: https://github.com/stratosk/kernel_msm/commit/2bc75c0a586113935fb28c621ff05c0f1254ee4d

I worked it a little bit more but the logic is more or less the same.

I hope it's OK now.
[Nexus 4 Original Android Development] gialakias:
This could help also http://xdaforums.com/showthread.php?p=44919049
[Nexus 4 Original Android Development] elderap:
Just installed version 1.56 and was unsigned

Enviado de meu Nexus 4 usando Tapatalk 4

---------- Post added at 06:35 PM ---------- Previous post was at 06:22 PM ----------

what can is wrong ?

Enviado de meu Nexus 4 usando Tapatalk 4

---------- Post added at 06:36 PM ---------- Previous post was at 06:35 PM ----------

Complementing slim bean beta 3

Enviado de meu Nexus 4 usando Tapatalk 4
[Nexus 4 Original Android Development] dahi:
+1

CM10.2 not baseband stratosk.

Nexus 4 cihazımdan Tapatalk 4 ile gönderildi
[Nexus 4 Original Android Development] "D":
[MENTION=3750240]stratosk[/MENTION]

Perfect my Friend

best regards
[Nexus 4 Original Android Development] bponury:
[MENTION=3750240]stratosk[/MENTION]: TC is not working with latest build (module loads fine but something else is going on). I tried compiling your kernel but I always get into bootloop.

I tried using gcc 4.6 and 4.8 from latest ndk and always bootlooping. Any ideas/solutions? I pulled config from /proc/config.gz
[Nexus 4 Original Android Development] reginickneo:
Hi all!

Sorry for not reading the last pages. I had been using Semaphore kernel since the beginning, but I didn't find it good under 4.3.

I reverted to 4.2.2 but I gave a new try to 4.3, I'm using crDroid ROM which I think is great.

With default CM kernel I feel that it drain more battery than in 4.2.2. I tried Semaphore (1.5.3 version if i remember corretly) but wasn't so good in battery life either.

My question is, how the new version performs? I'm goint to go to college next week, so I need a reliable device with great battery life (sometimes I will share data connection to my iPad).

Thank you in advance, sorry for writing so long, and my English isn't perfekt.

:cyclops:

edit: I love the dev and the great kernel so I didn't look around for faux kernel or so.
[Nexus 4 Original Android Development] snak3ater:
The default settings would give you the best performance.Buttery smooth ui. If you want to have better battery life,then you have to tweak the settings a little.There are so many softwares for that purpose..semaphore manager,trickster etc..

PS:I don't think so that there is any difference between the semaphore of 4.2 & 4.3..Battery life is the same
[Nexus 4 Original Android Development] stratosk:
I use gcc 4.7.

make semaphore_mako_defconfig

to get Semaphore's default config (you need to change of course initramfs path or build with your own initramfs).

Any logs?
[Nexus 4 Original Android Development] capoooro:
For me a major issue with 1.5.6.... Perhaps connected to the change of code for touch control. I cannot end a call... Perfect with 1.5.5 and 1.5.3.. I'm on paraNoid

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Original Android Development] stratosk:
I confirm the issue.

Please turn off the option 'touchwake disable' in Semaphore Manager-> SAI tab, as workaround.

This is definitely related to the latest changes for touchwake.

I'm sorry for the inconvenience. I will try to resolve the issue or revert the changes tonight.
[Nexus 4 Original Android Development] blade_:
Strato, thanks for this kernel.. I hope battery will be OK..

I see in 1st page only link for 1.5.1..not for 1.5
[Nexus 4 Original Android Development] hotnikkelz:
Is touch wake really worth all this hullabaloo lol, just curious :)
[Nexus 4 Original Android Development] spirosbond:
Hi there. New user here! I have just flashed your kernel on PSX 4.1 (4.3 JSS) nad it looks good so far. I confirm that the problem is fixed after turning off "touchwake disable".

One thing I noticed while looking logs is the "powerHAL permission denied error" when touching the screen. Every kernel which doesn't has Qualcomm's MP-decision has this error. It is said that it reduces smoothness, so is there any possibility of adding it or fixing this issue somehow?

Cheers!

EDIT:

I would also like touchwake to be on permanently if that's possible...
[Nexus 4 Original Android Development] :
I just wanted to say hello [MENTION=3750240]stratosk[/MENTION] from lesvos, before I leave this beautiful island. :)
[Nexus 4 Original Android Development] Marcb:
Hello [MENTION=3750240]stratosk[/MENTION]

I had a bug with version 1.5.5 that I don't know yet if 1.5.6 solved this, but when using your kernel, the "Android OS" would be the number 1 culprit for battery sucking.... Using stock and Franco's kernel did not trigger this issue... I'm using stock 4.3 ROM in all these tests... Do you need more details, or can I help in any other way?

Thanks!
[Nexus 4 Original Android Development] stratosk:
You can use 'Download section' (visible from browser) or find the links in semaphore.gr

What exactly do you mean?

Thanks for your feedback!

About PowerHAL: I don't think that this message causes a regressino to performance.

But in my plans to find a solution.

About touchwake: if it's always on your device will never go to suspend (battery drain)
[Nexus 4 Original Android Development] hotnikkelz:
[MENTION=3750240]stratosk[/MENTION] the amount of effort you are putting out in order to get it to work. Was wondering if all that effort is worth it for such a feature
[Nexus 4 Original Android Development] spirosbond:
Thanks. If I set touch wake delay to 0 with semaphore manager that means "max" ?

EDIT: Yes 0 means max. I just tested it.
[Nexus 4 Original Android Development] alexoz:
Well, touchwake is working fine as it is, the effort is to make this kernel compatible with touch control. As for whether it is worth it, I think it would be really nice to have the option to disable touchwake and use touch control, so please strato, keep working on it :)
[Nexus 4 Original Android Development] alktlr:
I'm on stock JWR66Y rooted with 1.5.6 non j version, but seeing tearing. Can anyone else confirm that or is it just me?
[Nexus 4 Original Android Development] stratosk:
I like touchwake and I use it.

As alexoz mentioned, touchwake was working fine with no issues.

The last issue came up trying to resolve conflicts with touch control.

If I can't resolve it I simply reverse the changes and get back a fully working touchwake
[Nexus 4 Original Android Development] stratosk:
Hello,

could you please check for wakelocks?
[Nexus 4 Original Android Development] stratosk:
0 is an invalid value (yes, I should fix it in Semaphore Manager).

Kernel simply does not accept 0 value, and the delay remains in the old one.
[Nexus 4 Original Android Development] jolas:
If it is not possible to resolve those issues, is it possible to make a version without touch wake (for those who wants to use touch control instead) or there is no way to remove it, as it is a core part of kernel?

Sent from my Nexus 4
[Nexus 4 Original Android Development] franciscofranco:
Hi [MENTION=3750240]stratosk[/MENTION]. This https://github.com/stratosk/kernel_msm/commit/18b475c5903fb401c85e82ea1337430fb994fbef is for fastboot boot boot.img did I understand correctly?
[Nexus 4 Original Android Development] snak3ater:
Have you tried Touch Control :confused:
[Nexus 4 Original Android Development] stratosk:
Hi [MENTION=3292224]franciscofranco[/MENTION]

Yes, that's correct.

It seems there is a missing command line parameter (lge.kcal=0|0|0|x), when you 'fastboot boot'.

Alternatively (if you don't use kcal default values) you may boot using:

fastboot -c "console=ttyHSL0,115200,n8 androidboot.hardware=mako lge.kcal=0|0|0|x" boot boot.img
[Nexus 4 Original Android Development] stratosk:
I'm sorry, I don't want to maintain 2 versions (actually 4) for with and without touchwake.
[Nexus 4 Original Android Development] Midomad:
Stratos you're kernel is good i don't need touch control touch wake is all i need!

Envoyé depuis mon Nexus 4 avec Tapatalk
[Nexus 4 Original Android Development] blade_:
semaphore killing by itself apps?in past every time i delete apps from currents,and i have to reopen an app after some minutes,it takes 1-2 sec to load..now seems to take much longer..p.e.,facebook ,starts from the facebook logo
[Nexus 4 Original Android Development] capoooro:
Please revert it back.... also I use it a lot. By the way I've tried Franco and faux but I think that you work on this kernel is really good. I would try to build it for grouper if I find the time and...the knowledge :D

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Original Android Development] stratosk:
Low memory killer driver (Android) will kill apps when there is no more available memory.

Do you have this issue only in Semaphore? Which version?
[Nexus 4 Original Android Development] uchihakurtz:
Silly question but, what's the difference between touchwake and touchcontrol in functionality? And what's the delay time for on touchwake? Thanks in advance.

A little suggestion since there aren't any mod yet, it'd be nice to have the double tap to wake and sleep like the LG G2.

But nonetheless, a great kernel for 4.3, more options than the kernels I've tried since far. Thanks very much dev. :thumbup: :thumbup:

Sent from my blazing fast Nexus 4
[Nexus 4 Original Android Development] snak3ater:
Touch wake feature is there in Touch Control App..You can use it once it gets fully functional with Semaphore..
[Nexus 4 Original Android Development] bponury:
[MENTION=3750240]stratosk[/MENTION]

I this is a fix for touchwake to not ignore touchscreen input (this fixes TouchControl)

diff --git a/drivers/input/touchscreen/lge_touch_core.c b/drivers/input/touchscreen/lge_touch_core.c
index 2fc1380..fc337c8 100644
--- a/drivers/input/touchscreen/lge_touch_core.c
+++ b/drivers/input/touchscreen/lge_touch_core.c
@@ -837,9 +837,9 @@ static void touch_work_func(struct work_struct *work)
if (likely(ts->pdata->role->operation_mode == INTERRUPT_MODE))
int_pin = gpio_get_value(ts->pdata->int_pin);

-#ifdef CONFIG_TOUCH_WAKE
- if (unlikely(!suspending && device_is_suspended())) {
- touch_press();
+#ifdef CONFIG_TOUCH_WAKE
+ if (unlikely(touchwake_is_enabled() && !suspending && device_is_suspended())) {
+ touch_press();
goto out;
}
#endif

Speaking of unable to hangup a call I can't reproduce it in any way so I can't help unless someone tell me how can I test this?
[Nexus 4 Original Android Development] stratosk:
New version 1.5.7

- Revert touchwake changes introduced in 1.5.6 (fixes issues after phone calls)
[Nexus 4 Original Android Development] stratosk:
Hi [MENTION=2538253]bponury[/MENTION],

At the moment, I just reverted changes that caused issue.

I tested both mine and yours version with same results.

You need to enabled touchwake disable in Semaphore Manager (SAI tab).

Do I have to use this patch only? Or I have to apply it over the previous one?
[Nexus 4 Original Android Development] blade_:
yes only in semaphore,but to be honest is the only custom kernel i used,except the stock of paranoid(which is stock as i know)
[Nexus 4 Original Android Development] stratosk:
Touchwake, keeps your phone awake for 'delay' time after the screen goes off due to inactivity. In this 'delay' period you may touch the screen

and your screen will switch on again. After 'delay' or if you use power button, your phone will suspend normally.

TouchControl, keeps touch always powered so you may turn it on swiping the screen.

It is normal behavior if you have many applications running. Eventually you will run our of RAM and the kernel will kill some apps.

But if it is happening without many apps opened, it's an issue.
[Nexus 4 Original Android Development] bponury:
You need to apply over the previous one. I'll take a look on how to quickfix that call issue
[Nexus 4 Original Android Development] Kindatired:
I have been having the same problem. I ran better battery stats for a day and had about 40 mins worth of kernel wakelocks from powermanagerservices.wakelock.

Going to do a fresh install of stock ROM and your kernel and run for another day. Won't install any apps and see what if it's still there.
[Nexus 4 Original Android Development] thracemerin:
Power Manager wakelock is the wakelock held by the kernel when apps are keeping the device awake.
[Nexus 4 Original Android Development] stratosk:
OK thanks.

The problem is that Semaphore Manager disables touchwake during calls.

After call ends, the screen goes on, and touch remains unpowered.
[Nexus 4 Original Android Development] Kindatired:
I know, and that's the weird thing. The only wakelocks I have are from media player, yet Android OS is still draining the battery way faster than it should. While I was asleep (6 hours) Android OS showed it had used 30% of the totally battery used during those 6 hours. Phone idle which was always the biggest drain during sleep showed 13% of total battery used. Whatever it is doesn't seem to show as a wakelock.
[Nexus 4 Original Android Development] blade_:
im sorry but i dont think its a normal behavior because i tested it with only facebook in recent apps...btw im not sure if its facebook problem because i updated today,the same time i installed your kernel strato:confused:
[Nexus 4 Original Android Development] bponury:
[MENTION=3750240]stratosk[/MENTION]

I'm attaching a complete patch that works on your latest kernel from repo (1.5.7)

View attachment 2223953

Here you will find just the fix for touchscreen not being responsive you can re-revert (re-add?) the commit you reverted and apply just this small patch instead:

diff --git a/drivers/input/touchscreen/lge_touch_core.c b/drivers/input/touchscreen/lge_touch_core.c
index 2fc1380..fc337c8 100644
--- a/drivers/input/touchscreen/lge_touch_core.c
+++ b/drivers/input/touchscreen/lge_touch_core.c
@@ -837,9 +837,9 @@ static void touch_work_func(struct work_struct *work)
if (likely(ts->pdata->role->operation_mode == INTERRUPT_MODE))
int_pin = gpio_get_value(ts->pdata->int_pin);

-#ifdef CONFIG_TOUCH_WAKE
-	if (unlikely(!suspending && device_is_suspended())) {
- touch_press();
+#ifdef CONFIG_TOUCH_WAKE
+	if (unlikely(touchwake_is_enabled() && !suspending && device_is_suspended())) {
+	touch_press();
goto out;
}
#endif
diff --git a/drivers/misc/touch_wake.c b/drivers/misc/touch_wake.c
index 86d7cd0..b234de6 100644
--- a/drivers/misc/touch_wake.c
+++ b/drivers/misc/touch_wake.c
@@ -74,8 +74,10 @@ EXPORT_SYMBOL(touchwake_is_enabled);

static void touchwake_early_suspend(struct early_suspend *h)
{
-	if (!touchwake_enabled)
+	if (!touchwake_enabled) {
+	touch_disabled = true;
goto out;
+	}

if (timed_out) {
wake_lock(&touchwake_wake_lock);
@@ -91,8 +93,10 @@ out:

static void touchwake_late_resume(struct early_suspend *h)
{
-	if (!touchwake_enabled)
+	if (!touchwake_enabled) {
+	touch_disabled = false;
goto out;
+	}

cancel_delayed_work(&touchoff_work);
flush_scheduled_work();
[Nexus 4 Original Android Development] stratosk:
I will test (thoroughly:) ) the patch tomorrow. If everything's OK I will re-add the changes in next version.

Thanks!
[Nexus 4 Original Android Development] Mercado_Negro:
It's really nice to see two developers with different agendas working together. That's what makes a great community. Thank you both!
[Nexus 4 Original Android Development] pnut22r:
^^ I am looking forward to this. I've always liked both
[Nexus 4 Original Android Development] snak3ater:
It would be better if some test versions are given out before going for the final changes. this way it won't cause any inconvenience for other users.I am always ready to test it out..

Ps: Glad to see that things are finally working out..it's great to watch 2 devs working together like that..thanks a lot
[Nexus 4 Original Android Development] BLADESMAN1889:
Don't beat about the bush ;)

Sent from NEXUS⁴ via XDA Prem [AOKP//Nightlies]​
[Nexus 4 Original Android Development] stratosk:
I do it sometimes when I feel that something may go wrong or if I make important changes.

It was my mistake that I didn't do it last time.

EDIT: Below a test version, with touchwake changes back and the last patch from bponury
[Nexus 4 Original Android Development] eksasol:
I'm going to buy a Nexus 4 and the fact Semaphore kernel is available for this device makes me very happy, since I'm used to using it on my previous Vibrant and Captivate.
[Nexus 4 Original Android Development] haasgo:
Jss or jwr or universal?
[Nexus 4 Original Android Development] gianton:
v0.4.0 installed and booted fine on CM-10.1, looks very smooth so far will test it for battery life. Thanks Strato for your work!

Uninstall trickster mod app and your CPU will idle at 384MHz or get the donate version and set your CPU freqs at 384/1512MHz.

All cores do get online when its needed, check the screenshots attached.
[Nexus 4 Original Android Development] ctfrommn:
LCD Calibration in the stock kernel is only for the RGB settings which does little to correct the terrible gamma LG/Google settled on. I think what users (including myself) are hoping for is including the ability to tweak gamma (either Franco's or Faux's method). The gamma variables need to be exposed at the kernel level so the end user can manipulate them.
[Nexus 4 Original Android Development] pitjago74:
Stratosk...no words...amazing....:eek::D:D

Enviado desde mi Nexus 4 usando Tapatalk 2
[Nexus 4 Original Android Development] stratosk:
mpdecision is a proprietary driver, running in user space (not in kernel) and decides how many cpus will be online or offline depending on system load. The minimum freq will be 1026MHz, only when you touch the screen.

You can still change governor or I/O scheduler.

You need more load on you phone to have 3 and 4 cpu active. (Run a CPU demand game for example).

So, lcd RGB calibration is not enough? OK, I'm not an expert in displays.

I will check it again.
[Nexus 4 Original Android Development] jarjar124:
Not really. RGB provides minimal contrast.
[Nexus 4 Original Android Development] matesc:
I agree! Gamma control would be nice. But no matter how you decide, i will use your kernel anyway :D
[Nexus 4 Original Android Development] stratosk:
Anyway, I will check it.

I can't promise anything, though. I would like to double check every feature I will add in Semaphore.
[Nexus 4 Original Android Development] eep2378:
Regarding gamma, if you wanna see the difference between simple RBG cal and more precise gamma adjustment, simply flash franco kenel or moles halfbreed/contrasty kernel. Just so you can see the difference. I would say even a "non-expert" in displays can tell there is a HUGE difference. Like ctfrommn said, the gamma the google/LG settled on is complete and utter rubbish :o
[Nexus 4 Original Android Development] playya:
Agreed although I flashed mart1x kernel you can definitely see the visual difference but like the above poster mentioned either way this is still a solid kernel. The updated version has not caused me any issues as did its predecessor 0.3.1. Updated display choices would only make your kernel even harder to leave... :good:
[Nexus 4 Original Android Development] gianton:
Is UV settings considered to be added in a future build?
[Nexus 4 Original Android Development] stratosk:
Thanks all for your interest.

I'm sorry but I can't promise for any feature at the moment.

After 10 days with my new N4, I just want to be familiar with the device.

Any new feature will not be blindly copied into Semaphore.

So, if you are going to use this kernel, please for your patience.
[Nexus 4 Original Android Development] playya:
thats about how long I have had mine.... I agree with you on that point patience is not a problem and just to clarify on my part I was not suggesting you change or add a thing but merely if you decide too it will be hard to go elsewhere.

Thanks for your work thus far
[Nexus 4 Original Android Development] a g bell:
Please the is not a feature request just maybe something else to look at TCP congestion Westwood would appear to be the best but missing

Thanks:)
[Nexus 4 Original Android Development] pitjago74:
UV?? What for?? That ist our problem.. Touching to many things....Im UV all the kernels....Franco,Faux,Harsh, Air,Matrix,Trinity...all

And with semaphore I get the best performance and battery life since November:D

Enviado desde mi Nexus 4 usando Tapatalk 2
[Nexus 4 Original Android Development] playya:
You right on that! :good:
[Nexus 4 Original Android Development] gianton:
I got a faster binned chip and can run -150mV from stock voltages rock stable. My main goal is that my device is running at least 3c cooler than stock voltages which is great considering I live in a pretty "hot" country.
[Nexus 4 Original Android Development] lsv-1:
I used to love Semaphore Kernel in my SGS1

Welcome!
[Nexus 4 Original Android Development] gianton:
Take your time my friend, I am sure you know better than us to what you want to achieve. I'll stick to your kernel for now and from the little I run it its a pleasure.
[Nexus 4 Original Android Development] pitjago74:
I live en Mallorca and ist ver y "hot"to:D

I UV -150 also....but I mean ist good sometimes no make UV....but of course,everybody does with HeS device whtat they like:D:D:D

Enviado desde mi Nexus 4 usando Tapatalk 2
[Nexus 4 Original Android Development] io53:
0.3 and 0.4 is running very good here :). Haven't seen anyone mention hsic yet so I'll throw it in here. It's a weird wakelock that happens when your on 3g and causes battery drain. I'm not that familiar with the cause of the wakelock but harsh as a bunch of commits that reduces it.
[Nexus 4 Original Android Development] stratosk:
It's for jwr
[Nexus 4 Original Android Development] snak3ater:
I am trying this test version but stuck here.Kernel works fine as usual..It's the TC app which is asking me to select a module but i cant find any module closest to semaphore..:(

No matter what module i select,it wont work
[Nexus 4 Original Android Development] stratosk:
Do you mean touchcontrol module?

I don't build them. I can't help you on this.

With this test version, you may test that touch wake functionality works as expected.
[Nexus 4 Original Android Development] snak3ater:
Yes..Touch wake works fine..No issues with that..But the Touch control App is not working.The module which is required to run touch control App on semaphore kernel is missing.

I have reported it to Bpoury. Now i guess he can do rest of the job..Lets see what he says..