yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] jhericurls:
Re: [KERNEL][Feb 3][Linaro]Exp:b32/Main:b57 _motley kernel for the N4

Undervolting doesn't give you that much more battery life.

First check if your getting high drain on standby. If so, its app causing battery lost.
[Nexus 4 Original Android Development] oblivionstalker:
Hi, i got a problem with wifi, on screen off after a period of time, no data can be send or recevied. i,e, only when i turn my screen on, i can only received whatsapp message and email that was sent like an hour ago. Anyway i can fix this?
[Nexus 4 Original Android Development] ltylty123:
Some apps must be running in the background that causes the drain. I dont think i will get only 1.5hours of screen time even without uv.

Im using the uv values through Trickster MOD given by z3r0_x since i have fast binned chip as well. hispeed_freq set at 91800 instead. 5+hours of screen time with auto brightness on.
[Nexus 4 Original Android Development] freaksamael:
here: http://xdaforums.com/showthread.php?t=2072930
[Nexus 4 Original Android Development] apascual89:
Re: [KERNEL][Feb 3][Linaro]Exp:b32/Main:b57 _motley kernel for the N4

@ motley. Where can you set all the presets described on post #2 in the source? Like the boost pulse max speed, etc.

Like always, thanks for your work!
[Nexus 4 Original Android Development] jazzboyrules:
Hey guys, I have added the script for holoblue in my script post. I have renamed the variables in the script to match those used by moles to avoid confusion. Hey! and he used inline gamma var tweaking this time like I did last time. So that part of code got some good use. :D
[Nexus 4 Original Android Development] JaysonthePirate:
Re: [KERNEL][Feb 3][Linaro]Exp:b32/Main:b57 _motley kernel for the N4

I'm running the latest b57 build, but am still draining about 5%/hour on hspa+ Att signal strength of 2-3 bars. Can anybody help me diagnose this wakelock? :/ can't find any mention of it online.
[Nexus 4 Original Android Development] azrash:
Re: [KERNEL][Feb 3][Linaro]Exp:b32/Main:b57 _motley kernel for the N4

You are using the mainline version. The latest stable version is exp b31. The naming might be experimental, but it is perfectly stable. Exp b22 onwards have the Hsic patch.

Flash the appropriate version of latest b31 and i am sure those hsic wakelock would drop a lot.

Hope this helps.

Sent from my Nexus 4
[Nexus 4 Original Android Development] JaysonthePirate:
Re: [KERNEL][Feb 3][Linaro]Exp:b32/Main:b57 _motley kernel for the N4

My mistake, I'm on b32 already.
[Nexus 4 Original Android Development] jazzboyrules:
Can you verify if you get a similar drain on wifi overnight? If the battery level is almost flat on wifi then you can be sure that the cause of this is not some app. Battery drain when idle is expect to be higher when on mobile data than on wifi.

What apps show up in the Alarms section in Better Battery Stats?

Also do you have Location Sync on? That could also be the reason for the drain. I have set my location updates to manual and Bactitude app updates my location every hour. That way I don't see the auto location update drain and I also get the benefit of Google Now updates based on location.
[Nexus 4 Original Android Development] ctfrommn:
Then you have a runaway app/process. I get like 1-2% hsic wakelock using b32. What is showing in your battery stats as using the most?
[Nexus 4 Original Android Development] whittikins:
Re: [KERNEL][Feb 3][Linaro]Exp:b32/Main:b57 _motley kernel for the N4

Thanks for the scripts. How can I make them work on Harsh kernel? It supports gamma but uses a different checksum method I think.

Edit: I got it to work by changing the red to r, green to g, and blue to b. Thanks for the scripts!
[Nexus 4 Original Android Development] JaysonthePirate:
On wifi the battery drain is very low. Last night it was completely flat for about 3 hours, then for the next 3 it was a little less than 1%/hour. So maybe it might be an app?

I didn't check the alarms section of BBS, but I'll idle my phone today then send you all the screens you need. Also my location reporting is turned on for Latitude and Google Now. What's Bactitude? You mean Latitude?

In the system battery usage report I believe Android System is using the most in terms of %. No particular apps stand out. I'll post more pictures later today. Just let me know what screens you guys need. I had similar results using Franco's Kernel as well, so it might be some app I'm running. If it was I thought I'd be able to find it by now.
[Nexus 4 Original Android Development] jazzboyrules:
I meant Bactitude Backtitude. You set the Latitude updates to manual and then set Backtitude to update the locations instead in the way you want.
[Nexus 4 Original Android Development] AirOne70:
Just download, extract and copy/paste your file to my init.d folder ?

