Database Develop

Review & Fixes for [ROM] IncDoes Sense "Desire HD"

My findings and fixes on the Desire HD ROM by IncredibleDoes with fixes maintained as they're collected from the community to help those with issues as well as provide those with information whom might be interested and are "on the fence".
After having run v0.2.1 but unable to get MMS working I decided to wait. While v0.3.0 or v0.3.1 does not fix MMS, there is a procedure that does fix the issue (listed below). I did not have my sdcard formated with an A2SD sd-ext partition and was awaiting IncredibleDroid's completion of v0.3.1 which does not require an sd-ext partition. However, after it was completed, many reported that they had no signal and a few other major issues. I had already backed up my sdcard and created an sd-ext partition but was hoping I could use the non-sd-ext v0.3.1 but with the issues posted regarding the v0.3.1 build, I decided to stick with the original v0.3.1 build that required the sd-ext partitioned sdcard and suggest you do too at this point.
First let me start with a big thanks to IncredibleDoes and a link to his main thread for you to get the latest updates and other information: IncDoes Sense "Desire HD"
Remember, a FULL wipe of data & cache is required.
So if you've skipped this process...start over rather than post any issues you may have.
Device Setup
My device info:
HBOOT v0.92
Radio 2.15.00.07.28
First, some have asked if having their sdcard formatted FAT32 was sd-ext - the answer is no.
Second, if you get the following error message:
Can't mount /dev/block/mmcblk1p2 (file exists) 3 times, then
Can't mount SDEXT:
Failure at line 12:
copy_dir PACKAGE:ext SDEXT:
Installation aborted
Then you need to create an sd-ext partition.
Creating a sd-ext partition:
I tried to use the SD Partition option in ROM Manager but it did not work. It was suggested by ID to use Amon_RA's recovery image which was actually a very simple process.
NOTE: Unlike many downloads, you will actually need to read & follow the instructions properly. This is an actual .zip archive that you will need to extract the PB31IMG.ZIP image and place on the root of your sdcard, not simply rename it.
Once you boot into the Amon_RA recovery you should create a 512MB sd-ext partition and a 32MB swap file. You will need to select the SD:ext2 to ext3 option, then SD:ext3 to ext4 option to create the properly formatted sd-ext partition.
There is a link posted to an Android and Me article that shows how to do it via a command line but that's by far taking a more difficult approach.
The Amon_RA recovery is quite nice but if you have neen using the ClockworkMod recovery and want to flash back to the ClockworkMod recovery, the PB31IMG.ZIP ClockworkMod image can be found here "http://unrevoked.com/rootwiki/doku.php/public/forever" near the very bottom.
My Review
Three second boot:
I find this has been highly over rated. Since the phone is not completely shut down, it is not actually booting up. A restart or battery pull will provide you with the same boot speed that you are used to seeing.
Since the Shutdown option does not actually shut the phone down, people are complaining about having to do battery pulls to get back into HBOOT. While ROM Manager will reboot into Recovery, HBOOT is a different story. The way I have found to do this is to long press on the power button and select Restart. Once the lighted buttons below your screen goes out, press and hold the volume down button to boot into HBOOT.
MMS fix:
Use the provided files by es0tericcha0s but after installing APN Backup & Restore you need to delete the APN settings from the ROM before you restore the provided backup .xml file. This will fix the MMS issue in v0.3.0 (and possibly other build versions if broken).
Credit to es0tericcha0s for the post & files and to pd240 whom pointed out that the APN settings needed to be deleted before you restore the .xml file. Thanks!
Battery life:
In originally writing this yesterday (before the digital gremlins hit XDA), I had made a 1.5hr phone call using BT, downloaded just under 500MB of data over Wi-Fi for the Locations app (more info on that below), sent/received about 30 SMS messages, received about a half dozen e-mails, browsed the Web for awhile, watched a couple YouTube videos, streamed music over Y! Music & Slacker to test (but not for very long) and had GPS on for a bit. While I've seen several people complain of battery use, I did not see poor battery issues and was quite surprised since the 500MB download itself took well over an hour.
Call screen & Phone:
While broken in v0.2.1, as stated in the ROM's OP, these work 100% as expected in v0.3.0. Tone sounds for voicemail etc. work properly...all issues in this area are fixed. I believe that I read there were some issues with v0.3.1 however but I am not sure as I don't recommend that version anyway.
Camera & Camcorder:
Still broken as ID's OP states however it is different in v0.3.0 than it was in v0.2.1. In v0.2.1 the app would launch then quit back to Sense. In v0.3.0 it launches to a black screen and does not quit back to Sense and the back button does nothing. After pressing the Home button I used Astro's Tools to kill the Camera process and have since not futzed with the camera.
Chrome to Phone:
With many ROM's I have had trouble getting this to work and this was no exception. I figured out last nigh that even though I had played the Disconnect, uninstall, reinstall C2P game over & over without any success as well as logging out and back in with the extension in Chrome (Mac version) I had finally found the issue. Once I uninstalled the Chrome C2P extension, restarted Chrome and reinstalled the C2P extension and logged back in via Chrome, my phone was flooded with link notifications! All along I thought it was a device issue.
Date format:
I've seen people asking if the Calendar app states the actual day in the Agenda & Day views rather than just the date. The answer reported was no. This is not entirely correct. The date format set in the System Settings is a global setting. Whatever you choose is used for the lock screen, notification bar, clock widget as well as the Calendar app. Kind of odd but there you go!
Notifications:
With all of the ROM's I've run, none (even the 2.2 OTA) provided proper SMS, FeedR etc. "unread" counts. This new version of Sense does which is nice.
Also, for those not aware, recen apps are now listed along the top of the notifications panel in a sliding ribbon once dropped down. Could be useful if you remember that they're there.
Connected Media:
This is a cool central hub for the media (music, photos & videos) on you device as well as that which is "connected" to your device (e.g., via your Wi-Fi connection). In v0.2.1 this worked very well and was the only media app I used since it launches the required Gallery, Music & Video's apps as needed. Something cool I noticed is that it saw my DirecTV HD receiver. Now, there was nothing it was able to play on it but it makes me wonder if one had Hulu or Netflix setup through an Xbox 360 or Windows box, could it possibly stream that content? I don't have any of that setup to test but kind of looks promising.
UPDATE 9/26
via dgourd
Just to help clarify:
This is a DLNA addition to the phone, so it can basically communicate with any other DLNA device. I can confirm that it works since I have a Windows Home Server in my house which supports DLNA. My Incredible can find all my music and videos. It will only display files it supports though. For example, it can play all my mp3 songs and mp4 videos, put my mkv videos are unplayable since it is not natively supported.
Click to expand...
Click to collapse
Unfortunately, there are some things that work differently in v0.3.0 with the Connected Media app. The photos aren't able to view full screen without first looking at a photo that was in a linked Facebook album. Once a photo was looked at in a Facebook album, photos on my device would display when the thumbnail was tapped. However, quitting the app would force you to go through the same steps again (this applied to videos too).
In addition, if there wasn't an sdcard installed, the app cannot see any media even if it's stored within the device itself. I do not know if this applies to the individual apps themselves (too lazy to bother at this point).
HTC Hub:
This is a cool idea from HTC that with an HTCSense.com account allows you to preview and download many items for your device. Everything from Skins (themes), Widgets, single Sounds and even full Sound Sets that you can listen to before you bother to download them. Pretty nice.
HTC Likes:
Access to apps that other HTCSense.com users can comment as well as "Like" (think of Facebook's "Like" button). There are recommended apps as well and this should rally take off once HTCSense.com launches!
Locations:
While I have no use for it, people were asking about this app so I gave it a shot. As I launched the app it wanted to download maps before it would work. The maps it wanted were just under 500MB (as stated above). After downloading the maps, there were several categories displayed as one would expect (gas stations, restaurants etc.) but selecting these provided a "no locations found" message then prompted to tell me that I needed to download updated maps (WTF?). The maps for the Western U.S. were over 800MB and I did not bother so I cannot go any further with how this app works...sorry.
Market:
I think it was a CM6 ROM I had installed that asked if I wanted Google to keep track of my data & settings that I answered yes to. This new ROM does the same and something nice was that after installing the ROM, all of my apps were automatically downloaded for me. Very nice! Now, since I had installed v0.2.1, I had already setup my System Settings, these too were restored during the v0.3.0 ROM install (but not any app settings).
The Verizon tab is replaced with a "Downloads" tab and many Verizon apps are not available for download (NFL couldn't be found, nor Skype, My Verizon etc.). Kind of a bummer for some.
Quick Lookup:
This is a cool app that will lookup what you've typed in the search box. Sure, sounds boring but, you select from where it searches from the ribbon at the bottom. Your choices are: Wikipedia, Google, YouTube, Translate and Google Dictionary.
Quadrant:
For those interested in Quadrant scores...first run 1108 second run 1168.
Streaming Audio:
As mentioned above, both Y! Music and Slacker streamed just fine through the external speaker. I was told that Slacker sounded tinny using headsets but I did not confirm this.
Web Browser:
Looks a bit more polished. Using Wi-Fi YouTube videos played smoothly (unlike the YouTube app below). There's a new checkbox setting for animated .gif files which is unchecked (off) by default. I did notice in the 2.2 OTA that animated .gif's do play now, I guess this simply lets you choose to turn them on or off for speed. If you pinch the window down, it gets displayed just as though you selected Windows from the Menu button which is handy if you're in the habit of using multiple windows (which I'm not).
YouTube:
The YouTube app is broken in so far as you cannot log into your account. When you try, after selecting your account from the popup, the app just sits there and you're unable to do anything without hitting the back button. I tried this both over 3G and Wi-Fi with the same results. Also, when choosing an HQ video from my YouTube Favorites from the main site it was very choppy & not worth watching (unlike in the browser above but that was at 360 not HD). None the less, the Gymkhana THREE Part 2 video that's at the top of the YouTube app currently plays just fine in HD so other than the inability to login, I'm confused why some HD plays and others do not (but do on the 2.2 OTA).
Well, there you have it. After a second write-up (now over 8 hours of time spent) I hope this is of some use to the community. Since it was suggested I create a thread for this so that the information did not get lost in the main ROM thread I think it will be useful. If there's something other than trying different kernels or over-clocking that you would like me to try & add, please let me know. I will keep this updated as best as possible.
X

Useful Links
[ROM] IncDoes Sense "Desire HD"
ROM Thread
IncredibleDoes Twitter account
http://twitter.com/IncredibleDoes
Tested Kernels
KiNgxKernel [2.6.32.15] [HAVS] [BATTFIX] [BFS] [OC] [UV] #5
Hydra Kernels - Stock Undervolted used by ID but that doesn't meant you can't run an overclocked kernel
Skins
via touchpro247
Donate to IncredibleDoes

i had a weird issue, one specific to this rom, and it ended up being the deal breaker for me
i have a california phone number, but recently moved to the midwest. on EVERY other rom ive used, across two different phones, this hasnt caused an issue, my messages and clls all read the right time. however on this one, my recieved texts messages were reading as california time. since the messaging app uses conversation style messaging, i would have to scroll up through two hours of my texts to find a text that i just recieved.
it was insanely annoying. that coupled with the camera killed it for me. i dont use the camera much, but the two in conjunction were just too much.
i tried pushing the old htc messaging app and using that, but no cigar.

the verizon tab issue can be fixed easily with some build.prop mods btw. im not familiar enough with the INC yet to give you the changes off the top of my head, but with the eris, the issue was solved by editing the ro.product.name and ro.product.device i believe

Just need camera to work and it will be perfect! Already is the best Rom for me
Sent from my Incredible using Tapatalk

Thank you all for helping!!
ID

es0tericcha0s said:
i had a weird issue, one specific to this rom, and it ended up being the deal breaker for me
i have a california phone number, but recently moved to the midwest. on EVERY other rom ive used, across two different phones, this hasnt caused an issue, my messages and clls all read the right time. however on this one, my recieved texts messages were reading as california time. since the messaging app uses conversation style messaging, i would have to scroll up through two hours of my texts to find a text that i just recieved.
it was insanely annoying. that coupled with the camera killed it for me. i dont use the camera much, but the two in conjunction were just too much.
i tried pushing the old htc messaging app and using that, but no cigar.
Click to expand...
Click to collapse
I wonder if doing a *228 option 2 would help by setting the proper local tower info for your phone? Have you tried this? I know ID said this was a GSM ROM which confuses me that it works at all (at least from my BB days) but I guess it's quite an apples & oranges comparison for Android OS to BB OS.
X

xwera43 said:
I wonder if doing a *228 option 2 would help by setting the proper local tower info for your phone? Have you tried this? I know ID said this was a GSM ROM which confuses me that it works at all (at least from my BB days) but I guess it's quite an apples & oranges comparison for Android OS to BB OS.
X
Click to expand...
Click to collapse
i didnt even think to try that, it may work. ill have to give it a shot later. thanks

I just wanted to say thank you for writing this review. It is a process to go create a EXT4 partition on an SDCard so I have been hesitant. This is well written and I really hope you take it upon yourself to write more reviews about new roms in the future. I think I might have to check out the next version of this Desire HD rom when he releases it. I can't wait for this to officially show up on our Incredibles in the future and get optimized to our liking by some of these guys.

Locations:
While I have no use for it, people were asking about this app so I gave it a shot. As I launched the app it wanted to download maps before it would work. The maps it wanted were just under 500MB (as stated above). After downloading the maps, there were several categories displayed as one would expect (gas stations, restaurants etc.) but selecting these provided a "no locations found" message then prompted to tell me that I needed to download updated maps (WTF?). The maps for the Western U.S. were over 800MB and I did not bother so I cannot go any further with how this app works...sorry.
Click to expand...
Click to collapse
I have a hypothesis...I'm downloading a premium navigation map update right now.

es0tericcha0s said:
i didnt even think to try that, it may work. ill have to give it a shot later. thanks
Click to expand...
Click to collapse
It kind of makes sense to me...Sure hope it works!
X

tdavis42 said:
I just wanted to say thank you for writing this review. It is a process to go create a EXT4 partition on an SDCard so I have been hesitant. This is well written and I really hope you take it upon yourself to write more reviews about new roms in the future. I think I might have to check out the next version of this Desire HD rom when he releases it. I can't wait for this to officially show up on our Incredibles in the future and get optimized to our liking by some of these guys.
Click to expand...
Click to collapse
Thanks!
The partitioning after reading the command line process was a no go for me. While I would have no trouble doing it, it was just too much work. The fact that ROM Manager was failing was a bummer too but the steps I took were very simple. Being that I had 10GB on my 32GB sdcard was the most time consuming portion (about 20 minutes to back it up from an adapter & an hour to re-write the data). Partitioning was/is pretty easy.
Also, now that the ROM is in ROM Manager, that should be helpful too (even though it's a tad under 200MB).
X

douger1957 said:
I have a hypothesis...I'm downloading a premium navigation map update right now.
Click to expand...
Click to collapse
I wasn't taken to a premium option, just a simple menu selection of map locations (World wide). Being basically homebound, an additional 800MB+ was just kind of silly.
X

Great write-up. ID has done a very nice job porting this rom.
Thanks!

Shutting down is fixed now!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I know this is a review about the Rom itself, but what about including reviews of optional kernels that work the best. Such as Kings #5 or Hydra etc

xwera43 said:
I wasn't taken to a premium option, just a simple menu selection of map locations (World wide). Being basically homebound, an additional 800MB+ was just kind of silly.
X
Click to expand...
Click to collapse
It's not obvious how to do it. I asked about it in the other Desire HD thread.

Cached maps!
Sent from my Incredible using XDA App

littleguevara said:
I know this is a review about the Rom itself, but what about including reviews of optional kernels that work the best. Such as Kings #5 or Hydra etc
Click to expand...
Click to collapse
I'm planning on adding those to the second post. Links based on user input whom have tried kernels. If you have some input on kernels you've used, please post it and I'll update the second post with link info.
X

IncredibleDoes said:
Click to expand...
Click to collapse
Nice ID!
X

App Requires Phone Number work around

I tried to install the verizon fios dvr manager/remote control - the application however requires a cell phone number - does any one know a work around to create a "fake number" on the nook to use these apps?
Thank you

xtrezpasor said:
I tried to install the verizon fios dvr manager/remote control - the application however requires a cell phone number - does any one know a work around to create a "fake number" on the nook to use these apps?
Thank you
Click to expand...
Click to collapse
I would also like to get something like this working for Google Voice so that I can use the messaging service.
Any and all help is appreciated.

I signed into my google account and google voice "just worked". Of course i can't make any calls but i can use it to send texts and receive texts sent to my gv number.
Sent from my LogicPD Zoom2 using XDA App

I think if you could lift the data/configuration from your existing phone then you could copy that to the Nook and be working. I could not find where the data was stored though for the app.

GarJones27 said:
I would also like to get something like this working for Google Voice so that I can use the messaging service.
Any and all help is appreciated.
Click to expand...
Click to collapse
I just entered my iPhone's number (which is already registered to Google Voice and has the Google Voice app on it) and I can use it for texting just fine.

KitF said:
I just entered my iPhone's number (which is already registered to Google Voice and has the Google Voice app on it) and I can use it for texting just fine.
Click to expand...
Click to collapse
Can you give a short tutorial on how to get this set up? I too (and im sure others) would like to be able to text from the Nook.
Sent from my HERO200 using XDA App

Setup gvoice on a phone first (you should able to find a tutorial by searching google). Then use the same # when setting up on the nook.

seeddemon said:
Setup gvoice on a phone first (you should able to find a tutorial by searching google). Then use the same # when setting up on the nook.
Click to expand...
Click to collapse
Edit: Okay, set up Google voice and I'm able to send texts using that number however the apps that require a phone number do not see it. Not a huge deal, but there might be more apps out there that require a phone number to work.
I simply set up Google voice via the Google.com/voice website. And then got a Google number to use for texts. In the voice app you can compose a message and my Google contacts are available.
Sent from my Nook Color.

This isnt what what I was looking for - I was looking for a way to use verizon Fios manager...

hijacked
I agree this thread was hijacked. We want a workaround for the Android verizon manager on the kindle fire or nook color where the app was meant for a mobile phone. Would there be a way to give a rooted device a phone number?

3EyedPhish said:
I agree this thread was hijacked. We want a workaround for the Android verizon manager on the kindle fire or nook color where the app was meant for a mobile phone. Would there be a way to give a rooted device a phone number?
Click to expand...
Click to collapse
Depending on the ROM your running, you may be able to enter a phone number in the settings.... otherwise you may be able to edit TelephonyManager.smali and find the section to pull the phone number and hard code a phone number in the same way we do IMEI edits.

DizzyDen said:
Depending on the ROM your running, you may be able to enter a phone number in the settings.... otherwise you may be able to edit TelephonyManager.smali and find the section to pull the phone number and hard code a phone number in the same way we do IMEI edits.
Click to expand...
Click to collapse
I got the FIOS app to run on my Nook by doing the reverse of this. I found the few places in the app where the phone number was looked up and replaced those by calls to get an apps prefs setting "Display Name" which is entered during set up but unused by the app. So I put in the phone number under Display Name during set up.
This was done using apktool to patch the app but I am reluctant to post the modified version as this is explicitly ruled out by license agreement.
I did consider going the TelephonyManager route but as I am using CM9 which is still changing quite a bit then that becomes a moving target. If CM9 puts explicit coded support in for entering a number like CM7 did then that would be the best option. I did find, however, when using the CM7 option that it had a tendency to lose the entered number during reboots.

You can set a phone number, IMEI, location and many other things for each individual app with PDroid without modifying any code on those apps.
All you need is to enable the PDroid framework. There are packages in Botbrew for Nook or you can use the auto-patcher if you have Linux.
The above links are for CM9. If you have cm7 there are auto-patchers for Linux and windows, which can be found at the PDroid thread.

mateorod said:
You can set a phone number, IMEI, location and many other things for each individual app with PDroid without modifying any code on those apps.
All you need is to enable the PDroid framework. There are packages in Botbrew for Nook or you can use the auto-patcher if you have Linux.
The above links are for CM9. If you have cm7 there are auto-patchers for Linux and windows, which can be found at the PDroid thread.
Click to expand...
Click to collapse
That looks like a better more general method. In checking this out I also notice that Verizon did do an update a couple of weeks ago where the FIOS remote app claims it has a new pairing method which works with non-phone tablets so maybe this isn't needed any more for this particular app. I'll try that out.

It is a pretty neat program, with a ton of functions and uses that go pretty unnoticed.
One note, though: due to an update in the CM repo, our auto-patcher ( and even the patches I used to make the auto-patcher) broke.
I have updated everything for CM9, but we are waiting on an aokp build before releasing another version of the auto-patcher.
But the Botbrew packages are up to date and can be used immediately for 5/08 and the patcher will be updated soon.
If you are running an older build, make sure the package you use matches the build date. And the auto-patcher still works to builds from 5/06 and earlier.

bobtidey said:
In checking this out I also notice that Verizon did do an update a couple of weeks ago where the FIOS remote app claims it has a new pairing method which works with non-phone tablets so maybe this isn't needed any more for this particular app. I'll try that out.
Click to expand...
Click to collapse
I tried out the new version of the Verizon app and it now does allow use of a 4 digit PIN as opposed to a phone number for setting up the remote control pairing. It finds the set top box OK but then immediately crashes on the Nook Color CM9.
I'm going to do a bit more investigation and maybe try it from a Touchpad to see if that behaves the same way.

[Q] about the new Amazon Instant Video app

When the HD comes out, could somebody rip the Amazon Instant Video app apk and post it on xda?
The reason: Old app only works on Gingerbread. The new one should work on ICS and JB because the new Kindle Fire's OS is based on ICS.

Was just about to post a thread over here, we has one going on the old KF forums. ES File Explorer is on the Amazon market and should be able to read the /system/app directory without root. Really hoping this apk works on other ICS/JB devices.

An update bin file was posted and I grabbed the apk file from that. So far no luck, it FCs on my Touchpad with CM9. I tried installing as a regular app making sure Voodoo had me unrooted. I also tried as a system apk and rebooted, still FCs. It refuses to install on GB so I imagine its using API Level 15.
Hopefully it just needs another apk installed, Ill play around with it and see if I can get it working.
EDIT: I installed aLogcat to see if I could narrow down what is causing the FC. Its looking for the class "amazon.unifiedsettings.UnifiedSettingsHelper" which doesn't exist. Later in the log the FC is caused by a fatal exception with the class "amazon/unifiedsettings/UnidifedSettingsHelper" not being found. Is this a lib file or a system apk it wants?
EDIT2: I gave up on it for now. I tried some lib files, tried installing as many apks as I could (didn't try replacing system apks). It still FCs with the same error log and I can't find any files that reference unified settings. I also downloaded the Kindle Fire 2 update file (the updated original fire) and its using the same APK. LCD Density for the HD is 240 and 160 for the regular Fire 2. I use 160 on my Touchpad so that shouldn't be the issue.

How does one get apks out of Amazon's .bins?
com.amazon.dcp.apk
MyAccount-unsigned.apk
AccountAndSyncSettings.apk
These are the three extra apks (in addition to video apk itself) I needed to get it running on my Nook Tablet back in the day. I noticed back then that it seemed to work a little different for everyone. Some folks didn't need any of those while others of us experienced all manner of crashing without some of them. Sadly, one also forced my NT to appear as a KF in the Amazon app store, which made some of my purchased apps incompatible. Caveat emptor.
Would love to see those posted though if someone gets around to it. Would also love to see Amazon get their rear in gear and release a prime streaming app for android that didn't require all the fuss.

The bin files open for me in WinRAR, I think they are just zip files. AccountAndSyncSettings.apk is gone from the new Kindle Fires, the other two files are still there. I remember using those 3 files before allowed you to add an Amazon account and then open the app and you would already be logged in. With the new 2 files, it FCs in settings when I try to add an Amazon account. I didn't try using the old GB apks, it may be worth a try as they allowed an Amazon account to be added even on ICS.
I'll upload them, there is only 2 now, because you may have a different outcome than me on a different device.

No luck on a simple side load to an Acer A700 or an Acer A100 both stock and unrooted running ICS. I am reluctant to try the other apk's because I also had my a100 appear as a kindle fire and had to restore it to get use of my apps that were not kindle compatible.

I was messing around on my Touchpad with CWM so I always have the option to restore a nandroid if I were to screw something up. But I played around with it a lot this morning and didn't do any damage, everything was FCing.

No luck on Nexus 7. Tried after installing all three apk.
Sent from my Nexus 7 using Tapatalk 2

I too am looking to stream amazon on my cm9_tp but did not see anyone mention the fact it works perfectly on WebOs.

rfauconn said:
I too am looking to stream amazon on my cm9_tp but did not see anyone mention the fact it works perfectly on WebOs.
Click to expand...
Click to collapse
I will work through a flash capable browser with a desktop user agent in Android as well, but its not optimized very well for mobile devices. The app is much nicer when it works. At this point we may be better off trying to get the GB version working in ICS since it will at least open and let you browse.

In addition to a better UI in the app, I've also experienced intermittent, albeit minor, audio sync issues with mobile flash that I never had in the app. I hate that.

can someone with a kindle fire hd open up the app and then post the log? Wouldn't we be able to see where the unifiedsettingshelper file was with the log of it opening successfully?

Any update on this?
Sent from my Transformer Prime TF201 using Tapatalk 2

We need a Fire HD user or somebody with more knowledge of how things work to figure out where we can get "amazon.unifiedsettings.UnifiedSettingsHelper" from. This is the missing service it crashes on. I can't find any lib files or apks from the ROM that fix this issue. Also even if we get past this crash error another one may appear. At this point I'm thinking we may be better off trying to get the old GB app working since it seems to have fewer issues. It allows you to open and browse to videos on ICS, also allows you to add your Amazon account to the device, but crashes when you go to play a video. Its having a database issue according to the crash log posted over in the GB thread:
http://forum.xda-developers.com/showpost.php?p=31633773&postcount=193

spunker88 said:
We need a Fire HD user or somebody with more knowledge of how things work to figure out where we can get "amazon.unifiedsettings.UnifiedSettingsHelper" from. This is the missing service it crashes on. I can't find any lib files or apks from the ROM that fix this issue. Also even if we get past this crash error another one may appear. At this point I'm thinking we may be better off trying to get the old GB app working since it seems to have fewer issues. It allows you to open and browse to videos on ICS, also allows you to add your Amazon account to the device, but crashes when you go to play a video. Its having a database issue according to the crash log posted over in the GB thread:
http://forum.xda-developers.com/showpost.php?p=31633773&postcount=193
Click to expand...
Click to collapse
could amazon.unifiedsettings.UnifiedSettingsHelper be part of one of the odex files in system/app ?

It will be fantastic once this can be resolved. I hate that they are allowing this on iOS but not on other android devices.

Yes, it is absurd that iPad has access and general android devices are SOL. We purchased our content...and can't watch it reliably (app access). I would encourage everyone to let amazon know this is unacceptable - and I'm hopeful the good people here find a fix for us in the mean time.

Gonzorito said:
Yes, it is absurd that iPad has access and general android devices are SOL. We purchased our content...and can't watch it reliably (app access). I would encourage everyone to let amazon know this is unacceptable - and I'm hopeful the good people here find a fix for us in the mean time.
Click to expand...
Click to collapse
I tried giving Amazon some feedback on supporting other Android devices - they didn't seem to care much. I guess they want to sell more Fires, but if they're selling them at a loss wouldn't they make more profit by supporting their app on other devices?

Our how about, I purchased my kindle to read, purchased a tablet before the fire was a gleam in their eye.
I purchase video content and have limited access to it, so i won't purchase future content with amazon as a result.
No I won't buy a fire and I am encouraged to buy my future content through Google play on top of that!
Loss, loss, and more loss for Amazon. Doesn't make sense.
Sorry for side tracking the thread, I will end the QQ

Gonzorito said:
I would encourage everyone to let amazon know this is unacceptable - and I'm hopeful the good people here find a fix for us in the mean time.
Click to expand...
Click to collapse
Yup. Of course they aren't going to listen to any one complaint, but Amazon is a pretty responsive company on the whole. Squeak enough and they'll grease the wheels. There's no indication they want to make this fire-only, given how many other devices its on, it's just a question of priority. You can bet the apple people whined more than the android people, so if you want them to get it in gear get on their contact page and make the request. I've done it repeatedly, but we need more people to get noticed.

Request for xposed module to enable screen casting on any capable device

I think Google is holding out on some of us that have newer phones with the encoder, and older phones and tablets like the n7 '12. Could someone with programming experience try to make an exposed module to enable it on all phones and let the users decide if it really works instead of old mother Google?
Sent from my Nexus 7 using Tapatalk

I'd like to know if its just the decoder or if individual handsets have to be whitelisted as well. I noticed the cast screen menu doesn't appear for non compatible devices but is there a script reference to handest model that can be changed.

The first thing to try is editing the build.prop
If that works, an xposed module can spoof this.

Edited my xoom build prop. Which now shows the option to cast screen however the play services FC . Looking at the logs it appears to be a egl error. So its likely the xoom just won't work.
But if someone wants to try on a newer device just change the info to reflect a hammerhead and reboot to see if it works
sent from::§::

Which prop?
Not uncommon for it to crash if there is no decoder. Same thing happened to my RAZR HD MAXX

runandhide05 said:
Edited my xoom build prop. Which now shows the option to cast screen however the play services FC . Looking at the logs it appears to be a egl error. So its likely the xoom just won't work.
But if someone wants to try on a newer device just change the info to reflect a hammerhead and reboot to see if it works
sent from::§::
Click to expand...
Click to collapse
I did the same and experienced the same play services crash...using HTC Droid DNA....was hoping the approved list of devices was just preliminary and that many current smart phones would be capable somehow but its seeming more and more that there may not be a mod or workaround to this.

Ya, same here
Sent from my Nexus 7 using Tapatalk

Downgrading Play Services to stock version on Moto X enables the cast screen option...
http://forum.xda-developers.com/moto-x/general/chromecast-mirroring-moto-x-t2810937/post54042606

fndpena said:
Downgrading Play Services to stock version on Moto X enables the cast screen option...
http://forum.xda-developers.com/moto-x/general/chromecast-mirroring-moto-x-t2810937/post54042606
Click to expand...
Click to collapse
:good:
I totally agree with your sentiment on that thread about changing build.prop. Doesn't take much to forget that you're "spoofing" another device, then accidentally load the wrong version of something critical (like
a recovery) using a tool that just looks at build.prop
I also tried my favorite device spoofer, Market Helper (not the one for Titanium Backup), which does not change build.prop, but that did not seem to make any difference, which makes sense since the Chromecast app seems to look at build.prop rather than whatever the Play Store looks at.
I wonder if someone smart could write a Cydia Substrate module to just spoof the device ID for the Chromecast app similar to how Root Cloak Plus can hide root just for certain apps. I'm not sure which framework is better suited for the task.

bhiga said:
:good:
I totally agree with your sentiment on that thread about changing build.prop. Doesn't take much to forget that you're "spoofing" another device, then accidentally load the wrong version of something critical (like
a recovery) using a tool that just looks at build.prop
I also tried my favorite device spoofer, Market Helper (not the one for Titanium Backup), which does not change build.prop, but that did not seem to make any difference, which makes sense since the Chromecast app seems to look at build.prop rather than whatever the Play Store looks at.
I wonder if someone smart could write a Cydia Substrate module to just spoof the device ID for the Chromecast app similar to how Root Cloak Plus can hide root just for certain apps. I'm not sure which framework is better suited for the task.
Click to expand...
Click to collapse
Looks like the Moto X is capable of cast screen to chromecast out of the box, but Play Services 5 breaks it on this device. Probably because the feature is not really stable atm. I wish there was a way to update my Play Services back to version 5, while keeping cast screen option untouched.

fndpena said:
Looks like the Moto X is capable of cast screen to chromecast out of the box, but Play Services 5 breaks it on this device. Probably because the feature is not really stable atm. I wish there was a way to update my Play Services back to version 5, while keeping cast screen option untouched.
Click to expand...
Click to collapse
Ahh, that's unfortunate. Hopefully Google gets it fixed.

bhiga said:
Ahh, that's unfortunate. Hopefully Google gets it fixed.
Click to expand...
Click to collapse
Didn't it have to do something with the notification bar? Like if somebody installed another notification bar that error went away?

hawkeye680 said:
Didn't it have to do something with the notification bar? Like if somebody installed another notification bar that error went away?
Click to expand...
Click to collapse
AFAIK notification bar issue is a different issue that affects Samsung and LG devices, possibly others.
Suppose it might be related somehow though.

Ya, but play services has been a huge inconvenience on the X with it seeping tons of battery life. So, hopefully, they'll fix it without breaking something else
Sent from my Nexus 7 using Tapatalk

Any updates? I tried changing the build.prop to reflect hammerhead on my 2012 Nexus 7 but no dice.

Try other build.props maybe an s4

abuttino said:
Try other build.props maybe an s4
Click to expand...
Click to collapse
Nothing. It seems like the check may be deeper than that.

It's not Xposed, but check here:
http://forum.xda-developers.com/showthread.php?t=2812193
This *should* work. It definitely does make the menu pop up. Whether or not the casting works is all dependent upon the device.

ok after digging into the chromecast and google play services apk i can see whats going on here
first we obviously know that the cast apk needs our device id. however it is not searching for it anywhere in the code
of the chromecast apk. in fact its looking at
Code:
Lcom/google/android/gms/cast/CastDevice;->getDeviceId()Ljava/lang/String;
[\code]
so this is why if you grab an older play service apk its possible that this location did not excist or whatever may be the deal.
looking at
com.google.android.gms-1\smali\bkr.smali
you can see here is where the chromecast apk is getting the deviceID from gms (google play services)
[code]
invoke-virtual {p0}, Landroid/telephony/TelephonyManager;->getDeviceId()Ljava/lang/String;
[\code]

runandhide05 said:
ok after digging into the chromecast and google play services apk i can see whats going on here
first we obviously know that the cast apk needs our device id. however it is not searching for it anywhere in the code
of the chromecast apk. in fact its looking at
Code:
Lcom/google/android/gms/cast/CastDevice;->getDeviceId()Ljava/lang/String;
[\code]
so this is why if you grab an older play service apk its possible that this location did not excist or whatever may be the deal.
looking at
com.google.android.gms-1\smali\bkr.smali
you can see here is where the chromecast apk is getting the deviceID from gms (google play services)
[code]
invoke-virtual {p0}, Landroid/telephony/TelephonyManager;->getDeviceId()Ljava/lang/String;
[\code][/QUOTE]
Dude, check out my app. It just enables 'gms:cast:mirroring_enabled' in '/data/data/com.googlegoogle.android.gsf/databases/gservices.db' by setting it to 'true'. Apparently that's enough to enable the options and streaming. :D
It was a lucky find, if I do say so myself.
Click to expand...
Click to collapse

Working: Hidden 'Cast Screen' on Amazon tablets [SEPT 2017]

UPDATE September 18, 2017: So I just wanted to update everyone. I still own my Fire HD 8 and I recently unlocked the bootloader to my rooted XT907 phone and flashed Marshmallow Lineage 13. I also acquired a Fire 7 rooted and also with a custom ROM, Fire Nexus (From XDA). I also now have a Samsung Galaxy S7, unlocked from carriers and rooted. I am happy to report, with the right app, the entire thing works perfect across all devices, rooted or not.
Please see this final update to this thread regarding the function of screen mirroring/casting.
My current device list:
-Fire HD 8, 2016 - No root, bootloader locked, stock ROM, Lollipop 5.1
-Fire 7 2015 - Rooted, bootloader locked, custom ROM, Fire Nexus Lollipop 5.1
-Motorola Droid Razr M, XT907 - Rooted, bootloader unlocked, custom ROM, Lineage Marshmallow 6.0
-Samsung Galaxy S7 - Rooted, bootloader locked, stock ROM, carrier unlocked and not attached to one, Nougat 7.0
I can screen mirror to and from every one of these devices now. It appears the more recent devices have the functionality intact, including the Amazon HD 8, and possibly the rest (see the above link to my update). RemoDroid uses the actual built in 'cast screen' software to capture and send. If you pull down the statusbar, and look at your quick settings, you will see the 'cast' icon is turned on and in use by RemoDroid. Just make sure the devices are all on the same Wifi network and the process should work. If it doesn't, one of your devices isn't compatible and likely won't be. You can thank Google, your manufacturer and your service provider for that. They won't rewrite your OS so you're likely to be locked out of screen mirroring indefinitely.
1) Download RemoDroid and install on your HD 8 and or 7
2) Install RemoDroid on a device that has ability to screen mirror, but no software to do so (Like the HD 8 or 7)
3) Make sure both devices are on the same WiFi network. Start the app on both devices. If rooted, grant the app root access. On the HD 8 and 7, ignore the no root warnings.
4) On the HD 8 or 7, tap 'stream', ignoring the warnings.
5) On your other device, tap connect. In a few seconds your HD 8 should appear on the list. Tap it. Your HD 8 or 7 screen is now being mirrored to your device :highfive:
6) On that device, tap the back button and tap ok to stop the connection. On the HD 8 or 7, stop streaming.
7) On your other device, tap 'stream'
8) On the HD 8 or 7 tap 'connect' and select your other device from the list. You are now mirroring to your HD 8 or 7. :highfive:
Video Here
-----------------------------------------------------------------------------------
***OLD***: It's exactly what it sounds like. I was, and am still looking through the various activities and their settings that Amazon has hidden from us (Using Activity Launcher) This particular find is my favorite...so far.
It's called 'Cast Screen.' It can be found in the Settings drop down activity menu. On my Fire HD 8, android 5.1.1, it's called 'Cast Screen' and on KitKat it's 'Wireless Display' (Owned by Miracast). You are supposed to be able to cast let's say video or whatever you want, from your phone to a tablet or TV...or from a tablet to phone or TV. They are both blocked by the manufacturer and I read you needed root at least until 5.0 to get access to it.
I have tried a few apps that only activate it in the form of a shortcut, and others that are supposed to use that advantage to cast your screen. So far I've not been able to get it to work From what I can tell, it relies partially on Blue tooth and partially on WiFi. Both devices have to be on the same Wifi network, and both have to be 'discoverable' in Blue Tooth. Check and Check. This launcher does a great job at opening these hidden features, but Amazon also does a good job of making them hard to use and you can't make them into a shortcut without a 3rd party app. On both 5.1.1 and Kitkat, the interfaces are very very basic and I can't find any settings to toggle in the 'apps.'
How would I go about making this functional? I can't find any APKs related to them on the device. And I can't find away to bring the player out as a standalone app/setting, even with root on my phone. This would really make a cool addition/feature for these tablets if I can get them working.
The properties are:
Name: 'Cast Screen' on Lollipop 5.1.1
Package: com.android.settings
Class: com.android.settings.Settings$WifiDisplaySettingsActivity
Icon: com.adndroid.settings:mipmap/ic_launcher_settings
Name: 'Wireless Display' on KitKat 4.4.2
Package: com.android.settings
Class: com.android.settings.Settings$WifiDisplaySettingsActivity
Icon: com.adndroid.settings:mipmap/ic_launcher_settings
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

