Database Users

Porting Sense to Vibrant?

Is this possible?

As of right now I think the development are worrying about getting a recovery on our phones and we need the recovery to flash roms unless there's another way...

Not only that but sense is a cpu hog. Such a horrible UI.

CM6 is all I care about getting on here. FB/Twitter integration all exists in 2.1, Sense adds little other than pretty looking widgets.

Isn't cm6 2.2??
Sent from my T-Mobile G1 using XDA App

robavila721 said:
Isn't cm6 2.2??
Sent from my T-Mobile G1 using XDA App
Click to expand...
Click to collapse
Yes, I was just referring to the fact that we havent needed Sense UI for anything but pretty widgets since Android SDK 2.1

Why would you want Sense over TouchWiz? If you we're looking for pretty there are lots of HTC Sense packing HTC phones on the market. The myTouch Slide is kind of running an ugly version of Sense but it still is Sense.

One more thing to consider, also. You won't find any reputable developer such as Cyanogen putting sense in their roms because of legality issues. So, if you do happen to come across a rom for this phone running sense, chances are its going to be pretty bunk.

Sense has some very appealing factors, such as the hibernate support and of course, the cosmetics of it
In addition, the new version of HTC sense is supposed to have a lot of optimizations meaning it will be faster than before.
At the very least, is it possible for a dev to port the algorithms used for hibernate to the Vibrant?

Use this. its not sense but its a launcher close to it. has 3d drawer and everything.

sombionix said:
One more thing to consider, also. You won't find any reputable developer such as Cyanogen putting sense in their roms because of legality issues. So, if you do happen to come across a rom for this phone running sense, chances are its going to be pretty bunk.
Click to expand...
Click to collapse
but there are many more reputable developers then CM

kingkurry said:
Is this possible?
Click to expand...
Click to collapse
Possible? perhaps...
Desireable? perhaps not...
Likely? Given the legal issues involved? not very...

I am also interested in this.. But to be honest if it where to happen, it won't happen until the developers get the source code for 2.2 and haber time to play with it.
So, if we are lucky and someone does decide to work on this.. knowing the possible legal issues. It would take a few weeks (after official 2.2) to get it done.
But I have no doubt in my mind that it would work in our phones.
Sent from my SGH-T959 using XDA App

KingKlik(sp?) made a lot of sense roms for the MT3G and a lot of people seemed to like them. I just think Sense looks terrible, compared to any UI on any new age smartphone I have seen(except maybe Windows Mobile). I'm mainly talking about the launcher tough, the part that people for some reason like to throw on their phone even if they don't have sense.

new rom

Are we going to see any new roms for the aria or no...
Sent from my HTC Liberty using XDA App

what do you mean by new roms?

We have 4 well made roms already, stock 2.1, liberated 2.1, liberated 2.2, and cm6. If you want to re-roll the stock rom 100 different ways that are all nearly exactly the same like some other phones, go right ahead.

I look forward to the new rom you are going to develop and can't wait to try it out!
g4ess said:
Are we going to see any new roms for the aria or no...
Sent from my HTC Liberty using XDA App
Click to expand...
Click to collapse

Language edit

It really doesnt get any better than what we already have available! In this case quality is far superior to quantity. And less confusion this way as well having less of the same thing being re-made.

thanks to all the people that made since i appricate it.. to the other fools that just wanted to come here just to type cause u are bored kick rock u lames.. i asked the question 1 maybe i am not a phone geek like u and 2 i am trying to learn.. i wasnt being smart...

It's a legit question.
People coming from other phones (WM especially) might expect 2 dozen different ROMs. The fact is, we have 4 great base ROMs, and Android's ability to customize them however you want, without needing a ton of expertise. We don't have to wait around for a select few people to cook up new updates for us.
Although, I really wouldn't be opposed to some people creating some dedicated theme ROMs.

Moved to general as this is not development.

Thats what i meant a fully theme rom.. i had a mytouch n windows mobile in the pass n i no people made more themed n customizable roms.. thank u guys..
posted via htc aria xda app..

As far as roms go - i dont think we need any more base roms - but maybe some decent themes for the Aria.

I like how polished (but few) options we have for aria. If you've ever wandered over to Nexus One development forum you will see rom overload. How would I even know where to start? With the aria it's simple, yet we have very polished options. Got to give props to attn1.

Cyanogen mod for dummies

