yashsingh1/xdaforums huggingface dataset:
[Xperia Z3 Compact Q&A, Help & Troubleshooting] Christopher Price:
Seeing as nobody seems to be able to test this, I've started searching for a D5803 to acquire. Bit of a hassle to test since the Z3c now costs more than a Nexus 6 ($299 new as of this morning).

But, I will be happy to add this to my list of do-it-yourself Android accomplishments if I pull it off :)
[Xperia Z3 Compact Q&A, Help & Troubleshooting] MGSBigBoss:
I'd be curious to know this as well, what about the z5 from Canada bell. They are a cdma company I'm told. But can't find what bands it uses from their website. I'd be willing to help if I'm able in finding out.
[Xperia Z3 Compact Q&A, Help & Troubleshooting] Christopher Price:
The Z5 should work fine on Bell. Bell stopped using CDMA in 2012, and the network will be shut down completely by 2017. It's mostly today just used for roaming from US CDMA customers.

Only the Z3v has CDMA in terms of modern Xperia phones (the last being Verizon's Xperia Play). The (potential) benefit to the Z3 compact D5803 is VoLTE on Marshmallow bypassing CDMA completely on Verizon - since Verizon has enabled VoLTE.
[Xperia Z3 Compact Q&A, Help & Troubleshooting] MGSBigBoss:
Any updates on whether or will work with verizon? Also can't lollipop bypass cdma and use volte?
[Xperia Z3 Compact Q&A, Help & Troubleshooting] Christopher Price:
Well I spent $250 (of my own money), to buy another D5803.

And guess what? Verizon is barring the device from registering on their network.

This is major for two reasons:

1) I previously used a D5803 on Verizon, it registered fine at the time as a data-only, non-VZW device

2) The barring status is only after VoLTE was added to the ROM

I'm guessing nobody else monitoring this thread has a D5803 or D6603 and a Verizon SIM, to confirm with.

But if I am correct, Verizon is violating C-Block auction rules and agreements with the FCC by barring network access to the Z3/Z3c.

I tested the D5803 with my T-Mobile SIM, and it is in proper working order.

I will contact Verizon folks tomorrow and see if I can sort this out. My guess is that the D5803 is being banned because of its VoLTE support (perhaps due to bugs in its VoLTE) - but that's no excuse, there are no exceptions to the rule.
[Xperia Z3 Compact Q&A, Help & Troubleshooting] Christopher Price:
Not as much progress, but some understanding.

When Verizon rolled out VoLTE to Android 5.1+ devices, it seems they realized Band 4 devices (like Nexus 5) could then be used on the network.

So to fix this Verizon banned all foreign IMEI's from the network. They have been patchwork whitelisting Band 13 devices as people file FCC complaints.

Case in Point: Someone filed an FCC complaint recently because their UML290 Prepaid LTE aircard was not being allowed on a smartphone SIM. Verizon surprisingly responded saying that they would comply and add UML290 PP's to the whitelist.

So it seems Verizon has a process, but is only reacting to FCC complaints. They are certainly aware of the D5803 - they just are not being proactive (as required by the C-Block mandate).

I asked the UML290 complainant to pass me the Verizon employee's contact info who responded to the FCC complaint. I haven't heard back. If I don't hear back Monday, I'll reach out to Verizon public relations.
[Xperia Z3 Compact Q&A, Help & Troubleshooting] MGSBigBoss:
You know after reading this I'm kinda appalled that business practice this blatantly bad continues with what looks to me as illegitimate practice. Only when the fcc knocks on their door will they stop? It's like a bad behaved child that keeps going until reprimanded by mom.

I'm considering taking my z3v and switching to tmobile pending the z6 release which I'd buy unlocked.
[Xperia Z3 Compact Q&A, Help & Troubleshooting] Christopher Price:
I'll stop a little bit short of that. This is an important test case. If Verizon quickly (within say, 30 days) does whitelist the D5803 & D6603... then I'll give them the benefit of the doubt.

Verizon can make a good case for blacklisting "unknown" LTE devices, until they find a valid Band 13 device to whitelist. Imagine someone activating a Nexus 5 on Verizon? They would be denied CDMA registration, and only have access to LTE Band 4. That would cause signal and other issues - even if VoLTE worked properly.

So, I get why Verizon is doing this - but the real lynchpin will be reacting quickly when someone wants them to add a LTE Band 13 device - as required by the FCC mandate.
[Xperia Z3 Compact Q&A, Help & Troubleshooting] MGSBigBoss:
Well let me know how it goes for you. I've a retailer near me selling the international version of the z3 new for near 400 I'd buy if verizon would do their end.
[Xperia Z3 Compact Q&A, Help & Troubleshooting] Christopher Price:
Well, the first step was pleasant!

