yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] benrees21:
If coming from another kernel, flash stock boot.IMG, flash kernel. Right? Just checking, I'm loyal to the Trinity Kernel but while Morfic is on holiday I thought I'd try some others out.

Because I'm a Nexus b!tch and I like to run the latest source and binaries!!
[Nexus 4 Original Android Development] elwaxman:
Sure wish i can try this kernel out but the DL links are down in op, does anyone have an alternative DL link?
[Nexus 4 Original Android Development] benrees21:
Was just about to ask myself. Does anyone have a link to the latest stable?

Because I'm a Nexus b!tch and I like to run the latest source and binaries!!
[Nexus 4 Original Android Development] AppReviewBros:
Here, I just uploaded it:

http://www.sendspace.com/file/kmubio

Sha1: b405be47562e50fb5e0c35b129f213dcddb49819

md5: 8f334de1b295e96ad21073efaf7df3f8
[Nexus 4 Original Android Development] giantflash:
Also the stock kernel and a few others use the "project butter" implementation which lets the min frequence jump to 1GHz if you touch the screen, so it's just normal that they will be more responsive, but it eats battery of course, too.
[Nexus 4 Original Android Development] elwaxman:
Thank you, I do appreciate it!!
[Nexus 4 Original Android Development] ceejay83:
Yea but why is game performance so bad?
[Nexus 4 Original Android Development] Connor Baker:
Hey all!

Thank you for your awesome work Show! I do have a quick question regarding UV though. On the latest Xylon ROM (12/20/12) using the Trickster Mod app, I noticed that the values I've specified for voltages don't stick through use within the phone. I'll have the lowest power set at 650mV, and then I come back into the app and it's set at 700mV. Any clues? No reboots, and I haven't set it to change on boot.
[Nexus 4 Original Android Development] joshnichols189:
700mV is the lowest the kernel allows so anything lower will default to that.
[Nexus 4 Original Android Development] show-p1984:
2phase was included. It might influence that.

What he said. :p

To the offline site:

My server had a few hickups the past days, which I will discuss soon with customer support. I just didn't want to do anything on it before Christmas.

Server restarted and online!
[Nexus 4 Original Android Development] Crenshaw-PCGH:
In germany its Christmas.. Where is the sweep2wake?? :D ;)
[Nexus 4 Original Android Development] denzel09:
+1

Sent from my Asus Nexus 7 3g 32GB
[Nexus 4 Original Android Development] Connor Baker:
Thanks for that. Was wondering if there was anything wrong with my flash. Is there any way to UV lower on a different kernel? Want to know because on my old Infuse, UV'ing reduced the heat created by the processor (if only slightly).

Connor Baker

Also, whats the gain in overall "snappiness" of the device between CPU and GPU overclocking?
[Nexus 4 Original Android Development] show-p1984:
Sweep2wake is trying to analyze why my server thinks it's running out of ram and killing off all processes.

Seems to be a Debian issue though...

Yeah it's time for

apt-get dist-upgrade
[Nexus 4 Original Android Development] joshnichols189:
I believe the only kernel that will allow a UV below 700 right now is Motley, and he isn't sure it is actually taking effect.
[Nexus 4 Original Android Development] undercover:
In Germany it's Christmas Eve. As it is everywhere else on 24th of Dec.
[Nexus 4 Original Android Development] ctfrommn:
Awesome kernel. It is now much better than it was on v.5. I am getting pretty amazing idle temps and drain. I will need another day or so to determine battery effects, but it seems very promising so far. I also disabled 2 of the cores so I expect even better than usual battery. This kernel has the best thermal/performance ratio I have seen to date! Find a way to integrate some gamma tweaks into it and it may be perfect.
[Nexus 4 Original Android Development] katestar:
Hi, I am wanting to go back to a different kernel as I respect your kernel but I was having problems with lowest freq sticking to 384mhz when waking up. So I flashed matrix which is what I was using before and none of the cores would shut down. So I flashed yours back then flauxs rest kernel and the cores wouldn't shut down on the stock either. May I ask if you know how to fix this please? Maybe it's something about the disabling of mpdecisions?
[Nexus 4 Original Android Development] jassycliq:
Flash your ROM again. Then flash whatever kernel you want.
[Nexus 4 Original Android Development] show-p1984:
The scaling_min frequency is not changed once with my kernel. The only frequency that is being changed is scaling_max, which is also only changed when the device is being thermal throttled and restored back to the frequency it was before when the device has cooled down.

