yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] yak84:
Running SlimKat 4.4.3 and bricked 4.4.3 beta ,all is A-OK :D
[Nexus 5 Original Android Development] fbf2201:
Latest exp contains 4.4.3 source. Stable is still from 4.4.2, but also works though.
[Nexus 5 Original Android Development] spica123:
Stable works really well! Battery life and performance are simply perfect.
[Nexus 5 Original Android Development] estallings15:
Just wanted to report in that I've had zero bugs with the latest test build on 4.4.3.
[Nexus 5 Original Android Development] adame09:
Latest beta is smooth!!!
[Nexus 5 Original Android Development] AFCAjax:
Hi folks,

Anybody can tell me how battery life is with S2W copared to non-S2W at the moment? Is any progression made to make it use less battery? :)

Thanks in advance!

AFCAjax
[Nexus 5 Original Android Development] yak84:
S2W is still quite a battery hog.
[Nexus 5 Original Android Development] resynx:
The latest beta is running extremely smooth :D
[Nexus 5 Original Android Development] kkk-sgs2:
Hi, i have extrem thermal problems with this kernel. I watch YouTube on 80°C. I use trex rom based on carbon 4.4.3.

This kernel is one of my favorite, but not usable at the Moment for me. Clean install after 4.4.3 update. Anyone the same Problem?

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] yak84:
Well after playing 20 min straight of plants vs zombies the CPU temp gets to 65C , watching videos in YouTube for the same time only gets the CPU temp to 50-55 C depending on the ambient temp. Start by finding what process running in background and ramping up CPU freq.
[Nexus 5 Original Android Development] show-p1984:
Something is using your CPU in background. If I enable background data collection in KControl and play some YouTube video for about 7 minutes (in this case NASA Johnson style, because it was the first HD video that came to mind) I get about 30-45% less average CPU usage than you do. Which is a lot. For reference see attachment.

It's also normal that a CPU that is being used > 50% is getting warm/hot over time. Especially with a higher ambient temperature and / or charging, exposing the device to sun light, etc etc.

After all the "heatsink" on our devices mostly starts and ends with the memory chip, which is pop-stacked to the top of the soc.

You can also see that the kernel is doing what it is supposed to, once the temperature hit 81°C the frequency was throttled and in both cases it dropped fairly quickly to the clear threshold.

A kernel can't change the laws of physics though.

PS: when taking the screenshot the ambient temperature was about 28°C, so not that cool either.

At this temperature, this curve here shows 8 minutes of flicking through apps, reading websites, news, watching a short YouTube video and updating my todo list: https://www.dropbox.com/s/lrp8ymwp7if4cst/Screenshot_2014-06-11-16-47-52.png

Also bear in mind that background data collection can be taxing too. A full history requires 960 items to be held in memory, parsed, drawn as a graph and scrolled on each update each second. This was the main reason as to why I disabled it as default and reduced the history kept by about half. Especially tegra devices had huge trouble updating > 1000 items. KControl2 addresses this issue with a native solution instead of relying on slow java.
[Nexus 5 Original Android Development] kkk-sgs2:
I will check for a background process. But 80°C on 60% usage is to high, no charger, no lights and ambiente is 30°. On stock with 100% usage, i have lower temperatures. I will search a process and test a little bit with other Roms.

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] show-p1984:
You obviously didn't read my post. That is impossible. There isn't a make-it-hot button in the kernel, nor would I press it if there was. When all cores are online and you have a constant of 50%++ CPU usage, all kernel running the same voltage and frequency will yield the same CPU temperatures, provided external influences are the same as well.

There is no way there would be a difference. Not in this universe at least.

Yes, stock throttles earlier, too early (qcom sets the throttle temp to 90°C, bricked uses 85, 5°C below. Lg set 75°C for the n5 if I remember correctly), but if you run it for 10minutes it doesn't make any difference anymore. The luring suspicion is that lg throttled the n5 earlier to boost the g2 in comparison, since the benchmark results plumit downwards if you throttle too early.

Anyways, as evidenced by my screenshots and another user your temperature is way to high for YouTube only. Find the rouge process and kill it.
[Nexus 5 Original Android Development] CaspaTheGhost:
But there is the 'drop it like its hot' button in Kcontrol no? ?

Jokes aside, if there was a make-it-hot button you know people would press it regardless!

Sent from my Slim N5
[Nexus 5 Original Android Development] Citizen_Snips:
Show-p1984. I love how you always have a detailed, technical answer to your users questions. Also I love your sass. Don't ever change. Thanks for developing for us. You really are great. I bought KControl, but I'd gladly buy KControl2 as well if it's a paid app. You're the man.