It's work with Motley Kernel ? (For Faux: http://xdaforums.com/showpost.php?p=37749861&postcount=178 )
[Nexus 4 Original Android Development] jazzboyrules:
Simply unzip it and execute in Terminal with su enabled. Once you get the verification message showing the set rgb and gamma values after running it and those values ARE what you expected to be then go ahead and put it (unzipped of course) in init.d if you want to. Yes, the zips in this post work with motley's kernel.
[Nexus 4 Original Android Development] bamsbamx:
Well, i had a SoD yesterday... this is what i did:

Turn bluetooth on

Connect phone to my car

Then press power button to lock the screen

Push play in the car... all music sounded well

When i disconnect the car engine bluetooth disconnected

Go to turn on the screen but phone didnt turn on...

Its not the first time it happens this although it doesnt happen always.... no lastkmsg

Undervolted to 650mV @300MHz
[Nexus 4 Original Android Development] jazzboyrules:
Re: [KERNEL][Feb 3][Linaro]Exp:b32/Main:b57 _motley kernel for the N4

I got an SoD when I used to undervolt. I haven't seen that issue since I stopped doing that. Try running the kernel at the stock settings and then see if that gets rid of the SoDs.
[Nexus 4 Original Android Development] JaysonthePirate:
Re: [KERNEL][Feb 3][Linaro]Exp:b32/Main:b57 _motley kernel for the N4

Follow up with battery stats today. Added backtitude to change latitude polling frequency. Battery drain still around 5%/hr
[Nexus 4 Original Android Development] anoymonos:
Re: [KERNEL][Feb 3][Linaro]Exp:b32/Main:b57 _motley kernel for the N4

If I am running an Aokp rom which version of version 31 should I use to flash?
[Nexus 4 Original Android Development] azrash:
Re: [KERNEL][Feb 3][Linaro]Exp:b32/Main:b57 _motley kernel for the N4

AOSP

Sent from my Nexus 4
[Nexus 4 Original Android Development] whittikins:
Motley, I got a SoD (I think?) on b32 just now. I turned the screen on, and the touchscreen was unresponsive. A few seconds later, it rebooted. Here's the last_kmsg. https://www.dropbox.com/s/nux536lqzqjzih2/last_kmsg.txt

I'm running the latest Xylon nightly, and my process was:

- flash xylon

- flash gapps

- flash motley_n4_exp_build_31_initd.zip

- flash motley_anykernel_nexus_4_EXP_build_32.zip

It was running fine for a few hours. Also, I'm not undervolting. The only init.d I use is for gamma/rgb. Can you tell anything from the log?

Thanks!

EDIT: I think this might just be a Xylon issue because I just saw several other people reporting reboots with the latest nightly (2/7).
[Nexus 4 Original Android Development] ceejay83:
Re: [KERNEL][Feb 3][Linaro]Exp:b32/Main:b57 _motley kernel for the N4

Is interactive the default governor for b32?
[Nexus 4 Original Android Development] cocchiararo:
i tried running your scripts with moles contrasty kernel (wanted to try holoblue and halfbreeD), and also with faux 006b7.

I get what i attach.

I tried running it from tasker too.

EDIT: ok, sorry, somehow i thought i was in some other thread :P maybe this only applies for this thread's kernel ?
[Nexus 4 Original Android Development] thracemerin:
Are you running the script as root?

If not, type 'su' (no quotes) into the terminal first, then run it.
[Nexus 4 Original Android Development] gaeng4665:
AW: [KERNEL][Feb 3][Linaro]Exp:b32/Main:b57 _motley kernel for the N4

Which version to use with carbon rom? Thanks for the answer in advance
[Nexus 4 Original Android Development] cocchiararo:
yes, i am.

i noticed it complains about missing/non existent "kgama_ red", and in the directory it looks for it, it really does not exist. There is a "kgama_ r" tho. (Same thing for each color)

EDIT: changing that did it
[Nexus 4 Original Android Development] thracemerin:
You're using faux kernel? cuz faux123 uses kgama_r instead of kgama_red.
[Nexus 4 Original Android Development] cocchiararo:
i am now (i was not before when it did not work either)

thx
[Nexus 4 Original Android Development] trismegistos:
AW: [KERNEL][Feb 3][Linaro]Exp:b32/Main:b57 _motley kernel for the N4

Yes

---------- Post added at 11:48 AM ---------- Previous post was at 11:46 AM ----------

