yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] rans0m00:
USB-rom just didn't run very well on my n7. It ran passable but far from well. When it ran right then everything worked passable... but I would say about 1/8 of the time something would go wrong when waking the device... which is totally unacceptable in a truly fixed installation as my car is... a simple power off and on of the car usually fixed it but slight hassle. I got around this by adding a switch inline to the entire setup and just used the switch to avoid the starting and stopping of my car. This could be due to the version of android it was based on or whatever but when I upgraded from usb-rom to redeyes it was like a breathe of fresh air into my n7. I use it as my daily driver and enjoy the experience.

Coming from USB-rom to redeyes rom I am very content with the way he is heading. Only thing I do miss is having the volume and track controls always in the same spot on the screen. For my uses once he has the stopping of anything waking the device when it loses power implemented then I am content... until the next big step in android os that is :P Oh and if the power management was implemented more into the rom like in the settings it would be nice for new people that dont crawl the thread for the power management apk. I don't use any cameras or anything... so pretty standard install.

Giving credit where I feel it is due with Timur... awesome rom for the time it was released but time for an update. If my 2013 N7 would have fit in my car I would be using his stuff for sure.

Keep up the good work redeyejedi and I appreciate the work you do. One day I might try to get into this stuff as a hobby but till then I am leaching off people like you to keep my android devices running better than they should.
[Nexus 7 Android Development] khahn:
Hello, I,m trying to setup a fixed installation with USB ethernet connection.

I'm using your Kernel in combination with slimkat.

Everything seems to work fine and I can access the network.

But when I disconnect the pad from USB and reconnect again it doesn't connect anymore.

When I check with Netcfg the interface eth0 is up but it gets no IP address and DNS.

After setting these with ifconfig everything works again.

I have found no 4.4.2 room where I can find the menu for ethernet settings either.

Any ideas to fix this?

Klaus

Gesendet von meinem Nexus 10 mit Tapatalk
[Nexus 7 Android Development] redeyedjedi:
Ill put this on "the list" but it may be a rom function...or at least the action of reseting automatically when the device is unplugged and replugged. It is a good sign that it works to begin with, means the kernel/ramdisk/rom all have the essentials.

the menu you are talking about, was this present on JB roms? there is a lot of ipv6 updates for kitkat and the ethernet setup may need updating on the rom side of things. I will look into it, but if you do find a rom or kernel that doesnt have this problem, let me know.
[Nexus 7 Android Development] _crue_:
hi, when you will release kernel update?

with fix for plug power and probably other

I've got issues

sometimes especially after games when I put table in sleep (via button - not deep sleep - fixed install mode = 0)

tablet never returns back, only reboot.
[Nexus 7 Android Development] NoXXX:
I had such issue too but with FI turned on.

Отправлено с моего SM-N9005 через Tapatalk
[Nexus 7 Android Development] redeyedjedi:
too busy with rom. Im uploading an update for the rom now, and next I will test netflukes fix for power plugged in and deep sleep.

You are getting a SOD using the "sleep" button from your pwrmanager app? do you have a last kmesg when you reboot it? do you have the charger plugged in when this happens, or no charger plugged in when this happens? repeat the error and then post the last kmesg. Even better would be if you could connect to a PC with adb, and then get a logcat of whats going on when you make it crash. I will try to make mine crash too and see if I can get the reboot error and a log as well.
[Nexus 7 Android Development] _crue_:
no, its not a deep sleep, simple power button presing.

I don't hvae as after reboot all logs are cleared.

sometimes it's plugged sometimes not.
[Nexus 7 Android Development] redeyedjedi:
ok. connect it to your pc with adb. Then from pc terminal run "adb logcat"

while the logcat is running on the pc, put your tablet to sleep, and intentionally crash it, or repeat the error. then, when you reboot it, cut and paste all the output from there to a pastebin. dont need an account you can do it as a guest user.
[Nexus 7 Android Development] redeyedjedi:
At first glance it all starts with a failure to locate a /sys file for the cpu governor to scale the cpu. It seems to show that the first time you tried the screen came on, but the second time you tried, it didnt. Can you look and see what governor you are using? Do you have it set to turn the screen on when power is removed with screen off? What kind of cable are you using to charge when this happens, normal usb or otg y cable?

And, it might sound wierd, but does it matter if you were using youtube or not when it crashes like this? I thought I saw some errors there too.

