yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] snak3ater:
It's a common issue with all Aosp roms..cm is based on JSS so it's a rom issue.. Not kernel
[Nexus 4 Original Android Development] reginickneo:
I installed latest CM (i had 04.18 version) and my lag-problem solved.

Battery life is really great.

4,5 hours of screen! 8% left. Web browsing with opera, pdf reading, few minutes RR3, and I flashed the latest CM + kernel. Auto brightness.

Thanks man!
[Nexus 4 Original Android Development] kfheaven:
We are the champion.....:highfive:
[Nexus 4 Original Android Development] Fabio3105:
Hi, this is the first kernel that i'll flash on my nexus4 because from changelog I read that the wifi problems are fixed.

what process I must do to flash this kernel? I've TWRP recovery. thanks for attention and have a nice day
[Nexus 4 Original Android Development] razerblade17:
wipe cache, wipe dalvik cache, flash kernel..done :D
[Nexus 4 Original Android Development] tisov:
hi guys, will it work on vanilla rootbox? thanks

thanks stratosk for ur great work
[Nexus 4 Original Android Development] gianton:
Yes it will work. Both AOSP and CM-10.1 ROMs are supported.
[Nexus 4 Original Android Development] eep2378:
Dalvik/cache wipe doesn't touch anything on the kernel level when flashing a kernel. Therefore its not needed.

Sent from the Nodes of Ranvier
[Nexus 4 Original Android Development] Fabio3105:
perfect, thanks...

so, if i want (in future) flash another kernel i'll do same procedure or i've need a wipe script?
[Nexus 4 Original Android Development] gianton:
If coming from another kernel, you should flash your ROM with the included kernel and gapps if needed reboot and then flash a new custom kernel.
[Nexus 4 Original Android Development] davwman:
Uhhh...no. Totally unnecessary. Dalvik/cache wipe is all you need

Sent from my Nexus 4
[Nexus 4 Original Android Development] grisha1:
No clue how this is coming back again and again. Dalvik/cache wipe is nonsense for a kernel flash.

But the suggested dirty flash of the ROM (with gapps, if necessary) prior kernel change does eliminate a lot of potential problems (=ramdisk...).

No advise would be better than a plain wrong one :cowboy:
[Nexus 4 Original Android Development] gianton:
Exactly.
[Nexus 4 Original Android Development] davwman:
Yup, absolutely wrong:rolleyes: been flashing kernels like this for nearly 4 years. Using the nexus 4, I never reflashed a ROM and gapps before flashing a new/different kernel. Using a kernel wipe script or simply reflashing a stock kernel before changing from Francos kernel, which is the only one that causes issues because of the modified ramdisk. Trinity, matrix, harsh, semaphore, etc. Do not have these issues. But that's OK, I'm completely wrong. And to add to that, try not wiping dalvik, at least. And let me know if you get fc's. It doesn't always happen, nor does it have to, sometimes it just does.

Sent from my Nexus 4
[Nexus 4 Original Android Development] aimcr7:
Sometimes you need to dirty flash ROM and gapps if you come from kernel that modify mpdecision or removed it. I dont know if kernel cleaning script or stock kernel package included a script to recover mpdecision or mpdecision itself.

And for wiping cache and dalvik, you dont need to do that, its nothing to do with kernel. Franco said that couple times.:)
[Nexus 4 Original Android Development] davwman:
I'm not trying to start a war. There is enough of that in the world. However Based off my experiences over 4 years, I've been flashing kernels this way. Now I know the nexus 4 is different as is every device, but with the nexus 4 if I personally don't wipe dalvik, I usually get fc. Reflashing a stock kernel should be enough using Francis kernels, it was in the past with the nexus 4 and it should still be today. In fact I just started using his kernels again, and when I need to flash a different kernel I'll give it a shot, just reflashing the stock kernel.

Sent from my Nexus 4
[Nexus 4 Original Android Development] grisha1:
Doing something for 4 years does not make it more right or wrong.

