yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] redeyedjedi:
There are 6 or 7 grouper roms based on cm11, and zeljkos has dac mods, just not dac on boot. I wanted to use omnirom because multiwindow is so useful, but my omnirom builds dont even boot. So I used my favorite kitkat so far, purity. Eventually ill patch in multiwindow and an aospbased rom will make this easier.

The device trees for tilapia are kind of trivial, I just need time to make sure its right.

I used to have to fiddle with my viewsonic gtab trees for hours because it was never even an official google device, and was never updated past froyo......while we were hacking together asus transformer proprietary blobs and doing a mix and match until it booted.

Setting up tilapia for purity rom with a known good device tree should be nothing.......im just cautious because I dont own a nex7 3g to test.

Its happening tho...
[Nexus 7 Android Development] Vilen77:
I have an issue when I'm trying to use purity rom with the easycap device. The /dev/videoX device has 660 permission for CM and purity roms. I'm using Carcam for easycap camera and it works flawlessly in CM but not in purity or stock. After modifying manually the permissions to 666 the carcam works well (until unplug/plug easycap). I installed CM10,1 USBROM and modules from pccar.ru and saw the /dev/videoX has by default permissions 666. Also saw some posts about modification in uventd.grouper.rc to set the right permission for the devices. Could you also take a look on this please?
[Nexus 7 Android Development] redeyedjedi:
I actually just got done using my easycap device on my purity build after realizing the same thing. Tested my USB webcam and its working too. Yes, this needs to be fixed, and will be. Good news is that we can get easycap devices and USB webcams on any kitkat ROM now.........cant believe it was so simple, although im thinking in jellybean it was only 0660 and that was enough.

Either way, a simple terminal command for now will do it:

su

chmod 0666 /dev/video0

EDIT: tilapia rom still not building, so device trees still need tweaking. I did find the "missing" board files, in the grouper folder of course..... Too many foolish mistakes from doing too much at once. I hope a fresh look tomorrow will resolve this issue as well
[Nexus 7 Android Development] ZenInsight:
Can you release Grouper first and Tilapia later? Is this kernel only for CM11 or works with stock rooted as well?
[Nexus 7 Android Development] redeyedjedi:
Should work on any kitkat or jb ROM......just wont flash in twrp 2.6.3.1

Grouper release is done..... "kangarom"

http://xdaforums.com/showthread.php?t=2660803
[Nexus 7 Android Development] ZenInsight:
So, it has to be sideloaded or loaded through CWM. Correct?

Edit: Someone mentioned to me that 484 is the most OC the GPU can actually benefit from? Anyone testing benchmarks agree or disagree? My stock ROM is a sluggish crapfest. Sorry for my bad language.
[Nexus 7 Android Development] Kuchar09:
You the man!!! I'm gunna test this in the next few days so hopefully I can finally get my car install back together.
[Nexus 7 Android Development] redeyedjedi:
No, just use twrp 2.6.3.0, not the newest one. The newest twrp wont flash smoothrom and LOTS of other grouper ROMs, kernels. It is a problem with twrp. I have never used cwm so i don't know.

I have no opinion about GPU OC, except that i run it at 446, have no lag ever, and get a little over six hours screen time..purity ROM.
[Nexus 7 Android Development] NoXXX:
How long will it take to bake tilapia build? Days/weeks/years? ;)

Отправлено с моего SM-N9005 через Tapatalk
[Nexus 7 Android Development] redeyedjedi:
Well, as soon as I figure out this error:

target thumb C++: keystore.grouper <= vendor/nvidia/tilapia/keymaster/keymaster_grouper.cpp

target thumb C: libSR_AudioIn <= external/srec/audio/AudioIn/UNIX/src/filter.c

target StaticLib: libESR_Portable (/home/redeyedjedi/android/pure/out/target/product/tilapia/obj/STATIC_LIBRARIES/libESR_Portable_intermediates/libESR_Portable.a)

In file included from vendor/nvidia/tilapia/keymaster/keymaster_grouper.cpp:39:0:

libnativehelper/include/nativehelper/UniquePtr.h:20:38: fatal error: algorithm: No such file or directory

compilation terminated.

make: *** [/home/redeyedjedi/android/pure/out/target/product/tilapia/obj/SHARED_LIBRARIES/keystore.grouper_intermediates/keymaster_grouper.o] Error 1

make: *** Waiting for unfinished jobs....

