yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] redeyedjedi:
Thanks for your input... I absolutely want this to work on 4.4, but on my end, I can only say that at least wifi has worked. It is bricked kernel, I have done nothing else to it with respect to overall performance, but Ive never been upset I guess. GPU can be OCed, dont know if it makes a difference. I do know this, the next oxydo release will have these functions as he has pulled them, so maybe you will like the smoothness of it instead. Showp originally put the wifi in module form, to reduce size, and it works for me because I play with external wifi adapters instead sometimes, but Im sure it could be built back in. However, there is no reason why you shouldnt be able to load a module in 4.4. At some point, Im gonna figure it out, but if you do first, please share.
[Nexus 7 Android Development] redeyedjedi:
I just remembered, I havent released a build with all the ipv6 changes for 4.4 yet..... SOOOOO sorry. It is my mistake, but at least I know now. I will get this up for you guys ASAP.

for hotplug DAC, the audio patcher needs adjusting or a manual smali operation needs to be figured out. Im thinking that the cm guys actually pulled these patches already tho, i need to check that....standby for a fully operational 4.4 build, I hope.
[Nexus 7 Android Development] andrew9292:
Just flashed CM11 (4.4.1) and the wifi works!

So it should be Purity's problem instead, or a conflict from the combination of rom and kernel.

Performance is subjective and hard to guage.

Slap a fast kernel with a crappy bloaty rom or some weird souped up ramdisk, guess what? :D

This kernel is great, just that stupid wifi quirk with purity.

looking forward to next build with better ipv6 too! PMed u btw & cheers. :highfive:
[Nexus 7 Android Development] willis936:
I was having boot loop after the install. Whittled the issue down to the governor. Setting it to interactive as opposed to the default ondemand with no other settings changed causes boot loop. Overclocking past 1.3/416 also causes boot loop on my hardware too so maybe it's not the installer's fault.

Edit: Even with default settings I'm on boot loop now. Caches wiped. I'm on smoothrom 5.3 and have been running lean kernel @1.5 no issues.
[Nexus 7 Android Development] sgt. meow:
I just pulled the USB hostmode and the DAC patches. Nothing to do with the WiFi and all other haxx stuff you got here. If you're going to make your N7 an all-round device that can take in anything from the hardware side, I highly suggest you try this kernel (as in this one). I haven't tried it myself but the OP's work is legit on Github. This should be able to take in different sorts of peripheral devices.

Regarding modules, I haven't checked but in the defconfig you have to set LOADABLE_MODULE (or something similar; you'll know) to Y.

Cheers.
[Nexus 7 Android Development] redeyedjedi:
Well, unfortunately, I can confirm this. Setting to interactive via the aroma installer WILL CAUSE BOOTLOOP. Dont know why, and I suspect this is a bug in the bricked release too, cause I did absolutely nothing to change his install scripts or the governor code. I prolly wont be able to help you on this except to say that he has customised the ondemand governor and it works very well, and there is no reason not to run with it. Also, I set it with ondemand via the aroma installer, and then used trickstermod to set it to interactive, with NO issues??? so, I guess its just the aroma script. BUt, you can bet Im gonna change the aroma installer to remove this option, and tell people to use trickstermod instead.... so thank you very much for pointing this out to me, to save other people from the same headache.

If you find, that even with this way to use interactive you still dont like it, then just wait for the next oxydo release, it will have the usb mods as well.
[Nexus 7 Android Development] willis936:
Nah it's no trouble at all. I'm just grateful to have usb audio support on android!

I'm still fiddling with things to get it to talk to my odac but I don't have too many ideas. I ran the mod linked in the op and I use usb audio recorder pro (trial) to test if there's a connection and I'm still not having much luck. It's still early in my quest to get it to work though.

Also my current phone is a droid razr maxx and I don't suspect that will change any time soon. Surprisingly the community is still busy over there with gnex 4.4 ports all over the place. The meta for me would be usb audio on my phone. Idk what goes into building a mod like that though and it may be out of everyone's scope right now.
[Nexus 7 Android Development] TheTenth:
I'm pretty sure that my N7 2012 with official CM11 works when plugged-in at boot into my usb PCM2704-based dac. But the fact it doesn't work for you makes me want to try again tonight :confused:

Also have to try on Sigma-based Hegel HD2 but it's a bit more tricky since it's usb-powered.

I've been trying to patch 4.4 with jacknorris' tool before, but haven't been able to give it much time. DAC hotplug would really be an awesome feature. (Have it on my semi-retired Acer A500 with tegraowners' 4.3 rom)

