yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] thracemerin:
Well, then two versions I posted are working, and I'm working on seeing if I can inject the JS blobs into JW and therefore go back to a unified kernel rather than 2 separate versions, we'll see how that goes.

As for more features like I said above I want to wait and see how these builds go before I start putting back the under the hood tweaks and stuff we had in 4.2.2.

To be honest, a mess like this is a little fun to work with because you have to think outside the box more than you would if everything was simple and straightforward.
[Nexus 4 Android Development] Kocai:
I agree. I want to stay with Alpha 3 for a while. Get the feel or something with stock 4.3 kernel, something to compare with when trying a custom kernel (when it's available).
[Nexus 4 Android Development] Remoteconcern:
Using alpha three since release. No problems to report.

Situation with AOSP is annoying. I hate not using stock, but feel like it actually is significantly older than the AOSP version. Maybe they'll update it OTA soon.
[Nexus 4 Android Development] Scallywag1:
Could anyone post a flashable zip of latest alphas? Not near a computer and want to try. I'm on jw version. Thanks
[Nexus 4 Android Development] meangreenie:
grab 4.2.2 reset kernel from one of the main kernel threads like faux's, unzip, delete boot.img and replace with renamed apha.img to boot.img, rezip, flash
[Nexus 4 Android Development] thracemerin:
I tried just swapping the libs in the /system/lib/egl folder on stock to the ones from AOSP, the ROM still boots but there is nothing on the screen on both the JW and JS version of the kernel, so there must be some other libs that need to be swapped too.
[Nexus 4 Android Development] Kocai:
I apologize in advance because I know you don't like it when people post battery life screenshots but I want to show you how good is the 4.3 kernel with ondemand and Mpdecision. I rarely can get this good battery life previously on 4.2.2.

Note: all I do is changing the color and UV a little bit.

Sent from my Nexus⁴
[Nexus 4 Android Development] thracemerin:
You're excused....for now ;)
[Nexus 4 Android Development] jlink38:
I'm guessing this is AOSP? Looks great! I just sold my Note 2 to get a Nexus 4 and those numbers look like Note 2 SOT numbers!
[Nexus 4 Android Development] Kocai:
I won't do it again :)

It'll be interesting if the interactive governor and auto hotplug can give smoother experience and better battery life like previously.

Stock JWR66V actually. Using Alpha 3 from a few pages back.

Sent from my Nexus⁴
[Nexus 4 Android Development] thracemerin:
Interactive is there, just not on by default.

I'm on the fence about auto hotplug, but we can definitely build a test build to see at some point.

Edit: I also don't care that much about battery screen shots, but it annoys me when the thread devolves into pages of 'look at how cool my battery stats are', 'how did you get that? i can only get this', etc...
[Nexus 4 Android Development] show-p1984:
did that too, (additionally to all the other stuff related to egl) with no success either. (multiple switcharoo combinations)

The two versions are just too different.

So I will probably throw out a 100% stock aosp build. People who don't switch to that will have to use another kernel / the stock kernel. JW is just too 'old' (no arp offloading, older gfx drivers, etc). I won't use it and I won't flash back/forth between two versions all the time to check if everything works. Additionally to all the bug reports that will get mixed up it would also require two threads/download pages/buildbot modifications/etc. No thank you :)

Pressure Google to throw out JS for the Nexus 4. :p
[Nexus 4 Android Development] thracemerin:
Yeah, what a pain, time for a petition.
[Nexus 4 Android Development] Kocai:
I understand what you mean. I only posted that as a reference. So I can see if auto hotplug can give better battery life than mpdecision.

Can I ask what's the difference between the WCNSS_qcom_cfg.ini file in the JWR66V and JS build? Is it only the ARP offload on or off?

I made several tests using my work Wi-Fi and so far I haven't had any delay receiving WhatsApp messages. So it's safe to say that the issue has been fixed. But reading your other thread makes me confused since some say that JWR66V still has that Wi-Fi notification delay. I already downloaded the wifi-delay-fix-for-jwr66v.zip but I haven't flashed it.

Sent from my Nexus⁴
[Nexus 4 Android Development] thracemerin:
Well:

On JWR66N (the leak) ARP offload was enabled and there was no delay with WiFi optimization on

On JWR66V (the OTA) ARP offload is disabled, some people say there's no delay with WiFi optimization on, but most say you need to turn it off to avoid the delay.

On JSS15J (AOSP) its back to on and reacts the same as JWR66N

if it works for you without the fix and with WiFi optimization on, then I wouldn't flash the fix. If you have to turn WiFi optimization off to get no delay, I'd flash the fix and then turn optimization back on.

There are always outside factors like network configuration can affect this in ways that make it hard to say 100% what will work for who.
[Nexus 4 Android Development] Kocai:
My Wi-Fi optimization is always on. Yesterday I was at home all day and the longest delay I had upon receiving WhatsApp messages was 3 minutes. Most of the time there's no delay at all. Impressive considering previously on 4.2 I wouldn't receive any notification at all until I woke up my phone.

Today at work, I haven't had any delay as well so I'll hold back from flashing that zip file.

I do remember that on my Galaxy Nexus, sometimes I'd have notification delay if the Wi-Fi optimization is on. So yeah, I agree that the results may vary.

One thing that I would definitely try is going to this restaurant that sometime ago I couldn't connect to its Wi-Fi network. I want to know if I can now connect to it.

How about you? How's your experience so far with the Wi-Fi on 4.3 kernel?

Sent from my Nexus⁴
[Nexus 4 Android Development] thracemerin:
I had to use the fix (edited the files manually) on stock to avoid the delay. I think the overall WiFi speed is faster though.
[Nexus 4 Android Development] Kocai:
So far the only difference are that JWR66V has gEnableActiveModeOffload=0 and hostArpOffload=0 correct? I'll make some test with changing it to 1 when I find some time. This situation with different builds for JWR66V and JSS15J is confusing to say the least. I'm hoping that Google would just OTA update to JSS15J so there wouldn't be any need for different builds.

Sent from my Nexus⁴
[Nexus 4 Android Development] adichandra:
currently using aosp 4.3 jarjar build. if i flash this JS kernel, can i undervolt it? because what i missed from android 4.2.2 is able to undervolt with lots of custom kernels. thanks
[Nexus 4 Android Development] Kocai:
Yes you can UV.
[Nexus 4 Android Development] adichandra:
thanks, btw i checked my cpu binding with dmesg | grep PVS, in the other thread while everyone has fast, faster, nominal and slow, why mine says "1"?? is it slow or faster?

but the last time i uv with matr1x in 4.2.2 i can do 1.5ghz @ 1050 stable
[Nexus 4 Android Development] Kocai:
1 is slow I think. Every kernel is different. I can run 775@384 on Trinity but not on this kernel. Lower than 825 and I'd get crackling sound on my notifications.

If you want, you can try my UV setting. Do it at your own risk.

#! 825000 830000 840000 860000 885000 895000 930000 955000 980000 1005000 1030000 1070000
echo "384000 825000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "486000 830000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "594000 840000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "702000 860000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "810000 885000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "918000 895000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "1026000 930000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "1134000 955000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "1242000 980000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "1350000 1005000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "1458000 1030000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "1512000 1070000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels

Sent from my Nexus⁴
[Nexus 4 Android Development] adichandra:
thanks, but i think 1 is nominal. someone with proof of codes showed it to me. :D
[Nexus 4 Android Development] Kocai:
Anyone knows why script in init.d doesn't work? Busybox 1.20.2 Stericson is installed in /system/xbin

Sent from my Nexus⁴
[Nexus 4 Android Development] thracemerin:
Weird...it seems that your script above isn't applying for me either.
[Nexus 4 Android Development] meangreenie:
Check the supersu app to make sure the binary hasn't gone walkies.

Also check permissions.
[Nexus 4 Android Development] thracemerin:
make sure the first line of the script is:

#!/system/bin/sh
[Nexus 4 Android Development] Kocai:
Already flashed superSU 1.51. Permission is set correctly -rwxr-xr-x (chmod 755)

Always, that script worked for me previously. Do you have a suggestion for installing busybox? Right now I'm using Stericson BusyBox app.
[Nexus 4 Android Development] thracemerin:
Well, I copied that script from your post and it didn't work because it was missing that line, then I added it and now it's working perfectly.

I used the Stericson busybox app to install it too.

Dunno what else to suggest.
[Nexus 4 Android Development] Kocai:
Yes, I'm aware that the command that I posted was missing that line however my script has that line. What version of busybox are you using?
[Nexus 4 Android Development] thracemerin:
1.20.2 I think.
[Nexus 4 Android Development] thracemerin:
Try this:

using terminal emulator

get root by typing 'su'

go to /system/etc/init.d/

try running the script './<scriptname>'

see if it throws an error

if there's no error, see if it actually modified the sysfs files by going to the path and looking in the file.

let me know the results.
[Nexus 4 Android Development] Kocai:
I'm really stupid when it comes to using terminal emulator.

Are these the correct commands?

su

cd /system/etc/init.d

./<bundi22motley>

I got sh: syntax error new line unexpected

Sent from my Nexus⁴
[Nexus 4 Android Development] thracemerin:
without the < > in the name :)
[Nexus 4 Android Development] Kocai:
Sorry! :/

