Database Users

Can I remove all of Sense UI?

Hey guys, sorry for the n00b question, but after searching briefly, I couldn't find it anywhere else on the Hero forums. I am running Damageless non-expresso, and I wanted to know: Is there a way for me to remove ALL of sense ui? If HTC made it, I don't want it. I know, I know, should have gotten the moment, but I don't trust hardware keyboards after 3 terrible experiences with the Touch Pro. I have already found out how to get rid of Sense UI, but the thread said that it left "the HTC Dialer and HTC Customizations." I just want stock android 2.1 with the .29 kernel. What can I do? Is there another ROM I can get instead? Thanks.

Get Darch's AOSP ROM. I don't know if it has the latest kernel yet, but it is Sense-free.

Thanks, but...
TheBiles said:
Get Darch's AOSP ROM. I don't know if it has the latest kernel yet, but it is Sense-free.
Click to expand...
Click to collapse
Is there then a way for me to update the ROM to get the Camera working?

USAF22 said:
Is there then a way for me to update the ROM to get the Camera working?
Click to expand...
Click to collapse
I think darch ran into some problems with the .29 kernel. either wait for him to give it a shot or take a stab at getting it going. Stripping sense out of a Rom would be a total pain to do at best.

Okay.
Thanks for the help and info. Will do.

Who will give the first ROM

As the title states.. at this moment there is absolutely no reason why we dont have custom roms floating around for our devices yet, other then the fact that noone has taken the time to make one
We have a fully functional recovery from koush as far as pushing custom roms go.. we also have a fully functional froyo base to work with as well as a froyo .32 kernal.. nothing is stopping us at this point other then the fact that noones done one yet
Whos going to be the first to throw one out there?
Whoever it is, please remove all the bloat... Deodex all the system files for easy theming and try to zipalign and optimize however you can

This thread is absolutely useless, not to mention in the wrong section.

anybody can post it. But why sud be Start to Speculate or Gamble. When it will be available it will be like we got Froyo 2.2 stock image

Joe92T said:
As the title states.. at this moment there is absolutely no reason why we dont have custom roms floating around for our devices yet, other then the fact that noone has taken the time to make one
We have a fully functional recovery from koush as far as pushing custom roms go.. we also have a fully functional froyo base to work with as well as a froyo .32 kernal.. nothing is stopping us at this point other then the fact that noones done one yet
Whos going to be the first to throw one out there?
Whoever it is, please remove all the bloat... Deodex all the system files for easy theming and try to zipalign and optimize however you can
Click to expand...
Click to collapse
if your phone has root you can remove all the bloat you want and install whatever you want. you should get started with root explorer

Make your own F***ing rom then if you dont feel like waiting for somone to make one. Anyway I bet there is many people working on roms right for the droid x

So many smartasses. How about you guys lay off and get a life, the guy was just asking a question.

I agree with the OP, right around the time that koush released his recovery there were a bunch of people talking about coming out with froyo roms (birdman and rainabba namely)but without the froyo kernel, then the leaked froyo came out and nothing ever happened since.
Now we have a froyo kernel to work with, we just need a stock android build without any oem customization.

Bootloader still locked?
Sent from my DROIDX using Tapatalk

I dont feel like we really need a new rom, whats it gonna do for me? It will either be 2.1 or the 2.2 leak with different themes/different apps, something I could and would rather do myself.
Outside of theming, I dont see the point.

LegionTHEFecalExcretion said:
I dont feel like we really need a new rom, whats it gonna do for me? It will either be 2.1 or the 2.2 leak with different themes/different apps, something I could and would rather do myself.
Outside of theming, I dont see the point.
Click to expand...
Click to collapse
There is definately benefits to be had as far as performance goes as well.. cleaning up the froyo build and optimizing / zipaligning the apks will get things going well, and as you said as far as theming goes, a completely deodexed rom will allow complete themes from A to Z not just status bar things, could even put a new lockscreen in place that may not have any crazy lag

I could see an industrious dev cleaning up the froyo build a little, but I have had almost zero issues with this build, outside of a build.prop change. We will see one soon I am sure, hell, Im just glad we finally have a custom recovery.

