Fire Stick issue with Ouya Controller

Hi all,

I'm trying to setup RetroArch on my Fire TV Stick with an Ouya controller, and have the controller keymap working properly. Now I am running into an issue that the left trigger is always mapped to Home on the Fire Stick, and am unable to get around it. This is problematic as I can't map the trigger to anything else, and inadvertantly pressing the trigger while in RetroArch causes the game to pause and the Ouya controller is no longer recognized after resuming.

I can see the keylayout file in /system/usr/keylayout for the Ouya controller, but can't comment out the line mapping the left trigger to home. (Not rooted).

Any ideas?

Thanks in advance.

fire stick need advice with heat

hello to all
lately my fire stick is running hot to the touch then other times is normal warm i even remove the covers so more air can flow thru but like today it's been running very hot any tips or trick to the heat dilema.?? thanks and yes i'm using original power adapter

Full easy instructions for running os remix off usb stick without errors

This is a working usb install media creator method for os remix installation circumventing all known errors made for noobs including USING full drive internal storage space etc.

You will be able to use this usb stick for future creation of other usb install media

you will have the choice to also install to hard drive

you will need 2 x usb drives and require drive write speed to be higher than 10 mb/s

the first drive will be the installer drive and the second will be the actual usb drive used to run remix os.

For first drive basic fat 32 install you will need rufus 2.9 usb boot media creator

after creation of the installer drive keep it safe i reccommend you use a 4gb drive /£2 off ebay but get something thats got a write speed higher than 10 mb/s or else install will fail!

Format the second drive to your liking ext 4 for example on your pc with minitool partition or acronis disk manager (make sure the drive is formatted as primary and set to active flag)



1. Create fat 32 usb boot disk with first usb drive and rufus 2.9 and the remix os iso
2.make sure after creation you boot up the usb drive and enter remix os
3.make sure you dont boot up the ufi version of the boot up, only use the legacy version (it will have ufi next to boot drive in bios usb boot up list)
4.after you enter remix os go to settings and download the update (ota) (this is the main fix)(if this update fails you cannot proceed further with instructions)
5. After ota update reboot and enter remix os again and let android upgrade
6.after this stage is complete your fat32 remix os usb bootable drive is ready to create a usb drive that runs remix os from the drive itself.
7.insert the second drive in a usb hub and boot up the computer with both drives in the computer and boot from the first drive (the usb remix os installer drive)
8.boot up and at the grub boot menu (it should look blue with yellow writing not the black ufi version) press tab and type: INSTALL=1
9. You will enter usb media creation menu select scan usb drives and select the second drive (the remix os running drive)
10. It will ask you what you want to format the drive as so select do not format option (becus you already formatted it)
11.then it will ask you to install first grub boot menu say yes
12. Then it will ask you to install second boot grub efi menu say yes
13. Next it will ask you if you want to format the boot partition or something like that say *** no ***
14. Then it will ask you if you want read/write privelage say yes
15. It will proceed to write the remix os onto the drive
16. When finished it will ask to restart (at this point i just switch the pc off by holding power button then restart and boot off the new second drive to run the os from it already upgraded too)



note: If wanting ntfs version of remix os then its a little complicated than this and you will need to use imgtools to increase the data.img file on the ntfs drive after creation with the first usb media creator drive.

The remix os ota update addresses the boot media creation errors. After the ota update all drives created with the grub menu installer boot up as they should but only ufi boot up option hangs!



Hope this helps hit the thanks dont forget so i know how many people were helped by this and if thats high i will continue helping happily! enjoy.

I have the ative pc pro xe700t1c the uk version with intel core i5 quad core and its also a convertible tablet with msata ssd as hdd drive and as you all probbaly know android was created for fast flash memory and linux format os so the best combination is an ssd and ext4 linux file format. I have a 64gb 544 mb/s msata drive in a usb 3.0 enclosure which i use to boot remix os and run it off it. Its perfectly smooth and fast enough and the ativ pc pro convertible laptop/tablet is fully compatible hadware software wise, no problems at all.

Full easy instructions for running os remix off usb stick without errors

This is a working usb install media creator method for os remix installation circumventing all known errors made for noobs including USING full drive internal storage space etc.

You will be able to use this usb stick for future creation of other usb install media

you will have the choice to also install to hard drive

you will need 2 x usb drives and require drive write speed to be higher than 10 mb/s

the first drive will be the installer drive and the second will be the actual usb drive used to run remix os.

For first drive basic fat 32 install you will need rufus 2.9 usb boot media creator

after creation of the installer drive keep it safe i reccommend you use a 4gb drive /£2 off ebay but get something thats got a write speed higher than 10 mb/s or else install will fail!

