Related
If you like me have just upgraded to the 2.03 rom released in January and now HTC released a new rom with exactly the same changelog it may not be worth all the hassle with reinstalling / configuring all your stuff once again already.
I was pissed at HTC since they couldn't tell us what they changed since they told us to REAPPLY this update if we had installed it prior to february 27. So today I sent them this email:
Latest ROM update for HTC Touch Diamond. It took me over a week to customize my device after the 2.03 ROM released in january since I prefer to cleanly re-install everything instead of backups. Now a new ROM with the same changelog is already released & you say we should re-apply this ROM if we installed before february 27! Why? We are many people who don't wanna go trough all the hassle again. Why can't you just tell us what you fixed so we can decide for ourselves if it's necessary. The january ROM works just fine. Yours sincerely, ******.
And I just got an answer from them that I can't post here since it came with a confidentialy note. But I can tell you in short that they explained that there are lots of things and bugs for different time made devices and changes and that is why they can't say what is changed in the february 27 rom.
They also told me not to reapply the update if my device is working fine, there is no need to.
So you can without any worries stick with the january update for now if you don't experience any issues or don't feel like installing all your stuff from scratch
owziee said:
If you like me have just upgraded to the 2.03 rom released in January and now HTC released a new rom with exactly the same changelog it may not be worth all the hassle with reinstalling / configuring all your stuff once again already.
I was pissed at HTC since they couldn't tell us what they changed since they told us to REAPPLY this update if we had installed it prior to february 27. So today I sent them this email:
Latest ROM update for HTC Touch Diamond. It took me over a week to customize my device after the 2.03 ROM released in january since I prefer to cleanly re-install everything instead of backups. Now a new ROM with the same changelog is already released & you say we should re-apply this ROM if we installed before february 27! Why? We are many people who don't wanna go trough all the hassle again. Why can't you just tell us what you fixed so we can decide for ourselves if it's necessary. The january ROM works just fine. Yours sincerely, ******.
And I just got an answer from them that I can't post here since it came with a confidentialy note. But I can tell you in short that they explained that there are lots of things and bugs for different time made devices and changes and that is why they can't say what is changed in the february 27 rom.
They also told me not to reapply the update if my device is working fine, there is no need to.
So you can without any worries stick with the january update for now if you don't experience any issues or don't feel like installing all your stuff from scratch
Click to expand...
Click to collapse
I have to soft-reset my device everytime during an installation, then run the install again. The x-button doesn't work properly (turned "close programs using x" on). Never had to use the red soft-reset button as often as with this ROM (crashes easily). Plus it's much slower than my previous official ROM.
I think this ROM update is for people like me...
Well maybe... I don't experience any of the problems you mentioned.
owziee said:
...It took me over a week to customize my device after the 2.03 ROM released in january since I prefer to cleanly re-install everything instead of backups. Now a new ROM with the same changelog is already released & you say we should re-apply this ROM if we installed before february 27! Why? ...
Click to expand...
Click to collapse
are u suggesting that htc should stop releasing updates for diamond?! dude, why using stock rom's, what's the fun in it anyway!?
No no, absolutely not!!!
But HTC released this rom (february 27) with the same changelog as the 2.03 rom they released in january and I've just gone trough reinstalling everything so the idea of installing virtually the same rom once again gave me a headache.
HTC urged us to reapply the update if we installed it before february 27 and I really needed to know why so I had to send them the email.
Of course I would be very happy to see new rom upgrades in the future as long as there are changes / fixes worth mentioning (They didn't even mention any fixes this time since they just posted the same changelog all over and it was only 1 month between the updates).
ROM info...
What's more... take a look at the version numbers:
January's ROM: v2.03.405.2
February's ROM: v2.03.405.3
When a version number change isn't even a point (i.e. the '.03' in the above example), believe me, not a lot has changed. But this is worse than that, a change from .03 to .04 would probably mean just correcting a spelling mistake... this change is so far down the points, it doesn't even make it past the 'what's the POINT' stage with me (get it... what's the POINT!!) - OK, rubbish joke
Maybe the newer ROM fixes problems that only appear under special constellations.
For my part it fixed a problem i had:
Sometimes TouchFlo 3D diddn't start correctly after a softreset (from Sprite Backup),
device kept powered on until battery was empty.
They don't list a newer changelog for this ROM, but i find it strange that the Jannuary
version is no more available on the website.
But i agree, if the Jannuary version runs fine absolutely no need to upgrade.
This is a flashable ROM from generated from Football's RUU_Vision_Hutch_AUS_1.85.861.3 release. It includes all applications and original vendor configuration. In other words, it is untouched with the exception of the following:
Rooted with my customized version of Superuser (required until ChainsDD releases a version with my patches).
Deodexed with moderate compression throughout.
Busybox installed in /system/xbin.
Added large APNS list to /system/etc.
WWE-equivalent language support.
There are no other changes. Just to be blindingly clear, this is NOT Virtuous; although a future version of Virtuous may be based on this ROM. Anyone building ROMs is welcome to use this as a base. Thanks again to Football for continuing to provide us with the latest RUUs.
Disclaimer: This is a one-time release. Unless a problem can be identified with the changes mentioned above (rooting, deodexing, etc), it will not be updated or supported. Use this as-is or find a ROM which uses this release as its' base if you would like support and/or expect to see changes.
Remember to hit the "Thanks" button if my work ends up being useful to you.
Download ROM
(MD5:a764d0e09975209ab4268cfa3cef3167)
Please do not ask me how this is different than the 1.85 orange release, as HTC does not exactly provide us change logs.
Orange, it is a name of telecom provider, right? If yes is it possible for you to get similar stock ROM but for Era polish provider and a little older, like 1.7...?
I am asking because as a newbe I didn't make any backup for my stock ROM delivered with my phone and I would like have a possibilty to back to the original stock for Era when for example I will have to give my phone back to service.
Or maybe You can suggest other way to back to Era stock, please indicate any thread if you know.
Thanks a lot for helping
Just flashed this ROM. It has a slow desktop draw issue. When I go to the main screen all icons appear very slowly. I do not understand if this ROM is untoched why it has the same issue as Virtuous?
denich said:
Just flashed this ROM. It has a slow desktop draw issue. When I go to the main screen all icons appear very slowly. I do not understand if this ROM is untoched why it has the same issue as Virtuous?
Click to expand...
Click to collapse
It's clearly a bug this version of Sense and has nothing to do with Virtuous. This is actually the case with many of the bugs in the ROM, we inherit them from HTC.
Just wondering, What did you use to Deodexed the apks/jars?
rmk40 said:
It's clearly a bug this version of Sense and has nothing to do with Virtuous. This is actually the case with many of the bugs in the ROM, we inherit them from HTC.
Click to expand...
Click to collapse
Seems like a bug only with froyo sense...
bigmoew said:
Seems like a bug only with froyo sense...
Click to expand...
Click to collapse
Push Rosie.apk from 1.82 or 1.72 to fix the problem.
rmk40 said:
Push Rosie.apk from 1.82 or 1.72 to fix the problem.
Click to expand...
Click to collapse
I applied the patch which returns rosie to 1.72 (the patch from virtuous thread). it do no help the problem remains
to hopefully decrease the number of posts from members in the coming days about the new OTA that Sprint/HTC released today (but will not officially "push" to devices until January 24,) I would like to point out some things to new members as well as veterans, as we see this happen every time a new OTA is pushed.
1. Number one rule, and i will cap this DO NOT ACCEPT A OTA UPDATE IF YOU ARE ROOTED. it has been said many many times here, and members with rooted phones do it anyways. why risk it???? we all saw the gingerbread debacle last year.
2. New HBoot. it seems the new ota update has a new h-boot, 2.18, and from what it seems and this may remain to be seen 100% it is not unlockable with revolutionary. i can not confirm this personally.
3. New Radios. seems the baseband /radio has been updated. we eagerly await caulkin to possibly update his posts with the new updates.
edit: seems new radios have been posted in his thread: http://forum.xda-developers.com/show...postcount=3214
4. Why the update? The big part of this update was to remove CIQ from the evo's. yay. There were small improvements to Peep (the htc twitter client) and other various fixes.
5. So when will my favorite rom be updated to the OTA base? well, we already have a stock rom based on the ota (actually 2!) , it is located here:
http://forum.xda-developers.com/show....php?t=1455340
so this is a start. your favorite rom will be updated by it's developer when the dev has time, last update we had (4.54) we saw a rapid update of roms.
6. Great, so has sense changed at all? No we are still at sense 1.0 sigh.
7. so how about the new kernel? it is now based on htc 2.6.35.10 dated december 21, 20011. Captain_Throwback has extracted the kernel standalone: http://forum.xda-developers.com/show...postcount=3214
7a. What "hacks" work with the the new stock rom you posted? from what I have read, none of them, although people are still flashing/testing.
8. i have a question!! well use the search function and see if it has been answered, look here, the general threads, or the dev threads. I hope this will clear down some of the clutter that comes up during this wonderful thing called an OTA update.
I was playing with some apps and files from Android L and I finished doing this lol I hope Enjoy it as much i do make this stuff
Thanks to CyanogenMod for the Base
if you want full experience enable On-screen Nav Bar
also for the new keyboard you have to go to Settings>Language & input>Google Keyboard then scroll all that way down till Advanced settings>Color Scheme and select Material
as always do a BACKUP and full format no your Internal Memory but you know that
NOTE: THIS IS NOT ANDROID L IS CM11 THAT LOOK LIKE ANDROID L
Download it from here
Nice. Can you specify in the thread title that this is not Android L?
This is pretty awesome. I love the look. Can I ask a favor? Would you mind doing the same thing to a newer version of CM11? I see the kernel is from June 8, is that the build you used as a base? In the official CM11 thread Shelnutt said that the data issue was fixed in newer nightlies. The issue is that for us 3G users we keep getting a FC for the phone UI. It happens when mobile data is on. It used to be able to be fixed by replacing the apn config file. I am going to try and I will let you know.
Thanks for the time you put into this.
Ill Try to do it as soon as i can =]
dopy25 said:
This is pretty awesome. I love the look. Can I ask a favor? Would you mind doing the same thing to a newer version of CM11? I see the kernel is from June 8, is that the build you used as a base? In the official CM11 thread Shelnutt said that the data issue was fixed in newer nightlies. The issue is that for us 3G users we keep getting a FC for the phone UI. It happens when mobile data is on. It used to be able to be fixed by replacing the apn config file. I am going to try and I will let you know.
Thanks for the time you put into this.
Click to expand...
Click to collapse
sure i can do that i choice this build because is the most stable lol i also just finished another rom called Xperia G which i love it lol but is base in the same build of CM but on that one you can flash the Apps over any Cm11 version i guess ill do the same with this ROM that way the people can use any base and just flash the APPs/UI over =]
XDA doesn't allow Telegram and a few other site links so I'm taking down the thread as I don't want to post an incomplete guide.
You may find the full guide here: https://bit.ly/3rGKKtQ , this will be the only place I maintain bugs and guides.
Bugs on Android 11/R AOSP ROMs
1. Work in progress
-
-
Reserved
Thanks to Haris. New wifi fix for Android Q is available for some North American V30 variants: https://forum.xda-developers.com/lg-v30/how-to/q-wifi-fix-north-american-variants-t4012635
On Pie LOS ROMs, U.S. Verizon carrier users have to make a phone call after any reboots to receive texts.
May also be on LOS-17 based Android 10 ROMs. Not sure.
ChazzMatt said:
On Pie LOS ROMs, U.S. Verizon carrier users have to make a phone call after any reboots to receive texts.
May also be on Q/Android 10 ROMs. Not sure.
Click to expand...
Click to collapse
Thanks
I would request others to post bugs too as I can test bugs only for h930 variants and not others. Also there may some features that I don't use so I may not notice even if there's a bug with them
PS: Added a bug that screencast doesn't work.
Added general tip with solution for bug 14 in Q bugs section.
deleted
FIX for the quad dac/avc reset bug when listening to music in AOSP
https://play.google.com/store/apps/details?id=com.phascinate.lgv10.dacfix
You still need to toogle off and then on the first time, but when you pause music it should not reset itself anymore. Tested for a couple of days now and works well.
@tech_infinity can you add this to the main post? At least until a proper fix is available
Hey,
Would you mind telling what version that is? Your link seems to be dead so I'll go grab the latest from gcam port site
Thanks!
The link is working for me, anyway its
MGC_6.1.021_V2e-fu24_Aux3way_4Lens-04h-dual.apk
Search it on Google should find it, be advised picture quality is not the greatest, and I haven't been able to import any config files. Its the only one where everything works though.
Hi, how can you install that version of Maps ? I uninstalled the buggy one but i can't install any older version...
Pluginbaby00 said:
Hi, how can you install that version of Maps ? I uninstalled the buggy one but i can't install any older version...
Click to expand...
Click to collapse
Remove gmaps completely
Install apk from here: https://www.apkmirror.com/apk/google-inc/maps/maps-10-9-2-release/
I can't install this one too...
What error do you get? Screenshot?
Also: you have to uninstall any other version of maps before installing it again, otherwise it fails to install
Yes i uninstalled the other version of the app with Uninstall System App...
Try installing maps using this app, if it fails again post the error info you get
You can also try installing as root (see in settings of the app)
IT didn't work, see the screenshots