yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] oscaraigf:
Sorry for my ignorance.

Currently I'm on AOSP JSS1J and see a bifurcation with JWR66V. Then they base the kernel versions from now (including yours) JSS1J is the latest version?

Pardon my English po
[Nexus 4 Original Android Development] show-p1984:
If I understood you correctly:

JS is newer than JW. JS has vastly superior graphics drivers, both kernel side and accompanying libraries.

If you are on JS, stay on JS. If you are on JW (like I am currently) flash JS :)

It will make your life easier, as a lot of kernel devs will probably stick to JS builds, I will probably do that too.

When I am finished building JS stock, I will try to dirty flash it over my JW build, should that work there will be no reason for anyone not to switch to JS.
[Nexus 4 Original Android Development] Mahdi786:
I was going through cm-10.2 dalvik branch and I noticed that they've used your ksm patch :)
[Nexus 4 Original Android Development] show-p1984:
That has been merged some time ago and has been used a bunch of times. Originally it was from somebody else, though after adding loads of robustness checks and improvements only a small portion of the original code was left over iirc, so I didn't bother going back and editing the author on that.
[Nexus 4 Original Android Development] snak3ater:
Already flashed the latest build..will try yours for sure :thumbup:
[Nexus 4 Original Android Development] oscaraigf:
Thank you very much, I stay clear
[Nexus 4 Original Android Development] montbazon:
Sounds Great!

BTW can I see 600mhz gpu clock on upcoming builds?

Sent from my xda apps
[Nexus 4 Original Android Development] show-p1984:
600 Mhz is not possible.

Here you can see what is possible:

https://docs.google.com/spreadsheet/ccc?key=0AlTn7X59NcPxdFI1bGVzZU9qNWp1Y0VDWkM5SndPTmc&usp=sharing
[Nexus 4 Original Android Development] montbazon:
I see. It's helpful:D thank you, man.
[Nexus 4 Original Android Development] guru_shastri:
got lost here with the JS and JW..

is there a new 4.3 compatible version?
[Nexus 4 Original Android Development] jassycliq:
They're both 4.3 builds. JS is basically anything built from source. JW is if you're using the build from Google.
[Nexus 4 Original Android Development] keda:
can't wait to try out js build flash on top of stock .
[Nexus 4 Original Android Development] justthefacts:
Isn't Google the source?
[Nexus 4 Original Android Development] g_mosh:
Yes, Google is the "source". On the one hand they have the constituents; just so we can go grab and build. On the other hand, they have an already built image; just so we can grab and flash.

Nexus⁴ & Tapatalk⁴
[Nexus 4 Original Android Development] show-p1984:
Coming soon(tm):

booted with stock kernel for testing :)

Purist build:

https://plus.google.com/u/1/108262968419038009038/posts/VoqdRjCmkHa

Kernel that goes along with it:

http://bricked.de/downloads/kernel/mako/exp/bricked_mako_20130727_023549_exp-d64cabc.zip
[Nexus 4 Original Android Development] keda:
can't wait for your ASOP build. Do you have swipe to wake implemented in 4.3 yet?:D
[Nexus 4 Original Android Development] show-p1984:
All kernel features are ported.

The kernel build for the above aosp build is running.

Seems I forgot to fix some -o3 initialization issues. Will be back in a minute with the fixes :)

This is a JS build. There will be no JW builds of bricked.

Kernel Download on bricked.de:

http://bricked.de/index.php?action=kdownload&device=mako&release=beta&type=aosp
[Nexus 4 Original Android Development] g_mosh:
Oh, we waited for so long for your builds :)

Is the AOSP on G+ good to go?

Thanks!!

Nexus⁴ & Tapatalk⁴
[Nexus 4 Original Android Development] show-p1984:
Yes :)

Remember: It's the purist build. No changes whatsoever. (I just zipped the partitions)

