yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] sirxdroid:
USB debugging does not matter while you are in recovery mode. See where the toolkit put adb.exe, cd do that directory and run adb from there like this:

.\adb devices
[Nexus 4 Android Development] mangomonkey00:
srry to ask such a noob question but do i have to flash two zip i.e. build 1 and the latest to get everything working
[Nexus 4 Android Development] AcmE85:
Yes, exactly. :good:

Always build 1 at first, followed by the latest build (either exp or wip).

No need to restart in between.
[Nexus 4 Android Development] lazer155:
I wound up factory resetting through recovery because I didn't see your reply in time and a few other threads that I read made it sound like usb debugging was required to sideload with adb. I did try what you said though with finding adb.exe and I can sideload with usb debugging turned off so that's useful to know for any future bootloops.

Do you have any idea why it would have bootlooped in the first place? I had just flashed a fresh copy of CM to reset my kernel like the instructions said to do.
[Nexus 4 Android Development] azrash:
if you are using CM nightly, the 0407 build has a bug that would produce system UI FC, that should be fixed in 0507. So use 0307 or older build first, and update once 0507 or newer is out.

Did you flash the correct base? There are two version, one for AOSP and one is specifically for CM and CM based ROMs.

Flash base, then exp or wip

Flowed from my Nexus⁴ using Tapatalk 4 Beta
[Nexus 4 Android Development] lazer155:
Yeah I saw that. I was using the 0307 build. 0407 never even downloaded for me using the built in updater. I kept getting failed download messages. So it wasn't that problem.

I used the CM base then the latest exp. Maybe it was just a random error. I'll try it again today.

Is battery life any more improved in the latest experimental compared to the last build made by motley?
[Nexus 4 Android Development] azrash:
Try checking the md5sum of the files, against the MD5 value posted in Goo.im

You can either use winMd5Sum or rapid CRC to calculate the md5sum, both are free and available as portable version at portable apps. Com, incomplete download maybe?

Quite surprised to hear that it didn't boot though, I am using nightly myself.

Have not done any proper benchmark against the last motley's, but the new simple governor for the gpu should reduce battery usage.

Flowed from my Nexus⁴ using Tapatalk 4 Beta
[Nexus 4 Android Development] lazer155:
Well I couldn't even start the download from my nexus using the updater so I couldn't get any bit of the file to check the md5checksum. I had the same issue just now with the 05/07 build so I restarted my phone. After that it started downloading and the md5checksum matched when I checked it. I'm not sure what was going on. But that's an issue that I had after the boot looping and subsequent factory reset from recovery mode. (I was on nightly 03/07 the entire time). The updating problem isn't kernel related. It was probably so issue with the factory reset or just needing a quick restart (it had been on since the factory reset).

Anytime I've had incomplete downloads with ROMs it's been on my phone but my computer winds up downloading fine so I think the nexus is just a bit less reliable with large files. It works 99.9% of the time though so it's not a big issue.

I'm flashing the base and experimental builds of m+ for cm right now so we'll see how that goes.

Edit: It flashed perfectly this time. However I can't under volt with the same super low settings I had before with motley's last build:

600000 600000 600000 600000 600000 600000 600000 850000 887500 937500 950000 962500 975000 987500 1067500 1075000 1100000

I'll have to retest all my values again to get new ones.

Does this kernel use the mid range frequencies more compared to motley's? I think he or thracemerin mentioned in motley's thread once or twice that a lot of times old values don't work anymore with improvements/updates to kernels because more of the mid/mid-low range frequencies get used mire often rather than only the high and low ones (which is beneficial for battery life since those mid frequencies use less power than the high ones).
[Nexus 4 Android Development] veyka:
Before about b8 uv was not being set below 800ish (I forget what it was exactly) whatever value you put in, due to an issue with the UV code. Thus your phone was never actually using 600mv.

Also, how goes getting Mpdecision as an option going? ;)
[Nexus 4 Android Development] thracemerin:
Yes, _motley edited the wrong regulator file which meant that the voltage was capped at 850mV minimum regardless of what you set, I fixed this.

The latest internal version of the mpdecision version is still rather disappointing, I'm not sure what I'm doing wrong with it, but I'm still not at a point where if I show it off that we won't end up with everyone saying "this thing sucks, i'm reverting".

