yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] thracemerin:
I seem to have fixed it at least temporarily, but I didn't do anything other than turn off and on wifi a whole bunch and now it's connecting every time again, no idea what the heck is up with that. :confused:
[Nexus 4 Android Development] ctfrommn:
Ok....thanks again Ubuntu 13.04
[Nexus 4 Android Development] thracemerin:
ok, grab the abootimg package

sudo apt-get abootimg

abootimg will let you take a boot.img and unpack it into the zImage, the config file and the ramdisk (initrd.img)

abootimg -x boot.img

you'll have to do a little more unpacking after that:

gunzip -c initrd.img | cpio -i

might want to move it into its own directory because it's going to dump the files into whatever directory you're in.

you can then look at/edit any files in the ramdisk that you want, when you're done repack it with (ensure there are no extraneous files, like the old initrd.img file are present)

find . | cpio -o -H newc | gzip > ../myinitrd.img

then you can use abootimg to repack it

abootimg -u boot.img -r myinitrd.img

if all goes well you can then fastboot that boot.img to see if it werked.

Note: you can also switch the zImage out by using abootimg

abootimg -u boot.img -k zImage

if your kernels zImage differs in size there may be a few other mods you need to make because it'll throw an error, but I can help you with that too if it happens.
[Nexus 4 Android Development] ctfrommn:
sudo apt-get abootimg

Invalid operation abootimg ??
[Nexus 4 Android Development] thracemerin:
oops :eek:

sudo apt-get install abootimg
[Nexus 4 Android Development] ctfrommn:
:D Thats better....do I need a boot.img from my Rom or just the one Ive been working on?
[Nexus 4 Android Development] thracemerin:
any boot.img will be fine, but if you want it to boot on your ROM I'd grab the one from there and work on that, you definitely want to start with one you know boots before you mess with it.
[Nexus 4 Android Development] ctfrommn:
Any idea what folder contains the governor settings?
[Nexus 4 Android Development] thracemerin:
should be in the init.mako.rc file, i think it's in the root of the unpacked ramdisk.
[Nexus 4 Android Development] ctfrommn:
It is...Im using the boot.img I was messing with earlier and all the settings I changed are there. I actually added it to my Rom and flashed it and all the settings are correct :)

I am wanting to use the anykernel zip that I started with. There is no ramdisk in an anykernel correct? It looks like the issue I had before was using the zImage and putting it in the anykernel zip and not placing the boot.img into the Rom itself. I assume I can do the zip though?

Im out of thanks for the day....but thanks so much for your help and patience :)
[Nexus 4 Android Development] thracemerin:
Yeah, if you're using anykernel it takes the boot.img that is already on the phone and throws the zImage into it, so if the ramdisk sets the governor to ondemand you can't do anything about that unless you do some fancy scripting (it's possible, just not that easy, show-p does it for bricked), it's easier to make such changes by flashing an entire boot.img.

Also, I'm glad to help, often times questions like this make me think about stuff and I learn something too.
[Nexus 4 Android Development] ctfrommn:
Gotcha....that explains why I couldnt change it....the ramdisk on my Rom boot.img was overwriting it. All should be well now. I do see why Franco and others modify the ramdisk though as this is the only place you can make these kind of changes.

Another new thing learned....cha-ching! :D
[Nexus 4 Android Development] thracemerin:
Using a full boot.img has it's drawbacks, like there are occasionally compatibility issues but it's far more complicated to make ramdisk adjustments with an anykernel script.
[Nexus 4 Android Development] moskito-hd2:
Hi,

i am on the "Rootbox" ROM and till yesterday motley's latest kernel was installed ;)

Today I installed your Kernel in the version 8.1 and till now, it works perfect :) :)

congratulations to you :beer: :thumbup:

moskito

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Android Development] pa.pn2:
kernel is really nice even on miui

and battery life is fantastic:good:

thx for continuing this masterpiece@thrace
[Nexus 4 Android Development] moskito-hd2:
yes, I am surprised, the battery life is fantastic. Thumbs up.... ;) :thumbup:

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Android Development] IAmAN00bie:
thracemin, what are your thoughts on the simple GPU governor that Faux recently implemented (I also believe the latest Franco nightly just implemented this)?

https://github.com/faux123/SGH-Krait/commit/a9361283fceebbf160c4507202515b0a4e83a814
[Nexus 4 Android Development] SkyBeam2048:
You might have a look here as well. Just be careful about voltages lower than 850mV on m+ kernel newer than Build 7. Previously voltage limit was set to 850mV which was fixed in Build 7. So builds after this will really apply lower voltages than 850mV. So be careful about any settings in the table which state to be stable below 850mV, they might have been tested on motley or m+ kernel below m+ Build 7 and therefore not been applied properly.

