yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] delacrow:
Re: [KERNEL][DEC.24]Bricked-Kernel|3.4|v0.7|thermalguard|mpdecision|stickyfre q |OC&U

Interesting. Slide-to-wake app users seem to associate the wake locks and battery drain with carrying the phone in a pocket. I also notice that often when i have to carry a phone in a pocket for a while the screen is no longer responding to the touch. Knowing earlier reports about potential heat issues - do you think there is something to it?
[Nexus 4 Original Android Development] show-p1984:
O'rly? I suggest you look again at my git.

if wakelocks are higher (aka = more time spent active) then battery can't be better. A sleeping device will use less power than one holding a wakelock.

This is not Slide to wake, so no idea.

Sweep2wake is currently broken. S2W2 will fix that once it is integrated into KControl.

There are no heat issues.

Could you please maintain some context within your post the next time? 3 topics in one line is quite confusing to read.
[Nexus 4 Original Android Development] gavin-phelan:
Re: [KERNEL][DEC.24]Bricked-Kernel|3.4|v0.7|thermalguard|mpdecision|stickyfre q |OC&U

Any eta on kcontrol?
[Nexus 4 Original Android Development] undercover:
Re: [KERNEL][DEC.24]Bricked-Kernel|3.4|v0.7|thermalguard|mpdecision|stickyfre q |OC&U

Only quoting what has been said. I don't have an opinion on that as I haven't tested it. On paper you are right, but we both know that weird things happen in the world of 1/0 :p
[Nexus 4 Original Android Development] show-p1984:
I am currently finishing up the cpu activity. (probably will be done with it today)

So that will be ready then, but the rest is still wip.

What feature of KControl do you want to see the most?

Actually, no. The world of 1/0 is pretty logical. Computer don't make any mistakes :)

Except when people interfere with it.

"Noobs think computers are perfect.

Advanced users think

they

are perfect and look at the computers for errors.

Hackers know that computers are almost perfect and look at themselves for mistakes."

Translated from German, hopefully it hasn't lost it's touch :)
[Nexus 4 Original Android Development] Emilius:
I would like to have mp decision (to put all cores on line), voltages and governor. ;)
[Nexus 4 Original Android Development] show-p1984:
I completely forgot voltages :eek:

Thx for reminding me :)

The next features being completed will be mpdecision, governor, thermal and color. Those are nearly complete.

Mpdecision will have an advanced mode, but that is currently under ndk development. Then I have to cook up a voltage ui :p

I can tell you what dependencies KControl will need in order to run:

Permissions:

Run on boot completed (to set the frequencies you chose)

Prerequisites:

Root (obviously)

Android api level 14 and above (ICS ++)

The final version will need a kernel compiled with CONFIG_KALLSYMS_ALL to archive 100% functionality.

(The next bricked version will have that)

The alert viewer will see the differences in the latest version:
[Nexus 4 Original Android Development] Emilius:
KControl will be massive, I can see that clearly. Well exactly what kernel support, massive.... :fingers-crossed:
[Nexus 4 Original Android Development] gianton:
Re: [KERNEL][DEC.24]Bricked-Kernel|3.4|v0.7|thermalguard|mpdecision|stickyfre q |OC&U

On which color defaults will you base yours, faux's or Franco's?

Thanks for your work.
[Nexus 4 Original Android Development] Emilius:
Just please don't make it so dark like some kernels. Personally I would like to stay the way how is now so everyone can do whatever...

---------- Post added at 07:22 AM ---------- Previous post was at 07:13 AM ----------

Oh btw show-p can you please make sure KControl will be possible to backup settings with Carbon.For some apps like XiiaLive I can not do that and that's killing me softly. :(
[Nexus 4 Original Android Development] gianton:
Sorry maybe I wasn't clear, I meant on which color code show-p will base his kernel? There are two well known already, color code based on faux and franco.
[Nexus 4 Original Android Development] show-p1984:
Default will be stock. Why? Because I happen to like it. :p