Edit: more specific to the above, I'm trying to work on a way to force mpdecision to behave in a slightly more battery friendly manner without losing the smoothness that comes with using it, unfortunately rather than reigning in mpdecision the kernel is fighting with the mpdecision binary and causing all sorts of strange behavior. I'm not yet ready to abandon this plan, but if it continues to do this i'll just revert this stuff for now and release it.
[Nexus 4 Android Development] lazer155:
Lol, I missed that post. :o I had no idea it wasn't setting.

It's a great kernel so far :good: Nice and snappy.
[Nexus 4 Android Development] thracemerin:
Glad you like it :D
[Nexus 4 Android Development] veyka:
Thanks for the information! Franco did the same sort of thing in some of this early nightlys, maybe have a look, pre 100 ish
[Nexus 4 Android Development] thracemerin:
Since franco has rebased so many times since he used mpdecision most of his changes for that stuff are gone.
[Nexus 4 Android Development] veyka:
Well blast!
[Nexus 4 Android Development] azrash:
After a week using s2w and s2s, I am happy to report that there is no screen freeze so far. Both works great!

Just a few occasions where I have to swipe twice to wake up the device, but that is not an issue.

Thanks again thracemerin and showp

:good:

Flowed from my Nexus⁴ using Tapatalk 4 Beta
[Nexus 4 Android Development] danorthstar:
Sorry for the noob question but how do I enable S2w and s2s? Got trickster mod and running CFX SR15 with m+9.. Thanks

Sent from my Nexus 4
[Nexus 4 Android Development] thracemerin:
Have to use the latest Alpha to have s2w.
[Nexus 4 Android Development] azrash:
as thracemerin said, you need to flash alpha version.

then,

In trickster, it is under 'specific' - 'screen wake control'.

You can also run it as a script and put it in either userinit.d or init.d for it to start on boot. the command is available at the OP or here http://j.mp/10NwleD

Flowed from my Nexus⁴ using Tapatalk 4 Beta
[Nexus 4 Android Development] AcmE85:
Is s2w draining the battery any faster?
[Nexus 4 Android Development] thracemerin:
It does a little bit, for me between .2% and .5% more per hour vs comparable usage without s2w, it really only drains during idle however.
[Nexus 4 Android Development] AcmE85:
Thanks, but somehow i can't get it to work.

I flashed the wip build and put the script in place with the right permissions.

I am on CM10.1 LinaroBean

edit: nevermind, I activated it through FauxClock app.

Though it is weird that the script did not work...
[Nexus 4 Android Development] azrash:
Weird, I was using linaro bean last week and it worked fine. Did you edit the file on your PC or something? If you did, the formatting might be the issue. I used notepad++ to edit it. Or the built in text editor in root browser

Flowed from my Nexus⁴ using Tapatalk 4 Beta
[Nexus 4 Android Development] thracemerin:
I was going to build and post b10 this morning, but there have been a bunch of security holes identified in Android and in the linux kernel over the last few days some of which have existed for a while and have now been patched, so I decided to build a new Alpha quickly including these patches to ensure that nothing bad happens as a result before posting a stable.

The latest Alpha is in Post 4.

The following patches are included, more details are in the commit messages on github.

b33b387bc76041e4fbf185a7954a5be69541ad18 msm: msm_fb: remove mmio access through mmap
6fc45c026630d0516f849539899d20a0307503b2 msm: msm_fb: Add range checks for fb cmap.
0f87d1d4842f45643c5083d6fbbb826dc35d1d16 msm: audio: qdsp6v2: Add size safety check to ACDB driver
ee0792fd782d8888605e38b8e434c344142b3fc4 perf: Treat attr.config as u64 in perf_swevent_init()

Please test this out for the next 24 hours and let me know if you experience any odd behavior, if there are no reports I will build it as b10.

Happy Flashing :victory:
[Nexus 4 Android Development] lbtc777:
Thanks for continuing this awesome kernel.

Been using the latest beta since being uploaded and no issues to report. Smooth and stable.
[Nexus 4 Android Development] caliban2:
No issues to report on latest Alpha, I've been downloader #3. :)
[Nexus 4 Android Development] veyka:
No issues with the newest WIP here :)
[Nexus 4 Android Development] thracemerin:
Thanks for confirming that there don't seem to be any unusual issues, b10 will be up later today but since most of you are on the WIP anyway it won't really matter since there won't be any changes. :D
[Nexus 4 Android Development] Remoteconcern:
Late I know but no problems at all! Thanks, won't flash b10 if it's the same.
[Nexus 4 Android Development] rancatoco:
This kernel is still solving the problem of notifications with the screen off like it did Motley? I'm using Motley but screen colors are terrible!
[Nexus 4 Android Development] thracemerin:
B10 is up, see post 1 for the changelog.

