International firmware update - Sprint HTC One (M7)

Hey all,
So after trying to figure out why my camera won't focus where I tell it to, it seems that there was an international One update about a month ago that made improvements to the camera, as well as updating it's firmware. While reading the article, it was unclear whether or not that update was applied to the Ones that were to be sold in the US before release day.
Does anyone have some info on this? Can we expect this update sometime soon, or has it already been applied?
Edit: Well it seems there are multiple updates involving the camera (and a few other goodies) http://tech2.in.com/news/smartphone...ttery-life-improved-camera-performance/872234
How long does it take for sprint to rollout updates?

roflhorse said:
Hey all,
So after trying to figure out why my camera won't focus where I tell it to, it seems that there was an international One update about a month ago that made improvements to the camera, as well as updating it's firmware. While reading the article, it was unclear whether or not that update was applied to the Ones that were to be sold in the US before release day.
Does anyone have some info on this? Can we expect this update sometime soon, or has it already been applied?
Edit: Well it seems there are multiple updates involving the camera (and a few other goodies) http://tech2.in.com/news/smartphone...ttery-life-improved-camera-performance/872234
How long does it take for sprint to rollout updates?
Click to expand...
Click to collapse
We have the updates already..What we are waiting for now is the capacitive button fix..I honestly can't believe a update for the buttons has taken this long..(Im not a Samsung fan) but they got a pretty quick update after release to fix small issues.

I'm not sure if any of the updates were included with the US version. My camera seems fine, my "back" button, however, is a mess. It barely works, takes 2-3 presses sometimes. I put a freezer bag on my phone at work to keep metal shavings off of it (due to the 100% lack of a good pouch available) and the back button is non responsive through the bag. I have read it's the same way with a screen protector.
So, hopefully we will be getting an update soon to fix this, and whatever other issues people are having.

That's odd. I never have an issue with any of my buttons
Shifted from the ONE

heres what you can do guys, extract the rom.zip out of the RUU for the international update, decrypt the rom.zip which will give you output.zip. remove and replace any frameworks, modules, binaries, etc... as per instruction on the Porting any ROM to Sprint thread. be sure to remove any radio, hboot, modem, etc... images before flashing. hope this fixes your issues, but i haven't even heard of any of those issues prior to this thread. :\ good luck! may the droid be with you

Tilde88 said:
heres what you can do guys, extract the rom.zip out of the RUU for the international update, decrypt the rom.zip which will give you output.zip. remove and replace any frameworks, modules, binaries, etc... as per instruction on the Porting any ROM to Sprint thread. be sure to remove any radio, hboot, modem, etc... images before flashing. hope this fixes your issues, but i haven't even heard of any of those issues prior to this thread. :\ good luck! may the droid be with you
Click to expand...
Click to collapse
Really?... Cause the capacitive buttons being a crapshoot has been on numerous threads. It's a hugely known problem.
The camera though is new to me.
Sent from my HTC One

+1 on the buttons being wonky. Proven issue and supposedly fixed with the international update. Some people may not notice it simply becuase they naturally hit the sweet spot so to speak since the touch footprint of the button is sort of small.

The back button works best for me when I swipe it instead of pressing..

I see several of the issues the int'l update was supposed to fix. I don't think we have it. I emailed HTC about some issues I've had and their canned response seems like they're already it but no eta.
Sent from my HTCONE using xda app-developers app

Related

Is Froyo (FRF50) official - or just an "accident"?

