Just wondering. Waiting to really do some fun stuff with this fun if/when we gain that capability. Does anyone know if any of our roms have it?
Bulletproof doesn't yet but I was around and very closely following that develop from nothing to something on the Nook Color and have at least some of the project files from playing along way back when.
It's on the short list when I get the chance to start working on the ROM again, because I plan to use that as a band-aid for the PS3 controller while working on fixing the BT issue around that in Sense.
It would also be nice to be able to plug in and use my handful of flash drives while out and about using the compact package the doubleshot is instead of having to rely on something as large as the tablet as the best I got.
Right now there are other issues to work out on the device first as far as my dev time is allocated, and I can't speak for any other dev's work, but I am curious as well to know if anyone else is spending time on this.
Sent from a digital distance.
Thanks Blue "The Reason I Still Have My Doubleshot" 6IX. I am looking forward to the day this arrives. Been in the NC forum salivating over USB host stuff. It's more than a bit for my skill level at this point but fascinating! I'm going to mainly be utilizing DSLR Controller.
Sent from my myTouch 4G Slide using Tapatalk
Blue6IX said:
Right now there are other issues to work out on the device first as far as my dev time is allocated, and I can't speak for any other dev's work, but I am curious as well to know if anyone else is spending time on this.
Sent from a digital distance.
Click to expand...
Click to collapse
Well I'm so glad you have a plan
Just a side question for you Blue: IF we do get a OTA update from T-Mobile or HTC and it is ICS...would you rebase to that and start developing for ICS?
Because I see you are trying hard to make the stock ROM all that it can be; but if we get a OTA ICS would you switch your attention to making that 'all that it can be?'
Typed by ---- oh wait! I'm schizophrenic!
Blue6IX said:
Bulletproof doesn't yet but I was around and very closely following that develop from nothing to something on the Nook Color and have at least some of the project files from playing along way back when.
It's on the short list when I get the chance to start working on the ROM again, because I plan to use that as a band-aid for the PS3 controller while working on fixing the BT issue around that in Sense.
It would also be nice to be able to plug in and use my handful of flash drives while out and about using the compact package the doubleshot is instead of having to rely on something as large as the tablet as the best I got.
Right now there are other issues to work out on the device first as far as my dev time is allocated, and I can't speak for any other dev's work, but I am curious as well to know if anyone else is spending time on this.
Sent from a digital distance.
Click to expand...
Click to collapse
whaddya mean ps3 controller? is my doubleshot going to finally work on a ps3? O.O and what is usb host support exactly anyways and what can it be used to do ?
Appreciate the kind words _atlien_
@CoNsPiRiSiZe :
If HTC releases an official ICS ROM with corresponding kernel source, i'd jump on that pretty exclusively in an instant without a backward thought.
The only kernel source we have is 2.6.35.10 which corresponds to the 1.28.531.9 / .10 software version. This is really the limiter on my decision for what to work with.
Being as this is my first Android phone, I don't really know enough yet about how it works to be comfortable writing my own source for a kernel (basically) from scratch like tbalden and others are doing, so starting with a working and official source is necessary at this point in my education so I can make progress instead of a mess.
I imagine by the time I eventually move on to another device I'll know enough to just do what I want. Not having prior experience with this stuff is a bit frustrating sometimes because I do really want to play with ICS and the latest and greatest Google is providing us. Intentionally ignoring it sucks, but i'd rather make progress and not problems, hence this is my pennance for not getting a smart phone before this device launched.
I'd rather get a solid education then a whole lot of scattered knowledge if possible, my aim is for being involved with Android for a long time to come so having the patience and restraint to build a solid base of knowledge on how it works will serve me well in the future, even if it forces me to work with yesterday's software now.
Think of it like learning to drive a stickshift on a $200 beater P.O.S. instead of in a lamborghini - you could do it either way but one method makes more sense then the other.
The other thing, though, is the balance of trying to do what would most benefit the whole doubleshot user base the most instead of just the people on my ROM or whatever, so something like working on and posting details about progress on S-OFF trumps it all because that is the single most important issue I can help with I think. Even if I don't get it, maybe my notes and discoveries will help someone else solve it who has a better understanding or more experience with that kind of stuff.
Both of my devices were S-OFF and I had to go out of my way to learn how to put one S-ON again to work on the problem, I could have just ignored it because it didn't affect me but i'd rather try to help everyone, at any cost, then just serve my own selfish desires.
/end thread derailment
----
The question still remains, though, is anyone else working on USB host / OTG cable support?
Sent from a digital distance.
Some_dude36 said:
whaddya mean ps3 controller? is my doubleshot going to finally work on a ps3? O.O and what is usb host support exactly anyways and what can it be used to do ?
Click to expand...
Click to collapse
PS3 controllers cannot connect to and be used by HTC Sense devices, the bluetooth software HTC went with prevents it. If you flash an AOSP ROM you can use one, though, so it's not that it doesn't work but that HTC doesn't want to let us. (Technically broadcomm, but their name isn't printed on the device)
USB host support means that if you get a micro-usb to female USB cable or an adapter you could plug in flash drives, portable hard drives or even other devices to this phone directly.
Since I can get usb cables and adapters at the dollar store now, they aren't hard to come by.
Being able to plug in a flash drive, or install linux on the doubleshot and use it to run the android sdk and program other phones or android devices by plugging it in to this one would be nice - I can install linux on my nook color and then plug this phone into it directly and run fastboot commands while I'm sitting on the bus or something without a bulky laptop - pretty sweet, huh?
No reason we can't do it with this nice, tiny, portable android powehouse other then someone hasn't sat down to take the time and make it happen.
Sent from a digital distance.
I thought the cable used for the ps3 was for charging only and still sends signal via bluetooth. I knoww that's how the xbox works with it's plug and play kit.
Sent from my HTC myTouch_4G_Slide using xda premium
ps3 controllers
PS3 controllers communicate with either USB or bluetooth. He was refering to using the bluetooth part with our phones and "sixaxis controller" app to pair them together.
Any new word on this?
I know tbalden an kornyone have put together a customized kernel for the CM9 alpha releases in http://forum.xda-developers.com/showthread.php?t=1644084
I haven't seen any mention of USB host mode, but I don't have enough posts on xda to ask if that's even a consideration.
my aokp rom has customizable usb host support. idk if cm does
Man, I'd love to see OTG in Miktouch or one of the Sense ICS ROMs.
scverhagen said:
UPDATED 10-27-2012 (r7b)
ROM
This is the stable version of CyanogenMod 9.1 with some modifications:
- Battery drain bug fixed
- Remote Wipe hack/exploit patched (see here)
- Includes modified kernel (see next section)
Stable Kernel
- Linux Kernel 3.0.48
- Kernel debugging disabled to improve performance]
- USB Fast Charge - credit to yank555-lu and xmc-wildchild22
- Undervolting tweaks - credit to xmc-wildchild22
- Overclocked GPU - credit to xmc-wildchild22
- Snapdragon optimizations - credit to xmc-wildchild22
- Inverted front facing camera mirroring issue [r3] (CyanogenMod)
- bluetooth deep sleep issue fixed (lpm -- credit to Agrabren) - modified in [r5] to (hopefully) reduce wifi drain issues
- ondemandx governor (existz [email protected])
- lulzactive, lulzactiveq, and hotplug governors (thanks to SilverL for the pull request)
- IO Schedulers: noopp, deadline, cfq, sio, vr
- USB OTG support (SebastianFM)
- Camera flash enabled down to 5% battery [r7]
- zsmalloc from kernel 3.5 (godmachine81) [r7]
Click to expand...
Click to collapse
quoted from cm9.1
mattlowry said:
quoted from cm9.1
Click to expand...
Click to collapse
Too bad it isn't a Sense ROM. Hopefully, someone will be able to incorporate it into one soon. I just don't like CM or AOKP at all.
Related
Is there a way to get basic RNDIS or ECM support using a USB host cable?
I have a 4G USB dongle that is hostless, meaning it does not require any drivers to run. It simply needs the PC/Tablet to recognize ethernet over USB. It works great on a my laptop running either Win7 or Ubuntu without installing any drivers.
Using an OTG USB cable that I made the dongle will connect to the network just fine, just the Xoom does not recognize the ethernet connection over USB.
Can anyone offer some help? Right now my Xoom is completely stock, but if there is hope that this can work with some other kernel I am up for experimenting.
I'm not familiar with the method you're asking about, but Tiamat 1.4.2 (http://forum.xda-developers.com/showthread.php?t=978013
) has this listed in the release notes:
•Implemented USB Ethernet for USB Tether from phone to Xoom!
Whether it meets your protocol needs is the question to ask in that thread I guess?
I noticed that as well. I am currently running completely stock right now. I am a little concerned with going down this path. I know there is a ton of information out there and honestly it is a bit overwhelming. I am not concerned with the actual process but more any negative impacts to running a custom kernel. I am not even sure if these are valid concerns.
-OTA updates
-Netflick and Google Movies
-Android and Amazon purchased applications
-Stability
I know this is going to derail this topic but can you share with me your experience?
Netflix works on my rooted epic, just Google movies seem to be the issue.
All app purchases are linked to your respective accounts, they carry across devices and flashes.
OTA updates should never be excepted if your rooted.
Stability is usually greater on custom kernels and Roms than the stock experience. How ever it can take a few flashes to find the right combination for your taste, style, and needs.
Sent from my SPH-D700 using XDA Premium App
There is a lot of info and paths to choose. Go slowly and follow directions concisely. If you're not sure ask before embarking.
If it doesn't work out you can always go back to stock.
Ota are always reworked for rooted users - never accept an ota on a customer kernel without the dev saying OK.
Google movies doesn't work - I'll bet Google is afraid that stream recording will take place and they have to avoid piracy.
Netflix doesn't exist for xoom yet but there's a good chance it will work since Netflix auth is by device/account, not just account.
Market follows account - any device any kernel.
Stability varies on kernels, but the most popular ones are usually more stable and have better features/fixes than stock.
Sent from my Xoom using Tapatalk
Thank you both for your comments. I may just go the Tiamat route. I need to find a good step by step guide, including all steps to go from bone stock to having the custom kernel. There are a lot of guides on doing each step individually, but it would be nice to find one concise guide so I do not miss something in the middle.
I am pretty happy with my Xoom now, the only driving factors are the USB over ethernet and it would be nice to use my SD card for something. Neither one of these is a huge deal, just a nice to have. Given enough time I think Google\Motorola will fix the SD card. The USB over ethernet is more of a neat trick. I am usually in an area with WiFi and if not I can BT tether to my phone. The WiMax dongle would be interesting to have as a third option.
I see there are some options with the latest kernel with how much overclocking, so I will most likely be conservative and go with the slower one.
I want to keep the g1 alive, so here's something I'm offering to the community.
I have set up a server dedicated to g1/magic rom and kernel development. It is rather low spec and not the best machine for this, but it's better than nothing and will be upgraded as I get more money and if I get a reasonable amount of users.
if you want to use this, just send me a pm with the following info:
- desired username
- password you want
- project you want to work on
After I receive a pm, I'll set up your account and tell you what server and port to connect to via SSH. You can pull your files of via scp, sftp, and (once I set it up) http
Specs:
Operating system - debian Sid
Pentium 4 - 2.8 ghz, HyperThreading enabled
1gb ram, 6g swap (another gb of ram will be added later)
Hard drives are formatted with ext4 (keeping it simple this time..)
Drive 1 - 80gb (for now)
build stats (from the old box. should be similar. will update later):
Cm7:
Clean build: - 2-3 hours (haven't really timed)
Rebuild - 8-20 minutes, depending on how many changes
Cm9:
Clean build - start at night, check in the morning. a long time
rebuild - around 20 minutes
More info on how the build server will work:
For devs:
-anyone can use it, just send me a pm.
-it is dedicated to building g1 roms, but during downtime i am okay with people using it for other small projects.
-there will be no bandwidth or storage limits (besides the physical 300 + 230 gb limit of my harddrives) unless I'm forced to set them
-no guaranteed uptime. it'll probably be okay, but i like to experiment, so no promises.
-I'll announce here anything about downtime (and try to give an hour or two warning)
-I'm obsessed with security, but that shouldn't matter here (you don't have anything to hide, right?) through the use of simple unix permissions, your work will only be able to be accessed by you (and root obviously, but no one but me has root access)
for regular users with no interest in development:
once there are enough people using this, i will post a link here to a website where you can download users work. still figuring out how I want to implement this. I'm a nerd, i want it fancy and nerdy.
current users:
previous users:
me
dfang123 (idk his xda username.. should know it)
arnold (xda username? Idk..)
Cole2kb
Austrie
Server status: getting set up again
well... there seems to be no interest for this. ~24 hours and i am giving up on the idea.
oh that's too bad I wish the dream would stay a little more active for longer
tvall said:
Server status: online.
any other users? come on guys..
Click to expand...
Click to collapse
Do not get discouraged...!!will continue online?
ROCKO1234 said:
Do not get discouraged...!!will continue online?
Click to expand...
Click to collapse
its still up, but no one is really using it yet. i also havent figured out what its next job will be.. so untill i get users, or think of something else to do, its still online
tvall said:
its still up, but no one is really using it yet. i also havent figured out what its next job will be.. so untill i get users, or think of something else to do, its still online
Click to expand...
Click to collapse
and has not said anything of his work ics..
I'm bad to develop u___u,
raydar670 said:
oh that's too bad I wish the dream would stay a little more active for longer
Click to expand...
Click to collapse
Lol, just because people don't want/need to use a build server does not mean that the HTC Dream is dead LOL.
I think this is a great idea, but I already have a development computer
Infinimint said:
Lol, just because people don't want/need to use a build server does not mean that the HTC Dream is dead LOL.
I think this is a great idea, but I already have a development computer
Click to expand...
Click to collapse
i guess ill keep it ready for a while then
No one in the g1 section seems interested... but I got a user wanting to develop for the LG optimus v! So I guess there is interest in something like this.
well... someone decided it would be a good idea to randomly pull the power cord while the box is running. btrfs doesnt handle sudden reboots too well... well now the box has been wiped and reinstalled. you should re sync your repos and go back to normal life. (todays project= off-site backups [this was also my backup server..])
Well if anyone cares, completed a minor hardware update to the box today.
A few days ago I switched from ext4 to btrfs (yes, I know, I'm insane). Today I added a 230gb hdd to the btrfs pool.
Btrfs is currently set up to mirror metadata and stripe data (raid1 metadata, raid0 data). So now we have a "fast" "530gb" hard drive.
(For those of you who don't know, btrfs is a new filesystem with cool features like snapshots, checksumming, raid, subvolumes, compression... etcetera. Its great, but not considered "stable" yet [but the fedora distro is seriously considering making it default. And the Ubuntu installer makes use of all the cool features out of the box if you select it. Debian.. supports it]. I haven't had issues with it that weren't caused my my stupidity yet)
Also changed the hostname ("debian" is boring, it is now Athena)
Small note: my girlfriend told me I'm not allowed on my computers tomorrow. So.. I won't be making any changes, building anything, or rebooting the box. But if it goes down on its own, I won't be on to fix it.
Another random piece of info: I have 3 Pentium 4 computers all kept in the same spot (they are my only computers...). I compiled the Linux 3.3.4-ck1 kernel on all of them with the same config. This box is fastest.
tvall said:
Small note: my girlfriend told me I'm not allowed on my computers tomorrow. So.. I won't be making any changes, building anything, or rebooting the box. But if it goes down on its own, I won't be on to fix it.
Click to expand...
Click to collapse
tell her she cant dress up or go shopping or w/e shes passionate about then! xD
Shano56 said:
tell her she cant dress up or go shopping or w/e shes passionate about then! xD
Click to expand...
Click to collapse
Well... I'd like to not piss her off. She kinda has a lot of say in some of the activities I really enjoy doing. One day of going to the park or something to keep her happy is definitely worth it
And I like her photography, not going to tell her to stop that
tvall said:
Well... I'd like to not piss her off. She kinda has a lot of say in some of the activities I really enjoy doing. One day of going to the park or something to keep her happy is definitely worth it
Click to expand...
Click to collapse
Happy wife (girlfriend), happy life.
Sent from my HTC PH39100 using Tapatalk 2
I just put a few missing parts in my other p4 box. Should I set it up as a second, separate server, or should I try to set up a cluster? (If I go cluster, that's 3 p4 cores between 2.8 and 3.2 ghz w/ ht and a total of 7.5gb ram [I'd use all 3 boxes I have])
Anyone have experience with clusters?
Also, I'm currently using a Linksys e2000 router. But there are no more open Ethernet ports... anyone know of a reliable wifi router with more than 4 LAN ports, wifi n, and supported by openwrt or tomato? Or should I just take the jump up to a switch an firewall with a wifi router behind it?
tvall said:
I just put a few missing parts in my other p4 box. Should I set it up as a second, separate server, or should I try to set up a cluster? (If I go cluster, that's 3 p4 cores between 2.8 and 3.2 ghz w/ ht and a total of 7.5gb ram [I'd use all 3 boxes I have])
Anyone have experience with clusters?
Click to expand...
Click to collapse
A cluster would be pretty cool and would make for much faster build times, but I myself have never made a cluster nor do I have any experience with making them. However, it looks as if these could be of some help:
http://www.mcsr.olemiss.edu/bookshelf/articles/how_to_build_a_cluster.html
http://byobu.info/wiki/Building_a_simple_Beowulf_Like_Cluster_with_Ubuntu
http://source.android.com/source/downloading.html#using-a-local-mirror
Infinimint said:
A cluster would be pretty cool and would make for much faster build times, but I myself have never made a cluster nor do I have any experience with making them. However, it looks as if these could be of some help:
http://www.mcsr.olemiss.edu/bookshelf/articles/how_to_build_a_cluster.html
http://byobu.info/wiki/Building_a_simple_Beowulf_Like_Cluster_with_Ubuntu
http://source.android.com/source/downloading.html#using-a-local-mirror
Click to expand...
Click to collapse
started working on this today
i can run a helloworld on all 3 boxes i have and get a response from all three. can also run hostname on all 3 and get each hostname back. now i just have to set it up to build android!
Is there any major milestone that must be overcome in order for the cyanogenmod team to officially support the HOXL? Are we just waiting for ROM cooks to take initiative? I know S-off is nice to have, but I don't believe it's a requirement.
No but kernel source would be required for jelly bean at the very least. And probably a little more developer interest.
Sent from my HTC One XL using Tapatalk 2
jordanetodd said:
No but kernel source would be required for jelly bean at the very least. And probably a little more developer interest.
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
what's the deal with developer interest on the One X ? Is this not a popular phone or is it that most developers bought an international version?
Seems like ther'es been a fair amount of work as far as ROMS and mods and things go, but the Kernel source is the reason that there are working JB roms for the GS3 and we don't even have CM9 fully working yet....
I believe the developer interest come from a few factors.
1) There are few developers that get paid nothing and porting CM9/10 is a lot of work.
2) There are hundreds of devices how do you pick which one gets the CM9/10 .... sales.
The HTC One XL is a nice device but as a LTE device and from HTC it is likely not the strongest selling phone in North America
shorty6049 said:
what's the deal with developer interest on the One X ? Is this not a popular phone or is it that most developers bought an international version?
Click to expand...
Click to collapse
There's definitely more people on the One X international version. People will find that most phones with kernel source available and unlocked bootloader will draw more developers... But in this case quantity =/= quality. I've had several android phones over the years and yes, while it's nice to have a giant land of developers with pages and pages of roms to look through, they lose their luster to mediocrity. You'll find some of the best devs who weren't discouraged by the locked down devices such as this one, and as a result, the product (ROM, kernel, etc) will always be top-notch. And a smaller, more intimate dev community encourages more interaction and community support, making the overall experience that much better.
I think we already have pretty solid support, given that there's still no kernel source available.
We have great Sense-based ROMs (the CleanROM family, amongst others) as well as pretty-solid alphas of CM9 and AOKP. Personally I've been very tempted to try either CM9 or AOKP, but I haven't made the plunge yet. A friend of mine is using CM9 has his daily driver without issue.
I believe the team working on CM9 has plans to incorporate their currently-unofficial branch into being officially a part of CM9 (or CM10) once kernel source is released and the remaining issues are resolved.
Functioning CM9/10 is all i really want on this device. I don't need anything flashy. Just give these awesome devs the source kernel HTC!!!
The major milestone is kernel source. Without it, the devs can't squash some of these remaining bugs on our device. Without that, we won't get merged into the main branch (afaik). As to why there are more people on the international version, just look at what you just said. The INTERNATIONAL version. It's available on more carriers and yes, it is a heck of a lot easier to develop for since they didn't have to waste time trying to figure out how to unlock the bootloader (which makes them at least a month of ahead of us in terms of development) and they have source.
Trust me, once we have source, development will skyrocket.
---------- Post added at 04:47 PM ---------- Previous post was at 04:45 PM ----------
pearlbrian said:
Functioning CM9/10 is all i really want on this device. I don't need anything flashy. Just give these awesome devs the source kernel HTC!!!
Click to expand...
Click to collapse
Our CM9 port is totally functional! Though...not 100%...but from what I've seen it's good enough for a daily driver. I'm running AOKP M6.2 and it's perfectly usable.
stnguyen09 said:
The major milestone is kernel source. Without it, the devs can't squash some of these remaining bugs on our device. Without that, we won't get merged into the main branch (afaik). As to why there are more people on the international version, just look at what you just said. The INTERNATIONAL version. It's available on more carriers and yes, it is a heck of a lot easier to develop for since they didn't have to waste time trying to figure out how to unlock the bootloader (which makes them at least a month of ahead of us in terms of development) and they have source.
Trust me, once we have source, development will skyrocket.
---------- Post added at 04:47 PM ---------- Previous post was at 04:45 PM ----------
Our CM9 port is totally functional! Though...not 100%...but from what I've seen it's good enough for a daily driver. I'm running AOKP M6.2 and it's perfectly usable.
Click to expand...
Click to collapse
Sorry, i didn't mean functional. I meant, like you said, 100%.
pearlbrian said:
Sorry, i didn't mean functional. I meant, like you said, 100%.
Click to expand...
Click to collapse
yeah, my issue is that the few things that ARENT working are the things I want the most. Frustrating that this is as good as it can get unless HTC releases that source (which it's sort of staring to look like they may get away with not doing at all)
I think source will come. It's just sad that i have JB running on my old as bones Captivate while my shiny new one x is stuck with Sense :crying:
AOKP is great, very little doesn't work. It even has NFC. I have been using it for about a week. Very stable.
Sent from my HTC One X using xda premium
kleeman7 said:
AOKP is great, very little doesn't work. It even has NFC. I have been using it for about a week. Very stable.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
what on AOKP doesn't work currently? I'm trying to decide whether to switch back to something like CleanROM DE or over to AOKP right now.
I just got a nexus 7 and was planning on using it as a nav/media player in my car , mounted in front of the existing stereo. What I'd like to do is use my phone as a wifi hotspot (triggered by a NFC tag in the car) and then stream music through the tablet via bluetooth.
shorty6049 said:
what on AOKP doesn't work currently? I'm trying to decide whether to switch back to something like CleanROM DE or over to AOKP right now.
I just got a nexus 7 and was planning on using it as a nav/media player in my car , mounted in front of the existing stereo. What I'd like to do is use my phone as a wifi hotspot (triggered by a NFC tag in the car) and then stream music through the tablet via bluetooth.
Click to expand...
Click to collapse
If you connect your tablet through the wifi hotspot on your phone then you wouldn't need bluetooth right?
SkizzMcNizz said:
If you connect your tablet through the wifi hotspot on your phone then you wouldn't need bluetooth right?
Click to expand...
Click to collapse
Not quite sure what you mean,
The tablet would get Internet from my phone, then I'd use the tablet to stream music to my stereo via bluetooth
shorty6049 said:
what on AOKP doesn't work currently? I'm trying to decide whether to switch back to something like CleanROM DE or over to AOKP right now.
I just got a nexus 7 and was planning on using it as a nav/media player in my car , mounted in front of the existing stereo. What I'd like to do is use my phone as a wifi hotspot (triggered by a NFC tag in the car) and then stream music through the tablet via bluetooth.
Click to expand...
Click to collapse
From the AOKP thread:
What doesn't work:
Tethering (coming soon)
Panorama mode in Camera app
2G/3G switch (needs kernel source)
Same multitouch bug as CM (needs kernel source) <- When you have multiple touch points active and you remove one, the phone loses track of all of the others
Face Unlock
Other things may come up too depending on your specific situation (especially if you don't clear dalvik and cache or don't factory reset).
stnguyen09 said:
From the AOKP thread:
What doesn't work:
Tethering (coming soon)
Panorama mode in Camera app
2G/3G switch (needs kernel source)
Same multitouch bug as CM (needs kernel source) <- When you have multiple touch points active and you remove one, the phone loses track of all of the others
Face Unlock
Other things may come up too depending on your specific situation (especially if you don't clear dalvik and cache or don't factory reset).
Click to expand...
Click to collapse
Edit- I was looking at the wrong AOKP thread.
(for whatever reason, android beam doesn't seem to be working when I try it on milestone 6.2 though) I touch the phone to the tablet (both with NFC and android beam turned on) and nothing happens.
Tried it with a photo open as well to see if you needed content to beam . No luck
shorty6049 said:
Edit- I was looking at the wrong AOKP thread.
(for whatever reason, android beam doesn't seem to be working when I try it on milestone 6.2 though) I touch the phone to the tablet (both with NFC and android beam turned on) and nothing happens.
Tried it with a photo open as well to see if you needed content to beam . No luck
Click to expand...
Click to collapse
I don't think beam can actually send photos, only links and contact information. SBeam on the SGSIII can send files and such because it uses Wifi Direct to transfer files. Try sending a web page or a contact card between your devices and see if that works? I've never used NFC yet so I'm just going by what I read.
stnguyen09 said:
I don't think beam can actually send photos, only links and contact information. SBeam on the SGSIII can send files and such because it uses Wifi Direct to transfer files. Try sending a web page or a contact card between your devices and see if that works? I've never used NFC yet so I'm just going by what I read.
Click to expand...
Click to collapse
I got it to work using CleanRom (not a photo, it told me it didn't support receiving large files) . I might flash something new tonight... I really just want something that does wifi tether (which I'll have to read into more... I feel like it's tougher to get that feature working on this phone than it was on my Evo) and NFC (so I can automatically turn on tethering when I get in the car) . I'm alright using a sense-based ROM if I have to since anything is pretty fast on this phone and cleanrom is relatively AOSPish
stnguyen09 said:
I don't think beam can actually send photos, only links and contact information. SBeam on the SGSIII can send files and such because it uses Wifi Direct to transfer files. Try sending a web page or a contact card between your devices and see if that works? I've never used NFC yet so I'm just going by what I read.
Click to expand...
Click to collapse
Sending Photos only works on JB. With ICS you can you can send contact info and Youtube links. Works between CM9 on One X and my N7 running JB.
Hey, I'm a noob, let's get that out of the way first.
Alright, so I'd like to know, why is it so hard to get special ROMs working on certain devices?
For example, I have an Evo 3D (HTC Evo V 4G, whatever), so why is it so hard to get, say, stock ICS running on it?
Inthe end, isn't the hardware all the same, other than say processors and screen size? To get a stock ICS ROM working, couldn't you just pull it off of a similar phone with an S3 processor and a 4.3 inch screen?
Or is it not that simple? Are different codes baked into the hardware that make it impossible to just modify the pixel density, size of the screen and have the ROM work with the processors?
I understand the cameras are different, hence cameras not working on early builds of CM9... but considering many phones run the same processors, couldn't they just all work?
Please explain... thanks, thebeastglasser.
thebeastglasser said:
Hey, I'm a noob, let's get that out of the way first.
Alright, so I'd like to know, why is it so hard to get special ROMs working on certain devices?
For example, I have an Evo 3D (HTC Evo V 4G, whatever), so why is it so hard to get, say, stock ICS running on it?
Inthe end, isn't the hardware all the same, other than say processors and screen size? To get a stock ICS ROM working, couldn't you just pull it off of a similar phone with an S3 processor and a 4.3 inch screen?
Or is it not that simple? Are different codes baked into the hardware that make it impossible to just modify the pixel density, size of the screen and have the ROM work with the processors?
I understand the cameras are different, hence cameras not working on early builds of CM9... but considering many phones run the same processors, couldn't they just all work?
Please explain... thanks, thebeastglasser.
Click to expand...
Click to collapse
Is not that easy! I'm an EVO user/rom porter and I hear this alot where users such as yourself think is an easy process BUT is not. Same processor, same screen size maybe the same BUT at times the kernel is not there. Either the kernel for the device doesn't support ROM A or ROM B and therefore it can't be ported to whatever device or the libs keep it from running half way decent.....i.e WiFi doesn't work, sound is **** up or whatever the case maybe...just not functional to say the least.
Take for example Sense 4.0 on the One V....it was ported to the EVO4g and the ROM barely works! Both the One V and the EVO4g have similar hardware but one runs Sense 4.0 like a dream and the other one struggles with simple things like WiFi and Sound.
Now I'm sure someone else with a bit more knowledge on this can get into the specifics and the why's and what's of WHY this can't happen BUT that's it in a nut shell.....the kernel and 9/10 times libs
See ya around dude!
Hey first off, thanks! Second...
Another question then. If they all have relatively similar hardware, why isn't it that a universal kernel for similar phones can't be created?
Or better explained, what about the phone, makes it so that the kernel doesn't work? Or why couldn't you just take the kernel from device A and shove it on device B?
Sorry if I'm overloading you with questions, but hey I'm curious. Ya know?
EDIT: Or if they're practically both the same phones, why is it that you can't just take the ROM AND the kernel from phone A and put it onto phone B?
thebeastglasser said:
Hey first off, thanks! Second...
Another question then. If they all have relatively similar hardware, why isn't it that a universal kernel for similar phones can't be created?
Or better explained, what about the phone, makes it so that the kernel doesn't work? Or why couldn't you just take the kernel from device A and shove it on device B?
Sorry if I'm overloading you with questions, but hey I'm curious. Ya know?
EDIT: Or if they're practically both the same phones, why is it that you can't just take the ROM AND the kernel from phone A and put it onto phone B?
Click to expand...
Click to collapse
It's the manufacturer of the device who would need to release the kernel sources for the certain firmware version which they won't do continuously. In other words, device A may get ICS, hence the kernel sources may be released, but device B may be stuck with gingerbread and may not have a kernel which supports ICS. Back-porting can be done, but in many cases it is very difficult and in the end there still could be a lot of bugs.
You can't just take a kernel and "shove" it in another device. If you did this, it's quite likely nothing would work. The device would not even boot. Remember, the kernel is the center of android (Linux), so everything needs to be "linked" and correspond with each other exactly for it to work (I'm trying to make it as simple as possible ).
If they are the same devices, that would not be necessary. They would use the same roms/kernels. If they are just very similar (e.g. the a100 and a500) you may have some luck with the roms, but not the kernel. Some a500 roms can be flashed onto an a100 and work flawlessly BUT the device's original kernel must be restored for the device to boot.
Theonew said:
It's the manufacturer of the device who would need to release the kernel sources for the certain firmware version which they won't do continuously. In other words, device A may get ICS, hence the kernel sources may be released, but device B may be stuck with gingerbread and may not have a kernel which supports ICS. Back-porting can be done, but in many cases it is very difficult and in the end there still could be a lot of bugs.
You can't just take a kernel and "shove" it in another device. If you did this, it's quite likely nothing would work. The device would not even boot. Remember, the kernel is the center of android (Linux), so everything needs to be "linked" and correspond with each other exactly for it to work (I'm trying to make it as simple as possible ).
If they are the same devices, that would not be necessary. They would use the same roms/kernels. If they are just very similar (e.g. the a100 and a500) you may have some luck with the roms, but not the kernel. Some a500 roms can be flashed onto an a100 and work flawlessly BUT the device's original kernel must be restored for the device to boot.
Click to expand...
Click to collapse
I have the strangest feeling I just tried to jump into the shallow end of the swimming pool, and yet instead was shot out of a cannon into the middle of the sea without a scuba diver's suit... If only I could understand this more!
thebeastglasser said:
I have the strangest feeling I just tried to jump into the shallow end of the swimming pool, and yet instead was shot out of a cannon into the middle of the sea without a scuba diver's suit... If only I could understand this more!
Click to expand...
Click to collapse
Think about it this way. The Android OS could be run on a number of different devices that run slightly different hardware such as cameras, touchscreens, processors, etc...but the OS has to be able to communicate properly to that hardware using device drivers. Just like Windows from a 30000 foot view. It can run on a Dell or Acer computer, but must have the proper drivers.
If the manufacturer's of those devices do not write ICS drivers or preferably furnish their source code, then it is incredibly difficult if not impossible for someone without the internal company documentation to write such a driver.
mf2112 said:
Think about it this way. The Android OS could be run on a number of different devices that run slightly different hardware such as cameras, touchscreens, processors, etc...but the OS has to be able to communicate properly to that hardware using device drivers. Just like Windows from a 30000 foot view. It can run on a Dell or Acer computer, but must have the proper drivers.
If the manufacturer's of those devices do not write ICS drivers or preferably furnish their source code, then it is incredibly difficult if not impossible for someone without the internal company documentation to write such a driver.
Click to expand...
Click to collapse
Ohhh... so say you decided to put your own little phone together according to your own prerequisites, it'd be simple for you to do something on it, but not so much for someone who only has the hardware to look at... correct?
Another question, why is it so easy to port things onto Nexus Devices? Are they just more compatible with all drivers? As I've heard from one of my friends that he has a fully working Sense 4 ROM on his Nexus S... and yet it's tough to find one for my Evo V.
EDIT: I'm out of "thanks" I'll give you one as soon as I get some more...
thebeastglasser said:
Ohhh... so say you decided to put your own little phone together according to your own prerequisites, it'd be simple for you to do something on it, but not so much for someone who only has the hardware to look at... correct?
Another question, why is it so easy to port things onto Nexus Devices? Are they just more compatible with all drivers? As I've heard from one of my friends that he has a fully working Sense 4 ROM on his Nexus S... and yet it's tough to find one for my Evo V.
EDIT: I'm out of "thanks" I'll give you one as soon as I get some more...
Click to expand...
Click to collapse
Hmmm, I am not as familiar with the Nexus devices, but I suspect that Google has released the hardware spec details and the source code for the drivers for Nexus phones, so the source code can be modified and included for the ports. HTC unfortunately has not been as open with some of their phones.
If you were to put a phone together, you would need to use hardware in it that you had access to the specs and source code for. This is not a great analogy, but I think it will serve. The camera app tells the OS, "take a picture", then the OS tells the driver, "make the camera take a picture", and the camera device driver controls the hardware parts like the shutter, the focus, and zoom to cause the picture to be taken and handed back to the OS to be saved and then the OS notifies the app, "here is your picture, awaiting next command".
If you do not have access to the camera driver source code and camera hardware specs to create a driver, or an actual driver from the camera manufacturer, then you are missing the crucial third part and you cannot make the camera take a picture even if you get an OS loaded and an app installed there.
Check out The Tricorder Project for an excellent example. Create your own Star Trek "tricorder" with various sensors and a touchscreen that runs on Linux for around $200 and some work putting it together.
thebeastglasser said:
Ohhh... so say you decided to put your own little phone together according to your own prerequisites, it'd be simple for you to do something on it, but not so much for someone who only has the hardware to look at... correct?
Another question, why is it so easy to port things onto Nexus Devices? Are they just more compatible with all drivers? As I've heard from one of my friends that he has a fully working Sense 4 ROM on his Nexus S... and yet it's tough to find one for my Evo V.
EDIT: I'm out of "thanks" I'll give you one as soon as I get some more...
Click to expand...
Click to collapse
Its easy to develop for nexus devices since Google always releases their sources and those devices are easily unlockable (the bootloader). This is one reason why they are usually referred to as development/developer devices.
So in other words, the software communicates with the hardware, but without the proper code embedded in the hardware, it's not possible for the software to communicate with it? And without source code given from the developer of the hardware, you're making software that hypothetically should work, but because of the different device hardware it may or may not work...?
And that's also big because some guy on the portal recently found out that all of the eight mega pixel cameras on HTC devices are the same, so it should now be easy to use working cameras on ported and newly created ROMs...
Am I getting anywhere with this?
thebeastglasser said:
So in other words, the software communicates with the hardware, but without the proper code embedded in the hardware, it's not possible for the software to communicate with it? And without source code given from the developer of the hardware, you're making software that hypothetically should work, but because of the different device hardware it may or may not work...?
And that's also big because some guy on the portal recently found out that all of the eight mega pixel cameras on HTC devices are the same, so it should now be easy to use working cameras on ported and newly created ROMs...
Am I getting anywhere with this?
Click to expand...
Click to collapse
Yes, you got it a bit better now. The software needs to have the same codes embedded in the hardware to correspond with it. The source code is not from the hardware but of the software (kernel source).
Yes if the ROM was ported to other HTC devices with the same/similar camera (some libs will still need to be changed though).
Theonew said:
Yes, you got it a bit better now. The software needs to have the same codes embedded in the hardware to correspond with it. The source code is not from the hardware but of the software (kernel source).
Yes if the ROM was ported to other HTC devices with the same/similar camera (some libs will still need to be changed though).
Click to expand...
Click to collapse
Alright that makes a bit more sense. Thanks for your help guys!
I have had a Samsung Epic that has served me well for a couple years. I'm looking to upgrade, and seeing no other qwerty sliders worthy of consideration on Sprint, I am really interested in the Q.
Just the name Q makes me all nostalgic for my old MotoQ9c that is still activated and sits in my drawer for the occasional use as a backup phone. And I have to say that I am impressed with the keyboard on the new Q after trying it out a few times.
My Epic is just about worn out. I have been running CM9.0 on it since alpha, and have it running as good as is to be expected. But it's loaded down with apps, and the slider and keyboard are just about worn out. It's laggy just because it's under powered for all the stuff I'm making it do. To top it off, my otterbox commuter case has broken, and even if I could find a new one, I don't see myself investing in more accessories for this old phone.
The nice thing about the epic, though, was that the dev community was, and to some extent still is, EPIC. So let's just say that coming over here seems a little quiet. I see that there is development happening, of course, just not on the same scale. I also see that CM 10 is available, so I know my ROMing needs will probably be met. So, this alone will not stop me from a move.
Neither will lte/wimax coverage.
So, if some of you would be so kind, just give me your reasons why you think I should or should not buy a new Q. Let me know the strengths and weaknesses of the phone from the perspective of those who have had it for a while.
I greatly appreciate your input.
-AH
Sent from my SPH-D700 using xda premium
Photon Q:
Pros:
Dual core 1.5ghz Krait.
Nice keyboard.
$50 phone with contract
Cons:
Integrated SIM and battery.
No ROMs available until all kinks are worked out, I would not expect a fully functional ROM any time soon.
I'll think of more .
I would wait more and spend more on a better, more supported phone, though it might the best Keyboard phone available on sprint. iPhone is probably the best on Sprint, for those who don't like freedom, we'll see what Ubuntu OS has to offer! I can't wait for a native system, Android has been disappointing in the app/ROM stability/speed department.
Depends on personal preference. Even with very little development currently going on for the Q, in terms of performance it is leaps and bounds ahead of the Epic. On the stock Q rom no Custom Rom on the Epic is going to come close for multitasking and performance.
The stock rom rooted and with custom mods is pretty snappy. I have no regrets coming from the Epic. The battery life is great on the Q. I had the Epic for two years, and always had terrible battery life no matter what custom rom or mods I ran.
Sent from my XT897 using xda app-developers app
Pros:
Fast as ****. 2nd fastest SOC in the market .
Best keyboard I have ever used.
Brilliant screen.
Cons:
Battery life.
Not much development.
Sent from my GT-N8013 using Tapatalk HD
Thanks, guys. That's good info, and all along the lines of what I expected. I've got a couple weeks before I make the final jump, so, unless another phone comes along that just blows everything else out of the water, I'll be getting the new Q on or around March 1.
And if something better does come along, well then I guess I can upgrade that line my MotoQ9c has been on for the last 5 years. =)
Sent from my SPH-D700 using xda premium
I have had every QWERTY phone available on Sprint.
The Moto Q is the best yet. I think you will be happy with the decision.
I was hesitant about giving up the removable battery.
But, I bought a Anker 5600 Mah power bank that I keep in my car or in my front pocket with my wallet and I'm happy.
On a side note, the width of the phone is perfect. Probably the widest I would want.
Let's just hope the Moto Q is not the last, great QWERTY phone.
dpwhitty11 said:
Cons:
Not much development.
Click to expand...
Click to collapse
That's going to change
Porting CM10 on the Photon Q and another guy with MS1 - the CM maintainer for MS - kabaldan - is getting the Q too. Although CDMA support might be a problem since he's from Prague too.
So far I got basic things working (display, sound, camera, adb, modem, wifi (partially - doesn't seem to detect networks properly)). Main thing though - QWERTY keyboard - still needs properly patched framework (that's right, stock ICS+ Android lacks support for physical QWERTY keyboard on the phone) ...
Skrilax_CZ said:
That's going to change
Porting CM10 on the Photon Q and another guy with MS1 - the CM maintainer for MS - kabaldan - is getting the Q too. Although CDMA support might be a problem since he's from Prague too.
So far I got basic things working (display, sound, camera, adb, modem, wifi (partially - doesn't seem to detect networks properly)). Main thing though - QWERTY keyboard - still needs properly patched framework (that's right, stock ICS+ Android lacks support for physical QWERTY keyboard on the phone) ...
Click to expand...
Click to collapse
I'm glad to hear things are about to pick up!
Now I'll be less tempted to jump onto a Nexus 4 once it eventually comes to Sprint.
Sent from my GT-N8013 using Tapatalk HD
Skrilax_CZ said:
That's going to change
Porting CM10 on the Photon Q and another guy with MS1 - the CM maintainer for MS - kabaldan - is getting the Q too. Although CDMA support might be a problem since he's from Prague too.
So far I got basic things working (display, sound, camera, adb, modem, wifi (partially - doesn't seem to detect networks properly)). Main thing though - QWERTY keyboard - still needs properly patched framework (that's right, stock ICS+ Android lacks support for physical QWERTY keyboard on the phone) ...
Click to expand...
Click to collapse
lol, why haven't you said anything......
I feel like I'm reinventing the wheel over here! You guys meet on IRC somewhere, or do I need to speak Czech?
Skrilax_CZ said:
That's going to change
Porting CM10 on the Photon Q and another guy with MS1 - the CM maintainer for MS - kabaldan - is getting the Q too. Although CDMA support might be a problem since he's from Prague too.
So far I got basic things working (display, sound, camera, adb, modem, wifi (partially - doesn't seem to detect networks properly)). Main thing though - QWERTY keyboard - still needs properly patched framework (that's right, stock ICS+ Android lacks support for physical QWERTY keyboard on the phone) ...
Click to expand...
Click to collapse
Is there anything public we can see? Like a git somewhere?
Repos are on github in current state: https://github.com/SkrilaxCZ?tab=repositories (use android_kernel_moto_asanti_c for kernel). Or see here how to clone the entire tree: https://github.com/SkrilaxCZ/android (jellybean branch). Vendor repo is included too, no need to extract anything from phone. Also I'm on ASA14 firmware. I'm porting CM10 as there are problems with camera on CM10.1 on the similar phones such as RAZR HD as of now. And I started this weekend, that's 4 days
Framework is forked, but I haven't patched it yet. So as I said QWERTY keyboard isn't working properly (backlight, onscreen keyboard shows up etc.).
You can find me and kabaldan (as nadlabak) on freenode #motomagic, there are also other guys from US in there to help (well, mind the timezones, CZ is GMT+1).
Skrilax_CZ said:
Repos are on github in current state: https://github.com/SkrilaxCZ?tab=repositories (use android_kernel_moto_asanti_c for kernel). Or see here how to clone the entire tree: https://github.com/SkrilaxCZ/android (jellybean branch). Vendor repo is included too, no need to extract anything from phone. Also I'm on ASA14 firmware. I'm porting CM10 as there are problems with camera on CM10.1 on the similar phones such as RAZR HD as of now. And I started this weekend, that's 4 days
Framework is forked, but I haven't patched it yet. So as I said QWERTY keyboard isn't working properly (backlight, onscreen keyboard shows up etc.).
You can find me and kabaldan (as nadlabak) on freenode #motomagic, there are also other guys from US in there to help (well, mind the timezones, CZ is GMT+1).
Click to expand...
Click to collapse
Friggin sweet!
So when are you going to post CM10? When you get the kb stuff worked out?
I'm building now, hoping to get some success. Hoping you post it to the public soon!
I will post when the "child illnesses" are solved.
I just upgraded from the Evo Shift and I'm glad I did. The Shift was a great phone but like you, it couldn't keep up with me anymore. I rooted, flashed pwnyourface's customish stock ROM and debloated and the phone's running great. With the fast processor, multi-tasking is much easier and even Sprint's abysmal 3G speeds seem better because the apps can us it more efficiently.
Battery life's not bad but with being faster and with a bigger screen' I was expecting a dip from the usual 18hrs I would get out of my Shift. The good thing is that if you buy the Q from Costco Wireless, it's only $40 (edit - with upgrade) plus you get the following:
-belt holster (won't use but I'll take it)
-a slip over case (can't use it in the case but it's good until I get my Otterbox which I found for $21 on Amazon)
-a car charger/wall charger combo with extra cable (cheapish but whatever, it's free)
- mail-in-rebate for a battery pack and nav dock (will take 4-8 weeks to process BUT FREE! WOOOOO!)
Overall, more than happy I upgraded though I'm having to retrain my fingers to work with this keyboard.
Skrilax_CZ said:
Repos are on github in current state: https://github.com/SkrilaxCZ?tab=repositories (use android_kernel_moto_asanti_c for kernel). Or see here how to clone the entire tree: https://github.com/SkrilaxCZ/android (jellybean branch). Vendor repo is included too, no need to extract anything from phone. Also I'm on ASA14 firmware. I'm porting CM10 as there are problems with camera on CM10.1 on the similar phones such as RAZR HD as of now. And I started this weekend, that's 4 days
Framework is forked, but I haven't patched it yet. So as I said QWERTY keyboard isn't working properly (backlight, onscreen keyboard shows up etc.).
You can find me and kabaldan (as nadlabak) on freenode #motomagic, there are also other guys from US in there to help (well, mind the timezones, CZ is GMT+1).
Click to expand...
Click to collapse
Wow! That's all so great to hear. I'm sure if the JB upgrade from moto and sprint ever actually arrives and we get source code on it it will help to figure out a lot of those issues as well. I'm definitely not letting development or lack thereof affect my decision. I know development will happen, it's just a matter of time. My feeling is that some of the newer phones haven't been developed as much as older ones like the Epic because they work so well out of the box with faster processors and more ram. You can't imagine how shocked I was when my Epic froze up less than an hour of leaving the sprint store with it. Everyone knew the hardware could do better, so the tinkerers had to fix it...and boy did they. But if a phone works well out of the box, then there isn't the perceived need for it. Still, I've gotten used to having my phone rooted, checking CM nightlies, and doing my own tweaks. So the fact that this is out there is icing on the cake.
Sent from my SPH-D700 using xda premium
brandontowey said:
I just upgraded from the Evo Shift and I'm glad I did. The Shift was a great phone but like you, it couldn't keep up with me anymore. I rooted, flashed pwnyourface's customish stock ROM and debloated and the phone's running great. With the fast processor, multi-tasking is much easier and even Sprint's abysmal 3G speeds seem better because the apps can us it more efficiently.
Battery life's not bad but with being faster and with a bigger screen' I was expecting a dip from the usual 18hrs I would get out of my Shift. The good thing is that if you buy the Q from Costco Wireless, it's only $40 (edit - with upgrade) plus you get the following:
-belt holster (won't use but I'll take it)
-a slip over case (can't use it in the case but it's good until I get my Otterbox which I found for $21 on Amazon)
-a car charger/wall charger combo with extra cable (cheapish but whatever, it's free)
- mail-in-rebate for a battery pack and nav dock (will take 4-8 weeks to process BUT FREE! WOOOOO!)
Overall, more than happy I upgraded though I'm having to retrain my fingers to work with this keyboard.
Click to expand...
Click to collapse
Yeah, I saw the deal from costco, and am probably going that way. We don't have a membership, and it's about 20 miles to the nearest store, and we pass two Sam's clubs on the way, but my wife is interested in getting a membership and checking it out for a year, so that's the plan.
And I know what you mean about changing the keyboard. I picked the Epic because I felt it had the best keyboard available at the time, and that was largely due to the 5th row of keys. My first couple tries with the Q were like going into bazaaro land, but the feel of it is just so much more positive. I agree with the guys over at A|C: the best keyboard on an android phone, period.
Sent from my SPH-D700 using xda premium
Wow, this generated more response than I expected. Thanks so much to all of you for all the info.
Sent from my SPH-D700 using xda premium
I thought you needed a membership but when I ordered two phones from the website, membershipwireless.com, it never asked for a Costco customer number, just my Sprint info. I think it's a separate entity that's partnered with Costco or something but you don't need to join to buy stuff from the wireless division.
Hey guys.
Just ordered up my phone from Costco. Can't wait until it comes in.
Sent from my SPH-D700 using xda premium
amateurhack said:
Hey guys.
Just ordered up my phone from Costco. Can't wait until it comes in.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Great choice!! You gotta love it. For custom ROM,I think it will come considering this phone has an unlocked bootloader.