yashsingh1/xdaforums huggingface dataset:
[Ouya Android Development] TwitchyEye:
I came up with a hardware fix for my issue. I was inspired by a guy somewhere on the ouya forums. Basically I took a wifi antenna and it's little snap on connector out of an old laptop and attached it to my ouya. When I tested it at my shop I saw no difference but when I got it home and set it up where I had issues before I do see a pretty drastic improvement where I was getting like 300-800kbps I now get 12mbps. As far as Bluetooth, I only get controller lag out of the ouya controller if I also have a ps3 controller paired, and it is also present in the ps3 controller but not as bad.
[Ouya Android Development] IncognitoMan:
Since you are on ddwrt could you try enabling Bluetooth coexistence mode? I haven't gotten around to checking if that helps since I don't get much time on the ouya but it *may* help out. Also if you are not using Bluetooth on the ouya try turning it completely off in settings.
[Ouya Android Development] HT123:
I don't remember seeing it as i am running a mini build due to the size of the storage on the wndr3300 but if it is there i can turn it on. I will try to disable Bluetooth altogether as well and let you know what happens.

Do you know how to re-enable it via adb?

---------- Post added at 09:15 PM ---------- Previous post was at 08:26 PM ----------

Bluetooth Coexistence Mode made no difference. I will install a bluetooth toggle later tonight and i will give that a try.
[Ouya Android Development] HT123:
I turned the other router on and was getting an excellent signal to the ouya and still was only getting about 1 down but still getting 2.5 to 3 up so i don't think it is a signal issue. Something else is going on. I saw CM 10 for the HP Touchpad do something similar early on but it was resolved in one of the night updates. The Ouya and my phone running 2.3 are the only android devices in the house. The 2.3 phone never has an issue with wifi and speedtest give me at least 5 down consistently.
[Ouya Android Development] Oscar_david:
Tried several already. Frodo was working just fine prior to updating the rom. So was Netflix and YouTube. Now they're all broken.

---------- Post added at 04:51 AM ---------- Previous post was at 04:47 AM ----------

I'm on ethernet not Wifi. I guess I'll try Wifi see what happens.

edit: well that was weird. just booted up and the issue seems to have fixed itself.

all's well that ends well i guess.

cheers. and thanks for the responses.
[Ouya Android Development] TadeoNYC:
Native Init.d is not working. I spent the better part of the night and early morning trying to use a script to mount my ext4 partition before I finally installed universal init.d. The test says no support in Rom, and now with it installed everything linked right up
[Ouya Android Development] IncognitoMan:
Okay... lets say that what you are saying is true and init.d is not working.

Then my net_patch in init.d also wouldn't work... correct? Lets find out.

The net_patch is a cheap script really that just writes the value over to min_free_kbytes ( I did this because I didn't know if there would be problems later down the road with this but since no ones really complained maybe I can just add this in by default. )

The script is simple

#!/system/bin/sh
echo 16384 > /proc/sys/vm/min_free_kbytes

Now, if Init.d doesn't actually work the result in min_free_kbytes will be something like 3182. So lets cat /proc/sys/vm/min_free_kbytes

shell@android:/ $ cat /proc/sys/vm/min_free_kbytes
16384

The result is 16384.

I'm guessing what people are having a problem understanding is how to copy over init.d scripts. By default I do not allow RW access to system which also means I do not allow RW to init.d ( I've seen what people do so I figure its best that anyone who wants init.d scripts running knows how to use it ) and thus things that see if init.d works will report back that it doesn't ( when it does )

Simply put if you want to use your init.d script you just need to mount system rw

adb shell
su
mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP

And then copy your init.d script to /etc/init.d/

Once copied over, chmod 777 the script and reboot the OUYA.

If you don't want to go through making system rw again you could make a script that automatically mounts system as rw but I'll leave that up to the user end to decide.
[Ouya Android Development] TadeoNYC:
Alright, I'll walk you through the basic steps I took.