KControl will allow everyone else to set the stuff they choose on boot.

Carbon sounds nice :)

I can look into that but I can't see a reason why it would not work.

Hybrid Interface to support both.
[Nexus 4 Original Android Development] gianton:
Great thanks! :good:
[Nexus 4 Original Android Development] Emilius:
Show-p is there any chance to get conservative gov.? I am big fan of interactive gov. but conservative could be good choice. I would like to test it and compare.
[Nexus 4 Original Android Development] n3ocort3x:
Looks awesome and really really nice showp :) cant wait until we get final !
[Nexus 4 Original Android Development] TaRsY:
Hey show-p and others!

I'm happily using your kernel now on my Nexus too. Really missed this feeling again after selling my Sensation. :D

Today I got with my casual using (wifi on all day up, mostly browsing, whatsapp, reading pdf's (cheating on tests lol), no gaming 3h39min screen on time and 23% still left! So battery life, speed and stability is awesome.

It's OK now, this kernel doesn't have so much attention (they don't really know you because you were working on HTC), but if you release the next verion and the KControl too I hope you get more attention and the thread stays all the time on the first page of the developement thread. This kernel deserves much more users.

Here are my screenshots about battery:

https://www.dropbox.com/s/udzgu4jpey3ovne/2013-04-02 20.12.07.png

https://www.dropbox.com/s/tfrj2gfd9t90vyh/2013-04-02 20.12.12.png
[Nexus 4 Original Android Development] Emilius:
That is exactly my question. How come this kernel does not get more attention? This kernel is second to none. The best kernel ever. I am not kidding here. I was so unhappy when I find out that Nexus 4 will never get LeanKernel. Now, with Briked kernel I am set. Everything I wish for and more. The way how I use my phone I can charge every 3 days and it's till some juice left. Before Bricked to make true 2 days was hard. Thank you show-p :good:
[Nexus 4 Original Android Development] brainbeatuk:
Re: [KERNEL][DEC.24]Bricked-Kernel|3.4|v0.7|thermalguard|mpdecision|stickyfre q |OC&U

Any chance you can lower voltage threshold to 600 as I know my CPU is stable at 918mhz at 650 and 600 lower on another kernel

Eg 4x 182mhz at 825mv uses as much if not more power as 304x4 on Motleys for me.

I like the flow of your governor though does seem battery efficient.
[Nexus 4 Original Android Development] Emilius:
Can you share your voltages? I have -125 mW applied to all but I am not sure how low I can really go on 192 MHz.
[Nexus 4 Original Android Development] brainbeatuk:
Re: [KERNEL][DEC.24]Bricked-Kernel|3.4|v0.7|thermalguard|mpdecision|stickyfre q |OC&U

I couldn't drop more than -25 from kernel default. I'm back on Motleys for now.. Don't mean sound rude I use your kernel on nexus 7 is beast. What CPU binning do you have showp
[Nexus 4 Original Android Development] show-p1984:
That makes total sense because the kernel influences at which voltage your soc is happy.

Btw, this:

Sound like some dev forgot to lower the restraints, meaning:

You are not running 918Mhz at 600mV, it is just displayed and overridden by the kernel again. Running that would be crazy. Additionally to the fact that the PLL isn't calibrated for that voltage I would take a bet and say that the best chip you can have will at least require ~800mv @918Mhz to be stable, everything else is a lie. And even that would be the best chip of the century, soldered together by the hand of one of the hard working people in China who had to quit after this one chip. (because he kept whispering "My precious!")

I have a fast binned CPU, and no I do not undervolt. Why? Because crazy **** tends to happen if you do and I can't have that while developing.

918Mhz at 600mV... - It's like looking through a microscope at a cell culture and seeing a thousand dancing hamsters. It's impossible!
[Nexus 4 Original Android Development] Emilius:
You make me cry here.:crying:

Anyhow I would like to share my stable voltage. I did not have any crashes but each phone is different.

192 @ 700

384 @ 750

432 @ 762

486 @ 775

540 @ 787

594 @ 800

648 @ 812

702 @ 825

756 @ 837

810 @ 850

864 @ 862

918 @ 875

972 @ 887

1026 @ 900

1080 @ 925

1134 @ 937

1188 @ 950

1242 @ 962

1296 @ 987

1350 @ 1000

1404 @ 1012

1458 @ 1025

1512 @ 1050

I don't overclock my CPU or GPU. Usually I keep max. CPU clock at 1242. It is fast enough for my needs. Battery life on my mind all the time ;)
[Nexus 4 Original Android Development] El Nino1977:
Re: [KERNEL][DEC.24]Bricked-Kernel|3.4|v0.7|thermalguard|mpdecision|stickyfre q |OC&U

You should write a book "Show-p's metaphors" I would certainly buy it... :P It would cheer me up no end! ;) :D
[Nexus 4 Original Android Development] guru_shastri:
hi, a bit of a noob here, just flashed the 0.7 version.

its seems to get the device going a wee bit faster, but i can't see serious improvement in the battery life. i like the s2w very much, but could this be draining the battery?

i tried undervolting just a bit, are there any specific preferences to UV? or i'm just to lower it a bit at a time and as long as the device is stable things are ok?

another thing - i set the wifi to turn off when the device is sleeping, but it doesnt seems to do so. could it be a minor bug in the kernel?

thanks show-p. again..

i'm using stock ROM.
[Nexus 4 Original Android Development] gianton:
Sweep2wake drains your battery, I tried it and overnight lost 7-8% where usually loosing 1-2%.
[Nexus 4 Original Android Development] Emilius:
To turn off WiFi while phone is sleeping is a rom option. Go to WiFi settings. My suggestion is to leave it on because sync over WiFi will take less battery then sync over mobile data. Other thing about Bricked kernel. Grab the latest beta version .77 and test it without s2w. Make sure for a min. CPU clock to put 192 MHz. You don't need to undervolt but you can take down -100 mW without thinking at all. That should give you excellent battery life results.
[Nexus 4 Original Android Development] resynx:
Re: [KERNEL][DEC.24]Bricked-Kernel|3.4|v0.7|thermalguard|mpdecision|stickyfre q |OC&U

Excited to try out Bricked again pretty soon :D

Looking forward to KControl and s2w2 :)
[Nexus 4 Original Android Development] guru_shastri:
i've moved on to 0.77 and turned off the s2w and it does seem to slow the drain.

