yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] Harsh:
Seem like modem is going of in no-data state. I mean if this happens you will not receive calls too during those seconds. Complete modem shutdown.

D/StatsProvider(12831): Current value: No Data Connection 9 s (9 s) Ratio: 0.1%

D/StatsProvider(12831): Current value: No or Unknown Signal 9 s (9 s) Ratio: 0.1%​

Its same 9 seconds when you did not have data and also signal (no or unknown signal)... I will check more on this. I am not reverting 3g power saving commit at any cost (huge battery improvement when I am not home), so I need to find a solution for this
[Nexus 4 Original Android Development] eep2378:
Ok. let me know if you need anything else to try and pin this down and solve the issue.
[Nexus 4 Original Android Development] UnitedOceanic:
it happend to me twice now that i locked the phone with the powerbutton and immediately started to sweep2wake, screen was off and i could not turn it on again, anly holding the powerbutton to reboot seemed to help.

saw this in the faux kernel thread, too.

what logs can i provided if i stumble on this behavior again?
[Nexus 4 Original Android Development] Harsh:
Showp already pointed out that, there is problem in touchscreen driver. And he also fixed this problem, so just waiting for sweep2wake v2.... :)

Sent from my Nexus 4
[Nexus 4 Original Android Development] undercover:
Son of a.....

I'm really liking this kernel, but this data problem is driving me nuts. Moved around quite a bit today, and experienced something new. Data showed on, icons stayed blue but data took a while to kick in. I hope that log I emailed myself went through, caught it right in the action.

Sent from the fridge. Make: LG Model: N4
[Nexus 4 Original Android Development] Heini_:
I am running Build 0201 and having issues with push-notifications. I receive facebook and gmail notifications with a slight delay (comparing to my old HTC Desire) which is fine but other notifcations like whatsapp I don't get at all as long as I don't open the app manually.

Faux Kernel had similiar problems some time ago...

Are you aware of this issue? Has it been fixed?
[Nexus 4 Original Android Development] Harsh:
Thanks for reporting.

We are aware of this problem, its all due to fix we implemented for wakelocks. Trying to fix it without reverting those wakelock fixes.
[Nexus 4 Original Android Development] DowntownJeffBrown:
Re: [KERNEL][UV][Linux 3.4.32] Harsh Kernel build Feb-20 - JB 4.2.2

I'm using halfbreed ATM.
[Nexus 4 Original Android Development] flxdms:
Most likely, yes. I'm not sure. I'll check.

edit: welp, I'm guessing that they're the same as franco unless morfic didn't update to franco's latest gamma interface.
[Nexus 4 Original Android Development] aimcr7:
Re: [KERNEL][UV][Linux 3.4.32] Harsh Kernel build Feb-20 - JB 4.2.2

Harsh i noticed you change ondemand sampling rate to 50000 in latest kernel, is it for better battery or performance? Cause i got a best balance between battery and performance with older settings.

And in trickster i see GPU settings, is this kernel include gpu oc now? My guess it is a trickster bug. :confused:
[Nexus 4 Original Android Development] icemasta31:
Thanks again for the script. I've been running the Jan 29th LOW version (last LOW version) without any issues since I have a FASTER binned CPU.

Since Harsh UV by 100, this will UV to 150 then right? Also, looking at the code it seems the UV is only for 0&1 CPU and only on Interactive Governor? Also, do I just flash through CWM and thats it?

Thanks.
[Nexus 4 Original Android Development] -iNSiGhT-:
@75markus or anyone knows,

Is there a script among yours (i mean in your mediafire) which fit with Moles' brighter kernel colors?

