breaking DX news

[dvader]

the issue here first is this ******* lied to the whole community played everyone for a fool knowing full well how many people wanted this and how badly they did.

2nd. all these great roms you guys are talking about, are going to go away soon.
fab has already said he's not likely going to do any more dev on apex.
all the rest of the dev's are getting the tbolt and /or getting tired of deving for the dx.
liberty is great and all, but it doesn't 100% support the phone.
the dialer sux, there is no hdmi.. etc.
so our choices are thin and getting thinner.

if the the bootloader was unlocked more dev's would work on the phone and we would have CM which is constantly being worked on. unlikely to go away any time soon.

 

[tntdroid]

A guy working on cm has it booting on his x. Just needs to work out some bugs. It may not be 100% really cm but close to it and he will continue Support on it. That is a big plus and gives us something new to try.

Follow @cvpcs for more info on this.

Sent from my DROIDX using Tapatalk

 

[digitalslacker]

I've ran Cyanogen on several phones, most recently a HTC Incredible, and I'm in the same boat with you and fail to see the fuss. The fervor for CM kinda reminds me of the D1 devs who would try to explain ad nauseam that the Pete's (Bugless Beast) hacks are the same hacks that everyone else is using. However, they couldn't' sway the crowd. They were convinced that Pete's ROM was the only true path to salvation. CM does have its perks, most notably the fact that its based off of Gingerbread. There isn't anything going on in CM that Liberty Toolbox doesn't accomplish. but I digress...

I have yet to hear anyone tell me one advantage of hacking a kernel that didnt involve correcting some huge omission or **** up made by the manufacturer. Thankfully, the DX is a pretty bad ass phone - hardware wise. Its the software that needs work. Which is why I would have been anxious to see MIUI on the Droid X. Now THAT, is one bad ass ROM. Its so much more than an extension of stock features, its like an entirely different experience, much like Sense UI is - sans the awful battery life that is associated with them.

If I'm missing something, I'd love to hear it. I would love to hear an explanation that doesn't involve chirping about the amount of people who use it, its popularity, blah blah blah because that only proves my point that its acceptance is just a huge popularity contest.

My understanding is it's very much a situation where we don't exactly know what it is we're missing because we (ok, devs smarter than me) haven't had the opportunity to dive in and see what is possible.

In the case of the gTab that I referenced earlier there are several features enabled by way of a custom kernel that aren't available stock. Stuff like NTFS support, IPv6, governors, EXT4 and more.
Here is a list [Kernel] 2.6.32.33 - VFPv3_FP - Gtab/Zpad - xda-developers

We lucked out with the DX because many great devs found awesome work arounds for much of what is typically done with a kernel, like OCing or being able to flash recovery via bootstrapping. That's stuff just works when the bootloader is unlocked.

Tech is always about pushing limits and innovating. Open > Closed. That won't always equate to results you want or care about...but if its closed then you'll never know what you are missing...

Hope that helps, I'm probably a little of a purist when it comes to this stuff but, I completely understand your position. I was in agreement with it before I got the gTab.

 

[jerseyboy357]

It seems he is still miles away, but he's less miles away than he was yesterday, so I would call that anticipated progress. It is odd how it would only boot on his phone. I do think less devs will be working on the X, but will still be working on the X for some time AND if @cvpcs does succeed to standard, it will open the X world once again for some time. Just think at the sheer number of people that are willing to try CM7 on the X.

 

[Bushido Brown]

My understanding is it's very much a situation where we don't exactly know what it is we're missing because we (ok, devs smarter than me) haven't had the opportunity to dive in and see what is possible.

In the case of the gTab that I referenced earlier there are several features enabled by way of a custom kernel that aren't available stock. Stuff like NTFS support, IPv6, governors, EXT4 and more.
Here is a list [Kernel] 2.6.32.33 - VFPv3_FP - Gtab/Zpad - xda-developers