I will post a build wrapped in a flashable zip with gapps later/tomorrow.
[Nexus 4 Original Android Development] Emilius:
So this is complete 4.3 AOSP rom? It confuse me for the moment, posted here in kernel section, LOL. Clean AOSP with your latest bricked kernel. Now is just KControl missing to fine tune these baby :(
[Nexus 4 Original Android Development] show-p1984:
Yes. Complete as in: No Gapps. It's just compiled, no modifications, nothing else done to it. 100% compiler ouput.

I will post a gapps/ro_secure=0/flashable-zip rom later. (let's call it stocklike)
[Nexus 4 Original Android Development] resynx:
The kernel caused me to get stuck at Google boot up screen on jarjar's AOSP ROM :( Can anyone else boot up with it? Can't wait to use Bricked :)
[Nexus 4 Original Android Development] show-p1984:
The new build (bricked_mako_20130731_082718_exp-73fe91e.zip) is ONLY for JS.

The older ones are for 4.2.2.
[Nexus 4 Original Android Development] resynx:
I am on JS, hm.. let me try flashing 1 more time. Maybe I messed something up on my end :silly:

Edit: Stuck on installing the kernel at 50%. Says:

Installing...

Pull the boot.img from your phone...

=\
[Nexus 4 Original Android Development] show-p1984:
That's aroma. It sucks sometimes.
[Nexus 4 Original Android Development] resynx:
Still stuck on boot logo :( Will patiently await your next release :)
[Nexus 4 Original Android Development] show-p1984:
Then it's not a real JS you are on :)

Works for me, as the screen proves.

Don't forget to rename mpdecision_bck and thermald_bck (omit the _bck) if you haven't done a backup.
[Nexus 4 Original Android Development] resynx:
Renaming? Where are these files found? :) Is it sufficient enough if I just did a reflash of my ROM?
[Nexus 4 Original Android Development] show-p1984:
adb shell
su
mount -o remount,rw /system
mv /system/bin/mpdecision_bck /system/bin/mpdecision
mv /system/bin/thermald_bck /system/bin/thermald
sync && reboot

yes.
[Nexus 4 Original Android Development] mumaster20:
Boots just fine for me on Jarjar's rom :confused:

While it boots fine, my wifi seems te be screwed. Unable to turn it on. Any suggestions?
[Nexus 4 Original Android Development] show-p1984:
2nd post :)
[Nexus 4 Original Android Development] mumaster20:
ooh, will try that out, did not have busybox, so that was probably the culprit ;)
[Nexus 4 Original Android Development] Emilius:
The new build is bricked_mako_20130731_082718_exp-73fe91e.zip not this one from 27th. I am on one from 27th with SlimBeam 4.22 ROM. SO this one from 31st id for 4.3 only, right?
[Nexus 4 Original Android Development] show-p1984:
Copy and paste failed me. Thank you :)
[Nexus 4 Original Android Development] Emilius:
No problem show-p. Maybe you should add to the file name of the kernel 4.2.2/4.3... It is easy to see what is what without reading the forum pages.
[Nexus 4 Original Android Development] show-p1984:
Done. Newer builds will have "_JSS15J" behind the device name.
[Nexus 4 Original Android Development] resynx:
Ok kernel booted up just fine for me on Paranoid Android :) looking forward to KControl and running with Bricked :D
[Nexus 4 Original Android Development] eep2378:
@show, this looks to be some great kernel work here. Plenty of tweaks, etc. Appreciate your work. Some real nice work is starting to really go full steam ahead. Thanks! :)
[Nexus 4 Original Android Development] alewis2k12:
+1 to that...Great Job man...still kinda iffy about the OC though seen a couple post back someone ran into some issues...but other than that like I said before very good work...
[Nexus 4 Original Android Development] italia0101:
ah cool, thanks for your replies :)
[Nexus 4 Original Android Development] ctfrommn:
Ok, loving this kernel. Any thought in offering 700mv or lower like Motley? Or possibly a lower base frequency?
[Nexus 4 Original Android Development] slambkny:
Question. I flashed no problems. But I'm stuck at 1350 can you tell me why. Faux clock settings won't stick
[Nexus 4 Original Android Development] show-p1984:
Not with that screenshot.

kmsg, governor, mpdecision / thermals settings modified?, min/max settings, other changes, rom, etc...
[Nexus 4 Original Android Development] meangreenie:
This kernel is very awesome, it's the first one i can actually control all the cores using 'system tuner'.. and as the title suggests, the settings stick wether they go offline or not.

I have had 2hrs 15 minutes on screen time today with 49% battery still left ... and that includes playing 'vice city' for a good half hour+ and a fair few runs at 'temple run brave' ..uv at @125mv

thank you again 'show-p1984'

just one question, low cpu setting stays at 384 to which i prefer and doesn't jump up to @1ghz. I was just wondering is this default behaviour for your kernel or is my setup malfunctioning?
[Nexus 4 Original Android Development] joshnichols189:
I love the kernel, I've used it on a few of my other devices in the past.. but when I lower the minimum clockspeed to anything under 702mhz while on Interactive I experience incredible lag. It's pretty strange.
[Nexus 4 Original Android Development] show-p1984:
The frequency is supposed to stay @ 384. That jumping was a terrible idea from a pencil pusher @ qcom (because their mpdecision binary does that!).

Haven't looked at interactive yet (not even selected once). That's why ondemand is the default governor which will get some goodies soon(tm).