And, lastly, bluetooth....does it still crash if bluetooth turned off?

You are using pure stock 4.4.2? Or some other rom?
[Nexus 7 Android Development] _crue_:
Y otg

stock govenor

Do you have it set to turn the screen on when power is removed with screen off? I dont know where to set this? so nothing did change

eveything stock :)

no matter on bluetooth or of.

youtoobe is not started it's a service
[Nexus 7 Android Development] redeyedjedi:
they both have the wifi modules.....the other just has extra. wifi should be working, I tested with two different 4.4 roms.....what rom are you using? do you have left over scripts from other kernels in init.d? DAC hotplug wont work unless you also mod the rom.
[Nexus 7 Android Development] _crue_:
stock kitkat, no script (yesterday I've reverted all to stock full cleanup, all partitions, no backup :) like if it virgin from the box)
[Nexus 7 Android Development] redeyedjedi:
sorry.....I had no such issues with my tests against stock rooted, or purity rom. ill go back and look at my uploads to make sure its all right.
[Nexus 7 Android Development] _crue_:
thank you, don't be sorry :good: good job

greate kernel

I like the way how OTG works :) even better than Timur's :angel:

is this a feature:

1. if I have powered OTG (with connected devices) so if I lost a power devices also will lost power also (OTG disabled)

but if device is powered and I connect new usb device - it doesn't work (until I'll do a re-plug of OTG)

2. if I have no power (just OTG) all devices work as usual (pluging/unplugin)

can you confirm this or comment how it works :cyclops:
[Nexus 7 Android Development] redeyedjedi:
The way it is supposed to work, is using his pwrevntmngr.apk. It was released individually and you can still download it from his site. It will active "firm sleep" "airplane mode" and pull audio focus from all other apps. then, reverses it when power returns. then, you also flash the modded Apollo I linked in my OP. it also has a modded media scanner, which doesn't remount/rescan after deep sleep, so your drives will start working again. I didn't link the pwrevntmngr in my OP because there is no source code available, but it still functions the same. Also, you can go into init.d "usbcontrols" script, turn on fixed install, and lock usbdisk to keep them virtually mounted through deep sleep. so what you are seeing is not malfunction, but things still missing to do what you want to do. I redownloaded both kernels, WiFi works on both.
[Nexus 7 Android Development] _crue_:
external wi-fi or built-in? I dont have external :)

could I somehow check logs or something else to get know a reason why it fails?

pwrevntmngr.apk instalation failed on stock kitkat rom 4.4.2 :(

pkg: /data/local/tmp/PowerEventMgr.apk

Failure [INSTALL_FAILED_SHARED_USER_INCOMPATIBLE]
[Nexus 7 Android Development] redeyedjedi:
I'm talking about internal......I guess you need at least a rooted ROM, I don't know. there is some other reason you don't have WiFi, its not related to the kernel. maybe stock ROM won't execute init.d scripts i don't know, but it works without issue for me, its not the kernel. I haven't tried pwtevntmngr in 4.4, but it works fine in 4.3...... it needs to be flashed in recovery, or pushed to /system/app,, but maybe it won't work in 4.4. I made a kernel with his newest code, but I'm not trying to make a new usbrom. If you follow the instructions in the OP for the various mods, they are only tested and working with smoothrom 5..3, they should work in theory on others, but that's hours of time I don't have.

I need a dmesg to see what's going on, but with no WiFi, I don't think you can install terminal..... I will go and see if there are still more kernel updates for WiFi from 4.4.1 to 4.4.2 but I have all the same updates as mkernel, and Franco kernel. my 4.4 tests are with 4.4.1, but if there are more needed updates I will pull them in.
[Nexus 7 Android Development] _crue_:
this is log from Timur's log app (kernel tab)
[Nexus 7 Android Development] redeyedjedi:
OK, whatever ROM you are using, it doesn't have busybox installed. userinit is enabled but none of the scripts are executing because busybox isn't there. On a fully stock ROM, you are gonna need at least root and busybox. you probably don't have proper access to your otg without root either. the "complete Linux installer" or one of the "busybox" installers will do it, but you need root first. I'd suggest downloading a stock ROM already rooted. I was having trouble figuring your issue because I kindve assumed you at least had that.

you can flash a different kernel with inbuilt WiFi, add busybox,then reflash mine and it WILL work. my next release will see WiFi built back in,but this is how showp1984 made it, and I have been using a "ain't broke,don't fix it" approach. hope this helps.
[Nexus 7 Android Development] _crue_:
I have busybox installed? but :) not all tools instaled? could add in description minimum of require tools that should be installed via busybox.

