yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] thracemerin:
goo.im transition finished, Post 1 updated. :good:

New build in the works, I'm digging through _motley's 4.2.1 kernel to see if there was anything he didn't merge forward to 4.2.2 :D
[Nexus 4 Android Development] sirxdroid:
And while they are at it, I hope they also take care of sending track info to the receiver when streaming music via Bluetooth. It's ridiculous that it's 2013 and that basic feature doesn't work. I don't suppose anything can be done about it in the kernel, it's in the Bluetooth driver stack which I understand is new for 4.2.x
[Nexus 4 Android Development] thracemerin:
Yeah, Bluetooth issues are all in the garbage Bluetooth stack Google decided to go with for 4.2.x.
[Nexus 4 Android Development] thracemerin:
Build 3 is on the buildbot now (could be up to 1hr until it's done and downloadable), changelog is in Post 1. :good:

Happy flashing! :victory:
[Nexus 4 Android Development] Kocai:
What if I don't want to use 192mhz frequency? Can I just delete the script that you added?
[Nexus 4 Android Development] thracemerin:
Yep. It's /system/etc/init.d/01cpu.

You can delete it from the zip before flashing too if you want.
[Nexus 4 Android Development] Kocai:
Yes, that's what I already did. Thanks for the quick reply and confirmation.
[Nexus 4 Android Development] thracemerin:
Added that info to Post 3 :good:
[Nexus 4 Android Development] Kocai:
May I ask if in the next build you plan to modify the ramdisk to make the 192mhz frequency as the default minimum frequency? Or are you waiting for feedbacks? Nevertheless please put it in the changelog so I can add the lines from your script to set my preferred minimum frequency in my script. Thank you :)
[Nexus 4 Android Development] thracemerin:
Modified ramdisk will be in the next base build, it will probably be a while.

My kind of unofficial plan is to release a base build once a month, (we'll call B1 the May version) so not for a few weeks, and it will absolutely be in the change log :)
[Nexus 4 Android Development] gianton:
Testing with 192MHz min freq at 600mV.
[Nexus 4 Android Development] thracemerin:
Let me know how that goes.

I'd like to find the stable voltage for 192MHz, so if people could do the following.

If you undervolt it below the default value and get no SoDs or other odd behavior (over a reasonable period of testing time, 5 minutes is not reasonable, 12 hours+ would be most helpful), post the following here:

CPU Bin (slow, nominal, fast, faster)

voltage value you're using

If we can find a good value, I'll lower the stock voltage to that.
[Nexus 4 Android Development] gianton:
I'll do, currently charging... will let you know how it goes. :good:

---------- Post added at 07:53 PM ---------- Previous post was at 07:22 PM ----------

In b3 zip file, inside kernel folder there is another zip file "m+_anykernel_422_build_11.zip". Is it left in purpose?
[Nexus 4 Android Development] sirxdroid:
Any lower freq than 192? I think the latest Faux kernel can go down to 162 :)
[Nexus 4 Android Development] thracemerin:
LOL, no.

I wouldn't flash that, I have no idea where it came from.

Edit: oh, it appears my buildbot was doing some strange things and decided to make that zip for some reason, anyway the build is perfectly safe nothing happens with that zip at all, but i wouldn't extract and flash it or anything like that.

Edit 2: the mystery zip is now gone.
[Nexus 4 Android Development] gianton:
OK thanks. So if we flashed b3 the mystery zip wasn't flashed too? No need to reflash b3 right?
[Nexus 4 Android Development] thracemerin:
Nope, the flash script doesn't do anything at all with it, it's just there taking up space in the zip.

I give an inch and you want a mile huh? I'll think about it :)
[Nexus 4 Android Development] sirxdroid:
Not sure if you guys have seen this new Community Kernel project:

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

Maybe there's some stuff in there that can be pulled into _m+ and the other way around.
[Nexus 4 Android Development] thracemerin:
Yeah, I've been looking at it, right now it's just bricked with a few cherry-picks from faux and franco.

I've been thinking about using showp's three phase thermal rather than the one that's in the kernel now since it does a little better at keeping the heat under control. Otherwise there isn't much they have that we don't, other than the option to use showp's mpdecision, faux's intellidemand hotplug or stock mpdecision and I personally think that the current hotplug driver we use is better and who really needs 3 different hotplugging options anyway? just seems like it wastes space and has the possibility for odd consequences if a bunch of them are online at the same time.
[Nexus 4 Android Development] sirxdroid:
It would be cool to have a kernel that you can customize at install time, like you can do with some ROMs and Aroma installer, pick and choose only the features you want. Or at build time, a build system that can be set up to build a customized kernel with only the features someone would use and with the default settings that someone would use (but still be able to tweak some settings post install). I would love to be able to sync the source for such a kernel and just fire up a build on my own machine.
[Nexus 4 Android Development] thracemerin:
Some things can be built as modules (WiFi driver, file system mounting (cifs, tun, nfs, ntfs), android logger, etc...) and installed during boot or later, but you can't really do that for everything.

