Hi all, my system works great except for one small problem. Bluetooth works with my phone and other devices, however when I connect an OBDII adapter after coming out of sleep or when booting up it seems to do it twice. I get the boot animation come up, then the home screen shows for about one second where I can operate the device then the boot animation comes up again. After the second bootup everything works fine, including Torque. Any thoughts?
Model #: S07
MCU version:
MTCB-KLD6-V2.86
Mar 21 2016 22:33:56
Android version:
5.1.1
Kernel version:
3.0.101+
[email protected] #34
Wed May 11 16:49:48 CST 2016
Build number:
rk3188-userdebug 11052016.20:05:38
Same problem here...
ksin86 said:
Hi all, my system works great except for one small problem. Bluetooth works with my phone and other devices, however when I connect an OBDII adapter after coming out of sleep or when booting up it seems to do it twice. I get the boot animation come up, then the home screen shows for about one second where I can operate the device then the boot animation comes up again. After the second bootup everything works fine, including Torque. Any thoughts?
Model #: S07
MCU version:
MTCB-KLD6-V2.86
Mar 21 2016 22:33:56
Android version:
5.1.1
Kernel version:
3.0.101+
[email protected] #34
Wed May 11 16:49:48 CST 2016
Build number:
rk3188-userdebug 11052016.20:05:38
Click to expand...
Click to collapse
Same issue here, however I do not have an OBD device connected to BT. I'm am running Booroondook's 5.1.1 ROM. I did not have this issue on stock 4.4.4 firmware.
I have this same issue on Malaysk's 5.1.1 rom. Has anyone tried a USB OBDII reader to see if they get the same results?
I have the same problem with my Pumpkin 6,95inch car radio (Android 5.1.1 - MCU-Version KLD6-V2.85). Since I connected an OBD device via bluetooth, the radio allways boot up twice. So I wrote Pumpkin about the problem and they sent me a firmware-update. After I installed the update, the radio boots up but the display stays black. So I installed the latest MCU (MTCC KLD9 v2.98) and after that the firmware-update again. Now, the black display is history, the rebooting-problem still exists. It makes me mad
Does anyone here has a solution for problem already?
Related
I've been running AOSB on SGH-T999 for several months. Upgraded to AOSB 1.3.6 (Android 4.4.4) yesterday and Bluetooth is no longer functioning and will not pair with any Bluetooth devices, i.e. my phone does not see any devices and other devices do not see my phone. I've reinstalled the ROM (wiped cache and dalvik only, not a clean install; was previously on 1.3.5).
Build #: cm_d2lte-userdebug 4.4.4 KTU84P 30a2494bce test-keys
CyanogenMod version: 11-20140628-unofficial-d2lte
Baseband: Y999UVDLJA
Kernal: 3.4.95-cyanogenmod-gd55ed95
Anyone else experiencing this issue with AOSB 1.3.6 or any other ROM?
Ditto
yardsale said:
I've been running AOSB on SGH-T999 for several months. Upgraded to AOSB 1.3.6 (Android 4.4.4) yesterday and Bluetooth is no longer functioning and will not pair with any Bluetooth devices, i.e. my phone does not see any devices and other devices do not see my phone. I've reinstalled the ROM (wiped cache and dalvik only, not a clean install; was previously on 1.3.5).
Build #: cm_d2lte-userdebug 4.4.4 KTU84P 30a2494bce test-keys
CyanogenMod version: 11-20140628-unofficial-d2lte
Baseband: Y999UVDLJA
Kernal: 3.4.95-cyanogenmod-gd55ed95
Anyone else experiencing this issue with AOSB 1.3.6 or any other ROM?
Click to expand...
Click to collapse
This Happened to me as well, even did a complete wipe and even ended up reflashing the modem file due to losing service/baseband..... anyone know of a solution?
Just flash in TWRP three times. Works every time for me.
Dr. Singh IT Guru said:
Just flash in TWRP three times. Works every time for me.
Click to expand...
Click to collapse
I'll try it again with TWRP. Ever since the AOSB OTA went live, I've been flashing through the application, perhaps there is some interference. Will flash this evening directly through TWRP and report results following.
Thanks.
yardsale said:
I'll try it again with TWRP. Ever since the AOSB OTA went live, I've been flashing through the application, perhaps there is some interference. Will flash this evening directly through TWRP and report results following.
Thanks.
Click to expand...
Click to collapse
Reflashed several more times through TWRP, no change, Bluetooth still not working.
Some ROMs for the d2lte do not have working BT at this time. There are a few that have working BT however. I don't know all of them that have working BT, but I know that Carbon for sure has working BT.
GS³: Carbonized, LeanKernel'd, Philz'd
mp3deviant721 said:
Some ROMs for the d2lte do not have working BT at this time. There are a few that have working BT however. I don't know all of them that have working BT, but I know that Carbon for sure has working BT.
GS³: Carbonized, LeanKernel'd, Philz'd
Click to expand...
Click to collapse
Thanks, mp3deviant721. I noticed many others are having the same problem. For now, I'll do without BT and wait for the next release of AOSB, if my BT withdrawals get too severe, I'll revert to the previous version.
Hello when I'm on the stock rom or any stock based rom the connection between my smartband talk swr30 appears like this //images.tapatalk-cdn.com/15/11/22/9cb1436cd57d0043be16dac3a9e879b3.jpg only call audio.
cant post links copy the text after the //
The problem is that I cant use voice commands or answer messages by voice because the smatbands mic isn't recognised.
Other devices work perfectly an pair like this //images.tapatalk-cdn.com/15/11/22/46c2e329efa11203d145add97219cc02.jpg with call audio and media audio.
But when I flash any aosp or cm based rom the smartband talk connects with media and call audio, the voice commands work, everything works perfectly.
Any ideas?. There is something i can modify on stock bluetooth files [emoji23] ?. I dont know any help is appreciated[emoji3] and sorry my english hope you understand.
Sent from my LG-D855 using Tapatalk
Any ideas?
Hello,
I have exactly the same problem ! (I received my Swr30 three days ago for my birthday)
Do You find a solution about the Bluetooth ?
If not, I think that I'll try to flash a cm rom, but it will be cool if I 'll don' t need to do that.
Sorry too for my en glisse.
Have a good Day !
I had the very same problem with Garmin VivoActive with stock v30N EUR.
Instead Garmin works with Fulmics 7.6.
Instead I have another bluetooth problem: no voice commanding with JVC car radio KD-784BT and Motorcycle Intercom Midland BT-X1 FM.
Voice commanding work with:
- LineageOS 14.1
- RR 5.8.4.
They do not work with:
- Stock v30n EUR
- Fulmics 7.6
- Stock v21A
- Stock V30A (March 2017) Bumped
- Stock V30A (March 2017) Bumped + Xceed Kernel
I have a Joying car radio RK3188 1024x600 and it works fine till I got laast week on my Oneplus One smartphone Marshmallow update (Cyanogen OS 13).
Now I can't connect my device anymore via bluetooth.
I can see that the two devices are paired but the letters on the radio screen are still white an phonebook is not available. On my smartphone I see under bluetooth settings that there is a connection but without phone funktion.
I contact manufacturer and he offered to go into recovery and wipe all data/ factory and cache reset and then install firmware. I did this exactly two times with firmware JY_rk3188_h(20160222) RK3188 1024*600 from february and the latest firmware JY_rk3188_h(20160328) RK3188 1024*600. But I still can't connect phone with bluetooth, has someone an idea and maybe the same problems?
MueKo said:
it works fine till I got laast week on my Oneplus One smartphone Marshmallow update (Cyanogen OS 13).
Now I can't connect my device anymore via bluetooth.
Click to expand...
Click to collapse
Well known problem with CM13 and HU bluetooth...
Apparently no other solution than going back to CM12, at least for Oneplus smartphones.
themissionimpossible said:
Well known problem with CM13 and HU bluetooth...
Apparently no other solution than going back to CM12, at least for Oneplus smartphones.
Click to expand...
Click to collapse
Thanks for your answer. Is it known where the problem comes from, CM13 or HU?
MueKo said:
Is it known where the problem comes from, CM13 or HU?
Click to expand...
Click to collapse
My speculation is that there might be some incompatibility between the 2 Bluetooth stacks profile implementation... as the problem is only with CM13, this incompatibility should be mostly ascribed to CM13.
Same issue here
Does anyone know if this will be resolved in an update to CM13?
I found a thread saying this:
open the /system/etc/init.qcom.bt.sh and edit the following line:
Setprop ro.bluetooth.hfp.ver 1.7
... To:
Setprop ro.bluetooth.hfp.ver 1.5
But my phone is not rooted
This is interesting, maybe someone has a rooted OnePlus One and can test this?
Tested and Working well
Tested and making no difference. Still no phone BT connection to my car hands-free head unit.
PAPPAFRITAS said:
Tested and Working well
Click to expand...
Click to collapse
Can you specify which OS do you have used.
Same issue here, now on CM13-20160415-NIGHTLY-bacon... I hope in the near future it will come fix... (MCU KGL5 2.55)...
ranmic said:
Does anyone know if this will be resolved in an update to CM13?
I found a thread saying this:
open the /system/etc/init.qcom.bt.sh and edit the following line:
Setprop ro.bluetooth.hfp.ver 1.7
... To:
Setprop ro.bluetooth.hfp.ver 1.5
But my phone is not rooted
Click to expand...
Click to collapse
Worked like a charm for me!
OnePlus One on Android 6.0.1 - first time Bluetooth is actually working with that unit.
Fixed in nightly 2904 and working perfectly since.
Sent from my Bacon via XDA free
Today I checked this solution. I rooted my OnePlus One with CM13.0 and edit init.qcom.bt.sh file like this:
ranmic said:
Does anyone know if this will be resolved in an update to CM13?
I found a thread saying this:
open the /system/etc/init.qcom.bt.sh and edit the following line:
Setprop ro.bluetooth.hfp.ver 1.7
... To:
Setprop ro.bluetooth.hfp.ver 1.5
Click to expand...
Click to collapse
And I can confirm that it works.
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
This firmware was developed for the p905. It doesn't apply to the p905v at this time because it's bootloader locked and a custom recovery isn't possible.
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
I'm using nano gapps.
Instructions
1. Install custom recovery
2. Download the zip(s) - firmware and Google Apps additional package (optional)
3. Backup all partitions (it least efs) and store somewhere - it need to do - because you can loose imei
4. Full wipe all
5. Flash firmware and gapps
Work
All
Known Issues
Rotate buggy a bit
Links
LineageOS Builds
11. 20200411: march security patch, kernel update: https://drive.google.com/file/d/1-wnPhbSngsVtXMHiIP0SFEyZI4Q8C0GI/view?usp=sharing
10. 20191211: december security patch: https://drive.google.com/file/d/1orGzMGWg00oIeeDxCHjRzULpmC49s3Oo/view?usp=sharing
9. 20191113: november security patch: https://drive.google.com/file/d/1a1kpJrSSMB-5E_3e63W45dFNVMOcu6zR/view?usp=sharing
8. 20191023: october security patch: https://drive.google.com/file/d/1K_yyDFPhnWHzF-AlITWrJ6nKVV9g0Hys/view?usp=sharing
7. 20190912: september security patch: https://drive.google.com/file/d/1XJVJ3n-jqUL8IA5xhjgjNKhGzCQnNoMS/view?usp=sharing
6. 20190811: august security patch: https://drive.google.com/file/d/1hZqmxaVkUykhgiSpiDbxsHq5QWLu5C94/view?usp=sharing
5. 20190708: july security patch, kernel up to orignal msm8974 lineage kernel, small sensors update: https://drive.google.com/file/d/1Db52CGuuK-9bz0Rs24J2RIT0YntRVSUE/view?usp=sharing
4. 20190528: may security patch: https://drive.google.com/file/d/1kekyqJUVtIzU4rjK4YNQz9w0Y57G_s0i/view?usp=sharing
3. 20190327: https://drive.google.com/file/d/1Ub1aCJHr9JV9Uo__9sbWfm2ZySSBLDWT/view?usp=sharing
2. 20190219: fix flip, fix mic gain: https://drive.google.com/file/d/1K2wJJGox4qAURyWeGxZsPuJoYYZTRx0w/view?usp=sharing
1. 20190217: https://drive.google.com/file/d/1n_HNKxZYvt5VIQ2gf-h7hri6fkltqjcX/view?usp=sharing
Gapps
https://opengapps.org
Recovery
Use official 3.0.2-0 version from: https://twrp.me/samsung/samsunggalaxynotepro122qcom.html
or use my twrp version: https://forum.xda-developers.com/galaxy-note-pro-12/development/recovery-twrp-3-1-1-0-t3684802
Sources
Sources: https://github.com/Lineageos
Device: https://github.com/Valera1978/android_device_samsung_viennalte
Kernel: https://github.com/Valera1978/android_kernel_samsung_msm8974
Vendor: https://github.com/Valera1978/android_vendor_samsung_viennalte
Thanks
Thanks to LineageOS team
Hi all
I'm here, i'm still continue working on note pro 12.2.
I was absent for a while, it was a lot of another projects.
Time ago I started work on treble project for our 12.2 and it was almost done, now i'll continue work on it, based on lineage pie sources.
And then I'll try to make actual stock (8,0+) port, based on treble.
Thx a lot,
On evening the flash party started [emoji16]
Found simular issues as with CrDroid :
Notification Loop sound, if the power cable is connected ( slow charging)
Very Low Mic on WhatsApp / Sound recorder... OK Google is working..
Magnet Flipcover doesn't open /close the screen
Magisk 7.0&18.1 is working
which one would you recommend ?
lineageos 16.0
or
[ROM][P905][UNOFFICIAL] CrDroid-5.1 | Android 9.0 20190217
Form my point of view in this Moment: CrDroid, if root is working...
The sound loop is the notification for charging. i dont know, wäre I can disable this in this Rom.
Gesendet von meinem SM-P905 mit Tapatalk
Valera78 Thank you for your work!
For first 12 hours I have no problem with battery drain.
BT keyboard connect (logitech K480).
WiFi and 4G works good too.
Apps and data restring paused and cannot to finish.
As you describe some lags with change screen orientation.
S-Pen works well in Squid , Google Keep, MS OneNote and Google handwrite
Thanks @Valera1978, great work...
I installed the Rom with dirty flash over the 15.1.
Then opengapps nano and Magisk 18.1 with TWRP flashed.
Everything works so far, including root.
Only one thing ... The security patch level is given as May 1th 2016. Is that correct ?
Many Thanks again...
bemanet said:
Thanks @Valera1978, great work...
I installed the Rom with dirty flash over the 15.1.
Then opengapps nano and Magisk 18.1 with TWRP flashed.
Everything works so far, including root.
Only one thing ... The security patch level is given as May 1th 2016. Is that correct ?
Many Thanks again...
Click to expand...
Click to collapse
This is correct. This is date from our original latest P905XXUABPE2
I can skip it and this field will be empty.
It does not affect anything, just the information on the date of the vendor.
Main security patch level - this is feb 5, 2019 - it's come from android sources.
s-pen
dan435 said:
Valera78 Thank you for your work!
For first 12 hours I have no problem with battery drain.
BT keyboard connect (logitech K480).
WiFi and 4G works good too.
Apps and data restring paused and cannot to finish.
As you describe some lags with change screen orientation.
S-Pen works well in Squid , Google Keep, MS OneNote and Google handwrite
Click to expand...
Click to collapse
Thanks for the awesome rom.... I noticed that the s-pen does work very well. But would it be possible to look at the palm rejection as it is not working. Battery stand by is awesome. Rotation is still a bit ******ly, i have to push the screen off button to rotate back to landscape from portrait.
Once again thank you for keeping our 12.2 alive.
@Valera1978
1. Palm rejection not working. PR did not work since your 8.X rom. If there is no fix I need to go back to 7.1. I used Lecture Notes for testing. S-Pen not working on a Note device makes no sense to me.
2. Charing sound using Samsung network dongle causes the device to play some unknown alarm instead of the standard notification sound. It seems the alarm sound caused by charging can only be stopped by rebooting. Turned it off in the settings. That's o.k.
3. Rotations seems to work - sometimes. After booting it works, then it seems later it does not anymore.
4. Could be me, but I think charging is slower than using 7.1.
If you can't fix PR can you continue to update the 7.1 rom?
I don't get this. The P905 device is the last of its kind. Big 12" IPS screen with pen support. The Note 12.2 is in the category of an Apple Ipad Pro but Samsung abandoned this line. Well they seem only be interested in the mass market. Fair enough, so does Google save their android eco-system? No, their newest tablet is a chrome OS bastard which is neither Chrome OS nor android.
Hi. Does it works for p905m ?
This firmware and the CrDroid version is very simular.
The issue e. g. with the notification tone during charging can be disabled in the CrDroid version
Resolved by wiping all and reflash the rom, thanks for your awesome job !
One issue same as mentioned above that the palm rejection has not been supported, which is most important to me for my heavy using the squid and onenote apps . So can PR be supported in the future build?
__________________________
Help !!
Stuck into endless boot loop , only the first time boot after flashing can enter the lock screen but it reboots just for a while, after that ,endless boot loop ...
Someone nice well can give me a resolution?!
Poor student thanks you very much !
Hello,
Is 3G / LTE working on lastest build ? Same question for tethering.
Thanks for your answer.
Envoyé de mon LYA-L29 en utilisant Tapatalk
Feb19 built
4G works perfect.
Rotation works well.
Hotspot WiFi work well
A new port would be fantastic!
Valera1978 said:
Hi all
I'm here, i'm still continue working on note pro 12.2.
I was absent for a while, it was a lot of another projects.
Time ago I started work on treble project for our 12.2 and it was almost done, now i'll continue work on it, based on lineage pie sources.
And then I'll try to make actual stock (8,0+) port, based on treble.
Click to expand...
Click to collapse
I'm looking forward to see a new port from stock rom.
I'm using P555 port and I'm very satisfied.
And Linux on Dex would be just a dream!!!!!
Thank you Valera for your effort.
Can someone help?
twrp-3.0.2-0:
E3004: This package is for device: viennalte, viennaltexx; this device is .
E: unknown command [log]
Updater process ended with ERROR: 7
Error installing zip file...
I'm trying a dirty flash over the 15.1.
Thanks
I use the latest TWRP from Valera1978 ( see first post) and it works...
... now works, thanks and thanks Valera
This was my original setup stock unit:
Px3 (1024x600 0)
Android 7.1.2
Patch lvl may 5 2017
Kernel 3.0.101+
Mcu version mtcd_xrc_v2. 58_1
Cpu arm cortex-a9 @1.6ghz (x4
I flashed Hal9k Rom and currently have magisk v18 installed. I then used magisk to install Sony framework to be able to use Sony apps.
I installed remote play and psvue. I then proceeded to hide them with magisk hide. I still get errors for remote play (the one saying my device is rooted) and psvue comes on without the black screen saying it isn't supported for rooted devices. However I can't scroll down the screen to click sign in my account.
If anyone at all can help me, I would be very grateful and so would my children during long commutes to and from.
UPDATE: I got PSVue to work flawlessly. And I though I got remote play working but unfortunately, it will not register ps4, however the app itself isn't blocker or detects my root. Getting closer to my overall goal.