To your issue:

rename /system/bin/mpdecision_bck back to mpdecision &

rename /system/bin/thermald_bck back to thermald.

This is shown during the flash of the kernel.
[Nexus 4 Original Android Development] show-p1984:
After inspection of his source I saw that this is not even being used. (It is displayed, sure, but not the clock the system runs with)

https://github.com/motley-git/kerne...e6e55152399eca4d220fd96#commitcomment-2350864

I commented on his github repo so he can fix that.

btw: https://twitter.com/showp1984/status/283050098265571329
[Nexus 4 Original Android Development] estallings15:
Holy balls! 192 MHz? If that can be done without sleep of death issues... it will be a good day.
[Nexus 4 Original Android Development] meangreenie:
With 2 phase ondemand, does the 1st phase track down with the maximum clock setting ?

maybe?? this was the source of jerkiness i found when running games with ondemand, as I had adjusted the max clock setting for all cores down to 1.2ghz
[Nexus 4 Original Android Development] show-p1984:
You got somewhat lost in those posts.

Thank you for this, I will test it and should it work include in the next release.

Would have probably taken a bit before I would have looked at it, just because I simply don't care :p

EDIT:

Tried it, doesn't work. (aroma isn't shown at all now, though it is there, pwr btn vibrates)

But as I said, I don't care :p

The max clock won't be adjusted, 2phase just adds a step in between and if there is not enough load the cpu won't scale higher.

You can adjust it via sysfs to your liking. /sys/devices/system/cpu/cpufreq/ondemand/two_phase_freq (1.24Ghz is default)
[Nexus 4 Original Android Development] meangreenie:
Thank you show-p1984, I'm experimenting with a lot those ondemand settings now and getting great results. Your kernel is a dream.
[Nexus 4 Original Android Development] show-p1984:
Updated to 0.7!

* sweep2wake (there is one deep sleep issue remaining, you may have to 'sweep' twice)

* 192Mhz min clock

* added FASTER PVS bin acpu tables from caf and modified for oc

(if you have a FASTER cpu it will use those now)
[Nexus 4 Original Android Development] wera750:
Any plans to give this color adjustments?
[Nexus 4 Original Android Development] ceejay83:
Awesome, sweep2wake ftw
[Nexus 4 Original Android Development] noneabove:
I think I will give this a shot when you have your app out :D any chance of seeing a beta version of it around here ? After Christmas of course XD
[Nexus 4 Original Android Development] ctfrommn:
Is anyone able to download this on there phone? I never get a complete file doing it. From my computer is just fine.
[Nexus 4 Original Android Development] noneabove:
What browser?
[Nexus 4 Original Android Development] Weeehe:
Just downloaded it with Chrome
[Nexus 4 Original Android Development] show-p1984:
I think I have explained this before already, here it goes again:

Androids webkit is (for some reason) not transmitting the referrer URL. So if you click on the download link my server only sees that somebody clicked the download link, not that you clicked on the link ON bricked.de. Since direct linking to my files is forbidden the server will redirect you onto the main page. Androids webkit fails here the second time, it doesn't catch the redirect and wraps my homepage into the filename of the download. (open it with an editor... html code of my homepage -.-)

So every Browser using Androids webkit will not work.

I believe Firefox or Opera work just fine.
[Nexus 4 Original Android Development] ceejay83:
Download worked fine for me on chrome
[Nexus 4 Original Android Development] b4ifuru18:
Sweet! Thanks.
[Nexus 4 Original Android Development] pnut22r:
So smooth right now. Love the s2w feature. Underclocked, undervolted and smooth.
[Nexus 4 Original Android Development] zimphishmonger:
S2w working perfectly, no dual sweep necessary here. Underclocked to 1.1ghz, plenty speedy......

Sent from my Nexus 4
[Nexus 4 Original Android Development] vikas_toad:
what is all this red led light problem??

as far as i have read.. it happens only due to OCing or OCed kernel.. if i just flash this kernel (or any other kernel )and not do any OCing ..will i be fine?
[Nexus 4 Original Android Development] show-p1984:
As far as I know can't you get the red light shutdown anymore on Bricked, even if you try to. I did oc to 1.8Ghz and ran a stability test for two hours, everything is peachy.

Try it.
[Nexus 4 Original Android Development] AppReviewBros:
Just flashed the kernel and I must say the S2W feature works perfectly! It is really an amazing job you have done there!
[Nexus 4 Original Android Development] vikas_toad:
thank you,

