yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] funcrusher:
Bad form, bro.

Why do all the dirty work when you can pay a dev $2 to do it for you??!
[Nexus 4 Original Android Development] Scallywag1:
Are you only commenting bc he said that he didn't want the investment to go to waste?

I also commented on the same thing. I completely understand if Dev for any kernel doesn't want to include something, that's their right and choice.

I figured I'd ask bc

1. It really does improve the sound by a lot.

2. This kernel uses or got ideas from faux display, so why not ask for the sound ones if he's familiar?

3. Could care less about 2 bucks. I don't buy anything, I support what I believe makes my phone better and I get use out of.

I'm not coming at you for your response, just venting in a weird way.

This thread is probably the nicest thread I've ever seen on xda. So I wanted to agree with the original post that it does improve sound and also the comment about bad form. I only asked for this feature bc I use it and it seriously works. I use the speaker for music for my kids. Originally the speaker was weak. After these 2 mods it's great.

I'm currently using a different kernel bc of the mods, but want this kernel to include it. I tried it for a couple days and it was great and the thread was a delight to read and follow

Bottom line, ur both right. And bc of this thread I want to donate.

But want to use kernel as well.

So why not ask....
[Nexus 4 Original Android Development] stratosk:
As I responed to previous requests, no plans for sound improvements, but I will check it when I will find some free time.
[Nexus 4 Original Android Development] Tylog:
This would be nice if you find time, this is the only small thing I am missing for the absolutely perfection :)

Tapatalk
[Nexus 4 Original Android Development] jelle2503:
if you are that desperate for your 2USD investment, why not go build semaphore with faux sound yourself? It kind of gets old seeing people spam faux sound requests.

I really like a lot of things added too, but i dont go around pushing the dev for him to include it.

Besides im pretty sure that with time stratosk will include sound mods. Of his own.

Verstuurd van mijn Nexus 4 met Tapatalk
[Nexus 4 Original Android Development] Slymobi:
Is it really necessary though. ?? I have no sound problems with my phone.

Sent from my Nexus 4
[Nexus 4 Original Android Development] BlueFlame4:
Yes, the stock mic gain is way too low. Whenever I call someone with disabled sound mods my call partner can hardly understand me.

[MENTION=3794725]jelle2503[/MENTION]: What's the problem with a feature request?

Sent from my Gameboy Color
[Nexus 4 Original Android Development] Tylog:
The point are not sound pRoblems, the point are louder head phones and speaker :)

Tapatalk
[Nexus 4 Original Android Development] benkya:
If something is not broken why should we fix it.

Sometimes, something usefull to ones, didnt to other.

If its a good thing, then stratosk want to make sure it will not harm to our device. So he will need some times to look at it.

patience guys, lets old man stratosk do what ever he want to do.

*** Sorry for my english***

Sent from my nexus 4
[Nexus 4 Original Android Development] eep2378:
For those looking for improved sound have a look in themes and apps forum. There are a few different apps/mods that will help. I use misledz X louder and I have no problems with sound volume/quality. :)

Sent from the Nodes of Ranvier
[Nexus 4 Original Android Development] Scallywag1:
They're not the same thing. They are mods to enhance the equalizer on ur phone. Were talking about actual apps that connect with the speaker and enhance the actual speakers.

Like I said, its obviously up to dev. Completely agree either way. Just wondering, and he already commented on it.
[Nexus 4 Original Android Development] giajp:
Here the "franco_profile" color settings (best configuration existing for me)

temperature - red, green, blue: 255

gamma - red, green, blue: 0 119 119 1 0 0 23 7 1

someone have a guide or explanation on the jitter filter?
[Nexus 4 Original Android Development] eep2378:
If your referring to earpiece and speaker then x louder does that too. Check his OP.

Sent from the Nodes of Ranvier
[Nexus 4 Original Android Development] sirxdroid:
[MENTION=3750240]stratosk[/MENTION] - are we positive that Semaphore undervolting actually works? I don't see the CPU temps being different from stock even though I disabled uv boost and went -100mV from there (for a -125mV total).

Please have a look at this post:

http://xdaforums.com/showpost.php?p=41677083&postcount=296
[Nexus 4 Original Android Development] a g bell:
They do:)

sent from slim nexus 4
[Nexus 4 Original Android Development] thracemerin:
UV below 850mV won't work on this kernel either, the regulator will prevent it, the files are the same as the ones I identified in that post, unless stratosk has bypassed it somewhere else.