And while flashing stock kernel does the job for most kernels, it will not for some that rename thermald and mpdecision. And then there are kernels that chang powerhal. So, long story short, dirty flash ROM is all it takes to be safe (and it's a quick process), no wiping of any sort needed. Everything in between can be fine or not, depending on the from/to kernels involved. Peace :angel:
[Nexus 4 Original Android Development] Fabio3105:
so, for the first time i've must do wipe cache and flash a "new" kernel.

to return at stock kernel, or other kernel, i'll must flash a new rom... it's correct??
[Nexus 4 Original Android Development] grisha1:
So, long story short, dirty flash ROM is all it takes to be safe (and it's a quick process), no wiping of any sort needed.

No wiping in general needed. But if it makes you feel better, it won't do any harm either.

If you come from stock rom or custom rom (except minooch...), just flash the kernel you want to try. To flash afterwards any other kernel, dirty flash the ROM you're on.

Good luck, have fun :good:
[Nexus 4 Original Android Development] Semantics:
Nice job hijacking this thread. Anyone using 4.0 getting random freezing?
[Nexus 4 Original Android Development] stratosk:
What do you mean freezing? Reboots?

Do you have enabled touchwake? I had some reboots using touchwake.
[Nexus 4 Original Android Development] stratosk:
I thought about following your solution but I didn't want to change anything in /system.

Now all Semaphore changes exist in initramfs and if user decides to change kernel he just flash another kernel without the need of restoring libs or something.
[Nexus 4 Original Android Development] ZioGTS:
I switched from SGS to N4 recently and just flashed the newest Semaphore. Perfect, as always. Thanks Stratos, I can't even think about having an android phone without your kernel, guess I'm totally addicted to Semaphore's smooth and clean feeling... :)

Inviato dal mio Nexus 4 usando Tapatalk 4
[Nexus 4 Original Android Development] Luigi_2:
sounds great to me :good:, tired of dirty flashing rom just to change the kernel
[Nexus 4 Original Android Development] stratosk:
Hey, my friend!

Welcome to N4 forums! I hope you will enjoy your new device and I hope you'll be satisfied with Semaphore kernel. :)

Unfortunately, you can't always avoid this.

My initial approach was to provide an initramfs 99.9% stock with Semaphore changes without any installation to /system

CM broke my plans. I have to distinguish initramfs for stock and CM (or CM based ROMs) and I used anykernel update method.

Though, other kernels also use this method.

So, if you want to install other kernel over Semaphore and other kernel also use anykernel updater you will still have a conflict (maybe).

Anykernel updater will get Semaphore's initramfs and pack it with other's kernel zImage.

Theoretically, the only solution is everybody to use stock initramfs and kernel's installation procedure to leave system untouched.
[Nexus 4 Original Android Development] GreenSGS:
+10000 Exactly my words.

This kernel is superb with cleanness. It works out of box. App is free, Stratos is very brilliant and cool developer.

I always feel happy to support and donate him. I personally request to donate him to support his excellent work.
[Nexus 4 Original Android Development] happiboi:
After another brief stint away from semaphore, I"m back on 1.6.0 and loving the the touch control support too :D no issues yet :D
[Nexus 4 Original Android Development] dsmpampis:
Hey Strato, why you don't make a donation app? e.g. The same application as the one you have for free but with money!
[Nexus 4 Original Android Development] Midomad:
You can donate to him if you want :)

The app is good as it is.

Envoyé depuis mon Nexus 4 avec Tapatalk
[Nexus 4 Original Android Development] ihancioglu:
Hi there, I am using your kernel with stock rom even no root. So my prefered method is flash via fastboot. So when you will back to .img file? Never? :((
[Nexus 4 Original Android Development] Fenvarien:
Hey, today I received my N4 too! Now it's finally time to join the Semaphore party again ;)
[Nexus 4 Original Android Development] gialakias:
It is in the zip if I am not mistaken.
[Nexus 4 Original Android Development] snak3ater:
No..There is no boot.img file in the Zip..But instead you get the contents that are inside the boot.img ie the zImage file..

You can compile it yourself if if having the kernel & the ramdisk..

But the question is..Will it even work :confused:

There is a reason why Stratosk started using this method..

I would suggest that you install 'Flashify App'..This way you can flash semaphore without using fastboot..

---------- Post added at 07:43 PM ---------- Previous post was at 07:42 PM ----------

Sorry..Quoted wrong person..It was meant for ihancioglu :D
[Nexus 4 Original Android Development] gialakias:
Sorry I forgot the change he made in the procedure. It was but no more!
[Nexus 4 Original Android Development] ihancioglu:
Thanks, I can install supersu and CWM , that's not the point. The point is, it is not just kernel. It modified something in the system while installation process which is not good for me.. I would prefer pure kernel file .img as It should. Hopefully there is a way to do this. Because your kernel is superb performance & battery with latest kernel version.
[Nexus 4 Original Android Development] snak3ater:
Let's see if the Dev himself gives you the boot.img file :)

Ps: there shouldn't be any issues if the semaphore kernel is flashed on stock rom kernel..
[Nexus 4 Original Android Development] twowheeler:
How do you guys use touch control. I mean: it isn't in the semaphore app.

1.6.0 + pa is an awesome pair btw!
[Nexus 4 Original Android Development] stratosk:
When I developed Semaphore Manager, I was thinking to make it a paid app, to get some money and continue Semaphore project.

Greece was (still is) unsupported merchant country in Google Play and I had to find different ways to sell the app.

It was sad and I decided to make it a free open source app.

People supported a lot when I was first released Semaphore Manager and I was able to continue the project.

Conclusion. Semaphore Manager IS a free open source app (GPL) and will remain as is. :)

I also prefer fastboot. :)

I still keep my old building procedure.

The problem is that I don't want to distribute and extra boot.img with the old Semaphore initramfs. I think this will cause an extra confusion.
[Nexus 4 Original Android Development] stratosk:
They use TouchControl app (paid version)
[Nexus 4 Original Android Development] snak3ater:
Touch Control App
[Nexus 4 Original Android Development] jokermithun:
can someone explain me "pickup the phone" tweak in semaphore manager app:confused:

Sent from my Nexus 4
[Nexus 4 Original Android Development] stratosk:
When your phone is ringing, pick it up without touch your screen. Simply put it near you ear and SAI service will do the job for you.
[Nexus 4 Original Android Development] toge64:
when i go into semaphore manager to tweak some undervolt settings, i can't view the cpu table. is this correct or does the app have a bug? im running stock 4.3
[Nexus 4 Original Android Development] stratosk:
No, this is not correct.

You should view this table.

Please run the following in terminal emulator:

su

cat /sys/kernel/debug/acpuclk/acpu_table

if you can see something, then something goes wrong in Semaphore Manager app.

Please send a logcat (I hope you can enable logger module from Manager app and reboot) after you will select the specific option in app.
[Nexus 4 Original Android Development] toge64:
yes, i can see it after running the command on terminal emulator. after i rebooted it is working again hmm... i will see if i can recreate it. thanks stratosk!
[Nexus 4 Original Android Development] sgw99:
Which one to use with JSS15Q?
[Nexus 4 Original Android Development] Midomad:
J version.

Envoyé depuis mon Nexus 4 avec Tapatalk
[Nexus 4 Original Android Development] IImanuII:
[MENTION=3750240]stratosk[/MENTION]

Semaphore 1.6.0 works with new cyanogenmod 10.2 (based on 4.3)? If yes i must flash the j version?

Edit: Works! J version works! Great! :)

