yashsingh1/xdaforums huggingface dataset:
[Motorola Droid RAZR] alidano:
Links are down

Links are down
[Motorola Droid RAZR] pedrotorresfilho:
Hi kent_lkc

These firmwares shares same secure level and can be applied over any ICS version to latam devices.

But you should advice folks this is the an older version firmware, the otas we've got to retail.br are newer. But this firmware is really nice to have, same to that vivo you released, just in case someone need to send the device for a repair center.

Nice work, Cheers!
[Motorola Droid RAZR] Eighthourblink:
I'm not new to the flashing ROM game but I am new to the Motorola Droid RAZR. I had a Eris and laetly i had a Droid X2 but now I have a Droid RAZR (CDMA) Starting on 4.0.4 i have tried to flash over two different ROMS ( Eternity Project v3 and Eclipse)

Eternity Project flashed over just right but I had no signal connection. I think that is due to it being a GSM ROM that i later found out. Eclipse didnt flash over the first time using BOOTmenu Manager. Had to use SafeStrap. Everything looked good after reboot but after looking into it, it was should on the stock ROM.

Im kinda stuck on what to do next - i have been reading about some kind of patch? IS this what i need to install / apply? I really like the Eternity Project so if theres a way to have that - it would be nice.

Thanks EhB
[Motorola Droid RAZR] Nicoleef:
I've never heard of a patch to get GSM ROMs to work with CDMA phones I know of CDMA ones to GSM, but you can ask the developer of the ROM.
[AT&T, Rogers HTC One X, Telstra One XL] Beaucoq:
Lost my H1X today and I have some "sensitive" info on it especially in the pictures department. I know on some phones when you plug in via usb it auto mounts even if you dont put in the password on the screen...I never paid attention to whether or not the One X does this. Anyone know for sure?
[AT&T, Rogers HTC One X, Telstra One XL] stoopid2001:
I don't have a screen PW set, but if I just plug the usb in while my phone is locked it does not auto mount. I have to unlock the screen and select USB storage instead of Charge only.
[AT&T, Rogers HTC One X, Telstra One XL] Beaucoq:
Well, half way. Anyone with a screen lock have to unlock before it'll mount?
[General Questions and Answers] cfli1688c1:
i just loaded milestone on my droid x, wanting to load a custom rom on it, i went to rom manager. I click update and select milestone x and rom manager updated to a lower version. should I have select droid x?

when i boot into recover, i only have 4 options, no option to wipe?

should i go back to the higher version on rom manager?

Thanks.
[Galaxy S II Q&A, Help & Troubleshooting] ptscon:
Are there any ICS roms that have support for bluetooth message access profile? It's for accessing sms via external equipment like car decks.

Thanks
[Galaxy S II Q&A, Help & Troubleshooting] Immortalis:
Functionalities depend on module, not ROM.
[Galaxy S II Q&A, Help & Troubleshooting] ptscon:
So does that mean GSII does not and will not have MAP capability?
[Galaxy S II Q&A, Help & Troubleshooting] ptscon:
I'm pretty sure GSII is capable of doing MAP ..it's just missing the software. It uses the same Broadcom BCM4330 chip which is also found in the Nexus ..and that according to Google, supports Message Access Profile http://support.google.com/nexus/bin/answer.py?hl=en&answer=2687662
[Galaxy S II Q&A, Help & Troubleshooting] wing851:
MAP sounds like it could be incorporated into another Rom.

How can we do this?

Can the bluetooth software from the Galaxy be pulled from the phone?

Who knows how to do this?
[Samsung Galaxy Nexus] cmcfalls:
Ok, so I am on my 4th replacement Galaxy Nexus (CDMA/LTE) All of them are dropping 4G signal every 3 to 5 minutes, but sometimes will go as long as 30 minutes or an hour. Either way, there's WAY too many signal drops. And, for clarification, I don't mean low bars...I mean going from 3 or 4 bars to no connection with the "x".

My original one was I515.09. All of the replacements have been I515.10's. I know the .09 / .10 are the hardware versions (.09 make in Korea and .10 made in China I believe). My wife's does not have the problem (.09 version), my brother in law does not have the problem (.09 version) and the one in my local Verizon store does not have the problem (oddly, a .10 version).