I did my homework, and have come up mostly empty. Read what I could find on the CM site; wikipedia; blogs; newsgroups; and a lot more. Probably at least 2 hours trying to get a comparative handle on CM vs. stock release derived ROMs.
After all that, I'm only a tiny bit closer to understanding what I gain, and what I give up, going to CM.
If there if a good, detailed articulation of this somewhere, please help us CM noobs with a pointer; Otherwise, I'd like to start a thread to capture as much detailed information about comparing CM to stock-based ROMs so people can make informed choices.
Sent from my mind using telepathitalk

http://wiki.cyanogenmod.com/index.php?title=What_is_CyanogenMod

Thanks, that's a start, but in truth it's information like that that prompted my starting this thread.
That's generic information. Only moderately helpful in judging specifically for the Epic whether I should go CM, or with another custom ROM.
For example, info like this: CM does not include the accelerated Samsung video player, and doesn't handle many video formats and codings well in comparison. So, if playing h264 coded video in mkv containers is important to you, CM will be a challenge, where Bonsai, ACS, Midnight, etc. will be a much simpler choice to meet your needs.
Sent from my mind using telepathitalk

Think about it like this. If you buy a PC from a big company (HP, Dell, etc) it comes with a fully functional install of software. Windows + drivers + all other crap they decide you should have. That is equivalent to the Samsung ROM that comes stock on Epic.
What if you build your own PC from components? You will install Windows, then you will dig up the drivers you need separately, and then load your own applications.
Android AOSP in this comparison is the "base" install of Windows. Nothing else added in.
The drivers and other changes required to make the base Android work with your hardware is CyanogenMod.
So basically, Samsung based roms will have all the functioning drivers and everything else in them. Dev's tear them apart and remove/change what they don't want, but don't have to worry much about hardware cause the drivers are straight from Samsung.
AOSP based roms (CyanogenMod) will be utterly broken and have no hardware support at first. Developers have to write real lines of code into the software to make it support the Epic or any other phone. The are built from the ground up. That is why it is so amazing what Team CM7 has already got working in so little time!

Again, thanks for the sincere attempts to answer this qualitatively. However, that's not the issue. See my example above.
What you describe above with the custom PC example, while true, isn't informative enough for most people to make an informed decision.
Knowing that CM is free of carrier bloatware doesn't help me understand in any way that the video player with CM had some important limitations when compared to the optimized video player Samsung includes. For some people, this may be a critical issue in making a decision.
It is those sort of specific differences that I thought would be helpful to enumerate and capture. Of course anyone can simply install the ROM and discover for themselves... Judging by my own struggle to find enough information to make an informed choice myself, I thought others might benefit from nailing this stuff down.
So far, it looks like I may have been mistaken?
Sent from my mind using telepathitalk

dwallersv said:
Again, thanks for the sincere attempts to answer this qualitatively. However, that's not the issue. See my example above.
What you describe above with the custom PC example, while true, isn't informative enough for most people to make an informed decision.
Knowing that CM is free of carrier bloatware doesn't help me understand in any way that the video player with CM had some important limitations when compared to the optimized video player Samsung includes. For some people, this may be a critical issue in making a decision.
It is those sort of specific differences that I thought would be helpful to enumerate and capture. Of course anyone can simply install the ROM and discover for themselves... Judging by my own struggle to find enough information to make an informed choice myself, I thought others might benefit from nailing this stuff down.
So far, it looks like I may have been mistaken?
Sent from my mind using telepathitalk
Click to expand...
Click to collapse
So, you're looking for a more hand held description of what CM7 doesn't have?
....

Sent from my SPH-D700 using XDA App

I can give you the best piece of advice....
This is a development site, not a front end rom publishing site..
If there's not already documentation, test the differences yourself, and report the findings for the next gentleman who comes along with your same questions...
Then before too long you're not a "noob" anymore..
But to answer your question, cyanogen is a more bare bones android experience.. it is built off of the AOSP (ANDROID OPEN SOURCE PROJECT).. It is stripped of any carrier or manufacturer additions (like HTC Sense or Touchwiz).. and is usually a cleaner and less buggy experience... Then the cyanogen team customizes and polishes features... (like menu infused theming instead of flashable zips..)
If you're too scared of bricking during experimental build testing, etc, this isn't the place for you...
Sent from my Samsung-SPH-D700 using XDA Premium App

Will Cm7 on the epic have no CIQ?
Sent from my SPH-D700 using XDA Premium App

