yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] senthilrameshjv:
How did i miss this kernel so far.. This one sleeps like baby.. Couldn't attach screen shots bc of some issue.. But without doing anything spl, i got just a straight line during my sleep of 7 hrs..

I'm down to 54 p.c and my screen on time is already 2.15 hrs.. On data, not wifi..

Gummy rom with semaphore 1.7.1
[Nexus 4 Original Android Development] Barbatos19:
deleted

---------- Post added at 03:55 PM ---------- Previous post was at 03:48 PM ----------

Got unexpected reboot. This happens after i press the power button to wake the phone but suddenly it doesnt open. then it open for about 10sec then it reboot itself.

http://www.mediafire.com/download/vr85yo1znbn1vy3/last_kmsg+(1) here' the file. cant upload the files on the attachments.
[Nexus 4 Original Android Development] stratosk:
I'm afraid, I can't do anything for this. You can't distinguish in kernel that the suspend cause by screen inactivity or by other software.

So, power button is the only solution to turn off the screen and touchwake.

I'm sorry, I can only see there a normal reboot.
[Nexus 4 Original Android Development] senthilrameshjv:
Hi [MENTION=3750240]stratosk[/MENTION],

Im using multi rom but I'm not able to flash your kernel on primary rom as it doesn't have kexec patch.. Are you planning on adding it any time soon?
[Nexus 4 Original Android Development] stratosk:
Hi,

I'm sorry, not in my plans.
[Nexus 4 Original Android Development] Skkip:
[MENTION=3750240]stratosk[/MENTION]:

Hello my friend! How are you? :)

I was working with the ondemand governor and I think i found a bug / unwanted behaviour with the sampling_down_factor. If a cpu hits the up_threshold and the sampling_down_factor kicks in, the delay gets multiplied with it, resulting in no update of cpu load for that time. Meaning that your and my hotplug will get the same very high values of cpu load for this time from this cpu. To fix this I did this: https://github.com/SkipXS/kernel_msm/commit/7f71357041caccdf36d82b1a9d2a74fc708bd310 :) Looking forward to hear what you think about this.

Another thing is that you could simplify your touch boost in ondemand if you want to like this: https://github.com/SkipXS/kernel_msm/commit/25b4e0ca446f3928bcdb67f0c9acc77792634c4c

The next thing I would like to ask is if I may use your mpdfake and cwm zip if I ever decide to release my kernel. :) Thanks in Advance :)

I also did some other changes you can find here https://github.com/SkipXS/kernel_msm/commits/JWR/Y if you are interested ( GPU Governor, Global Boost Flag, Simplification of Ondemand Governor)

Greetings from Germany
[Nexus 4 Original Android Development] ihancioglu:
Hi guys, I would like to ask you why you need to create mpdfake service? As Franco is publishing just img, I think no service like this with it. Is there another way to prevent these error messages?
[Nexus 4 Original Android Development] californicated:
Took some pictures and viewed them in the gallery. Result: reboot

