on body detection*
Hi, my one m9 is 2.7 weeks old , I setup a lockscreen password and then smartlock , I realised that on body detection is missing .
I waited , just because play services might update itself,
but nothing happened.
HTC one m9 should support it as it has an accelerometer
Tell me what the problem is , is it that I'm using a topic old version of play services , if that's the case , could you advice me as to which one should I install . My current play services version is : 7.0.99(1809214-448)
Just for the info ,my one m7 has on body detection
Thanks in advance ,
sishirbaid
EDIT
it now works!
all you need to do is update google play services to :- Google Play services 7.3.29 (1866531-448)
link down here
http://www.apkmirror.com/apk/google...ices-7-3-29-1866531-448-android-apk-download/
Moderators, you can close this thread.
That is only for 5.1 I think. We are on 5.0.2 now.
threev said:
That is only for 5.1 I think. We are on 5.0.2 now.
Click to expand...
Click to collapse
i think its there.. (it is on mine)
based on this article
http://www.androidcentral.com/smart-lock-body-detection-now-rolling-out-lollipop-devices
under Settings/Security (set a lock type first) then under trusted agents select Smart Lock
I had it on my m8 with 5.0.1 sense 6 but not on my m9. Used it well. Need it back. ?
Sent From My HTC One (M8)
I can confirm that the feature is on the M8 but not the M9. It was a useful feature.
nutmegy said:
i think its there.. (it is on mine)
based on this article
http://www.androidcentral.com/smart-lock-body-detection-now-rolling-out-lollipop-devices
under Settings/Security (set a lock type first) then under trusted agents select Smart Lock
Click to expand...
Click to collapse
Weird. I don't have it on my M9 but you do? I had it on my Nexus 5 but I think I assumed it came with 5.1 because they happened at the same time.
HTC support informed me that the developers decided to disable it in Sense 7. No information available on whether it will return with a future update.
mzguy said:
HTC support informed me that the developers decided to disable it in Sense 7. No information available on whether it will return with a future update.
Click to expand...
Click to collapse
well, that cant be true AS on- body-detection is a part of google play services , htc cannot modify google play services. well , the innitial release of play service which shipped with our phones could have been modified but i tried installing the exact same version from apkmirror and it still lacked the feature
so it certainly is not blocked by htc. idk what the real problem is , i hope someone gets it quickly, im dying to use it again. :crying:
sishirbaid said:
well, that cant be true AS on- body-detection is a part of google play services , htc cannot modify google play services. well , the innitial release of play service which shipped with our phones could have been modified but i tried installing the exact same version from apkmirror and it still lacked the feature
so it certainly is not blocked by htc. idk what the real problem is , i hope someone gets it quickly, im dying to use it again. :crying:
Click to expand...
Click to collapse
It may be part of Google Play Services, but might Google provide a facility for Sense to disable it? HTC Sense skins the Android settings, so perhaps they just didn't give users a means to enable it. I'm not an Android developer though. Is this possible? I don't know which I'd rather have control here. With some things, Google is responsive and fixes issues quickly. With other critical issues, they are still present 6 months after being reported!
mzguy said:
It may be part of Google Play Services, but might Google provide a facility for Sense to disable it? HTC Sense skins the Android settings, so perhaps they just didn't give users a means to enable it. I'm not an Android developer though. Is this possible? I don't know which I'd rather have control here. With some things, Google is responsive and fixes issues quickly. With other critical issues, they are still present 6 months after being reported!
Click to expand...
Click to collapse
A new version of google play services is rolling out . Let's wait and see what that one does for our phones.
It is version 7.3 and our device specific IE 448 isn't yet available on apkmirror , will post as to what it does in reguard to on body detection .
NOTE do not install just any version of play services on your device . Install only the following
X.xxx(xxxxxxxxxx-448)
Working NOW
okay, i can confirm, on-body detection is working with the newest play services. namely 7.3.29 (1866531-448)
ill post a link to the file in the original post
There is an XDA thread entitled What Is Lost by Moving to CM from FireOS. This thread is the opposite: What is Lost by Staying with FireOS instead of Switching to CM?
Now, obviously, there is a difference in UI, which involves a substantial amount of individual preference. Some people like FireOS, others like CM.
But what concrete things are unavailable that a typical Android user may want?
For example, as of this posting, it appears that Amazon Underground will not (ironically) work on the Amazon Fire Phone.
Which common apps will still not work reliably with FireOS?
Anything else?
That depends. Do you mean to side load Google Play services and the Play Store?
I think FireOS (with root, Google Framework etc) you would keep all Amazon stuff.. on CM, you would lose everything related to the Amazon framework stuff. I personally just stay on root for now.
DePingus said:
That depends. Do you mean to side load Google Play services and the Play Store?
Click to expand...
Click to collapse
From everything I'm reading here on XDA, there does not seem to be a reliable way to get it work (and stay working)... or has someone found a way?
rockpaperlizard said:
From everything I'm reading here on XDA, there does not seem to be a reliable way to get it work (and stay working)... or has someone found a way?
Click to expand...
Click to collapse
I've had Google services running OK since I installed several months ago. I'm sticking with rooted stock with a third party launcher. IMO this combination works fine and I've pretty much zero annoyances with it.
The threads for the roms are pretty clear on the bugs: lots of camera issues, no mute, no nfc, Play service crashes. Some people are also reporting call drops and wifi issues on certain channels. If you read through the thread you'll notice a few people end up switching back to stock FireOS.
My phone updated to 4.6.4 when I got it so Google Play Services won't work (unless I downgrade to 4.6.3, but I don't want to start flashing stuff just yet). Right now I'm using a combination of F-Droid and apkmirror to sideload apps like FireFox and alternate launchers. I've gone through the pre-installed apps and disabled some of the Fire OS crap like Quick Start, AT&T app, Facebook and Twitter connect, Telemetry junk, etc. Some apps like Silk Browser will not stay disabled (because it does an update and I haven't figured out how to stop it from auto-updating).
Right now I'm REALLY missing Google Inbox.
DePingus said:
Some apps [...] will not stay disabled because it does an update
Click to expand...
Click to collapse
Disable the following apps:
• Amazon Device Client Platform
• DCP Platform Contracts
• System Update(s) - yes, there are 2 apps with that description, disable BOTH
This will stop all updates: app updates and OS related OTA updates.
ratbags said:
I've had Google services running OK since I installed several months ago. I'm sticking with rooted stock with a third party launcher. IMO this combination works fine and I've pretty much zero annoyances with it.
Click to expand...
Click to collapse
DePingus said:
,,,,My phone updated to 4.6.4 when I got it so Google Play Services won't work (unless I downgrade to 4.6.3, but I don't want to start flashing stuff just yet). Right now I'm using a combination of F-Droid and apkmirror to sideload apps like FireFox and alternate launchers.
Click to expand...
Click to collapse
This is the part that confuses me... some people say Google Play store is working fine on FireOS and others say it won't work. Can you explain why the different reports? Does it all come down to downgrading to FireOS 4.6.3 and sticking with that version? If so, isn't Stagefright an issue?
rockpaperlizard said:
Can you explain why the different reports? Does it all come down to downgrading to FireOS 4.6.3 and sticking with that version? If so, isn't Stagefright an issue?
Click to expand...
Click to collapse
Bottom line: Google Play Store & services...
• ...work well on the "GSM unlocked" OS versions - 35.4.6.1 (461013820) and 35.4.6.3 (463001620).
• ...doomed on the "AT&T" OS versions - 32.4.6.1 (461013320) and 32.4.6.4 (464000420)
• GER version of the OS was problematic as well, tested it myself in the beginning (just as another example)
Using the latest US "GSM unlocked" 4.6.3 (463001620) is the best option, all known Stagefright vulnerabilities are patched in this one*.
And yes, all OS versions can be installed on all devices, netlock is ofc. not affected, multi language support is available.
Using the AT&T verson is a lost cause, because you have to use a work around, e.g. blocking updates of the Play services or uninstalling Play services updates everytime they update.
It's a dead end, because (some) apps will demand a newer version of the Play services, so all the effort is not worth it.
*A little bit of history: Stagefright Patch Round 1: 4.6.3 (463001420) / Stagefright Patch Round 2: 4.6.3 (463001620)
rockpaperlizard said:
This is the part that confuses me... some people say Google Play store is working fine on FireOS and others say it won't work. Can you explain why the different reports? Does it all come down to downgrading to FireOS 4.6.3 and sticking with that version? If so, isn't Stagefright an issue?
Click to expand...
Click to collapse
I blocked updates after 461 as I anticipated problems. Stage fright isn't much of an issue because I use a third party SMS app and block auto retrieval of MMS messages. Then again, I never send or receive MMS.
Bingo Bronson said:
Bottom line: Google Play Store & services...
• ...work well on the "GSM unlocked" OS versions - 35.4.6.1 (461013820) and 35.4.6.3 (463001620).
• ...doomed on the "AT&T" OS versions - 32.4.6.1 (461013320) and 32.4.6.4 (464000420)
• GER version of the OS was problematic as well, tested it myself in the beginning (just as another example)
Using the latest US "GSM unlocked" 4.6.3 (463001620) is the best option, all known Stagefright vulnerabilities are patched in this one*.
And yes, all OS versions can be installed on all devices, netlock is ofc. not affected, multi language support is available.
Using the AT&T verson is a lost cause, because you have to use a work around, e.g. blocking updates of the Play services or uninstalling Play services updates everytime they update.
It's a dead end, because (some) apps will demand a newer version of the Play services, so all the effort is not worth it.
*A little bit of history: Stagefright Patch Round 1: 4.6.3 (463001420) / Stagefright Patch Round 2: 4.6.3 (463001620)
Click to expand...
Click to collapse
WOW! That is great info! THANK YOU! :good: That should be part of a FAQ (or a FAQ on its own).
Questions:
If you buy an AT&T Fire Phone, and it includes the unlock code, will you still have the problems since it still is the AT&T ROM?
When buying a phone, besides asking the seller to turn it on and tell you the version of the ROM (which they may not do if it is new in the box), how do you know if it is a GSM unlocked version or the AT&T version?
Does the GSM unlocked version of FireOS only auto-update to new GSM unlocked versions, or has Amazon merged everything into one FireOS version at this point?
rockpaperlizard said:
If you buy an AT&T Fire Phone, and it includes the unlock code, will you still have the problems since it still is the AT&T ROM?
Click to expand...
Click to collapse
Yes, the unlock only changes some information stored in a chip, eeprom maybe, who knows...
Problems are caused by the ROM, so the best thing to do is:
Receive new phone, boot it up, don't register anything and don't connect to WiFi, check the installed version, if AT&T:
Power off the device, sideload the 4.6.3 image via ADB recovery (there's a link in my sig. "Fire Phone stock recovery: factory images")
When buying a phone, besides asking the seller to turn it on and tell you the version of the ROM (which they may not do if it is new in the box), how do you know if it is a GSM unlocked version or the AT&T version?
Click to expand...
Click to collapse
Fortunately, the seller doesn't need to boot it up, on the box is a sticker with basic info like: storage size, OS version, IMEI, UPC... so as long as the seller is honest, it should be clear which version is actually on the device.
Does the GSM unlocked version of FireOS only auto-update to new GSM unlocked versions, or has Amazon merged everything into one FireOS version at this point?
Click to expand...
Click to collapse
Each version is independent and it will stay that way, wouldn't make much sense for them to change it and I guess there are some agreements they made with AT&T which have to be met...
Bingo Bronson said:
...
Fortunately, the seller doesn't need to boot it up, on the box is a sticker with basic info like: storage size, OS version, IMEI, UPC... so as long as the seller is honest, it should be clear which version is actually on the device.
...
Click to expand...
Click to collapse
Thanks for all the super helpful info! :good:
Do the outside of the boxes indicate sufficient version info to tell if it is AT&T or not?
rockpaperlizard said:
Do the outside of the boxes indicate sufficient version info to tell if it is AT&T or not?
Click to expand...
Click to collapse
Well, it does read the short version number, like "OS V 3.6.0" but the seller knows ofc. that he bought (e.g.) a pallet full of AT&T devices because it has to be declared on the paperwork.
edit: A 2nd sticker on the other side of the box states: "the device can only be used with a SIM card from T-Mobile" (dark grey font on black background, neat ^^)
I guess they will have a sticker like this in the U.S. for the AT&T variants as well, so that's another good indicator to know "what's in the f***ing box !?!"
The two biggest sellers (regarding Fire Phone) on Ebay (US site of ebay, fer sure) sell the remaining "AT&T UNLOCKED (+ PRIME)".
Bingo Bronson said:
• ...work well on the "GSM unlocked" OS versions - 35.4.6.1 (461013820) and 35.4.6.3 (463001620).
Click to expand...
Click to collapse
Forgive me if I missed in this thread... Which versions of the Play Service and Play Store are you referring to?
FWIW, I am running 4.6.4 with Player Services 7.8.99 and Play Store removed. I get "XXX relies on on Google Play services which is not supported on your device" complaints from some apps, but most things continue to work anyway. That is most non-Google apss - Hangouts and YouTube are problematic.
jwernerny said:
Which versions of the Play Services and Play Store are you referring to?
Click to expand...
Click to collapse
No version in particular. (All versions I were referring to are Fire OS version numbers)
On the GSM unlocked version, I never had trouble with any version of Play Store & Services, so I just used the latest at that time (updates were also without issues).
I am running 4.6.4 with Play Services 7.8.99 and Play Store removed [...] complaints from some apps, but most things continue to work anyway [...] Hangouts and YouTube are problematic.
Click to expand...
Click to collapse
Well, as long as it's working for you and all your favorite apps keep working properly, you don't need to switch. Livin' on the edge!
Speaking of YouTube, if you like to download videos / audio from there:
SnapTube (Received more updates lately, still beta, supports multiple media sites, can download audio only on YT as well)
NewPipe (Very lightweight, watch or download videos, just released this week, still new & buggy = be gentle ^^)
So If you have an ATT phone there is no way to get the software off the unlocked version on it?
I have the ATT and if I need to I will buy an "factory unlocked for learning rooting and installing mods as It has been a couple of three years since I have done this.
I hope the fire phone mod project succeeds and I think it will be great when the bugs get worked out. I enjoy following this but I bought the unlocked ATT because I needed a new smart phone and for $115 with a year of prime...
Ask me about my warranty service from Amazon!!!!!!!! Horror story but thats another forum!!
RandB fan said:
So If you have an ATT phone there is no way to get the software off the unlocked version on it?
[...] but I bought the unlocked ATT because I needed a new smart phone and for $115 with a year of prime...
Click to expand...
Click to collapse
Don't worry, there is no "AT&T phone" only an AT&T OS variant.
All Fire Phones are the same, regarding hardware, netlock is no biggie since you already received an unlock code.
You can install the 4.6.3 version on your device, since it is the preferred version when it comes to Google Play Store & services.
Maybe you could explain that process for all of us ATTers? links?
So I don't screw things up...
Hey guys... could you clarify things up a bit so I do things correctly. My case is this:
I've ordered a brand new in box Fire Phone off Ebay that should be arriving in a couple of days, and I know for sure (as it's clearly stated by the seller) that this is the AT&T version. According to the seller they don't open the box, they just provide you the unlock code and you do the whole unlock and activation yourself.
The main reason I ordered this phone is to give it to my kid as his first smartphone but at the same time enjoy the year of Amazon Prime service, since I've been a Prime subscriber for a good 3 years now and I'm up for renewal in November. So essentially my goal is to renew my Prime subscription and give my son a decent Android phone for $35 at the same time.
Based on what I've read I'd be planning initially to keep FireOS to make it stable for him. He also has a Nexus 7 Tablet where he does most of his gaming and school stuff, so I think we can live with FireOS to keep it stable as a phone but still I'd like to install Google Playstore to have access to Google's apps, so I'd guess I'll have to replace the AT&T Rom the Unlocked-GSM FireOS ROM as described by Bingo.
What should be the recommended path for my case?... I don't want to compromise the initial activation so I get the Prime-year with no issues, after that I could play with all the Roms, roots and sideloads that are necessary (and have fun in the process). My concern is that I'd suppose that once I go through the initial activation process for the phone with my Amazon account most probably it will try to update to the latest OS version right?... since these is just a Rom I'd suppose that there should not be issues to let it update and then do the whole safetrap/rooting and sideload the GSM Unlocked Rom?... or should I take a different approach.?
Thanks, George
I remember reading about Google enabling Lollipop devices to start using Google assistant but it's now mid January and my device still has bupkis! I have tried the unofficial ways to get it but they all fail on my stock, un-rooted T-Mobile Samsung Galaxy Note 3. I get the Google Assistant Launcher to install but after I do, a reminder it says device is not supported. I have the Play Services beta and Google Search Beta and still nothing, what the heck?
They recently updated Google to this crappy new style which removed the hamburger menu and puts everything on a disappearing bottom bar like iPhones, WTF?! Also it moves all personal items to this weird button that looks like a pimple art demo and the mail Google feed simply shows news? I would rather have my personal Google (scores, travel times, shipping info, etc) on my main page and click a button for the news.
Why does Google always fluck with sh!t? Does anyone know how to enable Google Assistant on the Note 3? Thanks in advance...
It's now almost April and still nothing? Anyone have any ideas? Thanks in advance...
I've seen the app floating around the Play Store, but I'm not sure if it's compatible with Lollipop 5.0 since I'm running 8.1 via Lineage 15.1 (haggertk), but it's worth a try I guess.
Can't post a link as I'm still considered new despite being here for 4 going on 5 years now... RIP
Fifth313ment said:
It's now almost April and still nothing? Anyone have any ideas? Thanks in advance...
Click to expand...
Click to collapse