Database Users

EVO 4G ROM Leaked today.

The shipping ROM of the HTC EVO 4G has now been leaked. The RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_release_171253.exe file is the official ROM present on the devices that will go on sale on June 4th (and probably originates from one the handsets offered yesterday during Google I/O). You can grab the file here. I guess that the next logical step will be an attempt to port this ROM to the HTC HD2.
http://www.mobiletechworld.com/2010/05/21/official-shipping-htc-evo-4g-rom-available-for-download/

I wonder how long it will take......Hopefully not longer than June4th

SPENONE said:
I wonder how long it will take......Hopefully not longer than June4th
Click to expand...
Click to collapse
My prayers are with your post

plzlordplzlordplzlordplzlord.....
Im sure the awesome modders here in the greatest mobile phone fourm in the UNIVERSE can work their magic

hd2 is watching u!

reorx24 said:
plzlordplzlordplzlordplzlord.....
Im sure the awesome modders here in the greatest mobile phone forum in the UNIVERSE can work their magic
Click to expand...
Click to collapse
+1 lol. can't wait to see android on this hd2.

I think it is better to wait for froyo if this rom can be installed on the HD2.

this i would love to see

Could someone who knows about the difficulties associated with porting ROMs quickly describe how feasible getting a work of port of android from the EVO 4G over to the HD2 would be?
I imagine the fact that the camera is different would cause problems?

laserviking said:
Could someone who knows about the difficulties associated with porting ROMs quickly describe how feasible getting a work of port of android from the EVO 4G over to the HD2 would be?
I imagine the fact that the camera is different would cause problems?
Click to expand...
Click to collapse
Lawl, you guys must be smoking some pretty good pot. This will take months. You are assuming that every single internal part save for the camera is identical. I'm pretty certain it won't be. It'll be a long time before any port of Android is working on the HD2. Until then, it's best you not get your hopes too high because you'd surely be disappointed if you think a working port is feasible in 4 ~ 8 weeks.

this topic has been beaten to death over and over guys. i'm not trying to come off as a ****, but please search and read before making posts, because it upsets the devs. A LOT of parts are different between the HD2 and EVO, they don't even use the same touchscreen. This is going to take some time. Be patient.

a quick Google search will reveal picture and video evidence of this already working, along with Windows Phone 7 succesfully ported on the HD2. problems arise with the assignment of the hard buttons more than anything else.

PoisonWolf said:
Lawl, you guys must be smoking some pretty good pot. This will take months. You are assuming that every single internal part save for the camera is identical. I'm pretty certain it won't be. It'll be a long time before any port of Android is working on the HD2. Until then, it's best you not get your hopes too high because you'd surely be disappointed if you think a working port is feasible in 4 ~ 8 weeks.
Click to expand...
Click to collapse
I've got no such expectations, for one I pointed out at least the camera is different and I assume a whole lot of other stuff is too.
Anyway, here's a question I've never seen addressed in any topic but is interesting for layman plebs:
What information do official HTC devs have access to which XDA devs don't, which makes churning out working drivers, etc. for phones doable for the former and nigh-on impossible for the latter? Please don't misinterpret this post as accusing XDA devs of being lazy or anything, I'm just curious as to why it's so difficult.

laserviking said:
Anyway, here's a question I've never seen addressed in any topic but is interesting for layman plebs:
What information do official HTC devs have access to which XDA devs don't, which makes churning out working drivers, etc. for phones doable for the former and nigh-on impossible for the latter? Please don't misinterpret this post as accusing XDA devs of being lazy or anything, I'm just curious as to why it's so difficult.
Click to expand...
Click to collapse
The knowledge that a hefty paycheck is arriving at the end of every two weeks and that if they don't perform, they'll get replaced with another person who is qualified and willing to deliver on said schedule. Things change when you do it as a hobby and when you're struggling to make a better life for yourself and/or spouse and kids.
Even a somewhat working version of Android on the Blackstone came out what, 12 months after its release? Making Android work on a Windows Mobile device is not some plug and play magic or drag and drop process as a lot of you are making it out to be (not directly at you, in general). While I'm only a beginner in programming, I know the difficulty that goes into making a good single working software, let alone making an entire OS work on a completely different set of hardware.