Lol? You are on faux and posting your problems here?
[Nexus 4 Original Android Development] cocchiararo:
did you read my EDIT mr nice ?
[Nexus 4 Original Android Development] ceejay83:
Re: [KERNEL][Feb 3][Linaro]Exp:b32/Main:b57 _motley kernel for the N4

Anyone?
[Nexus 4 Original Android Development] z3r0_x:
Already answered: YES!
[Nexus 4 Original Android Development] gaeng4665:
AW: [KERNEL][Feb 3][Linaro]Exp:b32/Main:b57 _motley kernel for the N4

Anyone?
[Nexus 4 Original Android Development] ceejay83:
Re: [KERNEL][Feb 3][Linaro]Exp:b32/Main:b57 _motley kernel for the N4

Looks like moles revised the half breed gamma settings

http://xdaforums.com/showthread.php?p=37774762
[Nexus 4 Original Android Development] z3r0_x:
It's based of AOSP
[Nexus 4 Original Android Development] zagzag99:
Re: [KERNEL][Feb 3][Linaro]Exp:b32/Main:b57 _motley kernel for the N4

Gr8 kernel.

Can it include 2 way recording support for CallRecorder?
[Nexus 4 Original Android Development] syncopy:
2 way recording is not supported on any of the N4 kernels at the moment IIRC.

---------- Post added at 11:25 PM ---------- Previous post was at 11:23 PM ----------

AOSP.
[Nexus 4 Original Android Development] trismegistos:
nope! did it now, sry for my comment :angel:
[Nexus 4 Original Android Development] efan3719:
could someone explain to me how to use this like i'm 5? i'm just not getting it. i've tried copy and pasting it into terminal after typing SU but it doesnt seem to do anything. idk what i'm doing.:confused:
[Nexus 4 Original Android Development] IAmAN00bie:
You have to turn your screen off before the changes take effect.
[Nexus 4 Original Android Development] efan3719:
:silly: i'm dumb. thank you.
[Nexus 4 Original Android Development] qwerty9876:
The halfbreed colours has undergone a small update/revision:

http://xdaforums.com/showpost.php?p=37774762&postcount=262

Any chance we get an update to your post/zip, jazzboy?
[Nexus 4 Original Android Development] cocchiararo:
not rocket cience :P
[Nexus 4 Original Android Development] efan3719:
i dont think that'll work on motley. those values are still in hex.
[Nexus 4 Original Android Development] ceejay83:
Re: [KERNEL][Feb 3][Linaro]Exp:b32/Main:b57 _motley kernel for the N4

It's pretty simple to convert. Just edit the first halfbreed file that jazz posted.
[Nexus 4 Original Android Development] efan3719:
i noticed in his file he has unknowns. and no grey. i'm not sure what is what in order to edit.
[Nexus 4 Original Android Development] ceejay83:
Re: [KERNEL][Feb 3][Linaro]Exp:b32/Main:b57 _motley kernel for the N4

Read jazz's post.you only need to edit the orange values.
[Nexus 4 Original Android Development] efan3719:
yeah i know but they dont match. he has three variables that say unknown. idk if that is grey or what. or are they just left alone?
[Nexus 4 Original Android Development] ceejay83:
Re: [KERNEL][Feb 3][Linaro]Exp:b32/Main:b57 _motley kernel for the N4

Just leave it alone. I honestly can't tell the difference between the two halfbreeds
[Nexus 4 Original Android Development] cocchiararo:
values are not in hex, they are already converted, the values in hex are comented, i needed to store them somewhere when i did it :P
[Nexus 4 Original Android Development] efan3719:
my apologies. i didnt notice that. i'm sick with the flu. haha :p
[Nexus 4 Original Android Development] cocchiararo:
i have no idea how that happened, since i took the first halfbreed script and edited the values, but it was something that happened in my pc :P
[Nexus 4 Original Android Development] karanrajpal14:
Re: [KERNEL][Feb 3][Linaro]Exp:b32/Main:b57 _motley kernel for the N4

Umm motley, do you plan on adding 2 way recording?
[Nexus 4 Original Android Development] jazzboyrules:
Re: [KERNEL][Feb 3][Linaro]Exp:b32/Main:b57 _motley kernel for the N4

The contrasty script in the BB CODE tags and zip was written when it wasn't figured out that the second last number in the gamma array is perhaps for the grays. So that was named "unknown2" (as there was another unknown preceding out in the array).

But in holoblue onwards, Moles from his investigation shared that that second last number is perhaps for the grays. To avoid confusion, I followed his define names so that people can easily correlate between the script and his gamma tweak updates and update those values by themselves in future.