Edit: from the screenshots I looked at quickly, it doesn't look like anyone is going below 850mV anyway so in that case it would be applied correctly.
[Nexus 4 Original Android Development] ctfrommn:
So is the assumption that 850 is the floor on every kernel then? I know if I lower 384 to below 725 ish I get freezes and reboots so I think some kernel devs have figured out a workaround for it.
[Nexus 4 Original Android Development] thracemerin:
The stock regulator prevents UV below 850mV, whether its possible to go lower or not depends on the chip, but unless the regulator is modified from stock the voltage will be set to 850mV regardless of what appears in the table.

The problem I identified in the other thread stems from the fact that LG decided to have 2 copies of a lot of board files, so there is a board-8064-regulator and a board-mako-regulator, both have to match for things to apply correctly, this wasn't done in the other kernel. On this kernel, both are set to 850mV like stock.
[Nexus 4 Original Android Development] ctfrommn:
Very interesting proposition.....it feels like this would be a good thread starter/topic to round table with some more kernel devs. I would be very interested in what the consensus is. I really appreciate the tenacity to which you dig into these things and dont just accept what is said. :)

Crap, ran out of thanks......but thanks!
[Nexus 4 Original Android Development] sirxdroid:
I tried the theoretical 384Mhz @ 750mV on mine and saw no temp difference. Last I played with uv on other kernels (I think Franco and Faux 014) I think I saw the CPU running cooler, but it's so hard to actually tell what's going on because the ambient temp can be so different and that will impact CPU temp.
[Nexus 4 Original Android Development] thracemerin:
Faux and franco have the regulator voltages set correctly for UV below 850mV. (so do trinity, bricked & harsh, I didn't check the others)
[Nexus 4 Original Android Development] sirxdroid:
Thanks for confirming. I'm out of Thanks for the day and it's only 10am where I am.
[Nexus 4 Original Android Development] ctfrommn:
Ok, that makes sense then....I was wondering why I could UV this one by -150mv and temps didnt change a bit.
[Nexus 4 Original Android Development] stratosk:
Thanks for catching this!

I will check it as soon as possible.

EDIT: BTW, board-mako-regulator.c is the file that is compiled in our config
[Nexus 4 Original Android Development] stratosk:
Thanks you also for catching.

I guess thracemerin is right, but you can still undervolt down to 850.
[Nexus 4 Original Android Development] a g bell:
So from this can it be assumed everything set below 850 in table is in fact 850:confused:

sent from slim nexus 4
[Nexus 4 Original Android Development] ctfrommn:
Currently yes, but seems a fix is imminent.
[Nexus 4 Original Android Development] mundixx:
You pretty much nailed it. :D

Tapatalked from my AOSPA Nexus 4
[Nexus 4 Original Android Development] thracemerin:
Based on what I've seen, yes
[Nexus 4 Original Android Development] a g bell:
Thankyou:)

sent from slim nexus 4
[Nexus 4 Original Android Development] stratosk:
Mea culpa!

I'm sorry for this inconvenience.

I didn't notice this limitation in regulators, although I crashed my phone many times to confirm that UV is working.

Thanks everyone who noticed this. It will be fixed in next version
[Nexus 4 Original Android Development] sirxdroid:
Nothing to be sorry for, don't worry about it.
[Nexus 4 Original Android Development] eep2378:
No worries my friend, the power of collaboration in full effect :)

Sent from the Nodes of Ranvier
[Nexus 4 Original Android Development] philidor:
We asked for UV and you give us a fast end functional UV. When you fix this little issue and make perfect your UV... Will be many people vpwith cooler but unstable N4 :)

(And I'll be among these peoples)

Inviato dal mio GT-P3100 con Tapatalk 2
[Nexus 4 Original Android Development] stratosk:
Yes, this bug saved us from many instabilities issues.

I fixed and tested on my phone. I was thinking: "I have to warn people to remember to untick 'Apply on boot' option before flash the new version".

Suddenly my phone rebooted. **** I forgot to untick the option! :laugh:

Maybe a flashable zip that deletes /data/data/com.semaphore.sm/shared_prefs/com.semaphore.sm_preferences.xml should be in OP. :)
[Nexus 4 Original Android Development] sirxdroid:
Yes, that's exactly what Trickster does, it provides a flashable trickster_reset.zip for those "oh $#!t" moments.
[Nexus 4 Original Android Development] stratosk:
In SGS kernel I have an option in own built CWM recovery to clear Semaphore Manager properties...
[Nexus 4 Original Android Development] funcrusher:
Yes. Asking about a desired mod is all good, but holding a $2 donation over a dev's head is ridiculous.

(sorry for bringing up old sh*t)

