yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] thracemerin:
It's not a screw up, the CM team upgraded to a different version of HWcomposer which requires different graphics drivers from the ones that are shipped with AOSP this was done intentionally, not to break custom kernels but to attempt to fix some other issues related to mako and JSS/JLS, the end result was that custom kernels are no longer compatible, the CM team has never supported or recommended using other than the kernel that ships with the ROM so things being broken if you use a custom kernel is not surprising.
[Nexus 4 Original Android Development] GalaxyGusta:
Hi i wanted to try this kernel because of the review seems nice :D

but I don't understand how to calibrate the screen like i did with franco kernel

i was using the 44_bundi22 profile if anybody can tell me how to apply it in the number I will appreciate that

https://docs.google.com/spreadsheet/ccc?key=0AoDp2qRui0u0dGE4T2gtSDBTRHVFSldPS2RrX1Rya0E#gid=6

its here number 44 how do it apply those numbers?
[Nexus 4 Original Android Development] manpildo:
http://xdaforums.com/showpost.php?p=44132536&postcount=2364
[Nexus 4 Original Android Development] GalaxyGusta:
Thanks that worked now I will test if its batter for my battery :)

one thing i didnt understood is what "XX" is
[Nexus 4 Original Android Development] snak3ater:
Franco-Semaphore Gamam Values

Thanks to Anrikus for the spreadsheet
[Nexus 4 Original Android Development] californicated:
Disabled blue led for touchwake. The white led for whatsapp is working fine again. Strange strange, but I'm fine with the workaround
[Nexus 4 Original Android Development] coloxim:
Sorry buy for 36g rom which kernel I've to use?

Inviato dal mio Nexus 4 con Tapatalk now Free
[Nexus 4 Original Android Development] manpildo:
I created a few colour profile scripts using the code asasione provided there, so all credit goes to him. It will save you from punching in the numbers and you can change your colour profiles by simply running the script in Script Manager or Terminal Emulator.

To use it in Terminal Emulator type:

su

sh /storage/emulated/0/profile_name.sh (if you put the files inside a folder, then use the full directory location)

To use it in Script Manager:

Choose the file, tap on "Su" skull and tap "Run". Done.

So far I made only 5 presets for Kel Ghu (gamma 2.2), obsanity_AMOLED, Archmag3, bundi22 S3 and bundi22 iPhone5.

If somebody finds this useful and wants some other color profiles, then I can make it.

EDIT: Added PA_Halfbreed and Holoblue.
[Nexus 4 Original Android Development] gpvecchi:
Guys, I would really like to convert faux to franco gammas, but there's still something that is not clear...

I asked Franco about the 2 unknown values and he said that he leaved the untouched, so 1/1 for red and green and 0/3 for blue.

But converting this way gives different results (tried with colorimeter); it seems that 1/1 for all is more similar.

Trickster mod exposes some other values that are not coded nor in Franco nor in Semaphore.

This thing is driving me mad... :silly:
[Nexus 4 Original Android Development] twowheeler:
I will keep an eye out to see if i can help you. But what I want to say: thanks for doing this, it really helps if somebody with the proper tools can change these settings. Thanks and keep it up!
[Nexus 4 Original Android Development] coloxim:
Can I flash on last aokp?

Inviato dal mio Nexus 4 con Tapatalk now Free
[Nexus 4 Original Android Development] meangreenie:
I think Franco uses lg colours for default so the unsetable values will be whatever lg colours are.. 0 and 2 respectively for all 3 colours if i recall correctly. Also check the order of the other values by looking at the numbers to check each setting is being set the same, i think franco swapped the labels too.
[Nexus 4 Original Android Development] apatal:
Should be fine. Use 1.7.1j though. Oh and better research about a display color fix. Some users have been getting funky colors after using non-cm kernels on cm and aokp lately.
[Nexus 4 Original Android Development] awacker89:
Yes, but you need to flash the CM color fix at the same time as AOKP is now on CAF source for kernel libraries.

https://www.dropbox.com/s/36ydmd1kniy7wgz/cm10_colorfix-signed.zip

[MENTION=3750240]stratosk[/MENTION], any way we could add this to OP? I struggled with an unusable ROM for quite a while today until I found this information out for myself.

---------- Post added at 05:49 PM ---------- Previous post was at 05:48 PM ----------