laserviking said:
I've got no such expectations, for one I pointed out at least the camera is different and I assume a whole lot of other stuff is too.
Anyway, here's a question I've never seen addressed in any topic but is interesting for layman plebs:
What information do official HTC devs have access to which XDA devs don't, which makes churning out working drivers, etc. for phones doable for the former and nigh-on impossible for the latter? Please don't misinterpret this post as accusing XDA devs of being lazy or anything, I'm just curious as to why it's so difficult.
Click to expand...
Click to collapse
The official developers get the hardware datasheets from the manufacturers and software apis because they are licensed to work on these devices. If xda devs got those things, it would be much easier.

CraigBirnie said:
a quick Google search will reveal picture and video evidence of this already working, along with Windows Phone 7 succesfully ported on the HD2. problems arise with the assignment of the hard buttons more than anything else.
Click to expand...
Click to collapse
Android has not been ported yet. I don't know where you saw that, but its probably fake. There have been videos of WinPhone 7, but it hasn't been established whether its fake or not.

CraigBirnie said:
a quick Google search will reveal picture and video evidence of this already working, along with Windows Phone 7 succesfully ported on the HD2. problems arise with the assignment of the hard buttons more than anything else.
Click to expand...
Click to collapse
Oh hey, thanks for the link.
Kids on here are incredibly stupid.

zarathustrax said:
The official developers get the hardware datasheets from the manufacturers and software apis because they are licensed to work on these devices. If xda devs got those things, it would be much easier.
Click to expand...
Click to collapse
Thanks! I knew there had to be a missing link somewhere.

porting apps

This may be the wrong thread to put this in (and if so any mod feel free to move it to the correct thread) but i felt that with the amount of experience all you guys have making roms and such im sure you all have a bit of other programming experience too. I was just wondering if there was a way of porting Iphone games to work on android? There is one game in particular that i want bad on my droid that my buddy has on his Iphone but its not available to us yet and there are only rumors that the devs of the game are working on an android version. So if anyone knows of a way or knows of somewhere i can read more about it i would love to hear it, especially since my wife and son are leaving to go back home for a week or two so i will have a lot of free time.
thanks in advance!

There is no easy way to port over iPhone apps to Android. Especially when you do not have the source code, which I doubt you do.
Even if you do have it, you have to rewrite it almost entirely because all iPhone apps are written in Obj-C and all Android apps are written in Java (some have small parts written in C/C++).

nindoja said:
There is no easy way to port over iPhone apps to Android. Especially when you do not have the source code, which I doubt you do.
Even if you do have it, you have to rewrite it almost entirely because all iPhone apps are written in Obj-C and all Android apps are written in Java (some have small parts written in C/C++).
Click to expand...
Click to collapse
Thats pretty much what i expected to hear, which is kind of a bummer... but the more i thought about it last night the more i realized how much work it would end up being considering nothing is perfect and there are always things that are breaking or not working properly and i could only imagine some of the problems that could come up.... but i suppose i could wait a few more months and hope that the rumors are true.

Why it is so difficult?

I do not want to upset anybody, just trying to get some understanding of the entire upgrade to a new OS version.
I'm a programmer myself, but on Windows platform and mostly do middle tier business server side apps. Do not know a thing about Linux and android. But had some java experience in the past.
I wonder why we cannot get Froyo so long? Ain't the sources open? Even if we do not have some drivers, these parts cannot change dramatically from version to version. Published API must be stable...
Is this about Dalvik JVM? But, I guess this must be in released ROMs for other phones in the line.
What's the deal? Will appreciate some explanation here.

