Galaxy Nexus Signal Problem

Ok, I've had dozens of Verizon Phones but something is going really wrong with the Galaxy Nexus that I own. It started out as the best device that I have ever owned. Then I had a problem with it non-related to the signal issues. The tier two tech support had me do a software update on the phone and ever since, the 4G, 3G and phone signal truly struggle. Calls are dropped. Texts wont go through. And internet is often inaccessible. This is all intermittent and untraceable as far as a pattern goes. So Verizon sent me a replacement device. It was worse...to the point that it would not connect to anything reliably, including wifi. They sent me another device and it was more of the same. I am now out of town and having the problems continue with my original phone. A third device is waiting at my house for what Verizon thinks will solve the problem. I'm hoping it is the answer.
Who else is having these problems. Tier Two tells me that this is not a common problem with this phone. It's hard to believe because, I am 0-4 on this device. Also, if you are having problems, did you start having problems in July/August when an update was possibly released?
Let's hear from you!

I just bought a nexus fully aware of the signal problems but was assured by best buy that it is a sim card issue and they would repeatedly replace the sim card until it worked. I am running 4.0.4 the phone was updated before I bought it or came with the update as it was in an unopened box brand new. I have not had any issues other than I cant seem to get more than 2 bars of service in places where my old phone had full signal. so for those of you waiting for an update it may fix some issues but as far as I am concerned it does not fix the signal problem. I bought 3 of these phones and all three have not gone over 2 bars in multiple locations. no other issues though, phone is very fast and easy to operate and battery is what to be expected on this type of phone as far as I am concerned.

Similar Messages

Galaxy Nexus display+ problems

My 12-day old is Galaxy Nexus acts as though it's possessed. The display flickers. Phone goes in to applications and screens without my commands. For example, in the txt mode, the keyboard screen goes from qwerty screen to numeric screen by itself. When I try to return to the qwerty screen, the voice-to-txt screen pops up. Another example is the phone going to URLs and opening articles without my ever touching the link in Google News.
I first noticed the "possessed" behavior on the very day I got the phone. Because I had the 4G reception problem, which VZW told me was a 4G network issue, I blamed the erratic behavior on the network issues. Since then, I have encountered the flickering screen and erratic behavior a few more times. But last night, the erratic behavior continued for hours.
Has anyone encountered similar problems? As much as I like my Galaxy Nexus, I may have to return it....

Make sure that your fingers are not damp or have hand cream on them. Having moisture while using a touch device (smartphone or mousepad) will result in erratic behavior.
If you know that your fingers are not damp, then exchange it for another unit.

Problems with the Galaxy Nexus

I upgraded to the Galaxy Nexus – your flagship device. It now has a whole laundry list of known, critical issues. You’re holding the Android software update that will fix these known problems but you won’t release it. After 5 months, still no fix. Even while the Sprint Galaxy Nexus has Android 4.0.4, we're stuck on the the buggy 4.0.2.
Now that you have me locked in a contract the only thing you’ll do is replace my phone with the same model that’s refurbished – not even a new phone of the same model. And it would come with the same software version. You won’t even replace my phone with a different model that works as expected. I’m just one of many, many people in this situation. Let’s see where JD Power and Associates ranks your customer service next time, Verizon Wireless. Shame on you! Even your own forums are filled with complaints from Nexus owners and still VZW remains silent. This is **** poor customer service and it has definitely been noted by me and many others.

Now that 4.0.4 is slowly being released, I'm yet to hear anyone say that the intermittent muting problem, the random resets, or any of the other problems have actually been fixed. I found an app that helped with the 3G dropping problem, but that was on the last phone, and I don't remember the name. I'm sure it is in the My Apps section somewhere. Not going to bother since I'm going to ask for another replacement phone soon.
I was told by a rep that I had to receive three phones before Verizon would give me a different model. I'm on number 3, but their records only show 2 replacement phones. I guess the one I got 3 days from original purchase didn't count 'cause I got it from the store and not through customer service.
Anyway I'd like to see a list of the bugs/problems that 4.0.4 actually fixes. What I've seen is a list of new problems.
My biggest frustration is that verizon doesn't/won't even admit they have a problem. If they would just give the reps a line or two about the problems and send us to tier 2 or 3, it would be different, but tier 1 wants to try everything on their list of fixes before they will let us talk to a tech that at least knows there is a problem, however won't say so directly. I'm fed up with Verizon and it's time to do something. I'm looking at the other 4GLTE verizon phones and they seem to have problems too. I'm not an apple fan so there really isn't anything that Verizon has that I want to downgrade to, except maybe a phone that I don't use and just pay the base for the remainder of the contract.
I hate liars and by withholding the truth, it makes Verizon Wireless reps look like liars.
ok I've said too much, but seems like a good place to rant for a while. Thanks for listening.

Galaxy Nexus: No 4G signal After Update to Android 4.02

I purchased a Galaxy Nexus today, connected to 4G, downloaded ap's and used the phone on 4G for approximately an hour today with no issues. I was then altered to an update for Android 4.02.
After completing the update, I am no longer able to get 4G in most places. When I can get 4G, it is very weak.
For comparison, in the same spot, a Rezound will get 4 bars of 4G and the Galaxy Nexus will not connect to 4G (just 3G). I have confirmed this behavior on both of the Galaxy Nexus' purchased by our company.
Has anyone else seen this behavior with the 4.02 update? I have tried rebooting the phone as well as a hard reset, no luck. An hour on the phone with a Verizon 4G specialist with no luck.
Help.

