yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] ciprianruse88:
Yes.CatLog app works fine.It must be something to syslog app :thumbup:

"by failing to prepare, you are preparing to fail" - Benjamin Franklin
[Nexus 4 Original Android Development] coloxim:
Now I'm using semaphore on stock ROM... Always perfect.. Good battery and performance...

Thank you so much.. Thanks thanks thanks..

Inviato dal mio Nexus 4 con Tapatalk
[Nexus 4 Original Android Development] Dan1234567890:
PA 3.99 RC2 - official version. Thx for all the work and support!!! :) I have one more strange issue; after rebooting or powering on the phone, if i don't keep my screen on with touch, and I let it go of, I cannot turn it on with power button. If i dont let it go off, I unlock the screen, and I can see that semaphore kernel was granted with SU access, and everthing is ok... I didn't saw anyone with same issue, so I thought it is something with my setup... But if you are interested, when you take deserved rest (:)) I can provide you with logcat or whatever you would like, cause I can replicate this behaviour every time. I have dirty flashed rom, so this can be the issue, but every time I reflash stock kernel, let it boot, than go to recovery an flash semaphore... Not a big issue and it doesn't concern me, and I think not a big issue for you cause nobody else reports anything similar... so must be something on my side :)
[Nexus 4 Original Android Development] DontPushButtons:
Always a good idea to wipe data/cache on kernel control apps when you flash a new rom/kernel. Since every rom COMES with a kernel included, it's likely your problem is coming from the semaphore app trying to apply changes to the new kernel.
[Nexus 4 Original Android Development] Tipkaros:
A lot of people aren't commenting simply because everything is working great. Look at this:View attachment 2341400

The last time I rebooted my phone was to flash 1.7.1 :D

Add to that the great battery life and useful options.

Don't quit! ;) :thumbup:
[Nexus 4 Original Android Development] szucsgf:
Stratosk, I apologize for posting rarely here. Your kernel is simply the highest quality custom kernel available. I always keep both jwr and jss versions on my SD card; it's my go to kernel. No other kernel has a better mix of performance, battery, and stability. If I could only choose one kernel to use ever again I would choose semaphore. I'm sometimes surprised that more people don't use semaphore, and never hesitate to recommend your work.

Like others say, this thread is relatively quiet because your kernel has very few issues and I suspect your users are of relatively high quality (which means they search and solve their own problems).

On another note, I wonder if you expect to get the Nexus 5? I plan to, and I wonder if I'll have the pleasure of trying semaphore kernel on that device?
[Nexus 4 Original Android Development] Fenvarien:
+1000 :)

I can't speak for Stratosk, but regarding the N5 he stated several times that he's not going to buy one. http://xdaforums.com/showthread.php?p=45680868
[Nexus 4 Original Android Development] Dan1234567890:
Thx for the help! Clearing data/cache on Sema. manag. app didn't change anything, but regarding your post, I decided to go further that way and uninstall the Sema. manag. app. So without the app, everthing is ok! Than, when I install the app, everthing is ok, as well. But, if I change any value in S. M. app, issue appears (cannot turn the screen on after first boot if screen goes of).

Looks like the problem is in SuperSU granting root privileges to the Sema. manag. app. first time after the boot if the screen is off and locked.

I flashed SuperSU after ROM/GApps install because integrated superuser in PA rom had issues with some apps... And with SuperSU I had no issues, till now... ;)
[Nexus 4 Original Android Development] stratosk:
No need to apologize, my friend! You help a lot in this thread and I really appreciate it.

Thanks for your kind words.

You are right. As I said, I can't afford for a new device.

I use supersu and have no issues on stock rom.

Do you grant permissions 'always' to Semaphore Manager app?
[Nexus 4 Original Android Development] Dan1234567890:
I have an option "grant" selected... But as I think, the problem is that SuperSU wont grant access on first boot if the screen is not on&unlocked.... Strange. :rolleyes:
[Nexus 4 Original Android Development] stratosk:
Can you this in superSU log? (that permission is not granted?)
[Nexus 4 Original Android Development] twowheeler:
To be honest: most of us are probably very happy with this. Not with the fact that you can't afford one, but with the fact that you'll be with us on the n4 for some time ;)

Sent from my Nexus⁴
[Nexus 4 Original Android Development] Dan1234567890:
Ok, I just rebooted, let the screen go off, couldn't wake it with power button.

Pressed power button for long time to turn phone off, turned it on, didn't let the screen go of, unlocked the device, saw message that semaphore manager app was granted with root, and everthing is ok...

