Bluetooth isn't working on any ROM with any kernel combination! Not even the default kernel that comes up with the ROM. I'm talking about bluetooth file transfers, not connecting to speakers or anything. When I transfer/receive a file, it says 'Unfortunately com.android.bluetooth has stopped.' and then bluetooth is stuck on 'Turning on bluetooth...'. After rebooting, the bluetooth is already ON but still the same thing happens again when I use it. I can just connect and pair devices, can't share any file with them. Tried clearing data and cache of the Bluetooth Share app too, nothing helped.
It's strange because it works perfectly on OxygenOS with any kernel flashed on top of it. It's just perfect with Oxygen... ONLY! On all CM (never tried CM12S or COS12.1, I'm talking about CM12.1 only because I'm not gonna use others at all!) , Slim and other ROMs, the same problem occurs with all the kernels.
I thought the problem wouldn't be somewhere in the /system or /boot partitions and so I tried flashing OxygenOS and a CM12.1 ROM on top of it without booting into OxygenOS. Still, bluetooth doesn't work.
Help! I don't know where I'm wrong but I know that this is just happening with me and no other OPO user!
See the attachment for more information.
Got the culprit. Don't flash the Xperia Z2 Smart Social Camera on OnePlus One. I found it here . It breaks the bluetooth on any ROM. And on OxygenOS, the ROM will keep on saying 'Camera has stopped.' , so I didn't flash it.
After i updated to android 9 I am no longer able to play music to my Bluetooth headphones. Already tried forgetting the device and reparinig but the problem still remains. I am rooted if that makes any difference and running magisk version 17.1.
svenac20 said:
After i updated to android 9 I am no longer able to play music to my Bluetooth headphones. Already tried forgetting the device and reparinig but the problem still remains. I am rooted if that makes any difference and running magisk version 17.1.
Click to expand...
Click to collapse
Working here on Pie and same magisk version. I am using the bluspark kernel but I'm pretty sure it worked with the stock kernel too. Perhaps clean flash.
Works here aswell.
Pie, magisk 17.2 twrp.
Had stock kernel before and it worked.
I am on Franken v3 and it works now too.
svenac20 said:
After i updated to android 9 I am no longer able to play music to my Bluetooth headphones. Already tried forgetting the device and reparinig but the problem still remains. I am rooted if that makes any difference and running magisk version 17.1.
Click to expand...
Click to collapse
Hello,
I have the same problem. I update by dirty flash i don't try with a clean flash. A lot of pie user on the pixel have the same issue.
Did you think is just an issue of dirty flash or of pie ?
Sorry for my english.
Zak2878 said:
Hello,
I have the same problem. I update by dirty flash i don't try with a clean flash. A lot of pie user on the pixel have the same issue.
Did you think is just an issue of dirty flash or of pie ?
Sorry for my english.
Click to expand...
Click to collapse
I did dirty aswell. And it works. :s
I return to oreo for that and with oreo it works well
I wait and see if it Will be a solution for users Who they have an issue with Bluetooth
I have exactly the same problem, after ota update i have no music playback via bluetooth but calls working just fine. Any fix? i am rooted with magisk 17.1
svenac20 said:
After i updated to android 9 I am no longer able to play music to my Bluetooth headphones. Already tried forgetting the device and reparinig but the problem still remains. I am rooted if that makes any difference and running magisk version 17.1.
Click to expand...
Click to collapse
A simple wipe/ factory reset from recovery solved this issue for me
I don't have any issue with BT music playback, however, I'm not rooted and did a clean flash when upgrading to Pie.
I had the same problem and it turned out to be the dual speaker mod in Magisk. I disabled that rebooted and had music again.
I have a different issue.. Music works fine on bluetooth but when I recieve any kind of notification music souds in like paused intervals and go to normal speed when the notification sound ends... Im rooted with magisk 17.1 no dual speaker mod, just call recording, air audio and youtube vanced....
jc073 said:
I had the same problem and it turned out to be the dual speaker mod in Magisk. I disabled that rebooted and had music again.
Click to expand...
Click to collapse
This did the trick for me also....thanks
Finally i flash oos pie again for try if it works. And if i have dual sound mod the bluetooth don't work for music and if i don't have dual sound mod it works fine. With oreo with dual mod works fine but not with pie. I stay on pie and hope dual sound mod works fine with Bluetooth.
Different problem here. Bluethoot audio works, but connected devices' buttons don't work and metadata don't show up on connected display.
jc073 said:
I had the same problem and it turned out to be the dual speaker mod in Magisk. I disabled that rebooted and had music again.
Click to expand...
Click to collapse
Thank you! I was going insane trying to figure out what happened.
Sent from my ONEPLUS A6003 using Tapatalk
Hi all,
Last weekend I rooted my phone. I treble-ized it and tampered with a few GSIs. I finally chose to use PHHs Treble 9 GSI.
When I connected my phone to my car's Bluetooth I could call, but there was no sound. Is this a driver issue on my Vendor partition (ie did I use the wrong Vendor), or is this a general problem with GSI?
roytje88 said:
Hi all,
Last weekend I rooted my phone. I treble-ized it and tampered with a few GSIs. I finally chose to use PHHs Treble 9 GSI.
When I connected my phone to my car's Bluetooth I could call, but there was no sound. Is this a driver issue on my Vendor partition (ie did I use the wrong Vendor), or is this a general problem with GSI?
Click to expand...
Click to collapse
it wouldnt be a dirver since android doesnt use drivers, it would be in the bluetooth stack. likely caused by a failed flash of your ROM especially if other users arent having the same issue. What kind of car is it (assuming the deck is stock to the car)
Youdoofus said:
it wouldnt be a dirver since android doesnt use drivers, it would be in the bluetooth stack. likely caused by a failed flash of your ROM especially if other users arent having the same issue. What kind of car is it (assuming the deck is stock to the car)
Click to expand...
Click to collapse
Good to know it's only a problem what's occurring on my phone. That would mean flashing a different rom could solve the issue.
The car is a Punto EVO. I haven't tried any other Bluetooth devices, but I expect the same result.
I'll flash a new rom and report back. Thanks for replying.
roytje88 said:
Good to know it's only a problem what's occurring on my phone. That would mean flashing a different rom could solve the issue.
The car is a Punto EVO. I haven't tried any other Bluetooth devices, but I expect the same result.
I'll flash a new rom and report back. Thanks for replying.
Click to expand...
Click to collapse
yeah, reflash the same ROM or try a different one. Back in the day, there were tons of issues with stuff that was designed to work on the phone based on specific kernel programming that spoke to the hardware to allow these features to physically operate, but only in touchwiz based ROMs, AOSP based ROMs were left out in the cold. With the emergence of the necessity of a clean knox in order for certain things to work, i have given up on root for the time being so that i can enjoy the awesomeness that is paying for stuff with my watch (which requires an unrooted phone to work. Technically your phone can be rooted but it makes it a pain in the anus)
anyways, i think your audio issue might be a GSI specific thing, just a hunch tho. Might want to go look in the GSI threads and see if there is a list of what works/whats broke in the ROMs. They usually just come out and tell you if ti doesnt work because if its the other way around, the devs reputation will be tarnished
I flashed Lineage OS 16 (Android 9) GSI. Same problem. Also with other Bluetooth devices. I'm thinking it's the vendor I flashed. I did find an Oreo vendor for this device mentioning Bluetooth calls don't work.
Searched for a rom without Treble but couldn't find one that has December security (or November). For now I'll use my earbuds when calling from the car.
I could flash a number of images, but don't really want to the time of finding the perfect rom for my devices has passed. I'll just keep this rom and when I feel like it, I'll flash the stock rom.
Thanks anyways for the advice!
roms - Google Drive
drive.google.com
This ROM is built using binaries from non-european (TEE) version of Jelly 2. Theoretically it should work on european (EEA). If it won't - contact me, I'll prepare ROW based on EEA binaries.
ROM can be installed via TWRP. How to install TWRP - https://forum.xda-developers.com/t/recovery-twrp-3-5-2-unihertz-jelly-2.4281493/
Source code - https://github.com/Meetoul/android_device_Unihertz_Jelly2
UPD. Experimental version of Lineage OS 18.1 (Android 11) is also available by the attached GDrive link.
Hi, would you be willing to share the source repo and build instructions? Thanks!
lakkimsetty.baba said:
Hi, would you be willing to share the source repo and build instructions? Thanks!
Click to expand...
Click to collapse
Here you go https://github.com/Meetoul/android_device_Unihertz_Jelly2
Meetoul said:
roms - Google Drive
drive.google.com
This ROM is built using binaries from non-european (TEE) version of Jelly 2. Theoretically it should work on european (EEA). If it won't - contact me, I'll prepare ROW based on EEA binaries.
ROM can be installed via TWRP. How to install TWRP - https://forum.xda-developers.com/t/recovery-twrp-3-5-2-unihertz-jelly-2.4281493/
Source code - https://github.com/Meetoul/android_device_Unihertz_Jelly2
Click to expand...
Click to collapse
Thanks for developing the room
But unfortunately it does not work
After burning in twrp it constantly makes a boot loop
I tried several times
I'll be happy if you can fix that
(Sorry for my obscure language, I use translation,)
Gon112 said:
Thanks for developing the room
But unfortunately it does not work
After burning in twrp it constantly makes a boot loop
I tried several times
I'll be happy if you can fix that
(Sorry for my obscure language, I use translation,)
Click to expand...
Click to collapse
Hi!
What version of Jelly2 do you have? TEE, EEA, JP?
Meetoul said:
Hi!
What version of Jelly2 do you have? TEE, EEA, JP?
Click to expand...
Click to collapse
NONE EEA
Gon112 said:
NONE EEA
Click to expand...
Click to collapse
Sorry, I cannot understand you.
Please put a number that corresponds to the yours Jelly2 version
TEE
EEA
JP
1
Meetoul said:
Sorry, I cannot understand you.
Please put a number that corresponds to the yours Jelly2 version
TEE
EEA
JP
Click to expand...
Click to collapse
1
Gon112 said:
1
Click to expand...
Click to collapse
The ROM is already built on top of the latest TEE binaries and it works on my Jelly2...
Probably, you have faced some issues during flashing the ROM. Please flash your Jelly2 back to stock ROM using SP Flash Tool and try again.
I have been using this ROM for couple of weeks now, it seems solid - didn't crash or had any issues.
The battery life however is very bad. I am using Magisk ACC module to limit the charge to 70% and it dropped from 70% to 34~37% within 8-ish hours (while I am asleep) consistently with all radios off (with regular cell network on for calls and texts, LTE off). The stock ROM used to drop at most 3% while I am asleep.
I think the stock ROM has aggressive app kill/ background process limit. I am going to try with those options enabled (in developer options) to see if there's going to be an improvement.
If anyone had issues like the above and has a conf, do let me know, thanks!
Edit: Forgot to mention that I also use AccuBattery and Greenify. Greenify is set to kill all user apps except for Magisk and AccuBattery.
I have the EU Version of Jelly 2, and yet it seems to work fine
Thank you very much for your efforts.
If i find any bugs ill report them
beck.hannes said:
I have the EU Version of Jelly 2, and yet it seems to work fine
Thank you very much for your efforts.
If i find any bugs ill report them
Click to expand...
Click to collapse
Thank you for your feedback. Probably, I won't fix the bugs in LOS 17.1, cause now I'm working on LOS 18.1 (based on Android 11) .
You can try it by this link https://drive.google.com/file/d/1kG8ebEf-GZW_AZ_d42HuxHHmHv0sQDl5/view?usp=sharing
Please note that I'm trying to keep this ROM as clean as possible, so currently it does not contain any proprietary Mediatek or Unihertz binaries (except vendor image, of course ). It means, that ROM does not include FM Radio or IMS. AFAIK, VoLTE is barely supported in Ukraine (yes, I live here ), so this feature is not really necessary for me. But I'll try to get those features working in future, just to have fully functional Jelly 2.
What's tested and working:
Voice Call
SMS
WiFi
Bluetooth
Wired headset
NFC (it reads and emulates tags, GPay doesn't work because of SafetyNet, but I think I can bypass it)
IR remote control (I tested with ZaZa remote software)
Meetoul said:
Thank you for your feedback. Probably, I won't fix the bugs in LOS 17.1, cause now I'm working on LOS 18.1 (based on Android 11) .
You can try it by this link https://drive.google.com/file/d/1kG8ebEf-GZW_AZ_d42HuxHHmHv0sQDl5/view?usp=sharing
Please note that I'm trying to keep this ROM as clean as possible, so currently it does not contain any proprietary Mediatek or Unihertz binaries (except vendor image, of course ). It means, that ROM does not include FM Radio or IMS. AFAIK, VoLTE is barely supported in Ukraine (yes, I live here ), so this feature is not really necessary for me. But I'll try to get those features working in future, just to have fully functional Jelly 2.
What's tested and working:
Voice Call
SMS
WiFi
Bluetooth
Wired headset
NFC (it reads and emulates tags, GPay doesn't work because of SafetyNet, but I think I can bypass it)
IR remote control (I tested with ZaZa remote software)
Click to expand...
Click to collapse
Hi
How many times have I tried to install LOS 17.1 it did not work,
Now I have tried to install LOS 18.1 and it works fine and perfect
Thanks!!
I'll be happy if you can add support for things you mentioned that are not currently supported,
Thank you good man.
Meetoul said:
AFAIK, VoLTE is barely supported in Ukraine (yes, I live here ), so this feature is not really necessary for me. But I'll try to get those features working in future, just to have fully functional Jelly 2.
Click to expand...
Click to collapse
Would it help for you to have someone test VoLTE (and possibly WiFi calling?)
I'm considering picking one of these up and was just assesing what the community is behind it for custom ROMs. I had the original Jelly and the ROM community for that was very limited, and I was in over my head when trying to build it for myself. I would be glad to help however if you think you'll be using the device for a while
Meetoul said:
Thank you for your feedback. Probably, I won't fix the bugs in LOS 17.1, cause now I'm working on LOS 18.1 (based on Android 11) .
You can try it by this link https://drive.google.com/file/d/1kG8ebEf-GZW_AZ_d42HuxHHmHv0sQDl5/view?usp=sharing
Please note that I'm trying to keep this ROM as clean as possible, so currently it does not contain any proprietary Mediatek or Unihertz binaries (except vendor image, of course ). It means, that ROM does not include FM Radio or IMS. AFAIK, VoLTE is barely supported in Ukraine (yes, I live here ), so this feature is not really necessary for me. But I'll try to get those features working in future, just to have fully functional Jelly 2.
What's tested and working:
Voice Call
SMS
WiFi
Bluetooth
Wired headset
NFC (it reads and emulates tags, GPay doesn't work because of SafetyNet, but I think I can bypass it)
IR remote control (I tested with ZaZa remote software
Click to expand...
Click to collapse
Meetoul said:
Thank you for your feedback. Probably, I won't fix the bugs in LOS 17.1, cause now I'm working on LOS 18.1 (based on Android 11) .
You can try it by this link https://drive.google.com/file/d/1kG8ebEf-GZW_AZ_d42HuxHHmHv0sQDl5/view?usp=sharing
Please note that I'm trying to keep this ROM as clean as possible, so currently it does not contain any proprietary Mediatek or Unihertz binaries (except vendor image, of course ). It means, that ROM does not include FM Radio or IMS. AFAIK, VoLTE is barely supported in Ukraine (yes, I live here ), so this feature is not really necessary for me. But I'll try to get those features working in future, just to have fully functional Jelly 2.
What's tested and working:
Voice Call
SMS
WiFi
Bluetooth
Wired headset
NFC (it reads and emulates tags, GPay doesn't work because of SafetyNet, but I think I can bypass it)
IR remote control (I tested with ZaZa remote software)
Click to expand...
Click to collapse
Hey, as far as i tested everything works for me.
There is one thing i noticed:
When booting, Lineage OS tells that the Build has been signed with Public Key, this seems to be a bit of a security issue. Is it possible to resolve that for the LOS 18 version. (Is that testable yet?)
Im fine with not having VoLTE, i think no Custom Rom is able to support it yet and it will just get important when the 3G network will be disabled...
Also if you need more help for testing specific stuff, i can do it.
beck.hannes said:
Hey, as far as i tested everything works for me.
There is one thing i noticed:
When booting, Lineage OS tells that the Build has been signed with Public Key, this seems to be a bit of a security issue. Is it possible to resolve that for the LOS 18 version. (Is that testable yet?)
Im fine with not having VoLTE, i think no Custom Rom is able to support it yet and it will just get important when the 3G network will be disabled...
Also if you need more help for testing specific stuff, i can do it.
Click to expand...
Click to collapse
@Meetoul I installed the LineageOs 18 now which seems to be fine too.
2 Warnings appear after boot. Again the one with the public key, and a new one: "Serial Console active"
My apologies for cross posting. But I initially replied in the wrong topic.
I just received my Jelly 2. It was on 2020 and I went straight through your files. Your TWRP does not respond on my European Jelly 2. And after a first reboot to recovery, TWRP was gone. What I mean with not responding is that the touch screen does not respond. But I connected an USB trackball to use as an input device and switched cables in between adb sideloads. So I finally got it working.
For some reason during reboot TWRP warns me that there is no OS installed. But LoS 18.1 (yours) booted fine. Also flashed opengapps 2707 nano.
After a reboot (phone is still restoring apps) there is a "serial console is enabled" message "performance is impacted, check bootloader". Any instructions on how to get rid of that message? Other than that so far so good.
Die Bruine said:
My apologies for cross posting. But I initially replied in the wrong topic.
I just received my Jelly 2. It was on 2020 and I went straight through your files. Your TWRP does not respond on my European Jelly 2. And after a first reboot to recovery, TWRP was gone. What I mean with not responding is that the touch screen does not respond. But I connected an USB trackball to use as an input device and switched cables in between adb sideloads. So I finally got it working.
For some reason during reboot TWRP warns me that there is no OS installed. But LoS 18.1 (yours) booted fine. Also flashed opengapps 2707 nano.
After a reboot (phone is still restoring apps) there is a "serial console is enabled" message "performance is impacted, check bootloader". Any instructions on how to get rid of that message? Other than that so far so good.
Click to expand...
Click to collapse
Touch in recovery
Have you tried the latest release which includes fixes for both available touch panes (at least for TEE Jelly2)? If yes and it doesn't work anyway, could you please provide dmesg output from recovery and from normal boot? Output of dmesg should be collected as soon as ADB available. Also, please collect kallsyms using the following steps:
Code:
adb root
adb shell
echo 0 > /proc/sys/kernel/kptr_restrict
sysctl -w kernel.randomize_va_space=0
cat /proc/kallsyms >/sdcard/symbl.txt
exit
exit
adb pull /sdcard/symbl.txt
Annoying "Serial console is enabled" notification
You can just long press on the notification and disable notifications from Development Settings.
Thanks, this 'latest' release works! I am curious though, why do I get the message that there is no OS installed when I reboot from recovery? Or is that gonna be a long as reply .Also a few mount errors during flashing and reboot. But, my phone works for 99%.
Only thing not working in my banking app is the fingerprint sensor, also in the Ebay app (which I use once a year). Do you know why this is? Amazon video, Ziggo streaming app, even my banking app works. Fingerprint to unlock the phone also works. Just not in apps. Is this due to it being unlocked?
I come from a qx1000/Pro1 with LoS 18.1 which died on me Wednesday night. That's why I'm asking. That thing was also unlocked, but no error messages there. Also the Corona check app states that the J2 is rooted (which it isn't). Exactly the same configuration as my Pro1. But no warnings on that phone.
Not real complaints, just thought I'd share. This will be my daily driver for the next few months. So if you need a heavy tester, I'm your man.
@Meetoul
The battery drains in 24 hours, is this normal? I can't find any apps draining it. Could the enabled serial console be the culprit?
Edit2:
Hotspot not working for me. It connects but does not provide an IP address to clients. I tried several stock Android devices, without success. All four devices connect, but keep waiting for an IP address.
So now I'm typing this via Bluetooth sharing, which sucks I can tell you.
If you have any suggestions, I am more than willing to try them out...