Does charging work when connected to a DAC through USB hub ?
[Nexus 7 Android Development] redeyedjedi:
yes,it will charge while connected to a DAC. its easy to add USB audio support at the kernel level, its one line in the defconfig. the thing with THIS kernel is you can hotplug, no need to be attached at boot, so it will work after a deep sleep, or suspend, without restarting tablet. and you can charge tab while using it.

the 4.4 thing is an easy fix, sort of.If there was just one 4.4 ROM that everyone uses, I could mod the source and build it. but everyone uses different ROMs, and I still use my tablet with a ROM that has tabletui....... so it is not reasonable to go around just modding one part of every 4.4 release. I highly recommend that you message the OP of the ROM you use, and ask them to pull the changes from here:

github.com/jacknorris

it has no effect on the ROM otherwise, it just redirects audio when DAC is plugged, and back to Internal afterwards. I myself have a bad history of asking people for their sources so I could change it myself, failing to realize some people don't care about the middle two letters of aosp. so I'll make things work from the kernel end, the rest is up to the user.

I have a new build almost ready that is fully updated for 4.4 mr1, including all ipv6 updates. I'm also close to getting drivers for the easycap dc60++ to build... If you have ANY piece of USB hardware that you want to use on your tablet....just ask, and I'll look into it. I've decided that this kernel should have something original about it, while everything else is based on stable kangs.
[Nexus 7 Android Development] sgt. meow:
Can't agree more on the AOSP bit.

However not all DACs work with our kernels. Dunno why. [MENTION=4705288]spthacker[/MENTION] can you see if your DAC works with this?
[Nexus 7 Android Development] _crue_:
instalation failed

my default.prop (stock 4.4.2)

#

# ADDITIONAL_DEFAULT_PROPERTIES

#

ro.secure=1

ro.allow.mock.location=0

ro.debuggable=0

persist.sys.usb.config=mtp

ro.adb.secure=1

installation looks for device name in props :( and fails

(nexus 7 wi-fi 2012)
[Nexus 7 Android Development] sgt. meow:
It checks the build.prop IIRC.
[Nexus 7 Android Development] _crue_:
TWRP: 2.6.3.1

I've got this, but I'm reporting :) that installation fails on stock 4.4.2, as in topic description writen about support of 4.4
[Nexus 7 Android Development] redeyedjedi:
Installation is just fine on 4.4, and 4.4.1/4.4.2. Where it fails is with TWRP 2.6.3.1. Im using the latest multirom recovery 2.6.3.0 without issue, but have had many issues with twrp 2.6.3.1, roms and kernels....I think it is a recovery issue.
[Nexus 7 Android Development] _crue_:
thanks :good::good::good: with 2.6.3.0 everything fine! :victory:

wifi gone to slepp :)

I'm no wifi at all :( did I done something wrong?
[Nexus 7 Android Development] redeyedjedi:
damn, forgot again. I've pulled all the ipv6 changes to bring the kernel to 4.4mr1, but haven't got it built and uploaded yet, will try to today. IIRC, purity has no WiFi but cm11 does. I'll get fully updated kernel to you all today I hope.
[Nexus 7 Android Development] _crue_:
np, :) I'm just tring to help make it better :silly:
[Nexus 7 Android Development] redeyedjedi:
OK just posted new update, wifi issues with any 4.4 roms should be resolved.
[Nexus 7 Android Development] _crue_:
Has kang1-1allmodules wi-fi included?

and will I able install modules from kang1-1allmodules on kang1-1 (base) kernel?

ps. I'm sorry, but wi-fi doesn't work :(

I've flashed kang1-1.

DAC, I can test, because hotplug doesn't works and loading with plugged DAC also

but OTG charging :) works fine.

I didn't test other (SDR radio) devices as I don't have wi-fi to download them.
[Nexus 7 Android Development] NoXXX:
So I just need to replace 4.4 files with NetFluke's ones and it will magically work?
[Nexus 7 Android Development] _crue_:
It should :) but as I didn't test it I can only hope it will works :)

patcher works :) with tablet content and patch resources.

it combine them, compile and put back on table

if there no compile issues (or similar) then it will works
[Nexus 7 Android Development] redeyedjedi:
I too don't get your troubles with pwrevntmngr. You can pull Timur's from usbrom (/system/app) and it will work in kitkat, but it always triggers on power loss..... It doesn't know the difference between fixed install/normal otg because the ROM doesn't tell it..... While crues version does. It should still work because you are in a fixed install. I can honestly say crue's version is just as reliable as timurs, but works in kitkat. I guess the 3g has something to do with it, that's the only difference.
[Nexus 7 Android Development] redeyedjedi:
This is how I patched purity ROM.......tho its not magic just replacing the code...... It absolutely works on purity ROM..... DAC on boot, hotplug dac, and volume control.