Sorry for the double post, the xda app submitted when open the physical keyboard. I too have been wondering what the big deal is with cm.. I can't find any concrete info that tells me what is so great about it. I'm on acs now and love it.
Sent from my SPH-D700 using XDA App

Overstew said:
Will Cm7 on the epic have no CIQ?
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
It will not have CIQ. That is from Sprint, and this will have no traces of sprint whatsoever.

CM is completely customizable, it comes with all kinds of tweaks to make the phone a whole lot smoother, it gets updated constantly, and since its based on AOSP you can really do what ever you want with it. Whereas a stock samsung ROM you have to be careful what you do cause so many things rely on frame work and what not. The CM team is absolutely amazing the wrote code completely from scratch for $g and full HDMI mirroring to work on the evo. Also the size of the rom, CM is around 80 mb where most stock roms are 200, so you will have that much more space on the phone.

To set the record straight, I am hardly a "noob" in the sense that some here seem to think. I'm building kernels for my own use, and am working on a rewrite of the keyboard driver to more completely fix the problem so skillfully determined and patched by mkasick.
What I'm "noob" at is understanding in detail what I gain, and give up, by installing CM over the other custom ROMs based on stock releases. I have the broad strokes -- I need more specifics to decide if it's worth the hassle to give it a try.
We now have two new pieces of valuable information not obvious in any of the general info out there: Compromised video support (negative), no CIQ (positive). So, a little progress.
Sent from my mind using telepathitalk

i doubt anyone actually knows what you're asking....
Cyanogenmod is just pure android no bloatware from sprint/sammy
the way android was meant to be.

