yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] snak3ater:
Edit:Just now Enabled Touch wake & then dialled a call..Then disconnected it myself..No issues in that..

There is another thing which is new to me..It is normal for screen to turn off while on a call & phone held near our ear.But the screen showed up when i touched it just now while on a call.Also while the screen was off,i was able to disconnect the call by hitting the exact same spot where call end button is..

Call ended but the phone app disappeared & i was taken to the lock screen..did unlock & the phone app was there right in front...

Note: (This happens only with touch wake enabled)...Is this a normal thing?

---------- Post added at 06:32 PM ---------- Previous post was at 06:24 PM ----------

Sorry this is the first time i am dialling a call with touch wake enabled..
[Nexus 4 Original Android Development] BLADESMAN1889:
Yes this is a bug but not one of Semaphore kernel, it seems to be happening across multiple Roms - it is thought to be a proximity sensor issue.

Sent from NEXUS⁴ via XDA Prem [AOKP//Nightlies]​
[Nexus 4 Original Android Development] stratosk:
Thanks for testing and your feedback.

Could you please enable 'touchwake disable' option in Semaphore Mamager/ SAI tab? This should disable touchwake during calls and you shouldn't have this issue.
[Nexus 4 Original Android Development] snak3ater:
Yes..Enabled it just now & everything is perfect..No issues.

So the new patch is working fine as it was intended or still got issues :confused:
[Nexus 4 Original Android Development] BLADESMAN1889:
Thankyou for this tip Stratosk - I will feedback the next time I make/receive a call.

This has cropped up several times over different threads & no one has known what was the cause - or fix. :thumbup:

Sent from NEXUS⁴ via XDA Prem [AOKP//Nightlies]​
[Nexus 4 Original Android Development] dsmpampis:
After a few days with Semaphore kernel I have to admit that the kernel is awesome! Is snappiest than the Franco.Kernel (since I have my N4 always had franco.Kernel) but is not so battery friendly. I'm gone stuck with Semaphore!

Only one issue, when I'm powering off or rebooting my phone if I don't unlock it immediately I have to press the power on/off button a lot times because the device is not responding at all! But if I unlock my phone right after the lockscreen is appear I have no issues at all!

Thanks for the great work!

Και όταν ξανά έρθω Θεσσαλονίκη κερνάω καφέ!

Tapatalked with my ΝΕΞΟΥΣ⁴ powered by ParanoidAndroid 3+
[Nexus 4 Original Android Development] stratosk:
It seems that it works OK. But we will see...

Thanks!

Though, I didn't understand your issue.

Do you have this on 1.5.7 or 1.5.8? Is this happening with touchwake enabled or not?

Do you wait for screen to switch off? Do you use PIN lock?

Αν έρθεις Θεσσαλονίκη θα πρέπει εγώ να σε κεράσω καφέ! :)
[Nexus 4 Original Android Development] dsmpampis:
On 1.5.6 and on 1.5.8

I don't use touch wake.

That is happening when the screen is switched off. (booting –> lockscreen –> off)

I don't use PIN lock.

Thanks in advance!

Tapatalked with my ΝΕΞΟΥΣ⁴ powered by ParanoidAndroid 3+
[Nexus 4 Original Android Development] stratosk:
I tried to reproduce it in 1.5.8 (stock ROM) without success.

I tried with PIN lock, slide lock, face unlock, no lock.

I rebooted my phone, waited until screen of and then turned on the phone.
[Nexus 4 Original Android Development] clshack:
it's ok 1.5.3
[Nexus 4 Original Android Development] dsmpampis:
I don't know what is going on!

When the screen is switched off for the first time after booting without unlocking the device, is not responding at all! I have to keep pressing the power off button for a couple of seconds then leave it for 2 seconds and with the second attempt it's coming on!

But, if I unlock the device after the first boot, it's working just fine.

Ok, I can live with that. It was only an observation.

Thanks a lot for the response!

Tapatalked with my ΝΕΞΟΥΣ⁴ powered by ParanoidAndroid 3+
[Nexus 4 Original Android Development] stratosk:
I can think only the different ROM.

Maybe I can investigate a little bit more. Please send me a kmsg and a logcat (enable logger first) after this happens.
[Nexus 4 Original Android Development] dsmpampis:
Maybe it's the Rom. I'm on PA.

Ok, I'll do it.

Tapatalked with my ΝΕΞΟΥΣ⁴ powered by ParanoidAndroid 3+

---------- Post added at 07:21 PM ---------- Previous post was at 06:49 PM ----------

I don't know if that will help...

http://db.tt/qu9E6saH

Tapatalked with my ΝΕΞΟΥΣ⁴ powered by ParanoidAndroid 3+
[Nexus 4 Original Android Development] bponury:
I've uploaded module compiled for Semaphore 1.5.8 and it seems to work just fine :)

Glad that we managed to fix that. [MENTION=3750240]stratosk[/MENTION] if you're interested in stats on how many people ask for this you can see stats here:

http://touchcontrol.paranoid.me/stats.php

(it will show up as soon as it hits some threshold - 64 requests as of now). It also counts requests that didn't succeed (no module found)

Cheers and thanks again :)
[Nexus 4 Original Android Development] artifex21:
Touch control is working great, thanks a ton guys! :)
[Nexus 4 Original Android Development] pnut22r:
I concur. Looking forward to JSS version :)
[Nexus 4 Original Android Development] mendozaram:
I try 1.5.7 jss and lost my network connection. I got to flash my ROM kernel again and it works. Also try FK and works too. Dont know why