Sorry for OT...
[Nexus 5 Original Android Development] ausaras:
SlimKat & 4.4.3

Hi,

Anyone running SlimKat weekily 5.7 or 5.8 (android 4.4.3) with Nova Launcher 3.0.1?

Bricked is my favorite kernel and the latest beta was updated for 4.4.3 but I am experiencing lags when using Nova Launcher. The stock Slim Kernel works well. Elemental X 0.43 is a bit laggy as well but better than Bricked. Elemental X 0.44 is very smooth.

Is it just me that Bricked is laggy on SlimKat? I wiped System and cache before "dirty" flashing.
[Nexus 5 Original Android Development] DroidIt!:
I have the same setup as you but I use Apex. With apex there is a setting to keep the launcher in memory to reduce redraws and I never see any lags. That's under clocked to 1.7 GHz. Is there any such option in Nova?

from my N5
[Nexus 5 Original Android Development] dwxvi:
Hello everyone! I decided to try out the latest beta of the kernel, and whenever I clean flash the latest SlimKat Weekly with this kernel, my GPS is always turning itself back on after I turn it off. I decided to clear the data of Google Play Services and reboot to see if that would help in any way, but it didn't. When I clean flash SlimKat with just the stock kernel, I do not have this problem. How on earth does this happen?
[Nexus 5 Original Android Development] :
Yes there is.
[Nexus 5 Original Android Development] yak84:
I have the same setup , SlimKat 5.8 & nova , I use the latest bricked beta and have no lag whatsoever, not in nova and not in general.

P.S

I don't use that keep in memory option.

---------- Post added at 06:39 AM ---------- Previous post was at 06:33 AM ----------

It's very strange indeed, I clean flashed SlimKat 4.7 and on top of that 4.8 and don't have this problem.
[Nexus 5 Original Android Development] DroidIt!:
Me neither and for sure I updated my radios. However, I don't have WiFi on my N7.

from my N7
[Nexus 5 Original Android Development] ausaras:
Just clean flashed SlimKat Weekily 5.8 with Nova 3.0.1 and it is smooooooth. I guess my dirty flashing was the problem.
[Nexus 5 Original Android Development] PetritH:
Yeah, dirty flashing cause more problems than people think, I always find time for a clean install every week :p
[Nexus 5 Original Android Development] RobbieL811:
Does anyone know the sysfs path to input boost frequency in this kernel?
[Nexus 5 Original Android Development] yak84:
/sys/kernel/msm_mpdecision/conf/

And here is all the info you need :

http://xdaforums.com/showpost.php?p=47399641&postcount=2
[Nexus 5 Original Android Development] RobbieL811:
Damn. I feel kinda stupid now! It was in the OP the whole time. Thanks man. I'll go off continuing to be a dummy.
[Nexus 5 Original Android Development] derukun:
I didn't even enable swipe to wake/sleep or double tap and the wakelocks are just killing my battery. Franco all the way..
[Nexus 5 Original Android Development] flar2:
I don't think you gave it a fair chance. Those wakelocks likely have nothing to do with the kernel. Did you reinstall the stock kernel before you installed bricked?

Not even my thread, but it just bothers me when people make posts like this.
[Nexus 5 Original Android Development] Tylog:
Hm ..... No, I let it be :)

Tapatalk Team SlimRoms
[Nexus 5 Original Android Development] raubkatze:
I used Franco's r53 a few days to compare with the latest Bricked and now came back :)

To get Bricked work correctly, as flar2 said above, you should restore original kernel at first.

So now I have stock 4.4.3 + 20140605_083038_exp-9bcd40e and this combo works perfectly well.
[Nexus 5 Original Android Development] RobbieL811:
You do not know what you are talking about. This kernel doesn't carry a lot of wakelocks that "kill" your battery! Educate yourself before you make posts.

Sent from my Nexus 5
[Nexus 5 Original Android Development] DroidIt!:
Agreed. Tried a lot of kernels across a lot of different devices and this is the most conservative battery-wise. Also it's the snapiest I think I've ever used. That's about as good as it get's for mobile devices. ;)

from my N5
[Nexus 5 Original Android Development] derukun:
There are four new sources of wakelock when I look at BBS's kernel wakelock. Event something, I've never seen such wakelocks until I flashed bricked. They only appeared after flashing bricked.

That being said, I didn't flash stock kernel prior so I'll try again and we'll see how it turns out.

Franco is gdlk still, the only kernel where I can get 7 hr sot on a single charge with average usage (Web browsing, wifi and lte, DS emulator gaming, texting, shooting some videos).