For those of you using the last WIP there are no differences between it and B10, so there is no need to flash if you don't want to.

Happy Flashing :victory:
[Nexus 4 Android Development] Remoteconcern:
No it doesn't. Read the third post for more details.
[Nexus 4 Android Development] Archmag3:
yup read :) thanks..was just wondering is it same thing that is in Air kernel ? or this is some different thing for wifi fix ?
[Nexus 4 Android Development] thracemerin:
Completely different.
[Nexus 4 Android Development] yurilebbie:
Thanks for doing this.

One question though: are you going to try out going -O3 or use -O2 and just play some extra flags like _motley did?
[Nexus 4 Android Development] thracemerin:
_motley was using -O2, my test attempt to get -O3 to work won't boot, I'll figure it out and get it going. Right now it's -O2.

Also looking at the linaro gcc-4.8 toolchain, but that will take a lot more work than -O3, something for the future tho.
[Nexus 4 Android Development] mpmilestogo:
I just moved over to Motleys build 49 then saw the work is continuing. I want to flash build 2. Since motley 49 and your build 1 stable are the same, it's okay to just flash build 2 over the top of Motleys 49? I don't mind flashing your build 1 stable build and then moving on either.

Thanks.
[Nexus 4 Android Development] thracemerin:
If you flashed motley b49 using his method of b37->b49, then yeah should be no problem.

If you didn't, I would go b1->b2.
[Nexus 4 Android Development] thesebastian:
Thracemerin could you please create another opcional m+ build2 with the newest WiFi drivers?

gEnableSuspend=2 is actually good for text notifications.... But is definitely not good for VoIP calls notifications....(sometimes it requires more than 20 seconds to appear).
[Nexus 4 Android Development] oblivionstalker:
Hi thracemerin, faux has implement the customization of the C-state options in his kernel, will you be interested in the implementing it as well?
[Nexus 4 Android Development] thracemerin:
Well, the possibility exists to do what showp-1984 does and build the wlan modules separately and insert them on boot, this would allow for different prima versions to be added to a single kernel, I'll consider that.

I added Krait Retention (C3) if thats what you mean.
[Nexus 4 Android Development] raidrom:
I know motley was right along side faux . could you possibly lower min MHz to 164 . like faux I'm getting good battery there as my phone sleeps 95 percent of the day
[Nexus 4 Android Development] swaggerwocky:
Is there any way to confirm if scripts are properly enabling features?
[Nexus 4 Android Development] meangreenie:
Follow the paths in the scripts witha file explorer, and check the values.
[Nexus 4 Android Development] gianton:
I check mine with trickster mod app.
[Nexus 4 Android Development] thracemerin:
Info regarding C states is now in Post 2. :good:
[Nexus 4 Android Development] sigma392:
I love this kernel. Gave me an impressive 4 hours SOT. Too bad it died before I could screen it lol. Anyway is it possible to release a version that includes the latest WiFi drivers for the N4? Thanks in advance :)
[Nexus 4 Android Development] thracemerin:
I'm thinking up a way to do this because as I said in post 3 the new Prima introduces some other issues one of which makes my WiFi pretty much unusable at work, I think that I may be able to solve the problem by switching prima to a module and building a couple of switchable versions. I'll have to see how feasible that will be to support.

For now the workaround in post 3 will fix most delayed notification issues, but it isn't a perfect solution either. Ultimately we need Qualcomm, LG and Google to solve the issue because its a low level firmware problem and those are proprietary which means no source so probably no 3rd party fix.

Stay tuned ... :)
[Nexus 4 Android Development] TheDarkDefender:
Oh. Wow. Continuing motley's work! My favorite kernel on nexus! Great job!
[Nexus 4 Android Development] thunderger:
Fried CPU/GPU... yummy. ;) I saw some CPU OC in franco and faux kernel. In games, especially while using them with TV out, could profit. But everday usage won't profit. Perhaps benchmark overall scores. :) So GPU OC is more interesting to get highest game perfomance.

About integer perfomance, I'll try stock JB, CM10.1 with CM kernel, than m+, franco and faux. After getting results I'll post them here. I noticed low integer perfomance with motley b49, too.
[Nexus 4 Android Development] thesebastian:
I'm using Motley kernel (now m+) since a long time ago.

And I have a noob question.