Pretty simple: If it is software that is added by a carrier or a manufacture (Sprint ID, touchWhiz, Samsungs Video Codecs) It will not be there. What it does have:
CM UI Tweaks, CM Hardware Tweaks, CM Performance enhancement options (adjustable heapsize) Default install location, Screen On Animation, Surface Dithering, Locking the Homescreen App in memory (so it doesn't rebuild it self when you press home), locking the messaging app in memory, DSP Audio Manager for Custom EQ setups over BT, Speaker, and head phones, Lock screen gestures, Lock screen music controls....
This is all of the top of my head.

Kcarpenter said:
Pretty simple: If it is software that is added by a carrier or a manufacture (Sprint ID, touchWhiz, Samsungs Video Codecs) It will not be there. What it does have:
CM UI Tweaks, CM Hardware Tweaks, CM Performance enhancement options (adjustable heapsize) Default install location, Screen On Animation, Surface Dithering, Locking the Homescreen App in memory (so it doesn't rebuild it self when you press home), locking the messaging app in memory, DSP Audio Manager for Custom EQ setups over BT, Speaker, and head phones, Lock screen gestures, Lock screen music controls....
This is all of the top of my head.
Click to expand...
Click to collapse
O O Don't forget the BJ's Feature
i even dumped my GF

There's a lot of misinformed posting going on in here.
First of all, CyanogenMod is NOT AOSP. It is, however, more AOSP than Samsung's or HTC's stock ROMs. It is based on AOSP and built from the ground-up, but AOSP it is not.
AOSP is the bones on which everything you see on Android is built. Some phones have true, pure AOSP builds, but we do not. The CyanogenMod project, once completely, will allow a build of AOSP to run on the Epic since they share all the same drivers, but, once again, that doesn't make CyanogenMod completely AOSP, as people so willingly say.
Now, what IS CyanogenMod?
The goal is quite simple: It aims to achieve a single user-experience across multiple platforms through the use of open-source software and alternatives. One thing you can expect from the base CyanogenMod experience is that if you are running CyanogenMod7-RC2 on your MyTouch 3G Slide, you can talk to you friend who is using CyanogenMod7-RC2 on his HTC Evo 4G and be able to completely understand everything each other's phone can provide (sans hardware differences, such as CPU speeds and front-facing camera).
It is also meant to open new doors for developers to completely customize their user experience. Every last part of the CyanogenMod experience is open source. That's how new features are almost constantly being added.
Another goal is to keep every phone up-to-date with the newest version of Android as it is rolled out. Providing a basic starting ground for every phone means that patching the Android system to the latest version is considerably easier. That's why, several times, I've mentioned that the work done by noobnl on CyanogenMod6 has helped us getting where we are with CyanogenMod7. While we are not using it verbatim, the work points us in the right direction and shows us how to easily fix what is broken.
People are asking questions like "Will program X be left in" or "Does this add X". The answers are a lot more complicated than just yes or no. The fact of the matter is that, for the most part, NOTHING from the stock Samsung software is included. Apps may resemble what was in your stock experience, but that's only because Samsung based their own software after their AOSP counterparts. With that said, none of Sprint's bloatware is on CyanogenMod. I'm not even sure the most of them would even work. Things like Nascar, Sprint TV, and the like just are not there because the system is not built around them, plain and simple.
Because of this lack of bloat, you are gaining much in the way of speed, performance, and usability. Carrier IQ isn't there to bog your phone down. Useless DRM services aren't running in the background, eating your battery. The Sprint Apps aren't taking up valuable space in your phone's memory. It's clean.
Another thing CyanogenMod will provide to the community is a basis to provide some real meaty ROMs. Right now, for the most part, the ROMs are reskins and rehashes of other ROMs, save two or three. Fight as you might, but that's the truth. CyanogenMod is completely different and will allow developers more control over what they are doing. A lot of cool features can be made, such as autoupdaters and random system tweaks, and they can all be built in. For example, if you look at CyanogenMod now, you'll notice that ADW is the default launcher, and its settings are integrated into the phone's settings instead of being a standalone.
And the beauty of it all is that everything can be made to work how you please. For those worried about the video codec problem, it's a problem that can be solved simply by making those codecs work on CyanogenMod, which shouldn't involve too much trickery.
I hope this answers your question.

I concur. You are really thinking too far into things. There are very few limitations that cm7 will bring. For all of these, there are other apps that rectify it.
Sent from my Samsung-SPH-D700 using Tapatalk

Thanks Devin for a great response. Why is it we needed development to come give a nice answer... and the rest of the users just wanted to be know it all jerks?

skywalkr2 said:
Thanks Devin for a great response.
Click to expand...
Click to collapse
agreed, thanks
Why is it we needed development to come give a nice answer... and the rest of the users just wanted to be know it all jerks?
Click to expand...
Click to collapse
aww man, don't do that.. it doesn't really help anything, it just invites people to get all butt hurt about your being butt hurt about whatever the ****.. Just let it go.
My only question about CM is the obvious one.. "Is it done yet? (for my phone obviously)"

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

Am I expecting too much from a ROM?

My Gb ROM, the stock sense, was pretty f'n awesome when it came to functioning with a lot of apps loaded. All these Jelly Bean ROM's are all show and no go. They look great. But once you get a few apps loaded, you can forget about stability and speed. Some ROM's are better than others, but they all seem to share this same theory. I speak too soon on many "good" things about a ROM then feel like an idiot later once I see the nitty gritty is seen and I move on to the next one. I am so fed up with looking for the perfect ROM. I don't need to look any more. The perfect ROM for the Evo is the one that came with it. I jsut need to find my stock version, with 4G, and no spyware and be done. I can't wait to get a Galaxy S 4. I need a second job....

Not expecting too much just using the wrong roms. The Og is an awesome device but like all money hungry corporations Htc put the Og in the grave. While it can handle some of the new Os's we dont have the proper drivers to run our hardware so only gingerbread roms will run properly. Now the devs have done the best they can to keep this ancient device up and running the latest software but without the proper drivers we can not expect everything to work correctly.
Now if you want the Og to be the best it can you need to use gingerbread otherwise you have to make compromises. Reloaded .500, Jellybread, GB MIUI are all great roms that work very well with our device. If you are looking for the jellybean/ics flare, bells, whistles, and such you could also try my rom (CyanMobile). But if you must have the latest and greatest then there is only one thing to do. That is what the corporations are counting on anyways. Go get you the latest and greatest phone out there. Oh yeah and a second job will help you pay for that device also. Lol.
Long live the Evo 4G. The device that has been dead for years now but still being developed and running strong!!!

If we had FFC on the JB roms then I would run MIUI JB...I use apps like Google Now and Keep on my tablet but sadly I like snapchat and I'm stuck with Gingerbread on my EVO. Still a great phone.
Sent from my PC36100 using xda app-developers app

Still using mikg 3.11 on my OG EVO.
Unfortunately I to would like some jellybean love, but without proper drivers for hardware I rather stick to a fully functional rom.

OP, very true but you are also very fortunate to have the ongoing development that is available.
Before I bought a new phone, I always used the very stable GB sense ROMs but still loved the fact that I could still play around with ICS and JB ROMs when I was bored.
The support and development the OG still has is amazing, and it gives YOU your choice of what to run .
Also, there is always boot manager...
Sent from my SPH-L710 using xda app-developers app