yashsingh1/xdaforums huggingface dataset:
[HTC Rezound] Rezinator:
Yes it is/was odd.....and I figured TiBu would be consuming some CPU for all it's work and not getting hung up at the 96 frequency....That's why I was on Hiro 7/20 for a while....but after Neo and a few others posted about raising the min CPU...I went back to the stock one...and it's running great.

FYI....Here's my steps for upgrading Roms.....Hoping to get to exercise it again with a new version of Infection soon :)

I'd be curious what others do....My goal is to minimize down time and get up and running as fast as possible. [I've been doing 90% of the same steps for quite some time....compiled from notes that a lot of the experts here have already posted......thank you]

1. Boot to Custom Recovery (currently on TWRP 2.6)

2. Factory Reset * 2

3. Wipe Dalvik-Cache * 2

4. Wipe Boot

5. Wipe System

6. Flash CleanWIPE_1.0_-_Rezoundv2.zip [the 5x one]

7. Flash Infection-2.9.X.zip

If S-Off, go directly to 8, else.....

==================

S-On Only:

A. In custom recovery, go to Developer Options and reboot to bootloader

B. On your PC, do the command: fastboot flash boot boot.img (where boot.img is the boot.img you got after expanding Infection-2.9.x.zip on your PC)

==================

8. Reboot....

9. Get all registered with Google

10. Reboot....make sure base is working/clean

11. Configure some basic settings

Security...Check "Unknown Sources"

Enable debug....."About Phone"..click "Build number" 5 times...go to Developer options...check "Advanced reboot" and "Android debugging"

NEW for 2.9.1 "only" = Change min/max frequencies "Setting....Performance....Processor...Min = 384, Max = 1512, Check "Set on boot"

12. Reboot....make sure settings stick

12. Go to Google Play....Download & Install TB

13. Launch TIBU ....run "Restore missing apps with data...and a few select system settings (I grab all the green ones)

14. Reboot....this time....just because it's fun.....hehe

15. Enjoy Infection 2.XXX!!!
[HTC Rezound] darienms1986:
If I'm mistaken, "b's" were the rock solid ones. A's had the most problems. And xa was hit and miss
[HTC Rezound] Gornul:
More followup: I was willing to accept the theory that restoring TiBu might have been the issue, so I just spent 3 hours on the following:

5x factory reset

5x cache wipe

5x dalvik wipe

Reinstall 2.9.1 from zip

Allow ALL my apps to reinstall from the google market while driving through spotty signal on back roads

When I finally got done with all that, literally five seconds after I went to start using it, before I could even do a reboot of my own, it immediately spontaneously rebooted. So let's put that theory to bed: TiBu is not the culprit here.

---------- Post added at 07:40 PM ---------- Previous post was at 07:36 PM ----------

In fact, it is now bootlooping, with no further provocation on my part.
[HTC Rezound] sn2hotty:
Works for me! Mine's not too much different except I don't use Cleanwipe anymore. I just do the wipes mentioned above manually 3x. And I'm S-off so I flash and boot LOL. But prior to the first step above, don't forget one last minute TiBu backup of apps and then a Nandroid in recovery!
[HTC Rezound] Uzephi:
Yes, XA was hit and miss, I was simply stating mine was one of the hits on being decent build quality. Never said rock solid, just stated "sturdy."
[HTC Rezound] darienms1986:
For sure, didn't mean to come off like that.
[HTC Rezound] highdro:
you are suppose to wipe system as well so maybe that's why you have so many issues
[HTC Rezound] acejavelin:
Yes, system should definitely be wiped, as should boot if you are changing kernels or want to use the dev's embedded kernel. When changing ROMs, as a general rule wipe everything but sdcard. There is a CleanWipe script that is a flashable ZIP here: http://xdaforums.com/showthread.php?t=1562176 just put on your sdcard, boot into recovery and flash, it will guarantee that you are wiped properly.
[HTC Rezound] Neo:
It may just be that it doesn't like you. ::shrug:: :D

All I do is 1 factory reset, 1 format system, and flash rom. Smooth sailing after that.

Next release will have min freq set to 384, and max to like, 1555 or something like that. Should massively curve the incompatibility issue on start up. Being on clean source will hopefully do away with other glitchy issues too
[HTC Rezound] Gornul:
I'm doing absolutely everything that's available on any menu or submenu of CWM 6.0.3.2. I was wiping system and boot BEFORE and it wasn't doing anything to stop the problem. I'll give this a try just in the interest of thoroughness though, we'll see what happens.

:D (Just kidding, you rock, Neo)

