Ehh no!
Well for sure wasnt keeping up with the times, it seems like dalvick VM is more optimized then iOS's C, or considered to be anyway.
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Ehh no!
Well for sure wasnt keeping up with the times, it seems like dalvick VM is more optimized then iOS's C, or considered to be anyway.
Dalvick VM is more optimized than iOS's C? wait what?![]()
I was just reading opinions in the two platforms and i see devs praising dalvich more and more.
I was just reading opinions in the two platforms and i see devs praising dalvich more and more.
While Dalvik might present a bit more overhead than that of a natively written C app(at least in theory), its not what is responsible for some of Android's battery issues. Google's own lower level services seem to be more and more of a battery drain lately.
Im not sure if the lower level would be the major culprit. Apple etters power consumption by strict management of background tasks as well as utilizing slower hardware with a smaller screen.
I think the biggest thing that differentiates (outside of third party software) is physical hardware. Next would be software, but it appears overhead isnt the big problem anymore.
I know they're two completely different platforms, but if iOS can last all day with a 1430 mAh battery, Android should last at least a couple days with a 2300+ mAh battery. I hope this is what they focus on in the next major revision. Large batteries are only masking the real issue and they take longer to charge.
iOS has two pretty huge advantages on that front though - small screen & low resolution. The current crop of Android phones have 5" 1080p screens. That's 50% larger in surface area (meaning bigger backlights, which are quite power hungry), as well as 2.8x more pixels. That's a hell of a lot more CPU, GPU, and memory bus work just to keep the framebuffer full of pixels, to say nothing of rendering those pixels. Not surprising that a 60% larger battery doesn't make up the difference.
It was the same with pre 1080p screens though, the only phone that offered good stock battery life was the razr maxx and even it had about the same screen on time, really good talk time though.
Im not sure if the lower level would be the major culprit. Apple etters power consumption by strict management of background tasks as well as utilizing slower hardware with a smaller screen.
I think the biggest thing that differentiates (outside of third party software) is physical hardware. Next would be software, but it appears overhead isnt the big problem anymore.
I don't necessarily agree, but a lot of problems are coming from the Google Services. Android needs a serious improvement in the PowerManager department and how the OS handles Wakelocks and pending app requests in the background.
Unfortunately for Mako and for us Google/CAF is not using the latest Kernel Power drivers that for example Manta does. I don't know why to be honest. I tried merging them once but things went kaboom after I flashed it for reasons that I'm too tired to explain at the moment. Not saying that the problem is that Power drivers, but the newer implementation that is used on Manta is much improved from Mako's code (which is pretty old in that department). These drivers are responsible for the PowerManagement routines from the Kernel side, wakelocks, suspend etc etc. Also Mako doesn't have a proper idle-state scaling like Manta or Tuna does, and that is also a big letdown. With proper C-state implementation the device wouldn't need to use Hotplugging to reduce power usage. I could go on and on. If the new Nexus comes with a proper modem solution, not this USB crap that we have, I'm sure things will be so much better in the long run.
It was the same with pre 1080p screens though, the only phone that offered good stock battery life was the razr maxx and even it had about the same screen on time, really good talk time though.
http://forum.xda-developers.com/showthread.php?p=45367788
A Kernel Devs take on it
If I had to guess, I'd say pricing will line up with Nexus 10.I just hope Google doesn't increase the base price of the Nexus 5 much from the Nexus 4. I'm especially nervous because the Snapdragon 800 has only appeared in very expensive, very large, monster phones. Hopefully going with that doesn't force them to up the base price by more than $30 or so (similar to what happened with the Nexus 7).
If I had to guess, I'd say pricing will line up with Nexus 10.
In fact - I wouldn't be surprised if they continued to sell the Nexus 4 into next year simply to have a cheaper alternative.
If I had to guess, I'd say pricing will line up with Nexus 10.
In fact - I wouldn't be surprised if they continued to sell the Nexus 4 into next year simply to have a cheaper alternative.
Based on the FCC filings, it looks like it will have a S800 and not the 600 based on SW versions of the test devices given to the FCCThey've already dropped the price of the N4 though, so if they retained the $300-$350 prices of the previous Nexus flagships, they'll already have a cheaper alternative.
I'll bet they use the S600 instead of the S800 to keep the price down. I just hope they offer something with more than 16 GBs for once, even if they have to charge $400+ to do it.
They've already dropped the price of the N4 though, so if they retained the $300-$350 prices of the previous Nexus flagships, they'll already have a cheaper alternative.
I'll bet they use the S600 instead of the S800 to keep the price down. I just hope they offer something with more than 16 GBs for once, even if they have to charge $400+ to do it.
TBH I have a hard time believing going back to S600 will make any meaningful difference in material costs, especially since you'd still have to add a separate cellular radio instead of just using the integrated one in S800.
On Nexus 5 rumors and renders
http://www.androidcentral.com/nexus-5-rumors-and-renders
This phone uses Snapdragon 800, is made by LG, running Key Lime Pie (or KitKat at the moment), and surprisingly lightweightIs it the Nexus 5? To answer that question, do you guys really think the new version of the G2 will run on 4.4?
yupAm i the only one who is really hoping that the next Google Nexus phone is from the Samsung Galaxy line?
My preference is Samsung, HTC, Sony, LG in that order.I personally would want the next Nexus to be a Sony rather than Samsung. HTC is okay too I guess.
I wonder if they'll pack a really nice camera for once into the Nexus. Bigger battery would be good too. While I'm dreaming how about 32GB default.
My preference is Samsung, HTC, Sony, LG in that order.
I hope they put a good camera in this Nexus. Every Nexus has had a horrific camera and is one of the few gripes I have about it. Ditch the fragile glass back and add a great camera and they'll have a winner IMO.