Vanilla (stock) ICS vs. Sense 4.0 + ICS - EVO 4G General

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

Related

Customizing vs. N1

So I may jump ship from the N1 to the Vibrant. On the N1, in less than ten minutes I can run a nandroid backup, flash a new kernel, new radio and a new rom. In another 3-4 minutes, I can switch back. I've literally switched kernels >3 times/day before. How much different will things be on the Vibrant? Is it harder to do these things? Is there as much risk?
Thanks
right now no one knows, there is no custom kernels, custom recovery, custom roms, etc
There are custom roms and you can easily root the device...but it will obviously take some time to reach N1's customization...
I've had my G1(I know, not the N1) since day 1, and I've been flashing roms since day one. The only reason I flashed roms was because I felt the G1 was lacking in a lot of things. Now that I have the Vibrant, I feel like there's no need to flash a different rom. It's already pretty fast, and I actually like the touchwiz UI. The UI doesnt completely take over the Android interface, it's more like adding extra little features.
ultra spikey said:
I've had my G1(I know, not the N1) since day 1, and I've been flashing roms since day one. The only reason I flashed roms was because I felt the G1 was lacking in a lot of things. Now that I have the Vibrant, I feel like there's no need to flash a different rom. It's already pretty fast, and I actually like the touchwiz UI. The UI doesnt completely take over the Android interface, it's more like adding extra little features.
Click to expand...
Click to collapse
Exactly, plus the Black/Blue color scheme is far better looking to me over stock Android. TouchWiz is not like Sense or previous generations of the skin and that's a good thing.
Ill second that. I am really enjoying my touch wiz interface and I didn't think I would. That being said I miss my app drawer that slid up from the bottom.
Sent from my SGH-T959 using XDA App
I don't know much about flashing to different ROMs yet, but I can give you an overview of the TouchWiz experience from my viewpoint.
Coming from an iPhone, I really like TouchWiz 3.0. And believe me when I tell you: that was their goal with the UI. It screams Apple, in layout and function. But of course, it ultimately feels a bit like an imitation in some areas. I feel like they rushed TouchWiz 3.0 out of the door.
The Clocks and Alarms app is much better than the iPhone's, which is something I was not at all expecting. It's really quite nice. The calendar app is about on par, in terms of layout. The upper hand is that this syncs OTA with Google's cloud services. The music player is very 'iPod-like', but is ultimately a rush job (embedded album art does not work very often and so forth).
All things considered, it's a really nice UI for Android.
That said, there are some really basic functions which did not make the transition from stock Android. For example: you cannot fully edit contacts in the 'Contacts' app. You cannot delete them, you cannot add custom ringtones. Coming from the iPhone, where I had meticulously completed the profiles of every contact with an obscene amount of info and custom ringtones, this is annoying.
There are a few 'little things' like that, which really matter to me. And this has kind of soured the experience for me, making me second-guess my decision. To be honest, I'm still sort of on the fence over this of the N1 as my iPhone replacement.
The grey area for me is in Android 3.0's release. Google has stated that they're going to overhaul the UI. The idea is that they want to make it more user-friendly, to make the use of custom skins less prevalent. Well, I'm all for this. Trouble is: will these handset manufacturers adopt it, considering their vested interests in their custom experiences?
Samsung's UI is definitely my favorite out of Sense, MotoBlur and the lot. But I'd be lying if I said that I didn't wish for a Nexus One for the security of owning the only unlocked stock device.
Hope that helps...
Give it some time and stock Android will be on the Vibrant. Thats the great thing about Android and Xda.
Yeah, I really love the idea of xda and the amount of support that all of these devices receive from the community. Of course, the trouble is: if you root for a custom rom - even if it's stock Android - the N1 is the only solution for getting OTA updates regularly. With stock Android on the Galaxy S, you're going to have to re-flash every time the ROM is updated. Not the end of the world, but definitely irritating.
Running a JB/Unlocked iPhone, I'm used to dealing with work-arounds, and waiting for hacks. That's the price I paid for using a non-carrier phone. I couldn't accept the automatic updates from Apple, and this became a mild annoyance (reinstalling everything and so forth). But when you decide to 'play nice' and own a carrier-specific phone, you kind of want the experience of timely OTA, non-hacking-related updates that simply update your device, without first wiping it clean.
Know what I mean?
I'm still not sure if I'm going to keep my Galaxy S, or buy an N1 while there's still time (the 'rumors'? of the N1's touchscreen issues are really all that held me back). But either way, I hope that all devices have some way to experience the latest and greatest from Google.
The touchscreen is bad on that phone especially when it comes to multitouch. I'm sure you've already seen the videos comparing the two touchpads and the Vibrant's touchscreen is SO accurate... multitouch included.
Jon C said:
Yeah, I really love the idea of xda and the amount of support that all of these devices receive from the community. Of course, the trouble is: if you root for a custom rom - even if it's stock Android - the N1 is the only solution for getting OTA updates regularly. With stock Android on the Galaxy S, you're going to have to re-flash every time the ROM is updated. Not the end of the world, but definitely irritating.
Running a JB/Unlocked iPhone, I'm used to dealing with work-arounds, and waiting for hacks. That's the price I paid for using a non-carrier phone. I couldn't accept the automatic updates from Apple, and this became a mild annoyance (reinstalling everything and so forth). But when you decide to 'play nice' and own a carrier-specific phone, you kind of want the experience of timely OTA, non-hacking-related updates that simply update your device, without first wiping it clean.
Know what I mean?
I'm still not sure if I'm going to keep my Galaxy S, or buy an N1 while there's still time (the 'rumors'? of the N1's touchscreen issues are really all that held me back). But either way, I hope that all devices have some way to experience the latest and greatest from Google.
Click to expand...
Click to collapse
While its a little early to be 100% yet but Android hacking is a lot different than iphone hacking. The iphone is a closed system and you have to wait till its broken open to update. Android is already open when its released. As for OTAs if Cyanogen supports the Vibrant then there is an app to download and install new updates. Typically if you stay with the same developer, like Cyanogen, then you don't have to wipe when there are updates.
After froyo 2.2 all my touch screen problems was gone.
Sent from my Nexus One using XDA App
So untrue after froyo 2.2 those problems was fix the nexus one is a awsome phone.and I believe the same for the vibrant.
Sent from my Nexus One using XDA App
Can you do me the world's biggest favor?
Would you make some YouTube videos, showing the multitouch tests of your N1? I so, so, so, would love to own one, but I have zero tolerance for faulty hardware. I've been researching this stuff since the N1 launch, and it's the only thing holding me back from purchasing that device.
'Multitouch Vis Test' is probably the easiest way, but if you can think of others to test with, that would be great.
Jon C said:
The music player is very 'iPod-like', but is ultimately a rush job (embedded album art does not work very often and so forth).
.
Click to expand...
Click to collapse
I haven't used my iPod Nano 4th Gen in some time, I find that the N1 is handling my music needs just fine. But if I had a nickel for every time album art was hosed on my iPod Nano I would not have a mortgage anymore...
hah2110 said:
So I may jump ship from the N1 to the Vibrant. On the N1, in less than ten minutes I can run a nandroid backup, flash a new kernel, new radio and a new rom. In another 3-4 minutes, I can switch back. I've literally switched kernels >3 times/day before. How much different will things be on the Vibrant? Is it harder to do these things? Is there as much risk?
Thanks
Click to expand...
Click to collapse
First you must know that the process is completely different. For right now most roms are installed through the Odin process. This process completely wipes all of the information on the phone (including apps and settings) and then installs the new rom. So you will have to backup your apps and settings every time you change roms (Titanium backup would work but it's not always fool proof). Second all roms are going to be based off of Samsung code. That means no Sense roms, no stock roms (well you can get the stock launcher but your dialer and notification bar will always be touchwized), and no froyo until Samsung releases there own version. This has been true so far with all previous Samsung phones and looking at the development with the I9000 it seems to hold true for the Galaxy S. All this does put you at less risk of bricking your phone but it does mean you also have less chance of serious customization. Also with limited source code for the I9000 (there are some drivers that are not source code but actually compiled) it's very difficult to just plop roms on from other sources.
psychoace said:
First you must know that the process is completely different. For right now most roms are installed through the Odin process. This process completely wipes all of the information on the phone (including apps and settings) and then installs the new rom. So you will have to backup your apps and settings every time you change roms (Titanium backup would work but it's not always fool proof). Second all roms are going to be based off of Samsung code. That means no Sense roms, no stock roms (well you can get the stock launcher but your dialer and notification bar will always be touchwized), and no froyo until Samsung releases there own version. This has been true so far with all previous Samsung phones and looking at the development with the I9000 it seems to hold true for the Galaxy S. All this does put you at less risk of bricking your phone but it does mean you also have less chance of serious customization. Also with limited source code for the I9000 (there are some drivers that are not source code but actually compiled) it's very difficult to just plop roms on from other sources.
Click to expand...
Click to collapse
Why can't CM do his thing?
cm is trying to port cyanogen to the vibrant. in fact ive read that the vibrant and the droid x are his 2 top priorities so it will come soon enough. and once he gets it done we will probibly see a bunch of roms based of cyanogen
blazewit said:
cm is trying to port cyanogen to the vibrant. in fact ive read that the vibrant and the droid x are his 2 top priorities so it will come soon enough. and once he gets it done we will probibly see a bunch of roms based of cyanogen
Click to expand...
Click to collapse
I have yet to see any information confirming any of that. First on his twitter he only seems to be working on the Evo right now. Second I doubt he would work on the Droid x until it's rooted (which most likely will be never). Last I have seen only a small pattern of talk about someone in conversation with Cyanogen about allowing a Galaxy branch of the CM code for use with the Galaxy S. Problem is this doesn't solve the issue of not having source code for a few drivers. This does not even attack the issue of getting the rom onto the phone. So don't hold your breath for any of that.
yea your right it was just one site claiming that cm is working on the vibrant,from what i can tell gothdroid and a bunch of other g1/dream devs are working right now for custom recovery and porting cm6 and froyo asop

[Q] To flash or not to flash (Stock ROM to CM7 alpha)

For those who have tried, is the CM7 alpha worth replacing the stock Glacier ROM? What are the benefits over the current stock HTC Sense ROM? What's missing or not quite there?
Wrong Section, good question though
Sent from my HTC Glacier using XDA App
Cm7 nightlies - no longer CM7 alpha
It's true that this is probably the wrong section and I'm a noob too but before they bring in the new rules about minimum postings in the developer section, I'll throw in my ten cents.
Background:
US T-Mobile version of Mytouch4G and had no reason to be unhappy with the stock Rom but just love to scratch an itch and see what happens.
In the pursuit of seeing what happens I successfully rooted the phone to the point of permanent S=off (but not complete unlock as I have no need for that yet)
and over the course of the last few weeks systematically installed and tested three of the froyo builds/ports available on this forum.
Each have their strengths and weakness which are clearly listed so I wont catalogue the details I'll just say the following:
It's a lotta lotta fun! there was a geek in me waiting to get out and I finally see what the true potential is with this platform (android) - It's probably unlimited.
Aside from the philosophical point of wanting to have the freedom to do whatever with and put whatever you want on the device, that rooting facilitates (I’m a veteran of two generation of iphones), there is also that practical point that rooting does unlock the full potential of the device available right now which includes a host of apps already on the market only for rooted devices.
I don’t want to go into all those possibilities here because they are covered in detail in any google search but let’s just say that once you’re on the other side of the proverbial fence, the grass really is greener.
I know I’m being vague at this point, but let me continue a little longer.
Having also owned a number of windows based htc devices through 2005-2008 I’m no stranger to htc sense and some of the useful little gadgets that they seem to have evolved to a fairly decent level in android and I’ll say this:
Take away the surface veneer which is not as bad in the MT4G as in some others (bloatware) and you find that the meat and potatoes of the platform/operating system is all android.
And it runs MUCH better without the crap. – forget about overclocking (which helps and is fun) loose the veneer and the device flies.
And what you lose in the process – a couple of apps – you replace immediately with comparable ones for free down at the market.
So – phone runs better, can do more, has a host of better looking ui’s and themes that all the talented developers on this forum are constantly pushing out – then what about the risks?
I haven’t had a single hitch – not one.
I’m as impulsive as the next guy but I just took it steady with the information overload – carefully rooted the phone and from there, flashing one rom after another has become no more complicated than booting into recovery – case closed.
It’s become second nature.
And I’ve had to do a double take once or twice when something didn’t play out exactly as described but I’ve discovered that I had overlooked a detail here and there and it’s an easy fix.
Point being that there are constant warnings and disclaimers for obvious reasons, but my device at least has turned out to be very hardy – no scares here.
So finally, I’ve been eyeing developments in the gingerbread camp like everyone else and I’ve been wary of the alpha builds because my zero level of expertise keeps me from playing in that league and I see early this morning that an official CM7 release is out for my model the glacier.
At first I run I into problems flashing Clockworkmod to 3.0 and even try to flash the rom and boot from 2.5 with the predictable conclusion of a stuck boot loop all the while not really knowing what to expect from this ginger hype and whether it’s really worth the trouble of leaving my now very stable cooked froyo rom.
Someone then creates the thread a few lines up describing how to simply use rom manager to install the update for CWM 3.0 and at 2am I’m on my way.
I flash the rom and install the additional google apps and what do I find?
GINGERBREAD IS **** HOT!
Nuff said.
I won’t be overclocking it as a rule but I get 2805 on quadrant – previous high being in the 2500’s (each chip is actually different so I’ve heard that everyones score will vary)
The device has no lags, splutters, and runs quite literally incredibly.
and the look and feel of gingerbread? – I’ll add to what I said earlier – it’s amazing – it’s a moving graphical, visual feast.
It will seriously rain on apple’s parade when this thing hits the main stream and I think quite honestly that it’s the greatest mobile device operating system ever created.
I know I’m gushing but it really is that good and considerably more impressive than froyo while having the same core navigation and other functionality.
I won’t be going back.
I won’t endorse taking risks with your device but I’ll say it’s worth taking a look.
A few afterthoughts for those asking the questions:
There is a brand new version of the market packaged with the 20110115 version of the larger gapps file floating around on this forum – it also rocks!
Although most apps available on the market have not yet been updated for gb 2.3, they all work so far on my machine with one or two unimportant exeptions.
I’ve replaced all sense functionality with free apps off the market – no loss there.
The device runs smoothly and all functionality is tested and working in the latest release - great job guys doing the work here.
Long and the short of it being …it’s all good.
hope that helps.
Definitely worth a flash to try yourself. I mean it's CyanogenMod so how could it not be good?
Sent from my HTC Glacier using Tapatalk
matkam said:
For those who have tried, is the CM7 alpha worth replacing the stock Glacier ROM? What are the benefits over the current stock HTC Sense ROM? What's missing or not quite there?
Click to expand...
Click to collapse
You would be very surprised at how extremely stable these roms are. I've been running them for a few weeks now and they're definitely stable enough to be your daily driver.
The main thing to consider is that Sense is a highly customized ROM while CyanogenMod is based on Pure Google with some additional configurations available.
Try it out, it's pretty easy to go back if you don't like it. For a while there I was nandroiding back and forth between Sense and CM6 about twice a week, lol.
CM7 some after thoughts
Continuing from my earlier post, I thought I would head off a few questions about observable differences in gingerbread - well the CM7 incarnation:
Android market loads and populates faster.
The wireless radio picks up signals/networks faster and connects gracefully and quickly.
All aspects of the functionality of the whole system and each individual app seems to be smoother and more efficient.
Youtube no longer has that annoying glitch coming out of landscape.
My new 16bg class 6 mini sdhc card finally works and no longer gives me the blank card or damaged card bull crap every time I unmount or remount from usb mode – didn’t expect that one and had resigned myself to going back to the stock 8gb card it shipped with.
The app drawer pops out at you in what seems like 3d while leaving the background wallpaper intact. – so the app drawer just floats while you scroll through it.
Every aspect of the device and systems are customizable – I mean everything – probably in part due to the efforts of the CM7 team.
The stock gingerbread phone dialer app is changed for the better and is obviously one of many enhancements including the ability to program your sip (voip) settings straight into the phone doing away with third party apps altogether to make or receive calls (if you’re into voip)
You’ll have to dig around to find the .apk for the stock car/navigation mode app and I solved that riddle by downloading the free android app(car home) from the market and also installing a third party app (car mode control) which is used to launch it – I’ve been lazy and haven’t investigated yet whether it’s actually necessary to have the go between, but it works.
and swype, if you want it, can be downloaded direct from the guys that developed it at the beta.swype page (wasn't allowed to post the link) - by simply registering to test the latest beta, which is better than in the stock MT4G rom.
Someone report the first post to have this moved.
Sent from my SPH-D700 using XDA App
Whosdaman said:
Someone report the first post to have this moved.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Didn't realize it had to be reported. I always assumed that because you're a mod you can do whatever the hell you want.
Well in your case just pick current RC fork from repository and use it normally you don't have to wait for the SR fork. Unless you are dev I don't see why you would want to flash it every night unless you understand basic and even in that case weekly might be fine. I been there done that as flashing new rom everyday as it came down the pipe I tried few CM7A few times let the dev do more work as ill make that my rom when SR is out, ATM have IGv1.1.6 as I flashed it this afternoon.
matkam said:
For those who have tried, is the CM7 alpha worth replacing the stock Glacier ROM? What are the benefits over the current stock HTC Sense ROM? What's missing or not quite there?
Click to expand...
Click to collapse
If you thought your phone was fast out of the box, this is faster. If you thought it was a bit laggy (like me), it's like getting a brand new phone.
Also, having better experiences with CM7 GB on MT4G than I ever did on my Nexus S. This is saying a lot.
ZeroSX said:
Also, having better experiences with CM7 GB on MT4G than I ever did on my Nexus S. This is saying a lot.
Click to expand...
Click to collapse
Same for me. Such a smoother experience all around.
Sent from my HTC Glacier using Tapatalk
I just flashed & I must say it is a much smoother expericence. I love it & its not even a stable build.
matkam said:
For those who have tried, is the CM7 alpha worth replacing the stock Glacier ROM? What are the benefits over the current stock HTC Sense ROM? What's missing or not quite there?
Click to expand...
Click to collapse
Is this your first Android phone? Have you ever played with a Pure Google Experience Android phone? If you're nervous about the CM7 builds, try CM6. Easier to flash since you don't need to manually flash the recovery and it will give you a feel for CyanogenMod and the Pure Android feel.
Think of the G2, that comes with plain Android right out of the box. Go to a T-mobile store and poke around with it to see if you like it.
I simply cannot stand the HTC Sense stuff... Personal preference.
I had CM6.1 for a couple weeks and I am VERY happy with it. I am waiting another week or so to start using the CM7 builds just because I have been too busy with other stuff.
neuralboy said:
It's true that this is probably the wrong section and I'm a noob too but before they bring in the new rules about minimum postings in the developer section, I'll throw in my ten cents.
Background:
US T-Mobile version of Mytouch4G and had no reason to be unhappy with the stock Rom but just love to scratch an itch and see what happens.
In the pursuit of seeing what happens I successfully rooted the phone to the point of permanent S=off (but not complete unlock as I have no need for that yet)
and over the course of the last few weeks systematically installed and tested three of the froyo builds/ports available on this forum.
Each have their strengths and weakness which are clearly listed so I wont catalogue the details I'll just say the following:
It's a lotta lotta fun! there was a geek in me waiting to get out and I finally see what the true potential is with this platform (android) - It's probably unlimited.
Aside from the philosophical point of wanting to have the freedom to do whatever with and put whatever you want on the device, that rooting facilitates (I’m a veteran of two generation of iphones), there is also that practical point that rooting does unlock the full potential of the device available right now which includes a host of apps already on the market only for rooted devices.
I don’t want to go into all those possibilities here because they are covered in detail in any google search but let’s just say that once you’re on the other side of the proverbial fence, the grass really is greener.
I know I’m being vague at this point, but let me continue a little longer.
Having also owned a number of windows based htc devices through 2005-2008 I’m no stranger to htc sense and some of the useful little gadgets that they seem to have evolved to a fairly decent level in android and I’ll say this:
Take away the surface veneer which is not as bad in the MT4G as in some others (bloatware) and you find that the meat and potatoes of the platform/operating system is all android.
And it runs MUCH better without the crap. – forget about overclocking (which helps and is fun) loose the veneer and the device flies.
And what you lose in the process – a couple of apps – you replace immediately with comparable ones for free down at the market.
So – phone runs better, can do more, has a host of better looking ui’s and themes that all the talented developers on this forum are constantly pushing out – then what about the risks?
I haven’t had a single hitch – not one.
I’m as impulsive as the next guy but I just took it steady with the information overload – carefully rooted the phone and from there, flashing one rom after another has become no more complicated than booting into recovery – case closed.
It’s become second nature.
And I’ve had to do a double take once or twice when something didn’t play out exactly as described but I’ve discovered that I had overlooked a detail here and there and it’s an easy fix.
Point being that there are constant warnings and disclaimers for obvious reasons, but my device at least has turned out to be very hardy – no scares here.
So finally, I’ve been eyeing developments in the gingerbread camp like everyone else and I’ve been wary of the alpha builds because my zero level of expertise keeps me from playing in that league and I see early this morning that an official CM7 release is out for my model the glacier.
At first I run I into problems flashing Clockworkmod to 3.0 and even try to flash the rom and boot from 2.5 with the predictable conclusion of a stuck boot loop all the while not really knowing what to expect from this ginger hype and whether it’s really worth the trouble of leaving my now very stable cooked froyo rom.
Someone then creates the thread a few lines up describing how to simply use rom manager to install the update for CWM 3.0 and at 2am I’m on my way.
I flash the rom and install the additional google apps and what do I find?
GINGERBREAD IS **** HOT!
Nuff said.
I won’t be overclocking it as a rule but I get 2805 on quadrant – previous high being in the 2500’s (each chip is actually different so I’ve heard that everyones score will vary)
The device has no lags, splutters, and runs quite literally incredibly.
and the look and feel of gingerbread? – I’ll add to what I said earlier – it’s amazing – it’s a moving graphical, visual feast.
It will seriously rain on apple’s parade when this thing hits the main stream and I think quite honestly that it’s the greatest mobile device operating system ever created.
I know I’m gushing but it really is that good and considerably more impressive than froyo while having the same core navigation and other functionality.
I won’t be going back.
I won’t endorse taking risks with your device but I’ll say it’s worth taking a look.
A few afterthoughts for those asking the questions:
There is a brand new version of the market packaged with the 20110115 version of the larger gapps file floating around on this forum – it also rocks!
Although most apps available on the market have not yet been updated for gb 2.3, they all work so far on my machine with one or two unimportant exeptions.
I’ve replaced all sense functionality with free apps off the market – no loss there.
The device runs smoothly and all functionality is tested and working in the latest release - great job guys doing the work here.
Long and the short of it being …it’s all good.
hope that helps.
Click to expand...
Click to collapse
Where did you see a link for an official CM7 release for this phone?!?!
Q.Entity said:
I simply cannot stand the HTC Sense stuff... Personal preference.
I had CM6.1 for a couple weeks and I am VERY happy with it. I am waiting another week or so to start using the CM7 builds just because I have been too busy with other stuff.
Click to expand...
Click to collapse
You know that's how I felt when I bought the phone. I kept thinking about returning it for a G2 just to get plain Android. Ironically, by the time I finally rooted my phone and flashed CM6, Sense had grown on me to the point that I kept nandroiding back and using it by choice. Ha!
Now I've been on cm7 for a few days and I'm pretty happy with it.
CM7 official nightlies
I can't post a link out but the link to the CM7 builds is usually towards the top of the mytouch 4G Android Developement forum page.
It's constantly being updated and it looks like the latest build takes care of a number of little issues including swype, google car home and maybe the apps pack too
To those voting not to flash, have you tried CM7? What's keeping you from being happy with it?
I just flashed it myself and am pretty happy with it. The experience is much more consistent than the stock Sense ROM, gingerbread is really fast/smooth, and CM7 adds a lot of options for customization. Wifi isn't working though.
matkam said:
To those voting not to flash, have you tried CM7? What's keeping you from being happy with it?
I just flashed it myself and am pretty happy with it. The experience is much more consistent than the stock Sense ROM, gingerbread is really fast/smooth, and CM7 adds a lot of options for customization. Wifi isn't working though.
Click to expand...
Click to collapse
Reboot for wifi to work.
BTW, CM7 is slick as an iced glacier.
Sent from my HTC Glacier using XDA App
neuralboy said:
GINGERBREAD IS **** HOT!
Nuff said.
Click to expand...
Click to collapse
This has got to be the biggest fanboism i've every heard on any forum. Gingerbread is not that different from FroYo. It looks the same it feels. it acts the same.
To the OP If you want to flash the most current baked variant of Android then by all means flash away. If not FroYo will serve your needs just fine.

Give me one reason I need an unlocked bootloader.

Other than these two:
Overclocking
Loading modded roms
I mean let's all be honest, even if you undervolt and remain stable, any overclocking that will allow noticable performance, will have just as much noticable effect on the battery. And these are mobile devices. Battery should be considered top priority, not speed.
And what's the deal with wanting to load all these custom roms? Are they significantly better than stock, Adeo, or gingerblur? What do we need to load a fully custom rom for? Are they lightning fast and extend battery life by 100%? I guess I just don't get it. Deodexing and visual mods can be done without an unlocked bootloader.
Basically what im trying to say is. What is everyone *****ing about?
Sent from my Atrix using XDA App
As far as I know, there is no way to unlock the Atrix's bootloader. It is encrypted. You may check the xda's frontpage, there is news several weeks ago regards to the Moto's bootloader.
mccoy007 said:
As far as I know, there is no way to unlock the Atrix's bootloader. It is encrypted. You may check the xda's frontpage, there is news several weeks ago regards to the Moto's bootloader.
Click to expand...
Click to collapse
I think you missed the purpose of the thread. He is not asking HOW to do it, only WHY you would need to, other then overclocking or loading ROMs.
Honestly, it does make a big difference. Battery life can be very substantially increased in many of these roms. They both over and under clock processors to maximize the life. It's possible to get gingerbread on the inspire right now through custom roms because the boot loader isnt locked. It's possible to completely remove sense, whereas we have to live with motoblur. There really are a lot of reasons. Honestly, look at what Xda is all about, it's android development. Just take a look at the atrix dev forum vs the inspire one. Phones with a strong development community tend to live far longer because they can upgrade the os long after the company stops trying. The original g1 was only officially upgraded to 1.6 (I believe) but Xda has a few 2.2 roms that actually run pretty solid.
Tl:dr the list goes on and on of reasons that you want an accessible boot loader.
Ability to load a custom recovery menu. Nandroid.
it's simple dude. people do it because they can.
Besides the fact you would get work and support from the awesome devs here another good reason would be most phones have their shortcomings.Most of the time this can be fixed in the software.The awesome devs here are able to in most cases get it sorted out within a week or 2 whereas if the phone manufacturer or carrier is gonna do something about it your gonna wait 6 months to get an update. A prime example of this was the rediculously low external and earpiece speaker volume on the inspire.On max volume it was just too low. Now the rom chefs can cook up custom roms with 20% volume increase.
The 2 reasons you want to exclude are the main points. It's like saying "other than drowning; what's the point of learning to swim".
i want android 2.3.3 , can i ? no! i have to wait to an official update from motorola.. why ?!
i want htc sence in motorola , can i ? no !
we love to play and change things.. uman nature
seh6183 said:
Other than these two:
Overclocking
Loading modded roms
I mean let's all be honest, even if you undervolt and remain stable, any overclocking that will allow noticable performance, will have just as much noticable effect on the battery. And these are mobile devices. Battery should be considered top priority, not speed.
And what's the deal with wanting to load all these custom roms? Are they significantly better than stock, Adeo, or gingerblur? What do we need to load a fully custom rom for? Are they lightning fast and extend battery life by 100%? I guess I just don't get it. Deodexing and visual mods can be done without an unlocked bootloader.
Basically what im trying to say is. What is everyone *****ing about?
Sent from my Atrix using XDA App
Click to expand...
Click to collapse
Your first question says "ignoring custom ROMs..." and your second question says "What about custom Roms..." so I'll address the second question.
ROMs. Gingerbread. AOSP. Stock Android. Kernels.
Another consideration in favor of ROMs is the continuation of support by the dev community even after the manufacturer has EOL'ed a product. You still see the Dream (G1) getting roms with new features even though the phone has been effectively dead for a while now.
It is always in the phone manufacturer's and the carrier's best interests to kill off support to get you to buy the newest, latest device.
daveop said:
Just take a look at the atrix dev forum vs the inspire one. Phones with a strong development community tend to live far longer because they can upgrade the os long after the company stops trying.
Click to expand...
Click to collapse
I love my atrix.. but I visited the Inspire 4G dev forums... and.. yeah I got a little bit jealous. lol
I hope the few devs we have don't end up leaving and can crack this bootloader!!!!
s1mpd1ddy said:
I love my atrix.. but I visited the Inspire 4G dev forums... and.. yeah I got a little bit jealous. lol
I hope the few devs we have don't end up leaving and can crack this bootloader!!!!
Click to expand...
Click to collapse
I know what you mean. That's one thing I like/liked about my FUZE: there was a pretty active dev community, at least until the HD2 came out.
I'm planning on getting an Atrix on Monday and this is making me think about getting an Inspire instead. I guess I'll get the Atrix and if it blows I can take it back, get an inspire, and pocket $100.
Wow is this seriously a question?
Nandroid backups, AOSP ROMs like Cyanogen where you get updates every NIGHT if you wish from the source Android build so it'll always be the latest version - no waiting for Motocrap. Battery life is usually way better, TONS of tweaks (being able to tweak my color balance of the screen, gamma levels, haptic feedback behavior, autobrightness levels and thresholds, lockscreen and messaging gestures, etc). That's all before even mentioning performance increases like overclocking, deodexing for themes, ext4 modifications for faster I/O. There's just way too many things to list but if you've never experienced a phone that has custom ROMs (especially Cyanogen) then I can see why you don't miss anything, but if you have, like me, you'll probably never want to settle for an Android phone that doesn't allow custom ROMs.
custom roms is reason enough...like dinan said if you ever used them you would understand. pretty much all the problems that people are having with the atrix could be solved if our devs had access to the bootloader.
I do see the importance of having continued support after moto leaves the phone behind. And it would be nice to have a dev make a rom to fix the coloring on the Atrix screen. Also I didn't realize that updates to custom roms come so often and that they had that much support.
I am starting to see now.
Sent from my Atrix using XDA App
mccoy007 said:
As far as I know, there is no way to unlock the Atrix's bootloader. It is encrypted. You may check the xda's frontpage, there is news several weeks ago regards to the Moto's bootloader.
Click to expand...
Click to collapse
Luckily, there are a few other people working on the bootloader (I hope), as it is signed, not encrypted; there is a difference.
My phone before the Atrix was the TytnII, and the only reason I was able to keep it as long as I did was because of custom ROMS. If they are able to increase the performance of this phone the way they increased the performance of my 300Mhz/128MB RAM TytnII, then I will be giddy as a school-girl.
Do I need an unlocked bootloader? No, I absolutely love my phone the way it is right now, as this is my first Android, so I don't know what else is possible.
Battery life?
I am running a test of a custom kernel for my captivate. I turned off everything and wanted to see how long it would last.
No wifi or data (no sim card installed) it ran idle for 11 days.
Custom Kernel with no wifi or data its going to last about 50 days. (based on current estimate as im still testing it)
Just an FYI, there are devices with locked bootloaders that have custom ROMs. This includes the X10, which has a Gingerbread ROM. The issue is getting a newer Android build to work with a stock kernel. Unlocking the bootloader is key to building custom kernels but there are methods for getting custom ROMs without a custom kernel.
Developer support.
/thread
-Sent from my Galaxy Tab
Athailias said:
Battery life?
I am running a test of a custom kernel for my captivate. I turned off everything and wanted to see how long it would last.
No wifi or data (no sim card installed) it ran idle for 11 days.
Custom Kernel with no wifi or data its going to last about 50 days. (based on current estimate as im still testing it)
Click to expand...
Click to collapse
Well this isn't exactly a real world situation. Who's to say that you're not running the cpu at 1mhz with the screen powered off 24/7. wouldn't you prefer to test under load and real use?
Sent from my Atrix using XDA App

Evo LTE...In layman's terms...

So my 2 year contract just ran last month.
I have LOVED my EVO 4G. Have flashed countless roms. Favs have to be Tommy's and MIUI but I also really liked Synergy before Tommy's was released.
So I hear all this talk about the EVO LTE not being fully rootable. So, can someone please point me in the right direction...?
The biggest selling point for me when it comes to getting a new phone is the screen/display. I NEED a large screen and want it to look nice (vibrant colors). I know the LTE has a 4.7inch screen which is very attractive to me.
I assume the LTE will be fully rootable sometime down the road. Maybe like a month or two after release I hope. I hear all this talk about the Galaxy Nexus and another model so I'm not sure if going LTE is the right choice? I want to be able to flash new roms when needed. I don't mind Sense as you can see based on my fav roms but I am not "tech" savvy so will it still be possible to flash roms on the LTE using Amon Recovery? I don't know how to push things using the PC and root commands like "su" so if that is the only way to flash stuff on the LTE then I will have a problem.
Any suggestions would be greatly appreciated.
I think it'll be possible to fully root it, I don't think Sprint will go the same route AT&T went with when they had HTC lock down the One X, though that's certainly within the realm of possibility as well. We'll just have to wait and see if the unlocker tool will work for the EVO LTE. If not, then I give it a few months. Somebody will find a work around.
You'll be able to flash ROMs just fine from what I understand. Unless boot.img has to be done thru fastboot. I saw that being the case somewhere recently, I just can't remember where. But you won't be able to flash splashscreens and radios until/if S-off.
From what I've seen you can flash kernels and recoveries using flash_image GUI app. Now, that was the case apparently for Evo 3d, but if the partitions are written and protected differently from that then this may not still hold true.
I intend to get it, see how it goes over the first 14 days, and if it looks like brick walls on S-off or easy kernel flashing, I'll exchange it for galaxy nexus on 15th day.
sent from 2yr old Evo on ICS
if rooting and flashing roms really are important factors in your decision, just wait. Wait until devs have the LTevo in their hands and what happens with root (shouldnt be more than a couple weeks) if there arent any issues than jump on board. if for some reason there are issues, go with the gnex. it sucks that sprint is now charging a $35 restocking fee for all its phones if you swap within the grace period (you could always go this route too if you have the extra cash)
they both have big, beautiful screens and both are excellent phones. one gripe i hear about for the gnex is battery life but then you have removeable batteries as an option
Until the Evo LTE is sitting in the hands of developers for a few weeks at the minimum, a question like this can NOT be answered.
Starzboy77 said:
So my 2 year contract just ran last month.
I have LOVED my EVO 4G. Have flashed countless roms. Favs have to be Tommy's and MIUI but I also really liked Synergy before Tommy's was released.
So I hear all this talk about the EVO LTE not being fully rootable. So, can someone please point me in the right direction...?
The biggest selling point for me when it comes to getting a new phone is the screen/display. I NEED a large screen and want it to look nice (vibrant colors). I know the LTE has a 4.7inch screen which is very attractive to me.
I assume the LTE will be fully rootable sometime down the road. Maybe like a month or two after release I hope. I hear all this talk about the Galaxy Nexus and another model so I'm not sure if going LTE is the right choice? I want to be able to flash new roms when needed. I don't mind Sense as you can see based on my fav roms but I am not "tech" savvy so will it still be possible to flash roms on the LTE using Amon Recovery? I don't know how to push things using the PC and root commands like "su" so if that is the only way to flash stuff on the LTE then I will have a problem.
Any suggestions would be greatly appreciated.
Click to expand...
Click to collapse
Go into an AT&T store and play with the One X, you WILL want this phone! This is basically the same as the EVO LTE, though the LTE does have some nicer specs!
Scott is right, you will be able to have access to flash ROM's, I don't know about the flash image GUI, I heard that they lock out any flashing from within /system...
About recovery, I don't know which ones will be available as one will need to be ported. Hopefully someone will work on porting Amon Ra, usually Clockwork is the first available.
You WILL have to learn fastboot commands prior to a one-click type of root being made available, this isn't that hard, if you can get through the HTC unlock process you can do pretty much anything in fastboot or ADB.
With Sense 4 being so light, beautiful and functional you won't have much need of flashing ROM's until some good tweaks are developed. Basically all of the tweaks you would make to a normal ROM have now become built into Android. Swipe to clear notification? Stock. Inverted pull down menu? Stock. Anything ICS styled? Stock. Plus there is more. Really go play with the One X and you won't regret your decision to get the LTE.
This is coming from someone who is not going to get the phone, by the way... I plan to get either the Galaxy Nexus or the next Nexus unlocked from Google and put it on a sim plan with T-mobile. This is primarily for monetary reasons, and it doesn't hurt to get a device designed for developers...
imheroldman said:
With Sense 4 being so light, beautiful and functional you won't have much need of flashing ROM's until some good tweaks are developed. Basically all of the tweaks you would make to a normal ROM have now become built into Android.
Click to expand...
Click to collapse
Your forgetting about an important aspect which is tethering..
^^^^that will be taken care of by simply using HTCdev then flashing SU
@imheroldman
Good point about flash_image GUI and writing to system from within android. I know that hasn't happened yet for one x. It must be locked differently than 3d. But swagstr wrote that on 3d they could use flash image to flash recovery and kernel, but couldn't use ROM Manager (which I would never use) cuz they can't write to /system from within Android. Interesting puzzles.
sent from 2yr old Evo on ICS

[CHALLENGE] Disprove HTC's statement that ICS updates will require repartitioning

TL;DR: Basically, here is a challenge to all XDA developers: Disprove HTC's statement that ICS updates will require repartitioning or factory reset. If we succeed, HTC will be stuck in a rock and a hard place.
We're getting a major uproar and petition over HTC's refusal to update the Desire HD, and all we get from it is a statement from a PR team giving us these reasons:
For more background, due to how storage on the HTC Desire HD is partitioned – and the larger size of Android 4.0 – it would require re-partitioning device storage and overwriting user data in order to install this update. While technically advanced users might find this solution acceptable, the majority of customers would not. We also considered ways to reduce the overall size of the software package, but this would impact features and functionality that customers are currently using. Even after installing the update, there were other technical limitations which we felt negatively impacted the user experience.
Click to expand...
Click to collapse
For the uninitiated journalist, it seems legit. I mean, we all had to do a factory wipe before trying out XDA's ICS ROMs, right?
However, I don't think a single person on this forum has had to repartition their system to get even Sense 4 ICS, much less Sense 3 ICS working well. And if they had to drop a feature from gingerbread stock to update, just what kind of massive bloatware are they adding in?
I question the validity of this statement, and many others on XDA feel the same. But if we don't counter their argument, the general public will just grudgingly accept it.
-------------------------------------------
So, XDA, here is a list of challenges for you to complete.
1. Create a Sense 3 ICS ROM within the existing partition size that keeps all existing functionality from the stock Desire HD.
2. Try a test case where we flash over a 2.3 stock ROM with that ROM without data loss or factory reset.
The other challenges are nice touches, but the first two will be enough to reveal the fallacy of their statements.
3. (if needed) Create a method to repartition the user and system data through OTA update
4. Provide examples of phones with similar specs or partitioning scheme that have been successfully updated to ICS, or at least have promises
5. (EXTRA CHALLENGE) Provide an example of a phone that has an OTA update that repartitions the internal memory
---------------------------------------------
Here are some useful notes that I or other users here have brought up:
1. We will need to find or create a stock-quality ICS ROM that retains all functionality of the existing gingerbread stock, and adds even more apps to accentuate the point. The stock Incredible S ICS ROM is a good start. Better yet, I haven't seen a single rom on this forum that goes over the limit.
2. Factory resets are recommended when switching ROM types, but I think it will be okay to go without for stock ROMS.
3. Take a look at Libparted from Linux, it is constantly used for repartitioning without risking data loss and has been used to good effect on other devices.
4. The Incredible S currently has ICS rolling out, and it is very similar, down to the system partition which is only larger by 3.5 KiB. Why this and not the Desire HD?
5. This is the only truly difficult challenge here, repartitioning in an OTA update is something that has not been done before in recent memory. If you can't find it, create a method to repartition.
-------------------------------------------------
Just for kicks, what is the real reason that HTC isn't updating? A combination of cost and planned obsolescence. The reality is that system updates for smartphones cost a lot to make and get FCC certification. Then the update has to be up to standards unlike our custom ROMs. With the amount of phones they have thrown out into the market, that adds up to a massive sum.
Finally, keeping phones updated just doesn't make sense to shareholders or the CFO, who have to justify going above and beyond to give more features to old phones when 1) HTC has sold you everything they advertised, 2) Few other manufacturers do the same, and 3) It dissuades customers from paying more for the latest and greatest. HTC did not sell you an upgrade service, they sold you a phone designed for Android 2.2.
The importance of software updates are a new thing to a company that was built on hardware innovation. But this is not acceptable in the modern market, one that is undergoing a worldwide recession, and one that demands powerful new software over expensive hardware. Unless they, and the other manufacturers find a solution, HTC's dated business model will lead it to certain destruction.
---------------------------------------------------
I would try and contribute directly, but my main phone is an HTC HD2, and all I have is my grandfather's Inspire 4G, who happens to be away on a cruise in Alaska.
Totally disagree
I am totally disagree to you as what you are saying is not going to bring us nothing. Let the devs work on their started projects and ignore HTC for the future.
antonizoon said:
TL;DR: Basically, here is a challenge to all XDA developers: Disprove HTC's statement that ICS updates will require repartitioning or factory reset. If we succeed, HTC will be stuck in a rock and a hard place.
So, XDA, here is a list of challenges for you to complete.
1. Create a Sense 3 ICS ROM within the existing partition size that keeps all existing functionality from the stock Desire HD.
2. Try a test case where we flash over a 2.3 stock ROM with that ROM without data loss or factory reset.
The other challenges are nice touches, but the first two will be enough to reveal the fallacy of their statements.
3. (if needed) Create a method to repartition the user and system data through OTA update
4. Provide examples of phones with similar specs or partitioning scheme that have been successfully updated to ICS, or at least have promises
5. (EXTRA CHALLENGE) Provide an example of a phone that has an OTA update that repartitions the internal memory
Click to expand...
Click to collapse
LOL that seems like a good idea, call htc on their bluff!
I might give it a try, it shouldn't be too hard to do. Just put back a stock ruu, install a stock (ported) ics from sxl/ds/Inc's with bloat without wipe, done!
Edit: although wisperhack is correct, it's not going to make htc change their mind it is okay for a bit of fun
Sent from my Galaxy Tab 10.1 using XDA Premium HD app
scaryshark said:
LOL that seems like a good idea, call htc on their bluff!
I might give it a try, it shouldn't be too hard to do. Just put back a stock ruu, install a stock (ported) ics from sxl/ds/Inc's with bloat without wipe, done!
Sent from my Galaxy Tab 10.1 using XDA Premium HD app
Click to expand...
Click to collapse
You will prove nothing. They refer to send ICS over GB.
whiperhack said:
I am totally disagree to you as what you are saying is not going to bring us nothing. Let the devs work on their started projects and ignore HTC for the future.
Click to expand...
Click to collapse
Let each person/dev decide what they want to do. Besides, if someone does manage to do it, it's bad PR for them. If someone wants to take this upon themselves, they are free.
Sent from a dream.
lol it would be better to work on the camcoder bugfix rather than to port sense 3 with ICS...
whiperhack said:
I am totally disagree to you as what you are saying is not going to bring us nothing. Let the devs work on their started projects and ignore HTC for the future.
Click to expand...
Click to collapse
While you might be right, that HTC will not even respond to the attempt, I strongly support it, since dropping ICS on a worthy Desire HD sets a bad precedent for their policies in the future. Our petition means little if HTC convinces enough end users that ICS will lose their data or features, as they seem to be grudgingly accepting.
I am not demanding that developers take their time away from their existing projects, (in fact, if you are working on other things, just skip this challenge entirely) I am asking that we show HTC and the users that OTA ICS updates can be installed safely without even bothering with repartitioning, as we've been doing for years on end.
I will try this challenge out myself as a long-awaited first foray into ROM development, as soon as I have a chance.
shad0wboss said:
lol it would be better to work on the camcoder bugfix rather than to port sense 3 with ICS...
Click to expand...
Click to collapse
It would be, but repackaging a ROM and fixing driver problems are different beasts. Also, I'm not all that in favor of taking extra work to port Sense 3 ICS either (Sense 4 ICS would be okay too), just that it would be closer to HTC's projected plan like the Incredible S and Sensation XL.
antonizoon said:
It would be, but repackaging a ROM and fixing driver problems are different beasts. Also, I'm not all that in favor of taking extra work to port Sense 3 ICS either (Sense 4 ICS would be okay too), just that it would be closer to HTC's projected plan like the Incredible S and Sensation XL.
Click to expand...
Click to collapse
Mate, those multinational companies aren't affected by anything. Even if they loose 30,000 - 40,000 HTC members, they would have millions who actually received ICS update and would definitely go for another HTC phone...
A custom rom will prove nothing. The fact that a GB rom can be overwritten by an ICS one is proved by HTC themselves by upgrading other models. What we need to do is compare directly the partitions of the DHD with same specced devices that run ICS, like the Desire S and the Incredible S. If their system partitions are similar in size to ours, we prove again that HTC is lying.
The thing is, IMO we should not fight for the update that much. We should bring this to the attention of the media and not only tech sites. The consumers must know how blatantly HTC are lying to the consumers. People must learn who they are and stop supporting them for false promises.
Personally I don't care that much about the update anymore. AOSPX is stable enough for my daily needs and by discovering their lies on top of their attempt to cover them with more lies makes me sick of that company.
Let's join forces to protect innocent consumers around the world before they discover HTC's lies the same way we do and also protect people who won't be able to understand their lies and fall in their traps to buy new hardware when it's not needed.
Sent using xda app-developers app
tbh this idea is really good but we cant do anything about htc releasing or not relasing the rom
developers over here are more dedicated to work,in my opinion,then to prove something to other..
as said by another member that htc is multinational company blah blah,that a fact and i agree with since htc still still didnot lose me as customer coz i love htc sense and i cant do anything about it desire hd is an old device if we still look at other devices of that time and same proce we would see that they are mostly discontinued on froyo or gingerbread , as far as the idea is concerned let just hope and pray that the rom we want is perfect and finished bug free quickly ,(insha'allah),very little people on htc followers are used custom roms so it not a good idea to just make a rom which is quite difficult to make and which would have no affect on the company
Iam not saying that they should stop but just my opinion on this idea i would also love to see this being completed but y just not focus on devices and roms blah blah blah
thanks guys and just pray that the roms are 100 % completed and bug free
good luck to them working hard
p.s iam no developer just a noob
XL3N7 said:
What we need to do is compare directly the partitions of the DHD with same specced devices that run ICS, like the Desire S and the Incredible S. If their system partitions are similar in size to ours, we prove again that HTC is lying.
The thing is, IMO we should not fight for the update that much. We should bring this to the attention of the media and not only tech sites. The consumers must know how blatantly HTC are lying to the consumers. People must learn who they are and stop supporting them for false promises.
Personally I don't care that much about the update anymore. AOSPX is stable enough for my daily needs and by discovering their lies on top of their attempt to cover them with more lies makes me sick of that company.
Let's join forces to protect innocent consumers around the world before they discover HTC's lies the same way we do and also protect people who won't be able to understand their lies and fall in their traps to buy new hardware when it's not needed.
Sent using xda app-developers app
Click to expand...
Click to collapse
I agree that my original post and ideas were a bit flawed, but this man gets the gist of it: The consumers must know how blatantly HTC are lying to the consumers. If proving that they are wrong is not going to work out, what do you guys have in mind to do?
Great Idea IMHO
I think exposing whether HTC is lieing or not is a great use of time. Of course, it would be great if this could be done at a minimal cost to devs who are currently working on various ICS and JB ports for the DHD.
d3sperad0 said:
I think exposing whether HTC is lieing or not is a great use of time. Of course, it would be great if this could be done at a minimal cost to devs who are currently working on various ICS and JB ports for the DHD.
Click to expand...
Click to collapse
I completely agree
Sent from my HTC Desire HD using xda premium
antonizoon said:
TL;DR: Basically, here is a challenge to all XDA developers: Disprove HTC's statement that ICS updates will require repartitioning or factory reset. If we succeed, HTC will be stuck in a rock and a hard place.
We're getting a major uproar and petition over HTC's refusal to update the Desire HD, and all we get from it is a statement from a PR team giving us these reasons:
For the uninitiated journalist, it seems legit. I mean, we all had to do a factory wipe before trying out XDA's ICS ROMs, right?
However, I don't think a single person on this forum has had to repartition their system to get even Sense 4 ICS, much less Sense 3 ICS working well. And if they had to drop a feature from gingerbread stock to update, just what kind of massive bloatware are they adding in?
I question the validity of this statement, and many others on XDA feel the same. But if we don't counter their argument, the general public will just grudgingly accept it.
-------------------------------------------
So, XDA, here is a list of challenges for you to complete.
1. Create a Sense 3 ICS ROM within the existing partition size that keeps all existing functionality from the stock Desire HD.
2. Try a test case where we flash over a 2.3 stock ROM with that ROM without data loss or factory reset.
The other challenges are nice touches, but the first two will be enough to reveal the fallacy of their statements.
3. (if needed) Create a method to repartition the user and system data through OTA update
4. Provide examples of phones with similar specs or partitioning scheme that have been successfully updated to ICS, or at least have promises
5. (EXTRA CHALLENGE) Provide an example of a phone that has an OTA update that repartitions the internal memory
---------------------------------------------
Here are some useful notes that I or other users here have brought up:
1. We will need to find or create a stock-quality ICS ROM that retains all functionality of the existing gingerbread stock, and adds even more apps to accentuate the point. The stock Incredible S ICS ROM is a good start. Better yet, I haven't seen a single rom on this forum that goes over the limit.
2. Factory resets are recommended when switching ROM types, but I think it will be okay to go without for stock ROMS.
3. Take a look at Libparted from Linux, it is constantly used for repartitioning without risking data loss and has been used to good effect on other devices.
4. The Incredible S currently has ICS rolling out, and it is very similar, down to the system partition which is only larger by 3.5 KiB. Why this and not the Desire HD?
5. This is the only truly difficult challenge here, repartitioning in an OTA update is something that has not been done before in recent memory. If you can't find it, create a method to repartition.
-------------------------------------------------
Just for kicks, what is the real reason that HTC isn't updating? A combination of cost and planned obsolescence. The reality is that system updates for smartphones cost a lot to make and get FCC certification. Then the update has to be up to standards unlike our custom ROMs. With the amount of phones they have thrown out into the market, that adds up to a massive sum.
Finally, keeping phones updated just doesn't make sense to shareholders or the CFO, who have to justify going above and beyond to give more features to old phones when 1) HTC has sold you everything they advertised, 2) Few other manufacturers do the same, and 3) It dissuades customers from paying more for the latest and greatest. HTC did not sell you an upgrade service, they sold you a phone designed for Android 2.2.
The importance of software updates are a new thing to a company that was built on hardware innovation. But this is not acceptable in the modern market, one that is undergoing a worldwide recession, and one that demands powerful new software over expensive hardware. Unless they, and the other manufacturers find a solution, HTC's dated business model will lead it to certain destruction.
---------------------------------------------------
I would try and contribute directly, but my main phone is an HTC HD2, and all I have is my grandfather's Inspire 4G, who happens to be away on a cruise in Alaska.
Click to expand...
Click to collapse
Not very much to do anymore except for a few bugfixes. Ten we have a fully working htc sense 4.0 ics rom. I think we have made it pretty far without original 3.0 kernel. And i'm happy with what we have got now.
I say let's kidnap the HTC Devs and Marketing team and make them watch every episode of " Saved By The Bell " until they confess their sins and release ICS For DHD
Yes. I myself would like to know if there are differences with how the Desire HD ROM is partitioned differently from the Desire S and the Incredible S. That HTC won't release a ICS update for the DHD is very disappointing. But, if they lie about the reason why, that is a real slap on the face.
Sent from my Desire HD using xda app-developers app
menditsa said:
I say let's kidnap the HTC Devs and Marketing team and make them watch every episode of " Saved By The Bell " until they confess their sins and release ICS For DHD
Click to expand...
Click to collapse
or just kidnap them and make them release the ICS under the supervision of those 13,000 DHD users who signed the petition

Categories

Resources