We lucked out with the DX because many great devs found awesome work arounds for much of what is typically done with a kernel, like OCing or being able to flash recovery via bootstrapping. That's stuff just works when the bootloader is unlocked.

Tech is always about pushing limits and innovating. Open > Closed. That won't always equate to results you want or care about...but if its closed then you'll never know what you are missing...

Hope that helps, I'm probably a little of a purist when it comes to this stuff but, I completely understand your position. I was in agreement with it before I got the gTab.

The EXT4 hack is a perfect example of what I'm talking about. It's used to fix whatever god awful read/write system that makes all of the Galaxy S devices I/O so slow. NTFS and IPv6? Why do I care about that on a mobile phone/device?

As far as I can tell, Motorola doesn't use some wonky file system that screws with the I/O portion of the device, it doesn't need a workaround for notification lights, it didn't have a 30fps cap, it doesn't need a hack to support the FM radio hardware it has, it doesn't need it's charging algorithm corrected to avoid having to top off, or various other tweaks to get an extra hour out of the EVO or the Incredible.

Those are the majority of the hacks I see from various kernel mods over the past year or so. How is any of that useful to the Droid X? I'm the type that needs no WHY something is supposedly useful. Just saying it is, or saying other people use it isn't enough for me.

 

[.46caliber]

The EXT4 hack is a perfect example of what I'm talking about. It's used to fix whatever god awful read/write system that makes all of the Galaxy S devices I/O so slow. NTFS and IPv6? Why do I care about that on a mobile phone/device?

As far as I can tell, Motorola doesn't use some wonky file system that screws with the I/O portion of the device, it doesn't need a workaround for notification lights, it didn't have a 30fps cap, it doesn't need a hack to support the FM radio hardware it has, it doesn't need it's charging algorithm corrected to avoid having to top off, or various other tweaks to get an extra hour out of the EVO or the Incredible.

Those are the majority of the hacks I see from various kernel mods over the past year or so. How is any of that useful to the Droid X? I'm the type that needs no WHY something is supposedly useful. Just saying it is, or saying other people use it isn't enough for me.

The kernels built for the Droid allowed for doubling the clock speed while getting improved battery life over stock. I'd love a 2 GHz Droid X that gets even better battery life than what I have now.

 

[Bushido Brown]

I never got a chance to use those kernels you're referring to, but the ones I did use turned my phone into a hotplate when it was clocked above 1 gig. I have no idea how a kernel can improve battery life while ramping up the voltage high enough to create a 1.2GHZ cycle on a 65nm chip.

 

[.46caliber]

I never got a chance to use those kernels you're referring to, but the ones I did use turned my phone into a hotplate when it was clocked above 1 gig. I have no idea how a kernel can improve battery life while ramping up the voltage high enough to create a 1.2GHZ cycle on a 65nm chip.

I'm currently using a Chevy No. 1 kernel for my Droid running CM7 nightlies. 1.2GHz ultra low voltage. The kernel underclocks idle down to 250 MHz, and voltage has been greatly reduced across the clock speed slots. It never gets significantly warm unless I run something like Quadrant a few times in a row.

Doing amazing things with kernels is what guys like p3, slayher and Chevy No. 1 are known for. I couldn't tell you exactly how they build the kernel to get both amazing performance and battery life. For all I know, they could be sprinkling magical dust on their keyboards when building them, but I'm sure they could answer your questions. Chevy No. 1 has set up shop on the DroidForums if you want to ask how it can be done.

 

[.46caliber]

I should add, just because the Droid was able to be overclocked to the extent that it was, doesn't mean the DX would be the same way. What bothers me most is that unfortunately, we may not ever know exactly what the DX hardware is capable of. I'm really hoping that the guys pursuing the kexec path find a way.

 

[digitalslacker]

Those are the majority of the hacks I see from various kernel mods over the past year or so. How is any of that useful to the Droid X? I'm the type that needs no WHY something is supposedly useful. Just saying it is, or saying other people use it isn't enough for me.

