yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] jst_tsj:
So, the output is

root@android:/sdcard/sema # strings /data/local/logger.ko | grep Sema

vermagic=3.4.62-Semaphore_N4_1.6.5 SMP preempt mod_unload modversions ARMv7

root@android:/sdcard/sema # uname -a

Linux localhost 3.4.62-Semaphore_N4_1.6.5 #634 SMP PREEMPT Mon Sep 16 23:33:09 EEST 2013 armv7l GNU/Linux

while you can find dmesg and init.rc at the following link. "cat /proc/kmsg" is not showing anything

https://dl.dropboxusercontent.com/u/17484732/sema.zip

Thanks for your time!
[Nexus 4 Original Android Development] stratosk:
Very weird! Everything seems normal.

Did you change SELinux mode? (to enforcing)

Otherwise, maybe the issue appears to Slim rom.

I mean init.rc tries to insmod the logger.ko module as the last thing in on post-fs-data section.

Custom ROMs use one import as their custom stuff in init.rc. So CM uses this line:

import /init.cm.rc

and Slim uses this

import /init.slim.rc

Insmod line is after the above import. Maybe something in ther stops the execution of insmod. I tested this successfully on CM.

Anybody with the same issue on Slim??
[Nexus 4 Original Android Development] jst_tsj:
Thank you stratosk! :) I didn't change the SELinux mode, so I don't know what's happening here :) I'll try to clean install and see if I have this problem again. I'll let you know! :) Good night!
[Nexus 4 Original Android Development] vampire36:
[MENTION=3750240]stratosk[/MENTION] : I dont know if this ris reported but touchwake max delay is 45 sec...using semaphore manager even if you set it too > 45 sec...say max 300 sec still wakelock is held for 45 sec and then tap won't switch on the screen...tried all posibble cases to make it work...but it stuck at 45 sec :)
[Nexus 4 Original Android Development] necrologo:
I had a reboot when I tried to make a photo via whatsapp. Don't know if it is rom related or kernel related, anyway

I had "logger" in semaphore app disabled (don't know why) and these are the only things I can provide. Hope can help... Anyway great job [MENTION=3750240]stratosk[/MENTION], only 1 reboot in more than a week with semaphore !

https://db.tt/cwjRxHm3

Inviato dal mio Nexus 4 usando Tapatalk 4
[Nexus 4 Original Android Development] stratosk:
Thanks for your report! Confirmed.

Now you can set the max delay up to 90sec. I will fix it in next version of Semaphore Manager.

It was a hw_reset. This was caused from a process from userspace (AFAIK).

I'm sorry I can't do anything for this.
[Nexus 4 Original Android Development] eainyow:
Just had a random reboot while playing with terminal. It was a soft reboot that rebooted into the boot ani straight. Here's the last_kmsg http://pastebin.com/r9PFyHNh
[Nexus 4 Original Android Development] stratosk:
The power management hardware reset your phone.

Do you undervolt?
[Nexus 4 Original Android Development] -iNSiGhT-:
On boot this morning, touchwake was disabled... Verifying with Semaphore manager, it was off...

It's the only setting which has changed on boot...

Will see tomorrow and days after (first time it happens)

But I have a strange behavior with touchwake. Sometimes, when I lock my phone (with power button) touchwake is active (I set blue led for touchwake so I see it on lock)? Is that normal?

;)

Paranoid mako
[Nexus 4 Original Android Development] twowheeler:
I have that too. That touchwake turns off is something I only had at first boot. Sometimes when I unlock my phone it only makes the led light up. But it's not happening often. Touch wake is pretty awesome if you ask me
[Nexus 4 Original Android Development] stratosk:
Please note that Semaphore Manager does not update the settings unless you explicitly select to read system settings.

So, if you have an option disabled in SM and the you change the same setting from sysfs or another app, SM still will show the option disabled.
[Nexus 4 Original Android Development] jst_tsj:
OT: Stratosk, which ROM are you using right now? Thanks :)
[Nexus 4 Original Android Development] stratosk:
I use stock. :)
[Nexus 4 Original Android Development] ole12:
Just flashed Semaphore_N4_1.5.1 (the one without the "j") for PA 3.99 RC2, and I lost Root.