Anyway, 0.9.5 has been running great!
[Nexus 4 Original Android Development] philidor:
May be a good solution, that function saved me many times on sgs. And may I ask for the semaphore kernel logo at boot... I like it on sgs

Inviato dal mio GT-P3100 con Tapatalk 2
[Nexus 4 Original Android Development] Slymobi:
Mmmmmm I'm confused now.

So UV is not working correct ?

We can UV only to 850 ?

So if I just remove boost then the lowest CPU is 850 and that's it ?

Or I set low/high UV at most 850 for across the board ? ( but the slider doesn't have 850, it jumps from 750 to 875 )

Mmmmmmm again I'm confuddled :eek:

Sent from my Nexus 4
[Nexus 4 Original Android Development] a g bell:
The lowest UV is 850 anything lower is still 850 the display is lying:)

sent from slim nexus 4
[Nexus 4 Original Android Development] Slymobi:
So if I understand !!! Then this should work then ????

Sent from my Nexus 4
[Nexus 4 Original Android Development] Slymobi:
Mmmm no. Just noticed 702000 is still under. Oh well I'm resetting and leaving it as it comes lol.

Sent from my Nexus 4
[Nexus 4 Original Android Development] stratosk:
Yes, it would be a good solution. But I will not build CWM for N4. Maybe, I can do something different. I will think about it.

About the logo. I tried to implemented but with no luck. Although I fixed a broken stock functionality about logo, there is a timing issue.

There is no much time to show it. I mean you can show the logo when the frame buffer is up. But the boot animation starts in less than 1 second. So, I would have to introduce a delay between them. And this is quite ugly hack. :)

Yes, this is true. I'm not sure if everything under 850 remains 850 or if it's rejected.

A comment about this

Absolutely, no offence to people who ask for new features.

But I want to mention that my main goals are.

1) Up to date kernel with the latest versions from Linux (and some cherry-pick from Code Aurora)

2) Fixes (when possible, and if my knowledge permits this)

3) New features, that I try to develop and they are absolutely necessary or add some value to my knowledge.

4) Implementation of features from other devs that are absolutely necessary.

I will not include any feature that:

1) it's just fancy and every kernel in the forum includes it (I fully respect other devs and their work)

2) May cause instabilities

3) It's not coded with Linux standards (there are exceptions - I'm newbie in true kernel development)

That was my logic in my first Semaphore kernel for SGS. I will follow this logic in Semaphore for N4.

But, simply I will follow it more strictly with the hope that people like this work.
[Nexus 4 Original Android Development] Slymobi:
And I couldn't agree more. Its your Kernel and that's why I use it daily now. You have what is NEEDED and do a fine job at supporting your work. Adding this and that just to please x amount of persons is not necessary imo . keep up the great work strat and keep your kernel how YOU want it.

No disrespect intended to anybody else.

Kindest regards.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Slymobi:
Ok because I don't use 384 this should work as a minor UV yes ?

For now at least ;)

Sent from my Nexus 4
[Nexus 4 Original Android Development] endrekok:
I use these settings. Works great. It is stable.
[Nexus 4 Original Android Development] sirxdroid:
Because anything under 850 is actually 850 or maybe even the default, depending what the kernel does with values under 850.
[Nexus 4 Original Android Development] bmakk2055:
How does touch to wake work? I can't get it to work
[Nexus 4 Original Android Development] endrekok:
I didn't know that. Thanks for the info.
[Nexus 4 Original Android Development] sirxdroid:
You can read the last 2-3 pages in this thread, we just discovered the issue a few hours ago.
[Nexus 4 Original Android Development] stratosk:
Please enable it and set a delay (using Semaphore manager)

Every time that your screen goes off due to inactivity (not using power button) the device will be awake for 'delay' msecs. In this period you can touch the screen to fully wake your phone.
[Nexus 4 Original Android Development] stratosk:
Yes, UV works fine for every voltage (final) that exceeds 850mV
[Nexus 4 Original Android Development] Fabio3105:
i'll try this settings... thanks ;)
[Nexus 4 Original Android Development] nicolovitello:
to change the colors with this kernel there are preset file?
[Nexus 4 Original Android Development] emanuele1986:
Hi stratosk, i had again kernel crash after reboot.

Here the kms log

http://db.tt/LOWzfDgD
[Nexus 4 Original Android Development] stratosk:
Sorry, no info about crash in log. Do you undervolt?

No, you have to change the values manually.
[Nexus 4 Original Android Development] stratosk:
New version 1.0.0

- Linux kernel 3.4.46

- msm: mako: Change CPU regulators min_uV to 700mV (thanks to sirxdroid, thracemerin)