Smali/backsmali manager.....I think is what I used.
[Nexus 7 Android Development] NoXXX:
I replaced all files are in 4.4.zip archive by those you placed here. Patcher worked with no errors, but no sound on usb dac at all for me :(

Отправлено с моего SM-N9005 через Tapatalk
[Nexus 7 Android Development] NetFluke:
It might not - you may need default_audio.policy.so

I'll attach it later.
[Nexus 7 Android Development] NoXXX:
Lol. Spent a couple of hours fighting it :)

Отправлено с моего SM-N9005 через Tapatalk
[Nexus 7 Android Development] redeyedjedi:
So its working for you? Excellent. Ill update my OP within link to the patcher.....I've already uploaded the right audio.policy.so file.

http://d-h.st/g8s
[Nexus 7 Android Development] NoXXX:
No it didn't neither with CM, nor with stock 4.4.2.

On stock 4.4.2 I got bootloop after applying the patch. Bootloop caused by some services died (kinda camera, media and something else. saw it through ADB logcat).

On latest tilapia CM11 patcher worked, but USB DAC didn't work. I replaced audio.policy.so placed at /system/lib/hw/ with the one you've uploaded, set permissions like files' nearby, reboot and still no sound through USB DAC.

I feel unlucky today :(
[Nexus 7 Android Development] _crue_:
Did you applied patch a few times?

You have not!!!!!!!!

only once, this is related to re-compiling, it will went wrong in second time (no errors but patched files will be damaged)

to check is patch was allied just pres volume button

in stock 4.4.2 you have 11 levels in patched 44

then copy default audio policy so (exectly "default" in the name).

and sure you have to flash KANG-AROO kernel first of all, with out kernel :) you will get noting but USB audio
[Nexus 7 Android Development] NoXXX:
No, I applied it once.

1. Flashed CM11, flashed kernel, patched, replaced audio policy, set permissions, reboot - no usb audio.

2. Flashed stock 4.4.2 image wiping everything, flashed kernel, patched - got bootloop.

Don't know what am I doing worng.
[Nexus 7 Android Development] _crue_:
for stock :) you have to use mine patch, they different a bit? I've cut all CM11 logic from it

what USB DAC used?

Here is my pacthed files for stock, try to copy in /system/framework
[Nexus 7 Android Development] NoXXX:
I use Sabre Android DAC. It works fine on 4.2.2 USB ROM.

I'll try it tomorrow. It's late here in Moscow to walk around with notebook and do something in a car :)
[Nexus 7 Android Development] redeyedjedi:
When I get off work..... ill upload modded files for purity...... ill try to do a write up for manual patching for people who need it.
[Nexus 7 Android Development] jeb192004:
I been reading thru here and haven't seen anyone else with this issue I'm having so I'm gonna ask about it. I'm on CM11 and tried installing this kernal and now my tablet won't recognize my charger unless I have the screen on. I tried the newest and the older advanced power manager apps and it still won't recognize the charger u less the screen is on.
[Nexus 7 Android Development] Mugga:
Ah ok. For viewing the OBD information I programmed my own app. Also the info I'm getting for the app is not from an obd connector, I get the data directly from the can-bus behind my radio unit.

Regarding Firm Sleep:

I did a fresh install and there are several problems I discovered:

- The tasker plugin from the PowerEventMgr is broken at version 1.6 and higher. When I press configure and then the save icon, there is no command entered in the configuration tab. Version 1.5 is working, I hit save and under configuration "sleep" is listed.

- Also I deactivated firm sleep, the tablet is going into sleep after 5 seconds. When 5 seconds later the command to go into sleep is send via tasker, the screen is waking up.

Without tasker actions, and firm sleep activated trough PowerEventMgr, the tablet is sleeping fine. But I have to kill some apps via tasker when power is off. But killing seems to interrupt this process.

I did a little video to show you my settings and also the behaviour:

https://www.dropbox.com/s/0jxwnfa6hxo2qxt/FirmSleep.mp4

