Hi Guys,
As I have a really opportunity to get me a Nexus 9 32GB + Google dedicated keyboard for a stunning price, I was wondering if it is possible to cast/mirror it's display to a VP be it wired or wireless.
I will root it and I am also almost sure to install a custom ROM to it...
I intend to use it to display my .ppt slides on the University/School VP.
Those usually have a Wi-Fi network, but it's sometimes a real nightmare to get the L/P to connect and, even when I have those, it's sometimes difficult to get a reliable connection to that Wi-Fi network.
Given these considerations, I would like to know if it is possible to cast/mirror the Nexus 9 display to a VP.
It seems that when it came out, the Nexus 9 could not output anything via it's USB port (no SlimPort nor MHL support). Is this still correct or has this been addressed by Google ?
Will I be able to cast/mirror with a Chromecast ? I had the "old" Chromcast but that required to be connected to the internet permanently, so I could not use it... Does the "new" Chromecast allow to cast/mirror directly from the Wi-Fi ?
Will I be able to cast/mirror with Miracast ? It seems that does not require an external netwark as it provides it's own network, but when it was released, it seems the Nexus 9 wasn't compatible with Miracast... There have been some workarounds, but those are for Android LP. Has this been adressed by Google or are the tricks reported here and there also working on Android MM ?
I would really appreciate you answers... and yes, I have done some research, but the results seem to be old (more or less when the N9 was released).
Regards.
NexusPenguin
I think Google doesnt support Miracast tech in their new products. It wants to sell Crapcast to everyone. I read somewhere on xda thats possible to enable Miracast trough root and editing some files.
Found on reddit
If you're rooted, add this to your build.prop. It will re-enable wireless display
persist.debug.wfd.enable=1
Or non root method not confirmed
Grim-Sleeper5d,
You don't even technically need to be rooted. All you need is an unlocked boot loader. You can then use "fastboot boot twrp-2.8.7.2-angler.img" to start TWRP recovery mode.
And from there use "adb shell" to access your device. You can edit either "vi /system/build.prop", or "vi /vendor/build.prop". Make sure you told TWRP to mount these partitions.
Wysłane z mojego GT-I9295 przy użyciu Tapatalka
Hi Ewa12321,
Thanks for your reply.
I have seen the link, but that is for Android LP isn't it ?
Do you if it's going to work with Android MM ?
Regards.
Enable Mircacast feature on Nexus 9
Has anyone tried successfully to enable this feature?
Renate NST said:
You don't need to modify /system/build.prop
You only need to add that property as persistent and you can do that in /data/property with setprop.
Code:
C:\>adb shell
[email protected]:/ $ su
[email protected]:/ # setprop persist.debug.wfd.enable 1
[email protected]:/ # reboot
On the Nexus 9, after you reboot you need to click the enable Wifi Direct box on the Screen Mirroring setup.
Click to expand...
Click to collapse
SGH-i200 said:
Has anyone tried successfully to enable this feature?
Click to expand...
Click to collapse
it enables it but then crashes as soon as i try and connect to my firetv stick
Related
I bought this nice minicomputer - MK812 Mini PC Dual-Core Android Camera Mic BT 4.2.1 and I relied on the fact that since there is Android 4.2 installed, I can use switching users, but unfortunately this function is disabled. I need to get it to work.
Of course, I googled. This is what I've already tried:
http://www.pocketables.com/2013/03/how-to-enable-multiple-user-mode-on-cyanogenmod-10-1-and-some-other-android-4-2-2-roms.html
The problem is that this command pm get-max-users returns Unknown command get-max-users.
Furthermore, when I enter SetProp fw.max_users 8, it has no effect, even after a reboot. The command pm usernameyouwanthere create-user is also without effect.
http://forum.xda-developers.com/showthread.php?t=2187934
App - 4.2 Multiple users feature enabler
This app can't be installed by Google Play (apparently MK812 is not a compatible device). Since I couldn't get APK anywhere to download, I downloaded the source code and compiled it and generated APK. Unfortunately, can't be installed either.
I studied the source code and found out that even if i was able to get it installed, it wouldn't have worked anyway, because this app runs similar commands (as those above) instead of the user.
https://play.google.com/store/apps/details?id=fahrbot.apps.switchme
This could be a solution even for Android 4.0 and 4.1. It works, but switching takes too long, because it requires a reboot and this switching is not integrated into the system. So I do not want it.
Do you know of any other solution or anything what I could try?
I googled again, found this - http://forum.xda-developers.com/showpost.php?p=34362377&postcount=8
But setting fw.max_users=8 in /system/build.prop haven't helped either.
Unfortunatelly they answer me, that MK812 mini pc does not support multiple user function. So I have to use SwitchMe Multiple Accounts
H0w4rd said:
Unfortunatelly they answer me, that MK812 mini pc does not support multiple user function. So I have to use SwitchMe Multiple Accounts
Click to expand...
Click to collapse
try
"setprop fw.max_users 8"
Lower-Case setprop without the quotes.
Edit: I see, can you and are you willing to get the source, modify it, build it and flash it? I'm going to have to enable it for my phone so when I figure out what needs modifying I'll let u know.
hey.. since i switched from pershoots (i guess it were his) builds to the official cm nightly builts (which merged his work)
i cannot load my tablet on a normal usb port while it is turned on.. just with the ac adapter or if i turn it off
this renders my accupack useless.. is this behaviour planned or just an accident?
i wanted to post this in the cyanogenmod forums first but since they don't provide a forum for this device i thought this would be the place to ask
It's blocked for some security reasons, you have to enable it again, go to your terminal emulator app(if you don't have it install from play store) or ADB
Type:
su
echo 1 > /sys/class/power_supply/battery/force_usb_charging
Now you should be able to charge your tablet via an USB port
thank you very much.. it is all working now. i don't really see the security feature but okay.
Sent from my GT-P7500
Tyrado said:
thank you very much.. it is all working now. i don't really see the security feature but okay.
Sent from my GT-P7500
Click to expand...
Click to collapse
Don't worry about it, as long as it's working it's okay
I have been reading recently about people wanting to know how to enable a wi-fi hotspot from their Axon 7 without being prompted from their provider (T-Mobile, AT&T, etc.) to change/upgrade their current data plans. Well, today I will give you a step by step guideline on how to bypass this. Please note, though, that your device must be rooted. In addition, I strongly recommend that you do a backup of your device just in case something goes wrong.
To begin, download the following apps to make this process as painless as possible Material Terminal and BuildProp Editor.
1. Launch the BuildProp Editor app and tap the menu icon (the 3 vertical dots) found on the top right of your screen. When the dialog box appears, tap on + New.
2. When the + New system property dialog box appears, under the first subheading Name type in the following: net.tethering.noprovisioning. In the next subheading named Value, type in the following: true. Once completed, press SAVE. You may be prompted to give BuildProp Editor root access. Choose GRANT and exit the app.
3. Launch the Material Terminal app.
4. In the first command line, type su and then tap enter to give it root access.
5. When the next command line appears below, type settings put global tether_dun_required 0 and then tap enter. Please note that there must be a space between the words settings and put, put and global, global and tether and required and 0. You will not believe how many people type this all as one word.
6. Exit the Material Terminal app and reboot your device. If the steps were followed carefully, you should now be able to use your device as a wi-fi hotspot without being prompted on your connecting devices to change/upgrade your data. This method should also work on other android devices.
Enjoy!
My device (A2017U) isn't rooted. It uses Cricket (AT&T) MVNO. I can use mobile hotspot without any modifications. I just assumed everyone else could, too.
Most on this phone aren't rooted.
Sent from my ZTE A2017U using Tapatalk
markwebb said:
Most on this phone aren't rooted.
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
That's okay. This only applies to those who are rooted and interested in doing this. I just thought I would help out.
rczrider said:
My device (A2017U) isn't rooted. It uses Cricket (AT&T) MVNO. I can use mobile hotspot without any modifications. I just assumed everyone else could, too.
Click to expand...
Click to collapse
If not mistaken this method is so instead using hotspot data which is very limited (in my case I have 7gb) you use your normal data (I have unlimited).
DrakenFX said:
If not mistaken this method is so instead using hotspot data which is very limited (in my case I have 7gb) you use your normal data (I have unlimited).
Click to expand...
Click to collapse
I don't have any hotspot data, though. Still works.
My tethering works out of the box on unlimited Verizon's data plan. I thought they all worked.
I just want to make the following clear: This post ONLY applies to those who are not able to use their Wi-Fi hotspot because they are prompted by their service providers to change/upgrade their data plan once they are tethering. If you have unlimited data or simply have no problem connecting to your hotspot then that's great! I am simply trying to reach out to those have been asking for a solution.
Thanks, my unlimited att ipad plan now tethers, it was bocked before doing the mod. The Axon7 was one of the few devices that was blocking it, Windows Phone was the other device that blocked it.
rczrider said:
My device (A2017U) isn't rooted. It uses Cricket (AT&T) MVNO. I can use mobile hotspot without any modifications. I just assumed everyone else could, too.
Click to expand...
Click to collapse
Thanks for this info. I'm on Cricket as well and appreciate the heads up. My Axon 7 should arrive from Swappa this week.
This was a concern for me buying this phone. I have always had Google phones which are easy to root and modify. I need to upgrade my Nexus 5 and the new Pixel was announced today but it's too expensive for me. I hope this works when I get my phone in a couple of days. How did you guys root? Did you unlock your bootloader or no?
FunkyELF said:
This was a concern for me buying this phone. I have always had Google phones which are easy to root and modify. I need to upgrade my Nexus 5 and the new Pixel was announced today but it's too expensive for me. I hope this works when I get my phone in a couple of days. How did you guys root? Did you unlock your bootloader or no?
Click to expand...
Click to collapse
You can manage to get root with or without Unlock Bootloader, i just rather unlock and skip all the hassle when flashing files hehehe.
Using @tenfar tool is the way to start you journey for root/Unlocking Bootloader.
DrakenFX said:
You can manage to get root with or without Unlock Bootloader, i just rather unlock and skip all the hassle when flashing files hehehe.
Using @tenfar tool is the way to start you journey for root/Unlocking Bootloader.
Click to expand...
Click to collapse
I'd hate to throw away the warranty. My luck I'd crack my screen right after unlocking the bootloader... Which shouldn't have anything to do with one another but ZTE won't honor hardware warranties after it's been software unlocked
FunkyELF said:
I'd hate to throw away the warranty. My luck I'd crack my screen right after unlocking the bootloader... Which shouldn't have anything to do with one another but ZTE won't honor hardware warranties after it's been software unlocked
Click to expand...
Click to collapse
you warranty won't be touch at all, there is no way for ZTE to know if you are Unlock or not via the methods posted here in XDA unless you go official way which is not even available and the new method ZTE is working on will be different from the previous one.
If my guess is correct with the new Official Unlocking method Warranty won't be voided if is Hardware defects, Water Damage will have the deductible, but don't quote me on that.
T-Mobile and no root needed. Just flip the toggle and connect.
ItsLasher said:
T-Mobile and no root needed. Just flip the toggle and connect.
Click to expand...
Click to collapse
On T-Mobile on my Nexus 5 I had to do that tether_dun_required setting.
I forget whether I needed root for that or not.
B4oE said:
I have been reading recently about people wanting to know how to enable a wi-fi hotspot from their Axon 7 without being prompted from their provider (T-Mobile, AT&T, etc.) to change/upgrade their current data plans. Well, today I will give you a step by step guideline on how to bypass this. Please note, though, that your device must be rooted. In addition, I strongly recommend that you do a backup of your device just in case something goes wrong.
To begin, download the following apps to make this process as painless as possible Material Terminal and BuildProp Editor.
1. Launch the BuildProp Editor app and tap the menu icon (the 3 vertical dots) found on the top right of your screen. When the dialog box appears, tap on + New.
2. When the + New system property dialog box appears, under the first subheading Name type in the following: net.tethering.noprovisioning. In the next subheading named Value, type in the following: true. Once completed, press SAVE. You may be prompted to give BuildProp Editor root access. Choose GRANT and exit the app.
3. Launch the Material Terminal app.
4. In the first command line, type su and then tap enter to give it root access.
5. When the next command line appears below, type settings put global tether_dun_required 0 and then tap enter. Please note that there must be a space between the words settings and put, put and global, global and tether and required and 0. You will not believe how many people type this all as one word.
6. Exit the Material Terminal app and reboot your device. If the steps were followed carefully, you should now be able to use your device as a wi-fi hotspot without being prompted on your connecting devices to change/upgrade your data. This method should also work on other android devices.
Enjoy!
Click to expand...
Click to collapse
Question -
Tether dun required
Or
Tether_dun_required
Since I updated to B29 my tether has stopped working. This did not work for me.
HTC55555 said:
Question -
Tether dun required
Or
Tether_dun_required
Since I updated to B29 my tether has stopped working. This did not work for me.
Click to expand...
Click to collapse
Tether_dun_required
Hello still no go. Devices see my phone. Just can't get past obtaining IP address. Ran across this
#!/system/bin/sh
iptables -I FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT
iptables -I FORWARD -s 192.168.0.0/16 -j ACCEPT
iptables -P FORWARD DROP iptables -t nat -I POSTROUTING -s 192.168.0.0/16 -j MASQUERADE
Guy wrote a script for Tasker. Can I use these in terminal to accomplish other devices obtaining my ip address when tethering? Devices can see my phone but not connect.
Thanks in advance
I literally use 100gb monthly as in Poland LTE is free. Phone works as router for me all the time. Never been prompted with any message.
I downloaded the DirecTV Now app on New Year's Eve hoping for $35/cable. Instead, I was greeted with the same Error 40 that everyone with a rooted device got. It took me a couple of days of researching and playing and reflashing and..., but I've finally figured out the simple(r) method to bypass this stupid root check for DirectTV Now (AKA Error 40, QP1005)
This applies to the TX5Pro, but it should work on any s905x based AMLogic SoC running Marshmallow 6.0 (A95X, CQ9, TX5, TX3, X96, NEXBOX, +many more.) As I understand it, they all have similar Android builds using the p212 board and firmware. I also have a M8S s812 running Kit-Kat 4.4.2 that I'll work on breaking, next.
First things, first: If possible, find your firmware and do a clean flash. Not a requirement, but if you've been playing with this for a while and you've ended up here, you've probably mucked up your /system files in some way or another. I managed to screw up my su binary location a few times and couldn't get it back without a lot of work. Reflashing was a three-minute, headache-free task.
That said, you'll want to adb over tcp/ip as these devices don't like to play the USB cable game.
Code:
adb connect deviceipaddress:5555
Follow up with
Code:
adb shell
and
Code:
su
to get into a root shell (if you don't get one by default.) Mine came with SuperUser from ClockworkMod preinstalled as a system app. Mount your system folder
Code:
mount -o rw,remount,rw /system
and edit your build.prop file with Vim.
Code:
vi /system/build.prop
If Vim is new to you, search the interwebs for a Vim cheat sheet.
Here's the trick with this... DirecTV Now's shared object file in lib/armeabi/libdrmagent_downloadable_jni.so looks for a few keywords within a few properties. Those properties are:
Code:
ro.build.product
ro.build.tags
ro.build.type
ro.build.display.id
...and the keywords are:
Code:
"release-keys, OnePlus2, OnePlus, Z26CL, STUDIO_C, user" are keywords that it favors, while "cm, cyanogen, cyanogenmod, debug, userdebug, A0001" are disqualifying keywords. Supposedly, "test-keys" is a bad word, too.
In my case, I needed to edit my build.prop to eliminate any sign of the bad words. Example:
Code:
ro.build.display.id=p212-userdebug 6.0.1 MHC19J 20160909 test-keys
to
ro.build.display.id=p212-user 6.0.1 MHC19J 20160909 release-keys
Run through the file and replace anything that says userdebug with user and test-keys with release-keys until you get to "#end build properties" Then save and reboot.
After reboot, install Hide My Root (I used the one from Amphoras) and hide the Su binary. This is where things might be getting tricky for some of you... on the TX5Pro, the SuperUser app is a system installed app, meaning it can't be uninstalled (it can, but it's not exactly a simple task for everyone) so you'll need to go into settings -> apps -> superuser and disable the app from there. Reboot again. Now, with the su binary hidden and the app's manifest not showing up in the system, the error 40 message should go away. This option will allow you to quickly restore su and SuperUser without needing a bunch of additional steps. You'll still need to set the device location service to "battery saving" (or use mock locations) but that's a simple task anyone can figure out.
The app is a choppy on high def feeds for some reason. I can't tell if this is processing/memory issue or a feed (wifi) issue. By default, the app doesn't work on ethernet, meaning you'll have to use wifi until you can fix that issue. But hey, one thing at a time, right? Anyway, I hope this helps anyone with this particular headache.
Thanks for pointing me in the right direction...
Got DirecTV NOW working on my nexus 6 running pure nexus ROM... I just did the edits with super su root and root explorer. Then disabled super su and rebooted.
Now to update the the build.prop files on the lineage os 13.0 nexus 10, and my wife's kltevzw (on ting gsm network) running lineage os 14.1
hi please help i flashed wrong twrp recovery i think now my amlogic smartbox failed to boot in recovery mode and the main problem is my smartbox Encryption Unsuccessful Factory reset, when i click factory reset nothing happend please guide how to solve this
Sent from my SM-N910G using Tapatalk
jameson.donaghy said:
I downloaded the DirecTV Now app on New Year's Eve hoping for $35/cable.
Click to expand...
Click to collapse
Any chance that you tried this out with Data Free TV/"Sponsored Data" with an AT&T wireless account? i.e. running the box through a Cellular Hotspot or tethered to your phone. I've been looking at if one could use one of therse Android TV Boxes to basically get Data Free TV.
my live tv app detect root try with magisk also but no success in my s905x help me guys
Sent from my SM-N910G using Tapatalk
is anyone help me out
Sent from my SM-N910G using Tapatalk
I edited my build.prop files to try and "hide" the root and I still get the error. I also tried root cloak with xposed and still nothing
Thanks so much
This really helped. I used Xposed module to hide those keywords. Worked a charm!
Hello all,
Mirroring through miracast works fine now! I managed to fix the issue I faced with trying to mirror the phone with miracast.
The phone I bought from China came with apparently some manually altered rom. It didn't have much of the bloatware of the Nubia stock firmware. Also, it did not come with the "screen projection" app of Nubia. This app seems to be integrated into the phone. I couldn't find any .apk of it online. I tried a bunch of different apps, none worked. Also, factory resets, did not reinstall that app either.
The solution was simple. I used TWRP to wipe the phone and install the latest (v2.23) rom from the official nubia website: http://ui.nubia.cn/rom/detail/56
After installing it, the app was there and worked instantly.
At the moment now I have some issues with TWRP. I will fix it and see if the build.prop presisted through all of this, I doubt it.
If it did, and any changes are still required, I will update the post.
Kind regards,
Rup7ur3
---- initial post ----
Dear folks,
I'm trying to fix miracast on the Nubia Z18 (NX606J). Currently when I try mirror with the use of wi-fi direct, it doesn't show the miracast dongle I use (anycast).
I've not any experience in this and am trying to google for solutions. Online I have found some answers, but it's not yet working.
Hopefully I'm on the right path, but if anyone can help, it's greatly appreciated.
Why
The reason I want to use miracast, is to stream content to a portable display without the use of internet (so by cable or with WIDI). I don't think this phone supports hdmi/display port. If someone manages to get mirroring to work over cable, please let me know. As for WIDI, I think miracast is the only option? So, my bets are on this horse and I'm trying to make it run. Also, I'm new to this forum. If I post this at the wrong place, please forgive me. I created this thread for this specific model, because the manufacturer, Nubia, creates it's own (quite elaborate) UI on top of stock android. I suspect this could be part of the issue.
Summary so far
What I tried so far, is to install the custom recovery image of TWRP on my smartphone and adb + drivers on my windows 10 pc. Next I used the "mount" option in TWRP to enable adjustments of system files. The file I changed is the /system/build.prop file. I pulled the file using adb commands. Then changed the file on my pc and pushed it back to the phone. I will describe it in detail below. Yet, the sad thing is: it does not work. On another, older, model of the Nubia Z line, the Z9 mini, it did work.
Details
I installed drivers & adb/fastboot and twrp.
TWRP: https://forum.xda-developers.com/nubia-z18/development/recovery-twrp-nubia-z18nx606j-t3882098
Drivers & adb/fastboot: https://bbs.app.nubia.cn/forum.php?mod=viewthread&tid=1412934 (in chrome download didnt start for me, had to use firefox)
Once the above were installed, I connected my phone with the pc. I put phone settings in developer options to enable usb debugging. I got a notification to let my pc debug the phone, and accepted. Next I enabled "wireless display certification", "OEM unlocking" and set usb configuration to "MTP" instead of charging.
The adb on my pc was installed on my C:\adb\ folder. In the folder hold shift & right click, select open powershell or adb. I checked if my phone was connected using "adb devices". It listed my phone. So I went on and put it in fastboot mode (hold power + decrease volume). I checked if adb recognized fastboot with "fastboot devices". It listed my phone. Then next I unlocked the phone and installed TWRP with the help of this guide, from step 2 onwards: https://bbs.app.nubia.cn/forum.php?mod=viewthread&tid=1412934
Once TWRP installed. I created a backup of the phone through there. Then I selected the tab "mount" and enabled the system folder. Back to adb, I ran the command "adb devices" to see if my phone was listed, it was. Then I ran the command "adb pull /system/build.prop" that copied the build.prop file to my c:\adb folder. I made a reserve copy of the file and adjusted it with notepad++. These are the lines I added or enabled:
ro.hdmi.enable=true
ro.hdmi.mirror.enable=true
persist.adb.notify=0
net.tethering.noprovisioning=true
persist.debug.wfd.enable=1
persist.sys.wfd.virtual=0
Click to expand...
Click to collapse
Then I pushed it back with the adb command: "adb push build.prop /system/build.prop". Rebooted the phone, tested the mirroring option, no luck. The phone runs on android 8.1.0, has the nubia V6.0 UI and the build number is NX606J_CNCommonV2.23. Any app whatsoever with a miracast option, will redirect to the system miracast settings. The following screen will appear: https://imgur.com/a/Otf1YO0
The Struggle
I read online several forums where they claimed that setting these was helping other phones to enable miracast. For the Z18 it did not work. I tried this with the Nubia Z9 mini. Miracast did not work on there before, now it does. The build.prop seems to persist fine now. For some reason, the first few attempts (attempt 1 & 2) wiped TWRP and the adjustments on the build.prop. Third time it kept working. TWRP however, still is wiped after a few reboots, but the build.prop file remains intact with the changes I made.
The Nubia Z9 mini has a few stock apps: "screen projection", "screen projection services" and "projection sink". It loads the screen projection app and allows to chose from project/receive and works flawlessly after the build.prop changes. The Z9 mini runs on android 5.1.1 and as Nubia UI V4.0 with build number: NX511J_INCommon_V4.0.4.
I read online that:
Miracast is available on Android devices with Android 4.2 Jelly Bean
Click to expand...
Click to collapse
and
no more supported by Android since 6.0
Click to expand...
Click to collapse
Yet, I've seen people make it work, by adjusting the build.prop, for later versions also. Not seen one working with android 8.0 or 8.1. Is it impossible for some reason / a hardware thing? If it's a software issue, surely it can be overcome?
I found that the build.prop in the Z9 mini contained the following lines:
#property to enable VDS WFD solution
persist.hwc.enable_vds=1
# Add by ztemt for ZWfd begin
#property to set wfd output resolution is 1080P(0) / 720P(1) / 960*540(2) / 800*480(3)
persist.sys.wfd.zte_resolution=0
#property to show wfd sink false(0) / true(1)
persist.sys.wfd.zsink_support=1
#property this is device support wfd 1080p output support(true) not support(false)
persist.sys.wfd.1080p_support=false
# Add by ztemt for ZWfd end
Click to expand...
Click to collapse
I believe it's coupled to those apps I mentioned screen projection apps which are on the z9 mini. It had no effect adding these on the Z18. Now I'm attempting to find those apps and install them on Z18. Or looking for ways to downgrade the Z18 to android 5x. Ideally I do not want to downgrade the android. Any help, advice or questions are greatly appreciated.
rup7ur3 said:
Dear folks,
I'm trying to fix miracast on the Nubia Z18 (NX606J). I've not any experience in this and am trying to google for solutions.
I have found some answers, but it's not yet working. Hopefully I'm on the right path, but if anyone can help, it's greatly appreciated.
Why
The reason I want to use miracast, is to stream content to a portable display without the use of internet (so by cable or with WIDI). I don't think this phone supports hdmi/display port. If someone manages to get mirroring to work over cable, please let me know. As for WIDI, I think miracast is the only option? So, my bets are on this horse and I'm trying to make it run. Also, I'm new to this forum. If I post this at the wrong place, please forgive me. I created this thread for this specific model, because the manufacturer, Nubia, creates it's own (quite elaborate) UI on top of stock android. I suspect this could be part of the issue.
Summary so far
What I tried so far, is to install the custom recovery image of TWRP on my smartphone and adb + drivers on my windows 10 pc. Next I used the "mount" option in TWRP to enable adjustments of system files. The file I changed is the /system/build.prop file. I pulled the file using adb commands. Then changed the file on my pc and pushed it back to the phone. I will describe it in detail below. Yet, the sad thing is: it does not work. On another, older, model of the Nubia Z line, the Z9 mini, it did work.
Details
I installed drivers & adb/fastboot and twrp.
TWRP: https://forum.xda-developers.com/nubia-z18/development/recovery-twrp-nubia-z18nx606j-t3882098
Drivers & adb/fastboot: https://bbs.app.nubia.cn/forum.php?mod=viewthread&tid=1412934 (in chrome download didnt start for me, had to use firefox)
Once the above were installed, I connected my phone with the pc. I put phone settings in developer options to enable usb debugging. I got a notification to let my pc debug the phone, and accepted. Next I enabled "wireless display certification", "OEM unlocking" and set usb configuration to "MTP" instead of charging.
The adb on my pc was installed on my C:\adb\ folder. In the folder hold shift & right click, select open powershell or adb. I checked if my phone was connected using "adb devices". It listed my phone. So I went on and put it in fastboot mode (hold power + decrease volume). I checked if adb recognized fastboot with "fastboot devices". It listed my phone. Then next I unlocked the phone and installed TWRP with the help of this guide, from step 2 onwards: https://bbs.app.nubia.cn/forum.php?mod=viewthread&tid=1412934
Once TWRP installed. I created a backup of the phone through there. Then I selected the tab "mount" and enabled the system folder. Back to adb, I ran the command "adb devices" to see if my phone was listed, it was. Then I ran the command "adb pull /system/build.prop" that copied the build.prop file to my c:\adb folder. I made a reserve copy of the file and adjusted it with notepad++. These are the lines I added or enabled:
Then I pushed it back with the adb command: "adb push build.prop /system/build.prop". Rebooted the phone, tested the mirroring option, no luck. The phone runs on android 8.1.0, has the nubia V6.0 UI and the build number is NX606J_CNCommonV2.23. Any app whatsoever with a miracast option, will redirect to the system miracast settings. The following screen will appear: https://imgur.com/a/Otf1YO0
The Struggle
I read online several forums where they claimed that setting these was helping other phones to enable miracast. For the Z18 it did not work. I tried this with the Nubia Z9 mini. Miracast did not work on there before, now it does. The build.prop seems to persist fine now. For some reason, the first few attempts (attempt 1 & 2) wiped TWRP and the adjustments on the build.prop. Third time it kept working. TWRP however, still is wiped after a few reboots, but the build.prop file remains intact with the changes I made.
The Nubia Z9 mini has a few stock apps: "screen projection", "screen projection services" and "projection sink". It loads the screen projection app and allows to chose from project/receive and works flawlessly after the build.prop changes. The Z9 mini runs on android 5.1.1 and as Nubia UI V4.0 with build number: NX511J_INCommon_V4.0.4.
I read online that:
and
Yet, I've seen people make it work, by adjusting the build.prop, for later versions also. Not seen one working with android 8.0 or 8.1. Is it impossible for some reason / a hardware thing? If it's a software issue, surely it can be overcome?
I found that the build.prop in the Z9 mini contained the following lines:
I believe it's coupled to those apps I mentioned screen projection apps which are on the z9 mini. It had no effect adding these on the Z18. Now I'm attempting to find those apps and install them on Z18. Or looking for ways to downgrade the Z18 to android 5x. Ideally I do not want to downgrade the android. Any help, advice or questions are greatly appreciated.
Click to expand...
Click to collapse
Never try downgrading this phone. It's a nightmare because it's using AVB2.0 which was introduced with Android 8 I think. So getting that to work would be extremely difficult. What I'm not sure about is if nubia is doing anything different from other vendors as, judging by the source code, it looks the same as Sony for example (actually that's no wonder since they got 70% of their code from Sony).
What's difficult about this is that they define custom, vendor and device specific values as you can see with the Z9 build.prop. I'm not that well versed in Android actually and mostly just learning all this stuff by experimenting right now, but I would say your best bet would be some tool that scans a system for possible values in build.prop. However I'm unsure if such a tool exists unfortunately..
Sorry I can't be of more help as of now. I think Lineage is supporting Miracast though? So once I got that to work, it might be an option for you
Nubia z18 support screen cast without internet.
I use with EZcast 2.4g/5g without any internet and wifi hotspot.
I buy from Aliexpress " EZCAST 1080P TV Stick Dongle 5G Wifi Support HDMI DLNA Miracast Airplay DLNA Stick For IOS Android Windows Smartphone"
jagdishgeb said:
I use with EZcast 2.4g/5g without any internet and wifi hotspot.
I buy from Aliexpress " EZCAST 1080P TV Stick Dongle 5G Wifi Support HDMI DLNA Miracast Airplay DLNA Stick For IOS Android Windows Smartphone"
Click to expand...
Click to collapse
Thank you for the response, great to hear that it is possible! Did it work immediately?
Also, if you don't mind me asking. Could you maybe check if there are any default screen projection / sink apps pre-installed on your z18?
Mine came without any. I will try reinstall stock to see if that helps. All apps I use go to this screen: https://imgur.com/a/Otf1YO0
Online I read there are supposed to be options to enable wireless display in there. However, I think Nubia disabled it in their UI.