DragonFire1024 said:
It's exactly what it sounds like. I was, and am still looking through the various activities and their settings that Amazon has hidden from us (Using Activity Launcher) This particular find is my favorite...so far.
:
Click to expand...
Click to collapse
It's a feature native to Android 5.x. Amazon disabled it in favor of their own proprietary solution. Unlikely the underlying code is included with FireOS. Need a custom ROM for that. Sorry, mate.

Davey126 said:
It's a feature native to Android 5.x. Amazon disabled it in favor of their own proprietary solution. Unlikely the underlying code is included with FireOS. Need a custom ROM for that. Sorry, mate.
Click to expand...
Click to collapse
It's pretty much "available" on a vast majority of Android devices. The problem is, there's more than one line of code missing. In some cases, several and not just in the build.prop. Each service provider is different. Even the strongest mirror casting apps can't get it to work. This one for example even asks for SU permissions on my rooted Moto Razr M XT907, yet still fails.
There are several lines from the XML code that are missing or marked as 'false,'. Unfortunately I have to research more to understand how to edit the Method Flow with Zygote. Each XML is different from one person and device to the next, so this isn't something that will be easy.
As most have not been lucky, I seem to have gotten further than most. At least I managed to get the button to show up in settings:

I managed to find a debugging option which supposedly forces the cast screen/wireless display to work. I just have no clue what to do with it. I just spent hours trying to figure out how to place this where it needs to go and pretty much got no where. Any thoughts?

