yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] stratosk:
I understand that you are not referring to me in particular. I just wanted to answer because you posted on my thread.

And of course I don't take it personally. :)

I don't have absolutely any problem with CM (they are amazing devs) and there is no war.

As I said they made their choice. I don't want to play this compatibility game. It's simple as this. :)
[Nexus 4 Original Android Development] ak:
So why you prefer not to have a branch dedicated to cm and why this war versus cyanogen by users and developers?
[Nexus 4 Original Android Development] stratosk:
I've already answered that I don't have time and I don't want to maintain 1 more branch.

I don't know about this war. As I said I don't fight CM. I build a kernel based on CM's for SGS.

I don't like that they diverged from stock on mako kernel, but I fully respect their choice.
[Nexus 4 Original Android Development] Fenvarien:
Yes, I can't transfer with MTP mode too. But I suspect(ed) my windows installation or driver leftovers to be the culprit...

Anyone else with MTP problems?
[Nexus 4 Original Android Development] ak:
Thanks a lot [MENTION=3750240]stratosk[/MENTION] and I'm sorry again for having opened this debate on your thread. :highfive:
[Nexus 4 Original Android Development] Fenvarien:
In my opinion it's the privilege of the developer to decide if he wants to put time and resources into a certain feature or the support of some kind of ROMs. ;)

There's no war going on, just personal decisions of several developers to rather 'play with their kernels' then to 'play the compatibility game', like [MENTION=3750240]stratosk[/MENTION] stated already. :good: :)
[Nexus 4 Original Android Development] melbourne408:
Thanks for helping hope alive, both of you.

Just for my sake, could there be a way to utilize 4.4 code in a way heritable to the legacy of that which shall not be named?
[Nexus 4 Original Android Development] Barbatos19:
With this kernel i cant transfer huge file. but files below 1gb is a flawless. Dont know why. On stock i can copy it all on my desk.
[Nexus 4 Original Android Development] Fenvarien:
I will test it with huge files later on, but I still think that my windows os is bugged somehow.
[Nexus 4 Original Android Development] stratosk:
Could you please test this with stock kernel?

BTW, I have no problem on my Linux box.
[Nexus 4 Original Android Development] miksontije:
Me too. I cant transfer big files too on stock rom. Now on purity with semaphore i can. It start worked to me when i conected mu n4 to pc to work like modem. I try on couple pc and it working
[Nexus 4 Original Android Development] kandarpck:
[MENTION=3750240]stratosk[/MENTION], If I may ask, what's your PC configuration for building a Kernel? :)
[Nexus 4 Original Android Development] Barbatos19:
On stock kernel I got no issue. I mean stock 4.3 kernel. I don't know if this is a ROM issue or kernel issue. Anything you need like log cats just tell us so that we can help :)
[Nexus 4 Original Android Development] stratosk:
Do you mean hardware?
[Nexus 4 Original Android Development] MuertoKo:
For me, any file over 400Mb or so is failing to transfer from/to phone. I've not tried running stock really and probably won't bother trying. Tried reinstalling drivers from scratch and so on to my Win7 pc, but didn't worked either. Any chance to pull a log about this?

When the file is over 400Mb it just pops-up a fail message, not even tries to transfer it.
[Nexus 4 Original Android Development] Skkip:
[MENTION=3750240]stratosk[/MENTION]:

Hi my friend,

first thanks for the true words regarding cm compatibility. It's really hard to follow the cm changes right now, as they are appear to be submitted directly to github and to find which changes are necessary to maintain compatibility.

And now as ever my latest findings:

kgsl_pwrctrl.c: change pwr->default_pwrlevel: I tested the change to idle at min_pwrlevel and there is absolutely no change in either behavior nor battery life :)

By looking around in MSM_RUN_QUEUE_STATS I found an interesting way for cpu util notification. Namely the scaled load:

(max_load * policy->cur) / policy->max

