yashsingh1/xdaforums huggingface dataset:
[Xperia Play Q&A, Help & Troubleshooting] marvi0:
thanks bud, managed.
[HTC Vivid, Raider, Velocity] badboyz:
When on a call the other person sounds very metallic, but when playing music through the back speaker it sounds fine. Also when on a call the speaker phone sounds fine. Is my speaker detective or is the quality just bad for the ear speaker?
[HTC Vivid, Raider, Velocity] chocodough:
HTC phones always have crappy speakers in them. I doubt you have a bad one, it's just that HTC is cheap and won't put in better speakers.
[HTC Vivid, Raider, Velocity] rquinn19:
I disagree. Quality isn't bad, volume is the issue.
[HTC Vivid, Raider, Velocity] russell1997:
of the 3 HTC phone i've had here is my raking

1. tilt... by far had the best speaker

2. vivid

3. aria

i'm not impressed with the vivid's speaker but it's not horrible. not something i would choose as to whether to get the phone or not.
[HTC Vivid, Raider, Velocity] badboyz:
well I mean does anyone else's sound like they have their ear on a tin can?
[HTC Vivid, Raider, Velocity] deepsunn:
I'm not having issues with my earpiece speaker but I am with the back speaker.. I can get a call and it is SUPER loud, so much so that the speaker actually distorts. I've tried turning it down but I have "pocket mode" on, so it boosts the volume, weird thing is, it's in a case, not my pocket. Could the case be screwing with the phone's ability to "sense" whether it's in a pocket or not? And why in the heck would the speaker even be distorting?! It does not do this when I play music thru it at max volume, by the way..
[HTC Vivid, Raider, Velocity] Mocaris:
I'm having the exact same issue.
[Omnia 7 General] pLUSpISTOL:
This works with the Omnia 7 and can shoot video calls using the rear-facing camera and receive video/audio too.

Calls can be made over 3G and WiFi.

Make calls to WP7, Android, iPhone and PC contacts.

There is a contact list, recent calls and push notifications for incoming calls.

Your phone must be developer unlocked.

Tango version 1.6.14192 (beta)

Many thanks to Tango (in particular Dmitry S), thesecondsfade and contable!

[DOWNLOAD LINK]
[Omnia 7 General] sarathvenmony:
thx for uploading
[Omnia 7 General] Radek Hulán:
http://www.windowsphone.com/cs-CZ/apps/fe30c379-d111-427d-894f-dc3bfa0ec371
[Omnia 7 General] contable:
The marketplace version is older than the provided one and doesn't support video on the Omnia 7. I got build 1.6.14192 directly from Tango...just for your info.
[Motorola Droid 3] LifeInAnalog:
Honestly, I'm not sure what all the *****in' for an XT860 forum is all about. Do we really need a lot of space to discuss all the dev that doesn't work on our phones? I'm sure one thread is enough. That way, maybe all the d3 users can get some peace from us constantly asking about compatibility.

Maybe, as a public service, all the d3 devs could stop in here after they've produced the next great ROM, and just let us know (without laughing) that NO, this will NOT work with your phone.

Ah...I feel better now.
[Motorola Droid 3] ChaoticWeaponry:
Venting feels great eh? Haha I'm sorry I cant relate to your problems (XT862 user) But I wish you luck on future ROM's being developed!
[Motorola Droid 3] Endoroid:
*subscribe*

Sent from my rooted xt860
[Motorola Droid 3] eezdva:
Oh well. The thing is that Bell should just come with an update so devs can start. Wonder if Bell is waiting for ICS to update instead of updating now and then having to update again for ICS???

But yeah where is the freaking update. Maybe some Canadian people know more about it ????
[Motorola Droid 3] LifeInAnalog:
...it just gets frustrating. The D3, if you include the leaked 5.7.894, is now two updates ahead of us...and we're stuck on what...er...windows 3.1?

There's also a level of frustration with myself. After all, with alternate launchers, UOT kitchen, root, debloating, its not like its a bad phone..I guess I just have the patience level of the average 3 year old.:o

Just to be clear, once we get an update then someone can get an sbf from that? Or am I totally out to lunch...remember, I'm the guy who has a flashing clock on his vcr. VCR....video cassette recorder? Never mind kiddies.
[Motorola Droid 3] Endoroid:
It still has some major glitches in my opinion that Motorola should have already fixed for us. I asked bell and was told the updates come from the manufacturer. I'm still waiting to hear back from Motorola, despite the 24 hour for a response auto reply I got. While ROMs would be nice, the cell standby, slow camera and buggy keyboard are all issues that Motorola should have addressed already imho