If I just install the kernel (now m+ build2). Its runs just like Occam kernel? By default it has no OC/UC no voltage tweaks anything?

(Of course with new Qualcomm patches etc)
[Nexus 4 Android Development] thracemerin:
There was nothing in the official Motley kernel that changed how notifications work, if you are referring to the build by kszaq then no that fix is not present in this kernel, there are instructions in post 3 on how to fix most push notification issues however.
[Nexus 4 Android Development] veyka:
Any luck with the Mpdecision version? :D
[Nexus 4 Android Development] rokK0:
Can someone please take a screenshot of the m+ stock sound setting?

Thx a Lot
[Nexus 4 Android Development] thracemerin:
Yes, but I messed my N4 up pretty severely (requires JTAG), luckily I have a JTAG machine available to me, I just need the right bootloader files to get it going again, should be a couple of days I hope.

By the way, never try to modify the bootloader with a hex editor, it was a horribly poor idea.
[Nexus 4 Android Development] thracemerin:
What sound settings are you referring to? the faux sound ones?
[Nexus 4 Android Development] sirxdroid:
You are hard-core! :)
[Nexus 4 Android Development] thracemerin:
I'm really not sure what I was thinking, I guess I was less worried because I knew I could fix it myself if I did something horrible to it (which I did) :D. I'll blame the heat over the last few days, I guess it made me crazy, but days like this are when I'm glad I work in the basement of a building near the servers so it's always freezing cold down here.
[Nexus 4 Android Development] sirxdroid:
What were you trying to do to the poor bootloader anyway?
[Nexus 4 Android Development] thracemerin:
I was trying to see if I could get access to the secure partitions, even with bootloader unlocked there are some partitions you can't access (with good reason), but there is a theory that the Prima drivers don't work properly because we need to modify something in the persist partition which remains locked. Either way, bad idea.
[Nexus 4 Android Development] rokK0:
Just your default sound settings that you give your kernel with :)

Thx
[Nexus 4 Android Development] veyka:
Well bugger! You are just doing stupid stuff to keep me waiting now ;) But in all seriousness, hope you do manage to fix it, if you need anything dumped from a n4 I would be happy to help.
[Nexus 4 Android Development] thracemerin:
Naw, I just need my coworker to quit being on vacation and get back here so he can do it because I don't trust myself with a solder gun.
[Nexus 4 Android Development] veyka:
People on holiday, whatever next!
[Nexus 4 Android Development] thracemerin:
I called him and told him to quit being on vacation, but he hung up on me, the nerve!
[Nexus 4 Android Development] veyka:
People these days, you give them a inch, and they take time off! I am shocked and horrified.
[Nexus 4 Android Development] lightningstalon:
I would say, "please stay on topic," but this is actually kinda entertaining :p
[Nexus 4 Android Development] thracemerin:
I'm pretty sure I'm allowed to be off topic in my own thread, just sayin :cowboy:
[Nexus 4 Android Development] Remoteconcern:
Hahaha. Good stuff.

Is there anyway to auto online all 4 cores with screen on? I occasionally get wake up lag, where the elements on screen take a while to populate. I'm fairly sure Franco mentioned this was the way to deal with the problem. Obviously this is N4 dependent!

Thanks Thrace :)
[Nexus 4 Android Development] itsita:
I actually have this problem as well. What launcher are you on? I've never had at on trebuchet, it started with apex...
[Nexus 4 Android Development] iamhacked:
When do you think this kernel will be supported by touch control? Motley was recently dropped support as well.
[Nexus 4 Android Development] thracemerin:
Probably never, the author of touch control has ignored my attempts to connect with him to get it working. It now has s2w and s2s by default however.

Edit: if you want touch control you'll have to talk to bponury, I have no control over what he feels like supporting and not supporting.
[Nexus 4 Android Development] iamhacked:
Oh, well that's all I need, perfect.
[Nexus 4 Android Development] thracemerin:
Please note: This kernel is not known to be compatible with 4.3, nor will it be until the AOSP sources drop (probably next week), do not attempt to run this kernel with any 4.3 leaks that may be floating around as you will almost certainly boot loop , if by some miracle you don't boot loop you will probably experience other issues.