That does not mean you cannot go below 850mV. As you can see in the table I am running a couple of frequencies at 700mV. They even appear to be stable at 650mV for hours and suddenly might lead to spontaneous reboot.
[Nexus 4 Android Development] thracemerin:
Alpha with this enabled is incoming :D
[Nexus 4 Android Development] azrash:
Will s2w make it to the alpha as well? :P

Flowed from my Nexus⁴
[Nexus 4 Android Development] thracemerin:
DOH! I completely forgot about that :eek:
[Nexus 4 Android Development] Sblast:
thanks :)

Downloading from GOO!
[Nexus 4 Android Development] thracemerin:
Ok, new alpha is available in Post 4 (968bd10).

All the info regarding the simple gpu governor is in Post 4 as well.

S2W and S2S will be in the next alpha, SORRY!

Happy Flashing :victory:
[Nexus 4 Android Development] pa.pn2:
thx for the update

for miui just flash the miui base kernel and the updated kernel,right?
[Nexus 4 Android Development] thracemerin:
Should be able to just flash it over 8.1 without flashing the base.
[Nexus 4 Android Development] pa.pn2:
Worked. Just have to wait until trickster updates this gpu stuff lol
[Nexus 4 Android Development] Remoteconcern:
Does anyone know if s2w uses lots of extra battery? My power button is broken so I'd quite like to try it but I do value my battery life.
[Nexus 4 Android Development] veyka:
Thanks for the new WIP, did you get the patches to fix the notification light on cm in yet? Had a look but i don't think you pushed the source yet!

Cheers.
[Nexus 4 Android Development] thracemerin:
When I tested it last time it tended to use between .2% and .5% more battery per hour during idle.

Which patches were those? my notification light is working fine on CM to my knowledge.

And you're right the source didn't get pushed because my SSH key was wrong, ill push it now, but the only change was the GPU governor.
[Nexus 4 Android Development] veyka:
Sometimes when theres more than one notification it gets a bit mixed up and the light starts flashing random colours

patches:

http://review.cyanogenmod.org/#/c/43348/

http://review.cyanogenmod.org/#/c/43587/

2nd one is the kernel one, and without it I get the issue described.
[Nexus 4 Android Development] thracemerin:
For those of you using the new GPU governor, I need opinions on whether it's better/worse in terms of battery but also smoothness (especially in 3D games, etc...). If you don't notice a difference, that's fine, I just don't want to keep something that results in significantly reduced performance or significantly worse battery life. Do use it for a while before you say anything though, a report after 10 minutes of use is relatively pointless :)
[Nexus 4 Android Development] thracemerin:
I'll have a look, gotta make sure it has no adverse effect on other ROMs, but I can't see why it would.
[Nexus 4 Android Development] aimcr7:
I read on franco thread the responses is positive, smooth but more battery friendly. Franco use it on his latest r666 kernel.

Still downloading PA from goo, 15 minutes remaining, then will flash latest alpha along with PA.

I can jump flashing build 1 then latest alpha, right? Just to make sure ;)

Btw I am new to this kernel, came from Franco to try different kernel and stuck on this kernel for 3 days now, I love the smoothness and battery life of this kernel, keep it up mate :)
[Nexus 4 Android Development] thracemerin:
Yeah, you can go from Build 1 to the alpha directly.
[Nexus 4 Android Development] thracemerin:
Quick gift for those of you without fauxclock.

Here's a script to set the governor to simple, it also sets the values for threshold and laziness to the defaults, but you can play with that to suit your individual needs.

How to use:

1) Download

2) Remove the .txt extension

3) Move to /system/etc/init.d

4) Set permissions (rwxr-xr-x)

5) Reboot

6) Profit!

You can then edit the tunables in the script as you see fit, the explanation of what laziness and threshold do is in Post 4.

Hopefully this helps some folks out.

Note: If you have trickster mod installed, it may say that your governor is set to performance and not simple, this is an error in trickster, you can verify by looking at the contents of the file at /sys/devices/platform/kgsl-3d0.0/kgsl/kgsl-3d0/pwrscale/trustzone/governor
[Nexus 4 Android Development] aimcr7:
Thanks mate, works great!