Well I thought I had made some progress. Well I had. I managed to get half of the screen cast to work by using RemoDroid. I installed both apps, one on my Fire tablet and the other on my XT 907. For about a minute or less, I am able to cast my screen from my XT907 to my tablet, before RemoDroid freezes and crashes. However, I had exactly the opposite effect when I cast from my tablet to my phone. Much to my surprise the tablet worked perfectly. Remo brought out the casting very well. I was actually very surprised by that. I also tried All cast and was able to get that to work, but not good at all yet. You can't cast youtube videos because the site thinks you minimized the app so the video never plays. I also can't figure out how to cast screens in Allcast.
I was really excited and had planned to do an awesome write up on all this today, but found myself still piecing together the damn code. So far I managed to come up with a tiny bit of code for the build.prop, which I can only apply to my XT907 because the tablet isn't rooted and I am unable to push files back to the system without SU. Still haven't gotten my XT907 to cast though. Still a work in progress.
#property to enable user to access Google WFD settings.
#
debug.wfd.enable=1
ext_only.debug=1
persist.sys.ext_only.debug=1
persist.sys.hwc.ext_only=1
persist.sys.hwc.disable=1
Click to expand...
Click to collapse

Warning: That build.prop addition didn't go with my phone too well. Or I mounted it wrong. Nonetheless I am pretty sure I just bricked my XT907. Thank god I didn't have anything on it.