Reflashed the rom, root is back. Reflashed the kernel again, and still no root.

I was running stock PA kernel before I flashed Semaphore kernel.
[Nexus 4 Original Android Development] -iNSiGhT-:
I only use Semaphore manager...and do all the changes with it.

Paranoid mako
[Nexus 4 Original Android Development] stratosk:
Why did you flash an old Semaphore version?
[Nexus 4 Original Android Development] arifroni:
because in main post's download section latest version is 1.5.1. fews days ago i did same mistake and got bootloop, i thought CM's JLS is the problem, today i downloaded new nightly and came to download kernel and found this. i tried 1.6.5j from semaphore website. now its working.
[Nexus 4 Original Android Development] ole12:
THIS.

I found the lastest on your website, and its working now,

Thanks.
[Nexus 4 Original Android Development] stratosk:
You may also find the latest versions in the downloads section on the top of the screen. (You can see this option via broswer)
[Nexus 4 Original Android Development] Fenvarien:
After 7 days of really heavy and intense usage of my N4 I'm absolutely impressed by the perfect stability, reliability and battery life of Semaphore kernel.

Stratosk, thanks for your work and the helpful information you provide to us here [MENTION=243864]xda[/MENTION] and at your website. :)
[Nexus 4 Original Android Development] worldgorger:
I'm using Semaphore kernel for a long time. I have never seen lag, random reboot or something like that. Unfortunately my curiosity made me to change Semaphore to Neo. I used it for about two days and fast go back to Semaphore. This kernel is like the best suit from Armanii. I would like to thank stratosk for all his great and hard work at this. Good job!

Wysłane z mojego Nexus 4 przy użyciu Tapatalk 4
[Nexus 4 Original Android Development] Sanael:
Hi Stratosk.

Could you take a look on last changes in Cyanogenmod ? They made some changes that breaks color compatibility with custom kernels this 02 oct nightly.
[Nexus 4 Original Android Development] McPh1st0:
Yep....same problem here too...

With cm-kernel all is good...

Could it be that they changed android version (jls36g), or am I wrong?
[Nexus 4 Original Android Development] stratosk:
I read that all custom kernels have issues with latest CM nightly because they merged incompatible libs from CAF.

I will think about this. I don't want to maintain 2 different branches. And I feel that CM doesn't care much about compatible custom kernels.
[Nexus 4 Original Android Development] Fenvarien:
Franco stated in his thread that 'CM merged Mako and Flo kernels together using CAF's tree and not AOSP tree. Additionally they started using a different hardware composer.'

Seems to be a difficult move by CM, why do they intentionally break compatibility?

Ahh yes, that's CM... :'( Sad but true. ﻿
[Nexus 4 Original Android Development] stratosk:
Thank you both for your kind words! :)
[Nexus 4 Original Android Development] stratosk:
I don't think they 'intentionally' break compatibility against a custom kernel.

They just follow their own path without caring much to be compatible with other kernels or ROMs.

They are powerful enough to do it and also as a company now have their own goals and reasons to do something like that.
[Nexus 4 Original Android Development] Sanael:
Yup.

They wrote something on this topic here.

Anyway, since they will have to relicense some things for their company, one day you guys will be forced to stop CM support.

But for now CM did'nt sell its soul.

If you can do something about this issue, it would be great. If you can't or if it would be too time hungry, i would change my ROM.

Your kernel makes my phone (and made my sgs).

ROM is just about customization, there is other choices.
[Nexus 4 Original Android Development] Fenvarien:
I know what you mean, Stratosk, but aren't goals and reasons led by intentions? :) :good:

Regarding the technical repercussions of this news by CM... Do you recommend to leave CM or is this problem solvable? Of course I want to stay with Semaphore whatever it takes! :)