1.35 a.m. here, have an exam tomorrow, I have to sleep, gonna give report about battery life and performance tomorrow ;)
[Nexus 4 Android Development] sirxdroid:
I never understood this step :)
[Nexus 4 Android Development] thracemerin:
My device deposits money in my Google wallet account at this point, if yours doesn't I can't help you :p

Perhaps RMA :p
[Nexus 4 Android Development] sirxdroid:
Will do, thanks.
[Nexus 4 Android Development] veyka:
Cheers! (also mpdecision hehe)

Also: plug for http://www.veyka.co.uk/other/motley/ lots of scripts still, init script all the way!
[Nexus 4 Android Development] show-p1984:
And here I thought that my device is the only one doing this :silly:
[Nexus 4 Android Development] thracemerin:
I'm a little scared now that someone is actually gonna try to RMA because of this. :eek:
[Nexus 4 Android Development] pa.pn2:
Lol
[Nexus 4 Android Development] atulalvenkar:
I have a strange problem on my phone and have had it from the time I got the device. Tried flashing almost every kernel out there. This kernel helps a bit but

still it happens every now and then.

It's like the data drops some people have reported, but not exactly the same. What happens in that after couple of mins of screen off the phone sort of looses data. I can

still see the H symbol and the bars are still blue not greyed, but no sync takes place. I don't get any notification from hangouts, gmail or even whatsapp. I can however

browse with chrome. Sometimes it will autoconnect after half hour or so.

Any idea what might be the problem?
[Nexus 4 Android Development] aimcr7:
Playing around with latest alpha with simple governor, here is my report, no performance drop so far, playing temple run 3 still so smooth, UI interaction is smooth too, got a great battery life btw 54% left, 7h standby. Reading docs and ppt for my exam, browsing, falcon pro, whatsapp, 10 minutes temple run.

Very happy with the result of the latest alpha, I hope you make simple gov as default gpu governor.
[Nexus 4 Android Development] iPwn_:
I've been noticing some wake up lag with this kernel. Compared to a stock Nexus 4, there's a bit more latency between the time I wake the device from sleep and the time that it becomes fully responsive. The easiest give away is the lock screen to home screen animation dropping a few frames.
[Nexus 4 Android Development] edwardeutsch:
OK...i've tried so many kernels out there with official CM 10.1 (Now i'm on Stable). But i always return to stock CM. Now i want to try out your work! Thanks for this! I've heard many good things about it!
[Nexus 4 Android Development] thracemerin:
Probably a function of the hotplugging routine, mpdecision ramps the cores up more quickly during wakeup than auto hotplug does, the problem of course is if I make the hotplug more aggressive it will hurt battery life, but I might be able to force a second core for a few seconds during the wakeup process to help with the initial load.
[Nexus 4 Android Development] funcrusher:
Just curious - what ROM you on? I used to have this issue with _motley, but it was only bad on rasbeanjelly.

---------- Post added at 01:20 PM ---------- Previous post was at 01:01 PM ----------

And thanks, finally flashed _m+ yesterday. So far, so good. :)
[Nexus 4 Android Development] iCole:
Can't say I'm noticing this since using this kernel. I've had it happen before on franco, intersectRaven and even _motley, but not _m+. Maybe it's ROM or CPU version (slow, nominal, fast, faster) dependant?

Also, I'm running the alpha right now with Simple GPU governor and I'm definitely sure that heavy graphics performance got better.

On earlier builds if I was playing Real Racing 3 and had a race with many other cars in it, fps dropped visibly (still playable, but you could see it dropped).

Battery life seems to remain the same. I'm currently on CM 10.1 Stable and my CPU is Fast, if that's useful information.

<3 you thracemerin (no homo), keep doing what you do!
[Nexus 4 Android Development] iPwn_:
I'm on Xylon. Also, I disabled the deeper sleep states and it seems a bit better now, but it's still not as good as stock.
[Nexus 4 Android Development] hospital349:
_m+ WIKI is now available. [MENTION=4303511]thracemerin[/MENTION] - enjoy! :good:

(For further information regarding all things MAKO WIKI related, please click: HERE.)
[Nexus 4 Android Development] AcmE85:
So far there were no problems with your latest WIP build.

Everything is as smooth as before, no negative effects on battery life.

btw I never experienced any kind of wakeup lag with motley's or this kernel.
[Nexus 4 Android Development] thracemerin:
The wakeup lag is probably related to the deeper sleep states, if you have them disabled you likely wouldn't notice.
[Nexus 4 Android Development] iCole:
After a few days with the new Alpha and Simple GPU governor, it seems like the battery life is improved, although I cannot verify since I kinda changed my usage pattern in the last few days and that might be affecting it as well.

