Apologies if I'm in the wrong forum, this is my first post here
I've heard about a hardware sensor in the Nexus 5 onwards which enhances step counting and step detection - has anyone ever heard whether this is likely to be copied by other manufacturers and likely to feature in future iPhones or Galaxies?
It seems to be getting a lot of attention and I wonder why LG's rivals aren't already working on incorporating this sensor into their own phones
thanks for all answers
some fitness or running applications has a step counter that work with accelerometer
you can check for them if your phone didn't have a full pedometer sensor built-in :good:
thanks but I know that phones have accelerometers - I'm trying to find out if more phones are likely to get step counter sensors build in, as the Nexus 5 currently has
thepom said:
Apologies if I'm in the wrong forum, this is my first post here
I've heard about a hardware sensor in the Nexus 5 onwards which enhances step counting and step detection - has anyone ever heard whether this is likely to be copied by other manufacturers and likely to feature in future iPhones or Galaxies?
It seems to be getting a lot of attention and I wonder why LG's rivals aren't already working on incorporating this sensor into their own phones
thanks for all answers
Click to expand...
Click to collapse
I'm pretty sure the S5 has a pedometer
Sent from my GT-I8190 using Tapatalk
Related
It seems like Near Field Communications (NFC) is going to be the next big sensor for portable devices. Is there any way to retrofit NFC to a device or does it need to to be on-board (literally).
It requires hardware we don't have.
This doesn't belong in accessories , please post questions in Q & A from now on.
gdbassett said:
It seems like Near Field Communications (NFC) is going to be the next big sensor for portable devices. Is there any way to retrofit NFC to a device or does it need to to be on-board (literally).
Click to expand...
Click to collapse
Yup.
TYFONE PUTTING NFC IN MICROSD CARDS
jasonsf said:
Yup.
TYFONE PUTTING NFC IN MICROSD CARDS
Click to expand...
Click to collapse
Except for the minor detail of them not being available (yet).
063_XOBX said:
Except for the minor detail of them not being available (yet).
Click to expand...
Click to collapse
He didn't ask if there was a way to do it TODAY
Good to see there will be an accessory to bring this capability to our phones, even if it is in the future. (I don't live in salt lake city so no NFC here yet anyway.)
Sent from my SPH-D700 using XDA App
Personally I think this is a bad technological improvement as it just opens up more access to our personal data for a minimal increase in the ease of our daily lives.
My plastic RFID-free credit card suits me just fine.
063_XOBX said:
Except for the minor detail of them not being available (yet).
Click to expand...
Click to collapse
This is a development forum, 90% of anything discussed here isn't available yet.
As I understand it NFC will be supported natively in Gingerbread, which is in the works for the Epic right now. As far as the hardware goes, there are cradles or adapters available for some phones right now to support NFC. Since Sprint announced recently they will be making a big push this year for NFC, I would expect they would release an NFC adapter for many of their phones.
Yeah........ I do live in SLC... and I'm not looking forward to NFC.
Anything that increases the ease of transferring sensitive personal information or money to random people worries me.
Look at all the security holes RFID has.
I can't see this taking off for at least another year and by then I hope to be looking at what new phones are available. Bought a G1 on launch and I've learned my lesson in early adopting.
Sent from my SPH-D700 using XDA App
Have we been able to port the GS2's 2point zoom feature on the browser and gallery to our captivates?
This is what I'm talking about
http://www.youtube.com/watch?v=3J2yRvTcZMY
I don't think it's possible. The Captivate, Vibrant, or the Galaxy S line in general doesn't have a gyro. And the gyro is needed to make that feature work. Which means it will never work with these phones.
Sent from my HTC Glacier using XDA App
Ah le sigh. Your absolutely right, for some reason I just assumed we did have gyroscope without checking on it. Though our accelerometer would definitely be able to do it. Only thing that would be stopping us is that the tilt direction may not be the sensing direction of the accelerometer.
But then I would assume changing that function from the gyroscope to the accelerometer would take a good deal more work.
idk....yall r the experts
Nevermind - just saw the previous post.
So curious to know if this phone will be like all the new top tier phone and offer IR transmitter so we can control TV's and other devices from it?
anyone has any clues?
Aydthird said:
So curious to know if this phone will be like all the new top tier phone and offer IR transmitter so we can control TV's and other devices from it?
anyone has any clues?
Click to expand...
Click to collapse
Only speculation. The FCC photo shows a strange cut-out/window in the upper back middle, which led to the speculation, but the recent Service Manual leak had no mention of this hardware and capability.
wideasleep1 said:
Only speculation. The FCC photo shows a strange cut-out/window in the upper back middle, which led to the speculation, but the recent Service Manual leak had no mention of this hardware and capability.
Click to expand...
Click to collapse
I had been waiting, I know the LG G2 and original G had them, and Kit Kat is said to improve IR remote control yet they didn't implement it on their new device... Weird
Aydthird said:
I had been waiting, I know the LG G2 and original G had them, and Kit Kat is said to improve IR remote control yet they didn't implement it on their new device... Weird
Click to expand...
Click to collapse
It's not that Kit-Kat improved it, they added initial support. Prior to 4.4, all IR phones had proprietary interfaces that were not inter-operable.
Considering these phones are in development for over a year prior to release, IR wasn't even on the table for Google when the HTC One and Galaxy S4 were released. Adding it at that point would have been a dramatic setback on the release, and mostly a pointless one. There's no apps out right now that would even support it (as they all are designed to run on the proprietary IR emitters, not KitKat's).
I picked up a Smartwatch 2 for $60 two days ago at a closing Sony store. I've built AOSP before for my GNexus but that's the extent of my Android dev experience. So with the announcement of Android Wear today and the info from the Open Smartwatch Project I feel life may be telling me to put on the developer hat for real this time and test the waters surrounding porting Android Wear to the SW2. I can't say I'll be successful since I'm obviously in way over my head but sometimes jumping in the deep end is the best way to learn. Any advice or opinions you guys can give me would be much appreciated!
Sounds like a really good idea
Sent from my C6903 using Tapatalk
All our support for you
Enviado desde mi Galaxy Nexus mediante Tapatalk
Good luck. Would be interested in testing what you come up with.
Sent from my GT-I9300 using Tapatalk
Ready for testing It would be great.
Same here. I would love to try some new things on my SW2.
Sent from my C6903 using Tapatalk
SW2 is NOT running android
you probably won't be able to come up with something, sorry
greetings
MJFox
MJFox78 said:
SW2 is NOT running android
you probably won't be able to come up with something, sorry
greetings
MJFox
Click to expand...
Click to collapse
I was thinking the same thing but that's not to say it's not impossible.
Best of luck to you OP.
Not to mention there is no microphone
MJFox78 said:
SW2 is NOT running android
you probably won't be able to come up with something, sorry
greetings
MJFox
Click to expand...
Click to collapse
Thanks, I actually know that it runs microC/OS-II. The chip however is an ARM Cortex M3 which has already had Linux ported to it. I'm also waiting for an Android Wear release because I imagine a lot of these wearables are going to be using these low power ARMs and should provide a platform to start working from. Sony's Bluetooth chip is actually my biggest concern since there's very little documentation for it. Like I said, I'm not sure I'm going to be successful, just going to try.
Please keep up the criticism! Anyone bringing up topics I may not have considered could be helping me find more information!
cabal51 said:
Thanks, I actually know that it runs microC/OS-II. The chip however is an ARM Cortex M3 which has already had Linux ported to it. I'm also waiting for an Android Wear release because I imagine a lot of these wearables are going to be using these low power ARMs and should provide a platform to start working from. Sony's Bluetooth chip is actually my biggest concern since there's very little documentation for it. Like I said, I'm not sure I'm going to be successful, just going to try.
Please keep up the criticism! Anyone bringing up topics I may not have considered could be helping me find more information!
Click to expand...
Click to collapse
Here is pretty much the only documentation I could find about the SW2's hardware. It does indeed run some form of uC-OS/II on an ARM Cortex-M4 (STM32F4-series system-on-chip), but it's only got 256 KiBs of RAM - if you're skilled and resourceful enough, you might be able to get a uclinux build to run on it (there is one for ST's STM32F4-based Discovery board), but any form of Android is out of the question.
Of course, if you've got the skills, making any sort of third-party code run on the thing would be godly.
Would love to see it running! Here for testing too!
Good luck
Sent from my One using xda app-developers app
I was really disappointed when i saw Android Wear But then i just realized that our sw2 is way more useful becouse of all its apps (torch, calendar, calc etc) and also for the necessity of Android Wear to use the mic all the time... Just my two cents
Inviato dal mio Galaxy Nexus utilizzando Tapatalk
-=W1S3=- said:
I was really disappointed when i saw Android Wear But then i just realized that our sw2 is way more useful becouse of all its apps (torch, calendar, calc etc) and also for the necessity of Android Wear to use the mic all the time... Just my two cents
Inviato dal mio Galaxy Nexus utilizzando Tapatalk
Click to expand...
Click to collapse
I think that the screen transrefelctive is the best solution for a smartwatch, I selected SW2 for 3 reasons : Screen visible in all conditions (other watch are not visibile so good under the sun light), battery life and waterproof...
Android Wear in my opinion will use more battery, will use lcd or oled screen... 2 reasons to prefer SW2 at the moment...
magicdark said:
I think that the screen transrefelctive is the best solution for a smartwatch, I selected SW2 for 3 reasons : Screen visible in all conditions (other watch are not visibile so good under the sun light), battery life and waterproof...
Android Wear in my opinion will use more battery, will use lcd or oled screen... 2 reasons to prefer SW2 at the moment...
Click to expand...
Click to collapse
I'm with you guys, I think I will be happier with the SW2 than the first generation of Android Wear. I expect that will change over time though.
Aside from the voice thing (which is socially awkward) the sw2 would be capable of showing Now cards if there was an api for it. That's all Android wear does at the moment.
Sent from my LT30p using Tapatalk
how is this going? even after update i still wanna try this out
up ?
Here for testing as well!
I would love to just be able to flick through notifications and Google Now cards, don't really care about the whole "no microphone" thing. If I need to talk to Google, I'll be on my phone or Google Glass.
according to
www.clove.co.uk/download.aspx?download=ee0fdaa0-7b8f-47f7-941f-c9baceaf853e
it is a STM32F429
a few other threads about 'open smartwatch' and firmware mods/hacking. there's arduino for the 1st smartwatch
STM32F4 code compiles if you drop it in and make minor changes
https://github.com/underverk/SmartWatch_Toolchain
if sony had a
http://developer.sonymobile.com/services/open-smartwatch-project/smartwatch-hacker-guide/
page like this for SW2 - i think we'd be all good
Hi
My current device is the Galaxy S3 i9300. I have found that the android development section for the s3 is plagued with limitations due to the manufactures (Samsung & other parties) holding back the sources. This results in lag, glitches etc ...stuff not working as good as it could.
My question is : does the Nexus 5 face the same limitations as the s3 due to google or lg holding sources back, causing things not to be working in custom roms?
I like what I see with the Nexus 5 but I want to be sure that I'm not falling into the same trap again before I buy one
Thanks in advance
You will not see the same limitations you see with the s3 on the n5. Almost everything is open source and you won't see locked bootloader, a bunch of carrier crap, etc
Sent from my Nexus 5
steve.p.russell said:
Hi
My current device is the Galaxy S3 i9300. I have found that the android development section for the s3 is plagued with limitations due to the manufactures (Samsung & other parties) holding back the sources. This results in lag, glitches etc ...stuff not working as good as it could.
My question is : does the Nexus 5 face the same limitations as the s3 due to google or lg holding sources back, causing things not to be working in custom roms?
I like what I see with the Nexus 5 but I want to be sure that I'm not falling into the same trap again before I buy one
Thanks in advance
Click to expand...
Click to collapse
Nexus`s are build to be customised, you won`t find KNOX or bootloader unlockcode.bin`s (both will void warranty when triggered) here. Happy flashing mate Read the first 4 threads in the General Section well before you do anything . And don`t use tookits.
You obviously have never owned a Nexus. The Nexus isn't locked down like Samsung, HTC, etc. There are no hurdles to jump over when unlocking or modifying. Google makes there phones this way on purpose. That is why nexus phones are the best for ROMs and other modifications. Get a Nexus 5 and you will see how easy it is.
Nexus phone are developer phones. They're created to be modified, tampered, and messed with. You won't find any limits here, so go mental ?.
Sent from my Nexus 5 using xda app-developers app
WI FI Direct
But wi fi direct does not work which is really annoying wish i had knew that before i bought my N5 last week i would have gone for the LG G2 which to tell the truth i think is better.:cyclops:
chainsuk said:
But wi fi direct does not work which is really annoying wish i had knew that before i bought my N5 last week i would have gone for the LG G2 which to tell the truth i think is better.:cyclops:
Click to expand...
Click to collapse
I'm the opposite of you. I have the G2 but feel like I want a 5.
Sent from my LG-D800
As i say though wi fi direct does not work yet which is annoying im just hoping they fix it soon as its software problem not hardware,apart from that its a nice phone
With a Nexus you can go as far as the mind can see... or as far as its fans want it to go.
Samsung don't release Exynos source. Actually Qualcomm also don't release snapdragon source either.
However, difference being, google releases full AOSP source code for Nexus 5 where as Samsumg does not, so unlike my old GT-i9300, Camera can still work, audio can still work as well as it would on stock. Samsung only release blobs and no HAL so that's why it suffers,
There will always be limitations developing new features on qualcomm devices, BUT existing features on N5 can work as well as stock. No hardware in the android world is truly / fully open source because of the proprietary nature of SoCs, but as long as the AOSP repository includes everythign we need to run that hardware, it's not so much a big deal.