I'm hoping it's the source or something, because I already set Kernel Tuner to the recommended levels and it's still doing random reboots.
[HTC Rezound] stankopp:
I could not agree more.:victory:
[HTC Rezound] geronimo48:
Ringtones

I have had a few bootloops on 2.8.1. I have had to system wipe and re-install Infection to recover. First question: Is there a way to recover from bootloops without doing a full re-install? The last time, I ended up with no ringtones. I have a TiBU backup, but I can't find the ringtones to restore. Any help will be appreciated.
[HTC Rezound] stankopp:
You also did not mention whether you are s-on or s-off. If you are s-on, then you MUST flash the boot image from recovery.

---------- Post added at 04:39 PM ---------- Previous post was at 04:38 PM ----------

There's nothing worse that not being wiped properly...:rolleyes:
[HTC Rezound] acejavelin:
Not true... The proper way to flash when S-On doesn't even require the installation of a custom recovery, all you need to use is the "fastboot boot recovery.img" in Fastboot then wipe and flash ROM zip, using fastboot boot essentially gives you a temporary S-Off, including boot.img flash as part of the ROM installation.

One of my Rezounds doesn't even have a custom recovery installed, its done all via fastboot and works extremely well. Doing it this way also prevents the "TAMPERED" flag, although it won't clear it if already set.

Sent from my Infected Rezound
[HTC Rezound] zourn:
Actually, you should not wipe boot when switching kernels. The boot partition contains more than just the kernel, and custom kernels do not have a new ramdisk, they just modify the existing boot partition.

If you are on TWRP 2.6, just do an advanced wipe and select Dalvik, Cache, Data, and System, and wipe it. Wiping more than once is really just superstitious.
[HTC Rezound] sn2hotty:
LMAO! That's awesome. You almost make soda come out my nose as I read that! LOL

---------- Post added at 02:16 PM ---------- Previous post was at 02:06 PM ----------

Yes, that's true, but his way works too, especially if you're not near a PC. :)
[HTC Rezound] carngeX:
Edit: ignore this. Got it figured out.
[HTC Rezound] spitzaf:
I'm going to put my soft reboot solution out there as "do not restore app data".

After all the discussions I did a reinstall last night. I'd been getting daily soft reboots (less than some but still there). Tried the following:

- Update to Funky 3.8 kernel

- Switch to Hero 7-20 kernel

- Increase min freq to 384

- Increase voltages by 25mv

- Decrease max freq to 1.2GHz

In the end, the only way I didn't get a reboot was to wipe and let Play reinstall all my apps, then manually enter all my login creds again. I didn't restore a thing. For the record, Setup Wizard cacks for me after it goes all the way through and I hit Finish, but no lasting issue.

Try it yourself:

1: Wipe system / data / cache / dalvik

2: Install ROM

3: Wait for Play to reinstall apps