Send from my Slimmed N4
[Nexus 4 Original Android Development] snak3ater:
Yes... finally tested tc with 1.5.8... working great without any issues..

Thanks Stratosk
[Nexus 4 Original Android Development] stratosk:
I'm sorry, I can't identify an issue in the log file.

Thanks!

Most probably I will apply the changes back in next version, if everything is OK with testing.
[Nexus 4 Original Android Development] sgw99:
Just my bits of feedback:

Cm 10.2 3108 -> JSS15Q

Should I use the j-version of 1.5.7 or is it non working for cm right now?

I run j right now ... it crashed somehow after first boot, now OK so far.

Edit: seems I have no radio ...
[Nexus 4 Original Android Development] stratosk:
There is a SElinux conflict in CM with Semaphore.

Please for your patience. I try to resolve this.

According to some reports you may put Semaphore boot.img in CM zip and reflash the ROM.
[Nexus 4 Original Android Development] sgw99:
Thanks for your very quick reply ;) I am not in a hurry, thanks ... reflashed CM right now and will just wait for any updates.

Thanks for your ongoing efforts, Stefan
[Nexus 4 Original Android Development] alexoz:
TC working fine with v1.5.8, thank you stratos for taking the time to implement this :)

Sent from my Nexus 4
[Nexus 4 Original Android Development] GreenSGS:
Hi Stratos,

Any chance getting Faux sound patches?

I not into too much customization in sound (Never play music on phone) but this low mic during a call problem is hitting me hard. Everyone complains during call, I speak too low but that's not true.

So may be some mic gain can help.

or may be changes to gain mic volume is enough.

Please correct me if it's not related. I am not the only one to have low volume, calls via headset or voip call (Skype, Rebtel) does not cause problem its loud and clear but GSM call, man..... everyone says speak louder.

Can you please help my friend. I am thinking about selling this phone just because of this issue but it's a birthday gift. Never buy LG...
[Nexus 4 Original Android Development] xatou:
Hello stratos I just flash your last kernel. I use before Franco's. I use these settings for calibration but with semaphore manager are different. What can I do to have the same?

Στάλθηκε από το Nexus 4 μου χρησιμοποιώντας Tapatalk 2
[Nexus 4 Original Android Development] philidor:
[MENTION=3750240]stratosk[/MENTION] I use semaphore with cm10.2 without problem from the start. so there is a way for me to help you understand the problem that some user have reported with CM?

PS SELinux is set by default in permissive mode ... It

only create a log. How it can be the cause of all this problems?

Thanks for all your work

EDITED