However, I can definitely confirm that the phone does not get as hot as it did before, even during very GPU heavy tasks (gaming). This was a great surprise and I'm definitely sticking with the Simple governor from now on thanks to this.
[Nexus 4 Android Development] AcmE85:
I am using retention, never actually tried c2 or c3. Will give it a go on the weekend.
[Nexus 4 Android Development] thracemerin:
I don't even use retention personally and haven't experienced the problem, but if I had to guess it's a c2 or c3 related issue.
[Nexus 4 Android Development] sirxdroid:
[MENTION=4303511]thracemerin[/MENTION] - any more thoughts on adding an option for MPDecision? I've been a fan lately of MPDec + interactive governor (with the latest patches). Thanks!
[Nexus 4 Android Development] thracemerin:
I'm not at all happy with how my initial work turned out, so I'm rethinking how I want to do it.
[Nexus 4 Android Development] AcmE85:
Regarding the sleep states,

I can simply enable all of them (as mentioned in post2)

via init.d script? Or do I have to chose only one?
[Nexus 4 Android Development] thracemerin:
You can turn them all on. Faux initially recommended 0,1 & 3.
[Nexus 4 Android Development] karanrajpal14:
Hey mate, any luck with adding s2s and s2w? Looks like you've forgotten about it!
[Nexus 4 Android Development] soumoks:
simple governor has been included in the latest version right? i also updated trickster mod,but whenever i select simple governor it goes back to ondemand :confused:

edit: the latest version is the one in wip directory? if so sorry for my post,i am on 8.1 :p
[Nexus 4 Android Development] AcmE85:
Right now I am testing sleep states c0,1,3 and can not notice any difference in wake-up behaviour.

Just to make sure, this is how my script looks like:

Permissions are set correctly.
[Nexus 4 Android Development] thracemerin:
That should do it.
[Nexus 4 Android Development] thracemerin:
I did forget and I promised I'd get it in for the next Alpha, should be soon. Though I don't seem to be able to find the actual code for s2s, I know it's in AK, maybe it's just part of his s2w implementation.
[Nexus 4 Android Development] thracemerin:
Just a small request: I'm not going to name and shame anyone, but if you are going to PM me with questions about the kernel (I would much prefer that you post them here, but if you have less than 10 posts or whatever), please try to make it so your question makes sense, if you PM me something I can't understand there is no way I'm going to ever be able to answer you or help you. I understand that not everyone's first language is English and it's very likely that it's a Google translate problem, but I've received a couple of PMs lately with such incomprehensible gibberish in them that I can't even come up with a question that might get me the info I need to answer the original questions.

I don't want anyone to take offense, but this is probably why you didn't get a reply from me :D
[Nexus 4 Android Development] karanrajpal14:
Yeah I guessed that. No hurry though I just wanted to remind you. Yeah I guess it is. Out of the few kernels that I tested, his was the only one with s2s. Try to add it if you can. If not then no biggie. S2w will be enough.
[Nexus 4 Android Development] thracemerin:
Build 9 should be available on goo.im shortly, changelog is in post 1.

Happy Flashing :victory:

For those wanting s2w, I decided to release B9 before I published another Alpha, the s2w Alpha will be available in the coming days. :D
[Nexus 4 Android Development] iCole:
Is build 9 the same as the previous alpha, just bumped up to a "stabler" release?

And I suppose the 98gpusimple script you posted earlier will still work with this, correct?
[Nexus 4 Android Development] thracemerin:
It's the previous Alpha with simple governor set as default, you can still use the 98gpusimple to set the tunables. You can remove the part of the script that sets the governor to simple, but setting it a second time won't hurt anything if you don't feel like modifying the script.
[Nexus 4 Android Development] iCole:
One further question: Are you going to merge the 2 CM notification LED patches that were mentioned here a few times already into the next alpha? Without them the LED seems to be acting crazy every once in a while, displaying wrong colors etc.

http://xdaforums.com/showpost.php?p=42906621&postcount=690
[Nexus 4 Android Development] thracemerin:
Yes, only one of them is kernel related. I considered doing a 9.1 for it, but i'll just release the new alpha.
[Nexus 4 Android Development] thracemerin:
New Alpha released in Post 4! All the important details are there.

Note: s2w does continue to contain bugs that may make it a deal breaker for some (screen freezes, etc...), I'm not really willing to spend a lot of time looking at or fixing them, so use s2w at your own peril.