LegionTHEFecalExcretion said:
I could see an industrious dev cleaning up the froyo build a little, but I have had almost zero issues with this build, outside of a build.prop change. We will see one soon I am sure, hell, Im just glad we finally have a custom recovery.
Click to expand...
Click to collapse
Yeah i just find it humerous that everyone was complaining we dont have a custom recovery and the world is goin to end, and im not going to buy a Droid X because the bootloader is locked etc etc yada yada... but then when we actually get rom flashing capabilities, noone even uses it lol

Isn't the bootloader for the Droid X still locked? IE no custom roms?
Sent from my Cyanogen Froyo using XDA App

They found a way around it, custom roms are doable now, just noones made one
Sent from my DROIDX using XDA App

So, maybe this would be better asked in another thread, but how would I go about pulling the recovery image in order to customize it? I'm simply assuming that's how it's done, so if not, let me know. I would like to start messing with making some roms, but have no clue where to start as it seems to be all device-centric. Where does one learn all of this?

Joe92T said:
They found a way around it, custom roms are doable now, just noones made one
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
I don't understand how it's doable with a locked bootloader? If someone created a clean froyo rom how would it boot? Wouldn't that be similar to removing all the apk's from the leaked rom and expecting it to boot?
Please tell me if I'm wrong...

bart77 said:
I don't understand how it's doable with a locked bootloader? If someone created a clean froyo rom how would it boot? Wouldn't that be similar to removing all the apk's from the leaked rom and expecting it to boot?
Please tell me if I'm wrong...
Click to expand...
Click to collapse
We can do custom roms, but have to include and not modify the stock kernel. So, no modular overclocking I believe.
Basically, the first roms to come out will be de blur'd so to speak, and then AOSP roms will hit later. Promise Just a matter of time.
The original lockdown of the bootloader and "efuse" scared a lot of dev's off of getting the X. I only know a handful of people deving for the X, so I assume this is why customs roms are taking a while to come out.
Regardless, they'll be here soon enough. Patience

Im getting the x soon, and maybe i can whip up a rom
Sent from my ADR6300 using XDA App

Someone correct me if I am wrong, but isn't Koush's recovery for 2.1? Will it work on 2.2?

Steeleio said:
Someone correct me if I am wrong, but isn't Koush's recovery for 2.1? Will it work on 2.2?
Click to expand...
Click to collapse
Unless the 2.2 out isnt root friendly, it should work, but then again, i dont have an x
Sent from my ADR6300 using XDA App

android 2.3 hacked evo rom on a dhd

I noticed that the guys in the evo section have a dev/test only 2.3 rom compiled from reverse engineering off the 2.3 sdk. They have already got most of the functions to work, all a bit buggy but cool all the same. I was wondering if I were to flash a evo rom onto my DHD and it didnt work would I still be able to use clockworkmod and reflash my nand backup off sc card?
Or am I just crazy to even think of trying?

alphabuilders said:
I noticed that the guys in the evo section have a dev/test only 2.3 rom compiled from reverse engineering off the 2.3 sdk. They have already got most of the functions to work, all a bit buggy but cool all the same. I was wondering if I were to flash a evo rom onto my DHD and it didnt work would I still be able to use clockworkmod and reflash my nand backup off sc card?
Or am I just crazy to even think of trying?
Click to expand...
Click to collapse
I also noticed while rooting/updating my mates Sony Ericsson X10 that there is a sdk dump of 2.3 available. Doesnt really work but still nice to check it out
Anyone willing to do a sdk dump or point me in the direction of how to do it

Ok i attempted to flash the evo 2.3 rom on my DHD.
Didnt work, guess it is because wrong kernal.
Am I the only person who would like to see a skd port of 2.3?
Just to check out, obviously would not run well enough to use as daily rom.
If any1 can point me in the right direction I would love to learn how to port/compile over from a sdk.

I'm as eager as you are! I want a tasty gingerbread
But i'd suggest you wait until a rom is released SPECIFICALLY for your phone...jumping ahead can result in great losses...i'm sure you don't want a £450 paperweight
And trust me, time will fly, before you know it some smart XDA Chef will have released an optimised rom just for our shiny Desire HDs!