Verizon technical support has a form just for this very situation now! The DMD Device Add form (my nickname, not theirs) is what they fill out. They took down my device's bio (IMEI, make/model, LTE bands supported... even the storage capacity), and then sent the request.

They told me that if it is approved, the device will be added to the network in 1-2 business days, and my active SIM should then work with the device.

Now, my big concern is - they're provisioning the IMEI manually... they could easily block VoLTE in the process, but I hope they don't.
[Xperia Z3 Compact Q&A, Help & Troubleshooting] MGSBigBoss:
Well the other user that got verizon to white list their device. He didn't have issues right? So you shouldn't I'd think. Also if they are taking that info down they shouldn't go out of their way to block the IMEI...
[Xperia Z3 Compact Q&A, Help & Troubleshooting] Christopher Price:
The only other user that I'm aware of was using the UML 290 PP. A prepaid version of a Verizon device that was already whitelisted. In that case, Verizon responded to the FCC complaint admitting they made an error - since it was a Verizon-branded device, it should have been whitelisted (for postpay accounts) already.

With the D5803, there's the added factor of VoLTE. We don't know how Verizon will code the whitelisted device. It could be they code it as a data-only device, and deny access to VoLTE. That was an issue with the HTC One A9 for awhile.
[Xperia Z3 Compact Q&A, Help & Troubleshooting] MGSBigBoss:
Any updates on whether verizon will add the phone to the list or you think they will decide tomorrow?
[Xperia Z3 Compact Q&A, Help & Troubleshooting] Christopher Price:
At this hour, I'm now two full working days since submitting my DMD device add request. No call back, and my D5803 still is actively being denied registration on Verizon LTE.

Guess I'll give it until Monday to call back in again. No action next week, I'll take it to corporate relations, and then off to the FCC if that goes nowhere.

My understanding is that you have to call Verizon Technical Support and do the process for your specific IMEI. They are only whitelisting entire device blocks when either the manufacturer cooperates, or when enough customers jam up the call center that it's efficient for them to whitelist the entire block range for the particular device make/model.

Anyone that has Verizon and also has a Band 13 LTE Sony phone, I strongly encourage to call technical support and file the request... even if you have Verizon prepaid. Once your phone is whitelisted, it's whitelisted for life.
[Xperia Z3 Compact Q&A, Help & Troubleshooting] MGSBigBoss:
Now if I didn't have a z3v, I'd get the z3 and try this out as one model does have the bands.. But I prefer the z3v over that. However sony announced that they are releasing unlocked z5 in us in places like best buy. Now I checked but couldn't find what model nor what bands it has. Do you know if any of the existing z5 models have band 4 and 13?
[Xperia Z3 Compact Q&A, Help & Troubleshooting] Christopher Price:
Here's the bad news on the Z5: Sony put all its bets on the Z4v in the U.S. and Brazil, so they scrapped Band 13 on the Z5 in favor of Band 12.

Then (apparently, Verizon) killed the Z4v, leaving Sony with no Band 13 devices. I have actually suggested Sony re-release the Z3 & Z3 Compact as Band 13 phones, a la Nexus 5X & 6P.

Unless Sony re-tools and creates U.S. variants of the Z5 (unlikely at this point), they will only work on AT&T and T-Mobile.

You're not missing much. The Z5 (Compact) is not dramatically faster. And it lacks the awesome magnetic charging connector. Nor does it have Qi (which Verizon pestered Sony to add just for the Z4v).

Z3v owners got burned by Verizon blocking (or making too difficult) for Sony to ship Marshmallow. So you are stuck with the Z3 platform, in a Z2 body, which will always be stuck on Lollipop. Really odd combo, but it hopefully will get you another 9 months to the Z6.

What Sony should be doing, right this very minute, is arming the Z6 and Z6 Compact with Sprint and Verizon VoLTE support, so they can be like the Nexus. If Sony sticks with it, and does that, they'll be amazed how many phones they sell over here. But I've been following Sony (Ericsson)'s shell casings for 15 years. They always come super close (T606, T608, Z4v) and kill it off right on the eve of success.

Edit: I just learned that the U.S. version of the Z5 will have *some* modifications. I only can confirm the fingerprint scanner won't be included. No word yet on bands.
[Xperia Z3 Compact Q&A, Help & Troubleshooting] MGSBigBoss:
I just spoke with sony mobile us customer support. They gave me no info on a lollipop release stating service providers handle updates on branded phones.. So it's on verizon.