btw:

I identified a whole bunch of thermal bugs and updated for soc "peaky-ness".

"peaky-ness" = In some situations our soc is capable of peaking to 82+°C while it only had ~69°C 250ms before! (that's a friggin quarter of a second...)

updates incoming. soon(tm)
[Nexus 4 Original Android Development] noneabove:
Can you comment on mpdecision and why you use it? I only ask because many devs joke that it stands for m(ake)p(oor)decisions, did you alter it to be useful or do you find it useful where others just don't?

For the record, I have no personal gripe with it, all I know is other devs don't like it, and would like to know more
[Nexus 4 Original Android Development] seriouslyjeff:
What is mp decision?? I can't seem to find an answer anywhere!
[Nexus 4 Original Android Development] show-p1984:
I rewrote it.

The userspace binary of qcom is ****, yes. My in-kernel solution is not :)

In short:

It hotplugs/unplugs your cpu cores based on load to save power.

there are two types currently out there:

Userspace mpdecision (qcom) as a binary.

In kernel mpdecision (like my solution).

mpdecision = multi processor decision.

some light reading: https://github.com/showp1984/bricked-mako/blob/master/arch/arm/mach-msm/msm_mpdecision.c

##

Btw, hp updated go grab 0.6. Thread follows now.

Whoever manages to get the red LED + shutdown on 0.6 gets a free DOTA2 beta key. I am serious, I got 2. :p

(verifiable posts only please :))

If you only get a shutdown: that doesn't count :p That is thermal guard saving your ass in the last second.

btw: possible uv pushed down, happy undervolting.
[Nexus 4 Original Android Development] ptr_hamilton:
I have some bsod with 0.6. Didn't have those with 0.5

Am using AOKP by roman

coming from stock kernel, because 0.5 became laggy at lockscreen after few hours

Once screen is off I can't get it on again. have to reboot phone.
[Nexus 4 Original Android Development] show-p1984:
In that kmsg you powered your phone down 9 seconds after boot time.
[Nexus 4 Original Android Development] omvir:
Hello, I'd really like to give your kernel more time to run, but I am getting lock screen lag and its bothering me :p. Every time I lock my screen, and unlock after a few seconds the lock screen lags.

Sent from my Nexus 4
[Nexus 4 Original Android Development] show-p1984:
I bet you are not on 0.6.

If you are: Log?
[Nexus 4 Original Android Development] Somairotevoli:
I started to experience the same lag on .5 and .6. It seems when waking up it sticks at 384 for a bit. I fixed it by using system tuner and using on demand for screen off. Using interactive otherwise. Will try to get a log.

Sent from my Nexus 4 using Xparent ICS Tapatalk 2
[Nexus 4 Original Android Development] show-p1984:
That explains it. I have neither tested nor used interactive, it is still in stock kernel condition. (Which didn't use it either)

I recommend to stick with ondemand for now.
[Nexus 4 Original Android Development] ptr_hamilton:
Yes I did because I couldn't get the screen back on

Edit: Okay. What I've found out. It is off anyhow. I try to get the screen back on but it doesn't respond. If I plug the USB cable I can see the battery symbol. Meaning it starts loading. The problem is that I didn't power it off.

Again a last_kmsg. What else could I try to find out why it powers off?
[Nexus 4 Original Android Development] giantflash:
Can you put the lowest frequence to 304MHz like motley did? The phone is a lot on this frequence and I think this should improve the battery life
[Nexus 4 Original Android Development] show-p1984:
This Rom 'Stockified' is now live.

http://xdaforums.com/showthread.php?p=44162544#post44162544

If you are still on JW based builds, I highly recommend to switch over to this and flash bricked :p
[Nexus 4 Original Android Development] Sukhi:
Your latest stockified rom and the bricked JSS kernel look promising. Gonna play with the settings to tweak it upto my taste. I may be wrong but isn't the gpu governor suppose to idle at the min freq? By default the gpu governor idles at 325mhz and jumps back to either 128 or 200mhz when used. I hope you could work on this in the next update
[Nexus 4 Original Android Development] noctilust:
I am on rooted Stock 4.3 JWR66V, flashed Bricked-Kernel 0731, everything is great except that I noticed slightly 2D rendering issue if you scroll the screen very quickly. Tried switch on and off "Force GPU rendering" didn't help. Anyone experienced similar thing?
[Nexus 4 Original Android Development] nadiros:
Pretty sure this is for JSS15J builds only. You will get screen tearing otherwise.
[Nexus 4 Original Android Development] snak3ater:
Ohh man :fingers-crossed:
[Nexus 4 Original Android Development] show-p1984:
Governor:

Conservative.

Scheduler:

noop (no algo is used, stuff is being put into queue as it arrives, hence no cpu overhead for scheduling) or cfq

Sweep2wake:

off.

For my 3-phase-thermal:

Lower all thermal temperatures (except shutdown) by the same amount (lets say 15 °C). Lower = better for battery, less heat, a lot less performance.

For my msm_mpdecision:

It's really up to personal preference. In general: Higher nwns/twts values will get you better battery life, but less performance because the cores are plugged in later/unplugged sooner.

Disabling the input boost will also save you some battery.

When you have tweaked everything above you can also set max_cpus to 2 which will effectively make your mako a dual core.

There are a few more possibilities, but this should cover most of them.
[Nexus 4 Original Android Development] betovanbuuren:
I will give this a try... I like the sweep2wake option
[Nexus 4 Original Android Development] show-p1984:
The 4.3 JSS15J version of bricked is now out of beta and stable.

http://bricked.de/index.php?action=kdownload&device=mako&release=stable&type=aosp

Try it with my Stockified AOSP JSS15J build:

http://xdaforums.com/showthread.php?t=2387480

Happy flashing :)
[Nexus 4 Original Android Development] sMtt:
Any news from kcontrol? :fingers-crossed:
[Nexus 4 Original Android Development] show-p1984:
Sure: CPU-Voltages are working&stable, Gamma&Sound are in bug fixing phase.

