yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] undercover:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Feb-03

:D
[Nexus 4 Original Android Development] bleuf1sh:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Feb-03

Lol... I just saved that image for reference later....

sent from my nexus4 | bionic | harsh
[Nexus 4 Original Android Development] immunityx:
LMFAO
[Nexus 4 Original Android Development] Lownita:
I can confirm, this syntax works for voltages:

#!/system/bin/sh
echo "384000 700000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "486000 700000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "594000 712500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "702000 737500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "810000 775000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "918000 787500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "1026000 812500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "1134000 862500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "1242000 887500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "1350000 912500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "1458000 925000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "1512000 937500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
[Nexus 4 Original Android Development] Hexxer:
Hi,

thanks. But i cant sent logs because i cant grab it. If the device in this "lock" state that i cant start it adb logcat wont work. Any other ideas?
[Nexus 4 Original Android Development] bleuf1sh:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Feb-03

.......confusion sets in ........

sent from my nexus4 | bionic | harsh
[Nexus 4 Original Android Development] nycelitemaster:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Feb-03

@harsh, i just suffered first SOD don't know how, i will try to reproduce and get log. I am running stock rom and your feb3 version since yesterday evening. Never experienced anything like this before. Never flash any other kernel except yours.

Sent from my Nexus 4
[Nexus 4 Original Android Development] immunityx:
Ok for what its worth i was able to reproduce the same issue with the SOD and this is after reloading stock firmware and fastboot the Feb 3 kernel. The screen doesnt wake up if you not charging the phone, soon as you plug in the phone to charger it turns on... weird stuff.
[Nexus 4 Original Android Development] DowntownJeffBrown:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Feb-03

Every time I update your kernel I reflash the ROM then Gapps then the new kernel. It's the fastest most reliable way I've found to get a good clean install of the kernel.

Sent from my Nexus 4 using Xparent BlueTapatalk 2
[Nexus 4 Original Android Development] nycelitemaster:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Feb-03

So once the phone goes into deepsleep the sod comes?

Sent from my Nexus 4
[Nexus 4 Original Android Development] immunityx:
yup
[Nexus 4 Original Android Development] undercover:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Feb-03

http://xdaforums.com/showthread.php?p=23036410

You nee option 3,last_kmsg
[Nexus 4 Original Android Development] Lownita:
Finally, I don't need Trickster anymore! :D

Perhaps, for playing around, what do I have to echo to get sweep2wake working?

Also, does it make sense to test every frequencies stability? I did this back in the SGS2 days to verify my UV settings. But is it even possible with mpdecision on? Cause I can't lock the freq?

#!/system/bin/sh

# First we set colors
echo "255 255 255" > /sys/devices/platform/kcal_ctrl.0/kcal

# Now Gamma, need to change values at place 6 and 7 only
# value at 6 is amp0 and at 7 is amp1
# kgamma_r is for red, g for green and b for blue

# values amp0 and amp1 are located below $$$$
# ---------------------$$$$$-----------
echo "208 114 21 118 0 20 00 80 48 2" > /sys/devices/platform/mipi_lgit.1537/kgamma_r
echo "210 114 21 118 0 19 00 80 48 2" > /sys/devices/platform/mipi_lgit.1537/kgamma_g
echo "212 114 21 118 0 19 00 80 48 2" > /sys/devices/platform/mipi_lgit.1537/kgamma_b
# undercover's LG Preset values :D, thank you.

# vibration intensity, 100 is max
echo "100" > /sys/class/timed_output/vibrator/amp

# voltages, "frequency voltage"
# these are very low, will most likely only work on faster binned cpu
echo "384000 700000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "486000 700000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "594000 712500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "702000 737500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "810000 775000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "918000 787500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "1026000 812500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "1134000 862500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "1242000 887500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "1350000 912500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "1458000 925000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "1512000 937500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
[Nexus 4 Original Android Development] jassycliq:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Feb-03

#Sweep2Wake

chmod 777 /sys/android_touch/sweep2wake

echo "1" > /sys/android_touch/sweep2wake
[Nexus 4 Original Android Development] pkadavid:
Does fastboot have something to do with it, in your opinion? Running smoothly on the previous version, so I wanted to see if the SOD happens no matter what or if it has something to do with fastboot.