Inviato dal mio GT-P3100 con Tapatalk 4
[Nexus 4 Original Android Development] dsmpampis:
You can use this onehttp://db.tt/8of0XIFV, but the you're looking for is not in there....
[Nexus 4 Original Android Development] jolas:
+1000!!!

Ευχαριστώ Στράτο για την εξαίρετη δουλειά σου!
[Nexus 4 Original Android Development] snak3ater:
Go for this arrangement in semaphore manager.This way you can easily set any value you want..

greys, mids, blacks, 1, contrast, brightness, saturation, whites, 1, Red

greys, mids, blacks, 1, contrast, brightness, saturation, whites, 1, Green

greys, mids, blacks, 1, contrast, brightness, saturation, whites, 1, Blue

---------- Post added at 04:31 PM ---------- Previous post was at 04:29 PM ----------

Can't wait to see 1.5.8...Right now i have shifted back to my JWR Nandroid just to test Touch control..

Will go back to my fav JSS rom once new Semaphore shows up :fingers-crossed:
[Nexus 4 Original Android Development] cantevencode:
Just out of interest, which baseband are people with the problems using? Also, did you upgrade to it with a flashable zip or fastboot? Just trying to understand this. I had this problem with .84 baseband and I upgraded to it with a zip file
[Nexus 4 Original Android Development] philidor:
Never problems with CM. I start upgrade to Google stock 4.3 (wipe all data, Via bootloader) root and custom recovery. After flashed CM 10.2 and semaphore (from the first version, this appended some times ago)

Inviato dal mio Nexus 4 con Tapatalk 4
[Nexus 4 Original Android Development] rschueg:
coming from cm10.1 nightlies, flashed cm10.2 with just clearing caches. flashed bootloader and .84 baseband via zip.

with cm, and franco no problems, with semaphre no baseband (unknown) and no gsm network.

N4|CM10.2N|FK
[Nexus 4 Original Android Development] gpvecchi:
Perhaps, that's the problem: I made a full wipe...
[Nexus 4 Original Android Development] stratosk:
Hi,

I promise, I will look into this.

But please for your patience. I have to resolve those SELinux issues and been really busy last week.

I tried Semaphore on CM10.2 and the issue was there.

Then I used SElinux related initramfs files from CM in my initramfs and the issue gone.

I believe that if Semaphore will boot for the first time in CM (and not CM stock kernel) there will be no issue (there are reports for this but I will also try).

I'm not an expert on SELinux, but I also believe the problem is that when kernel boots with SELinux enabled (even in permissive mode) all files are 'labeled' according to configuration files. When you use other kernel, with different initramfs (and different SElinux configuration files), you have conflict.

Last week I decided to work on 'any kernel' installation solution. With 'any kernel' cwm, the installation script gets the initramfs from the existing installation and makes a new boot.img using the old initramfs, with the new zImage (the kernel).

The issue with this logic is that Semaphore uses initramfs to change some stuff (logger, default governor settings, init.d scripts).

So, I modified the 'any kernel' script to 'inject' Semaphore changes in initramfs.

My only problem with this approach is about the old initramfs. User in many cases should flash a 'reset', stock kernel.

And this may cause confusion.
[Nexus 4 Original Android Development] philidor:
Thanks for your answer! Now I have a better understanding of the problem. Very kind of you!

So if you implements the "inject" solution we may need to dirty flash our ROM and after flash semaphore but only the first time. It's correct? For me this can be a good solution to have a 'any kernel' installation solution.

Inviato dal mio Nexus 4 con Tapatalk 4
[Nexus 4 Original Android Development] stratosk:
Yes, that's correct. Or flash the stock kernel and then Semaphore.

Some kernels change some binaries in ROM, so maybe the cleanest way is to dirty flash ROM first.

But I'm really skeptical about this, because of extra overhead to user. :confused:
[Nexus 4 Original Android Development] gpvecchi:
Ops... Bootloop with today's CM10.2 nightly, even if flashed after using stock kernel...
[Nexus 4 Original Android Development] stratosk:
Attached is a test version 1.5.9j

The major change is the update procedure.