which i implemented in my governor util functions and results in much faster off- and slower onlining while having the same performance. Of course this would need a change in your cpufreq_notify_utilization but I guess it was worth pointing out since it works really great and improves hotplug/battery quiet a bit. You can find it here: https://github.com/SkipXS/kernel_msm/commit/8f4905dc4d2ea51ed307b8369bc16fb4bb1543f8

Regarding hotplug I changed my mind and removed the earlysuspend_handler and set min_online to 1 to allow the usage of cpu0 cstates. To compensate this, I added a touch listener which onlines a number of wanted cpu's on touch (like mpdecision does). The results look very promising performancewise and battery life also improved a bit. If you are interested you could check here: https://github.com/SkipXS/kernel_ms...24c4ce285cd76/arch/arm/mach-msm/dyn_hotplug.c

Edit: Forgot to add that all changes to hotplug and ondemand are long tested on booth my nexus 4 and my nexus 7 (2012)

Edit Edit: https://github.com/SkipXS/kernel_msm/commit/4f1059e80486d7c7e106b31dff1dbd2e9ed4dd38 <-- What do you think about that having user interaction and thermald in mind?

Greetings from Germany
[Nexus 4 Original Android Development] Fenvarien:
As soon as my little daughter is sleeping, I will test this. ;)
[Nexus 4 Original Android Development] soumoks:
Yes even I would like to know your hardware configuration :)
[Nexus 4 Original Android Development] cmajetic:
for the ones with MTP problems:

On Paranoid Android RC2 sabermod I can't transfer any files with MTP. no matter what kernel. my drivers are 100 percent not the problem. it is PA.

it's not semaphores fault. it's the ROM!

Gesendet von meinem Nexus 4 mit Tapatalk
[Nexus 4 Original Android Development] capoooro:
Perfect, after two days with the test kernel 1.7.5 no issues at all. Touchscreen never hangs. Tnx

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 Original Android Development] franciscofranco:
This post is awesome, thanks for the laughs :D
[Nexus 4 Original Android Development] fario78:
This rom rom that works with Eclypse? gives better performance than the hells b39?Where is the download link for the latest kernel, 1.7.5?
[Nexus 4 Original Android Development] kandarpck:
Yes, your hardware configuration, if you don't mind sharing. :)
[Nexus 4 Original Android Development] stratosk:
Almost all my Semaphore for SGS kernels were built on an 7 years old Acer Aspire (Intel centrino duo, 2GB RAM, Fedora 15-17).

Since last year (at last!) I changed my workstation to a desktop PC (Asus, Intel I7 3770, 8GB RAM, 1TB HDD).

When I purchased it I booted it once in Windows 8 (blah), and then installed Fedora. Now, running Fedora 19 with gnome desktop. Recently I throw away the NNVIDIA GT 640 and I use the embedded Intel graphics system (just fine). I always use the latest self built Linux kernel.

Software for building kernels is typical (gcc, git etc). I use Linaro toolchain and I code in vim. I also use gitcola and I use meld (awesome tool).

I use NetBeans for Semaphore Manager development, Chrome for browsing and gmail, Thunderbird for other emails.

Useless info, but maybe a psychologist could make my profile :)
[Nexus 4 Original Android Development] kandarpck:
Lovely :) Thanks

Any particular reason for choosing Fedora over Ubuntu?

And what was the performance drop after removing the graphics card? NVIDIA drivers for Linux are such a pain :/
[Nexus 4 Original Android Development] stratosk:
Hi my friend!

Do you have any explanation why the utilization in term of freq gives better results than in term of load?

About your latest commit, it was discussed in LKML. IMO it's better if ondemand calculates the target frequency and then the policy is applied after. User policy->max or policy->min should not change the calculation method. It's better to use another tunable if you want to change the way that the target frequency is calculated.