I'm going to see about building WiFi as a module so people who want new prima can use it without having to build a separate kernel each time, but right now the prima master branch is screwed up (someone pushed changes without rebasing and partially reverted some other changes) and wont build, so I have to wait for them to get their act together with that before I move forward on that particular idea.
[Nexus 4 Android Development] Four1Fool:
When grabbing a build from Goo, are people just flashing on top of a previous m+ build, or do I have to backup and reflash my system rom as well? Can I just slap this thing on, reboot and keep going? Noobish question I know, but currently I go through the process of TWRP/Nandroid backups, then factory wipe, flashing, restore. That seems like a pain. How are people flashing updates of kernels and other roms and getting back up and running quickly?
[Nexus 4 Android Development] thracemerin:
If you are coming from B1 or B2 (without flashing a ROM) you just need to flash B3, shouldn't need to do anything else.

If you are coming from another kernel (without flashing a ROM), you need to flash B1 then B3.

There isn't any need to reflash the ROM or do backups or anything, but it's never a bad idea to have a semi-recent backup just in case.

If you flash a new ROM, you'll need to flash the ROM then flash B1 and B3.
[Nexus 4 Android Development] iamhacked:
After I installed this kernel, WiFi won't turn on. I tried flashing stock, motley, matr1x kernel, clearing cache and dalvik cache, even factory reset but WiFi still won't turn on. I of course lost my root during the factory reset too. The phone was charging, could it be the heat that destroyed the inside hardware? Because my phone didn't crash or anything, just longer than usual boot times after restoring and factory reset. I've had one kernel not turn on WiFi before but it was fine after flashing another kernel, not like this where WiFi doesn't turn on AT ALL. What should I do?
[Nexus 4 Android Development] thracemerin:
What kernel were you on before? If it was one with a non-stock prima try flashing the wlan revert that is in post 3.
[Nexus 4 Android Development] iamhacked:
I was on the motley kernel modified with prima retention fix before, but I'll try that.

EDIT: Worked, funny I had this problem. great now I just have my app data to restore back manually. :D
[Nexus 4 Android Development] DroidBlaze:
I just wanted to say thank you so very much for doing this. Motley's kernel was my favorite kernel in terms of smoothness and battery life. The addition of the 192 freq was just the cherry on top for me. It makes a big difference in battery life for me when listening to music and makes my phone run cooler (I can uv this freq more than 304). The only thing I would love would be gpu oc but if you don't include it that's fine since this kernel is awesome as is :highfive:. Thanks
[Nexus 4 Android Development] gianton:
Update testing 192MHz at 600mV (CPU Bin faster), all my usual stuff running rock stable. Noticed around 1-2c lower temp of CPU.

All settings run with scripts.
[Nexus 4 Android Development] Remoteconcern:
I've been running 192 at 600 also, no problems with overnight usage. I've got a fast binned chip, not a faster. I'm not sure how stable that would be for other people though!
[Nexus 4 Android Development] Franklin Bernard:
Hi Thracemerin,

Thanks for continuing Motleys work.

I have been running with 192 for first 2 cores and 594 for last2 with 600mv for both (with init.d removed yours). Its been running great.Fast binned.

I have a few questions not related to 192 though.

1. This probably would have been discussed so many times. I am getting drain of 2+% for every hr in 3G with and without sync on ( thought it would be better without sync)when I am not using it. Is this normal ?

2. Do u know how many CPUs will be online when the screen is off ? Is it 1? or may be based on load like sync , etc ?

3. Is there anyway possible to force the number of CPUs online when the screen is off ?

Thanks,

Franklin Bernard
[Nexus 4 Android Development] rokK0:
Do I have to flash the WLANfix with?

Getippt von meinem zivi
[Nexus 4 Android Development] AirOne70:
Thanks for this kernel ! I like Motley's kernel, so Motley+ is perfect.

Just.. We need this: https://github.com/faux123/mako/commit/d13a5c5511dd84095b57eceb845508336028ff30

:angel:
[Nexus 4 Android Development] thracemerin:
Next build, I didn't realize there was an update. :good:

1) I average about 1% or less an hour while idle on WiFi and about 1.5% on 3G. There are a lot of factors with 3G that may make your drain worse, but the big one is if you have weak signal the radio has to step up to max power and it takes longer for the data to sync, that can cause you to have some pretty nasty drain, sadly not much can be done about this because the radio itself is a huge black hole that nobody knows how to modify.

2) It should be 1, but it will ramp up depending on load based on the governor you're using, though for just sync you probably shouldn't need more than 1.

3) You could use the min_online_cpus/max_online_cpus and tasker (or similar) to set a different number of processors when the screen is off, there is no direct way to do this in the sysfs right now.

This has the stock Prima WiFi driver at the moment, the information on how your files should be set up is in Post 3
[Nexus 4 Android Development] knitler:
Not to start a flame war, but what makes this kernel better/worse than Faux's ?
[Nexus 4 Android Development] thracemerin:
It's worse than faux kernel in every way ;)

Edit: Well, maybe I wasn't being serious about that. I wouldn't say it's better or worse, but it does include some features and implementations that faux kernel doesn't, just like faux kernel provides some features and implementations that this kernel doesn't. It's a personal preference whether or not you prefer this kernel or faux (or any other kernel for that matter.
[Nexus 4 Android Development] knitler:
I wish there was a sticky that listed the features/differences in the different popular kernels.
[Nexus 4 Android Development] swaggerwocky:
For what it's worth, I stayed on motley's kernel even while the others were being updated and his did not see any progress for quite some time. I did not find it necessary to look elsewhere since it gave me the balance of speed, stability and battery life that I wanted with my phone.
[Nexus 4 Android Development] thracemerin:
Me too, which is what motivated me to put some work into doing a few updates on it.
[Nexus 4 Android Development] funcrusher:
Same here, guys. I actually just started trying a couple other kernels in the past few days. I'm definitely going to check this out. Thanks.
[Nexus 4 Android Development] SeaSeeC:
I know you don't really like getting asked this but would you ever consider putting Sweep2wake on this?

Sent via my Nexus⁴
[Nexus 4 Android Development] thracemerin:
As far as I know this kernel still supports Touch Control (if it doesn't bug bponury in his thread), a kernel can only support the in kernel solution or Touch Control not both since they conflict.

Edit: oh, I guess Touch Control is broken and bponury said this kernel is too small for him to support. Not that I'm advocating harassing bponury but his solution is much better than the in kernel versions, so this would be the preferable method to get this functionality, I suppose if it looks like he's not going to support it once this kernel gains a little more momentum I'll consider adding something.
[Nexus 4 Android Development] brainbeatuk:
Hi theraceman did you read my message? Wondering if you still got that test build with low UV.
[Nexus 4 Android Development] thracemerin:
I'll get you something ASAP, I have a lot going on :)
[Nexus 4 Android Development] brainbeatuk:
Cool cheers.
[Nexus 4 Android Development] thracemerin:
Build 4 is on the way (changelog in Post 1) :good:

As always, it'll take some time to make it from the buildbot up to goo.im and available to download.

I also linked my jenkins status page in post 1 so you can watch the buildbot do it's thing.

Note: As I said in Post 1, there are archives that are technically downloadable from jenkins (i can't get them to go away without disabling the archive script completely)

DO NOT DOWNLOAD THEM

, this is the one and only warning, if anyone does the build bot status page will disappear.
[Nexus 4 Android Development] AirOne70:
http://goo.im/devs/thracemerin/mako/m_plus/exp/m_plus_anykernel_422_build_4.zip

B4 is here! Thanks. ;)

Envoyé depuis mon Nexus 4
[Nexus 4 Android Development] brainbeatuk:
Hi I've tested turning thermal off on this build 3 and 4 and managed 600mv at 1674mhz performance. Gonna test battery life at 1296 600. :)
[Nexus 4 Android Development] IAmAN00bie:
...there's no way that's even remotely physically possible. Maybe we haven't been using 600mV at all this whole time like show-p mentioned in his thread?

Also, does anyone know the directory to control the Headphone power amp?
[Nexus 4 Android Development] brainbeatuk:
Well I just tested method on other kernels trinity and matrix. Trinity I managed to be stable at 800 and crashed 750 at 1812 matrix I couldn't crash and I get better top end benchmarks. Can't remember volt think 700.

Whether its 600 on this is a mystery
[Nexus 4 Android Development] thracemerin:
I'm reasonably sure that we are in fact using 600mV if that's what's set.

I can't explain how this is possible, but even on a faster binned chip this should be nowhere near possible. Turning off thermal will of course get you better benchmarks since it won't throttle when your chip gets hot, but this isn't a good idea.
[Nexus 4 Android Development] caaznkid:
Headphone poweramp control?

Can someone explain to me what it is? What's the difference between this and adjusting the headphone gain, etc? Thanks!
[Nexus 4 Android Development] AirOne70:
Delete this message please
[Nexus 4 Android Development] thracemerin:
Looks like all the sound control parameters are in /sys/kernel/sound_control

For those interested:
[Nexus 4 Android Development] brainbeatuk:
Well I figured out when I'm on 1512 at 600 I tried making a screen off profile. Tried a few different ways performance etc got sod on wake every time. I realised you can change from 1512 at 600 to 304 at 600 but crashes if I then go 1512 again so I presume you need alot of volt to change state higher.

I think if I turn thermal back on though it'll crash on overheat when changing speed. I had running for few days but not done a full rundown battery test yet keep getting sidelined.

I noticed standby time isn't affected by this maybe music wake lock uses slighty more draw but on a whole looked shorter times when I was checking on matrix got a full batt now so testing your build 4 at 1026 600 performance 4 core allways on

Just an early report down to 75% with 1.5 hrs screen on time. Looking 5 or 6 hrs lol
[Nexus 4 Android Development] IAmAN00bie:
Anyone know any good values to use for the headphone power amp feature? I read on Faux's thread that to get the best quality one needs to lower the Digital gain and increase the Analog gain. What would be good numbers for these?
[Nexus 4 Android Development] thunderger:
While reviewing some cyanogen-commits I noticed that the sony exp. Z/ZL uses the apq8064 soc that should be the same as the nexus 4 uses. Sony has an official aosp repo, so perhaps there a some cherries to pick :)

https://github.com/sonyxperiadev/device-sony-c6603
[Nexus 4 Android Development] veyka:
It seems that the ability to disable the input boost pulse via /sys/devices/system/cpu/cpufreq/interactive/input_boost was broken at some time, I am not sure when, but it's not working in the newest build :)

Sent via Nexus 4
[Nexus 4 Android Development] thracemerin:
How are you trying to shut it off?
[Nexus 4 Android Development] veyka:
As per the post with all the script instructions, echoing 0 to that interface, but the file doesn't exist.

Sent via Nexus 4
[Nexus 4 Android Development] thracemerin:
/sys/devices/system/cpu/cpufreq/interactive/input_boost ?

I think that might have been disabled by _motley. I'll look into it, if it was i'll remove it from the instructions.
[Nexus 4 Android Development] brainbeatuk:
Hi so I found out some more info. I can set two to performance and two to interactive so long as max on interactive isn't same as performance.

I have tweaked governor and hot plug settings and added to 01cpu init.d script. BTW trickster mod is incompatible as it doesn't have multi core control like android tuner. I have turned thermal off. Only need to do a heavy game session to test but it passes antutu stability test. Could be modified for better battery still. Not able to upload on phone here is lines of script.

Edit. Actually just tested gta vc it ran at 40fps for 20mins got to 81°c eek. Gonna try like 2x 1350 interactive and 2x performance 1512. So I deleted script
[Nexus 4 Android Development] veyka:
Cheers! I suppose flashing the inert powerhal would also do the job, but would be nice to have the option back for fiddling :)