My phone was so stable since weeks, and now I got two reboots in two days :(

https://www.dropbox.com/s/g9xh4qa22tih235/2013-10-19_16.55.zip

Gesendet von meinem Nexus 4 mit Tapatalk
[Nexus 4 Original Android Development] AhmedFaiz:
I had a reboot too while using camera app. Is it known issue.

N⁴/PA3.99_RC2(NIGHTLY)/Semaphore 1.7.3 /V4A
[Nexus 4 Original Android Development] Fenvarien:
Have you touch wake enabled? I encounter those reboots only when I have this option enabled.
[Nexus 4 Original Android Development] californicated:
Nope. At the moment it's disabled

Oh boy, next reboot.. Got a call, phone vibrated instead of ringing, phone.apk freezed and I could close it. Still no sound when pressing volume rockers. Tadaaaa, reboot.

Again, logs attached. Thinking if my phone is ****ed up?
[Nexus 4 Original Android Development] Fenvarien:
Try to run stock settings, no uv and remove any scripts from etc/init.d.
[Nexus 4 Original Android Development] ihancioglu:
I got reboot / crash while on camera application.(viewing a photo) I have attached last kmsg file.

cataclysm rom, semaphore 1.7.3, uv -100 , touchwake enabled
[Nexus 4 Original Android Development] californicated:
No init.d scripts, removed uv and sai after last reboot. Although this settings worked for at least two weeks?
[Nexus 4 Original Android Development] stratosk:
Hi, my friend!

Thanks for your shares.

About the sampling down factor issue. I didn't understand how your patch may help. Could you please clarify.

Regarding, mod_timer I will try and use it. Good catch!

Yes, you may use mpdfake binary. Please note that you have to change ownsership to /dev/socket/mpdecision/touchboost file (system system).

Thanks again!

Franco kernel uses a modified powerHAL lib that silences this error message.

I don't want to modify any system libs. I use this service in initramfs that simply consumes powerhal messages to mpdecision.

It's the same reason in all cases: hw_reset due to VFE (Video Front End). It's the known stock issue.

No idea how to resolve this.
[Nexus 4 Original Android Development] californicated:
known stock issue = same will happen with stock rom and kernel?
[Nexus 4 Original Android Development] jst_tsj:
Would you be so kind to share your profile values? I've been playing with sensor values but cannot get a proper result..
[Nexus 4 Original Android Development] fortunz:
Sure thing. My night reading light level is 0, my indoor daytime level is 1-125, my outdoor is >750. Your eyes, tolerances and environments may vary greatly, so best advice I can give you is to create a little light meter profile, something that let you monitor light levels in real time. You wouldn't want to have it on all the time, but you flip that profile on when you want to get an idea of light levels in a particular environment.

I made mine as Profile -> event -> variable set %LIGHT, Action -> Variable Set %LightCheck (or whatever) to %LIGHT, now once it's activated and tasker is reloaded, you can watch it change in your VARS tab and get a good idea of what sensor ranges to use.

One more thing, I noticed I was getting a lot of old readings when I first polled %LIGHT on a power on, so I added a poll to an unused variable (Ex %LVDiscard), added a 500ms wait action, then set %LightValue. I never got around to figuring out if I really needed a discarded polling or if just a wait would have been enough. My %LVDiscard reading (first poll of %LIGHT after power on) is always the actual light value of the prior power on. So if I turn on my phone in a dark room, turn it off, than go out in the sunlight and turn it on again, the actual light will be in the hundreds, %LVDiscard will read 0 (as if I were still in the dark room) and the %LightValue will correctly read in the hundreds. If I turn it off again, go back to the dark room and turn it on, %LVDiscard will read in the hundreds, remembering that last poll.

Good luck. :)
[Nexus 4 Original Android Development] readon1:
Quick question: how is the auto brightness with no tweaking on my side on this kernel. Is it just like stock or brighter/darker?

Thanks in advance

Verzonden vanaf mijn Nexus 4 met behulp van Tapatalk
[Nexus 4 Original Android Development] AhmedFaiz:
No touch wake is off, but uv is on that might be the issue for me.

N⁴/PA3.99_RC2(NIGHTLY)/Semaphore 1.7.3 /V4A
[Nexus 4 Original Android Development] stratosk:
I think so. I didn't change anything related, so yes you may have this issue on stock.

It's exactly like stock.
[Nexus 4 Original Android Development] Fenvarien:
I know this issue from stock rom/kernel. Too aggressive UV and maybe touch wake seem to make hardware resets more likely during intensive camera usage.
[Nexus 4 Original Android Development] stratosk:
IMHO, touchwake is unrelated to this issue.
[Nexus 4 Original Android Development] Fenvarien:
Yes, it could well have been coincidence regarding touch wake. :good:

But UV is definitely related. I was easily able to reproduce reboots during camera usage with UV settings, that were rockstable since days.