I fixed the cpu graph (temperature was one datapoint ahead of usage) and I fixed a crash in the tegra gpu settings. Oh and the slightly delayed tegra gpu frequency reset was fixed too (~2 secs).

But I think you meant news as in "when to expect it?". Well it's huge, and I don't want to deliver something that force closes, at all. (Sure that's impossible but you always do your best)

I can't tell you a different, earlier, date since I found a bunch of stuff I want to fix with gamma and sound before going over to releasing it. One huge feature will be included after release, since it takes too much time to do it now, so the release time table is back on schedule.

btw, tegra frequency settings video with KControl on my Nexus 7 (sadly there is still that reset button lag, in fact I noticed it when recording this video):

https://dl.dropboxusercontent.com/u/44206202/VID_20130804_005337.mp4

And: Yes, my music is always on when coding, not just for the video. Otherwise I would have swapped out the audio track. :)
[Nexus 4 Original Android Development] shalom06:
s2w fearure is very buggy dosent work 75% of the time..
[Nexus 4 Original Android Development] snak3ater:
+1...

It works but very often..Try to wake it up with a sweep & it doesn't wake up.It works but after many tries.Sometimes doesn't work even after many tries
[Nexus 4 Original Android Development] californicated:
It must be a general s2w issue to look at. I experience the same with faux kernel
[Nexus 4 Original Android Development] sicto:
Which app is the best for this kernel ? Trickster mod or something like that ?
[Nexus 4 Original Android Development] snak3ater:
Trickster
[Nexus 4 Original Android Development] sicto:
And how to change color profiles ? Can I change them or I can only mess around with numbers ?
[Nexus 4 Original Android Development] resynx:
We can't as of now. When KControl drops we will be able to.
[Nexus 4 Original Android Development] italia0101:
Awesome kernel , really enjoying it on PA , just wondering i dont see an option for fast charge, im guessing thats not supported ? no big deal if it isnt,
[Nexus 4 Original Android Development] apatal:
Yep, no fast charge here. :)
[Nexus 4 Original Android Development] PetritH:
Just installed this kernel, lets see how it goes, too bad we I can't use halfbreed thought but whatever.
[Nexus 4 Original Android Development] apatal:
Stock colors are much better in 4.3, IMHO.
[Nexus 4 Original Android Development] sid21:
Anyone using sweep to wake as daily driver on 4.3?

Just wanted to know any screen unresponsiveness faced after a few days of usage??
[Nexus 4 Original Android Development] justthefacts:
Yes indeed.
[Nexus 4 Original Android Development] PetritH:
Well I always used halfbreed thats why I liked it more, but stock 4.3 doesn't look bad either.

I had to reboot my phone today cuz the screen was unresponsive... happned once though
[Nexus 4 Original Android Development] diggy_:
Just flashed this up on PA. I love having the the s2w feature. Ill see how this treats me. Thanks
[Nexus 4 Original Android Development] keda:
same here. hopefully will get addressed in next version.
[Nexus 4 Original Android Development] sid21:
Thats the most disturbing thing of sweep to wake..

Wish ever it could get solved or any eay to workaround..

Would like to hear from the dev

As he himself is the one who found this feature..