Sent from my rooted xt860
[Motorola Droid 3] DoubleYouPee:
Well I once e-mailed motorola canada with questions about the XT860 - haven't heard from them since (it's been weeks). So don't get your hopes up :D :o
[Motorola Droid 3] danifunker:
I completely agree with you Endroid. I am also curious about one other thing... Lets say I wanted my phone in french, how would I be able to convert it over, or vice versa? Maybe we could get an SBF out of it???
[Motorola Droid 3] Endoroid:
Settings>language and keyboard>select locale.

Sent from my rooted xt860
[Motorola Droid 3] danifunker:
Weird bug I just noticed... I did that and changed to French, back to English, then to Spanish, then to English and I noticed that my message icon for my Exchange account changed colours...
[Motorola Droid 3] static416:
Yeah my gf has the XT860 and she's not very happy with it. Part of that is because it's more complicated than her 3GS, but part of that is also because there are a number of bugs and it's laggy at times. Tons of bloatware.

At least if we had some way of loading our own ROMs I could fix some of that for her.

I know that my stock AT&T Captivate was a piece of crap. It wasn't until I installed Cyanogen Mod that I had something useful.
[Motorola Droid 3] Endoroid:
I truly apologize for the inconvenience that you are experiencing at this time. What issues are you experiencing with the unit? Unfortunately, there is not an update scheduled to be released at this time and we do not have any information as to when one will become available. You can check our site for future updates. I truly understand your frustration and I apologize again for the inconvenience. If you need further assistance please contact Customer Care at the following number (800) 461-4575. Thank you for your continued patience.

http://www.motorola.com/Consumers/CA-EN/Home

Sincerely, Latasha Customer By Web Form (Marc Laferriere) 11/06/2011 07:40 PM I am the owner of a XT860 4G, which i am beginning to regret. The phone has numerous issues and bugs, which i'm sure Motorola is aware of, as pretty much all of these issues were fixed in the recent update to the XT862 (5.6.890). I have previously contacted Morotola about this and was told that there currently is no update and there is no information pertaining to one. Now i see that there is yet another update coming for the XT862(an unofficial leak, however that means that one will be released soon) yet still nothing for the XT860. The lack of support for this device is offensive to me. When i purchase a device i expect that it will be supported for at least a few years. As it stands i would not purchase nor recommend Motorola products. So again i ask, is an update for the XT860 forthcoming, or should i be looking for a device that will actually see some support.

Thanking you in advance Marc

Sent from my rooted xt860
[Motorola Droid 3] pfak:
I just want a fix for the battery life, 12 hours is unacceptable ...
[Motorola Droid 3] Endoroid:
Hell I don't even get that. Granted I could make some changes to improve my battery life such as turning off background data but then what's the point of having a smartphone. 6-10 depending on my usage

Sent from my rooted xt860
[Motorola Droid 3] LifeInAnalog:
Great post, Endoroid. As doom and gloom as the lettter appears, its still possible that the letter is simply holding to company policy of not releasing info until its ready to be released. That's what I'm gonna tell myself anyway.

Its been said before somewhere, but I'll re-iterate, never ever buy a country specific phone like this...unless you are happy with the stock experience.

I'm very happy I didn't actually pay for this baby, having won it in one of Mobile Syrups giveaways.
[Motorola Droid 3] danifunker:
Endroid,

Can you go to Bell and have them talk to Motorola regarding these issues? Unfortunately I'm not on their service so I don't have as much leverage as someone like you would...
[Motorola Droid 3] ChaoticWeaponry:
Wow guys I'm sorry. My droid 3 can get almost 3 days if I use it sparingly.. I wish you guys could use our system updates..
[Motorola Droid 3] Endoroid:
I'm out of country the next week but when I return I plan on also contacting bell and escalating with Motorola. I have been into a bell store but the sales reps are pretty useless for this.

I mean honestly, given the similarities between the 2 phones I don't understand why we wouldn't receive updates around the same time as d3. It should be easy enough for Motorola to modify the update to apply to our device

Grrrr

Sent from my rooted xt860
[Motorola Droid 3] eezdva:
Yeah yeah, Rub it in lol.

Well sad news for the Bell users for sure.
[Motorola Droid 3] leobg:
Huh, we don't even recovery to get back to stock if things go wrong.

I heard Motorola issues updates based on phone popularity/user base. If this is true, it will be awhile before we see any updates. XT860 has the same bugs, if not even more like D3 with original release firmware. D3 is now getting second OTA while we have not even heard about first one to address these obvious bugs. If we look back at Milestone 2, to compare to Droid 2 Global which took 8 months to get GB upgrade, M2 has not yet received it.