Here is pic from SU log, if it helps.... As I said its not a big issue, so don't waste to much time on this...
[Nexus 4 Original Android Development] vampire36:
You know I somehow secretly love the fact you ll be sticking to N4 like me...you not buying N5 tells me 1 thing...I would still get A class support for my Rolls-Royce N4 come what may from an amazing yet humble dev...:) Purity rom + this kernel have been nothing short of amazing,,,:) Love your work and appreciate all the eforts and pain you take :):good::good::good:
[Nexus 4 Original Android Development] stratosk:
Sorry, I forgot. I guess we need superSU pro to get log details.

Anyway, it's definitely not kernel related. My app, simply asks for su permissions when the device boots and receives a BOOT_COMPLETED intent from framework.

One more idea is to change the default access to 'grant' for testing purposes.
[Nexus 4 Original Android Development] ihancioglu:
Hopefully leave it logcat enable by default as 1.7.3 anymore... I don't want to install su and busybox binaries. Semaphore will be last kernel with my n4.

Very good news that you will not switch n5 as n4 still needs your attention. Congratulations my friend.
[Nexus 4 Original Android Development] stratosk:
I'm sorry. Logger will remain as module.

Thanks for you kind words, my friend.
[Nexus 4 Original Android Development] Tex99:
n 1.7.3 is perfect, no issues no reboot. smooth and good battery. thank you for this solid rock kernel :)

I remember a list of different color configurations for semaphore app on google plus, but i don t find the link. someone has it ? thank you
[Nexus 4 Original Android Development] spr33:
Can we start a fund to get [MENTION=3750240]stratosk[/MENTION] a Nexus 5? I personally couldn't contribute much due to having a baby due in December but I feel we could all chip in and get the ball rolling ready for the announcement on Thursday!
[Nexus 4 Original Android Development] okanb3:
Hey sorry about that but i'm on PSX and when i installed Semaphrone Kernel to my device, i lose my root. I tried to search the thread but it seems thread function not working properly; it gave me error.
[Nexus 4 Original Android Development] szucsgf:
It's got nothing to do with semaphore specifically. Just reflash the Supersu.zip after flashing semaphore. Here's the direct link to the psx add-ons folder where you can find it.

https://drive.google.com/folderview?id=0BzX_bRKRGmexSEhUb3R5MWVDd2M&usp=sharing
[Nexus 4 Original Android Development] l33chpda:
Hi. I'm using Slim ROM and I've noticed that whenever I flash Semaphore over the slim kernel, my Gmail becomes unable to download any attachments. I can reproduce this over and over again.

I use slim gapps, pa full gapps, minimal gapps, and the behaviour is always the same.

Ive not tried it with another ROM but wondering if anyone has this issue ?
[Nexus 4 Original Android Development] meangreenie:
Downloading in gmail works fine here, 1.7.1 on deodexed stock 4.3 with krait and dalvik patch
[Nexus 4 Original Android Development] Luigi_2:
Why not :cool:
[Nexus 4 Original Android Development] saintsinner25:
thanks for this great kernel man :D rock solid yet to have single hiccup/reboot and battery also feels better than stock with interactive.running stock with xposed.

thanks again!
[Nexus 4 Original Android Development] richardddd:
This kernel is by far the most battery efficient and best performing I've used on my n4. But since the CM team changed to Qualcomms kernal branch I cannot use it with correct colors anymore. Could one hope for a special cm10.2 version??? I think a lot of users would appreciate that! :)
[Nexus 4 Original Android Development] twowheeler:
I thought there was/is a flashable fix for that.

Sent from my Nexus⁴
[Nexus 4 Original Android Development] snak3ater:
That fix isn't working in the latest nightlies
[Nexus 4 Original Android Development] Skkip:
[MENTION=3750240]stratosk[/MENTION]:

Hi friend,

I am still working on ondemand governor and saw this patch https://patchwork.kernel.org/patch/1650611/ which caught my attention.

From what I've seen in Interactive governor there is also an IF which handles this.

So I decided to avoid unnecessary switches/cpu transitions in ondemand governor (https://github.com/SkipXS/kernel_msm/commit/c3113239f4800e393e21d0b7f35fe9fecc80625b)

and thought you'd might be interested.

EDIT: please note, that this might not be the prettiest solution for this :)

EDIT2: also found this: https://lkml.org/lkml/2013/8/7/212

Greetings from Germany
[Nexus 4 Original Android Development] snak3ater:
Great to see everytime you visit this thread,you come up with a new idea.Giving suggestions to Stratosk & trying make changes that you feel would enhance this great kernel..I've seen not many people around here who would come forward to help other developers like that :good:
[Nexus 4 Original Android Development] twowheeler:
Then I don't know. But I don't think that its up to stratosk (or any developer that has nothing to do with cm) to fix this problem. Cm introduced it, so they should be the one fixing it I guess.

