yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] tdunham:
Not familiar with virtualbox but VMware recognizes the bootable OS cd and does an easy install for you of multiple operating systems. Its pretty slick.

Plus you can take snapshots of the OS so you can 'go back' easily in case you're testing something out and want to revert to an earlier build or whatever.
[Miscellaneous Android Development] Shikhar A:
it depends... well .. i guess latest baksmali and smali jar support kitkat api ... so you should just upgrade to those... and the latest apktool jar... thats it i guess.. for deodexing....
[Miscellaneous Android Development] Shikhar A:
It better to run Kitchen in Ubuntu /Linux Mint... much faster... VMware is way too slow... in linux based it uses SWAP very efficiently...
[T-Mobile Samsung Galaxy Note 3] Ark1406:
I'm currently on AOSP, Is there any way how I can update my bootloader to the latest one? I know you have to Odin flash and check update bootloader, but which 4.4.2 official firmware do I flash? Would flashing an SM-N900 work?
[Nexus 7 Android Development] jfmcbrayer:
Notes

F2FS support

While this kernel (from a22 on) includes the f2fs driver, it does not include any of the ramdisk or init tweaks that you would need to use f2fs. This is because I am not in a position to test f2fs myself. That said, the a22 (and later) kernel installer will not disturb any changes you have already made to your ramdisk or ROM to support f2fs, so if you have already got f2fs working on your device, it should continue to work after installing this kernel. Don't forget to do a nand backup in your recovery before installing, though. Seriously.

NTFS R/W support

This kernel (from a22 on) includes RW support for NTFS. However, in KitKat, NTFS USB drives mounted with StickMount are not writable due to SELinux policy. To write to an NTFS USB drive, you need to (from a root shell) 'setenforce off', then 'setenforce on' when you're done using it. I do not recommend that you put SELinux in permissive mode permanently. It's there for a reason, and this is just a workaround for a policy error in KitKat. The SELinux SetEnforce Toggle app is a convenient way to turn it off and on for this.

Mount slave namespace workaround

Android apps that mount filesystems (e.g. CIFS, Lil'Debi's loopback fs), mount them in a private namespace that is not shared with other apps (as explained by mkasick). There is a rom-based workaround applied in CM-based roms, and probably many others, but not in stock. Instead, I am applying his kernel/ramdisk based workaround. If you are on stock and need this workaround, do not use the anykernel build; use the one with the full disk image.

Configurable baseband_xmm_power wakelock timeout

This is based on work by Sgt. Meow, with some tweaks. It is controlled by the module param /sys/modules/baseband_xmm_power/bb_timeout, which defaults to 10, and represents the time, in 10ths of a second, that the baseband_xmm_power wakelock should be acquired for before timing out. 0 will disable the wakelock completely as in earlier versions of carcosa-kernel. These semantics are not the same as those for the same parameter in Oxydo, so be aware.

-------------------------------------------------------------------------------------------------------

Camilla: You, sir, should unmask.

Stranger: Indeed?

Cassilda: Indeed, it's time. We all have laid aside disguise but you.

Stranger: I wear no mask.

Camilla: (Terrified, aside to Cassilda) No mask? No mask!