Android is open source, but that is only the operating system and the kernel, but the drivers and RIL that make the device actually functional are the issue as far as I'm aware. From what I've read here and in IRC, Samsung gave us a hack-job RIL, which is causing many of the issues with getting an AOSP ROM fully compiled and working. I think there may be some driver issues as well to be worked out yet, but I feel those are less important than getting things like phone/data/messaging working. I'm guessing there are more technical reasons why they can't just get 2.1 or 2.2 built from source, but those are probably the big issues.

Honestly, it boils down to Samsung.
Put simply, they're crappy coders (as HTC once was many moons ago), or they're just hella lazy (I strongly believe its the former, given RFS and this RIL mess). Most companies are pretty crappy coders, but most of the time, it doesn't interfere with major things, like OS upgrades.
That, plus the lack of effort or support on Samsung's part, has me never wanting to buy another Samsung phone again, or ever recommending an Android phone from Samsung....
I'm gonna do my best to find in my next phone another quick processor with a nice super AMOLED screen and be done with Samsung, I've had enough, and I'm a very patient person....

What is RIL? Is this Radio Interface Library?
Is it linked into kernel or other module? Not extractable at all?
As I imagine it to myself, if it is some sort of dll or package, it shouldn't matter if we do not have source, because it's interface have to be already strictly defined. It doesn't matter if it is buggy. It should work with any android version.
Please correct me if I'm wrong.
P.S. I have Dell Axim v50x and people already created ROM from scratch! However it doesn't have RIL. ;-)

CNemo7539 said:
What is RIL? Is this Radio Interface Library?
Is it linked into kernel or other module? Not extractable at all?
As I imagine it to myself, if it is some sort of dll or package, it shouldn't matter if we do not have source, because it's interface have to be already strictly defined. It doesn't matter if it is buggy. It should work with any android version.
Please correct me if I'm wrong.
P.S. I have Dell Axim v50x and people already created ROM from scratch! However it doesn't have RIL. ;-)
Click to expand...
Click to collapse
if it could have been done, birdman would have done it already

Well I think it's a valid question. Some might think it tedious or obnoxious, but absolutely valid. This is a development forum after all. The reason we don't have 2.2 isn't a hardware limitation, so it must be a practical one -- or yes it would be here.
But I'll just speak from speculation in the hopes that someone will correct me. For god sakes this is a development forum! We've got releases, we have fixes, we have patches, we have complaints, we have gossip. I'd love to see all the _development_ discussion I can get.
From a wider puzzle-piece perspective, I would like to know what is missing. We have working drivers. We have working hardware. We have full source from Google for the operating system. There are several other android phones on Verizon, a few even have Froyo. Sprint currently offers a CDMA Galaxy S phone (Epic) with android 2.2, and that phone possibly shares some hardware (though the WIMAX radio is totally irrelevant to us).
I'm not up to speed on exactly what the RIL is, or how it gets plugged into the android kernel. The RIL (Radio Interface Layer) is a software layer between android itself and the drivers controlling the phone hardware. Google provides some samples for a carrier to create one to govern communication on their network. I'd expect one issue of randomly hacking something like this, is if you are taking over your radio hardware's communications, then you have the capability of putting unwanted data on the network, which might even be criminal. Am I being extreme? So, perhaps we can't touch the RIL and need to wait for it to be spoonfed to us by those that bought the radio band from the FCC. Perhaps this code is inexorably married to particular hardware, unavailable for reading, or even encrypted. Maybe the primary limitation is the royal pain in the apricots that it is to inspect, decompile, and reverse engineer binary code.
But what if we could do something?
My understanding is the RIL is only a carrier-specific interface to the underlying hardware. Shouldn't it be similar between phones, even with wildly different hardware? Shouldn't its interface also be similar between close versions of android? The Droid 2 is a verizon phone with a RIL that does indeed work with Froyo. What I'd like to know is A) can another phone's RIL be extracted within the same carrier, and B) Being the abstract entity that it is, what prevents it from being married to the Fascinate's hardware base?
To be honest, I ardently believe a frank discussion (sans opinions, complains, problems, just productive discussion w/ a smattering of facts) BELONGS in the Development forum.
I'll stop here, in case this thread dies, as so many of mine do.