I assume that some generally very rare used voltages are somehow important for the camera/gallery app or drivers. When these voltages are borderline uv'ed the phone reboots, bang. ;)
[Nexus 4 Original Android Development] stratosk:
I agree. When I test UV on my phone, I first open camera app to test stability.
[Nexus 4 Original Android Development] Skkip:
[MENTION=3750240]stratosk[/MENTION]:

hey :)

Ok, I'm trying to clarify as good as I can now :)

As you know Ondemand uses a workqueue to poll the cpu load and change the frequency every sampling_rate.

Each time this is done, we report the current load to our hotplug solutions.

If the cpu load is above up_threshold (95) the cpu frequency will be set to policy->max and the sampling_down_factor will get applied.

This means dbs_info->rate_mult will be set to sampling_down_factor. Then the workqueue of this cpu is set to sampling_rate * dbs_info->rate_mult.

The effect of this is, that the next poll will be sampling_rate-times later than the default sampling rate, with no reporting of the current load to our hotplug solutions.

An example of the adressed problem:

WAIT (sampling_rate)

--> evaluate cpu_load (65%)
--> report cpu_load to hotplug (65%)
--> frequency setting (xxxx MHz)

WAIT (sampling_rate)

--> evaluate cpu_load (> 95%)
--> report cpu_load to hotplug (> 95%)
--> frequency setting (policy->max MHz)

WAIT (sampling_rate) \
WAIT (sampling_rate) | sampling_down_factor-times (4): BUT !!!HOTPLUG NEEDS THE CPU LOAD OF THIS CPU!!!
WAIT (sampling_rate) | !!!HOTPLUG STILL THINKS THE LOAD IS >95%!!!
WAIT (sampling_rate) /

--> evaluate cpu_load (65%)
--> report cpu_load to hotplug (65%)
--> frequency setting (xxxx MHz)

with patch:

WAIT (sampling_rate)

--> evaluate cpu_load (65%)
--> report cpu_load to hotplug (65%)
--> frequency setting (xxxx MHz)

WAIT (sampling_rate)

--> evaluate cpu_load (> 95%)
--> report cpu_load to hotplug (> 95%)
--> frequency setting (policy->max MHz)

WAIT (sampling_rate)
--> evaluate cpu_load (65%)
--> report cpu_load to hotplug (65%)
WAIT (sampling_rate)
--> evaluate cpu_load (65%)
--> report cpu_load to hotplug (65%)
WAIT (sampling_rate)
--> evaluate cpu_load (65%)
--> report cpu_load to hotplug (65%)
WAIT (sampling_rate) /
--> evaluate cpu_load (65%)
--> report cpu_load to hotplug (65%)
--> frequency setting (xxxx MHz)

....

I hope you understand what I mean :)

Greetings from Germany
[Nexus 4 Original Android Development] stratosk:
I know the stock ondemand behavior and you are right that we will have a delay to cpu load report to hotplug driver.

I rechecked your patch and now I see your logic.

But I think that initial approach is correct. The measured CPU load (in your example) is still > 95%. We used sampling down factor and we want the CPU to stay on its highest frequency more.

Please note that with your approach you will have the overhead of the governor itself (that needs to check CPU load every sampling rate even if user selected sampling down factor > 1)

I will stay with initial approach.

BTW, you were right about mod_timer. It works fine! Thanks!
[Nexus 4 Original Android Development] Skkip:
That's why I named it more a undesirable behavior :) If you want this, and i can see your point here, it works just fine. For me it will cause hotplug to online a cpu even though it is not needed, because ondemand handles the cpu load spike. And you are right about the overhead, but I think there are many other places in the kernel which are much worse, then just evaluating the load in ondemand with dbs_check_cpu and two inlined calls for idle time.

BTW, I tested some samping_down_factors with my default sampling rate of 50000 and would recommend to set it either to 1 or 4 or above (using cfbench, antutu and 3dmark). A sampling_down_factor of 2 decreases overall performance. I guess the reason for that is that the scheduler will pass most of the work to the fast cpu, which wont stay fast long enough. I'm not sure whether this applies to your short sampling rate too, or if it is time based...