As others I am in the same boat. Picked up the Nexus after I got off work yesterday. Original downloads were quick as the phone was synching and installing my apps and gmail account. Once that was done the rep installed the extended battery and booted the phone and then from what I can tell, installed the update since while I was leaving the store (corporate store) it rebooted. I did not pay much attention as I was headed to another job. Got there and was on wifi and then wifi when I got home. Came to work today and was looking at my connection, which has been great before on my Bionic for both 3G and 4G and have a very weak 3g running at 117-120 dBm and no 4G at all. I will be going into town for a Dr's appt adn will see how it is there (still a stong 4G area). More than likely will be going back to the VZW corp store and see what they have to say.

Samsung Galaxy Nexus Android 4.2 Update

When will Verizon approve the Android 4.2 update for the Samsung Galaxy Nexus? The slowness of Verizon to approve updates is inexcusable! And to that I'll say, "I'm done!" I am so disgusted with Verizon and their inability to provide updates to what is supposed to be a "Nexus" device. It's not like they have to manipulate around manufacturer software. It's pure Google operating system. Load and test the drivers for CDMA and LTE and then launch the update. At the MOST that should take no more than 2 weeks! Since I have had my Nexus on Verizon, I have not recieved a single update prior to 2 months! Android 4.2 update from Android 4.1 is so miniscule and, might I add, required no additional new drivers, so what is the hold up Verizon? Where is the Android 4.2 update? And, yeah, I know some techy out there is going to say, " well why don't you just jailbreak and load it yourself?" Because I shouldn't HAVE to jailbreak my phone. It's not a matter of can I do it, it's why can't I do it without jailbreaking from Verizon? They sold this phone initially by claiming it to be a "pure Nexus" device and it's been nothing of the kind ever since! So I say, "I'm done!" That means that when my contract is up, I'm return to AT&T! They have upgraded the towers in the area that I live and my friends on AT&T say their signals are even better than Verizon's. AT&T's new LTE towers download at faster speeds than Verizon's too. I would have happily stayed with Verizon if they would have only taken the Pure Nexus experience seriously!
To those who have stated that I've said this for Jelly Bean 4.1, you are correct! The only reason I'm still here is because of the hefty penalty Verizon will charge me for terminating my contract early. My contract doesn't expire until December 2013 so it would be a rather hefty penalty to pay. But Android 4.2 has confirmed that Verizon refuses to change their position on slow updates, so when my contract is up (as I believe I stated on 4.1), you won't see REDNIBKRAM on Verizon anymore!
It appears as though the Verizon "love freaks" just can't seem to get the message. I'm not saying that the updates aren't difficult, I'm saying that if Verizon chooses to use CDMA technology over GSM and that requires them to jump through hoops to get updates completed, then they should have NEVER agreed to carry a "pure Nexus" device, or at the very least, should have NEVER advertised the device as such. My whole point is that Verizon LIED TO ME and told me that my phone was a "pure Nexus" device when I purchased it and switched from a GSM phone company (AT&T) when, in fact, they knew that I would NOT be getting updates directly from Google as the GSM versions of the SGN do. At the very least, if Verizon really wanted to make this right, they would offer to allow anyone with a SGN phone who was lied to when they purchased it to exit from their existing contract without penalty, so we can purchase a "TRUELY PURE NEXUS" phone direct from Google or provide us with a choice of another phone (Windows Phone, iPhone, etc.) without having to renew a 2 year contract.
All I'm saying is that if Verizon won't or can't update the phones they themselves advertised as a "pure Nexus" phone, then they should make it right to the people they lied to.

I didn't go back to AT&T for JB in August because the of VERY HEFTY penalty I will have to pay for cancelling my contract early and I got the Android 4.1 JB update. Once I received the update and because the the penalty, I decided to give BIGRED another change at the next update. I thought, "maybe it was such a huge update that they really needed to make sure everything was done right." So, now here we are waiting for the 4.2.1 update and I'm still getting the same response from BIGRED as I got for JB 4.0 update. It's quite clear that VZ DOESN'T CARE about customer satisfaction. They use the excuse that they want their network to be the best and they want their phones to operate with little or no problems, yet when problems ARE discovered, it takes them months to send out the updates that Google has already released months prior. I have discussed updates with Verizon, Google and Samsung support personnel. I have even contacted Verizon Corporate and I fully understand the process by which updates are done, and believe me when I say that the update process at VZ is in serious need of restructuring. Especially when it comes to Android devices. But as far as this Android 4.2.1 update is concerned, I have spoken with Google and they have informed me that there was NO changes made to the operating system that would affect the CDMA or LTE drivers on the Verizon Samsung Galaxy Nexus, so there should be no reason why Verizon would not want to release the update. The small changes (additions) to the operating system would in no way affect the communications on VZ. So why hasn't VZ released this update yet. Corporate says they need to test the software to ensure it doesn't affect communications on their network, yet Google hasn't changed anything in the operating system that would, so what are they testing? VZ may have the better network, but CARRIER EXPERIENCE ISN'T ALL ABOUT THE BEST CONNECTION. It's about customer SATISFACTION and not receiving updates on a pure NEXUS device in a timely manner is inexcusable and in NO WAY SATISFYING! So when my contract is up, I will be returning to AT&T or giving T-Mobile a try on a pure Nexus device with no contract!

Galaxy Nexus 4G

Good Evening Everyone,
So i recently got a replacement phone for my fualty/disfunctional android II. This phone replacement phone turned out to be the Galaxy Nexus 4G. I had not read the known errors or any issues with the phone previously. However, after activating the phone i noticed there was some signal strength issues/4g dropping in and out. I also noticed that when checking the phone signal strength under status that the Bdm was fluctuating between -99 and -115. However, other phones in the house on verizon were sitting at a cool -78 through -84. This would be optimal to great service. So i called into tech support the guy told me that yes there is an issue with how the phone interprets the phone but it should not be such a low signal strength. So they sent me a new phone, the new phone had the same problem. Called back they just said its a signal reading issue with the phone.
I looked up some known issues and there was mention of an update to be released in the fall of 2012 to fix the issue. However, i am not finding if this update was ever released. My phone is still occurring the signal strength problem. What if anything can i do to remedy this?
thanks
mike