I downloaded the zip from Natorus87 http://xdaforums.com/showthread.php?p=43137447 then using ES File Explorer I made system RW and unzipped the file to where it goes. Then it didn't mount the drive on boot, so I disconnected all other devices repeatedly mounted it again in terminal shell, opened the script to look at it and check it was correct. Finally I installed Universal init.d and it is the self test in that app that says init.d support is not present, and after enabling it with the app the drive now mounts. It is possible that SDext2mounter broke init.d when I tried to mount the drive using that but I have no way to check that now and I am not sure how it could have.

Install universal init.d and check what results you get. If it was broken by SDext2mounter then I sincerely apologize. You have to understand how frustrated I was after troubleshooting this problem for several hours using both a drive and a thumb stick I unnecessarily formatted to ext4. As I said, I did my due diligence and it is because I did and installed Universal Init.d that I got the rest result that init.d support was not present.
[Ouya Android Development] IncognitoMan:
Okay then since you used Universal Init.d lets use the authors init.d checker script to see if init.d is enabled and working on the rom.

So we download and extract the script to a folder... open up term or command line window to that folder and first make /system RW

adb shell
su
mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP

We then exit out of adb shell and push the script "00test" to /etc/init.d

adb push 00test /etc/init.d/

We then go back into adb shell and chmod 777 the script

adb shell
chmod 777 /etc/init.d/00test

At this point we can reboot the OUYA.

After reboot adb shell back in and check /data/ for Test.log

adb shell
su
cat /data/Test.log

At which point the result should output...

shell@android:/ # cat /data/Test.log
Ryuinferno @ XDA 2012
Init.d is working !!!

This script also automounts RW /data and /system if you want to leave it there for making it left to always mount as RW but again i leave this up to the user.

Also this gives a pretty good "guide" to how installing init.d scripts work.
[Ouya Android Development] TadeoNYC:
My apologies. I did not run the test as individual scripts, I ran it through the app. That said, the result came back that there is no init.d support present.

So somehow within the 24 hours between installing StockPlus after a factory reset and installing universal init.d something broke init.d support. If there is anyway you can think of for me to figure out the culprit, I'd be glad to pull some logs.
[Ouya Android Development] HT123:
Turning off Bluetooth made no difference.

I ran a cable to the borrowed router that was about 30 feet closer so another wndr3300 with dd-wrt on it sat about 17 feet from the Ouya. I set up the router and connected the Ouya to it and was able to get consistent performance on par with the other devices in the house.

It truly is just really crappy wifi hardware on that device. With the new router it makes a great xbmc box which is what it was bought for but without it, the device was useless.
[Ouya Android Development] IncognitoMan:
I really don't know... all I can say is that init.d does indeed work.

I'd say to make sure the script actually does work.

Hmm... question is how did you turn off BT?

The reason I'm thinking its OUYA doing something wrong with BT ( or at least possibly ) is because of how my wifi performance drops significantly when the OUYA is on.

Here are some results of pinging on the local network to the main router

------- OUYA ON ---------

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=46ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=11ms TTL=64
Reply from 192.168.1.1: bytes=32 time=30ms TTL=64

Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 5ms, Maximum = 46ms, Average = 23ms

------- OUYA OFF --------

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64

Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 3ms, Average = 2ms

We can at least establish that the OUYA is doing some form of interference.

Whether it be from BT or something else... that has yet to be figured out.

If I get around to it today... I'll investigate it a bit more.
[Ouya Android Development] HT123:
I'm at work but looking for the link. It involved installing a widget and extracting the command that was used to toggle BT and then using adb to execute it. (I take no credit for that one i just followed somebody else's instructions)

I have never seen an issue on internet speeds devices when the Ouya is on but have not looked at very granular results to local machines. I did notice that for the short time my Ouya got good speeds (maybe 3 days) it was right after I had manually set the channel on the wireless. I live in the woods and am the only wifi signal withing 1/4 mile so i never bothered to set it until i setup WDS.

I also set my cell phone connected to the wifi directly on top of the Ouya while it was on and got normal speed with the speed test app.

As i said, the new router makes it so the Ouya is useable but it s crappy solution. It seems that if it was able to get decent speed once, it should be able to do so again. Especially since it kept that speed for a few days from having nobody home and no interference to having 2 computers and 3 ipads all on the seam connection at the same time.
[Ouya Android Development] Phen0m:
Great Rom! However, was the Cifs.ko left out on purpose? Its not listed under lib/modules?
[Ouya Android Development] crdnilfan:
As an FYI, I installed this today and my system started downloading a firmware update. I couldn't finish the setup without the update downloading to completion. I assume this is unwanted behavior.