Jt1134, adrynalyne, and fallingup(angel12) are all very capable as well. This is solely the fault of none other Samsung.
Edit: to answer your question, i think that.the answer about RIL is no, although i dont have a good qualified answer about why the RIL from D2 cant be ported im sure that if it could have, it would have. Sorry thats not a better answer.
Sent from my ADR6300 using XDA App

I don't know anything about how the RIL works, but I would assume that it could only be easily ported from one device to another if they were using the same chipset in the underlying hardware for the phone. I doubt you'd be able to take the Droid 2/X RIL, and take it to the Droid 2 Global or Droid Pro. Given that, I'm guessing that you can't really take a RIL from one phone and put it on another without extensive work, since most OEMs tend to use different hardware in their devices. From what I've heard, there is a semi-working AOSP build floating around, so the devs are trying, but Samsung's crappy source to work from is not making things easy for them.

There are actually some semi-working builds of aosp floating arpunfld but the last time I checked one out it was missing one thing that I consider to be kind of a biggie. It couldn't quite make calls. I'm sure they have it to make calls now but there is a reason its not out to the forums yet. I agree withstand nuts up there. Thanks you Samsung.
Sent from my ADR6300 using XDA App

ksizzle9 said:
There are actually some semi-working builds of aosp floating arpunfld but the last time I checked one out it was missing one thing that I consider to be kind of a biggie. It couldn't quite make calls. I'm sure they have it to make calls now but there is a reason its not out to the forums yet. I agree withstand nuts up there. Thanks you Samsung.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
i believe there was still no radio at all in aosp, and the hope is that 2.2 can fill in the gaps

Wow, wow, wow!
Why do we need another phone RIL? Current one from SF at hand should do perfectly. Did Google changed something in android API related to a RIL? I don't know for sure, but never heard or read anything making me think they did it. Android should call RIL and that is set in stone. ALL calls signatures must to be known. Something new may be added, but it is not show stopper.
So, I still do not understand - is it not extractable or what?
Even if not and it is somewhere in protected memory, encoded or whatever, Froyo slapped on top must work, IMHO. And sources available. So, why we stuck waiting for Samsung?
I know, one may say - do it yourself if you are so smart... Once again, I just want to understand root of the problem. I probably can do something, because I have degree and experience. But, it will take me forever. From what I've tried and seen learning curve is very steep.
On the other hand, skilled developer might simply need fresh look at the problem... May be guys just hitting wrong wall?

CNemo7539 said:
Wow, wow, wow!
Why do we need another phone RIL? Current one from SF at hand should do perfectly. Did Google changed something in android API related to a RIL? I don't know for sure, but never heard or read anything making me think they did it. Android should call RIL and that is set in stone. ALL calls signatures must to be known. Something new may be added, but it is not show stopper.
So, I still do not understand - is it not extractable or what?
Even if not and it is somewhere in protected memory, encoded or whatever, Froyo slapped on top must work, IMHO. And sources available. So, why we stuck waiting for Samsung?
I know, one may say - do it yourself if you are so smart... Once again, I just want to understand root of the problem. I probably can do something, because I have degree and experience. But, it will take me forever. From what I've tried and seen learning curve is very steep.
On the other hand, skilled developer might simply need fresh look at the problem... May be guys just hitting wrong wall?
Click to expand...
Click to collapse
is it possible? perhaps...but the 5 or so guys who really develop for this phone havent been able to get it to work....nor is aosp working 100% on any galaxy s phone

Response from developers?
Anyone?

Yes, you know so much, we are waiting for you to fix it.
Hurry the hell up.