Inviato dal mio Nexus 4 con Tapatalk 4
[Nexus 4 Original Android Development] ZioGTS:
Uhm... since I flashed Semaphore 1.60 I'm experiencing 99.7% powermanagerservice.wakelocks... My phone does not enter deep sleep anymore. Prior to this I had stock 4.3 (JWR66Y) kernel. I'm still on stock rom, only change was flashing Semaphore, no additional apps or anything that could cause this behavior. Help?!
[Nexus 4 Original Android Development] snak3ater:
Check your partial wake lock..
[Nexus 4 Original Android Development] ZioGTS:
Nothing strange on partial wakelocks, there are several apps like WhatsApp or LightFlow, with usual numbers of wakelocks. All in the same range, though, no "battery killer" activity. Anyway, shutting down the phone and rebooting after a few mins brought back the situation to normal, apparently. Now I have 75% deep sleep and 25% awake. Let's see if the problem surfaces again in the next 24 hours... :eek:
[Nexus 4 Original Android Development] snak3ater:
powermanagerservice.is the sum of all the partial wake locks So that's why i asked to check it..There must be something..Have you checked the kernel wakelocks:confused:

What's the situation of 'Android OS' & 'Android System' in battery stats :confused:
[Nexus 4 Original Android Development] stratosk:
Most probably an app is causing this:

https://github.com/asksven/BetterBatteryStats-Knowledge-Base/wiki/PowerManagerService

Please let me know if you will find the issue.
[Nexus 4 Original Android Development] marhensa:
64 68 118 1 0 0 48 32 1

64 68 118 1 0 0 48 32 1

32 35 116 0 31 16 80 51 3

is there any documentation about gamma control value?