I think I realized the issue. I very well could have remounted the wrong build.prop. so that will pretty much screw my phone. I'm pretty sure there's no recovery from that.

Perhaps I should wait until my battery isn't dead to make assumptions *facepalm* Awaiting full charge and will give results.

Nevermind. I've tried every possible option. Still won't boot.

Ok A few things before I work on recovering my phone from ever lasting bootloop or lack thereof. I can confirm, without a doubt, Screen Cast ability is ACTIVE in Amazon Fire tablets. I am pretty sure the option applies to most newer models. There are a few things you can check, which I'll get to in a moment. In the coming days, or weeks (hopefully sooner rather than later) I will be writing a detailed analysis of Miracast...or what we are being or were being made to believe what Miracast is/was. I think many will be disappointed because I think most of us had a certain vision of what Miracast is, or the perception of it, when in fact it appears to be quite the opposite.
So without spilling too much beans, let me just say this: you can blame the manufacturers and or service providers of your devices and even Google itself. Because all of them have been actively covering up this technology, though not for the reasons you might suspect. The entities involved with Miracast or Wireless Display or Cast Screen (pick your name), have done a lot of work and went through an extensive amount of trouble to do everything they can to hide the feature from you and almost completely disabled it altogether. Some actually have. Ok here is proof it exists on Fire tablets.
1) /system/build.prop In the Fire 8, some of the code you find on the web to enable Wireless Display, is already part of the hardware. So if you're root, I'm not sure there is much more you can do to the build.prop to activate it, aside from a line or two and that will vary with devices.
2) XML aka your Android Source Code. Google, at least in the past, went through extensive work to cut off Wireless Display from their devices. A user (developer?) on GitHub, RC3 kensuke has gone through his own extensive work at tracking down what was 'wrong' in the Android source that stopped Wireless Display (Miracast) from functioning. He has created tools, which I believe no longer function, to go through and make the necessary corrections, but does list some files and fixes you can try, at your own risk. You can also browse the chapters on the list to the right, that will take you through the steps to activate it, assuming it was done in your Android source.
One final thing: I've tried dozens of apps and to be honest, very very few work. They try so hard, but some information in the necessary places is just too little for the displays to function. So if you've tried Casting apps or screen sharing apps, or you've downloaded the shortcuts or makeshift Miracast sinks, and couldn't get them to work, or function very poorly, the above is why. If the hardware and code don't exist on your device, those apps and what not WILL NOT WORK. 95% of these apps require root or a custom rom and rely heavily on the available code and information your devices carry. Even then, With my rooted XT907, still couldn't get it to work.
I really do hope I can get a functioning cast system for everyone. I am doing my best and I'll share more info with you in time.
There is so much more to this and so many details and screenshots I will share with you in the coming days and or weeks.

