It is the latest version of Viper, and rooted A1601.
Reported the bug via email to the shown email address, but no reply at all(Tut).
So, anyone can solved this problem?
OPPO F1s 3GB RAM, 32GB ROM
Mediatek(I think the Viper don't really support Mediatek much)(told by my cousin)
Stock ROM used (Color OS 3.0, Android 5.1)
ROOTED...(SuperSU granted its access ,sure)
Viper 4Android worked twice on my device actually,but stopped after that
Driver status is normal and supported when it worked twice, but then driver status abnormal and unsupported audio format!
Solution:
??? HELP, help!
Related
Hi everyone,
i got a problem connecting my Android device to my rk3188 HU via Bluetooth.
My devices:
Google Nexus 5 : Android version - 6.0.1 cyanogenMod
rk3188: Android Version - 4.4.4 Malaysk rom(newest)
Display - 1024x600
To my problem: i can pair my phone to the hu. No problem, but when i want to connect my phone to the rk3188 device it says, that it is connected but telephon is not possible. After that it disconnects itself. The connection breaks up. I tested it on several devices with different Android Version like 4.4.2 and 5.1.1 and it works just like it should. Seems like its an Android 6.0 and higher problem. Is there somebody with the same problem and know how to solve this?
Thank you!
Hi,
i can´t help, but i have similar problems...
My Devices:
LG G4 (Andoid 6.0)
Erisin ES2046B (rk3188 / 1024x600 / newest Malaysk Rom 4.4.4)
I can pair my Android phone to the HU, but when i try to sync my contact list it breaks up the connection.
I tested several MTCBlueTooth.apk (by Malaysk and other) but still the same problem.
I also changed the way of sync in the phone contact list options and tried to send the contacts manually,
but nothing really works.
I also tested another phone (Samsung Galaxy Note 3) a few months ago and it worked like a charm.
Now after an update to Android 6 it seems like the same problem like yours, its still paired but it randomly
breaks the connection.
I´m still holding out hope for a solution and thanks for reading...
Kuba791 said:
To my problem: i can pair my phone to the hu. No problem, but when i want to connect my phone to the rk3188 device it says, that it is connected but telephon is not possible. After that it disconnects itself. The connection breaks up. I tested it on several devices with different Android Version like 4.4.2 and 5.1.1 and it works just like it should. Seems like its an Android 6.0 and higher problem. Is there somebody with the same problem and know how to solve this?
Thank you!
Click to expand...
Click to collapse
Hi,
I have experienced the same issue with CM13 on N7100 and i9506. Appears to be a CM13 issue - perhaps post logcats on CM forums?
-M
marchnz said:
Hi,
I have experienced the same issue with CM13 on N7100 and i9506. Appears to be a CM13 issue - perhaps post logcats on CM forums?
-M
Click to expand...
Click to collapse
i don't know, i still think that it is an android 6.0+ issue. A friend of mine has a android m stock rom and it appears the same problem.
I have an LG G4 6.0 and it works fine with my Joying rk3188. But to be honest I haven't done more than make sure I can stream music and test out the hands free calling features.
I thought I was the only one!....I got a Lenovo zuk z1 with android 6.0.1 and the same problem.....you even can listen to the streaming music through you android car radio, but nothing about calls,.It seems can't synchronize with your contacts.Any help?
My Huawei Mate 8 with Android 6.0 connect perfectly via Bluetooth (phone calls, contacts, music) to my Eonon RK3188 4.4.4.
To all of you who don't have any issues with Bluetooth connection, which Rom have you installed on your HU?
G2110F stock rooted.
Still running the stock ROM it came with. Will give the ROM number next time I get in my car.
Sent from my Nexus 7 using Tapatalk
I can't make any promises, but I'm willing to look into logs from your phones (especially CM13 devices) as I have the same issue. Phone shows up as "Connected (no phone)" and Bluetooth media works fine. Grab a logcat or a bug report and attach or post on pastebin.com and I'll see what I can find.
Sent from my SM-N910P using Tapatalk
Pardon my ignorance here (still learning) but nothing in the "About machine" is labeled as the ROM so I will list the following:
MCU - MTCB-JY-V2.73
Android version - 4.4.4_25082015
Kernel version - 3.0.36+
Build number - rk3188-eng4.4.4.25082015.12:15:58
One thing I did notice when I was pairing my G4 was that the HU was trying to control the pairing where as every other Bluetooth pairing was controlled by the phone. I stopped the HU and used my phone to control the pairing. And I did confirm that all features work properly. I loaded up my directory, controlled music, etc all from my HU.
Sent from my Nexus 7 using Tapatalk
i solved this problem flashing cm12.1 (android 5.1.1) back to my nexus 5. Now everything ist working like it should. I'm little upset to downgrade, because some features are missing which were very important to me. @nivron: i try to find some time to flash to cm13 again and get the logs. After that i will try to post it here or on pastebin.com or both.
nivron said:
Grab a logcat or a bug report and attach or post on pastebin.com and I'll see what I can find.
Click to expand...
Click to collapse
Hi! I have same problems with connecting my OnePlus One (CM13) to HU (RK3188, Android 4.4.4).
I grab logs as you ask. Attached logs represent new connection attempt - I remove all devices and run search. I prepared both log from my phone and HU.
Thanks!
Bodun said:
Hi! I have same problems with connecting my OnePlus One (CM13) to HU (RK3188, Android 4.4.4).
I grab logs as you ask. Attached logs represent new connection attempt - I remove all devices and run search. I prepared both log from my phone and HU.
Thanks!
Click to expand...
Click to collapse
Problem is fixed with latest cm13 nightly... But be aware of the launcher problem! So I would suggest to wait one day! Launcher fix is already added but not in a build!
Cheers
gismo2004 said:
Problem is fixed with latest cm13 nightly... But be aware of the launcher problem! So I would suggest to wait one day! Launcher fix is already added but not in a build!
Cheers
Click to expand...
Click to collapse
It's just a great news! I'd like to thank you for info and great job!
which CM13 will fix the problem? I under 28 and same...
gismo2004 said:
Problem is fixed with latest cm13 nightly...
Cheers
Click to expand...
Click to collapse
I confirm - now BT paired as expected.
Checked on cm-13.0-20160501.
Thanks!
What about those of us not running cyanogen? I have a Nextbit Robin and its bluetooth functionality is heavily impaired thanks to the changes in android marshmallow.
Is there any fix or app to downgrade the bluetooth protocol or something?
Same issue since Marshmallow update
Hi
I have a rooted RK3066 4.4.4 unit and and Xperia M5. Since the Marshmallow update on my M5 i can no longer connect my phone to my headunit. I pairs fine but just connects the reconnects. Has anybody found a solution to this problem?
Hi,
New to this site but having issues with message access in my Peugeot Boxer 2014.
I assume that what is needed is Bluetooth Message Access Profile and my previous stock Rom didn't support this so I flashed the recommended Chroma 6.0.1 custom rom and Gapps and still exactly the same.
In the Bluetooth settings (cog next to devices in list) I get music access, phonebook access but NO message access option.
Does this mean MAP is not supported in Chroma?
Can anyone recommend a way to get my van radio to read out my messages please.
Any help or advice would be very welcome.
Pete
Hi, I have two G9100 ( first white, second black ), white with original Samsung 4.1.2 where Rsap is without problems in my bluetooth car. ( I see three profiles on my bluetooth car radio - connection RSAP mode, HF mode and Audio Mode).
But on my second G9100 with Resurection Remix 5.8.1. - RSAP is not possible, i do not see this mode in car radio connection and Rsap NOT WORKING.
I tried load application RSAP from googleplay, sucesfull installed it, all checkers are green, but RSAP not working too. Do you know some ROM 7.1.1. or 7.1.2., which works with Rsap on G9100? Thank you!
I've successfully used the Android rSAP app with the SGS2 (GT-I9100) and CyanogenMod (up to CM13 Android 6.0.1 Marshmallow). I will give it a try with LineageOS (LOS14.1 Android 7.1.1 Nougat) and report back. Do you have root access? It was mandatory in CM13 to get rSAP access on SGS2..
OllieW said:
I've successfully used the Android rSAP app with the SGS2 (GT-I9100) and CyanogenMod (up to CM13 Android 6.0.1 Marshmallow). I will give it a try with LineageOS (LOS14.1 Android 7.1.1 Nougat) and report back. Do you have root access? It was mandatory in CM13 to get rSAP access on SGS2..
Click to expand...
Click to collapse
Thank you. Yes, I have root access. I am tried only Remix Resurection 5.8.1. Lineage 14.1. i still not tried it.
I will be very happy with your message about it.
OK, I did the installation and rSAP app now reports "SIM Status ready" after turning off and on bluetooth a second time. It's necessary to select "Standard" mode with rSAP install app in advance - i tried with "Android 6+RIL" mode, but then the SIM card won't be detected (no PIN unlock offered) after reboot (although everything was checked green before reboot). Seems to be a problem in RR5.8.1 for me..
OllieW said:
OK, I did the installation and rSAP app now reports "SIM Status ready" after turning off and on bluetooth a second time. It's necessary to select "Standard" mode with rSAP install app in advance - i tried with "Android 6+RIL" mode, but then the SIM card won't be detected (no PIN unlock offered) after reboot (although everything was checked green before reboot). Seems to be a problem in RR5.8.1 for me..
Click to expand...
Click to collapse
I HAVE THE SAME EXPERIENCE.
I have the same idea - an error in RR5.8.1. Therefore seeking alternative ROM Nougat 7 and functional rSAP
MilanXD said:
I HAVE THE SAME EXPERIENCE.
I have the same idea - an error in RR5.8.1. Therefore seeking alternative ROM Nougat 7 and functional rSAP
Click to expand...
Click to collapse
So, LineageOS 14.1. 7.3.2017 - the same result as Resurection 5.8.1. - rSAP is not possible .:crying::crying:
MilanXD said:
So, LineageOS 14.1. 7.3.2017 - the same result as Resurection 5.8.1. - rSAP is not possible .:crying::crying:
Click to expand...
Click to collapse
I confirm, CM 13 . Android 6.0.1. rSAP comunications with my car. I will be very happy with any report on the potential use rSAP with Android 7 Nougat, please !
MilanXD said:
I confirm, CM 13 . Android 6.0.1. rSAP comunications with my car. I will be very happy with any report on the potential use rSAP with Android 7 Nougat, please !
Click to expand...
Click to collapse
I have the same problem on my I9105 with Resurrection Remix 5.8.4 for Android 7.
Are there news about it? Can anybody tell me if RR for Android 7 will sometimes support rSAP or should I step back to RR for Android 6 (last version is 5.7.3) assuming that there will be support for rSAP as in the case of CM13?
Thanks.
@MilanXD: Please correct the phone type in the title of the thread from G9100 to I9100 or GT-I9100. So it can be found better.
The latest official LineageOS 14.1 ROM for GT-I9100 now support rSAP out-of-the-box without installing any app.
So I searched for These and found a app named Miracast enabler. Thanks To @r3pwn
Though the app is not the only thing that will enable miracast there are some other things to do....
**A rooted Phone must required for this. And LineageOS or LOS based ROM.
So...
Here are the steps.....
1) First add the line in your build.prop and restart ur device.
persist.debug.wfd.enable=1
2)Now download the Apk and install
Link -- https://drive.google.com/file/d/1qIaDJmdbIJKvJEw-MZmhhvkoTpPdQ9-5/view?usp=drivesdk
Then open the app and give root permission then click on install. Give storage permission if it ask.
2) Now download Mirror enabler from this thread
Thread Link -- https://forum.xda-developers.com/android-tv/chromecast/experimental-enable-mirroring-device-t2812193
Direct download link from thread --- https://www.androidfilehost.com/?fid=95784891001616583
Open It and give root permission
Then u will see 3 options Disabled
Enable Them one by one! Then restart your phone! ( If The app crashes Try yo enable 2nd option first then reboot then Enable other 2 options.Then reboot)
After that goto Settings >Display> Cast then click on option(3 dot in the top). Then mark "Enable Wireless Display".
Now u will be able to cast ur device screen on any wireless display!
*****This tricks is tested on Redmi 3 with Lineage14.1+Opengapps nano.
Does this work con LoS 15.1?
Does anyone know why Miracast support is not included in LoS?
Thank you! I have Redmi 3 too and this instructions work for me!
webr0ck3r said:
Thank you! I have Redmi 3 too and this instructions work for me!
Click to expand...
Click to collapse
Which option you have success connect to wifi display?
Android Pie
Does this app also works for android pie (Lineage 16), because there is native mirrcast Support dropped?
i try it without sucess on mi note6 pro pixel experience android 9.0 , and lg g3 android 9.0 lineage big probleme with miracast on android pie rom
i try many fix but not working
MirrorEnabler is Incompatible with my device
I'm currently running Lineage 16 on an A7 2017
I've done the first few steps, but the MirrorEnabler says its incompatible with my device and I'm lacking audio_submix file and I should contact my provider, what does this mean? And can it be fixed??
Is it compatible with ZTE Blade V7 Lite phone(Android 6 version) that has no built in screen mirroring function at all?? ?
RobNg said:
Is it compatible with ZTE Blade V7 Lite phone(Android 6 version) that has no built in screen mirroring function at all?? ?
Click to expand...
Click to collapse
I doubt it, except if you are running a LOS 14 (based) ROM. But try it out and report: Make a backup in TWRP, install the apks as explained in the OP and try it out. If it works, great, if it doesn't just restore the backup from TWRP and tell us in this thread if it did(n't) work.
Patolaa said:
I'm currently running Lineage 16 on an A7 2017
I've done the first few steps, but the MirrorEnabler says its incompatible with my device and I'm lacking audio_submix file and I should contact my provider, what does this mean? And can it be fixed??
Click to expand...
Click to collapse
same here. lacking audio_submix file.
I didn't get any help!
Hey I think this project is dead, so probably we won't get any response from the developers. Also I left Lineage Os for crDroid, and I am a lot happier with crDroid mainly because ScreenMirrowing is work, Hotspot, ECT. Sound works absolutely fine, you can fix some call cracks by turning off (Google's) Microphone! Here's a link , check it out and a lot of what's working in crDroid compared to Lineage Os whether 14.1/15.0 or 16. Enjoy -- https://forum.xda-developers.com/sa...pment/unofficial-crdroid-5-7-a5-2017-t3958315
Riyad_ said:
So I searched for These and found a app named Miracast enabler. Thanks To @r3pwn
Though the app is not the only thing that will enable miracast there are some other things to do....
**A rooted Phone must required for this. And LineageOS or LOS based ROM.
So...
Here are the steps.....
1) First add the line in your build.prop and restart ur device.
persist.debug.wfd.enable=1
2)Now download the Apk and install
Link -- https://drive.google.com/file/d/1qIaDJmdbIJKvJEw-MZmhhvkoTpPdQ9-5/view?usp=drivesdk
Then open the app and give root permission then click on install. Give storage permission if it ask.
2) Now download Mirror enabler from this thread
Thread Link -- https://forum.xda-developers.com/android-tv/chromecast/experimental-enable-mirroring-device-t2812193
Direct download link from thread --- https://www.androidfilehost.com/?fid=95784891001616583
Open It and give root permission
Then u will see 3 options Disabled
Enable Them one by one! Then restart your phone! ( If The app crashes Try yo enable 2nd option first then reboot then Enable other 2 options.Then reboot)
After that goto Settings >Display> Cast then click on option(3 dot in the top). Then mark "Enable Wireless Display".
Now u will be able to cast ur device screen on any wireless display!
*****This tricks is tested on Redmi 3 with Lineage14.1+Opengapps nano.
Click to expand...
Click to collapse
Force-Close FIX button is DISABLED (cannot be enabled).
App force closes. How to fix sir?
CANNOT ENABLE WIRELESS (MIRROR CASTING) ON DEVICE running Pie
Will it work on aosp based rom ?
In Lineage 17.1 its posible ?
doesnt work on Lineage 18.1 (galaxy mega 6.3) and the problem still persists ..
Hello guys
My device is H4S01 (sky)
cpu:S905X
rom:8gb
ram:2gb(DDR4)
I downloaded it from the website
Aidan's ROM Android TV 7.1.2 (successfully s flashed in)
Problem: no BCM wife normal resolution only ssupport 1080p 60fps my monitor is 2k 144fps
I think it's because my system version is too low, or there is no some driver that causes the resolution to be low
So I saw another rom
[v9] Aidan's ROM [S905X] [ATV 9] (Universal RTL & BCM).rar
This is the best one I've seen so far for me
But I can't get this firmware in using usb_tools
There is an error report exception (device enumeration error)
I'm pretty sure there's nothing wrong with the way I'm doing it, because I flashed Aidan's ROM Android TV 7.1.2 with the same operation
Anyone who is willing to help me can sponsor me via PayPal