4: Use KernelTuner or similar to set min freq to 384 on both cores (I'm told performance menu only changes cpu0)
[HTC Rezound] acejavelin:
Hmmm... Really? I have always done it this way with my Rezound and have had no issues...
[HTC Rezound] stankopp:
I have never wiped boot...I said boot.
[HTC Rezound] acejavelin:
Yup, I understood... I wipe boot all the time, never had an issue.

Sent from my Infected Rezound
[HTC Rezound] spitzaf:
What would cause the internal storage to not mount? Checked in settings and recovery and can't read /emmc
[HTC Rezound] ecetim:
Can anyone confirm their MD5 sum for 2.9.1? I downloaded it twice and got this for both:

0883fcb4f7a5f2437cfbf38eb752293e
[HTC Rezound] SteveG12543:
That's what I have as well.
[HTC Rezound] jski711:
OK so ROM has been running great until the last few days. I've been getting random reboots all of a sudden and along with that my soft keys aren't working all the time. Not sure if the soft key issue is related but I'm not sure what to try in order to resolve the issue. Thanks.
[HTC Rezound] xustfosorcim:
I turned minCPU up to 384, and max down a notch to just over 1500, and i'm having issues with random reboots when I try to turn the screen on. The screen goes black, and after 30 seconds or so, it reboots (but boots VERY quickly).

I'm not ready to go through nearly 800 pages to find a fix. Any tips on this?

Somebody should get a post on the first page of this thread with some common issues/fixes. I know this is an issue, wifi was an issue with 2.9, and system ui crashes with older versions. All i'm aware of, but I don't know of any fixes.
[HTC Rezound] sidgallup:
Ok, ive tried flashing and reflashing and reflashing and refhasing for maybe a dozen times, always wiping dalvik, system, data and cache, and everytime i get the "anroid keyboard AOSP stopped working" and also there's no launcher... so i can't open the file manager to install a keybioard i have in the microsd as an apk, what gives?

Iw as using Liquid 2.9, did a factory reset and wiping EVERYTHING before flashing this ROM, always the same error, any suggestins?
[HTC Rezound] osmidy:
Wipe multiple times, this used to happen to me all the time. And make sure you wipe boot. To be safe, look up Scott's CleanWipe tool, and that should do the job.

Worst case scenario, maybe flash a sense rom and then try again with CleanWipe.
[HTC Rezound] Neo:
Re-download the rom and try again. You may have a bad download
[HTC Rezound] Quadman:
Neo anyway to add swipe to switch and pics to the drop down in the next version???
[HTC Rezound] Hatchet23:
I did this seemed to work then started same **** again. I've changed to HIRO and it seemed to get better then I started getting what I assume are soft reboots..black screen of death, soft keys stay on and liquid comes up quick then reboots.
[HTC Rezound] Neo:
Liquid??
[HTC Rezound] Hatchet23:
sorry...that's the rom I'm on now. That did seem to help. All the flashing is getting to my brain lol. I was just looking for a touch longer batt life when I switched. All seem to bed fairly close to the same.
[HTC Rezound] Neo:
So then the problem you are talking about isn't even on my rom?
[HTC Rezound] Quadman:
Thanks Neo....:good:
[HTC Rezound] Hatchet23:
No. I accidentally replied to the wrong quoted post. Sorry. Black screen of death is from liquid. If you have an amazing battery life trick I'll come back :D...I did get reboots on infection but not this many. These are at least 2 a day
[HTC Rezound] mpguzman04:
Is anyone else having issue with Bluetooth connectivity while driving. I have a Motorola Roadster 2 and for the longest time had no issues. On 2.9.1 as well as the 8/11 CM build, it seems like I will lose connection when on the road. I don't know if its due to switching from 3g to 4g and vice versa, or what, but my phone will disconnect, yet while disconnected it will show in the Bluetooth menu that it is in fact connected.

When I toggle Bluetooth off and on, sometimes it will permanently stay off. When I attempt to toggle on, the switch jets right back to the off position. This is confusing the crap outta me. Does Bluetooth connection rely on anything I am not aware of? My phone has been through the trenches and the connections on the back of the phone (not the cover but the actual phone back) may not all be touching the back cover. (Not 100% sure though, nor do I know if that could cause an issue).

Just thought I'd stop in to report and see if anyone has similar issues or a solution for such an annoyance.
[HTC Rezound] zourn:
Are you running the included kernel?
[HTC Rezound] thatsricci:
2.9.1 has been pretty solid for me... Using neo's stock kernel in it too as I had a multitude of other unexplainables when running Hiro or funky.

Only thing that happens to me is like every day or two it just plain loses the background :) I'm setting the background using an image stored on my SD card. And after some days go by I'll wake it up and just see the stock rainbowy background on there :)

Oh well, can live with that! otherwise it's great! Rezound proximity fixer is set on boot and the cpu min to 384 (max: 1512) are the only things I've adjusted to set on boot and all's been good!

I use everything from GPS (waze) to facebook, music streaming (subsonic) w/ Bluetooth to my car. Gmail... Zooper Widget, and it's all been solid. Only thing I do on a daily is clean up the running apps that don't need to be lingering. I've reckoned this cut down on random reboots as I notice my free memory hovers around 110mb, I consider that a bit low, but tolerable.
[HTC Rezound] mpguzman04:
Currently running Flyhalfs build, but Bluetooth has an issue connecting with both stock and other kernels on his and I believe I ran just hiro with 2.9.1. The first time it connects is usually fine. But if I leave my car and it then reconnects later, it doesn't hold a connection. Not sure if Bluetooth relies on a working data connection or not though. If so, that might be the issue while driving since I am in a zone that constantly switched in and out of 4g and 3g.
[HTC Rezound] spitzaf:
I've been soft-reboot free since doing this. 5 days and climbing.

I also swapped to Funky 3.8 yesterday to get the additional governors.
[HTC Rezound] NapalmDawn:
Have you tried one of the "keep BT alive" apps that are on the play store? They were created because of so many BT stacks going into deep sleep if there isn't activity and this forces a manual BT toggle to get it back on.
[HTC Rezound] loki993:
So what's the difference between recoveries? Can it really make that much difference? I ask because for Neos ROMs hes always stated that we need to flash with Amon Ra...Im looking at some other roms and they say CWM or TWRP...