i hope s2w will get better in the future..
[Nexus 4 Original Android Development] -Asskicker-:
Installed latest Bricked yesterday and seemed to work quite smoothly but I had 2 problems;

- GPS not working: I'm not sure if this is even possible because of kernels, but I used the GPS during the morning and it instantly locked, I flashed Bricked during lunch break and when going home I couldn't get a lock with GPS any more. Only other thing I did was undervolt a tiny amount and install Trickster. Going to test it this evening with stock kernel.

- Big delay on turning screen on sometimes: Sometimes when turning the screen off and back on there is quite a big delay on the screen coming back on, could this be due to the tiny amount of undervolting I did?

If there's any information you need from me, please do tell. :)
[Nexus 4 Original Android Development] guru_shastri:
don't know what happened to your GPS. mine is working alright using 0.77 kernel.
[Nexus 4 Original Android Development] gianton:
+1 No problem with GPS, using it all the time with jassy's #3 version (based on 0.77). You should check your ROM settings, GPS issues are ROM related.

No delays in locking unlocking the screen, actually this kernel is very smooth everywhere.
[Nexus 4 Original Android Development] -Asskicker-:
Really strange, just reflashed stock kernel and still can't find GPS. I'll try to re-flash rom tonight :/
[Nexus 4 Original Android Development] Dr_Ash:
Can't get WiFi working