Gesendet von meinem Nexus 4 mit Tapatalk 4
[Nexus 4 Original Android Development] stratosk:
Yes, you are right! :)

Anyway, I can't recommend to leave CM and I can't recommend to stay on CM. :)

I also didn't have the time to check exactly the changes. So, I can't say that I will follow or not with a Semaphore compatible version.

It's not interesting to cherry-pick CM's git to make Semaphore compatible, every time.

It's also not interesting to work hours and days trying to resolve compatibility issues (remember the initramfs changes? I was forced to work on a new update method). I prefer to work on something more creative...
[Nexus 4 Original Android Development] hellsgod:
Did they ever care about Custom Kernels? I don't think so. But now it's a different game, you're right :) That's why I started a CM Branch of my Kernel. It's a pain, but the best thing I can do :)

hells
[Nexus 4 Original Android Development] stratosk:
New version 1.7.0

- Linux kernel 3.4.64

- mach-msm: dyn_hotplug: On early suspend use min_online value of 1 (make use of C3 power state on CPU0 when the screen is off)

- mach-msm: dyn_hotplug: Use cpumask_next_zero to find the next offline CPU (thanks to Skkip)

- Possible fix from CAF for a cpuidle bug

- video: lm3530_bl: Introduce new tunables to control LED driver (LCD backlight)

lm3530_min_br: sets the minimum brightness level (2-114)

lm3530_max_br: sets the maximum brightness level (2-114)

lm3530_br_mode: sets the linear (default 1) or exponential (0) brightness mapping mode.

The sysfs path is /sys/devices/i2c-0/0-0038/

Please note that the exponential brightness mode uses a very low LCD brightness on a low external light. You may need to increase the min_br for better results.

Link temporarily removed.
[Nexus 4 Original Android Development] MuertoKo:
Just flashed, why link removed? All good? I just couldn't see Led settings but that's like all

Enviado desde mi Nexus 4 usando Tapatalk
[Nexus 4 Original Android Development] stratosk:
I think I introduced a last time issue. Investigating.

It will not have very serious effects. It just don't turn off the backlight completely when the device is suspended. You will notice that your screen is not totally black...
[Nexus 4 Original Android Development] MuertoKo:
Just noticed :P will keep 1.6.5 then to avoid draining, we should adjust led settings via script or perhaps another app than semaphore manager right?

Gogogo!

Enviado desde mi Nexus 4 usando Tapatalk
[Nexus 4 Original Android Development] Barbatos19:
Got a random reboot again while taking pic on camera. This happens for the second time around.

I like 4shared file "last_kmsg" - http://www.4shared.com/file/txHUCHDC/last_kmsg.html
[Nexus 4 Original Android Development] stratosk:
This version is supposed to fix this. (I hope)

building and uploading as 1.7.1
[Nexus 4 Original Android Development] rankesz:
When can we download it?

Im sleepy, and im on 1.7 with the light issue...
[Nexus 4 Original Android Development] stratosk:
In few minutes. I was going to sleep too when I saw the device too bright... :)

EDIT: Done.

Uploaded 1.7.1 with the issues fixed.

I'm sorry for the inconvinience
[Nexus 4 Original Android Development] 4NDR345:
Too bright on stock? Or this happens only on custom rom?
[Nexus 4 Original Android Development] stratosk:
I mean when the screen should be normally black (when suspended). on stock (and on custom, I guess)
[Nexus 4 Original Android Development] edbertin:
Every rom, display is not complete turning off after entered on sleep mode. Just read previous page. Don´t hurts...
[Nexus 4 Original Android Development] 4NDR345:
ahh ok i understand thx...but u are using only stock or?
[Nexus 4 Original Android Development] rankesz:
i was too slow...
[Nexus 4 Original Android Development] stratosk:
I use stock
[Nexus 4 Original Android Development] klasszsrac:
Thanks the great kernel.