but can you just explain me a bit more what it is.. also relating to other kernels?
[Nexus 4 Original Android Development] AppReviewBros:
As others have mentioned, the first thing I have actually noticed is that gaming is not smooth at all compared to the stock kernel.
[Nexus 4 Original Android Development] show-p1984:
As you can see from the two quotes above there are some things you can experiment with. especially the two_phase_freq of ondemand.

The red led shutdown is triggered when your soc is getting too hot.

The reason why you get it on stock kernel or other kernels using thermald from qcom is that thermald sucks. Hard. Even the stock kernel implementation sucks. Both are not working correctly.

That's why I included the msm_thermal implementation from the pyramid and improved it. It offers you 3 throttle steps that will be taken before it shuts down your phone (without the red led, since msm_thermal shut down your phone)

Under normal circumstances (20°C room temperature) your phone should jump between your selected max freq and the first throttle step (1.3Ghz). There are still two more steps that will be activated should the temperature rise further.

Enough detail? :)

I have written a longer post with a few guidelines on how to configure it yourself a few pages back (should you want to switch from the default values)

I will update the second post with more information.
[Nexus 4 Original Android Development] ceejay83:
I have no knowledge of this, and don't know what this means. What value should i use if i want smoother gaming?
[Nexus 4 Original Android Development] jan.ringas:
Everything's working fine, thank you very much for this year's early first christmas present! ;)

I have one question though regarding

As long as my screen turns off after sweeping, will my phone go into deep sleep or may the remaining issue cause the phone not going into deep sleep although the screen is turned off?

---------- Post added at 09:57 AM ---------- Previous post was at 09:54 AM ----------

I would guess that you set the value of the two_phase_freq higher / closer to your max_freq. To do so you should use System Tuner, Kernel Tuner or any similar app.
[Nexus 4 Original Android Development] show-p1984:
Your phone will sleep normally, the only thing that might happen is that you have to 'sweep' two times to wake it up (power button will work always). This is one last very random issue with sweep2wake and affects nothing else.

Exactly. (or use the shell or an init.d script)

###

I have added the explanation of my mpdecision and 3-phase thermal guard in the second post.

Look here.

A few people might not understand this the first time reading through, but please don't bombard me with questions.

Read it again and try to understand it. This is explained as easy as it gets.

(or search the thread, I have dropped an explanation here and there for thermal stuff already)
[Nexus 4 Original Android Development] ptr_hamilton:
Damn how much i missed sweep2wake :D

Finally have it back

Thank you so much show p

Merry Christmas to all of you
[Nexus 4 Original Android Development] paratox:
does this kernel overwrite touchscreen firmware with E027 version or will E015 stay after a reboot when i flashed E015 before manually?
[Nexus 4 Original Android Development] show-p1984:
There was something i had forgotten today... :D

I did not make any changes to the touchdriver firmware update function. Mainly because I did not feel any reason to, the issue described by some people just never occurred for me.
[Nexus 4 Original Android Development] paratox:
It would be nice if you could remove update function so we can flash E015 manually and it will stay after e reboot. default every other one will have E027 so nobody will have a downside. thanks for your nice work!
[Nexus 4 Original Android Development] joshnichols189:
Merry Christmas Eve/Christmas everyone!

.7 is running great with the exception that I cannot get my phone to go into deep sleep. I actually have fewer things running in the background thanks to s2w but my phone just sits on 192mhz without properly deep sleeping. Any ideas?
[Nexus 4 Original Android Development] aventu:
Thank you very much Dennis :good:

Is "Project Butter" still active? The frequency doesn't lock at 1GHz when you touch the screen. I noticed a few lags as well.
[Nexus 4 Original Android Development] Crimsonthunder:
No I think project butter is not active.
[Nexus 4 Original Android Development] AppReviewBros:
Renamed both mpdecision and thermald and now everything's running as smooth as it can get. Back to stock until the lag issues get solved.
[Nexus 4 Original Android Development] Stylez Ray.:
Still having problems with my phone being laggy sometimes after waking up the device..happens on interactive governor...I hope you get this fixed as I think some people prefer that project butter feeling!
[Nexus 4 Original Android Development] estallings15:
He can only undo the poor kernel design so much at a time. Give it some time. OP has made great leaps with his kernel. Google sacrificed EVERYTHING for smoothness, including game performance and battery life. The phone is, what, 6 weeks old? It will get better.
[Nexus 4 Original Android Development] shaider_516:
I guess it not working with cm10.1, im stuck at google logo.

