Bit rate is far too low, but the FPS bother me the most. i know it is software so maybe there is still hope? HTC have been fantastic providing OTA's so far. Still, we should not of had these issues in the first place, but still.
OTA Update available now with Android 4.0.4 & Sense 4.1, next Jelly Bean & Sense 4+ ?
- Thread starter surfer1000
- Start date
- Status
Bit rate is far too low, but the FPS bother me the most. i know it is software so maybe there is still hope? HTC have been fantastic providing OTA's so far. Still, we should not of had these issues in the first place, but still.
I doubt they'll be fixing bugs for different phones, but you never know. I wish you luck.
Different phones? Sorry, I'm not following you. We've got an AT&T One X, is this strictly referring to the international version?
-Brett.
Well, it is in the international One X forum, and does refer to the leaked (and now available in at least 3 roms) 2.05.401.2 base for the international One X. I've not heard of the SMS notification bug, despite reading quite a bit in here.
Your AT&T version may get 4.0.4, but I am not aware of any leaked ROMs as of yet. But then I don't follow the AT&T One X forum.
D'oh! Sorry about that. I ended up here via a search. Didn't realize there were distinct subforums for International One X vs AT&T's version. I'll go back to the Vivid forum (my phone) and stop bugging you guys!
-Brett.
Yea i thought the same, look at the home button its different.. either its a new revision or photoshooped.
I thought the same thing but flash any custom (old) kernel and its gone, thought i was going mad but it looks like the case that the display driver is different in the new kernel.
can't believe no devs have cracked the bitrate and FPS on the stock camera yet
I don't know why either, their might be someone working on it, hopefully so because HTC don't seem to want to fix it?
I just saw a YouTube video of the Omega Rom for the Galaxy 3. I guess they already hacked the Galaxy 3 camera to function at a different bit-rate, so I would say its software related issue.Displays due seem to change based on kernel and region for instance, I have an Unlocked One X Asia 707 region, Build SH23. When I was on my stock rom 1.28.xxx.xx my screen was on the yellow side of tint it was really yellow. I unlocked and flashed up to the newer base with 1.29.xxx.xx LeeDroid rom which upgraded my phone to the 1.29 base and it was still on the yellow side a little lighter though. Then I flashed the Charmeleon Rom v5.0.0 which was on the same base 1.29.xxx.xx and my screen looked totally different it was a lot more on the white side, really white, you could really tell the difference, and they were the same base 1.29.xxx.xx, I think maybe it could have been different regions was why? IDK to be sure, all I know is that my phone looked a lot brighter with the whiter display.
I have read where there was two different displays when I got my phone it was really yellowish display which I was told was a Sharp display if it was yellowish? Now that I put the rom on it the phone has a really white display so I really don't know whats up with that, and the 2 displays because I have had yellow and white tint, and they have been dramatically different tints on the same display. The yellow was way different, when I flashed my rom now it is a totally different looking screen?
Between 1.28 and 1.29 there was a screen calibration update, HTC even stated it in their changelog. From reports and even test's the white balance was changed to adjust for the warm/yellowish tint presented on specific screen types only. Also from what i know only the kernel can change this as it holds the display driver.
Well, I have an yellowish screen and using the 1.29 update since a month or even more. This is my second hox. The first one had the blueish screen and grey flickering. My yellowish one now has, even with the update, flickering when scrolling on white pages and so one... I mean the other flickering, not the grey background flicker. So for me the update didn't solve anything.
Greets
V
Gesendet von meinem HTC One X mit Tapatalk 2
It was a very minor update from something like 5400k to 6100k which is just noticeable. From a standpoint it just takes the edge off the yellow tint and if you were to still compare it to the blueish tint version of the one x there will of course be a difference but that does not mean the blue is the correct scale. Iv seen both and the acer panel is not as accurate as the sharp even though it may appear otherwise, the sharp panel infact is closer to a natural white balance than the acer but the acer does give off the effect of a brighter and more pop feel but that's normal and why a lot of tv manufacturers have their white balance too high to give that impact and fool people.
Even it was released you can't flash it manually so it's pointless to have online tbh
- Status
Similar threads
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
26How the Sausage is Made
Let me share with you guys what goes in to developing and testing commercial s/w. I don’t know exactly how HTC approaches it but it’s a pretty standard process.
I’d guess there are different teams that work on different components of a ROM.
Plumbing– These are the nuts and bolts that support the OS calls and include things like drivers, low-level code, and the kernel. This team also liaises with third-parties like Nvidia.
Wireless - This include the radios; cellular, BT, GPS, and Wi-Fi.
Application Layer – This includes the OS, Sense 4.0, any HTC proprietary apps, bundled third-party apps (EG: Polaris) and the integration of things like the accessories (desk dock, car dock, Media Link HD).
So to release an update, multiple teams are working on various aspects of it at the same time. Each team tests their work but can only do so much with their individual pieces. As work is completed it’s glommed together in the form of a single ROM for the first time. That’s when internal testing begins in earnest. At the same time, the now complete ROM is placed in a version control system so all the teams are working on it together rather than focusing on their individual components.
Typically there’s a team of testers pulled from various departments in the company because you can’t have 10-30 people standing by to test full time because the work ebbs and flows. The test scripts that are followed are probably the size of a phone book. As issues are identified during internal testing the person overseeing testing tries to isolate it, logs it, and reports it to the team most likely responsible for resolving it. Each time a team or member of a team identifies and resolves an issue, depending on how core the issue is to the entire ROM, testing may have to start again from the very beginning of the script. This repeats dozens of times until the ROM passes internal testing cleanly.
Once internal testing’s complete testing is opened up to a broader user audience. Most likely having HTC employees and/or Elevate members starting to use the ROM on their personal devices. They provide feedback via a problem tracking system and the developers look for commonality in the problems reported and make changes to the code accordingly. If major issues are uncovered it’s back to square one which includes another full round of internal scripted testing followed by pushing the revised ROM out to the larger user group. This repeats until the ROM is deemed “acceptable.” Since no s/w is ever perfect, “acceptable” usually means shippable.
So the six-week old 2.05 test ROM passed internal testing and was distributed to a larger user group. Something must have been discovered that caused the developers to make some major changes. So it’s somewhere in the (re)testing process right now.
Like I said, this is the way s/w development is done. HTC may have their own unique spin but it’s not going to be much different than I described. So, while we want it now, we don’t always get what we want. And I’d personally rather wait until it’s done than have to suffer through some of the issues we all faced with the original shipped ROM. I'm guessing but the actual coding of an update could take anywhere from four to twelve weeks with testing always being as long (or longer) than coding. And based on the way this process works you can pretty much take as a given that JB isn’t “right around the corner.”
And that's how the sausage is made.15For those who want to download the RUU from filefactory here you go...
Filefactory Premium Account:
User: liveacteam09@gmail.com
Pass: www.liveac.blogspot.com
:thumbup:
Sent from my HTC One X13
The title of this thread is "Massive HOX OTA Update coming soon with Android 4.0.4!" It’s been up until now a positive thread. I find it fascinating that, somehow, you managed to work yet another discussion of the same known One X issues and the SGS3 in to it. There are plenty of issues threads already open that welcome comments from disgruntled owners. This isn’t one of them.
Since we're OT any way, here's a link to why I canceled my SGS3 order and decided to keep the One X.
http://xdaforums.com/showpost.php?p=27663514&postcount=1525
A little advice too. If some of you pull the crap you've pulled here when you're on the SGS3 forum and start polls, petitions, and whine about petty issues they'll eat you alive.10
New posts
-
Question Question about the most recent (April) official Google security updates
- Latest: AggresiveSoldier