Happy Flashing :victory:

It's a crack flashers delight today :cowboy:

If you aren't planning to use s2w and don't have problems with your LED, I recommend staying on build 9.
[Nexus 4 Android Development] thracemerin:
I edited post 4, but in case people missed it, the kernel version string in Android says the kernel version is wip_build-57d07f4 this was an error in my build script and nothing to worry about, you have the correct version. :angel:
[Nexus 4 Android Development] iCole:
Can confirm LED no longer goes nuts on the alpha!
[Nexus 4 Android Development] Remoteconcern:
Really needed s2w. Thanks thraceramin!

Been away, I missed all the simple governor stuff. Should I expect any difference in performance or battery life if I don't game? My phone feels incredibly fast on new alpha but I also hadn't rebooted in over a week (stability ftw!)
[Nexus 4 Android Development] thracemerin:
Simple governor should keep your gpu at lower clock rates more often which should save you some battery.
[Nexus 4 Android Development] azrash:
Thanks for adding s2w and s2s back!

Based on trickster mod app, there are three possible mode for s2w.

I have checked android_touch/sweep2wake after I enabled the three modes and the value is as below

0 off

1 s2w+s2s

2 s2s

I tried mode 2,which is s2s only but s2w is still enabled, even after turning it off first. Not an issue for me since I normally use both of them, but perhaps people that use s2s only(if there is any), would be affected.

Thanks again thracemerin! For continuing the project

Flowed from my Nexus⁴
[Nexus 4 Android Development] show-p1984:
If it's my s2w then this is bull :) Sorry :)

0 off

1 s2w enabled

2 s2w with button backlight (since the n4 has none this is not used)
[Nexus 4 Android Development] thracemerin:
So S2S is in fact working then?

I think the trickster option includes stuff that faux123 added to his version of s2w/s2s which aren't part of show-p1984s initial implementation, I'll have a look at the differences.
[Nexus 4 Android Development] azrash:
I see. Thanks for clarifying it! Will pass the info to the trickster mod devs

:good:

Yeap it works! swipe the Nav bar from right to left.

Flowed from my Nexus⁴
[Nexus 4 Android Development] thracemerin:
Looks like s2s requires stuff faux123 added to show-p's initial implementation.
[Nexus 4 Android Development] veyka:
My notification LED is thankful for your kindness! No more random tosh!
[Nexus 4 Android Development] lazer155:
I was on cm10.1 (latest nightly) and the last motley kernel update. I finally tried this kernel and now I am stuck in a bootloop. Is there a way to get out of the bootloop without erasing my data? I tried flashing motley kernel again and it remained in a bootloop. I can't mount the sdcard from cwm recovery so I can't push another copy of the rom back to it to dirty flash out of the bootloop.

Wiping the caches, got it stuck at starting apps.
[Nexus 4 Android Development] sirxdroid:
Try "adb sideload" to push a ROM if CWM supports sideloading - not sure about it, I use TWRP. It is always a good idea to keep a stock ROM and the current ROM on the sdcard, for situations like this one.
[Nexus 4 Android Development] lazer155:
CWM does support that. However I realize now that I have usb debugging enabled. I usually only enable it for the short periods I need it then turn it off. It was off before this happened. Doesn't that make adb sideloading not work?
[Nexus 4 Android Development] sirxdroid:
Put CWM in sideload mode (not sure how to do it as I never used CWM).

Then from your PC, command line type:

adb sideload your_rom.zip

(you need a recent version of adb, the latest one is 1.0.31, sideload was added at .29 or something)

It may take a few attempts, for some reason after I put TWRP in sideload mode it takes a while for the computer to detect the phone in sideload mode. Just be patient and give it a bit of time. I'd say if it still doesn't work after something like 2 minutes, there's probably something wrong

The file will end up under /sdcard/sideload.zip so you can just flash it if CWM doesn't automatically start flashing it for you.

Have you tried "adb push your_rom.zip /sdcard" in CWM? It works in TWRP... sometimes ... so you may not need to use sideload.
[Nexus 4 Android Development] lazer155:
It says adb is not a recognized command. I installed adb using the toolkit a member here made: http://xdaforums.com/showthread.php?t=1995688 It said it installed successfully. I'm going to try installing it from the sdk now and see if that works. The phone is recognized in the toolkit and says that it is in adb mode. But I did disable usb debugging and I think that is problem that makes adb useless.

Edit: Yep I'm stuck, even if adb worked, usb debugging has to be enabled. If I factory restore, will I lose everything? My last backup is pretty old.