yes we could set it on Semaphore Manager, but without any documentation about list order i found it difficult to understand.. :(

Sent from Android device using Tapatalk 4
[Nexus 4 Original Android Development] stratosk:
From Semaphore changelog (I would prepare soon a Howto for all Semaphore Manager options):

You may tune gamma through sysfs using the following path:

/sys/devices/virtual/misc/gamma_control/gamma_r

/sys/devices/virtual/misc/gamma_control/gamma_g

/sys/devices/virtual/misc/gamma_control/gamma_b

You have to pass 9 values for each file (r, g, b). For example:

echo "64 68 118 1 0 0 48 32 1" > /sys/devices/virtual/misc/gamma_control/gamma_r

For your convinience, franciscofranco uses the terminology below for array's positions

"greys, mids, black, XX, contrast, brightness, saturation, white, XX"

So, he leaves positions 4 and 9 with hardcoded values. (You may also leave them untouched)
[Nexus 4 Original Android Development] snak3ater:
Gamma Values

---------- Post added at 11:48 PM ---------- Previous post was at 11:47 PM ----------

Omg..Devs are always faster :D
[Nexus 4 Original Android Development] marhensa:
thank you for your explanation.. :D

gotta play with it now..

will share it later.

-----------------

so when i want to set these values for all RGB

-----

Grey: 114

Mids: 21

Black: 118

White: 48

Contrast: 30

Brightness: 5

Saturation: 80

-----

with your semaphore manager pattern

and leaving 4th and 9th value as is (default?).

it should be like this?

R: 114 21 118 1 30 5 80 48 1

G: 114 21 118 1 30 5 80 48 1

B: 114 21 118 0 30 5 80 48 3

am i right?

what's exactly 4th and 9th value?

Sent from Android device using Tapatalk 4
[Nexus 4 Original Android Development] giannz:
Hi stratosk,

I'm using CyanKang, an almost-stock CM10.2 rom with the last j version of your kernel and I can't get the logcat output, I already enabled the module and rebooted the phone several time, since I installed your kernel it doesn't work.

Any hint? Thank you!
[Nexus 4 Original Android Development] marhensa:
okay...

after messing around,

found the AMOLED-LIKE color profile for this kernel.. :)

Color Temperature

R: 245

G: 245

B: 255

Gamma Control

R: 114 21 118 1 30 5 80 48 2

G: 114 21 118 1 30 5 80 48 2

B: 114 21 118 0 30 5 80 48 3

turn off and turn on display to take effect.

it looks nice..

at least for my taste, of course :p

i came from GNex, i missed amoled screen so much..

with that settings, is the near amoled experience i could get.

Sent from Android device using Tapatalk 4
[Nexus 4 Original Android Development] stratosk:
Hi,

The module is located in /lib/modules.

The init.rc tries to load it from /data/local directory.

Please check that the module is in /data/local when you enable it from Semaphore Manager (it copies the file there)
[Nexus 4 Original Android Development] PRGUY85:
Hey, is this kernel optimized for better battery life compared to stock out of the box?
[Nexus 4 Original Android Development] C4SCA:
Yep. As any other custom kernel... The main point of all of them is increase the kernel efficiency wich means more battery life and better performance

sent from my NEXUS 4 tasting a revamped cooking recipe of Jellybeans (stock 4.3).
[Nexus 4 Original Android Development] jtwlbz:
1.6 feels really good! Good work
[Nexus 4 Original Android Development] kandarpck:
1.6 feels great. Heavy usage. 5 hours SOT. I'm enjoying this more than ever :)
[Nexus 4 Original Android Development] apatal:
Hi [MENTION=3750240]stratosk[/MENTION]: just curious, if for example, we set the kernel to only use 2 or 3 cores, is there a way to set which cpu core (0, 1, 2, or 3) would actually turn on and which one(s) would remain off?

Thanks! :)
[Nexus 4 Original Android Development] stratosk:
No, you can't set this.

You only set the number of CPUs (min and max) you want to stay online. The driver will take care the rest.

But, why do you need this?
[Nexus 4 Original Android Development] apatal:
Oh I know about those settings. I just noticed that when I set it to two cores only, only CPU 0 and 3 remains online while 1 and 2 remains offline. Just thinking if I keep it this way, won't there be any harmful effect on the device SoC as opposed to using different cores at different times? Educate me though, as I hope you can, see thru my cluelessness about chip architecture. I'm just thinking aloud here, and you're one of the more helpful devs in the community I know. :)
[Nexus 4 Original Android Development] Franklin Bernard:
HI Stratosk,

Greetings,

Thanks for your wonderful Kernel.

One question - will faux latest sound drivers be included in the Kernel ?

Thanks.
[Nexus 4 Original Android Development] stratosk:
I doubt that there will be a negative effect to your CPU for many years.

When the kernel hot-unplugs a CPU, essentially it removes all the work from the specific CPU. This allows the CPU to enter to deeper power state (less power consumption) more easily.

Stock kernel uses mpdecision (userspace driver) to hotplug CPUs. CPU 0 is online always and it hotplug CPUs 1-3 according to load.

