Database Info

[Q] Tasker on MIUI/WajkIUI

Hi all.
Sorry if this is the wrong place to post, but this thread is regarding bugs on custom ROMs, so here I am.
A while back I switched from CM7 to WajkIUI, and I really have enjoyed this ROM since trying it. Recently however, I've noticed a couple of issues regarding MIUI/WajkIUI and Tasker. I've mentioned my problems in the relevant ROM thread here, and also on MIUIandroid.com, but nobody seems able/willing to help.
I have profiles configured within Tasker that will switch my phone to mute (Silent Mode) when I'm at work (based on WIFI near attribute, which is working fine). WajkIUI ROMs subsequent to 1.9.2 are unable to switch this, or indeed make any changes to volume.
I also have a profile that will switch on Bluetooth when I get an incoming call (using the Incoming Call option in Tasker). I've no idea when this stopped working, I'm on 1.9.2 at the moment, and it doesn't work here. I've tested the profile activates, and it does - but it doesn't switch on Bluetooth.
Finally, my third bug relates to the above, but not Tasker. If I switch Bluetooth on manually and pair with my headset - I can't get my headset to answer the call or to ring the last number (two things it has always done before).
Is there ANYONE who can help fix these? Are these issues solely on MIUI based ROMs, or does CM7 also have this issue - as I'm seriously considering switching back.
Thanks.

250+ views and not one response? Boy do I feel lonely now.
So, seeing as how nobody can offer any help on my actual problems - can someone give me a clue to how I go about decompiling a ROM to check the code out myself please?

simon211175 said:
250+ views and not one response? Boy do I feel lonely now.
So, seeing as how nobody can offer any help on my actual problems - can someone give me a clue to how I go about decompiling a ROM to check the code out myself please?
Click to expand...
Click to collapse
Try to update to 1.9.23

Will that work? I've tried all of them up to that, but every time had to downgrade due to the problems. I got fed up of installing a ROM only to have to uninstall it five minutes later.

simon211175 said:
Will that work? I've tried all of them up to that, but every time had to downgrade due to the problems. I got fed up of installing a ROM only to have to uninstall it five minutes later.
Click to expand...
Click to collapse
I think it's a bug in MIUI itself. If you check the app on market, there's a lot on Market who says so.

that's what I thought - I've an ignored thread in the bug forum on miuiandroid, hence my last question about decompiling the ROM so I can investigate myself.

[Q] Verizon Galaxy S4 / SCH-I545 - Issues with Headphones and GPS

Greetings all, first time post / long time watcher. Love the forums, been on Android since the very first G1 and these forums have been fantastic over the years.
I have Cyanogenmod 3.4.0 June 7th nightly and have been having this same issue since the first. Headphones work great for music, movies, etc... Even can hear emulated DTMF tones just fine, however when I get into a call there is no far end audio coming through, pretty weird. If i unplug the headset, i can hear just fine from the phone speaker. It is only when the headset is plugged in... What gives? Just wanted to make sure that someone was aware and that there is a bug worth fixing. I noticed in the nightly thread (which i am not authorized to post to yet) that others have complained about this as well. Wish I could collaborate there, but alas I cannot so here I sit on Q&A.
Outside of that, GPS issue is a bother. Must disable "Wi-Fi & mobile network location" in order to sync up with a GPS. Doing this kills the location features which is a super downer, so I find myself toggling this on and off all the time just depending on what I need to do.
I am able and willing to provide technical feedback in the form of logs, images and whatever is needed to help resolve. Just let me know what I can do. Thanks a bunch!
Robert

Sent from my SCH-I545 using xda app-developers app

At least you have that. Nothing fixes mine. Won't even see one bird. ..