Looks like you beat me to it! See my post for a link. I can confirm that you have to flash the fix to run ANY custom kernel not built for CAF source.
[Nexus 4 Original Android Development] cantevencode:
Yeah. Depending on which version you flash you'll need the color fix. I believe the official nightlies and whitehawkx's unofficial need it. Kecinzer's nightlies don't need it and I'm not sure about Mark Landis's builds but I think they do too
[Nexus 4 Original Android Development] Barbatos19:
How about on PA 3.99 rc2? Does it need to flash a color fix too? I got light color but I used this value on semaphore manager app.

0 39 119 0 6 0 5 0 2
[Nexus 4 Original Android Development] cantevencode:
I don't think pa uses any caf so I don't think so. The color fix is for if your colours are inverted but the correct brightness
[Nexus 4 Original Android Development] Barbatos19:
oh i see. thanks :)
[Nexus 4 Original Android Development] nemanja066:
Vibration is the same in both cases. I 'm not noticing any difference.:o
[Nexus 4 Original Android Development] Barbatos19:
i noticed that if i used terminal emu to config the value, semaphore manager app LCD calibration wont change. And do you think there will be no problem if i use terminal emu and on the other hand the gamma value on semaphore manager app is different from the one you give?
[Nexus 4 Original Android Development] manpildo:
I noticed this too. You can make sure your new values got applied correctly by checking these four files:

/sys/devices/platform/kcal_ctrl.0/kcal

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

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

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

or alternatively you can choose one of the scripts (doesn't matter which one) and add "-p" at the end of the command line, for example: sh /storage/emulated/0/pa_halfbreed.sh -p (the -p gives the command to show currently applied values, this is probably quicker than going through the files manually)
[Nexus 4 Original Android Development] Barbatos19:
got it and its in there :) thanks mate :). check PM i replied there too a while a go.

BTW are you having issue transfering files on laptop using this kernel? i noticed that since i transfered from stock PA kernel to Semaphore 1.6.5 i got error while transferring files on my laptop using usb cable. But then when i flashed 1.7.1 i can transfer files to the laptop but with atleast 1gb in size. more than that the transfer process hangs for more than 30mins and will be stopped if i remove the usb cable.
[Nexus 4 Original Android Development] coloxim:
Thanks guys... Today I'll try, I've last official nightly..

So is better j version?

Inviato dal mio Nexus 4 con Tapatalk now Free

---------- Post added at 08:36 AM ---------- Previous post was at 08:34 AM ----------

Thanks guys... Today I'll try, I've last official nightly..

So is better j version?

Inviato dal mio Nexus 4 con Tapatalk now Free
[Nexus 4 Original Android Development] cantevencode:
Yes
[Nexus 4 Original Android Development] deeppans:
Stock version

[MENTION=3750240]stratosk[/MENTION]

I know you only use stock rom, but which version? The one that is provided by Google (Factory Image JWR66Y) or do you build it using Android repo.

Thanks
[Nexus 4 Original Android Development] stratosk:
I use Google binaries JWR66Y.
[Nexus 4 Original Android Development] Slymobi:
[MENTION=3750240]stratosk[/MENTION]

Hi

Do you know why slimport ( adapter to connect phone to TV via HDMI ) wouldn't output and cause reboots whilst connected. I ask because it works from stock jw ( not tested semaphore jw ) and also on AKOP with their stock kernel but then the only change I make is to flash your js 1.7.1 latest kernel only for the above to occur ( no output and constant reboots until I disconnect the adapter.

Other than this the kernel runs perfect by the way.

I'm currently away so cannot provide logs etc but just asking in general.

cheers.

Sent from my Nexus 4
[Nexus 4 Original Android Development] manpildo:
Just broke my battery record on semaphore. I had auto brightness, touch control, google now, location services and constant wifi scanning on the whole time.

Total: 1d 15h 50m

SOT: 4h 22m

My previous best was barely 4h of SOT, average for a long time has been 2-3hrs.
[Nexus 4 Original Android Development] stratosk:
Hi,