thanks
[Nexus 4 Original Android Development] Last Second:
Hello guys i am new to the N4 and this section;).

After rooting, i was interested in new kernels and the harsh kernel seemed very suited.

So i wiped caches ans installed it (over stock rom and kernel)... so far so good. I am on 301K, Rev 11 and Fast CPU.

After a short while i recognized that my phone doesn't come back after screen of - it's not a traditional SOD, because I don't need to plug it on charging, just long pressing the power button until it reboots.

So is there a solution for this one?
[Nexus 4 Original Android Development] eep2378:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Feb-03

Are you UV'ing? If so back off a little.

Sent from the Nodes of Ranvier
[Nexus 4 Original Android Development] Harsh:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Feb-03

How long did you let it sleep? Also some logs would be helpful if you could get. I have no sod no matter what. And people facing sod were unable to get logs until now. So install some logcat app and keep it running and writing log to some file in sdcard. If sod happen it will be written, and you can get me logs after reboot.

Something for later today :). But stability is not tested (toolchain accuracy), my ssd failed so I had to setup all back in my old HDD.

Sent from my Nexus 4
[Nexus 4 Original Android Development] CrimsonSmear:
Let me impart a bit of information for those that are unwilling to search for solutions or generally impatient... Do not use TEST builds, they are not for you.

Test builds are for troubleshooters that follow the developer and are capable of seeking solutions, they are not for the general populace.

Here is the procedure that you will need to perform to correct your problem:

Reflash franco.Kernel test-r61/62

Reboot (to stabilize your system)

Delete /system/lib/hw/power.msm8960.so and rename the backup file

Give the file the appropriate r/w permissions as indicated by the other files in the dir

Flash your original backed up kernel or a reset kernel

Flash desired kernel

If your system is stable enough, you may be able to simply delete/rename power.msm8960.so (as above) and reboot.
[Nexus 4 Original Android Development] abufaka:
Wouldnt logcat writing constantly logs stop the phone from going to deep sleep? I tried alogcat and lumberjack, but there seems to be no option for continuous writing or i'm just blind.
[Nexus 4 Original Android Development] Junglist86:
AW: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Feb-03

Are the values for "faster" CPU to?

Gesendet von meinem Nexus 4
[Nexus 4 Original Android Development] Lownita:
Yes. My CPU is faster binned, but after some hours of using those, I got a reboot! I will stick with an overall offset of -50 mV from harshs stock voltages, that should be fine :)
[Nexus 4 Original Android Development] aimcr7:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Feb-03

After using latest kernel for a day, i got pretty good battery life so far, and performance wise its smooth, very smooth.

Interactive, custom tunables, -162.5mV.

Great work harsh! Keep it up! ;)
[Nexus 4 Original Android Development] superleeds27:
Latest vrsion working fine for me. Had a massive drain earlier. Turns out it was Friendcaster!

Why are there no decent facebook apps!
[Nexus 4 Original Android Development] bleuf1sh:
also been working really nicely so far.... over 14 hours of on time and 4+ hours of screen time
[Nexus 4 Original Android Development] Mr Djoegoe:
Before and after Harsh Kernel
[Nexus 4 Original Android Development] ftarules:
I am using the Feb 3 version of the kernel with Feb 1 Stable build of Xylon.

Now I am using the script for Udnercover settings of gamma from post 3.

I run the script and for a short period of time the gamma values stick. But after a few minutes (half an hour so) the gamma values revert back to zero. I am using Faux123 kernel app to check. After running the script the Faux app correctly displays the gamma values. But after half an hour so, all the gamma values go to zero (as per the Faux 123 app.).

My question is this:

1) Is the Faux app wrong? I don't think so, since I can tell change the screen color.

2) If the gamma values are NOT sticking by the script, what should I do?
[Nexus 4 Original Android Development] undercover:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Feb-03

Uninstall faux app. It might be interfering.
[Nexus 4 Original Android Development] ftarules:
I am NOT using faux app to change any parameters. Just trying to check to see if the gamma script values 'stick'.

Still I will uninstall the app.

Is there a way to check if the values stick? Meaning are there any terminal commands that I can run to see if the values stick?
[Nexus 4 Original Android Development] estallings15:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Feb-03