Having the same problem with GPS
ogonzoo,
I'm having the same problem with GPS. So far, I haven't been able to get it to work except by toggling off the Wifi/Mobile Network location. I did run across a post mentioning a possible fix involving a Touchwiz ROM, but I'm not sure I understood.
I found this other thread seeming to explain the procedure for actually implementing that fix, but I don't know how to apply it to the Cyanogenmod Nightly ROM (assuming that's even possible). Hopefully someone else here will.
EDIT:
Apparently, there's a pretty extensive discussion of this problem in the thread where I read invisiblek's post (first link above), starting at about page 31. It seems to be an acknowledged bug and the Cyanogenmod devs are supposed to address it in a forthcoming build.

[Q&A] [ROM][LP][5.0.2] CyanogenMod 12 - UNOFFICIAL BUILD for M4

Q&A for [ROM][LP][5.0.2] CyanogenMod 12 - UNOFFICIAL BUILD for M4
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][LP][5.0.2] CyanogenMod 12 - UNOFFICIAL BUILD for M4. 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!

Giving it a shot
I'm not a big camera user anyway, so I'm going to give this a shot. Wish me luck!

Hi Plesse fix camera THX

Hi there..
Is 4g/Lte working?

4g LTE dont work

Great job!
Thanks for your work! This ROM is awesome and if you fix the camera too you're a god. By the way... on this forum there is another Lollipop ROM (Candyrom) where the camera is working. Can you use that? i'm a noob so don't judge me

Just flashed earlier today and seems to be working great! cheers man. Any update on the camera?
Thanks

Camera Works!!!
Great job!!! The camera works and the system is very fluid. i notice some problems on activating mobile data. First time i tried it didn't work. I switch some APN, turned Airplane mode on/off (strange, it required me to enter the PIN 2 times in a row). Finally it worked (i saw the LTE text on signal bars and i was happy ). Another thing i noticed is that the Prefered Network was 3G and i couln'd choose LTE only if i select 2G first and then LTE.
Thanks again!

no sim found
i have a problem, the rom can't find my sim, anyone had a solution?

SIM
(This rom doesn't ask for my PIN so I guess it doesn't read my SIM at all? Clean install (I guess), everything else I tried is working quite fine.)
Settings say baseband version is unknown.

They can't hear me well
Another problem that i noticed is that the other person i'm talking to hears me, and i quote them, "like you are in a tunnel". At first i thought that is their phone, but multiple persons reported that to me. Also, this happened after i flashed this rom.

Baseband Unknown
Hi,
Just installed this and everything works great except for the mobile network. Settings say baseband version "Unknown", doesn't detect sim at all.
Does anyone has any idea on how to fix it?
Cheers!

....
Hello , I friend says to me : "You don't need root to install cyanogenmod on m4 , only TWRP (teamwin or something like this..) "
And my question is : Is this real ? I don't need root , only TWRP? to install cyanogenmod on m4 ?

Installing the app Selinux and setting it to permissive fixes APN and mobile network problems. I would advise doing some background reading of this app first though.

Flashed it 2 days ago, everything is fine. Sometimes it is a bit laggy, but it looks very nice!
First i had problems with the google play music app. I was not able to listen to music with my headphones but now it works... Don't know why ?

cm12
who can do not be razognanoe kernel on cm12? you're welcome

Hello Guys,
I just tested the CM12 build for the One m4 and i have some issues... i cant connect to my carrier and somehow i can't install the gapps. i downloaded the one provided in the first post and i tried to download the most recent ones. If i try to install the gapps, my recovery just pops up the main menu with no error-codes or something. it is just loke blown away, if you know what i mean... and, yeah, i cant connect to my carrier, which is like... meh... not actually good for daily use... :/ if there is a way to fix it all, please let me know, i could use some help here.
Greetings Meritili
Edit:
Managed to install the gapps, carrier Problem is still there, help please!

Great Rom !! Thnx

Nice Rom
but... vibration intensity does not work

