yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] jazzboyrules:
Yes, I am using Touch Filter. I will turn it off and try s2w.

Thanks!

UPDATE: I disabled Touch Control and enabled s2w and so far all the edges show proper sensitivity. I will update if I see that issue again.
[Nexus 4 Android Development] thracemerin:
Yeah, hmmm.....that's gonna be a tricky one to track down.
[Nexus 4 Android Development] emmanueldmc:
I just downloaded the application of tickster MOD and changed several things ... anyone know how to restore the default settings of the kernel?
[Nexus 4 Android Development] azrash:
Since trickster doesn't change the things permanently (they only have an option to set it on boot, which is a good thing) you can just clear the data of the trickster app, or uninstall it and reinstall it. then, reboot. The values should be back to the default ones.

Flowed from my Nexus⁴ using Tapatalk 4 Beta
[Nexus 4 Android Development] karanrajpal14:
Is anyone else facing lockscreen lag after waking the device?
[Nexus 4 Android Development] jazzboyrules:
The issue returned after a while yesterday. I was playing the 10000000 game and during that the bottom edge went dead; I could no longer activate the Pie.

The tweaks I had enabled in the kernel were:

- Vibration intensity

- SD card scheduler

- Thermal throttling

- Color and gamma

- Sound

- s2w
[Nexus 4 Android Development] thracemerin:
I'll just leave this here.....:p
[Nexus 4 Android Development] Kocai:
Have you tested if the Wi-Fi notification delay has been fixed?
[Nexus 4 Android Development] thracemerin:
Seems to be :D
[Nexus 4 Android Development] karanrajpal14:
It's fixed. Tested for the past few hours and it's a lot better now.
[Nexus 4 Android Development] Mahdi786:
Which toolchain did they use 4.6 or 4.7?
[Nexus 4 Android Development] veyka:
Very nice! Did you get a chance to work on mpdesion as well? /endnag hehe
[Nexus 4 Android Development] sirxdroid:
Did Google change the color calibration in the 4.3 kernel? Thanks for checking :)
[Nexus 4 Android Development] thracemerin:
4.7, I couldn't get 4.8 to boot yet, still looking into why.

The alpha is using mpdecision right now, I decided to do a full rebase, it'll take me a bit longer to get all the features in but there are less likely to be weird issues from trying to merge the 4.3 code in on top of all the changes that were made to the 4.2.2 kernel.

It looks better, but I didn't dig in far enough to be able to answer that one yet, I'll have a look and get back to you.
[Nexus 4 Android Development] show-p1984:
There was a bug in the 'old' 4.8 linaro toolchain which generated faulty code with anything other than -Os (related to memory allocation, which causes an early page fault and kernel panic). Either use that optimization level or use a newer version with that fixed (if available).

Or stay on the rock solid gcc4.7 until 4.8 is reasonably save and stable to use.
[Nexus 4 Android Development] thracemerin:
I used the latest 4.8 (2013.07) and it wouldn't boot even after I switched SLUB to SLAB which is how I fixed the problem on the 4.2.2 kernel, I'm just gonna stick with 4.7 for now, I think most of the difference in performance was placebo anyway :)
[Nexus 4 Android Development] hellsgod:
Do you compile with Os or O2/3? I'm asking, because i can only compile the Source with Os. Is there something i have overlooked? I'm using GCC 4.7. Thank you.

hells

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Android Development] thracemerin:
Small gift for those of you excited for 4.3:

What's included:

init.d support (you need to install busybox to /system/xbin)

insecure boot.img (adb remount seems to be broken still, but that may be an issue with supersu)

undervolt support

gamma control support (motley, faux and franco interfaces)

WARNING: this is only for stock factory images from Google, not AOSP 4.3 builds, not CM, not MIUI, just stock, if you ignore this and blow your device up, too bad!