adrynalyne said:
Yes, you know so much, we are waiting for you to fix it.
Hurry the hell up.
Click to expand...
Click to collapse
Agree get your ass moving so we can have teh honeycombzzzz. Quit being such a lazy stingy jerk and get us our AOSP!

ksizzle9 said:
Jt1134, adrynalyne, and fallingup(angel12) are all very capable as well. This is solely the fault of none other Samsung.
Edit: to answer your question, i think that.the answer about RIL is no, although i dont have a good qualified answer about why the RIL from D2 cant be ported im sure that if it could have, it would have. Sorry thats not a better answer.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
yes i was just pulling one dev name out for the heck of it
but i subscribe to the "if it could have been done, it would have been done"

adrynalyne said:
Yes, you know so much, we are waiting for you to fix it.
Hurry the hell up.
Click to expand...
Click to collapse
I don't care what you did for community! But you behave like f****g jerk.
No real explanation for the rest of us? Stay on irc, we will survive without your comments here.

CNemo7539 said:
I don't care what you did for community! But you behave like f****g jerk.
No real explanation for the rest of us? Stay on irc, we will survive without your comments here.
Click to expand...
Click to collapse
that may be a problem for those who just stay here as virtually everything is irc only these days...or the majority of it anyway

CNemo7539 said:
I don't care what you did for community! But you behave like f****g jerk.
No real explanation for the rest of us? Stay on irc, we will survive without your comments here.
Click to expand...
Click to collapse
How many different ways do people need to say that "it's being worked on"? The devs are doing a lot of work on our device, but also working with other stuff, all in their free time. Follow the stuff they do on Twitter and github, or join in on IRC.
Attitudes such as your's are precisely why the devs have stopped posting stuff here. You act as though it's a simple process to do things, when it isn't, especially when Samsung gives you a crappy base to start from. The devs have to first get Samsung's source fixed and cleaned up, then start on whatever it is they want to work on, all while finding more bugs and issues that need fixed, primarily all stemming from the crappy source. If you want to be angry at someone, make it Samsung, not the few devs that are working on our device.
Sent from my StupidFast Voodoo Fascinate

As I said - I will survive. I'm OK even with not rooted stock.
Was it so difficult to answer what the real problem is? I don't know what is the problem with this generation? Do I need to be on FB, irc or whatever to get the answer? Why do not answer in place? Ain't it this forum purpose?
No, seems like I need to kiss somebody ass to get meaningful response these days... That way he can maintain his "super god" status.
I do believe I've been pretty polite stating my question, even though English is not my native language. What generated so much sarcasm?

One ROM One Source with Many tweaks

Hi everyone please before anyone throw curses at me, it is only a request to make things more organize at least for noobs like me
i have entered the world of andorid not so much as a month ago with galaxy S2 i was amazed with the possibilities of this software and how much customization can go with it but all this come with cost which is mess, lost and confusion
i mean there is like 10 or more roms for S2 alone as we can see and it just been a month only what will happen after plus we are always asking which is the best rom what is the best theme etc
that is why i suggest the following:
one custom rom which belong to XDA to name as please or XDA rom since XDA the biggest android forum and all developers can work on it to tweak it as they please and submit to the ppl in charge of it and update frequently (example villin rom with its tweaks app which need some work in organizing, i thank him for his work)
in this rom there will be apps like that but will be all in the offical app for tweaks( like cydia in the iphone OS) inside it everything from themes to addons
i know i might not clear but what am saying lets try to have One rom and in it all the tweaks possible since in the end of what am seeing all ROMs have minor difference(someone can shot me down if am wrong and i say sorry)
waiting for your thoughs follow XDA members

A few quick thoughts here. You can never please everyone because people want different things out of a rom and the result can be that as things go forward you end up pleasing no one by trying to be all things to all people. Also right now the roms are fairly similar because the phone is so new but that will change going down the road as things settle in and they will become more divergent. While it seems chaotic now this is not a bad thing in that you likely will find a chef who does work that you will prefer. Once CM comes to fruition you will see in some respects what you are talking about as many people will theme directly for it and so also with mods.