Thanks!
[Nexus 4 Original Android Development] stratosk:
Many many years ago I first I was using slackware and then mandrake. Then I started to use Red Hat. Now I use Fedora because:

1) I'm comfortable because of Red Hat

2) Because most people use Ubuntu :p

I don't play games. In my every day use Intel graphics (I think HD 4000) it's just fine - I can't see any noticeable difference. I install the new kernel version reboot and it just works! And less noise!
[Nexus 4 Original Android Development] Skkip:
Well, the explanation is pretty simple. Since I only take the weightened average the cpu utilisation ( policy->util = (policy->util + util)/2; ) this change in connection with my hotplug up_threshold of 75 only onlines a new core when the average frequency is at or above 1512 * 75% = 1134 MHz. Which makes more sense then quickly reacting on only 75% load, which may occur on each frequency, or counting the spikes ;) . These spikes are now flattened and switching between cpus for tasks is reduced, resulting in better cache handling and no time needed for switching. (I hope this is understandable)

About the latest commit. But what happens if a user changes scaling_max_frequency to 1026 MHz for example to save battery. With the old approch every load above:

1026 MHz / 1512 MHz = 67% will result in 1026 MHz being used, which makes up_threshold useless and scaling really suffers from this. With my approach this won't happen.

Maybe you can comment on this :)
[Nexus 4 Original Android Development] gianton:
Running v0.5.5 build with Linaro CM10-1 trailblazerz11's ROM, very smooth and fast.

Thanks for your work Strato!
[Nexus 4 Original Android Development] Mercado_Negro:
Yes, set permissions to rwx-rx-rx.
[Nexus 4 Original Android Development] Elting:
It seems that the 0.5.5 knows only two states : 1512 and Deep Sleep. So the battery drain is very bad for me...
[Nexus 4 Original Android Development] pixiebob:
what's the echo command to enable only 2 core, thanks by advance (mpdecision is off)
[Nexus 4 Original Android Development] cryingrock:
I set the permissions to 755 and rebooted but still not working:(

Sent from my Nexus 4
[Nexus 4 Original Android Development] Mercado_Negro:
I wonder what the problem is. As per http://xdaforums.com/showpost.php?p=40862047&postcount=438 this should work. I'm doing it with ROM Toolbox (Paid) but there's ROM Toolbox Lite https://play.google.com/store/apps/details?id=com.jrummy.liberty.toolbox&hl=es though I'm not sure if it has the Scripter
[Nexus 4 Original Android Development] stratosk:
Something went wrong in my release. Anyway, it works as it should now.

So, you have to build the module with exactly the same version number as the kernel.

Init process will run it only with 'secure' permissions: not group/world writeable and executable.

Since your system is up, you may load as root with any permissions from any directory
[Nexus 4 Original Android Development] stratosk:
Works fine here. Please check your config. Any apps that handle CPU freqs?
[Nexus 4 Original Android Development] masterchif92:
So mpdecision must be on or off?

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Original Android Development] pitjago74:
On is the normal:D

Enviado desde mi Nexus 4 usando Tapatalk 2
[Nexus 4 Original Android Development] stratosk:
mpdecision must be on.

I didn't change anything in kernel to substitute mpdecision.

I just post an east method to disable it if you want.
[Nexus 4 Original Android Development] masterchif92:
U can post raccomended setting by u! I know that I haven't the phone but I want to try

Inviato dal mio Nexus 4 con Tapatalk 2

---------- Post added at 08:29 PM ---------- Previous post was at 08:28 PM ----------

U can post raccomended setting by u! I know that you have't the phone but I want to try

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Original Android Development] stratosk:
Recommended setting for mpdecision? I recommend to have it enabled.
[Nexus 4 Original Android Development] Tylog:
:D

Tapatalk
[Nexus 4 Original Android Development] a g bell:
sorry for OT but What are the disadvantages of having mpdecsison disabled because my battery life doesnt seem greatly reduced, or my phone over heating:confused:
[Nexus 4 Original Android Development] stratosk:
You will not have 1026MHz when you touch the screen, reduced battery life (maybe not to much, depending one your usage) and more heat.