sent from my awesome Nexus 4
[Nexus 4 Original Android Development] Stylez Ray.:
That's absolutely fine with me! I know he is aware of this problem as I already reported it some ages back.

I am in now way rushing or begging...I am just a user of this wonderful kernel and the dev can take any time he wants and can do anything he wants with it! Using it though as this problem is annoying (sometimes) but not a biggie for me!
[Nexus 4 Original Android Development] reneph:
Its working fine with cm10.1 here!
[Nexus 4 Original Android Development] wera750:
So everyone using on-demand on this kernel?
[Nexus 4 Original Android Development] jarjar124:
sweep2wake is just simply awesome! thanks!
[Nexus 4 Original Android Development] bumbumquietsch:
In the s2w video it looks like you use Pin-Lock but still have the lockscreen widgets. How's that possible?
[Nexus 4 Original Android Development] JonnyJaap:
grouper?!

Hello my friends, happy X-mas :)

I want to flash the kernel, but the screen turned slightly into green/blue.

And there was are notification it says: "You are flashing Brickeg-Kernel on the Google/LG Nexus 4 (grouper)".

But the codename for the Google/LG Nexus 4 is mako.

Why says he "grouper" and not "mako" ?

I downloadet it her .
[Nexus 4 Original Android Development] SleemLDJ:
Can I flash this on CM10.1?
[Nexus 4 Original Android Development] chiensibut:
I dont know if s2w is gonna drain battery and unlock it self if it in pocket
[Nexus 4 Original Android Development] joshnichols189:
The one at the top is correct, just make sure the file name has n4 in it and you will be fine. It is probably just reused from the grouper kernel.

Yes
[Nexus 4 Original Android Development] show-p1984:
Issue tracker -> new issue -> enhancement

Thanks.

My n4 sleeps as it should. I suspect a pebcak-error (or kzb-transistor issue as we would say in Germany)

Project butter != min frequency boost.

Project butter is a huge huge huge huge huge project, and it's very useful so far, but whoever thought of the min frequency boost should just rethink this approach. (it's disabled in bricked because it sucks.

No log @issuetracker -> no fix.

Yes, at least everyone should. It's recommended to do so. (and it is default)

No idea, it just works (stock 4.2.1)

Probably because I am a lazy person and just c&p the installer from the grouper and forgot to change that. #fixed

Yes it works on cm10.1.

Read the 2nd post, brush up your knowledge on capacitive touchscreens and if you don't want it, disable it.

Btw anyone who shows me reproduceable unlocks in the pocket gets a DOTA2 beta key. #improbable
[Nexus 4 Original Android Development] joshnichols189:
So would you say it is improbable I'll be able to help the situation? Battery seems fine thanks to the lower min frequency but of course it would probably be even better in deep sleep. Maybe I'll try a clean slate later on in the day. Thanks for your hard work, Merry Christmas! I'll shoot a few brewskis your way next paycheck :)
[Nexus 4 Original Android Development] show-p1984:
How did you manage to establish that you phone doesn't sleep?

You phone won't sleep under these circumstances:

- usb is connected

- charger is connected

- you are in call

- your screen is on

- data is being transmitted over wifi

- data is being transmitted over cellular

- various other interrupts and wakelocks (kernel)

- an app keeps your phone awake with wakelocks (userspace)
[Nexus 4 Original Android Development] shaider_516:
Im on latest cm10.1 build, its just that any kernel wont boot but francos. I dont know what's wrong, i did wipe cache and kernel reset on other instances. I really wanna try this kernel and faux, i've been using their kernel since my sensation days.

sent from my awesome Nexus 4
[Nexus 4 Original Android Development] show-p1984:
flash cm-stock boot.img

flash this.
[Nexus 4 Original Android Development] DroidRC1:
I'm getting screen touches while on a call with your kernel ...think its cause of sweep2wake feature

BTW Merry Christmas
[Nexus 4 Original Android Development] jhericurls:
Franco uses his own ramdisk. Flash the Faux reset kernel, before flashing Brick.

http://faux.androidro.ms/mako/mako_421_reset_kernel.zip
[Nexus 4 Original Android Development] joshnichols189:
CPU-spy and BBS are reporting that deep sleep is an unused frequency, with most CPU time being reported as at 192mhz. I don't have anything out of the ordinary that would be holding a wakelock, I actually have fewer processes running in the background than usual. I just had a random reboot (no fault of the kernel), which wiped my BBS logs but I will take a look when I can again to make sure.
[Nexus 4 Original Android Development] shr33kant:
It's sleeping fine for me.