I asked about the z5 which they confirmed is coming to the US. The rep did not know a date, nor the bands or service carriers it will support. What's the point of having a us branch that's in the dark and know less than we do about the phones they are releasing?
[Xperia Z3 Compact Q&A, Help & Troubleshooting] Christopher Price:
Generally until it's on sale, the sales people aren't briefed. It's basically SOP today to not feed customer service any details until the launch docs are sent. They may not know until February, even if it's on the blogs.

In the early 2000's - we got most of our phone leaks from customer service people who got briefs way too early. It just led to a lockdown on all that info outside of product and PR staffs.
[Xperia Z3 Compact Q&A, Help & Troubleshooting] user23785:
An interesting thing is Nexus 5, which doesn't support band 13 and VoLTE, was able to connect to Verizon with KitKat and Lollipop, but not with Marshmallow according to https://www.reddit.com/r/verizon/comments/3jihcj/why_am_i_able_to_connect_my_nexus_5_to_verizon_lte/

So maybe Verizon didn't start blocking devices with not whitelisted IMEIs or with VoLTE support, but Marshmallow changed something that prevents non-VZW devices from connecting to the network. I don't know if D5803 or D6603 have Lollipop 5.1 with VoLTE support, but if they do it would be worth trying.

By the way, did you select LTE-only mode and then tried to turn off and turn on radio in the hidden menu?
[Xperia Z3 Compact Q&A, Help & Troubleshooting] MGSBigBoss:
Well it's Tuesday. Did you get any results from verizon regarding this device?

Sent from my Sony Z3v on Tapatalk
[Xperia Z3 Compact Q&A, Help & Troubleshooting] Christopher Price:
Edit: Deleted, see below.
[Xperia Z3 Compact Q&A, Help & Troubleshooting] Christopher Price:
Got the device working, Verizon added the IMEI (confirmed by my account status showing Non-VZW Device when the SIM was in it).

But the D5803 wasn't registering on the network still. Tier 2 was no help (the above/deleted post mentioned how they blamed the fact the SIM was previously in an iPhone... ahem).

I went into Android debug settings and forced the phone to LTE Only. I then added an APN for Verizon. And that did it!

So, for the Z3 D6603 & D5803, here's the steps:

1) Call Verizon, get them to do the DMD Device Add Request

2) Dial *#*#4636#*#* in the Phone app then tap Phone Information on the next screen.

3) Change the network setting to LTE Only (you MUST do this step - LTE/GSM is not enough, it must be LTE Only!!)

4) Create an APN - the only setting you need is vzwinternet in the APN field, and name it whatever you want.

5) Reboot the phone. You should now have LTE.

Unfortunately, VoLTE doesn't seem to be working. Just getting "mobile network not available". Tethering does power up.

I can't flash the Marshmallow beta as it's barred in the USA (this may be why), and people who have tried manually flashing have reported bricked devices (plus I'm out of warranty).

Still, I'm optimistic Marshmallow might remedy the VoLTE front, hopefully the update will be out shortly.

Edit: Even without VoLTE, this is a win for me. I can drop my iPhone 5S's Verizon SIM into my D5803 when I need to tether, or use Hangouts VoIP when the battery dies in my iPhone. Plus, I can save my Smartel/T-Mobile Data Stash by offloading big downloads/streams onto the Verizon SIM too. And I can conditional call forward my Verizon number to my Hangouts VoIP number.

My small superphone now works on Verizon, I'm happy. :)
[Xperia Z3 Compact Q&A, Help & Troubleshooting] MGSBigBoss:
So you can't make phone calls at all with the phone since there's no volte support? So it's data only that they approved it for?

Sent from my Sony Z3v on Tapatalk
[Xperia Z3 Compact Q&A, Help & Troubleshooting] Christopher Price:
It's too soon to say who is to blame for VoLTE not working. We need Sony to release the Marshmallow upgrade.

Verizon-compliant VoLTE was added very late in the Lollipop lifecycle, and it was out of band with AOSP. For example, my Nexus 6 offers an option to "Disable VoLTE Provisioning Flag" whereas my D5803 in debug settings does not.

This indicates that the D5803 does not have a new-enough version of Android VoLTE to work with Verizon.

Then again, Verizon could be blocking it based on IMEI. I wish I could flash my D5803 with the Marshmallow beta FTF, but I've heard of at least two perma-bricks from bypassing the region lock on the beta.

I think we just have to wait for Marshmallow at this point, and test again.

In the mean time, I have a working alternate solution. Dial (on my Verizon-branded phone) *72 + My Google Voice number to call forward to my Google Voice phone number. Then I take the SIM out and put it in my D5803. Then Verizon voice calls are forwarded to Google Hangouts on my D5803 as VoIP calls. And I dial outbound using the Hangouts app. 911 calls would be routed via GSM/UMTS using any available signal.
[Xperia Z3 Compact Q&A, Help & Troubleshooting] Christopher Price:
Two relevant updates:

1) I've comprised a mega-guide for those that want to follow in my footsteps and activate a D6603 or D5803 on Verizon: http://www.christopherprice.net/sony-xperia-z3-compact-lte-phone-verizon-wireless-3199.html