Also is anyone still having battery life issue or getting frozen at the splash screen on this rom yet?
[HTC Rezound] acejavelin:
Pretty sure Neo is now recommending TWRP, Amon Ra seems to be a root cause of some issues in the latest builds of many ROMs, including Neos... Haven't seen any concrete evidence to why exactly, but switching from Amon Ra and reflashing seems to fix issue for many people.

Battery life on the Rezound is always an issue, irregardless of ROM, although Infection gave me similar or slight improvement over stock, never had an issue with getting frozen at splash screen (white HTC screen) on any current ROM (Infection, Tron, Liquid Smooth, Beanstalk, CM, or XenonHD). Only thing I have found with most of these ROMs is that I have to change the minimum CPU speed to 384MHz to keep stable on wake up from sleep.
[HTC Rezound] loki993:
Maybe its Amon Ra them thats causing issues for me.

My battery life was never great but even since Neos last update it was horrible, I mean dead in less than 6 hours horrible. I tracked most of the issue to the groupme app and then helped and it was more or less normal again. I know some people were saying location access or something cause a similar issue.

As for the freezing all of his ROMs have done it to me. after a few reboots one a week or every 2 maybe the ROM would start acting up id reboot and get stuck at the splash screen. Nothing could be done and id have to do a full wipe and reflash.

Maybe Ill install TWRP then and see if that helps anything........
[HTC Rezound] Froeleaf:
TWRP v Amon Ra

I, too, switched to TWRP after reading a similar suggesting for Tron. Infection is now much more stable. I had perhaps one random reboot in about two weeks. Thanks Neo! (I suggest updating the frontpage to suggest using TWRP instead. I'm also curious why TWRP solves the instability.)
[HTC Rezound] NapalmDawn:
For battery life tracking, what is the best app for tracking what is chewing up the battery the most? I think I remember a really good one but the name is escaping me atm.
[HTC Rezound] acejavelin:
I prefer GSAM Battery Monitor just because I've used it for a long time, but a lot of people prefer Better Battery Stats.
[HTC Rezound] sn2hotty:
I like GSAM also. It is very informative and complete. Better Battery Stats is too confusing.
[HTC Rezound] Neo:
Working on it ;)

A CM-10.2 Android 4.3 Rom

COMING SOON...​

.
[HTC Rezound] wiredwrx:
Will this be replacing anything? Have an ETA?
[HTC Rezound] Dark Jedi:
Oh he said the words that should

not be said. Oooooh naughty lol.
[HTC Rezound] Neo:
It will not be replacing this rom however, this rom will not proceed past cm-10.1. TACHYON is a new rom and should be viewed as INFECTION 3.0 for those used to this rom. Aside from a faster OS with some new abilities plus a slight theme change, it won't be too different. However, further development will continue through TACHYON.

No ETA's as of yet. I'm only starting to really work on it now that my GCC Freedom script is nearly complete.
[HTC Rezound] Dark Jedi:
Will it fix the reboots and screen flickers that some people gets beings its 4.3. I had to go to Tryon for better battery life as infected drained my battery fast while at work and hardly used the phone.
[HTC Rezound] wiredwrx:
Sweet.
[HTC Rezound] netjetman:
Will it include any of the chromecast screencasting we've all heard so much of?
[HTC Rezound] Antoine.WG:
Will there be any improvements to the RIL? The data dropping seriously has me considering going back to a Sense ROM, but I'm completely torn between connection reliability and performance and buttery smoothness.

------

I digress. I don't mean to sound like an unappreciative jerk. I truly appreciate everything you have done for the Rezound community and I truly hope that you can continue to unlock the full potential of our phone that was ahead of its time.
[HTC Rezound] lamborg:
Hey, I have a question. Can I use this ROM without having an external memory card installed?

Last time, perhaps 2.8 version gave me an error "Cannout mount SD card" or something like that when I opened up the camera and it exited as soon as I clicked OK. So, there was no way to change save location from External to Internal.
[HTC Rezound] 3L3C7R0:
I have zero data dropping problems...
[HTC Rezound] sn2hotty:
All good with data here too.
[HTC Rezound] vpatterson1976:
Same here. Data has been working flawlessly.
[HTC Rezound] azbeerhugger:
The only time I seem to have data issues is in the office and maybe a few times a week at home. Other than that it's great.
[HTC Rezound] Rezinator:
2 Months stable...now a boot loop.....looking for a few suggestions.