I can't get wifi working

busybox is installed and I can see the init.d folder in system/etc

I've flashed the kernel twice

ADB thinks my device is offline so I can't run "adb shell lsmod"

any ideas?
[Nexus 4 Original Android Development] jassycliq:
First off you need to update adb.

Second, when you connect your phone (adb debugging turned on blah blah you know the deal) check your phone. A little box should pop up, allow it.

Third, adb should be working :)
[Nexus 4 Original Android Development] mumaster20:
Got the same problem as Asskicker above me stated on the beta .77 kernel.

My screen won't turn on all the time when i try to wake it, there's quite a big delay between pressing the button, and the screen turning on.

This does not happen all the time though.

doen anyone know a fix for this problem?

Rest from the kernel is completely kick-ass!
[Nexus 4 Original Android Development] ctfrommn:
I would start with changing your min to 384 or 486 and see if that helps.
[Nexus 4 Original Android Development] jassycliq:
Try using kernel tuner on the play store to set values.
[Nexus 4 Original Android Development] gianton:
Do you recommend kernel tuner over trickster mod using with your test kernel?
[Nexus 4 Original Android Development] jassycliq:
With any kernel that's based off of shows I'd recommend that. For some reason other apps don't play as nicely with his kernel as Kernel Tuner does. Its a good app either way. Let's you modify the mpdecision values. Thermal also. Very much geared towards this shows kernel :)
[Nexus 4 Original Android Development] gianton:
I'll give it a try, been using trickster mod with no issues noticed BTW. Can you point me to what settings are you suggesting for mpdecision values?
[Nexus 4 Original Android Development] mumaster20:
I tried upping the minimum frequency of the cpu to 702 MHz and the problem seems to go away.

But ofcourse, i'm not going to let the min freq stay at 702, since it will be a constant battery drain in my pocket.

Now another thing i noticed is that the option for max screen off freq is greyed out, and its at 192 MHz.

Maybe thats the culprit?
[Nexus 4 Original Android Development] ctfrommn:
Thats definitely the culprit....dirty flash your Rom, Gapps, and then kernel again. That should clear it up.
[Nexus 4 Original Android Development] mumaster20:
will try that later, thanks for helping me!
[Nexus 4 Original Android Development] Emilius:
Put 192 MHz as min. freq. but try to put all 4 cores on line with Kernel Tuner and change gov. to interactive. My phone is crazy smooth that way and I don't have any look screen problems. Also you can try to limit max. freq. to 1.2 ghz for even more battery savings.
[Nexus 4 Original Android Development] ctfrommn:
This is his issue....

Now another thing i noticed is that the option for max screen off freq is greyed out, and its at 192 MHz
[Nexus 4 Original Android Development] Emilius:
That is exactly what I have. I am not sure is this an issue or Kernel Tuner just don't play nicely here. I don't have any problems with that even if is really true max. freq. is 192 when screen is off. We just need to wait for KControl. Until then Kernel Tuner is the best option i guess.
[Nexus 4 Original Android Development] italia0101:
This is what i was worried about.... Were you OCed? this has only ever occured when someone had OCed. or used an OC kernel.

Any chance you could make two versions. .. One that doesn't have any oc at all . but all your other stuff
[Nexus 4 Original Android Development] jc monkeyballs:
I re-flashed ROM to restore kernel, then wiped cache+dalvik and flashed the kernel. Like the other poster said, it's not every wake-up but it's often enough to be noticed. I'm going to stick it out with this kernel for a little while and see if it improves.
[Nexus 4 Original Android Development] ctfrommn:
Had to be...I ran multiple benchmarks and no frequency spikes over 1512mhz and no issues at all.
[Nexus 4 Original Android Development] jc monkeyballs:
Rule #1: Don't Panic.

I found a post from Faux that might be helpful:

http://xdaforums.com/showpost.php?p=35595046&postcount=1776