If the DX's bootloader was unlocked then we would know all the answers to "WHY" its worth it or not. Right now though we don' t know for sure what is possible or what the limits are to those possibilities. We're drawing comparisons about what's possible on other phones and devices. That may or may not be accurate.

Let's be honest here though, many of the reasons we're pointing out are just attempts to justify why the bootloader should be unlocked by pointing out what we could be missing. In reality, most of us just want it unlocked because we believe that it should be. We bought these devices and we should be able to work with them without any limitations. It's like buying a car and then being told you can't rip it apart and rebuild it your way. Some people just have a fundamental issue with that, me included.

Truthfully, I'm not sure having the bootloader unlocked at this point would really get us a whole lot that we don't already have which is probably why it hasn't happened.

 

[Ricky Babalu]

Any chance we could see a Motorola insider leak the key? Kind of like a "Wikileaks" for the Mobile community.

 

[Bald Steve]

...Which is why I would have been anxious to see MIUI on the Droid X. Now THAT, is one bad ass ROM. Its so much more than an extension of stock features, its like an entirely different experience, much like Sense UI is - sans the awful battery life that is associated with them.

You aren't kidding, man. I just did some research and wow - that MIUI is sick.

 

[.46caliber]

Any chance we could see a Motorola insider leak the key? Kind of like a "Wikileaks" for the Mobile community.

Only if someone wants to get themselves fired from Moto. But, bigger than that, there may be a confidentiality agreement involved with those that are privy to that info that could hold much larger penalties than a termination of employment. But one can hope, right?

 

[Bushido Brown]

I should add, just because the Droid was able to be overclocked to the extent that it was, doesn't mean the DX would be the same way. What bothers me most is that unfortunately, we may not ever know exactly what the DX hardware is capable of. I'm really hoping that the guys pursuing the kexec path find a way.

I've ran their stuff before. I was thinking you were talking about something that came out after I sold my Droid back in August last year. Anyway, over/under clocking speed and voltage has already been done on the Droid X. So access to the kernel isn't necessary anyway.

Its hard enough to get a phone to run stable at stock speed with the kernel undervolted, let alone at what, + 120%? - AND improve battery life in the process? That just doesn't make any sense. I've ran the same hacks you have, 1GB or higher your phone cooked, and your battery strained. That's why I got the Droid 2, otherwise there wouldn't have been much reason to upgrade.

 

[.46caliber]

I've ran their stuff before. I was thinking you were talking about something that came out after I sold my Droid back in August last year. Anyway, over/under clocking speed and voltage has already been done on the Droid X. So access to the kernel isn't necessary anyway.

Its hard enough to get a phone to run stable at stock speed with the kernel undervolted, let alone at what, + 120%? - AND improve battery life in the process? That just doesn't make any sense. I've ran the same hacks you have, 1GB or higher your phone cooked, and your battery strained. That's why I got the Droid 2, otherwise there wouldn't have been much reason to upgrade.

The clocking and volting done on the DX and D2 is a tack-on. It's not a totally rebuilt kernel. We don't know what the DX or D2 could do with a re-built kernel.

I don't know how they do it, but my phone does not get hot with Chevy's 1.2GHz ULV and I do get great battery with it. Maybe I'm not as heavy as a user, all I know is what I've seen done with the device and the kernels I've tried.

 

[Ahowe125]

I have been using Jrummy16's Droid X Overclock, and today I tried the ULV 1.3ghz overclock, and I have not had a single error, hitch, or issue. and its battery life has been better then normal. Now I don't have any real proof thats its been better, but I know that I had more battery left at the end of a normal work day. And I haven't seen the battery temp above 85 at any point.

With results like that, who needs a custom kernel.

 

[Bushido Brown]

Changing the slots and voltage is changing the slots, and voltage. There is no difference. The only advantage is that it can't get overwritten from other scripts, or a reboot like the DX's current method(s).

I think you may have fallen victim to the placebo monster.