Ok So Here is confirmation that at least the Fire HD 8 with 5.3.3.0 has Cast Screen operational. Anyone can check this to see if it exists on their device, however you need ROOT to edit it.
1. Download a file manager and install it. My preference is Total Commander. (APK: click here).
2. Open Total Commander. Navigate to the ROOT folder, system, then click once on build.prop. I found it much easier to read and scroll using a build.prop editor. Especially if I change anything in that file. One mistake like a period out of place or wrong spacing, you WILL brick your phone (I did a few days ago and remounted it wrong and unmounted /system/ instead. Luckily I was able to recover). (BuildProp Editor: click here). (APK: click here).
3. closer to the bottom, you will see some additions that enable Cast Screen, Wireless Display etc. The props are as follows (Note: I am not sure the syntax listed in the prop is correct. I think the '_' are supposed to be periods. This might be how they are able to hide it from us? If not, then I have no clue whatsoever how they hide it from us).
persist.debug.wfd.enable=1
ro.mtk_wfd_support=1
ro.mtk_wfd_sink_support=1
ro.mtk_wfd_sink_uibc_support=1
ro.mtk_wfd_hdcp_tx_support=1
wfd.dummy.enable=1
Click to expand...
Click to collapse
This is just part of the puzzle and some of the many many pieces to get this to work. The good thing is, this makes it very easy to use the service to cast to another device, if you can get it to connect to one. I have had very little success with that thus far.
******I AM NOT RESPONSIBLE IF YOU BRICK YOUR DEVICE(S)******