Sent from my Nexus⁴
[Nexus 4 Original Android Development] stratosk:
Thank you very much for your thoughts and your intention, my friend!

I hope you all the best to you and to your new baby!

I know about this patch, I also searched about this in the past.. Actually the specific patch does not add to much to performance. Most of the time target frequency will not much the available frequencies in freq table. So, you have to device if you want one more check in almost every sampling rate (that returns false almost every time).

I did this (that actually do almost all cpufreq drivers):

https://github.com/stratosk/kernel_msm/commit/cfc233b5642d8313afe07bdfa5d02e59728cdf66

About your patch. I have a couple of objections :)

1) It's not generic. It maybe works only for our device. Because freq_table might not have frequencies specifically in ascending or descending order (according to documentation).

2) You may want to use core cpufreq_frequency_table_target, but I'm not sure that is good to check this every sampling rate (because cpufreq driver will run this either way). And again I think this is not governor's work. Governor should find the target frequency. cpufreq driver will match the correct frequency according to freq_table.

Thanks again for your interest!
[Nexus 4 Original Android Development] stratosk:
New version 1.7.4

- Linux kernel 3.4.67

- Fix logger loading issue in some custom ROMs

- ondemand: A small optimization in input event (thanks to skkip)
[Nexus 4 Original Android Development] Fenvarien:
Thanks [MENTION=3750240]stratosk[/MENTION] for the new tasty Semaphore version 1.7.4 :)

Gesendet von meinem Nexus 4 mit Tapatalk
[Nexus 4 Original Android Development] "D":
[MENTION=3750240]stratosk[/MENTION]

Thanks for the Kernel Update :) Good Work!

regards from Germany
[Nexus 4 Original Android Development] hughfollett:
Thanks [MENTION=3750240]stratosk[/MENTION] :)

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 Original Android Development] panart:
[MENTION=3750240]stratosk[/MENTION]

Thanks for the update!

Χαιρετισμούς από Λευκωσία
[Nexus 4 Original Android Development] HiM@L:
this kernel is simply awesome... used it with my vibrant years ago... and now with Nexus 4. thanks for the great work.

OT:

is there a simpler way to get color profiles....Trickster MoD has some but i prefer...iPhone5 profile by bundi22..
[Nexus 4 Original Android Development] cryingrock:
The ridiculous speed and smoothness are just getting worse:p
[Nexus 4 Original Android Development] galaxys:
Awesome version as always! Good stuff!!
[Nexus 4 Original Android Development] chineel:
On latest Vanir it wont boot with colorfix without colour fix it works but colours messed up.

Same happen yesterday with BeanStalk but with 171 kernel.
[Nexus 4 Original Android Development] Fenvarien:
That was discussed just a few posts ago. Those ROMs are CM based, the existing fix doesn't work anymore. The latest working CM build is dated 10-21-2013.

Try Purity ROM! ;)
[Nexus 4 Original Android Development] -iNSiGhT-:
Thanks Stratosk !

Sure it'll be awesome as always...

Paranoid mako
[Nexus 4 Original Android Development] twowheeler:
Having a beer while flashing the new version of this kernel. Cheers Stratosk

Sent from my Nexus⁴
[Nexus 4 Original Android Development] Barbatos19:
Is this official or nightlies?
[Nexus 4 Original Android Development] galaxys:
V1.7.4 is official.
[Nexus 4 Original Android Development] dmourao:
Bump... I would really like that too! :good:
[Nexus 4 Original Android Development] manpildo:
http://xdaforums.com/showpost.php?p=46295694&postcount=4291

Hope this helps.
[Nexus 4 Original Android Development] hughfollett:
There's Semaphore Manager in the play store! And search this thread for franco Semaphore spreadsheet :)

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 Original Android Development] ciprianruse88:
1.7.4 is perfect !! Fantastic work as always !! :thumbup::thumbup::thumbup:

"by failing to prepare, you are preparing to fail" - Benjamin Franklin
[Nexus 4 Original Android Development] nemanja066:
iPhone 5

RGB "0 39 119 0 6 0 2 0 2"
[Nexus 4 Original Android Development] BigDig:
If I'm switching from Franco, should I flash stock first? I'm running stock, rooted...
[Nexus 4 Original Android Development] senthilrameshjv:
Just dirty flash your ROM, Gapps and any other mods you have already had and flash this kernel.
[Nexus 4 Original Android Development] BigDig:
I'm on stock Google ROM, can't dirty flash...I can just flash stock kernel
[Nexus 4 Original Android Development] senthilrameshjv:
One of the best ROM combination for Semaphore, Purity, has its new build up.. http://xdaforums.com/showthread.php?t=2281607