Just another thing, your updated audiopatcher isn't working for me. It just closes after launching it. With the other audiopatcher versions I got no problems. Here is a picture of the error: https://www.dropbox.com/s/1h7bjjnc66wxg6z/WP_20140212_02_56_19_Pro.jpg
[Nexus 7 Android Development] redeyedjedi:
Its kind of a bug and it kindve isnt. On purity rom and stock 4.4.2 this issue does NOT exist. On any other rom with an otg y cable it doesnt happen. On cyanogenmod and aokp with a regular microusb cable, it happens. It also doesnt go into lp0 unless using an otg y cable. This is only cyanogenmod and aokp and was also an issue in usbrom..... I havent messed with it because its exactly timur code and I didnt change it. Netfluke has a code change that I thought fixed it for cyanogenmod.....but I think he said it still isnt right. I dont know what to do about it.....ive always ignored it....again I havent wanted to change timurs code.

It does still charge when the screen is off.....you dont have to leave it on...... just use an otg y cable for cyanogenmod....behavior should be normal.
[Nexus 7 Android Development] NoXXX:
Oh, at last the patcher worked for my stock 4.4.2.

The problem was that the image I flashed was not really stock image. It was prerooted and something else. I downloaded stock-stock image, flashed it, patched and everything worked.

Will test powereventmanager later. I hope there will be no problems with it.

Thanks!

UPDATE: NAH, I can't control dac volume. Volume control has a lot (44?) levels of volume, but it doesn't control the dac volume.
[Nexus 7 Android Development] maharu567:
For me is the same...
[Nexus 7 Android Development] NoXXX:
I'm glad that it's not just me ...

---------- Post added at 11:56 AM ---------- Previous post was at 11:28 AM ----------

Well I replaced stock default audio policy library by the one redeyejedi attached and volume control now works. BUT there's still no DAC on boot. When I reboot Nexus with DAC plugged in, sound goes through internal sound card, not USB DAC. DAC hotplug works fine.

What's the problem?
[Nexus 7 Android Development] NoXXX:
UPDATE: looks like it works in FI mode like it should. :o
[Nexus 7 Android Development] NoXXX:
Guys, I can't find if there any way to change standby logo. Is it in the same way as were on USB ROM?
[Nexus 7 Android Development] GrandeParade:
Standby logo as in the image that is shown when the stand by countdown is showing?
[Nexus 7 Android Development] NoXXX:
Yep, exactly.

Отправлено с моего SM-N9005 через Tapatalk
[Nexus 7 Android Development] redeyedjedi:
Fixed Install Mode.
[Nexus 7 Android Development] redeyedjedi:
Yes you can......ask crue what to name it and where to put it.

Volume control requires the new audio policy and the patch.......exactly like jacknorris patcher
[Nexus 7 Android Development] NoXXX:
It's OK now, everything works fine now for me on stock 4.4.2 using the patch and default audio policy.

Отправлено с моего SM-N9005 через Tapatalk
[Nexus 7 Android Development] GrandeParade:
You have to add an image called powerdown.png to /data/data/org.kangaroo.pem and make sure you have read permission on the file.
[Nexus 7 Android Development] NoXXX:
I think that it would be great if this info is in the OP. I mean about patch and audio policy.

Отправлено с моего SM-N9005 через Tapatalk

---------- Post added at 07:37 PM ---------- Previous post was at 07:36 PM ----------

Oh thanks a lot!

Отправлено с моего SM-N9005 через Tapatalk
[Nexus 7 Android Development] redeyedjedi:
Yep......its good tho. Things get fixed/added/changed/figured out and then the OP is outdated. I'm forgetting to keep up and getting sidetracked.

I will fix it again when I get a chance.

Has anyone who has tried the r820t drivers gotten a picture yet in droidtv???? I'd like to update OP/kernel with these but I'd like their functionality confirmed first.
[Nexus 7 Android Development] _crue_:
Updated Power Event Manager.

fixed Tasker plugin bug.

fixed notification (opening application, settings, executing sleep).

minor fixes
[Nexus 7 Android Development] _crue_:
try this updated version.

http://xdaforums.com/showpost.php?p=50265682&postcount=411

if tabler wake up after going to sleep (no firm sleep) check what cause this wake up.

In tasker or notification (or main app button) mode (when table going to sleep no by power event), there is special listener for display (message that you got on wake up).

When display is on, power event manager restore audio focus and air plane mode.

this listener doesn't work if table going to sleep by power event.

So looks like some your app waking up tablet.

I've removed ADB from tools. It should be installed on your PC and added to PATH.

I've done this to prevent using out dated ADB, as this cause some issues in patch process.
[Nexus 7 Android Development] GrandeParade:
Nice!

