Related
Hello everyone,
I'm new to this forum so hopefully, I'm posting to the right section. If I'm not, please let me know where I should be posting.
I'm the owner of the Oppo Find 5 and have been using the OmniROM since December, flashing it to the latest nightly on a daily basis.
I recently used the nightlies form 3/24 to 3/26 and have noticed the following issue with these releases:
Unable to connect to Wi-Fi networks. I click to connect but it never does. The Wi-Fi icon doesn't appear in the top right hand corner either.
I can receive calls, but cannot place them. Every time I try, the call just ends
Another observation I have is after 3/23 the size of the nightly zip file has decreased from ~187MB to ~177MB.
I have reverted back to the 3/23 build and both the Wi-Fi and call placement functions were fine. It's only when I update to 3/24 build or later do I encounter the aforementioned issues.
Please advise or confirm if the issues can be duplicated.
Big OmniROM fan by the way.
Thanks and regards.
Starting from the 3/24 build, you must flash the 4.2 modem or wifi and/or calls won't work.
Check here : https://plus.google.com/102780705077397176621/posts/VqxUMPEumx7
That worked. Thanks!
Q&A for [ROM][CM10][CM10.1][CM-10.2][CM-11.0][GT-S7710] Samsung X Cover 2
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][CM10][CM10.1][CM-10.2][CM-11.0][GT-S7710] Samsung X Cover 2. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Kosh_swe said:
Cm10.2 is all BUT stable! ...
My hardkeys (back/menu/home) stopped working ONLY on flxo/Vanir firmwares, ive tried both cm10.2 (20140204_cm_10.2_skomer-ota-eng.flx, which is supposed to be "rock solid", i dont want nightlies since this phone is going to my gf so im after a stable firmware) but i've also tried latest nightly vanir 4.4 but that got the same bug in it!
...
Click to expand...
Click to collapse
@Kosh_swe, have you found a solution? I also failed to get the Vanir ROM to work and I'd consider the flox CM10.2 ROM. Your post suggest that my radio would be dead in flox, too.
---------- Post added at 12:35 PM ---------- Previous post was at 12:26 PM ----------
Matt64 said:
Hey guys,
I recently compiled flxo CM11.0 rom with STE OMX support (from TeamCanjica).
I've been testing it for a couple of weeks, for me everything seems ok (no reboots, camera working ...)
I didn't test bluetooth hand's free, but it's certainly still broken.
You can download this rom from my dropbox account :
xxx
I'm also trying to compile Ubuntu Touch for S7710, I'll let you know when the rom will be flashable.
Click to expand...
Click to collapse
@Matt64, could you provide a hands-on on how to do the compiling?
Never mind, fixed my radio issue. See http://forum.xda-developers.com/showpost.php?p=56293409&postcount=37
Testing radio issues
Hi to all,
I just tested radio issues on my phone. I was researching, why radio is not working.
Here are results, maybe it will help. Anyway, I have my GT-s7710 for testing and I can do some tests or catch some debug informations if needed.
It seems that problem why radio is not working is located in modem-supervisor process. In original firmware, this process is responsible for uploading firmware into dbx500 platform chip. But in CM, there is no such process.
I am not expert, but it seems to.
I tried to use old modem-supervisor process to make everything working.
Services line from original fw:
Code:
service modem-supervisor /system/bin/modem-supervisor -r -f /dev/dbx500_mloader_fw -i /sys/devices/platform/ab8500-i2c.0/chip_id -c monitor -t 0
but it needs to be changed because /sys/devices/platform/ab8500-i2c.0/chip_id changed to /sys/devices/platform/ab8505-i2c.0/chip_id
Problem is that firmware event for loading firmware is never generated and firmware is not uploaded.
I have some dumps and traces if you need them. Thank you for your work!
Lukas
loneraver said:
I tried it, and got none of the "known" issues. Give it a try. If you get any issues, you can always flash back to stock rom.
Click to expand...
Click to collapse
Your "tested" devices are just headphones, right?
The Problem is not the hearing part - the microphone signals are blocked...
if you have a real headset - please try with that one again and tell me
an idea
The 7580's phone hardware is almost identical to the 7710. The processor in the 7580-higher heights, but the hardware buttons and then there are all of the functions, but it has the 4.2.2 firmware, which allow moving to the SD card. Somehow it should possess to operate from 7710.
I'm Hungarian, sorry if the translation is wrong, happened with google.
Okay so I am having the same problem with HW buttons as many others before me...
http://forum.xda-developers.com/showpost.php?p=51234756&postcount=329
http://forum.xda-developers.com/showpost.php?p=51253847&postcount=333
http://forum.xda-developers.com/showpost.php?p=54973574&postcount=362
Click to expand...
Click to collapse
After clean 1st boot after the installation the buttons are working perfectly, but after reboot (2nd boot) they are not working properly. Only long presses are working (google search by long press of menu button, kill aplication by long press of back button, last apps by long press of home button).
So? There is no such responde on how to fix that..!
DaGrizzly said:
Your "tested" devices are just headphones, right?
The Problem is not the hearing part - the microphone signals are blocked...
Click to expand...
Click to collapse
In my cited post I refer to a previously made post where I listed the devices:
loneraver said:
I tested it with logitech ue9000 and samsung hs2000.
Click to expand...
Click to collapse
Both are real headsets with working mics.
Know it's OT but if it's true it's exiting:
Miui for our phone coming?
http://forum.xda-developers.com/showthread.php?p=58720490
Sent from my GT-S7710 using XDA Free mobile app
Sent from my GT-S7710 using XDA Free mobile app
Try other
this one is very very STABLE :
http://forum.xda-developers.com/showthread.php?t=2689010
XCover 2: BT hands free - Problem fixed yet?
Hey developers,
I was wandering if the BT problem has been fixed for Cyanogenmod Version 10.2 for XCover 2.
BT hands free. Connection/pairing works, but the audio path is broken.
Thanks a lot!
baseband wipe
I can't get Cyanogenmod 10.2 working. Everytime installation wipes my baseband.
When I install the Stock ROM SIM works again - but after flashing CM again also wipes baseband again.
My Installation-Tools:
Odin v3.07
CMW: 20140112_cwm-6.0.4.6_skomer_fixed.tar.md5
CM: 20140204_cm_10.2_skomer-ota-eng.flx.zip
Is there any chance to install the baseband (I think it's inside the modem.bin)?
No network available in Polish Play
I'm installing CM for my father in law on Samsung X Cover 2 and I'm facing problem with no available network.
I've tried CM 11 and CM 10.2 - both are running fast but both doesn't recognize any network operator.
CM11 has additional problem with hanging during shutdown.
I've found that Polish network Play has common problems with radio: like here
https://code.google.com/p/cyanogenmod4milestone/issues/detail?id=510.
But even I'm putting T-Mobile sim card then still phone doesn't recognize (phone is coming from Play but it is unlocked).
When I restored Play stock ROM then it works.
Could anybody help in this?
I cannot point link to logcat because new user limitation - pastebin URL part is rWttd9PH
sk_8x said:
I'm installing CM for my father in law on Samsung X Cover 2 and I'm facing problem with no available network.
I've tried CM 11 and CM 10.2 - both are running fast but both doesn't recognize any network operator.
CM11 has additional problem with hanging during shutdown.
I've found that Polish network Play has common problems with radio: like here
https://code.google.com/p/cyanogenmod4milestone/issues/detail?id=510.
But even I'm putting T-Mobile sim card then still phone doesn't recognize (phone is coming from Play but it is unlocked).
When I restored Play stock ROM then it works.
Could anybody help in this?
I cannot point link to logcat because new user limitation - pastebin URL part is rWttd9PH
Click to expand...
Click to collapse
Forget CM en try Vanir or MIUI these are more up2date. Also CM11 is alpa with camera bug:
First look at: http://forum.xda-developers.com/t/xcover-2
Vanir
Second, I use Vanir 4.4.4 daily. It has some bugs, but not some bugs that makes it unstable. Known issues:
Start/Stop navbar after every restart
Use this solution to fix connection errors after a fresh Flash: http://forum.xda-developers.com/showpost.php?p=60411469&postcount=612
Other small bugs:
2G/3G quick setting and normal settings dont work properly because of absence of LTE
Navigation Ring and immersive mode causes dead touch screen space
DSP manager doesn't work
After using Vanir 4.4.4 I never want to go back! It's that much faster, more free RAM en better battery performance. Because of the better RAM performance, you must kill apps more often else it will drain the battery quicker :silly:.
Best way to Flash with 4.4.4 is to first flash Clockworkmod through ODIN, then do the usual Full Wipe --> Wipe Cache --> Flash Rom --> Flash GAPPS. Here is a video of someone doing these things. P.S. in this video the process is speeded up also reboot can freeze the system (just remove battery after a couple of minutes)
Files
Vanir: https://drive.google.com/file/d/0B7agwkTbiz0pNHZMQlpudkR4NUU/view
GAPPS: https://mega.co.nz/#!kokjzJwT!eqmMam5r5N2kWvtmSMy4QnaHnxvoqhDtr_joSDU5anI
MIUI
Another option is MIUI (used on the the popular Chinese Xiaomo phones). Instead of the Vanir build, this build is still being maintained. But because it's based on Vanir it has most likely has the same bugs. Never tried it because I prefer stock Android.
2nd, the connection error fix for vanir could also work for CM (vanir uses stuff from CM).
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 friends!
I used to be on Dirty Unicorn and ElementalX kernel. I was able to pair the bluetooth with my mini cooper so that I am able to make calls or answer calls in my car handsfree.
Today i decided to flash Paranoid Android. I did a clean flash by wiping everything except internal storage, followed by flashing PA, then supersu, then elementalx. When i went for a drive later at night, I realised that my bluetooth was unable to pair with Mini. It was able to find the Mini in the bluetooth list, but clicking on it it will say pairing and then it stopped, as if i have never clicked on pairing. Repeated attempts gives same result. I am just unable to pair with my Mini cooper.
Is there anyway I can make it pair? Was it my bluetooth driver or something (which i highly doubt). Im on the latest June security update, it was also working with the latest june security update before.
Although im not hopeful that this problem could be solved, just wanna try my luck and see if there happen to be any mini cooper owner or anyone who understands and can offer me advise. Thanks!
sp0rky said:
Hi friends!
I used to be on Dirty Unicorn and ElementalX kernel. I was able to pair the bluetooth with my mini cooper so that I am able to make calls or answer calls in my car handsfree.
Today i decided to flash Paranoid Android. I did a clean flash by wiping everything except internal storage, followed by flashing PA, then supersu, then elementalx. When i went for a drive later at night, I realised that my bluetooth was unable to pair with Mini. It was able to find the Mini in the bluetooth list, but clicking on it it will say pairing and then it stopped, as if i have never clicked on pairing. Repeated attempts gives same result. I am just unable to pair with my Mini cooper.
Is there anyway I can make it pair? Was it my bluetooth driver or something (which i highly doubt). Im on the latest June security update, it was also working with the latest june security update before.
Although im not hopeful that this problem could be solved, just wanna try my luck and see if there happen to be any mini cooper owner or anyone who understands and can offer me advise. Thanks!
Click to expand...
Click to collapse
If I had a guess it's PA is only early development for them so that could be it
jaythenut said:
If I had a guess it's PA is only early development for them so that could be it
Click to expand...
Click to collapse
oh well...
sp0rky said:
Hi friends!
I used to be on Dirty Unicorn and ElementalX kernel. I was able to pair the bluetooth with my mini cooper so that I am able to make calls or answer calls in my car handsfree.
Today i decided to flash Paranoid Android. I did a clean flash by wiping everything except internal storage, followed by flashing PA, then supersu, then elementalx. When i went for a drive later at night, I realised that my bluetooth was unable to pair with Mini. It was able to find the Mini in the bluetooth list, but clicking on it it will say pairing and then it stopped, as if i have never clicked on pairing. Repeated attempts gives same result. I am just unable to pair with my Mini cooper.
Is there anyway I can make it pair? Was it my bluetooth driver or something (which i highly doubt). Im on the latest June security update, it was also working with the latest june security update before.
Although im not hopeful that this problem could be solved, just wanna try my luck and see if there happen to be any mini cooper owner or anyone who understands and can offer me advise. Thanks!
Click to expand...
Click to collapse
I had a similar issue with mine, but I were able to make it pair from my car(making the pairing request from my multimedia) and not from the phone.
zopostyle said:
I had a similar issue with mine, but I were able to make it pair from my car(making the pairing request from my multimedia) and not from the phone.
Click to expand...
Click to collapse
I only have AUX and USB under my multimedia option in mini visual boost... i think i gonna flash back to Dirty Unicorn
I recently bought a FLIR ONE thermal imaging camera. Unfortunately, the device is not detected on my D802 using any marshmallow ROM.
I was using Resurrection Remix rom, but also tried Paranoid, XOSP, Dirty Unicorns, AICP, .... with no luck. Also, flashing Dorimanx and Lambda kernel didn't help.
When I run Chainfire USB Host Diagnostics, it says the kernel supports it, but OS does not.
On Lollipop (stock-based) roms, there is no issue, and the device is detected.
Can someone explain why the marshmallow ROMs miss this support. Is there any way to get this working ? I'm now running a LP rom again, just to be able to use the cam, but it really feels like a downgrade.
Same here, did you manage to fix it?
tehsYs said:
Same here, did you manage to fix it?
Click to expand...
Click to collapse
No fix other than going to stock based ROM or other phone.
All mm/aosp/caf roms are using a generic otg driver that breaks support for usb host intent filters. In other words, the phone won't broadcast to applications the a usb otg device has been plugged in.
It's not just your device in question, any device other than flash storage doesn't get detected. A developer could probably fix this but as it is broken in all non-stock roms it would probably be challenging to fix.
I do android development Mostly for the droid turbo, apps and tweaks. I think i may be able to help out here.
I did manage to get flir one working on none stock rom last night. It worked fine on stock. Then i seen this post installed cm and no joy. So after a bit of tweaking i did get it to work. I will see if i can come up with some kind of Universal patch for all users.
I will try and post a how to video to get it working on non stock roms. I am going to pull out some other phones to see if the patch works on all phones.
Keep an eye on my youtube channel http://www.youtube.com/iphostway/videos
I will work on a Universal fix starting today.
computerfreek274 said:
I do android development Mostly for the droid turbo, apps and tweaks. I think i may be able to help out here.
I did manage to get flir one working on none stock rom last night. It worked fine on stock. Then i seen this post installed cm and no joy. So after a bit of tweaking i did get it to work. I will see if i can come up with some kind of Universal patch for all users.
I will try and post a how to video to get it working on non stock roms. I am going to pull out some other phones to see if the patch works on all phones.
Keep an eye on my youtube channel http://www.youtube.com/iphostway/videos
I will work on a Universal fix starting today.
Click to expand...
Click to collapse
That would be really cool
If I can help testing your fix, please let me know.