I am only providing the boot.img for now specifically because if you don't know how to use fastboot to flash kernels you shouldn't be using this ALPHA, don't ask for a flashable zip as none will be provided and I ask that nobody convert this to a flashable zip.

Instructions:

boot into fastboot

fastboot flash boot mplusboot.img

reboot

Edit: use the one here: http://xdaforums.com/showpost.php?p=43954819&postcount=847 instead.
[Nexus 4 Android Development] thracemerin:
The issue with adb remount is an issue with the way that Google patched android to avoid elevated permissions on the /system directory, easily fixable in the ramdisk but I'll hold off until Chainfire, Koush, etc... have a little more time to look at the situation and possibly come up with a solution that doesn't require messing with the ramdisk.

Anyway, stay tuned on that one :D
[Nexus 4 Android Development] thracemerin:
Well, this is interesting: http://www.androidpolice.com/2013/0...ager-control-permissions-for-individual-apps/
[Nexus 4 Android Development] Remoteconcern:
Great job Thrace. I've flashed the boot image, and with 4.3, it is really flying. Loving it. Still haven't rooted 4.3 yet because it sounds like things are weird with that still but I will do once everything has been figured out.

Is there anything missing or not complete with this version?

---------- Post added at 07:34 PM ---------- Previous post was at 07:33 PM ----------

Ah I remember CM7 having something similar. Really useful I think. Hopefully it becomes an actual feature at some point.
[Nexus 4 Android Development] thracemerin:
It's pure stock with the stuff I listed as included right now, I'm merging things slowly because some of the things that were added in 4.2.2 were merged or partially merged by Google, it's also running mpdecision right now, autohotplug is being insanely difficult to merge.
[Nexus 4 Android Development] Remoteconcern:
Personally I would just leave it out. I don't think it's as good as mpdecision, and probably just bloats the kernel a bit.
[Nexus 4 Android Development] thracemerin:
Well, this is annoying....

Google added 3 commits to the kernel branch a couple of hours ago related to the GPU.

Prior to these 3 commits AOSP builds (JS) experienced some strange visual tearing.

After these 3 commits the stock build (JW) has this same visual tearing but I'm assuming that those built from AOSP do not.

Bleh....what a pain in the butt.
[Nexus 4 Android Development] Remoteconcern:
Ah man, irritating. I don't understand why Google have given an update which is significantly different to the AOSP version.
[Nexus 4 Android Development] thracemerin:
I think it was a mistake, but either way it means I have to build a separate version for those who stay on the stock ROM.
[Nexus 4 Android Development] thracemerin:
Question for those early adopters: have they solved the msm_hsic_host wakelock issue with 4.3? the one thing I have yet to fix on my N4 is the 3G radio so I can't test that part yet and I need to know if I should look at merging the patches from 4.2.2 or not.
[Nexus 4 Android Development] thracemerin:
NEW ALPHA!

What's included:

All the stuff from the previous alpha

Faux Sound Control including poweramp controls (Thanks Faux123)

Dynamic Fsync (Thanks Faux123)

Note: The 4.2.2 kernel contained both dynamic and regular fsync control, for the moment this version only has dynamic so you have the option of fsync on or dynamic on, not fsync completely off, default is dynamic on.

Warning: This is only for stock factory/OTA builds (builds starting with JW) not CM, AOSP, MIUI, etc...

Again, only a boot.img for now.

Enjoy :victory:

Use this build instead: http://xdaforums.com/showthread.php?p=43993185#post43993185

MD5: fbd1519143248b255d2ba4e3e939bbc5

source: https://github.com/thracemerin/kernel-Nexus4/tree/m_plus_43_exp_JW
[Nexus 4 Android Development] thracemerin:
Also fyi, Chainfire fixed SuperSU for 4.3, see here: https://plus.google.com/113517319477420052449/posts/Jkuu84odnx6
[Nexus 4 Android Development] whittikins:
Nice work! Should I be able to use Franco kernel app to use the "recomended gamma settings”? When I do, the colors are off. Much bluer than usual. Same gamma control as Franco kernel?
[Nexus 4 Android Development] thracemerin:
As far as I know you should be able to use the franco app without trouble, it is possible that franco updated his settings somewhere since _motley incorporated the interface (I just pulled it forward from the 4.2.2 kernel), I'll have a look at it prior to the next version.