Really hope this helps.
[Nexus 4 Original Android Development] ctfrommn:
Kernel settings? Rom?
[Nexus 4 Original Android Development] Holo_:
Not to worry it does this when it gets really hot just let it sit cool for a minute ok now press and hold the volume down rocker yes just down then plug in your charger and don't let go to red led is gone and you inside the bootloader now you can proceed works for me all the time good luck
[Nexus 4 Original Android Development] Dan37tz:
Yeah, I pushed it to 1.7GHz with no voltage changes. I guess that's a risk I was willing to take and it bit me hard.

Anybody know if there is any life left in this Nexus or is it now a nice $400 paper weight? :fingers-crossed:

On the upside I swapped my SIM back into my Note 2 and boy did I miss this thing. :)
[Nexus 4 Original Android Development] italia0101:
There are a few suggestions above ... But from what I've heard its a hardware failure. . it really doesn't like going aboove 1.5
[Nexus 4 Original Android Development] ctfrommn:
That and the voltage required to do so is not good. If it was left stock maybe, but these Krait cores dont like voltage.
[Nexus 4 Original Android Development] Holo_:
N4 is fine red led is some kind of failsafe just follow what I said and you will be back in action I got the red led a few times today cause I push silicon to its limits but you fine ;)
[Nexus 4 Original Android Development] ctfrommn:
1720 is a full 100mv higher than the highest stock voltage at 1300mv. Love the kernel but I agree about offering either a non OC version or at least leaving voltages alone.
[Nexus 4 Original Android Development] Dan37tz:
Whooooaaa dude you're my hero. It's alive!! :good::good:

I think I'm going to have to back away, tail between my legs from this flashing addiction. I always have the worst luck. Restoring a previous nandroid as we speak. stock rooted rom and stock kernel then calling it a day.
[Nexus 4 Original Android Development] italia0101:
Awesome it worked!! thats brill, but yea, i wouldn't OC anymore
[Nexus 4 Original Android Development] caxio:
show-p1984 thanks for your wonderfull kernel now for nexus 4 , you can apply 2-way call recording patch?

thanks:good:
[Nexus 4 Original Android Development] Holo_:
Voltages need adjusting I agree hopefully next build uses stock or lower voltages

Pushing silicon to it's limits is not for everybody but a choice
[Nexus 4 Original Android Development] italia0101:
Yea I know ... It just seems this phone is a lot more temperamental when it cones to oc ...
[Nexus 4 Original Android Development] D-m-x:
I can confirm the lag after wake up. Compared to Francos Kernel, Bricked isn't that smooth sadly (for now). I went back for that reason.
[Nexus 4 Original Android Development] dw9906:
+1
[Nexus 4 Original Android Development] ctfrommn:
Kernel settings?
[Nexus 4 Original Android Development] Cydras:
I can't flash this Kernel. Aroma Installer is freezing.

I use CWM 6.0.2.0
[Nexus 4 Original Android Development] ctfrommn:
So you run 192/192 with no lag? Doubtful....what does youre CPU state history show as used frequencies?
[Nexus 4 Original Android Development] Emilius:
No I don't have any lags at all. But again, I use all 4 cores on line all the time and interactive gov. Battery life is just amazing that way and no lags at all. Nice and smooth.
[Nexus 4 Original Android Development] mumaster20:
Where can you adjust the minimum cores online? I'd like to try it.

