Related
Have a few questions for people on the Droid 3, since I haven't been able to find anything elsewhere. Currently have an Epic 4G on Cricket and was thinking about buying a Droid 3 and going to Page Plus to save money (I don't use a LOT of data, and if I do, I'm usually at work/home, so 100MB should be fine if/when I'm on the road or away form home). I had an original Droid, but needed something with a slightly larger screen, better keyboard, front facing camera, etc (which the Droid 3 now has).
1. Is the Droid 3 locked like the Droid 2/X was? I believe it was an encrypted bootloader or something like that. I know HTC apparently is getting away from using locked bootloaders after massive public backlash. It looked like there were a few bootloaders in the development section. In the end, I'll likely want to jump on the CM train and get their firmware, which may take a while. But like most people at XDA, I don't like running stock ROMs.
2. How is the development area for Droid 3? I know Samsung actually has a public portal for releasing source code to kernels, etc, after the OTA (sometimes right before) is released. Does Moto open source its stuff? Just trying to get a feel for how long it'll be (months vs. weeks) for some ROMs, even if they're just deodexed.
3. Is there a better phone to get than the VZW branded one? I saw one from some nigelelectronics or something like that, which was unlocked (the x860 I believe). I don't mind VZW, since I could put it on PagePlus for $30 a month. Is the $200 extra worth it? Does that mean it'd work on AT&T/T-Mobile (I like T-Mobile's month-to-month plans best) and be capable of getting updates for stuff like CyanogenMod, AOSP ROMs, etc? i.e. are they all really the same hardware and can accept flash's from each other's ROMs, but they have hardware locked in different places (i.e. VZW locks out US GSM carriers in the radio, I thought?). I know Samsung Galaxy S's phones share similar core stuff, but modems, keyboard, cameras, etc, are all different and/or not present, so it makes a common ROM for them all impossible.
Sorry for the novel! Just trying to understand where things are at... Thanks in advance!
The bootloader is encrypted. There will be custom roms for it, but we will be unable to use any kernel other then Motorola's. DX and D2 eventually were hacked with 2nd-init which allowed roms like Cyanogenmod and MIUI to run on them. As far as development for the Droid 3 so far, it's pretty much non existent. We just got our hands on some fastboot recovery files that will allow us to recover from any bricks. Now we need a custom recovery and then the roms will begin to roll out.
Thanks for that! Just a few other quick questions.
Given that -- 2nd init I assume is another kernel (or maybe emulator) that runs after and connects into the encrypted one? Is CM a possibility for Droid 3, I think is the real question (and not a "anything is possible... someone might break the encryption or Moto might unencrypt it).
Also -- any thoughts on the different versions of the phone hardware? All mostly same hardware so the ROMs all work on the same phones? Or totally different? Just curious if anyone has thoughts on this from the differences between Moto Milestone 2 vs Droid 2 (but Droid 3 is the Global version as well, since it has SIM enabled by default... so comparison may not be as good)?
Thanks!
2nd init is not another kernel. Its in the name. it is a second init process over the original init that gives us control over the initialization of the system.
Does that same process work for the Droid 3? Is that a possibility, then? Or is that something known that Moto patched (or maybe potentially left in for developers)?
It took a couple people over a year to successfully get 2nd-init to work properly. I wouldn't expect CM7 or MIUI for quite a while. We will have other roms though. Apex and Liberty used motos kernels on the DX and I have to say they were amazing roms.
Sent from my DROID3 using xda premium
I think CM7 will be adapted to the D3 sooner then many would expect. The Droid X already has it and the bionic has similar hardware. I do not think we will have to wait as long as the Droid X did.
Hello all,
According to my depth researches, I'v summed up bits into a package:
- Atrix MB860 does have Wolfson WM9803L DAC chip. (1-?) (Even though all Tegra 2 AP20H should have the same SoC, but after a lot of questions, AP20H {Ventana} stands out for handheld performance (CPU, GPU), power only) Update: Wrong!
- The Asus Transformer uses Tegra 2 T20 , Wolfson WM9803L chip. Does have Voodoo sound support. Based on V1 voodoo drivers.
- I'v got into the same confusion about the 'L' in 'WMxxxxX'; The DAC is based on 2 revisions, both ends with L. Useless
- They both use same SoC implementation, very similiar drivers, nearly same headers. (Based on my own research.)
- Supercurio did not support the Atrix 4G, due its locked bootloader based on the V1 driver date of WM8903L. (So, he might not look back, Wolfson's WM1811 on the road) Update: Atrix 4G = Optimus 2x/Galaxy R
I know I might seem like asking questions, but it should also be considered as a dump project based on both devices. Plus, opening opportunities on other Tegra 2 hard/soft-ware porting.
I don't agree with the idea ignoring 1+ yr old phones with such capabilities...
I consider it just like the fame of the Gi9000, <<<Voodoo = major plus.
P.S. : Supercurio once stated that, Atrix 4G has a diff implementation... Though, after chatting over the IRC, he stated that he do not touch locked bootloader based phones. Thats totally different story. Diff implementation means indirect hardware access, using NVRAM i2c communication (registers)
Big thanks for supercurio, making our phones more valuable. Not anymore... -__-
Thank you all
I will appreciate any help/comment/feedback/correction/response.
Click to expand...
Click to collapse
Thats Bla bla bla above...
Conclusion: Voodoo sound is communicating with #? low level registers with the DAC. Same as what ALSA mixer do when modifying STdac (ICS leak). Unfortunately, Atrix uses OSS on GB, or barebone ALSA thought thats not a problem.
Project STATUS:
Found the right DAC, its WM8993!! Developers/Anyone try Optimus 2x Voodoo sound driver using the patch, patch it to the kernel (WIP)... Loading Voodoo Sound Plus modules didn't work :/
Alternative to Voodoo app coming soon for Atrix/Optimus2x/GalaxyR Tegra 2 Ventana
Workaround for ICS Leak kernel and Kernel 3.x (that includes tiny-ALSA), install AlsaMixer from Play, modify STDac Only While listening to music (be sure not to leave the head/earphones on) to 15. Now you can drive 300 ohms headphones (Though its still limited, shows 10db but not exact) Note: When you remove the earphones or stop music for 5 secs, settings will revert.
List of the confusing/wrong info about Tegra 2 DAC links:
http://forum.xda-developers.com/show....php?t=1124198 Those guyz heard from Androud forums lol
http://www.head-fi.org/t/549644/moto...-sound-quality That guy heard from xda! ^
http://androidforums.com/motorola-at...ola-atrix.html Those are the guilty ones (kidding ), they referred to Tegra 250, thats Harmony used in Tablets not Vantanna 250. :silly:
Having Voodoo sound on the Atrix would be great! I had a Samsung Vibrant before my Atrix, and Voodoo sound was pretty nice! I really like how it sounded and all the settings that it had.
One that i miss for sure is the ability to make the sound mono. I haven't found how to do it on my Atrix yet.
Keep the good work dude! Hope to see it done soon! If it can be done.
I'll be glad to see voodoo sound capabilities on my atrix.Wish you can port this without any problem.
MB860 cihazımdan Tapatalk 2 ile gönderildi
WOOOOOO!! YESSSS!! FINALLY!! I know its not ready, but thank you for looking into it!
djluis48 said:
Having Voodoo sound on the Atrix would be great! I had a Samsung Vibrant before my Atrix, and Voodoo sound was pretty nice! I really like how it sounded and all the settings that it had.
One that i miss for sure is the ability to make the sound mono. I haven't found how to do it on my Atrix yet.
Keep the good work dude! Hope to see it done soon! If it can be done.
Click to expand...
Click to collapse
Mono can be done as a software wise.
Use Poweramp, it has the mono DSP feature.
Good luck.
As stated guys, still haven't got my Atrix, and wish me a luck getting it .91 bootloader :/
bets of luck!! and it will be one hellova feat if u can pull this off ... i have used sgs, nexus s and sgs2 with voodoo ( yes i have purchasrd it from market )... and it makes them a formidable music player rival... i'd really really love to see it for ATRIX also
My friend had this on his Samsung Galaxy Tab and I have been jealous of him ever since lol. I was hoping someone would port it but had given up. I'm glad to see someone is on the case!
Sent from my MB860 using xda app-developers app
Guys, I need your help.
Test this: https://play.google.com/store/apps/details?id=zausan.zdevicetest&hl=en
Or at Play store: Z-DeviceTest
I wan't an info about the DAC. Since i still don't have my Atrix 4G.
Just curious about the WM8903, this info was based on some rumors, a confirmation surely helps, since most tegra 2 ap20h are based on WM8990
EDIT: My Atrix is comming after 2 days...
what to check with that app ?
plus i found some things that u might want to read..( or already read it )
http://forum.xda-developers.com/showthread.php?t=1124198
http://www.head-fi.org/t/549644/motorola-atrix-sound-quality
http://androidforums.com/motorola-atrix-4g/265304-wolfson-audio-hub-hd-motorola-atrix.html
I have downloaded that app but i can't find anything about the DAC...
raghul said:
what to check with that app ?
plus i found some things that u might want to read..( or already read it )
http://forum.xda-developers.com/showthread.php?t=1124198
http://www.head-fi.org/t/549644/motorola-atrix-sound-quality
http://androidforums.com/motorola-atrix-4g/265304-wolfson-audio-hub-hd-motorola-atrix.html
Click to expand...
Click to collapse
Yes I already read it
However, the last link was a guess before the Atrix release i guess, though, what they said is about the Tegra 250 T20 not the A20HP...
All T20 has the WM8903L, while all the A20HP has the WM8990. Thats the confusing part, however, when i get the Atrix, Ill be analyzing the implementation they are using... Might be indirect driver, but i dont think so (Inside a SoC=Direct)
Confusing topic also: http://www.androidtablets.net/forum/shenit-com/18404-tegra-t250-vs-tegra-t20-same-thing.html
What also worries me about the Moto X2. It does have Tegra 2 Ventana. No voodoo sound support, or at least DAC lookout. I don't think there is any A20HP with WM8903 (Does moto play with the sound layer? It should be strict since its a SoC)
I'm not sure between an implementation fault, or lack of support (VoodooSound author). (Though the GS is old)...
Dude, tell me if there is any way i can help you. This is something i really want to help with this project.
Now this is the way for the diff. between T20/T2 ...
http://www.toradex.com/Products/Colibri/Modules/Colibri-T20
And guys, this thread is leaning towards dumping, which clarification can be simplified by yes or no (nothing new), due to poor documentation etc...
And please, can anyone test this https://play.google.com/store/apps/details?id=zausan.zdevicetest&hl=en
It only shows the DAC name on SoC based systems...
Worked with Galaxy R. Result: WM8990 ...
Can't wait to get the Atrix. I'm eager about it...
Plus, I won't lean to the software part, only hardware.
In case it needs to be re-developed, I will work only on the driver. (More to C orientation / kernel...)
Edit: okay, thanks Night Walker! ! For testing the app
Okay guys,
Anybody owns one of these devices except the Atrix:
T2-A20HP:LG Optimus 2X, Motorola Atrix 4G, Motorola Droid X2, Motorola Photon, Samsung Galaxy R, Samsung Captivate Glide
Other: i9023, i9000, Galaxy Tab.
If yes, try the same app above, seems the only app that shows the chip info through alsa...
O2X uses different implementation, thats why supercurio gave a deep shot supporting it, even though, it only supports bits of the original voodoo capabilities...
Can't wait for the new Kaudio driver, might work with the Atrix with no SoC mods.
Just another sound driver made specifically for voodoo. (LG uses its own implementation to the DAC, its driver)
Here is a screen shot of the sound section of that app on my atrix running paranoid android 1.9.5
r3xx3r said:
Here is a screen shot of the sound section of that app on my atrix running paranoid android 1.9.5
Click to expand...
Click to collapse
Same as yours on neutrino 2.8.
MB860 cihazımdan Tapatalk 2 ile gönderildi
K, the Atrix 4G has a different driver...
Tpr0,
I'm unfortunately not a dev, but is there any way I can help with this project?
Guys, sorry for the delay, got ill. And yes, I know your intentions towards support...
I still haven't got my hands 'tight' on the project, got distracted by setting it up... (the Atrix kernel compilation errors)
Anyways, thanks guys, it certainly needs a (low level dev. me) I'm not a high-level programmer, more into hardware level (intermediate) But this project doesn't seem hard to accomplish, but poor documentation does it... ( IT is based on low level programming )
At present, we have topics every few weeks or so with someone new, coming to ask if GSM works in America. Then, someone wants to help and try to figure out why -- but there is no consistent thread for this. So let's use this.
Does the Droid 4 work in the US on GSM yet? NO
This is to be used as a master thread to post research/thoughts/findings. If anyone has any clever thoughts, please search the thread first to make sure it hasn't been found yet.
What we do know is that with OTA ICS from Verizon, the Droid 4 supports GSM for *OTHER* carriers outside of the US. There could be any number of reasons that it does NOT work. As a quick run-down of the problem, I'll identify where the primary issues could be and allow for anyone else to build upon it, ask questions, and discuss.
The Radio Firmware
-- The firmware for the radio itself could have a lock or a setting that needs to be adjusted and all data requests are blocked through this.
RIL
-- The interface between the radio and Android -- there could be a software lock here that restricts specific carrier ID's.
ROM
-- The ROM itself has a baked-in block for GSM in America.
The best thing we can do is to try and identify or step through the stack (if such is possible -- I'm a developer, but not for Android) and see WHERE the calls break at.
--If it is a software lock in the ROM, then aftermarket ROM's like CyanogenMod should allow data to work in the US. If we're not seeing this, then this is likely not the case.
--If it is a software lock in the RIL library, then we'd have to have a reverse-engineered library (which could be very difficult to do). We should be getting some kind of error somewhere in here. At this point, though, it's hard to tell if the Radio Firmware or RIL is the actual problem.
Anyone with any background on this, please feel free to contribute. correct, and update. I'll try to get back here and update this master page as I see responses further in the thread.
Can we try to load up a deodexed rom and replace the ril file with, let's say one from XT910 in canada?
Sent from my XT894 running ICS
I assume this is just a GSM radio, without HSPA+, but does anyone know the frequencies it uses?
I just finished comparing a Droid RAZR XT912 to a Rogers RAZR XT910, I checked the /system/lib folder and build.prop files.
I found some really interesting differences, and also found that most of the important build.prop differences between the Rogers XT910 and Verizon XT912 were also consistent with the D4.
lines like:
persist.ril.modem.mode = (1 = CDMA, 2= UMTS)
persist.ril.mux.noofchannels = (10 on Rogers, 8 on VZW)
persist.radio.ap.phonetype = (1 = GSM, 2= CDMA)
and my favourite line
persist.ril.features = (0x182 = Rogers, 0x90A = Verizon)
I also found something only in Rogers build.prop:
ro.tether.denied=false
What's also interesting, is that most of the files in the /lib folder is consistent between the D4 and the RAZR, I have also included this report in the attached ZIP file.
Maybe this in combination with some files from the /lib folder might help. Either way, I've included my comparisons in the attached ZIP.
Does anybody want to just try changing the persist.ril.features in the US and see what happens??
Let's get US bands unlocked soon!!!
In my comparissions,
D:\ = XT894
G:\ = XT912
H:\ = XT910
I saw these and a couple other changes comparing the D4 file to the bionic GSM-working ICS leak build.prop. Unfortnately I'm studying for a GRE exam I have tomorrow but will try to give these changes a try when I take a break and if not, definitely by the end of tomorrow. I'm starting to have faith we'll find something. I don't think Verzion did anything that low-level to implement this US carrier block.
Sent from my SGH-T839 using Tapatalk
blackstar1744 said:
I saw these and a couple other changes comparing the D4 file to the bionic GSM-working ICS leak build.prop. Unfortnately I'm studying for a GRE exam I have tomorrow but will try to give these changes a try when I take a break and if not, definitely by the end of tomorrow. I'm starting to have faith we'll find something. I don't think Verzion did anything that low-level to implement this US carrier block.
Sent from my SGH-T839 using Tapatalk
Click to expand...
Click to collapse
School first, xda second. Good luck on your GRE!
Sent from my myTouch_4G_Slide using Tapatalk 2
Trying to get Radiocomm to recognize my phone but my phone keeps switching to mass storage mode even with Android debugging and mock location enabled. Was in Hashcode's AOKP and went back to the stock ROM and now I can stay in Media Device (MTP) but still don't have the appropriate Windows x64 driver. I'm currently running the attached file which I came across at some point in the Android Development forum in my earlier research into this whole domestic GSM issue. Does anyone else have another x64 driver?
The motivation for my question: Yesterday ariethekid claimed to get T-Mobile working on his Droid Bionic running Verizon's official ICS 246 release so the steps on this page *should* work - http://forum.xda-developers.com/showthread.php?t=1297714&page=13 along with the appropriate build.prop modifications. The bionic build.prop I attached includes the necessary changes. They would have to be included migrated to the D4 build.prop and I would/will eventually do it but I'm just not that far along yet given my Radiocomm issues.
Update: The OTA ICS updates already includes this 8 byte revision. I believe the only thing that needs to be done is the update of the build.prop.
blackstar1744 said:
Trying to get Radiocomm to recognize my phone but my phone keeps switching to mass storage mode even with Android debugging and mock location enabled. Was in Hashcode's AOKP and went back to the stock ROM and now I can stay in Media Device (MTP) but still don't have the appropriate Windows x64 driver. I'm currently running the attached file which I came across at some point in the Android Development forum in my earlier research into this whole domestic GSM issue. Does anyone else have another x64 driver?
The motivation for my question: Yesterday ariethekid claimed to get T-Mobile working on his Droid Bionic running Verizon's official ICS 246 release so the steps on this page *should* work - http://forum.xda-developers.com/showthread.php?t=1297714&page=13 along with the appropriate build.prop modifications. The bionic build.prop I attached includes the necessary changes. They would have to be included migrated to the D4 build.prop and I would/will eventually do it but I'm just not that far along yet given my Radiocomm issues.
Update: The OTA ICS updates already includes this 8 byte revision. I believe the only thing that needs to be done is the update of the build.prop.
Click to expand...
Click to collapse
In order to get the RadioComm interface, make sure you're using the latest Motorola Mobile Phone Drivers (these are different than the android drivers), they are version 5.9 as of right now. Please download them from here :
https://developer.motorola.com/tools/usb_drivers/
Looks like the Motorola site is down though, so you can download them from here :
http://handheld.softpedia.com/get/Drivers/Motorola-Handset-USB-Driver-for-Windows-64-bit-38124.shtml
http://forum.xda-developers.com/showthread.php?p=33230579
this was just posted, has all NV lines together, maybe we can figure it out in here!
dewhashish said:
http://forum.xda-developers.com/showthread.php?p=33230579
this was just posted, has all NV lines together, maybe we can figure it out in here!
Click to expand...
Click to collapse
Just a thought. Perhaps these values could be checked against a Bionic?
4869^"GSM Carrier Suppression"^"GSM*"
4870^"GSM 850 Carrier Suppression"^"GSM*"
4871^"GSM DCS Carrier Suppression"^"GSM*"
4872^"GSM 1900 Carrier Suppression"^"GSM*"
blackstar1744 said:
Just a thought. Perhaps these values could be checked against a Bionic?
4869^"GSM Carrier Suppression"^"GSM*"
4870^"GSM 850 Carrier Suppression"^"GSM*"
4871^"GSM DCS Carrier Suppression"^"GSM*"
4872^"GSM 1900 Carrier Suppression"^"GSM*"
Click to expand...
Click to collapse
You would have better luck posting this question in that forum.
By the way, Bionic GSM is a go. They have it fully up and running in that thread. Confirmed working by quite a few users
danifunker tried that already and folks have posted results in this topic (and it didn't work, apparently):
http://forum.xda-developers.com/showthread.php?t=1916869
Apparently, it does not apply to GSM in the US:
http://forum.xda-developers.com/showpost.php?p=32478552&postcount=21
They, however, did not try to toggle 4869. They did 4870 - 4872. Apparently the Bionic ignores those keys and does not worry about it.
Has anyone actually tried, for sure, to toggle these settings and verify whether they work or not?
D4 for US GSM Bump
Hello out there?
Has anyone come up or been experimenting on how to get the domestic U.S. carriers unblocked on the Droid 4? I've been searching high and low and apparently the Bionic fixes do not work on the D4.
daqueenzkid said:
Hello out there?
Has anyone come up or been experimenting on how to get the domestic U.S. carriers unblocked on the Droid 4? I've been searching high and low and apparently the Bionic fixes do not work on the D4.
Click to expand...
Click to collapse
Quite a few poked around, but there hasn't been any progress in the past few months. If this phone had more support, I'm sure it could be figured out, but not like this. It does take brilliant minds at work to figure this stuff out.
Sent from my SGH-I927 using Tapatalk 2
gtmaster303 said:
Quite a few poked around, but there hasn't been any progress in the past few months. If this phone had more support, I'm sure it could be figured out, but not like this. It does take brilliant minds at work to figure this stuff out.
Sent from my SGH-I927 using Tapatalk 2
Click to expand...
Click to collapse
There are some people looking into it but it is absurdly complicated. Granted they keep moving closer to a solution, this is the most complicated phone workaround I've ever seen. Motorola/Verizon is straight evil.
http://forum.xda-developers.com/showthread.php?t=2144335
Sent from my XT894 using Tapatalk 2
blackstar1744 said:
There are some people looking into it but it is absurdly complicated. Granted they keep moving closer to a solution, this is the most complicated phone workaround I've ever seen. Motorola/Verizon is straight evil.
http://forum.xda-developers.com/showthread.php?t=2144335
Sent from my XT894 using Tapatalk 2
Click to expand...
Click to collapse
Yea that's definitely apparent. That's a brand new thread. Haven't seen it before. Those guys are doing alright
Sent from my SGH-I927 using Tapatalk 2
You can try my Rom.
I edited all settings about CDMA to GSM not only build.prop but I'm not in USA so I can not try.
droid bionic gsm unlock
Hey guys. Ive been on XDA for so long and never reslly mentioned that the gsm on my droid bionic on ICS is unlocked. Ive tried alot of methods but one method i used finally worked. i just pop a non verizon sim card in and it works 100%. txt etc.
What is this method?
It's been known and well established that the MDM6600 radio on Bionic, in particular the hardware revision A first production devices, do not have the block on US GSM carriers that the subsequent RAZR/D4 models have and can be made to work with a few simple modifications.
This does not apply to the RAZR/D4 and after a great deal of examination it has been determined that the block is in the signed BP radio image and cannot be disabled via NV editing nor any other means.
Hello all, Quick question about the Motorola Droid. I have heard that this is/was a popular phone for custom ROMs. I found a new one locally for $40 and am thinking about purchasing it. I have am currently using a Galaxy S3 which has limited possibilities due to the know that came with 4.3 OTA. I also have been playing with a Samsung Charge but that never really had a lot of ROMs developed and traffic on that forum has come to a standstill.
So my questions, Does the the Motorola Droid forum still happening and functioning? Are there many custom ROMs to play with? A quick glance at post dates lead to mixed data.
Second, the phone I found was a A855 with slide out keyboard. When I see a reference to the 'Motorola Droid' or even the Motorola Droid 1' as in this post http://forum.xda-developers.com/showthread.php?t=1098483 are they referring to the A855 or the A853 for even some other phone? Seems confusing.
Thanks for any help!
You know it was a great phone and still is (build quality, screen, qwerty, etc) but it is really outdated.
I mean RAM is the bottleneck of Android and this phone has only 256MB.
If you want a phone to mess around with it, then go ahead, if you need a qwerty Android phone, buy a Moto Photon Q.
Afaik, there are no active developer on the Droid (the development on the Milestone halted a year ago).
Btw, A855 is the NA edition but you can look it up on wikipedia.
It was a great phone while it lasted, and there are a ton of roms out there, but as far as I know there aren't any with active development. I still get mine out every once in a while to mess with, but it isn't really good for anything except a toy at this point.
Hi there, I have a question about Droid turbo, because i'm between LG G3 and Droid Turbo.]
I would like to know with the software of Droid Turbo is good than LG G3 and if it has multi task like LG G3 and S5
Any owner of droid turbo can help me with it ?
RaR System said:
Hi there, I have a question about Droid turbo, because i'm between LG G3 and Droid Turbo.]
I would like to know with the software of Droid Turbo is good than LG G3 and if it has multi task like LG G3 and S5
Any owner of droid turbo can help me with it ?
Click to expand...
Click to collapse
Android operating system will multi-task by default - so Turbo does true multi-tasking like any other Android device. However, some apps (Youtube) will pause/terminate when you switch away from them. That is due to the way that the app is programmed, not due to the operating system. (Youtube has just been updated with a music mode that will keep music videos playing even when you switch away from them).
Some android devices take that extra step of having "multi-windows" so that you can have 2 apps running on the screen at the same time. The Turbo doesn't do this; the Galaxy Note 4 does.
jasoraso said:
Android operating system will multi-task by default - so Turbo does true multi-tasking like any other Android device. However, some apps (Youtube) will pause/terminate when you switch away from them. That is due to the way that the app is programmed, not due to the operating system. (Youtube has just been updated with a music mode that will keep music videos playing even when you switch away from them).
Some android devices take that extra step of having "multi-windows" so that you can have 2 apps running on the screen at the same time. The Turbo doesn't do this; the Galaxy Note 4 does.
Click to expand...
Click to collapse
Ooh right, and sorry I did confusion with multi task and multi window... I did this question because i'm between LG G3 and Droid Turbo, I have a RAZR HD but unfortunately I had some problems with him, and now I don't know with I keep with motorola (droid turbo) or I try a new product like LG G3 (I liked so much of the modifications that LG did)
I stay preoccupied if I buy a LG G3 because it's a snap801 while Droid Turbo 805 ...
Both are good phones
I recently went with choosing the Droid turbo over the G3. I'm happy with my choice. My friend who has a G3 likes it, and yes it has some really neat features, but he said that my phone is way faster than his. Plus if you use your phone a lot, then the turbo battery is great for you especially if you're on the go a lot. So it comes down to preferred device.
Honestly when will you honestly use the multitasking feature? When I had the g2 and partially the g3 for a while I rarely used that feature and mostly used it to show off to my friends.