Edit: we're still using v1 of franco's interface and he's using v3 which probably explains the difference in appearance, I'll update it ASAP (more complicated than you think since I have faux and motley's interfaces in the code too, but shouldn't be too terrible).
[Nexus 4 Android Development] whittikins:
OK great, thanks for all the work !
[Nexus 4 Android Development] meangreenie:
Been using alpha 2 since it was posted. Running with 0 problems UV by 150 at the higher frequencies.
[Nexus 4 Android Development] ludoanimation:
I flash 4.3 alpha2 this morning with flashImageGUI and everything seems to be OK :good:

with trickster i change MPDecision = OFF , Min freq = 384000 max freq = 1512000 Max GPU freq = 400, do i forgot something ?
[Nexus 4 Android Development] frontlyna:
So just to be clear, this won't work with new aosp 4.3 Roms?
[Nexus 4 Android Development] thracemerin:
If the build number begins with JS you may experience some odd graphical tearing and artifacts, I will be pushing a JS build soon as well.

If you turn MPDecision off you will have all 4 cores on all the time, not that that's bad, but there are no other hotplugging options in the kernel at the moment.
[Nexus 4 Android Development] oscaraigf:
JS Jajar AOSP.

Eager to test the kernel

Greetings and thanks for sharing
[Nexus 4 Android Development] show-p1984:
I haven't updated yet, but if it's as you say, then why don't you just stick with the newer solution and provide the adreno libs for that in your install zip? Should get rid of the tearing.
[Nexus 4 Android Development] thracemerin:
Hmm...hadn't considered that, thanks for the suggestion.
[Nexus 4 Android Development] thracemerin:
Of course Google seems to have changed the binary page to suggest the binaries are only for JW builds now, I'll have to dig into an AOSP build from yesterday to see if they are the same blobs or not.
[Nexus 4 Android Development] thracemerin:
NEW ALPHA

What's Included

Everything from Alpha 1 & Alpha 2

Updated Franco Gamma Control to latest (hopefully this fixes any issues with using FKU to set gamma)

Warning: Flash only on JW builds!

Enjoy! :victory:

MD5: 9a5da98c3df01ff10a87a5878b991f17 mplusboot.img
[Nexus 4 Android Development] frontlyna:
OP can we please get an aosp version? The stock colors are driving me insane!
[Nexus 4 Android Development] thracemerin:
I'm not able to test them, so...
[Nexus 4 Android Development] Kocai:
Have you or have you not merged the CAF patches to improve 3G or data speed? I got way faster speed with alpha 2 (didn't test alpha 1) compared to the previous m+ version for 4.2.x.
[Nexus 4 Android Development] thracemerin:
NEW ALPHA (

JS BUILDS ONLY!!!!

)

What's included:

Everything from the JW build posted on the previous page.

Note: Flash only on JS builds! If you flash this on JW builds you will have all sorts of strange graphical oddness, you've been warned!

Note 2: This will only boot on ROMs that have unmodified AOSP boot.img packages, if your ROM cook has modified their ramdisk it probably won't work, check on this before flashing it.

Enjoy :victory:

Note: I can't test this right now, if it boot loops let me know.

MD5: de88dceb7e8ed938aebd0e742206a5eb mplusbootJS.img
[Nexus 4 Android Development] thracemerin:
I haven't added anything that I didn't explicitly list.
[Nexus 4 Android Development] Kocai:
Ah okay sorry. That means Google made a lot of improvements. Btw, I think the msm_hsic host wakelock is significantly reduced, at least compared to stock 4.2 or custom kernel that doesn't use CAF patches for it.
[Nexus 4 Android Development] thracemerin:
No need to be sorry, I'm just as thorough as possible with my changelogs so everyone knows whats going on :)

That's good news that Google has worked out the msm_hsic_host issue and fixed the data speed issue to boot.
[Nexus 4 Android Development] Bionik_kaos:
Flashable zip soon ???
[Nexus 4 Android Development] thracemerin:
Soon? Yes :D

Very Soon? No :crying:

I want to get it past the testing phase before I get the anykernel system working for flashable zips.
[Nexus 4 Android Development] Kocai:
Yeah, at least less people would complain about it. The one thing I'm still not sure of is the Wi-Fi notification delay issue. I need to test with Wi-Fi at work. But seeing the improvement Google made on 4.3 kernel so far, I'm very happy.

I confirm that I can change color using franco kernel updater app however, the misc. gamma settings (Saturation, Brightness and Contrast) loaded the wrong numbers.
[Nexus 4 Android Development] Bionik_kaos:
I would test but I'm not with my PC so can't fastboot it .... Sorry
[Nexus 4 Android Development] thracemerin:
Well, there's some confusion about what Google did and/or intended to do with the settings in the WCNSS_qcom_cfg.ini file. In the 4.3 leaked build the ARP offload flags were set to 1, in the factory/OTA stock build they are set to 0, in the JSS AOSP build they are back to 1. When asked about it JBQ and some other Googlers gave very odd and contradictory responses to what they intended to do vs what they did, so I'm completely unsure what they are trying to do there, hoping for clarification before I look at it further.

Loading the wrong numbers when? After you set them? or on the first flash before you do anything?
[Nexus 4 Android Development] tmimaesk:
Yay, it does boot with JS build.. Using jarjar124 build..
[Nexus 4 Android Development] Kocai:
Surely they changed something else as well than just the value of the ARP offload flag. Please let us know if you find some more info about this. I'll try and report back about the WI-FI notification delay after I test with my work WI-FI.

I saved a color profile when I used franco kernel and bought his app. After flashing Alpha 3, I downloaded the app, loaded my color profile but the numbers for brightness, saturation and contrast are all wrong. Here's some screenshots; before loading the color profile and after loading it.

Sent from my Nexus⁴
[Nexus 4 Android Development] 3c:
That's why I never buy such a very expensive and niche app only working on one kernel on few nexus devices on specific Android versions. I use (and develop indeed) Android Tuner and it works on all devices, all Android versions. I switched to 4.3 a few days ago, all gamma profiles are working fine out of the box. Nevertheless I updated my app to cope with 4.3 changes (and temporary SU bugs) the morning of the official 4.3 release.

I'm sure there's many other apps that can do a better job than this non-compliant app.
[Nexus 4 Android Development] Remoteconcern:
Thanks for developing a free app - it's much appreciated. However, try not to criticise other people's apps too - everyone has their own ideas about how things should be done or look and I think that's a good thing :)
[Nexus 4 Android Development] 3c:
As this is completely OT I won't expand on this, but I entirely agree with you, so IMO removed (EDIT: pointless as it's in your quote now ;))
[Nexus 4 Android Development] Kocai:
I know about your app and I appreciate you developing it for free but what you said it's not fair. Especially since the app works just fine on his 4.2 kernel.