Of course as you noticed the lack of mpdecision will not blow up your phone.
[Nexus 4 Original Android Development] snOwjAwk:
Hey, I'm just wondering how to activate touch control. I got the app and the kernel app. In the touch wake app it doesn't work and in the kernel app I can activate it but it doesn't take affect (I guess it does I'm just too stupid to use it ) .

Ty for any help.:)
[Nexus 4 Original Android Development] a g bell:
Thanks,ok no smooth ui but 4cores running:)

And no big explosion yet:D
[Nexus 4 Original Android Development] stratosk:
Touchwake in Semaphore is different from touch control app.

Touchwake is an in-kernel implementation that enables a wake lock when the screen goes off (because of inactivity). The kernel holds the wake lock for a period (configurable) and gives you the opportunity to 'wake' your device touching the screen.

Touch control app uses a kernel module - not Semaphore compatible - to do something similar.
[Nexus 4 Original Android Development] snOwjAwk:
Thanks for the noob friendly and fast response. So when the screen is locked and the timer is over I have to hit the screen ? Because if I do that nothing happens.

---------- Post added at 09:36 PM ---------- Previous post was at 09:22 PM ----------

Oh I think I misunderstood u, with 'waking' the device u didn't mean turning on the screen, did you
[Nexus 4 Original Android Development] stratosk:
Maybe, I'm too tired and my brain is not working. I'm not sure I see the difference.

About your latest commit.

When user changes policy->max, he/she/it says: "I want maximum scaling frequency = policy->max". He doesn't say "Also change the calculation algorithm". If you want to change calculation algorithm is better to introduce a new tunable (if is absolutely needed). User may adjust the new tunable to change the calculation method.
[Nexus 4 Original Android Development] DontPushButtons:
This thread has been absolutely awesome with all the code discussion lately. Love learning about this stuff.

Thanks!
[Nexus 4 Original Android Development] stratosk:
Please find test 1.7.5 few pages back.
[Nexus 4 Original Android Development] Skkip:
Now, I get your point. Although I thought the algorithm means:

freq_next = max_load * policy->max / 100;
Calculate the next frequency based on the current load dependent
on the maximum [b]available[/b] cpu frequency

instead of

freq_next = max_load * policy->cpuinfo.max_freq / 100;
Calculate the next frequency based on the current load dependent
on the maximum cpu frequency, which may or may not be available

Thanks for your clarification :)
[Nexus 4 Original Android Development] fario78:
the 1.7.5 does not work in eclypse, is nothing black screen.Please link the 1.7.5j for use with eclypse?
[Nexus 4 Original Android Development] stratosk:
I'm sorry there is no 1.7.5j. 1.7.5 is a test version. Please use 1.7.4j instead.
[Nexus 4 Original Android Development] fario78:
1.7.4j Eclypse works very slow, 11000 and 3500 AnTuTu quadrant

Enviado desde mi Nexus 4 mediante Tapatalk
[Nexus 4 Original Android Development] stratosk:
Then, 1.7.5 will be 'slow' too. The only change is a bug fix in touchwake.
[Nexus 4 Original Android Development] fario78:
Which is better 1.7.1 or 1.7.4?

Enviado desde mi Nexus 4 mediante Tapatalk
[Nexus 4 Original Android Development] stratosk:
1.7.1

Semaphore is getting worse and worse. So, please try to use old versions.
[Nexus 4 Original Android Development] wozn:
Can I find a 0.1 alpha hosted somewhere?
[Nexus 4 Original Android Development] lilgiz:
Lol, funniest post I've read in a long time, or I've got a weird sense of humor.
[Nexus 4 Original Android Development] fario78:
For now, the 1.7.1 rom j eclypse perfect with very fast and stable, see battery consumption, very good job.
[Nexus 4 Original Android Development] thracemerin:
You know he was being sarcastic, right?