Or maybe I'll get even better after correctly installing bricked? We'll see
[Nexus 5 Original Android Development] yak84:
Does anyone have noticed more power consumption in deep sleep with the latest beta based on 4.4.3?

With the stable kernel I had a 1-3% drop over night (8H),

Now I have 7-10% drop.

No wakelocks , 99% deep sleep according to BBS.

I thought may be the new radio is at fault so I reverted to the 4.4.2 radio but with no luck.
[Nexus 5 Original Android Development] RobbieL811:
I am about to go to sleep here in a bit. I will leave my phone unplugged to check what mine is for you. do you leave WiFi on & stuff like that?

Sent from my Nexus 5
[Nexus 5 Original Android Development] yak84:
Thanks, WiFi on location off.
[Nexus 5 Original Android Development] jlevy73:
Show some respect for the developer. You're post is just straight rude. Show-p was the first developer to implement DT2W or S2S even before LG came out with knock on. Furthermore, your post is lacking any useful information. If you have wake locks post a screenshot of BBS.
[Nexus 5 Original Android Development] derukun:
lol, relax. I'll take one the next time I try the kernel.

Trying to find stock 4.4.2 kernel but no luck.
[Nexus 5 Original Android Development] Guzanni:
I'm one latest Mahdi, 4.4.3 ofcourse. Which version of bricked kernel can I use? Is it compatible with 4.4.3? I hwd way better battery life with bricked kernel when on Mahdi 4.4.2, that's why.

Verstuurd vanaf mijn Nexus 5 met Tapatalk
[Nexus 5 Original Android Development] jlevy73:
Which Rom are you using? My recommendation would be to dirty flash your rom then re-flash the kernel.
[Nexus 5 Original Android Development] derukun:
I'm on SlimKat. SlimKat has its own kernel that I'm not sure I can flash Bricked on top of.
[Nexus 5 Original Android Development] jlevy73:
I'll look for a stock kernel for you to flash.
[Nexus 5 Original Android Development] Phazmos:
You'll probably be good. Slim uses bricked mpdecision - and that's usually the cause for trouble with other kernels.
[Nexus 5 Original Android Development] Tylog:
You can :) no need to wipe anything.

Tapatalk Team SlimRoms
[Nexus 5 Original Android Development] derukun:
The thing is, I'm on Franco at the moment. And when I initially flashed Bricked on top of Franco, I had some issues with wakelocks.
[Nexus 5 Original Android Development] Tylog:
Dirty flash Slim ROM, after this Bricked Kernel and you are fine.

Tapatalk Team SlimRoms
[Nexus 5 Original Android Development] yak84:
[MENTION=4195844]show-p1984[/MENTION] Is there a way to know if the phone enters the deepest sleep state?
[Nexus 5 Original Android Development] hooliganx:
https://play.google.com/store/apps/details?id=com.bvalosek.cpuspy.realgpp

N5*SlimKat.5.0.(4.4.2)*El-X.044

*ART*TWRP.2.7.0*0.13
[Nexus 5 Original Android Development] fix21:
Nice kernel but when i play games and charge the phone battery drops down instead of increase the percents.
[Nexus 5 Original Android Development] show-p1984:
If you meant the usual "Deep Sleep state":
[Nexus 5 Original Android Development] yak84:
I meant the C1-C4 states.
[Nexus 5 Original Android Development] linezero:
The phone gets really hot when playing games. I wonder why? :/
[Nexus 5 Original Android Development] fix21:
yes i use another kernel and i try play games again the phone charge normal ....is it possible to fix this?
[Nexus 5 Original Android Development] yak84:
When you playing games the CPU and GPU are working hard.

More cpu load ->higher cpu freq ->more energy drawn from the battery+charging =massive heat.

At some point the battery will get to a threshold temp and will stop charging.

To make a long story short , avoid if possible charging and playing games.

---------- Post added at 10:33 PM ---------- Previous post was at 10:29 PM ----------

If the other kernel have lower thermal throttling point and to a lower cpu freq then yes.

You can change thermal throttling temp with Kcontrol app.
[Nexus 5 Original Android Development] linezero:
I'm nt charging while I play any game. it jst simply gets hot and hotter later. Games like clash of clans maybe for an example.
[Nexus 5 Original Android Development] fix21:
As I said before with the previous kernel used to play and charge my mobile for over an hour without any problem. :/ i play clash of clans too by the way.
[Nexus 5 Original Android Development] show-p1984:
This.