– from Act 1, Scene 2 of The King In Yellow
[Nexus 7 Android Development] bjcrj:
Kernel rocks! Thanks!
[Nexus 7 Android Development] jfmcbrayer:
You're welcome. Are you using the milestone release or the alpha? And are you on grouper or tilapia? I want to know if the baseband_xmm_power hack is being tested by anyone besides me.
[Nexus 7 Android Development] bjcrj:
I am using the alpha. I run a grouper rom on tilapia and didn't have any wake lock issues.
[Nexus 7 Android Development] gremlin89:
Hi, I'm using the newest CM Release and after flashing the kernel i got a com.android.phone has stopped error. I cleared the cache and the dalvik before restart.
[Nexus 7 Android Development] jfmcbrayer:
The boot.img in the zips I've provided us built with a stock ramdisk, and CM needs its own ramdisk. Perhaps I could build an AnyKernel zip for non stock users.
[Nexus 7 Android Development] pjcanales:
What ROM are you using?
[Nexus 7 Android Development] adrman:
Just flashed mr1 on bshiznit’s stock ROM earlier today. So far it's running nice and smooth. Nice work!
[Nexus 7 Android Development] bjcrj:
Aospal
[Nexus 7 Android Development] gremlin89:
Oh that would be really great. Is it easy to build such a rom?
[Nexus 7 Android Development] jfmcbrayer:
Not a ROM, just an updater zip. In principle, it should be easy. But somehow, I've never got it to work.
[Nexus 7 Android Development] sengst:
Thank you very much for your work! Without your kernel my battery was empty within one or two days due to the annoying wakelocks, now my N7 runs since 7 days and I still have 40%! Awesome!
[Nexus 7 Android Development] jfmcbrayer:
I'm glad to hear it. Am I correct in assuming that you have a tilapia device, and are running the alpha version of the kernel?
[Nexus 7 Android Development] ispukan:
Just a question

What is the difference between Milestone and Alpha ? btw i am using nexus 7 wi-fi only model
[Nexus 7 Android Development] sengst:
You are right: tilapia aosp and your a20 kernel.
[Nexus 7 Android Development] jfmcbrayer:
Currently, the difference is that the alpha disables the baseband_xmm_power wakelock, which some people perceive to be a major source of idle power drain on the 3g (tilapia) model.
[Nexus 7 Android Development] ispukan:
So i can install what ever i want there is now difference for wifi only model ?
[Nexus 7 Android Development] jfmcbrayer:
Right; you can run either on a Wi-Fi only (grouper) device, but the changes are only relevant to tilapia.
[Nexus 7 Android Development] sudipt123:
Hi, can I use this kernel on PA 4.1 beta on my tilapia? Currently using the Franco r77 kernel and still get massive baseband wakelocks! If this kernel doesn't work on the said ROM, how do I revert to the stock kernel? Using the FKA app and have a backup of stock kernel. Thanks
[Nexus 7 Android Development] jfmcbrayer:
I honestly don't know if it will work with PA or not.

What you'll want to do is in your recovery (cwm or twrp), do a full nand backup before flashing. Then flash my zip, and if it doesn't boot, boot back into recovery and restore the boot partition from your last backup.
[Nexus 7 Android Development] jfmcbrayer:
Thanks to some help from sgt. meow, I'll have an AnyKernel ZIP available some time this evening or tomorrow.
[Nexus 7 Android Development] jfmcbrayer:
I've built an AnyKernel zip for a20: carcosa-a20-anykernel.zip.

If you're using a non-stock ROM, please feel free to give this one a try. It ought to work with any ROM, but as always, no warranty, make a backup first.

I'll update the OP later.
[Nexus 7 Android Development] Fransis88:
can you please add support for f2fs A20, I would like to test this version in tilapia, but currently carry F2FS.

thanks
[Nexus 7 Android Development] jfmcbrayer:
My strong first inclination is to say no, mainly because I would not be testing it on my own device. I'm also not doing any ramdisk or ROM development, so if I added the f2fs driver, it would only be useful to people whose systems are already properly configured for f2fs and will use the AnyKernel zip to update.

Still, if all I have to do is cherry-pick a clean patch such as this one, then I could probably do that. I do want to have as many people testing the wakelock removal in tilapia as possible.
[Nexus 7 Android Development] Fransis88:
thanks man, I currently use with omnirom partition and format data in f2fs xperience kernel v17. if you could adapt I will be happy to try it. thanks

Enviado desde mi Nexus 7 mediante Tapatalk
[Nexus 7 Android Development] jfmcbrayer:
carcosa-a22-anykernel.zip is available now.It includes the f2fs driver (and adds ntfs r/w support). It doesn't include any other changes you might need for f2fs support, so you'll need to have all those set up before installing this kernel. Make sure you have an up-to-date backup in your recovery before trying this.