Also benchmark scores are not always a good indication of real world performance.
[Nexus 4 Original Android Development] puncha1580:
The kernels are getting really worse (better) ; they're absolutely useless(full). I managed to get 2.5 hrs OST with a massive (only) 24% drop.

Was reading an ebook thru that time.

And ah! Yes!! Who gave you that sense of humor???
[Nexus 4 Original Android Development] hughfollett:
Keep in mind that benchmarks mean nothing. 1.7.4 is smooth and flawless. I would go for the latest version with bug fixes and improvements, not the latest with more placebo ;)

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 Original Android Development] bantamdraper:
I'm trying out Semaphore after using hells-core and neo and I have a strange problem when benchmarking in Antutu. After only getting scores of under 19000, I noticed that Antutu is showing my frequency running as 1242, despite the fact that I have it set at 1512 max. I changed to a different max frequency and then back to 1512 and saved, ran Antutu again, and it's still reporting it at 1242 MHz. This seems to be the only kernel where I have this issue. :confused:

Anyone have an idea why it might be sticking at the wrong frequency?
[Nexus 4 Original Android Development] a g bell:
Thermal throttling maybe:eek:
[Nexus 4 Original Android Development] snak3ater:
May be due to Throttling..Set 1512 as max Freq & then run Antutu after some time..Never experienced this issue before..Freq drops down only when the device is too hot at my end
[Nexus 4 Original Android Development] ak:
Do you have restored default ramdisk?

neo kernel remove thermald daemon.

i dont know if hell make the same.
[Nexus 4 Original Android Development] bantamdraper:
Ahhh, that explains it. Hadn't run into that before while benchmarking.I let the phone sit for a little while and ran Antutu again. It's reporting 1512MHz now. All good now. Thanks :)

Yep, I had the default ramdisk. I did a clean flash of Purity with stock kernel before I flashed Sema. Thermal throttling :good:
[Nexus 4 Original Android Development] AhmedFaiz:
[MENTION=3750240]stratosk[/MENTION] will you be considering adding fast charge I really find it useful in my daily use, that's the only thing i miss here. Or is there any technical reason you don't b want to add it?

Thanks for the a nice balanced performance on kernel.:)

N⁴/PA3.99_RC2 (NIGHTLY) / semaphore 1.7.5 / V4A
[Nexus 4 Original Android Development] gialakias:
Stratosk are you attending? https://www.eventbrite.com/event/8258267701
[Nexus 4 Original Android Development] stratosk:
I don't think so. But I will recheck it. Generally I'm not comfortable making changes that may be against technical specifications.

I didn't know about it. Thanks for the information!

Though, I'm not sure I can attend it. Too much work in my real job...
[Nexus 4 Original Android Development] AhmedFaiz:
I am sure there are few how already wrote in this thread for that feature. Recheck is nice.

Thanks.

N⁴/PA3.99_RC2 (NIGHTLY) / semaphore 1.7.5 / V4A
[Nexus 4 Original Android Development] alen1901:
would you consider adding a row scheduler? with any other scheduler, over time, android becomes like less smooth (uptime 300 hours and more), but with row you never get that.
[Nexus 4 Original Android Development] thracemerin:
Stratosk has answered this in the past, ROW has not been added to Linux mainline because in testing by the maintainers there is no appreciable increase in performance over the stock schedulers, this is the reason he hasn't implemented it.
[Nexus 4 Original Android Development] alen1901:
no thanks for today, and im away from phone. so thanks for the answer. i really didnt saw the answer on my question. but we dont really need performance improvements on scheduler. or? i thougt row was coded from ground up just for mobile devices so it would work better for them.
[Nexus 4 Original Android Development] thracemerin:
I would assume that they did testing on flash memory devices which would cover mobile phones even if they didn't test mobile phones specifically. I've never seen a significant difference in performance between the various schedulers on the N4 including ROW.
[Nexus 4 Original Android Development] alen1901:
Neather do i, but in long term usage, row was more consistent to me, less slowdowns at high times without a reboot. Might be a placebo though. :D
[Nexus 4 Original Android Development] Barbatos19:
What happened? Everybody disappear after 4.4 release hahahaha.
[Nexus 4 Original Android Development] stylez:
So impressed with combo with Slim 4.3