Thanks.
[Nexus 4 Original Android Development] flxdms:
Halfbreed (most likely this one if you're looking for what PA 3.0 currently has by default)

http://www.mediafire.com/download.php?3b5epz1a3g3puya

Dark contrasty (probably not this one)

http://www.mediafire.com/download.php?vl3n91w6lyjh43e

Holoblue (probably not this one as well)

http://www.mediafire.com/download.php?9mv2x2i11tw4smn

I can make another zip file if you want the "2nd rev, brighter, rich colors but less saturation, less banding" colours from this thread : http://xdaforums.com/showthread.php?t=2136295
[Nexus 4 Original Android Development] dirtyhamster73:
Re: [KERNEL][UV][Linux 3.4.32] Harsh Kernel build Feb-20 - JB 4.2.2

Yes please :D

Is it just me or does half breed not look the same after 4.2.2?
[Nexus 4 Original Android Development] snorfu:
I flashed a Color script but nothing happened...i'm in the 20th build.
[Nexus 4 Original Android Development] -iNSiGhT-:
Re: [KERNEL][UV][Linux 3.4.32] Harsh Kernel build Feb-20 - JB 4.2.2

I'm talking about this one.

Thanks making a zip for it!!

Envoyé depuis mon Nexus 7 avec Tapatalk
[Nexus 4 Original Android Development] Crisisx1:
Re: [KERNEL][UV][Linux 3.4.32] Harsh Kernel build Feb-20 - JB 4.2.2

Awesome ..do you know what preset the kernel originally comes with?? I think I read somewhere its one of moles presets but not sure.
[Nexus 4 Original Android Development] hospital349:
@ Harsh.

Just a quick query:

Is HDMI via Slimport controlled by the Kernel or the Rom?

I mentioned a bug to Moles before realising that I'm using your Kernel & not Stock PA Kernel. I wasn't sure who to report it to, but HDMI isn't working via Slimport. My device crashes upon connecting it to the TV. Another user mentioned that it does read a 1080pi output, but it does in fact give a blue screen, instead of visuals.

If this isn't kernel related, disregard this post. Otherwise, if you need me to replicate the bug and send you a log, just let me know.

Many thanks! Build Feb-20 is great.

Snappy, sweet and great battery! :good:
[Nexus 4 Original Android Development] DowntownJeffBrown:
Re: [KERNEL][UV][Linux 3.4.32] Harsh Kernel build Feb-20 - JB 4.2.2

I think its still just Harshs personal presets.

Sent from my Nexus 4 using Xparent BlueTapatalk 2
[Nexus 4 Original Android Development] mkamal23:
I tried searching the forum... but can i use the Faux display app with this kernel?
[Nexus 4 Original Android Development] sean222:
Nope. Just download the bunch of zips mentioned earlier on Mediafire. You'll probably like at least one :)

I'm really enjoying not having an app to control the kernel or color settings...keeps everything nice and clean.

I was using the trinity app and also faux clock app (with their respective kernels) and I hated that the colors were not loaded until a few seconds after the phone booted up and the app had to set the settings :(

With Harsh and these zips, it's loaded right away and looks beautiful :) init.d FTW :D
[Nexus 4 Original Android Development] mkamal23:
Thanks for the tips :)
[Nexus 4 Original Android Development] bakedpatato:
Re: [KERNEL][UV][Linux 3.4.32] Harsh Kernel build Feb-20 - JB 4.2.2

I have the same thing happen on stock codefire.
[Nexus 4 Original Android Development] ruzkay:
AW: [KERNEL][UV][Linux 3.4.32] Harsh Kernel build Feb-20 - JB 4.2.2

I got the one with black screen instead of lock screen too just like you described. But I'm on 4.2.2 stock atm. Thought I'd share that it happens on stock aswell.
[Nexus 4 Original Android Development] Harsh:
Re: [KERNEL][UV][Linux 3.4.32] Harsh Kernel build Feb-20 - JB 4.2.2

Black screen only happens on stock. On other all ROM on this thread it is working flawlessly. And I don't know why is it happening only on stock? Never happened with me though.

I have checked logs but no findings from that yet. :(
[Nexus 4 Original Android Development] akira.pwr:
R: [KERNEL][UV][Linux 3.4.32] Harsh Kernel build Feb-20 - JB 4.2.2

I have stock fw with latest harsh kernel, I haven't noticed this issue, could you tell me how to reproduce it?

Inviato dal mio GT-N7100 con Tapatalk 2
[Nexus 4 Original Android Development] more2come:
This could be a problem within the display driver module. I guess Harsh can give you more information on that.
[Nexus 4 Original Android Development] DynamicRam:
The UV is for all the cores, i used this script to set interactive as the default governor but it won't be executed in the attached script i just forgot to remove it
[Nexus 4 Original Android Development] jarayn:
Its so easy using trickster though.

Change the colours reduce the max and min cpu and u/v all in GUI.

Downside? A fraction of a second where you see different colours just as you boot? I have never noticed that but even if I did Im not rebooting enough or staring at my phone intently as I do so for it to be considered a negative.
[Nexus 4 Original Android Development] flxdms:
There you go.
[Nexus 4 Original Android Development] nokkenas:
Is the battery life improvement from further undervolting noticeable? My phone has a fast binned chip and I'd like to try it if there is.
[Nexus 4 Original Android Development] ruzkay:
AW: [KERNEL][UV][Linux 3.4.32] Harsh Kernel build Feb-20 - JB 4.2.2

Sorry what I was trying to say that it happens with stock KERNEL too and considering PA uses stock kernel too maybe it is only a problem with 4.2.2 stock ROM and has nothing to do with the kernel.
[Nexus 4 Original Android Development] sean222:
Re: [KERNEL][UV][Linux 3.4.32] Harsh Kernel build Feb-20 - JB 4.2.2

It bothers me because I love to reboot my phone and I love staring at it :) Trickster is very good though...I just prefer to keep things minimal. Min/Max OC, UV, and Colours can all be done through init.d script :) But this method is not as 'easy' as using Trickster though.