There are so many more devices, roms and people. Some roms make the whole operating system look completely different. (miui)
You want everything easily in one place. I actually don't. If you want one rom, pick one and stay with it. Simple right?
I like to compare different roms, certain ones have better features but a long with that it brings worse battery life. So I like weighing the differences.
Sent from my Samsung Galaxy SII with XDA Premium

Stick to the stock ROM for now, it's pretty balanced, till a few more months and Dev's get the hang of this new Phone.

Problem with the original only one rom . Who do you choose for the one rom do you ban the other devs .Ban Chainfire ban others like him who have developed individual bits that come together to make a whole .
No Android is independent custom at will rather than the dictate of one person (Hi Steve ).
Noobs need to accept that its a learning curve they have to learn how to read first follow instructions second browse the posts third and search fourth .
Simply put one rom defeats the whole point of XDA and Open Source .
jje

well thanks guys about the reply but i guess the idea far from coming to android or maybe because i am new, i cannot see the picture you guys are seeing since i came from iphone which used to have one version(jailbreak firmware) with cydia(the home of all great thing for iphone) and thought it is possible in android but it seems not so i just have to do what most have said stick to one rom and be updated with it
in the end i just wanted to share my thoughts and it has been nice reading your thoughts on the matter
stay alive

MoeBD said:
well thanks guys about the reply but i guess the idea far from coming to android or maybe because i am new, i cannot see the picture you guys are seeing since i came from iphone which used to have one version(jailbreak firmware) with cydia(the home of all great thing for iphone) and thought it is possible in android but it seems not so i just have to do what most have said stick to one rom and be updated with it
in the end i just wanted to share my thoughts and it has been nice reading your thoughts on the matter
stay alive
Click to expand...
Click to collapse
But thats the whole difference ONE = IPhone
What you want = Android .
What if that one rom is far behind rather than advanced = no choice .
If i had to go down the IPhone one rom walled garden do as you are told path i would not even contemplate a Smartphone .I want choice simple as that .
One rom might as well stick with the basic Google rom .
jje

Ok, in general these are the roms out here or yet to come:
- Android with Touchwhizz
- Stock android
- MIUI
- Cyanogenmod
- Stock android with Cyanogenmod tweaks etc
- Possibly a Sense rom.
These are 6 different android variants already. How can you put them in one rom? That is not possible. I like the stock android, you like touchwhizz etc.
The main advantage is that you can switch roms easily and flash the rom that suits you.
I agree that in the beginning you can't see the whole picture, but you will in time. Like JJEgan says it's a learning curve, although a lot of new people don't seem to realize that.

No Love

The X doesn't get nearly the love it deserves. It's still a perfectly good device with plenty of untapped potential.

So... what lead you to do that comment?

jorgicio said:
So... what lead you to do that comment?
Click to expand...
Click to collapse
Just a thought. No need to be snarky.

UbuntuBrandon said:
Just a thought. No need to be snarky.
Click to expand...
Click to collapse
Hey, I'm chilled out, I thought you had a problem with a Moto X, such as a brick or something what you expected but it did not happen D:

jorgicio said:
Hey, I'm chilled out, I thought you had a problem with a Moto X, such as a brick or something what you expected but it did not happen D:
Click to expand...
Click to collapse
Just doesnt get as many people dev'ing for it as other flagships this year. yea its a little old now but still lol

UbuntuBrandon said:
Just doesnt get as many people dev'ing for it as other flagships this year. yea its a little old now but still lol
Click to expand...
Click to collapse
Cause there is no need to. If you switch away from stock, you lose everything, that is special about this phone. I am in love with active display.
Not sure why people crave for every next phone with EVEN MORE cpupower. Dualcore can do everything just fine and who cares if apps load 0,02sec faster o_0