My wife's phone has been running Infection 2.8.0 for almost 2 months....no issues at all. Last night due to some strangeness with messaging, I rebooted it and went to bed.....Woke up this AM....it was still in a boot loop. I tried pulling the battery a few times...no luck....tried flashing a newer boot.img [She's s-on].....No luck. Unfortunately, she hasn't done a Nandroid since right before I upgraded it to 2.8...So I did a full nandroid of the current state[so i'd have everything]...and then restored the nandroid 2.7 restore and let the apps update...[so she'd have her phone/apps for today]. [She's still on Amon 3.1.6...will be on TWRP 2.6 soon....]

I did a few searches through the back posts about boot loops and they all seemed related to someone doing an upgrade and / or the easy answer is to flash a new rom/different rom. While I have/would do this if it was my phone....I'm trying to get her back to where it was yesterday [short of having a nandroid from yesterday] Seems odd that She'd be running fine for 2 months...and then get this bootloop.

Any other ideas I could try? I'm hoping that i can restore the Nandroid I took this AM...and then try to fix it "somehow"....

[As luck would have it, yesterday I told her that I was going to upgrade her phone to 2.9.1 and TWRP 2.6.x this weekend.[where I would have done all the right things ahead of time...argh]

Thanks,

Rez
[HTC Rezound] Neo:
I haven't noticed any screen flickering or reboots on my 4.3 build so although I can't say for certain, I feel it is fixed.

Most likely not but that's not to say it won't have it in the future.

No offense was taken. I do not believe the RIL will have been any improved from CM-10.1. Seems about the same to me. However, I don't have data problems. You may want to upgrade your radio if you have not already done so.

Not at the moment but the new change to device that Fly made sets internal EMMC as the default instead of sdcard so once I produce an update to this rom with his new changes, you should be able to without the need of an sd card.

You may want to take the opportunity to back all her stuff up and then upgrade her on a clean flash to the latest version of the rom and then restore her stuff. If she doesn't like it, you could leave her at the nandroid and with the older version, and then jump to TACHYON once I have finished working on it (or after it's had some time to get stable)

-Neo
[HTC Rezound] Antoine.WG:
I upgraded the radios a couple of months ago but it didn't make a difference. It usually shows fewer bars than stock did but that's normal and the signal strength is about the same. I've tried 2 different backs, the extended one that I usually use and my barely used stock one, and that doesn't make a difference either. Data drops on me mostly indoors at work and anywhere from a few times a day to nearly constantly dropped. Recently I've had it drop outdoors in areas with great signal strength.
[HTC Rezound] Neo:
Sounds like a hardware issue quite honestly. Flash a sense rom and see if it fixes the issue for you. If you still get drops then you have a hardware issue
[HTC Rezound] Antoine.WG:
That's exactly what I was going to do. I'm going to flash Nils' Business Sense tonight and give it a few days. Gods I hope it's not a hardware problem. I can't afford a new phone right now and a replacement through Asurion is a total craps shoot.
[HTC Rezound] Dogbone737:
Ahah, Thats probably it because I updated to Funky 1.7 when I was running my JB build. How would I go about replacing 1.7 with the kernel built into the Rom?
[HTC Rezound] Satava:
I've had issues with initial startup on some rom kernel combos. My fix was to enable wifi first then disable it afterwards try the hotspot. Seems like maybe the wifi radio doesn't initialize after a reboot without actually enabling it once.
[HTC Rezound] live2die:
reflash the rom and wipe nothing or just extract the boot image from the zip file and flash using adb commands.
[HTC Rezound] Neo:
You will not have that problem with this rom if you use the kernel included with it. For now, funky kernel versions above 1.4 will have that issue on aosp jb roms. That is specifically why 1.4 is the version being used :)
[HTC Rezound] Cybie257:
No such things as *228 on 4g/SIM phones

Unless something has changed, *228 won't ever work on your Rezound or any other 4G phones with the SIM Card.

The 4G method of *228, straight from a level 2 (or 3) tech at Verizon, is remove the SIM card for 30 seconds, then replace it and power up.

*228 is for 3g and previous phones w/o the SIM.

-Cybie

PS. should I be wrong, or something has changed, please don't hesitate to correct me on this... :)
[HTC Rezound] Neo:
I don't remember what life was like prior to aosp.. Must have been so traumatic that I blocked it out. Sounds right though
[HTC Rezound] d.kozzer:
Looks great Neo! Put me down as another interested party for the invert-revert. Thanks for all your efforts, as well add to Snuzzo (even if 2.0.1 doesn't have the funk), Chad and whoever else made this possible. :D
[HTC Rezound] Neo:
Hopefully an updated kernel with fixed tethering on Monday as well as a new invert revert flashable
[HTC Rezound] replica9000:
I think even on the stock ROMs, *228 gets you this:

"A Verizon Wireless SIM card has activated your service and updated your phone's roaming capabilities"