Bluetooth Problems
Hi, first of all thanks for providing this ROM. I tried both the 5.0 as well as the fresh 5.1 build and most things, apart from some spontanious reboots, are working exceptionally well (IMO better than CM11).
One problem I observed is that I can't use bluetooth to make calls. I am not sure, whether this is a general CM12 problem, or whether it's specific to our device. The same problem is also present when using the other Lollipop ROM based on CM12 in the forum (Candy5). I also found some reports of users of other devices that also have bluetooth problems when using CM12 or some other Android 5.x based ROM.
To clarify: I can pair and connect to bluetooth devices that offer headset functionality (tried bluetooth headset and bluetooth radio in car), and I can also stream music via bluetooth. What I can't do is making actual calls via bluetooth. Both bluetooth devices noticed that a call is about to be made, and also the correct number was displayed in the radio display. But no sound was audible and the other side couldn't hear me. The call itself was okay when switching to internal speakers. Dis-/Re-enabling of bluetooth options did not fix anything.
Audio playback over bluetooth is also rather sluggish and sometimes leads to freezes. Also sometimes the option to use bluetooth for media playback has to be disabled and reenabled for it to work.
Unfortunately I can only test bluetooth in my car (the headset wasn't mine) so it is kinda hard to generate logs. I will try over the next few days to produce one.

Unbelievable. Oneplus claims that a bug is now a feature.

Here, check this out.
Me:
When two BT devices capable of telephony functions are connected, the second one connects as "Connected (no phone)", and its telephony function cannot be used.
Example (picture attached). If Huawei Watch is already connected, when Jabra Talk attempts to connect, it will connect as described above, and one cannot make or receive phone calls on Jabra Talk (but still can on the watch.)
Oneplus support:
Thank you for taking the time to send us this email as well as the screenshot that you provided. I understand that you want to use both of the Bluetooth devices for easy access and getting in touch with loved ones for helping us keep on track with our daily activities.
I would like to inform you that the OnePlus 6 can actually connect to two Bluetooth devices. However, by default, you can only choose one for making and receiving calls. Just choose which you preferred to use by toggling the "Phone calls" under each setting of the Bluetooth devices.
This bug was not present in 5.1.5. They introduced it in 5.1.6/7.
This bug is present in all Pixel phones because it's a buggy Google code that Google simply does not care to fix.
Samsung fixed this in their phones.
So, I am guessing OP had this fixed in 5.1.5, but then they just lazily copied and pasted that Google garbage code.
And they don't know how to fix it now. So now it's a freaking feature.
UNBELIEVABLE!

I have the same problem with my Huawei Watch and my cars hands free system
I tried to disconnect the watch with Tasker as soon as my hands free system connects, but it never worked reliable (because the watch connects again immediately and takes over the call functionality)
I guess we need to wait until we get Android Pie because as far as I know this problem is solved with Android Pie

MJFox78 said:
I have the same problem with my Huawei Watch and my cars hands free system
I tried to disconnect the watch with Tasker as soon as my hands free system connects, but it never worked reliable (because the watch connects again immediately and takes over the call functionality)
I guess we need to wait until we get Android Pie because as far as I know this problem is solved with Android Pie
Click to expand...
Click to collapse
I hope so. But I'm not that hopeful - I think it's a Google bug, and they simply don't care to fix it.
Meanwhile, I have to disable the phone functionality on the Watch so I can use my hands free car kit.
It's so disappointing, especially since this stuff always worked with Samsung phones, OOS 5.1.5 (the bug was introduced in 5.1.6/7) and even the early Pixel, pre Android 7.0.2.

nabbed said:
Here, check this out.
Me:
When two BT devices capable of telephony functions are connected, the second one connects as "Connected (no phone)", and its telephony function cannot be used.
Example (picture attached). If Huawei Watch is already connected, when Jabra Talk attempts to connect, it will connect as described above, and one cannot make or receive phone calls on Jabra Talk (but still can on the watch.)
Oneplus support:
Thank you for taking the time to send us this email as well as the screenshot that you provided. I understand that you want to use both of the Bluetooth devices for easy access and getting in touch with loved ones for helping us keep on track with our daily activities.
I would like to inform you that the OnePlus 6 can actually connect to two Bluetooth devices. However, by default, you can only choose one for making and receiving calls. Just choose which you preferred to use by toggling the "Phone calls" under each setting of the Bluetooth devices.
This bug was not present in 5.1.5. They introduced it in 5.1.6/7.
This bug is present in all Pixel phones because it's a buggy Google code that Google simply does not care to fix.
Samsung fixed this in their phones.
So, I am guessing OP had this fixed in 5.1.5, but then they just lazily copied and pasted that Google garbage code.
And they don't know how to fix it now. So now it's a freaking feature.
UNBELIEVABLE!
Click to expand...
Click to collapse
if Google's code is garbage, I suggest you stop using android and start making your own good code!

nabbed said:
I hope so. But I'm not that hopeful - I think it's a Google bug, and they simply don't care to fix it.
Meanwhile, I have to disable the phone functionality on the Watch so I can use my hands free car kit.
It's so disappointing, especially since this stuff always worked with Samsung phones, OOS 5.1.5 (the bug was introduced in 5.1.6/7) and even the early Pixel, pre Android 7.0.2.
Click to expand...
Click to collapse
I disabled the phone functionality too
I had a Samsung phone before as well (Note 8) and with that I had no problems with my hands free kit but instead the smartwatch lost the phone functionality after a few hours so I always had to reconnect it (basically the same problem but the other way round)... it's very frustrating that such a pretty basic thing doesn't work properly
I also tried this app: https://play.google.com/store/apps/details?id=org.myklos.btautoconnect
but it didn't seem to make any difference, it didn't seem to make anything at all
I read that Android Pie is able to connect to more than one Bluetooth headset at a time so this should fix the issue after all

kewlest22 said:
if Google's code is garbage, I suggest you stop using android and start making your own good code!
Click to expand...
Click to collapse
I had a Pixel XL for over a year. Only kept it for Project FI. Bug ridden POS.
Sold it for half going price just so I could feel clean again.
Even if Samsung *used* to have sluggish Touchwiz in the past, at least it didn't have deal breaking bugs.
Don't even have to make my own code - some XDA roms had fixed this bug, as opposed to Google.
MJFox78 said:
I disabled the phone functionality too
I had a Samsung phone before as well (Note 8) and with that I had no problems with my hands free kit but instead the smartwatch lost the phone functionality after a few hours so I always had to reconnect it (basically the same problem but the other way round)... it's very frustrating that such a pretty basic thing doesn't work properly
I also tried this app: https://play.google.com/store/apps/details?id=org.myklos.btautoconnect
but it didn't seem to make any difference, it didn't seem to make anything at all
I read that Android Pie is able to connect to more than one Bluetooth headset at a time so this should fix the issue after all
Click to expand...
Click to collapse
I am almost positive that if you had a somewhat similar problem on a Note 8, it's probably Google's fault.
I don't really use the 2 BT phone functionality for more than 30 min on average, but I've never had any problems on Note 7, GS6 or GS9, or even on a Pixel pre 7.0.2 android, when this bug was first introduced.
After 7.0.2, bluetooth stuff just broke everywhere. This bug, constant disconnects and reconnects, for some people music skips, for some doesn't even work, BT UI in Settings just crashing etc.
It's like Google replaced their BT programmer with a monkey at that point, or even a monkey's nephew.

So just because you cannot use 2 Bluetooth devices simultaneously to make phone calls, it's a deal breaker??? Lmao please please please go back to Samsung so we don't have to hear the whining anymore. Good luck with those bootloaders

Mi Note3 Bluetooth Logs

Hi all,
I am not sure if this is the correct place to adk this question but I have noticed that my mi note 3 is switching on Bluetooth automatically.
I have checked all of the settings and I can't figure it out.
Is there a log that I can access to see what is switching my Bluetooth?
I know about HCI log in dev. options - would that include this type of info?
Or is there maybe some other log that I could access to see this type of information?
I am running Linage OS 16.0.

Anyone?