2) Sony has posted the Z5 (Compact) USA product pages: http://www.sonymobile.com/us/products/phones/xperia-z5-compact/specifications/

Unfortunately LTE bands are conspicuously absent. :/
[Xperia Z3 Compact Q&A, Help & Troubleshooting] MGSBigBoss:
Yeah Ive already gone through customer support which did not have any information on the release date that we can easily find online nor the bands the device supports.

In regards to getting those devices activated on Verizon if you can't make a phone call with it then that defeats the purpose of having a smaller phone if you have to carry two phones.
[Xperia Z3 Compact Q&A, Help & Troubleshooting] Christopher Price:
If you follow the mega-guide linked in my last post, you don't have to carry two phones. Once you enable conditional call forwarding, it works perfectly over VoIP via Google Voice on Verizon LTE. Including calls from people dialing your Verizon phone number.
[Xperia Z3 Compact Q&A, Help & Troubleshooting] MGSBigBoss:
Text messages work too?
[Xperia Z3 Compact Q&A, Help & Troubleshooting] Christopher Price:
Text and MMS now work with Verizon on Google Voice. The workflow in my mega-guide will not call forward your Verizon MDN text messages. You need/should give everyone a Google Voice number to communicate with you - just for all the reasons Google Voice is great.

I made sure long ago anyone that texted me, only used my Google Voice phone number. That ensures I always can text (regardless of device), and text from my PC - plus security with Google 2-factor.

But if that is a deal breaker for you, there is a fix! You can port your Verizon MDN to Google Voice, then have Verizon issue you a new MDN. That way, all the people that text you won't have to update their number.
[Sony Xperia C] Jang le:
How installer xposed in c3 d2502 for 5.1.1
[Sony Xperia C] Jang le:
I installer it but erro bootloop :(
[Sony Xperia C] wwwhana:
Do not bombard .....

C3 lollipop can't install xposed..

give up

kitkat is possible

---------- Post added at 09:11 AM ---------- Previous post was at 08:39 AM ----------

[MENTION=7126455]Jang le[/MENTION]

if try this one? http://xdaforums.com/t2-ultra/development/stock-xperia-t2-deodex-patch-t3254093
[Sony Xperia C] bourseindia:
Thanks for sharing the installer of Xposed C3.
[Nexus 6P Q&A, Help & Troubleshooting] androidphan88:
So I am loving my 6p but this is highly annoying. So when I am in an application and want to share a pic, it will only show me recent pictures and I cannot go back through old photos.

You can share from photos without issue. But why in marshmallow can I only share recent photos inside an app.
[Nexus 6P Q&A, Help & Troubleshooting] gie62001:
Can't you just slide from the left to have more options on where you want to share them from like drive, folders, and other apps?
[Nexus 6P Q&A, Help & Troubleshooting] jaythenut:
You have to give that app permission to open your photos
[Nexus 6P Q&A, Help & Troubleshooting] androidphan88:
I thought that as well, but it never asked me to grant it permissions. Also yes there are options on the left, but that is for photos stored on the device. The photos I want are in Google cloud
[Android Q&A, Help & Troubleshooting] adeelkhan09:
Hi all,

Sir I have successfully installed cm12.1 on my galaxy s5 sm-g900f now I want to disable its camera drivers from build, so that no body can access its camera features but I am unable to find exact path to disable its drivers, you quick response will be highly appreciated.

Thanks

Adeel
[Android Q&A, Help & Troubleshooting] Ayumi_Jitsukawa:
Searching the same for cm11 on se xperia pro...
[ZenFone 2 Q&A, Help & Troubleshooting] xuggs:
Has anyone (who is lucky enough to have an invite) tried Project Fi SIM with the Zenfone2? I've read that it works with the Note 5 despite the fact that it only supports Nexus devices currently.

Thanks!
[Samsung Gear S2] Zagzagel:
Is AT&T Numbersync available on the Gear S2 3G yet? If so, please share your experience using it.
[Samsung Gear S2] SicEm06:
Numbersync is not yet available on AT&T. Anticipated release was late Dec or early Jan. For now it's simply call forwarding.
[Samsung Gear S2] Zagzagel:
That's what I thought. I bought my Gear S2 3G at the AT&T store, and they told me Numbersync was already released. It took me a few days to figure out my outgoing watch phone number was changing when the Gear S2 became unpaired from the phone. At first I thought it was because HD Voice wasn't actived on my account, but now I understand that the whole feature hasn't even been implemented. The AT&T employees are clueless.
[Samsung Gear S2] starman62:
number sync from att is now working on my Gear s2.
[Samsung Gear S2] SicEm06:
Did you have to download some type of update? Update from the Gear Manager app or something else?
[Samsung Gear S2] crp62:
Update the Gear App on your AT&T phone, and you'll see an update for the watch.

I updated mine today. It's not a big update and only took a few minutes to download on broadband.

Afterwards, you have to agree to allow AT&T to store your messages on their server for 90 days, via a checkbox screen that your phone is directed to. After agreeing to that, a code is sent to your watch and you enter the code on your phone.

That installs the update to the watch, it'll reboot, think about things for awhile and then come back up with a new welcome message.

Others who have completed the upgrade have reported rapid battery drain afterwards (over on Android Central): http://forums.androidcentral.com/samsung-gear-s2/610948-t-gear-s2-3g-number-sync-2.html

I seem to be in that camp myself.

HTH,

crp
[Samsung Gear S2] hlanclos:
I updated mine last night...have not been able to receive any texts or calls on my watch since. Brought it to AT&T to look at, they just exchanged it for a new watch. Was not able to set it up while I was there because it was not registering on the AT&T network yet...told me to give it about an hour. Still not connected yet, will keep you posted.

UPDATE: I did a "Light Reset" on my phone and followed the NumberSync instructions when prompted...as of now it all seems to be working correctly. I'm receiving all of my calls and texts on my watch. When I create a text or make a phone call from my watch (via remote connection, not bluetooth), it is showing my primary number instead of the watch's number.
[Samsung Gear S2] gnahc79:
After the update, no text msgs were being sent to the watch while paired to the phone (s5 active). Calls were being sent though. I ended up doing all sorts of things and I think it's working now.

1) disable numbersync on the at&t website