UbuntuBrandon said:
The X doesn't get nearly the love it deserves. It's still a perfectly good device with plenty of untapped potential.
Click to expand...
Click to collapse
this topic has been posted several times over, with the same results. people, in general, love the phone how it is. the only benefits you will receive are through xposed. ROMs are basically non-existent (compared to some devices) although there is a kernel being developed.
my opinion: root/unlock, xpose/hack, done. the phone doesn't need any "help".

The OP is very correct. The Moto X did not receive nearly as much love as most other flagship phones. Now here is where the hate mail and complaining begins. Everyone says you don't need roms it breaks active display. WRONG run Eclipse or any other stock based rom it works fine. It is only broken on Aosp roms and they have their own active display so do some homework. And everyone feels like Xposed and gravity box is the best thing in the world. It hack and slashes your framework. I would prefer to have a dev hard code in the mods so it is much cleaner. But hey I am no dev so everyone will ignore this and continue saying the X does not need anything but stock and xposed and gravity. I am glad some are happy with that.

I'm with Travis. Stock (blur?) Based Roms are better than stock. I'm no fan of xposed either. Adding another framework to Android seems so... TouchPissy (twframework-res.apk anyone?).

Travisdroidx2 said:
The OP is very correct. The Moto X did not receive nearly as much love as most other flagship phones. Now here is where the hate mail and complaining begins. Everyone says you don't need roms it breaks active display. WRONG run Eclipse or any other stock based rom it works fine. It is only broken on Aosp roms and they have their own active display so do some homework. And everyone feels like Xposed and gravity box is the best thing in the world. It hack and slashes your framework. I would prefer to have a dev hard code in the mods so it is much cleaner. But hey I am no dev so everyone will ignore this and continue saying the X does not need anything but stock and xposed and gravity. I am glad some are happy with that.
Click to expand...
Click to collapse
Sure they have an app that works like active display but doesn't use the lowpower-chip that the stock app is using. So your juice will go out the window using it cause for it to work like active display, it has to monitor the sensors, preventing deep sleep.
What's the point in developing, if you can't use AOSP? I know there are stock-based roms, but I wouldn't call that developement. That are merely stripped stockroms with added apps and some tweaks. I like a good AOSP-rom as much as the next guy though. It's a pain to make it work like Slim does and I'd rather just install Slimkat but as I said, I'd hate to lose active display.

Hasuris said:
Sure they have an app that works like active display but doesn't use the lowpower-chip that the stock app is using. So your juice will go out the window using it cause for it to work like active display, it has to monitor the sensors, preventing deep sleep.
What's the point in developing, if you can't use AOSP? I know there are stock-based roms, but I wouldn't call that developement. That are merely stripped stockroms with added apps and some tweaks. I like a good AOSP-rom as much as the next guy though. It's a pain to make it work like Slim does and I'd rather just install Slimkat but as I said, I'd hate to lose active display.
Click to expand...
Click to collapse
You have no idea what you are talking about. I recommend looking into Eclipse. Highly modified stock based with his own coding for many features. Active display is not lost. And for the record I don't run aosp on this device but love aosp on other devices. But saying a stock based ROM is not developing then you are way out of line!
Do yourself a favor just run stock with xposed lol

Travisdroidx2 said:
You have no idea what you are talking about. I recommend looking into Eclipse. Highly modified stock based with his own coding for many features. Active display is not lost. And for the record I don't run aosp on this device but love aosp on other devices. But saying a stock based ROM is not developing then you are way out of line!
Do yourself a favor just run stock with xposed lol
Click to expand...
Click to collapse
I am no developer too and what I said came from my impression of some glances through the threads. But like I said, I am not able to judge and appologize if I oversteped. Didn't mean to offend.
Maybe many people are held back because of the risks involved in flashing with the Moto X. I own a Nexus 7 and a Defy and never was it such a hassle. Like you can't downgrade or you'll brick your phone and stuff. I guess devs only develop either for the phones they own or phones, that have a high demand for customroms. Neither of which are true with the Moto X I think.