I have updated my stock 2.1 N1 to Froyo (Build FRF50) manually. I'm wondering, though, if this release is really meant to be the official, final Google-supported update.
Is there any word from Google (except for MG Siegler's "The roll out to Nexus One devices has begun!" over at Seeking Alpha) that this is the one?
Same question here. Also if this turns out to be a pre released update, can the stock N1 be updated to a official version?
from what i understand there is no actual official word. That said im loving froyo: As with previous updates, froyo added features and bug fixes and also brought some new issues, so if you are thinking maybe its not official because of some bugs, to me that wouldnt be sufficient evidence: I havent experienced any of the complaints save one- Anyone else having the phone randomly go to sleep and not wake up?
The scrolling,
updated native apps (youtube is amazing now),
overall speed increase,
awesome camera/camcorder updates,
very smooth BETA flash,
simple and effective tethering,
fantastic new setting options throughout the OS,
left AND right rotating
updated UI (love the phone/app drawr/ browser buttons)
and im sure im forgetting stuff...All extremely awesome features and my personal new issues of freezing and hard sleep i can live with i just hope they arent harmful.
i't doesn't feel like a complete FroYo. I have little bugs that i noticed. screen goes black and don't go on anymore, have to take out battery. When the phone is in the charger and i'm playing with it, It gets really really hot.
The new features are great i miss some CM tweaks The UI was a little different at the IO so maybe there will be more surprises?
this was a prerelease to the developer holiday phone the official is coming out around the 29th of may and will continue to roll out till all nexus ones have the update
jdmoore81 said:
this was a prerelease to the developer holiday phone the official is coming out around the 29th of may and will continue to roll out till all nexus ones have the update
Click to expand...
Click to collapse
How do you know this? also will we get that update too?
Well the "leaked" URL was pulled, wasn't it?
this was very likely to be a pre test release. I've looked into the build.prop and there are signs that it is a test release as the word test appears several times throughout.
Given the silence from Google, and the subsequent removal of the link, I suspect this was an accident... meant it to go to a select few whilst forgetting how easy it was to distribute the location of the update.zip.
Wouldn't bother me any if this was the official ... its flawless for me. No freezes or any wierd stuff. Pure froyoness
m00moo said:
this was very likely to be a pre test release. I've looked into the build.prop and there are signs that it is a test release as the word test appears several times throughout.
Click to expand...
Click to collapse
Thnx for the info, so this is a test version. felt that way
Rusty! said:
Given the silence from Google, and the subsequent removal of the link, I suspect this was an accident... meant it to go to a select few whilst forgetting how easy it was to distribute the location of the update.zip.
Click to expand...
Click to collapse
So the link is gone than it's definitely a accident.
I'm gonna say this ain't the final release. But I doubt it'll be any diff. How much more could they fix or improve from the accidental release to the real one.... I bet the same bugs people are seeing now will be present in the final...
Nothing's perfect
Except for me.lol no issues
oh dear... not so good if this is true!
I spose people on here flashed the update.zips from xda?
Hopefully Google will push out the live update now certainly with the potential problems people could be getting
No, I flashed with the file direct from Google before the link was pulled.
So it's all over the news Nexus has froyo now but has anyone with a legit locked stock phone actually gotten it? Like one of the ATT folks?
Anyone have any links to some real clarification on this?
No stock AT&T/Vodafone customer can get it yet.
Zenoran said:
So it's all over the news Nexus has froyo now but has anyone with a legit locked stock phone actually gotten it? Like one of the ATT folks?
Anyone have any links to some real clarification on this?
Click to expand...
Click to collapse
No, I am one of the many AT&T folks that is still waiting for the official release from Google. I have a 3 week old N1 that is still stock and with locked boot loader, and I have no problems waiting, as I am not ready to root my new N1 just yet.
the official will we the frf86 as seen in a couple threads this version will work fine for the holiday version of the nexus one . i tried it on both the holiday nexus one and the official release of the nexus one and it runs better for some reason on the holiday version
Where are you getting all the info from?
Is there likely to be much added between FRF50 and FRF86?
How SO we know if its a holiday one?

Boy, the leaks dried up.

For a few weeks there the leaks where coming one a week, sometimes two. Now nothing. Wonder if its the calm before the OTA storm.
This is just another piece of evidence in my theory that someone somewhere has made it their job to sit there and **** with the hackers and modders all day long.
The thought has crossed my mind to just go back to 100% stock, but I'm just too addicted to having at least root.
If you ever installed any of the leaks, there is no going back to 100% stock.
stevessvt said:
For a few weeks there the leaks where coming one a week, sometimes two. Now nothing. Wonder if its the calm before the OTA storm.
Click to expand...
Click to collapse
Generally, traffic like we've seen means one of a few potential things.
First, a specific phase in dev is complete. The testers provided, information/confirmation of results and they are moving on to next phase.
Second, they are now in a bake period, letting it sit ages days before processing for release.
Third, it's is ready but don't want to release with Razr. Normally multi releases are no big deal but they have a nice budget for advertising and are releasing in multiple formats. They may want to have some focus.
My guess is 2. 8 weeks post release is still early for an ota, so they have time. Reading up in the results of the ota seems to indicate a fair amount of success. Some last minute fine tuning may be in order. I doubt they want to stretch this to the week of thanksgiving...so its next week or december. Just my opinion
I'm just glad they leaked what they did. Really helped me not smash my Bionic into little tiny pieces. I hope they are still working on it because there are still problems with it.
The leaks have stopped bc they have pushed out a final release candidate till the next update.
Sent from my DROID BIONIC using xda premium
papi92 said:
The leaks have stopped bc they have pushed out a final release candidate till the next update.
Sent from my DROID BIONIC using xda premium
Click to expand...
Click to collapse
I got crucified on another forum for suggesting multiple releases. They might burn you in effigy.
One other factor is that the devs working on it are likely playing their cards much closer to their chest, now that Motorola seems to be actively working to counter the efforts of developers. So, I suspect many things are going on with the devs, and likely releases are being found, but they're not being discussed.
MODERATOR MESSAGE
alodar1 said:
I got crucified on another forum for suggesting multiple releases. They might burn you in effigy.
Click to expand...
Click to collapse
I really dont mind a little OT on my forums, as long as its civilised
stevessvt said:
If you ever installed any of the leaks, there is no going back to 100% stock.
Click to expand...
Click to collapse
Cant you get back to stock by running moto-rooter fastboot?
2fast4u89 said:
Cant you get back to stock by running moto-rooter fastboot?
Click to expand...
Click to collapse
With a locked bootloader, No. You can restore the stock system but the radio and kernal cant be rolled back because the update only goes one way.
r0ckstar323 said:
With a locked bootloader, No. You can restore the stock system but the radio and kernal cant be rolled back because the update only goes one way.
Click to expand...
Click to collapse
I disagree. As I recall (I haven't done it with the latest file format from Motorola) you can reset the entire phone using the fastboot restore files no matter what version of kernel/BP you have.
You start by flashing the "cdt.bin" file first. This resets the signatures that are verified on all of the other partitions.
Then do the entire set of files which will completely reset all of your partitions on the phone + the BP code.
If it's not CDT.bin first, then it's 1 of the other partitions, then the CDT.bin, and then the whole set of files.

[Q] Why no Honeycomb OTA on this unit?

WiFi S7 with 2.2.2
Bought in July - works fine but I'd like Honeycomb. Apparently others have gotten it OTA already. I check for updates and get nada...
Why not this one?
What rom do you have installed?
noguru said:
WiFi S7 with 2.2.2
Bought in July - works fine but I'd like Honeycomb. Apparently others have gotten it OTA already. I check for updates and get nada...
Why not this one?
Click to expand...
Click to collapse
Yeah, mine is the same. Several other people noted the same thing, and curiously still it does not have the OTA even though the official one works just fine. Look in Settings, I suspect you have a 338.
Probably the best thing to do is go over to where DJ Steve is now and install his latest ROM.. I am soon, but right now there's some weird problem where the display blinks randomly so I'm waiting for that to get figured out.
Why go through the extra steps of a rom when you can just force the official one on your DS7. It's been posted. Pop this in your browser:
http://mobileupdate.dell.com/?version=GLUNB1A334430
dbpaddler said:
Why go through the extra steps of a rom when you can just force the official one on your DS7. It's been posted. Pop this in your browser:
http://mobileupdate.dell.com/?version=GLUNB1A334430
Click to expand...
Click to collapse
Because Steve's ROM is much better than Dell's, obviously.
Yeah, that's why his thread hasn't been touched since august 29th with zero updates since a bit before then. Once official HC hit everyone NV flashed back to stock and updated to official HC. But I'm sure you're right. A ported Xoom dump of 3.2 modified to work on the DS7 is going to be better than the official version made for it.
Sent from my SPH-D700
dbpaddler said:
Yeah, that's why his thread hasn't been touched since august 29th with zero updates since a bit before then. Once official HC hit everyone NV flashed back to stock and updated to official HC. But I'm sure you're right. A ported Xoom dump of 3.2 modified to work on the DS7 is going to be better than the official version made for it.
Click to expand...
Click to collapse
um.. Yeah. Look again, the mods here closed his thread because he couldn't provide the kernel source he's using. So he's on another forum now, with a large number of people using it. It's based on the official version, better setup, kernel, rooted, etc...
Use whatever you want.
Not that I mind standing corrected, but giving vague advice with no real direction doesn't really help the guy. You could at least point him in the right direction. Tell someone to just do "this" and assume he knows where to go or what to do doesn't really help.
There's a REASON that direct links arnt posted, since xda had issues previously with him and his source code, the right thing to do is not post direct links. (Though the sauce issue has resolved itself)
If you look at the other website they avoid linking back to xda.
Well I could care less about political crap on here and who has issues with what. If they want to flag my post, so be it. If the link is there, he can click on it.
Sent from my SPH-D700
I took the paddler's advice (and thanked).
Honeycomb works as advertised, though to tell the truth I haven't found a reason (yet) to prefer it over Froyo.
Just start roaming through the tablet oriented apps in the market. There are a few that make a difference. The one problem is if you already have vga res on your phone. The Dell just stretches it to a 7" screen, so you won't notice that much of a difference during normal use as you would if you had a 600p screen (like I have on my Evo View now, though it's only running GB).

New to the N1: Couple of introductory questions

Heyo N1 community!
So, after much deliberation, I dropped some cash on newegg for the first nexus experience...I also just needed a good backup phone.
That said, I'm probably going to be spending a lot more time here than in the Atrix forums as I'm REALLY liking the N1...and MIUI (...I'm kind of in love).
All this said, I had a couple questions about things I should be wary of...and just am not familiar with.
1. Blackrose
-From what I understand, due to the small ROM capacity, this is used to repartition the N1 to accommodate larger ROMs. I also see something about a custom HBOOT being involved. I don't really know what that is, though. Do most ROMs need this now? I was lucky enough to flash MIUI which apparently doesn't require blackrose. Granted, I don't know any of the implications of Blackrose. Is it reversible? Does it limit you in any way if you're on it?
2. Kernels
-Back on the Captivate, I feel like it was the roaring '50s with kernels. You could flash whichever kernel you wanted on whatever ROM you wanted...it was all about preference. With the Atrix, it's the opposite...doesn't help that there's basically only 1 stable kernel either. That said, I flashed the latest (non-ICS) MIUI and it looks like it comes with a slightly dated CM7 kernel- is this a big deal? Should I look to update it to something more recent/stable/etc? Or are kernels pretty specific as to ROM compatibility?
3. Radios
-Pretty much same situation with the kernels. I want to be careful because I know the N1 shipped for a couple different carriers, T-Mo and AT&T at the forefront. Now, I'm on AT&T, but the box my N1 came in is marked for Vodafone UK. As I understand it, Vodafone's freq's are the same as T-Mo's, right? Is there any difference between my "vodafone" N1 and one designed to work with T-Mo, AT&T, or any others?
4. Hardware issues/life expectancy/replacement options
-First and foremost, I'm still confused as to whether Nexus 1's are even still being manufactured. I heard somewhere that some UK carriers still sell them (obviously Google stopped doing it direct awhile ago). To me, it's the kinda thing where, in all honesty, I'd love to use the N1 as my EDC forever- the screen size is perfect for me, the Dev community is MASSIVE and very experienced, and the phone is simply iconic. That said, though, I'm wondering how long it'll be until things start to bite it and I have to look for a replacement...and if I'll even be able to find one. Alternatively, I've seen a lot of people say that HTC has been pretty forgiving about replacing busted power buttons and the like. Besides the power button, though, is there anything else I should be keeping an eye on?
Lastly, I want to thank all the Devs who've contributed. Poking around through the dev section gave me an overwhelming sense sense of options, and the conversation here seems a bit more mature than over in the Atrix forums ("WHEN WILL WE HAVE CM7/CM9?!" was almost every other thread...and the poor devs got TORN UP trying to contribute what they could).
Sorry if I blinded anybody with all the writing, but I appreciate any advice or input you can give me.
1. You don't need Blackrose for MIUI. Use A2SD and partition your SD card. How? Search. Help - Wiki link is in my signature.
2. You don't need to switch from default MIUI kernel, unless you want to overclock.
3. Doesn't matter, as long as you're on one of the Gingerbread radios. Any of the latest will be good enough. No difference in baseband builds between different N1 models.
4. You're going to eat a lot of pain with screen touch craziness, which is the most painful part of this phone. The second most painful part is sub-par GPU, but unless you game a lot, you won't notice it - MIUI is smooth. So I'm really in doubt you'll want to keep this phone for a long time. In any case, press the power button gently and closer to the inside of the phone, and avoid pressing it as much as you can (use ROMs with trackball wake and screen lock widget).
Jack_R1 said:
1. You don't need Blackrose for MIUI. Use A2SD and partition your SD card. How? Search. Help - Wiki link is in my signature.
Click to expand...
Click to collapse
Thanks for the tip. It occurs to me that I jumped the gun and flashed a ROM before I should have- not that anything bad has happened. Just thinking I'll probably go round two here shortly once I learn all the ins and outs (like Apps2SD...and popping in an SD that bigger than the included 4GB one to make it worthwhile). Thanks for the tips bro.
Jack_R1 said:
2. You don't need to switch from default MIUI kernel, unless you want to overclock.
Click to expand...
Click to collapse
Not worried about OCing. UVing might be nice...but I'm thinking unnecessary for battery life- First discharge gave me 1 day 12 hours after WHALE-HEAVY use...and even then I still had 20% left.
This is something I'm actually in awe regarding.
Jack_R1 said:
3. Doesn't matter, as long as you're on one of the Gingerbread radios. Any of the latest will be good enough. No difference in baseband builds between different N1 models.
Click to expand...
Click to collapse
Awesome. Now, real quick- did MIUI include a GB radio upon flashing it? I haven't flashed one specifically yet...should I head over to the Kernel/Radio thread and pick one out? Also, just to clarify/double-check, you're saying that a T-Mo N1 = Vodafone UK N1 etc etc? Same hardware and everything? (Obviously excluding N1's designed for AT&T's freq's?)
Jack_R1 said:
4. You're going to eat a lot of pain with screen touch craziness, which is the most painful part of this phone. The second most painful part is sub-par GPU, but unless you game a lot, you won't notice it - MIUI is smooth. So I'm really in doubt you'll want to keep this phone for a long time. In any case, press the power button gently and closer to the inside of the phone, and avoid pressing it as much as you can (use ROMs with trackball wake and screen lock widget).
Click to expand...
Click to collapse
Ha! Yep, I've definitely gotten some odd touches from the screen even after my little time with it. I've found I am ALWAYS hitting the home button...or the area that REGISTERS as the home button...whenever I go to press the space bar when typing. Quite possible it's due to having only used Android phones w/ larger, 4" screens...so I'm used to "reaching down farther" for the space bar, so to speak. And about trackball/volume wake & screenlock widget- already on it, ha! Not only is it a lot more convenient, but I figured it's something I should get used to in light of the power button's frailty.
It occurs to me- how wiggly is the trackball supposed to be? When I got my phone and started playing with it, I noticed a slight amount of give before it'd click (to select). Is this normal? While it always returns to it's normal amount of...portruding (sp?)/portrusion, should there be NO give before it clicks? Thanks for the input.
Also...about the screen...are there any mods/hacks to make it more accurate/less glitchy? Fix multitouch snapping? Etc?
Lastly, I'd always rock the V6 supercharger script on my Atrix. Now that I'm on MIUI, do they have it baked in? If not, is it compatible? Does it make a difference?
Thanks for the info/input so far bro I really appreciate it.
xyrovice said:
Awesome. Now, real quick- did MIUI include a GB radio upon flashing it? I haven't flashed one specifically yet...should I head over to the Kernel/Radio thread and pick one out? Also, just to clarify/double-check, you're saying that a T-Mo N1 = Vodafone UK N1 etc etc? Same hardware and everything? (Obviously excluding N1's designed for AT&T's freq's?)
Click to expand...
Click to collapse
No rom should include a radio, and as a general rule you should always flash radios from fastboot to avoid any problems.
xyrovice said:
Also...about the screen...are there any mods/hacks to make it more accurate/less glitchy? Fix multitouch snapping? Etc?
Click to expand...
Click to collapse
What can be done has already been done as far as tweaks.
evilkorn said:
No rom should include a radio, and as a general rule you should always flash radios from fastboot to avoid any problems.
Click to expand...
Click to collapse
Hmm...gotcha. Just wondering (as I didn't mess w/ fastboot until the Atrix- all Captivate radios were just flashed in recovery), what problems could arise from non-fastboot flashes? And how likely is this? Thanks for the info btw.
Update:
Well so I quickly checked the Radio thread, specifically the newest one (from a Korean update?).
Read and read and read and read before doing anything...then went and checked my phone only to find out the baseband version in my setting>about phone matches that of the newest one: 5.12.00.08. Don't know what difference it makes, but I have a "U" halfway through instead of an "H." So, two possibilities: Either my phone shipped with it (Odd as it's a Korea update?), or it was included in the ROM. Either way, I haven't noticed any issues, and I figure I'll leave it be.
Thanks again for the info though fellas.
I know your questions probably have been answered but I'll give it a shot:
1 - Blackrose will repartition the N1's partitions regarding cache, data, and such. If you want MIUI or pretty much any Gingerbread ROM you most likely 99.9% don't need Blackrose or a custom partition layout. Only certain ICS ROMs require Blackrose. The custom HBOOT you are referring to is Blackrose and the custom partition sizes. There are no limits if you are on Blackrose, and you can always get rid of it just as easy as installing it. Getting rid of Blackrose HBOOT will also refer you back to the stock partition layouts, if you made any changes while on Blackrose.
2 - There are a rather great deal of kernels for the N1 out there. I can think of at least 5 main ones, such as Wilmonds, IR's, and many more. Most will work with any ROM, such as CM or MIUI. But as always, backup before you flash. As for need, you don't really need to flash a custom kernel yet it can help. Some kernels boast improving animations and performance while others try to boast battery saving. Just check out the comments of each kernel's thread for a true evaluation.
3 - As for radios, flashing is not really that important. Most N1's are on 5.08 version which is the latest release for the US; all be it that is is a year or so old. There is a newer 5.12 radio released in Korea but there is no need to flash/install it. Some say connection is better but there is no difference if you are in the US. No ROM requires a certain radio.
4 - I had my N1 for almost 2 years with absolutely no issue with any buttons. I do hear that some have issues with the power button however. I guess it depends how well you take care of your device. I have dropped my phone very rarely and I take pretty good care of it. No complaints here.
Hope this helped you. And welcome to the N1 community! Any other questions feel free to ask!
Androidity3000 said:
I know your questions probably have been answered but I'll give it a shot:
...
Hope this helped you. And welcome to the N1 community! Any other questions feel free to ask!
Click to expand...
Click to collapse
Awesome info bro! Your explanation of Blackrose was especially concise, simple, and informative. Thanks for the kernel advice too! I appreciate it man!
Hey fellas, I hate to double post in the interest of bumping, but there are still a couple questions I'm still wondering about, and I'd rather bumprez than make another/2/3 different threads about each question.
The info you've given me so far has been AWESOME, and I'd appreciate any more input you might have.
Thanks in advance fellas.
What are the remaining questions?
Can't go wrong with Nexus One. Any weakness in memory can be dealt with through blackrose and a2sd. Hardware issues are minimal and even potential power switch problem is easily repaired.
Sent from my Nexus One using xda premium
Jack_R1 said:
What are the remaining questions?
Click to expand...
Click to collapse
So sorry- let me lay them out:
(And my bad for getting back to this so late- been really quite swamped with life!)
xyrovice said:
It occurs to me- how wiggly is the trackball supposed to be? When I got my phone and started playing with it, I noticed a slight amount of give before it'd click (to select). Is this normal? While it always returns to it's normal amount of...portruding (sp?)/portrusion, should there be NO give before it clicks? Thanks for the input.
...
Lastly, I'd always rock the V6 supercharger script on my Atrix. Now that I'm on MIUI, do they have it baked in? If not, is it compatible? Does it make a difference?
Click to expand...
Click to collapse
Also, I'm wondering about the AMOLED vs SLCD differences- something I don't think I've asked about yet.
Basically, regarding any and all facets of a screen- what are the differences between the AMOLED and the SLCD hardware?
And to reiterate- I'm talking about any kind of difference regarding anything, whether it's vibrancy, clarity, powerdraw, touch-sensitivity/accuracy...anything at all.
Lastly, regarding Blackrose:
So, Androidity3000 gave me a great cliff's notes on Blackrose, but I want to make sure- If I flash Blackrose (which is a custom HBOOT that reconfigures the partition sizes so as to avoid space-constraint issues?) can I just keep that all the time? Can certain ROMs NOT be flashed if I'm running Blackrose? Also, does Blackrose automatically decide the sizes of the new partitions, or do I have to configure the sizes myself? If so, are different configurations better, and why?
Thanks for all the good info and patience so far, breauxs. I appreciate it.
Trackball has some free movement, what you describe seems normal.
I've expressed my opinion on all kinds of "magical" scripts at some other point in time. Look at the free memory you have (which is probably >100MB at any given point in time), and think - do you need anything?
SLCD and AMOLED look a bit different. If you search the forum and Google, I bet you find enough examples and explanations. The question seems way too lazy.
Read the Blackrose thread to understand more, what it is and what it does. Also too lazy of a question.
I just picked up a N1 off ebay. It is in almost new condition got it for $155.00. I moving over from a mytouch 3g fender so the n1 is much better, i love it. This post helped me out alot. I've always wanted the n1 I've had my mytouch since it came out
Jeffrey.Dahmer said:
I just picked up a N1 off ebay. It is in almost new condition got it for $155.00. I moving over from a mytouch 3g fender so the n1 is much better, i love it. This post helped me out alot. I've always wanted the n1 I've had my mytouch since it came out
Click to expand...
Click to collapse
Glad to hear it bro! I like thinking that there have gotta be others with the same questions/concerns as me, and I'm glad this thread was of some use!
...AND that, as it hopefully filled you in sufficiently, you didn't feel the need to make another thread!
Enjoy the phone man!

rooting the ONE is it worth it...or should i

any one regret rooting the one ? i had a htc sensation rooted but alll the roms seem to have some thing that did not work...the one seems to be fine the way it is so before i root it i wanted some option ..... do the the htc one also have roms with broken parts of it ?
should i just wait on the updates ?
Really depends on how you use your device and how you feel about the stock setup. I didn't like having all the bloatware that AT&T packed on and really wanted to play around more under the hood, but obviously that is not for everyone and comes with all of the standard risks.
I'm running the latest ViperOne ROM and really love the options that can be set and tweaked. So many ROM options available for the device the choices are almost endless.
You haven't tried Trickdroid 9.0. Amazing rom that's not missing anything! insane battery life also
does the update also add alot of features ?
I've rooted every android phone I've had and flashed numerous roms on each one but this is the first device that I've left completely stock. I don't even have an unlocked bootloader. The phone is just fine the way it is, I will not be rooting or unlocking the bootloader on this phone anytime soon. Myself and many other users used to root our phones and flash custom roms because android phones used to be incredibly laggy and we always wanted better performance. Overclocking our processors was the norm but now android has matured so much and devices are ridiculously powerful now there is just no need to change them. Even if we were to still overclock our devices you wouldn't see a change in performance.
It's completely up to you though.
Personally, I think rooting is worth it just for the ad blocking it allows; i.e. editing the hosts file. Running a custom rom, being able to backup with titanium and nandroids, and changing radios is just gravy. And if you've ever had a device go south without a custom recovery already on it it's incredibly difficult to fix.
Sent from my HTC One using xda app-developers app
lampel said:
Personally, I think rooting is worth it just for the ad blocking it allows; i.e. editing the hosts file. Running a custom rom, being able to backup with titanium and nandroids, and changing radios is just gravy. And if you've ever had a device go south without a custom recovery already on it it's incredibly difficult to fix.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Devices don't tend to break on stock, that is a case for warranty
Matt said:
Devices don't tend to break on stock, that is a case for warranty
Click to expand...
Click to collapse
The wife bought a refurb Acer tablet - no warranty (I think it was thirty days.) Was ridiculous to restore. I learned my lesson, well! And I'd rather be able to fix it myself than be without while I wait for someone else to. To each their own...
Sent from my HTC One using xda app-developers app
yeah if this was a slow phone or laggy maybe i would,but a have read a few tread with custom roms and some are having trouble with them,think i'll wait on update....although the 4.2.2 update seems to not be coming to t-mobile,all i got so far was a small update.
I have only had the One for a few weeks, but I rooted it and flashed CM10.1 before I even put my SIM in it. Definitely worth it. No reason to deal with carrier restrictions.
t mobile told me there is no 4.2.2 update for the htc one......HTC said the same thing,so now im wondering how come people are saying there receiving this update..
who's lying
bucknaked said:
t mobile told me there is no 4.2.2 update for the htc one......HTC said the same thing,so now im wondering how come people are saying there receiving this update..
who's lying
Click to expand...
Click to collapse
There will be no 4.2.2 update from tmobile, my guess is they are gonna skip that and go straight to 4.3 plus they said it on the internet on the news that htc said it themselves and that there would be no customer benefit for an update like 4.2.2 so they said they were gonna skip it and bring up 4.3.
The update started along the lines of outside international countries that aren't big market carriers and then it rolled on slowly...so no one's lying you just have to do some research on the internet but that 4.2.2 update never got to the US thats why it was never rolled out to large carriers to their customers..
Hopefully this gave you some insight on things that are currently happening.
Sent from my ViperOne
leohdz148 said:
There will be no 4.2.2 update from tmobile, my guess is they are gonna skip that and go straight to 4.3 plus they said it on the internet on the news that htc said it themselves and that there would be no customer benefit for an update like 4.2.2 so they said they were gonna skip it and bring up 4.3.
The update started along the lines of outside international countries that aren't big market carriers and then it rolled on slowly...so no one's lying you just have to do some research on the internet but that 4.2.2 update never got to the US thats why it was never rolled out to large carriers to their customers..
Hopefully this gave you some insight on things that are currently happening.
Sent from my ViperOne
Click to expand...
Click to collapse
there was alot of people saying they received the 4.2.2 update to there htc one
bucknaked said:
there was alot of people saying they received the 4.2.2 update to there htc one
Click to expand...
Click to collapse
It had to have been those in the UK or in some parts of the world because it started from one small part of the world, I mean those that are not on carriers, and it did end up in parts of the UK but it never got to the US and if people who are in the US saying they got the update they changed their CID to a region that had the update rolling out so really no one on this side of the US has that software except verizon because they shipped those one models with the current software, and the GPE ones got an update first because well those aren't sold by carrier they are sold by htc themselves on their website. So yes people have said that they receive it but unless there is proof I wouldn't go off of their word, they more than likely did something to their phone to get that software, they might have a custom rom on their phone or done something to get it officially but here in the us there is no word of 4.2.2 ever coming to their customers....of course except verizon....
Well hopefully this helps...if you have any other questions or concerns please do let us know as we want to help you out
Sent from my ViperOne
guess i may have to root it to get the extra features,just hate all the other problems that comes with custom roms,there always updating to fix this or that.
bucknaked said:
guess i may have to root it to get the extra features,just hate all the other problems that comes with custom roms,there always updating to fix this or that.
Click to expand...
Click to collapse
Not always. Running a stock 4.2.2 Rom or something without major modifications will be smooth for a long time. I ran Mike's stock build rooted for almost a month with no issues at all.
It all depends on what you want from it. If you want all the themes and icon changes and modify this and that, you will have issues. But if you JUST want the newest version out there then I would say go ahead and run a stock build, get it odexed (not deodexed) and you will have buttery smoothness
Sent from my HTC One using Tapatalk 4
is revone still not working for updated htc ones ?
or have they got that fixed ?
zammboss said:
You haven't tried Trickdroid 9.0. Amazing rom that's not missing anything! insane battery life also
Click to expand...
Click to collapse
Hi, I am looking for ROM with better battery life than Stock.
My average battery drain about 1% for about 4-5 minutes while using Internet via WIFI for browsing using JB's 4.2.2 default browser, chatting via WhatsApp, reading emails and using Blink Feed.
How about using this ROM?
Thanks.
My main reason FOR rooting, was to theme the phone red. I have the HTC one Red edition. And just love red. I also hate blink feed. Ive flashed Venom rom, and desensed it. Battery life is amazing, I cant find anything that don't work, well nothing I need to use anyway. Plus they have there own red theme, and with the help of a few icon designes from Seriously Crazy. http://forum.xda-developers.com/showthread.php?t=2091654 This is what ive come up with.
So worth rotting for me, if only for the theming, and gtting rid of blink feed.
Steve

Categories

Resources