Things don't look good with XT860 in this aspect for sure.

Lets hope Motorola will prove me wrong!
[Motorola Droid 3] DoubleYouPee:
I read that the next big safestrap update should work on XT860 as it's not dependent on pre-install size.

Don't quote me on it though
[Motorola Droid 3] danifunker:
I have a system recovery image that I created a few months ago, before I really started to play with my phone. Another user was able to restore their phone enough for it to work after their broke their /system/apps.

Check the development threads for the details. It involves doing a dd back to the phone.
[Motorola Droid 3] Willis111:
My preinstall and userdata are the same size hashcode posted for the vzw model In this thread.
[Motorola Droid 3] Hashcode:
Today, I posted a new build of CM7 which is installable with Droid3Bootstrap.

I'm VERY curious of this will be usable on the XT860.

You can download from RomManager or via my blog:

http://hash-of-codes.blogspot.com/p/android-downloads.html

Still no solution as to why Safestrap doesn't want to work on the Bell phones. :/ But maybe in the meantime the CM7 will help.

There's a very good chance however, that your 3G won't work as the build is set to Verizon Wireless US. I was working on supporting network switching in the ROM, but I had to revert as I'm going a different route with the WCDMA/GSM support. So it will be coming in the future.

On a side note playing with these /system/build.prop values (and rebooting) might also get 3G access for you:

ro.telephony.default_network=4

ro.cdma.home.operator.numeric=310004

ro.cdma.home.operator.alpha=Bell

I read somewhere that ro.telephony.default_network needs to be "0" for WCDMA, but I don't know the ro.cdma.home.operator.numeric for Bell/Canada. :/
[Motorola Droid 3] LifeInAnalog:
I'm assuming that the 3g issues will be the same for an unlocked 860 on the Telus network. Can't wait to get home to give this a try. Thanks Hashcode.
[Motorola Droid 3] danifunker:
Why not just go through the original build.prop file? Bell 3G is HSPA and HSPA+ *NOT* EVDO. There are a number of tweaks in the build.props file specifically pertaining to the non-cdma version of the Droid3 phone such as the tweaks mentioned in other threads.

I have also attached the stock version of the file maybe this can help uncover more info.
[Motorola Droid 3] btn21:
I'm guessing it's not just the build.prop which needs to be modified, as danifunker says, the XT860 uses HSPA, not EVDO. So the radio files probably needs to be changed as well.

Maybe we need to do the same as they do for the Motorola Milestone. Create update.zip for the different radio files.

I wouldn't mind testing this, but not sure which files to copy...
[Motorola Droid 3] Hashcode:
When I was testing the network switching I saw settings for about 8 different network types, etc. So it's worth a testing out just build.prop tweaks and see what happens.
[Motorola Droid 3] btn21:
Well, I tried changing the build.props file in your CM7 build to match the network settings from the build.props from the XT860. It bootloops and eventually goes back to recovery. I also tried without making any changes to build.props, same result.

This makes me think there's more to it than just changing settings
[Motorola Droid 3] Hashcode:
Did it bootloop before those changes? Or just no 3G when it came up.

---------- Post added at 10:02 AM ---------- Previous post was at 10:01 AM ----------