Last thing I would like to mention is the io-scheduler. I am still trying to figure out which scheduler fits best in terms of battery life and performance. By digging deeper I found this: http://www.cs.wm.edu/~xqi/pdfs/ubicomp13-nguyen.pdf and was surprised about the results. Mainly because I thought that less overhead (noop) would be more beneficial. Maybe you are interested in this topic too?

:) Have a nice day
[Nexus 4 Original Android Development] necrologo:
Yesterday my wifi stopped working, and i wasn't able to put it off and then off... The only solution was to reboot.

Can I give you log? How can i get it?

P. S. Since the reboot to fix the issue I haven't rebooted the Phone

Inviato dal mio Nexus 4 con Tapatalk
[Nexus 4 Original Android Development] stratosk:
I don't know why a sampling down factor of 2 decreases performance. I use 4 as stock.

When I was searching about schedulers, I found that noop operates best on ssd media. And I like it's simplicity :)

What's your ROM?

Yes, you may post it. I'm not sure it's kernel related but logs are always welcome :)

In terminal emulator:

su

cat /proc/last_kmsg > /sdcard/last_kmsg.txt

Please send last_kmsg.txt
[Nexus 4 Original Android Development] stratosk:
Well, I checked again the logs.

It's not game's fault. Kernel ideally, should not restart or crash for any reason.

I think there's a bug in gpu drivers. I found a related commit in Code Aurora. The problem is that our kernel is far behind from the newest CAF code and I can't apply this patch. It requires many changes and I don't want to risk incompatibility with ROM's libs or something.

(I really hate that there is a ton of code that it's not up-streamed and every vendor maintains it's own code).

It's the first time I saw a similar log so I consider that it's a rare issue. But, please let me know if you will have this issue again.
[Nexus 4 Original Android Development] necrologo:
My rom is slimbean. Here you are my log. Thank you for your work!!!

https://db.tt/sY0IzVdj

Inviato dal mio Nexus 4 con Tapatalk
[Nexus 4 Original Android Development] sami_22:
Hi, I'm a big fan of your kernel and I would like to use MultiRom too.

So please could you try to make that your kernel support the Kexec-hardboot ?

http://xdaforums.com/showthread.php?p=46223952
[Nexus 4 Original Android Development] Slymobi:
I Knew you were on slimbean before I even read this post! Its ROM and router related for some reason, I had it every time on slimbean no matter what kernel I used. My only solution was to reboot my router whilst on mobile data on phone then forget my WiFi network and reapply when my router had rebooted.

I logged this with slimbean ages ago and devs (Kuf) couldn't explain it. I've

Never had the issue on other ROMs that are not slim based.

Its a shame as slim is 1 of my favourite roms although I've been away from slimbean for a long time now.

Sent from my Nexus 4
[Nexus 4 Original Android Development] galaxys:
Slim's 1.9 weekly has just been released...maybe its fixed? I don't use wifi enough to notice, and slim is my favorite daily driver.
[Nexus 4 Original Android Development] szucsgf:
http://xdaforums.com/showthread.php?p=46611527
[Nexus 4 Original Android Development] ihancioglu:
Hi, [MENTION=3750240]stratosk[/MENTION],

I found that , I am able to crash / reboot with hw_reset in camera application with -125/-100 UV (swipe to much, explore panoramic photos, focus,etc..) Tried and confirmed a few times..

Then decrease UV to -75/-50 , no more reboots.

I think this problem related UV. Do you apply UV on your device? I am using cpu type nominal PVS

Thanks,

EDIT : I am able to crash / reboot even with -75/-50 now. I will try with disable UV completely and let you know..

