Hi.
So, i just watched a show called SourceFed on youtube where they talked about a guy getting arrested for "driving homicide",
basically he texted while driving, he ended up in the wrong lane and fronted another car killing the other driver.
Which brings me to my request:
Could you guys help me by developing a free application which disables the text (sms) function in a phone once the phone reaches a speed of 25km/h (15mph)?
That's "all" the app has to do, just disable the SMS function while driving.
One downside that i would like you to ponder about, is the fact that this would disable the text function for the passenger as well, how can this be worked around without the driver being able to do so as well?
Perhaps a WiFi module somewhere in the car which gives more accurate GPS positioning data which then leads to you being able to tell if the phone is in the driver seat or not?
I'm not doing this for commercial purposes or for profit, i just had a good intention which i would like to see available to everyone and perhaps even standard in the next generation of phones so we don't loose lives due to technical gadgets..
torxed said:
Hi.
So, i just watched a show called SourceFed on youtube where they talked about a guy getting arrested for "driving homicide",
basically he texted while driving, he ended up in the wrong lane and fronted another car killing the other driver.
Which brings me to my request:
Could you guys help me by developing a free application which disables the text (sms) function in a phone once the phone reaches a speed of 25km/h (15mph)?
That's "all" the app has to do, just disable the SMS function while driving.
One downside that i would like you to ponder about, is the fact that this would disable the text function for the passenger as well, how can this be worked around without the driver being able to do so as well?
Perhaps a WiFi module somewhere in the car which gives more accurate GPS positioning data which then leads to you being able to tell if the phone is in the driver seat or not?
I'm not doing this for commercial purposes or for profit, i just had a good intention which i would like to see available to everyone and perhaps even standard in the next generation of phones so we don't loose lives due to technical gadgets..
Click to expand...
Click to collapse
Hate to be the bearer of bad news but gps is not accurate enough to tell if you are in the passenger seat of a car.
The speed limit thing can be done though, and I think has, but it would be easier for drivers to simply use self control.
However you can try apps like call guard, that apparently blocks texts and calls while you are driving.
Dave
( http://www.google.com/producer/editions/CAownKXmAQ/bigfatuniverse )
Sent from my LG P920 using Tapatalk 2
or the most dummy-proof way: don't text and drive!
unless you are using your device as an GPS, shouldnt be using a phone while driving anyway.
got a text? read it during red light/traffic jam
need to talk on phone? invest in headset
etc
jt.one said:
or the most dummy-proof way: don't text and drive!
unless you are using your device as an GPS, shouldnt be using a phone while driving anyway.
got a text? read it during red light/traffic jam
need to talk on phone? invest in headset
etc
Click to expand...
Click to collapse
I know that you shouldn't, and i don't unless i'm parked.
This is my issue: google: teen-sentenced-to-prison-for-texting-while-driving-death (a few days old)
Over here perhaps 10-15% of drivers admit that they do text while drying more then once a week,
and most of them claim that they don't notice any difference while driving, meaning that they think they operate just as good as they normally do.
The rest knows it's bad but do it anyway.
Thx mistermentality, will check out Call Guard
Hi All I have just purchased a new nexus 5 (gear live pre-ordered) in a curious attempt to have a go at android from my Iphone 5c.
I am tweaking the handset at the moment to give me some lost functionality from IOS. I have stumbled across a really painful problem that i can not find a solution to. I use a pair of bose wired earphones to listen to music and use as hands free in the car. On my iphone, I am used to to pushing the mic button and activating the voice dial from the locked screen, all good.
When i try doing this on my nexus, i get the "can not use OK Google until the phone is unlocked" message in my ear.
I have to have a passlock on the handset due to work security restrictions.
Does anyone have a work around for this? I am hoping my new gear live will keep the pass lock when in close proximity (A major flaw otherwise - unlocking your phone before you can see anything on your smartwatch!) in the interim though, putting a pass key in the phone every time i want to make a call whilst riving is pretty poor!
currently on stock 4.4.4. not rooted yet -
Thanks all
randomtechgeek said:
Hi All I have just purchased a new nexus 5 (gear live pre-ordered) in a curious attempt to have a go at android from my Iphone 5c.
I am tweaking the handset at the moment to give me some lost functionality from IOS. I have stumbled across a really painful problem that i can not find a solution to. I use a pair of bose wired earphones to listen to music and use as hands free in the car. On my iphone, I am used to to pushing the mic button and activating the voice dial from the locked screen, all good.
When i try doing this on my nexus, i get the "can not use OK Google until the phone is unlocked" message in my ear.
I have to have a passlock on the handset due to work security restrictions.
Does anyone have a work around for this? I am hoping my new gear live will keep the pass lock when in close proximity (A major flaw otherwise - unlocking your phone before you can see anything on your smartwatch!) in the interim though, putting a pass key in the phone every time i want to make a call whilst riving is pretty poor!
currently on stock 4.4.4. not rooted yet -
Thanks all
Click to expand...
Click to collapse
I'll be honest and say that being able to make a call with the phone being pin locked would be a security risk. Now as for a workaround I can only think of one thing that would work but it requires some time to configure things correctly.
You could us ethe app tasker to automate this. You can set a profile for when you are in your car. When you are driving in the car (e.g. moving over 10 MPH) you can have tasker turn off your PIN Lock. Then when you get out of your car (eg not moving) it would reenable your PIN lock.
If that's too hard to configure (I can show you if you are interested in the above method) You can just set up a much simpler profile in tasker that whenever your BT headset is connected disable your PIN lock. THough this is less secure.
Those are the only options I can think of and honestly I would be surprised if anyone came up with a true solution to this
I have posted a similar post in the CRV Owners forum, but I thought this forum would make more sense since it's filled with a bunch of hardware-hacking programmers!
The interface between my car and my phone (LG G2 Lollipop stock) is abysmal. I have seen a number of posts on the web about this issue with modern cars, but no real solutions. The following is a list of what I would like the interface to be between the phone and car. Then at the end of the email I'll flame a little about the "why"s.
GIve me a button to allow me to talk to my phone directly without the HondaLink getting in the way. There was a similar issue with a Volkswagon and a solution using Tasker to intercept the call. That solution doesn't work with my Honda and is a kludge.
Always have the phone interrupt the radio (whether it's a call or audio, e.g. Google maps navigation). For me, the information coming from the phone will always be more important than the music or talk show on the radio.
Mirror the phone screen onto the car screen when I'm driving (so I can see my map when I need to)
When I receive a call, let the phone do the talking (the phone can speak the caller's name to me and can send the caller's name over the bluetooth connection) and let me hit a button to answer it.
Has anyone successfully hacked into the firmware/software in the CV-R to fix these issues? Is it possible? At this point, based on my research, I see no other option. If there is another option that doesn't involve replacing the system or "just dealing with it," I'd love to hear it.
The "why"s:
My phone is custimizable, has all of my contacts, recognizes my voice, has GPS, accurate and up-to-date maps, and does everything that I need a phone and navigation system to do. The Honda solution tries to duplicate all of that functionality and does it very poorly. As one user wrote last year, my $50 bluetooth headset can listen to my phone and pipe in navigation directions and let me know when I get a call. It is a joke that an expensive car can't even get that part right. The fact that I can't put my phone screen on the car screen while I'm driving is idiotic. Now I've got to find some way to hold my phone up for navigation. I don't want this post to degenerate into a series of posts and counter-posts on whether drivers can handle the increased cognitive demand. I've been driving long enough to see that the majority of drivers are not paying any attention at all to the road anyway and no one seems to care.
The hardware in the CR-V seems to be capable of doing the things that I have listed above. So, if the Honda programmers can't get it the way I want it, the only solution is to take the programming away from them and do it ourselves. Has anyone done this yet?
Thank you in advance for your help.
As per phonearena.com Mate 9 is starting to get update to Oreo
https://www.phonearena.com/news/Unlocked-Huawei-Mate-9-receiving-Android-8.0-Oreo-in-the-US_id102104
Wait is over
Android Central is reporting it too. Anyone get it?
I have checked mine several times and nothing yet
it's approved for update in Firmware Finder
Edit: nevermind, jumped the gun...only approved if you check without the imei.
As someone who has been on the beta test for this for the past 2 months, it's pretty disappointing that they're releasing this. It has issues that they haven't fixed. If .360 is the final version, I'll have to see if I can get rolled back to Nougat.
dscline said:
As someone who has been on the beta test for this for the past 2 months, it's pretty disappointing that they're releasing this. It has issues that they haven't fixed. If .360 is the final version, I'll have to see if I can get rolled back to Nougat.
Click to expand...
Click to collapse
What issues are you having?
audioman42 said:
What issues are you having?
Click to expand...
Click to collapse
I stream Google Play Music via Bluetooth in my car. Until Oreo, when I turn off my car, or switch to another audio source, streaming from the phone is paused. Next time I start up the car, it resumes. Now, I have about a 50% chance of it resuming Google Play Music. It will randomly decide to instead use the built in music app to play something stored on the phone (one of the demo songs that came with the phone, or the one track I have saved on the SD card). I’m constantly having to go to Google Play Music & re-start whatever I was playing.
I’m also having unreliable visual notifications, particularly text messages (I use Textra). I do at least sometimes get the audio ding, but more often than not, no flashing light, and no badge on the shortcut. So if I’m not within earshot of the phone when I get a txt, I don’t know I received one (I can’t say for certain audio notifications always work, but I know at least sometimes I’ve heard the ding, but visually the phone doesn’t indicate it).
The above two issues are new since the Oreo update. Another issue I have that also existed in Nougat: the phone has difficulty managing multiple simultaneous Bluetooth connections. My car requires two connections: one for phone calls, and another to a 3rd party streaming adapter. If I have my Huawei Watch on/already connected to the phone when I get in the car, the two car connections won’t connect, at least not both of them. I have to toggle Bluetooth off/on on the phone to get all three connected at the same time. If I don’t have my watch on, there’s a better chance that both will connect, but at least one will. I didn’t seem to have these issues with my previous Note 3, but the Mate 9 seems to have a hard time reconnecting Bluetooth when there are multiple simultaneous connections involved. This issue is the one that caused me to join the beta, hoping to ensure it was fixed in the new software. Instead, it persists, and I gained a couple new ones.
dscline said:
I stream Google Play Music via Bluetooth in my car. Until Oreo, when I turn off my car, or switch to another audio source, streaming from the phone is paused. Next time I start up the car, it resumes. Now, I have about a 50% chance of it resuming Google Play Music. It will randomly decide to instead use the built in music app to play something stored on the phone (one of the demo songs that came with the phone, or the one track I have saved on the SD card). I’m constantly having to go to Google Play Music & re-start whatever I was playing.
I’m also having unreliable visual notifications, particularly text messages (I use Textra). I do at least sometimes get the audio ding, but more often than not, no flashing light, and no badge on the shortcut. So if I’m not within earshot of the phone when I get a txt, I don’t know I received one (I can’t say for certain audio notifications always work, but I know at least sometimes I’ve heard the ding, but visually the phone doesn’t indicate it).
The above two issues are new since the Oreo update. Another issue I have that also existed in Nougat: the phone has difficulty managing multiple simultaneous Bluetooth connections. My car requires two connections: one for phone calls, and another to a 3rd party streaming adapter. If I have my Huawei Watch on/already connected to the phone when I get in the car, the two car connections won’t connect, at least not both of them. I have to toggle Bluetooth off/on on the phone to get all three connected at the same time. If I don’t have my watch on, there’s a better chance that both will connect, but at least one will. I didn’t seem to have these issues with my previous Note 3, but the Mate 9 seems to have a hard time reconnecting Bluetooth when there are multiple simultaneous connections involved. This issue is the one that caused me to join the beta, hoping to ensure it was fixed in the new software. Instead, it persists, and I gained a couple new ones.
Click to expand...
Click to collapse
Same here with bluetooth inconsistencies when connected to my car. I have resynched several times and sometimes it helps for a short while and other times no improvement. Sometimes I can control songs and other times not. Sometimes it shows songs and other times it shows connecting. Sometimes it shows the correct name of song and other times it freezes on a song title that is long gone. Even when deleting and resynching my phone, an old song title is displayed and not the same as being played. Total bummer as I use bluetooth music every time I get into my car. On recent update (360) which appears to be the same one they are releasing as OTA.
hmmm, this must be a states model thing, my huawei mate 9 works perfectly on oreo...i dont use textra, use normal default...anyway is one of the reason i dont buy or use states systems on no phone...i always buy the international phones(orignal phone) the company put out...they better and receive the update in a timely manner...sorry, but state phones suck! i havent bought one in over at least 10 years....
Still waiting. To be honest though, it's not even Oreo I want, I just want the dang security updates. April 2017 is wayyy too old.
dscline said:
I stream Google Play Music via Bluetooth in my car. Until Oreo, when I turn off my car, or switch to another audio source, streaming from the phone is paused. Next time I start up the car, it resumes. Now, I have about a 50% chance of it resuming Google Play Music. It will randomly decide to instead use the built in music app to play something stored on the phone (one of the demo songs that came with the phone, or the one track I have saved on the SD card). I’m constantly having to go to Google Play Music & re-start whatever I was playing.
I’m also having unreliable visual notifications, particularly text messages (I use Textra). I do at least sometimes get the audio ding, but more often than not, no flashing light, and no badge on the shortcut. So if I’m not within earshot of the phone when I get a txt, I don’t know I received one (I can’t say for certain audio notifications always work, but I know at least sometimes I’ve heard the ding, but visually the phone doesn’t indicate it).
The above two issues are new since the Oreo update. Another issue I have that also existed in Nougat: the phone has difficulty managing multiple simultaneous Bluetooth connections. My car requires two connections: one for phone calls, and another to a 3rd party streaming adapter. If I have my Huawei Watch on/already connected to the phone when I get in the car, the two car connections won’t connect, at least not both of them. I have to toggle Bluetooth off/on on the phone to get all three connected at the same time. If I don’t have my watch on, there’s a better chance that both will connect, but at least one will. I didn’t seem to have these issues with my previous Note 3, but the Mate 9 seems to have a hard time reconnecting Bluetooth when there are multiple simultaneous connections involved. This issue is the one that caused me to join the beta, hoping to ensure it was fixed in the new software. Instead, it persists, and I gained a couple new ones.
Click to expand...
Click to collapse
I've noticed similar Bluetooth problems. I stream in my car pretty often and through headphones at work, and at times I won't be able to skip songs via the receiver/headset. Since a reboot always fixes it, I've been doing preemptive reboots as I walk to my car in the morning to circumvent the issue.
I've had zero issues with Textra. If anything, it's working even better now than it did before - all of my MMS sending issues are gone. Apparently, though, this was less of a Huawei problem and more of a Nougat problem.
cross1989 said:
hmmm, this must be a states model thing, my huawei mate 9 works perfectly on oreo...i dont use textra, use normal default...anyway is one of the reason i dont buy or use states systems on no phone...i always buy the international phones(orignal phone) the company put out...they better and receive the update in a timely manner...sorry, but state phones suck! i havent bought one in over at least 10 years....
Click to expand...
Click to collapse
Which region did you rebrand to? I was on 432 running a custom ROM for a while, but went back to 567 thinking that would solve my MMS sending issues. I want to rebrand, but I've heard that rebranded phones don't receive OTA updates because the IMEI doesn't match the region.
Thanks
I did not rebrand any thing, as I stated I don't buy state side phones, I buy original unlock phones directly from company (Amazon).. I have international version, MHA-L29C185... Now on oreo from Ota... Yea you loose Ota on those rebranding systems most of those require to unlock bootloader and twrp... That alter the system... If you want a good Huawei phone, buy international or China version off Amazon, yes both work in the states.
Just got my ota update today
Can someone who got Ota update check to see if any of the files on the FF app are giving an imei approval?
Mine still isn't and I didn't get Ota yet, so if it does for you and u got the Ota it may shed some light on whether the server shown on FF is directly linked to Ota files...
I just got the OTA update...downloading it now
kullum79 said:
I just got the OTA update...downloading it now
Click to expand...
Click to collapse
Where are you located??
shae23 said:
Where are you located??
Click to expand...
Click to collapse
I am in Chicago Central Standard Time... playing with the camera as we speak....
kullum79 said:
I am in Chicago Central Standard Time... playing with the camera as we speak....
Click to expand...
Click to collapse
Lool same location, no update, man Huawei is funny, oh well, guess it'll get here in its own time
It doesn't matter about the area it's being done in Bach's by imei .
---------- Post added at 09:11 AM ---------- Previous post was at 09:02 AM ----------
U can download it in ff but when it finishes download and install it won't verify because the it's has the imei in the download bricked one phone so I will wait for the ota I called huwaei to c about unbricking and the told me the date and time of the forced update voided the warranty
I got my Oreo update just a few hours ago, bought off Amazon, in KY, on T-Mobile
Oreo Update
I got my OTA update late yesterday. Haven't had it long enough to see if the battery life is better.
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