Good morning sir,
I am currently on my second sim card with my second device. After spending a good deal of time speaking with a tech support Representative on my first call, i asked the guy if there were any known issues with the device outstanding. The guy read a comment or an internal PSA that said the device is known to have signal issues in which is does not read the depth of signal as other phones do. It also said that samsung knows about the problem and was working to put out an update. However, this internal PSA was october of last year and if they did put out an update its not working. I am curious to know if this is still a known issue and any plans to fix are in order?
Also if you think getting a 3rd sim card could possibly remedy the issue i will gladly do so.

Verizon Galaxy Nexus - Defective Charging Port

Bought my Galaxy Nexus in April of 2012, along with insurance on the phone. Love the phone and the pure Android experience. However, back in February, I woke up one morning and noticed that even though my phone was plugged in, the battery was not charging. I tried using different cords and my spare battery, neither fixed the issue, which meant that the charging port on the phone was defective. I brought it to a VZW store, and since the issue occurred within a year of purchasing the phone, they sent me a certified pre-owned galaxy nexus as a replacement (They had to send me three replacement phones total because the first two would not boot properly, but that's a different story.)
So here I am, 5 months later, and I woke up one morning and discover the same issue. Phone is plugged in (using the original charger that come with the original phone by the way), but it is not charging. Won't charge with a different cord, won't charge with a different battery, which means that the port is defective. I take the phone to the Verizon store, and am informed that A) my year-long warranty has run out, so if I want to replace the phone I will have to pay full retail price for it, and B) The default insurance plan on these phones only covers cracked screens or lost devices. The VZW support rep actually suggested that I damage the screen on the phone before sending it to the insurance company, because otherwise they would send it back and refuse to replace it.
So to recap, Verizon sold me a defective device, replaced it with another defective device, and now in order to fulfill the remaining nine months of my contract with them, I will have to purchase another device at full retail value. That's $600-$700 I'm expected to pay just to continue adhering to the terms of my contract. For now, I went on amazon and bought an external battery charger which I now have to carry with me at all times, which is an unacceptable solution for the next nine months. Surely there has to be a better option?

This is the same problem I had in the past and Samsung fixed the phone
under warranty. Since a warranty is only 1 year and not the length of the
contract it doesn't help anymore. I do not have insurance and the phone
has never been wet. I have to wiggle the port or reset something on the
connect to have it charge properly. Verizon was unwilling to help me the
last time I had this issue since I purchased the phone new from Amazon. I
would appreciate it if you could help.
On Mon, Aug 26, 2013 at 12:32 PM, Verizon Wireless Customer Support <

Galaxy Nexus: To return or roll the dice on an update? The issues had by many, the Q's we all have.