1.7.1 work on Aokp 4.3
[Nexus 4 Original Android Development] jst_tsj:
Thanks for the new version! However, is it just me or touchcontrol is not working with latest version?
[Nexus 4 Original Android Development] thiskar:
ah good to see you here, i used your kernel on my old galaxy s every time :) still rocks
[Nexus 4 Original Android Development] Ensifolk:
Semaphore? Hahahaha! MY FAV KERNEL FROM THE Galaxy S Days ! Wooha :) welcome
[Nexus 4 Original Android Development] prbassplayer:
Hey stratosphere great to see you here :)
[Nexus 4 Original Android Development] emanuele1986:
Fantastic news!

I installed on galaxy s1 friends your kernel and it was fantastic. I hope the same for nexus 4. Waiting for next release.

Thanks ;)
[Nexus 4 Original Android Development] benkya:
Finally... Now i can join you here stratosk.. I just got my nexus 4 today, with discount :)
[Nexus 4 Original Android Development] camp70:
Great notice! Big fan of your work on galaxy S :good:
[Nexus 4 Original Android Development] aaron.bufc:
Delighted to see you here! You were my hands down favorite dev during my galaxy s days. The more kernels the merrier :) I look forward to your work!
[Nexus 4 Original Android Development] Armin_van_buuren:
Oh my God!

I followed your work in the S1 and were by far the best kernels that had.

As I am happy to get them back!
[Nexus 4 Original Android Development] pitjago74:
Nice to see you!!!!great work at sgs1:D:D:D
[Nexus 4 Original Android Development] zadock:
Nice to see you stratosk and welcome!!

I used your kernel in my old SGS and was the best!
[Nexus 4 Original Android Development] trailblazerz11:
Glad to see you with a N4 :) Your work on i9000 was fantastic
[Nexus 4 Original Android Development] leventccc:
I was using your kernel on i9000 so I know how great the battery life is, welcome to nexus 4 community.
[Nexus 4 Original Android Development] luiseteyo:
Famous semaphore for n4! Thanks!

Enviado desde mi Nexus 4 usando Tapatalk 2
[Nexus 4 Original Android Development] Dougfresh:
Stratos, you just got your N4 monster and delivered a beautiful kernel. Is it tweakable with the semaphore manager apk? Thank You brother!
[Nexus 4 Original Android Development] stratosk:
Some common options (like governors) will work.

But app needs some re-work to to fit in both devices. In my TODO list.

@all

Thanks everybody for your welcome messages. I will do my best to deliver a high quality kernel for N4.
[Nexus 4 Original Android Development] Tylog:
Sounds nice, let's see what comes :) welcome to the great N4 community.

Tapatalk
[Nexus 4 Original Android Development] TheeWolf:
Wouldn't it be simpler to make a separate app for N4 and for I9000?
[Nexus 4 Original Android Development] stratosk:
Yes, it would be simpler to make it. But it would be more difficult to maintain for 2 (or more?) devices.
[Nexus 4 Original Android Development] mumaster20:
Woop woop, awesome to see you here!

Was using your kernel all the time on my Galaxy S, and oh boy, what an awesome kernel was it.

Hope to see the same results here! Goodluck!
[Nexus 4 Original Android Development] luiseteyo:
Maybe u could delegate the maintenance of those kernels to some developers/friends! :)

Enviado desde mi HTC One X usando Tapatalk 2
[Nexus 4 Original Android Development] Sanael:
Yup.
[Nexus 4 Original Android Development] davidcd13:
Free

Voila. ;)
[Nexus 4 Original Android Development] leos0000:
Here u go mate ;)

From Moscow
[Nexus 4 Original Android Development] stratosk:
Just curious: why someone rated this thread as "terrible"?

May I know the reason, please?
[Nexus 4 Original Android Development] razerblade17:
maybe that person cant read, so he think 1 star mean, this kernel is best among others,,im just think positively :p
[Nexus 4 Original Android Development] apatal:
Must be a troll. Always one lurking in the crowd. Don't worry he'll be drowned by 5-star voters pretty soon..
[Nexus 4 Original Android Development] philidor:
I just go to my PC and vote this thread 5 stars. I forget to vote for this is a new thread (stratosk you are you are making a excellent work in so few days...)