Or have a look at the second post on how to do it manually. ( http://xdaforums.com/showpost.php?p=47399641&postcount=2 )

If you have no experience modifying settings depending on a threshold (allowed_XXX_high) and a clear threshold (allowed_XXX_low), then just lower each setting by the same value, for example: 15 °C.

Otherwise take care not to raise the clear threshold (allowed_XXX_low) above the threshold (allowed_XXX_high) or mid above high, etc... :) This will cause unwanted behavior, mostly resulting in a permanently throttled device.
[Nexus 5 Original Android Development] show-p1984:
Nope you meant C0-C3 :)

Upcoming KControl Feature @ attachment, still #unfinished. Would call it early beta state. It works as far as it reads stats out, but there is some more "magic" to do :)

EDIT:

I think I can leave it like this: https://www.dropbox.com/sh/l973z99dduykce7/AABhLfr3DXUeptrsxYdxAzdXa

;)
[Nexus 5 Original Android Development] SnoopHTC:
Hello Show-p1984, just to say Thanks for your great work!! your kernel work perfectly for me with Mahdi-Rom and i patiently wait kcontrol v2 ?☺

@++^^
[Nexus 5 Original Android Development] RobbieL811:
What do you mean? You want the stock Google 4.4.2 kernel? Just download the stock 4.4.2 factory image & extract the boot.img & flash it in fastboot.

Sent from my Nexus 5
[Nexus 5 Original Android Development] derukun:
I'm a noob, no idea how to do that. I was looking for flashable .zips.

By the way, dirty flashed SlimKat and flashed Bricked.

Still getting wakelocks.

They're listed under BBS kernel wakelock as

"event0-781", "event1-781" and so on and so forth (event2, event3, event4, event5).

Each event has kept the phone awake for about 40 minutes so far. 40 minutes screen on time, with 80% battery on WiFi.

On BBS it states the Screen has been on for 40m but it has been awake for 3h 18m. In fact, the phone has only been in deep sleep for 14 seconds.

What the heck is going on?
[Nexus 5 Original Android Development] RobbieL811:
Those are in "kernel wakelocks" or "partial wakelocks"? You are gonna get most of your info from the partial wakelocks area. That is gonna be all of your user apps. PM me some screen shots of your partial wakelocks, alarms, & CPU states.

Sent from my Nexus 5
[Nexus 5 Original Android Development] derukun:
They're under kernel wakelocks.

There's nothing wrong with my user apps, nothing in the apps have changed from when I flashed Bricked and when I flashed Franco.

Everything looks the same under partial and alarms.

On CPU states, the phone has spent more time on 300 mhz than anywhere else. No deep sleep going on at all.
[Nexus 5 Original Android Development] RobbieL811:
I'm trying to help you, & you won't let me. Will you please send me the screen shots that I requested? Just send me a BBS dump.

Sent from my Nexus 7
[Nexus 5 Original Android Development] yak84:
The CPU spent a lot of time at 300MHz because, I guess ,your phone won't get in to deep sleep.

We need to find the cause and for that you need to upload a screen shot of BBS kernel wakelocks.

Do you use any kernel tweaker app?
[Nexus 5 Original Android Development] derukun:
A screenshot isn't necessary when I just listed the wakelocks on the kernel wakelock section...

I have Trickster Mod, MP Decision is off though. And I'm not using S2W or double tap.

Since you all insisted, here is the bull**** in all of its glory:
[Nexus 5 Original Android Development] yak84:
OK let's try this:

1) uninstall trickster.

2) go to recovery and format system manually.

3) flash slimkat+gapps.

4) flash bricked kernel.

5)reboot to system.

Use the phone and report back.
[Nexus 5 Original Android Development] RobbieL811:
You are acting like a doosh. Like you don't WANT to fix the problem. I am done helping you. You say that you are new but somehow you know all of the answers?? Flash back to Franco.

Sent from my Nexus 7
[Nexus 5 Original Android Development] show-p1984:
This is an arm perfmon feature.

eventX-yyyyy

yyyyy = process id.

Process yyyyy is keeping your phone awake. Fix that.
[Nexus 5 Original Android Development] derukun:
Under processes I have "kworker/u:0" with Uid:0 running 1 hr 31 m 22 s.

I don't know what process "781" is nor how to check it...
[Nexus 5 Original Android Development] RobbieL811:
You won't lose ANYTHING if you do exactly as he told you.

Sent from my Nexus 5
[Nexus 5 Original Android Development] show-p1984:
You won't if you do what you quoted.

There are

no such issues.

An app is causing your issues, see my previous post, which you just ignored completely.

This kernel is pretty much flash and go.

You had to reboot in between right? Probably installed a few apps?

That's why your previous boot was ok and this one isn't. A rouge process/app is keeping your phone awake. Fix it.