It seems the same file is used for grouper and it works just fine, but this pops up on the tilapia build, and I need to figure what is different in the makefiles that is causing this, as it is not related to the file it refers to......this same file I have used for about 7 grouper builds now.
[Nexus 7 Android Development] _crue_:
#include <algorithm>

somewhere in keymaster_grouper.cpp:39:0:

called http://www.cplusplus.com/reference/algorithm/

for file that doesn't exist
[Nexus 7 Android Development] redeyedjedi:
found it.....kitkat uses new file, thanks rascarlo!!!!!!

https://github.com/rascarlo/android_vendor_asus/commit/07a7733001a5ec6a2d0d6222697c21038765ec84

tilapia is now building.... no really, it is.
[Nexus 7 Android Development] redeyedjedi:
I need a tilapia volunteer or two for testing......any guinea pigs?
[Nexus 7 Android Development] tjl_48:
How do you get your easycap to work? I've been reading through all the threads I can't find what I need. I'm running this kernel and kangarom. What else's is needed?
[Nexus 7 Android Development] Vilen77:
It is needed to add the script below in your /system/etc/init.d directory and set the permissions to 777. After restarting you should be able to see the videoX device in your /dev directory.
[Nexus 7 Android Development] redeyedjedi:
Also, as a temporary fix you need to enter in terminal:

su

chmod 0666 dev/video0

I will get this fixed once I get tilapia working.
[Nexus 7 Android Development] Old Guy:
I have the kernel installed with a rooted KitKat rom.If I try too boot up with an OTG y cable and the charger connected it will go into a bootloop. If I unplug the power it will boot up fine. Also tried OmniRom and the same thing happened.

I was wondering if anyone else has experienced this behavior or is it just me. Once booted up all of the features in Power Event Manager and everything else seem to work fine.
[Nexus 7 Android Development] redeyedjedi:
Definitely should not have this happen.... id try a different cable.
[Nexus 7 Android Development] NoXXX:
I will test it today and report

Отправлено с моего SM-N9005 через Tapatalk
[Nexus 7 Android Development] Old Guy:
I messed with this a little this morning. Tried a couple of different OTG cables and adaptors.

If I have just the OTG cable plugged in it will boot up fine. If I have any kind of usb device connected to the cable, or use a y cable with the charger connected and a usb device either plugged or unplugged I get a bootloop.

I am using multirom and multirom manager. Maybe this is what is causing the problem.

Not really a big problem. But if someone was using this in a fixed car installation, it would.
[Nexus 7 Android Development] redeyedjedi:
Thats what I mean, no one should be experiencing this....I certainly dont. If its not the cable then maybe its the amount of power applied. Im just guessing, but that is not normal behavior. There are many people confirming dac on boot working....although storage drives arent automounting for everyone on boot, I havent heard of anyone else having such bootloops. Im almost certain its not the kernel.....maybe its the rom, or ramdisk.
[Nexus 7 Android Development] tjl_48:
I believe I am missing something. I did this but didn't get VideoX in my dev directory. I ran the script manually and it gives me an error saying file exists. So I think it is running on boot but I am not getting the Video folder.
[Nexus 7 Android Development] redeyedjedi:
Dev/video0 shows up after you plug the device in. Also, do you have the full version with all the modules? Another problem is that some gapps fillup all 650mb of /system, and then not all the modules are installed cause of no more room. Check /system/lib/modules and see if the modules are in there.
[Nexus 7 Android Development] j41224:
redeyedjedi

Is there anyway you could post just a flash for the ezcap portion of your kernel. I have tried your rom and also your kernel on zeljko1234 cm11 rom but I would like to add just the ezcap on top of his rom and see how it functions. Both are great roms I just have minor random things that happen with both and I would like to try this route. I have tried putting in your script and placing all of the files in \system\lib\modules but apparently there's more to it than that. I would be using his latest usb dac rom, netfluke v5 otg kernel, and hopefully your ezcap drivers. Any help would be greatly appreciated.
[Nexus 7 Android Development] redeyedjedi:
This is not that simple. The modules are built with kernel source, and will only work for that kernel.

But.......