So please to all forgetful peoples like me, you have to vote so trolls will be crushed by the weight of our RIGHTFUL opinions.

PLEASE VOTE 5 STAR:

Stratosk EXCELLENT work = 5 stars

(sorry for OT, I know it's stupid but it made me really angry) :mad:

Inviato dal mio GT-P3100 con Tapatalk 2
[Nexus 4 Original Android Development] matesc:
5 stars, definitely! :p
[Nexus 4 Original Android Development] Fabio3105:
https://docs.google.com/file/d/0BwwSoSb9gBtyOW9uUkF1WE9CalE/edit?usp=drive_web this is my screenshot of terminal emulator... Thanks man!!!

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Original Android Development] stratosk:
Don't worry my friend. I fully respect his/her opinion about the thread or the kernel. I just wanted to know why?
[Nexus 4 Original Android Development] aventu:
I think it has the same irrational reason that people give one star for apps. A missing feature maybe.

5 stars: hype or really happy

4-2 stars: they somehow thought about their rating and maybe have a improvement proposal

1 star: 5% reasonable rating, 95% too stupid to use or just trolling because f*** everything
[Nexus 4 Original Android Development] jelle2503:
franco rated this thread 1 star :D

Verstuurd van mijn Nexus 4 met Tapatalk
[Nexus 4 Original Android Development] Vangelis13:
^^

Some sarcasm isn't funny even when it's obvious that it is a joke.. :(

The thread rating system should be removed, simple as that.
[Nexus 4 Original Android Development] Maddmatt:
Don't see the big fuss. The overall rating is close to 5-star, no point worring about why some random person gave a bad rating.
[Nexus 4 Original Android Development] Sad56:
Stratosk can you have the 120 sec delay for touchwake in the next semaphore manager update?

Because trickster mod have it but not your app and anytime I start semaphore manager it overlaps trickster settings..

Thanks

N4 - Xenon HD - Semaphore Kernel
[Nexus 4 Original Android Development] stratosk:
Noted for next version. Thanks
[Nexus 4 Original Android Development] Tylog:
The Kernel looks very Good and works fine, the only reason why i dont use it for longer is that no gamma controle is posible at the moment, from the time when it will addet i will use the Kernel :)

Thank you for your work.
[Nexus 4 Original Android Development] a g bell:
Is UV supported in semaphore manager?
[Nexus 4 Original Android Development] android88:
This kernel doesn't support UV.
[Nexus 4 Original Android Development] TheeWolf:
Hi,

The kernel does not implement UV so Semaphore manager doesn't have that option.
[Nexus 4 Original Android Development] meangreenie:
Hmmmm, reluctant to move from 1.6.5 it's so good.:)
[Nexus 4 Original Android Development] sgw99:
For the records (no complaint): I still have ugly colors with CM-10.2 from 1002 and Semaphore 1.7.1 ... I thought 1.7.1 tries to solve this?

Thanks!
[Nexus 4 Original Android Development] snak3ater:
Yes..Touch Control is not working..

Please report it in the Touch Control Thread
[Nexus 4 Original Android Development] stratosk:
No, it doesn't. I didn't add anything related.
[Nexus 4 Original Android Development] sgw99:
Ah, that explains it. So I have to roll back to 1001 (if even possible) or skip Semaphore for now ...

Thanks anyway, Stefan
[Nexus 4 Original Android Development] ihancioglu:
Hi stratosk,

Could you please explain a little bit more what is lm3530_br_mode used for? What will the benefits If we enable that? I just realized that brightness very low as you described, but min value 50 is looks good for indoor light. I think that should be so much as 114 is full?

What about the changes are made in sysfs folder, I think that will on the fly and disappear on next boot right?

Thanks in advance,