I'm mobile so will upload pics later.

My setup is sync always on / all social media 3 hour sync / 98 user installed apps / tasker for auto rotate & gps selected apps.

Kernel default settings.

25% battery still was left but had to charge as appointment today.

Screen on : 3:43

Time from charge: 10:45

If I had left through sleep I can normally get through a 9hr sleep on aprx 12% so real time from charge if hadnt of had to charge would be aprx 20+ hours.

More than substantial for a day out and home charge.
[Nexus 4 Original Android Development] stratosk:
I'm here... :)
[Nexus 4 Original Android Development] snak3ater:
Lol..yeah..I hope all devs start working on 4.4 sources soon.Can't stay away from my favorite kernel..If it takes long for Stratosk,i might revert back to 4.3 :D Right now checking out 4.4 :highfive:
[Nexus 4 Original Android Development] AhmedFaiz:
[MENTION=3750240]stratosk[/MENTION] I am on 4.4 aosp rooted is fine to flash the kernel or will have to wait for 4.4 builds?
[Nexus 4 Original Android Development] stratosk:
I have no idea. :)

I will wait for the official images for N4 (and kernel source)
[Nexus 4 Original Android Development] snak3ater:
Let me know what happens after flashing this kernel on 4.4 :D
[Nexus 4 Original Android Development] ciprianruse88:
[MENTION=3750240]stratosk[/MENTION]

Had a reboot when I was taking some pics with front camera.Purity rom+ 1.7.5 .UV settings attached(fast chip).Cheers !:thumbup:

Last_kmsg - https://db.tt/EccEbbFw

"Energy and persistence conquer all things." - Benjamin Franklin
[Nexus 4 Original Android Development] AhmedFaiz:
Haha not in a mood to explore without guidance ,enjoying this pure stock experience really nice all set to take off from here into 4.4 development? waiting for n5 too?
[Nexus 4 Original Android Development] stratosk:
I'm sorry, I can't help.

It's the known camera issue (stock). I am not familiar to that code.
[Nexus 4 Original Android Development] ciprianruse88:
Thank you Stratosk! Let's see if 4.4 brings a fix for this bug :thumbup:

"Energy and persistence conquer all things." - Benjamin Franklin
[Nexus 4 Original Android Development] stratosk:
I also hope so. There are some tricky bugs in stock code.
[Nexus 4 Original Android Development] Fenvarien:
[MENTION=3750240]stratosk[/MENTION] Regarding the MTP file transfer, my issues only exist with my windows machine. When I connect to my netbook with xubuntu there's no problem or failing large files. :good: :)

Semaphore 1.7.5 (test) is running perfectly with Purity ROM here!
[Nexus 4 Original Android Development] Barbatos19:
Glad for you buddy. Haven't fix mine.
[Nexus 4 Original Android Development] fario78:
Hello kernel for better performance in the Purity rom?
[Nexus 4 Original Android Development] ak:
@stratosk

i have merged these commits and i have resolved crash with front camera.

I don't know if it works for all combinations rom and kernel.

msm: camera: Check if client is NULL before calling ion_free
msm: camera: Enable pixel line buffer for ispif.
msm: camera: Fix mctl release crash issue.
msm: camera: Fix camera crash when ctrl_q is empty
msm: camera: Fix camera crash in msm_open_config
[Nexus 4 Original Android Development] stratosk:
Thanks!

What's the origin of those patches?