It also includes support for ntfs r/w and changes some defaults for the smartmax governor (which is now default).
[Nexus 7 Android Development] Fransis88:
moment as installed and operating normally. leave smartmax governor and other defaults, consumption will comment in a few days time performance of the ommirom, and activated f2fs art is spectacular ... thanks for the work

Enviado desde mi Nexus 7 mediante Tapatalk
[Nexus 7 Android Development] Fransis88:
I managed to install pac tilapia (sabermod) with your kernel and booted all great! and f2fs ...

pac = cm = caf?? thought your kernel is based on stock and not stand CM roms??

either case, the result with a rom compiled with sabermod is very good, I'm going to stay with pac and your kernel.

I'm sorry I changed rom, MultiROM me is that it does not work with ommi f2fs and missing things for my taste, although it is my favorite.

in defnitiva, I prefer the pac + kernel Carcosa, and in a few days I'll have my news consumption and performance.

thanks
[Nexus 7 Android Development] jfmcbrayer:
a22 and later will work with most ROMs.
[Nexus 7 Android Development] Fransis88:
could introduce oc? I'm used to always carry a 1.5 ghz frequency. I goes great performance and consumption are not usually see very upset .... pac moment with me and your kernel will all ok.

Enviado desde mi Nexus 7 mediante Tapatalk
[Nexus 7 Android Development] jfmcbrayer:
I will probably not add overclocking, as I just don't see it as necessary (I actually underclock to 1.2 GHz). I might add undervolting given a clean patch.
[Nexus 7 Android Development] sgt. meow:
https://github.com/souljaboy11792/oxydo-grouper/commit/a57c4dfbb211f2aea96275701a0606ca7ad42d2f

and

https://github.com/souljaboy11792/oxydo-grouper/commit/8879d61799eeae4a309c442c45ecfa87ecf9c9cc

There you go
[Nexus 7 Android Development] jfmcbrayer:
Thanks! Ironically, I applied these yesterday just because I got a "round tuit" and looked through my various git remotes for clean patches ?
[Nexus 7 Android Development] jfmcbrayer:
Okay, carcosa-a23 is up, and includes undervolting.
[Nexus 7 Android Development] chaostrodamis:
Does your last update support F2fs data only or is this a allf2fs supported kernel.
[Nexus 7 Android Development] jfmcbrayer:
The kernel includes the f2fs driver. Whether your system is set up for f2fs data only, or all partitions f2fs, depends mainly on the initial ramdisk, which this kernel updater doesn't change. So if you have already set up either data only or all f2fs with another kernel, this kernel should work. Bear in mind that there are no warranties associated with this kernel, and be sure to back up at least your boot partition with your custom recovery before flashing it.
[Nexus 7 Android Development] bjcrj:
Kernel works great on omni ROM all f2fs!
[Nexus 7 Android Development] jfmcbrayer:
OP updated with new version (carcosa-a25). This includes a fix for empty app-mounted directories on stock (probably not needed on non-stock roms), and, against my better judgement, overclocking. Enjoy with care.
[Nexus 7 Android Development] Fransis88:
God work...excellent combination(crom+carcosaA25@1,5 smartmax) 16900 pts antutu

Enviado desde mi Nexus 5 mediante Tapatalk
[Nexus 7 Android Development] jfmcbrayer:
By the way, is anyone testing this on tilapia having occasional mobile data dropouts? I have one about once a day that is usually fixable by turning on airplane mode and turning it off again, but I'm not sure whether it's related to my patch, or just a coincidence (could be my mobile provider). I'm personally testing a patch using a wakelock timeout (as suggested by [MENTION=4394172]sgt. meow[/MENTION]), but I may not bother publishing it if no one else is having problems.

Update1:

So, after testing overnight, I've got 11h 50min unplugged, and baseband_xmm_power wakelock for 1h 7min (9.5%, 1666 locks), compared to 25min for PowerManagerService.Wakelocks. IMO this is still too much; it needs to be equal to or less than PowerManagerService.Wakelocks. I'm going to leave it in place for today to see if it solves my data dropouts, and if so, I'm going to reduce the timeout. It's currently 5 seconds; going to try reducing it to 0.5 seconds.

Update2

The patch doesn't seem to fix my data dropouts. If I keep having them, I'm going to test with mr1 for a few days to make sure it's my data provider. In the mean time, I've reverted to a25. I'm still interested in hearing other peoples' experiences.
[Nexus 7 Android Development] jfmcbrayer:
a27 is up. It is merged with 4.4.3 sources but has no other changes.
[Nexus 7 Android Development] Monfro:
Working really well here on allf2fs (as previous version)!!

Great work!!
[Nexus 7 Android Development] jfmcbrayer:
I goofed, actually, and included baseband_xmm_power timeout. A28 will be up later.
[Nexus 7 Android Development] alexche77:
Hi men thank you for your work!

I managed to download it nd flashed it, excellent battery life but i think that due to GPU OC i get reboots due to overheating!
[Nexus 7 Android Development] chaostrodamis:
Are we still expecting this release?
[Nexus 7 Android Development] jfmcbrayer:
Yes, sorry about that. I meant to get it up the same day, but life interfered. A28 is up.
[Nexus 7 Android Development] jfmcbrayer:
The GPU clock defaults to the stock 414MHz. If you're overclocking it and having trouble, of course turn it down. You might also check the MPU clocks and voltages. Since I added overclocking, I think the default voltages may be a little lower than stock (they're from faux), so you might do a comparison, and/or not use the higher clock speeds.
[Nexus 7 Android Development] chaostrodamis:
Well understood. Thanks for the hard work
[Nexus 7 Android Development] theoctavist:
Been running this with carbon all f2fs. Nice work fella.
[Nexus 7 Android Development] Carter07:
Is voltage control implemented in this kernel?

I can't find it in fauxclock and trickster mod.
[Nexus 7 Android Development] jfmcbrayer:
Voltage control is on the "specific" tab of TricksterMod.
[Nexus 7 Android Development] jfmcbrayer:
a29 is out. It makes the baseband_xmm_power wakelock run on a configurable timeout, or allows you to disable it completely at runtime. See the second post for details.
[Nexus 7 Android Development] Carter07:
Can't find it, see screens. :(
[Nexus 7 Android Development] jfmcbrayer:
Oh, you're running mr1. That's very old. Look at the release history to see which was the earliest release with voltage control, or just install the latest.

I really ought to pick a recent release to designate mr2. Any preferences, dear users?
[Nexus 7 Android Development] Carter07:
Oops sorry didn't see changelog, now I'm running a29 and runs great. :)
[Nexus 7 Android Development] marco.palumbi:
hello [MENTION=4075479]jfmcbrayer[/MENTION]

I see that your install zip includes the library power.grouper.so

why did you include it?

which are the differences with the stock one?

where are the sources for it?

I flashed the zip after removing the file and it seems to work fine (solving the power drain issue..)

thanks
[Nexus 7 Android Development] jfmcbrayer:
That is the power HAL. It is my understanding that the stock power HAL will not tolerate overclocking: it will reset the max CPU frequency to stock whenever the screen goes off. I pulled this binary from M-kernel, if I remember correctly, but all the overclocking kernels for grouper and tilapia include it. I think it is based on the sources here: https://github.com/thalamus/android_powerhal.

I've stopped including it on my experimental builds for lollipop, and it seems like it's not necessary any more.
[Nexus 7 Android Development] jfmcbrayer:
Lolipop update is here: carcosa-a33-lp-anykernel.zip. It rebases on the released sources for 5.0.2 and adds the SIO IO scheduler.

At some point, I want to tag my last (unreleased) KK kernel as milestone release 2, but I'm pretty limited on time right now.
[Nexus 7 Android Development] x-system:
Oh. thank you very much!