Hey all,
I'm in a bit of a pickle and was curious what other nexus owners would have to offer. First of all, Im not just trolling the boards, Ive been doing a lot of extensive research on these problems and have found that Im not the only one experiencing them and, at least until this fabled 4.0.3 update comes along, there is no real "fix" except perhaps to swap out the phone and hope it doesnt act the same way, or continue going around with a phone you paid 5 bills for, knowing that it works worse than your treo 750 of yore. So let me explain the deal...
I got the GNex on the 15th, one of the first in line. I love the phone (screen quality, ICS, camera, etc) but have since had a fair number of issues. The battery problem, well, its a 4G phone with a huge display so I can live with the fact that I have 2 batteries for it and one extended. Im not complaining about it being a juice hog (it is), I can live with that. Furthermore, theres a lot of speculation that the juice problem is a correlation of the 4G "lock on signal issue" that myself and many others are having, and that if verizon/google does release this next update, it should eliviate both issues. The main issue with my signal is the fact that I cant lock on to a good 4G or 3G signal. After turning on the screen, the phone searches for 4G, eventually aquires a signal but will also eventually lose it and be in "data limbo" where its unable to get to a stable 3G signal and hovers below 1X, being effectively useless for a phone or mobile data device. The area I live in has fine 4G and even better 3G, yet when I've tried to set the phone to 3G as the preffered network, it has an even tougher time aquiring a 3G signal than it does a 4G one. It just seems to always be looking for 4G, which is a possible reason for the battery woes myself and a great deal of us are going through. Im upset that Verizon did acknowlege there was an issue with the phones signal and that it would be addressed via update, but then 2 days later, pulled a 360 and said that "there is no performance issues with the phone whatsover and the update 4.0.3 will address a problem with the signal reading of the phone". This is upsetting. I was in my local verizon store, where, god bless em, they didnt even know how to look up the signal strength on the phone, let alone how to interpret the numbers. I showed the "tech support" woman my signal strength of -75dbm in contrast to a driod razors of 55db, and she immedietly said "Oh, see! You have a stronger signal. Thats good." I then told her that 75 is a horrible signal compared to 55 and she managed to wipe the egg of her face, looking fine in her verizon skirt but not knowing anything when it comes to the questions I had at hand.
Recently my phone has been having the random reboots that a great deal of us have had aswell. Once while driving and listening to music via bluetooth and last night after shutting the phone down, it immedietly rebooted. (Google nexus auto reboot and youll see what im talking about). Its happened a few more times than this, but these times are the ones I remember exactly what I was doing with it, and, lets face it, 1 reboot for a new GNex is one too many; this phone is too hardcore and beefy to suffer from reboots. My phone is not rooted and I have minimal apps installed from my HTC incredible, most of which are news reading apps like CNN or google currents, which arent running in the background and only use data when I open the app. I havent even been executing any apps with regular frequency except google music which I use on the regular. Im about to do another hard reset and install no apps at all and see how it fairs. The signal issue is one thing, and I am hopeful that it will be addressed in this next update, but the fact that I dont have a lot of apps (especially any that I would see causing a hardware conflict needing a reboot) and Im still getting this occasional reboot, is troubling, to say the least. Again: I absolutely love this phone. Im a gadget freak, have had many a smartphone and I really like the formfacter, OS and screensize/density of this device. Its also my first nexus device, which I've waited for since the nexus one came out on Tmobile and I was still loyal to big red. I like the nexus line because its to be the hackers phone, a phone for developers, freakers, pirates, what have you. Ive always loved that idea, as I wear a few of those hats but...my confidence is sorely shaken.
I have until the 15th to take the phone back and am toying with the idea of swapping out one for a "newer" one, as Ive read that people with compaints similar to mine have done so and had great success with their "newer" replacement phones, but theres also the possibility that this is just a problem with the GNex as a whole, or a large batch of em so that I could switch out again and again and I'll always get one with a defect of some kind, that wont be able to be fixed with an update, and I'll be stuck with my super expensive, super awesome phone that works poorer than a cheap prepaid moto flip phone.
Im wondering if anyone else is having these issues and how they plan about going about it. In my mind, if I swap out this phone and am stuck with another "lemon"(if thats even the problem, a QC issue) then Im stuck with that one indefenetly. I talked to the verizon rep in the store and asked that if I wanted to bring it back for a refund, to wait until the bugs are officially sorted out, would I have to pay the restock fee? The answer was an absolute and cold "yes". Im cool with restock fees, but not if the device I bought has any many issues as this phone I have, and many of you out there as well. Im very torn. I've had a taste of ICS and dont wanna go back to anything else. Its possible to wait till ICS comes to the Droid Razer, which had a nice screen, better battery life and a signal stronger by 20dbm then the GNex. Also, I havent seen nearly as many problems with reboots, forceclosing and droped signals as with the GNex. But still...I just want the GNex to be "the one".
Anyone have any experience swapping out their phones for "newer ones"? The woman at verizon did a hard reset and noted it in my account but would not yet do a sim card swap or reactivation, as (Im guessing) she just wants to take away as much time from me as possible before the 15th comes. A hard reset does nothing. I still get the reboots and signal issues with a clean slate. Do we think, for sure that the issues myself and a lot of you are in fact software related, eble to be fixed via updates? Or is it still possible that this device is mechanically flawed? And that if we stick with out GNex's, even though we love how they feel in our hands, the screen, the OS, the google branding, that we will be stuck with something of inferior performance/stability? I know my question is kinda broad and not too specific. Im asking a lot, from any direction, any input from someone not wearing a verizon badge will help. The clock is ticking. I love this phone, I just want it or the replacement I get to work and be stable and it scares me, pinning my hopes on a replacement device or an update that has yet to surface, whose original purpose was to "fix signal issues with regards to the GNex" but now, it seems, is meerly out there to "better visualize an accurate signal strength" of a device that supposedly "doesnt suffer from any perfomance issues at all". Im guessing big red has never had their brand new top of the line GNex reboot on them while shutting down or simply doing its job: to serve as a mobile device.
Thanks for any and all input on what to do. Its like asking a buddy if the girl your seeing is right for you. All I want is some honest input as I am head over heels, less the fact that she doesnt work all the time and is so unstable she needs meds of some kind.
Cheers.

Wow, well thanks for your replies guys. Thanks for not bashing me or anything like that. Its a very tough predicament a lot of us seem to be in. I have a problem with hyping myself up for things. I will never forgive George Lucas for the last Indiana Jones movie, but this device, its so much more personal. Our phones are all extensions of us and the fact that I and others have been salivating for this phone for quite some time, only to run into a bevy of issues, well...it doesnt make it any easier, as I still wanna believe in this phone. I still want it to be my daily driver. Im just glad Im not the only one stuck between a rock and a hard place. I had a pretty unflatering day with it today, with a couple of data conection issues, then went back to 3G mode have still had terrible servie (in a well lit 3G area) as well as battery woes. Im gonna go to verizon this upcoming week but its really hard trying to formulate a game plan. If I exchange it than I feel as though I've made my bed with this phone, for the next two years, but if I return it, Im still going to have to pay 15% of the $500 I forked out for it, to have only rented a lackluster nexus for 2 weeks. This...is not right. I stil dont have an answer, but im glad there are others like me. I still do like it, its like your mother meeting a chick and saying "shes not right for you" but you still find yourself talking through her logic and reasoning, hoping your still togather in the coming months.
I was wondering, Ive been thinking about the warrenty procedure with verizon and the nexus. I do have the full insurence but am not sure if I make a claim, weather or not they will send me a refurbished or used device (I dont want that). If I wait and dont exchenge or return it, or even if I do exchange it and still run into problems, will the warenty cover me if a hardware flaw is discovered on these earlier batches of nexus'? Im not new to being a first adopter to technology and Im not a fan of the whole iphone fad, but I did wait outside ATT for the first gen iphone and was much more happier with that thing than this. I didnt have a quarter of the problems of dissatisfication as this thing. The word "bugs" is completely understated when talking about my experience thus far. Just wanna make sure Im covered. I dont know how much big red really has our backs and Im not fabricating the problems I and others have faced. I think we all deserve a pat on the back for being so paitent and willing to continue to give our GNex's more chances. I trust google too, or, at least I want to. I really hope I make the right decision and it all works out. I was reading another review today which said a scary reality that I cant stop thinking about. In a few months we're sure to see a bevy or 4.0 devices and when that comes, the GNex may lose its one redeaming attribute. If it still has these types of problems (Signal issues, reboots, stabilty, batt power, etc) then we are stuck with what is basically an outdated lemon for the next two years. A lemon that was supposed to be king of the hill for some time, and which we all paied way, way too much for. Im sad I missed out on the Nexus one and even sader about the Nexus S. I know the S has had similar issues when it first came out, I just am scared going day to day, hoping a fix arises.They were eventually fixed (for the most part). Hoping so with this device...its just a terrible feeling as Im unhappy yet want it to work, desperatly.
And 21stNow: I like your question of weather or not I'd be willing to put up with this stuff until March 2012...I can answer right now, unequivocally yes. I love the phone (or atleast I want to love it that much). But Im very scared in the possibility of there being a major hardware issue or them just never correctly addressing the issues, leaving us GNex users out on the learch. Ive seen it with other pieces of tech. The fact that big red admitted there was an issue then turning around and saying that theres nothing wrong with the phone is a slap to myself and every one else whose had signal problems, reboot issues, etc. Furthermore, the fact that I got a phone that doesnt work as well as others who rave about not having one of these issues is disturbing. So I and others just got bad luck, with a bad batch? I find that hard to believe. We paid just as much, if not more (I had to get the accessory pack with my store when I bought it so that jacked up the price considerably) and should not be the black sheep of the gang, while others run free without issues or worries about their beloved device.Why cant either all the GNex's either work 100% or not? Its terrible, hearing both sides of the experience. This is what keeps me up at night while the clock nears the 15th. But at least I still have a horse in the race as I have yet to take it back indefentely.
We are not alone in our feelings and troubles.