Okay there's no error. And when I check by using these command:

#!/system/bin/sh

cat /sys/devices/platform/mipi_lgit.1537/kgamma_red

cat /sys/devices/platform/mipi_lgit.1537/kgamma_green

cat /sys/devices/platform/mipi_lgit.1537/kgamma_blue

cat /sys/class/timed_output/vibrator/amp

The results match with my script. Now I'm more confused.

Edit: thracemerin, you once said that you're willing to try gammacontrol that doesn't make the screen looks like a SAMOLED.

This is my favorite settings. The whites look really white. No yellow tint.

#!/system/bin/sh
# Color settings
# Set the gamma values
echo "164 0 39 119 0 1 1 2 0 2" > /sys/devices/platform/mipi_lgit.1537/kgamma_red
echo "164 0 39 119 0 1 1 2 0 2" > /sys/devices/platform/mipi_lgit.1537/kgamma_green
echo "164 0 39 119 0 1 1 2 0 2" > /sys/devices/platform/mipi_lgit.1537/kgamma_blue

# Set the complimentary RGB values for this calibration
echo "255 255 255" > /sys/devices/platform/kcal_ctrl.0/kcal
echo 1 > /sys/devices/platform/kcal_ctrl.0/kcal_ctrl

Sent from my Nexus⁴
[Nexus 4 Android Development] thracemerin:
So are other scripts working? or no scripts are working? in init.d that is.