By a real stretch this could also be ramdisk related since franco overwrites the ramdisk with his own iirc. Bricked is much more "social" it uses the ramdisk you have installed on your device. To test this just flash the stock boot.img from google and then bricked.

This is kernel

unrelated

.
[Nexus 5 Original Android Development] derukun:
To be fair, I didn't install any apps in between flashing the two kernels.
[Nexus 5 Original Android Development] RobbieL811:
He doesn't want help. He has completely ignored a oust or two of mine & he replies with his own answer to the problem..."this kernel has problems". I haven't had ANY problems out of this kernel. I use FK every now & then too & don't get me wrong, he is a good dev but this kernel is twice as stable on my device. I never have a problem with it.

Sent from my Nexus 5
[Nexus 5 Original Android Development] derukun:
Lol wat are you seriously speaking for me? Who do you think you are...

I'm just saying, there's no possible room for error on my side. I haven't installed any apps in between flashes, everything is the same. Maybe not directly Bricked kernel's issues, I take that part back. But definitely not anything that I did... everything has remained the same aside from flashing different kernels.

Its not like I don't want a solution, I'm just dismissing what's unlikely.

I still don't know what this kworker app is though.
[Nexus 5 Original Android Development] RobbieL811:
Not speaking for you, just posting what I have seen. You haven't taken any of the advice given to you. You have had a bad attitude about Bricked since your first post in this forum about the problem. If you would have made a clean flash of your system, like [MENTION=5590545]yak84[/MENTION] said to do, the problem most likely would have been solved. Then, I asked for a BBS dump and some screenshots. You didn't send the dump and you posted a screen shot that I didn't request! You posted the screenshot that YOU said was causing the problem. Go into recovery and wipe /system, then reflash your rom & gapps, and Bricked, wipe cache and dalvik, and fix permissions and reboot phone. This will most likely fix the problem. If not, at least we know that your system is clean, and we can begin to help figure it out. Who knows what all has been done to your device over the time??? This is why what yak84 suggested was a good idea.
[Nexus 5 Original Android Development] derukun:
Sigh, okay. I'll be back after I try that.

(This better be worth it >_>)
[Nexus 5 Original Android Development] show-p1984:
/proc/<pid>/
[Nexus 5 Original Android Development] derukun:
Under the processes tab, I couldn't find anything that matched the ID 781. :/
[Nexus 5 Original Android Development] RobbieL811:
ALWAYS make a backup.
[Nexus 5 Original Android Development] derukun:
I did what you told me to do (format system, flash slimkat/gapps, flash bricked, wipe cache/dalvik).

Same problem already. The phone isn't deep sleeping. What to do now? Now the kernel wakelocks are referencing uid 918. But again, no such process exists ...
[Nexus 5 Original Android Development] yak84:
Install a file explorer like root explorer and go to proc folder , in proc search for folder named 781 ,in that folder go to file named status and open it.

You will see the name of the process listed in the file.
[Nexus 5 Original Android Development] derukun:
918 is system_server...

After wiping, 781 is not in the proc folder anymore. Maybe 918 has replaced it?
[Nexus 5 Original Android Development] show-p1984:
It has nothing to do with a wipe.

/proc is a kernel generated folder, and the process ids are like condoms, there is a new one on every execution of that process.

Soooo... system_server is causing your issues? I guess it isn't the kernel after all? :rolleyes:
[Nexus 5 Original Android Development] derukun:
But what is system_server?

Again, I switched back and forth from Franco and Bricked. I had no wakelocks from any apps on Franco.

Still don't know what the real problem is.
[Nexus 5 Original Android Development] show-p1984:
Last time: Franco overwrites your ramdisk with his own. It's not unplausible that a change in that ramdisk causes issues. Though system_server shouldn't be affected theoretically.

Anyway: Flash your roms/stock roms boot.img, then Bricked. Bricked will always use the ramdisk that is installed, whereas other kernels just overwrite it.
[Nexus 5 Original Android Development] yak84:
There always will be some kind of weird process running , I have process 768 for example but it only kept my phone awake for 1min in 24h so if the wakelock of the process is neglectable it's OK.
[Nexus 5 Original Android Development] :
But its not negligible. Its kept the phone awake ever since it boots, it never goes into deep sleep cuz of it.

Installing slimkat replaces Franco's with slimkat's kernel and ramdisk. The only option left would be to try 4.4.2 stock kernel, but I don't know how to extract boot.imgs and stuff.
[Nexus 5 Original Android Development] :
which version of Slim are you running

and which version of bricked?
[Nexus 5 Original Android Development] :
Latest stable of Slim, I believe build 5.

And the latest stable of Bricked as well.