My wife gave me a Fitbit for Christmas (Apparently, she wants me to get off my butt more and move around!)
The Fitbit is a small wearable device that measures your activity level, etc. The Fitbit app uses Bluetooth 4.0 to sync with the device. The sync function is working with my Samsung Galaxy S3 phone, which is setup with a custom ROM. The app does not sync on the G Pad using stock firmware.
According to the specs I see, the G Pad is supposed to have support for BT 4.0. I don't have any other devices that use it.
Does anybody here have a Fitbit device? I'm curious to know if anybody has tried to sync one on a G Pad with different firmware. Or on a GPE device. It might be that it would work on a 4.3 or 4.4 ROM.
I have a GPE and the app syncs fine with my Flex. I did, however, participate in the Fitbit beta program when they were testing for devices other than the Galaxy series (namely Nexus and Motorola devices with BT 4.0). My Fitbit app is version 1.8.4 if that helps. Here's the link to the beta program: https://docs.google.com/forms/d/1ZVjMd9JsDyo45g7uUV60clx7D780ouDka-wgNwvqxmA/viewform
Yes, I was playing with my new fitbit all day yesterday and unless you have one of their devices that is currently known to be compatible you have to be signed up for the Beta program. I am currently running android 4.4 with the cyanogenmod.
I signed up for the Beta by joining the google group here: https://groups.google.com/forum/#!forum/fitbit-android-sync-beta
Which allows you to go to: https://play.google.com/apps/testing/com.fitbit.FitbitMobile
Where you click become a tester. You then need to uninstall the fitbit app, clear the cache for the google play store (I used Clean Master to do this), and reinstall the fitbit app. You will now have the beta version of the app and when you login it will automatically find and start syncing to your fitbit. Note that by default the background syncing is turned off. If you want to be able to do this you have to enable it under devices.
Indeed LG gpad Hardware supports bt4. You need 4.3+ Android for bt4. I tried it with cm and it works.
If you want stock experience, then you have to wait for the Kitkat release.
Forgot to add : I tried it with a polar h7 bt4 heart rate monitor. Works great.
Not necessarily true regarding needing 4.3. They do support the LG G2 which is still on 4.2 stock. Im using it with mine and it syncs fine to the G2. I've never tried syncing to my G Pad tho
chadderbox said:
Not necessarily true regarding needing 4.3. They do support the LG G2 which is still on 4.2 stock. Im using it with mine and it syncs fine to the G2. I've never tried syncing to my G Pad tho
Click to expand...
Click to collapse
Good to know. I might check the fitbit after all.
Unfortunately the polar h7 doesn't want to pair with my Stock LG g2. It is after 4.3 that Android provides platform support to bt4. The solution that LG and Samsung used in the lower api levels apparently doesn't pay nice with all hardware.
http://developer.android.com/guide/topics/connectivity/bluetooth-le.html
Sent from my LG-V500 using Tapatalk 4
chadderbox said:
Not necessarily true regarding needing 4.3. They do support the LG G2 which is still on 4.2 stock. Im using it with mine and it syncs fine to the G2. I've never tried syncing to my G Pad tho
Click to expand...
Click to collapse
Correct. The Fitbit app syncs on my Galaxy S3, which is using a custom rom running Android 4.1.2. That version doesn't support Bluetooth 4.0., so I think they must have it working with Bluetooth 3 on some devices.
woody1 said:
Correct. The Fitbit app syncs on my Galaxy S3, which is using a custom rom ruining Android 4.1.2. That version doesn't support Bluetooth 4.0., so I think they must have it working with Bluetooth 3 on some devices.
Click to expand...
Click to collapse
I have an LG Lucid 2 running 4.1.2 on a custom rom and while the tech specs say it has bluetooth 4.0 I can't get it to sync. It doesn't even look like the beta version is installing at all but I don't know how to tell for sure.
colwellkr said:
I have an LG Lucid 2 running 4.1.2 on a custom rom and while the tech specs say it has bluetooth 4.0 I can't get it to sync. It doesn't even look like the beta version is installing at all but I don't know how to tell for sure.
Click to expand...
Click to collapse
Looks to me like the app checks to see what device it's installed on and the sync features are only enabled for certain devices. On the G Pad, I can check my my dashboard, etc., but I can't sync or interact with the tracker. On the S3, the app lets me sync and do other things.
I've no way of trying this myself but to you guys who say that you should have support for BT4.0, you could try and trick the device that will not sync. Go into the build.prop and take the ro buildnumber and name and so on and change them to the same of a device that you are certain it works with. If the the Fitbit is checking up against a buildnumber or model number, chances are it's from the build.prop. And could be funny if you could actually trick it just by making your phone into something else. ^^ (That is if BT4 is supported as said.)
CuraeL said:
I've no way of trying this myself but to you guys who say that you should have support for BT4.0, you could try and trick the device that will not sync. Go into the build.prop and take the ro buildnumber and name and so on and change them to the same of a device that you are certain it works with. If the the Fitbit is checking up against a buildnumber or model number, chances are it's from the build.prop. And could be funny if you could actually trick it just by making your phone into something else. ^^ (That is if BT4 is supported as said.)
Click to expand...
Click to collapse
That's a really good idea. I have double and triple checked the specs for my phone and it does say Bluetooth 4.0. I think I'll try this since it worked for me tricking QPair into thinking my gpad was a v510. Thanks!
colwellkr said:
That's a really good idea. I have double and triple checked the specs for my phone and it does say Bluetooth 4.0. I think I'll try this since it worked for me tricking QPair into thinking my gpad was a v510. Thanks!
Click to expand...
Click to collapse
Don't thank me yet. ^^ Fingers crossed.
CuraeL said:
Don't thank me yet. ^^ Fingers crossed.
Click to expand...
Click to collapse
Hmm, trying to edit build.prop on my phone does not seem to be working. Neither ES File Explorer, nor 920 Text Editor, are able to edit/rename/save anything to build.prop or in /system. It says is a read only file system.
colwellkr said:
Hmm, trying to edit build.prop on my phone does not seem to be working. Neither ES File Explorer, nor 920 Text Editor, are able to edit/rename/save anything to build.prop or in /system. It says is a read only file system.
Click to expand...
Click to collapse
Ah, rule number one of flashing KitKat: When done go to play store and get supersu, run it and let it update the binary. Choose normal, not CWM\TWPR. Let it finish the install, takes10 secs or so. Restart and tadaa root. It has to be done on all devices for now. Go into supersu after reboot and find Settings and then untick "Respect CM superuser bleh bleh."
Good luck.
CuraeL said:
Ah, rule number one of flashing KitKat: When done go to play store and get supersu, run it and let it update the binary. Choose normal, not CWM\TWPR. Let it finish the install, takes10 secs or so. Restart and tadaa root. It has to be done on all devices for now. Go into supersu after reboot and find Settings and then untick "Respect CM superuser bleh bleh."
Good luck.
Click to expand...
Click to collapse
My phone is running a custom 4.1.2 Rom called Lucidian. Would this still apply to that? I have superuser already working on it. And on my gpad running 4.4.2 cm11 I didn't have to do that to get root.
colwellkr said:
My phone is running a custom 4.1.2 Rom called Lucidian. Would this still apply to that? I have superuser already working on it. And on my gpad running 4.4.2 cm11 I didn't have to do that to get root.
Click to expand...
Click to collapse
And you have tried build.prop and it worked on your G Pad with CM 11? Funny, I had to do it on two different devices and just assumed I would have to on the G Pad as well. Now 4.1 i don't recall had any root issues, beats me why you can't edit the system on that one. Anyways, sounds like an incomplete root, like what happened in ICS 4.0 on the first Galaxy Note. Gave root but didn't do it for the full system..
Related
I found this on the http://techland.time.com/
So i dont take credit for this so i posted the whole page please in joy.
Unless you own one of the five phones that support Netflix's new Android app, Thursday's announcement was worthless.
But thanks to some clever folks on Reddit, Netflix's petty device restrictions needn't apply. With a rooted Android smartphone, you can trick Netflix into thinking your device is approved for streaming video. It's not a perfect fix -- some users can't get it to work -- but it'll do until Netflix officially brings its app to more Android phones.
The first thing you'll want to do is root your phone. You can look up instructions for specific devices at xda-developers, but keep in mind that rooting is not supported by warranty and could turn the phone into a paperweight.
Still with us? Now, follow the instructions, as posted on Reddit:
1) Download ES File Explorer (Or any other root file editor)
2) In ES File Explorer, go into Setting > Root Settings and enable both check boxes
3) Navigate to /system/ and copy/paste build.prop to /sdcard/ (just in case)
4) Open & edit /system/build.prop
5) Change the following lines to make your phone think it is an HTC G2:
--ro.product.model=HTC Vision
--ro.product.manufacturer=HTC
OR
--ro.product.model=Nexus S
--ro.product.manufacturer=samsung
6) Reboot the phone
7) Install the netflix apk (if you haven't already)
Enjoy
I haven't tried this myself, as my only Android device is a Droid Incredible, which doesn't require extra hoop-jumping. Obviously, you work around Netflix's obstacles at your own risk, but the ability to tinker is one of the reasons you got an Android phone in the first place, right?
Read more: http://techland.time.com/2011/05/13/...#ixzz1MHgvQ9x3
just tried it, phone goes into an infinite boot loop... :/
Those changes were.tried and it doesn't work.
Sent from my SGH-T959V using Tapatalk
sgyee said:
Those changes were.tried and it doesn't work.
Sent from my SGH-T959V using Tapatalk
Click to expand...
Click to collapse
Yep. These changes don't help on mt4g. I tested this yesterday
Sent from my HTC Glacier using XDA App
best app ever im waiting to find positive attitude so i can donwload to my phone and make it work nicee anyone know if its working good the netflix aps or it crashes?
I installed the hacked version that doesn't try to authenticate your phone and it lets me view and manipulate my queue, but when I try to stream, I get a blank white screen with nice clear audio. It seems there's a legitimate reason that Netflix is only releasing the app for certain phones. We may just have to wait on them to get it working for our hardware.
JaylanPHNX said:
I installed the hacked version that doesn't try to authenticate your phone and it lets me view and manipulate my queue, but when I try to stream, I get a blank white screen with nice clear audio. It seems there's a legitimate reason that Netflix is only releasing the app for certain phones. We may just have to wait on them to get it working for our hardware.
Click to expand...
Click to collapse
Netflix does work on our phones. There are Three ROMS out there that work perfectly. Sense 3.0, Cyanogen, one of the MiUi, and some of the TeamRoyal ROMs.
why wait when you can obtain now?
Can u share more I have cyonagen mod and haven't found a working version.
Sent from my HTC Glacier using XDA Premium App
neidlinger said:
Netflix does work on our phones. There are Three ROMS out there that work perfectly. Sense 3.0, Cyanogen, one of the MiUi, and some of the TeamRoyal ROMs.
why wait when you can obtain now?
Click to expand...
Click to collapse
it works on the faux123 AOSP rom flawlessly. i was able to finish patrice oneals special at work!
Sent from my rooted HTC Glacier, running faux123 1.2.0 AOSP 2.3.4 using XDA app
Have to use CM nightlies. Forget when they introduced it, but Cyanogen tweeted he had a fix a few days before the nightly was released.
I have to use the latest nightly and change the build.prop to HTC vision. Then I can download from the market and it works great.
Sent from my HTC Vision using XDA Premium App
I've tried this before and it doesn't work. This is the reason why I looked into rooting my device and ultimately flash it with teamroyal's ROM. Like neidlinger said, I got netflix working on my phone flawlessly!
i've tried all kinds of ROMs and netflix apps. none worked. until today! CM7 Nightly #100. then i had to install the 6.6.2011 updated netflix apk and boom, its working!!!!!!!!!!!!!!
interesting i just downloaded the apk off the internet and it seems to work fine so far, but i haven't used it that much either
slolifesux said:
i've tried all kinds of ROMs and netflix apps. none worked. until today! CM7 Nightly #100. then i had to install the 6.6.2011 updated netflix apk and boom, its working!!!!!!!!!!!!!!
Click to expand...
Click to collapse
I did that a week or two ago.
The Unlockr had the updated .apk posted.
First off, the new CM for the T-Mobile note 4 developed by Slayher is simply awesome. Lollipop, stable, good battery life, and wicked fast.
It does not run gear manager however so I found a decent workaround.
First, I used an S4 I have for a spare to run gear manager, and paired the watch to it. This phone has no Sim in it, so it's strictly to stay at my house on the Wi-Fi. I setup gmail, Viber, calendar, and a few other items I like to see on the watch.
I then was trying to figure out how to get SMS and call notifications from my note 4 when I remembered an excellent app: PushBullet.
For those who don't know, pushbullet accesses your notifications and pushes them across devices and chrome on your PC. Now, there is an experimental feature which syncs notifications across all devices! Once I set it all up, I added the notifications from pushbullet to gear manager and Voila- I can see SMS and incoming calls (although I cant answer). Not a bad compromise.
In essence, the only functionality that's missing is answering phone calls and replying to SMS.
Haa haa haa. . . bit like a car with the only functionality missing being the wheels and the engine!
esseff said:
Haa haa haa. . . bit like a car with the only functionality missing being the wheels and the engine!
Click to expand...
Click to collapse
seeing as i don't typically answer calls on my watch but do like to be notified of them, it's basically enough functionality that I don't miss TouchWiz too much.
pretty much the same with SMS... I don't typically answer from my watch but I like reading them. I didn't specify that I can forward calls to the watch if I want to leave the phone behind- it does have a SIM in it and it's own number.
Your opinion may vary from mine on what the core functionality of the Gear S would be, and that's alright. CM12 is just starting to become a great daily driver for the Note 4 and unless Samsung makes a GREAT lollipop ROM, I'm sticking with it for a while.
edouble312 said:
First off, the new CM for the T-Mobile note 4 developed by Slayher is simply awesome. Lollipop, stable, good battery life, and wicked fast.
It does not run gear manager however so I found a decent workaround.
First, I used an S4 I have for a spare to run gear manager, and paired the watch to it. This phone has no Sim in it, so it's strictly to stay at my house on the Wi-Fi. I setup gmail, Viber, calendar, and a few other items I like to see on the watch.
I then was trying to figure out how to get SMS and call notifications from my note 4 when I remembered an excellent app: PushBullet.
For those who don't know, pushbullet accesses your notifications and pushes them across devices and chrome on your PC. Now, there is an experimental feature which syncs notifications across all devices! Once I set it all up, I added the notifications from pushbullet to gear manager and Voila- I can see SMS and incoming calls (although I cant answer). Not a bad compromise.
In essence, the only functionality that's missing is answering phone calls and replying to SMS.
Click to expand...
Click to collapse
The note 4 on CM doesnt run gear manager? I just install DomPop's version of lollipop on my Tmobile note 3 and then the 11 apk's for gear manager, everything is running 100%.
cipherswitch said:
The note 4 on CM doesnt run gear manager? I just install DomPop's version of lollipop on my Tmobile note 3 and then the 11 apk's for gear manager, everything is running 100%.
Click to expand...
Click to collapse
yea the touchwiz lollipop ROMs like that one can run it no problem, but CM has something missing that's needed. HostManager FC's when pairing and nobody's gotten any further than that.
I see over in the International N4 forum that TW Lollipop leaked for the Chinese variant, so maybe it's getting closer.
That said, I'll still be torn between how amazingly well CM12 is running and reverting to TW. Getting gear manager back would be great though.
edouble312 said:
yea the touchwiz lollipop ROMs like that one can run it no problem, but CM has something missing that's needed. HostManager FC's when pairing and nobody's gotten any further than that.
I see over in the International N4 forum that TW Lollipop leaked for the Chinese variant, so maybe it's getting closer.
That said, I'll still be torn between how amazingly well CM12 is running and reverting to TW. Getting gear manager back would be great though.
Click to expand...
Click to collapse
that blows, I did have to mess around with a few versions of gear manager before it worked, feel free to download and try it out, unzip and install in order.
right from my mediafire ---> gear manager lollipop
cipherswitch said:
that blows, I did have to mess around with a few versions of gear manager before it worked, feel free to download and try it out, unzip and install in order.
right from my mediafire ---> gear manager lollipop
Click to expand...
Click to collapse
thanks. maybe i'll give it another whirl
quite a few people downloaded my gear manager package since yesterday, can anyone post any results?
No dice for me, a few apks wouldn't install.
cipherswitch said:
quite a few people downloaded my gear manager package since yesterday, can anyone post any results?
Click to expand...
Click to collapse
Still no luck getting gear manager functioning on CM rom.
edouble312 said:
First off, the new CM for the T-Mobile note 4 developed by Slayher is simply awesome. Lollipop, stable, good battery life, and wicked fast.
It does not run gear manager however so I found a decent workaround.
First, I used an S4 I have for a spare to run gear manager, and paired the watch to it. This phone has no Sim in it, so it's strictly to stay at my house on the Wi-Fi. I setup gmail, Viber, calendar, and a few other items I like to see on the watch.
I then was trying to figure out how to get SMS and call notifications from my note 4 when I remembered an excellent app: PushBullet.
For those who don't know, pushbullet accesses your notifications and pushes them across devices and chrome on your PC. Now, there is an experimental feature which syncs notifications across all devices! Once I set it all up, I added the notifications from pushbullet to gear manager and Voila- I can see SMS and incoming calls (although I cant answer). Not a bad compromise.
In essence, the only functionality that's missing is answering phone calls and replying to SMS.
Click to expand...
Click to collapse
How do you enable push bullet on the gear
If you want a toy, get an iPhone. If you want a Smartphone, get an Android
Jazznax said:
How do you enable push bullet on the gear
If you want a toy, get an iPhone. If you want a Smartphone, get an Android
Click to expand...
Click to collapse
Just add the notifications from pushbullet to the list of apps you get notifications from in Gear Manager settings.
edouble312 said:
Just add the notifications from pushbullet to the list of apps you get notifications from in Gear Manager settings.
Click to expand...
Click to collapse
So how do you get notifications from your note 4 on cm12
If you want a toy, get an iPhone. If you want a Smartphone, get an Android
Jazznax said:
So how do you get notifications from your note 4 on cm12
If you want a toy, get an iPhone. If you want a Smartphone, get an Android
Click to expand...
Click to collapse
Click the option on both the cm note 4 and the touchwiz device in pushbullet which syncs notifications across devices
edouble312 said:
Click the option on both the cm note 4 and the touchwiz device in pushbullet which syncs notifications across devices
Click to expand...
Click to collapse
So you need push bullet on the s4 and the note 4. Notifications go from the note 4 to the s4 to the gear. Correct?
If you want a toy, get an iPhone. If you want a Smartphone, get an Android
Jazznax said:
So you need push bullet on the s4 and the note 4. Notifications go from the note 4 to the s4 to the gear. Correct?
If you want a toy, get an iPhone. If you want a Smartphone, get an Android
Click to expand...
Click to collapse
Yea. not ideal but if you wanna test run Cm12 it's the only way to use the gear s for now.
I switched back to kitkat on my note 4.
edouble312 said:
Yea. not ideal but if you wanna test run Cm12 it's the only way to use the gear s for now.
I switched back to kitkat on my note 4.
Click to expand...
Click to collapse
Yeah I'll pass for now thanks anyway. I just can't carry around 2 phones
If you want a toy, get an iPhone. If you want a Smartphone, get an Android
Jazznax said:
Yeah I'll pass for now thanks anyway. I just can't carry around 2 phones
If you want a toy, get an iPhone. If you want a Smartphone, get an Android
Click to expand...
Click to collapse
I didn't carry 2 phones. I just left the s4 at home and used the Gear S via remote connection
edouble312 said:
I didn't carry 2 phones. I just left the s4 at home and used the Gear S via remote connection
Click to expand...
Click to collapse
If you leave your phone at home you can just use your carrier's call forwarding to forward calls to your watch. I have AT&T and I can just dial **21*Watch's Number# and it will forward calls to my watch. I don't like the auto call forward because it doesn't work sometimes.
Sent from my LG-V410 using XDA Free mobile app
I have searched and tried several things but I can not seem to fix a Google play issue I am having. After I updated to the Global Update 4.03.605.2 710RD, I have not been able to download certain apps from the Play Store. I get a message saying "This device is not compatible with this version". And these are simple apps like Dunkin Donuts and Starbucks (I like coffee... a lot). Here is what I have tried so far but to no avail:
1) Using Root Explorer, I edited the Build.prop file to change the resolution from 320 (which is a normal resolution but I gave it a shot anyway) to 240. Cleared out the PLay Store cache and restarted the phone. No luck.
2) Edited the build.prop file again to change the phone to a Nexus S and the manufacturer to Samsung. Cleared cache and rebooted. No luck.
3) Used Market Helper and tried several different options. No luck.
4) Used RootCloak. No luck.
Attached are screenshots of the specs for my phone, including the build.prop. Any suggestions?
Are you using a stock ROM with only root added? The official Global update is 4.05 (it's an OTA patch, not a full system update), maybe try to apply it and then try to check the Play Store again?
Try changing the dpi back to 320. Changing the dpi often "breaks" compatibility.
Are you S-OFF? I would follow the full downgrade/upgrade guide in this section and get it to an official version (4.5.605.14) or at least reflash the full RUU of the version you have... Once you get it up and running and signed into Google Play, give it some time for all the services to update (Play Store updates automatically after first opening/closing) and load something that forces Play Services to update like Hangouts. Then do a full update of all embedded apps and give it 10-15 minutes after that for all the Google services to update, restart and try download the Starbucks app (ONLY, no other apps).
acejavelin said:
Are you S-OFF? I would follow the full downgrade/upgrade guide in this section and get it to an official version (4.5.605.14) or at least reflash the full RUU of the version you have... Once you get it up and running and signed into Google Play, give it some time for all the services to update (Play Store updates automatically after first opening/closing) and load something that forces Play Services to update like Hangouts. Then do a full update of all embedded apps and give it 10-15 minutes after that for all the Google services to update, restart and try download the Starbucks app (ONLY, no other apps).
Click to expand...
Click to collapse
I have tried to fully downgrade and return to the fully updated stock. I am currently unlock with s-off. I still cannot download certain apps I had before, i.e Dunkin Donuts, Starbucks, Google Search. These apps are all compatible with my HTC Incredible. I can't figure out why my phone is all of a sudden not compatible. Does it matter that I'm unlocked?
sotssax said:
I have tried to fully downgrade and return to the fully updated stock. I am currently unlock with s-off. I still cannot download certain apps I had before, i.e Dunkin Donuts, Starbucks, Google Search. These apps are all compatible with my HTC Incredible. I can't figure out why my phone is all of a sudden not compatible. Does it matter that I'm unlocked?
Click to expand...
Click to collapse
No, it does not. Neither Google Play or the app knows your unlocked or S-Off.
So you are saying that completely stock, no custom ROM, changes to build.prop, or root, and these apps are still listed as incompatible?
Sent from my Nexus 4 using Tapatalk
acejavelin said:
No, it does not. Neither Google Play or the app knows your unlocked or S-Off.
So you are saying that completely stock, no custom ROM, changes to build.prop, or root, and these apps are still listed as incompatible?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Everything is stock except for the recovery. I am rooted. I followed the Downgrade and fully updated stock thread and used RUUs. I have been able to sideload the Dunkin Donuts app by downloading it from APK Downloader and it runs fine. For some reason I can't get the Starbucks app that way.
sotssax said:
Everything is stock except for the recovery. I am using CWM recovery. I followed the Downgrade and fully updated stock thread and used RUUs. I have been able to sideload the Dunkin Donuts app by downloading it from APK Downloader and it runs fine. For some reason I can't get the Starbucks app that way.
Click to expand...
Click to collapse
Really not sure what to say, recovery would not be relevant (although on a different note, TWRP is recommended over CWM)... Compatibility typically looks at setting from build.prop to verify model and relevant data like PPI and size of screen, and Play knows your OS version already.
Unfortunately I no longer own a Rezound so I can't confirm any of these issues.
Sent from my Nexus 4 using Tapatalk
Starbucks, at least, requires 4.1 or higher. That is stated in the description. This may be the limitation on the other app as well. Be sure to check that next time both were updated recently and probably had a feature added not compatible with 4.0 and lower.
Uzephi said:
Starbucks, at least, requires 4.1 or higher. That is stated in the description. This may be the limitation on the other app as well. Be sure to check that next time
Click to expand...
Click to collapse
This makes sense, check the basics first... But how did they work on an HTC Incredible? But which Incredible, the original, 2, or 4G? And stock or no?
Sent from my Nexus 4 using Tapatalk
acejavelin said:
This makes sense, check the basics first... But how did they work on an HTC Incredible? But which Incredible, the original, 2, or 4G? And stock or no?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Maybe an older version worked? Since M is around the corner, maybe ICS is just starting to get phased out on recently updated apps like GB was when LP launched.
Sent from my HTC6500LVW using XDA Free mobile app
Uzephi said:
Starbucks, at least, requires 4.1 or higher. That is stated in the description. This may be the limitation on the other app as well. Be sure to check that next time both were updated recently and probably had a feature added not compatible with 4.0 and lower.
Click to expand...
Click to collapse
Thanks for figuring this out. Is there a way to trick it to think I have 4.1? Maybe change a line or two in the build.prop then change it back after downloading?
acejavelin said:
This makes sense, check the basics first... But how did they work on an HTC Incredible? But which Incredible, the original, 2, or 4G? And stock or no?
Click to expand...
Click to collapse
I had an older version of the app on my phone before I started to update. I should have backed up the APK before I wiped the phone.
sotssax said:
Thanks for figuring this out. Is there a way to trick it to think I have 4.1? Maybe change a line or two in the build.prop then change it back after downloading?
I had an older version of the app on my phone before I started to update. I should have backed up the APK before I wiped the phone.
Click to expand...
Click to collapse
I think your missing the point... If it requires Android 4.1 or higher, they are using certain APIs or something else in the OS that didn't exist in previous versions, there is a reason its marked as incompatible. You are better off to look at one of the APK repository sites and grab an old version of the app.
Don't mess in build.prop unless you really know what you are doing.
Sent from my Nexus 4 using Tapatalk
sotssax said:
Thanks for figuring this out. Is there a way to trick it to think I have 4.1? Maybe change a line or two in the build.prop then change it back after downloading?
I had an older version of the app on my phone before I started to update. I should have backed up the APK before I wiped the phone.
Click to expand...
Click to collapse
Your best bet would be to flash a JB rom. Most of the 4.1 and 4.2 ones work fine with no issues on this phone.
I first got this app for my FireTV and loved it. Developer now created an android tv version compatible with nexus player.
It allows you to use your stock remote as a mouse. Root is required on the nexus player.
No brainer for $0.99 as it eliminates the need for a separate bluetooth mouse or trackpad.
IMPORTANT FYI: The mouse function works WITHIN apps but not on the home screen!
Link and author's description:
Mouse Toggle [ROOT]
https://play.google.com/store/apps/details?id=com.fluxii.android.mousetoggleforandroidtv#hw-item-401
Add a mouse mode to the stock remote control or gamepad for Android TV.
NOTE: ROOT access is REQUIRED for this app to function.
Features:
Works just like a regular mouse that can click, long click, wheel up, wheel down, and drag.
Simple to toggle between regular remote and mouse modes.
Requirements:
1.) Android TV device(see below for supported devices).
2.) Stock / original remote control or game controller.
This actually work surprisingly well and includes an leanback icon, although I kind of wish we could hide things like this from the lean back launcher itself...
n1gh7mar3 said:
This actually work surprisingly well and includes an leanback icon, although I kind of wish we could hide things like this from the lean back launcher itself...
Click to expand...
Click to collapse
I agree with you on the leanback launcher icon. I know there needs to be a way to launch the app, but I hate scrolling through the list of apps when I know I won't be starting it up all the time.
Just tried the app. No go on Android TV 6.0. It kept on saying starting but sat there. Ended up asking for a refund. May try it again later when bugs are worked out.
Sounds cool but I will stick to my Logitech K400 Plus. I'm in and out of chrome on my nexus player anyways. However, this would have been helpful for me with HBO Go when it had to be sideloaded. Now it is available on the app store though so remote works great.
xaudiblex said:
Just tried the app. No go on Android TV 6.0. It kept on saying starting but sat there. Ended up asking for a refund. May try it again later when bugs are worked out.
Click to expand...
Click to collapse
Which method did you use to root your Nexus Player? I have restored the device via the factory images(https://developers.google.com/android/nexus/images?hl=en#fugu) and have used both methods(post #1 & #2) in the following link: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
I flashed the factory images before each attempt to root and tried each method a couple of times. The app worked great during all 4 tests so hopefully we can discover what is different with your setup.
Thank you
Bought this for my fire tv and it was probably the most useful app ive ever bought for the price. On NP Im really just playing around trying to find a good use for the device. Right now im using android M rom (no leanback UI) and stock remote is useless. DOES this app work with the custom roms?
KLit75 said:
Bought this for my fire tv and it was probably the most useful app ive ever bought for the price. On NP Im really just playing around trying to find a good use for the device. Right now im using android M rom (no leanback UI) and stock remote is useless. DOES this app work with the custom roms?
Click to expand...
Click to collapse
I would like to know this as well as I am running Full Android 6.0. Looks interesting as I am sick of using a mouse and keyboard on my couch lol.
treezy26 said:
I would like to know this as well as I am running Full Android 6.0. Looks interesting as I am sick of using a mouse and keyboard on my couch lol.
Click to expand...
Click to collapse
Still waiting... I finally broke down and forked over the cash for droidmote. Its a good app but doesnt replace a physical remote imho. You want to be able to just feel for the buttons when your watching tv. A phone or tablet isnt the same. Good rom. Itd be great if the remote worked.
KLit75 said:
Still waiting... I finally broke down and forked over the cash for droidmote. Its a good app but doesnt replace a physical remote imho. You want to be able to just feel for the buttons when your watching tv. A phone or tablet isnt the same. Good rom. Itd be great if the remote worked.
Click to expand...
Click to collapse
Well I went ahead and did the same thing to only find out I cant even download it because it doesnt show up in the play store for me. But I am running a custom rom and that might be the issue. I've emailed the dev but still waiting on a reply.
treezy26 said:
Well I went ahead and did the same thing to only find out I cant even download it because it doesnt show up in the play store for me. But I am running a custom rom and that might be the issue. I've emailed the dev but still waiting on a reply.
Click to expand...
Click to collapse
Good. Could you please post back here when you get a response? Thanks.
KLit75 said:
DOES this app work with the custom roms?
Click to expand...
Click to collapse
The latest update(v1.03) that was just submitted today will work with custom ROM's(non-Leanback Launcher).
Thank you
iostouchdev said:
The latest update(v1.03) that was just submitted today will work with custom ROM's(non-Leanback Launcher).
Thank you
Click to expand...
Click to collapse
Purchased it but doesnt seem to work on marshmallow 6.0 rom. Double tap play/pause but no cursor. I have droidmote installed. Not sure if theres a conflict?
KLit75 said:
Purchased it but doesnt seem to work on marshmallow 6.0 rom. Double tap play/pause but no cursor. I have droidmote installed. Not sure if theres a conflict?
Click to expand...
Click to collapse
Shouldn't be any conflict. The double tap of the play / pause button does have to be pretty quick(~400ms).
I would recommend opening the app and then toggling the enable switch off and then on to see if that helps. Did the SuperSU app prompt you for permission initially?
iostouchdev said:
Shouldn't be any conflict. The double tap of the play / pause button does have to be pretty quick(~400ms).
I would recommend opening the app and then toggling the enable switch off and then on to see if that helps. Did the SuperSU app prompt you for permission initially?
Click to expand...
Click to collapse
I did. And just took your advice and toggled on/off. Also rebooted just to see. But its working for you on 6.0? Thats strange. I just get normal remote functionality. Tried it in netflix where its needed but no cursor appears. I do have wifi keyboard attached. Would that cause issues? Doubt it since i quit droidmote and turn off keyboard. Ill keep trouble shooting but never had any issues with your app on aftv (also with wifi keyboard so yea thats not a factor)
KLit75 said:
I did. And just took your advice and toggled on/off. Also rebooted just to see. But its working for you on 6.0? Thats strange. I just get normal remote functionality. Tried it in netflix where its needed but no cursor appears. I do have wifi keyboard attached. Would that cause issues? Doubt it since i quit droidmote and turn off keyboard. Ill keep trouble shooting but never had any issues with your app on aftv (also with wifi keyboard so yea thats not a factor)
Click to expand...
Click to collapse
Other devices won't cause any conflicts so you are ok there. Just to confirm a couple of items: The Nexus Player is rooted? Was the app granted root access and is it listed in the SuperSU app?
If you want to email me that may be easier.
Thanks again for your patience.
iostouchdev said:
Other devices won't cause any conflicts so you are ok there. Just to confirm a couple of items: The Nexus Player is rooted? Was the app granted root access and is it listed in the SuperSU app?
If you want to email me that may be easier.
Thanks again for your patience.
Click to expand...
Click to collapse
Im not overly concerned. Feel like a got more than my moneys worth with aftv app. Yes. All of the above. Should be working. Ill email you when i get more time to play around with it. Thanks.
KLit75 said:
Im not overly concerned. Feel like a got more than my moneys worth with aftv app. Yes. All of the above. Should be working. Ill email you when i get more time to play around with it. Thanks.
Click to expand...
Click to collapse
I just heard from another user that had the same issue. Apparently the Nexus Player remote was somehow displayed as 'Spike' instead of 'Nexus Remote' in the Bluetooth paired device settings. They were able to resolve the issue by un-pairing the remote and pairing it again which correctly identified the remote as 'Nexus Remote'.
Any chance your remote is also named 'Spike'?
iostouchdev said:
I just heard from another user that had the same issue. Apparently the Nexus Player remote was somehow displayed as 'Spike' instead of 'Nexus Remote' in the Bluetooth paired device settings. They were able to resolve the issue by un-pairing the remote and pairing it again which correctly identified the remote as 'Nexus Remote'.
Any chance your remote is also named 'Spike'?
Click to expand...
Click to collapse
I pm you but just so others no... Yes. That was the issue. Unpair then repair and nexus remote appears (took me 3 times) but it finally appeared. Thanks.
@iostouchdev this application is a total game changer for the Nexus Player. THANK YOU!!!!!!!!!!
@iostouchdev best dollar i've ever spent thank you
Is there any way to install samsung gear manager on my motorola nexus 6 running android Marshmallow?, I want to use notifications, etc.
In advance, thanks!!!!!!
Search the other "non-Samsung device" thread, there's an .apk file for it. However, after installing the app, you will not be able to find your Gear S. The Gear S (at least for me) isn't working with devices running Marshmallow.
ycats said:
Search the other "non-Samsung device" thread, there's an .apk file for it. However, after installing the app, you will not be able to find your Gear S. The Gear S (at least for me) isn't working with devices running Marshmallow.
Click to expand...
Click to collapse
Just installed, but no success........
The Saint Hyoga said:
Just installed, but no success........
Click to expand...
Click to collapse
We need to wait for samsung to have 6.0 on their devices, after this hopefully we can pair them
Herp94 said:
We need to wait for samsung to have 6.0 on their devices, after this hopefully we can pair them
Click to expand...
Click to collapse
Hopefully that will be soon. They keep teasing a 6.0 release for Galaxy s6 and s6 edge, but still no definite release date
So i purchased a Galaxy Gear S for 100$ and i have a Nexus 6. I see the APP store has Galaxy Gear Manager and i installed it im using CM 13 Snapshot (Android 6.0.1) but the manager is still not detecting my watch.
I found out how to bypass the initial setup (tapping on the watch icon) and connecting via bluetooth however the functions seem limited. Currently the only thing i can do is use it to make bluetooth calls.
As it stands its just a fancy normal watch with some fitbit functionality and thats it. even the cheap 5$ watch from ebay let me play music and get notifications on it.