as your kernel is big there is 0 free space :)
[Nexus 7 Android Development] andrew9292:
Sorry being MIA for a few days, been flashing n testing almost every possible combination out there.

Confirm WiFi now works well on Purity, great job! Stock should need to be rooted and needs busybox if i remember correctly.

Cant help the usb audio bit, purity n stock n other roms probably doesnt hav the framework yet. Been asking but no reply

For public info, the only curently working 4.4+ ROM with USB audio is CM11 with it's stock kernel combination only. The info at headfi forums is wrong and incomplete! Even so it's minimal support, no hotplugging and auto output switch, must connect b4 boot.

Flashing kangaroo kernel breaks usb audio, not sure what else it breaks. CM and their souped up stuff as usual. Performance much better on kangaroo as expected

Good news is, there is at least one 4.4+ rom that supports usb audio.

Hm... Might wanna get a 3G dongle to use with this kernel, this doesnt need rom side support right?

Also do share if there's another workable combination. Cheers. :)
[Nexus 7 Android Development] _crue_:
wifi finally ;) works - after busybox installation. thanks

but init.d still doesn't run (how could I check it?) I mean deep sleep functionality
[Nexus 7 Android Development] redeyedjedi:
init.d is workin or you wouldnt have wifi. deep sleep? if you mean, firm sleep, you need pwrevntmngr. If it wont work on 4.4, then you still have lp0 deep sleep, just not firm sleep. without source code I cant fix this. sorry.
[Nexus 7 Android Development] redeyedjedi:
wow......this sucks. I was thinkin that I saw jacknorris commits on cyanogenmod gerrit review.....as in the same code im using on smoothrom, which works but is still 4.3. Again.....dont know how the kernel can do this....usb audio=y. have you tried hotpluggin it after boot up. maybe go into init.d "usbcontrols" and turn on FixedInstall. Im sure you are right, I just wanna fix it. clearly, people are diggin on kitkat more than me. thanks for the feedback.....I will just keep tryin to make it better.
[Nexus 7 Android Development] _crue_:
by init.d I mean that values from 01usbcontrols do no aoolied on boot to /kernel/usbhost....
[Nexus 7 Android Development] redeyedjedi:
do you have root access? this isnt possible that one init.d script works but not the other.....unless you do not have root and rw access to /sysfs. 4.4.2 just wont give up with out a fight will it?
[Nexus 7 Android Development] _crue_:
sure I have :) wi-fi works good (re-installed busybox)

I dont know how to chek why it fails

should be there in log something?

also is there in log some messages if fast changing used?

....

1. #!/system/bin/sh on the start of the file - missed

2. looks like after executing files in kernel/usbhost got rewritten :( don't understand how
[Nexus 7 Android Development] redeyedjedi:
the default values are set by the kernel....the init script changes it at boottime........its supposed to change the values when executed. on reboot the are back to default until the script changes them back how the user sees fit..much better than releasing 15 different kernels based on all the possible settings.
[Nexus 7 Android Development] _crue_:
I dont understand why, but 01usecontrols doesn't executed :(

I've chnaged file names on kernel/usbhost/1usb..... no new files

init.rc has "service userinit busybox ...."

wifi works fine

what the reason?

filing stupid :) lol
[Nexus 7 Android Development] andrew9292:
Removed. Redundant. Solution next page.

[/COLOR]

Okay, will try that soon. Thanks for your help. Hmm, how did you made it work in smoothrom 4.3? :confused:

Im gonna full wipe, install smoothrom (comes with gapps right), install kangaroo, all before first boot.

Tried that last time n it didnt work out. M i missing something?

Also you got the patch to install on smoothroom? I got the 'couldnt find patch for 4.3.1' error.