Format the second drive to your liking ext 4 for example on your pc with minitool partition or acronis disk manager (make sure the drive is formatted as primary and set to active flag)



1. Create fat 32 usb boot disk with first usb drive and rufus 2.9 and the remix os iso
2.make sure after creation you boot up the usb drive and enter remix os
3.make sure you dont boot up the ufi version of the boot up, only use the legacy version (it will have ufi next to boot drive in bios usb boot up list)
4.after you enter remix os go to settings and download the update (ota) (this is the main fix)(if this update fails you cannot proceed further with instructions)
5. After ota update reboot and enter remix os again and let android upgrade
6.after this stage is complete your fat32 remix os usb bootable drive is ready to create a usb drive that runs remix os from the drive itself.
7.insert the second drive in a usb hub and boot up the computer with both drives in the computer and boot from the first drive (the usb remix os installer drive)
8.boot up and at the grub boot menu (it should look blue with yellow writing not the black ufi version) press tab and type: INSTALL=1
9. You will enter usb media creation menu select scan usb drives and select the second drive (the remix os running drive)
10. It will ask you what you want to format the drive as so select do not format option (becus you already formatted it)
11.then it will ask you to install first grub boot menu say yes
12. Then it will ask you to install second boot grub efi menu say yes
13. Next it will ask you if you want to format the boot partition or something like that say *** no ***
14. Then it will ask you if you want read/write privelage say yes
15. It will proceed to write the remix os onto the drive
16. When finished it will ask to restart (at this point i just switch the pc off by holding power button then restart and boot off the new second drive to run the os from it already upgraded too)



note: If wanting ntfs version of remix os then its a little complicated than this and you will need to use imgtools to increase the data.img file on the ntfs drive after creation with the first usb media creator drive.

The remix os ota update addresses the boot media creation errors. After the ota update all drives created with the grub menu installer boot up as they should but only ufi boot up option hangs!



Hope this helps hit the thanks dont forget so i know how many people were helped by this and if thats high i will continue helping happily! enjoy.

I have the ative pc pro xe700t1c the uk version with intel core i5 quad core and its also a convertible tablet with msata ssd as hdd drive and as you all probbaly know android was created for fast flash memory and linux format os so the best combination is an ssd and ext4 linux file format. I have a 64gb 544 mb/s msata drive in a usb 3.0 enclosure which i use to boot remix os and run it off it. Its perfectly smooth and fast enough and the ativ pc pro convertible laptop/tablet is fully compatible hadware software wise, no problems at all.

Full easy instructions for running os remix off usb stick without errors

This is a working usb install media creator method for os remix installation circumventing all known errors made for noobs including USING full drive internal storage space etc.

You will be able to use this usb stick for future creation of other usb install media

you will have the choice to also install to hard drive

you will need 2 x usb drives and require drive write speed to be higher than 10 mb/s

the first drive will be the installer drive and the second will be the actual usb drive used to run remix os.

For first drive basic fat 32 install you will need rufus 2.9 usb boot media creator

after creation of the installer drive keep it safe i reccommend you use a 4gb drive /£2 off ebay but get something thats got a write speed higher than 10 mb/s or else install will fail!

Format the second drive to your liking ext 4 for example on your pc with minitool partition or acronis disk manager (make sure the drive is formatted as primary and set to active flag)



1. Create fat 32 usb boot disk with first usb drive and rufus 2.9 and the remix os iso
2.make sure after creation you boot up the usb drive and enter remix os
3.make sure you dont boot up the ufi version of the boot up, only use the legacy version (it will have ufi next to boot drive in bios usb boot up list)
4.after you enter remix os go to settings and download the update (ota) (this is the main fix)(if this update fails you cannot proceed further with instructions)
5. After ota update reboot and enter remix os again and let android upgrade
6.after this stage is complete your fat32 remix os usb bootable drive is ready to create a usb drive that runs remix os from the drive itself.
7.insert the second drive in a usb hub and boot up the computer with both drives in the computer and boot from the first drive (the usb remix os installer drive)
8.boot up and at the grub boot menu (it should look blue with yellow writing not the black ufi version) press tab and type: Install=1
9. You will enter usb media creation menu select scan usb drives and select the second drive (the remix os running drive)
10. It will ask you what you want to format the drive as so select do not format option (becus you already formatted it)
11.then it will ask you to install first grub boot menu say yes
12. Then it will ask you to install second boot grub efi menu say yes
13. Next it will ask you if you want to format the boot partition or something like that say *** no ***
14. Then it will ask you if you want read/write privelage say yes
15. It will proceed to write the remix os onto the drive
16. When finished it will ask to restart (at this point i just switch the pc off by holding power button then restart and boot off the new second drive to run the os from it already upgraded too)



