Hi guys,
im trying to get my phone jtaged so i can finally have it rooted. are there any suggestions on the best mod to use for the g1? i know we have limited memeory and i beleive we cant even run 2.0 or 2.1 on the phone is that correct?
THanks!
does this mean we get 2.1!!!
Posted by Cyanogen in Home on May 21, 2010
A whole bunch of us have been working hard to get Android 2.1 (CM 5.0.7) running perfect on the HTC Dream and Magic phones and I think it’s nearly ready to go. This release is almost exactly the same as the Nexus One and Droid versions of CM now, minus a few of the heavier apps.
This was an incredible community effort and I hope everyone likes the result. Breathing new life into old hardware is always awesome.
I expect that a stable release of 5.0.7 should be ready for all devices in the next few days.
And after that.. Google has confirmed that Android 2.2 (FroYo) will be available for ION phones, so it’s guaranteed that CM-6 will continue to support the G1 also when the source code hits AOSP.
Cyanogen 5.0.7test7 runs pretty sweetly on my G1 and its based on 2.1
does it lag at all? are there any limitations that i should know of
I find it ok with comcache enabled, around the same speed (if not a little quicker) then the stable based on 1.6.
It is still a "test / experimental" build though, so proceed at your own risk etc...
Link to the download and details - http://forum.cyanogenmod.com/index....ic-would-you-like-a-pony-v507-test7-05222010/
Changelog for test7 - http://wiki.cyanogenmod.com/index.php/Release_Notes#5.0.7-DS-test7_.28experimental.29
omgkush said:
Hi guys,
im trying to get my phone jtaged so i can finally have it rooted. are there any suggestions on the best mod to use for the g1? i know we have limited memeory and i beleive we cant even run 2.0 or 2.1 on the phone is that correct?
THanks!
Click to expand...
Click to collapse
Running the Rom on my signature which is CyanogenMod5, latest version themed and tweaked. It is a 2.1 and is running very fast/stable so far. Major downside is the battery life however and is a bit hard to get used to vs. a 1.6 Donut Rom.
In all honesty Id say you try SuperD v1.11 (Best Donut Rom in my opinion) first and then flash the Eclair Roms later on. Sooner or later I am sure a developer will improve the battery degradation problem on the 2.1's.
vixsandlee said:
I find it ok with comcache enabled, around the same speed (if not a little quicker) then the stable based on 1.6.
It is still a "test / experimental" build though, so proceed at your own risk etc...
Link to the download and details - http://forum.cyanogenmod.com/index....ic-would-you-like-a-pony-v507-test7-05222010/
Changelog for test7 - http://wiki.cyanogenmod.com/index.php/Release_Notes#5.0.7-DS-test7_.28experimental.29
Click to expand...
Click to collapse
Its been released "stable"
omgkush said:
Hi guys,
im trying to get my phone jtaged so i can finally have it rooted. are there any suggestions on the best mod to use for the g1?
Click to expand...
Click to collapse
And what, might I ask, is a "g1"?
This phone you speak of is an HTC phone called "DREAM".
i know we have limited memeory
Click to expand...
Click to collapse
That statement is absurd. EVERYTHING has limited memory. Unlimited memory is by definition IMPOSSIBLE, even the smallest memory component possible would consume more than the total available space in the universe to produce unlimited/infinite memory. In fact, it would consume the space consumed by INFINITE UNIVERSES. Inconceivably huge, eh?
and i beleive we cant even run 2.0 or 2.1 on the phone is that correct?
Click to expand...
Click to collapse
And just where did you come up with this nonsense? Do you realize that all the chicken littles in the world will always say "your old hardware will never see this!" -- fact is that this is NOT WINDOZE!! Just because windoze phones don't get to see the newer versions does NOT mean that WE won't get to see our newer versions.
**** this guy is annoying with this rooting ****...
You push too much dude. People don't want to work on your phones cause your too pushy
You start threads about the same thing.....useless
I mean a lot of ROM's have more of the same. Basic speed enhancements, bug fixes/ compatibility changes, and maybe some graphical changes.
But with 2.2 coming out on more platforms is it possible that some of the features of 2.2 might come to the Eris? Or is the phone just not strong enough?
once the source is out new things will start coming.
Like what? We already know what's in 2.2 for the most part. What features from 2.2 could be ported to Eris?
not even sure. havent even looked at froyo or its features.
You also have to keep in mind that there a limitations to the Eris. It simply may not be able to runall of the features that new versions of android will provide.
-------------------------------------
Sent via the XDA Tapatalk App
actually we could port a froyo rom to eris and have it work. we already have kaos froyo, there are major bugs in it, which is because of the porting, not a limitation in the eris.
but once we have source code for froyo, we can build a rom off of it, and have every feature in it. we can do this for atleast the next few versions of android, as long as android doesnt require insane requirements.
Well I assume things like flash won't really be running all that great on our phones. It's only really running well on the top ones.
Also keep in mind that every new version of AndroidOS actually runs faster on each phone than the previous version and I've heard the same about 2.2.
If you look at benchmarks 2.2 is making phones run twice is fast lol but it's optimized for those phones. And isn't the reason 2.2 is running so fast partly because of JIT?, which we have.
Hungry Man said:
If you look at benchmarks 2.2 is making phones run twice is fast lol but it's optimized for those phones. And isn't the reason 2.2 is running so fast partly because of JIT?, which we have.
Click to expand...
Click to collapse
Good point, but they did make Android faster going from 1.5 to 1.6 and to 2.0 and then to 2.1 without JIT, so it's reasonable to assume they made it even at least slightly faster besides the JIT.
Yeah I think they focused on making bootup faster. The entire thing is supposed to be super optimized. I definitely would like that.
So, coming from a string of G1's and a Nexus, I cannot stand SenseUi. At ALL. I can live with the widgets and launcher- they are actually tolerable- what I cant accept are the keyboard, the way contacts are brought up, the lack of cut/paste in several areas, and all the frilly crud that goes along with it. I seek a TRUE vanilla rom, based on Android components not HTC. People constantly recommend using advanced launcher or one similar, but these are just launchers- they dont change the stuff back to stock that I seek. So my question is, can there ever be a REAL vanilla rom that has none of the Sense components? Is it possible to de-theme these areas in similar fashion to how the current de-sensing works, or would it require that HTC releases a vanilla version (which they never will). I guess I am asking, am I fighting a loosing battle?
You are coming from an N1 and asking this question?
Really?
Cyanogenmod ring a bell?
i was in the same boat as you. i am on cyanogen now, however there are a few issues with this port. on the nexus i didn't ever have any issues with cm6 but on the incredible you have to install another kernel after you install cm6 so that the camera will work, the camcorder just doesn't work yet, and when i have wifi on i get a reboot about once a day. i live with it because like you i hate sense ui but i wish they would have released a n1 for verizon. they did just release the source code for 2.6.32 which is froyo today, so the code shoulod be added into the nightlies of cm6 shortly.
It's been said that the latest radio fixes many (if not all) of those problems in Cyanogen on DInc. I can't attest to this being true or not, but some people were talking about it last night in the "Unrevoked - Forever" thread in the dev section.
cool! so there is hope. I figured the CM rom would be truly vanilla, but since it had so many little oddities I haven't given it a go yet. Good to know there is the possibility. Thanks guys
gospeed.racer said:
cool! so there is hope. I figured the CM rom would be truly vanilla, but since it had so many little oddities I haven't given it a go yet. Good to know there is the possibility. Thanks guys
Click to expand...
Click to collapse
The new .32 kernel source that was just released will also allow koush to finish CM6 for the incredible. Basically now that this new kernel is out the bluetooth stack and everything else including the camcorder not working in CM6 will all work once implemented.
Even though the bluetooth works perfect in CM6 unlike normal senseui roms. /letting out BT steam
...
I wonder when this will be ready?
So, let me start off by saying that I have searched, read and spent time trying to understand this... but still don't. Which answers why I'm posting this question.
First, what exactly is the reason that an AOSP rom is being developed and a Vanilla Froyo ROM is being developed?
Is the AOSP rom the important one here? Does the working AOSP rom with working kernel mean that we would have 2.2, 2.3.... and so on supported regardless of Samsung?
I understand that Samsung has not supported tremendously up to this point, I understand 2.2 has not been released for the CDMA version yet, and I understand the code they have released is "crappy." When I hear everyone talk about the great work the devs are doing, are they referring to mainly working on the AOSP? If this rom is built, will we be able to just keep developing it for the new versions of Android?
Sorta like in Back to the future when they break off the real timeline and go into the alternate 1985?
Samsungs Android - 2.1, 2.2.... EOL
Dev's Android - 2.1, AOSP, 2.2, 2.3?
Is this how it works? Basically just trying to understand what needs to happen for the Fascinate to get to at least 2.3... not WHEN or even IF it'll get to 2.3.
Thanks
AOSP means Android Open Source Platform.
It's a version of Android built entirely from sources provided by Google. It's completely Vanilla and comes with zero customer or manufacturer customizations. It's easily root-able, and able to be customized completely by the user if desired.
AOSP ROMs are desirable because they tend to be a bit faster and lighter due to their lack of crapification.
AOSP builds are only distributed in their complete and compiled form by Google for their developer handsets (Currently the Nexus One and Nexus S), and not by any carrier or manufacturer.
Okay, I appreciate that definition... I think I've gotten what AOSP is exactly... but I guess my question is does AOSP have any involvement in a future for this phone if Samsung decides to close its doors. Is a working AOSP, radio, kernel... whatever basically devs developing a future of this phone parallel to whatever Samsung does for it?
Like, I see from other threads that the ROM for Froyo and Gingerbread isn't necessarily the problem, its the radio and the RIL? If that is the case, what needs to happen for everything to figured out and for us to have a bright future for the Fascinate? Samsung has to release code for the RIL and radio? Are we SOL without Samsung helping here or will the devs definitely figure something out to get 2.2, 2.3... and so on for the Fascinate?
Bwangster12 said:
Okay, I appreciate that definition... I think I've gotten what AOSP is exactly... but I guess my question is does AOSP have any involvement in a future for this phone if Samsung decides to close its doors. Is a working AOSP, radio, kernel... whatever basically devs developing a future of this phone parallel to whatever Samsung does for it?
Like, I see from other threads that the ROM for Froyo and Gingerbread isn't necessarily the problem, its the radio and the RIL? If that is the case, what needs to happen for everything to figured out and for us to have a bright future for the Fascinate? Samsung has to release code for the RIL and radio? Are we SOL without Samsung helping here or will the devs definitely figure something out to get 2.2, 2.3... and so on for the Fascinate?
Click to expand...
Click to collapse
It's kinda like building an office park, or strip mall or something. You toss up the basic vanilla buildings, and when it's finally done, companies move in and tweak it how they deem fit.
With a working ASOP build, it'll remove some of the shackles of Samsungs bs code.
So... the AOSP build IS THE KEY here? I understand it isn't working yet, but if the devs get AOSP working, does that mean we will get a 2.2, 2.3 and so on regardless of what is released by Samsung?
I'm just trying to figure out what is happening to keep the G1, Droid, Droid 2... supported by ROMs like Cyanogenmod and others, that hasn't happened yet for the Samsung Fascinate.
I'd like to get the Fascinate, but am sorta waiting because I don't wanna be stuck with a phone for the next 2 years that will max out at MAYBE 2.2 if we are lucky.
I don't know where to start with your confusion.
Samsung has not given 2.2 to us. This means that we do not have froyo...
The RIL is an interface layer between the os and the radio. I'm not too sure about it, but anyways...
The developers are working around the fact that samsung has not given further tools that they need to get froyo ported over. Currently they are working on a 1.6 RIL to get froyo working. On another note, vanilla aosp is a good thing because it gives developers more freedom to customize the roms. It also allows for them to be able to port over other roms.
I really don't understand your confusion. If you want a better explanation , I recommend getting on irc.
If I were you, I'd wait. Next gen phones are coming from vzw in the next few months which will essentially blow the existing tech soon.
Bwangster12 said:
So... the AOSP build IS THE KEY here? I understand it isn't working yet, but if the devs get AOSP working, does that mean we will get a 2.2, 2.3 and so on regardless of what is released by Samsung?
I'm just trying to figure out what is happening to keep the G1, Droid, Droid 2... supported by ROMs like Cyanogenmod and others, that hasn't happened yet for the Samsung Fascinate.
I'd like to get the Fascinate, but am sorta waiting because I don't wanna be stuck with a phone for the next 2 years that will max out at MAYBE 2.2 if we are lucky.
Click to expand...
Click to collapse
Basically, that's the hope at least. If there are changes in say, 2.4 that require something that couldn't be hacked around with ASOP, we'll be stuck waiting for Samsung. But with a working ASOP, the groundwork is laid for updates to be ported over a bit more quickly by the devs.
Regardless of the future of this device, the Fascinate is one of the better Android handsets on the market. The screen is brilliant, it's the perfect size, and it's damn fast. The only thing that drags it down is the factory setup (although I personally think it's idiotic to ding the phone because of the inclusion of Bing like some people/reviewers have.)
I'm trying to understand what is going on instead of being one of the millions to ask about updates for this phone. I see phones like the droid series and read that they basically are being supported forever and then I see the Samsung Fascinate, and while I understand that the code is crappy/not released to community... I'm trying to figure out what needs to happen for it to be a supported device like the droids have been.
Bottom line, nothing at all is going to happen unless Samsung releases more than just a 2.2 update? If I see 2.2 drop like tomorrow, does that mean anything for a future, or is it just 2.2 update and we will just get devs releasing their versions of 2.2 roms?
RacerXFD said:
I really don't understand your confusion. If you want a better explanation , I recommend getting on irc.
Click to expand...
Click to collapse
I read his questions as:
"Will a working ASOP build mean better developer support/faster developer released updates?"
I did skim them though.
RacerXFD said:
If I were you, I'd wait. Next gen phones are coming from vzw in the next few months which will essentially blow the existing tech soon.
Click to expand...
Click to collapse
This is a good point. There's an LTE Samsung handset coming out soon, so it might be worth holding out for a little.
Although the Fascinate is no slouch.
Pretty much what I am asking. Like of everything that could possibly happen, Samsung releasing 2.2, AOSP being finished, blah blah what is the key that a consumer should look for to say...
"Well, now the Fascinate has no negatives to it and I have no fear that in a year, we won't still be stuck on 2.1 or 2.2 because Samsung screwed us."
Doesn't necessarily seem like Samsung needs to do MUCH to future this phones life and turn over the keys to the devs (like HTC seemingly has done), but I'm trying to understand what that thing is they need to do. Release a newer kernel, RIL, 2.2 ROM, some code that magically allows devs to port over future roms eternally...
I don't think I care if the phone has LTE capability. I won't get LTE and a regular 3G phone is beyond enough for me. LTE is zero impact for me.
Bwangster12 said:
Pretty much what I am asking. Like of everything that could possibly happen, Samsung releasing 2.2, AOSP being finished, blah blah what is the key that a consumer should look for to say...
"Well, now the Fascinate has no negatives to it and I have no fear that in a year, we won't still be stuck on 2.1 or 2.2 because Samsung screwed us."
Doesn't necessarily seem like Samsung needs to do MUCH to future this phones life and turn over the keys to the devs, but I'm trying to understand what that thing is they need to do. Release a newer kernel, RIL, 2.2 ROM, some code that magically allows devs to port over future roms eternally...
I don't think I care if the phone has LTE capability. I won't get LTE and a regular 3G phone is beyond enough for me. LTE is zero impact for me.
Click to expand...
Click to collapse
What does SAMSUNG need to do? Release their source code, and not just incomplete parts of it.
Will that happen? I doubt it, but it might. Clearly the companies ears are perking up with all the yelling by the consumers.
What can we do in the meantime? Support the devs and wait for them to crank out a working ASOP build and Froyo.
Yes, would be nice to have a fully working AOSP build, and then Froyo... but they are seperate from each other right?
AOSP build is being done for 2.1? It can't just be magically updated to 2.2 can it? Does Froyo have to be officially released for them to update it to AOSP 2.2?
Basically... AOSP will only be updated to whatever version Samsung has released?
Bwangster12 said:
Yes, would be nice to have a fully working AOSP build, and then Froyo... but they are seperate from each other right?
Click to expand...
Click to collapse
No. Android Open Source Project means "Android" in general. It can be 2.1, 1.6, 2.3, whatever. The devs elected to start with 2.1.
AOSP build is being done for 2.1? It can't just be magically updated to 2.2 can it? Does Froyo have to be officially released for them to update it to AOSP 2.2?
Click to expand...
Click to collapse
If you've followed anything in the dev folders, clearly not. JT's "Vanilla" Froyo looks like an AOSP build.
Basically... AOSP will only be updated to whatever version Samsung has released?
Click to expand...
Click to collapse
No. At least not our version.
Bwangster12 said:
Yes, would be nice to have a fully working AOSP build, and then Froyo... but they are seperate from each other right?
Click to expand...
Click to collapse
It's hard to answer your question because AOSP and Froyo refer to two completely different things, which can be the same or separate.
AOSP is basically Android, built from clean, unmodified source code directly from Google, without any changes by carriers or manufacturer.
Froyo is simply the 2.2 version of Android.
So, you can have Froyo that's modified by a carrier and/or manufacturer. This wouldn't be AOSP. And you can have Froyo, built directly from Google code. This would be AOSP. You can also have Eclair (Android 2.1), or any other version of Android that's AOSP or not AOSP depending on whether it was built directly from Google code, or modified by a carrier or manufacturer.
AOSP doesn't refer to a single, particular version of Android, but the state of the code that was used to compile whatever version you want to talk about.
Bwangster12 said:
AOSP build is being done for 2.1? It can't just be magically updated to 2.2 can it? Does Froyo have to be officially released for them to update it to AOSP 2.2?
Click to expand...
Click to collapse
A lot of the issue surrounds the kernel. When Google releases a new version of Android, it runs on a particular version of the kernel, which supports it's particular features. Manufacturers have to modify the kernel to support their particular hardware. So, since Samsung has only released source code for the kernel for Android 2.1, we're stuck on 2.1.
The versions of 2.2 from Kaos and JT are running on the Android 2.1 kernel that's been hacked to enable 2.2 to boot and run correctly. It works, but it's far, far from ideal. It doubles (if not more) the amount of work necessary to get 2.2 running, which is the reason for the rather slow pace of development.
So for your question, once Samsung releases 2.2 (the system and kernel), it'll be much easier to get an AOSP build of Android running, since the devs will only need to worry about the system instead of hacking together a kernel and RIL (radio interface layer) as well.
At least this is my understanding of the situation. I'm sure people with more knowledge and experience can correct me where I'm wrong, but I think this is the basic gist of it.
ChrisDDD said:
It's hard to answer your question because AOSP and Froyo refer to two completely different things, which can be the same or separate.
AOSP is basically Android, built from clean, unmodified source code directly from Google, without any changes by carriers or manufacturer.
Froyo is simply the 2.2 version of Android.
So, you can have Froyo that's modified by a carrier and/or manufacturer. This wouldn't be AOSP. And you can have Froyo, built directly from Google code. This would be AOSP. You can also have Eclair (Android 2.1), or any other version of Android that's AOSP or not AOSP depending on whether it was built directly from Google code, or modified by a carrier or manufacturer.
AOSP doesn't refer to a single, particular version of Android, but the state of the code that was used to compile whatever version you want to talk about.
A lot of the issue surrounds the kernel. When Google releases a new version of Android, it runs on a particular version of the kernel, which supports it's particular features. Manufacturers have to modify the kernel to support their particular hardware. So, since Samsung has only released source code for the kernel for Android 2.1, we're stuck on 2.1.
The versions of 2.2 from Kaos and JT are running on the Android 2.1 kernel that's been hacked to enable 2.2 to boot and run correctly. It works, but it's far, far from ideal. It doubles (if not more) the amount of work necessary to get 2.2 running, which is the reason for the rather slow pace of development.
So for your question, once Samsung releases 2.2 (the system and kernel), it'll be much easier to get an AOSP build of Android running, since the devs will only need to worry about the system instead of hacking together a kernel and RIL (radio interface layer) as well.
At least this is my understanding of the situation. I'm sure people with more knowledge and experience can correct me where I'm wrong, but I think this is the basic gist of it.
Click to expand...
Click to collapse
Okay, thank you for this answer... this makes sense to me.
So, have HTC and Motorola released newer kernels for the devs of roms like Cyanogemod to update their ROMs, despite HTC and Motorola not actually releasing newer versions? I mean, how is the G1 updated as far as it has. Did HTC release a 2.2 kernel to allow devs to put 2.2 on it?
That's were I'm start confused as well.
I understand that Samsung has some proprietary kernel level code and drivers.
But, I'm curious what is the difference between Linux kernel versions used for different versions of Android. It doesn't sound like major version change and hence should not change anything dramatically. It should be mostly bug fixes. That's why jt was able to get kernel work.
As in relation to ASOP for SF, I see it like attempt to adapt Samsung code to current android interfaces. Once again, these interfaces should not change dramatically between versions, because these are evolutionary. So, I assume when done it is pretty much paved road up to 3.0 at least. That said some new features might not work at all, because we do not have working initial binaries from Samsung.
By the way mrbirdman has GB in progress.
Alright... so this may sound like I'm oversimplifying it, but I don't mean to.
Why can't the dev community just create a "custom" kernel to work with their versions of 2.2, 2.3 and so on? You say that they are working to hack the 2.1 kernel Samsung has released so it allows 2.2 to run on the Fascinate... but why can't they just make a 2.2 kernel? Is that sorta what Cyanogenmod is doing to get a 2.2 Froyo build to work on a G1?
Based on the amazing things I've seen the dev community do, building ROMs from scratch, I guess I don't understand how the kernel can't be built specifically for each new version... forgetting about what Samsung releases.
Bwangster12 said:
Why can't the dev community just create a "custom" kernel to work with their versions of 2.2, 2.3 and so on?
Click to expand...
Click to collapse
Theoretically they could, it would just be a lot of work. Hardware drivers might not be compatible with the kernel version designed for 2.2 or 2.3. I don't think manufacturers are required to release the code for their drivers, so if a driver wouldn't work, one would need to be written from scratch, and without the detailed knowledge of the hardware itself, that is very difficult.
Hardware support is very integral to the kernel, so a kernel for one phone wouldn't run at all on another. So in addition to the difficulty of putting together a totally independent kernel, it would need to be done separately for each and every phone out there, and how many versions of the Galaxy S alone are there? How many HTC phones, how many Motorola and LG and Sony and so on.
It's just not realistic for people doing this, essentially, in their spare time.
So, what the devs generally do is wait until a carrier releases a version of Android (System, kernel, radio, etc.), and with all the hardware support in place and working, they can focus on building custom or AOSP versions of the system.
It's not that they couldn't build their own kernel, it's just a matter of practicality, audience and the shelf live of the particular phone. As it is, a new generation of phones are already either coming out or on the near horizon... and our phone is what, 4 to 5 months old?
Bwangster12 said:
Based on the amazing things I've seen the dev community do, building ROMs from scratch, I guess I don't understand how the kernel can't be built specifically for each new version... forgetting about what Samsung releases.
Click to expand...
Click to collapse
The misunderstanding is in the complexity of compiling a custom system, and developing a custom kernel. They are hugely different in terms of complexity.
Think of a ROM as taking Windows 3.1 and simply tweaking the components that are installed by default - what accessories are installed, what wallpaper is selected, the color scheme of the windows. Not terribly complicated.
Think of the kernel as having to compile DOS, complete with custom drivers for all the hardware - CPU, graphics, memory, storage, multitouch, sound, radio, modem, WiFi, networking, power management, USB support, file system support, etc. all by hand.
After the update to 2.2.1 I didn't see any speed improvement whatsoever (well at least not 5x more speed then 2.1).
So is there really JIT enabled in the official 2.2 update for the Wildfire?
No, it isn't. JIT is apparently very unstable on Sense based ROM's.
Well that is a big minus for HTC. WhyTF don't they do something about this? There supposed to be smart people working at HTC so they can provide us (the HTC products buyers) with a fully featured ANDROID smartphone.
This just sucks. I don't want to think that I have a branded phone, a sense branded one that is, with a customized original android update so that the sense crap can run.
I hope that the rooting problem will be solved soon.
That's rather unfortunate in your case, but, if you would have read the forums,many people have actually reported slowdowns after installing the official 2.2.1 update. Besides, we are Wildfire users, and, at the bottom of the ladder, so I don't really think they will be devoting a lot of time to the Wildfire.
Anyway, well, as you put it, you will have to wait till 2.2.1 is rootable.
Just a little question: the custom roms like wildpuzzle and cyanogenmod, do they have jit enabled, since they aren't sense based?
Thank you in advance,
Erwin
Wildpuzzle is Sense based. Cyanogenmod is JIT enabled
Michealtbh said:
Wildpuzzle is Sense based. Cyanogenmod is JIT enabled
Click to expand...
Click to collapse
Cm has option to enable jit, but it is disabled by default
Sent from my HTC Wildfire using XDA App