2) remove numbersync on the at&t website

3) light reset on the phone, skip numbersync setup

4) disable Messages in the notifications list, select Done. Then enable messages, select Done.

turn off/on the phone and watch numerous times. at one point only some txt msgs were being sent to the watch (like 1 out of 5)...now all seems to be sent to the watch.

everything seems to be working now that numbersync is completely removed from the at&t website

---------- Post added at 02:57 PM ---------- Previous post was at 02:51 PM ----------

cool, good to see that a light reset on the watch+ enable numbersync seems to work. I may try enabling numbersync at a later time.
[Verizon Droid Incredible 2] sadhubava:
Verizon Htc droid incredible 2 stuck on bootloop... plz help

while writing nav from cdma workshop. it was working properly but when i restart the phone it stuck on bootloop...

cant factory reset not working, recovery not working

fastboot working... adb not working

htcdev unlocked S-on stock rom gingerbread

my hboot screen shot in attachment

plz help me how to get out of it....:confused:

tried this RUU it finished sucessfully after rebooting device no results... stuck on same issue bootloop..

RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_5.10.605.9_Radio_1.09.01.1111_NV_VZW1.92_release_225831_signed.exe
[XDA Assist] XDA Visitor:
First of all, sorry if I am posting this in the wrong thread or wrong area.

I'm seriously depressed and deprived of sleep because I finally rooted my phone and everything went wrong.

Yeah, I fell in with that crowd. Shame on me, i know ,_,

Samsung Galaxy Note 3 SM-N900W8 is the victim. I downloaded CF AUTO ROOT HLTECAN HLTEUB SMN900W8 which, apparently, should have had no problem. Used Odin 3.07 on my laptop and the process was smooth and quick. Buuuut of course my phone got mostly wiped (no surprise here, totally worth the root). Along with that wipe came the rage of Google and Samsung.. don't know why but most apps just force close when I try to open them.

Long-story short I need to regain access to my Google account, my messages (so I can, you know, message my grandmother so she can pick me up at the university) and the ability to have a functional good phone.

I've learned my lesson, I'm leaving this rooting stuff to the more apt. However I need guidance on how to what I believe is called "flash" the system back into having all the permissions it used to have. Not sure what I'm talking about any more.

If it is possible to keep the root and somehow fix the problem (regain access to basic services such as messages and play store) that'd be nice. But really, I just wanna travel back in time and forget this ever happened so late at night that it's almost morning and my feelings are extra hurt.