Regardless of what Verizon and Samsung say, this is NOT a coverage issue; it is either a hardware issue or something in the software causing interference with the 4G radios (it doesn't affect 3G signals, only 4G).

The problem seems so prevalent that I decided to do a poll...who among you DO NOT suffer from the signal drop issue? And, if you don't mind, provide a little information if you don't care. I am doing this in hopes of figuring out if this affects all .10 versions (obviously it does not). And if you have a .10 and do not have the issue, I am trying to figure out what combination of roms, kernels, and radios are working for you. I know that none of the variables should affect the signal drop issue, but for some reason some kernels and radio combinations seem to do better than others..

Do you have the issue?

What is your baseband version (.09 / .10)

What rom are you using?

What kernel are you using?

What radios are you using?
[Samsung Galaxy Nexus] HeroShot:
Fellow GNex users,

I have been having this same exact problem, too. My original phone was a I515.09, purchased back in early May 2012. Unfortunately, that phone had separate issues with it and I had to send for a replacement. Here I am, two replacements later, and I am experiencing the same issues the OP has. However, with the second phone, I decided to try and isolate the problem, and in an effort to save people some time, I thought I would post what steps I have already taken to try and resolve this issue. The bottom line: I believe it is in fact a hardware-related issue with the newer phones released and/or some firmware issue that is impossible for a user to manipulate.

:::None of these solutions resolved the problem:::

Replaced both the battery and the sim card

Rooted the phone, replacing the bootloader with CWM and installing AOPK milestone-5 on 4.0.4 (full wipe)

Manually installed the latest 4.0.4 Radios (FC04/05)

Installed older Radios (EK04/06)

As for some .10 versions working, it seems there are a few .10's floating out there that have existed at the launch of the product. It must be an older version .10 that does not suffer the same hardware issues that all the new ones have. I have even heard, first-hand, of people purchasing brand new GNex's and experiencing this problem, too. Therefore, I think it extends beyond just a "replacement product" problem.

:::My Solution:::

After talking with a "level two" technician at Verizon who handles dispatching replacement phones, I have requested a notation on my account to send out a baseband version I515.09 (the technician had all .09's at his disposal at the facility, so he was certain there are some in stock, as well.)

I will update this thread after I receive my new replacement, most likely this Friday.

:::UPDATE:::

Just got off the phone with Verizon/Samsung and received some troubling news. According to Verizon, it is basically impossible to know what version they are sending you. As for Samsung, the representative said she is unaware of any problems of this magnitude with the Galaxy Nexus and does not see any updates to correct it in the foreseeable future.

Looks like we are up a creek on this one. It's a sad day, but getting a different phone as a replacement may be the only option we have.

:::FINAL UPDATE:::

Just got off the phone with Samsung. I wanted to call them directly to make sure this issue was reported. After some digging, the representative saw a ticket for a known issue with some versions of the Nexus where an error in the firmware keeps causing the modem to reset, thereby creating the constant dropped signals with 4g. There was no date scheduled for fixing this problem, but he mentioned the ticket saying it would ultimately be resolved by a firmware update over the network.

In the meantime, I did discover that the phone should function properly if you run it in CDMA mode only. I recommend moving to 3g for the time being until a patch can be pushed out to us.
[Samsung Galaxy Nexus] Ryjabo:
I did but only at my house, where coverage blows. I got a free Airave, problem solved.

Never happens when I'm out and about or at work.

Sent from my Galaxy Nexus

Sprint, the Maybe Later Network
[Samsung Galaxy Nexus] Zeinzu:
No signal issues here. CDMA/LTE.

Sent from my AOSP Android 4.1.1 Galaxy Nexus
[Samsung Galaxy Nexus] Xerodark:
I was having this problem a lot when I first got the device and was running the stock 4.0.4 and I'm on the .10 baseband. I tried a couple of the cm10 ROMs and the problem seemed to persist, but then I tried paranoid android and haven't really had an issue since. I found it to be rather odd, but so far so good since this flash.. keeping my fingers crossed that I didn't jinx something.
[Samsung Galaxy Nexus] Philosophre:
flashed paranoid android and I am still getting drops in 4g. lemon!
[Samsung Galaxy Nexus] adrynalyne:
I wish I could vote twice. No I do not. .09 and .10 devices here.
[Samsung Galaxy Nexus] icebear8:
Have not had any drop data yet, I just got my nexus about 4 weeks ago. I'm using the jelly belly rom.
[Samsung Galaxy Nexus] 3devious:
Where do you live? I'm coming over to steal one of them. I'll get away with it too because I'm going to bribe Mrs. Adrynalyne! :beer:
[Samsung Galaxy Nexus] glennj99:
I am on my second Verizon Galaxy Nexus. So far, 4G has been miserably bad here in Raleigh, NC - including right inside the Crossroads Mall Verizon company store where they swapped me a new one out for my current new one. They did that because I was going on a trip that afternoon and customer service could not get me a replacement phone in time. They checked the old phone's reception in the store and 4G came up, stayed connected for a minute or two, then dropped to an x without even going back to 3G. The salesguy told me he had never seen anything like that before and got me the replacement from stock. He said that 4G reception was perfect at this store, and smiled...

The new phone seemed better at first, but I had to go before I could really check it out. Then I was in a non-4G area during most of the next week and while only 3G was available the data connectivity seemed alright. Things did not look so good though when I got home to Raleigh after that. 4G never stays connected for more than a few minutes here now on this phone either. Locking it down to 3g seems to make it so at least 3g connectivity stays up reliable, but if it is set to Network Mode LTE/CDMA then it will stay briefly in 4G, maybe, and then drop to x and then maybe come back after a while to 3g, which is iffy. Meanwhile my wife's droid3 has a solid 3G connection and my tenant's S3 is solid 4G.

I tried the *#*#4636#*#* menu this afternoon and set the preferred network type to GSM auto (PRL) which is odd because my understanding it that this phone doesn't even have GSM hardware. That sets it into a 4G that seems to maybe stay connected better, maybe because it avoids switching to 3G as easily ?

I guess I will have to get another replacement and hope the new one has a .09 radio instead of the .10 radio like both have had before ?

I am wondering if this is a network type hand-off problem between 3G and 4G or something like that.

Glenn
[Samsung Galaxy Nexus] blackjer:
I am on .10 and havent had an issue. I got my gnex last month with 4.0.4 installed and it was fine. I then flashed the AOSP JB rom from muzzy and its been working great too. Stock kernels and radios.
[Samsung Galaxy Nexus] lrs421:
In NYC. Rev. 9. No signal dropping issues at all. Completely stock, locked boot loader.
[Samsung Galaxy Nexus] cmcfalls:
Thanks for all the replies. Looks like there are some good .10 versions out there after all.

Quick update on mine...I'm on replacement #6...or is it #7?...I've lost count. But, I know I still have the issue.

A couple of weird things though...this most recent phone was made in Korea, not China. When I opened it up and saw that I just KNEW I had a .09 version. But, alas, when I turned it on it is indeed .10. I thought all ones made in Korea were .09 and ones made in China were .10, but that doesn't appear to be the case.

And, another weird thing, this new replacement has IMM76Q on it, not 76K. I find that interesting because 76Q hasn't been pushed OTA yet that I am aware of. I actually called Verizon again yesterday and had to go through the same old song and dance with the tech guy and one of the questions he asked me was the build number. When I told him 76Q he informed me that 76Q was not the most recent update and it should be on 76K ( :rolleyes: ). I just LOVE knowing more about their devices than they do. I had to inform him that no, 76K is the most recent OTA, but 76Q is actually more recent, just not pushed out yet. He went on to accuse me of rooting my phone (which I haven't yet since it's going back...again) and installing 76Q on it.

I freaking HATE getting "specialists" who do not know what they are talking about. I know more about this phone than they do it seems.
[Samsung Galaxy Nexus] saltyteabag:
FML

Glad someone brought this back up. I'm about at my wit's end, and am seriously considering their offer to send me a RAZR. Sure I can't hack it, but at least I will have a usable phone.

Just to reduce the repetetiveness I will say I ran whatever kernel came with the ROM I was using at the time. Also, I've not experiemented with the so-called "hybrid" radio sets. All 4 phones always experienced fairly weak signal when compared to my previous phone, an OG Droid. But then again my Droid could send a text message through 3 inches of steel when I was on a ship. My work is a fringe area, so I'm going to focus on the issues I have at home, where I usually get 3-4 bars. Located in Virginia, near Virginia Beach and Norfolk.

Original Phone (bought on release day):

Reception: No major reception issues.

HW Ver: i515.09

ROM: Stock unrooted, stock rooted, GummyROM, CM9 nightlies

Radios: EK02/EK05, EK04/EK06, FA02/FA02

Replacement Phone #1:

Reception: Can hold signal for an hour or so on average. 20-40 drops per day.

HW Ver: i515.09

ROM: Stock rooted, CM9 nightlies

Radios: EK02/EK05, EK04/EK06, FA02/FA02, FC04/FC05

Replacement Phone #2:

Reception: Could not hold signal for more than 5-10 minutes. ~150 drops per day.

HW Ver: i515.10

ROM: Stock rooted, CM9 nightlies

Radios: FC04/FC05

Had the SIM card replaced at this point, while I had replacement phone #2, but it didn't make any difference.

Replacement Phone #3:

Reception: Could not hold signal for more than 5 minutes. 200+ drops per day.

HW Ver: i515.10

ROM: Stock unrooted

Radios: FC04/FC05

Most recent phone (received it yesterday) also came with IMM76Q. Couldn't tell you what the other's came with. I did try turning off 4G about an hour ago, and haven't had a single signal drop since then. <sigh> I totally don't consider this an acceptable solution. Time to call VZW again!
[Samsung Galaxy Nexus] I Am Marino:
I do not have signal drops.

Except some random 3G drops in the past day or so but I do think it's a result from a dirty flash catching up with me.

Other than that, no issues.

i515.09
[Samsung Galaxy Nexus] tailsthecat3:
I don't have signal drop issues.
[Samsung Galaxy Nexus] DirgeExtinction:
I'm on my second Gnex, with no reception issues. My first kept dropping signal at least twice a day. I exchanged it after about a week of having it.
[Samsung Galaxy Nexus] d11dog11:
My first one had that issue brand new out of the box. Got it replaced with my current one that works flawlessly. Its a baseband .10
[Samsung Galaxy Nexus] Nirodha:
Worst phone yet

I was having similar LTE drops with my Bionic (after I allowed the .905 OTA update). I ended up getting another Bionic and then another SIM. Didn't fix anything. It was obviously the latest build and god knows when the next Motorola update would be, so I got a GNex replacement. That was a mistake. I'm having worse issues with this phone than the Bionic. Can't hold a 4G signal to save my life. Heaven forbid I need to make a phone call, because that's unreliable also. VZW tier 2 tech said it's a known issue and an update is needed to fix it, but the ETA is unknown. She said some of them work and others don't, based on her own personal experience (her sister has a GNex). So I'm getting another Nexus to replace my replacement. We'll see if the next one is any better.

Current Specs:

i515.10 v.FC04/FC05

Stock Kernel 3.0.8-gda6252b

build IMM76Q​
[Samsung Galaxy Nexus] tgyberg:
On .09 / LTE and been solid all around for 7 mo's. No matter the rom, version etc.
[Samsung Galaxy Nexus] imnuts:
I've seen a .09 and a .10 without the problem, and a .10 with the issue. Since the CLNR program only really tests to make sure the radios are functional and not much else, problems like this likely aren't caught by testing. You would think they'd actually try phones for 30 minutes to see how they work before packaging them, but apparently not.
[Samsung Galaxy Nexus] DertyDOH:
had this problem, dropping every 5 seconds, thought it was just mine so I sent it to Samsung for repair under warranty (bought it off eBay so Verizon wouldn't do anything). Came back with the bootloader unlocked and IMM76Q installed. As soon as I activated it, it started dropping like before. I kinda like this better than my S3 in some ways, but no 4g makes it not logical to keep. Looks like I'll be selling my Nexus. I'm on .10
[Samsung Galaxy Nexus] glennj99:
I got a replacement Verizon gnexus by going to the local Verizon store, and demonstrating the fact that 4G would not hold even in their store.

They had no trouble admitting that dropping 4G inside their store was an obvious flaw in my phone, messed around with it a bit (factory reset, etc) that had no positive effect, then went into the back and brought me a new phone.

It was also .10

They gave me a while to setup and test this new one. It held 4G. I took it home and it gets 4G upstairs and holds it, though downstairs it holds 3G only. I think that's he best this phone and Verizon can do here.

I am not altogether happy, but I chose this phone over things like the Razor. I'll stick with it, now I have one that works, more or less.
[Samsung Galaxy Nexus] Pierceye:
I've had mine for a couple of weeks now and haven't seen any issues.
[Samsung Galaxy Nexus] Citizen_Snips:
I have never had an issue with dropping 4G on my gnex. CDMA running CNA 3.3.1. :)
[Samsung Galaxy Nexus] sbrownla:
Only in weak 4G areas and that is rare.
[Samsung Galaxy Nexus] HeroShot:
Hey guys, it's me again:

Just wanted to give you a little update, after my original post. I notice that there are quite a few out there that are experiencing the same 4G drop issues (not switching to 3G, simply dropping to no signal -X-). I decided to hold off on any more replacements for the month, knowing well that it is more likely an issue with the batch received by Verizon/from Samsung.

Yesterday, I decided to pull the trigger on authorizing another replacement. My thought is that I will give it another try and if this fails, I will send the phone directly to Samsung to have them repair the supposed "modem reset firmware issue." GOOD NEWS! I've had it out of the box and functioning, stock, for the better part of an hour and have not experienced any of the 4G drop issues. I have been able to update contacts, download 16+ apps, and during that time I have not seen a signal drop (-X-).

Looks like they may have finally fixed this issue with a new batch of phones, so I recommend reaching out for your replacement now. Do not give up on this phone just yet, because I think your issues will be resolved, just like mine seem to be. I just hope I haven't spoken too soon and jinxed myself...

Phone Specs:

Verizon Carrier LTE/CDMA

Android 4.0.4 STOCK

Baseband .10 FC04/05

Build IMM76Q

Good luck, everyone! Keep me posted and let me know if your next replacement resolves the issue.
[Samsung Galaxy Nexus] joshpersaud:
I haven't read through the entire thread but i am also having the 4G dropping issue. i'm on the .10 baseband, and will be taking my phone to best buy to see what they can do(bought it at best buy mobile).
[Samsung Galaxy Nexus] chukis13:
I honestly have not had a single signal loss since I flashed the new radio and boot loader posted by winner00 in the Verizon dev forum.
[Samsung Galaxy Nexus] 513fabe:
On ICS I used to get dropped calls all the time. Id have to stand outside in Cincinnati. Same place I got 42mbps down and 16mbps up. So I know my phone wasn't in a dead zone

Phones are warrantied for a year and Verizon will send me another one if I say I'm still having same problem.
[Samsung Galaxy Nexus] glennj99:
Less than 14days = new phone

More than 14 days = refurbished phone with probably the same problem.
[Samsung Galaxy Nexus] joshpersaud:
Returned it and got an s 3. I was the fifth person that day with the same problem.

Sent from my Jelly SIII
[Nexus 7 General] Schmeggma:
I've had my N7 for a week and a half now, and there is only one flaw: I have a 1.5cm dark band down the right side of the screen. It's only really noticeable on white or solid pale colours, so for videos and games it's fine but it's a little distracting when reading black on white.

I have only the slightest amount of backlight bleeding round the edges, even under extreme conditions (ie. full brightness in dark room,) no dead pixels, no ghosting, no issue with washed out colour. So I'm just wondering if it's worth getting a return or just waiting to see if it evens out a bit.

I haven't found any mention of similar issues on the forum, so I'd like to ask how people are finding the uniformity of the display?
[Nexus 7 General] sipo75:
same problem

I have the same defect.

How did you resolve? Did you get a replacement?
[Nexus 7 General] Fobz:
I think I might have the same problem. But with mine it only shows after having the screen off for a while, and it slowly fades to normal after the screen warms up.

So far what I have done is have all dark themes so I dont see it anymore. Have tried to refit the cables inside and using pixel fixer apps, none had worked.

Sent from my Nexus 7
[T-Mobile, Samsung Galaxy SIII] keinam.ty:
Few items I wanted to share about the way Galaxy S3 handles contacts which I don’t fully grasp. My earlier phone did not have any of those problems (Nexus S) which I accidently dropped in the pool and as a result I ended up buying the S3. My Nexus S still does not power up. I am also to this forum so please go easy on me…. Here is my list or frustrations:

1.	Pictures look tiny and small:

Why use small and low resolution to show pictures? There is enough empty space when displaying a contact.

2.	Facebook and LinkedIn always syncs entire contact network:

I cannot seem to understand how the contacts sync works. Facebook and LinkedIn accounts are always synced fully – selecting option “sync only with existing contacts” does nothing as I still end up with an address book full of people I don’t want on my phone. It always syncs entire Facebook and LinkedIn contact networks.

3.	Twitter does not sync at all.

What happened here, does anyone know? Is twitter removed from supported apps?

4.	Duplicated records:

When I turn on the sync I ended up with multiple duplicates. What does “join contacts” mean exactly?

5.	Unable to hide certain “groups” / accounts

Is there a way to hide contact on my SIM card? My good old nexus S had the ability to only display groups I wanted on the phone and this one completely disregarded that option.

6.	Reject call list

Reject list is the only part I like about S3’s contact management.

7.	Copy / edit contact’s pictures

Is there a way to copy / move pictures from Facebook or LinkedIn to Google address book?

Thanks,
[T-Mobile, Samsung Galaxy SIII] Crisisx1:
yeah i have the same issues with the facebook app syncing. when i click sync only contacts, it syncs all, and also does not sync the pictures. hmm