Sent from my Nexus 4

---------- Post added at 09:02 AM ---------- Previous post was at 09:00 AM ----------

Not 'noticeable'. A lot of people say they do it to help reduce temps...some games/apps can make the phone really warm :)

Sent from my Nexus 4
[Nexus 4 Original Android Development] bleuf1sh:
Re: [KERNEL][UV][Linux 3.4.32] Harsh Kernel build Feb-20 - JB 4.2.2

I'm sure some of y'all also use paranoid.... How have you kept his colors after flashing harsh.... Was it with the zip a few posts up called 2ndrev moles?

mako | paranoid | stock
[Nexus 4 Original Android Development] FatalityBoyZahy:
Re: [KERNEL][UV][Linux 3.4.32] Harsh Kernel build Feb-20 - JB 4.2.2

I never experienced it on stock, it only happened once, and that was with the previous build while running CM10.1.
[Nexus 4 Original Android Development] icemasta31:
OK sounds good.

So I guess it's OK to remove

#echo "interactive" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

#echo "interactive" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor

and just leave

echo "-50000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels and just flash the ZIP through CWM?
[Nexus 4 Original Android Development] hospital349:
Bumping for your attention, Harsh.

Many thanks! :)
[Nexus 4 Original Android Development] undercover:
[KERNEL][UV][Linux 3.4.32] Harsh Kernel build Feb-20 - JB 4.2.2

Why not just attach a log so people can have a look into it. This would greatly improve your chances of getting an answer. Do from terminal

su

logcat -c

To clear cache, then replicate problem and get logcat.
[Nexus 4 Original Android Development] hospital349:
Agreed, this would be constructive. However, my phone crashes upon connecting my device to my TV via Slimport-HDMI and I lose all functionality. I have to hard reset which causes my phone to lose all of its logs.

If you know of an alternate method, let me know and I'll try and get something for Harsh.

Apparently, this problem is present in several other custom kernels...
[Nexus 4 Original Android Development] schizophrenia:
trying this solely to see if it fixes the hsic wakelock

when on 3G connection, I always get at least 10% to 15% of hsic wakelock which my N4 can never sleep well and therefore battery drain.

see if Harsh Kernel can help

Thanks Harsh.
[Nexus 4 Original Android Development] drdrewdown:
it will
[Nexus 4 Original Android Development] bakedpatato:
Re: [KERNEL][UV][Linux 3.4.32] Harsh Kernel build Feb-20 - JB 4.2.2

I did a log using wifi adb and DDMS which I posted to codefire (who has not responded)* . I'm thinking this is a 4.2.2 AOSP issue as the phone crashes with both Harsh and stock codefire kernel.