alphabuilders said:
Ok i attempted to flash the evo 2.3 rom on my DHD.
Didnt work, guess it is because wrong kernal.
Am I the only person who would like to see a skd port of 2.3?
Just to check out, obviously would not run well enough to use as daily rom.
If any1 can point me in the right direction I would love to learn how to port/compile over from a sdk.
Click to expand...
Click to collapse
I strongly suggest that you don't do this roms must be device specific
Sent from my Desire HD using XDA App

Common Misconceptions About the DX.

So after seeing many things that is said with the DX I thought I should write a post like this. This is just to clear up confusion so users can have the knowledge to use in the future.
Every ROM for the DX is AOSP
I have seen this said many times and it bugs me that people think that all ROMs are AOSP. As of now, there are actually only a few AOSP ROMs for the DX, cvpcs' Tanzanite/Obsidian, Cobalt, and blackdroid's Ultimate Droid. Other ROMs like rubiX, Liberty, ApeX, and Fission are basically Motorola ROMs with the blur applications replaced with AOSP applications. Now this does not actually make it AOSP. It has features from AOSP, but there is much more to it than the applications. These blur-based ROMs actually have other AOSP-like features, such as lock screen music controls and a few others. Now that also doesn't make it AOSP, those are just a few features that were originally modifications to AOSP to add more functionality to a ROM. That doesn't mean these ROMs are bad in any way. They are actually very good. The only downfall of them is the fact that they are limited to what can be done.
There can't be AOSP ROMs without a custom kernel.
Another statement I have been told or have seen several times. It is considered AOSP if it comes from Google's source. A kernel won't affect the fact that it was built from source. Although it would be ideal for a custom kernel with AOSP, it isn't needed.
A custom kernel is needed.
This is another incorrect statement. It would be nice to replace the kernel, but it isn't needed. The kernel that is provided to us from Motorola includes basically everything the end user would need. Also there is overclocking(although it isn't the easiest implementation) by adding a temporary module to the kernel that is erased after the phone is powered off.
Gingerbread won't come to the DX until Motorola releases a new kernel with their Gingerbread update.
Incorrect. What the original concern was that Gingerbread would not boot with a .32 kernel(the kernel the DX has.) and that it needs a .35 kernel. This was later proven wrong with D1. The D1 has been running Gingerbread for a bit now with a .32 kernel. Now I know people will say it is is a different kernel or something along those lines, but that doesn't matter. Gingerbread will boot on it without needing to replace the current kernel.

this is something that should be posted on every forum about the DX. Great info

Would getting building GB on the DX give us the new garbage collector too? I'm so tired of waiting for memory to clear after PewPew (makes a TON of objects).

Trongable said:
Would getting building GB on the DX give us the new garbage collector too? I'm so tired of waiting for memory to clear after PewPew (makes a TON of objects).
Click to expand...
Click to collapse
Don't think GB would do anything different with it.

Moved and stuck. Thanks Matt! Please add info as it strikes you, this could be really helpful to the newer folks.

I feel like this info is either wrong or irrelevent.
I'm leaning towards irrelevent. Why don't we have Gingerbread yet if it's possible? I feel like you are saying technically we can have 2.3 w/ the X's current kernel, but it looks like realistically we will never see 2.3 until Moto steps up.
edit: I was mainly referring to your last point

sciulli999 said:
I feel like this info is either wrong or irrelevent.
I'm leaning towards irrelevent. Why don't we have Gingerbread yet if it's possible? I feel like you are saying technically we can have 2.3 w/ the X's current kernel, but it looks like realistically we will never see 2.3 until Moto steps up.
edit: I was mainly referring to your last point
Click to expand...
Click to collapse
First off, please don't bash on the devs that work so hard to give us new material for a phone that everyone expected to be impossible to do anything on...
2nd, gingerbread is possible, but you can't just take a release (even when possible) and dump it on a phone. It needs to be recompiled with the appropriate modifications to allow it to work on the X's hardware. Droid2169 is currently working on this, and has made some progress, he is working out usb drivers/connectivity I believe.
I understand waiting can be frustrating, but please don't bash on the devs who help us out.

thanks for the info

misconceptions
misconception?---do i really need to "deodex" my droid x before flashing a custom rom? i was under the impression that installing a custom rom would deodex the phone, and deodexing only has to be done manually before theming.