I have absolutely no idea (since I didn't change anything related) and I have no hardware to test it.

If it's convenient for you, please post kmsg and last_kmsg. Please also test (if possible) with stock jwr66y and Semaphore.
[Nexus 4 Original Android Development] aLPaSLaN07:
Vibration is set to 100. The option under it , which is test, proves it is 100 but when a call comes, it vibrates like it is 60..
[Nexus 4 Original Android Development] -iNSiGhT-:
Did you try to "read system settings" in Semaphore manager (in option menu) after configuring gamma values?

Paranoid mako
[Nexus 4 Original Android Development] manpildo:
Yep, tried it now and it works. I suggest doing so after applying one of my scripts, otherwise the settings won't stick after reboot and the colour profile will need to be reapplied.
[Nexus 4 Original Android Development] apatal:
Hi [MENTION=3750240]stratosk[/MENTION] got a random reboot after turning on torch. I'm using 1.7.1j on GnOmE ROM and GravityBox. Here's the last_kmsg. Kindly check please. Thanks.
[Nexus 4 Original Android Development] Slymobi:
Will do tests as requested asap. it was more a general question and you answered as I expected really. Thanks for clarifying.

Sent from my Nexus 4
[Nexus 4 Original Android Development] stratosk:
Again, this weird line:

Last boot reason: hw_reset

The only path in the kernel that should produce this is

/sys/module/lge_panic_handler/parameters/gen_hw_reset

If you echo 1 to that file you will produce a hw_reset. I don't know which userspace process does this hw_reset and for what reason. Maybe thermald?

Did your phone was hot when you used torch?
[Nexus 4 Original Android Development] soumoks:
I had the very same problem when I enabled uv and used the torch, the problem doesn't seem to appear when uv is disabled.. The led uses lot of current it seems.
[Nexus 4 Original Android Development] -iNSiGhT-:
I think too it's because of UV. Because with 137500 uV on higher frequencies, torch works great and no reboot, but if I set 150000uV, I can have reboot.

Paranoid mako
[Nexus 4 Original Android Development] gpvecchi:
This helps a lot, I'll make some test.

I even noticed that trickster doesn't sync with semaphore app, too...

What are the stock values for exponential lightning? I think I read them some page ago, but I cannot find them...
[Nexus 4 Original Android Development] apatal:
Not particularly. And I was in an air conditioned room then. Also I don't UV. Hope this helps. :)
[Nexus 4 Original Android Development] cmajetic:
with GMD gesture control from playstore you can turn off the screen by gesture and turn on with touch control again. awesomeness :D best kernel no question!

[MENTION=3750240]stratosk[/MENTION] you said that you will change the touch to wake to max 90 seconds but in your app you can change to much higher values. does it work? didn't test it yet but does it work with 5 minutes?

Gesendet von meinem Nexus 4 mit Tapatalk 4
[Nexus 4 Original Android Development] cantevencode:
Could the torch require the camera to work? There's a bug in 4.3 that means the phone sometime reboots when the camera is used. I've had this several times with snapchat and others have experienced it with similar apps. I can't find the bug tracker link but it's fairly common and it's put down as a hardware reset in the last_kmesg
[Nexus 4 Original Android Development] ioucorsa:
i have uv -175000 and tested the torch and nothing happened...

stock rom with semaphore...
[Nexus 4 Original Android Development] snak3ater:
Setting it up to 5 mins would just kill the purpose of touch wake I guess..it would drain the battery a lot as the device would be kept awake for 5 whole mins every time screen goes off due to inactivity..
[Nexus 4 Original Android Development] stratosk:
Yes, Semaphore Manager app allows values for touchwake delay up to 5 min.

AFAIK, yes. You have to use camera interface to enable torch through android framework.

Also, it seems in the logs that everytime you enable torch VFE interface is used. VFE (Video Front End) is used in camera.

So, maybe you are right and there is a bug in VFE.
[Nexus 4 Original Android Development] gpvecchi:
Sorry, which values do I have to set to have the stock backlit? I don't understand how new brightness works... :silly:
[Nexus 4 Original Android Development] aLPaSLaN07:
FauxSound support would be awesome..

https://github.com/faux123/mako/commit/911a80eb10df7b1f0c120ae29137e1b682f8ab7e

:)
[Nexus 4 Original Android Development] stratosk:
Default values are equal to stock.

Min brightness = 2

Max brightness = 114

Linear mapping mode
[Nexus 4 Original Android Development] apatal:
Or you can just use Viper4Android. Awesome stuff. ;)
[Nexus 4 Original Android Development] gpvecchi:
Thanks! If I uncheck linear, I just get a dark screen, is that right?
[Nexus 4 Original Android Development] stratosk:
Yes, it's OK. It's the exponential mapping method. You may need to increase the min brightness if you want to use it.
[Nexus 4 Original Android Development] PetritH:
I just can't describe how good this kernel is, i like to switch betwen them just to try but I always come back to semaphore.

thanks again, much appreciated
[Nexus 4 Original Android Development] stratosk:
Hi, my friend!

Thanks for sharing your ideas.

If I understand correctly the new stuff here is that you check if the cpu is boosted or not. My concerns:

1) You make boost true on every input event. My approach in ondemand boosts the CPU if the load is over touch_load_threshold

2) Did you notice any issues before this change? I mean, did you notice that boosted CPU goes offline? Usually when user interacts with device the CPU load increases. I don't know how often this will happen.

Please let me know if I miss something here.

Also, if it's possible, can you please send a diff or a patch (or even your commits to github). It'a a lot easier to read patches because I can see the diff at once. :)

Thanks again!
[Nexus 4 Original Android Development] gpvecchi:
Well, ok, I tested conversion to Franco's gamma: thanks to everyone for informations provided.

The correct conversion is: greys, mids, black, 0, contrast, brightness, saturation, white, 2 for all colors.

I dropped trying to convert to Faux, there are too many values. A simply way could be convert from Franco to Semaphore and then read results in Faux using Trickster app.

ToDo: perfectly calibrate display (I'm near!); understand what effect have those 2 unknown values to gamma.
[Nexus 4 Original Android Development] californicated:
More perfect than this? :eek:

http://xdaforums.com/showpost.php?p=46177864&postcount=4082

Looks awsome
[Nexus 4 Original Android Development] gpvecchi:
Well, it depends what you mean: I mean something like a calibrated professional monitor for photographer...

Correct gamma, color temperature, gamut...

Usually comsumer monitors are blueish (around 8000k insthead of 6500) because they are more impressive: in this case you'll like PA Halfbreed more.
[Nexus 4 Original Android Development] californicated:
Well, I'm curious about the results :)

btw I don't like PA halfbreed ;)
[Nexus 4 Original Android Development] N4Solomon:
Flashed this kernel last night, absolute love it because of the drain rate and the answer call feature but I have a serious problem with the Wifi......It connects and everything works then over some time Wifi and the whole "Settings" app fail to open then the wifi disconnects and I can't reconnect because settings won't open......Doing a restart does fix the issue temporarily but then it happens again and it only happened since flashing this kernel.

I was using Hellscore before and I dirty flashed the kernel but then I thought it was the dirty flash so I flashed the latest 4.3 Carbon nightly booted it up then redownloaded and reflashed the Semaphore kernel and the exact same thing happens. Any ideas why this is happening?
[Nexus 4 Original Android Development] coloxim:
Someone can explain what is it exponential in LCD calibration?

Inviato dal mio Nexus 4 con Tapatalk now Free
[Nexus 4 Original Android Development] ismethajametovic:
I tried flashing the 150 kernel for cm10.2 4.3, but all i get is a blank screen or a blueish screen.
[Nexus 4 Original Android Development] manpildo:
Why do you want to use an outdated build from July? And by the way the latest CM versions don't play nice with most custom kernels. I would suggest you search for a kernel having a separate CM version (I know hells-core has it, don't know about others) or stay on stock CM. Refer to this post for an explanation.
[Nexus 4 Original Android Development] shubu000:
Hi straosk, just wondering if the cpuidle fix from CAF fixes the problem on the jss branch?
[Nexus 4 Original Android Development] stratosk:
Hi,

There are many fixes in CAF.

Could you please clarify which one? What is the problem in jss branch?
[Nexus 4 Original Android Development] KingBeike:
Hi Stratosk,

as you told me, i deactivated Touch Control completly, but the random soft reboots are still there, got the last a few seconds ago :crying:.

I think it is not Rom related, because they are present on PSX and Cataclysm ROM, both with a full clean flash :(

Any help? Do you know a way to figure out the Problem?

I really want to use your kernel, because no other kernel reaches the UI Smoothness! No micro lags in transitions on the homescreen, as on the other kernel around the forum ;)
[Nexus 4 Original Android Development] stratosk:
Hi,

So, we exclude the touch control.

Maybe you could try to get a logcat. I hope the logcat messages survive after the softreboot.

Please enable logger in Semaphore Manager app and restart the phone. Please make sure that logcat is working and wait for the next reboot. Then get the logcat. Which Semaphore version do you use?
[Nexus 4 Original Android Development] KingBeike:
Hi, okay, i will do this! i use your latest 1.7.1, JWR version.