Can't mount my Galaxy Nexus correctly with MTP

Hello everyone,
I am posting because I can't mount my Galaxy Nexus correctly and I am not sure where the problem is. I am glad for any pointers. I am basically following the Arch Linux Guide to MTP, so moving along I get these outputs:
[root@Caduceus parcival]# mtp-detect
Error: Unable to open ~/.mtpz-data for reading.
libmtp version: 1.1.5
Listing raw device(s)
Device 0 (VID=04e8 and PID=685c) is a Samsung Galaxy models (MTP+ADB).
Found 1 device(s):
Samsung: Galaxy models (MTP+ADB) (04e8:685c) @ bus 4, dev 4
Attempting to connect device(s)
Android device detected, assigning default bug flags
Error 1: Get Storage information failed.
Error 2: PTP Layer error 02fe: get_handles_recursively(): could not get object handles.
Error 2: Error 02fe: PTP: Protocol error, data expected
USB low-level info:
Interface has a kernel driver attached.
bcdUSB: 512
bDeviceClass: 0
bDeviceSubClass: 0
bDeviceProtocol: 0
idVendor: 04e8
idProduct: 685c
IN endpoint maxpacket: 512 bytes
OUT endpoint maxpacket: 512 bytes
Raw device info:
Bus location: 4
Device number: 4
Device entry info:
Vendor: Samsung
Vendor id: 0x04e8
Product: Galaxy models (MTP+ADB)
Vendor id: 0x685c
Device flags: 0x48008107
Configuration 0, interface 0, altsetting 0:
Interface description contains the string "MTP"
Device recognized as MTP, no further probing.
Device info:
Manufacturer: samsung
Model: Galaxy Nexus
Device version: 1.0
Serial number: 01498B301401B014
Vendor extension ID: 0x00000006
Vendor extension description: microsoft.com: 1.0; android.com: 1.0;
Detected object size: 64 bits
Extensions:
microsoft.com: 1.0
android.com: 1.0
Supported operations:
1001: get device info
1002: Open session
1003: Close session
1004: Get storage IDs
1005: Get storage info
1006: Get number of objects
1007: Get object handles
1008: Get object info
1009: Get object
100a: Get thumbnail
100b: Delete object
100c: Send object info
100d: Send object
1014: Get device property description
1015: Get device property value
1016: Set device property value
1017: Reset device property value
101b: Get partial object
9801: Get object properties supported
9802: Get object property description
9803: Get object property value
9804: Set object property value
9805: Get object property list
9810: Get object references
9811: Set object references
95c1: Unknown (95c1)
95c2: Unknown (95c2)
95c3: Unknown (95c3)
95c4: Unknown (95c4)
95c5: Unknown (95c5)
Events supported:
0x4002
0x4003
0x4004
0x4005
Device Properties Supported:
0xd401: Synchronization Partner
0xd402: Friendly Device Name
0x5003: Image Size
Playable File (Object) Types and Object Properties Supported:
3000: Undefined Type
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME FORM READ ONLY
3001: Association/Directory
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME FORM READ ONLY
3004: Text
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME FORM READ ONLY
3005: HTML
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME FORM READ ONLY
3008: MS Wave
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dce0: Display Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME FORM READ ONLY
dc46: Artist STRING data type READ ONLY
dc9a: Album Name STRING data type READ ONLY
dc9b: Album Artist STRING data type READ ONLY
dc8b: Track UINT16 data type ANY 16BIT VALUE form READ ONLY
dc99: Original Release Date STRING data type DATETIME FORM READ ONLY
dc89: Duration UINT32 data type ANY 32BIT VALUE form READ ONLY
dc8c: Genre STRING data type READ ONLY
dc96: Composer STRING data type READ ONLY
3009: MP3
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dce0: Display Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME FORM READ ONLY
dc46: Artist STRING data type READ ONLY
dc9a: Album Name STRING data type READ ONLY
dc9b: Album Artist STRING data type READ ONLY
dc8b: Track UINT16 data type ANY 16BIT VALUE form READ ONLY
dc99: Original Release Date STRING data type DATETIME FORM READ ONLY
dc89: Duration UINT32 data type ANY 32BIT VALUE form READ ONLY
dc8c: Genre STRING data type READ ONLY
dc96: Composer STRING data type READ ONLY
300b: MPEG
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dce0: Display Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME FORM READ ONLY
dc46: Artist STRING data type READ ONLY
dc9a: Album Name STRING data type READ ONLY
dc89: Duration UINT32 data type ANY 32BIT VALUE form READ ONLY
dc48: Description STRING data type READ ONLY
3801: JPEG
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dce0: Display Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME FORM READ ONLY
dc48: Description STRING data type READ ONLY
3802: TIFF EP
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME FORM READ ONLY
3804: BMP
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dce0: Display Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME FORM READ ONLY
dc48: Description STRING data type READ ONLY
3807: GIF
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dce0: Display Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME FORM READ ONLY
dc48: Description STRING data type READ ONLY
3808: JFIF
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME FORM READ ONLY
380b: PNG
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dce0: Display Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME FORM READ ONLY
dc48: Description STRING data type READ ONLY
380d: TIFF
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME FORM READ ONLY
b901: WMA
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dce0: Display Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME FORM READ ONLY
dc46: Artist STRING data type READ ONLY
dc9a: Album Name STRING data type READ ONLY
dc9b: Album Artist STRING data type READ ONLY
dc8b: Track UINT16 data type ANY 16BIT VALUE form READ ONLY
dc99: Original Release Date STRING data type DATETIME FORM READ ONLY
dc89: Duration UINT32 data type ANY 32BIT VALUE form READ ONLY
dc8c: Genre STRING data type READ ONLY
dc96: Composer STRING data type READ ONLY
b902: OGG
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dce0: Display Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME FORM READ ONLY
dc46: Artist STRING data type READ ONLY
dc9a: Album Name STRING data type READ ONLY
dc9b: Album Artist STRING data type READ ONLY
dc8b: Track UINT16 data type ANY 16BIT VALUE form READ ONLY
dc99: Original Release Date STRING data type DATETIME FORM READ ONLY
dc89: Duration UINT32 data type ANY 32BIT VALUE form READ ONLY
dc8c: Genre STRING data type READ ONLY
dc96: Composer STRING data type READ ONLY
b903: AAC
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dce0: Display Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME FORM READ ONLY
dc46: Artist STRING data type READ ONLY
dc9a: Album Name STRING data type READ ONLY
dc9b: Album Artist STRING data type READ ONLY
dc8b: Track UINT16 data type ANY 16BIT VALUE form READ ONLY
dc99: Original Release Date STRING data type DATETIME FORM READ ONLY
dc89: Duration UINT32 data type ANY 32BIT VALUE form READ ONLY
dc8c: Genre STRING data type READ ONLY
dc96: Composer STRING data type READ ONLY
b982: MP4
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME FORM READ ONLY
b983: MP2
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME FORM READ ONLY
b984: 3GP
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dce0: Display Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME FORM READ ONLY
dc46: Artist STRING data type READ ONLY
dc9a: Album Name STRING data type READ ONLY
dc89: Duration UINT32 data type ANY 32BIT VALUE form READ ONLY
dc48: Description STRING data type READ ONLY
ba05: Abstract Audio Video Playlist
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME FORM READ ONLY
ba10: WPL Playlist
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME FORM READ ONLY
ba11: M3U Playlist
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME FORM READ ONLY
ba14: PLS Playlist
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME FORM READ ONLY
ba82: XMLDocument
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME FORM READ ONLY
b906: FLAC
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME FORM READ ONLY
Special directories:
Default music folder: 0xffffffff
Default playlist folder: 0xffffffff
Default picture folder: 0xffffffff
Default video folder: 0xffffffff
Default organizer folder: 0xffffffff
Default zencast folder: 0xffffffff
Default album folder: 0xffffffff
Default text folder: 0xffffffff
MTP-specific device properties:
Friendly name: (NULL)
Synchronization partner: (NULL)
libmtp supported (playable) filetypes:
Folder
Text file
HTML file
RIFF WAVE file
ISO MPEG-1 Audio Layer 3
MPEG video stream
JPEG file
BMP bitmap file
GIF bitmap file
JFIF file
Portable Network Graphics
TIFF bitmap file
Microsoft Windows Media Audio
Ogg container format
Advanced Audio Coding (AAC)/MPEG-2 Part 7/MPEG-4 Part 3
MPEG-4 Part 14 Container Format (Audio+Video Emphasis)
ISO MPEG-1 Audio Layer 2
Abstract Playlist file
XML file
Free Lossless Audio Codec (FLAC)
OK.
[root@Caduceus parcival]#
[root@Caduceus parcival]# mtp-connect
Your system does not appear to have UTF-8 enabled ($LANG="en_US.utf8")
If you want to have support for diacritics and Unicode characters,
please switch your locale to an UTF-8 locale, e.g. "en_US.UTF-8".
Error: Unable to open ~/.mtpz-data for reading.
libmtp version: 1.1.5
Device 0 (VID=04e8 and PID=685c) is a Samsung Galaxy models (MTP+ADB).
Android device detected, assigning default bug flags
Usage: connect <command1> <command2>
Commands: --delete [filename]
--sendfile [source] [destination]
--sendtrack [source] [destination]
--getfile [source] [destination]
--newfolder [foldername]
[root@Caduceus parcival]#
[root@Caduceus parcival]# lsusb
**clipped irrelevant devices**
Bus 004 Device 004: ID 04e8:685c Samsung Electronics Co., Ltd GT-I9250 Phone [Galaxy Nexus]
[root@Caduceus parcival]#
The content of /etc/udev/rules.d/51-android.rules:
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", ATTR{idProduct}=="685c", MODE="0666"
[parcival@Caduceus ~]$ mtpfs -o allow_other /mnt/galaxy/
Error: Unable to open ~/.mtpz-data for reading.
Listing raw device(s)
Device 0 (VID=04e8 and PID=685c) is a Samsung Galaxy models (MTP+ADB).
Found 1 device(s):
Samsung: Galaxy models (MTP+ADB) (04e8:685c) @ bus 4, dev 4
Attempting to connect device
Android device detected, assigning default bug flags
Error 1: Get Storage information failed.
Error 2: PTP Layer error 02fe: get_handles_recursively(): could not get object handles.
Error 2: Error 02fe: PTP: Protocol error, data expected
Listing File Information on Device with name: (NULL)
LIBMTP_Get_Storage() failed:-1
[parcival@Caduceus ~]$
Although it doesn't mount properly, Rhythmbox recognizes and lists the Galaxy Nexus in its GUI. I can even look at the device's properties window. Rhythmbox fails to list any files already on the Galaxy Nexus, though, and I can't transfer anything to it as the following error message in Rhythmbox appears:
Error transferring track
Unable to send file to MTP device: PTP Layer error 02ff: send_file_object_info(): Could not send object info.
Googling for Error 2 brought up some Ubuntu posts from Dec 12 when they had a bug in libmtp 1.1.1, but the current version installed on my system is 1.1.5-1 from the Arch repositories.
Thanks for any help in advance.