Edit: here is the log. Hospital349, if you get the same nullpointerexception from interceptKeyBeforeQueueing while using Harsh, it's probably a 4.2.2 AOSP issue(that would make sense that most of the source built kernels do this).

*DDMS is in the ADT bundle . Install a wifi adb app on your phone, run adb connect x.x.x.x:5555(where x is the ip address of the phone),verify connection with adb devices(The ADT bundle comes with adb.exe, it's in sdk/platform tools, run those commands in a command window you open in the folder). Also run a dmesg too (adb shell dmesg >dmesg.txt, should write out a dmesg.txt to where adb.exe is)

Unzip the ADT zip, click on eclipse.exe(it's in the folder eclipse) and click on Window > Open Perspective > Other... > DDMS. You should see on the upper left hand of the screen a tab with a phone logo with the ip address of the phone. On the lower part of the screen is the log reader. Select the phone in DDMS,check to see you can read the logs, plug in Slimport adapter, wait for crash. Then shift click the relevant lines of the log and hit the save button.
[Nexus 4 Original Android Development] undercover:
[KERNEL][UV][Linux 3.4.32] Harsh Kernel build Feb-20 - JB 4.2.2

Sounds like kernel issue. Try this http://xdaforums.com/showthread.php?t=1520508

Section 3
[Nexus 4 Original Android Development] Harsh:
Re: [KERNEL][UV][Linux 3.4.32] Harsh Kernel build Feb-20 - JB 4.2.2

I can't access logs posted by you.

And I have not changed in slimport driver so it should be stock Google problem. Did you check if problem happening with my 422 stock kernel with UV and gamma?

Sent from my Nexus 4
[Nexus 4 Original Android Development] bakedpatato:
It could be a issue with 4.2.2 source;The bottom of the my log's NullPointerException stack trace is a native method. I wouldn't be surprised if Google didn't regression test for the Slimport adapter as it's pretty rare.
[Nexus 4 Original Android Development] bakedpatato:
Yeah, that's what I was thinking that this is a regression in 4.2.2 stock(the log is from codefire with codefire stock kernel which is built from source with no uv beyond binning,I didn't log with your kernel but the same crash with blue screen after plugging in Slimport adapter happened with your kernel).

I don't think the log will help you in any case as WindowManager is killed by a null pointer exception from InputManager...seems mostly userland to me. I'm at work right now without my slimport adapter so I'm unable to get you a dmesg before crash(the crash doesn't cause kernel panic, no last_kmesg). In any case I attached the log.
[Nexus 4 Original Android Development] hospital349:
Exactly the same situation my end.

I think Franco has contacts @ Google. Maybe he can drop them a email. I'll ask him about it. Thanks everyone. :good:

EDIT: Tried out Google's Stock Kernel. I can confirm that it's a AOSP bug and that HDMI output is completely non-functional. There you have it.
[Nexus 4 Original Android Development] bleuf1sh:
Re: [KERNEL][UV][Linux 3.4.32] Harsh Kernel build Feb-20 - JB 4.2.2

Bump.... :)

I'm sure some of y'all also use paranoid.... How have you kept his colors after flashing harsh.... Was it with the zip a few posts up called 2ndrev moles?

mako | paranoid | stock
[Nexus 4 Original Android Development] ftarules:
Re: [KERNEL][UV][Linux 3.4.32] Harsh Kernel build Feb-20 - JB 4.2.2

Yes just use the zip file from the mediafire folder posted a few pages back.

Here is the link to the folder: http://www.mediafire.com/?mnttdfpgqnoey
[Nexus 4 Original Android Development] bleuf1sh:
Re: [KERNEL][UV][Linux 3.4.32] Harsh Kernel build Feb-20 - JB 4.2.2

On moles site

http://goo.im/devs/paranoidandroid/roms/mako

His colors were last edited 2 days ago.... I don't think the ones in your media fire are up to date

mako | paranoid | stock
[Nexus 4 Original Android Development] hospital349:
Hey Harsh.

Here's a little something that might help with the HDMI fiasco:

CM 10.1 Kernel (HDMI confirmed working!!)