---------- Post added at 06:10 PM ---------- Previous post was at 06:10 PM ----------

Yeah that'll work :)
[Nexus 4 Original Android Development] Barbatos19:
I think there is and I'm using it right now.
[Nexus 4 Original Android Development] twowheeler:
Really have to try that rom I guess. Have been on pa for a long time now

Sent from my Nexus⁴
[Nexus 4 Original Android Development] eluspo:
Is it normal that my gpu is always @ 320 mhz?
[Nexus 4 Original Android Development] eluspo:
Gpu is always [MENTION=2539186]320[/MENTION] and scales down only if i touch the display. Is this normal?
[Nexus 4 Original Android Development] nemanja066:
Maybe, wrong statistics :P
[Nexus 4 Original Android Development] eluspo:
I hope so lol! Its just weird that when i press something the gpu scales down and when i leave it idle it stay @ 320 mhz.
[Nexus 4 Original Android Development] dmourao:
Thanks! I end up finding a spreadsheet with the converted values, but this way is quite faster. :thumbup:
[Nexus 4 Original Android Development] alen1901:
The only thing i miss is row scheduler. :) 1.7.4 working like a champ. ;)

Poslano sa mog Nexus 4 koristeći Tapatalk
[Nexus 4 Original Android Development] eluspo:
Bump!

---------- Post added at 11:56 AM ---------- Previous post was at 11:24 AM ----------

What is the max & min gpu freq for this kernel? Is the gpu governor stock? Thanks
[Nexus 4 Original Android Development] Fenvarien:
As far as I know, Stratosk implemented the stock gpu driver. I trust Stratosk by far more than what trickster mod tells us. Most probably trickster mod is polling the gpu too often - then you can't see an idle state.
[Nexus 4 Original Android Development] benbugohit:
Please stop bumping. Search in this thread !

Be careful, this could be interpreted as spam, and the typical answers to ppl asking several times the same thing is almost:

"RTFM, or LOGCAT, or reboot, or wipe cache & dalvik, or... SEARCH pls."

Hope you're not too lazy asking the same thing several times, and refreshing the page to see if answers, but not taking time to search in this thread.

If u have no answer, maybe it's because the answer is not far !.

It took me 3 seconds to find a relevant answer..

Stratosk is a kind dev, so take care to follow the advices, and prevent him from losing time.
[Nexus 4 Original Android Development] meangreenie:
Trickster always, or at least use to, see the minimum cpu freq on stock mpdecion as 1024mhz. It never shows the drop after a few secs back to 384mhz.
[Nexus 4 Original Android Development] mat0122:
Is the newest semaphore work without problems on CM 10,2?
[Nexus 4 Original Android Development] benbugohit:
That's how to get rid of it
[Nexus 4 Original Android Development] snak3ater:
What Semaphore version are you using?.

There's hotplug driver which can be tweaked.Latest Semaphore does not have mpdecision.Don't understand how will you remove it if it's not there :eek:
[Nexus 4 Original Android Development] sryche:
soft reboot 3 times in last 9 hour. this is my setting and log file. I'd appreciate if you can help.

rom:slimbean 1.9

governor:ondemand

min freq:384

max freq:1026

dynamic hotplug enabled: min 2 max 3

uv:-100
[Nexus 4 Original Android Development] Fenvarien:
Try to use stock settings or at least no UV and report back if you still get those soft reboots.

Gesendet von meinem Nexus 4 mit Tapatalk
[Nexus 4 Original Android Development] kalpik:
If the reboot happens to the Google screen, it's a kernel problem. If it reboots to the Slimbean boot animation, it's a ROM problem.

P.S.: I've also been having a lot of soft reboots (to the Slimbean boot animation with all kernels, so I switched my ROM, and no issues since then!
[Nexus 4 Original Android Development] Fenvarien:
If the phone reboots to the Google screen it's a hardware reset. But you can't talk about a kernel problem if there's just too much UV.

Every piece of hardware is different and successful undervolting is not guaranteed. ;)
[Nexus 4 Original Android Development] kalpik:
That's true! But first we need to determine what exactly is happening. I was getting soft reboots on Slimbean even without U :(
[Nexus 4 Original Android Development] benbugohit:
I didn't had one single since i stopped playing with dirty flashing ROMs and kernels. I prefer performing clean flashs, or at least /system format when upgrading rom (slimbean since i have my N4).

Sometimes it happen when we flash different kernel, without restoring default rom's one, and without cleaning former kernel settings, and playing with uv, frequencies...