The CWM zip works with Koush's any kernel update procedure.

Flashing the zip, the installer will extract the current initramfs, will inject Semaphore's initramfs changes on the fly, repack initramfs and flash the boot partition.

If you flash it on stock ROM, you will get stock's initramfs + Semaphore kernel + Semaphore changes on initramfs.

If you flash it on CM (tested), you will get CM's initramfs + Semaphore kernel + Semaphore changes on initramfs.

So, it's important to remember that you need a clean, bootable kernel (ROM's stock) in your boot partition before you flash this zip.
[Nexus 4 Original Android Development] sgw99:
installs, boots ... works so far ;) thanks
[Nexus 4 Original Android Development] Naa Laa:
[MENTION=3750240]stratosk[/MENTION]

I am having similar issues as reported with 1.5.7j - unknown baseband. I have been using your kernel (all updates) with RBJ (which is very stable and stockish) updates. I had no issues till 1.5.5j using .33/.84 LTE hybrid radio.

Please advise if you think its kernel related as I am still trying to investigate.

Thanks for all your hard work!
[Nexus 4 Original Android Development] jelle2503:
Test version working well. All aboard!

Verstuurd vanaf mijn Nexus 4 met Tapatalk 4
[Nexus 4 Original Android Development] stratosk:
It's the different selinux configuration.

Please flash your ROM's stock kernel and then 1.5.9j.
[Nexus 4 Original Android Development] Anrikus:
Thank [MENTION=3750240]stratosk[/MENTION],

