Related
Hi All,
has anyone been able to test the NFC scanner since update 2.3.3? i have a few RFID chips laying around and they done seem to want to scan..
Possibly in wrong forum...
have you tried searching the market for "nfc"
Yes and still doesn't scan..
Sent from my Nexus S using XDA App
Elvoski said:
Yes and still doesn't scan..
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Have you enabled NFC in the Settings?
Elvoski said:
Hi All,
has anyone been able to test the NFC scanner since update 2.3.3? i have a few RFID chips laying around and they done seem to want to scan..
Click to expand...
Click to collapse
Do you know what kind of technology those RFID chips use? They have to be the of the correct technology for them to work.
Nfc is activated in settings. I'm pretty sure they are the right tech.. ill havs to find some more
Sent from my Nexus S using XDA App
Make sure your tags are 15.36MHz type and not the oh-so-very-common 125KHz ones. The NFC only works with 15.36MHz tags. If you are not sure of what you have, you probably have the 125KHz ones (very common for access control etc).
dnts said:
Make sure your tags are 15.36MHz type and not the oh-so-very-common 125KHz ones. The NFC only works with 15.36MHz tags. If you are not sure of what you have, you probably have the 125KHz ones (very common for access control etc).
Click to expand...
Click to collapse
Nexus S can't read 125Khz ? (disappointment)
The long awaited upgrade is here but with it come some bugs. I didn't try out the SOAK as it was too much hassle for me, but some reported bugs there already...and since Motorola didn't really care about these minor bugs, we have to live with them now in the final release.
Here is my idea: let's collect the bugs we experience and let's find solutions for it.
The most annoying thing I encouter is the always shown 3G symbol, even when I have no or jost slow network. Does someone know how to fix this?
Sent from my XT897 using xda app-developers app
Jelly bean works great for me, very fast and smooth.
I don't know about the 3g symbol, but if stays on 3g I like it, lol
Sent from my XT897 using Tapatalk 2
I'm not sure that I've seen 1x yet, but otherwise my 3G indicator seems to work fine. It switches to 4G when applicable, and goes away entirely if I have no signal or enter a voice-only roaming area. Signal strength bars work properly too.
EDIT: I started with a clean install of the most recent 4.0.4 release and immediately upgraded to the JB soak with the OTA that was posted here. Maybe you've got something from a previous install that's borked the network indicator.
BAMF said:
I'm not sure that I've seen 1x yet, but otherwise my 3G indicator seems to work fine. It switches to 4G when applicable, and goes away entirely if I have no signal or enter a voice-only roaming area. Signal strength bars work properly too.
EDIT: I started with a clean install of the most recent 4.0.4 release and immediately upgraded to the JB soak with the OTA that was posted here. Maybe you've got something from a previous install that's borked the network indicator.
Click to expand...
Click to collapse
That means you are on CDMA/LTE networks? I performed the SIM Mod, maybe just GSM is messed up...? I read in another thread that someone had the same issue during the SOAK.
I wonder if a hard reset would fix the issue, but I am too lazy to try out...But the symbol is a bit annoying when I _know_ that there is no signal...
Sent from my XT897 using xda app-developers app
oTToToTenTanz said:
That means you are on CDMA/LTE networks? I performed the SIM Mod, maybe just GSM is messed up...? I read in another thread that someone had the same issue during the SOAK.
I wonder if a hard reset would fix the issue, but I am too lazy to try out...But the symbol is a bit annoying when I _know_ that there is no signal...
Sent from my XT897 using xda app-developers app
Click to expand...
Click to collapse
Oh yes, I missed that you are on GSM. I am indeed running on CDMA, unfortunately I don't have any experience with the GSM service on this phone.
I don't have any probs like that in CM10.1, using the radio proprietaries / firmware from stock JB. So it's somewhere inside Moto's Android code.
CDMA 1XA was added to the 3G standard awhile back so technically the 3G symbol is correct.
oTToToTenTanz said:
Here is my idea: let's collect the bugs we experience and let's find solutions for it.
Sent from my XT897 using xda app-developers app
Click to expand...
Click to collapse
- USB OTG for flash disk not working
- sometimes shift key need to be hold when typing on some form
anyone having same issue?
pb908 said:
- USB OTG for flash disk not working
- sometimes shift key need to be hold when typing on some form
anyone having same issue?
Click to expand...
Click to collapse
I have had the shift key issue with different apps and it seems to be app dependent, the two I notice most are irissi connect not and pro board app.
Sent from my XT897 using xda premium
Lapdock 500
Just another noted JB bug
REMOVES ALL LAPDOCK FUNCTIONALITY
Reverted back to ICS Using RSD lite 6.1.5
to get around errors for:
Security
gpt_main0.bin
etc
remove lines with:
getvar
md5
OEM
Back to ICS and happy to be there
Hinyo said:
Just another noted JB bug
REMOVES ALL LAPDOCK FUNCTIONALITY
Click to expand...
Click to collapse
What lapdock functionality do you have in ICS? I thought all it did was HDMI mirroring and USB keyboard? I would think HDMI wouldn't distinguish between a lapdock monitor and a TV, is it just the USB OTG issue causing the keyboard not to work?
This jellybean fix also lowers the ring volume.....and notification volume....does anyone know how to bring back the volume to its normal state...
BAMF said:
What lapdock functionality do you have in ICS? I thought all it did was HDMI mirroring and USB keyboard? I would think HDMI wouldn't distinguish between a lapdock monitor and a TV, is it just the USB OTG issue causing the keyboard not to work?
Click to expand...
Click to collapse
NO more HDMI mirroring at all. and limited USB functionality.
I used to use it along with the Linux chroot method as a "laptop" while im waiting for a true dual boot to be ported for android so I reverted back to ICS.
---------- Post added at 08:56 AM ---------- Previous post was at 08:48 AM ----------
kreizyidiot said:
This jellybean fix also lowers the ring volume.....and notification volume....does anyone know how to bring back the volume to its normal state...
Click to expand...
Click to collapse
Check My previous post in this thread.
But you need to use Skill_Cz's FXZ files along with RSD lite to revert back and make sure to remove the three lines in my post which i cant edit to be more specific if you like
Use the Latest 6.1.5 version of RSD lite to do so
The brightness slider keeps randomly reverting back to the lowest setting in the JB build also.
While I can't say that I make use of the HDMI, that is pretty awful that they straight up removed a feature. Have we not yet reached the point that HDMI support is native to Android?
kreizyidiot said:
This jellybean fix also lowers the ring volume.....and notification volume....does anyone know how to bring back the volume to its normal state...
Click to expand...
Click to collapse
Also have issues with this. And I am having issues with not being notified at all. On Vibrate, messages don't vibrate. I can select 'Vibrate on notification' and it wil work, but also vibrates when volume is up which I do not want. When the volume is up all the way, notification is barely audible. Voicecall notifications/ringtones work fine.
But it's also weird because sometimes it works fine. Trying to figure it out.
Otherwise I'm ok with JB. It's running decently and Smartactions are actually triggering by location now hehe.
BAMF said:
While I can't say that I make use of the HDMI, that is pretty awful that they straight up removed a feature. Have we not yet reached the point that HDMI support is native to Android?
Click to expand...
Click to collapse
HDMI still works. I have a dock I use to watch movies on my home theater with, and it still works. I believe the poster was reporting that Lapdock doesn't work anymore, not HDMI.
My new problem: app2sd doesn't work, the new version of android doesn't appear to support it manually, and I'm out of space on internal storage. Seriously, do they not have regression tests?
Mirroring on the lapdock
GDorn said:
HDMI still works. I have a dock I use to watch movies on my home theater with, and it still works. I believe the poster was reporting that Lapdock doesn't work anymore, not HDMI.
Click to expand...
Click to collapse
JB. On my lapdock image is flattened, not on the entire screen, black lines on top and bottom. In ICS I not have this problem.
I'm running stock Android 4.1.2 on an international version GT-P6800 (purchased in Thailand).
I've been subscribed to a magazine for months now. But with today's replacement (Play Magazines => Play Newsstand), the Google Play Newsstand app crashes immediately on launch. Same story for the updated version of Google Now (released over the past week).
Due to increased sluggishness of my tablet, I decided to backup data and do a factory reset. So all these problems are occurring on a "fresh" OS install. (So no significant app caches, etc.)
Newsstand and Google Now/Search are both working fine on my ASUS tablet, so these problems are definitely specific to this hardware/OS version.
Is anyone else having either or both problems? Ideas?
P.S. This is really making me more inclined to finally root my tablet and install the most stable custom ROM available.
Just tried Newsstand an I too am having issues, also been having issues with Google Now . I started a thread regarding that issue as well. Really getting frustrated
Sent from my GT-P6800 using XDA Premium 4 mobile app
adinis78 said:
Just tried Newsstand an I too am having issues, also been having issues with Google Now . I started a thread regarding that issue as well. Really getting frustrated
Sent from my GT-P6800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I am having the same issue on my tab 7.7 4.1 also.
hmm..
so far have no idea how to fix it ...
one more
+1, senda report to Google, maybe help
****mesta said:
+1, senda report to Google, maybe help
Click to expand...
Click to collapse
The problem is almost certainly caused by Samsung modifications to Jelly Bean. My other Android devices don't have any such problems.
I posted a message about my solution in another thread:
http://forum.xda-developers.com/showthread.php?t=2529929
Finally found easy fix!
Uninstall the update & revert back to factory app. Stupid updates just screw everything up! It was ridiculous!
What I don't understand is that my wife's Note I I was able to update both apps with no issues, her phone is running JB 4.1.2
Sent from my GT-P6800 using XDA Premium 4 mobile app
Were is the widget? This seems to be a flipboard take over so google needs widget.
I know I'm not the only one with this issue, anybody have an any ideas as to why Google search no longer works, even after new updates. On My wife's Note II she gets all the updates with no issue, she is also running 4.1.2. This is really pissing me off.
Sent from my GT-P6800 using XDA Premium 4 mobile app
It's happend to my tab 7.7 also..
Google Search And Newstand just crash when ever i lunch it
hopefully can get the fix soon ..
lnxcat said:
It's happend to my tab 7.7 also..
Google Search And Newstand just crash when ever i lunch it
hopefully can get the fix soon ..
Click to expand...
Click to collapse
It's been about 4 updates since problem started, I don't think Google is aware of it otherwise it would have been solved
Sent from my GT-P6800 using XDA Premium 4 mobile app
Another update released today and still same issue, what seems to be the problem?
Sent from my GT-P6800 using XDA Premium 4 mobile app
The power to solve the problem is available. But you'd rather complain.
adinis78 said:
Another update released today and still same issue, what seems to be the problem?
Click to expand...
Click to collapse
The problem is almost certainly Samsung 's work in modifying Android for our tablet model. There are no widespread complaints for other Android devices. And as I said when you started this thread: once I rooted the tablet and flashed Cyanogenmod, the problem became a far-off memory. That's the beauty of the Android community. My tablet can do more things now. And I don't have to think about whether Samsung cares about me.
What did I learn?That if I wanted a 7"tablet today, I would get the Nexus 7. I got a Nexus 4 phone when Google dropped the price. I rooted it in 15 minutes. And Kit Kat is available for it already.
goattee said:
The problem is almost certainly Samsung 's work in modifying Android for our tablet model. There are no widespread complaints for other Android devices. And as I said when you started this thread: once I rooted the tablet and flashed Cyanogenmod, the problem became a far-off memory. That's the beauty of the Android community. My tablet can do more things now. And I don't have to think about whether Samsung cares about me.
What did I learn?That if I wanted a 7"tablet today, I would get the Nexus 7. I got a Nexus 4 phone when Google dropped the price. I rooted it in 15 minutes. And Kit Kat is available for it already.
Click to expand...
Click to collapse
How can you recommend using Cyonogen when all of these issues are present?
1. Inherent from CM10.1
- Wifi-tethering, hdmi, Incall screen landscape, etc.
2. Bluetooh not working
- Need to see if the mojo in cm10.1 works here. (Lots of works...)
3. Camera not working yet
- Both camera can preview, Autio focus is OK for back camera. Can't save the photo...
(Seems bugs in framework_av cause it)
4. The default orientation of lockscreen is lanscape.
- not respond to rotation lock. Workaround: set only one angle in settings and enable rotation.
5. Screen rotation or rapid refresh cause transient noices. (Seems the new opengl issue, will try the new r3p2 mali driver later)
Unless you have a different version where everything works as it should.
Don't get mad, just pointing out the flaws of your suggestion.
Also my wife's Note II does not have this issue so I don't think it is a Samsung issue, then again I might be wrong.
Sent from my GT-P6800 using XDA Premium 4 mobile app
First off, I want you to know I am not angry; I am just realistic. Samsung released the GT-P6800 as part of their typical tactic: they offered tablets in every possible size:
7", 7.7 with AMOLED, 8.9, 10.1.
Then they waited to see what the market wanted. Our model's AMOLED display was an expensive (but excellent) component. When the smoke cleared, Samsung followed the market's signal. They never released a follow-up and decided on the Note series as a better product family. We are never going to get Samsung's attention. Between your experience, your wife's and mine, we know that the crashing apps only happen on the 7.7. So there is a combination of Samsung OS and hardware that causes the problem. For the reasons I just cited, Samsung IS NOT GOING TO OFFER FIXES OR PATCHES.
You've done a great job listing possible reasons why someone would not do what I did. (To root and flash a new ROM.)
So let me respond directly to your points.
adinis78 said:
How can you recommend using Cyonogen when all of these issues are present?
Click to expand...
Click to collapse
It's because of my priorities: I care deeply about reading on my tablet. That includes my subscription to The New Yorker magazine (via Newsstand) and PressReader for a variety of global newspapers. If I can't read what I want, I have to find a solution. You complained about Newsstand, so I told you how to get Newsstand working.
Another fringe benefit: I can get rid of the crap Samsung put in the firmware: Social Hub, Readers Hub, widgets, old PressReader, old Pulse, etc.
adinis78 said:
1. Inherent from CM10.1
- Wifi-tethering
Click to expand...
Click to collapse
I can confirm this does not work. If Samsung would release their WiFi drivers to the development community this problem could be fixed. (If Samsung is too busy with more profitable products, they should let the customers fix the problem, no?)
adinis78 said:
hdmi, Incall screen landscape, etc.
Click to expand...
Click to collapse
I have not tested these things.
HDMI
A direct physical HDMI connection is a pretty clumsy way of communicating with a TV. I'd rather use XBMC, DLNA, or one of the streaming boxes and "cast" the content to the TV across my network. Who needs to run a cable across the living room or bedroom between TV and tablet?
adinis78 said:
2. Bluetooh not working
Click to expand...
Click to collapse
Bluetooth is working. I use it.
adinis78 said:
- Need to see if the mojo in cm10.1 works here. (Lots of works...)
Click to expand...
Click to collapse
Sorry, I don't know what mojo is.
adinis78 said:
3. Camera not working yet
- Both camera can preview, Autio focus is OK for back camera. Can't save the photo...
(Seems bugs in framework_av cause it)
Click to expand...
Click to collapse
I did not spend a lot of time testing this. But I was able to save pictures from the back camera. I did not test the front camera. A quick test of Skype was not successful connecting even though wifi is working.
adinis78 said:
4. The default orientation of lockscreen is landscape.
- not respond to rotation lock. Workaround: set only one angle in settings and enable rotation.
Click to expand...
Click to collapse
I am not having this problem. I don't remember if this happened on my tablet after flashing CM. But now I am using Xposed framework + App Settings. So almost everything can be forced to auto-rotate.
adinis78 said:
5. Screen rotation or rapid refresh cause transient noices. (Seems the new opengl issue, will try the new r3p2 mali driver later)
Click to expand...
Click to collapse
I am not experiencing any unusual noises. I've never built a ROM so I have no idea about the underlying drivers.
adinis78 said:
Unless you have a different version where everything works as it should.
Click to expand...
Click to collapse
Unfortunately if Samsung won't release all the drivers to the development community, it's unlikely that there will ever be a fully functional alternative ROM for the GT-P6800.
adinis78 said:
How can you recommend using Cyonogen when all of these issues are present?
1. Inherent from CM10.1
- Wifi-tethering, hdmi, Incall screen landscape, etc.
2. Bluetooh not working
- Need to see if the mojo in cm10.1 works here. (Lots of works...)
3. Camera not working yet
- Both camera can preview, Autio focus is OK for back camera. Can't save the photo...
(Seems bugs in framework_av cause it)
4. The default orientation of lockscreen is lanscape.
- not respond to rotation lock. Workaround: set only one angle in settings and enable rotation.
5. Screen rotation or rapid refresh cause transient noices. (Seems the new opengl issue, will try the new r3p2 mali driver later)
Unless you have a different version where everything works as it should.
Don't get mad, just pointing out the flaws of your suggestion.
Also my wife's Note II does not have this issue so I don't think it is a Samsung issue, then again I might be wrong.
Sent from my GT-P6800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I think you listed the issues of CM 11 , and he's using CM 10.X
By the way I got same problem after updating those two apps. So I just uninstalled updates.
I'm still giving the stock ROM some time , as I own this tablet from only 2 months..but I think I'm gonna move to Cyanogenmod in time, its not only Samsung thing, all stock Roms from all brands I've tested get laggy after few months..:| , even with pure android on nexues 7 , this thing I've never seen with Apple tho they still power their flagship devices with Dual Core, and 1 GB Ram.!
Sent from my GT-P6800 using xda premium
Silver-7 said:
I think you listed the issues of CM 11 , and he's using CM 10.X
By the way I got same problem after updating those two apps. So I just uninstalled updates.
I'm still giving the stock ROM some time , as I own this tablet from only 2 months..but I think I'm gonna move to Cyanogenmod in time, its not only Samsung thing, all stock Roms from all brands I've tested get laggy after few months..:| , even with pure android on nexues 7 , this thing I've never seen with Apple tho they still power their flagship devices with Dual Core, and 1 GB Ram.!
Sent from my GT-P6800 using xda premium
Click to expand...
Click to collapse
Don't fill up the whole of your internal sdcard and fstrim (JB only) your partitions once a week or on boot. Also, improve android LMK & min frees with V6SuperCharger, or CrossBreeder etc. This may help, but involves some reading on your part.
Apple don't fill their device with as many useful features (or bloatware), which would require greater hardware capacity. There's no comparison.
Sent from my GT-I9500 using XDA Premium 4 mobile app
I tried and tested http://forum.xda-developers.com/showthread.php?t=2535734 latest Cyonoge romantic version and boy or boy was it buggy, issues with screen rotation (known factor) and bluetooth not working (known issue, and I really used this feature) so decided to go back to 4.1.2 stock and just get used to not having latest version of Google Now. At least I know I have a fully functioning rom and tab. I guess no more need to complain.
Sent from my GT-P6800 using XDA Premium 4 mobile app
These apps with updates working great with PAK 4.2.2 , so its a stock 4.1.2 issue.
Sent from my GT-p6800 using xda premium
Silver-7 said:
These apps with updates working great with PAK 4.2.2 , so its a stock 4.1.2 issue.
Sent from my GT-p6800 using xda premium
Click to expand...
Click to collapse
Could you please provide link to thread, thanks.
Sent from my GT-P6800 using XDA Premium 4 mobile app
Hi guys since the N5 and G2 are closely related I was thinking it might be possible to put the 13mpx camera module from the G2 into the N5. I did some searching for images and from what I can see the connector looks to be the same or at least very similar:
Nexus 5 camera module:
http://www.etradesupply.com/lg-nexus-5-d820-rear-facing-camera.html
LG G2 camera module:
http://www.ebay.com/itm/Camara-Prin...3?pt=LH_DefaultDomain_186&hash=item2330e302e7
Even if this fits there might be software related issues that might stop it from working (Drivers etc)
What do you guys think? worth a try? Or anyone tried it?
I think its pointless. Its not all about mega pixels you know?
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
probly wont work and would need a entire software rewrite if the phone even could detect it I think there would be serious software problems
I wouldn't bother
Sent from my Nexus 5 using Tapatalk
IMO, it's definitely can! The module is same!
Might be worth the hassle. You could always pop the original camera back in if it didn't work and sell the G2 camera.
Sent from my Nexus 5 using XDA Premium 4 mobile app
If it weren't around the holidays, I would probably at least try. My wallet is near empty. If it does fail, you can always just swap the N5 camera back in. Let us know if your going to move forward with the modding, I'd like to see that!
subscribed! I would honestly be more interested in having a camera app with the same iq and speed of the G2 Camera
bump, would like to know if that is possible too! I think we would need to modify a kernel and have a new camera app/drivers, but if hardware supports it, why not! Any testers? :fingers-crossed:
EDIT: Cheaper module: http://www.ebay.com/itm/Replacement...e_Replacement_Parts_Tools&hash=item4d1cd1ac7a
EDIT2: an even cheaperer module http://www.ebay.com/itm/Replacement...e_Replacement_Parts_Tools&hash=item2c80ba1e8b
If no one is willing to test I think I will go and try if this is possible when I get my nexus
No.
Sent from my Nexus 5 using Tapatalk
rootSU said:
No.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Why so pessimist?
ashirviskas said:
Why so pessimist?
Click to expand...
Click to collapse
Firstly I am a realist and that is because of my second point, which is that it can't be done. Try and prove me wrong if you like but I accept no responsibility for your device
Sent from my Nexus 5 using Tapatalk
Why can't it be done? I think with some kernel and android tweaking we could get that working, am I wrong? I've checked, they are the same connectors. I see only two problems that might stop from using G2's camera - no hardware support (which I think should be there as they are almost the same phones), or no one smart/determined enough to get it working on software. If I get it working somehow on hardware level and prove it to you (I don't even imagine how, but what if), would you help me with making it run properly? I am not saying that this is really possible, I am saying that no one knows that for sure (maybe exept LG).
Then buy it, do it and get it over with. Btw, it wont work.
We can make it shoot videos in 8k 120fps too :silly:
Seriously though, if it was possible, it would have been done already.
Lethargy said:
We can make it shoot videos in 8k 120fps too :silly:
Seriously though, if it was possible, it would have been done already.
Click to expand...
Click to collapse
But someone has to be first
ashirviskas said:
But someone has to be first
Click to expand...
Click to collapse
Excellent. Well let that be you. I presume you have solid experience in recreating closed source drivers from scratch?
Sent from my Nexus 5 using Tapatalk
Lethargy said:
We can make it shoot videos in 8k 120fps too :silly:
Seriously though, if it was possible, it would have been done already.
Click to expand...
Click to collapse
When it comes to any kind of porting, on any device that's been out awhile.....I always say this!
If it were possible, especially on a nexus, it would have been done by now.
---------- Post added at 01:48 PM ---------- Previous post was at 01:47 PM ----------
But yes....try it yourself....succeed and the masses will be eternally grateful to you. ?
rootSU said:
Excellent. Well let that be you. I presume you have solid experience in recreating closed source drivers from scratch?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
couldn't we just use G2's drivers..?
ashirviskas said:
couldn't we just use G2's drivers..?
Click to expand...
Click to collapse
Well if it were that easy it would have been done by now... But no. The G2 is a different phone. They haven't even been able to successfully port a G2 ROM to the n5 yet
Sent from my Nexus 5 using Tapatalk
In the change log of android l it mentions it has okay Google with screen off. Does the nexus 5 have the necessary dsp hardware to make that happen?
Sent from my XT1053 using Tapatalk
biggiestuff said:
In the change log of android l it mentions it has okay Google with screen off. Does the nexus 5 have the necessary dsp hardware to make that happen?
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
nexus 5 does that already, as long as your plugged in. turn it on in the voice settings. funny thing though. you can say ok google when the screen is off, and search for anything, but it wont turn the screen on
simms22 said:
nexus 5 does that already, as long as your plugged in.
Click to expand...
Click to collapse
Yeah that I know but the change log makes it sound as if it will be more like the moto x, where you wouldn't need to be plugged in.
Sent from my XT1053 using Tapatalk
biggiestuff said:
Yeah that I know but the change log makes it sound as if it will be more like the moto x, where you wouldn't need to be plugged in.
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
its possible. but the nexus 5 wont be able to do it then, as it would just kill your battery.
simms22 said:
its possible. but the nexus 5 wont be able to do it then, as it would just kill your battery.
Click to expand...
Click to collapse
I'm guessing the snapdragon 800 isn't capable which is why the moto x opted for at least the 801. Don't know really but I was hoping someone might know. Time will tell I guess.
Sent from my XT1053 using Tapatalk
Motorola uses the fabled "low power core" to run active display and touchless control. Without that, both features will destroy any devices battery.
Just like the N5 has a pedometer running in a similar way. LG has tap to wake, as does the M8. That's why tap to wake is a huge battery drain on the N5.
?
KJ said:
Motorola uses the fabled "low power core" to run active display and touchless control. Without that, both features will destroy any devices battery.
Just like the N5 has a pedometer running in a similar way. LG has tap to wake, as does the M8. That's why tap to wake is a huge battery drain on the N5.
?
Click to expand...
Click to collapse
Double tap to wake drains on the Nexus 5 because you can't just keep the digitizer on, you have to keep the entire panel on. On devices where it doesn't drain, you can power them on separately. Nothing to do with the low-powered core.
---------- Post added at 11:27 AM ---------- Previous post was at 11:26 AM ----------
biggiestuff said:
I'm guessing the snapdragon 800 isn't capable which is why the moto x opted for at least the 801. Don't know really but I was hoping someone might know. Time will tell I guess.
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
800 is just as capable as the 801. Low-power core is just used for a hardware pedometer instead of "always listening", as well as legal issues if you were to enable it without permission.
Lethargy said:
Double tap to wake drains on the Nexus 5 because you can't just keep the digitizer on, you have to keep the entire panel on. On devices where it doesn't drain, you can power them on separately. Nothing to do with the low-powered core.
---------- Post added at 11:27 AM ---------- Previous post was at 11:26 AM ----------
800 is just as capable as the 801. It's just used for a hardware pedometer instead, as well as legal issues if you were to enable it without permission.
Click to expand...
Click to collapse
Smarty pants! ?
Alls I know is I have it now and it's terrific. ?
I guess we'll find out soon. Android L is being released Friday for the n5 right? I guess there is no plausible way for lollipop to change the function on the low power core on the n5 to use it for listening instead of a pedometer.
Sent from my Nexus 7 using Tapatalk
KJ said:
Smarty pants! ?
Alls I know is I have it now and it's terrific. ?
Click to expand...
Click to collapse
Traitor
But yeah. The low-powered core is only good for things that usually require wakelocks (i.e. always listening, music playing, hardware pedometer). Screen-off gestures are done at kernel level and does NOT require a wakelock, so the low-powered core is completely useless in that regard.
Only factor determining if screen-off gestures drains or not is how power is provided to the panel. If it's possible to power the digitizer on separately, then it uses less battery. If you have to power the entire panel on, it'll use more. Either way, it's the exact same thing and not really done much differently across all devices; just make sure the digitizer is powered in any way and wake the device (or whatever) on specific gestures.
biggiestuff said:
I guess we'll find out soon. Android L is being released Friday for the n5 right? I guess there is no plausible way for lollipop to change the function on the low power core on the n5 to use it for listening instead of a pedometer.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
What is being released Friday is an updated preview
scottharris4 said:
What is being released Friday is an updated preview
Click to expand...
Click to collapse
Hopefully that have most of the features for us to test out
Sent from my Nexus 5 using Tapatalk
I doubt the preview will have all the features. From the looks of it, it doesn't even have most of them. They're saving it for the official release. The preview didn't include the new/updated apps either.
Anyway, the N5 isn't likely to get the feature you're asking about. It has to be enabled and setup with the processor's low power core. I don't think this can happen through an ota. From what I've heard it'll just be the new devices receiving that feature.
Sent from my Nexus 5
Even if your screen is off, you can say "OK Google" on devices with digital signal processing support such as Nexus 6 and Nexus 9
You can find the details in the lollipop specification in android official website
Sent from my Nexus 5 using Tapatalk
It does work on my phone, the thing is that have to hit the power button then the lock screen comes up, if you say "okay Google" it does work like call or text but still the screen remain unlock. I haven't tried doing "okay google", " unlock screen"
Sent from my Nexus IV using Tapatalk running Android 5.0 L Preview.