Sent from my Nexus 4
[Nexus 4 Original Android Development] cescof:
What about battery life with this kernel?
[Nexus 4 Original Android Development] jhericurls:
Flashed 0.7 this morning. Currently on 37% battery with 3:30 hours screen time. And this is with sync on.

Xylon rom, mileage on your ROM may vary.
[Nexus 4 Original Android Development] joshnichols189:
Figured it out, for some reason media scanner went AWOL. It wasn't showing up under battery usage as a big wakelock because I haven't charged to full in a few days. Thanks Show-p!
[Nexus 4 Original Android Development] cescof:
I've tried to install over franco r19 on slim 4.1.2 beta 1 but i was in stuck with boot.

No way to start... any suggests?
[Nexus 4 Original Android Development] ceejay83:
Flash the rom, gapps, and bricked kernel again
[Nexus 4 Original Android Development] jhericurls:
Read my post on the previous page.
[Nexus 4 Original Android Development] shaider_516:
Same benchmark with franco but less heat from the back. I think the UV causes the less heat when playing or benchmarking, im on v7 with -100mv

sent from my awesome Nexus 4
[Nexus 4 Original Android Development] noneabove:
Lol **** am I doing something wrong to not get that much deep sleep ? :S

---------- Post added at 12:59 PM ---------- Previous post was at 12:58 PM ----------

How'd you figure it out and what did you do to fix it ?
[Nexus 4 Original Android Development] joshnichols189:
I was in a low service area the last time I charged to full and I remembered that a game I was downloading was stuck in limbo. I basically just went to running processes and closed the download manager service that was running. All BBS and Gsam told me was that Android OS was sucking up my battery so I closed the related packages under running until I found it.
[Nexus 4 Original Android Development] noneabove:
Ah weird.. I have android os up at 23%, 17% drain in 7 hours with 41 min screen on, not terrible, but android os seems oddly high.. :S
[Nexus 4 Original Android Development] pac213:
Is this compatible with CM 10.1? and Do I need to install boot.img on the first page? Will it wipe my phone?
[Nexus 4 Original Android Development] jarjar124:
no it will not -___- please use the search button. People asked this so many times.

you're not the only one. I didn't touch my phone for the last 2 hours and Android OS was running the whole time which drained about 3-5%.... most of the time it was in deep sleep (2hrs) but the other 1hr was at 192mhz.... even though i wasnt using it :/ this sweep2wake thing is great, but I'm not sure if it's a fair trade-off for battery life.
[Nexus 4 Original Android Development] Mahdi786:
Hi showp, just installed your kernel after a long time with on franco's kernel, I was waiting for sweep2wake. One thing that's bugging me is Franco hard coded some colour values into his kernel and is made a big difference with greenish tint we have on our phones, if you could include that it would be great, no matter how I try to adjust the colour values I can't get rid of that nasty green,

Otherwise this kernel is great so far deep sleep is fine, sweep2wake sometime take a few swipes but you mentioned that, good we can save our hardware keys a little. Can't comment on battery drain yet. Waiting for your app so I can support you.
[Nexus 4 Original Android Development] romeoliny:
Hey Showp. I finally decided to give your 7.0 kernel a run and I'm loving the battery so far and after the proper kernel resets no lag issues yet. Thanks very much.

Other than the dual Sweep for sweep2wake that you already know about I also noticed that after shutting the screen off with a sweep that a blue tint appears on the screen when sweeping it back on. It seems to struggle through the blue a few times with a momentary flicker to the colors I set but eventually just sticks to the blue until user resets the colors on the app (faux clock) in this instance. Stock ROM here 4.21. Hope you'll find this info useful.

Thanks again!

Edit: Switched to Franco's color adjusting app seemed to resolve the color not sticking issue despite repetitive sweeps on and off.
[Nexus 4 Original Android Development] Cydras:
Hi,

Is sweep2wake not eating the battery, why the touch must be always on?

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] FSRBIKER:
Please move to before download link or change the font size of the warning about coming from another kernel especially Franco's.

Just installed, love sweep to wake feature. Thanks for your work.
[Nexus 4 Original Android Development] romeoliny:
Update: Appears that after deep sleep the screen will indeed revert back to old color settings rather than ones set with third party asps and hold a blue tint. Appears to be Sweep2wake related.
[Nexus 4 Original Android Development] Mahdi786:
Settings stick fine for me using trickster mod