Btw, here's the definitive answer as to why the XT860 won't currently support Safestrap (not that it matters as much since I've added Droid3Bootstrap support):

http://xdaforums.com/showpost.php?p=19440416&postcount=170
[Motorola Droid 3] btn21:
Yeah, bootloop happens without any changes to your CM7 build. Not able to start CM7 at all
[Motorola Droid 3] Endoroid:
Just to be clear, if we flash cm7 using bootstrap, since the xt860 has no fastboot files we have no way of returning to our stock rom, thus being forced to use the me863. Right?

If that's the case we would be better off waiting for the safestrap to be compatible

Sent from my rooted xt860
[Motorola Droid 3] btn21:
Endoroid. No, after installing CM7, it bootlooped a couple of times, then went back to recovery so that I was able to revert back to my XT860 nandroid backup.

Just make sure you do a nandroid backup before you try installing CM7.

Also, as pointed out. Safestrap doesn't work (yet), so you have to use bootstrap.

Note:

Don't take my word as a guarantee that you will be able to recover.
[Motorola Droid 3] danifunker:
Could you use my system dump that I made back in september as a recovery point? All you would need is a system shell then could just dd the image back to the right block (the block is in the filename). I'm pretty scared of playing with it since this is my only phone I have!
[Motorola Droid 3] btn21:
If you mess up your phone in such a way that you're forced to flash the ME863 ROM, then afaik there's no return. But if someone neglect making a nandroid backup, but are able to load recovery, then your system dump would work.

I had until today resisted trying to install any custom ROMs or make dangerous modifications. But I was able to get in to recovery after flashing CM7, and I made a nandroid backup before proceeding.
[Motorola Droid 3] danifunker:
What do the different recovery options mean when you press the vol+ and - buttons at the same time when booting? Here is the list I see on the phone, I'd like to know a little more as to what *exactly* it means, again I'm running stock, but this looks more like a BIOS level thing for me (I come from a PC background)

Boot Mode Selection Menu (0A.40)

Vol Up Selects, Vol Down Scrolls

Available Boot Modes:

Normal

Recovery

AP Fastboot

BP SBF Flash

BP Only

BP HW Diag & Boot Ap

BP Tools

Whare are some of the caveats and stuff? I am still new to the Android scene. Also, do all android devices have this boot menu?
[Motorola Droid 3] btn21:
Hashcode,

I gather you use some of the source from the Motorola released source for the Droid 3 at:

http://sourceforge.net/projects/droid3.motorola/files/droid3/5.5.1_84_D3G-20_TA-9/

I checked the version for my XT860, 5.5.1-112_SLU-54.4, and went back to the Droid 3 project at sourceforge, and found a matching directory for my version:

http://sourceforge.net/projects/droid3.motorola/files/milestone3%20LATAM/5.5.1_112_54.4/

Closely matching version anyway. When you download the Milestone 3 source from that link, you'll find that the version matches against the XT860 exactly.

I have started doing comparions, and found that the phones seems to have different omap revisions:

/kernel/omap4/arch/arm/mach-omap2/id.c:

450,451c442,443
< omap_revision = OMAP4430_REV_ES2_3;
< omap_chip.oc |= CHIP_IS_OMAP4430ES2_3;
---
> omap_revision = OMAP4430_REV_ES2_2;
> omap_chip.oc |= CHIP_IS_OMAP4430ES2_2;

There are tons of differences between the source trees, and it will take some time to sort out the stuff that could be of interest. But there could be clues in there as to why code built for the XT862 doesn't work on the XT820...

I will continue looking for clues, but I'm by no means a coder, so if someone would like to help out, please do...
[Motorola Droid 3] TBBle:
You can confirm this on your hardware in /proc/socinfo. You didn't say which file is which, but my ME863 (HK Milestone 3) is revision 2.3. Note that LATAM is "Latin America" (i.e. Brazil's Milestone 3) if that wasn't already obvious. (I didn't know that, for example)
[Motorola Droid 3] btn21:
Yeah, output from /proc/socinfo is indeed 2.2

So, to clarify, the Droid 3 (presumably XT862) is 2.3 and the XT860 is 2.2

Also, I figured LATAM meant Latin America, but keep in mind, the XT860 is available both in Brazil and Chile, so it might be fair to assume they share the same code.

Have you checked if your phone version is found under the LATAM directory? If it's there, maybe you could download the omap source, and check that file to see if it contains the omap revision matching to your phone.
[Motorola Droid 3] Hashcode:
Guh. Well I apologize to those that tried to boot it up and bootlooped. That's always scary.

I'm still rather mystified at some of the issues surrounding the XT860.

On the outside it *SEEMS* to be the Canadian counterpart to the XT862. But the deeper we dig the more issues that are uncovered. :/

Booting up w/ Droid3Bootstrap avoids the /preinstall issue (trying to mount it as ext3 for 2nd-system). So I was sort of hoping that would work.

I don't believe the version of OMAP4 will have an effect on the boot of CM7. But, you might be only to something by examining kernel differences.

Is there a complete system dump of the XT860 somewhere on the forums?
[Motorola Droid 3] btn21:
I have an old system dump with fairly minor modifications to the app tree, but I don't have one which is completely clean and untouched. Shouldn't be a problem though, as I said, it's just minor app changes, like removing some bloat.

I'll see if I can get it uploaded somewhere or possibly set up an ftp on my Sun server, but my upload speeds aren't great...
[Motorola Droid 3] TBBle:
I just had a look at the code in arch/arm/mach-omap2/id.c and the earlier diff wasn't exactly clear.

Basically, the D3 5.5.1_84_D3G-20_TA-9 kernel only recognises ES 1.0, 2.0, 2.1, 2.2 and if it doesn't recognise it, it reports 2.2