If 4.3 is in fact coming next week b10 will probably be the last 4.2.2 version, but all of this could change depending on if/when things are officially released, I will do my best to have a 4.3 alpha for you all as soon as I can.
[Nexus 4 Android Development] Four1Fool:
Who's using P.A.C. [http://xdaforums.com/showthread.php?t=2146879] and what version of m+ are you running? Since it's [PA3.60][AOKP-MR1][CM10.1] I wasn't sure which version to use.
[Nexus 4 Android Development] veyka:
Looks like selinux is hitting cm tomorrow, quite a bit of kernel stuff, would adding it cause issues on ROMs without it?
[Nexus 4 Android Development] thracemerin:
Not entirely sure to be honest. I'll have a look at it once they're done with the initial implementation.
[Nexus 4 Android Development] veyka:
Cheers!
[Nexus 4 Android Development] thracemerin:
I've been trying to figure out if the switch they're talking about in the blog exists yet and if so where it is in the settings all day, I've come to the conclusion that only parts of the SELinux implementation are currently in, even my homebrew build that was synced much later in the day than the nightly doesn't seem to have the toggle.
[Nexus 4 Android Development] Kocai:
This is the only info I got regarding SELinux from pawitp:
[Nexus 4 Android Development] veyka:
The mako stuff went in after yesterday's nightly, i dont know how much there is, or how much of it is turned on.
[Nexus 4 Android Development] thracemerin:
Given the sheer number of new packages required to enable SELinux support I may build it as a separate version for CM, plus it looks like Google may have put most of the support for SELinux into 4.3 so CM is just back porting it to 4.2.2, if that's the case and we're days away from a 4.3 release it seems a lot of trouble to get it working for the couple of weeks before the new CM 4.3 versions begin to appear. Either way, I want to make sure that Arcee and the others are happy with how it works on CM stock before I implement it, no sense in patching in a partially working feature :)
[Nexus 4 Android Development] rlaw:
Any idea why the new cfxperiment ROM won't boot with this kernel? Using build 10. The dev specifically mentioned the ROM being anykernel compatible..
[Nexus 4 Android Development] Koraboros:
Hey... so if I want to install build 10, do I have to install Build 1 first? then install b10?

Thanks.
[Nexus 4 Android Development] jazzboyrules:
Hi thracemerin, when I enabled sweep2wake, about 10 pixels on the left and right sides of the screen became unresponsive to touch. I use Swapps app that needs swipe gesture within 7 pixels of the right edge and that stopped working. It started working once I increased the activation width to 15 pixels. Have you seen this unresponsive edge syndrome :P ? I saw similar behaviour (either top-bottom edges becoming unresponsive or the left-right) when using bponury's TouchControl long time back. For now, I have disabled the sweep2wake but am looking forward to try it out again if you put out updates trying to fix this issue. Thanks!
[Nexus 4 Android Development] Remoteconcern:
I think you're best off posting this in showp's thread. Thrace just added it in, but showp wrote it. I use it but don't notice that by the way.
[Nexus 4 Android Development] thracemerin:
Rumor has it that showp is in the process of writing s2w2 so I don't know how much time and effort he'd put into the current version, I'll look at it a little and see if I notice anything glaring.
[Nexus 4 Android Development] show-p1984:
True, s2w2 is coming. It is taking quite a while because I cannot focus on it atm, the jetstream jellybean and kcontrol are pulling time away from it. (+ an unnamed mammoth project, lets call it project X)

Either way, it will take a while. S2W2 will be written completely device independent, meaning it should just be a matter of compiling the module for your kernel version and you are done. (like the kcontrol modules)

To the problem at hand:

You have a few very strange ( https://github.com/thracemerin/kernel-Nexus4/commits/m_plus_wip/drivers/input/touchscreen ) modifications to the touch driver in your source. I just tested the described behavior on my N4 with activated s2w with the exact conditions mentioned and do not get a touch screen lockup.

Now the question is: Does s2w break something that is influenced by those modifications, or do the modifications break something that s2w is influencing. :p (or am I just too stupid to trigger the bug?)

Maybe people noticing this bug could jump over to http://bricked.de and just test it with my kernel? Would help narrowing it down. (or you just provide a test kernel with stock touch driver + sweep2wake)

PS: The mako sweep2wake has quite a few s2w2 backports, ofc none of the features but a few 'robustness' and 'beauty' backports.
[Nexus 4 Android Development] thracemerin:
Ah, yeah the franco touchfilter stuff, I suppose I could remove it and see if that fixes the problem.

[MENTION=4304428]jazzboyrules[/MENTION]: are you using touchfilter? because I don't seem to be able to reproduce the behavior you mentioned with touchfilter off. I'm wondering if there is an interaction there that might be the problem.