This was after a full wipe and clean install.
[Ouya Android Development] IncognitoMan:
Its built into the kernel

Checked it out and looks like they changed the way OOBE checks for updates ( its completely different from before.... this method of checking wasn't in there when I was testing it on 439 and latest was 465/519 )

Sorry for the inconvenience and I should hopefully be able to get an update out quickly enough.

All I have to say is.... touche ouya, touche.
[Ouya Android Development] Prack:
Was going to install this weekend but I guess I will wait for your update :)
[Ouya Android Development] IncognitoMan:
So a quick update to address the issues with OOBE

OUYA has changed the updater check method in OOBE for whatever reason... it's now patched.

For those of you still on the older build... just wipe cache and dalvik cache and then install the updated rom.

For those of you who updated to latest OTA you'll need to do a full wipe ( wipe data/factory reset, wipe cache and wipe dalvik cache ).... then install the rom.

Again sorry for the inconvenience... I didn't think OUYA would change the update check method.
[Ouya Android Development] Prack:
Thank you for the quick update, looks like my OUYA project for this weekend is still on. Quick question for you though. Does anything not work with this ROM? I thought I heard someone say that they couldn't play some of the OUYA store games after installing.
[Ouya Android Development] IncognitoMan:
I've heard supposedly Play Store will update a game that was installed from the OUYA Discover store. The solution would be to go to play store settings and under "Auto-update apps" choose "Do not auto update apps".

Besides that I do not know of anything that doesn't work.
[Ouya Android Development] krest:
IncognitoMan could you add support for external mouse..... left click on the mouse ran the program, right click the mouse close the program, the middle mouse click caused the program settings.

Thanks.
[Ouya Android Development] vbrtrmn:
Saw both cifs and nfs in: /sys/module/

Having some issues mounting nfs or cifs via the command line:

Busybox nfs

$ busybox mount -o proto=tcp -t nfs 192.168.1.99:/export/TV /mnt/TV/
mount: mounting 192.168.1.99:/export/TV on /mnt/TV/ failed: Connection refused

Busybox cifs

$ busybox mount -t cifs //192.168.1.99/export/TV/ /mnt/TV/
mount: mounting //192.168.1.99/export/TV/ on /mnt/TV/ failed: Invalid argument

w/o busybox nfs

$ mount -o proto=tcp -t nfs 192.168.1.99:/export/TV /mnt/TV/
mount: Invalid argument

w/o busybox cifs

$ mount -t cifs //192.168.1.99/export/TV/ /mnt/TV/
mount: Invalid argument

I can connect to the mounts from several other machines with no problem.
[Ouya Android Development] malaquita:
The external mouse support will be great

Enviado desde mi HUAWEI U9508 usando Tapatalk
[Ouya Android Development] nex86:
there already is...
[Ouya Android Development] krest:
No...

This is not possible in the rom

support for external mouse..... left click on the mouse ran the program, right click the mouse close the program, the middle mouse click caused the program settings.
[Ouya Android Development] vbrtrmn:
Wound up switching to CM10 Exp, found this works, not sure if it'll work for StockPlus, but I don't see why not.

busybox mount -o nolock,rw,hard,intr,proto=tcp -t nfs 192.168.1.99:/export/Movies/ /mnt/Movies/
busybox mount -o nolock,rw,hard,intr,proto=tcp -t nfs 192.168.1.99:/export/TV/ /mnt/TV/
[Ouya Android Development] TadeoNYC:
Is anyone using StockPlus and Link2SD, if so please give me some help with some questions. This is my second go round from scratch, because I thought Android Tuner might have been interfering. I have tried using both a 1 TB Buffalo mini station and 16GB Sandisk Voyager, using mini tool I created a active primary Fat32 partition and a primary ext4 partition on both. They can both be mounted from command line, but will not mount at boot. I have tried the ext2mounter app and that does not see the partition even after it is mounted. I have installed the init.d script from Natorus87

!/system/bin/sh

mkdir /data/sdext2