With my my driver CPU 0 is online always (this cannot be changed in this architecture) and other CPUs again are online/offline according to load. I use a different algorithm and I put online the first available CPU if the load is more that up_threshold and put offline the first online CPU when the load is below up_threshold. This explains why CPU 1,2 are hotplugged first.

I think chips (and your CPU) are the last parts of your phone that will 'leave' this world. As long as the CPU runs in the acceptable safe thermal range I doubt that you will see the CPU die even if all cores are always online.
[Nexus 4 Original Android Development] ihancioglu:
Hi [MENTION=3750240]stratosk[/MENTION] ,

Would you please prepare v1.6.0 .img file for flash via fastboot on stock rom?

Great job,Thanks,
[Nexus 4 Original Android Development] nithin1992:
He doesn't really want to do it because it'd cause more confusion. He's replied to a similar post a few pages earlier :)
[Nexus 4 Original Android Development] stratosk:
Hi,

Thanks for your comments. :)

I'm not sure about faux hacks for sound. My concern is the sound quality. Digital amplification may cause sound distortion.

Of course the default settings will be similar as stock but...
[Nexus 4 Original Android Development] ciprianruse88:
[MENTION=3750240]stratosk[/MENTION]

Wow! I am very impressed with 1.6.0 ! Thank you very much for your amazing work !:cool:
[Nexus 4 Original Android Development] nadiros:
Just flashed this yesterday and I must say I am impressed :) Now that you have Touch Control support I think I'll be sticking around.

Thanks for all your time and sharing.
[Nexus 4 Original Android Development] nithin1992:
A feature request, why don't you add a few color profiles into the app? Probably halfbreed and a few other profiles? I know its easy enough to do it, but everytime you reflash you gotta look up for the color profile codes and enter them. So it'd be an easier way if it had inbuilt profiles
[Nexus 4 Original Android Development] manpildo:
Great kernel. Minimalistic and to the point :good: To be frank, the Nexus community has so many great developers I haven't stumbled across anything you can call bad.

Anyway, I have a question to undervolters with "faster" binning - how far down can you go and stay stable on this kernel?
[Nexus 4 Original Android Development] ioucorsa:
i'm with fast chip and i have -175 in all range and it solid rock... (i have 1.5.3 still and it's the max you can go with semaphore manager app)
[Nexus 4 Original Android Development] stratosk:
I'm sorry, no motivation to do something like that... :)

BTW, why you re-enter them every time you flash the kernel? Do you mean if you come from other kernel?
[Nexus 4 Original Android Development] manpildo:
What does it mean when my LED becomes red? In Semaphore Manager red should light up on "thermal", does this mean when thermal throttling comes into play? I just UV-ed by 100mV and started a stress test in Antutu and almost immediately the LED turned red, even though the phone isn't hot at all. What exactly does it show?
[Nexus 4 Original Android Development] nithin1992:
Ah no problem. It was present in most of the other kernel apps so thought i'd just request it here as well. Ty for the great kernel though. And yes, when coming from a different kernel. Also what exactly does the anykernel method do? What are its advantages?
[Nexus 4 Original Android Development] stratosk:
If you have thermal trigger on red LED, it means that the CPU temp is >= 52 degrees (Celsius).

The phone wasn't hot because the CPU just started to spread the heat.

Anykernel is used by most devs.

The advantage is that during installation you "inherit" your current initramfs. So, eventually you will have your ROM's initramfs with the kernel you are installing. The disadvantage is that you need a "clear" initramfs (ROM's stock). For example if you install Franco's kernel and then Semaphore, you will have Semaphore kernel with Franco's initramfs.

I just used anykernel and added something more. The script unpacks initramfs and put Semaphore's changes in it. Then it repacks with Semaphore kernel and flash it in boot partition (as anykernel script does). The result is that you have your ROM's initramfs with Semaphore's changes.
[Nexus 4 Original Android Development] H-Body:
I'm so sorry Stratosk, I cheated on you with another kernel. But now I'm back on Semaphore and it will never happen again, I promise! ;)
[Nexus 4 Original Android Development] stratosk:
:laugh:

No problem, my friend!

It's your choice to flash any kernel you want any time.

Whatever kernel you flash, you still my friend! :)
[Nexus 4 Original Android Development] nithin1992:
So I just google'd and found out more about initramfs. However I want one thing clarified, if your coming from a kernel like franco's in which the ramdisk is modified, would flashing this kernel without dirty flashing the rom itself use the rom's ramdisk or modified franco's ramdisk?