Database Users

Vanilla (stock) ICS vs. Sense 4.0 + ICS

In my recent mental debate over the EVO 4G LTE vs. the Nexus, I've pondered the differences between stock ICS (pure/vanilla/etc) and the ICS we will see on the One series by HTC, including our very own EVO sequel. From the few screenshots I've seen of the One X, it does not remotely resemble the ICS I've learned to know and love with the work our devs our doing to bring the latest and greatest to the OG. Examples include the lockscreen (the Sense ring appears to still be the default one - is there an option to go straight ICS for the lockscreen?), the dock (I'm sure I can switch the launcher to fix this issue...), the notifications pulldown (I've actually not seen the Sense one yet, but I've heard various things indicating it is different from the one I'm no accustomed to), etc. Heck, even the color of the battery meter is green instead of blue!
Does anyone know or at least have an idea if we can change some of those things without rooting our devices? Having a brand new device, I don't plan on needing to root (or at least install custom ROMs, that is) for a while. But I am already missing the slick new interface Google has provided. While many claim that Sense 4.0 is going for the minimalistic approach to the latest iteration of their infamous skin, why do I feel like they have completely altered a widely praised operating system that has barely rolled out? I'm a little saddened when I see the video of the EVO 4G LTE and feel like the look of everything is dated.
But then I look at the hardware, think about the devs who'll inevitably move to this phone, and that excites me about the possibilities. I guess I'm more curious than disappointed, but I was wondering others' feelings on this topic.

Long answer short, you'll get aosp, miui and sense on the HTC which is nice if you get bored and want something different.
Sent from my PC36100 using XDA

alaman68 said:
Long answer short, you'll get aosp, miui and sense on the HTC which is nice if you get bored and want something different.
Sent from my PC36100 using XDA
Click to expand...
Click to collapse
Can you make your short answer slightly longer? Haha how would I get AOSP and MIUI on the EVO LTE? You mean one devs get to work on it? Or stock?
Sent from my PC36100 using XDA

PsiPhiDan said:
Can you make your short answer slightly longer? Haha how would I get AOSP and MIUI on the EVO LTE? You mean one devs get to work on it? Or stock?
Sent from my PC36100 using XDA
Click to expand...
Click to collapse
Right. Not stock, would have to be rooted. My bad. The devs will be all over that phone anyway so it will be a blast
Sent from my PC36100 using XDA

It's a *good* thing the phone comes with Sense, its one more option you have, and Sense does add some useful features. Custom rom's will offer all kinds of options including optimized and bloatware free versions of Sense.

alaman68 said:
Right. Not stock, would have to be rooted. My bad. The devs will be all over that phone anyway so it will be a blast
Sent from my PC36100 using XDA
Click to expand...
Click to collapse
Completely agree. I'm kind of thinking of galaxy nexus, cuz I'm not fond of sense. But, I'm sure in no time we'll be able to rip sense OFF that SOB and put AOKP or some other variant of vanilla ICS.
Then, if you wanna run sense for a few days, that option will still be there. It's win-win.
Sent from my PC36100 using xda premium

If I'm running Sense 4.0, do you think I'll still be able to get the Quad ICS unlock screen, or something like that? I LOVE that lockscreen - way better than the silly ring that Sense creates. I don't understand why they didn't change that from 3.0 and 3.5 to something fresh. Oh, I would assume I have the "unlock with face" option too on this phone? It's been so long since I ran Sense, I forgot if these things are changeable or not!
My only concern with the custom ROMs is whether things will run okay, like camera and such. Also, if you are running AOSP, you'll miss out on the supposedly amazing camera suite that Sense 4.0 provides, right?
Tough choice!!!

Sense 4.0 + ICS ALL DAY!
Sent from my PC36100 using XDA

I went to tmobile today and toyed with the one s. I will say it isn't the ICS we know from the current development but it is beautiful and sleek. The soft keys are a bit cumbersome but I could get used to it. I am in no way drawn away from the evo lte and am more than anxious to own that device!
Sent from my PC36100 using xda premium

imheroldman said:
I went to tmobile today and toyed with the one s. I will say it isn't the ICS we know from the current development but it is beautiful and sleek. The soft keys are a bit cumbersome but I could get used to it. I am in no way drawn away from the evo lte and am more than anxious to own that device!
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
That's awesome, especially considering the One S is inferior to our EVO we're getting...
Sent from my PC36100 using XDA

Well I will answer my own question at this moment, because I stopped into a T-Mobile and played with the One-S for about 10 minutes. It appears that ICS as we know it is VERY coated by Sense, but not necessarily in a bad way. It is still beautiful, just very different. I noticed that there were no quick settings in the notifications menu, which is one thing I was very curious about. But overall, really nice and REALLY amazing! Considering that is the crappy version of our EVOs, I cannot wait for this thing. The One-S screen was awesome, and I know it can't touch the screen (both size and resolution-wise) of our new toy coming out. But the UI was terrifically smooth, the feel was nice (physically), and Sense was overall not intrusive. It was just omnipresent. I'm not disappointed at all - and I know the devs will give us amazing options in terms of removing Sense, or tweaking Sense to give us cool features like quick settings and slide to change brightness.
I can't wait until the One-X is out so that I can play with that one, since it will give a much more accurate portrayal of our experience we can expect. May 18th can't get here soon enough!

I'm posting this everywhere . Its a post by toastcfh over in the oneX forums about how much HTC locked the phone down. Among many things, it is impossible to mount SD from recovery due to their locking, even with custom recovery and HTC dev unlock. If toast says it, it is so, I mean, the guy is an Android/Linux GENIUS. he's the one that had the Evo root method instructions posted before launch day.
Quote.....
no, USB mount does not work in recovery. It appears to be locked out in recovery mode. the workarounds to get it working are one of two things.
(1) fastboot boot awesomeRecovery.img (this works because fastboot then boots recovery on the boot/temporary partition. So the you're not actually in recovery mode
(2) Offmode (this works because again you're again not technically in recovery mode. It uses the recovery ramdisk, kernel, and binaries but its still not technically recovery.
On that note I've seen suggestions that it's possibly a recovery issue with cwm and twrp. Unfortunately it doesn't appear to be the case. If it were then in CWM u wouldn't have usb when u fastboot boot the recovery or in offmode (fair assumption since both these options use the same kernel, ramdisk and binaries as recovery?). Can it be fix? Not that i know of. It looks to me like a total radio or bootloader lockout from using USB in recovery. Which means on a radio or bootloader level USB is disabled in recovery mode.
On that note I think we should raise the point to HTC that this locking down of the device does not suite our needs.Key points of fail would be as follows.
(1) Can NOT flash the boot partition from recovery. I've personally contacted HTC on this numerous times and they seem to just not care. Responding with "It's a security issue" and so forth. I would love to know how this is a security issue of any sort. Every other Android device has this ability except HTC devices since they started the HTC unlock ordeal. It's utter fail IMHO and HTC should listen to our needs .
(2) Can NOT flash recovery or boot partitions from system. This issue is NOT a deal breaker and isn't so bad when it comes down to the nitty gritty. But since the issue above exists, flashing with applications like htc dumlock and such were our only options. These work around apps cant be used to flash now because of the lockpout from system and it wouldn't be such an issue if HTC didnt lock us out in recovery from flashing boot.
(3) Can NOT flash P*IMG.zips in hboot/bootloader anymore. For the unlocked device running a custom firmware this is a must. Specially when radio updates and such are needed from the OEM. We seen a big use of this on the Sensation when HTC updated the device from Gingerbread to Ice Cream Sandwich. The update required new hboots, radios, and partitioning to actually use. So in that instead of having to flash a RUU Which didn't exist the only choice was to flash a custom P*IMG.zip that included all the radios and images need to run the builds. At this point we can't update those image/partitions without flashing an RUU. This makes no since and doesn't seem to do anything but make things more difficult on the unlocker to customize and modify their device.
(4) If all the conditions above HAVE to exist. Then why not give us documentation or utilities to flash fimware.zips from recovery like HTC does? When HTC was the proud Nexus device there was full support and documentation available on how to flash firmware on their devices. This made anyone choosing an HTC device blessed with knowing that their device was not only open and unlocked, but when flashing firmware that it was being flashed correctly to Google and HTC's standards. This code has now been moved out of recovery since right before the move to edify scripting and moved to vendor/htc/ (not arguing this choice as thats where it belongs from a maintaining point of view). But the problem is that vendor/htc is proprietary now. Which means Documentation and support for flashing firmware correctly is not available and left to developers of recoveries for the community to figure out. One would think if HTC was standing behind us that they would step up and give us a PROPER/OPEN/REAL unlock, or if they cant for the lame excuse of security concerns, then give us the documentation and utilities to flash the boot and firmware partitions properly. I mean really... what is there to lose there?
(5) WHAT WAS THE POINT OF HTC UNLOCK? I was to reach out and except us as a community. It was to keep us from having to exploit their firmware and look for holes to gain control of a device we rightfully own. WHAT DID HTC UNLOCK DO? It unlocked the devices at first and with each new revision of the unlock it gets more locked down and harder for us to use it as intended. WHAT DOES THAT LEAD TO? It leads to us hoping someone will take the time out of their life and exploit HTC's firmware so we can have access and control of our devices. I mean, it's bad when u have people poking a device with a paperclip to get a device unlocked to avoid a official unlock.
Bottom line; I'm personally fed up with HTC's unlock. It's absolute crap! It does not serve the purpose it was intended and only makes things harder then they were before. As a devoted HTC customer it has me questioning if my next device will be an HTC. With all the other options that would allow me to spend less time trying to gain proper access to my device and more time actually having fun with it, why choose HTC? Everyone else is shying away for these same issues. Everyone with an HTC unlocked device waits for someone to exploit HTC's firmware and give them a proper unlock. Why not just choose a device without the locked down/unlock instead? IDK but HTC needs to step up and listen to us. Every HTC forum with an HTC Unlock is screaming for these issues to be fixed.
My call to HTC is to fix these issue and/or give us proper documentation on flashing firmware to our devices via custom recoveries. The boot flashing lockout is dumb, pointless, and in NO WAY a security threat AT ALL and is nothing more then a CRAP RESPONSE to something that they sould be working to correct, instead of ignoring. In the end its hurting HTC's relations with developers and is ultimately doing the opposite of what it's original intent.
HTC, PLEASE READ AND LISTEN!!!11ONEone
To everyone else, SPREAD THE WORD!!!ONEone
End quote.........
There has to be a way to petition HTC. Reading this is making me lean galaxy Nexus, ...and I F$%kin HATE Samsung.
Edit: this post is from the One X forum TWRP topic.
Sent from my PC36100 using xda premium

No way I'm buying a Samsung phone.
I'll trust that someone will figure out how to get around the issue at some point. I love how the phone is stock anyway.
Sent from my PC36100 using XDA

PsiPhiDan said:
In my recent mental debate over the EVO 4G LTE vs. the Nexus, I've pondered the differences between stock ICS (pure/vanilla/etc) and the ICS we will see on the One series by HTC, including our very own EVO sequel. From the few screenshots I've seen of the One X, it does not remotely resemble the ICS I've learned to know and love with the work our devs our doing to bring the latest and greatest to the OG. Examples include the lockscreen (the Sense ring appears to still be the default one - is there an option to go straight ICS for the lockscreen?), the dock (I'm sure I can switch the launcher to fix this issue...), the notifications pulldown (I've actually not seen the Sense one yet, but I've heard various things indicating it is different from the one I'm no accustomed to), etc. Heck, even the color of the battery meter is green instead of blue!
Does anyone know or at least have an idea if we can change some of those things without rooting our devices? Having a brand new device, I don't plan on needing to root (or at least install custom ROMs, that is) for a while. But I am already missing the slick new interface Google has provided. While many claim that Sense 4.0 is going for the minimalistic approach to the latest iteration of their infamous skin, why do I feel like they have completely altered a widely praised operating system that has barely rolled out? I'm a little saddened when I see the video of the EVO 4G LTE and feel like the look of everything is dated.
But then I look at the hardware, think about the devs who'll inevitably move to this phone, and that excites me about the possibilities. I guess I'm more curious than disappointed, but I was wondering others' feelings on this topic.
Click to expand...
Click to collapse
There IS PLENTY of apps on the play store that offer home screen and lock screen customization, such as launcherpro, milocker, gosms, as far as changing the status bar and battery bar i'm not so sure, i haven't been on a phone with s-on in a while and can't tell you what rootless tweaks would work

Motorola is pleased to provide the open source software used in the Ultra-Family devi

I haven't seen this posted anywhere else yet. Looks like this is the source for the Droid Ultra/Maxx line.
Hopefully using this and the AOSP 4.3, we can get a 4.3 ROM brewed.
Announcing the release of open source for the Ultra family of products
And if you want the source for the Moto X it's there as well:
Announcing the release of Open Source Software for Moto X

Sorry for the noob questions but how does this effect the bootloader? Will it completely unlock the device for recovery/kernels/ROMs? TIA.
Sent from my SCH-I605 using Tapatalk 4

dr_acula said:
Sorry for the noob questions but how does this effect the bootloader? Will it completely unlock the device for recovery/kernels/ROMs? TIA.
Sent from my SCH-I605 using Tapatalk 4
Click to expand...
Click to collapse
This won't effect the bootloader but could be used for kernels and ROMs on the developer editions where the bootloader is unlocked.
Sent from my XT1080 using xda app-developers app

rowland007 said:
This won't effect the bootloader but could be used for kernels and ROMs on the developer editions where the bootloader is unlocked.
Sent from my XT1080 using xda app-developers app
Click to expand...
Click to collapse
Does that mean there's no hope still for locked devices? I got my Maxx and am now questioning if I should return it for a device that can be unlocked. I really love everything else about this phone though.

From what I have read around the forums, if you are looking for unlocked then this phone line isn't the way to go.
Sent from my XT1080 using xda app-developers app

Yep, the developer edition will probably be less headache for you in the long run.
Sent from my Nexus 7 using xda app-developers app

I don't really have 650$ lying around though :/
Sent from my XT1080 using xda app-developers app

Safestrap for moto X released, likely for maxx soon

rowland007 said:
I haven't seen this posted anywhere else yet. Looks like this is the source for the Droid Ultra/Maxx line.
Hopefully using this and the AOSP 4.3, we can get a 4.3 ROM brewed.
Announcing the release of open source for the Ultra family of products
And if you want the source for the Moto X it's there as well:
Announcing the release of Open Source Software for Moto X
Click to expand...
Click to collapse
thank you for the links.
thread moved to general section

Toledo_JAB said:
thank you for the links.
thread moved to general section
Click to expand...
Click to collapse
is this phone is locked to verizon only? how about the gsm? it's locked too?

The phone can be used globaly. That includes GSM networks.

Out of curiosity, is there any development going on with the Droid Maxx developer edition right now? I realize that some of the Moto X stuff works OK, but until someone figures out how to get the capacitive buttons working we're not going to see any ROMs. I'm willing to shell out the extra money for the Maxx Developer Edition if it meant I wouldn't be forced to wait for Verizon to approve firmware updates, but right now it's not looking promising that anyone is going to bother with Droid Maxx DE ROMs. Unless, of course, someone figures out how to unlock the bootloader on the non-developer version.

I haven't seen any activity in the known channels but then again it may be too early to expect anything.
On another note, it would be nice if you could port the Google Edition ROM over to the non Google Edition phones, without having to unlock the bootloader, maybe?

Yeah, I'm surprised at the complete lack of development on this phone. I realize that developer edition devices won't have communities nearly as large as other devices, but I expected at least SOME basic AOSP ROM's.

Wouldnt this being a offical source thats made for our phones atleast allow us to put 4.3 into our phones? Id guess it runs the stock kernel which is signed.

sfreemanoh said:
Yeah, I'm surprised at the complete lack of development on this phone. I realize that developer edition devices won't have communities nearly as large as other devices, but I expected at least SOME basic AOSP ROM's.
Click to expand...
Click to collapse
Yeah, I particularly expected some basic ROMs too, since the Maxx will essentially run Moto X ROMs (apparently someone just needs to figure out how to get those ROMs to use the Maxx's capacative buttons). But, there's not a ton going on with the Moto X, either. I'm guessing that's mostly because the Moto X is already mostly a stock ROM. You could build your own AOSP ROM, I suppose, but then you'd lose some of the major features of the Moto X and Droid lines. They're working on CM 10.2, though.

I'd be happy with an AOSP ROM with touchless controls and active notifications
Sent from my XT1080 using xda app-developers app

I have to say since SS came out and we have exposed as well as modules like gravity box etc I don't see a huge need for ROMs. This phones is almost stock android as it is. I would be happy with a deodexed system so it would be easy to install inverted apps and such. I think that is all this phone needs. Other than a ROM that looks or acts completely different from stock what would be the benefit. Without an unlocked boot loader I have always noticed kexec Roms to run glitchy. I don't want a glichy phone when I can do what most Roms do using exposed etc. I think the time would be better spent on creating themes that could be flashed to the stock system. This is just my opinion based on using the maxx for the last 2months.

bigv5150 said:
I have to say since SS came out and we have exposed as well as modules like gravity box etc I don't see a huge need for ROMs. This phones is almost stock android as it is. I would be happy with a deodexed system so it would be easy to install inverted apps and such. I think that is all this phone needs. Other than a ROM that looks or acts completely different from stock what would be the benefit. Without an unlocked boot loader I have always noticed kexec Roms to run glitchy. I don't want a glichy phone when I can do what most Roms do using exposed etc. I think the time would be better spent on creating themes that could be flashed to the stock system. This is just my opinion based on using the maxx for the last 2months.
Click to expand...
Click to collapse
I agree..seems as thow, if I had this stock ROM with a gray gapps to match system colors, maybe even a transparent status bar option, I'd be tickled..I do like some of the Apps. that come with this ROM, games I'm not into, and the "Amazon" stuff, nor the NFL, Ingress I would delete, BUT..The Droid Zap, Touch less Controls, NFC and others I'd like to keep..I do enjoy this device and for the most part, like the stock ROM..
Oh..and be able to turn GPS Off and On without having to give permission ever time ( check or uncheck the box)..
SafeStrap ver. 3.63a
System > 12.7.7.obake-maxx_verizon
Android > 4.2.2
Baseband > MSM8960PRO_BP_2323.011.75.00R
Kernel > 3.4.42
Build > 12.9.0Q2.X-160-OBK_TA-14-7
XT1080M (aka) Droid Maxx
(#2)

I'm perfectly happy with stock MotoX/Droid ROMs too, particularly since they are so close to stock Android. But, I don't want to have to wait for Verizon to approve firmware updates. I got a Galaxy Nexus hoping to avoid some of the headaches associated with flashing ROMs, That didn't exactly turn out as expected (though probably how I should have expected it).

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.

[BOUNTY][vk810] $135 KICKSTART KITKAT/LOLLIPOP ROM DEVELOPMENT

users of the vk810 are currently prepared to fork over $135+ to the Developer that produces a working L build, doesn't have to be 100%, but it needs to have the basics; data, GPS, wifi, etc... Any takers?
BOUNTY SET TO $135!!

Note: I sold the tablet and am no longer in the bounty. Sorry.

@adrianrom
Contact this guy.
Sent from my iPhone using Tapatalk

EdenGottlieb said:
@adrianrom
Contact this guy.
Click to expand...
Click to collapse
who is that? spelling mistake maybe?

cammiso94 said:
who is that? spelling mistake maybe?
Click to expand...
Click to collapse
He's an xda dev that posted great lollipop rom for v500
Sent from my iPhone using Tapatalk

I'd be willing to donate as well. Getting the tablet free. Should be here tomorrow.

I will add $10 if it has working LTE, Wifi, GPS and Bluetooth.

razgriz8426 said:
I will add $10 if it has working LTE, Wifi, GPS and Bluetooth.
Click to expand...
Click to collapse
All of those things should be covered with the $100, we'll just say that we have the bounty set to $110 or so. Anyone want to put on top? Lets get in touch with a developer to get this rolling!

Do u users have a working kitkat tree?

a2441918 said:
Do u users have a working kitkat tree?
Click to expand...
Click to collapse
we have a semi-working CM11 devicetree/kernel ported from the non-LTE model (LTE data/GPS doesn't work, everything else seems to work)
I'm still trying to understand more about kernel development/porting, just not much time to look at it...
http://forum.xda-developers.com/showthread.php?t=2759270

Why do you want Android 5.0 so bad to the point you want to pay money? I'm mean specifically, what in it is such a big deal that you need it NOW?
Why not just go buy a Google Play Edition if you want Lolipop that bad?
There's more to life than obsessing over having the lastest O/S version

Well a bounty is less than a gpe tablet lol. So there's that.

jazee said:
Why do you want Android 5.0 so bad to the point you want to pay money? I'm mean specifically, what in it is such a big deal that you need it NOW?
Why not just go buy a Google Play Edition if you want Lolipop that bad?
There's more to life than obsessing over having the lastest O/S version
Click to expand...
Click to collapse
users of this great, underestimated beast of a tablet, that for some reason LG dumped some unoptimized garbage on to it, then "replaced" it with tablets with WORSE hardware, are really missing out on what this tablet can do. What it needs is a build that will run perfectly on it. Furthermore if it works half as good as it should, it would be better than what LG is currently doing with it.
Lets get a dev to get 4.4 working with radios, and we'll go from there. We may have to wait for a dev to pick up this device, with that; I am also willing to allow the dev my device as a start.

I'll add 50 to it

I would just like to see CM11 or CM12.. The tablet would run so much better.

It's starting to look like a significant amount of people are buying this tablet with the recent promotions by Verizon. I really hope that a dev can pick this up and see if they can get us a working ROM. I'm in the process of prepping a server to do some of my own ROM builds for the LG G3. Wish we had a working base because I don't have the knowledge to do anything but compile the builds.

Even a custom kernel would be nice so we could boost the CPU back to the 1.7 that the other models run at.

I'll kick in $20 for this. Would be nice to be cm12 or even GPE rom with working data (or not at this point).

I just got this tablet from verizon about 2 weeks ago, I dont consider myself a dev in any shape or form but I have done enough to know what can break my device and what cant, a while back I successfully ported a rom to a cheap Chinese tablet I owned a while back, I am going to look into porting a (hopefully) lollipop rom to our VK810, gonna take me some time and who knows if I will even be successful, just wanted to let everyone know someone is trying..... I will let you know if I make any progress....

Prepare your bounties guys !
Development is in full swing. We'd see some love for developers in coming weeks !

Custom ROMs?

I have been waiting a while to post this because posts like this always get killed, but for a phone with a factory-available bootloader unlock, I am surprised we don't have a modded stock ROM to try out yet. TruPure on the Moto x Pure was awesome, although it altered very little. I know CM is being worked on but given some of the responses in that thread, it could be quite a while.
So aside from that observation, is anyone actively working on something like that and if so, can you post here and let us know how things are coming along? I know we all would be appreciative of the effort.

They're waiting on a full image of the ROM to be released, with all the img, radio, ect.. and other files needed to make it work. Once that drops form ZTE, it's on like some 80s video game reference.

tele_jas said:
They're waiting on a full image of the ROM to be released, with all the img, radio, ect.. and other files needed to make it work. Once that drops form ZTE, it's on like some 80s video game reference.
Click to expand...
Click to collapse
Noob question: Cannot these be taken from images that were extracted from the phone already? Does rom provide that much more?
This is a genuine question, isn't rom just a packed and zipped version of what is on the phone?

mhodak said:
Noob question: Cannot these be taken from images that were extracted from the phone already? Does rom provide that much more?
This is a genuine question, isn't rom just a packed and zipped version of what is on the phone?
Click to expand...
Click to collapse
I was pretty sure that once we got root and bootloader access that this could be done just as you said here. No need for drivers or proprietary anything...although the camera API will be a problem, but I think it's possible right now. I was just wondering why no one has the desire to attempt it. Did the weird release and shipping debacle for the grey phones really make everyone avoid the phone and hamper dev this much? Sort of disappointing if that is the case.

xgerryx said:
I was pretty sure that once we got root and bootloader access that this could be done just as you said here. No need for drivers or proprietary anything...although the camera API will be a problem, but I think it's possible right now. I was just wondering why no one has the desire to attempt it. Did the weird release and shipping debacle for the grey phones really make everyone avoid the phone and hamper dev this much? Sort of disappointing if that is the case.
Click to expand...
Click to collapse
This worries me as well. It appears that there is only one person actively working on a custom ROM. Although things can pick up later, this does not bode well for the future.

mhodak said:
This worries me as well. It appears that there is only one person actively working on a custom ROM. Although things can pick up later, this does not bode well for the future.
Click to expand...
Click to collapse
My thoughts are differently, base on the many issues people are running when trying to get back to stock and the fact they there's 2 B20 versions around (B20 Stock & B20_boot) make things a Little harder to do, like for sample,
I have the B20_boot version and as you can see I uploaded a backup with Xposed debloated and Rooted (I can consider that backup/ Custom ROM) but stock B20 can't use that backup as far as I know... I can easily release a flash able zip base on my backup but (Xposed,Debloated,rooted) but I bet only 5% of the user are using b20_boot.
So till find a way or just way till ZTE release a firmware image we are going to be little stuck with just CM which is getting more stable every day/week

xgerryx said:
I have been waiting a while to post this because posts like this always get killed, but for a phone with a factory-available bootloader unlock, I am surprised we don't have a modded stock ROM to try out yet. TruPure on the Moto x Pure was awesome, although it altered very little. I know CM is being worked on but given some of the responses in that thread, it could be quite a while.
So aside from that observation, is anyone actively working on something like that and if so, can you post here and let us know how things are coming along? I know we all would be appreciative of the effort.
Click to expand...
Click to collapse
First, the Moto X Pure was widely available. It was not shipped out in smaller batches once a month. When it was released, it was available for everyone to purchase. For the Axon 7, the first batch and second small batches of phones sold out during pre-order, and the third batch hasn't even shipped yet. (and it hasn't received a wide release in Europe yet either, think they just had one small batch)
Also, the Moto X Pure had bootloader unlock available at launch. The Axon 7 did not get a bootloader unlock method until August 11th, less than a month ago. (and at this time, there is no bootloader unlock for the European or Chinese models, just the North American model)
And just as a reminder, the Moto X Pure launched in early September. Dev for CM12.1 started in late September. The first custom ROM, an alpha of CM12.1, was released a month later, in the beginning of October.