Sent from my Nexus⁴
[Nexus 4 Android Development] 3c:
What's unfair saying his app works only on select Nexus devices, only on his kernels and that it's way too expansive while you can find the same features unlimited for half price or free? However when he says all other apps are ugly and not compliant, no-one says it's unfair and untrue, go figure.
[Nexus 4 Android Development] thracemerin:
It looks to me like in his code for the interface that franco has it set so if the value is over 31 it's set to 31 for brightness and contrast and if its over 255 its set to 255 for saturation, not that that explains how its interpreting your input to those variables incorrectly but it looks like thats whats happening. Try inputting the settings again and not loading them from your profile and see if that fixes it. I'm trying to see if its a FKU problem, or something with the 3 interfaces not playing nice together all of a sudden.
[Nexus 4 Android Development] paratox:
JS 4.3 alpha works nice here, thanks! :)
[Nexus 4 Android Development] Kocai:
I can input the numbers manually just fine and it sticks after a reboot. The problem is if I load a profile. The numbers for brightness, saturation and contrast are all wrong.

To be honest, I prefer _motley gamma control because we can set different values for brightness, saturation and contrast for each RGB gamma. It can be done easily using terminal as well. If I'm not mistaken, it's based on faux? But it's the first version or something since now faux gamma control has gradient / gray scales.

Edit: to add, personally I don't think there's a need for 3 gamma control interfaces.
[Nexus 4 Android Development] thracemerin:
Well, that means its something to do with FKU and not the interface itself, so I'll refer that issue to franciscofranco, but he's on vacation so he probably won't care much that it doesn't work on a non-franco kernel :D Out of curiosity, if you input the values without loading a profile, then set it as a new profile, then load that profile does it work?

I don't see the need for 3 either, but when they're not all there people come into this thread or _motley's thread and say 'why can't i use FKU to set gamma?' or whatever.
[Nexus 4 Android Development] Kocai:
Yeah, I don't think you need to tell him about this.

To answer your question, no. I tried with 2 different numbers. Specifically just the numbers for brightness, saturation and contrast. Input the values, save it as 2 different profile, and every time I load either one of those 2 profiles, the values for brightness, saturation and contrast are changed. The numbers are random as well. One time they're 0, 0 and 0. The other times they're 31, 31 and 39 (just like my screenshot).

My test also concludes that loading any profile (not just mine) will fail because the values are not set accordingly to the profile which makes the process completely pointless. Some profiles would have totally different values for every thing (blacks, mids, greys, etc) after loaded.

Well people would always ask this or that feature. I'm guilty of that as well. That doesn't mean you or any developer should add it just because people ask for it. Especially if there's a problem with the particular paid apps. Just my two cents.
[Nexus 4 Android Development] FeintDoxx:
Thracemerin. Can you link me to the page to the UV table from Motleys latest stable. You linked me a long time ago. But I finally update to CM 10.1.2 and flashed build 10 but I got rid of android tuner and completely forgot my setup. Sorry if its a bit off topic.

sent from the lone wolf next door with a Nexus 4 using XDA Premium.
[Nexus 4 Android Development] thracemerin:
This? https://docs.google.com/spreadsheet...dFU4U2xnSUxwUlNyQ05TVHF3ZDJCdXc&usp=drive_web
[Nexus 4 Android Development] FeintDoxx:
Yes exactly. Thanks!

sent from the lone wolf next door with a Nexus 4 using XDA Premium.
[Nexus 4 Android Development] thracemerin:
Interesting, I'll look into it eventually but it would require adding a bunch of debugging, buying Franco's app and then testing and doing a logcat, not that I can't do this but given that it appears on the surface to be an FKU issue possibly related to new sqlite in 4.3 or something else like that I'm not terribly inclined to put a ton of work into it right at the moment, especially since the interface itself can be manipulated correctly via scripts.

I added it to the list, and my own curiosity will eventually cause me to look into it, but like I said not a top priority right now.
[Nexus 4 Android Development] oscaraigf:
Thanks for your work and for sharing.

NEW ALPHA (JS BUILDS ONLY!!) Sweep2wake supported??

regards
[Nexus 4 Android Development] thracemerin:
Nothing is included that is not explicitly listed.

So at present:

Init.d support (busybox required)

Insecure boot.IMG

Undervolt (down to 600mV)

Gamma control (motley, faux & Franco)

Faux sound & power amp