He still used hard coding for 2 values (holoblue onwards) in the gamma array for which I used the names unknown1 and unknown2. If you open the holoblue and halfbreed scripts (in my script post), you will realize what I am talking about.

One thing to note if you haven't realized already : don't use holoblue as a template to simply change the variable values because contrast, saturation and other gamma parameters are tweaked separately for each color channel.

You can use the halfbreed as a template to make your own halfbreed version 2 script as channel specific tweaking is not done for that version.

TLDR: Use the zipped halfbreed script as a template to tweak the variable values to match the gamma tweaks Moles publishes in future. ( The script post referenced in this post: http://xdaforums.com/showthread.php?p=37673702 ).

---------- Post added 10th February 2013 at 12:00 AM ---------- Previous post was 9th February 2013 at 11:53 PM ----------

Yes that contrasty script I posted there with orange color highlighting is still valid. In the layer script zips I posted, I have simply renamed the variable names to match those of Moles to avoid the confusion. The base structure and function of all the scripts are the same.
[Nexus 4 Original Android Development] efan3719:
thanks for the reply and explanation. i appreciate it. i'm pretty sure i understand it all for the most part. shouldnt need to bug you guys anymore. :laugh:
[Nexus 4 Original Android Development] Mattymat:
Re: [KERNEL][Feb 3][Linaro]Exp:b32/Main:b57 _motley kernel for the N4

What are the chances that this kernel will eventually be able to work with the faux display app? I know it's for his kernel, but is it possible to that it would work with motley?
[Nexus 4 Original Android Development] stivy73:
R: [KERNEL][Feb 3][Linaro]Exp:b32/Main:b57 _motley kernel for the N4

Sorry for the noob question, but how can I use/install this .7z file? :confused:

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Original Android Development] zstoichev:
The Exp:b32 version causes problems with the Camera - damaged images, freezes, and ever reboots, phone gets hotter. No such issue with stock 4.2.1 kernel. I am on Stock ROM. Any one else experiencing this behavior?
[Nexus 4 Original Android Development] ceejay83:
did you change the undervolt settings?
[Nexus 4 Original Android Development] batman368:
didn't notice such behavior, and I have undervolted my mako quite far. but I'm on paranoid ROM. camera works fine every single time
[Nexus 4 Original Android Development] Remoteconcern:
Re: [KERNEL][Feb 3][Linaro]Exp:b32/Main:b57 _motley kernel for the N4

Agreed. No camera problems here, but they normally occur when the top frequency step doesn't have enough voltage. I can reproduce your problem by lowering 1500mHz to 950mV.
[Nexus 4 Original Android Development] jazzboyrules:
Re: [KERNEL][Feb 3][Linaro]Exp:b32/Main:b57 _motley kernel for the N4

Hey my explanation wasn't with an intention that you don't "bug" anyone in future, it was so that you get more freedom in playing with the gamma tweaks.

Feel free to have any questions you may have. This community is about learning and contributing.
[Nexus 4 Original Android Development] _motley:
No problem, thanks. Once a script gets contaminated, it will propagate all over the place.:eek:

There was an issue with this script, I didn't go back to see if he removed or corrected it. It's best to learn about the gamma interface in general (see post 2). After that, it will be easier to understand what others are doing via these more flexible "test and set" scripts.

Thanks, it looks like an interesting feature. The patches available are for the old 2.6 msm kernels unfortunately, but they do have similarities to our msm 3.4 kernel. If there was a patch I could just apply today and make it work for the N4, I would definitely do so. I have no plans to add, but I can take a look at the old patches when I get some free time. No promises that I will do anything with it though. This type of stuff can get very complicated and suck a lot of time.

I added support for this a couple versions back. AFAIK, it is still working ok. Let me know if anyone is having issues. Many of us have started using scripts since it exposes the whole gamma interface and takes away the limitations of the GUI.

Yes, the only time I have seen and heard of issues is when voltages are set to low at the top frequency. If you set the max frequency too low, it might also be sluggish and cause issues, I haven't tested that much. I leave my max freq set at 1.51 or higher all the time.
[Nexus 4 Original Android Development] jazzboyrules:
Hi motley,

I recently started using the Touch Control app. I am using the PA ROM with Pie enabled.

The issue I am seeing is that once the phone goes to deep sleep, if I wake it up using the power button or if the phone wakes up by itself (due to alarm), the whole screen become touch unresponsive. The only resort left to me would be to restart the phone.

I am using the latest version of Touch Control Pro. Would you know the possible causes that makes the screen unresponsive? Would any governor settings help avoid this issue?

