Good day
Let me start with a little background info. I had an eris and now Dx since well before they were rooted. I follow the forums here daily as I am an admitted gadget junkie;-) Well anyway I thought I kept up with most of the upcoming tech news but this slipped right by me. Happened to see it while wondering aimlessly in bestbuy yesterday. Of course I bought it. You all prolly already know about this product but just in case you didn't I just wanted to let my favorite devs on the best forums in on it. Hopefully you're all due for a printer upgrade. In case you don't figure it out the 7" detachable touchscreen printer interface has android 2.1 on it already. I've already figured out how to put alot of my own apks on it but maybe you guys will have ideas I could try on it Really need some market action on this thing. So check it out and have a good day.
http://www.shopping.hp.com/product/printer/Photosmart/1/storefronts/CQ140A%23B1H
I agree with you on the fact that it needs the market on there, but this was released well over 2-3 months ago. A lot has been written about it that it MIGHT get 2.2 and/or more upgrades come 2011, but that was also right before HP bought Palm and committed to WebOS.
I haven't found much information at all on it? Mine is offering to update rite now but I'm holding off until I learn more about it. I want to root it of course. I've already tried androot Z4root and dmupdater with no luck. If anyone could guide me through dumping the right info off it maybe we could get a recovery. I have learned that it's manufactured by foxconn, same company that has manufactured every "i" device apple has ever put out. Anyway hope there's enough interest in the device for some development
Amen brother... I can't wait for someone to sink their teeth into this thing and open up the potential...
Partial Root
I managed to load z4 root successfully, and could then load on various other .apk's. No market though. Once all of the HP junk was removed, it performed quite well.
Debug?
What did this do to your printer? Were you able to develop/debug to the zeen? I can't get the ADB to recognize it.
hey guys im a new user to this damn zeen i have an evo, so i was trying to get the market on this thing but no luck, have you been able to pull it off yet??
Anyone know a good alternative market to use on this, or how to get the official?
try app brain and let me know how it goes!!
I've added a Dev Thread for this at http://eb-productions.proboards.com/index.cgi since barak now has this device....
you wont get adb due to it being turned off in the kernel.
this is a work in progress from another thread, and its not working well yet. i dont know how to get it going, but it seems like it has something to do with the inputs not working yet. this runs GREAT on my thunderbolt, but wont move on the iconia. the inputs just dont work. basically take the minecraft apk, install it, extract the .minecraft directory to your sdcard so the tree is as follows
sdcard>.minecraft>saves>world1
the app will make it for you, so you just have to paste the world1 folder into the saves folder (this takes a while, theres over 10000 files, but its just 17mb)
minecraft app
http://dl.dropbox.com/u/9236041/MineDroid-130211.apk
minecraft zip
http://dl.dropbox.com/u/9236041/minecraft.zip
like i said this is really a work in progress, and what we need is someone far more skilled than i to get it going better
For the sake of my social life, I hope this is never completed
Thanks for the info.
i used this on my droid. its cool. but im going to wait a little longer. the official app is coming soon. imo i wouldn't focus to much on an app that will most likely die in a few weeks once the official one comes
well notch is making the app for gingerbread, and he's designing it mainly for the xperia play, i think this would be a little worthwhile because its going to be a pain to get the app to run on honeycomb anyway
krickatthedisco said:
well notch is making the app for gingerbread, and he's designing it mainly for the xperia play, i think this would be a little worthwhile because its going to be a pain to get the app to run on honeycomb anyway
Click to expand...
Click to collapse
from what i have been reading, it will be exclusive for the xperia for a short time and the opened up to all devices. (including iOS at some point) BUT ANDROID FIRST
nice, we never get anything first lol, i guess this is hopeless then. let the waiting begin '-'
join the club. been waiting for minecraft on android since i started playing in January
I know just the thought of opening up tab and getting onto my minecraft sever has gotten me excited
Just got done talking to Amazon and discovered that I'm still in the window to be able to return the OUYA and get a full refund, so I'm taking that opportunity rather than continue to hope that the OUYA team will decide to deliver on the open console they promised.
After seeing how others have been treated and being ignored myself, I simply have no faith in their ability to deliver. Instead I see only more of the same, and instead of problems being fixed I see OUYA choosing to release version 2.0. If they'd screw over the kick-start backers, why wouldn't they screw over us too? The lack of communication, lack of transparency, lack of honesty make me think the OUYA have no future going forward and no vision beyond chasing the next customer at the expense of current ones.
Why would I stick around? To throw more good money after bad? Even if the community manages to paper around most of the issues plaguing the console, it will be at the expense of the console functionality--being able to just buy a game and play it, instead everything will eventually be through the Google Play Store (in which case what is the point of buying OUYA games?) or there will be all sorts of alternative stores trying to deliver OUYA Discovery store games without the OUYA team's blessings and that will only work for so long before it gets categorized as piracy...
What future is there here?
And please don't say XBMC, because one of the reasons I'm throwing in the towel is because I am unable to get my USB drive with all my videos recognized on the OUYA. That being the case, it's not even good to me as a Media Center device. Not when there are much better supported options available that I don't have to hack to make work all the time.
Emulation you say? What good is emulation with such a small internal disk and no real ability to expand the storage?
No, I'm done. But I'm wondering who else is thinking about walking away and returning their OUYA for a refund, and what are they planning on getting as an alternative?
Sent from my Nook HD+ using Tapatalk HD
bornagainpenguin said:
Just got done talking to Amazon and discovered that I'm still in the window to be able to return the OUYA and get a full refund, so I'm taking that opportunity rather than continue to hope that the OUYA team will decide to deliver on the open console they promised.
After seeing how others have been treated and being ignored myself, I simply have no faith in their ability to deliver. Instead I see only more of the same, and instead of problems being fixed I see OUYA choosing to release version 2.0. If they'd screw over the kick-start backers, why wouldn't they screw over us too? The lack of communication, lack of transparency, lack of honesty make me think the OUYA have no future going forward and no vision beyond chasing the next customer at the expense of current ones.
Why would I stick around? To throw more good money after bad? Even if the community manages to paper around most of the issues plaguing the console, it will be at the expense of the console functionality--being able to just buy a game and play it, instead everything will eventually be through the Google Play Store (in which case what is the point of buying OUYA games?) or there will be all sorts of alternative stores trying to deliver OUYA Discovery store games without the OUYA team's blessings and that will only work for so long before it gets categorized as piracy...
What future is there here?
And please don't say XBMC, because one of the reasons I'm throwing in the towel is because I am unable to get my USB drive with all my videos recognized on the OUYA. That being the case, it's not even good to me as a Media Center device. Not when there are much better supported options available that I don't have to hack to make work all the time.
Emulation you say? What good is emulation with such a small internal disk and no real ability to expand the storage?
No, I'm done. But I'm wondering who else is thinking about walking away and returning their OUYA for a refund, and what are they planning on getting as an alternative?
Sent from my Nook HD+ using Tapatalk HD
Click to expand...
Click to collapse
I for one am planning on using my OUYA as a paperweight. It looks quite good.
In all seriousness, I bought this never intending to bother with stock firmware, so when I get back to school I'll toss CM10.1 on it and use it to complement an ailing Logitech Revue. As a kickstarter backer though, I can't exactly return my unit, and I don't know that I'd feel good about selling it to anyone. Neat idea, awful execution on the software side.
That's a rather long post to tell us you just don't like your unit. Mine works fine. No problems with XBMC either. Playing across from my 4 terabyte home server with no issues.
BAXY Launcher as a replacement, live wallpapers, music and more. Kind of funny that you're returning yours because software that hasn't been released officially for it yet doesn't work right. That doesn't sound funny to you?
Blasted from my Samsung Galaxy SIII (CM10.1 Masta Mix).
Rirere said:
In all seriousness, I bought this never intending to bother with stock firmware, so when I get back to school I'll toss CM10.1 on it and use it to complement an ailing Logitech Revue. As a kickstarter backer though, I can't exactly return my unit, and I don't know that I'd feel good about selling it to anyone. Neat idea, awful execution on the software side.
Click to expand...
Click to collapse
Well I differ slightly here. With exception of the USB bug, limited usability of the touchpad, and overscan issues (which AFAIK never effected me) I honestly thought the default launcher was pretty good.
The Discover menu could have been cleaned up a bit, but for a new console with a limited repository of software, it was pretty good at showing off what was available. Some of the lists were a bit redundant, but that was understandable considering at this point we're all playing the same games. I would have expected the lists to diverge quite severely as newer games were added.
I would have liked to see a list for games which had been bought by percentages, a queued downloads section somewhere so you knew what was already selected for download and a way to see how much was in the pipe left to come and a place for all the games you'd purchased previously so you could add them back in to your library more easily once you started building it up. Would have even been a good idea to add a wishlist option so you could remember games you'd tried in the past but decided to buy at a later time for some reason. Otherwise the interface really didn't offend me all that much.
It was hardware bugs and usability issues that bothered me more than anything.
And while I'm sure the community will be able to fix most of these, I feel that in doing so the OUYA stops being a game console and becomes an Android computer.
RED ZMAN said:
That's a rather long post to tell us you just don't like your unit.
Click to expand...
Click to collapse
Who says that I didn't like my OUYA? When it worked it was the most amazing thing in the world. I could have both games and my media all with the same device. I liked it so much that despite having intended it as an emulation\xbmc box I began buying games. Does that sound like someone who doesn't like their OUYA?
RED ZMAN said:
Mine works fine. No problems with XBMC either. Playing across from my 4 terabyte home server with no issues.
Click to expand...
Click to collapse
Not everyone has a NAS of that type. I do however have a 1TB WB USB drive formatted to NTFS, a 2TB Seagate USB drive also formatted to NTFS, and a 3TB Toshiba USB drive formatted to FAT32. Since the last update my OUYA likes none of them. Before the last few updates I was able to make use of all of them by powering off the OUYA, plugging them in and upon restarting doing a system reset (returning to factory defaults).
Then I too was able to enjoy xbmc from my OUYA and was blown away by how well the video playback was. The problem is that I am unable to get my USB drive to mount ever since the latest update. And having to do a system reset every time I moved the OUYA somewhere to show it off and having to readd all my xbmc libraries and all my games got old after the third time. Worse was when mandatory updates hit and required me to do a reset because the update unmounted the USB somehow. Worse yet was when I posted about it on the OUYA twitter account and was completely ignored.
RED ZMAN said:
Kind of funny that you're returning yours because software that hasn't been released officially for it yet doesn't work right. That doesn't sound funny to you?
Click to expand...
Click to collapse
Perhaps if that was why I'm returning the OUYA it would seem funny. Unfortunately for your strawman argument I am not returning the OUYA because it doesn't run alpha software without issues; I am returning my OUYA because it is missing basic functionality in the USB port and unable to mount USB drives. Amazon has listed as my reason for return "defective" hardware.
Without being able to mount the USB drive I am unable to use my OUYA for its purpose. By breaking the USB mounting as they have, the OUYA team have rendered the console unfit for its purpose. Is that clear enough?
--bornagainpenguin
bornagainpenguin said:
Well I differ slightly here. With exception of the USB bug, limited usability of the touchpad, and overscan issues (which AFAIK never effected me) I honestly thought the default launcher was pretty good.
The Discover menu could have been cleaned up a bit, but for a new console with a limited repository of software, it was pretty good at showing off what was available. Some of the lists were a bit redundant, but that was understandable considering at this point we're all playing the same games. I would have expected the lists to diverge quite severely as newer games were added.
I would have liked to see a list for games which had been bought by percentages, a queued downloads section somewhere so you knew what was already selected for download and a way to see how much was in the pipe left to come and a place for all the games you'd purchased previously so you could add them back in to your library more easily once you started building it up. Would have even been a good idea to add a wishlist option so you could remember games you'd tried in the past but decided to buy at a later time for some reason. Otherwise the interface really didn't offend me all that much.
It was hardware bugs and usability issues that bothered me more than anything.
And while I'm sure the community will be able to fix most of these, I feel that in doing so the OUYA stops being a game console and becomes an Android computer.
Who says that I didn't like my OUYA? When it worked it was the most amazing thing in the world. I could have both games and my media all with the same device. I liked it so much that despite having intended it as an emulation\xbmc box I began buying games. Does that sound like someone who doesn't like their OUYA?
Not everyone has a NAS of that type. I do however have a 1TB WB USB drive formatted to NTFS, a 2TB Seagate USB drive also formatted to NTFS, and a 3TB Toshiba USB drive formatted to FAT32. Since the last update my OUYA likes none of them. Before the last few updates I was able to make use of all of them by powering off the OUYA, plugging them in and upon restarting doing a system reset (returning to factory defaults).
Then I too was able to enjoy xbmc from my OUYA and was blown away by how well the video playback was. The problem is that I am unable to get my USB drive to mount ever since the latest update. And having to do a system reset every time I moved the OUYA somewhere to show it off and having to readd all my xbmc libraries and all my games got old after the third time. Worse was when mandatory updates hit and required me to do a reset because the update unmounted the USB somehow. Worse yet was when I posted about it on the OUYA twitter account and was completely ignored.
Perhaps if that was why I'm returning the OUYA it would seem funny. Unfortunately for your strawman argument I am not returning the OUYA because it doesn't run alpha software without issues; I am returning my OUYA because it is missing basic functionality in the USB port and unable to mount USB drives. Amazon has listed as my reason for return "defective" hardware.
Without being able to mount the USB drive I am unable to use my OUYA for its purpose. By breaking the USB mounting as they have, the OUYA team have rendered the console unfit for its purpose. Is that clear enough?
--bornagainpenguin
Click to expand...
Click to collapse
If it did work, don't you think it might have just broke in the last update. They wouldn't include a USB port if they didn't want everyone to use USB HDDs. It broke, but they'll fix it. Can't see returning it because of one update bug.
Sent from Nexus 7 FHD from XDA Premium HD
I'm rocking the hell out of my OUYA, with the Play store installed, sdcard enabled, and controller support becoming the norm I plan to be playing mine for a loooong time. It's a much more elegant solution than a phone or tablet with hdmi out. Yeah the OUYA store has a crappy selection, but that is about the only knock against it I have. Your loss man.
player911 said:
If it did work, don't you think it might have just broke in the last update. They wouldn't include a USB port if they didn't want everyone to use USB HDDs. It broke, but they'll fix it. Can't see returning it because of one update bug.
Sent from Nexus 7 FHD from XDA Premium HD
Click to expand...
Click to collapse
It's not just one update bug--before this to get it to work took a lot of jumping through hoops. And who says they'll get to fixing it in a reasonable time frame? Look how long it took for them to fix the overscan bug, people were waiting three or four months with an OUYA that couldn't play most games.
Maybe if I'd at least gotten a response or a promise that they were working on it, I might stay, but the silence from OUYA has been very telling. Amazon already refunded my debit card, so I don't think I have a choice at this point, even if I found out there was an update this afternoon that fixed everything.
Tapatalk steals from their customers by forcing them to view ads in a paid app! - - sent from my MIRAGE KANG running Nook Color
bornagainpenguin said:
Well I differ slightly here. With exception of the USB bug, limited usability of the touchpad, and overscan issues (which AFAIK never effected me) I honestly thought the default launcher was pretty good.
Click to expand...
Click to collapse
The stock launcher is horrible. I didn't think it was bad until I tried out BAXY, now I know it is utter crap. The BAXY developers have made a better launcher in 2 weeks than OUYA did in a year.
And while I'm sure the community will be able to fix most of these, I feel that in doing so the OUYA stops being a game console and becomes an Android computer.
Click to expand...
Click to collapse
Thats already what it is. It is both.
Who says that I didn't like my OUYA? When it worked it was the most amazing thing in the world. I could have both games and my media all with the same device. I liked it so much that despite having intended it as an emulation\xbmc box I began buying games. Does that sound like someone who doesn't like their OUYA?
Click to expand...
Click to collapse
Who said you didn't like it? Let's see... *Reviews thread* Oh, I did. You returned it because something went buggy for you in an update that took place exactly one week ago. ONE WEEK. Hell, Sony borks an update on the PS3 a few times a year, and the latest one took what, 3 weeks for them to patch? I wonder how many PS3 owners returned their POS3's during that time period...
No, it doesn't sound like someone that didn't like their OUYA, it sounds like someone that is unrealistic and doesn't understand how dynamic the firmware and software is these days. In your opinion, they should have just seen there is a problem, clicked "FIX USB BUGS" on their SDK interface, and sent out an immediate update.
Right?
Not everyone has a NAS of that type. I do however have a 1TB WB USB drive formatted to NTFS, a 2TB Seagate USB drive also formatted to NTFS, and a 3TB Toshiba USB drive formatted to FAT32. Since the last update my OUYA likes none of them. Before the last few updates I was able to make use of all of them by powering off the OUYA, plugging them in and upon restarting doing a system reset (returning to factory defaults).
Click to expand...
Click to collapse
Yay?
Perhaps if that was why I'm returning the OUYA it would seem funny. Unfortunately for your strawman argument I am not returning the OUYA because it doesn't run alpha software without issues; I am returning my OUYA because it is missing basic functionality in the USB port and unable to mount USB drives. Amazon has listed as my reason for return "defective" hardware.
Click to expand...
Click to collapse
Strawman argument? What is this, 1856? I didn't say anything sounded funny either. I reviewed the Amazon page for the OUYA, and yes, it says...
Need more storage? No problem. Just plug in an external hard drive into the USB 2.0 port.
So I agree, that would be basic functionality since it was listed to be a feature on the device. Did they screw it up? It looks like for some, yes, they did. Do you want a quick fix that borks something else or do you want them to fix it right, along with some other things, and submit an update once a week instead of once every day or two?
Oh, and don't pretend that "Amazon has listed as my reason for return 'Defective' hardware". You listed it as that for your reason of return, I've returned enough to Amazon to know how it works. Even that reason would be wrong. Your hardware is fine, the software has a defect. For now.
I guess I should return mine too since my USB mouse/keyboard combo keeps logging on as controller one. Amazon will list this as "damaged in shipping"
RED ZMAN said:
The stock launcher is horrible. I didn't think it was bad until I tried out BAXY, now I know it is utter crap. The BAXY developers have made a better launcher in 2 weeks than OUYA did in a year.
Click to expand...
Click to collapse
I guess I'd have to try out BAXY for myself to 'get' the improvement. I stand by what I said for now though, based on my use of the current store it doesn't strike me as all that bad.
RED ZMAN said:
Who said you didn't like it? Let's see... *Reviews thread* Oh, I did. You returned it because something went buggy for you in an update that took place exactly one week ago. ONE WEEK. Hell, Sony borks an update on the PS3 a few times a year, and the latest one took what, 3 weeks for them to patch? I wonder how many PS3 owners returned their POS3's during that time period...
No, it doesn't sound like someone that didn't like their OUYA, it sounds like someone that is unrealistic and doesn't understand how dynamic the firmware and software is these days. In your opinion, they should have just seen there is a problem, clicked "FIX USB BUGS" on their SDK interface, and sent out an immediate update.
Right?
I reviewed the Amazon page for the OUYA, and yes, it says...
Need more storage? No problem. Just plug in an external hard drive into the USB 2.0 port.
So I agree, that would be basic functionality since it was listed to be a feature on the device. Did they screw it up? It looks like for some, yes, they did. Do you want a quick fix that borks something else or do you want them to fix it right, along with some other things, and submit an update once a week instead of once every day or two?
Click to expand...
Click to collapse
Ha-ha-ha....yeah, that's exactly what I wanted! The OUYA team needs to just press their magic doo-hickey in their super duper OUYA SDK and reenable large disks support, all the while serenading us with music from unicorn horns and rainbows coming from every television set! How did you know?
Only, sarcasm aside and all your attempts to make me out to be foolish to the contrary--yes, that is exactly what I do expect to see happen. I expect the OUYA team to fix what they broke. What I start to suspect is deliberate breakage.
Hear me out please. And help me to understand please how any other conclusion is a better one to fit the details...maybe you'd rather pretend the OUYA team is simply incompetent? Although honestly I'm not quite sure how that makes things better...
Let's look at the facts, shall we? All it takes to fix USB external hard drive detection is root installation of the Paragon app. That's all that needs to happen, then the external storage will work again. Will work without a need to do a system reset every time you plug in the drive or jump through other hoops. This is something I've been told over and over again and seen others told over and over again whenever the issue of large USB disks not mounting was brought up--just root and install Paragon and your troubles will be over. It's easy.
I've also seen mention of a script which could run which would make needed changes in vold.fstab (a bit more understanding of the system needed to accomplish but easy enough if you know what you're doing and can follow instructions.) Since not everyone is comfortable with editing system files the easy button is to simply use Paragon and this is why it gets recommended so often.
Meanwhile I sit here just amazed that an external application can do what the OUYA developers seemingly cannot do and will not discuss doing. Are we really supposed to believe the makers of the system are unable to fix so simple of a problem as this because it is so extremely complicated---booooooooo--be very very scared---booooooooo....and yet outsiders can program an app that can do it apparently without breaking down a sweat? Really? Maybe incompetence is looking to be a better rationale after all?
No, as I said before this whole thing stinks to high heaven and between the USB bug (which looks less and less like a bug every day that goes by without an official fix) and the overscan bug which if posts by people who suffer from it are to be believed is only a bandaid that did nothing to fix the actual problem, the locked bootloader, the lack of root, lack of openness, large numbers of people on kickstarter who still haven't gotten their units, DRM that makes you depend on OUYA being there to continue playing what you paid for, etc etc...it starts to look like a pattern. And with the lack of communication it's impossible to know if things are ever going to be different.
I'm not hopeful. I posted this thread in hopes of someone giving me a reason to find hope again, to decide to stick it out and expect things would get better and no one has. So tomorrow after work when I can finally have some time to head over to the UPS pick up while the store is still open I'll be taking the printout Amazon sent me and returning the OUYA to get my money back.
I've seen others also making this decision and posting about it too. Maybe if enough of us return our devices the number of people saying no sale and voting with their wallets will be enough to make the OUYA team wake up and fix things. If they're as incompetent as you seem to think they are, I'm not sure how much good it will do though....
--bornagainpenguin
I think most of the problem with not having root, which is the root of a lot of problems, is that the device is being made for more than the members on this forum and other developer communities.
The device needs to be user friendly to some degree. If they start making root a standard, than those who don't know otherwise will start bricking their consoles left, right and center
Sent from my Xperia S using xda premium
sasamifan said:
The device needs to be user friendly to some degree. If they start making root a standard, than those who don't know otherwise will start bricking their consoles left, right and center
Click to expand...
Click to collapse
All OUYA would have had to do was made it accessible via easter egg, similar to how developer options are enabled now on most roms by tapping the build number. They could even have paid homage by making it be the Konami code that unlocked things.
It's not *that* hard and is what they promised.
Most of the user friendly issues could be resolved by having a working recovery that allowed backups to be created before messing with the system. Something like CWM....
Sent from my Nook HD+ using Tapatalk HD
bornagainpenguin said:
Well I differ slightly here. With exception of the USB bug, limited usability of the touchpad, and overscan issues (which AFAIK never effected me) I honestly thought the default launcher was pretty good.
Click to expand...
Click to collapse
There's no accounting for taste. I'm glad it worked for you-- for me, it was a thoroughly unpleasant experience (probably made worse by the physical arrangement of the OUYA buttons on the controller, which for me are simply confusing). It just looked and felt very tacky to me, and seeing how paltry the native settings menus were before the system rolled over and coughed up the Android native Settings app made me feel like I was running someone's first theme.
bornagainpenguin said:
The Discover menu could have been cleaned up a bit, but for a new console with a limited repository of software, it was pretty good at showing off what was available. Some of the lists were a bit redundant, but that was understandable considering at this point we're all playing the same games. I would have expected the lists to diverge quite severely as newer games were added.
Click to expand...
Click to collapse
For a storefront that ostensibly wants to highlight breakout titles as well as expose others, I found the display to be a fairly uninteresting grid that made it hard to see any given titles as standout. In their defense though, I was never really interested in the stock OUYA firmware.
bornagainpenguin said:
I would have liked to see a list for games which had been bought by percentages, a queued downloads section somewhere so you knew what was already selected for download and a way to see how much was in the pipe left to come and a place for all the games you'd purchased previously so you could add them back in to your library more easily once you started building it up. Would have even been a good idea to add a wishlist option so you could remember games you'd tried in the past but decided to buy at a later time for some reason. Otherwise the interface really didn't offend me all that much.
Click to expand...
Click to collapse
Ditto.
bornagainpenguin said:
It was hardware bugs and usability issues that bothered me more than anything.
And while I'm sure the community will be able to fix most of these, I feel that in doing so the OUYA stops being a game console and becomes an Android computer.
Click to expand...
Click to collapse
More or less yes, and if I could do it again I would definitely have opted for a different solution (probably one of the upgraded Google TV sets). Although I probably will enjoy messing with the OUYA later (not having a good TV at home makes this hard), I must confess that my interest in messing around with ROMs has been fading fast over the last few months (more or less coinciding with swapping out my Galaxy Nexus for a HTC One). I still primarily own and use Nexus to tinker, but for the TV? I kind of want to be a bit lazier there.
Anyway, as for what you were saying earlier, I doubt the bugs are out of deliberate malice but unintentional/unconscious priority bias. They're out to make money first over encouraging a dev community, which is understandable, but it means that any fixes and resources aren't going to go where we'd like. OUYA has had a sort of Jekyll/Hyde thing going for a while now-- is it a consumer product? A dev box? Both? It's harder than I think they realized to be both.
In the end I just couldn't do it. Subconsciously I guess I really didn't want to return my OUYA because I kept checking to see if there'd been any updates and putting off the return. It didn't help that I had to work overtime all week and kept missing the window where the drop off for UPS is. I finally got a hold of Amazon and cancelled the refund.
Nothing has changed, all of the issues I mentioned before still exist, but I just can't let go. If---a big gamble as far as I'm concerned---but IF the OUYA team do manage to pull themselves up from the tailspin they're currently in and fix the system so it'll do all that they promised us from the beginning, the OUYA has the potential to rule the family room. The truth is nothing else seems to be aiming for the same heights that the OUYA is. There are so many things they have right that it just frustrates me all the more when something doesn't work right.
And most of these things they keep getting wrong are things that are easily fixable! I think someone in the thread said that the launcher baxxy was banged out in two days? I see a fix for the USB problem was posted almost immediately on the OUYA developer forums in June. An app has been developed and posted that allows a one click root via a big button, just like we were promised... Like I said, frustrating.
But I'm in. For as long as the OUYA works, or can be made to work. For as long as there is a community who wants to keep going forward.
I apologize to anyone who thought I came off a troll, honestly I wasn't trying to be.
Sent from my Nook HD+ using Tapatalk HD
bornagainpenguin said:
In the end I just couldn't do it. Subconsciously I guess I really didn't want to return my OUYA because I kept checking to see if there'd been any updates and putting off the return. It didn't help that I had to work overtime all week and kept missing the window where the drop off for UPS is. I finally got a hold of Amazon and cancelled the refund.
Nothing has changed, all of the issues I mentioned before still exist, but I just can't let go. If---a big gamble as far as I'm concerned---but IF the OUYA team do manage to pull themselves up from the tailspin they're currently in and fix the system so it'll do all that they promised us from the beginning, the OUYA has the potential to rule the family room. The truth is nothing else seems to be aiming for the same heights that the OUYA is. There are so many things they have right that it just frustrates me all the more when something doesn't work right.
And most of these things they keep getting wrong are things that are easily fixable! I think someone in the thread said that the launcher baxxy was banged out in two days? I see a fix for the USB problem was posted almost immediately on the OUYA developer forums in June. An app has been developed and posted that allows a one click root via a big button, just like we were promised... Like I said, frustrating.
But I'm in. For as long as the OUYA works, or can be made to work. For as long as there is a community who wants to keep going forward.
I apologize to anyone who thought I came off a troll, honestly I wasn't trying to be.
Sent from my Nook HD+ using Tapatalk HD
Click to expand...
Click to collapse
Trust me if you think OUYA have made a pigs ear of software you've never had a really bad Android box. I put up with the Minix Neo X5 for 6 months before binning it. That was a truly god awful pile of crap. I've done more with the OUYA in a month than I did in 6 with the Neo. Sure, it's not perfect... but it's on the right track.
RED ZMAN said:
That's a rather long post to tell us you just don't like your unit. Mine works fine. No problems with XBMC either. Playing across from my 4 terabyte home server with no issues.
BAXY Launcher as a replacement, live wallpapers, music and more. Kind of funny that you're returning yours because software that hasn't been released officially for it yet doesn't work right. That doesn't sound funny to you?
Blasted from my Samsung Galaxy SIII (CM10.1 Masta Mix).
Click to expand...
Click to collapse
Would you rather he write a post saying "I dont like the ouya it isnt open and i want my money back." you know there are people who do post that way, be happy he detailed his experience.
danbst said:
Trust me if you think OUYA have made a pigs ear of software you've never had a really bad Android box. I put up with the Minix Neo X5 for 6 months before binning it. That was a truly god awful pile of crap. I've done more with the OUYA in a month than I did in 6 with the Neo. Sure, it's not perfect... but it's on the right track.
Click to expand...
Click to collapse
Well my first Android was a Pandigital Novel, so.....
Yeah, I get what you mean though. I was looking through the competition while I was unable to get to the UPS drop off point and kept thinking to myself that even with the stuff that OUYA's gotten wrong, they're still so much further ahead of the curve than anyone else! But that's why it's so frustrating to see them missing this stuff and ignoring the requests of their customers to fix things already. I really don't think it's as hard as people are pretending it to be.
--bornagainpenguin
bornagainpenguin said:
I really don't think it's as hard as people are pretending it to be.
--bornagainpenguin
Click to expand...
Click to collapse
Your absolutely right if you look in the lk bootloader source it's really easy to make a button to get into bootloader. Alot of the other issues would only take someone with the source code a day or less (per issue and some one who is familiar with it).
Asadullah said:
Your absolutely right if you look in the lk bootloader source it's really easy to make a button to get into bootloader. Alot of the other issues would only take someone with the source code a day or less (per issue and some one who is familiar with it).
Click to expand...
Click to collapse
So you see what I mean and understand why I'm so skeptical when people keep making excuses for them?
Like I said over at Ouya Forums, it's a two line edit thereabouts. If it can be done by you or I in vold.fstab as a dirty hack, there's no reason why the OUYA team with their access to the source code can't fix it properly.
The only thing I can think is malicious interference or sheer incompetence to explain their reticence in fixing things.
Sent from my Nook HD+ using Tapatalk HD
I like my Ouya, and thank goodness they sent me a retail kit instead of a preorder kit. Maybe getting it really late is a blessing in disguise.
I agree with a lot of things said in this topic RE: the makers of this box. The hardware's fine (well mine was), but their customer service support is lacking. I haven't seen this much reputation damage since XBAWKS. (not XBone, XBAWKS).
If the dev community is not happy and abandons the thing... at least the controller is salvagable. Not as good as the X360 or PS3's, but decent and better than the unusual Wiichuck, more comfortable than a bluetooth clip gamepad, no proprietary connection protocols and no MAC address hacking needed.
RED ZMAN said:
That's a rather long post to tell us you just don't like your unit. Mine works fine. No problems with XBMC either. Playing across from my 4 terabyte home server with no issues.
BAXY Launcher as a replacement, live wallpapers, music and more. Kind of funny that you're returning yours because software that hasn't been released officially for it yet doesn't work right. That doesn't sound funny to you?
Blasted from my Samsung Galaxy SIII (CM10.1 Masta Mix).
Click to expand...
Click to collapse
RED ZMAN!!!!, how make work CIFS.ko modules in ouya
i need mount NAS server in my home and add this munt at startup.
regards
Ariel
Dear esteemed community members of the XDA developers community website. I have a long and sad story, of which I am hoping you may be able to provide some extra insight into the troubles I have met with my Nexus 4.
I purchased my Nexus 4 (sans rubber feet) last year in August, bought from a Mediamarkt in Berlin during my first travels into Europe, when my Samsung SII met a cruel and drunken fate. When I first got the shining glittering Nexus 4, it notified me of an OTA system update, and doing as instructed I glibly pressed "Update". After the digital progress bar's needle finished injecting its panacea into the phone, it restarted and was then caught in a boot-loop. Frantic, repeated, turning off and on procedures followed, like I was trying to perform CPR at a crash scene. It was out like a light, except its light was still on in the shape of a glowing "X". After trying all the system/cache/data wipes the system tools would allow me, nothing made it budge. I resorted to flash everything to stock with fastboot to successfully get it up and running again, but it was a bad start to a troubled relationship.
A flight back to my home in Australia and some months later (about March this year) I decided to try the OTA update again. I figured after some time, surely they'd have fixed the OTA issues, no? Alas, soft-bricked again -- the glowing "X" taunting me once more. I tried and I tried with all my might to flash all number of versions of Android -- 4.2, 4.3, 4.4 -- using all manners of manual and automated (toolkit) methods, all to no avail. I put the phone in my drawer and borrowed a house mate's iPhone 4, replete with cracked screen.
Fast-forward to a few days ago: my house mate's own Nexus 4 kissed gravity and it was more an expression of a troubled break-up than any affection. She needed her iPhone back and I went back to no phone. There was some kind of bliss in being disconnected, however being a freelance designer and developer, my life-line is work and work is often received and completed via phone duties. Wondering if I could successfully defibrillate life back into this still-new and handsome looking Nexus 4, then the better I would be than without phone. I plugged it all in again, performed a manual flash of KOT49H to finally see past the rotating dots to view the android fellow lying on his back getting some much-needed TLC from some futuristic blue polyhedron tumbleweed. I was "in with a grin" -- the phone and I were back in business.
Lazing about one hung-over Saturday morning with my phone plugged into the charger, me checking out my family and friends' inane burblings on Facebook, the phone winked a red eye at me and went black. I was confused. What happened? Was it something I said? Posted? I tried to turn it on again, and yet silence persisted. It was plugged into the wall, power was on -- there should be juice present within this ripe fruit.
Holding it in my questioning hands, I shakily brought it over to my computer and plugged it into the USB. I tried turning it on again, and the eyes fluttered open, its stare fixated and blank, a rotating vision of 4 dots tumbling in an endless mocking loop. I sighed, "Not again." I tried more methods of flashing and restoring the phone's version of Android, both manual and automated. Nothing. Nada. Zip. Ziltch. Zero.
Here I am, again at the precipice of uncertainty with this phone's status and fate. No activity beyond those dots locked in an eternal dance of emptiness. The drapes of its consciousness are pulled, no vision of what's on stage or who's singing. Silence. Empty space. Lingering thoughts of my involvement bounding like playful lion cubs through the savannah: "if only I...", "if only it...", etc.
So here, dear reader of an esteemed Android developer community website, I petition you in great need and distress: if perchance you may be able to offer some insight into my troubled 'droid; if maybe there's some way to read some console output of what and where the errors are occuring; if perhaps there's something more physical that could be the cause of such pain and strife. I wish to understand my companion's feelings and thoughts more, to know why it feels such despondency in living and working, and how I may be able to coax it back to consciousness. Perhaps all it needs is to have some other sort of love and kindness, the type I'm potentially not adept at speaking in a language for it to understand. Either way, I would love any information someone may be able to proffer.
Please help me XDA developers -- you're my only hope.
lvl99 said:
Dear esteemed community members of the XDA developers community website. I have a long and sad story, of which I am hoping you may be able to provide some extra insight into the troubles I have met with my Nexus 4.
I purchased my Nexus 4 (sans rubber feet) last year in August, bought from a Mediamarkt in Berlin during my first travels into Europe, when my Samsung SII met a cruel and drunken fate. When I first got the shining glittering Nexus 4, it notified me of an OTA system update, and doing as instructed I glibly pressed "Update". After the digital progress bar's needle finished injecting its panacea into the phone, it restarted and was then caught in a boot-loop. Frantic, repeated, turning off and on procedures followed, like I was trying to perform CPR at a crash scene. It was out like a light, except its light was still on in the shape of a glowing "X". After trying all the system/cache/data wipes the system tools would allow me, nothing made it budge. I resorted to flash everything to stock with fastboot to successfully get it up and running again, but it was a bad start to a troubled relationship.
A flight back to my home in Australia and some months later (about March this year) I decided to try the OTA update again. I figured after some time, surely they'd have fixed the OTA issues, no? Alas, soft-bricked again -- the glowing "X" taunting me once more. I tried and I tried with all my might to flash all number of versions of Android -- 4.2, 4.3, 4.4 -- using all manners of manual and automated (toolkit) methods, all to no avail. I put the phone in my drawer and borrowed a house mate's iPhone 4, replete with cracked screen.
Fast-forward to a few days ago: my house mate's own Nexus 4 kissed gravity and it was more an expression of a troubled break-up than any affection. She needed her iPhone back and I went back to no phone. There was some kind of bliss in being disconnected, however being a freelance designer and developer, my life-line is work and work is often received and completed via phone duties. Wondering if I could successfully defibrillate life back into this still-new and handsome looking Nexus 4, then the better I would be than without phone. I plugged it all in again, performed a manual flash of KOT49H to finally see past the rotating dots to view the android fellow lying on his back getting some much-needed TLC from some futuristic blue polyhedron tumbleweed. I was "in with a grin" -- the phone and I were back in business.
Lazing about one hung-over Saturday morning with my phone plugged into the charger, me checking out my family and friends' inane burblings on Facebook, the phone winked a red eye at me and went black. I was confused. What happened? Was it something I said? Posted? I tried to turn it on again, and yet silence persisted. It was plugged into the wall, power was on -- there should be juice present within this ripe fruit.
Holding it in my questioning hands, I shakily brought it over to my computer and plugged it into the USB. I tried turning it on again, and the eyes fluttered open, its stare fixated and blank, a rotating vision of 4 dots tumbling in an endless mocking loop. I sighed, "Not again." I tried more methods of flashing and restoring the phone's version of Android, both manual and automated. Nothing. Nada. Zip. Ziltch. Zero.
Here I am, again at the precipice of uncertainty with this phone's status and fate. No activity beyond those dots locked in an eternal dance of emptiness. The drapes of its consciousness are pulled, no vision of what's on stage or who's singing. Silence. Empty space. Lingering thoughts of my involvement bounding like playful lion cubs through the savannah: "if only I...", "if only it...", etc.
So here, dear reader of an esteemed Android developer community website, I petition you in great need and distress: if perchance you may be able to offer some insight into my troubled 'droid; if maybe there's some way to read some console output of what and where the errors are occuring; if perhaps there's something more physical that could be the cause of such pain and strife. I wish to understand my companion's feelings and thoughts more, to know why it feels such despondency in living and working, and how I may be able to coax it back to consciousness. Perhaps all it needs is to have some other sort of love and kindness, the type I'm potentially not adept at speaking in a language for it to understand. Either way, I would love any information someone may be able to proffer.
Please help me XDA developers -- you're my only hope.
Click to expand...
Click to collapse
tl;dr is the phone rooted ?
fahadsul3man said:
tl;dr is the phone rooted ?
Click to expand...
Click to collapse
No
So after skimming through your jibber jabber the problem is the phone gets stuck in the boot loop no matter what method you used ? Try using different ROM instead of the KOT49H I am assuming you are out of warranty by now right ?
Sent from my Nexus 4 using Tapatalk
Hey guys,
I'm one of the app idea finalists in the LG/Xda qPair Developer Challenge. This will be my placeholder thread for up date to date info, for you all to give ideas/help/criticism.
My app is called qLink.
I am a student of Florida Tech and dev in my free time but never made an app to this scale. This will be a challenge for me but I will complete this app to the best of my ability. I work, am a full time student, and run a charity so i will do my best to keep you updated daily on progress but my response times here may be slow. Just know I am always working on this every day.
i do not have much in terms of pictures yet but will get screenshots up soon.
Whats Working
I haven't gotten the tablet yet so who knows
Some design work
Left To Do
Get the tablet to determine whats working
So what's the goal of your app?
EnergyUK said:
So what's the goal of your app?
Click to expand...
Click to collapse
to have a qpair alternativ which will work on aosp devices
EnergyUK said:
So what's the goal of your app?
Click to expand...
Click to collapse
That'll be updated with the screenshots this weekend. My app is actually impossible via my og method so I'm figuring out a rework (hackish way).
ckret said:
to have a qpair alternativ which will work on aosp devices
Click to expand...
Click to collapse
Lol maybe my next app
I'll get mine tomorrow hopefully. Good luck!
Dri94 said:
That'll be updated with the screenshots this weekend. My app is actually impossible via my og method so I'm figuring out a rework (hackish way).
Lol maybe my next app
Click to expand...
Click to collapse
so then i dont know what your app will do
maybe you could explain it or something like that?
Hey guys. So my original app was going to be to let you actually answer the call from your tablet and use it as bluetooth headset sort of way. However this is not possible due the bluetooth drivers not having ad2p sink enabled even though the tablet is capable. My app will now be a full fledged text client for your gPad. you can see all the texts on your phone and send and reply just as you would with any client on your phone. Development is going good. I have the mechanics of the phone part of the app down. No UI yet, just the code working (so no possible screenshots). I now need to learn how how xml files work to successfully sync the texts with your tablet. That should be done by next week and then i can implement sending the texts from your tablet to your phone. After i will begin building the UI based on Material Design.
The rate this is going is fast so if i complete this soon i will be accepting more (simple as i am a complete beginner) app ideas to do with qPair. I will also be getting back into ROM cooking and hopefully bring a big surprise to the GPad community. This is a learning experience for me, not a competition. So I'm welcome to all help. I will try to keep this thread updated as much as possible, I am a full time FIT student, I have a part time job, and also run my own business, so I have a lot on my plate lol.
Dri94 said:
Hey guys. So my original app was going to be to let you actually answer the call from your tablet and use it as bluetooth headset sort of way. However this is not possible due the bluetooth drivers not having ad2p sink enabled even though the tablet is capable. My app will now be a full fledged text client for your gPad. you can see all the texts on your phone and send and reply just as you would with any client on your phone. Development is going good. I have the mechanics of the phone part of the app down. No UI yet, just the code working (so no possible screenshots). I now need to learn how how xml files work to successfully sync the texts with your tablet. That should be done by next week and then i can implement sending the texts from your tablet to your phone. After i will begin building the UI based on Material Design.
The rate this is going is fast so if i complete this soon i will be accepting more (simple as i am a complete beginner) app ideas to do with qPair. I will also be getting back into ROM cooking and hopefully bring a big surprise to the GPad community. This is a learning experience for me, not a competition. So I'm welcome to all help. I will try to keep this thread updated as much as possible, I am a full time FIT student, I have a part time job, and also run my own business, so I have a lot on my plate lol.
Click to expand...
Click to collapse
Hi I'm also part of the challengers so I'm gonna have app ready and create dev thread once it's ready.
I'd suggest you'd learn a bit about ContentResolvers and http://developer.android.com/training/sync-adapters/creating-sync-adapter.html
For storing data I think you should look up on SQLite (and access it through ContentResolver such as the QPair API one).
Another thing to remember with SMS/Text on KitKat that's Google changed the permissions and API a little bit. you should check out MightyText...
Also if you plan on using LG's QPair SDK the transfer between devices would require you to pass very abstract types (putBoolean,putString etc...) but not custom parcels. so you'll have to do the parsing by yourself.
About A2DP sadly it's not supported by all Android devices I've seen so far only cumbersome hacking through rooting and changing Bluetooth drivers in Kernel would allow it but again it's super complicated unless you're the phone manufacturer (Eg. Apple's Handoff)
ttg said:
Hi I'm also part of the challengers so I'm gonna have app ready and create dev thread once it's ready.
I'd suggest you'd learn a bit about ContentResolvers and http://developer.android.com/training/sync-adapters/creating-sync-adapter.html
For storing data I think you should look up on SQLite (and access it through ContentResolver such as the QPair API one).
Another thing to remember with SMS/Text on KitKat that's Google changed the permissions and API a little bit. you should check out MightyText...
Also if you plan on using LG's QPair SDK the transfer between devices would require you to pass very abstract types (putBoolean,putString etc...) but not custom parcels. so you'll have to do the parsing by yourself.
About A2DP sadly it's not supported by all Android devices I've seen so far only cumbersome hacking through rooting and changing Bluetooth drivers in Kernel would allow it but again it's super complicated unless you're the phone manufacturer (Eg. Apple's Handoff)
Click to expand...
Click to collapse
Thanks for the tips. I'm going to look into content resolvers and have been looking into sqlite... Yea my app would have to be default on the phone unfortunately unless i find a hackaround but the table portion would appear as a normal app and require no extra permissions. I've created my own sms class for the apps to send the data between another so i wouldn't have to deal with apis I'm unfamiliar with... And i know. I looked into that. I do have one workaround but not the skills yet necessary to make it. I'll be doing that as i learn more.
Ive gotten the texts backup configured for the most part. Im in the testing phase of that. once i do ill begin actually building the app UI and have test builds out for everyone. After ironing out whatever bugs you report and any additional reportings, ill begin taking requests for more apps, and also trying my hackaround to get calls routed through the tablet.
Another round of bug fixes completed. Nearing release stage
Background of app done. Now creating UI according to material design
My workaround for sending sms will not work without root unfortunately so i am now creating a full text app. So that's why it's taking longer than expected. Sorry guys. Be patient with me. I have final exams in two weeks
What is the design concept for your app? did you do some work for UIs?
Yea but there is a bug in it and since exams are next week i haven't worked much at all. It will be minimal material design with hopes for a theme store.
I just realized the contest is over. Sorry guys. With exams, work, managing my seperate business, and still trying to live life i didn't have any time. I'm working on it again but stuck trying to find help sending a database from an array between activities. I didn't win this tablet for nothing and know i will continue working on my app even without the competition.