- ledtrig-thermal: Do not update LED brightness when there is no actual change.

- msm: acpuclock-krait: Cleanup code, fix a typo in message

- cpufreq: ondemand: Increase DOWN_DIFFERENTIAL to avoid oscillations between max - min freq

- config: little cleanup

Please reset your undervolt settings before flash the new version
[Nexus 4 Original Android Development] Slymobi:
Thanks stratos

Sent from my Nexus 4
[Nexus 4 Original Android Development] sirxdroid:
No really, all the credit goes to thracemerin and the users in the _m+ thread who discovered it. I just happened to notice that the temps were not running any lower for me on Semaphore vs stock, even though I lowered the voltages and I found that suspect so I asked the question.

I'll be sure to give this new build a try. Thanks stratosk!

---------- Post added at 02:12 PM ---------- Previous post was at 02:07 PM ----------

But now I have another one :)

There was some chatter a while back that the greys and whites should be swapped in the gamma interface.

I was just looking at the _m+ sysfs interface spec:

checksum, g_white, g_mids, g_black, 0, g_contrast, g_brightness, g_saturation, g_grey, 2

The Semaphore interface:

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

They look very similar, except for the checksum (which is fine) and the fact that white and grey are swapped. So I'm curious about the white/grey swap if [MENTION=3750240]stratosk[/MENTION] could shed some light on it please. Thanks!
[Nexus 4 Original Android Development] Slymobi:
Are semaphore settings applied on the fly or do they require a reboot ?

Tia

Sent from my Nexus 4
[Nexus 4 Original Android Development] ctfrommn:
On the fly.
[Nexus 4 Original Android Development] stratosk:
You notify me about this, and thracemerin helped me to identify quickly the change.

I don't read closely all the threads, so forgive me if I don't know who exactly found this (thank to him also).

About the gamma interface: they are just names. I expose only the tables. You may use any name you want for the position of the table. I used Franco kernel terminology my example.

Yes, they are applied on the fly. For UV settings you need to press 'Apply'.
[Nexus 4 Original Android Development] androidfoshizzle:
Should tag team with someone to create a ROM with this kernel...call it KreamSickleSoda or MakoFishnChips haha..randomness yes I know,
[Nexus 4 Original Android Development] philidor:
Semaphore N4 1.0

This much UV is real this time?
[Nexus 4 Original Android Development] a g bell:
I too seem to able to UV an awful lot?

sent from slim nexus 4
[Nexus 4 Original Android Development] thracemerin:
[MENTION=3750240]stratosk[/MENTION] still not right on the UV, need to change board-8064-regulator.c as well as board-mako-regulator.c since they are both built for the mako device. Right now you have the opposite problem from the one I identified in my kernel yesterday, but its still locked at 850mV.

Blame LG and their stupid duplication of the board files.
[Nexus 4 Original Android Development] funcrusher:
I'm not here to request any mods or features, just here to say..

THANK YOU THANK YOU THANK YOU

Just flashed 1.0.0
[Nexus 4 Original Android Development] ctfrommn:
700mv is pretty standard for a fast cpu....I can do 750 and sometimes 725 on my nominal.
[Nexus 4 Original Android Development] stratosk:
Thanks, but I don't build this file (at least in my config).

I think it's OK now.
[Nexus 4 Original Android Development] thracemerin:
All I know is faux, franco, etc... have it set in both files. You might be right that it's redundant.
[Nexus 4 Original Android Development] stratosk:
Do you mean this file?

arch/arm/mach-msm/board-8064-regulator.c

I double checked. I don't build this file.
[Nexus 4 Original Android Development] stratosk:
Sorry for my stupid question.

Did you press apply button?

I can't go that low anymore. Now my phone crashes in these voltages
[Nexus 4 Original Android Development] thracemerin:
Yeah, I guess you're right, I wonder why others modify both files.
[Nexus 4 Original Android Development] philidor:
Yes I press apply. And I remember that someone asked you to modify your app for -200 so my UV may be possible. I asked only to be sure of the new UV cap limit.

I leave my phone in standby all the night without set at boot option for UV settings and it don't reboot (setting are still the same in the morning) :) [MENTION=3750240]stratosk[/MENTION], what are your max UV setting?

Edit: someone of an app/way to alert you of a reboot (I so I will know if it reboot in my pocket without check UV on semaphore app)

Inviato dal mio GT-P3100 con Tapatalk 2
[Nexus 4 Original Android Development] philidor:
My settings after apply
[Nexus 4 Original Android Development] stratosk:
Yes, I remember too. But I will not do it. After this bug founded, I think -175mV is enough.