The GPL is your friend and Im its biggest fan. Just tell zeljko or netfluke to look in my github and kang the source for the drivers. Then, they can build them against "their" source and the drivers will work. I do believe that netfluke's kernel would be better with a cm11 rom, because it is a pure cm11 kernel, with the dac otg stuff added. Of course if he needs any assistance ill be glad to help.
[Nexus 7 Android Development] j41224:
Thank you. I copied our posts to his rom thread and I'll see if they can help me from there.
[Nexus 7 Android Development] redeyedjedi:
Well, if you get a chance, id like to know about any issues you were having, so I can fix them.
[Nexus 7 Android Development] alpkopat:
thanks for the kernel but i have got a problem with my easycap. when i directly connect my easycap to otg usb y cable it works. but when i connect my externally powered usb hub its not receiving video. what am i doing wrong?
[Nexus 7 Android Development] redeyedjedi:
If you do it without reboot, it may be at dev/video1...... Otherwise, its not enough power from the hub.
[Nexus 7 Android Development] alpkopat:
thanks for the reply redeyedjedi, our car project becomes true with you:laugh:

easycap connects on the usb hub and /dev/video0 file still there but image not getting recivied by the nexus. usb hub has got own power so it must get enough power. i cant figure out problem...

im going to try find a supported usb webcam to my backup camera...

thanks again...
[Nexus 7 Android Development] redeyedjedi:
Here is a good tilapia rom..... I will make a thread when I have time.

It is a build of purity rom with support added for dac on boot, dac hotplug, volume control, automount of drives including ntfs, exfat and read/write.

Use crue's latest pwrmngr for firm sleep, dac on boot with fixed install mode.

http://d-h.st/q6j
[Nexus 7 Android Development] redeyedjedi:
What needs to happen is I need to fix the permission problem permanently. When you replug the device you have to re enter the commands in terminal

Su

Chmod 0666 dev/video0

I will try by this weekend to get this taken care of so easycaps will just be plug and play for all kitkat roms.

Im not going to do dvbt like this tho, because of the userspace driver for radio. Instead I will make "load" and "unload" scripts to easily switch from tv and radio apps.
[Nexus 7 Android Development] chaostrodamis:
F2FS (Flash-Friendly File System)

Any plans on making a F2FS (Flash-Friendly File System) version of this great kernel. The whole system is so much more snappy while doing anything, especially multitasking. but i miss all the great feature this kernel gives. im Running lego kernel (only supported kernel for now, i think) for the time being to test the new file format. i want to continue using this file format but i think i might have to go back to the old one because i love how this kernel rocks.
[Nexus 7 Android Development] zenchowdah:
I've followed the link, but the level of technical expertise required to understand these guys goes significantly above my own. can anyone help me with a step by step?
[Nexus 7 Android Development] _crue_:
http://xdaforums.com/showpost.php?p=50189076&postcount=363
[Nexus 7 Android Development] zenchowdah:
Thanks for the link. This throws errors. i assume it looks for an ADB connection to a device, checks its android version, and patches as appropriate?

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

usb-audio-patcher 1.2

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

adb: Waiting for device.

Unhandled Exception: System.ComponentModel.Win32Exception: The system cannot fin

d the file specified

at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startIn

fo)

at android_framework_patcher.AdbHelper.RunAdbCommand(String command)

at usb_audio_patcher.Program.ApplyPatch()

at usb_audio_patcher.Program.DisplayMainMenu()

at usb_audio_patcher.Program.Main(String[] args)
[Nexus 7 Android Development] redeyedjedi:
Well, I've been thinking about it, and also I've already added CFS bandwidth to the exp. branch. Im waiting to see Sgt. Meow's results since he added it in his experimental branch.

In trying to push things that are daily-driveable, which slows the process, but makes it better, so i guess we will see.
[Nexus 7 Android Development] _crue_:
install adb (from google android sdk manager)

add path to it to system path
[Nexus 7 Android Development] zenchowdah:
Yep, i'm a moron. Thanks dude. now the question is, how do i force a media player to acknowledge my dac?
[Nexus 7 Android Development] _crue_:
after patching all sound will be played though dac (if plugged)
[Nexus 7 Android Development] zenchowdah:
maybe my patch didnt take, then. my nexus 7 still plays through the speaker on the back instead of through my aune T1.
[Nexus 7 Android Development] _crue_:
how much volume lvels? after patcing should 44 instead of stock 11
[Nexus 7 Android Development] zenchowdah:
44 levels.

Testing setup: http://imgur.com/W3ufEjR

EDIT: this is interesting. after a few reboots, plugging the DAC in while the device was off, or plugging it in, then rebooting, i've managed to get no audio at all.
[Nexus 7 Android Development] _crue_:
then it patched.

ask [MENTION=4035939]redeyedjedi[/MENTION], maybe kernel doesn't support your DAC.

could you check logs? on DAC connected there sould be some info about
[Nexus 7 Android Development] zenchowdah:
How do I check the logs?