Sent via Nexus 4
[Nexus 4 Android Development] thracemerin:
does setting /sys/devices/system/cpu/cpufreq/interactive/boostpulse_duration to 0 disable it?
[Nexus 4 Android Development] veyka:
Doesn't seem like it

Sent via Nexus 4
[Nexus 4 Android Development] thracemerin:
It looks like maybe CAF disabled the ability to turn it off.....hmmmmm
[Nexus 4 Android Development] thracemerin:
Google pushed a 3.9 branch to the kernel/msm git on android.googlesource.com.....interesting. Looks like it's missing most of the LG specific parts required for mako but it could have some cool stuff we can use nonetheless.
[Nexus 4 Android Development] veyka:
Sounds good, will be interesting to see what can be picked.

No issues with b4, and it's been running well, thanks your hard work!

Sent via Nexus 4
[Nexus 4 Android Development] gianton:
+1 b4 running great!
[Nexus 4 Android Development] sigma392:
Any update with the Prima drivers? :)
[Nexus 4 Android Development] rodries:
Yes, please.

With new prima drivers I have no delay using b49, but I want to use your new kernel and I have delay (I've tested changing gEnableSuspend to 2 but no luck)
[Nexus 4 Android Development] thracemerin:
I've said this before, I'll say it again, the Prima drivers break functionality that I need in order to be able to use WiFi on my work network, I am working on a solution to be able to build different versions that can be injected dynamically for those who would prefer to use a newer version, until then I will keep the WiFi driver as is so that I can use this kernel as my daily driver (there is no ETA for this, it's giving me nothing but trouble). I realize that the gEnableSuspend fix doesn't work for everyone but neither do the Prima drivers.
[Nexus 4 Android Development] sigma392:
I have found a temporary solution. Try turning off BMPS (Beacon Mode Power Saving) in the config file. Change the default value of 1 to 0.
[Nexus 4 Android Development] rodries:
Works!

I hope it doesn't affect battery too much

I'll use as a temporary solution

Thanks

Edit: no deep sleep. I can't use this solution.
[Nexus 4 Android Development] thracemerin:
Added a new Pre-release (Alpha) build to Post 4, see there for info. :good:
[Nexus 4 Android Development] AcmE85:
Thanks, I will test and report bugs.
[Nexus 4 Android Development] thracemerin:
Based on a few hours of testing, it looks like the patches to battery make the drain more linear rather than having it stick at a percentage for hours and then all of a sudden drop 5%, this may be placebo, but it's good if it's true :)
[Nexus 4 Android Development] Audioboxer:
Yeah the new test version is working good here.

Is there any chance sweep2wake could be added (default off obviously). It doesn't look like the touch control dev wishes to ads support.

Thanks
[HTC One S] Specimann:
Hey together.

(at first: I do not want use a finished custom rom. I am happy as my Rome is now running)

I Would like to deodex my JB Stock Rom to coustomize my self with Mods and other but for almost everything i used a deodexed Rom. I tried xUltima and the Android Kitchen, v0.223 by dsixda and both doesn't work.

On the Android Kitchen, v0.223 by dsixda i can't find my TWRP Backup and i don't know how i convert it or somthig else.

On xUltima i become instantly an Error. When i delete the odex file which caused the error i become instantly a another error.

Here is a Picture from xUltima:

i have no idee how i fix this.
[HTC One S] Specimann:
no one an idea?
[HTC One S] mr_verystock:
Make a imitation ROM:

Create a dump.

Download Rhythm Manager's version of file manager.

Now go to / (self explanatory) and copy system.

It'll take a while, but copy it to sdcard.

Now copy the file onto computer. Find a ROM and copy the META_INF.

Make a empty boot.img.

Put the boot.img, system, and meta_inf into a zip folder. THis would be your ROM.

You can take it from there.
[HTC One S] Specimann:
okay sounds quite simple but i have some questsions. it does not matter whitch META_INF i use? And how i make a empty boot.img? Can i put the Deodexed file back in the Data und Jar Folder or must i flash it?
[HTC One S] mr_verystock:
1) Yes. Any ROM is okay. Just get it from an actual ROM.

