[One (M7) Android Development] fisha21:
I'm sorry that it's not working properly on your phone, but there are at least 156 people running 8.1 who would probably disagree. Milestone 8.x underwent at least a week of intensive testing (I know, I did it :)) and we only released once it was working fine. I am at a total loss to explain why it doesn't seem to work on some devices, but you guys have to appreciate the near impossibility of fixing an issue that none of the team is able to replicate.

Thanks to [MENTION=1748233]CharliesTheMan[/MENTION] for his input trying to get to the bottom of this, and [MENTION=876012]veener79[/MENTION] and [MENTION=1373065]vonschau[/MENTION] for being willing to try out various attempts to fix it. Reading over the posts so far, I can't see any common factors: seems like the issue affects people on different carriers, stock and theme, various mods/theme choices, S-on or S-off.

Seems like there are two issues:

1) Aroma freezing

Generally, freezes within aroma have previously been due to AROMA or recovery. Not sure how to explain the fact it freezes at the same point every time. Nothing is getting installed at that point, so it can't be an install issue. I've tried every combination of choices before that page, and have tried stress-testing AROMA by going through the pages as quickly as possible, pressing back/next repeatedly etc and I simply can't get it to freeze. I could try uploading a version of 8.1 without the transparency page, see if that somehow solves the problems

2) Bootlooping after install

Again, difficult to diagnose without being able to reproduce it. Couldn't see any common factors here either. Has anyone experiencing these boot loops posted a logcat yet? Sorry, if I overlooked it, but couldn't see one so far. Also, have those people tried flashing without any mods at all? So full install, don't initialise repo, default options for clock, trans, prism etc, and no mods chosen at all. Would be good to have feedback on that...

Actually, I agree completely, it makes no sense at all. The only things that changed from 8.0 to 8.1 were a fix for missing statusbar clock, some fixes for landscape Prism navbar layout and one change to build.prop for the myHub OTA - none of those changes would stop the rom from working, or cause bootloops. That's why it is so difficult to explain why its not working suddenly, especially as it is working for everyone on the team. This is why the detailed feedback from others is very much appreciated.

Only the HTC app icons are themed as part of the rom, I haven't themed any of the bundled Google/3rd party apps. However, these are all included in the Renovate icon packs (I just double checked and the Voice Search one is already covered there)

If using with Sense, you'll need the Unicon icon themer. Full details are provided in post 5

I've had issues with the autobackup since the 4.06 base (stock and Renovate), but no problems restoring backups.

At the moment, there is no way to change the text, other than editing the Lockscreen.apk yourself. I am hoping to add custom lockscreen text to Tweaks, but I don't have a timescale on this I'm afraid.

As for the fade out screen off, we haven't looked into that yet. Again, hopefully this will be added as option at some point.

Again, this seems to be one of those things that varies from device to device. None of the team own a Media Link, so it is difficult to test that. When you say it isn't working, what exactly happens? It won't connect / recognise the device? Or something else? Also, when you say it was working before, what revision was that on?

Aroma choices are stored in system/aroma. Just delete all the .prop files in there, and all your aroma choices will be blank/reset on next install