Any way in which I can help you and bponury debug this?

I posted the same on Touch Control thread too and people have mentioned that they don't see this issue on stock or faux while running Paranoid Android.
[Nexus 4 Original Android Development] _motley:
Hi, I looked at your post in the Touch Control thread as well. It doesn't look like he changed anything besides tweaking his identification of kernels that it will work with. Once a kernel's "footprint" changes, it can easily break support. This is something only his application can deal with when it happens. However, the good news is that it does not appear to be the problem in this case.

I just upgraded to v1.5a using Rasbean and I don't have any issues waking the device with the power button or the touch events after letting it sleep for awhile. I force closed the app, cleared data and rebooted just to be sure. When the TC module loads, it still correctly identifies the kernel as "motley", so I think we are still in sync with kernel support.

Another user posted in his thread about using the app with PA and more specifically with Pie. It appears there is a known issue with Pie, so this makes the situation more convoluted. Does this sound like your issue too? Perhaps you can try running without Pie enabled and see if it still behaves the same way. Also, if you were on v1.5 before 1.5a, make sure you force close the app, clear data for the app, and then reboot. I never tried v1.5 straight up, just 1.3, 1.4, and now 1.5a, so it is possible we had an issue with that version and didn't know it. I don't think it changes the kernel module it uses unless you clear everything out and start over. It might not make a difference since the module he uses for this kernel doesn't have appeared to have changed, but it is worth a try.

I don't think this is a kernel issue, but I am happy to help however I can. It is best if you post your dmesg for bponury so he can take a look at what his kernel module is doing. He will likely want a logcat as well for his app events, but I am not sure how it all works. It sounds like he may have seen something like this before so perhaps he can figure it out.

P.S. thanks for the donation! And also thanks for the support and contribution you make in this thread:)
[Nexus 4 Original Android Development] jazzboyrules:
Hi motley, thanks for your reply. I had uninstalled Touch Control. Today morning I updated PA to its 3.0 version so hopefully that fixed something that clashed with Touch Control. If I had one thing to sacrifice from motley, Pie and Touch Control, I would sacrifice Touch Control because the other 2 things are much more useful to me :) I have cleared Touch Control's data and I'll see how that goes.

You posts and your thread are a learning experience. You are welcome :)
[Nexus 4 Original Android Development] Ulver:
Re: [KERNEL][Feb 3][Linaro]Exp:b32/Main:b57 _motley kernel for the N4

Great kernel motley! This is on b32
[Nexus 4 Original Android Development] magestic1995:
Hey guys I had a question I have been trying to figure out. So I am running b32 with RootBox and I was wondering. I was going to try to under-clock my device, but when I do I notice that now I have more of my cores running compared to the singular core. That runs when not under-clocked. Does this actually cause more battery consumption or will this save battery? Thanks for any help. Im having trouble trying to explain my thoughts
[Nexus 4 Original Android Development] Logi_Ca1:
Re: [KERNEL][Feb 3][Linaro]Exp:b32/Main:b57 _motley kernel for the N4

Hi motley! Firstly I just wanna say thank you for a great kernel!

Secondly, at this point in time do you know if setting voltage at 600mv actually does this, or is there a hard limit somewhere that prevents voltage from going below that hard limit. From my observations 600mv is completely stable at 384mhz, and given how much time the phone spends at 384mhz I think that the 600mv limit that you have set should be lowered even further, assuming of course that the SoC actually does follow this voltage.

Would be great to hear your thoughts on this, thanks!
[Nexus 4 Original Android Development] dark_ente:
Re: [KERNEL][Feb 3][Linaro]Exp:b32/Main:b57 _motley kernel for the N4

When you run processor intensive task, it'll use more power, for normal task it'll use less power. Depends on how you use your phone.

Sent from my Nexus 4
[Nexus 4 Original Android Development] jazzboyrules:
Re: [KERNEL][Feb 3][Linaro]Exp:b32/Main:b57 _motley kernel for the N4

Hi motley,

I found some more info about the touch screen issue when using Touch Control. I have posted the details here: http://xdaforums.com/showthread.php?p=37852474

Please have a look when you get a chance.

Update:

Also can you please also enable the Pointer location in Developer options and verify that you are able to make the trace touch each of the 4 edges? That will confirm the compatibility of TC+Rasbean+motley.

Stryder from the TC thread has reported that TC is running perfectly for him for TC+PA+Faux combination.

This issue is really intriguing, it gets activated for a very corner case. Probably very few like me come under that case. :(