Well developing "stock-based" roms IS indeed development, but it is probably not "original development" based on the XDA documentation. Developing an AOSP-based rom (as the original maintainer and not a derivative of his/her work) would be considered "original development".
The statement that the AOSP-compatible variant of Active Display does not use the "low voltage core" and hence results in higher battery usage than stock active display is correct.
Regardless, all DEVs, whether contributing "development" or "original development" deserve our respect and gratitude. Without them, XDA could not exist.
If anyone wants to read the official clarification between development and original development, see here: http://forum.xda-developers.com/moto-x/orig-development/original-development-t2456997

samwathegreat said:
Well developing "stock-based" roms IS indeed development, but it is probably not "original development" based on the XDA documentation. Developing an AOSP-based rom (as the original maintainer and not a derivative of his/her work) would be considered "original development".
The statement that the AOSP-compatible variant of Active Display does not use the "low voltage core" and hence results in higher battery usage than stock active display is correct.
Regardless, all DEVs, whether contributing "development" or "original development" deserve our respect and gratitude. Without them, XDA could not exist.
If anyone wants to read the official clarification between development and original development, see here: http://forum.xda-developers.com/moto-x/orig-development/original-development-t2456997
Click to expand...
Click to collapse
This is correct. But it is also correct that the X didn't get much love from the developer community. That's probably because it is so stock-based. There was very little, at the time of it's release, that people would have wanted other than the stock features.
I had a Samsung Epic 4g before this phone, and it had development even 2 years after it's release. I was running the latest Cyanogenmod 11 on the device even though it was so out of date.
The Moto X is a great phone and yes, it deserves more love, but it's hard to get that when the device is so 'stock' that only a minority of people actually want other options like Xposed, Custom ROMs, etc.
Any Samsung device on the other hand, plenty of people don't like TouchWiz so the developers get right on getting to back to stock android.

Who cares about ROM's or rooting when the phone allows you to do everything you need.
I really don't feel the urge to root mine at all. It does everything I need it to.
I really love the battery life and cool features like Active Display. I always use Touchless Control when I'm in the shower to do stuff lol, also when I'm driving.

Wutang200 said:
Who cares about ROM's or rooting when the phone allows you to do everything you need.
I really don't feel the urge to root mine at all. It does everything I need it to.
I really love the battery life and cool features like Active Display. I always use Touchless Control when I'm in the shower to do stuff lol, also when I'm driving.
Click to expand...
Click to collapse
I am glad you are so happy with your phone. Just because you don't have any needs for anything other than stock does not mean others feel the same way.

Like what??
I seriously can't even think of what else I'd want in a smart phone.

Wutang200 said:
Like what??
I seriously can't even think of what else I'd want in a smart phone.
Click to expand...
Click to collapse
If you have no idea why you would need root or have a custom rom then you should just stay stock. Everyone uses their phones different. The reasons why I bought a dev edition is too long to list. The moto X is a good device stock. But that does not mean that it can not be improved.

Wutang200 said:
Like what??
I seriously can't even think of what else I'd want in a smart phone.
Click to expand...
Click to collapse
The reason most people on this site buy android over apple.
The sheer fact that they can put their own spice on the device and truly make it an experience they love.
Just simple economics, that's why android has such a greater global marketshare of smartphones.
Because the user experience is just hands down better and less locked down, like apple.
And the more you can do with an open source architecture, the "better"

Moto X review
UbuntuBrandon said:
The X doesn't get nearly the love it deserves. It's still a perfectly good device with plenty of untapped potential.
Click to expand...
Click to collapse
Hello,
Indeed, the comment you have posted is right. If you compare Moto X with the other brand like Samsung and Sony then the features and quality in every brand we can see somewhere quite similar. And Moto X has its own name and originality to be in market.