Logcat is the Main log in the app syslog?
[Nexus 4 Original Android Development] stratosk:
I guess so, but anyway send them all (because it's easy :) )
[Nexus 4 Original Android Development] shubu000:
Hi I'm referring to the change log for 1.7.1 "patch from CAF for possible fix on cpuidle". Just wondering if you mean the idle freeze bug with the jss builds

Sorry that I wasn't clear :)
[Nexus 4 Original Android Development] stratosk:
Well, I'm not sure about the freeze bug.

I just wanted to resolve an issue I saw in some logs and I thought that this patch was related.
[Nexus 4 Original Android Development] californicated:
Today me screen became unresponsive for a few seconds (no deadlock) and went to normal so that I could write a message. When receiving a call the screen became unresponsive again (fortunately call was working fine). I was able to turn screen on and off, and press power button, but not a single touch or swipe would work. Had to reboot the phone.

Issue with touchwake? Deinstalled TC days ago and already flashed new version of my rom. So that's not the cause.
[Nexus 4 Original Android Development] snak3ater:
Screen going unresponsive,only screen on & off working..This is a common issue of Touch Control App..The fix is a simple reboot or just touching your screen with all of your fingers..Screen would come back to normal after a few secs :D

I was having this problem a lot with other kernels but in Semaphore,never faced this issue yet
[Nexus 4 Original Android Development] californicated:
Well, I know of this issue in connection with Touch Control. That's why I mentioned that it's not even installed on my phone :cool:
[Nexus 4 Original Android Development] stratosk:
What is your ROM? Semaphore kernel version?

Also please post last_kmsg and kmsg.
[Nexus 4 Original Android Development] Skkip:
[MENTION=3750240]stratosk[/MENTION]:

Hi, my friend!

Finally got the time to set up my git repo again. So before I start to talk about the changes, here it is : https://github.com/SkipXS/kernel_msm/commits/JWR/Y :)

about 1.) I modified this behaviour in the latest version. I only boost the frequency if load is above lower_threshold

about 2.) I noticed a cpu going offline in browser or chrome. In such a cpu bound app i prefer to keep the cpu online as long as possible, because every touch a huge numer of threads gets executed which scales nicely with more cpus.

Some new changes in my repo

3.) HOTPLUG: I removed the onlineing of cores on late_resume because after the implementation of something very similiar to your "up_all"-function i got my first SOD ever. I guess there is a race between normal hotplug operation and this fast onlineing which could cause SOD and reboots. Since I don't need it i removed it, because unlocking the phone is heavy enough for my "fast"-hotplug to kick in (using policy->util = (policy->util + util)/2; in cpufreq_notify_utilization). Edit: a lock would help too, i think :)

4.) HOTPLUG: I changed up_one and down_one to boolean to only reset last_change_time if onlinening or offlinening was successful. Because if we hit the max or min checks we would delay next hotplug event for 500msec even though we didn't change anything.

5.) CPUFREQ: The benefit of having a boost in cpufreq.c is that my ondemand only boosts cores available at the moment. If my hotplug decides to online another core it won't be boosted and may better scale for the remaining load.

6.) ONDEMAND: I did quite a bit of reworking here to allow boosting if a cpu hits up_threshold. My idea was that if a cpu gets such a high load the other cpus should try to help it, because lower frequencies are most benefitable for power consumption and heat.

7.) ONDEMAND: I also added boost_percent which adds to current load instead of having a fixed value. This way I use less high frequencies and am able to boost higher. If for example the cpu load is 72 and you register a touch the current implementation will only boost it to 75 which may or may not be enough. On the other hand the cpu will stay with a load of 75 for the next 1.1sec. With my approach, it allows the cpu to scale down but keep boost.

Ok, hopefully I haven't forgot anything and my ideas are understandable :) Looking forward for your feedback.

Changes are here: https://github.com/SkipXS/kernel_msm

;) and of course have a nice day
[Nexus 4 Original Android Development] stratosk:
Hi, my friend!

I will try to comment your points, although your code diverged from mine and maybe it's useless (for both of us) to compare the 2 drivers.

3) I've never had similar issues. I guess it was something in your code.

4) My code already handles this.

5) I think that a new onlining CPU should participate in boost if it's load is above the threshold.

6) I'm not sure I understood the logic here.

7) It's not the desired behavior for me. With my approach the CPU can also be boosted or not within touch duration if the load is above touch load threshold or not.

Have a nice day and thanks for your feedback and ideas!
[Nexus 4 Original Android Development] californicated:
There is no last_kmsg :rolleyes:

Rom is latest Rasbeanjelly, Semaphore kernel v1.7.1j
[Nexus 4 Original Android Development] stratosk:
OK, np. Please try next time if this will happen again.
[Nexus 4 Original Android Development] KingBeike:
Hi Stratosk, there is not logcat, i get only an empty text file :(. Last_kmsg and dmesg are there. But i think there a no important information in?