Really great work..but many a times cost..frustrates me..
[Nexus 4 Original Android Development] show-p1984:
I am working on s2w2 (at least I am trying to, other stuff is always pushing it aside) which will clean up this mess and also be a lot less invasive (less hooks in the touchscreen drivers) to allow easier porting.

I explained multiple times already why the current integration is failing on the mako (and grouper, hence it never got released, and newer one X sauce).

Somewhere between 3.0 and 3.1 the linux kernel mainstream changed the i2c sleeping behavior, hence i2c is now waking up AFTER the touchscreen driver. This leads to various problem since i2c is still sleeping when called by the interrupt-triggered-touchscreen-driver and is just giving back error code -16 (-EBUSY).

The data the touchscreen driver then generates is malformed and disregarded, no position data is available in this state.
[Nexus 4 Original Android Development] sid21:
i really admire your work with the aroma installer for easy purpose

and happy to hear that your working on the s2w driver

though i know it must be hard as to even integrate with the new 4.3 update

though its the feature we all want to use as a daily driver

the unresponsiveness quotient is well explained by you and i think other devs should help you to tackle it

well looking forward for a stable s2w with i2c working rather then the touchscreen driver in the release..

hope you find a workaround

all the best buddy :good:

keep up your good work

well even heard users of your kernel not experiencing the dead lock and stuttering in 4.3

somehow you managed to resolve

yours is the only kernel that passed through it

you rock man..
[Nexus 4 Original Android Development] GTM_rhinox:
Guys if you want to check out video on how to install and sweep2wake:

http://www.youtube.com/watch?v=MwhU4WEZin8

Video about overclock benchmarks at 1.8GHz!

http://www.youtube.com/watch?v=bB1KqAztd34
[Nexus 4 Original Android Development] PetritH:
Trickster Mod keeps changing my min freq to 918 even thought I applied on reboot.. it just changes the min freq the others stay as i've set.. anyone experienced this ?
[Nexus 4 Original Android Development] $droyd$:
Its mpdecision I believe... I've noticed with it enabled the min freq will scale..
[Nexus 4 Original Android Development] PetritH:
Thank you sir, btw cant wait for your new ROM.
[Nexus 4 Original Android Development] show-p1984:
2nd post...

If you mean that your min cpu frequency gets stuck at the boosted values:

Sadly some oc apps set the min freq again when trying to display the current min freq.

That's an android bug with some views as I have already explained multiple times (The same spinner used to display and set the freq for example).

What's happening is this:

Mpdecision boost the min freq because you launched your cpu watching app. (touch on the screen = boost)

The app reads the min freq, triggers the listener unintentionally which sets the now boosted min freq as the new min freq. (<= this is the error)

Mpdecision notices that sysfs tells the kernel to use a new min freq and updates it's stored pre-boost min freq with the new value. (this is intended, otherwise you couldn't set a new min freq while boosted)

The input boost times out and mpdecision restores the min freq, now to the just set value.

The bug in Android which allows this behavior is the following:

The default spinners (drop-down menus, there are others with the same issue) have no way to differentiate between "the user touched me and changed my value" and "the program code updated my value". It's both the same to the view, hence both trigger the same actions.

If you mean that your min cpu freq just jumps up/down depending on key presses and touches:

echo "0" > /sys/kernel/msm_mpdecision/conf/boost_enabled

This can be put in an init.d script, or whatever.

Beware: Doing this significantly lowers fluidity on ui interactions.
[Nexus 4 Original Android Development] Emilius:
JSS stable does not have 192 Mhz step anymore?
[Nexus 4 Original Android Development] show-p1984:
Nope. It was a pure placebo effect in regards to power consumption and battery life.

I tested faux's approach to lower clocks too, just to see if it's worth picking and if my approach was just flawed, but I came to the same conclusions. No improvement.

Testing environment:

Reboot to safe mode (long press on power, this only allows system apps to run!)

100% charge phone.

enable airplane mode.

Set lowest available clock to min/max.

Leave it over night. (it was exactly 8 hours each time, faux's, mine, and stock clocks)

The differences were marginal at best. I will just write them off as error-tolerance, since the lower freq actually used more battery during that period than the stock freq did. But as I said, probably just tolerance.

Either way: Makes no sense to use something that does not improve anything.
[Nexus 4 Original Android Development] Emilius:
My experience is different. To bad I use that all the time. That was excellent feature if you ask me.
[Nexus 4 Original Android Development] show-p1984:
Because you feel that it is better (subjective).

If you repeat the above test (which is pretty much as objective as it gets without a testing environment in a labor) then you will probably come to the same conclusions.

But if somebody has evidence to the contrary I am open to hear about it. :)