Related
According to this BBC article published today (17 May 2011) all android version with the exception of 2.3.4 version can expose personal data during the identification (Edit: Authentication) process with google services. A bad news ineed.
The good news, though, is that if this problem is publicised enough then it will force companies like Motorola to provide up-to-date version of android for their handsets. Of course not all old handsets can be upgraded but we all know Defy is very capable phone in terms of Android 2.3.4.
I'm still waiting for Froyo 2.2 upgrade, in the UK, and so furious with Motorola over this. Anyways, that matter is for another post.
yeah, tell me about it. I bought the phone from tmobile on date of launch... was told q1, then q2, now end of year... ahhh LOL
This doesn't mean anything. If the flaw is really critical, then I guess Google just release a patch for the module that's responsible for authentication - they won't force all carriers to update the whole system. Instead only some small fix may be pushed to affected devices.
Google announced today they will fix the problem on server-side.
Don't get it really, if plain text was sent out to google servers how the problem could be fixed on server-side? Also if no fix is necessary on the client side then why Android 2.3.4 was modified to encrypt data before sending it to the google?
Maybe this is me not understanding what the problem was. I found it difficult to imagine google would lie about the fix solution.
pkryger said:
This doesn't mean anything. If the flaw is really critical, then I guess Google just release a patch for the module that's responsible for authentication - they won't force all carriers to update the whole system. Instead only some small fix may be pushed to affected devices.
Click to expand...
Click to collapse
If Motorola is not going to give us 2.3.4 then they will have to release 2.2.3 to us if the solution turned out ineffective on the server-side.
Curr946 said:
yeah, tell me about it. I bought the phone from tmobile on date of launch... was told q1, then q2, now end of year... ahhh LOL
Click to expand...
Click to collapse
I really like (previously loved it) my Defy but can't understand why I have purchased a product about six months ago that I couldn't use many features that I wanted from day one. Many apps (email in particular) work properly from 2.2 and above.
I will only buy another phone from Motorola if it had the latest Android installed on it. I don't believe they are shipping Atrix with 2.2. Motorola will have the same attitude towards Atrix upgrade too.
CSharpHeaven said:
I really like (previously loved it) my Defy but can't understand why I have purchased a product about six months ago that I couldn't use many features that I wanted from day one. Many apps (email in particular) work properly from 2.2 and above.
I will only buy another phone from Motorola if it had the latest Android installed on it. I don't believe they are shipping Atrix with 2.2. Motorola will have the same attitude towards Atrix upgrade too.
Click to expand...
Click to collapse
Yeah? Well, email that didn't work on 2.1 still doesn't work on 2.2. For me anyway. Browser was way better in 2.1. Screen seems a bit smoother -- marginally. But you can move some apps to SD card.
you all should use cm7. it still has some bugs, but nothing serious, and its waay better and faster than motorolas softwares. plus its 2.3.4
Sent from my superfast CM7 Defy.
scrannel said:
Yeah? Well, email that didn't work on 2.1 still doesn't work on 2.2. For me anyway. Browser was way better in 2.1. Screen seems a bit smoother -- marginally. But you can move some apps to SD card.
Click to expand...
Click to collapse
Are you using the official 2.2 rom from Motorola?
zakoo2 said:
you all should use cm7. it still has some bugs, but nothing serious, and its waay better and faster than motorolas softwares. plus its 2.3.4
Sent from my superfast CM7 Defy.
Click to expand...
Click to collapse
If Defy officialy remains on Android 2.2 then I will be looking for alternative roms without caring about the warranty.
I like Android more than iphone but at least with iPhone you usually know some of the fixes that are in the works.
I don't know if a radio fix is coming with the next OTA update
I don't knonw when (if) I'll see an update for the Verizon Galaxy Nexus - I'm pretty sure I will but who is to say 100% other than Verizon or Android - tons of rumors like the 4.04 update and the 4.05 update etc but nothing concrete.
I suppose I'm kind of *****in but I'm also pretty sure they could make ALL of their clients happier if they released SOME info. E.g. a radio fix is in the works... or we'll have 4.04 for Verizon customers within 2 months - anything is better than nothing even if they don't' go into tremendous specfics.
Just my opinion of course.
boe said:
I like Android more than iphone but at least with iPhone you usually know some of the fixes that are in the works.
I don't know if a radio fix is coming with the next OTA update
I don't knonw when (if) I'll see an update for the Verizon Galaxy Nexus - I'm pretty sure I will but who is to say 100% other than Verizon or Android - tons of rumors like the 4.04 update and the 4.05 update etc but nothing concrete.
I suppose I'm kind of *****in but I'm also pretty sure they could make ALL of their clients happier if they released SOME info. E.g. a radio fix is in the works... or we'll have 4.04 for Verizon customers within 2 months - anything is better than nothing even if they don't' go into tremendous specfics.
Just my opinion of course.
Click to expand...
Click to collapse
We can always wish, but it has never been that way for any other device, so why would it change now?
Ive often wondered why they cant give us generic montly statements or something. Put an intern on it or something. 5 min of time once a month from an intern would be so easy.
boe said:
I like Android more than iphone but at least with iPhone you usually know some of the fixes that are in the works.
I don't know if a radio fix is coming with the next OTA update
I don't knonw when (if) I'll see an update for the Verizon Galaxy Nexus - I'm pretty sure I will but who is to say 100% other than Verizon or Android - tons of rumors like the 4.04 update and the 4.05 update etc but nothing concrete.
I suppose I'm kind of *****in but I'm also pretty sure they could make ALL of their clients happier if they released SOME info. E.g. a radio fix is in the works... or we'll have 4.04 for Verizon customers within 2 months - anything is better than nothing even if they don't' go into tremendous specfics.
Just my opinion of course.
Click to expand...
Click to collapse
I feel the same way.
RogerPodacter said:
Ive often wondered why they cant give us generic montly statements or something. Put an intern on it or something. 5 min of time once a month from an intern would be so easy.
Click to expand...
Click to collapse
That would be fantastic. Even if it said this month - update coming in June - that would be better than me hoping I might find a rumor that might seem credible. Then I'd know where to get genuine news relating to my device on MY carrier.
I am a looong time nexus user and I dont wish this anymore because I know it wont happend. Google works this way.
The only more or less "sure" thing is that when they say that it will be released in a couple of week is because it is already deployed in most employees devices for a long test and it will in fact be released in 2-3 weeks.
Google works this way because they don't have a ETA for when things are complete.
That's like saying telling CyanogenMod that you want more communication between them and the users so that they can post a timeline on when RC1/RC2 will be complete etc.
Things are just done when they're done.
RogerPodacter said:
Ive often wondered why they cant give us generic montly statements or something. Put an intern on it or something. 5 min of time once a month from an intern would be so easy.
Click to expand...
Click to collapse
Because...when something goes wrong, and they do not make their timeline, people would throw a fit, even more than they do now.
As others have mentioned, expecting any sort of ETA is completely unreasonable.
But honestly, this whole upgrade experience has been pretty underwhelming for two reasons: lack of communication and very slow speed. The volume bug -- a completely show-stopping bug -- took two weeks for a fix. I highly doubt it would take Apple that long to issue a software fix for such a serious bug. Sorry to bring Apple into the discussion, but it's true.
Not to mention that it's taken Google FIVE months to get NFC to be fully functional...
At the end of the day, having relatively quick updates of stock Android will probably keep me with Nexus devices, but an advertised and guaranteed monthly status update? That would be a killer USP. The silence between 4.0.2 and 4.0.4 was absolutely terrible.
boe said:
I like Android more than iphone but at least with iPhone you usually know some of the fixes that are in the works.
I don't know if a radio fix is coming with the next OTA update
I don't knonw when (if) I'll see an update for the Verizon Galaxy Nexus - I'm pretty sure I will but who is to say 100% other than Verizon or Android - tons of rumors like the 4.04 update and the 4.05 update etc but nothing concrete.
I suppose I'm kind of *****in but I'm also pretty sure they could make ALL of their clients happier if they released SOME info. E.g. a radio fix is in the works... or we'll have 4.04 for Verizon customers within 2 months - anything is better than nothing even if they don't' go into tremendous specfics.
Just my opinion of course.
Click to expand...
Click to collapse
Yes it sounds great, but it would just make things worse.
People would be exponentially more angry if they gave progress reports and they didn't go where people wanted. They'd complain even more because they'd know it wasn't fixing the way they wanted it to be fixed. And as soon as they promise a timetable and are unable to deliver, all hell would break loose. Either that, or they give a timetable too far in the future to keep from hurting themselves, and people complain the timetable is too far out.
Google and Verizon aren't just sitting on their asses doing nothing. They're working. Its downright insulting saying that Google isn't working hard on these updates. Just be patient ffs.
martonikaj said:
Yes it sounds great, but it would just make things worse.
People would be exponentially more angry if they gave progress reports and they didn't go where people wanted. They'd complain even more because they'd know it wasn't fixing the way they wanted it to be fixed. And as soon as they promise a timetable and are unable to deliver, all hell would break loose. Either that, or they give a timetable too far in the future to keep from hurting themselves, and people complain the timetable is too far out.
Google and Verizon aren't just sitting on their asses doing nothing. They're working. Its downright insulting saying that Google isn't working hard on these updates. Just be patient ffs.
Click to expand...
Click to collapse
Agreed. Also with Google (or the manufacturer doing updates) it has to be approved by the carrier UNLESS you're using the GSM model of Galaxy Nexus which is independent of any carrier.
This is from a news article I read yesterday,
“HTC has delivered a ROM to us however it is still having issues the reason that other sensation types have the update without issue and ours did not come out that way is because every ROM must be adapted to the hardware of the device because we use a different radio than other providers and also have applications such as wifi calling it also has to be compatible with those. What the HTC rep told you is most likely correct because once a ROM is delivered we have 2 weeks to test it and then approve it or send it back they then have 4 weeks to fix the bugs and return it back to us, where we are exactly in that process I do not know but that is how a ROM is delivered to the customer.
The original ROM was not delivered to us in November, we started testing it just recently but I think it has been longer than 2 weeks so at this point HTC most likely has the ball.
You bought a phone and it has been announced that you are getting ICS you have every right to know what’s going on with it and when you can see these awesome features. I did go into a lot of detail about how a ROM gets to the end user (you guys) but that wasn’t to point fingers only so you would have a better understanding of why you don’t have it yet, the bottom line is the Sensation has T-Mobile’s and HTC’s name all over it and both companies want to make you proud to be a Sensation owner so we are working as fast as we can to deliver it but also want to make sure that it stands up to your expectations.”
Click to expand...
Click to collapse
tl;dr it says that, the ROM that HTC made didn't meet T-Mobile's expectations and has to be fixed by HTC... then sent to T-Mobile to test the ROM equalizing MORE delay
I know OP has Verizon, but that's kind of your fault for using Verizon. We all know how it is when it comes to Verizon and keeping a tight control over their phones. I personally don't consider Galaxy Nexus (LTE) to be a "Nexus" device. It comes bloated with VZW apps, Verizon has to approve the update by Google, Factory images are no longer uploaded, etc.
Kind of off-topic but I'd love to see the idea of Google buying T-Mobile USA from Deutsche Telekom (owners of T-Mobile USA) then we would never have to worry about carriers trying to keep a tight grip on their phones. Not to mention then tight integration between Google services such as Google Voice would be tightly integrated between the carrier and Google services. Just a dream of mines.
Oh lord. Not another 'The Verizon Nexus is not a Nexus device' comment.
Sent from my Galaxy Nexus using XDA
adrynalyne said:
Because...when something goes wrong, and they do not make their timeline, people would throw a fit, even more than they do now.
Click to expand...
Click to collapse
But I'm not asking for an eta or timeline. Just something like "here's what we're doing this month, or even this quarter."
adrynalyne said:
Oh lord. Not another 'The Verizon Nexus is not a Nexus device' comment.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
Yea, everyone knows true Nexus devices only come with half the storage space and only on less desirable carriers.
TiltedAz said:
Yea, everyone knows true Nexus devices only come with half the storage space and only on less desirable carriers.
Click to expand...
Click to collapse
Ah, my bad
I'm gonna guess the OTA will come with the white 16 gig version on April 5th, and that the white Gnexs will come with 4.0.5 loaded. Just a hunch. The rumors have been early April, so on Thursday or that weekend is my guess.
Well, I don't know about everyone else, but my "fake" Nexus has had 4.0.4 for a long time now. I've seen 2 updates since I bought my Nexus (fairly early after release). Not EVERY update comes via OTA. The Nexus line has ALWAYS been like this. At any rate, my 3 month old "fake and unsupported" Nexus has already seen more updates than my Vibrant ever did.
As far as GSM users complaining over updates, shut up. Your phones didn't need the updates that Google implemented for the CDMA version. I don't want fixes for a phone that isn't mine. I don't want Google releasing something that isn't ready. Radio issues are up to Samsung and the carrier, not Google. Stop whining about Google. Stop thinking Google is the hold up. Google isn't the hold up. Samsung is the hold up. If you have a CDMA version, blame Samsung and Verizon. If you're GSM, place the blame where it largely belongs, on Samsung.
For some reason 80% of people on this forum seem to think that Nexus means that you get an update every month or something like that. Like we should be on 4.1.7 by now or something like that. It's the most insanely retarded community I think I've ever seen in my life.
As a member of the choir and a Verizon customer for12 years
.....
Keep preaching.
TiltedAz said:
Yea, everyone knows true Nexus devices only come with half the storage space and only on less desirable carriers.
Click to expand...
Click to collapse
Verizon is a less-desirable carrier for me. Just sayin'.
boe said:
I like Android more than iphone but at least with iPhone you usually know some of the fixes that are in the works.
Click to expand...
Click to collapse
and since when do you know about iphone updates before release? Apple is the most secretive tech company ever. They only comment on issues when they get really out of hand and media goes all over it (like the recent address book privacy issues or the better known antennagate).
iOS does have private betas though, which is kinda the equivalent of aosp for android in terms of release schedules. aosp 4.0.4 >>> 8 months >>> oem 4.0.4 updates
The styling I love. The way AW works I like. The internals of the watch I'm not happy with. It's screaming Gen 2 with all it should be now. Hate or love my post, it's my opinion.
Would you sell it to me and send it to Spain?
I made a couple of ROMS for the motoactv and I'd like to develop for the moto360 too, but it's going to take some time until it's released in Europe.
Sent from my GT-N7100 using XDA Free mobile app
dproldan said:
Would you sell it to me and send it to Spain?
I made a couple of ROMS for the motoactv and I'd like to develop for the moto360 too, but it's going to take some time until it's released in Europe.
Sent from my GT-N7100 using XDA Free mobile app
Click to expand...
Click to collapse
As long as after it's said and done I have everything I paid for it. I don't need to make money on it, but I also don't want to lose considering I can return for full refund. Let me know.
EVOme said:
As long as after it's said and done I have everything I paid for it. I don't need to make money on it, but I also don't want to lose considering I can return for full refund. Let me know.
Click to expand...
Click to collapse
I sent you a Private message.
dproldan said:
I sent you a Private message.
Click to expand...
Click to collapse
Replied
EVOme said:
The styling I love. The way AW works I like. The internals of the watch I'm not happy with. It's screaming Gen 2 with all it should be now. Hate or love my post, it's my opinion.
Click to expand...
Click to collapse
I may do the same, we'll see
After facing many connectivity issues and slow processor performance I'm on the fence about doing the same. It is sad as I really like the device but it is just too annoying.
I can't post my video on here but I have an awesome relic band I modified to get on my 360
ajamils said:
After facing many connectivity issues and slow processor performance I'm on the fence about doing the same. It is sad as I really like the device but it is just too annoying.
Click to expand...
Click to collapse
I'm on the verge of returning mine because of connectivity issues. I had seven disconnects during a 6 hour span today. Not sure what's causing them, I thought it was Greenify hibernating the Wear app, but I disabled it and the problem persists.
Log of my problems.
My phone is a Nexus 5 with CyanogenMod 11 M9, my 360 is on 4.4W.1 - KGW42N.
Anyone have any suggestions as to figuring out what's causing the disconnects?
Should I logcat both my N5 & 360?
B3RL1N said:
I'm on the verge of returning mine because of connectivity issues. I had seven disconnects during a 6 hour span today. Not sure what's causing them, I thought it was Greenify hibernating the Wear app, but I disabled it and the problem persists.
Log of my problems.
My phone is a Nexus 5 with CyanogenMod 11 M9, my 360 is on 4.4W.1 - KGW42N.
Anyone have any suggestions as to figuring out what's causing the disconnects?
Should I logcat both my N5 & 360?
Click to expand...
Click to collapse
I too get disconnection notifications all the time, but not sure it has actually effected notifications on the watch
slaydog said:
I too get disconnection notifications all the time, but not sure it has actually effected notifications on the watch
Click to expand...
Click to collapse
I'll continue to get event notifications or anything that was previously pushed to my device, but I can't do anything internet related. I normally check by doing an "Okay Google" and asking what my IP is. (It doesn't show it, but it's a simple search)
I'm almost all but certain that this is an AOSP or CyanogenMod problem, not the 360. What ROM are you running?
Over on the N5 CM 11 Nightly thread there's chatter about BT issues. I haven't been involved with the thread other than an initial flash to a Nightly 3 months ago then reversion back to Milestone, but some of the devs seem to be trying to fix the problem.
Artem at Android Police made a rant post about his 360 and specified disconnection issues. I checked his previous posts and it looks like he's running an AOSP ROM. Just Googling, "CyanogenMod Bluetooth issues" and you get a slew of posts about BT problems.
N5 CM just got a fix 16 days ago, so hopefully this is in the next Milestone. I'm tempted to flash the nightly to check, but I don't have any tinkering time right now because of work/school.
I'm going to guinea pig this app and have it reconnect when ever it disconnects (RIP battery life) but I'm not counting on it. I also just uninstall and reinstalled Android Wear on my N5, maybe that will help? - I read through the Artem post a bit more and an N5 user, Jason Bowers, mentioned that after to switching to Faux kernel things were seemingly better, I'm giving it a go.
Edit: Just want to point out that I'm retarded and CM doesn't work with Faux. I just got my N5 3 months ago and normally ran Sense, so was only Sense or AOSP concerned. Not CM others, didn't know it existed, no disclaimer on Faux N5 thread. - I might switch to a Nightly CM or a Faux compatible ROM, mainly because I'd like to experience my 360 before I make the final decision to return it or not. - Might try the BT app as previously mentioned.
I'm really curious if all these bad battery life problems people are having with their Wear devices are because they are on AOSP ROMs?
B3RL1N said:
I'll continue to get event notifications or anything that was previously pushed to my device, but I can't do anything internet related. I normally check by doing an "Okay Google" and asking what my IP is. (It doesn't show it, but it's a simple search)
I'm almost all but certain that this is an AOSP or CyanogenMod problem, not the 360. What ROM are you running?
Over on the N5 CM 11 Nightly thread there's chatter about BT issues. I haven't been involved with the thread other than an initial flash to a Nightly 3 months ago then reversion back to Milestone, but some of the devs seem to be trying to fix the problem.
Artem at Android Police made a rant post about his 360 and specified disconnection issues. I checked his previous posts and it looks like he's running an AOSP ROM. Just Googling, "CyanogenMod Bluetooth issues" and you get a slew of posts about BT problems.
N5 CM just got a fix 16 days ago, so hopefully this is in the next Milestone. I'm tempted to flash the nightly to check, but I don't have any tinkering time right now because of work/school.
I'm going to guinea pig this app and have it reconnect when ever it disconnects (RIP battery life) but I'm not counting on it. I also just uninstall and reinstalled Android Wear on my N5, maybe that will help?
I'm really curious if all these bad battery life problems people are having with their Wear devices are because they are on AOSP ROMs?
Click to expand...
Click to collapse
Interesting, I'm on Liquid Smooth (AOSP), so you could be right.
No other issues with Bluetooth that I've noticed - phone calls and streaming music seem to work fine...
---------- Post added at 02:23 PM ---------- Previous post was at 01:46 PM ----------
I left the Gear 2 not because I didn't like the watch, but because I couldn't stand stock-based ROMs any more - that and because the 360 looked so sweet and I wanted to try Android Wear - so I'm sticking with AOSP anyway, lol
Just got back a lil' while ago from returning mine. Build quality of the watch was a "little" disappointing to me, but the main issue was Android Wear; it just ain't fully baked yet. In addition to it not doing much, bugs with settings/connectivity and sending texts have me feeling it needs time.
After that time, I'll look at the hardware again; guessing it will be more capable as well.
Been struggling with returning mine. I had lost my pebble but then found it after i bought the 360. I have been wearing the pebble while waiting on my 360 screen protector. It providing me the same infomation it just doesnt look as good. I am wondering if the design is enough to keep it. I do have until Friday to decide.
dproldan said:
Would you sell it to me and send it to Spain?
I made a couple of ROMS for the motoactv and I'd like to develop for the moto360 too, but it's going to take some time until it's released in Europe.
Sent from my GT-N7100 using XDA Free mobile app
Click to expand...
Click to collapse
WOOT! I hope you get one dp. I've used your roms on my motoactv. I've got a 360 that I may buy from a coworker (he bought it and is going to return it, he loaned it to me over the weekend)
Anyone have a possible approximation of a date for release of 5.0 on our devices? I know it's nothing but a shot in the dark at this point, due to Sprint wanting to evaluate it and pile it full of their garbage apps.
hater0fyou said:
Anyone have a possible approximation of a date for release of 5.0 on our devices? I know it's nothing but a shot in the dark at this point, due to Sprint wanting to evaluate it and pile it full of their garbage apps.
Click to expand...
Click to collapse
Don't quote me on this but from what I've read we should have Lollipop by the end of the year. The Nexus 9 comes out November 3rd and it will be released with Android 5.0 already on it. And given our devices being a brand new release for Samsung we should have it relatively soon after all Nexus devices and Google Developer Edition devices receive the update.
Might take a little longer but I've had every Galaxy S device and the Note 3 (and now the 4) and they've always been good at updates compared to a lot of the other companies. And so has Sprint in that case as well - surprises me that your knocking on Sprint since they don't lock the bootloader on any of their Samsung devices like Verizon or AT&T and the amount of bloatware is relatively smaller.
You gotta look at it from the company's stand point (Sprint), it is understandable that they include that stuff - at least they aren't excessive about it.
Sent from my SM-N910P using XDA Free mobile app
No idea. The phone just go into people's hands on Thursday, and probably some pre-order may haven't even gotten their phones yet. Heck, we don't even have an official root method. Cool the jets just a bit.
Not that I don't blame you for being a bit excited for Android 5. It'll be interesting. It's going to come to sooner or later. I wouldn't necessarily hold my breathe on year's end, but it's probably not unrealistic either. I would assume more around February.
Sprint is pretty is light on Bloat. Probably means they don't have enough numbers to get more people willing to pay enough to put their crap on the phones and tick off more customers. Then again, I think Cyogenmod has some bloatware too.
My ideal rom, Nothing but Google Play Store; and maybe the other store services such as Movies, Music, and so forth since they're not really downloadable from the Google Play. Obviously a launcher too. and whatever background app are needed to make the phone work and all it's hardware. No widgets, no apps beyond the basic phone. This will never happen because there's no excitement is this basic of a ROM and carriers are paid to put apps on the devices or the manufacture put their versions on an app. I still laugh the Evo4G had two navigation/map applications on it that you could not uninstall, LOL.
But I digress..... Just be patient. Sounds like there are going to be some significant changes in the background of the OS, which means there are going to be unexpect bugs. Don't be surprise to see some apps get borked. I suspect the changes it gives us, will not be night and day of an experience, but most just a bit gray.
Follow Chainfire on Google+, might cool your excitement about Lolipop.......
hater0fyou said:
Anyone have a possible approximation of a date for release of 5.0 on our devices? I know it's nothing but a shot in the dark at this point, due to Sprint wanting to evaluate it and pile it full of their garbage apps.
Click to expand...
Click to collapse
Good morning - I've moved your thread to the Q&A section of this device's forums. Since it's obviously a question, that is where it should have been posted originally. Please post in the correct sections, thanks.
hater0fyou said:
Anyone have a possible approximation of a date for release of 5.0 on our devices? I know it's nothing but a shot in the dark at this point, due to Sprint wanting to evaluate it and pile it full of their garbage apps.
Click to expand...
Click to collapse
I would expect it sooner than later because the nexus 6 with specs rivaling the N4 is coming out soon and it will be installed with 5.0. This should motivate Samsung to move fast.
Sent from my SM-N910T using XDA Free mobile app
Hello!
This is not a problem specific to the HTC10, but I figured, I've got one and it's running LeeDroid's Oreo ROM, so maybe I have better luck here...
Got a Fit 2 Pro, and it looks like a great tracker. Problem is, Samsung's apps seem to detest either other manufacturers' devices or rooted ones. There's this thread here: https://forum.xda-developers.com/an...d-samsung-gear-app-android-n-samsung-t3547035 , however it's closed as the apps are supposed to be more 'open' now. However this is still not the case, as on my phone they appear as incompatible. I guess Samsung may have opened them to other devices, but not to rooted ones...
Anybody's got any success using Samsung's devices/apps?
Thanks!
krakout said:
Hello!
This is not a problem specific to the HTC10, but I figured, I've got one and it's running LeeDroid's Oreo ROM, so maybe I have better luck here...
Got a Fit 2 Pro, and it looks like a great tracker. Problem is, Samsung's apps seem to detest either other manufacturers' devices or rooted ones. There's this thread here: https://forum.xda-developers.com/an...d-samsung-gear-app-android-n-samsung-t3547035 , however it's closed as the apps are supposed to be more 'open' now. However this is still not the case, as on my phone they appear as incompatible. I guess Samsung may have opened them to other devices, but not to rooted ones...
Anybody's got any success using Samsung's devices/apps?
Thanks!
Click to expand...
Click to collapse
To use Samsung Tracker device with other manufacturers, your best option is to use an app like Open Fit.
You can find instructions for using it with the HTC 10 in THIS ARTICLE.
Thanks, but yeah, I've seen this and it won't cut it... at this point, an older version of Gear is a much better option than Open Fit unfortunately.
krakout said:
Thanks, but yeah, I've seen this and it won't cut it... at this point, an older version of Gear is a much better option than Open Fit unfortunately.
Click to expand...
Click to collapse
Fair enough. Though this is why I stay clear of anything Apple or Samsung personally.
Did you try installing the Samsung Accessory Service before trying to use their Fit App?
Pretty sure it's a prerequisite.
You're right, of course. The watch looked amazing (to me, at least - a great gadget between a fitness tracker and a smartwatch, certainly a couple of steps up from my Fitbit Charge 2) but obviously, little did I know about how locked these are... now I know
Yes, the Accessory Service is installed; with the modded apks it does work with my phone, but all them apps (except for Samsung Health, I think) still appear incompatible in Play. There's some suggestions about tweaking build.prop to fool it into thinking it's a Samsung device, but doing that opens a separate can of worms.
Btw, since we're at it, does Play sniff whether you're rooted or not?
Thanks for trying to help