It's not a surprise if reboots happen when we try to "push the limits" which means :

trying to change default rom and kernel settings adviced by their dev.

[MENTION=3524161]sryche[/MENTION] My advices if a reboot occurs :

- wipe dalvik & cache,

- format /system (to make sure there isn't any "crappy" init scripts left)

- flash rom default kernel (dirty flash rom + its gapps again in case some disappeared)

- reboot

- flash semaphore, wipe dalvik & cache again.

And see the magic: no reboot. soft nor hard.

So, the problem is not kernel nor rom, but user not beeing aware of its settings applied, and the history of apps + kernels beeing installed, and init scripts left in place...

Slimbean + semaphore jwr work well together.

I only add these things using TricksterMod when using stock slim kernel (or franco's one):

- cpu min & max freq tweaking (384 - 1135),

- gpu max to 320 MHz

- and generic mpd + showp mpd (if included in kernel as franco's one) disabling, screen turned off and back on, enable generic mpdecision, screen off and on again.
[Nexus 4 Original Android Development] stratosk:
I didn't change a single line in GPU driver, so I guess it's normal (it's also like this in stock kernel).

I suspect that either there is a specific reason for this, or it's just how it appears in sysfs.

The point is that the GPU is idling.

I don't know if it's true for our GPU, but it modern implementations a CPU/GPU can be in a low power state even if the 'current' frequency is high.

For example on an intel i7, it's better to use the performance governor (frequency always on max). The CPU itself will go to a low power state when it's idle.

If it's working like a charm, why do you miss the row scheduler? :)

I'm kidding. I mean, if we actually don't need a functionality in the kernel we should not add it.

ROW scheduler was rejected so far from Linux maintainers. Not because, it was bad.

But, because, nobody proved that other available schedulers can't do the job.

I agree with Fenvarien and kalpik.

I just want to say that I don't see anything special in kmsg.
[Nexus 4 Original Android Development] kalpik:
Love the kernel! Only deal breaker for me is the absence of USB fast charge. I charge from my Laptop at work. Can't carry my charger to work everyday :(

I know it's been stated that you won't add fast charge. So be it! I respect your decision. But I'm sure that may would appreciate that feature :)

In the end, thank you for your hard work, and the awesome kernel! Keep it up :)
[Nexus 4 Original Android Development] Skkip:
[MENTION=3750240]stratosk[/MENTION]:

Hi friend,

first thanks for your feedback on my last patch. You were completely right about the ordering

of cpufreq (saw it after the patch) and your approach is much easier :) Thanks for that!

About the GPU you may take a look at https://android.googlesource.com/kernel/msm/+/67b4c537b599fd650dbfc5ba20d1ab93d8cf2a20.

In short: Upon SLEEP/SLUMBER/SUSPEND the gpu gets set to 320MHz which corresponds to pwrlevel 1. I just added a patch to change

that behaviour (https://github.com/SkipXS/kernel_msm/commit/bfd633cfaae7ee17c3d35e08b841809405df4ebd). With this patch there are

no differences in benchmarks and no noticable differences in smoothness (I guess the trustzone handles the scaling fast enough). I can't

say anything about battery usage right now, since its been a short time testing. I will report back if I can say anything about battery.

From what I see in the kernel it may improve a tiny bit. Maybe you want to test too ? :)

Greetings

Skkip
[Nexus 4 Original Android Development] stratosk:
Hi, my friend!

Maybe the commit in google source answers our question.

The GPU shows 320Mhz current freq most probably is in sleep (or suspend) state. 320MHz will be used what the GPU wakes up.

At the moment I will not change anything there. But please report if you find something interesting.

Thanks!
[Nexus 4 Original Android Development] karthi89:
I couldn't believe that am reading a kernel thread in xda . Am not using semaphore (sorry stratosk) but man I love to read the thread. Everyone is polite and calm. I would love to see other threads like this. Not even a single rubbish word in last 8 pages that i read today. Everyone is doing a wonderful job here. We should keep this thread as a reference . (USB fast charge is the only thing that is stopping me to flash this awesome kernel) .But am always ur fan [MENTION=3750240]stratosk[/MENTION]. Keep up ur wonderful job.
[Nexus 4 Original Android Development] eluspo:
So i was right about gpu staying at 320 mhz, if its normal behavior the i wouldnt bother about it.
[Nexus 4 Original Android Development] sryche:
i think its not rom issue, with other kernels doesnt happen. trying default setting, for now its fine, thanx again stratosk.
[Nexus 4 Original Android Development] Fenvarien:
Thanks for the Semaphore Manager update [MENTION=3750240]stratosk[/MENTION]. :)