Ok. After hours and hours of editing XML and build.prop, I've failed yet again and it resulted in my phone getting bricked, again. I have a few more ideas, but it's not looking too good. Google sure made sure we wouldn't get access to this and are doing a good job on my end.

DragonFire1024 said:
Google sure made sure we wouldn't get access to this and are doing a good job on my end.
Click to expand...
Click to collapse
Amazon and Google have their own proprietary solutions; no surprise Miracast has been depreciated in generic Android builds. Likely legal and/or business considerations as well. Roll back a dozen+ posts; outcome was largely predictable. If it were easy someone would have already uncorked the Genie.

Davey126 said:
Amazon and Google have their own proprietary solutions; no surprise Miracast has been depreciated in generic Android builds. Likely legal and/or business considerations as well. Roll back a dozen+ posts; outcome was largely predictable. If it were easy someone would have already uncorked the Genie.
Click to expand...
Click to collapse
I know it's not easy. Didn't think it would be. I think the two biggest issues are:
1) the information and workarounds are scattered far and wide. I've pages and pages of links to fixes and edits etc. Nothing, and I mean nothing, is in one spot. My hope is to bring all of that together in one spot and in working order if at all possible.
2) Google has gone through a lot of trouble and effort to block access to this function. The amount of changes and or edits to the various source codes are extreme to say the least. Though most of the edits are very small, usually a few characters or a single line addition or subtraction, the amount of them makes this task nearly​ impossible.
With that being said, my next step is to go through a phone I just got solely for testing purposes (it's a UMX. Probably the deepest you can get in the barrel) and to copy over the build properties that allow it's screen cast/wireless display to work. It has Marshmallow 6.0. unfortunately I can't find a root for it though.
I also started a thread in the XT907 forum in hopes someone with the same device, has a prop and XML where Miracast etc is operational. That would make things easier.
I also can't figure out how Amazon is blocking the Cast Screen from working or launching. All of the props are there, but I haven't looked at the XML to see what that says.

So I just realized, after my second brick on my XT907, it was the first time after a full firmware reflash, that I went immediately to root. I did it before I turned on Wifi and before I added an account to my device. So I never got any updates to my device, OTA wise, since the actual build date of the phone. So I decided to take a good look at all my settings today, something I normally do when I get a new device or restore it. I found some interesting info.
Example: My build.prop is totally different than the one I was editing before. The WfdConfig XML files, are completely different. Well half different. Both of the two were the same as before the reflash, well half. Now I see a bunch of text following the properties to enable Wireless Display in the wfdconfig.xml
PHP:
<DynamicBitrateAdaptation>0</DynamicBitrateAdaptation>
<SendKeepAlive>1</SendKeepAlive>
<RTSPPort>5550</RTSPPort>
<EncyptNonSecureContent>1</EncyptNonSecureContent>
<PerformanceLevelTurboMode>1</PerformanceLevelTurboMode>
<BitrateTable>
<AAC>
<BIT0>
<MaxBitrate>256000</MaxBitrate>
<MinBitrate>256000</MinBitrate>
</BIT0>
<BIT1>
<MaxBitrate>384000</MaxBitrate>
<MinBitrate>384000</MinBitrate>
</BIT1>
<BIT2>
<MaxBitrate>512000</MaxBitrate>
<MinBitrate>512000</MinBitrate>
</BIT2>
</AAC>
<CEA>
<BIT0>
<MinBitrate>1000000</MinBitrate>
<MaxBitrate>4000000</MaxBitrate>
</BIT0>
<BIT1>
<MinBitrate>1000000</MinBitrate>
<MaxBitrate>4000000</MaxBitrate>
</BIT1>
<BIT2>
<MinBitrate>1000000</MinBitrate>
<MaxBitrate>4000000</MaxBitrate>
</BIT2>
<BIT3>
<MinBitrate>1000000</MinBitrate>
<MaxBitrate>4000000</MaxBitrate>
</BIT3>
<BIT4>
<MinBitrate>1000000</MinBitrate>
<MaxBitrate>4000000</MaxBitrate>
</BIT4>
<BIT5>
<MinBitrate>2500000</MinBitrate>
<MaxBitrate>10000000</MaxBitrate>
</BIT5>
<BIT6>
<MinBitrate>5000000</MinBitrate>
<MaxBitrate>20000000</MaxBitrate>
</BIT6>
<BIT7>
<MinBitrate>5000000</MinBitrate>
<MaxBitrate>20000000</MaxBitrate>
</BIT7>
<BIT8>
<MinBitrate>10000000</MinBitrate>
<MaxBitrate>40000000</MaxBitrate>
</BIT8>
<BIT9>
<MinBitrate>10000000</MinBitrate>
<MaxBitrate>40000000</MaxBitrate>
</BIT9>
<BIT10>
<MinBitrate>5000000</MinBitrate>
<MaxBitrate>10000000</MaxBitrate>
</BIT10>
<BIT11>
<MinBitrate>5000000</MinBitrate>
<MaxBitrate>20000000</MaxBitrate>
</BIT11>
<BIT12>
<MinBitrate>5000000</MinBitrate>
<MaxBitrate>20000000</MaxBitrate>
</BIT12>
<BIT13>
<MinBitrate>10000000</MinBitrate>
<MaxBitrate>40000000</MaxBitrate>
</BIT13>
<BIT14>
<MinBitrate>10000000</MinBitrate>
<MaxBitrate>40000000</MaxBitrate>
</BIT14>
<BIT15>
<MinBitrate>2500000</MinBitrate>
<MaxBitrate>10000000</MaxBitrate>
</BIT15>
<BIT16>
<MinBitrate>5000000</MinBitrate>
<MaxBitrate>20000000</MaxBitrate>
</BIT16>
</CEA>
<VESA>
<BIT0>
<MinBitrate>500000</MinBitrate>
<MaxBitrate>2000000</MaxBitrate>
</BIT0>
<BIT1>
<MinBitrate>1000000</MinBitrate>
<MaxBitrate>4000000</MaxBitrate>
</BIT1>
<BIT2>
<MinBitrate>2500000</MinBitrate>
<MaxBitrate>10000000</MaxBitrate>
</BIT2>
<BIT3>
<MinBitrate>2500000</MinBitrate>
<MaxBitrate>10000000</MaxBitrate>
</BIT3>
<BIT4>
<MinBitrate>2500000</MinBitrate>
<MaxBitrate>10000000</MaxBitrate>
</BIT4>
<BIT5>
<MinBitrate>5000000</MinBitrate>
<MaxBitrate>20000000</MaxBitrate>
</BIT5>
<BIT6>
<MinBitrate>2500000</MinBitrate>
<MaxBitrate>10000000</MaxBitrate>
</BIT6>
<BIT7>
<MinBitrate>5000000</MinBitrate>
<MaxBitrate>20000000</MaxBitrate>
</BIT7>
<BIT8>
<MinBitrate>3500000</MinBitrate>
<MaxBitrate>14000000</MaxBitrate>
</BIT8>
<BIT9>
<MinBitrate>5000000</MinBitrate>
<MaxBitrate>20000000</MaxBitrate>
</BIT9>
<BIT10>
<MinBitrate>3500000</MinBitrate>
<MaxBitrate>14000000</MaxBitrate>
</BIT10>
<BIT11>
<MinBitrate>5000000</MinBitrate>
<MaxBitrate>20000000</MaxBitrate>
</BIT11>
<BIT12>
<MinBitrate>2500000</MinBitrate>
<MaxBitrate>10000000</MaxBitrate>
</BIT12>
<BIT13>
<MinBitrate>5000000</MinBitrate>
<MaxBitrate>20000000</MaxBitrate>
</BIT13>
<BIT14>
<MinBitrate>5000000</MinBitrate>
<MaxBitrate>20000000</MaxBitrate>
</BIT14>
<BIT15>
<MinBitrate>10000000</MinBitrate>
<MaxBitrate>40000000</MaxBitrate>
</BIT15>
<BIT16>
<MinBitrate>5000000</MinBitrate>
<MaxBitrate>20000000</MaxBitrate>
</BIT16>
<BIT17>
<MinBitrate>5000000</MinBitrate>
<MaxBitrate>20000000</MaxBitrate>
</BIT17>
<BIT18>
<MinBitrate>5000000</MinBitrate>
<MaxBitrate>20000000</MaxBitrate>
</BIT18>
<BIT19>
<MinBitrate>10000000</MinBitrate>
<MaxBitrate>40000000</MaxBitrate>
</BIT19>
<BIT20>
<MinBitrate>5000000</MinBitrate>
<MaxBitrate>20000000</MaxBitrate>
</BIT20>
<BIT21>
<MinBitrate>10000000</MinBitrate>
<MaxBitrate>40000000</MaxBitrate>
</BIT21>
<BIT22>
<MinBitrate>5000000</MinBitrate>
<MaxBitrate>20000000</MaxBitrate>
</BIT22>
<BIT23>
<MinBitrate>10000000</MinBitrate>
<MaxBitrate>40000000</MaxBitrate>
</BIT23>
<BIT24>
<MinBitrate>5000000</MinBitrate>
<MaxBitrate>20000000</MaxBitrate>
</BIT24>
<BIT25>
<MinBitrate>10000000</MinBitrate>
<MaxBitrate>40000000</MaxBitrate>
</BIT25>
<BIT26>
<MinBitrate>5000000</MinBitrate>
<MaxBitrate>20000000</MaxBitrate>
</BIT26>
<BIT27>
<MinBitrate>10000000</MinBitrate>
<MaxBitrate>40000000</MaxBitrate>
</BIT27>
<BIT28>
<MinBitrate>5000000</MinBitrate>
<MaxBitrate>20000000</MaxBitrate>
</BIT28>
<BIT29>
<MinBitrate>10000000</MinBitrate>
<MaxBitrate>40000000</MaxBitrate>
</BIT29>
</VESA>
<HH>
<BIT0>
<MinBitrate>500000</MinBitrate>
<MaxBitrate>2000000</MaxBitrate>
</BIT0>
<BIT1>
<MinBitrate>1000000</MinBitrate>
<MaxBitrate>4000000</MaxBitrate>
</BIT1>
<BIT2>
<MinBitrate>500000</MinBitrate>
<MaxBitrate>2000000</MaxBitrate>
</BIT2>
<BIT3>
<MinBitrate>1000000</MinBitrate>
<MaxBitrate>4000000</MaxBitrate>
</BIT3>
<BIT4>
<MinBitrate>500000</MinBitrate>
<MaxBitrate>2000000</MaxBitrate>
</BIT4>
<BIT5>
<MinBitrate>1000000</MinBitrate>
<MaxBitrate>4000000</MaxBitrate>
</BIT5>
<BIT6>
<MinBitrate>500000</MinBitrate>
<MaxBitrate>2000000</MaxBitrate>
</BIT6>
<BIT7>
<MinBitrate>1000000</MinBitrate>
<MaxBitrate>4000000</MaxBitrate>
</BIT7>
<BIT8>
<MinBitrate>500000</MinBitrate>
<MaxBitrate>2000000</MaxBitrate>
</BIT8>
<BIT9>
<MinBitrate>1000000</MinBitrate>
<MaxBitrate>4000000</MaxBitrate>
</BIT9>
<BIT10>
<MinBitrate>500000</MinBitrate>
<MaxBitrate>2000000</MaxBitrate>
</BIT10>
<BIT11>
<MinBitrate>1000000</MinBitrate>
<MaxBitrate>4000000</MaxBitrate>
</BIT11>
</HH>
</BitrateTable>
<CyclicIntraRefresh>
0
</CyclicIntraRefresh>
<CIRNumberOfMacroBlocks>
50
</CIRNumberOfMacroBlocks>
<!-- To disable/enable audio stream playback
support during power suspend - 0 or 1
-->
<AudioStreamInSuspend>1</AudioStreamInSuspend>
<AudioAVSyncDelay>0</AudioAVSyncDelay>
<DisableFillerNalU>1</DisableFillerNalU>
</WFDConfig>
Not to mention this button had shown up in developer options and I have yet to find these alleged options:
I also found all the software. Yes...every piece of it, including the sink! However it doesn't appear to be compiled into anything and I'm not even sure what file types these are:
Any assistance with this would be much appreciated

Ok so I'm scratching the build.prop for now because while I realized the XML edits are correct, I can't make properties in the build for something that doesn't exist or isn't enabled in the source. I have to do more reading because I don't really understand what to do next.
That having been said, I still can't get the wireless display shortcut to properly open. Every time it does so, I get an error telling me "sorry settings had to close..." Still not sure why, but it may have to do with the absence of a sink/source.
However, there is a little light at the end of the tunnel. I have managed to successfully connect/pair my XT907 Razr M and my Fire 8 tablet, something I wasn't able to do before. The downside: I'm using an Google Play app as a sink and it doesn't work that great, but it's been the only one I've found/tested which successfully connects the devices for a period and for more than a few seconds.
Less of a light: unfortunately, as much as I don't want to say it, I haven't found a way around this without root. Now you can pull the required files aka build.prop and the XMLs from the tablet and edit them accordingly, but that's the extent as you can't remount them without SuperUser access. If there is a way to do so, by all means tell me so I can get this set up on the tablet.
The easy part: likely editing the build prop actually. Once the source is correct, it's a matter of adding the correct virtual hardware properties. I've learned through all of this, those differ from each device, sometimes as little as a number. But even that little number can brick your device....twice LMFAO.
I'm using the app to post this update so i apologize for not posting links. I will do so when I arrive home.

Ok so I found a way WITHOUT root...well sort of. I found it snooping with the terminal and found a few commands online. Need to go into ADB though. There is one problem. I tried this on the tablet and everything works, except it doesn't record.
Code:
adb shell screenrecord --help
Code:
Usage: screenrecord [options] <filename>
Android screenrecord v1.2. Records the device's display to a .mp4 file.
Options:
--size WIDTHxHEIGHT
Set the video size, e.g. "1280x720". Default is the device's main
display resolution (if supported), 1280x720 if not. For best results,
use a size supported by the AVC encoder.
--bit-rate RATE
Set the video bit rate, in bits per second. Value may be specified as
bits or megabits, e.g. '4000000' is equivalent to '4M'. Default 4Mbps.
--bugreport
Add additional information, such as a timestamp overlay, that is helpful
in videos captured to illustrate bugs.
--time-limit TIME
Set the maximum recording time, in seconds. Default / maximum is 180.
--verbose
Display interesting information on stdout.
--help
Show this message.
Recording continues until Ctrl-C is hit or the time limit is reached.
Record a demo of your screen. Make sure to specify your record time:
Code:
adb shell screenrecord /sdcard/demo.XX (XX=file name to be saved as mp4, etc)
Now when it saves, things stop working. It saves to the sdcard storage, but the file is empty and shows 00:00. I don't know what's up with that.

if you could indulge me and check my posts i would enjoy greatly ur expertise, you have gotten much further then i have but i sincerely doubt it has taken as long or been as much pain... xD this is quite nefarious and im at a loss.. i dont get how an android skin could take on a life of its own. first link my post is the last 1.
https://forum.xda-developers.com/android-tv/chromecast/workaround-fix-to-amazon-fire-tablet-t3240548
and this one goes back.,,, but if ur interested i have one from 2011 that makes me think i helped... at least bring mirrorcast to fruition in the first place. and another one from 2011 basically laying out the structure to make alexa a thing.. sry im just bored frustrated and blabbing. and im listening
https://forum.xda-developers.com/android-tv/chromecast/chromecast-prerooted-android-4-4-2-t3061705
just frustrating when i give constant feedback and help evolve then get thrown under the bus. hope u know what i mean.
~unemployed and hungry

ManiaC00L said:
if you could indulge me and check my posts i would enjoy greatly ur expertise, you have gotten much further then i have but i sincerely doubt it has taken as long or been as much pain... xD this is quite nefarious and im at a loss.. i dont get how an android skin could take on a life of its own. first link my post is the last 1.
https://forum.xda-developers.com/android-tv/chromecast/workaround-fix-to-amazon-fire-tablet-t3240548
and this one goes back.,,, but if ur interested i have one from 2011 that makes me think i helped... at least bring mirrorcast to fruition in the first place. and another one from 2011 basically laying out the structure to make alexa a thing.. sry im just bored frustrated and blabbing. and im listening
https://forum.xda-developers.com/android-tv/chromecast/chromecast-prerooted-android-4-4-2-t3061705
just frustrating when i give constant feedback and help evolve then get thrown under the bus. hope u know what i mean.
~unemployed and hungry
Click to expand...
Click to collapse
I actually haven't been able to get any further. However I just discovered where some of the Wireless Display lies. /system/framework/framework-res.apk. I might try to edit it later today. I only glanced at a file or two and saw the option that disabled Wireless Display. As soon as I firgure out how to edit it without failing at reinstalling, I'll post about it.

DragonFire1024 said:
I actually haven't been able to get any further. However I just discovered where some of the Wireless Display lies. /system/framework/framework-res.apk. I might try to edit it later today. I only glanced at a file or two and saw the option that disabled Wireless Display. As soon as I firgure out how to edit it without failing at reinstalling, I'll post about it.
Click to expand...
Click to collapse
Which fire are you trying to get this work on?
I have not been involved in any way in the fire dev. But found this thread researching getting screen cast to work for a ported rom on my phone. The stock rom has cast working and the port does not(slim6).
I do have a fire 7in 2015 (5th gen) loaded with slimLP. It has screen cast working.
If there is something I could pull for you to look at let me know.