Many thanks! :)
[Nexus 4 Original Android Development] dirtyhamster73:
Re: [KERNEL][UV][Linux 3.4.32] Harsh Kernel build Feb-20 - JB 4.2.2

Thanks so much! :thumbup:
[Nexus 4 Original Android Development] bakedpatato:
Thank you for doing all the legwork kind british man! I guess if I want Slimport right now I'll have to run CM10.1. Or I can use my university education and try to fix it and then upload the changes to AOSP upstream...:good:
[Nexus 4 Original Android Development] hospital349:
Which to choose, which to choose?

Convenience or greatness? :cyclops:

I know a lot of people would benefit from your great capabilities. When I mentioned it to Franco, he couldn't see any commits made by CM regarding the subject. I don't know how difficult it would be to iron out the creases, but if you did need me for anything else down the line, feel free to throw me a PM. :good:

EDIT: ...and thank you, Mr. American Guy. :highfive:
[Nexus 4 Original Android Development] hospital349:
Harsh/bakedpatato,

I was finally able to create the HDMI crash logs. Find them in the attachment. :)

I've passed them onto Franco, also.

Hope it helps! :good:

EDIT: Replaced previous log with kmsg. This should be more useful.
[Nexus 4 Original Android Development] bakedpatato:
Hmm...nothing seems wrong on this side...the anx7808(the Slimport chip in the Nexus 4) is working as expected it seems. I was going to say HDCP error but the log shows all HDCP auth working.

Only this line interests me:

<3>[ 1281.926354] sp_tx_lt_pre_config: video stream not valid!
[Nexus 4 Original Android Development] Harsh:
I cant see anything wrong in logs.... and also dont see any specific changes in CM kernel. Maybe its something which is missing on ROM side.

Did anyone test slimport in stock rom and kernel?

And I cant do testing myself, as I dont use it and dont own it either :(
[Nexus 4 Original Android Development] flxdms:
Re: [KERNEL][UV][Linux 3.4.32] Harsh Kernel build Feb-20 - JB 4.2.2

Flash the zip file that says halfbreed in the mediafire folder that was linked earlier.

---------- Post added at 01:40 PM ---------- Previous post was at 01:38 PM ----------

They are up to date. The reason moles changed his kernels two days ago is to update then to 4.2.2. The colours are the same.
[Nexus 4 Original Android Development] bakedpatato:
Well if a MechE and an CS guy come to the same conclusion it must be software!:D

I keep seeing a callback NullPointer on all the logcats I've done so(thereby causing the WindowManager to crash) I'm going to try diffing those source files vs CM.
[Nexus 4 Original Android Development] hospital349:
Hey Harsh/bakedpatato.

Just an heads-up: http://xdaforums.com/showpost.php?p=38293737&postcount=11611

I haven't got a clue what it was that Moles did, as I have heard that the HDMI connectivity issue exists in several other N4 Roms on XDA. Xylon being one of them (apparently).

I'm still waiting for an explanation to what he changed and whether or not it was in fact Kernel/Rom related. I'm assuming Rom/Software, as this is Moles's area of expertise.

Thanks for looking into the matter. :)
[Nexus 4 Original Android Development] rodries:
This is the fix: https://github.com/ParanoidAndroid/android_hardware_qcom_display/commit/d1f349ee7cce08826dc1be6522415872dfde9864
[Nexus 4 Original Android Development] Lownita:
So franco limited gamma values to 119, because of this I think: http://xdaforums.com/showpost.php?p=38175567&postcount=14150 Does that also adapt to harsh?
[Nexus 4 Original Android Development] bakedpatato:
It was software;there was a wonky method that wrote out data to the external display;thereby causing that invalid video error in the kmseg.
[Nexus 4 Original Android Development] MarcoPolo78:
How is the msm_hsic_host wake lock with this kernel ?
[Nexus 4 Original Android Development] flxdms:
He limited them in his app. The values are the same on Harsh, anyway. 119 will still be 119.
[Nexus 4 Original Android Development] jarayn:
I dont really understand this.

Theres a ton of info on modding the colors but not so much on setting cpu freqs and voltages.