The XDA app on the dark theme gets lighter when my gamma values don't take. I can tell at a glance. Try finding an app or screen that does the same for you.
[Nexus 4 Original Android Development] eep2378:
You can find your values in the following folders:

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

Gamma(amp0, amp 1,): sys/devices/platform/mipi_lgit.1537/kgamma_b(the other values will be in this same folder ending in kgamma_r, kgamma_g)
[Nexus 4 Original Android Development] Harsh:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Feb-03

If you have fauxclock why use script. But I insist on script and uninstall of fauxclock. And after uninstall values will always stick because there is nothing which can change it :)

And yes exactly this :)

Sent from my Nexus 4
[Nexus 4 Original Android Development] meangreenie:
settings->apps->fauxclock->force stop->disable :D
[Nexus 4 Original Android Development] kin24173493:
The min cpu always stays at 1026, is that normal?
[Nexus 4 Original Android Development] mundixx:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Feb-03

Yes. Harsh designed it to be as close to stock as possible (mpdecision), which is cool!

Sent from my AOSPA Nexus 4
[Nexus 4 Original Android Development] DowntownJeffBrown:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Feb-03

It shouldnt stay at 1026 it should come back down to 384 when idle. Every time u touch your phone it should shoot up to 1026 that's mpdecision. If its sticking on 1026 min all the time. Erase any kernel controlling app and

Reboot recovery

Dirty flash ROM

Flash Gapps (if needed)

Flash Harsh

Reboot

Sent from my Nexus 4 using Xparent BlueTapatalk 2
[Nexus 4 Original Android Development] rskyline:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Feb-03

Mpdesicion make that max freq turn down to 1.2Ghz too? Because apparently it doesn't stay at 1.5

Enviado desde mi Nexus 4 usando Tapatalk 2
[Nexus 4 Original Android Development] kin24173493:
How to check the cpu while in idle? Thanks.
[Nexus 4 Original Android Development] DowntownJeffBrown:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Feb-03

I have system tuner titanium backuped. I will restore it and check what I need to then un-install it. Usually I just monitor my CPU in better battery stats and if I see something wrong I just restore system tunner and the un-install it right after I'm done.

Sent from my Nexus 4 using Xparent BlueTapatalk 2
[Nexus 4 Original Android Development] ftarules:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Feb-03

Thanks. This was very helpful.
[Nexus 4 Original Android Development] zellleonhart:
I always get quite high amount of usage for Android System and Android OS, no matter which kernel I am using.

I checked BBS and wakelocks are low, but I still get considerable percentage of usage of Android System.

Any idea what may be the culprit? I am using PA ROM with Feb 03 harsh kernel at the moment. No kernel tweak apps installed.
[Nexus 4 Original Android Development] ftarules:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Feb-03

You need to wait at least one cycle to see if Android system and android OS contribute to use battery. For me Android System is around 8% which I think is okay after a full day of use and going into the night. In the screenshot you have only gone for less than 20% battery use total.

Also did you just install the ROM? New install of ROM can cause usage depending on your setup.

Lastly Android OS use = Apps . In this case you have an app that is eating battery. You may have to submit dump into the Betterbatterystats forum to get guidance.

Hope this helps
[Nexus 4 Original Android Development] zellleonhart:
I didn't install ROM, but I updated my ROM 2 days ago. I'll let it have a few more cycles before I judge then.

Thanks.
[Nexus 4 Original Android Development] farhanito:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Feb-03

As per Jan-20 build, I saw that CIFS is enabled in this kernel. Does this feature stays to the latest version? Is it rom dependant too?
[Nexus 4 Original Android Development] more2come:
Qualcomm's proprietary mpdecision boosts minimum frequency to 1 GHz, when you touch the display. It stays at that clock for a few more seconds and goes back down to 384 MHz when the system is idle and you don't touch the display.

When your maximum frequency goes down to 1.2 GHz, it's most likely due to thermal throttling. If CPU temperature surpasses a certain level, the CPU clocks down and/or deactivates CPU cores. If you take a look at Trinity Kernel for example, the dev decided to deactivate thermal throttling. Needless to say, that is quite risky and can damage your device!
[Nexus 4 Original Android Development] bleuf1sh:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Feb-03