Edit: are you using the JW or JS version of the kernel? and what ROM?
[Nexus 4 Android Development] AcmE85:
Could you tell me if the last boot works with cm10.2?

I am almost home, but maybe you already know if it works or not...

Thanks!
[Nexus 4 Android Development] thracemerin:
Here's what I'm thinking for 4.3, I'm open to comments if people have an opinion before I do it:

1) kill all the links to 4.3 versions in this thread.

2) post separate threads for 4.3 JS and 4.3 JW versions

3) deal with support for 4.3 in those threads as they may eventually present different challenges.

4) continue support for 4.2.2 b10 in this thread until it reaches end of life (all ROMs that are going to update have been updated)

I think this is the best way for me to provide help and support for everyone going forward without it becoming a huge confused mess with 3 kernels being supported in 1 thread.

Unless someone objects strongly to this plan, I will do the cleanup and begin with this later tonight or tomorrow.
[Nexus 4 Android Development] thracemerin:
If cm10.2 is like other cm builds, it will bootloop using the AOSP ramdisk which is what I'm using right now for the JS builds, I will build a CM version once the official nightly builds begin, until then the answer is likely neither version will work.
[Nexus 4 Android Development] ryan92084:
Go with whatever keeps you most sane imo.
[Nexus 4 Android Development] Remoteconcern:
Sounds fine to me, I think with the CM versions too that would be the easiest thing. Annoying from Google. I'm going to stick with factory images and await a point release in future.
[Nexus 4 Android Development] babymatteo:
I'm actually using your Alpha3 build on CM10.2 right now. Battery life is awesome so far and performance is buttery smooth. Played at least 30 mins of Riptide GP2 without any hiccups. ON-screen transitions are also smooth as hell. Much better than stock Aosp imo.

Flashed using Flash Image Gui without any problems. I'm always away from my home pc so i have no other means to flash boot.img' s unless i use Terminal, but that takes too much typing lol
[Nexus 4 Android Development] thracemerin:
I did identify an issue where the built-in root won't work on CM10.2 without a change to the ramdisk or an init.d script though, if you flashed superSU that won't matter. Good to know it works though :)
[Nexus 4 Android Development] babymatteo:
Yup I did flash SuperSu 1.50. But yah, loving this kernel so far.
[Nexus 4 Android Development] Kocai:
I only have one script...

I was using JW kernel on stock JWR66V from the factory image. I'm already using rascarlo's rasbean jelly so there's no need to discuss this anymore. I apologize for taking your time and thank you for being patient with me.
[Nexus 4 Android Development] FeintDoxx:
How hard would it be to add USB otg capability to this kernel? Well if possible. I need USB otg to back up some data but I really don't want to use another kernel.