Is there a post in here somewhere with what changes can be made and how.

...

Thanks
[Nexus 4 Original Android Development] schizophrenia:
it is working very fine

hsic wakelock is comparatively low as compared to a few out there
[Nexus 4 Original Android Development] DowntownJeffBrown:
Re: [KERNEL][UV][Linux 3.4.32] Harsh Kernel build Feb-20 - JB 4.2.2

Its extremely low

Sent from my Nexus 4 using Xparent BlueTapatalk 2
[Nexus 4 Original Android Development] MarcoPolo78:
Re: [KERNEL][UV][Linux 3.4.32] Harsh Kernel build Feb-20 - JB 4.2.2

Everything seems to be choppy after I flashed the kernel , is there a step that's needed before flashing or certain settings ?
[Nexus 4 Original Android Development] albundy2010:
Re: [KERNEL][UV][Linux 3.4.32] Harsh Kernel build Feb-20 - JB 4.2.2

None. I would check and make sure you don't have kernel control apps messing with things.
[Nexus 4 Original Android Development] ctfrommn:
If you are coming from any "non stock" kernel, flash your Rom and then this kernel. This will ensure all is running correctly.
[Nexus 4 Original Android Development] MarcoPolo78:
Re: [KERNEL][UV][Linux 3.4.32] Harsh Kernel build Feb-20 - JB 4.2.2

Ahhhh okay thanks
[Nexus 4 Original Android Development] Harsh:
did it work now?

This kernel should never feel choppy as its using mpdecision 1026 MHz boost on touch.

If you are facing any troubles it must be due to modified powerHAL from previous kernels or other kernel controlling apps.

Before flashing remove all kernel controlling apps to have true feel of this kernel.

Best process of flashing kernel is 3 steps. No wipe necessary.

1 flash ROM

2 flash gapps if needed

3 flash kernel
[Nexus 4 Original Android Development] Lownita:
AW: [KERNEL][UV][Linux 3.4.32] Harsh Kernel build Feb-20 - JB 4.2.2

Yes but from my understanding any value above 119 would be without any effect.

Papastalked from my Nexus 4
[Nexus 4 Original Android Development] meangreenie:
Just install 'system tuner' from the market. Its very easy to use, just don't set anything to start at boot until you know your settings are good.
[Nexus 4 Original Android Development] 75markus:
this kernel is undervolted by default, so there is really no need to undervolt more manually

the same goes for cpu freqs, it uses mpdecision, so no need to use a script or app to adjust. it just will make things worse
[Nexus 4 Original Android Development] estallings15:
Re: [KERNEL][UV][Linux 3.4.32] Harsh Kernel build Feb-20 - JB 4.2.2

I UV mine with a script in init.d. It helps tremendously with heat. If the chip can handle it, then why not?
[Nexus 4 Original Android Development] 75markus:
i just wanted to say that it´s already uv´ed by default, and Harsh has choosen values to ensure best stability & battery life for the average user.

if you can tweak some more mV and it´s stable, go ahead.

i never had heat problems and my battery life is great with this kernel, so i don´t bother :)
[Nexus 4 Original Android Development] Stylez Ray.:
Could someone please upload his script for governor settings so I can change it to my likings to get rid of trickster?
[Nexus 4 Original Android Development] FatalityBoyZahy:
+1
[Nexus 4 Original Android Development] :
Mine still don't work so I'm stuck with trickster, all my other scripts work, voltage just keeps giving me a exec '/system/bin/sh' failed: No such file or directory frustrating as hell though I found Novastar halfbreed coded Harsh kernel to be just what I wanted, just pulled the latest boot image from the ROM, using an old version of trickster cause the latest one screws around with the colors cause of gamma interface
[Nexus 4 Original Android Development] jarayn:
Mmm really?

I change min and max cpu to 384 and 1350. I figured that would be better for battery than 1026 and 1512. Are you saying thats not true?

If the colors in that hardcoded kernel are so good why do you need to mod them with trickster? Why not just go with stock and adjust?

I have seen no issues with the latest version and "screwing with the colors". It works perfectly what is the problem?