note: If wanting ntfs version of remix os then its a little complicated than this and you will need to use imgtools to increase the data.img file on the ntfs drive after creation with the first usb media creator drive.

The remix os ota update addresses the boot media creation errors. After the ota update all drives created with the grub menu installer boot up as they should but only legacy ufi boot hangs!



Hope this helps hit the thanks dont forget so i know how many people were helped by this and if thats high i will continue helping happily! :) enjoy.

I have the ative pc pro xe700t1c the uk version with intel core i5 quad core and its also a convertible tablet with msata ssd as hdd drive and as you all probbaly know android was created for fast flash memory and linux format os so the best combination is an ssd and ext4 linux file format. I have a 64gb 544 mb/s msata drive in a usb 3.0 enclosure which i use to boot remix os and run it off it. Its perfectly smooth and fast enough and the ativ pc pro convertible laptop/tablet is fully compatible hadware software wise, no problems at all.

Fire Stick Hidden - 711 Page (v 0.1)

I have a Fire Stick and basic remote. I "butt dialed" the remote by sitting on it. When I looked at my TV monitor there was a diagnostic screen I never saw before on the display. The diagnostic screen information was:

711 Page (v 0.1)
1 ******** Device ********
1.1 DSN : (numbers...)
1.2 Version : 54.5.5.0_user_550145120
1.4 Time : Jul 18, 2016 1:10:13 AM
1.7 TV model : (some info on my display)
1.8 TV resolution : 640x480p @ 60 Hz

3 ******** Connection ********
3.2 AP : (info on my access point)
3.2.1 Signal : -35
3.2.2 Captive : No(0)
3.2.5 Noise : -92
3.3 Scan : 3

4 ******** Interface ********
4.1 IP : 192.168.1.161

5 ******** Internet ********
5.3 Internet reachable : Yes(1)
5.5 Amazon servers reachable: Yes(1)

7 ********Channels ********
7.1 Current channel : 10
7.2 Recommended channels
2.4 Ghz: 9
5.0 Ghz: 48

8 ******** Fire HD10 Keyboard ********
8.1 Connection status : -1

At the bottom were three buttons: [Reconnect] [Reboot] [More]

The [More] button brought up a new dialog window, with a spinner. After spinning for about 2 minutes the following displayed:
More
Throughput: 37.78 +/- 24.99 Mbps

So I was wondering if someone could figure out what buttons on the remote cause these dialogs to display?

Maybe a developer using "strings" on some internal libraries tricks or other?

Thank you. Otherwise, FYI only.

Screen + back stick out, blurry pictures... Problem thread

Hey guys,
it seems that every smartphone i own breaks after ~18 months... Now my Z3 is finally gone, i guess.

Problems:

• Blurry Pictures, i guess a coating of the lens went off?


• One "system UIDs inconsistent" error, since then, whatsapp had "damaged databases" for at least 20 times - factory resettet twice, no difference


• REAL bad touchscreen response from time to time. It either doesn't detect inputs at all or thinks you already lifted your finger. Super annoying, especially when typing.


• Glas on front AND back is getting loose. The adhesive doesn't hold the phone together anymore

