kaskade said:Did they fix the battery status thing? It's kind of annoying that the indicator stays at 75% until it hits 50%.
jonnybryce said:Changes were smaller than I expected. Nice little stuff. So much for Google buying the webOS design guy, barely anything improved. Not jealous of Nexus S or Gingerbread on FroyoDroid.
The new maps load 100 times faster because instead of downloading the entire map image for each level, the app downloads meta data which describes the entire map at all different levels and then renders the appropriate sector on the fly. This will start to give Google Maps offline capabilities on mobile phones. It may be possible to cache a map of an entire city on the phone.
Luckyman said:
jonnybryce said:Changes were smaller than I expected. Nice little stuff. So much for Google buying the webOS design guy, barely anything improved. Not jealous of Nexus S or Gingerbread on FroyoDroid.
That's pretty awesome and not unreasonable for smaller areas. Those map caches could get pretty freaking huge if you're caching an entire city on the scale of Houston or Los Angeles, though.Luckyman said:
kIdMuScLe said:just rooted my cousin's Galaxy S Vibrant and is there any good ROM's for it? thanks.
Luckyman said:
I'm now more tempted to create a BS warranty claim, sell the new model, then buy the Nexus S...tabsina said:I'm reading on Engadget that Nexus One isn't supported for Maps 5 due to it's shitty multitouch controls? (Annoying that also includes my Desire)
That really sucks if it means that there will be no version of maps 5 (a cut down one) for nexus/desire
N1 is dual touch or something, not multi. Fucking sucks for us.Jamesfrom818 said:The Engadget article on the new Google Maps says that the N1 can't handle it 100% due to its lack of multitouch which is strange because the N1 does have multitouch.
EDIT: Beat...
Thats enough of a reason for me to want to upgrade to a G2. I can wait for HTC's next phone though.
Bboy AJ said:N1 is dual touch or something, not multi. Fucking sucks for us.
Hardware limitation so there is no way. I'm baffled as to why Google used the crappy input as opposed to true multitouch.Jamesfrom818 said:Our only hope is that xda can find a way.
Maybe they realize the screen is too crappy to work properly: http://m.youtube.com/#/watch?xl=xl_blazer&v=dsSUqkh8pcIJamesfrom818 said:I wonder why dual touch isn't enough for rotating the view. Doesn't seem like it would be that big of a deal.
Yeah, sucks that the N1 won't have full functionality for the new Maps, but it will still have some aspects, including caching.Jamesfrom818 said:I wonder why dual touch isn't enough for rotating the view. Doesn't seem like it would be that big of a deal.
Because our boy eric schimdt didn't want to hurt jobs feelings with the multi-touch screen and went with dual touch instead. They were scratching each others backs and eric bent over to jobs request. That's why early nexus adopters like myself didn't have dual touch enabled until 2.1Bboy AJ said:Hardware limitation so there is no way. I'm baffled as to why Google used the crappy input as opposed to true multitouch.
Gingerbreads UI brings GPU accelerated animations onboard and will likely provide some speedup to the interface which even with 2.2 was occasionally jittery even on the fastest hardware.
JCX said:I saw on wikipedia that video chat is supposed to be in gingerbread? Does this mean a native android video chat feature, or will it be separate like the current third party video chat features?
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S/SGH-I897Slizz said:Anybody root a ATT Galaxy S Captivate?
If yes, anyone have like a tutorial or something?
Epix said:Andy Rubin with prototype Motorola Tablet showing off Honeycomb and new Google Maps app.
WARNING: The two people interviewing him are tough to listen to.
Luckyman said:
This has been in development for ages now. For the longest time (close to an year I think) the hacked version by brut from XDA had a debug option to enable vectors. It was pretty cool, albeit incomplete of course.Luckyman said:
thespot84 said:http://lifehacker.com/5708080/use-the-new-gingerbread-keyboard-on-your-rooted-android-phone?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed:+lifehacker/full+(Lifehacker)
Haven't tried it but could be fun... (use 2.3 keyboard on rooted 2.2)
Just installed and it's working fine. I guess the new text selection system is something independent of the keyboard in Gingerbread, because I can't find a way to use it or bring it up.thespot84 said:http://lifehacker.com/5708080/use-the-new-gingerbread-keyboard-on-your-rooted-android-phone?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed:+lifehacker/full+(Lifehacker)
Haven't tried it but could be fun... (use 2.3 keyboard on rooted 2.2)
Are we sure thats not 2.3 only?zesty said:Just saw the info about the new Google Maps. Looks awesome, and I'm glad I'm not getting completely left behind with everything on my original Droid. Yet.
skybaby said:Are we sure thats not 2.3 only?![]()
-Galaxy S
-Droid
-Droid X
-Droid 2
-Droid Incredible
-Evo
-Nexus S
-G2
The update is due out in the "coming days," according to Rubin. Great way to kick off Nexus S' launch, then.
zesty said:http://www.engadget.com/2010/12/06/google-maps-for-mobile-5-unveiled-adds-dynamic-map-drawing-and/
Also:
So definitely not a Gingerbread thing, unless that is also coming out for all of those phones in the next few days.
Crisco said:Are they ever going to fix the overall "jankiness" of the Android UI? Even the latest video showing that tablet, the scrolling still looked slow. That's going to be an immediate turn off to anyone coming from an iPhone.
Gwanatu T said:I think this depends heavily on the hardware. On my HTC/T-Mobile G2 I never run in to any kind of slow down like I've seen on other hardware at times.
koshunter said:I've been trying to install the Gingerbread keyboard on my rooted HTC Hero (it is 2.2) and it keeps giving me a Status 0 error and aborts the installation.
I'm sure it's a simple fix but I can't seem to find a solution for it.
Crisco said:Are they ever going to fix the overall "jankiness" of the Android UI? Even the latest video showing that tablet, the scrolling still looked slow. That's going to be an immediate turn off to anyone coming from an iPhone.