mount -t ext4 /dev/block/vold/8\:2 /data/sdext2

And that does not work at boot either. For the second time now when installed StockPlus after a factory reset running the Universal init.d app's test for kernel support gives the result "Your kernel does not have init.d support", I'm not looking for another debate about this, I'm looking at the message on-screen right now. The last time i did this after I enabled init.d support in the app rebooted and then disabled support via the app, the test result then began displaying that support was present.

So as it stands right now. The script is in the init.d folder and can be executed manually to mount the partition. However ext2mounter does not see it and Link2SD is hinky. It appears in Storage Info, but if I try Recreate Mount Scripts it says second partition not found. However I can create links to SD, then after rebooting they disappear of course, but can be relinked after manually mounting then do not load after rebooting .

For a little while the first time I did this the partition would mount at boot and be visible to file managers but apps didn't load.I could relink them, hot boot by killing OUYA System and the apps would be restored., Now OUYA locks up during boot, usually the boot animation slows to a crawl and then just stops all together. If I leave it eventually the image changes to snow.

Where is the problem here? In the Rom? Link2SD? The OUYA?

My Ouya is a Kickstarter edition that I got in May. Does factory reset bring it all the way back to the original Rom? Would flashing a newer stock Rom before StockPlus make any difference?
[Ouya Android Development] Ipse_Tase:
Do you guys know if Ouya plans to release a new ROM when the USB storage beta is over? Second, any word from Ouya on Dolby/DTS licensing?

Can we expect a new StockPlus version at that time?

I'm super happy with 519r2 so far and I probably won't have to tinker at all once USB storage is officially sorted out.

PS. And pls don't tell me to go ask in the Ouya forums...I hate black holes :)
[Ouya Android Development] arohrmann:
No adb ?

After flashing this ROM I don't have ADB to connect to my OUYA.

Why and what I can do now to push files to OUYA's sdcard?

With ROM Manager I can boot in recovery.

------

Update: The problem was my notebook' USB-Port. After reboot ADB is activ now :)
[Ouya Android Development] nchantmnt:
Go to dev settings and enable ADB?

Otherwise you can boot your OUYA up normally while USB plugged into your PC. Just like you would do with any other Android device.

Gesendet von meinem One X+ mit Tapatalk

---------- Post added at 11:23 AM ---------- Previous post was at 11:10 AM ----------

I guess as soon as the usb storage feature is officially sorted out they will include it in their next fw-update.

Just be patient ... they're working hard on improvements and updates.

Gesendet von meinem One X+ mit Tapatalk
[Ouya Android Development] TadeoNYC:
The new stock firmware includes a strict TOS that needs to be approved before the OUYA can be used.

I'm not sure how incognitoman is handling that. I'm fine with what we have until the official OTA with USB storage is released, then it will need to be seen if all of the mods still work on it.
[Ouya Android Development] cgadgetz:
Does anyone have ES File explorer working with this new build? It work for me in all previous builds but not it force closes immediately
[Ouya Android Development] TadeoNYC:
It's the app, you need to roll back several versions to the version ending in .51
[Ouya Android Development] cgadgetz:
Thanks that worked perfectly
[Ouya Android Development] topnomi:
I've been invited to the usb storage beta.

The email i just received said my ouya would get the update automatically today. I'm on latest stockplus, so it probably won't be offered unless i switch to official.

Should i try to grab the update somehow to help development, or is this already taken care of?
[Ouya Android Development] Ipse_Tase:
Interesting, my Google Play version works fine, but ES Task Mgr is the one I had to find 1.3.1 to install.

Just curious - is this something we need to consider when changing ROMs? I.e. probably newer ROM will not change the behavior - or will it?
[Ouya Android Development] TadeoNYC:
i think peopleonstock havehad problems too
[Ouya Android Development] ph1nn:
Why mess with that when there is a simple and well designed file manager for free on the OUYA store Apps section? Just use FilePwn.
[Ouya Android Development] Ipse_Tase:
Because from ES File Mgr I can browse my NAS and Cloud-stored files as well as the local ones. No need to advocate ES File Mgr - it is y far the best app of its kind.

Using this file mgr and BS Player I can play a movie from my storage without even starting XBMC.