http://imgur.com/npYWy7R

http://imgur.com/5xVOA3Z

http://imgur.com/VUsoZWC

These came from USB host controller
[Nexus 7 Android Development] _crue_:
orf CM there is another patch file
[Nexus 7 Android Development] zenchowdah:
I used the cm11 rar listed a few pages back. I copied the contents of that into the folder the audio patcher, which I renamed 4.4.2
[Nexus 7 Android Development] redeyedjedi:
There is a different patcher i think, cant just swap files like that. One patcher does services.jar and the other does services.jar AND frameworks.jar, this is what you need.
[Nexus 7 Android Development] zenchowdah:
Where can i find this?
[Nexus 7 Android Development] physwizz:
great kernel

Thanks for your great work on this kernel. I got otg charging to work on smoothrom (internal) but it wouldn't get past the "starting apps" screen on smoothrom (external) or omnirom (internal).

Are there any plans to support external roms? I would reall like to recharge without having to shut down an external rom.

Thanks again for the great kernel.
[Nexus 7 Android Development] _crue_:
on a few pages before.

but remember patching should be done only on stock files, do not patch already patched system.

you could find original files in "/data/afp-tpm"
[Nexus 7 Android Development] zenchowdah:
So step one is restore files from afp-tpm, and then step two is patch new files with new patcher. Heading to work now so I'll let you know if I have any success this evening.
[Nexus 7 Android Development] redeyedjedi:
Hmmmm.........

I've tested many, many ROMs internal and external and I've had no such problem. I've booted the following as secondary ROMs:

Carbon, slim, PA beta, purity, omnirom. In not sure if I've had smoothrom as external tho.......regardless, the full kexec patch is there. Im on multirom v18, haven't needed to upgrade since so I cant speak for newer versions. If you are talking about from a USB stick, then i guess I've never tried that at all.

I'd like to see a dmesg/logcat, or last kmesg and see whats going on. Is anyone else have the same experience???

EDIT: make sure you are not trying to boot a JB ROM with a kitkat ramdisk, or a kitkat ROM with a JB ramdisk, this is the only thing ive done where I've had a ROM not finish booting like that, but its a guess.
[Nexus 7 Android Development] redeyedjedi:
No,no need. Just don't use the zeljko cm11, its already modded. Start with the official cm11. What he means by unpatched files is to use files with no DAC code already there, like a stock rom would be.
[Nexus 7 Android Development] physwizz:
Yes. When I said external I meant on a usb stick.

The omnirom that didn't work was a custom jb rom from chaoszx with splitview.

my multirom is 22a.

I wouldnt know how to get the logs?
[Nexus 7 Android Development] redeyedjedi:
Yea.....it'd be hard to pull logs without adb, but if it was enabled on that ROM by default, then you could open a terminal in windows, and with tablet connected via USB, when the boot process begins type:

Adb logcat

And when boot process gets stuck, you will see the output either stop, or you will start seeing the same code pop up over and over, a "bootloop"

With that said, the fullkexec patch is there, and well beyond my knowledge. So, if you can get a logcat and pastebin it, then you should seek help in the multirom thread. I've never even tried to use a ROM from a USB drive, so i doubt i can help you. I will re check and see if the patch has been updated.
[Nexus 7 Android Development] zenchowdah:
okay, im starting with cm-11-20140212-SNAPSHOT-M3-grouper.zip. after i install that, i will install GAPPS, and then the kernel from this thread. i'd like to do V3. any reason i should not?

after that, i'll run the patch, and see what happens.
[Nexus 7 Android Development] physwizz:
Thanks. I'll try that.
[Nexus 7 Android Development] redeyedjedi:
Should be fine.
[Nexus 7 Android Development] zenchowdah:
for reasons i cannot fathom, it isnt cooperating. ive seen everyone reporting success with purity rom, so i'll try that.

should i use the vanilla usb-audio-patcher? how was the cm11 set intended to be used?

---------- Post added at 11:19 PM ---------- Previous post was at 10:25 PM ----------

and this causes bootloop, with "com.android.phone stopped working" error. apparently i have no idea what i'm doing.
[Nexus 7 Android Development] redeyedjedi:
No, this patch process is very specific...ive had my fair share of issues too. At this point, you can download my kangarom build, which is purity with all this dac stuff already in it. Or you can try the zeljko cm11, but it doesnt support dac on boot, only difference. I am also workin on update for tethering, permanent ezcap fix, webcam support, other things which will be ready soon.