Whats your secret? :cool:
[Nexus 7 Android Development] redeyedjedi:
OK, stock ROM and stock ramdisk is set for interactive governor i think, but the updated governors are ondemand and smartmax. Can you install trickstermod and set governor to ondemand and see if you still get the crash??? I think i can make a ramdisk to fix your issue, but i need to see your results of this test. It is time to update the kernel again, and i am working on it right now....so i absolutely need to fix this. Don't worry about that screen setting, its not in stock ROM. On demand is a waaay better governor, but i can maybe fix the interactive one. So, try on demand, and see if you still get crash. If you can post a logcat of that, it would help a lot too.
[Nexus 7 Android Development] Notn4:
will this thread be updated when a tilapia rom thread is created? looking forward to it! oh and is it possible to flash the grouper rom on my tilapia? I dont need the 3G connectivity at all so if thats the only drawback then im fine with grouper rom
[Nexus 7 Android Development] redeyedjedi:
There is a tilapia build done, and it all works, and there is a link in this thread..... I just havent gotten around to making a tilapia thread for it.

Search this thread and you will find it. Ill post the dl link if I can find it, but it was about two weeks ago.
[Nexus 7 Android Development] Notn4:
Yeah I found it, flashing now, do the latest GAPPS work?

EDIT: wheres the power manager? am I supposed to install it myself? can't find anything called crue's power manager
[Nexus 7 Android Development] redeyedjedi:
Use the gapps recommended in the purity thread. Search this thread to find posts by crue with the latest version of his pwrmanager. It is his app, hit his thanks button. I think i linked to it in the OP of the kangarom thread.
[Nexus 7 Android Development] _crue_:
last crash

all info you will find here

https://drive.google.com/file/d/0BwubLw4Vnq3aOEZiY21tQlQ4NnM/edit?usp=sharing
[Nexus 7 Android Development] redeyedjedi:
Ok, thanks. Ill see what I can find. Did it still crash with the ondemand governor?

To all users: is anyone else experiencing a sleep of death type behavior on a NON stock rom?
[Nexus 7 Android Development] vovaxxxx:
red! I found one idea that sounds too close for my prob...

http://karapuzz.blogspot.com/2009/12/blog-post.html

here one guy tries to connect in linux 2 devices: tvtuner and webcam and he describes the same conflict btw two devices...

but in his explanation I can't detect a udev string in our nexus... What do you think about that?

(use google translate)
[Nexus 7 Android Development] redeyedjedi:
Its been a couple of years since I messed with that camera.tegra.so lib...but I remember that it is set up to use two webcams, one for the "front" and one for the "rear" but it of course disables the stock camera. You cant use dev/video1 because that lib expects a webcam to be there.

If you have an extra webcam you can try, as I have never tested it on a nex7. If you put back the stock camera.tegra3.so, you can use the mod from my OP for a webcam, which should also allow for the easycap device to function. The w3bcam will have to be mounted in landscape like the tablet tho....I havent figured out how to manipulate this through software yet.
[Nexus 7 Android Development] vovaxxxx:
red, I'm sorry for my drilling, but I need your help :)

What I found...

First:

file video0 in /dev (/dev/video0) is created after connection ezycap or webcam (separately or together connected) if unglug there is no such file in /dev.

second:

dmesg command gives me (connected ezy and webcam):

stk 1160 2-1.1:1.0 v4l2 device registered as video0

and such line as

uvcvideo: found uvc 1.00 device hd webcam c525 (046d:0826)

input: webcam c525 as /devices/platform/tegra-ehci.0/usb2/2-1/2-1.3:1.2/input/input3

next...

I found that /etc/udev/ in android is absent but realised as file init.rc (probably)

as I understood form this post http://karapuzz.blogspot.com/2009/12/blog-post.html

ATTRS{idVendor}=="046d", ATTRS{idProduct}=="09a5", ATTR{name}=="UVC Camera (046d:09a5)", NAME="video2"

KERNEL=="video*", ATTRS{vendor}=="0x1131", ATTRS{device}=="0x7133", NAME="tuner"

I need to change created /dev/video* to video1 or video2 to my easycap which have idvendor=05e1, idproduct=0408

but in android there are another way of writing...

How can I type it in init.rc ?
[Nexus 7 Android Development] redeyedjedi:
ReRead my last post.....it wont work at all unless you put back the stock camera lib. The stock camera lib wont occupy video0 and video1 but that custom one does. It wont allow you to do what you wanna do.
[Nexus 7 Android Development] vovaxxxx:
>ReRead my last post.....it wont work at all unless you put back the stock camera lib. The stock camera lib wont occupy video0 and video1 but that >custom one does. It wont allow you to do what you wanna do.

ok... sorry for my misunderstanding.