But we hijacked the OP thread...so I'll stop, waiting for a new ROM to play with ;)
[Ouya Android Development] ph1nn:
Gotcha, browsing NAS/cloud files is definitely reason enough, I hadn't needed that yet.

I'll check out BSplayer, I had played media files through XBMC (with a USB flash and over network) because the VLC is too slow and buggy right now. I digress :)
[Ouya Android Development] Hal9k+1:
For those of you struggling with the /etc/init.d scripts, it may be to the fact that other areas are still getting initialized (in parallel). I went about changing the 16384 in IncognitoMan's network/Ethernet script to 32768, as the former value doesn't quite plug the stuttering issue for me. Well, the change didn't apply.

I looked around and found Ouya's official change in /init.cardhu.rc, which also makes it 16384. Therefore I surmised that the Ouya change was running after mine.

As a workaround I placed the command "sleep 10" just prior to the "echo" command in the script, and that looks to have handled it.
[Ouya Android Development] TadeoNYC:
Thanks! Would that work for all scripts? Could this be the reason that checking for init.d script returns a negative result?

I gave up on init.d mounting a ext4 partition for Link2SD and use Android Tuner on a single Fat32 partition for linking apps and folders. However there are many other scripts available from Android Tuner that can use init.d rather than waiting for AT to run them after boot.
[Ouya Android Development] Hal9k+1:
It's tough to say if the "sleep" trick could handle other cases. But it was interesting seeing how the native Android scripts were apparently still running. Another possibility is that the kernel is missing some level of device support, or that a kernel module needs loading.

There is apparently no /tmp directory in this environment for logging purposes, but /dev can be used as a ramdrive. You could append something like ">> /dev/xyz 2>&1" to script commands for capturing any output to a file for later analysis. Start with the simple "date" command and then work from there.

Best of luck!
[Ouya Android Development] S13gfried:
Hello,

are there any known Issues or Bugs with some apps installed from Playstore.

I´m "new" on the latest (10/10/2013) StockPlus Rom. I´ve installed the superSU binarys, xposed updates + restart und selectet modules.

Apps not working are (installed from playstore):

Romtoolbox free - Ask for SU, get it, work some time. Now if I try to start it shortly seems to work, but no chance to make any input

ES Dateiexplorer (without root option)

Playstore crashes very often, for example by klicking the searchbox, sometimes after klickung "my apps". But NOT every time.

ASTRO File Manager

Goolge Chrome (crash during Login with account)

Apps working:

Dropbox

Youtube

USB OTG Helper

All pre installed (but little problems with Playstore

Apps from aptoide.com for testing

ES File Explorer (1.5 Cupcake) - works fine

Root Explorer - not working

Romtoolbox Pro - works until "please download from playstore"

I already tried via CWM:

wipe cache partition and wipe dalvik

Next step was factory reset. It does not help.

No more ideas. Maybe download and flashing the Rom again...

One more think. Ouya is connectet via Lan to an Accespoint, witch ist linked with the Router. I´m going to test a direct connection.

Thank you for helping :)
[Ouya Android Development] adfurgerson:
Got this up and running, couldn't figure out adb for the life of me. Ended up rerunning cwm installer to get back into recovery to flash the ROM. Just wanted to mention that Quickboot app works for booting to recovery. A big thank you to the whole community. Also wondered if there is an irc channel for this device?
[Ouya Android Development] Careless_:
if there's one thing, as a UI designer, that I could ask you to avoid doing in the future; please don't squish the OUYA logo in the opening loading screen. it looks unprofessional and unpolished. Keep it with the same dimensions as the original logo and it will look less amateur.

otherwise- that's not bad for my only issue with this rom. so far so good.
[Ouya Android Development] topnomi:
There was a new big update today. It seems like it changed a bunch of stuff under the hood.

https://www.ouya.tv/ouya-system-update-abominable-snowman-november-21-2013/?utm_source=feedly

[MENTION=5333435]IncognitoMan[/MENTION] - Are you planning on updating this soon, or should i just install the stock update?

I don't mean to rush you, or ask for eta's. i just want to know if it's in the works. I might get impatient and install it anyway, because i'm really interested in the usb storage feature.