Related
Hello,
I would like to change the HTC Hero's firmware/ROM to match that of the HTC Magic's firmware/ROM. My phone is CDMA, but I'm hoping that somehow, someway it is possible to do this. My reason for wanting this is so that I can finally do mods, like Cyanogen, since the CDMA Hero isn't really that widely supported, yet.
Thanks in advance for any help,
Tyler
Any new ROM will have to be CDMA, you can't change that since it has to do with phone hardware.
I have been.trying to port over gsm roms forever and.with no luck. Theoretically its possible but I haven't the faintest idea how.
Well, then I guess I have to resort to my last and great question. Since I'm stuck with my Hero, unless I go T-Mobile, how long, do you guys suspect, that it will take for more support to role out, like there is for the Magic? I ask because I'm wanting to know rather, or not there is a lot of development happening for the Hero because I really want great functionality and mod availability. At this point, if the answer is "not a lot", I may just drop the Hero for the Magic.
Thanks again for answering my questions,
Tyler
thejedislayer said:
Well, then I guess I have to resort to my last and great question. Since I'm stuck with my Hero, unless I go T-Mobile, how long, do you guys suspect, that it will take for more support to role out, like there is for the Magic? I ask because I'm wanting to know rather, or not there is a lot of development happening for the Hero because I really want great functionality and mod availability. At this point, if the answer is "not a lot", I may just drop the Hero for the Magic.
Thanks again for answering my questions,
Tyler
Click to expand...
Click to collapse
So you're saying you're "STUCK" with a month and a half old phone, unless "more people start supporting it"? i.e. People spending their free time creating mods for the Hero, so that you can get it for free? And if people aren't going to do mods and features for free in the near future, then you're just going to get rid of your Hero and go to T-Mobile for the Magic because it has people who are dedicated to releasing software they dont get paid to spend time working on? Seems like a lot of complaining about something that is completely voluntary, nobody has to work on any mods and nobody has to support any device. If you want to drop your Hero, just do it already. Nobody wants you to keep using it, nobody is forcing you to keep using it. Just do it already, nobody cares to read threads like this.
Wow, you took what I said and totally blew it out of proportion. The reason I wanted to get Android was because I wanted to be able to do things, like root my Android device. I fully support developers in their endeavor to develop applications, mods, ROMS, etc for all Android devices on their time. I do not, however, sit here and feel that the best idea to do is to whine and cry about support for my Android device not yet being fully supported or embraced. I simply asked rather, or not heavy development was going to happen in the near future, so as to ascertain a good decision on rather I should switch. That way I could get the full and best support and benefit from my personal experience with Android. I am not a developer. I've only gotten into this, so I was simply curious as to how development was coming along for the Hero at this time, and rather it may have been a better idea to just switch. Sorry To Have Offended The Offended.
**EDIT**
And understandably, having reread what I wrote, I can understand how what I said may have come off as a little dickish; however, it was not my intention, nor was it my wanting to cause a conflict.
thejedislayer said:
Wow, you took what I said and totally blew it out of proportion. The reason I wanted to get Android was because I wanted to be able to do things, like root my Android device. I fully support developers in their endeavor to develop applications, mods, ROMS, etc for all Android devices on their time. I do not, however, sit here and feel that the best idea to do is to whine and cry about support for my Android device not yet being fully supported or embraced. I simply asked rather, or not heavy development was going to happen in the near future, so as to ascertain a good decision on rather I should switch. That way I could get the full and best support and benefit from my personal experience with Android. I am not a developer. I've only gotten into this, so I was simply curious as to how development was coming along for the Hero at this time, and rather it may have been a better idea to just switch. Sorry To Have Offended The Offended.
Click to expand...
Click to collapse
There are many threads with people making their own roms, and modifications are being made to the hero by various people. Heavy development like going to 1.6 or 2.0 will most likely not happen by any developer, but by HTC itself. Once they release a new version, people will make a new rooted ROM with all the changes. For a fairly new phone, it got rooted fairly quickly (within a month of being released or so). It hasn't even been rooted all that long yet. All of this information is available in various threads. In the end its your decision on if you can wait or not to receive updates. Bleeding edge isn't always the best choice for everybody. If you prefer bleeding edge, perhaps you did get the wrong phone because there will likely be much more activity with, say, the Droid. But as for apps, there should be tons and tons of more apps coming available for the android platform as time goes on. I just cant see why you would want to switch phones based on a really short time period of it being out, jumping ship because it hasn't been hailed and given 100% attention by tons of developers yet. Honestly, as more android phones are released, I think more people will start developing for them and the android community itself will continue to grow. There are still some 7 year old Casio devices that receive updates, if you can believe that.
In all honesty, I knew I was a little quick to jump the gun when I said rather, or not it was a good decision to move from the Hero to the Magic. Again, this is all really new to me. In my mind, my main concern was that because of the Hero's Sense UI, this would make it a lot harder for developers, like Cyanogen Mod, to keep the Hero up-to-date with the rest of the older Android devices. The Magic, seeing it being a lot more supported in just three short months since its debut, made more sense to me to possibly move to. As it had tons of development happening for it, and I simply wanted to be apart of the action.
wouldn't a 1.6 Rom work since it "supports CDMA" out of the box???
@ azfxstb
I took the liberty of looking around, and I ended up finding some links from HTC for 1.6 support. Link: http://developer.htc.com/google-io-device.html
According to the article, though, the next successive version relies on a previous version in order to update properly. In other words, in order to know I have full functionality and support, I would have to start from the beginning of the Magic's support and simply continue updating till I reach the newest update. I may be wrong, but if I'm not, then it may be something worthwhile considering, even if it's a hassle. Anyone have any thoughts about this method?
I'd say stick it out. The Sprint Hero hasn't even been out for 2 months and it is rooted and there are a couple of custom ROM's posted here. I've had my Hero for 2 weeks and have already tried numerous releases, and all have been very stable for me.
I'd love to see some of the improvements Cyanogen come over, and I'm sure they will eventually, but you have to remember how long of a time frame the Magic had to work with.
azfxstb said:
wouldn't a 1.6 Rom work since it "supports CDMA" out of the box???
Click to expand...
Click to collapse
We don't know that HTC's shoehorned CDMA support into 1.5 is compatible with the built-in CDMA support in 1.6. What that means is that there's a potential that even if we did get a 1.6 build on the phone, HTC's proprietary (i.e., not required to release source code for) software that sits between the Android framework and the linux kernel (which in turn talks to the hardware) might be speaking a different language that Android 1.6 can't understand. That's the problem with their hacked-together 1.5 build. Make note that I do not know this for certain, but it's certainly a possibility, and if that's the case, we'd have a broken phone until those HTC layers could be translated from hacked-1.5 to native-1.6.
That's why, as already stated above, those moves probably won't happen until HTC releases a 2.0 build (which means we might never see 1.6 run on this phone even after the 2.0 release, since we'll never have the HTC software that is written specifically for the 1.6 platform).
To break it down, the phone has 2 processors: ARM9 and ARM11. ARM9 runs the radio hardware, and the radio controls literally *everything* that makes this phone usable. Think of ARM9 like your computer's BIOS chip. Except in a very rare case of someone who really really wants to hack on their phone, the ARM9 will never be modified by us.
The ARM11 is the next layer, and that's what actually runs the OS, recovery images, etc. The ARM11 is able to communicate with the ARM9 using a series of two-way communication channels (shared memory) and hardware interrupts.
The linux kernel contains drivers that on one side talk to the ARM11 and other hardware in the phone, and then expose controls on the other side that allow the rest of the OS to work with those things (e.g., turn the screen on/off, register touches on the screen, play sounds, vibrate, make calls, etc).
For some things, that's enough to let Android take over and actually make use of some of those things (LCD, touchscreen, sound, ...). Still, there are other things that require intermediate controllers between the devices exposed by the kernel and Android. For example, "rild" is in charge of managing the modem as far as things like issuing commands to your carrier, getting online, telling the modem to make a call, finding out signal strength, etc. But HTC wrote their own ril that interacts with the modem -- and they aren't required (in fact, they're not allowed!) to release the source code for that, because a) it was developed using proprietary information given to them (under NDA no doubt) by Qualcomm, and/or b) it contains information that HTC themselves want to keep private, protecting their intellectual property, etc. There are several other userland libraries like that, which are NOT part of the kernel, and therefore are not required to be released as open source. Yet they are required for Android to work, as android will speak directly to those libraries, which translate the messages in order to communicate with the kernel, which communicates with the ARM11, which talks to the ARM9, which makes it happen.
The breakdown happens at the "android speaks to the libraries" step, because Android 1.5 speaks a certain language, and that's (potentially) different from the Android 1.6 language. Yes this phone is CDMA, and yes Android 1.6 has native support for CDMA... So, you say, putting Android 1.6 on the phone should "just work". But the HTC libraries that are on our phones are not designed for 1.6, they're designed for 1.5. And they're not even designed for the "standard" GSM 1.5, but for a "hacked" CDMA 1.5! If we put Android 1.6 on the phones, we could *try* to reuse the existing binary form of the HTC libraries, but if 1.5 and 1.6 talk different languages (most likely they do), the 1.5 version of the binary libraries are going to get confused and reject it. Then we're left with a 1.6 platform that can't talk to the 1.5 libraries, and we get major functionality meltdown. To be fair, it would be possible to write an additional translation layer that would convert the 1.6 messages into something that we "think" the 1.5 libraries will understand, but is it really worth the effort? (hint: it's not a small effort ) Then try doing the same with 2.0, and the potential for translation problems are even worse...
And not to mention, 2.0 also requires the 2.6.29 kernel, which (surprise, surprise), does not exist (for this phone) in the wild. We could theoretically get 1.6 running, since we already have a working 2.6.27 kernel (the phone shipped with it, and if we assume that the shipped kernel is "good enough", we can simply reuse it -- we already do that with the recovery image and even MoDaCo's rom). But as soon as we think about either modifying the kernel as it is, or god forbid, upgrading to 2.6.29, we hit a roadblock because we don't have the source code yet for the 2.6.27 kernel. Once that code is released, we could hypothetically port that support to 2.6.29. Or once HTC releases an Eclair build for this phone, it'll be guaranteed to have a ready-made 2.6.29 kernel buried inside, as well as the binary HTC libraries that are required for our phone. Until one of those two things happens (or, admittedly, someone reverse-engineers what's required... which quite frankly is not worth anyone's time considering we know that HTC *will* release both of those things eventually), Eclair is absolutely out of the question.
The short version (go ahead, admit it, you skipped to here even though I didn't put a "short version at the end" disclaimer at the top): 1.6 will absolutely require reverse-engineering the HTC libraries, just to get an already outdated (albeit still an upgrade) version of the OS on the phone -- not worth the effort. 2.0 will absolutely require reverse-engineering (both the kernel AND the binary libraries), just to get Eclair running on the phone maybe a couple weeks before HTC gives it to us on a silver platter -- And you're still likely to have a partially gimped phone at that point!
And the moral is: this **** is hard. HTC is already doing the work we need. HTC will make everything work "reasonably well". And they'll give it to us when they're done. Thus, no one *wants* to waste the effort doing it themselves. Ergo: we wait.
maejrep said:
We don't know that HTC's shoehorned CDMA support into 1.5 is compatible with the built-in CDMA support in 1.6. What that means is that there's a potential that even if we did get a 1.6 build on the phone, HTC's proprietary (i.e., not required to release source code for) software that sits between the Android framework and the linux kernel (which in turn talks to the hardware) might be speaking a different language that Android 1.6 can't understand. That's the problem with their hacked-together 1.5 build. Make note that I do not know this for certain, but it's certainly a possibility, and if that's the case, we'd have a broken phone until those HTC layers could be translated from hacked-1.5 to native-1.6.
That's why, as already stated above, those moves probably won't happen until HTC releases a 2.0 build (which means we might never see 1.6 run on this phone even after the 2.0 release, since we'll never have the HTC software that is written specifically for the 1.6 platform).
To break it down, the phone has 2 processors: ARM9 and ARM11. ARM9 runs the radio hardware, and the radio controls literally *everything* that makes this phone usable. Think of ARM9 like your computer's BIOS chip. Except in a very rare case of someone who really really wants to hack on their phone, the ARM9 will never be modified by us.
The ARM11 is the next layer, and that's what actually runs the OS, recovery images, etc. The ARM11 is able to communicate with the ARM9 using a series of two-way communication channels (shared memory) and hardware interrupts.
The linux kernel contains drivers that on one side talk to the ARM11 and other hardware in the phone, and then expose controls on the other side that allow the rest of the OS to work with those things (e.g., turn the screen on/off, register touches on the screen, play sounds, vibrate, make calls, etc).
For some things, that's enough to let Android take over and actually make use of some of those things (LCD, touchscreen, sound, ...). Still, there are other things that require intermediate controllers between the devices exposed by the kernel and Android. For example, "rild" is in charge of managing the modem as far as things like issuing commands to your carrier, getting online, telling the modem to make a call, finding out signal strength, etc. But HTC wrote their own ril that interacts with the modem -- and they aren't required (in fact, they're not allowed!) to release the source code for that, because a) it was developed using proprietary information given to them (under NDA no doubt) by Qualcomm, and/or b) it contains information that HTC themselves want to keep private, protecting their intellectual property, etc. There are several other userland libraries like that, which are NOT part of the kernel, and therefore are not required to be released as open source. Yet they are required for Android to work, as android will speak directly to those libraries, which translate the messages in order to communicate with the kernel, which communicates with the ARM11, which talks to the ARM9, which makes it happen.
The breakdown happens at the "android speaks to the libraries" step, because Android 1.5 speaks a certain language, and that's (potentially) different from the Android 1.6 language. Yes this phone is CDMA, and yes Android 1.6 has native support for CDMA... So, you say, putting Android 1.6 on the phone should "just work". But the HTC libraries that are on our phones are not designed for 1.6, they're designed for 1.5. And they're not even designed for the "standard" GSM 1.5, but for a "hacked" CDMA 1.5! If we put Android 1.6 on the phones, we could *try* to reuse the existing binary form of the HTC libraries, but if 1.5 and 1.6 talk different languages (most likely they do), the 1.5 version of the binary libraries are going to get confused and reject it. Then we're left with a 1.6 platform that can't talk to the 1.5 libraries, and we get major functionality meltdown. To be fair, it would be possible to write an additional translation layer that would convert the 1.6 messages into something that we "think" the 1.5 libraries will understand, but is it really worth the effort? (hint: it's not a small effort ) Then try doing the same with 2.0, and the potential for translation problems are even worse...
And not to mention, 2.0 also requires the 2.6.29 kernel, which (surprise, surprise), does not exist (for this phone) in the wild. We could theoretically get 1.6 running, since we already have a working 2.6.27 kernel (the phone shipped with it, and if we assume that the shipped kernel is "good enough", we can simply reuse it -- we already do that with the recovery image and even MoDaCo's rom). But as soon as we think about either modifying the kernel as it is, or god forbid, upgrading to 2.6.29, we hit a roadblock because we don't have the source code yet for the 2.6.27 kernel. Once that code is released, we could hypothetically port that support to 2.6.29. Or once HTC releases an Eclair build for this phone, it'll be guaranteed to have a ready-made 2.6.29 kernel buried inside, as well as the binary HTC libraries that are required for our phone. Until one of those two things happens (or, admittedly, someone reverse-engineers what's required... which quite frankly is not worth anyone's time considering we know that HTC *will* release both of those things eventually), Eclair is absolutely out of the question.
The short version (go ahead, admit it, you skipped to here even though I didn't put a "short version at the end" disclaimer at the top): 1.6 will absolutely require reverse-engineering the HTC libraries, just to get an already outdated (albeit still an upgrade) version of the OS on the phone -- not worth the effort. 2.0 will absolutely require reverse-engineering (both the kernel AND the binary libraries), just to get Eclair running on the phone maybe a couple weeks before HTC gives it to us on a silver platter -- And you're still likely to have a partially gimped phone at that point!
And the moral is: this **** is hard. HTC is already doing the work we need. HTC will make everything work "reasonably well". And they'll give it to us when they're done. Thus, no one *wants* to waste the effort doing it themselves. Ergo: we wait.
Click to expand...
Click to collapse
WOW...did you stay at a Holiday Inn Express last night????....J/K thanks for the in depth explanation
READ YOUR HOMEWORK PEOPLE http://www.mobilecrunch.com/2010/06...kers-with-legal-action-for-distributing-roms/
I guess I know what i'll be downloading all day till I got work
That's for Windows Mobile.
hTC can't stop anyone distributing AOSP ROMs, but they could throw the hammer down on distributing their Sense ROMS.
Because of all that nonsense (no pun intended ), I've commited myself to getting this. I'll be more than satisfied.
wcdisciple said:
Because of all that nonsense (no pun intended ), I've commited myself to getting this. I'll be more than satisfied.
Click to expand...
Click to collapse
Man, i think you're not getting tired of emphasise how good apple is. Please don't take it offensive, but why are you in this forum if you will buy / have bought an iPhone?
HTC is only one company of many building phones with Android. Whether you like Sense or not is your decision. G1 and MT3G (with google) were never intended to run with Sense. And no one can sue us for using AOSP ROM's. So i have no problem with it compared to apple, who will preselect the software for you...
Jailbreaking the iPhone isn't legal by the way...
PS: don't want to start an Apple/Android war, but leaving one company suing others for another company suing people since years and taking it for the reason why, seems a bit curious to me...
hudl said:
Man, i think you're not getting tired of emphasise how good apple is. Please don't take it offensive, but why are you in this forum if you will buy / have bought an iPhone?
Click to expand...
Click to collapse
He's been on a rampage with it.
On a better note: I don't think this will stop ROM development. Didn't xda go through the same thing, but HTC didn't care about the actual developed ROMs?
Edit: Can't find anything to support that. :/ Remember reading it somewhere - might have been bs, but I swear it was on xda news.
HTC threatens handset hackers with legal action - WORST MISTAKE EVER
HTC is seriously making a mistake with that one.
Ive only been satisfied with my purchase of anything they have come with AFTER flashing a Rom into it.
If this continues I promise you they will regret it.
They will lose customers that WILL choose to go to other manufacturers.
The Devs and all who create on a constant basis are not hackers.
They innovate to make HTC a better phone than the competitors because of the work that are done by these fine people.
legend221 said:
HTC is seriously making a mistake with that one.
Ive only been satisfied with my purchase of anything they have come with AFTER flashing a Rom into it.
If this continues I promise you they will regret it.
They will lose customers that WILL choose to go to other manufacturers.
The Devs and all who create on a constant basis are not hackers.
They innovate to make HTC a better phone than the competitors because of the work that are done by these fine people.
Click to expand...
Click to collapse
But they didn't take it down because of them being custom ROMs. They were all just the basic stock ROMs that came with the phone. Honestly, there's not much of a difference as both custom and stock contain IP. However, I think they would've taken down xda a long time ago if they were worried about custom ROMs.
r3s-rt said:
Honestly, there's not much of a difference as both custom and stock contain IP.
Click to expand...
Click to collapse
There is a HUGE difference between stock and Custom Rom, anyone that has ever flashed a Rom will tell you this.
r3s-rt said:
However, I think they would've taken down xda a long time ago if they were worried about custom ROMs
Click to expand...
Click to collapse
A similar C&D almost stopped the progression of a certain legendary Dev on the android scene.
Luckily, there was a workaround and everyone was happy flashing and seeing for themselves how much better our phones have been on a customized, fast and stable Rom.
legend221 said:
There is a HUGE difference between stock and Custom Rom, anyone that has ever flashed a Rom will tell you this.
Click to expand...
Click to collapse
Are you serious? So you're telling me all HTC widgets involved in a sense ROM aren't IP? Or Google Apps included in most ROMs aren't IP? Google Maps? Market? Anything? That's actually pretty funny. No THERE IS NO DIFFERENCE between a stock ROM and a custom ROM on the IP subject with the exception of JUST a few. Like.... 2 or 3? Do you even know what intellectual property is?
A similar C&D almost stopped the progression of a certain legendary Dev on the android scene.
Luckily, there was a workaround and everyone was happy flashing and seeing for themselves how much better our phones have been on a customized, fast and stable Rom.
Click to expand...
Click to collapse
And no, the similar C&D did NOT almost stop ROM development. If that was the case, NO ROM would come with Google Apps included. However, they DO, and are they are NOT getting C&Ds. If you think Google isn't looking at XDA to see what's happening, you need to start thinking a bit more.
Edit: Also, not every ROM is based off of cyanogen. While there are A LOT that are, not ALL are.
r3s-rt said:
Are you serious? So you're telling me all HTC widgets involved in a sense ROM aren't IP? Or Google Apps included in most ROMs aren't IP? Google Maps? Market? Anything? That's actually pretty funny. No THERE IS NO DIFFERENCE between a stock ROM and a custom ROM on the IP subject with the exception of JUST a few. Like.... 2 or 3? Do you even know what intellectual property is?
Click to expand...
Click to collapse
Not everyone even cares about widgets. I only use the calendar one for example. Widgets are not the issue, we are talking about Roms overall because if HTC starts implementing a stricter enforcement of people not having the ability to use or host the Rom of their choice and preventing Devs to freely distribute their work then we are all held mercy to whatever HTC has pre-installed from the factory. A major FAIL for them.
r3s-rt said:
And no, the similar C&D did NOT almost stop ROM development. If that was the case, NO ROM would come with Google Apps included. However, they DO, and are they are NOT getting C&Ds. If you think Google isn't looking at XDA to see what's happening, you need to start thinking a bit more.
Edit: Also, not every ROM is based off of cyanogen. While there are A LOT that are, not ALL are.
Click to expand...
Click to collapse
Google knows its in their best interest to keep letting everyone that wants to flash a custom Rom. Some people buy specific phones (the past phones of mine as well) only if they are rooted or can install a custom SPL and flash their flavor of a Rom. The Cyanogen reference was an example not for every case, we are aware of the Windows Mobile, etc sections of xda.
legend221 said:
Not everyone even cares about widgets. I only use the calendar one for example. Widgets are not the issue, we are talking about Roms overall because if HTC starts implementing a stricter enforcement of people not having the ability to use or host the Rom of their choice and preventing Devs to freely distribute their work then we are all held mercy to whatever HTC has pre-installed from the factory. A major FAIL for them.
Click to expand...
Click to collapse
You're not continuing what you originally said. You said there's a huge difference between a custom ROM and a stock ROM. Now, this statement should have been based on IP terms, as this is clearly what the topic is supposed to be about. My point is that IP is still included in any ROM. It doesn't matter what you use - that is completely irrelevant to the subject matter. They clearly are not enforcing all little bits of IP. If that was the case, as I've said multiple times, xda wouldn't be here right now. HTC is WELL AWARE along with Microsoft and Google of what goes on here. I promise you they pay once lucky bastard to sit here and probe this site, along with others, all day everyday and flag anything they see unfit. The main thing they seem to not like is ROM libraries. That's just from my experience.
To sum this up" We are NOT at mercy of what is pre-installed from factory or they would have sent out much more C&D letters much sooner than this. XDA has over 2 MILLION users. That's all I'm saying.
Google knows its in their best interest to keep letting everyone that wants to flash a custom Rom. Some people buy specific phones (the past phones of mine as well) only if they are rooted or can install a custom SPL and flash their flavor of a Rom. The Cyanogen reference was an example not for every case, we are aware of the Windows Mobile, etc sections of xda.
Click to expand...
Click to collapse
Best interest? Are you serious, bro? Android is marketed as an open-source platform. That's not in their "best interest." It's in their intents! The unrootable is because of cell phone carriers! Guess what?! The Dream came out as a Development phone! The Google ION (more commonly the myTouch 3g)? Development phone! The cyanogenmod reference was taken for what it was - an C&D from GOOGLE! NOT HTC!
r3s-rt said:
You're not continuing what you originally said. You said there's a huge difference between a custom ROM and a stock ROM. Now, this statement should have been based on IP terms, as this is clearly what the topic is supposed to be about. My point is that IP is still included in any ROM. It doesn't matter what you use - that is completely irrelevant to the subject matter. They clearly are not enforcing all little bits of IP. If that was the case, as I've said multiple times, xda wouldn't be here right now. HTC is WELL AWARE along with Microsoft and Google of what goes on here. I promise you they pay once lucky bastard to sit here and probe this site, along with others, all day everyday and flag anything they see unfit. The main thing they seem to not like is ROM libraries. That's just from my experience.
To sum this up" We are NOT at mercy of what is pre-installed from factory or they would have sent out much more C&D letters much sooner than this. XDA has over 2 MILLION users. That's all I'm saying.
Best interest? Are you serious, bro? Android is marketed as an open-source platform. That's not in their "best interest." It's in their intents! The unrootable is because of cell phone carriers! Guess what?! The Dream came out as a Development phone! The Google ION (more commonly the myTouch 3g)? Development phone! The cyanogenmod reference was taken for what it was - an C&D from GOOGLE! NOT HTC!
Click to expand...
Click to collapse
Thanks for giving that one guy the heads up on what goes on and what doesnt go on around here if he indeed does exist. If theres anything we dont need is anyone giving them more fuel to thier fire.
No one said the C&D came from HTC, seeing as you are a reader on xda I knew I didnt have to explain this to you. hahaha. It is in Google's best interest to let the Devs continue thier greatness because guess what many would jump ship to Windows Mobile devices or other OS including the iPhone even though there are not Roms for it I believe. If Android Development was not allowed to continue, at least most people would stop buying Android powered phones I believe.
Yawn........ time for bed now.
Why are you all under the assumption that the majority of HTC sales all run off of custom firmware? Do you really believe that sales are going to be effected that much because of HTC's decision?
legend221 said:
No one said the C&D came from HTC
Click to expand...
Click to collapse
Did you even read the article? If you are referring to the one cyanogen got, I never said it did. Seeing as you are just a reader (not) I didn't have to explain this to you. But I did. Please, if you're going to try and get a point across, respect me enough to actually read what I said.
legend221 said:
Thanks for giving that one guy the heads up on what goes on and what doesnt go on around here if he indeed does exist. If theres anything we dont need is anyone giving them more fuel to thier fire.
Click to expand...
Click to collapse
I had to edit this is. Really? Have you been snorting cocaine or something? That's pretty damn paranoid. If you don't think that happens, you just need to get off the internet as that's just basic knowledge. If you were HTC, would you not watch us? If you wouldn't - stay out of sales forever.
Binary100100 said:
Why are you all under the assumption that the majority of HTC sales all run off of custom firmware? Do you really believe that sales are going to be effected that much because of HTC's decision?
Click to expand...
Click to collapse
I'm not under that assumption; I take you include me in the all. I just stated that at least this won't affect custom ROMs and he went on about how custom ROMs are so different and don't contain IP. That's what I've been trying to get across in all my posts. And no, I don't think their sales will be affected .
r3s-rt said:
Did you even read the article? If you are referring to the one cyanogen got, I never said it did. Seeing as you are just a reader (not) I didn't have to explain this to you. But I did. Please, if you're going to try and get a point across, respect me enough to actually read what I said.
I had to edit this is. Really? Have you been snorting cocaine or something? That's pretty damn paranoid. If you don't think that happens, you just need to get off the internet as that's just basic knowledge. If you were HTC, would you not watch us? If you wouldn't - stay out of sales forever.
Click to expand...
Click to collapse
You're still on what I said?
Get over it and realize not everyone is going to agree with you or your thoughts.
The one on drugs is YOU, damn get out of the forums and do something else with your time man. hahaha
That's why its a forum and NOT your personal website.
legend221 said:
You're still on what I said?
Get over it and realize not everyone is going to agree with you or your thoughts.
The one on drugs is YOU, damn get out of the forums and do something else with your time man. hahaha
That's why its a forum and NOT your personal website.
Click to expand...
Click to collapse
Any one with intelligence will tell you that 90% of custom ROMs contain IP. The fact that you are swearing up and down that they don't is just.... stupid.
r3s-rt said:
Any one with intelligence will tell you that 90% of custom ROMs contain IP. The fact that you are swearing up and down that they don't is just.... stupid.
Click to expand...
Click to collapse
The fact of the matter is that without proprietary IP, you can't even start the thing up. There is more IP than just widgets, launchers, and apps... there are DRIVERS and other such buried nonsense.
SOME of this IP *IS* distributed, have a look at developer.htc.com -- HTC eventually relented and opened their kernel modifications since they were committing a GPL violation, but there is other stuff on that page that is being distributed that IS proprietary IP, specifically, the "HTC Proprietary Binaries for ADP1". And those binaries don't even include all the proprietary binaries needed to make full use of the phone, such as the GPU drivers and the video decoder drivers.
THANKFULLY, the phone's owner IS licensed to use all of those binaries, so they can just keep them. Note that they're also included in the FULL SYSTEM IMAGES that HTC ITSELF distributed from developer.htc.com.
*** and that is a HUGE DIFFERENCE between the android platform and wimo.... the fact that HTC distributes ***all*** of the proprietary binaries straight from their website. It means that it ***IS*** possible to generate fully AOSP (but non-functional) system images, and the USER can combine them with the binaries provided by HTC to make a working system.
From what I've seen, HTC REALLY DOESN'T CARE and/or actually WANTS users to build custom roms for their phones. They send out the cease and desist order for distribution of wimo roms, PROBABLY in accordance with MS's demands. MS probably said to them -- "listen, you either try to put a lid on piracy or we're going to stop sending you MSTRASH." HTC distributes GOOGLE apps in the roms on their website because THAT'S WHAT GOOGLE WANTS.
lbcoder said:
The fact of the matter is that without proprietary IP, you can't even start the thing up. There is more IP than just widgets, launchers, and apps... there are DRIVERS and other such buried nonsense.
SOME of this IP *IS* distributed, have a look at developer.htc.com -- HTC eventually relented and opened their kernel modifications since they were committing a GPL violation, but there is other stuff on that page that is being distributed that IS proprietary IP, specifically, the "HTC Proprietary Binaries for ADP1". And those binaries don't even include all the proprietary binaries needed to make full use of the phone, such as the GPU drivers and the video decoder drivers.
THANKFULLY, the phone's owner IS licensed to use all of those binaries, so they can just keep them. Note that they're also included in the FULL SYSTEM IMAGES that HTC ITSELF distributed from developer.htc.com.
*** and that is a HUGE DIFFERENCE between the android platform and wimo.... the fact that HTC distributes ***all*** of the proprietary binaries straight from their website. It means that it ***IS*** possible to generate fully AOSP (but non-functional) system images, and the USER can combine them with the binaries provided by HTC to make a working system.
From what I've seen, HTC REALLY DOESN'T CARE and/or actually WANTS users to build custom roms for their phones. They send out the cease and desist order for distribution of wimo roms, PROBABLY in accordance with MS's demands. MS probably said to them -- "listen, you either try to put a lid on piracy or we're going to stop sending you MSTRASH." HTC distributes GOOGLE apps in the roms on their website because THAT'S WHAT GOOGLE WANTS.
Click to expand...
Click to collapse
1. Didn't even think about all that.
2. That's exactly what I thought. Microsoft is so scared of a lonely developer doing better than what their out-the-ass payed developers do. Honestly, why would the manufacturer of the phone give a damn what you do with it when you buy it? No matter what way you look at it: their task is to sell the phones they manufacture.
So, let me start off by saying that I have searched, read and spent time trying to understand this... but still don't. Which answers why I'm posting this question.
First, what exactly is the reason that an AOSP rom is being developed and a Vanilla Froyo ROM is being developed?
Is the AOSP rom the important one here? Does the working AOSP rom with working kernel mean that we would have 2.2, 2.3.... and so on supported regardless of Samsung?
I understand that Samsung has not supported tremendously up to this point, I understand 2.2 has not been released for the CDMA version yet, and I understand the code they have released is "crappy." When I hear everyone talk about the great work the devs are doing, are they referring to mainly working on the AOSP? If this rom is built, will we be able to just keep developing it for the new versions of Android?
Sorta like in Back to the future when they break off the real timeline and go into the alternate 1985?
Samsungs Android - 2.1, 2.2.... EOL
Dev's Android - 2.1, AOSP, 2.2, 2.3?
Is this how it works? Basically just trying to understand what needs to happen for the Fascinate to get to at least 2.3... not WHEN or even IF it'll get to 2.3.
Thanks
AOSP means Android Open Source Platform.
It's a version of Android built entirely from sources provided by Google. It's completely Vanilla and comes with zero customer or manufacturer customizations. It's easily root-able, and able to be customized completely by the user if desired.
AOSP ROMs are desirable because they tend to be a bit faster and lighter due to their lack of crapification.
AOSP builds are only distributed in their complete and compiled form by Google for their developer handsets (Currently the Nexus One and Nexus S), and not by any carrier or manufacturer.
Okay, I appreciate that definition... I think I've gotten what AOSP is exactly... but I guess my question is does AOSP have any involvement in a future for this phone if Samsung decides to close its doors. Is a working AOSP, radio, kernel... whatever basically devs developing a future of this phone parallel to whatever Samsung does for it?
Like, I see from other threads that the ROM for Froyo and Gingerbread isn't necessarily the problem, its the radio and the RIL? If that is the case, what needs to happen for everything to figured out and for us to have a bright future for the Fascinate? Samsung has to release code for the RIL and radio? Are we SOL without Samsung helping here or will the devs definitely figure something out to get 2.2, 2.3... and so on for the Fascinate?
Bwangster12 said:
Okay, I appreciate that definition... I think I've gotten what AOSP is exactly... but I guess my question is does AOSP have any involvement in a future for this phone if Samsung decides to close its doors. Is a working AOSP, radio, kernel... whatever basically devs developing a future of this phone parallel to whatever Samsung does for it?
Like, I see from other threads that the ROM for Froyo and Gingerbread isn't necessarily the problem, its the radio and the RIL? If that is the case, what needs to happen for everything to figured out and for us to have a bright future for the Fascinate? Samsung has to release code for the RIL and radio? Are we SOL without Samsung helping here or will the devs definitely figure something out to get 2.2, 2.3... and so on for the Fascinate?
Click to expand...
Click to collapse
It's kinda like building an office park, or strip mall or something. You toss up the basic vanilla buildings, and when it's finally done, companies move in and tweak it how they deem fit.
With a working ASOP build, it'll remove some of the shackles of Samsungs bs code.
So... the AOSP build IS THE KEY here? I understand it isn't working yet, but if the devs get AOSP working, does that mean we will get a 2.2, 2.3 and so on regardless of what is released by Samsung?
I'm just trying to figure out what is happening to keep the G1, Droid, Droid 2... supported by ROMs like Cyanogenmod and others, that hasn't happened yet for the Samsung Fascinate.
I'd like to get the Fascinate, but am sorta waiting because I don't wanna be stuck with a phone for the next 2 years that will max out at MAYBE 2.2 if we are lucky.
I don't know where to start with your confusion.
Samsung has not given 2.2 to us. This means that we do not have froyo...
The RIL is an interface layer between the os and the radio. I'm not too sure about it, but anyways...
The developers are working around the fact that samsung has not given further tools that they need to get froyo ported over. Currently they are working on a 1.6 RIL to get froyo working. On another note, vanilla aosp is a good thing because it gives developers more freedom to customize the roms. It also allows for them to be able to port over other roms.
I really don't understand your confusion. If you want a better explanation , I recommend getting on irc.
If I were you, I'd wait. Next gen phones are coming from vzw in the next few months which will essentially blow the existing tech soon.
Bwangster12 said:
So... the AOSP build IS THE KEY here? I understand it isn't working yet, but if the devs get AOSP working, does that mean we will get a 2.2, 2.3 and so on regardless of what is released by Samsung?
I'm just trying to figure out what is happening to keep the G1, Droid, Droid 2... supported by ROMs like Cyanogenmod and others, that hasn't happened yet for the Samsung Fascinate.
I'd like to get the Fascinate, but am sorta waiting because I don't wanna be stuck with a phone for the next 2 years that will max out at MAYBE 2.2 if we are lucky.
Click to expand...
Click to collapse
Basically, that's the hope at least. If there are changes in say, 2.4 that require something that couldn't be hacked around with ASOP, we'll be stuck waiting for Samsung. But with a working ASOP, the groundwork is laid for updates to be ported over a bit more quickly by the devs.
Regardless of the future of this device, the Fascinate is one of the better Android handsets on the market. The screen is brilliant, it's the perfect size, and it's damn fast. The only thing that drags it down is the factory setup (although I personally think it's idiotic to ding the phone because of the inclusion of Bing like some people/reviewers have.)
I'm trying to understand what is going on instead of being one of the millions to ask about updates for this phone. I see phones like the droid series and read that they basically are being supported forever and then I see the Samsung Fascinate, and while I understand that the code is crappy/not released to community... I'm trying to figure out what needs to happen for it to be a supported device like the droids have been.
Bottom line, nothing at all is going to happen unless Samsung releases more than just a 2.2 update? If I see 2.2 drop like tomorrow, does that mean anything for a future, or is it just 2.2 update and we will just get devs releasing their versions of 2.2 roms?
RacerXFD said:
I really don't understand your confusion. If you want a better explanation , I recommend getting on irc.
Click to expand...
Click to collapse
I read his questions as:
"Will a working ASOP build mean better developer support/faster developer released updates?"
I did skim them though.
RacerXFD said:
If I were you, I'd wait. Next gen phones are coming from vzw in the next few months which will essentially blow the existing tech soon.
Click to expand...
Click to collapse
This is a good point. There's an LTE Samsung handset coming out soon, so it might be worth holding out for a little.
Although the Fascinate is no slouch.
Pretty much what I am asking. Like of everything that could possibly happen, Samsung releasing 2.2, AOSP being finished, blah blah what is the key that a consumer should look for to say...
"Well, now the Fascinate has no negatives to it and I have no fear that in a year, we won't still be stuck on 2.1 or 2.2 because Samsung screwed us."
Doesn't necessarily seem like Samsung needs to do MUCH to future this phones life and turn over the keys to the devs (like HTC seemingly has done), but I'm trying to understand what that thing is they need to do. Release a newer kernel, RIL, 2.2 ROM, some code that magically allows devs to port over future roms eternally...
I don't think I care if the phone has LTE capability. I won't get LTE and a regular 3G phone is beyond enough for me. LTE is zero impact for me.
Bwangster12 said:
Pretty much what I am asking. Like of everything that could possibly happen, Samsung releasing 2.2, AOSP being finished, blah blah what is the key that a consumer should look for to say...
"Well, now the Fascinate has no negatives to it and I have no fear that in a year, we won't still be stuck on 2.1 or 2.2 because Samsung screwed us."
Doesn't necessarily seem like Samsung needs to do MUCH to future this phones life and turn over the keys to the devs, but I'm trying to understand what that thing is they need to do. Release a newer kernel, RIL, 2.2 ROM, some code that magically allows devs to port over future roms eternally...
I don't think I care if the phone has LTE capability. I won't get LTE and a regular 3G phone is beyond enough for me. LTE is zero impact for me.
Click to expand...
Click to collapse
What does SAMSUNG need to do? Release their source code, and not just incomplete parts of it.
Will that happen? I doubt it, but it might. Clearly the companies ears are perking up with all the yelling by the consumers.
What can we do in the meantime? Support the devs and wait for them to crank out a working ASOP build and Froyo.
Yes, would be nice to have a fully working AOSP build, and then Froyo... but they are seperate from each other right?
AOSP build is being done for 2.1? It can't just be magically updated to 2.2 can it? Does Froyo have to be officially released for them to update it to AOSP 2.2?
Basically... AOSP will only be updated to whatever version Samsung has released?
Bwangster12 said:
Yes, would be nice to have a fully working AOSP build, and then Froyo... but they are seperate from each other right?
Click to expand...
Click to collapse
No. Android Open Source Project means "Android" in general. It can be 2.1, 1.6, 2.3, whatever. The devs elected to start with 2.1.
AOSP build is being done for 2.1? It can't just be magically updated to 2.2 can it? Does Froyo have to be officially released for them to update it to AOSP 2.2?
Click to expand...
Click to collapse
If you've followed anything in the dev folders, clearly not. JT's "Vanilla" Froyo looks like an AOSP build.
Basically... AOSP will only be updated to whatever version Samsung has released?
Click to expand...
Click to collapse
No. At least not our version.
Bwangster12 said:
Yes, would be nice to have a fully working AOSP build, and then Froyo... but they are seperate from each other right?
Click to expand...
Click to collapse
It's hard to answer your question because AOSP and Froyo refer to two completely different things, which can be the same or separate.
AOSP is basically Android, built from clean, unmodified source code directly from Google, without any changes by carriers or manufacturer.
Froyo is simply the 2.2 version of Android.
So, you can have Froyo that's modified by a carrier and/or manufacturer. This wouldn't be AOSP. And you can have Froyo, built directly from Google code. This would be AOSP. You can also have Eclair (Android 2.1), or any other version of Android that's AOSP or not AOSP depending on whether it was built directly from Google code, or modified by a carrier or manufacturer.
AOSP doesn't refer to a single, particular version of Android, but the state of the code that was used to compile whatever version you want to talk about.
Bwangster12 said:
AOSP build is being done for 2.1? It can't just be magically updated to 2.2 can it? Does Froyo have to be officially released for them to update it to AOSP 2.2?
Click to expand...
Click to collapse
A lot of the issue surrounds the kernel. When Google releases a new version of Android, it runs on a particular version of the kernel, which supports it's particular features. Manufacturers have to modify the kernel to support their particular hardware. So, since Samsung has only released source code for the kernel for Android 2.1, we're stuck on 2.1.
The versions of 2.2 from Kaos and JT are running on the Android 2.1 kernel that's been hacked to enable 2.2 to boot and run correctly. It works, but it's far, far from ideal. It doubles (if not more) the amount of work necessary to get 2.2 running, which is the reason for the rather slow pace of development.
So for your question, once Samsung releases 2.2 (the system and kernel), it'll be much easier to get an AOSP build of Android running, since the devs will only need to worry about the system instead of hacking together a kernel and RIL (radio interface layer) as well.
At least this is my understanding of the situation. I'm sure people with more knowledge and experience can correct me where I'm wrong, but I think this is the basic gist of it.
ChrisDDD said:
It's hard to answer your question because AOSP and Froyo refer to two completely different things, which can be the same or separate.
AOSP is basically Android, built from clean, unmodified source code directly from Google, without any changes by carriers or manufacturer.
Froyo is simply the 2.2 version of Android.
So, you can have Froyo that's modified by a carrier and/or manufacturer. This wouldn't be AOSP. And you can have Froyo, built directly from Google code. This would be AOSP. You can also have Eclair (Android 2.1), or any other version of Android that's AOSP or not AOSP depending on whether it was built directly from Google code, or modified by a carrier or manufacturer.
AOSP doesn't refer to a single, particular version of Android, but the state of the code that was used to compile whatever version you want to talk about.
A lot of the issue surrounds the kernel. When Google releases a new version of Android, it runs on a particular version of the kernel, which supports it's particular features. Manufacturers have to modify the kernel to support their particular hardware. So, since Samsung has only released source code for the kernel for Android 2.1, we're stuck on 2.1.
The versions of 2.2 from Kaos and JT are running on the Android 2.1 kernel that's been hacked to enable 2.2 to boot and run correctly. It works, but it's far, far from ideal. It doubles (if not more) the amount of work necessary to get 2.2 running, which is the reason for the rather slow pace of development.
So for your question, once Samsung releases 2.2 (the system and kernel), it'll be much easier to get an AOSP build of Android running, since the devs will only need to worry about the system instead of hacking together a kernel and RIL (radio interface layer) as well.
At least this is my understanding of the situation. I'm sure people with more knowledge and experience can correct me where I'm wrong, but I think this is the basic gist of it.
Click to expand...
Click to collapse
Okay, thank you for this answer... this makes sense to me.
So, have HTC and Motorola released newer kernels for the devs of roms like Cyanogemod to update their ROMs, despite HTC and Motorola not actually releasing newer versions? I mean, how is the G1 updated as far as it has. Did HTC release a 2.2 kernel to allow devs to put 2.2 on it?
That's were I'm start confused as well.
I understand that Samsung has some proprietary kernel level code and drivers.
But, I'm curious what is the difference between Linux kernel versions used for different versions of Android. It doesn't sound like major version change and hence should not change anything dramatically. It should be mostly bug fixes. That's why jt was able to get kernel work.
As in relation to ASOP for SF, I see it like attempt to adapt Samsung code to current android interfaces. Once again, these interfaces should not change dramatically between versions, because these are evolutionary. So, I assume when done it is pretty much paved road up to 3.0 at least. That said some new features might not work at all, because we do not have working initial binaries from Samsung.
By the way mrbirdman has GB in progress.
Alright... so this may sound like I'm oversimplifying it, but I don't mean to.
Why can't the dev community just create a "custom" kernel to work with their versions of 2.2, 2.3 and so on? You say that they are working to hack the 2.1 kernel Samsung has released so it allows 2.2 to run on the Fascinate... but why can't they just make a 2.2 kernel? Is that sorta what Cyanogenmod is doing to get a 2.2 Froyo build to work on a G1?
Based on the amazing things I've seen the dev community do, building ROMs from scratch, I guess I don't understand how the kernel can't be built specifically for each new version... forgetting about what Samsung releases.
Bwangster12 said:
Why can't the dev community just create a "custom" kernel to work with their versions of 2.2, 2.3 and so on?
Click to expand...
Click to collapse
Theoretically they could, it would just be a lot of work. Hardware drivers might not be compatible with the kernel version designed for 2.2 or 2.3. I don't think manufacturers are required to release the code for their drivers, so if a driver wouldn't work, one would need to be written from scratch, and without the detailed knowledge of the hardware itself, that is very difficult.
Hardware support is very integral to the kernel, so a kernel for one phone wouldn't run at all on another. So in addition to the difficulty of putting together a totally independent kernel, it would need to be done separately for each and every phone out there, and how many versions of the Galaxy S alone are there? How many HTC phones, how many Motorola and LG and Sony and so on.
It's just not realistic for people doing this, essentially, in their spare time.
So, what the devs generally do is wait until a carrier releases a version of Android (System, kernel, radio, etc.), and with all the hardware support in place and working, they can focus on building custom or AOSP versions of the system.
It's not that they couldn't build their own kernel, it's just a matter of practicality, audience and the shelf live of the particular phone. As it is, a new generation of phones are already either coming out or on the near horizon... and our phone is what, 4 to 5 months old?
Bwangster12 said:
Based on the amazing things I've seen the dev community do, building ROMs from scratch, I guess I don't understand how the kernel can't be built specifically for each new version... forgetting about what Samsung releases.
Click to expand...
Click to collapse
The misunderstanding is in the complexity of compiling a custom system, and developing a custom kernel. They are hugely different in terms of complexity.
Think of a ROM as taking Windows 3.1 and simply tweaking the components that are installed by default - what accessories are installed, what wallpaper is selected, the color scheme of the windows. Not terribly complicated.
Think of the kernel as having to compile DOS, complete with custom drivers for all the hardware - CPU, graphics, memory, storage, multitouch, sound, radio, modem, WiFi, networking, power management, USB support, file system support, etc. all by hand.
Anyone know if this is affecting Cyan dev for the SGSii?
While the Samsung Vibrant may not be the newest kid on the block anymore, it’s still quite the capable device and one that has gotten tons of support through community development. One community ROM was the ever-so-popular Cyanogen Mod. I say “was” because support is no longer being offered for this device. Not, it’s n0t because Steve Kondik and his buddies don’t love you anymore.
It’s because of a 911 re-routing issue that causes problems when dialing the nationwide emergency help service. Workarounds have looked promising, but with the 911 operator not able to hear whoever’s calling from this phone with CyanogenMod it kind of defeats the purpose.
We are no longer supporting the Vibrant due to the inability to dial 911. We consider the issues related to this unresolvable without source code from Samsung related to the Radio interface layer and its interactions with the Audio layers and have taken the decision to no longer support this. We apologize for the inconvenience and strongly suggest that Vibrant users use a Samsung ROM due to the 911 issues with any ROMs based on open source code.
You can probably guess why they will no longer support this device. They don’t want to be held responsible for someone not being able to call 911 in a true emergency and time of need. Continuing to support and offer the ROM would be gravely irresponsible of the team.
Although most disclaimers remind users that anything that happens to their phone is not the developers’ fault, this issue is too sensitive to handle improperly and therefore they won’t. Instead, they’ll opt to direct users to TouchWiz-based ROMs based on official firmware versions.
Of course, those on Cyanogen Mod will still be able to use it and if you can find a download somewhere you can flash it, but until this 911 thing gets figured out on some of Samsung’s devices (the Epic 4G also has this issue and is a big reason why Cyanogen Mod was never officially released for it) you can pretty much say goodbye to future updates.
I do strongly encourage users to find and download a Samsung-based ROM that looks good to them because not having an emergency response service is not something you want to have to deal with. Trust me, I know from experience. [Cyanogen Mod via Androinica]
More info before anyone panics:
@Abhisek Devkota:
To clarify, this issue is strictly isolated against the Vibrant, not any of its i9000 counterparts.
International users using 112 do not seem to be affected, and the issue is prevalent on T-mobile's network, regardless of emergency number called (eg 911 or 112). The affected code is applicable to all ROMs utilizing either CM base code or Google's AOSP code. ROMs simply modifying stock Samsung distributions should not be affected.
As for discovery, this was discovered a couple months back, luckily in a non-life threatening situation. Since then, we have had a disclaimer in the release post, hoping that we would be able to come to a solution. Unfortunately, it appears that we will not be able to, and therefor, to limit user endangerment, our liability, and our own sense of personal responsibility, we are freezing any future releases for the device.
There are multiple roadblocks to solving this issue, namely the code responsible is Samsung proprietary, the issue is mainly network specific, and testing the solutions would require multiple calls to 911; which would be a felony in the US to abuse that system. Couple that with Team Hacksung being mainly internationally based, and the probability of solving it becomes a lot less.
---
In other words, this has nothing to do with the i777
Sounds like we gotta all put our heads together and get this 911 bug fixed at all costs
Sent from my SGH-T989 using xda premium
It is my understanding that the development of ROM for this phone may be limited since it won't be available in the US. Right now, I'm wondering if there's anything we could do to try to jump start development? I don't have enough knowledge to develop anything on my own but maybe I could supply data using my Moto X Play? I know enough to install stuff like TWRP without bricking the phone. Anyway, at least, we don't have to suffer the atrocities of an ugly skin like TouchWiz since Motorola adopted a bare to the bone attitude with its firmwares. I also heard that these Motorola phones will be among the first to receive an official Marshmallow update.
I'm in the same boat. I don't know what's all involved with custom kernels or anything, but would love to see how we could tweak our phones.
It's being released over there as a droid variant is it not?
Sent from my Vodafone Smart ultra 6 using Tapatalk
On Verizon, which is quite different from a cellular radio standpoint (not to mention good luck getting the bootloader unlocked (I'm sure Verizon won't let you use Moto's unlock tool)