sent from the lone wolf next door with a Nexus 4 using XDA Premium.
[Nexus 4 Android Development] Remoteconcern:
Is it even possible on N4? I think only very hacky solutions exist, including needing an external power source. Think it's been discussed before and said that it won't be added.
[Nexus 4 Android Development] thracemerin:
Short answer: not that hard, but...

^ This, it also seems that mathkid had difficulty implementing it into Matr1x and ended up reverting it due to other issues.
[Nexus 4 Android Development] FeintDoxx:
At this point I was wondering if I could do it myself. But that would require for me to have a PC. I'm familiar with the methods needed to get it to work. As which is why I got USB OTG y cable to get the external power source and the required patch to do so but as far as kernel modification goes I have no experience there but I'll probably attempt it once I get a PC and if time is available once school begins. Either way I appreciate the response and I'll just have to switch between the patches kernel and your kernel until I gain more knowledge in android development.

sent from the lone wolf next door with a Nexus 4 using XDA Premium.
[Nexus 4 Android Development] thracemerin:
NEW ALPHA for JS builds

Can be found here: http://xdaforums.com/showthread.php?t=2385840

Discussion about these builds should take place in that thread from now on.

Enjoy :victory:
[Nexus 4 Android Development] dxxvi:
Could you please tell me (or give me a link) how to flash boot.img using Terminal (the phone usb port has some issue I think because I don't see my phone with lsusb but I can see another Nexus 4 with the same usb cable)?

Thanks
[Nexus 4 Android Development] Kocai:
Using terminal emulator? It's dangerous because if you put the wrong path, you could potentially brick your phone. It's safer to do it via adb.
[Nexus 4 Android Development] aeroman:
I don't know why here its so quiet, but this Kernel rocks. :D :good:

I use it actually with very economy Settings (trickster mod) and Antutu gives me over 20.000 Points. :good:

But 1 question...

In the Op I read what from low CPU frequency 304 MHz. But Trickster or Android Tuner shows only up 384 MHz.

Where is the low freq. 304mhz? :D

Greetings

*tapatalked* Nexus 4
[Nexus 4 Android Development] thracemerin:
See post 3 :)
[Nexus 4 Android Development] Kocai:
From the 3rd post:
[Nexus 4 Android Development] thracemerin:
In fairness I should update the OP with the correct features :cowboy:
[Nexus 4 Android Development] aeroman:
I thanked you in Op, for good work. :good:

I see there is a lot of stuff in the Op, I must read it later [MENTION=313982]home[/MENTION] in peace. ;)

I quest me why all kernel developers put on Sweep2wake and not Touchwake? :)

I think touchwake is easier & user friendly, or what means you here?

Best Regards

*tapatalked* Nexus 4
[Nexus 4 Android Development] Remoteconcern:
Kernel developers add support for sweep2wake. The developer of touch control has to add support for kernels, and he has decided not to support this kernel.
[Nexus 4 Android Development] aeroman:
I use S2W with TricksterMod, works well with latest Version. ;)

Greetings

*tapatalked* Nexus 4
[Nexus 4 Android Development] :
Some feedback on S2W, when I have it enabled it acts weird during a phone call because my cheek touches the screen and sometimes after the call ends it goes inside settings. It happens even if the screen was locked and I picked up an incoming call.

This has never happened when s2w is disabled with this or any other kernel. Was wondering if it was specific to this kernel?
[Nexus 4 Android Development] californicated:
Also happening with other kernels when s2w is enabled. Hard to choose between s2w und touch control, both have their own pros and cons
[Nexus 4 Android Development] passlogin:
Does this kernel supports FauxSpeaker? If not, could you merge his patches?
[Nexus 4 Android Development] akiv:
Does anyone know where I could find stock 4.3 kernel+components. Coming from Franco and I know he has added his own ramdisck etc.
[Nexus 4 Android Development] show-p1984:
Since you have a Nexus you should use the advantages that come with such a device, exempli gratia: Factory Images.

https://developers.google.com/android/nexus/images
[Nexus 4 Android Development] thracemerin:
304 has slightly less voltage than the stock 384, otherwise the tables are the same as stock.

There are OC frequencies available (1566Mhz, 1620Mhz and 1674Mhz) but they are disabled by default, you would have to use a script or a tweaking app to enable them.
[Nexus 4 Android Development] Audioboxer:
Thanks for carrying this kernel on :good: Sadly abandoned it when motley went MIA :crying:

Out of interest, are your fixes from here already implemented? http://xdaforums.com/showthread.php?t=2102986
[Nexus 4 Android Development] pro.aggro:
Is this version with a wifi fix?
[Nexus 4 Android Development] thracemerin:
Read my comments regarding this in Post 3.
[Nexus 4 Android Development] pro.aggro:
I did, but these settings does not work for me.

motley49 with the updated prima drivers works fine.
[Nexus 4 Android Development] thracemerin:
So if you have the following settings:

McastBcastFilter=3

HostArpOffload=0

gEnableSuspend=2

You still get delayed notifications? In which apps?

I use a highly secure government network for work, the prima driver returning a bad MAC address effectively destroys my ability to use WiFi while at work because the server will deny authentication because the mac addresses don't match, as a result I can't use the new prima or ARP offload patches in any kernel I intend to use as a daily driver.
[Nexus 4 Android Development] thesebastian:
I always wanted to know this....

If i just installed Google Stock ROM and i want to flash:

- m+

- m+ build 2 (update)

- SuperSu.zip

Can i just flash the 3 files (in that order) and only do 1 reboot?

Up to now...i was always rebooting my N4 for each .zip file. (Using CWM).
[Nexus 4 Android Development] thracemerin:
No reason why you would need to reboot in between.
[Nexus 4 Android Development] thesebastian:
Thanks, You started to save me a lot of time! :)
[Nexus 4 Android Development] RaydenEris:
This Kernel works great on Carbon .... and that's all I'm going to say about that. Thank you for all your hard work. Hope this is helpful.
[Nexus 4 Android Development] RaydenEris:
Oh yea one last thing.
[Nexus 4 Android Development] pro.aggro:
WhatsApp and Email. Messages only arrive, when i turn my screen on.
[Nexus 4 Android Development] AcmE85:
Same behaviour here. Sometimes they arrive with screen off delayed by 5 to 10 minutes.

Motley+prima works better for me.
[Nexus 4 Android Development] gianton:
Which file has the prima drivers?
[Nexus 4 Android Development] thracemerin:
He's talking about the one in _motley's threads by kszaq.
[Nexus 4 Android Development] gianton:
Is there a file with just the prima drivers that we can flash with m+ b2?
[Nexus 4 Android Development] thracemerin:
Not currently, I'm working on a method of loading the wlan driver as a module which will allow for swapping between the stock version and newer ones from CAF. It presents a few small problems, like you have to have fully functional init.d, which means that it will only work on ROMs with busybox installed.
[Nexus 4 Android Development] gianton:
2nd full charge!

About 5 hours on 3G rest on WiFi
[Nexus 4 Android Development] thracemerin:
Keep in mind, the ARP offload fix (essentially the core of the new prima driver) has been reverted again by most devs who added it, both CM and PA reverted it due to issues with the MAC address problem that I talked about.

In my testing the prima patch only fixed the delayed notification issue for a short time (even on my home router which behaves more like most routers) it would eventually fail when the router attempted to cache the ARP information again (depending on router that could be somewhere between 1 and 24 hours), so it worked for a while but eventually the notifications stopped again and would only start again once I restarted the phone to reset the router's ARP information. This behavior was reported by numerous people in my hsic_fix thread where I've been working on this issue for a couple of months, it was also reported by people in the CM thread and the PA thread, the people who had no problems at all with the new prima driver was the very small minority of users, most had similar or worse problems than stock.
[Nexus 4 Android Development] gianton:
So really there's no proper fix yet and we have to wait for Qualcomm or/and Google to fix this for good. Is this correct?
[Nexus 4 Android Development] thracemerin:
Yeah, hopefully for whatever version of Android is coming at Google I/O (either KLP or JB 4.3 depending on who you believe).
[Nexus 4 Android Development] thracemerin:
On another note, goo.im approved my application last night and I'm in the process of setting up downloads from there and via goomanager.

All kernel versions will now be available from: http://goo.im/devs/thracemerin/mako/m_plus

The versions there have to be named m_plus instead of m+ because of their server naming rules but they are the same as the ones from dev host in every other regard.

I'll change Post 1 once the whole thing is finished setting itself up.

This will also allow my buildbot to build the kernel and push it directly to goo.im :)
[Nexus 4 Android Development] Kocai:
Maybe not as good as gianton's but it's still the best battery life I've had since I got the N4. Note: 7 hours were spent with mobile data and WiFi off. I only plugged the phone for a few minutes to get last_kmsg after I got a soft reboot.