@all: so you are basically telling me that my Galaxy nexus should properly mount despite the error messages in my Terminal?
@k.sarend: thank you, I'll try that once I get home.
@mzneverdies: interesting point... I didn't think the choice of the DE would have any impact on mounting devices, that's why I posted in the Kernel & Hardware Support section.
(on a side note: I was a Linux user from 2001-2004 and had KDE as my primary desktop. I just came back to (this time Arch) Linux two weeks ago with a new box and I decided to install Gnome since it seems to have progressed more... but really, I am open for both DEs, I'm not a fanboy/evangelist or anything)

Verizon's Handling of Galaxy Nexus

It seems to me that Verizon doesn't even really want the Galaxy Nexus or never did. I don't think Verizon can stand the fact the phone is free of all of their bloatware that they love to load down the phones that are on their network. No VZ Navigator or Verizon Video or Verizon Music. They barley advertised the Galaxy Nexus compared to the Motorola Droid Razr family of phones. The fact that the phone has had numerous problems since it was launched and they the fact that 5 months later only their version of the phone is the only one not to be updated to try and correct the issues just shows that the Galaxy Nexus is not high on their list of priorities. They only reason I stayed with Verizon was my unlimited data and because Verizon was suppose to get a Nexus phone phone, but as unlimited data is going away and the Galaxy Nexus is a Nexis in Name only, and I highly doubt that Google will ever launch another Nexus on Verizon after this disaster, I'm going to switch to Sprint or ATT. Both of those offer excellent phone at responsible prices. I know that there is a relatively small percentage of Android users that drool over Nexus phones, but its that small percentage that sway people away from purchasing certain phones. I've already talked a number of people out of getting a Galaxy Nexus at my local Verizon store.

I started service with Verizon back on Feb 08, 2012 after being with Sprint for the past 12 years. What a mistake... My reasons for switching were access to 4Glte and the galaxy nexus phone. I paid the $600 for to nexus and away I went. Rigt out of the box the shipped devices experienced one way audio, intermittent dropping from network, and unexpected reboots.. I called Verizon tech support and the answer was we have not heard of any of these type of issues and you must have gotten a bad batch. I promptly went down to my local Verizon store that day and exchanged for 2 brand new devices. The same issues occurred... I then called technical support back and we began what I cal setting the hook game. I was told that by level 2 technical support to start marking the the one way audio voicing with ## each time it occurred and someone would get back with me within a week. A week passed and no call back. I called technical support back on several occasions and was told each time that someone would be contacting me. Almost 3 weeks into this adventure I finally received a call from tier 2 technical support stating it was not a network issue but rather a problem with the handset. They wanted to send quote "a like new device" to resolve an issue with a brand new phone and I said no. I went back to the local store and exchanged for 3 more brand new devices which brings me to a total of 3 each for myself and my wife. Guess what the same exact issues! We are now ell beyond my 14 day trial period and I call technical support again only to be told that now there acknowledgement of known issues with some of the phones.... Where was the information during my 14 day trial period? The hook is now set... This technician took me through all the previou attempts to include performing a hard reset and returning my phone to factory default. None of this worked. I was then told that there was no reason for me to continue calling as now there was a known issue and it would be addressed in a software update sometime in March. No other resolution was offered. I went back to my local store once again and exchanged my phone for the 4th time in hopes that mabe I would get lucky and capture one of the few phones that apparently do not experience these issues. The same issues. I am now up a grand total of 7 brand new galaxy nexus phones all with thesame issues. I continue to call technical support routinely and received a garden variety of responses that ranged from Ihaven't heard of this issue, calling samsung for update schedule, don't call back again with this issue as you have an open ticket, and finally the big one Verizon is not responsible for the functionality of the phone. Approximately 3 weeks ago I spokewith a representative and told them I was no longer going to sit and wait for a software update and continue to work with a phone that could not reliably sustain phone calls and stay connected to their fantastic network. She reluctantly agreed to send 2 refurbishe like new raxor max phones as a replacement. I received the phones the next day and when I opened the boxes to my surprise were 2 more nexus phones! I call technical suppor and they verified the order and stated that I should have received 1 razor maxx. They could not get the right phone or quantity rght. I told the rep dod not send anymore phones and that I would be reporting the lack of agrreed service and suppor to the Better Business Bureau and the FCC. I filed grievances with both and received a call the next dayfrom a Verizon "Corporate Manager" saying he was very sorry to hear of my issues and admitted that he had a family member as well that was experiencing the same problems. He said let me research your account and I'll call you with a few days. He called back on Friday May 18th and exclaimed the update will be to you next week. I asked how he wasable to confirm this and he said at his level there is means to be aware of these type of occurences. I then posed the big question... What happens if the software either does not launch or does not resolve the issues? His reply was that let's worry about that if the need occurs. So here I am again waiting for the legendary update.... He rally did nothing but tell me the same story wait for the update. If the resolution is not satisfactory I will be breaking the 2 year contract based on the pretense that Verizon failed to provide the services as related to phone calls and utilization fo their network. This can be proven by phone call records and time actually logged onto their network. The expectation is that the $700 ETF will be waived. Count yourself lucky that I'm not charging you for the time and trouble spent on the phone with your technical suppor, the inconvenience of not being able to make calls reliably and continuing to sell and promote a phone that you knew since January had a host of issues. I will not trcommend Verizon to any of my colleagues, friends, or family based on deception, poor technical support, and lack of a tangible resolution.

Galaxy Nexus Losing Contacts

A few days ago my Galaxy Nexus erased all of the contacts that I had added within the last 6 months or so. Now when I save a contact it is initially saved correctly, but then within a day it is again erased from my contacts. Has anyone else had this problem? Any ideas? Thanks.

ok found this dont know if it helps but I did it already and hope it works!!!!! I can understand how important missing contacts can be.I would love to get the contacts back on your device.
Do you know if your contacts were saved to BackUp Assistant? If you have an Android device, you would also have the option to save your contacts to Google/Gmail.
Have you changed your phone number? When this is done, your contacts may be lost from the BackUp Assistant sitehttp://bit.ly/xtBN5j. What happens when you do try to sync the contacts back to the device? Do you get any error messages?
Tamara H.
Follow us on Twitter @VZWSupport

Galaxy Nexus Periodic Restart / Reboot

I have had my galaxy nexus since it came out 12.15. Since then it has been rebooting itself for no apparent reason. It is occurring something like 7-10 times a day. It has happened while tethered, while the alarm was going off, while on a call, while playing music, and also while on standby.
It is not a continuous restart problem like some are having with wi-fi. Wi-Fi doesn't appear to have anything to do with my particular problem. But it is incredibly annoying.
Version 4.0.2 is installed.

timbet wrote:
I have had my galaxy nexus since it came out 12.15. Since then it has been rebooting itself for no apparent reason. It is occurring something like 7-10 times a day. It has happened while tethered, while the alarm was going off, while on a call, while playing music, and also while on standby.
It is not a continuous restart problem like some are having with wi-fi. Wi-Fi doesn't appear to have anything to do with my particular problem. But it is incredibly annoying.
Version 4.0.2 is installed.
I have had 4 reboots total since I got my Nexus on 12.16. 3 reboots happened when I was playing Angry Birds, and 1 reboot happened when I accidently initiated a phone call and ended the call as quick as I could.
If you are getting that many reboots, I would do a factory reset and do not install any apps for a couple of days. If there are no reboots, then install the apps you want a few at a time, giving time to see if there are reboots, then one of the apps is causing the reboots.
if after the reset is still is rebooting, then getting another device will be in order.

My Samsung Galaxy Nexus closes out in the middle of texting

Moved for greater exposure

unchained9 wrote:
I got the new Galaxy Nexus two days ago and have had several problems already. Although I have been able to fix everything so far, the most recent issue that I am trying to fix occurs in the middle of texting. While I am in the middle of composing a text, occasionally the phone will just completely close out and go to the main menu (where it almost always opens a new app). How can I fix this?
Thanks!
I had this happen to me too 3 times the other day. What I figured out is that when I was trying to press the spacebar, my thumb would be too close to the home screen button icon. I was actually pressing the spacebar and home screen button, causing the phone to leave the text app and go to the home screen.
Not saying this is why in your case, but something to look for. I remember reading this post, a couple of hours before it happened to me.
Have a good day

Galaxy Nexus Data Issues

So, I have no 3g/4g data connection. Went to the Verizon store and they went as far as replacing my SIM card and even the phone. Still no data. I can text and make calls just fine and WiFi works. So they had to open a trouble ticket with support. Seems other phones are working fine (lg, motorola, HTC), just not my Nexus.
Anyone else using the Galaxy Nexus having data problems?
thanks

budone wrote:
techbeck wrote:
So, I have no 3g/4g data connection. Went to the Verizon store and they went as far as replacing my SIM card and even the phone. Still no data. I can text and make calls just fine and WiFi works. So they had to open a trouble ticket with support. Seems other phones are working fine (lg, motorola, HTC), just not my Nexus.
Anyone else using the Galaxy Nexus having data problems?
thanks
Where are you located?
Freeport IL I have a trouble ticket opened and was just curious if I was the only one. I had a 1x connection for about 10min.

Galaxy Nexus not getting or sending all texts.

I have noticed the problem for about a week. It seems my phone will pick and choose which text messages to send, and which to receive. I send them to all makes and carriers. I have tried restarting my phone, and it is also up to date. I am making some people quite angry and sad by not responding, but how can I, i don't get the messages. Is there anyway to fix this?
Phone Info:
Android Version :4.2.2
Build Number: JDQ39
Model Number: Galaxy Nexus.
I am by no means a computer or phone person when it comes to trouble shooting. If more information is needed let me know!!
Thank you so much!!

Hello FizzyCrow, let's get to the bottom of this together! When the messages don't go through to send, do you receive an error message? Have you tried sending text messages manually to the numbers it doesn't go through to? What zip code are you located in? Keep us posted!
WiltonA_VZW
VZW Support
Follow us on twitter @VZWSupport

Galaxy Nexus Signal Problem

Similar Messages

Maybe you are looking for