EDIT 2 : just got reboot even no UV , so this could be stock problem, but I would like to find cause of the problem, so I just switched to stock kernel for a while. I will try to get reboot with stock kernel. I will let you know If I succeed.
[Nexus 4 Original Android Development] californicated:
Thanks you took a look into it. I'll tell you if it happens again. Today there were no issues :cool:
[Nexus 4 Original Android Development] cantevencode:
My brother is running his n4 completely stock and his sometimes reboots when using camera apps
[Nexus 4 Original Android Development] Barbatos19:
Can I use semaphore manager app over trickster?
[Nexus 4 Original Android Development] Tylog:
Works fine, thank you for the quick reply :):thumbup:

This is what I call a good developer, great stuff and great and friendly support, thank you very much.

Tapatalk
[Nexus 4 Original Android Development] H-Body:
Yeah, that is exactly the Stratos we SGS users love :)
[Nexus 4 Original Android Development] a g bell:
Yes finally no more using trickster :)
[Nexus 4 Original Android Development] lethalboy:
Thanks for adding Gamma Control, now I will test this kernel. :)
[Nexus 4 Original Android Development] franciscofranco:
I'm intrigued, can you load the logger.ko module from /data/local without any problems?
[Nexus 4 Original Android Development] copi:
hi dev

trying ur kernel atm, thanks for gamma color, cant wait to be implemented on semaphore manager :)

1. about mpdecision.. what is ur recommendations? turn on or turn it off the mpdecision?

2. on semaphore manager it has option early ondemand,, is it ok (or its actually also ur recommendations) to turn it on?

3. touchscreen jitter on or off if I using touch filter?

hehe lots of question,, thanks much appreciated.
[Nexus 4 Original Android Development] reginickneo:
0.5.5 is great as always, but i have 2000 points less in Antutu (~18k). Maybe because of CM10.1 (also flashed the latest).

Anyways, it is smooth.

Accuracy and jitter filter are recommended?

Which value?
[Nexus 4 Original Android Development] stratosk:
The init process refuses to load an insecure file. Did you try to change the file permissions to 640?

1) I use mpdecision and I think it's good for battery and temperature to have it enabled. I just proposed a simple method to disable it.

2) I also use early demand. According to my measurements in my PC, it gives you 0.5 - 1% improvement in small CPU loads. You may try it.

3) You may experiment with this. I didn't try different values and combinations.

This works in every rooted device in every kernel. It's a 'dirty' way to disable mpdecision.

Also, you may just change file permissions to 666 (non executable).

Please use accuracy and jitter filters at your convinience (I don't use them yet)
[Nexus 4 Original Android Development] copi:
[MENTION=3750240]stratosk[/MENTION] thanks for ur quick n helpful reply

btw guys,, do u have ur favorite setting n mind to share? for now I really like and want to share my setting :

1. gamma (I just run it on terminal emulator) , its visceralpsyche setting:

#!/system/bin/sh

echo "0 5 119 1 1 0 7 2 1" > /sys/devices/virtual/misc/gamma_control/gamma_r

echo "0 5 119 1 1 0 7 2 1" > /sys/devices/virtual/misc/gamma_control/gamma_g

echo "0 5 119 1 1 0 7 2 1" > /sys/devices/virtual/misc/gamma_control/gamma_b

2. touch filter (not using jitter yet), and its from fransiscofranco kernel setting :
[Nexus 4 Original Android Development] franciscofranco:
This is when trying to insmod it after System had booted up.

insmod: init_module 'logger.ko' failed (Exec format error)

Do I need to load it from the ramdisk if I want the module to be loaded?

Just curious, thanks.
[Nexus 4 Original Android Development] stratosk:
Hmm.. The module must have the same version number as the kernel.

It's funny, but it worked perfect for me in my tests, but it does not in my final build.

I'm away from my build machine. I will test again tonight and let you know.

No, you don't need to load it from ramdisk. You can load it from any directory.
[Nexus 4 Original Android Development] apatal:
Wow. When 2 developers of this caliber throw ideas around, I can almost smell something special coming your way for fans of both kernels. ;)
[Nexus 4 Original Android Development] Mercado_Negro:
Just created this script with ROM Toolbox for Halfbreed colors, using the spreadsheet found here:

https://docs.google.com/spreadsheet/lv?key=0AoDp2qRui0u0dGE4T2gtSDBTRHVFSldPS2RrX1Rya0E

This is the first time I do something like this but I ran it from ROM Toolbox and it looks OK. I have not set it on boot, though.

Pull the file out of the zip with 7-zip, copy it to /etc/init.d and reboot.

Please try it at your convenience :)

Cheers

[EDIT]Just set it on boot and it runs flawlessly :)
[Nexus 4 Original Android Development] tisov:
I'm having problem with last release

The battery % will not update

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Original Android Development] stratosk:
Can you please be more specific? What exactly do you mean?
[Nexus 4 Original Android Development] tisov:
i flashed the new version, at 8am my battery was at 31% after 2 hours with wifi on and a lot of use the the battery was still at 31%

i try to do a reboot and after this the % was 20% and now it's blocked on 20%
[Nexus 4 Original Android Development] Vangelis13:
That happens with all the kernels. It's a derp on the battery stats reading & reporting that hopefully Google will fix in a couple of weeks.
[Nexus 4 Original Android Development] cryingrock:
Followed the steps but nothing changed...

Sent from my Nexus 4
[Nexus 4 Original Android Development] ksilver89:
set permissions to 755.
[Nexus 4 Original Android Development] oxxshadow:
so how often do the reboots on camera occur?
[Nexus 4 Original Android Development] szucsgf:
Yes, just make sure there are no inconsistencies in your settings. E.g. don't set interactive governor with one and Ondemand with another by accident.
[Nexus 4 Original Android Development] Kocai:
I'd say don't use those 2 apps at the same time so there won't be any conflict.
[Nexus 4 Original Android Development] cantevencode:
Very rarely in my experience
[Nexus 4 Original Android Development] Dan1234567890:
I just looked at the phone, and it was rebooting with boot animation on the screen...first time that I saw it.

here is last kmsg if it can help;

https://docs.google.com/file/d/0BytYviiZsKPxcGo2eDJQdm8yYms/edit?usp=sharing

I see the reason in kmsg is reboot, but...:confused:
[Nexus 4 Original Android Development] stratosk:
There are many error related to wlan.

But all seems to be handled properly. I don't know exactly about the errors but I don't think they are kernel related.

I'm really sorry. But I don't want more troubles (trying to be compatible with different ROMs).

Yes, I use UV. I had this kind of reboot once.

You are right. It seems like a normal reboot in the log.

What's your ROM? (Just for the history)
[Nexus 4 Original Android Development] twowheeler:
Are you still working on the new kernel? Cause it's still a test version. Curious what your plans are ;).
[Nexus 4 Original Android Development] stratosk:
Most probably, I will release a new version in 1-2 days.

No big changes. I was extremely busy and tired last days...
[Nexus 4 Original Android Development] twowheeler:
Alright, looking forward to it. But there's absolutely no need to hurry my friend!
[Nexus 4 Original Android Development] ciprianruse88:
[MENTION=3750240]stratosk[/MENTION]

I've did a clean install of Purity with 1.7.3 and still can't get locat with logger on/off - reboot between switching it but no problem because everything is flawless and there is no need for logcat :)

Edit : It works via adb but not with syslog app...:thumbup:

"by failing to prepare, you are preparing to fail" - Benjamin Franklin
[Nexus 4 Original Android Development] stratosk:
Thanks, my friend!

Too many obligations in real life with job and family. I can't move faster even if I want to.

Thank you all for your interest about Semaphore!

Your interest gives me the motivation to continue this project.

Many times I think to stop it, but then I think that I feel happy when I read some posts here...

Sorry for the nagging... I guess I'm too tired.

If you see full logs via adb then the module is properly loaded and works. I guess it's app issue. Did you try another app? (catlog or something). Also you should see logs via terminal emulator (su, logcat commands).