Also, can anyone show me the gerrit/github patch/commit from cm11 for cifs?
[Nexus 7 Android Development] zenchowdah:
Downloading. My N7 is becoming quite the slut. Could you humor me and give me a step by step?

EDIT: disregard previous request. it's working. do you have a donate link? i want to buy you and crue some beers.
[Nexus 7 Android Development] redeyedjedi:
Good to hear its working. No donate button for me....just a thanks is nice.
[Nexus 7 Android Development] lazynok:
Newbie question here. How come I cannot install the power Event Mgr? It says it cannot parse the package. It installs just fine on my note 3. But not my nexus 7 (I'm using USB rom, and I Uninstalled the regular power Event manager.)

Are you sure we cannot donate? I don't want you to just give up like Timur! ;D
[Nexus 7 Android Development] redeyedjedi:
Crues pwrevntmgr is installed as a user app, not a system app. It may not work on android 4.2 because the api he uses to build it is for 4.3 or higher.

I do this for fun, and there isnt that much "original" code by me, just some backporting of drivers and makin it work with kitkat etc. Most of it, hence the name, is other peoples work.

I have also kangarom, which is a kitkat rom with all the dac stuff, and it will soon be updated with lots of more useful stuff.....like wakelock blocker.
[Nexus 7 Android Development] lazynok:
Oh yeah I forgot this was kitkat. When I have more time I'll update to the whole room. Hopefilly itll be done in a few weeks when I have time ;D I'll check back, thank you (weird that it installed on my jelly been Note 3 though!)
[Nexus 7 Android Development] MetalMan2:
I feel this is worth addressing here: what makes you think Timur "gave up"? He didn't... he advanced the Nexus 7 fixed install way beyond any other developer (but of course he was able to implement some work from other developers too).

He "ended" his development because he felt his goal was completed. I mean, there will always be new versions of Android coming out, new changes that need to be tended to, etc. I personally feel he completed a nice ROM for fixed car installs which works wonderfully. Yeah it's

only

4.2.2 but otherwise still works great.
[Nexus 7 Android Development] Mugga:
Oh, much happend here.

I got a tilapia Nexus. Anything special I should test, or other things to keep in mind? Is this the latest rom version: http://d-h.st/q6j?
[Nexus 7 Android Development] lazynok:
Sorry to offend you. How about I just say he quit development? I was just looking for a way to help out this project
[Nexus 7 Android Development] MetalMan2:
You're welcome to call it what you want, I was merely trying to defend Timur and the work he accomplished.
[Nexus 7 Android Development] lazynok:
His work is great. I use his work. I just felt it felt unfinished. And judging by the "not enough funds raised for nexus 7 2013 room," I feel he quit. And I don't want the same to happen to another "fixed installation" rom.

Viva Timur ;D
[Nexus 7 Android Development] MetalMan2:
If I may ask, what more would you have wanted to make it more complete / less unfinished? This information could potentially be useful for [MENTION=4035939]redeyedjedi[/MENTION]

This stuff definitely takes a lot of time. I don't know that Timur was much into Android development prior to Timur's Kernel / USBROM, so that may have been the only Android project he invested into (unlike some other devs here, who have their feet in multiple ROM/kernel projects).

With the amount of time he spent on it, he probably set a minimum threshold of money to make N7 2013 development "worthwhile". Makes sense to me!

BUT!! He has been working on N7 2013 kernel/ROM, so if he "quit" then now he has reversed that.
[Nexus 7 Android Development] redeyedjedi:
Yea...... im tryin right now to get an update for ezcap devices to just work.....and wakelock blocker. That build will be better, but this one works fine, I just havent done a thread yet. This build is fine, and the update might be just dirty flash...... just too busy b3cause of tax season so it may be couple more days.

I also think timur did great work, as well as jacknorris (usb audio master), the cm guys, linus torvalds, etc. No rom or kernel is just one guy. And, being linux based, the kernel is GPL, the only reason i mess with android. I just think the GPL should be respected. Some people (like me) can get in trouble for ignoring such things. I angered timur when I said I cant donate unless he would comply, and he was just repeating he wanted more donations, illegal.

The GPL is what protects you from messing up ur device with unknown code. So, as long as I can stay GPL, I will do updates. Im sure it came out wrong when I asked him about it, since I have zero communication skills...but either way, I do add original stuff, and am working on more original stuff. But, I have community sharing ambitions, not personal. I love that purity rom is the same, so Im workin off it as a base. You will always be able to see the code before you flash it.