What max temp does Qualcomm have set before the throttles.... Just curious...

sent from my nexus4 | bionic | harsh
[Nexus 4 Original Android Development] more2come:
Hard to say. As far as I know, the CPU clocks down until the temps go down. So I guess in extreme circumstances, the device would clock down way beyond 1 GHz. If it gets too hot, it'll shut down completely.
[Nexus 4 Original Android Development] bleuf1sh:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Feb-03

I just check my temp every so often and I wanted to know what temp should worry me. Flashing ROMs and kernels may result in the device not throttling correctly and I just want to double check things are working well.

sent from my nexus4 | bionic | harsh
[Nexus 4 Original Android Development] more2come:
For a CPU built this size, temps beyond 60 °C would be something to worry about. But this you would feel very fast, considering the thickness and overall size of the Nexus 4! That would be very, very hot to the touch! The CPU starts to clock down around 40-45 °C from my experience. Latest Harsh kernel manages to stay very cool, even under heavy load.
[Nexus 4 Original Android Development] Poiuytrewqasdfghjkl:
Okay sorry for asking but im kinda new to this kernel stuff so please..

I installed the latest version from the 1st page. Flashed it through cwm Recovery.

Do i need to change anything else? Or am i good to go as it is?

Im assuming that harsh's gamma settings are already set by flashing this kernel right?

Sorry for the bad english.

Thanks!
[Nexus 4 Original Android Development] gianton:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Feb-03

No need to do anything leave it as is works great!

Sent from my Nexus 4
[Nexus 4 Original Android Development] roswell782:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Feb-03

Thanks OP for your work, let's try this kernel ;)
[Nexus 4 Original Android Development] bleuf1sh:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Feb-03

Thanks. True I'd feel it quickly through the glass. Thing is, I just got this case and I want to make sure it doesn't adversely affect the temperature to much.

sent from my nexus4 | bionic | harsh
[Nexus 4 Original Android Development] Harsh:
New build Feb-5 Uploaded....

Changelog:

Updated to Linux 3.4.29

My Laptop SSD had a crash, so compiled with new setup on HDD.

Nothing new and extraordinary, It just works as previous build :D

Download link: http://d-h.st/HN2
[Nexus 4 Original Android Development] nekbreak:
AW: [KERNEL][UV][Linux 3.4.29] Harsh Kernel build Feb-05

Thanks for your good works.

For me the best Kernel.

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] gianton:
Re: [KERNEL][UV][Linux 3.4.29] Harsh Kernel build Feb-05

Thanks for the update and hope you had a backup!

Edit: Flashed it all good so far. I noticed new files added in /system/bin and /system/lib/hw. What are these for?

Sent from my Nexus 4
[Nexus 4 Original Android Development] kin24173493:
Need to wipe anything before flash?
[Nexus 4 Original Android Development] syncopy:
Re: [KERNEL][UV][Linux 3.4.29] Harsh Kernel build Feb-05

Coming from a previous version of Harsh/stock kernel? No.

Coming from another kernel? Dirty flash your ROM, gapps if applicable and flash this kernel.

Sent from my Nexus 4
[Nexus 4 Original Android Development] kin24173493:
what is the default colour in harsh kernel in feb05?

after i flashed PA rom feb05 then i check the colour in fauxclock. it change to:

R: 255

G: 247

B: 243

amp0

0

0

0

amp1

0

0

0

is it the correct default kernel colour? thanks
[Nexus 4 Original Android Development] gianton:
Check in 3rd post for Harsh's defaults, I don't think they are changed in Feb 05 rel.
[Nexus 4 Original Android Development] DowntownJeffBrown:
Re: [KERNEL][UV][Linux 3.4.29] Harsh Kernel build Feb-05

Google presets 255,255,255 4,0,26 2,0,16

Sent from my Nexus 4 using Xparent BlueTapatalk 2
[Nexus 4 Original Android Development] gianton:
Hi Harsh,

I tried moles kernel (link here) and I really like the colors on my screen. Can you try to implement those values to your kernel too?
[Nexus 4 Original Android Development] -iNSiGhT-:
Re: [KERNEL][UV][Linux 3.4.29] Harsh Kernel build Feb-05