In kernel tuner is doesnt seem to stick after I hit apply.
[Nexus 4 Original Android Development] Emilius:
Same here. sometimes after reboot I need to redu in mp decision min. cpu on line again. Sometimes is okay but sometimes is back to default. That is maybe Kernel Tuner issue. I have no idea. There is some more options in Kernel Tuner which dues not stick after reboot. :(

I am not that much upset with that. Just wait for KControl and then Bricked kernel will be full functional and everything will work the way it should.
[Nexus 4 Original Android Development] ctfrommn:
Its in /sys/module/auto_hotplug/parameters
[Nexus 4 Original Android Development] Emilius:
How come I dont have that "auto_hotpug" folder in sys/module?
[Nexus 4 Original Android Development] show-p1984:
Or not.

It's in /sys/kernel/msm_mpdecision/conf/min_cpus

You don't have it because we have my mpdecision.
[Nexus 4 Original Android Development] ctfrommn:
Ah, sorry all the others have it there.... I don't use this. I shouldn't have assumed:)

Sent from my blazing bionic Nexus 4
[Nexus 4 Original Android Development] CheesyNutz:
not to be a **** but how would you now if your phone has no lag from the screenshots you never use it
[Nexus 4 Original Android Development] show-p1984:
Since I am a perfectionist, I added some stuff to the cpu activity :)

Antutu CPU Benchmark.

Forked and built upon GraphView by jjoe64.

My fork fixed for api level 14 and above: https://github.com/showp1984/GraphView

EDIT:

Heating and cooling curves during a ~160 second stress test:

(yeah I updated it once again... being a perfectionist is a curse, I tell you... :D)
[Nexus 4 Original Android Development] Zarboz:
*looks for rag to clean up*

ohmuhgawd its t3h s3x
[Nexus 4 Original Android Development] resynx:
Too excited for your release showp!! :D
[Nexus 4 Original Android Development] Emilius:
Hmmm, haaaa, what? What make you say that? How I use my phone is not your business my friend. Please don't let me started. 3 hours on screen and 3 day without charging is what I am getting from Bricked kernel. Everything else you don't really need to know.

---------- Post added at 06:13 AM ---------- Previous post was at 06:09 AM ----------

+1 can't wait any longer :silly:
[Nexus 4 Original Android Development] Emilius:
KControl alpha? No? The staf you show us here make me so tempted. I have to have it man, now... :laugh:
[Nexus 4 Original Android Development] show-p1984:
I could throw out a stable with cpu control only, as that is officially #rockstable and finished. But that wouldn't make much sense.

The rest is going a lot faster though, I have all my classes created and ready for use now.

Btw did I mention the best thing about that graph? As long as you are in the cpu activity (doesn't matter if timeinstate, the main cpu screen or the graph) data is being collected.

That even includes going back to the home screen with the home button or screen off time (as long as the device does not sleep. KControl will not hold a wakelock). The thread keeps running so you can monitor stuff.

It only stops once you press the back button or close KControl over the recent apps menu.

#perfect monitoring tool. :) I already had a lot of fun with it ^^

Example of use: Monitoring thermal throttling while playing a game, etc...
[Nexus 4 Original Android Development] Dr_Ash:
video playback

I'm using CM 10.1 and noticed that when I install bricked kernel and try and stream a video from e.g. Facebook or my Dropbox - I can hear the audio but the screen stays black.

If I rotate the screen by turning it on it's side, the video appears for a fraction of a second and then the screen goes blank again.

Doesn't happen on CM 10.1 kernel.

Any ideas?
[Nexus 4 Original Android Development] show-p1984:
Just tried it, working perfectly.

Edit:

Oh you are using cm10.1, well I am using stock rom. Shouldn't matter though since cm should not break any stockish behavior.

Some ppl using cm should test this as well.
[Nexus 4 Original Android Development] Dr_Ash:
Just tried Motley kernel and video playback is fine with that.

It only seems to affect streaming video, as the same file played from my internal memory and dropbox works fine on internal memory but not from dropbox.
[Nexus 4 Original Android Development] raikesy:
I'm also on CM10.1 (compiled myself about an hour ago, no changes) and do not have any issues with streaming video.

Sent from my Nexus 4
[Nexus 4 Original Android Development] resynx:
Currently testing ondemand as it's the recommended governor. How has everyone else's experience been with ondemand vs interactive using Bricked? Would just like to hear :D