Could you add a feature where you also set your standby image? The user selects the image and your app places it where it should be and set the correct permissions?
[Nexus 7 Android Development] _crue_:
I don't think this is major feature (as this is one time action) :) If I do more updates/fixes I will include this functionality.
[Nexus 7 Android Development] ZenInsight:
How is the battery life? Any recommendation for the kernel for best battery AND performance when I need it?
[Nexus 7 Android Development] redeyedjedi:
You should be getting six full hours screen on time..... At stock CPU, and 446 GPU, I'm getting consistently 6 hours and five minutes on smooth room AND purity ROM. On cm11 I get about 5 hour 45 minutes.

I don't know how that stacks up to other kernels, but I'm happy with it.

Can someone recommend a picture hosting website, I've got good screenshots showing stats I need to put in OP...... Also, I'mstill hoping someone can confirm the functionality of the new rt2832 driver for r820t.

Did you ever get any channels in your scan crue?
[Nexus 7 Android Development] _crue_:
use webpicessa :) there simple :) but nice scaling

not yet, I will try it somewhere outdoor, but I have no time yet
[Nexus 7 Android Development] Mugga:
Thx for the updated version. Tasker plugin is working again.

The strange thing is, that the kernel seems to ignore the settings I do with PowerEventMgr. I disabled Firm Sleep, but the tablet is going in standby on power loss. I did kind of a workaround which seems to work most of the time. When I let the "Skip countdown screen" option turned off, and I remove the power, the countdown screen pops up, but getting closed by I think tasker "taskkill".

After killing all apps I let tasker wait 5 seconds and then send a sleep command to PowerEventMgr. This way I make sure all tasks are done and the tablet doesn't wake up.

Regarding DAC-Patcher:

Thx I got it now. But the strange thing is after patching I can't change the volume (I got 45 levels).
[Nexus 7 Android Development] redeyedjedi:
There is 2 parts....the patch and the audio policy file ive uploaded.

I promise I will get OP updated....just no time at the moment.

Let me get you a dl link.

Here ya go...... post #388 in this thread.

Weve figured a lot of things out in the past few days.......ill try my best to organize the OP to cover it all but I think at this point we have dac on boot, dac hotplug, volume control (thanks crue/netfluke), easycap support for all jellybean roms and cm11,

Full firm sleep control thanks to crue, support for r820t dvbt sticks, and prolly more im forgetting. Im still working on carcam/easycap support for stock kitkat/purity.....and live ota tv (atsc) for U.S.

And still going over netflukes code for fixing sleep while charging with a regular cable......

Thanks to everyone for your help and feedback.
[Nexus 7 Android Development] Mugga:
No problem, take it easy.

Already found that file, replaced, checked permissions, rebooted, but no volume change.
[Nexus 7 Android Development] _crue_:
you hvae to disable no a Firm Sleep but fixed_install_mode

firm sleep - responsible only how the tablet going to sleep

fixed_install_mode - responsible for when it going to sleep

if device was unpowered in fixed_install_mode then Power Event manager will put it in sleep.

if you disable fixed_install_mode you could power/unpower table as much as you want and Power Event manager will do nothing.
[Nexus 7 Android Development] Mugga:
Ah ok. So this is the other way around than in timurs rom. Because in timurs rom "fixed installation mode" just makes sure that connected devices are not getting powered by the tablet battery.

So when I get it right, "firm sleep" with this kernel just makes sure that the tablet is going into deep sleep and is waking up when there is external power. Right?
[Nexus 7 Android Development] _crue_:
yes, firm sleep doing it.

fixed installation mode - works the same :) as in Timurs rom, but Power Event Mgr also using it to check does it need to put table in sleep or not on power loos.
[Nexus 7 Android Development] redeyedjedi:
No it works as it should...... fixed install mode controls dac on boot, enables/disables firm sleep, and only powers otg with external cable. If fixed install mode is disabled....then firm sleep setting is ignored. In other words the firm sleep switch turns firm sleep on and off......but it is completely disabled if fixed install mode is off. I think your power manager respects that setting....because as you said, If fixed install mode is disabled then pwreventmanager does not put tablet to sleep on power loss. I believe it functions correctly, but the tasker functions I havent tested.
[Nexus 7 Android Development] NoXXX:
Got another trouble.

USB sticks are not working with 4.4.2 patched stock + Kang-aroo V2 kernel :crying:

Just no reaction on USB stick insert. I tried 4Gb FAT32 stick and 1GB FAT32 stick with no luck.
[Nexus 7 Android Development] redeyedjedi:
http://d-h.st/Bsj

Flash that.......

Or..... You can flash mkernel, then reflash mine on top of it.....that would give you his ramdisk which has otg support. Either should work.
[Nexus 7 Android Development] NoXXX:
oh, thank you, i'll try the first, if it wouldn't work I try mkernel.

also, there's CM in the name of the vold archive. would it work on stock rom?