I have immediate crash at -150mV at lower freqs.

If you don't use PIN lock, you can check your uptime (Settings->About) to check if the phone rebooted.
[Nexus 4 Original Android Development] ratcav:
Hi

Thanks for the kernel.

I've installed it but my led is constantly red (very low brightness, almost invisible)

Does this mean that thermal throttling is always active?
[Nexus 4 Original Android Development] stratosk:
Hi,

Please check for a process that runs constantly and heats CPU.

In idle it should be switched off after some seconds.

This means that your CPU is over 52 degrees all the time. (unless there is a bug :) )
[Nexus 4 Original Android Development] ratcav:
Well, my CPU is at 40 degrees and the led doesn't switch off in idle
[Nexus 4 Original Android Development] stratosk:
How do you measure CPU temperature?

Please try to enable/disable thermal trigger from Semaphore Manager app.

Do you any other apps that use LEDs and may conflict? What's your ROM?
[Nexus 4 Original Android Development] ratcav:
It just switched off!

BTW I use trickster to see the CPU temperature.

Thanks for everything
[Nexus 4 Original Android Development] stratosk:
So, how?

Does trickster show CPU or battery temperature?
[Nexus 4 Original Android Development] ratcav:
After a bit it switched down, I think it needed to settle down a little bit.

Trickster shows both
[Nexus 4 Original Android Development] philidor:
Good Idea we don't need an unstable dead cool device :)

Maybe my device is stable at -175 MV. For now not reboot. But I can live even with only -150 MV :)

I never have a reboot with semaphore kernel w/o UV. If I find it unstable I have only to reduce my UV.

Thanks for all my friend

(PS I remember that with I9000 some peoples
[Nexus 4 Original Android Development] endrekok:
When i get a notification and my device is hot the thermal led confusing the notification's color when I unlock my screen. For example I set gtalk to flashing blue, but when I unlock the screen it turns into green, after the red thermal led is up. Is this kernel problem or ROM? :)
[Nexus 4 Original Android Development] bustem:
every kernel works with any rom..
[Nexus 4 Original Android Development] a g bell:
Hmm:eek::confused:
[Nexus 4 Original Android Development] gianton:
Not correct, flashed it already with CM-10.1 and got stuck at boot animation screen.
[Nexus 4 Original Android Development] stratosk:
I wonder why. I use the same initramfs as stock at the present. And the same kernel configuration

Is it 4.2.2?
[Nexus 4 Original Android Development] android88:
Yes, CM10.1 is 4.2.2.
[Nexus 4 Original Android Development] kwibis:
Didn't CM team change something in their builds so that you need to adjust your kernel for cm specific? Something with ramdisk?
[Nexus 4 Original Android Development] apatal:
Morfic managed to make a kernel that works on aosp and cm, by using anykernel thingy. Might be a good place to start looking, Strat, sir. :)
[Nexus 4 Original Android Development] port76:
works here on latest xylon . I'll let you know how it goes all:D:D:thumbup:;)
[Nexus 4 Original Android Development] stratosk:
Thanks, I can always compare CM's and stock's initramfs.

But, we have some time until this. :)
[Nexus 4 Original Android Development] bodom_hc:
Awesome to see a new kernel :)

will try out after i get out of work :p
[Nexus 4 Original Android Development] a g bell:
Hi Stratosk good to see you here chance you will support swipe to wake in the future ?
[Nexus 4 Original Android Development] lessirey:
Just hope there will be gamma correction enabled pretty soon.. gamma correction is a must for Nexus 4
[Nexus 4 Original Android Development] jarjar124:
If you're talking about touch control thats on the other dev side. Not kernel
[Nexus 4 Original Android Development] a g bell:
Ah OK sorry just get an error saying kernel not supported when trying to run it:eek:
[Nexus 4 Original Android Development] TheeWolf:
Guys, chill. Let him get settled on his device first, and make a more stable version. Right now he needs time to work quietly to improve the kernel as much as possible.

After that, bash at him with all your feature requests.
[Nexus 4 Original Android Development] stratosk:
Fortunately, there is nothing to fix (yet). :)

This functionality is simply not yet supported in Semaphore.

I believe that this first version is pretty stable because it's stock kernel + merged 3.4.40 linux kernel version.
[Nexus 4 Original Android Development] Anubiszx:
I changed from a SGS just a month ago and I was really missing your kernels. It's nice to see you here! :D
[Nexus 4 Original Android Development] tisov:
I just change my old s1 and I find u here :)

Thanks for your work man!

Inviato dal mio Nexus 4 con Tapatalk 2