2) Step 1: unhide extension by going explorer.exe --> organize --> Folder and search options --> view --> uncheck Hide extension ... --> click apply to folders--> Apply. Now simply make a .txt file on desktop and rename the extension as img, and the file name make it boot.
[Sony Xperia P, U, Sola, Go] lebartman:
First 1000 Thanks to s4tch for the info

http://xdaforums.com/showpost.php?p=40785050&postcount=94

Now flash this ICS ROM which have OTA Jelly Bean update.

http://www.xdafileserver.nl/Files/S...LT22i - 6.1.B.0.544 -Central Europe - ICS.rar

Root it with Flastool (very simple because it's 0.544 rom)

Install OTA RootKeeper

https://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper&hl=fr

Start OTA RootKeeper

Click "Protect root"

Click "Temp. un-root"

Download your OTA JB update (and only OTA)

Install you OTA update.

When your phone reboot, start OTA ROOT KEEPER

Click : RESTORE ROOT

Et voilà c'est fait :)

Envoyé depuis mon LT22i avec Tapatalk
[Sony Xperia P, U, Sola, Go] LilBlinx:
http://xdaforums.com/showthread.php?t=2249077

I think the link is enough
[Sony Xperia P, U, Sola, Go] lebartman:
Do you try it ? No

Do you link the right ICS rom for the OTA update?No

Do you thanks s4tch in the OP of your thread?No

I don't ask, don't want and don't need thanks...but i think the link to you thread is not enought

Do you want me to wipe the thread?

Envoyé depuis mon LT22i avec Tapatalk