but how to turn off front camera? I need to disable frontcam... cus automatically program connects to front cam to usbcam...

any solution? diassambling of nexus and plug off front cam? is it'll be useful?
[Nexus 7 Android Development] redeyedjedi:
flash this:

http://d-h.st/x5t

then, have webcam plugged in at boot, with power applied to your otg cable if you are using Fixed Install mode. It will be recognized as a builtin REAR camera.... so on the built in camera app or other play store camera apps, switching to the rear camera will actually switch to the webcam. the image will be off 90 degrees tho, unless you also rotate the webcam 90 degrees since the tablet is in landscape mode, the webcam must also be....because the tablet "thinks" its built in. then, your easycap should be at /dev/video1 and it should also work too.

the only way to disable the builtin cam and use only webcams requires the file you already flashed, and TWO webcams, for front and rear. In this scenario, the easycap will only work at /dev/video2 and after two webcams were plugged in.
[Nexus 7 Android Development] vovaxxxx:
ok... I understand.

now I don't have a second webcam probably I try later. After flashing N720webcam.zip any programs can't find a webcam. How can I revert to previous state? (how to erase N720webcam.zip ?)

And I stop my findings :)
[Nexus 7 Android Development] redeyedjedi:
you need to also copy the original "camera.tegra3.so" from the rom zip file and back into /system/lib/hw and reboot tablet.
[Nexus 7 Android Development] _crue_:
one more bugs :)

with using

fastboot oem off-mode-charge 0

if actually battery fully uncharged

device can not boot (or boot loop)
[Nexus 7 Android Development] jimmng:
[/COLOR]

dude honestly, and without disrespect,

this doesn't work properly. It works some of the time and it doesn't.

Also, it conflicts with tasker a lot of the time.

A lot of developers don't know about this hence they add it into their roms, thus leading many users to think that it would work.

The users then have to manually figure out what specific app or setting or system bug or kernel bug that is causing their audio dacs to be cut from power, or the screen not turning on, or the screen not turning off, or deepsleep sets still applied while screen's turned back on.

please, fix or at least state these issues and advise develops about issues before you release software.

alas; please take this as constructive criticism.

for people who have been using kangarom, usbrom, timurs kernel and many other car roms/kernels:

note that, powereventmgr does NOT reliably deepsleep your device. It totally messes up the devices' settings thus leading to loss of dac power, flight mode while screen on etc. Your Rom and Kernel are fine.[/QUOTE]
[Nexus 7 Android Development] _crue_:
tasker plug in used only for run application, there could not be conflicts.

if there is please give me an example.

please explaine step by step. I can not decompile that what you wrote, :) (English is not my native so please be patient)

it's true powereventmgr can not execute deepsleep

1. ROM sleep functionality accessible only for system applications.

2. deep sleep functionality handled only by kernel, so after powereventmgr putting table in sleep kernel could initiate deep sleep.

actually powereventmgr created for this, it turn on flight mode before sleep, and disable it after return.

it getting audio focus and return it back after wakr up

if you don't need all of this, you don't need powereventmgr at all.

or you thought that powereventmgr this is some kind or native based solution?

actually I've created (rewriter, refactored, rebuilede etc from Timur's powereventmgr) powereventmgr only for my self (as and other my apps)

and just share it here if someone will find it suitable for using.
[Nexus 7 Android Development] redeyedjedi:
[/QUOTE]

In my tests on jellybean ROMs and kitkat ROMs.....it does function properly, in the same manner as Timur's version. It grabs audio focus using the code from bobd, the same way Timur used bobds code. It DOES turn on airplane mode in screen off and it DOES turn it off with screen on. IF fixed install mode is on, it also activates firm sleep.

Two things to note...1. Crue's app does NOT implement firm sleep, the kernel does

2. Crues app only turns firm sleep on and off, but it is completely disabled if fixed install mode is off.

There are KERNEL level wakelocks that could be present, but it blocks all ROM level wakelocks.

If you don't use fixed install mode, then in kangarom I added a wakelock blocker so you can still force your tablet to sleep.

You can also use Timur's version of pwrevntmngr, it works too. Just pull it from usbrom and push it to /system/app. I don't know about the tasker function, but for me all other functions of crue's version seem to work as intended. Fixed install mode must be ON though.

To crue: i will have a test kernel for you in a day or two. I hope crash issue is fixed.