Ibrahim
[Nexus 4 Original Android Development] menkyy:
just flashed aokp Whitehawkx 2013-10-01 with semaphore 1.7.1j hope is running well :angel:
[Nexus 4 Original Android Development] twowheeler:
That dynamic hotplug feature looks really promising. Will flash when I get back from school. Lets see if the perfect 1.6.5 can be even better. Thanks again Stratosk! :)
[Nexus 4 Original Android Development] Fenvarien:
I switched to stock ROM for the time being... all CM dependent ROMs will sooner or later be problematic...

Semaphore 1.7.1 works fantastic here! :) :good:
[Nexus 4 Original Android Development] snak3ater:
Can you share the link of Whitehawkx :confused:
[Nexus 4 Original Android Development] menkyy:
sure, here's the link : http://goo.im/devs/Whitehawkx/mako/aokp_mako_jb-mr2_unofficial_2013-10-01.zip :good:
[Nexus 4 Original Android Development] stratosk:
Hi,

lm3530 is the LCD backlight driver chip. The chip supports 2 brightness mapping methods. Linear and exponential.

This means that when you set the brightness to a specific level, the 2 methods will have different effect to the LEDs brightness.

With the linear (default), LCD brightness is a linear function of the level that user sets and with the exponential is... exponentional.

The difference is that with exponential you will need greater values to brightness level to achieve more LCD brightness.

The other to tunables min_br and max_br are used to set the limits of minimum and maximum brightness.

Please note that these limits are in the kernel. So, Android framework still will try to use the default brightness range but the kernel will cap the final values.

EDIT: I think exponential is more battery friendly method
[Nexus 4 Original Android Development] rawdealer:
Does this affect to manually set brightness to max?

Sent from my Nexus⁴
[Nexus 4 Original Android Development] twowheeler:
I guess only the way it ramps changes, not the actual min and max values.
[Nexus 4 Original Android Development] ihancioglu:
Hi my friend,

I did not find right values for this setting. I just set

echo 90 > lm3530_min_br

Then I look current level with

cat lm3530_level

LCD Backlight Level is : 34

So I am just thinking that , when we switch to exponential, do we need to increase max value in that way? For example to 255 ?

I am really confuse for this settings. I think will leave default :)

EDIT: I would like to ask you what the setting you using about this? Maybe that will be good reference for us..
[Nexus 4 Original Android Development] 3mperror:
Hello everyone,

actually I am running Semaphore 1.6.5. I want to use the newest (1.7.1). What do I have to do? Just flash and wipe cache/dalvik cahe?
[Nexus 4 Original Android Development] stratosk:
In both cases the min-max brightess valid range is 2-114.

The current level reports the uncapped brightness value.

If may want to increase the min brightness when you set to exponential.

for example:

echo 0 > /sys/devices/i2c-0/0-0038/lm3530_br_mode # This sets mode to exponential

echo 50 > /sys/devices/i2c-0/0-0038/lm3550_min_br # This sets minimum brightness to 50

So, now the allowed values will be 50-114.

At the momemt I use stock. But during my tests I used the values above.
[Nexus 4 Original Android Development] edbertin:
Just flash it over 1.6.5
[Nexus 4 Original Android Development] alen1901:
So if i instal latest kernel and dont touch that, everything will be like in 1.6.5? I mean, if i set brightness with slider to 50% on 1.6.5 kernel, flash 1.7.1, put brightness slider to 50%, screen brightness will be the same or with 1.7.1 i would need to put slider to cca. 60% to be the same. I hope you understand :p
[Nexus 4 Original Android Development] stratosk:
If you leave the new tunables to default values everything will be like stock kernel (and Semaphore 1.6.5)
[Nexus 4 Original Android Development] Ümit:
Hi stratosk,

it's about brightness driver looks like galaxy S kernel?
[Nexus 4 Original Android Development] stratosk:
No they are absolutely different.

In SGS, the driver handles the brightness level according to sensor values. It also block any changes from userspace (ROM).

Now, I only exposed tunables for min and max, and also a tunable to handle chip's linear/exponential brightness mapping mode. ROM still handles

the brightness level.