How I can change GPU overclock, CPU overclock(in cm12 it not work), CPU voltage control?

What you think about 5.0.2? What better for good performance and battery drain? 4.4.4 or 5.0.2?
[Nexus 7 Android Development] paolocorpo:
He suggested this:
[Nexus 7 Android Development] x-system:
paolocorpo, jfmcbrayer Thank U. All work!
[Nexus 7 Android Development] paolocorpo:
very well

I think that this is a grear kernel !!

@ jfmcbrayer: i think that you would set by default ii in this way
[Nexus 7 Android Development] jfmcbrayer:
How has your battery life been with these settings, compared to the default?
[Nexus 7 Android Development] paolocorpo:
Frankly speaking i am not sure about ...

It seems smaller vs default setting but if it is true .. it is not so much :)
[Nexus 7 Android Development] x-system:
Hello! It kernal compatible whith 4cm11?

I have nexus 7 only one week and want compare whith 4.4.4.

Me still do not like battary drain(
[Nexus 7 Android Development] jfmcbrayer:
Use version a29 with 4.4.4. The only change is that a29 does not include the SIO IO scheduler.
[Nexus 7 Android Development] paolocorpo:
Do you have a TILAPIA model ??

Just TILAPIA has the isse related to baseband_rx_wakelock that is completely fixed by this kernel CARCOSA
[Nexus 7 Android Development] x-system:
Okay. I will try..

---------- Post added at 08:30 PM ---------- Previous post was at 08:24 PM ----------

hah) No)

At first my tablet was 4.4.4, but then 5.0 on air.

Then I flash cm12 and now want flash to 4.4.4 (cm11) =)

My eng is veri bad. I'm ashamed.
[Nexus 7 Android Development] x-system:
What about zram in your kernel?
[Nexus 7 Android Development] jfmcbrayer:
My experiments with it using other kernels suggest zram is not very useful on this device, so I haven't been highly motivated to port it.
[Nexus 7 Android Development] x-system:
Thanks for your answer.

Four kernels should be joined depending on the load or they should work all time?
[Nexus 7 Android Development] x-system:
So, yesterday I flashed cm12 (build from 2015.02.10) + carcosa-kernel and.. I in disheartened.

After reboot all settings in Trickster MOD are reset.

Battery drain during the night is very bad.

location off

wifi/3g off

ather programs not installed

Google sync only gmail and contact, but syc too off.

Also I disablet GoogleAnalytics service, but it again runing.

All standart program updated

Sorry for non-eng interface.

Also, top right corner slightly warm.
[Nexus 7 Android Development] jfmcbrayer:
I don't know what's causing your battery usage problem, but it's most likely not related to the kernel. I wouldn't try both a new ROM and a new kernel at the same time. Run the stock CM kernel for a few days before trying alternative kernels on it.
[Nexus 7 Android Development] x-system:
Thanks for you. What about Synman's rom? It rom will be develop next? I want try it)
[Nexus 7 Android Development] brainvision:
Woooow

Very impressive!

I can confirm BTW that the drain you had is not related to the ROM, can't be..

Maybe there was a process stuck in background: the system should have killed it, but for some reason it didn't.. Maybe if you rebooted the tablet the drain would have done.

My suggestion is to flash again from scratch: a clean flash so to be sure that nothing went wrong when you installed CM.

About the Synman ROM.. I tried it and I used it for a while when it was the only lollipop choose for us. But now I don't think I could stay with it.. ROM is solid as rocks, but its based on AOSP, so no themes and no CM goodies!
[Nexus 7 Android Development] x-system:
Thanks! I flashed cm12 2015-02-11 and I will be watch
[Nexus 7 Android Development] svs57:
AICP 5.0.2 + carcosa-a33-lp

N7 3g discharge when connected to USB.

usb_config_wake_lock prevents the tablet to sleep