Just take one of the 2 scripts in 2nd post of this thread, and edit it with moles value (moles gave his color values in his thread), then put it in /etc/init.d folder with rwxr-xr-x permission.

Paranoid Nexus4...
[Nexus 4 Original Android Development] gianton:
Re: [KERNEL][UV][Linux 3.4.29] Harsh Kernel build Feb-05

I don't think it'll work, moles said he added extra values too. Only Harsh can edit the kernel values to match moles's.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Nova163:
Re: [KERNEL][UV][Linux 3.4.29] Harsh Kernel build Feb-05

Hi all,

Coming from the P990 I was very happy to see Harshs name here! After installing this kernel I wasn't disappointed: I got 24h battery with 60% remaining.

However, when the screen is enabled it starts sucking some major battery. I understand that's the curse of having a phone with a nice and big screen, but are there any ways to lower the screen battery usage?
[Nexus 4 Original Android Development] JmPTaz09:
Re: [KERNEL][UV][Linux 3.4.29] Harsh Kernel build Feb-05

Lower screen brightness is only way I know of. I keep it at around 15% and I get great battery life with lots of screen on.
[Nexus 4 Original Android Development] Higgsy:
Yeah, I think you migt be able to do it by a script, but he said he is changing other values that apps like faux won't pick up. Must say I do like the colours on that testzip, the 05 Build of PA hurt my eyes, and I like harsh's defaults m,yself - but these are good.
[Nexus 4 Original Android Development] Harsh:
Install PA kernel, and check values in kgamma_r, kgamma_g, and kgamma_b from /sys/devices/platform/mipi_lgit.1537/

Copy those files in SDcard and put that values in init.d script, or upload it here.

it would surely work :)
[Nexus 4 Original Android Development] farhanito:
Re: [KERNEL][UV][Linux 3.4.29] Harsh Kernel build Feb-05

Harsh,

Sorry for repeating my question, have you enabled CIFS in your latest version?

Thanks
[Nexus 4 Original Android Development] 75markus:
guys, where´s the best place to check the kernel (linux version) changelog ?

is the official site http://www.kernel.org/ universally applicable for android kernels ?

this is the changelog for 3.4.29 http://www.kernel.org/pub/linux/kernel/v3.0/ChangeLog-3.4.29
[Nexus 4 Original Android Development] Harsh:
Yes, but not tested.

Yes but only arm changes are for us.
[Nexus 4 Original Android Development] Higgsy:
Yeah but I he indicated he changed other values than these that hadn't been explored before (thats how I read it). So we would need to know what/where these are wouldn't we?

Cheers...
[Nexus 4 Original Android Development] farhanito:
Re: [KERNEL][UV][Linux 3.4.29] Harsh Kernel build Feb-05

Well then I've tested it on Feb-03 build using cifsmanager and terminal, I got...

mount: invalid argument
[Nexus 4 Original Android Development] aikidoka90:
Please, add in the next build again support for the fauxclock app to can change the display settings!

Thanks for your amazing job!
[Nexus 4 Original Android Development] meangreenie:
Wonder when the other devs will realise that the other 3rd party mpdecision system is a jerky piece of crap ;) and go back to normal mpdecision too :)

aikidoka90... It already does
[Nexus 4 Original Android Development] Harsh:
Re: [KERNEL][UV][Linux 3.4.29] Harsh Kernel build Feb-05

It should be working. Just select type of preset and again change and select preset again. After that change gamma as you like, screen off/on and it should be done.

Also note if you use fauxclock you can't use script.

They will never go back to mpdecision until we get inkernel mpdecision merged in sources by Google. But we never know the future :)

Sent from my Nexus 4
[Nexus 4 Original Android Development] ftarules:
FauxClock app is NOT able to ajust the gamma values. This is since the Feb 3rd build for me. It used to work fine till Jan 29th build. I am able to adjust the slider for the gamma for one color, but then when I adjust he slider for the second color, the previous color slider goes back to zero.

I am using SuperSU pro with updated binaries, so its not that app.

For now I am resorting to running the script at startup.

if you could look into why Fauxclock app is NOT able to adjust gamma, that would be great.
[Nexus 4 Original Android Development] ctfrommn:
+1, this has been reality since the test builds started last week. Scripts work fine, but Faux Clock doesnt.