Dynamic fsync
[Nexus 4 Android Development] thracemerin:
Just to be clear: more stuff is coming, but I don't want to stray too far from stock until we're sure what we're dealing with. Google improved the kernel a lot between 4.2.x and 4.3, I don't want to randomly throw everything back in as it could be a step backwards, or if you have been following faux's thread create weird green screen followed by unexplained crashes. Better to do baby steps and make sure things are going well than jam everything in and then have to tear it all out searching for that one line of code that is buggering everything up.
[Nexus 4 Android Development] show-p1984:
showp1984@jarvis:~/Desktop/mako_new_libs/new$ sha1sum *
4fd2a6431d9d739ad2e8d6657a54e37e775a895d eglsubAndroid.so
8240382b01c0c3bbb127edd9ba9ba034fcfbad42 libEGL_adreno200.so
eb89ce89caff60bfc8fcc708cdb8617fd9bf2bba libGLESv1_CM_adreno200.so
2a0c48d17e9fb57bc6c0d83ae76763559e4729e3 libGLESv2_adreno200.so
ccff75df39eea0bcbd2b82f7346bbd2eba96c647 libGLESv2S3D_adreno200.so
8d0620b68d6f6f114c99253c8aaa705a3e7e148b libq3dtools_adreno200.so
showp1984@jarvis:~/Desktop/mako_new_libs/new$ cd ../old
showp1984@jarvis:~/Desktop/mako_new_libs/old$ sha1sum *
812655c141446e225230be00e36f7e9d6eb89106 egl.cfg
c5b28fe738a795f51f58cf36fb85bc108bb6d2a5 eglsubAndroid.so
137c674c62b3f45c11fe52ed050ace03de24d4aa libEGL_adreno200.so
6408e1256d8fe119b79c465bbc914671342d9fde libGLES_android.so
b489297acb4e30940ef52d01fd01272d4c0dec53 libGLESv1_CM_adreno200.so
9e11e263e862045f852a3345f1f65f997a780c81 libGLESv2_adreno200.so
cec07ae0889adaddef8191f075cebd52c07270fa libq3dtools_adreno200.so
[Nexus 4 Android Development] thracemerin:
So the ones on the binary site are different from the ones in the stock build or the ones on the binary site are different from the ones that were there earlier in the week?
[Nexus 4 Android Development] show-p1984:
JS != JW

(binary site != 4.3 stock)

Had to be, they are vastly updated. One of those caf commits for the kernel squashed 59 commits. That's a major change.

I don't quite understand why this was pushed directly after the official release, maybe it was meant to be in the 4.3 ota update but someone didn't merge it on time?
[Nexus 4 Android Development] thracemerin:
I'm puzzled too and JBQ and other Googlers gave strange and contradictory explanations on code.google.com. The binary site also originally said JW & JS and now they switched it to JW which is clearly wrong, I'm not sure anyone at Google really knows wtf they're doing.

The same thing happened with the ARP offload stuff, it was on in the leak, off in the OTA and is back on in AOSP. JBQ tried to explain that by saying they had negative battery impact with it on so they turned it off, but I've not seen this negative battery impact and that fails to explain why its on in AOSP.

Google seems to have really screwed up this release for reasons that they don't even seem to understand.
[Nexus 4 Android Development] sirxdroid:
Those who bought the new Nexus 7 already got two OTA updates: one that moves them to build JWR66N and then another one to build JSS15J. So it looks like JS is the current build ... for today that is, come Monday we may see yet another update :)
[Nexus 4 Android Development] thracemerin:
They certainly aren't inspiring me with great confidence that they have this release under control, that's for damn sure.
[Nexus 4 Android Development] sirxdroid:
I'm waiting for the dust to settle before I upgrade to 4.3, there are plenty of issues as it is with it. I don't think anyone would fault you if you took a break and didn't try to deliver a new kernel so quickly. But maybe that's just me.