User Tools

Site Tools


zenec-ze-nc5011d

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
zenec-ze-nc5011d [2013/11/14 13:16]
admin
zenec-ze-nc5011d [2013/11/14 13:42] (current)
admin
Line 3: Line 3:
  
 ^ <​WRAP>​=== Things I wish I knew before buying ===</​WRAP>​ ^ ^ <​WRAP>​=== Things I wish I knew before buying ===</​WRAP>​ ^
-| <wrap>+| <WRAP>
 Note: I was using a Sony Xperia Z Ultra (SXZU).  ​ Note: I was using a Sony Xperia Z Ultra (SXZU).  ​
   ​   ​
-  ​The USB port on the device only supports USB Mass Storage (and probably some Apple iPhone/iPad things). However, since Android 3.0 (Honeycomb) most Android-devices no longer support USB Mass Storage in lieu of MTP[(Media Transfer Protocol)]. [(It isn't physically possible to support UMS on devices that don't have a dedicated partition for storage (like a removable SD card, or a separate partition like Nexus S.) This is because UMS is a block-level protocol that gives the host PC direct access to the physical blocks on the storage, so that Android cannot have it mounted at the same time.+  ​The USB port on the device only supports USB Mass Storage (and probably some Apple iPhone/iPad things). However, since Android 3.0 (Honeycomb) most Android-devices no longer support USB Mass Storage in lieu of MTP[(Media Transfer Protocol)]. [(It isn't physically possible to support UMS on devices that don't have a dedicated partition for storage (like a removable SD card, or a separate partition like Nexus S.) This is because UMS is a block-level protocol that gives the host PC direct access to the physical blocks on the storage, so that Android cannot have it mounted at the same time.
  
 With the unified storage model we introduced in Honeycomb, we share your full 32GB (or 16GB or whatever) between app data and media data. That is, no more staring sadly at your 5GB free on Nexus S when your internal app data partition has filled up -- it's all one big happy volume. With the unified storage model we introduced in Honeycomb, we share your full 32GB (or 16GB or whatever) between app data and media data. That is, no more staring sadly at your 5GB free on Nexus S when your internal app data partition has filled up -- it's all one big happy volume.
Line 14: Line 14:
 On the whole it's a much better experience on the phone. On the whole it's a much better experience on the phone.
  
-http://​www.reddit.com/​r/​Android/​comments/​mg14z/​whoa_whoa_ics_doesnt_support_usb_mass_storage/​c30q93p)] I can enable UMS through procfs-hacks on my rooted SXZU, but this is far too hairy. Effectively,​ this means that I cannot use the USB interface to browse through the music library on my phone. ​ +http://​www.reddit.com/​r/​Android/​comments/​mg14z/​whoa_whoa_ics_doesnt_support_usb_mass_storage/​c30q93p)] I can enable UMS through procfs-hacks on my rooted SXZU, but this is far too hairy. Effectively,​ this means that I cannot use the USB interface to browse through the music library on my phone.
   ​   ​
-  ​The Bluetooth AVRCP support only allows me to play, stop and track skip forward/​backward. It does _not_ allow me to browse through my media library. Effectively this means that I can only start/stop music if I've already started a music program on my phone. And I can only back/​forward through whatever is in the playlist on my phone. ​ +  ​The Bluetooth AVRCP support only allows me to play, stop and track skip forward/​backward. It does _not_ allow me to browse through my media library. Effectively this means that I can only start/stop music if I've already started a music program on my phone. And I can only back/​forward through whatever is in the playlist on my phone.
   ​   ​
-  ​Every time I start my car, the device needs to boot before it is usable. This takes nearly a minute for the radio to start working, and takes half a minute after that for the bluetooth starts working. Effectively this means that if I want to listen to music while driving, I need to either wait with driving until the device is available, or control the device while driving which is less safe. +  ​Every time I start my car, the device needs to boot before it is usable. This takes nearly a minute for the radio to start working, and takes half a minute after that for the bluetooth starts working. Effectively this means that if I want to listen to music while driving, I need to either wait with driving until the device is available, or control the device while driving which is less safe. 
 +   
 +  * The navigation software. I can't point at a single issue that bothers me the most. The Text2Speech voices irritate me with misplaced '​klemtoon'​. The user-interface annoys me because it's not intuitive and every action requires just a few too many '​clicks'​. The drawing and updating of the screen is very choppy. I think I'm just spoiled by the Android experience.
  
-</wrap> |+</WRAP> |
  
 ^ <​WRAP>​=== Specifications ===</​WRAP>​ ^^^ ^ <​WRAP>​=== Specifications ===</​WRAP>​ ^^^
zenec-ze-nc5011d.txt · Last modified: 2013/11/14 13:42 by admin