Do only I have this issue?
[Nexus 7 Android Development] paolocorpo:
Does it happen only when it is connected USB to a PC ??

SO it means that the discharging process is "stronger" than the charging process ??
[Nexus 7 Android Development] svs57:
Yes. It happen only when connected to PC.

Tablet is in airplane mode. I have tested on empty Google account directly after fresh install AICP and kernel.

Tablet stay on the same battery level or even discharge.
[Nexus 7 Android Development] jfmcbrayer:
I have not seen this. However, you should generally not expect an N7 to charge on USB unless it is turned off, regardless of kernel.
[Nexus 7 Android Development] svs57:
Probably it is ROM's issue and not kernel. But when I use stock N7 charge from USB.

I thing it's nonsense that N7 discharge when connected to USB power and stay on the same battery level long time when disconnect.
[Nexus 7 Android Development] svs57:
I have the same issue on pure stock 4.4.4 with a29

I didn't install any application and test after reboot n7

N7 discharge and usb_config_wakelock about 80%

My Samsung S4 charge from the same cable and usb port even it heavy load.

It's kernel problem
[Nexus 7 Android Development] jfmcbrayer:
The proper test would be to compare to stock ROM *and* stock kernel on the same device, not to compare to a completely different device.
[Nexus 7 Android Development] svs57:
Result of this test is that cable and usb port work fine.
[Nexus 7 Android Development] jfmcbrayer:
I spent a little while researching this, and I'm pretty sure what you're seeing is the stock behaviour, but that you're just now noticing it.

The file that wakelock appears in hasn't been touched by me or anyone else outside of Asus, according to git log. I did take the time to do an experimental build that put a strict timeout on that wakelock. The result was that MTP file transfers didn't work, so I reverted that change.
[Nexus 7 Android Development] Tommmii:
Hi,

if a rom uses M-kernel, should it also work with Carcosa ?

Specifically [ROM] XenonHD-5.0.2 Stable 1.0 (18.02.15) F2FS, is using M-kernel, but the xmm wakelock issue is way better on Carcosa.

Thx,

Tom.
[Nexus 7 Android Development] jfmcbrayer:
Yes, it should work fine. Be sure to make a backup anyway ☺
[Nexus 7 Android Development] jfmcbrayer:
a35 is up. It syncs with the kernel changes in 5.1, but is still compatible with 5.0.x. The only notable changes are hardware support for the kernel's encryption routines. The 5.1 stock kernel has this support, but turns it off, so it's possible it's not ready for prime-time.
[Nexus 7 Android Development] paolocorpo:
downloaded

i will install on my n7 with synman
[Nexus 7 Android Development] ganeshp:
Is this Kernel compatible with 5.1 Stock ROM?

Also does this eliminate baseband_xmm_power wakelock permanently?
[Nexus 7 Android Development] jfmcbrayer:
The latest build is compatible with 5.1 stock. By default it eliminates the baseband_xmm_power wakelock completely, but you may have intermittent connectivity issues -- adjust the timeout to something other than 0 if you do (I'm currently setting it to 300 on my n7).
[Nexus 7 Android Development] Tommmii:
would a35 be ok on 5.1.1 rom ?
[Nexus 7 Android Development] jfmcbrayer:
I think so, but be sure to back up the boot partition first. I am running an unreleased build which is not very different from a35 on stock 5.1.1 currently.
[Nexus 7 Android Development] Tommmii:
no boot for me, then again might be due to the rom (xenonhd) and/or the filesystems (system : ext4 ; cache and data : f2fs )
[Nexus 7 Android Development] williamlaw:
any new update support 5.0 ?

Thanks
[Nexus 7 Android Development] jfmcbrayer:
a33 and newer support 5.x. I'm running a35 on 5.1.1 currently.
[Nexus 7 Android Development] williamlaw:
Thanks !

Since baseband_xmm_power keep happen.

I want to try "Experimental: remove baseband_xmm_power wakelock"

But actually after impact to function / network if disabled this wakelock ?

Thanks