working fine with slimbean 4.3 beta 4 (with the older version I lost my baseband as long as I didn't flashed the kernel directly after the installation of the rom)
[Nexus 4 Original Android Development] philidor:
Tried 1.5.7j with CM last nightly (01/09/13) and have unknown baseband problem. No problems until nightly of 31/08/13.

with semaphore N4 1.5.9j all work again. (dirty) Flashed last CM and after flashed semaphore N4 1.5.9j

Even touch control work well

Great work

(Edited J version)

Inviato dal mio Nexus 4 con Tapatalk 4
[Nexus 4 Original Android Development] snak3ater:
Having unknown baseband issue on latest Rasbeanjelly...Flashed the test kernel 1.5.9j & since then i am not getting any signals..

PS:I did flash the stock Rom kernel first.After that flashed 1.5.9j..
[Nexus 4 Original Android Development] Naa Laa:
Same here. Finally did a clean flash but not flash semaphore kernel yet.
[Nexus 4 Original Android Development] philidor:
Have you (dirty) flashed your ROM before flashing semaphore N4 1.5.9j? The new kernel use a injection system to work. [MENTION=3740016]Naa Laa[/MENTION] in all work with stock kernel try semaphore N4 1.5.9j.

For me all work again

Inviato dal mio Nexus 4 con Tapatalk 4
[Nexus 4 Original Android Development] snak3ater:
Yes..i did dirty flash the Rom before flashing 1.5.9j..

Just now again flashed the Rasbeanjelly Kernel but still got unknown baseband issue :(

What's happening here :(
[Nexus 4 Original Android Development] Naa Laa:
It doesn't work. I did dirty flash without semaphore kernel as well. Probably something changed with RBJ. I restored my backup from 08/17 (RBJ with 1.5.3j) all works good. Then I flashed the latest RBJ without any custom kernel and I loose the baseband. The backup had hybrid radio (. 33/.84).

I did factory image flash (including the latest radio) and then flashed the latest RBJ, everything works fine.

I didn't have issues till I flashed 1.5.7j but when I flashed 1.5 5j over latest RBJ it does not work. Its all strange to me.
[Nexus 4 Original Android Development] philidor:
Edited

probably something change in RBJ if [MENTION=3740016]Naa Laa[/MENTION] dirty flash without semaphore kernel and have problems. I confirm that work with latest CM10.2 nightly.

We have to find if someone with RBJ ROM manage to use semaphore kernel.

CM10.2 + SEMAPHORE N4 1.5.9J OK

[MENTION=3740016]Naa Laa[/MENTION] Now that you have all stock and worming can you tried Semaphore N4 1.5.9j.?

The are big chance in 1.5.9j
[Nexus 4 Original Android Development] stratosk:
Exactly.

The test procedure should be:

On fully working ROM with stock kernel (whatever is the stock kernel of the specific ROM), we flash 1.5.9j.
[Nexus 4 Original Android Development] philidor:
[MENTION=3750240]stratosk[/MENTION] I'm testing touch control. Work well. Even your touchwake work well (not both in at the same time) I will report about battery. But I think touchwake is more battery friendly

Inviato dal mio Nexus 4 con Tapatalk 4
[Nexus 4 Original Android Development] lyuz:
[MENTION=3750240]stratosk[/MENTION] CyanKang-10.2-20130902-NIGHTLY-mako(CM-based) Semaphore N4 1.5.9j works fine:good:
[Nexus 4 Original Android Development] stratosk:
Thanks everybody for testing 1.5.9j and for your feedback!

[MENTION=4770534]Sak3ater[/MENTION], [MENTION=3740016]Naa Laa[/MENTION]

I'm currently on my job and I can't test the issue on your ROM.

If you don't come to a solution, I will try to reproduce the issue tonight.

Thank you very much for your tests!
[Nexus 4 Original Android Development] Mercado_Negro:
Just flashed 1.5.9j on SlimBean 4.3 Beta 4 (I was using the stock kernel before, of course). Flashed it via TWRP 2.6.1.0. As usual, no need to wipe Dalvik/cache.

Result: everything is working fine.

Thanks again, stratosk!
[Nexus 4 Original Android Development] snak3ater:
Thanks Stratosk...1.5.9j is causing issues with latest rasbeanjelly even if we have stock rom kernel. I tried dirty flash of rom & then flashing 1.5.9...also in my 2nd attempt i manually flashed the rasbean kernel using fastboot & after that flashed 1.5.9j..in both the cases i got no signals & baseband was showing as unknown.. now i am back to my old nandroid & signals are fine now with faux kernel..

Thanks for all your hard work.. Really appreciate it

---------- Post added at 01:59 PM ---------- Previous post was at 01:58 PM ----------

Yeah..Touch control works fine in 1.5.9j :thumbup:
[Nexus 4 Original Android Development] stratosk:
I will flash rasbeanjelly tonight and check myself.

If it is not hard for you, can you please send me init.* files located in / (as zip attachment here)?
[Nexus 4 Original Android Development] snak3ater:
System/etc/init.d

This is the folder that you need right :confused:

View attachment 2229256
[Nexus 4 Original Android Development] jelle2503:
Touch control does not work for me on 1.5.9j , app cannot find module.

Stuck with a permanant toast su message coz of touch control app.. This happens everytime i start app after reboot. Continous su requests from TC spamming my screen full of toasts.

Better stay away from it, thought TC would be nice to give a spin.

Verstuurd vanaf mijn Nexus 4 met Tapatalk 4
[Nexus 4 Original Android Development] stratosk:
No I mean the files in your / (root) directory:

init.rc, init.mako.rc etc.

Please only send them if it's easy for you.

Thanks!
[Nexus 4 Original Android Development] snak3ater:
Okay.Now i found all the init files..

View attachment 2229281
[Nexus 4 Original Android Development] snak3ater:
Something wrong at your end..Tested it myself today & touch control App was working fine with 1.5.9j...

Just select 1.5.8 when the app asks for a module..It works..Several users confirmed it
[Nexus 4 Original Android Development] jelle2503:
App doesnt even ask for module. Fails to load any of them, then sticks a perm toast message on my screen.

Completely stock. So there can't be nothing wrong.

O well TC for me is a battery drain gimmick anyway :)

Verstuurd vanaf mijn Nexus 4 met Tapatalk 4
[Nexus 4 Original Android Development] philidor:
I (and Sak3ater I presume) are using paid version. I tried free version and it not work probably is not updated [MENTION=3794725]jelle2503[/MENTION] Are you using paid version?

Inviato dal mio GT-P3100 con Tapatalk 4
[Nexus 4 Original Android Development] snak3ater:
Yes. I'm also using the paid version..
[Nexus 4 Original Android Development] alexoz:
+1

bponury confirmed in his thread that for now only the paid version is compatible with semaphore. Works fine here with 1.5.8

Sent from my Nexus 4
[Nexus 4 Original Android Development] Mercado_Negro:
I'm not sure if it's related but I couldn't get any logcats with catlog (Play app) while using this new version, 1.5.9j. The app couldn't read anything from dev/log/system. I had to revert to stock kennel by dirty flashing.
[Nexus 4 Original Android Development] stratosk:
Yes it's kernel related. I forgot to mention that modules path temporarily has been changed.

Modules in 1.5.9 is in /system/lib/modules. I'm not sure if I will keep the old path or not.

You may manually copy the logger.ko module to /data/local, give it '700' permissions and reboot.
[Nexus 4 Original Android Development] Mercado_Negro:
I think I'm not following, Stratosk, sorry. I just tried to generate a logcat with an application called Catlog and it couldn't retrieve any log, the window was always blank in this application.
[Nexus 4 Original Android Development] trillo69:
Logcat app doesn't work in 4.3, same happens with logcat extreme. At least for me.

If you need to get a last_kmsg do it manually with terminal command: cat /proc/last_kmsg > /sdcard/log.txt. That will generate a log.txt file on the root of your sdcard with kernel log.

But I think stratosk meant that you should copy that file manually to the suggested path.
[Nexus 4 Original Android Development] cantevencode:
1.5.9j is working fine with cm10.2 for me. It's fixed the unknown baseband issue and touch control is working beautifully
[Nexus 4 Original Android Development] Mercado_Negro:
Catlog works on 4.3, I've been using it for weeks now on SlimBean 4.3 Beta. Thanks for the suggestion but I was looking for a full logcat, not just a last_ksmg. I understood that part where Stratosk said about copying the file manually but, if I understand this correctly, this file is generated by semaphore, the app. I wasn't using this app to generate the log but Catlog.
[Nexus 4 Original Android Development] snak3ater:
Lol..Finally ran out of patience & flashed Slimbean just for this Kernel :p

All working great :good:

PS:I guess it's only Rasbean which has got issues.Rest all Roms combined with Semaphore are fine i guess
[Nexus 4 Original Android Development] trillo69:
I'm not sure but I think that module (.ko file) is in the kernel (boot.img or zip), so I think stratosk is suggesting to move it from /system/lib/modules to /data/local.
[Nexus 4 Original Android Development] stratosk:
logger.ko module is needed to enable logging feature in Android. It's disabled by default in Semaphore.

In version 1.5.9 the module is located in different path, so Semaphore Manager can't copy the module.

It will be fixed. Until then you may copy manually the file as I mentioned to my previous post.
[Nexus 4 Original Android Development] Mercado_Negro:
Ok, I got it now. Thanks!
[Nexus 4 Original Android Development] rschueg:
currently running cm10.2 0902 with your new 1.5.9j "any" version. baseband now recognised, gsm works so far.

thx for your great job !

N4|CM10.2N|Semaphore1.5.9j
[Nexus 4 Original Android Development] snak3ater:
Here is an update..I was finally able to get the baseband back in rasbeanjelly..I simply flashed the old Twrp (2.6.0.0) recovery & then flashed your Kernel (1.5.9j) again..

Baseband back :D

It was the problem of recovery..Not your Kernel :good:
[Nexus 4 Original Android Development] Naa Laa:
[MENTION=4770534]Sak3ater[/MENTION]

Are you able to get data connection? I got the baseband issue solved but cant connect to data (wifi works fine) with stock (0.84) and hybrid (0.33/0.84) radios.

Thanks for feedback!
[Nexus 4 Original Android Development] snak3ater:
Yes.. Data connection working fine.. Just tested it now.. I am on radio 0.84 .
[Nexus 4 Original Android Development] Naa Laa:
Got it working. Flashed stock radio and then flashed the hybrid radio without flashing the ROM or/and kernel. All good so far with all stock. Will report back after I flash kernel. Thanks again!