ernesttatum said:
misconception?---do i really need to "deodex" my droid x before flashing a custom rom? i was under the impression that installing a custom rom would deodex the phone, and deodexing only has to be done manually before theming.
Click to expand...
Click to collapse
Odexing is a process that optimizes the java code. most carrier roms are odexed. It is possible to de-odex a rom. also, if you build an aosp rom, it is not odexed, but can be if you wish.
you cannot apply a theme to an odexed rom.
Definitely something that applies to the rom, not the phone.
Sent from my Incredible using XDA Premium App

Your kernel statement seems wrong. If the current Moto ROM has kernel # 1.2, but the newest version of Google's AOSP rom is kernel #1.4, there is no way for us to update to the newest AOSP kernel. Sure we can update the apps and whatnot from the newest version, but strictly speaking without the same kernel it is not AOSP.
Also I dunno where you get the idea that everyone think all DX roms are AOSP. If it has any sort of blur, it's not and many roms do.

aldo37 said:
Your kernel statement seems wrong. If the current Moto ROM has kernel # 1.2, but the newest version of Google's AOSP rom is kernel #1.4, there is no way for us to update to the newest AOSP kernel. Sure we can update the apps and whatnot from the newest version, but strictly speaking without the same kernel it is not AOSP..
Click to expand...
Click to collapse
The best example of this is probably coming up soon. If Netflix's app require's DRM api calls that are only supported in the 2.3+ kernels then you are SOL if you can't mess with your kernel. You lose features and any kernel fixes/optimizations.

new to the defy.

I'm by no means a rookie when it comes to android. But this phone confuses the hell out of me. I read the all in one defy guide, and it helped. However, I want to run ics, especially with jb having certain features broken that I use. I don't have the phone yet as its in the mail and I'm compiling everything to root and rom.
So my question is, what sbf rom file should I rsd to run cm9? I also have a new defy+ battery coming, would this battery cause the battery % drop thats heavily discussed here.
Sent from my SGH-T989

davwman said:
I'm by no means a rookie when it comes to android. But this phone confuses the hell out of me. I read the all in one defy guide, and it helped. However, I want to run ics, especially with jb having certain features broken that I use. I don't have the phone yet as its in the mail and I'm compiling everything to root and rom.
So my question is, what sbf rom file should I rsd to run cm9? I also have a new defy+ battery coming, would this battery cause the battery % drop thats heavily discussed here.
Sent from my SGH-T989
Click to expand...
Click to collapse
I've got an actual DEFY+ (MB526) and I've never had battery drops on any ROM's (tested more than 10 ROM's). I've read a lot about people with MB525's who bought DEFY+ battery and only had problems with it... Don't take my word for it, though and I hope it works out for you fine. Problems, like, it wouldn't charge to 100%. Don't know, Gingerbread kernel and a DEFY+ battd should be enough to make it work...should be
SBF ROM is not the way I would suggest, really... Messing with SBF's is not the smartest call.
What have you got? A DEFY on Froyo? Or Eclair? You should update to Froyo and then root using SuperOneClick and install 2ndInit (the installer is in the Themes&Apps subforum) and go ahead and flash any ROM in the custom recovery.
And may I ask what features does JB have broken compared to ICS? WiFi tethering doesn't work on ICS and does on JB, for a contrary example, though.
Cheers, mate! And welcome to the DEFY lot

That actually clarified a lot. Thanks. Not sure what is on the defy yet. Waiting for its arrival. The way you worded the process made this phone easier to understand as its just like every other moto phone out there.
Sent from my SGH-T989

I guess ill be running on the froyo kernel then with any rom i flash, correct? Also what jb rom would you suggest? It was my understanding that video recording didn't work.
Sent from my SGH-T989

davwman said:
I guess ill be running on the froyo kernel then with any rom i flash, correct? Also what jb rom would you suggest? It was my understanding that video recording didn't work.
Click to expand...
Click to collapse
"Which ROM is best" type threads are not allowed on XDA because of the controversy and arguments that question inevitably generates. As it seems like your other questions have already been answered, I'm closing this thread to avoid that type of discussion.