Related
I'm using Infused – any other have full-functioning bluetooth? Thanks!
Sent from my SAMSUNG-SGH-I997 using XDA App
Anything not based off of Cyanogenmod - IE, the samsung based roms, should have working bluetooth. I'm assuming, and someone please correct me if I'm wrong, most of the JVT roms ported to the Infused via LinuxBozo's amazing Hellraiser kernel/modem package should be bluetooth friendly.
---------- Post added at 07:50 PM ---------- Previous post was at 07:45 PM ----------
For future reference, this was a question and belongs in the Q and A forum. Adherence to the rules here (which I must admit I've broken frequently) is greatly appreciated among the community!
after doing some googling i found this i'm interested in trying it tonight maybe if you try before me let me know how it works out:
I had the same problem. My Desire CDMA did not pair with any bluetooth device anymore after switching from stock Froyo to CM 7.0.3.
Bluetooth pairing did not work with Lenovo Notebook under Win XP SP3. It used to work flawlessly with original Froyo as well as with half a dozen different devices (PC with BT dongle, mobile phones, BT keyboard, BT gamepad, BT headset, GPS receivers).
I restored my bluetooth settings with Titanium Backup and had my notebook still listed as paired but all file transfers fail. When I remove the pairing and try to pair again, both devices pop up a pairing code dialog but pairing always fails without any error message.
SOLUTION
I do not know if every step is required but this is what solved the problem for me:
I ran the Terminal app and entered
su
(App requests root permissions, grant them). Then I went to the device's bluetooth settings with
cd /data/misc/bluetoothd
(Note the 'd' at the end). There I found a directory named by the bluetooth chip's ID, in my case '38:E78:45:21:a4'. I renamed this directory
mv 3* hidden
, turned bluetooth off and back on and could use bluetooth again.
HTH
Click to expand...
Click to collapse
i found it on the cyanogenmod forum please note that i am NOT taking credit for this solution i tried to post the link to it but it wouldn't allow me :-x lol
So I have an interop-unlocked T-Mobile HTC HD7 that I have updated to version 7.10.7720.68. I am pretty sure that falls under the HTC V2 Drivers, but as it was already interop-unlocked before I updated, it shouldn't be a problem.
Anyways, on a registry editor I have installed I tried to change some PageBackgroundColor values etc. Well, after changing them, they revert back right away (to a previous color I set awhile ago: FF26C8F8). After further investigation, ALL registry values are "frozen". I can attempt to set them without error, but once I confirm my changes they just revert back.
Even other apps that change the registry will not work. I can, however, deploy apps that require interop-unlock to my phone. Does anyone else have this issue? Is there a solution out there? I didn't apply the registry value to stop itself from re-locking... so is that the problem? I doubt it, because first I Chevron-unlocked it and then interop-unlocked it (and then upgraded the phone software later).
[Sorry if this is in the wrong place... I don't think can't post in the hacking section yet since I don't have enough posts]
Thanks
are you using custom or official rom?
Official rom.
I fixed the problem, though. I ended up rolling back to a backup Zune had (luckily it was still Interop Unlocked). I'd like to know more about this problem though, just in case
Sent from my HD7 using XDA Windows Phone 7 App
You actually already hit on the problem without realizing it: those HTC v2 drivers.
Interop-unlock is just a registry change like any other. The driver update makes it impossible to change the (vast majority of the) registry using homebrew apps. That's why you have to interop-unlock before installing those drivers; if you wait, you can't make the registry change that is interop-unlock.
However, just because you are interop-unlocked doesn't mean the drivers keep working. Updating them won't revert the interop-unlock (you can still install lots of apps, including with ID_CAP_INTEROPSERVICES), but it does make it much less useful because now you can't edit the registry (or filesystem) anymore.
Hope that helps.
Thanks a lot!
Sent from my HD7 using XDA Windows Phone 7 App
your lucky, I still can't get my back up to work.
---------- Post added 2nd February 2012 at 12:02 AM ---------- Previous post was 1st February 2012 at 11:25 PM ----------
GoodDayToDie said:
You actually already hit on the problem without realizing it: those HTC v2 drivers.
Interop-unlock is just a registry change like any other. The driver update makes it impossible to change the (vast majority of the) registry using homebrew apps. That's why you have to interop-unlock before installing those drivers; if you wait, you can't make the registry change that is interop-unlock.
However, just because you are interop-unlocked doesn't mean the drivers keep working. Updating them won't revert the interop-unlock (you can still install lots of apps, including with ID_CAP_INTEROPSERVICES), but it does make it much less useful because now you can't edit the registry (or filesystem) anymore.
Hope that helps.
Click to expand...
Click to collapse
Other than using a previous back up is there any other work around? My backup is corrupt and I can't make Zune see it at all.
GoodDayToDie said:
However, just because you are interop-unlocked doesn't mean the drivers keep working. Updating them won't revert the interop-unlock (you can still install lots of apps, including with ID_CAP_INTEROPSERVICES), but it does make it much less useful because now you can't edit the registry (or filesystem) anymore.
Hope that helps.
Click to expand...
Click to collapse
I note that people say if you are IU before the v2 driver update that you are still unlocked after updating (you and Heathcliff and a couple others). I personally think this statement is wrong or misleading; you have lost ability to do anything (or most anything) you used to be able to do with these sideloaded apps so I like to call this "IU is BROKE" and you really are not fully IU anymore.
In my mind the IU is "handicapped/broken/whatever" but I don't like saying I am still fully "interop-unlocked".
P.S. I think we need a new term - handicapped IU, restricted IU, something...
---------- Post added at 11:13 PM ---------- Previous post was at 11:09 PM ----------
sinister1 said:
your lucky, I still can't get my back up to work.
---------- Post added 2nd February 2012 at 12:02 AM ---------- Previous post was 1st February 2012 at 11:25 PM ----------
Other than using a previous back up is there any other work around? My backup is corrupt and I can't make Zune see it at all.
Click to expand...
Click to collapse
For the VZW Trophy I can't think of one. There isn't even a custom rom for this phone.
LiFePo4 said:
I note that people say if you are IU before the v2 driver update that you are still unlocked after updating (you and Heathcliff and a couple others). I personally think this statement is wrong or misleading; you have lost ability to do anything (or most anything) you used to be able to do with these sideloaded apps so I like to call this "IU is BROKE" and you really are not fully IU anymore.
In my mind the IU is "handicapped/broken/whatever" but I don't like saying I am still fully "interop-unlocked".
P.S. I think we need a new term - handicapped IU, restricted IU, something...
---------- Post added at 11:13 PM ---------- Previous post was at 11:09 PM ----------
For the VZW Trophy I can't think of one. There isn't even a custom rom for this phone.
Click to expand...
Click to collapse
That sucks; what phones out there have custom ROMs? I'm looking into ther opptions and possibly even jumping ship to either back to WM if possible if not to Android. I am still looking to stay on WP but I need something better with more options than what I have now.
sinister1 said:
That sucks; what phones out there have custom ROMs? I'm looking into ther opptions and possibly even jumping ship to either back to WM if possible if not to Android. I am still looking to stay on WP but I need something better with more options than what I have now.
Click to expand...
Click to collapse
If you want to stay on Verizon there isn't any. As far as I know all WP7 phones EXCEPT the two CDMA versions (VZW Trophy and Sprint Arrive) have custom roms. I have read Darkforces might be working on a CDMA custom ROM but I have not seen anything.
@LiFePo4: With regard to interop-unlock, I must disagree. IU, although the term was coined here on the forum, still has a very specific meaning: MaxUnsignedApp > 300, which allows installing and using apps with ID_CAP_INTEROPSERVICES (required to access drivers). Just because the drivers that a bunch of apps have been using were crippled in an unrelated update (interop-lock is an OS "feature" in Microsoft code, but the drivers that you're thinking of are part of the OEM firmware) doesn't mean the unlock has gone away. Besides, there are (a few) apps which is ID_CAP_INTEROPSERVICES but don't call into the OEM drivers at all; without interop-unlock we wouldn't be able to use them. Additionally, if nothing else you can still install a great many unsigned apps, much more than the limit of 3 or even 10 (quite possible to hit just with non-interop apps, I believe).
I agree it would be useful to have a quick way to describe this state of the phone, but please don't co-opt interop-unlock for that purpose.
@sinister1: If your backup can't be restored (taken with a faulty tool?) then your only option is to flash a ROM. As you say, there are no custom ROMs for the Verizon Trophy, but there are certainly stock ROMs and I'll bet you can find one available for download somewhere via this forum. That will hard-reset your phone, losing all data, but it will also revert it to an earlier version, allowing you to do things like interop-unlock.
@GoodDayToDie - point taken and understood. IU should stand as it is and I will not abuse it. Need to think of something...Driver Restricted? OEM Hampered?Access Confined?
How about the term "driver-unlock" for having drivers that give you system access? We have Dev-unlocked, Interop-unlocked, Driver-unlocked? Then you can say when the latest driver updates will break your driver-unlock.
---------- Post added at 02:22 PM ---------- Previous post was at 02:00 PM ----------
Joying got in contact with me and asked me if I would wanted to test one of their new PX5 2GB models on Android version 8.
I decided that I wanted to do so, so I received for some 28 euros a Joying JY-VO130P2.
So what is it:
8" screen 2DIN unit for VW/Skoda/Seat/Audi
ARM Cortex based ARM V8, 1 processor 8 A53 cores (4 running at 1.5 GHz, 4 "low energy" running at 1.2 GHz)
FYT based SOM
2GB internal memory (RAM)
32GB storage (ROM)
Android version 8.0.0
particularities: DVD-player
I made a video review of it which you can find here:https://youtu.be/MH1snfDIU5A
The Good:
seems minimally faster than the Sofia 3GR
FYT/syu software the same as on Sofia 3GR.
Android 8.0.0, longer support
Android 8 supports split-screen functionality out of the box.
Improved radio reception (but needs to be tested over longer period)
Improved sound quality (I think, but I forgot to mention in the review)
The bad:
Too high temperatures of the cpu
No user configuration of buttons
FYT/syu software the same as on Sofia 3GR (I mean that some "weird" things are still there on the PX5 as well)
FYT/syu applications (radio, bt, music player, etc.) do not support split screen (and it is so simple to enable this)
No Android 8 Automotive integration
Chinese translations could be improved using on-line tooling like weblate.org or crowdin.com (or others) by using the user community.
The really bad:
Too high temperatures of the cpu. It really needs better cooling.
Update Sun 13 May 2018:
There is indeed an issue with the WiFi on this new Version 8.0.0 model. I already mentioned in my video review that it did not auto-connect to my WiFi networks.
- When fully rebooting the unit, it connects automatically to my home WiFi. No issue at all.
- When coming from deep-sleep, WiFi is either switched off ór WiFi is still on, but it doesn't connect automatically to my WiFi networks.
See update Fri 18 May
And maybe some explanation: I mentioned in the review that it is very simple to alter the AndroidManifest.xml to allow resizing the app and make it function in split-screen. So why didn't I do that myself?
The Joying apps are signed. Some parts can be easily changed without touching the signing, but the AndroidManifest.xml is part of that signing as it also contains the security options the application needs. Off course I do not have the Joying signature so I can't recompile the app with the same signature while the AndroidManifest.xml is obviously changed. That is exactly how it should work or any hacker could get access.
FYT/syu should change this.
Update Mon 14 May:
There used to be a bug in the older ROMs that where you gave the BT access to your contacts, it would erase all your contacts.
Well, 8.0 also erases all your contacts!
This issue annoys me highly as it is so old and it still isn't solved.
Update Tue 15 May:
The Google Assistant with spoken searches does not work.
When trying to use the voice search function (clicking the microphone in the search bar), It shows very shortly the 'Speak now' indicator before it turns into an error message that mentions "No internet connection". I checked very carefully and my internet connection is fine. I tried with 2 home WiFi networks and via hot-spot on my phone. All internet connections work fine, but Google search still gives this error message.
Update Fri 18 May:
See post #44
Update Wed 23 May (test of Android auto):
See post #54
Update Sunday 10 June:
See post #77
- OK Google solved.
Update Tuesday 12 June:
Some update about the BT app erasing your Google contacts: Joying is now working full steam on it. Another user made a nice video on youtube about it
Thanks a lot for your great review video!
Huh, 17 minutes... but it's definitely worth watching it fully till the end.
You spent a huge amount of effort and Joying still took 28 EUR from you? They should be ashamed!
So, the Joying Intel Sofia users (like me) will loose your support now? You state at the end of the video that you plan to continue using it in your car.
Interesting review, it addresses many of the questions I had regarding the new Joying PX5 units. Thanks!
Now as @realzoulou mentions above, I hope we won't lose you on the SOFiA platform! Your work on JET and on XSofiaTweaker is central to the success of those units.
I spend a day thinking whether I wanted to spend that money, because I really didn't. Finally I did agree because I thought: "then I have a spare unit for 28 euros".
Like I mentioned: the user layer software (the apks) is the same on the Sofia and the PX5. I already decompiled it in both apktool and jadx.
I can continue the XSofiaTweaker the same way for the PX5 as for the Sofia. Same for the JET apk with some small internal changes (if Sofia then, else ..)
I already made a nokill main server (=sofia server on Sofia) using the exact same steps as on the Sofia (and as explained by @realzoulou) and I replaced the radio mod.
Android 8 for this device is that new that there is no firmware to download yet.
I don't think rooting is a problem, but I'm not going to do/try that without firmware that allows me to reflash. Same for Xposed.
I will program the option to user-select the delay time for double/triple tap today (for Sofia), or at least early next week. However, I think XSofiaTweaker is now almost ready.
I think no new developments will come out for Android 6, so no further developments are necessary either for JET. Mods can easily be added as I simply upload them and use an xml to configure installation. Upload it, add a line to the xml, simply recompile: done.
I like to tinker, but I'm also a simple user that doesn't need that much. Especially when (or more probably: if) Joying/FYT/syu will make more hardware buttons and steering wheel buttons user configurable, there is even less need for special apps. (And I think I forgot to mention that GPS speed indication is correct on this units, but that should actually not be necessary to mention: it should simply work)
I just read on this forum Yesterday that on the standard Joying when you press the Navi button, the assigned (Navi) app will be started. If you press the button again, the previous app will be brought to front. Pressing it again the Navi app will be brought to front again. Etcetera. I did not even know that, but it is very handy. Of course that no longer works in the XSofiaTweaker (or in Gustdens mods).
Only that little overheating barbecue inside is worrying me.
https://www.joyingauto.eu/blog/category/update-firmware/
https://www.youtube.com/watch?v=AXQ4tsXO0Y0
@surfer63 what do u think? it will fit?
RoNeReR said:
https://www.joyingauto.eu/blog/category/update-firmware/
https://www.youtube.com/watch?v=AXQ4tsXO0Y0
@surfer63 what do u think? it will fit?
Click to expand...
Click to collapse
No it is not suitable. The 2GB-RAM/16GB-ROM and 4GB-RAM/32GB-ROM models are NOT FYT based and NOT compatible with the 2GB-RAM/32GB-ROM models.
The version I have is a FYT based 2GB-RAM/32GB-ROM version. There is no Android version 8 firmware for it yet.
Update Sun 13 May 2018
There is indeed an issue with the WiFi on this new Version 8.0.0 model. I already mentioned in my video review that it did not auto-connect to my WiFi networks.
- When fully rebooting the unit, it connects automatically to my home WiFi. No issue at all.
- When coming from deep-sleep, WiFi is either switched off ór WiFi is still on, but it doesn't connect automatically to my WiFi networks.
And maybe some explanation: I mentioned in the review that it is very simple to alter the AndroidManifest.xml to allow resizing the app and make it function in split-screen. So why didn't I do that myself?
The Joying apps are signed. Some parts can be easily changed without touching the signing, but the AndroidManifest.xml is part of that signing as it also contains the security options the application needs. Off course I do not have the Joying signature so I can't recompile the app with the same signature while the AndroidManifest.xml is obviously changed. That is exactly how it should work or any hacker could get access.
FYT/syu should change this.
(also added to first post)
There's a 4gb version now on the joying website that is FYT based...
Probably will pick one of these up as a spare, at least the SoM, if anything to test or generate a rom, and get Xposed working on this!
Once root is ahcieved, the manifests can be changed, the program only needs to be granted root, and it'll work fine.
Questions:
Did you look at the clock speed? Is it variable? What governor is used?
What is the three lines present in the system bar do?
Did you open the unit? Haven't found any photos of the interior of the new units yet.
gtxaspec said:
What is the three lines present in the system bar do?
Click to expand...
Click to collapse
Should be just the Menu icon, 3 dots.
---------- Post added at 02:58 AM ---------- Previous post was at 02:57 AM ----------
Testing Unit on Standby!
My PX5 is just sitting here, doing nothing. Will help test anything.
carter.w.jason said:
Should be just the Menu icon, 3 dots.
---------- Post added at 02:58 AM ---------- Previous post was at 02:57 AM ----------
Testing Unit on Standby!
My PX5 is just sitting here, doing nothing. Will help test anything.
Click to expand...
Click to collapse
You have the fyt model right?
gtxaspec said:
You have the fyt model right?
Click to expand...
Click to collapse
Correct
carter.w.jason said:
Correct
Click to expand...
Click to collapse
Are you able to get us some pictures of the internals?
@gtxaspec
Nice looks like a drop in replacement for the 6021...
---------- Post added at 05:51 AM ---------- Previous post was at 05:14 AM ----------
carter.w.jason said:
Should be just the Menu icon, 3 dots.
---------- Post added at 02:58 AM ---------- Previous post was at 02:57 AM ----------
Testing Unit on Standby!
My PX5 is just sitting here, doing nothing. Will help test anything.
Click to expand...
Click to collapse
You have the 6.0 os installed? Want to try a custom ROM ( if I can figure it out). You can reflash stock if needed.
gtxaspec said:
Nice looks like a drop in replacement for the 6021...
---------- Post added at 05:51 AM ---------- Previous post was at 05:14 AM ----------
You have the 6.0 os installed? Want to try a custom ROM ( if I can figure it out). You can reflash stock if needed.
Click to expand...
Click to collapse
Yes, should be 6.0, what ever is stock. I'm down to try a custom ROM. I've felt like this is the better unit, if it could be tamed.
Update Mon 14 May
There used to be a bug in the older ROMs that where you gave the BT access to your contacts, it would erase all your contacts.
Well, 8.0 also erases all your contacts!
This issue annoys me highly as it is so old and it still isn't solved.
surfer63 said:
There used to be a bug in the older ROMs that where you gave the BT access to your contacts, it would erase all your contacts.
Well, 8.0 also erases all your contacts!
This issue annoys me highly as it is so old and it still isn't solved.
Click to expand...
Click to collapse
That's a bug in the SYU dialer app, it never went away. The solution is to use Xposed app settings to deny contacts write permissions. Ouch.
gtxaspec said:
Did you look at the clock speed? Is it variable? What governor is used?
Click to expand...
Click to collapse
Overlooked this one. Will check tonight. It is variable from 216 MHz to 1.51GHz, but I will look at the specifics tonight.
surfer63 said:
Update Mon 14 May:
There used to be a bug in the older ROMs that where you gave the BT access to your contacts, it would erase all your contacts.
Well, 8.0 also erases all your contacts!
This issue annoys me highly as it is so old and it still isn't solved.
Click to expand...
Click to collapse
I have this bug on the 7.0 Android as well - this annoys the **** out of me!
Zeze21 said:
I have this bug on the 7.0 Android as well - this annoys the **** out of me!
Click to expand...
Click to collapse
I reported this bug immediately to Joying, like I did last year and like other users did as well: users from the XDA forum as well as the previous carjoying forum.
Joying reacted really surprised on my mail.
That surprised me again a lot (with some other emotions as well).
Hi guys.
I'm wanting to buy my partner a 2017 version of Amazon fire HD 8.
Before I do so, I'm wanting to know if it had the option of adding "unknown sources", and also, if I can mirror anything from the fire tablet which is seen on screen, to her TV, which is able to receive devices.
I know there's quite a few fire tablets over time, and they differ, but I want to know this tablet is good enough, before I purchase it. Thanks in advance
David7878 said:
Hi guys.
I'm wanting to buy my partner a 2017 version of Amazon fire HD 8.
Before I do so, I'm wanting to know if it had the option of adding "unknown sources", and also, if I can mirror anything from the fire tablet which is seen on screen, to her TV, which is able to receive devices.
I know there's quite a few fire tablets over time, and they differ, but I want to know this tablet is good enough, before I purchase it. Thanks in advance
Click to expand...
Click to collapse
Hey there - I wrote you a response but this system keeps blocking me from replying crying: ), so I'll send you a message. But in a nutshell - yes and yes.
---------- Post added at 11:51 PM ---------- Previous post was at 11:42 PM ----------
richaardvark said:
Hey there - I wrote you a response but this system keeps blocking me from replying crying: ), so I'll send you a message. But in a nutshell - yes and yes.
Click to expand...
Click to collapse
..........
David7878 said:
Hi guys.
I'm wanting to buy my partner a 2017 version of Amazon fire HD 8.
Before I do so, I'm wanting to know if it had the option of adding "unknown sources", and also, if I can mirror anything from the fire tablet which is seen on screen, to her TV, which is able to receive devices.
I know there's quite a few fire tablets over time, and they differ, but I want to know this tablet is good enough, before I purchase it. Thanks in advance
Click to expand...
Click to collapse
Hi David! To answer your questions:
Yes - you can install apps from "unknown sources."
Yes, - you can mirror your screen (using various third-party tools) but the built-in/stock Android casting/mirroring feature doesn't work. I've come close to getting it to connect but there's always an error. I've used several third-party casting apps though with overall decent screen mirroring quality.
Enhancing your 2017 Fire HD 8 by installing the Play Store/by way of some of the recent guides on here, especially (IMO) the most recent method for hiding/disabling system apps & bloatware, you're actually left with a pretty solid tablet! My expectations have been exceeded anyway, though I'll admit they were pretty low, lol. Just remember - no rooting nor bootloader unlocking options are available yet (and may never be), so you won't be able to install custom ROMs or anything of that nature. But I'd say it's worth it, especially if you buy one on sale for next to nothing.
richaardvark said:
you can mirror your screen (using various third-party tools) but the built-in/stock Android casting/mirroring feature doesn't work. I've come close to getting it to connect but there's always an error. I've used several third-party casting apps though with overall decent screen mirroring quality.
Click to expand...
Click to collapse
Can you recommend one of these third party casting apps? I've tried a few but nothing seems to work on my TV (which I believe uses miracast)
ModuRaziel said:
Can you recommend one of these third party casting apps? I've tried a few but nothing seems to work on my TV (which I believe uses miracast)
Click to expand...
Click to collapse
These tablets unfortunately have too much of the Miracast code missing so I can't get the actual original Miracast to work. The only Cast app I managed to get to work from device to device is Remo Droid which is available on the Play Store. It's relatively easy to setup and use. Let me know how it goes for you.
---------- Post added at 11:28 AM ---------- Previous post was at 11:22 AM ----------
richaardvark said:
Hey there - I wrote you a response but this system keeps blocking me from replying crying: ), so I'll send you a message. But in a nutshell - yes and yes.
---------- Post added at 11:51 PM ---------- Previous post was at 11:42 PM ----------
..........
Hi David! To answer your questions:
Yes - you can install apps from "unknown sources."
Yes, - you can mirror your screen (using various third-party tools) but the built-in/stock Android casting/mirroring feature doesn't work. I've come close to getting it to connect but there's always an error. I've used several third-party casting apps though with overall decent screen mirroring quality.
Enhancing your 2017 Fire HD 8 by installing the Play Store/by way of some of the recent guides on here, especially (IMO) the most recent method for hiding/disabling system apps & bloatware, you're actually left with a pretty solid tablet! My expectations have been exceeded anyway, though I'll admit they were pretty low, lol. Just remember - no rooting nor bootloader unlocking options are available yet (and may never be), so you won't be able to install custom ROMs or anything of that nature. But I'd say it's worth it, especially if you buy one on sale for next to nothing.
Click to expand...
Click to collapse
It's not that it doesn't work it's that most of the OEM have taken out the Android code that activates it. For example in fire OS, on every tablet except the HD 8, the 'wifi_display' string is missing in the public XML of the framework. I've recently come across a post on XDA that explains how to create settings like that, but I haven't read enough about it yet and haven't tried it. I have the next 2 days off and it's a project I'm going to try. And if it works it might reactivate the old stock feature.
DragonFire1024 said:
These tablets unfortunately have too much of the Miracast code missing so I can't get the actual original Miracast to work. The only Cast app I managed to get to work from device to device is Remo Droid which is available on the Play Store. It's relatively easy to setup and use. Let me know how it goes for you.
---------- Post added at 11:28 AM ---------- Previous post was at 11:22 AM ----------
It's not that it doesn't work it's that most of the OEM have taken out the Android code that activates it. For example in fire OS, on every tablet except the HD 8, the 'wifi_display' string is missing in the public XML of the framework. I've recently come across a post on XDA that explains how to create settings like that, but I haven't read enough about it yet and haven't tried it. I have the next 2 days off and it's a project I'm going to try. And if it works it might reactivate the old stock feature.
Click to expand...
Click to collapse
I'd be interested to see the results of your work. I just tried Remo Droid and a few other apps but none work. Remo doesnt detect any devices and the others all kick back to the amazon wireless settings page
ModuRaziel said:
I'd be interested to see the results of your work. I just tried Remo Droid and a few other apps but none work. Remo doesnt detect any devices and the others all kick back to the amazon wireless settings page
Click to expand...
Click to collapse
Weird. Remo worked on my HD 8. It kicks back likely because the 'config_enableWifiDisplay' in the framework is set to false.
DragonFire1024 said:
Weird. Remo worked on my HD 8. It kicks back likely because the 'config_enableWifiDisplay' in the framework is set to false.
Click to expand...
Click to collapse
I suspect Remo not working is more to do with the tv than the device. Im sure if i browsed on my pc to the url that remo puts out, id be able to see the screen, but it just doesnt see the tv as a device to connect to.
DragonFire1024 said:
Weird. Remo worked on my HD 8. It kicks back likely because the 'config_enableWifiDisplay' in the framework is set to false.
Click to expand...
Click to collapse
remo was the only oneto work for me.
---------- Post added at 05:11 PM ---------- Previous post was at 05:09 PM ----------
ModuRaziel said:
I suspect Remo not working is more to do with the tv than the device. Im sure if i browsed on my pc to the url that remo puts out, id be able to see the screen, but it just doesnt see the tv as a device to connect to.
Click to expand...
Click to collapse
And that case is quite possible you may need a dongle like Chromecast for you to use your television. Because I have the same issue with my computer monitor. It won't read any devices. And Google says I need Chromecast.
richaardvark said:
Hey there - I wrote you a response but this system keeps blocking me from replying crying: ), so I'll send you a message. But in a nutshell - yes and yes.
---------- Post added at 11:51 PM ---------- Previous post was at 11:42 PM ----------
..........
Hi David! To answer your questions:
Yes - you can install apps from "unknown sources."
Yes, - you can mirror your screen (using various third-party tools) but the built-in/stock Android casting/mirroring feature doesn't work. I've come close to getting it to connect but there's always an error. I've used several third-party casting apps though with overall decent screen mirroring quality.
Enhancing your 2017 Fire HD 8 by installing the Play Store/by way of some of the recent guides on here, especially (IMO) the most recent method for hiding/disabling system apps & bloatware, you're actually left with a pretty solid tablet! My expectations have been exceeded anyway, though I'll admit they were pretty low, lol. Just remember - no rooting nor bootloader unlocking options are available yet (and may never be), so you won't be able to install custom ROMs or anything of that nature. But I'd say it's worth it, especially if you buy one on sale for next to nothing.
Click to expand...
Click to collapse
***Thank you.
Which third party apps have you used to do this? I have the fire tablet, and there is no option for display mirroring, and therefore need to download an app which will mirror it. Ive tried a few on the app store which is on the fire tablet but with no joy. The TV I use received display mirroring. Thank
Xiaomi Mi A2 Lite privilege escalation
[CVE-2019-15468]
[CVE-2019-15472]
[CVE-2019-15473]
Suggesting replace the affected object with an alternative product.
https://vuldb.com/?id.145771
perfect_ said:
Xiaomi Mi A2 Lite privilege escalation
[CVE-2019-15468]
[CVE-2019-15472]
[CVE-2019-15473]
Suggesting replace the affected object with an alternative product.
https://vuldb.com/?id.145771
Click to expand...
Click to collapse
So replace the A2 Lite with another phone because of that ?
Who did that and why ?
I'm no expert in reading CVEs but "something is wrong, but we have no details" hardly seems like a sensible thing to be concerned about.
---------- Post added at 10:03 AM ---------- Previous post was at 09:44 AM ----------
Oh, that link was useless but it points to the actual CVE. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-15468
It's for 10.0.3.0. It says the com.huaqin.factory app allows unprivileged apps to set wireless settings.
I have a FactoryTest Kit that may be the same app? But without a proof of concept who can say if the bug even remains?
If you have root, i guess you can disable that app.
---------- Post added at 10:09 AM ---------- Previous post was at 10:03 AM ----------
I extracted it and dumped it. FactoryKitTest.apk is com.huaqin.factory. my version is QL1715_201901180953 which does not match the CVE version. Maybe it was fixed?
---------- Post added at 10:14 AM ---------- Previous post was at 10:09 AM ----------
BTW: This app is normally not even used? It's what runs when you enter *#*#6484#*#* into the dialer. I used it a loooong time ago to verify my LCD does not support DT2W. I have found it to be crashy with Magisk running.
I have the Magisk module "terminal debloater" for "removing" system apps without modifying /system. I removed FactoryKitTest and the phone booted and ran ok. Obviously that dialer code no longer works.
a1291762 said:
I'm no expert in reading CVEs but "something is wrong, but we have no details" hardly seems like a sensible thing to be concerned about.
Click to expand...
Click to collapse
There's 2 of them,
145771 = "The Xiaomi Mi A2 Lite Android device with a build fingerprint of xiaomi/daisy/daisy_sprout:9/PKQ1.180917.001/V10.0.3.0.PDLMIXM:user/release-keys contains a pre-installed app with a package name of com.huaqin.factory app (versionCode=1, versionName=QL1715_201812071953) that allows unauthorized wireless settings modification via a confused deputy attack. This capability can be accessed by any app co-located on the device."
and
145775/145776 = "The Xiaomi Mi A2 Lite Android device with a build fingerprint of xiaomi/daisy/daisy_sprout:9/PKQ1.180917.001/V10.0.3.0.PDLMIXM:user/release-keys contains a pre-installed app with a package name of com.qualcomm.qti.callenhancement app (versionCode=28, versionName=9) that allows unauthorized microphone audio recording via a confused deputy attack. This capability can be accessed by any app co-located on the device. This app allows a third-party app to use its open interface to record telephone calls to external storage."
Well the good news is that both of these apps are apparently safe to remove and don't even require root to do so:
https://forum.xda-developers.com/mi-a2-lite/themes/root-safe-to-remove-bloatware-googleware-t3899139
---------- Post added at 07:38 PM ---------- Previous post was at 07:30 PM ----------
FWIW: I have disabled both apps using the terminal debloater Magisk module and everything seems fine. I even verified that phone calls work
I only did this because I know how to revert that, getting the apps back. I don't know how to revert the "adb remove" stuff that works without root (you probably can't, without getting root first).
---------- Post added at 07:51 PM ---------- Previous post was at 07:38 PM ----------
Just to calm down anyone who reads this thread... These reports are for 10.0.3.0 and 10.0.2.0 so they may have been fixed (this is why you should install security updates).
None of these have been deemed critical, despite the thread title. They have been reported by a company, but have yet to be assessed for severity.
Official links:
https://nvd.nist.gov/vuln/detail/CVE-2019-15468
https://nvd.nist.gov/vuln/detail/CVE-2019-15472
https://nvd.nist.gov/vuln/detail/CVE-2019-15473
Actually, that last one has been analised and was given a severity score of 5.5 (Medium).
perfect_ said:
Xiaomi Mi A2 Lite privilege escalation
[CVE-2019-15468]
[CVE-2019-15472]
[CVE-2019-15473]
Suggesting replace the affected object with an alternative product.
https://vuldb.com/?id.145771
Click to expand...
Click to collapse
Well buddy, I must inform you that we're on the 10.0.16.0 version, not the 10.0.3.0 and neither on the 10.0.2.0.
So please go waste someone else's time.