The M3 5.5.1-112_SLU-54.4 kernel recognises 1.0, 2.0, 2.1, 2.2, 2.3 and if it doesn't recognise it, reports 2.3.

The actual revision is the first (hex) digit of the IDCODE line in /proc/socinfo: 3 is 2.1, 4 is 2.2 and 6 is 2.3.

A quick browse through that M3 kernel suggests that the only difference between 2.2 and 2.3 is that 2.2 has a potentially unset value to be worked around, and 2.3 doesn't need whatever the CONFIG_OMAP_HDMI_AUDIO_WA define is enabling. It's referred to elsewhere as "ACR workaround" and "HDMI audio WA for OMAP4430 ES2.0,1,2".

So yeah, I'd say ES revision is pretty safely ignorable for our purposes.

Although that does suggest that the model number reflects hardware revision. XT860 has the ES2.2, while XT862 and ME863 have the ES2.3 OMAP4430 revision SOC. I wonder if the newer Droid 3 firmware releases have integrated the ES2.3-supporting kernel or not...
[Motorola Droid 3] btn21:
My XT860 system nandroid can be downloaded here:

http://www.mediafire.com/?i6l9l8o3wwtb8yx
[Motorola Droid 3] danifunker:
I have a DD image

http://www.multiupload.com/SORQERFAYT

If you want instructions how to access it in Windows refer to this thread: http://xdaforums.com/showthread.php?t=1340492
[Motorola Droid 3] :
Hashcode -- you'll make many of us super happy if you can figure away to get CM7 on our XT860's!
[Motorola Droid 3] Endoroid:
I second that

Beamed by invisible waves from my rooted xt860
[Motorola Droid 3] Hashcode:
Sorry for the slower responses on this guys.

I've been busy in RL w/ work the last few days.

So the status update is: I grabbed the /system tar, and I'll take a look at it tomorrow.

Does anyone have a dd of the boot partition as well?

Also, I'm still adding the Motorola code to support dual radios into the D3 CM7 build.

It's quite a bit larger task than I would have thought originally as it weighs in at around 20-25 new java classes (includes LTE support) and also requires about 2-3 APK's be decompiled and reconstructed as well. The end result should be handling of the GSM/CDMA network switching JUST like MotoBlur does.

So we'll get there 1 way or the other.

Also, something I've done on my own system when I was building Safestrap and experimenting with how the hijack works, was to build a custom / logging set of init*.rc files using strace dumps. (A full boot can create about 20megs of data in the /data partition). In theory, I can walk an advanced user through that process and then get a .zip of the dumps to examine, it would indicate where the boot was stalling out.
[Motorola Droid 3] TBBle:
This's a dd of my ME863's boot partition, if that helps? http://www.mediafire.com/?4ovoaba5cxg59
[Motorola Droid 3] Willis111:
Sorry for the slow reply. Here is a dd of the boot partition from a bell xt860. I pulled it with "dd if=/dev/block/mmcblk1p15 of=/sdcard/boot.img". Thanks again for taking a look at this for us, it's very appreciated.

I could probably manage. Just push the files, set permissions, reboot basically? Ill start jumping on irc when I'm around.
[Motorola Droid 3] pfak:
The issue being is the phantom battery problems are caused by the Radio and not the version of Android at all.
[Motorola Droid 3] Willis111:
I took another users suggestion from these forums and installed Juice Defender off market, I've doubled my battery life from unsatisfactory to acceptable finally. It turns off 3g radio when my screen is off but honestly I noticed that that happened before I install Juice Defender.
[Motorola Droid 3] LifeInAnalog:
...same here. I don't know how many times a day I have to toggle airplane mode on and off just to get my data to kick in again..
[Motorola Droid 3] danifunker:
Initially I used JuiceDefender Ultimate, then I started getting behind on my emails (I use push-email) and also had to do the toggle as was specified by LifeInAnalog. Once I adjusted the settings I was only getting like an extra hour or two on the battery, but then after a few days I would notice my phone would slow to a halt. I checked other Droid3 users experience with JuiceDefender and read how it also slowed their phone down like crazy. So I figured I would just uninstall it and deal with the battery issues. I think Moto needs to issue a fix for this ASAP and I keep emailing their support but still haven't heard anything back yet.

It's definitley the radio code, and I think that moto has fixed it for the verizon customers, and they need to get it right for the bell customers.
[Motorola Droid 3] Willis111:
As far as I know it's bells responsibility to buy the updates for their customers. Imo, in cases of poor coding software updates (fixes) should be provided by the manufacturer free of charge.