I can shrug off the first two problems (that's something i could have lived with), but not with the bad adhesive tape (??) that doesn't hold the phone together properly. You can look under the screen, it's not that far out (yet!) on the backside of the phone. Has anyone had that problem before? The phone was looked after well, i haven't dropped it, it was ALWAYS in a case. It had a glass screen protector until the touchscreen response got too bad (it didn't get any better after i removed it though).

As for my bad luck, i dropped the phone for the first time ever about an hour ago, since then the power button can't be pushed in properly anymore. The screen survived it miraculously, even though it sticks out quite a bit. I wanted to send it in for repairs next week.

Attached Thumbnails

 


 


 


 

[Request] Backup App for rooted FireTV (Stick)

I search a working Backup App was backup App inkl. Data on a rooted FireTV-Stick

Have tested Titanium, but this will not work.

Today my Stick in Living Room has restarted and all Apps with Data are gone and i must all make new. Root, Busybox and Xposed are present so its format only Data and SD-Card Partition
And to prevent this, i want have a fully Backup so i can restore my Apps with data same as Titanium with a phone/tablet

My hope is i can clone it from my Stick in Kitchen

Fire TV Stick 'Not in Range' of Router?!

Hello people! I wanted to see if anyone else has been having any similar problems as I have been having.

I have had TWO different Fire TV Sticks recently that have been unable to connect to a WIFI connection. Both of them were very close to the routers. They both had the same message when I attempted to connect to the WIFI connection: 'Not In Range'.

I typed the WIFI password in with all lowercase and then all caps. I reset the stick. I even restored the stick back to the factory defaults. Nothing worked.

Any ideas?

:confused:

First time Rooting, vs98611a, advice? Should I update first or stick with 11a?

So, I've never rooted a phone before, a tablet yes, but that was almost 10 years ago. I can follow instructions, and am technically literate, but I'm worried about bricking my phone, so simple is better. Basicly I have an verizon LG G4 that I want to root. Primarily because I need to do some GPS spoofing, and mobile hotspot stuff. The version is 11a, Should I be trying to update that first? or is there a guide out there somewhere? I've found this thread

HTML Code:

---

http://forum.xda-developers.com/g4/orig-development/root-tmo-vzw-intl-variants-soon-root-lg-t3164765

---

Is this what I'm looking for?

I'm not sure if my software version matters or will limit my root options in anyway. Thanks in advance!

Screen Dim - stick

Has anyone else noticed if their Fire TV Stick looks dimmer than other streaming sticks and box? I have a Samsung BluRay player connected to same TV. In general the picture looks dimmer on the FireTV stick.

Should I stick with the N5 for another year? Or upgrade to one of the incoming nexus?

I have a Nexus 5 (16gb) since december 2013.
The battery life isn't amazing, and the limited storage & ram are bothering me sometimes.
But other than that - it works pretty well till now, and i'm satisfied with the 1080p resolution.

Should I spend 500$+ on a new nexus? just for more storge & ram (and more of "Google's support" maybe)?

PlayStation Vue Authentication on Fire TV vs Stick

So, I have been connecting to Vue behind a DD-wrt router so that I could access Chicago local networks. I don't live in an area where I can receive local channels OTA.

I have no trouble with the connection through Fire Sticks, but the PS4 and Fire TV box will not allow for authentication. I imagine this is because the hardware in those devices allows for a more complex authentication process and Sony is turning back folks from accessing their servers through VPN's.

Here's what happens:

Fire Sticks when connecting via VPN router - works like a charm.

PS4 and Fire TV box when connecting through VPN router - "There was an error during authentication. Please try again later. Press EXIT to close application."

Here's the part that may tell us something: ALL of the above devices, when connecting through my regular, non-VPN router, all return the message stating that I am currently not connecting in my home area, if I click "yes" a new home area will be established and I will no longer be able to use the old area. Again, all of the devices do that, including the Fire TV box and the PS4.

The question I have for the hive mind is: assuming it's an authentication issue, can I defeat or trick the authentication process? Is there a way to fool Sony's servers into thinking I am not, in fact, behind a VPN? Perhaps I need a different/better VPN?

Thanks for the thoughts, folks.

Install Fedora on Amazon Fire stick.

Hello everyone, Can I ask is it possible to install Fedora on Amazon Fire TV stick? I have rooted my stick. Thank you!

Modded Google play store, Fire Stick

Okay this is my first tutorial, so be patient.

I do not accept any responsibility for any damage this my cause.

Hi this is a tutorial for installing the modded Google play store on the firestick.

You need to be rooted in order to do this so do that first there are plenty of guides on here.

So here we go.

1. You need to download 2 applications, lucky patcher and Rotate screen orientation. I got these on Google play store

LUCKY PATCHER
http://s000.tinyupload.com/index.php...57159237994684
SCREEN ORIENTATION
http://s000.tinyupload.com/index.php...00727199415238

2. Transfer the apk files to the fire stick, I do this via my Dropbox but do what works for you.

3. Install both applications on the fire stick.

4. Run rotate screen orientation and make it active via onscreen instructions.

5. Open lucky patcher and click toolbox (at the bottom)

6. Now go to install modded Google play store.

7. Now click Modded Google play store 5.1.11 and click install as user app.

8. Click install

9. System will reboot then vuala you have modded Google play store to download all paid apps for free.
[emoji2] [emoji108]

Small problems.
1. Google play doesn't always open using the original fire TV menu but fire starter works perfect for me
2. May need mouse to use lucky patcher, I used mouse toggle.

Massive problems
1. My fire stick is now to good with Google play
2. I have to many apps to choose from [emoji56]

If anyone needs help or runs into problems please comment.

Notification ring tone choice will not stick

New P9000 and updated to 2016-05-31. Have set a notification ring tone as default in setting. However, system will not use it and I think uses the factory notification ring tone instead. It appears in the sound & notification section. I can change and hold the phone ringtone and can change ringtones for the contacts. Any ideas on how to spank this baby and make it use my notification choice? Thanks..