It varies depending on the connection type. DSL is usually interleaved, which increases latency quite drastically... hence the popularity of Fastpath with gamers. And even then, cable latency is usually almost an order of magnitude lower... Best I've seen around here is around 30ms for DSL vs. 5ms for cable.
Re:That's why I like the basic Kindle
on
The eBook Backlash
·
· Score: 1
It really depends on how/when/where you read. If you like to knock out a chapter whenever possible, it's great to be able to use your phone as an e-reader... I'm loving my Galaxy Nexus for this. That doesn't prevent me from having an E-Ink reader on my bed-side-table though - the lack of synchronization options is what's preventing that. Yes, Kindle + Kindle Apps are perfect in this regard, but can I continue to use all my old morally grey (buy the paperback, read digitally) TXT, LIT and EPUB files? No ****ing way I'm buying all those books again (I like to re-read a lot)...
Other e-readers are much better in terms of file format compatibility, but I haven't seen any with the synchronization options offered by the Kindle ecosystem...
It's not really a matter of error messages... but rather the fact that it's too easy to make one little mistake (flip a sync switch here, install a new app) that causes you to end up with an empty phone after just a few hours of standby. This is caused by exactly this school of thought:
"If the App is working correctly, Android should ignore it."
If the app drains 40% of the phone's battery over the course of three hours in standby, it's not working correctly - this should never happen. Yes, it should be possible to manually force these scenarios (because they are realistic for some particularly heavy users), but having apps be able to run like this by default is insane. That's the price we currently pay for full multitasking and a very open "you can do pretty much anything with it" system, but there are better ways to use it... say a simple whitelist for allowing apps to run during standby.
"Android 2.2 and on have had a really good battery metering tool built in that displays the amount of battery consumed by each process/device (Cell Idle, Screen, Android OS, Maps, et al.), but most users dont know about it. As of 2.3 ish it even recorded signal strength along with a graph of the battery level. Here's an example [tapatalk.com], powerful tools hidden from the user because designers insist on keeping users idiots rather then trying to help them."
Unfortunately, this battery metering tool is blunt and inaccurate at best. Not only is the system very simple and not particularly easy to read accurately, it doesn't show WHICH processes are keeping the phone awake very accurately. See the "awake" section on the screenshot you linked to? Problematic phones have solid blue strips of that (even though the screen is off at the time), and the only way to diagnose which app is causing it is battery history or third party tools like BetterBatteryStats (or the command line equivalent, but that's a little finnicky on a handset).
The built in battery monitoring is great for a quick overview, and for checking if everything's OK, but when I see a handset with bad battery life, the culprit only shows up in there about 50% of the time...
"Though Windows Phone 7.5 introduced new multitasking capabilities, allowing applications to do things like play music in the background and run periodic scheduled tasks, it only supports certain scenarios. VoIP is not one of those supported scenarios."
Hmmm, good point. My Galaxy Nexus take barely usable shots in broad daylight but churns out murky crap at night... maybe it really is time for a bigger camera.
Android has some sort of a built-in low power push-like mechanism that was implemented starting with Android 2.2 (Froyo), called C2DM. It's not quite real push, but the battery life is stupid good.
Your SGS2 is configured wrong. You should be getting a standby drain of about 1%/hour (or less) with sync enabled.
Two things are at fault here, of course:
1. The awful apps that keep the phone awake and active during standby - for instance: Facebook 2. Android, for not telling the user THIS APP IS KEEPING YOUR PHONE AWAKE, KICK THAT CRAP!
In your specific case: Check your battery usage (in your SGS2's settings), and find out which process is keeping your phone awake, either with the old battery history (Gingerbread and earlier, accessible via Spare Parts, apps like BatteryMonitorWidget or a dialer code that varies from handset to handset) or (ICS only - because someone at Google decided to remove the battery history) with an app like BetterBatteryStats.
The interesting part is usually partial wake usage. Eliminate the apps causing the most partial wake usage, and you'll have a power draw of next to nothing. Standby battery life with Google sync, a few IM clients (I run Skype and imo.im), Whatsapp, Viber and so on, should be around 4-5 days.
Seems to be different from country to country, I suppose. Here in Germany, I've had three routers, all directly from the ISP, and all of them had a SIP stack and a jack for an analog phone:)
As for SIP to Phone providers: You should check with your ISP, many of them offer SIP service too... mine just bundles a phone-flatrate (to all domestic landlines) with its internet service, which is useful - especially with SIP stacks becoming available standard on most smartphones. Free calls from anywhere you can get a 3G signal:)
As you can see, phone jacks, and there's a whole fully configurable SIP stack in the web interface. The one all the way on the left is the DSL line, and I'm assuming the one on the right is for some special kind of phone (ISDN maybe).
And it's not like stationary SIP is difficult to set up. Hell, most routers I've seen lately have an actual RJ-XX (the one that looks like a smaller RJ45) socket for phones, specifically for use with SIP... I know mine does.
If you really want voice over your new fibre: Set it up yourself. If not, well, just keep using POTS, because you probably won't know the difference anyway...
"Saying that FLAC is better than MP3 is like saying that an M1A1 is better than a smart car. If you care only about getting something from point A to point B undamaged, then yes, it is. If you care at all about efficiency, not so much."
If that M1A1 was as easy to drive and as cheap to build as the Smart, sure... and if we had a near-unlimited supply of fuel (I have a huge collection of ripped albums in FLAC, and I can't fill even a 500GB drive with it, even though it's mostly on the lowest compression setting).
Well, the 6870/6850 was pretty much the bang-for-your-buck card in the last gen, with the 6770/6670/6570 being really affordable for most any aspiring gamer - so I'd assume you'll need to wait for a 7870/7770/7670... shouldn't be all too long now. I'm waiting for the 7770 (or the 7 series equivalent of the 6770) myself - should be a nice reduction in power consumption and noise, coming from an 8800GT.
"Did they have goofy oversized widgets for sloppy finger-based simple computer usage by retards? No. They were pen based. You know..... for functional useful software in a professional environment instead of a web browser on steroids for morons that can't type or write legibly anyway."
I love you.
*hugs Thinkpad tablet* (no, not the slow-ass Android version - a REAL Thinkpad tablet!).
Don't you mean lack of dual link DVI is a pain in the ass? What problems are there with dual link, other than cheap graphics cards from 5 years ago not having had it?
DisplayPort/HDMI type plugs are nicer on mobile devices, I imagine - I still have DVI and VGA on some of my laptops, and plugging and unplugging them makes me cringe because I'm going to break pins any day now (after thousands of pluggings)...
Right now it would seem that you're dreaming - there's a very good chance that we'll never see anything comparable on ARM, simply because the devices will all be locked down.
Have you ever seen anything like this on a previous ARM tablet? What makes you think the Windows-based ones will be any different?
ARM going in this direction does not mean that X86 will follow - it's perfectly possible that this is the beginning of the end, but not for computing - just for ARM.
While I hope that's not true, it's actually a rather likely path - with even "open source" Linux-based ARM devices shipping with locked bootloaders, I'm not sure we'll ever see ARM devices that are as open as X86 BIOS/UEFI based general purpose computers. Right now it looks more like they'll be stuck in the consumer toy market for a while and then die a slow death when the tablet hype slows down.
Smartphones will keep them alive, but other than that... do we really have a use for such cut-down computing devices?
Slashdot Mirror
It varies depending on the connection type. DSL is usually interleaved, which increases latency quite drastically... hence the popularity of Fastpath with gamers. And even then, cable latency is usually almost an order of magnitude lower... Best I've seen around here is around 30ms for DSL vs. 5ms for cable.
It really depends on how/when/where you read. If you like to knock out a chapter whenever possible, it's great to be able to use your phone as an e-reader... I'm loving my Galaxy Nexus for this. That doesn't prevent me from having an E-Ink reader on my bed-side-table though - the lack of synchronization options is what's preventing that. Yes, Kindle + Kindle Apps are perfect in this regard, but can I continue to use all my old morally grey (buy the paperback, read digitally) TXT, LIT and EPUB files? No ****ing way I'm buying all those books again (I like to re-read a lot)...
Other e-readers are much better in terms of file format compatibility, but I haven't seen any with the synchronization options offered by the Kindle ecosystem...
Any suggestions?
It's not really a matter of error messages... but rather the fact that it's too easy to make one little mistake (flip a sync switch here, install a new app) that causes you to end up with an empty phone after just a few hours of standby. This is caused by exactly this school of thought:
"If the App is working correctly, Android should ignore it."
If the app drains 40% of the phone's battery over the course of three hours in standby, it's not working correctly - this should never happen. Yes, it should be possible to manually force these scenarios (because they are realistic for some particularly heavy users), but having apps be able to run like this by default is insane. That's the price we currently pay for full multitasking and a very open "you can do pretty much anything with it" system, but there are better ways to use it... say a simple whitelist for allowing apps to run during standby.
"Android 2.2 and on have had a really good battery metering tool built in that displays the amount of battery consumed by each process/device (Cell Idle, Screen, Android OS, Maps, et al.), but most users dont know about it. As of 2.3 ish it even recorded signal strength along with a graph of the battery level. Here's an example [tapatalk.com], powerful tools hidden from the user because designers insist on keeping users idiots rather then trying to help them."
Unfortunately, this battery metering tool is blunt and inaccurate at best. Not only is the system very simple and not particularly easy to read accurately, it doesn't show WHICH processes are keeping the phone awake very accurately. See the "awake" section on the screenshot you linked to? Problematic phones have solid blue strips of that (even though the screen is off at the time), and the only way to diagnose which app is causing it is battery history or third party tools like BetterBatteryStats (or the command line equivalent, but that's a little finnicky on a handset).
The built in battery monitoring is great for a quick overview, and for checking if everything's OK, but when I see a handset with bad battery life, the culprit only shows up in there about 50% of the time...
It's not the notification that's the problem, but rather that the call is ended when you switch to a different app.
The article he linked to.
"Though Windows Phone 7.5 introduced new multitasking capabilities, allowing applications to do things like play music in the background and run periodic scheduled tasks, it only supports certain scenarios. VoIP is not one of those supported scenarios."
Hmmm, good point. My Galaxy Nexus take barely usable shots in broad daylight but churns out murky crap at night... maybe it really is time for a bigger camera.
What exactly is wrong with them? Can you point out something?
Look at the sample shots. 41MP be damned, those photos look goooooood.
http://cdn.conversations.nokia.com.s3.amazonaws.com/wp-content/uploads/2012/02/Archive2.zip
Me likey...
Howdy Tex,
Wrong thread! :)
Spare Parts => Battery History => Partial Wake Usage.
If possible, post a screenshot and we can work from there :)
Not on Windows Phone it doesn't... what? Use C2DM? No surprises there, that's an Android thing that's not available on Windows Phone ;)
It really is unfortunate that Microsoft kludged the system like that - VoIP is a no-brainer for multitasking... :(
Android has some sort of a built-in low power push-like mechanism that was implemented starting with Android 2.2 (Froyo), called C2DM. It's not quite real push, but the battery life is stupid good.
I'd assume Skype uses C2DM, as do most IM apps...
http://code.google.com/android/c2dm/
Your SGS2 is configured wrong. You should be getting a standby drain of about 1%/hour (or less) with sync enabled.
Two things are at fault here, of course:
1. The awful apps that keep the phone awake and active during standby - for instance: Facebook
2. Android, for not telling the user THIS APP IS KEEPING YOUR PHONE AWAKE, KICK THAT CRAP!
In your specific case: Check your battery usage (in your SGS2's settings), and find out which process is keeping your phone awake, either with the old battery history (Gingerbread and earlier, accessible via Spare Parts, apps like BatteryMonitorWidget or a dialer code that varies from handset to handset) or (ICS only - because someone at Google decided to remove the battery history) with an app like BetterBatteryStats.
The interesting part is usually partial wake usage. Eliminate the apps causing the most partial wake usage, and you'll have a power draw of next to nothing. Standby battery life with Google sync, a few IM clients (I run Skype and imo.im), Whatsapp, Viber and so on, should be around 4-5 days.
Seems to be different from country to country, I suppose. Here in Germany, I've had three routers, all directly from the ISP, and all of them had a SIP stack and a jack for an analog phone :)
As for SIP to Phone providers: You should check with your ISP, many of them offer SIP service too... mine just bundles a phone-flatrate (to all domestic landlines) with its internet service, which is useful - especially with SIP stacks becoming available standard on most smartphones. Free calls from anywhere you can get a 3G signal :)
Really. Here's a picture I just snapped of the bog-standard router that came with my DSL package:
http://dl.dropbox.com/u/7086491/pictures/routerphonejack.jpg
As you can see, phone jacks, and there's a whole fully configurable SIP stack in the web interface. The one all the way on the left is the DSL line, and I'm assuming the one on the right is for some special kind of phone (ISDN maybe).
And it's not like stationary SIP is difficult to set up. Hell, most routers I've seen lately have an actual RJ-XX (the one that looks like a smaller RJ45) socket for phones, specifically for use with SIP... I know mine does.
If you really want voice over your new fibre: Set it up yourself. If not, well, just keep using POTS, because you probably won't know the difference anyway...
"Saying that FLAC is better than MP3 is like saying that an M1A1 is better than a smart car. If you care only about getting something from point A to point B undamaged, then yes, it is. If you care at all about efficiency, not so much."
If that M1A1 was as easy to drive and as cheap to build as the Smart, sure... and if we had a near-unlimited supply of fuel (I have a huge collection of ripped albums in FLAC, and I can't fill even a 500GB drive with it, even though it's mostly on the lowest compression setting).
Well, the 6870/6850 was pretty much the bang-for-your-buck card in the last gen, with the 6770/6670/6570 being really affordable for most any aspiring gamer - so I'd assume you'll need to wait for a 7870/7770/7670... shouldn't be all too long now. I'm waiting for the 7770 (or the 7 series equivalent of the 6770) myself - should be a nice reduction in power consumption and noise, coming from an 8800GT.
That's a bit of a dark path to start down.
I find myself rather more reminded of Harold and Kumar 2...
"Don't worry, it's just a bong!"
"He said he has a bomb!"
*Bong breaks*
"Aaaaah, poison gas!!!"
"Did they have goofy oversized widgets for sloppy finger-based simple computer usage by retards? No. They were pen based. You know..... for functional useful software in a professional environment instead of a web browser on steroids for morons that can't type or write legibly anyway."
I love you.
*hugs Thinkpad tablet* (no, not the slow-ass Android version - a REAL Thinkpad tablet!).
Interesting, I never even knew that there were DVI cables missing the second link...
Don't you mean lack of dual link DVI is a pain in the ass? What problems are there with dual link, other than cheap graphics cards from 5 years ago not having had it?
DisplayPort/HDMI type plugs are nicer on mobile devices, I imagine - I still have DVI and VGA on some of my laptops, and plugging and unplugging them makes me cringe because I'm going to break pins any day now (after thousands of pluggings)...
Right now it would seem that you're dreaming - there's a very good chance that we'll never see anything comparable on ARM, simply because the devices will all be locked down.
Have you ever seen anything like this on a previous ARM tablet? What makes you think the Windows-based ones will be any different?
ARM going in this direction does not mean that X86 will follow - it's perfectly possible that this is the beginning of the end, but not for computing - just for ARM.
While I hope that's not true, it's actually a rather likely path - with even "open source" Linux-based ARM devices shipping with locked bootloaders, I'm not sure we'll ever see ARM devices that are as open as X86 BIOS/UEFI based general purpose computers. Right now it looks more like they'll be stuck in the consumer toy market for a while and then die a slow death when the tablet hype slows down.
Smartphones will keep them alive, but other than that... do we really have a use for such cut-down computing devices?