Related
Hi,
Does anyone heard about S/W showing this information?
I tried to get it from the trace logger with trace viewer (more info here:
http://www.xda-developers.com/tracelogview/) and I tried to find it with the AtDbg (AT command viewer, in windows directory), but nothing...
It is important for me... I have it on my Nokia 7650, (from here:
http://groups.yahoo.com/group/7650-soft/files/Apps/Net Monitor 7650.zip), and I want to compare, to compare the RF behavior.
10x
Tomer
Ok this is what I've got so far.
There is no software at the moment that can display such info on the
background screen. The reason is because every developer is having
a spasm trying to get the microsoft SMS API to function correctly.
You can turn on the CELL INFO, by using the cell broadcasting feature
located in your phone, however the channels to receive is purely
depending where you are living. In Australia the channel is 50.
However after a while you will get so sick of the delivery method, which
is by SMS. There are people trying to write a software to take this
SMS and display it in a application on the background screen. However
Mircosoft SMS API only allows ONE application to receive SMS messages.
If other applications try to call the function openSms, it will return a failure
code informing that the handler is already currently used. I have tried
to unhook the MS SMS reciver software, however then I am confronted
with the issue of writing the entire software again to store the SMS messages. I do not know how Paragon did it with their SMS name software, but they seem to have more of a clue then I do, they are probablly the best to ask and I wish they would provide the source code
for that free software.
Does this cell broadcast cost the normal SMS charge?
Or is this just how the information is received, in SMS format?
Thanks.
Cell Broadcast is free of charge to receive.
On 'normal' phones the CB messages are usually shown on your main-display as a ticker-tape.
On the XDA / MDA the messages are treated as incoming SMS, which is a bit awkward as for some CB services, you receive a new message every 30 seconds . . .
Hi,
As the title suggests, is there any way to disable the bluetooth last number redial functionlity.
I have a Xperia Mini Pro (SK17i, Bootloader unlocked, Rooted) with a Samsung HM1700 bluetooth headset. The headset has a button for answering / ending calls and this same button also has the last number redial functionality, ie when not in a call, pressing this button redials the last dialed number.
AFAIK, the headset just sends a signal to the mobile which then calls the last dialed number.
What I need, is to disable only the bluetooth redial functionality on my mobile.
[ BUMP]
Any suggestions anyone?
Sent from my SK17i
BUMP
Sent from my SK17i
You can try the app Smart Bluetooth Headset from the Play Store.You can not only disable it but also make it do something useful
Since the app "Smart Bluetooth Headset" does not work reliably for me (e.g. not activated by default after program start) I use this now: Go to Bluetooth settings and find your headset. Uncheck Phone to disable the headset from being used for voice calls.
Use an app on your smartphone to enable bluetooth on call and disable after call. There are many apps for this, for example bluetooth on call: https://www.addictivetips.com/mobil...ndroid-bluetooth-for-bt-headset-during-calls/
In addition to solving this problem your phone battery will last longer.
Regards Rob.
Necroing this thread to say that I tried "Headset Button Controller" and "Smart Bluetooth Headset" apps, both free versions, on my rooted HTC10 running Oreo 8.0 with a paired MPOW Crescent. Both apps worked, in slightly different ways.
Headset Button Controller places a dummy call on the call log. Activating the redial function on the headset (double click the answer/end call button on the MPOW Crescent) makes the phone call to the dummy thing, and a little window shows asking for a valid number. No call is actually made.
Problem is, if a valid call is made (for example, you call your boss or a friend), the dummy call setting must be reenabled again manually in the app - meaning that, if you make a valid call, the next time you activate the redial function on the headset, it will call the valid call.
Smart Bluetooth Headset works basically the same way, except that, instead, the redial attempts to call the * or *1 numbers. These attempts open the call window but close it right away, and immediately activate whatever you set the redial function to do. I set mine to run "Tasker 01", but didn't set what "Tasker 01" is. So, what my phone does when I (accidentally) activate the redial function on my headset is open and close the call window, and then return an onscreen self-fading error notification stating that Tasker 01 could not be found.
Best of all, the settings stick - meaning that, if you make a valid call, the redial function will still attempt to dial the * or *1 numbers, as long as the Smart Bluetooth Headset service is active.
So, in my experience, the Smart Bluetooth Headset app works the best.
Of course, I could just turn the headset on and off, whenever I need. It has a physical on/off switch, and immediately pairs with the phone (if previously paired) when turned on.
Awesome guys, thanks! Well written instructions Kam0laZ So nice when a solution presents itself effortlessly. Just turned on my new Bluetooth piece and INSTANTLY ( double tapping by mistake Just to get the damn thing in my ear hole) redialed my (dreaded) Ex BF..... TWICE! .... Noooooooo! Damn it! *Fists shaking furiously* And the ball was only in MY court but for a fleeting moment... wah wah
Could you share a link for these two apps? I've been trying to find them on the Google play store..
Unfortunately, redialing is no easy feat (like instead the stupid "media player opens" case).
https://github.com/LineageOS/android_system_bt/blob/lineage-17.1/bta/include/bta_ag_api.h#L319
https://github.com/LineageOS/android_system_bt/blob/lineage-17.1/btif/src/btif_hf.cc#L423
https://github.com/LineageOS/androi...e-17.1/jni/com_android_bluetooth_hfp.cpp#L194
https://github.com/LineageOS/androi...luetooth/hfp/HeadsetNativeInterface.java#L118
https://github.com/LineageOS/androi...ndroid/bluetooth/hfp/HeadsetStateMachine.java
https://github.com/LineageOS/androi...droid/bluetooth/hfp/HeadsetService.java#L1331
So, like, simply put.. You have a bluetooth HFP device that sends an AT+BLDN command to your phone.
The bluetooth stack runs DialCallCallback in the bluetooth package, which getLastDialledNumber from your phonebook, and then sends an ACTION_CALL_PRIVILEGED intent to the rest of the phone with the number to call.
Where could we act?
Perhaps if you could force some sort of HSP-only mode, you could avoid all the extra cruft but I'm not aware of any way to do so.
Similarly, there are plenty of ways to "directly hack the code", but I don't think anybody has got such a solution yet.
So my efforts have focused on disturbing the phone dialer from getting the action to call.
The problem is, "install-only" permissions aren't changeable. And without root you can't even hope to revoke android.permission.READ_CALL_LOG. And without xposed you can't even block intents.
(if you have either of these though, something could be done I guess?)
So long story short, well, Smart Bluetooth Headset still sounds like the best option.
It's no longer available in any official place as already stated.. But luckily enough it was open source!
We'll see.
Hi,
Install macrodroid app from play store.
Create a macro as follows:
Trigger:
Call/sms -> call outgoing
(Select number(s) from the 3 bullet menu that appears, it is the 3rd)
Enter * (meaning all calls)
Action:
Phone -> call reject
Save the macro.
That's it !!!
Keep in mind to let the macrodroid app on the white list of any battery saver app you may have installed or is built in the android it self (eg xiaomi phones) easy to make it unrestricted to not be killed by any task manager.
Simple solution, minimal battery drain, no wake up the phone to check. The macro runs only on call intent
Thats's it.
Thanks
kounelii said:
kounelii said:
Hi,
Install macrodroid app from play store.
Create a macro as follows:
Trigger:
Call/sms -> call outgoing
(Select number(s) from the 3 bullet menu that appears, it is the 3rd)
Enter * (meaning all calls)
Action:
Phone -> call reject
Save the macro.
That's it !!!
Keep in mind to let the macrodroid app on the white list of any battery saver app you may have installed or is built in the android it self (eg xiaomi phones) easy to make it unrestricted to not be killed by any task manager.
Simple solution, minimal battery drain, no wake up the phone to check. The macro runs only on call intent
Thats's it.
Thanks
Click to expand...
Click to collapse
Click to expand...
Click to collapse
@kounelii how do you configure the macro so that it only applies to calls made from headphones when last number redial is executed?
kounelii said:
Hi,
Install macrodroid app from play store.
Create a macro as follows:
Trigger:
Call/sms -> call outgoing
(Select number(s) from the 3 bullet menu that appears, it is the 3rd)
Enter * (meaning all calls)
Action:
Phone -> call reject
Save the macro.
That's it !!!
Keep in mind to let the macrodroid app on the white list of any battery saver app you may have installed or is built in the android it self (eg xiaomi phones) easy to make it unrestricted to not be killed by any task manager.
Simple solution, minimal battery drain, no wake up the phone to check. The macro runs only on call intent
Thats's it.
Thanks
Click to expand...
Click to collapse
[Post Deleted]
glensantacruz said:
Hi Guys,
I've ported one of my apps: eNotify to the Ornate TrueSmart:
https://play.google.com/store/apps/details?id=com.hermes.enotifylite
A couple of users have written to request that eNotify turn on the screen when a new email arrives. So that works fine. However, they would also like the screen to be unlocked so that they don't need swipe to dismiss the clock-screen to see the notification.
We have a similar option that works on most Android devices: Settings / "Dismiss Screen Lock"
In code:
Deprecated Way:
KeyguardManager keyguardManager = (KeyguardManager) context.getSystemService(Activity.KEYGUARD_SERVICE);
KeyguardLock lock = keyguardManager.newKeyguardLock(context.KEYGUARD_SERVICE);
lock.disableKeyguard();
Current Way:
getWindow().addFlags(WindowManager.LayoutParams.FLAG_DISMISS_KEYGUARD);
BUT it doesn't work on the Ornate TruSmart which leads me to believe this isn't actually a lock screen, but something else. Is there a way to programmatically dismiss this screen?
Best Regards,
Glen
Click to expand...
Click to collapse
I don't use screen lock on my TS, and your app works fine for me, awaking the screen and presenting the popup notification. One question though: When in silent mode, the vibrate feels like just one small bump, and is barely noticed. Any way to increase the vibrate, or set a pattern? Thanks.
[Post Deleted]
glensantacruz said:
Okay. Thanks for the info. I'm still attempting to track it down. Apparently, removing the lock works on some ROMS, but not others.
You can set the vibration like:
Alerts Tab (!) -> Default Profile -> Default Alert -> Bell Chime -> Vibration
There are baked in vibrations such as:
short, medium, long
But you can also hold your finger down to record one of a custom length.
Please feel free to email me at the support address if you need anything. I'd also welcome any reports of TrueSmart specific issues that need investigating.
Thanks,
Glen
Click to expand...
Click to collapse
That worked, thanks. So far so good with my TS...
@glensantacruz, eNotifyLite did not function on my device at all. Sadly once I installed the app, google search started to crash constantly. this made my TrueSmart unusable. Once I uninstalled everything worked once again.
I had high hopes for this.
Suggestion. in the setup separate SMS and email configuration. I am not interested in email in my tiny watch screen. I only really want sms, hangouts, Phone calls and basic glance-able alerts to wake my screen. On my phone I might try your app for email.. I looks very interesting and full of features.
I am a bit confused. In order to receive these notifications the ts must be connect through BT to my phone? If that is true how are u getting past the issues with BT connection with a phone
rhineymac said:
I am a bit confused. In order to receive these notifications the ts must be connect through BT to my phone? If that is true how are u getting past the issues with BT connection with a phone
Click to expand...
Click to collapse
This is not a simple situation but I will attempt to explain my solution:
For SMS
first I have a full service SIM and account for my TS on ATT
next use google voice for my primary number, this involves installing the GV app and configuring it, then getting the GV number socialized..
next I force force sms responce on my phone and my TS to use the GV # with an Xposed plugin called "XVoice+".
For EMAIL / Internet based:
first I have a full service SIM and account for my TS on ATT that is part of a 15gb shared family plan.
The final result is I receive all SMS on both devices. A couple Caveats, GV does not support the short message format so no twitter alerts. depending on the sms source, some messages are more readable on the TS then others.
Unfortunately for me I'm in Canada and lacking Google voice. Thanks for the explanation tho. Omate is doing a ota in a few more weeks fixing the BT issue. I think I will hold off and wait and see how well it works. I've spoken with Le pen and he tells me that the new fix is working very well.
Hi, yesterday I set up the auto call forwarding calls from my phone to gear S, when the pairing is lost (ine the gear app). It works fine. Today it's not working. After the BT pairing is lost, I'm just getting the message on gear, that calls weren't forwarded, clik OK, to try again.
When the gear is paired remote (wifi), the OK click starts the fwd. But usually when I left the phone home, I got the fwd msg after couple of minutes, when I'm fair away, so I'm not even remote connected, and the OK click doesn't helps.
Anybody with this problem?
My workaround is to use Tasker, but better will be, if the auto fwd would works as it should.
Gear S, slovakia, O2 network, paired with i9505
i have the same problem....can you explain how you set up tasker? maybe it can be a solution for people with the same problem until we find another fix...thanx
tasker workaround
for auto fwd when BT pairing is lost:
(gear and phone should be paired via BT before starting this set up)
1. at the home screen I created new profile named Gear S (not necessary)
2. clicked "+" and selected State
3. click Net
4. click BT Connected (the task will be run one time after BT device is paired)
5. at State Edit screen in the Name field click magnifier icon and choose paired Gear S. The same do in the Address field.
6. Click back on your phone or the icon in the left top to go back.
7. new menu should appear, choose new task. Fill in name and click the Check icon
8. on Task Edit click "+" to add action
9. chose Phone
10. chose Call
11.now you have to find the operator code, which you have to call, when you want to redirect calls to another number. In my case it is **21*phonenumber#
12. click Auto Dial
Thats it, now just go back.
to disable autoforwarding, just create another State event and on the step 4. also choose Invert. and at the step 11 choose the code, in my case ##21#.
Analogicaly you can create another task (not BT con discon), when you ring your phone from gear number, than start auto forward to gear number.
hi, first of all thanks for the explanation..it works (kind off)
i followed your directions and now when i turn off BT on the phone the calls get redirected to the gear s, but only when the gear s is configured with mobile networks "always on"....when i put the mobile networks to "auto on/off" and call my phone, i get the answering machine from the sim in my gear s....is this normal?
i just worry when i have to put network always on, that the battery will drain much faster...
hmm, in my case, I have setings to auto ON/OFF. I think, that after disconecting BT, you have to wait couple of seconds (around 120) until the gear S gets registered to network, or until the phone autocalls call forwarding.
I had the same problem. that soon after closing BT I was unable to call to my phone number.
But It's still not working perfectly, I have to do some more research, why today after leaving phone home, the calls didn't get forwarded....
niio said:
hmm, in my case, I have setings to auto ON/OFF. I think, that after disconecting BT, you have to wait couple of seconds (around 120) until the gear S gets registered to network, or until the phone autocalls call forwarding.
I had the same problem. that soon after closing BT I was unable to call to my phone number.
But It's still not working perfectly, I have to do some more research, why today after leaving phone home, the calls didn't get forwarded....
Click to expand...
Click to collapse
The only way i am able to get a remote connection successfully is if my phone is on wifi and my watch is on wifi, i left my phone at my house on wifi, walked o my neighbors house and we sent messages to my phone and i got them on my watch. I noticed i successfully get a "Remote connection" notification on my watch, however if I'm using mobile data and blue tooth gets disconnected i will not have a "remote connection" notification on my gear and if someone calls it will take almost 10 mins before i say i got a missed call on my watch, just like your problem on the first post i get a phone icon that lets me try to retireive my missed call but it keeps failing and i get a phone icon with a small yellow "!". Ive tried resintalling gear app, ive wiped the watch plenty of times. Im starting to think it has something to do with ATT. As the remote connection always works if both are on wifi no matter where they are, which is removing the att network connection all together. The app is working by sending me data once wifi is connected.
niio said:
for auto fwd when BT pairing is lost:
(gear and phone should be paired via BT before starting this set up)
1. at the home screen I created new profile named Gear S (not necessary)
2. clicked "+" and selected State
3. click Net
4. click BT Connected (the task will be run one time after BT device is paired)
5. at State Edit screen in the Name field click magnifier icon and choose paired Gear S. The same do in the Address field.
6. Click back on your phone or the icon in the left top to go back.
7. new menu should appear, choose new task. Fill in name and click the Check icon
8. on Task Edit click "+" to add action
9. chose Phone
10. chose Call
11.now you have to find the operator code, which you have to call, when you want to redirect calls to another number. In my case it is **21*phonenumber#
12. click Auto Dial
Thats it, now just go back.
to disable autoforwarding, just create another State event and on the step 4. also choose Invert. and at the step 11 choose the code, in my case ##21#.
Analogicaly you can create another task (not BT con discon), when you ring your phone from gear number, than start auto forward to gear number.
Click to expand...
Click to collapse
Yessss...it's working
had to put gear manager back on my note 3 and to reset my gear s, but now it works great...when out of bt range it automaticaly forwards all calls to my gear s, and when i come back into range it automaticly goes back on bt mode....
perfect workaround till they firgure out how to make their built in function to work as it should.
thanx again
What do you mean built-in function working as it should?
As far as I can tell everything is working as designed. I didn't have to configure anything to get auto-forward to work....it seemed to be the default operation. As soon as the watch loses bluetooth connection with the phone, about 2 minutes later, all calls are re-directed, and a 3G data link is established between the watch and the phone so that notifications continue to work.
The ONLY issue is that when you dial-out from the watch it of course presents the caller ID of the SIM in the watch rather than your normal number, so your friends, relatives etc won't recognise the number.
the build in autofwd is sometimes working but usually not. Maybe the problem is, if the data on the gear S are off, than there are problems with autofwd.
When I have data "on" on gearS, there was no problem with autofwd, or the gearS were able to start autoFWD, after clicking on the OK in the "not paired message". Probably the autoforward is not working via network forwarding, but via samsung account.
Anyway, if data are off, then the gear is not receiving any notifications, just calls and messages (I guess).
niio said:
the build in autofwd is sometimes working but usually not. Maybe the problem is, if the data on the gear S are off, than there are problems with autofwd.
When I have data "on" on gearS, there was no problem with autofwd, or the gearS were able to start autoFWD, after clicking on the OK in the "not paired message". Probably the autoforward is not working via network forwarding, but via samsung account.
Anyway, if data are off, then the gear is not receiving any notifications, just calls and messages (I guess).
Click to expand...
Click to collapse
Okay I understand. The forwarding is indeed done via data. It sends a data signal via Samsung's server to your Note 3 to tell the Note 3 to forward the calls. It cannot be done at the mobile network level because the forwarding has to be set on the originating number. So the only way to do that is to send a signal back to the phone to tell it to forward the calls. And this is done of course by data.
Tasker solution sucks for me. one thing is my phone brings up a text box prompt asking if i want to forward calls before dialing the number and for some reason when i reconnect it does the cancel call forwarding task twice and again with a prompt.
Same problem.
It seems to be a problem with the Gear S watch. If I restart the watch all works fine for a while.
Wrong way round
niio said:
for auto fwd when BT pairing is lost:
(gear and phone should be paired via BT before starting this set up)
1. at the home screen I created new profile named Gear S (not necessary)
2. clicked "+" and selected State
3. click Net
4. click BT Connected (the task will be run one time after BT device is paired)
5. at State Edit screen in the Name field click magnifier icon and choose paired Gear S. The same do in the Address field.
6. Click back on your phone or the icon in the left top to go back.
7. new menu should appear, choose new task. Fill in name and click the Check icon
8. on Task Edit click "+" to add action
9. chose Phone
10. chose Call
11.now you have to find the operator code, which you have to call, when you want to redirect calls to another number. In my case it is **21*phonenumber#
12. click Auto Dial
Thats it, now just go back.
to disable autoforwarding, just create another State event and on the step 4. also choose Invert. and at the step 11 choose the code, in my case ##21#.
Analogicaly you can create another task (not BT con discon), when you ring your phone from gear number, than start auto forward to gear number.
Click to expand...
Click to collapse
I did this set up as explained above but found it was the wrong way round step 11 I had use the cancell Divert code ##21# and click revert don't know why but it works for me . When I did it as explained above when the phone and gear were connected it was diverting to the gear . Then when they were apart (lost Bt connection ) it would cancell the Divert. Anyone else had this problem regards Rob west ps top forum site very helpful
I'm using different SIM cards, with different numbers, on the Android and on the Gear S. The Gear S is set to use the Gear number for calls and for SMS sending. If I send an SMS to the Gear number, it always arrives there. If I try to send (compose or reply) an SMS message from the Gear, then:
* 99% of the cases it gives a timeout and is not sent
* if I quickly put the Gear in airplane mode, then turn airplane mode off, then send immediately the SMS, is is always sent
Any hints? Does anybody have issues with SMS sending (originating from the Gear, not proxied via the phone)?
Br,
C
PS. - I guess I just posted in the wrong area, but I have no clue as of how to move this to the Troubleshooting zone ...
When this happens, is your watch connected to your phone via BT? The watch's cell radio is auto-disabled whenever it is BT connected to the phone.
foxbat121 said:
When this happens, is your watch connected to your phone via BT? The watch's cell radio is auto-disabled whenever it is BT connected to the phone.
Click to expand...
Click to collapse
The watch is not connected via BT when this happens, and the 3G is always on. I made sure it only has the 3G connection and it is set to use the Gear number ...
Then you probably have SIM card or account setup issue not related to Watch itself. I don't know which region your watch is from. Here in US, my AT&T version won't allow sending text message from watch's radio using another number. It has to be the number of the watch itself. Security restrictions from the carrier I guess.
foxbat121 said:
Then you probably have SIM card or account setup issue not related to Watch itself. I don't know which region your watch is from. Here in US, my AT&T version won't allow sending text message from watch's radio using another number. It has to be the number of the watch itself. Security restrictions from the carrier I guess.
Click to expand...
Click to collapse
Did that too, forced the operator to send the configuration again to the Gear number, received it on the Gear, approved the setup, got the MMS and internet APNs updated ... the Gear sends SMSs from its own number, and it works for a couple of minutes after it is out of airplane mode, then stops working. It can also receive messages anytime, without any problems - so it must be something else. Since I seem to be alone having this issue, I will probably reflash and reinstall, maybe it fixes itself
I'm having almost the same problem except with calls --- texts go through fine both ways, but I can only receive calls, when I try to make an outgoing call on the gear in standalone mode (phone not connected) it says either "unexpected response" or "emergency calls only" I think it could be a firmware bug as I found two firmware updates I'd missed (will test it tomorrow, currently a storm so no ATT reception here) but make sure your firmware is latest version, if it's not, update it and try again.
i'm on the latest fw, take care, you may lose text messages too
Ah, well I guess it wont help you >.< sorry. Good Luck!
Though in my case, after updating the firmware it works perfectly for calls/texts now! Data doesn't work, but I don't really need that (I have an unlimited plan on my phone and excellent reception usually, the gear's tiny plan ($10/3 months) is just for those odd times when I forget my phone or it's battery dies, or it has no reception and I *have* to make a call --- to date not had a problem like that in 10 years, but peace of mind for $3/month is worth it )