yashsingh1/xdaforums huggingface dataset:
[HTC Rezound] acejavelin:
Change your minimum CPU clock rate to 384 MHz, clears up the reboot issue for most people.

Sent from my Infected Rezound
[HTC Rezound] pogibry:
That's what fixed it for me :D
[HTC Rezound] drynyks:
I think it was backward to release it with minimum that low. It cause problem for sure and for the few that want it they can set it.
[HTC Rezound] mantis406:
I couldn't get Exchange email to work while on Wifi with the stock kernel; couldn't connect to the server. I was also having many random reboots. Switched to Hiro and both problems were resolved. After reading more responses I realize the reboot issue could have likely been resolved by increasing the minimum clock speed, but the Exchange issue was a deal breaker for me.

I don't want to sound ungrateful, this is an amazing fast ROM and I appreciate all the work Neo and everybody has put into it.
[HTC Rezound] draklin17:
Is there any noticeable improvements for the battery life by changing the min rate? I mean, if I switch from 384 MHz to 96 MHz, would I be getting enough additional battery life to make a difference? I wanted to run 96 to save battery, but I kept getting reboots. I'm thinking that I couldn't have saved that much battery life with the lower frequency.
[HTC Rezound] acejavelin:
I have had no issue with Exchange email on WiFi (or 4G) and this is the first I have heard an Infection ROM having this issue, pretty sure people would be screaming about it if it didn't work... the kernel shouldn't be a part of this, if the WiFi connects and works for other stuff, it should work for Exchange services as well, it is just data like anything else.

That being said, if you literally did nothing but swap kernel and it worked... some handsets do seem to be more partial to certain kernels, guess you got one of those.

Actually no... I tried it both ways and noticed no difference, almost the other way that 384 MHz has better battery life, I know it's not logical but I think it handles background tasks better and more efficiently, plus watch the battery when your phone reboots... rebooting is a hog.
[HTC Rezound] onthehole:
Back to 2.8.1 for me and solid without reboots. On 2.9.1 Tried clean wipe 10x. Fresh install, all apps downloaded from Google play over night, no data restored. HIRO 7/20 384 min. Still soft reboots and not great battery life.

Back to 2.8.1 and all is Banging again. No placebo "384 fixed it" in this post. I thought 384 fixed it but it didn't though I tried various options. 2.8.1 is my favorite build this far and I need to donate again when I get home. Thank you for your amazing work along with the other great devs here.

Edit: I haven't had a single instance of being stuck at the boot logo since switching to cwr touch for what it's worth.

Sent from my HTC Rezound.
[HTC Rezound] hgoldner:
With AOSP/AOKP ROMs, the key to Exchange functionality is to make sure that before you set up the Exchange account on the Rezound, you turn ON autosync. Once you do that, and the data downloads to the phone, you can turn autosync on and off at will, or never turn it on again, if you like and sync manually; it's just that first time, before the account is set up, that you need autosync running.

If you have already set up an Exchange account and can't get it to download everything, delete the account, turn on autosync, and recreate the account. Saw this solution over on the Android support site at Google, and have been able to run AOSP/AOKP ROMs on both my Rezound and my Asus Transformer TF300T without any Exchange issues.

So, the issue is probably not related to this ROM.
[HTC Rezound] Avasta:
V 2.9.1 fail!!!

Version 2.9.1 fails over and over and over.. keeps crashing mid-use. Flashing back to 2.8.1 recovery.. MAJOR BUG NEEDS FIXING.
[HTC Rezound] carngeX:
Running 2.9.1 solid so far. 174 hours of uptime. Changed the min CPU speed as suggested to 384, and running Amon Ra 3.15. No issues so far that I've seen.
[HTC Rezound] Neo:
As am I with same results. Those having issues need to either re-evaluate their flashing procedures, or keep to the included kernel and change frequencies to 384/1512.

Not all boards are equal. Some are more sensitive than others.
[HTC Rezound] Quadman:
Before going back to 2.8.1 try snuzzo's funkybean 3.8. Snuzzo it's working flawlessly so far.
[HTC Rezound] aznjosh:
Does wifi tether with encryption work on Funkybean 3.8 with Infection 2.9.1?
[HTC Rezound] Quadman:
Sorry but I don't use it.
[HTC Rezound] carngeX:
Just to add on, that's the only thing I've changed, is the min frequency.

Governor is set to Interactive, max is set to 1566. Using the built-in Performance setting rather than a third party app to do it as well.

Only performance tools I've run is Lagfix to manually run the TRIM commands on my phone every once in a while, and Greenify to remove Facebook and a couple other apps from continuously running in the background.

When I flashed the ROM, I made sure to do Factory Reset, then I went and did each partition manually to make sure I got them all (except /boot), as well as dalvik cache.

I even restored data for all of my apps, as well as a few system things such as SMS/MMS using MyBackup Root.
[HTC Rezound] dbighead77:
Here here! I'm also on Amon Ra 3.15 and have 218 hours of uptime. I've been running vanilla 2.9.1 (no inverted, no lite, but the full thing.) I did switch over after an initial boot to Hiro 7/17 so I could get my governors and schedulers back. I've even been lucky enough to undervolt by 50mA, and have tweaked my governor to try and stay at lower frequencies. Since 2.9.1 came out, I haven't had a crash or reboot.

When I came from 2.8.1, I wiped everything (boot, android-secure, dalvik cache, factory reset), but didn't wipe my internal and external SD cards. I also used ROM Toolbox to backup just a few apps. I don't use Verizon texting, so I don't try and back up any texts. For the people reporting problems, I assume you're wiping stuff in recovery. I'm just wondering if you're wiping everything, or just doing a factory reset. I haven't had a problem for 3 ROMs since I started wiping everything (Sorry if I'm not diving into the old posts to look.)

I saw there's a new ClockworkMod recovery out, and some people are moving to that. I think I'm going to stay on Amon Ra 3.15 until I start having problems.

Neo, I think one way to maybe rule out a possible problem point is to post the MD5 of the ROMs. I usually download the ROM twice and make sure I get the same MD5 before I flash. I'm wondering if some of these random crashes people are reporting are due to a bad download. I've thoroughly enjoyed your work!
[HTC Rezound] echolocator:
So even though I had built in tether working with wpa2 and stock kernel, when I tried to use it today I got connected but no internet access. On a hunch I opened an admin command prompt and ran:

"Ipconfig /release && ipconfig /renew"

without the quotes and it fixed it!

This is for Windows only. Let me know if you have questions.
[HTC Rezound] onthehole:
I had the original kernel included with 2.9.1 with 384 min. Just didn't bite for me I guess. Dunno never had an issue before except for the stuck at the boot logo thing back around 2.6 when I was on ra still.

Sent from my HTC Rezound.
[HTC Rezound] Uzephi:
Using TWRP 2.6.0.0 as recovery, latest OTA/Radios, wiped everything (using advanced wipe option), installed 2.9.1 on release hour. Was one of the testers for cubed port for JB. 192/1620Mhz tweaked on demand gov for cpu0 and Lionheart for cpu1. I have not had a reboot yet.

Native WiFi tether may not work with this kernel, but 3rd party app and authentication before connect works great.

I do not know why everyone is having these reboots. I am at lower than recommended CPU freq with no issues at all.

Edit: I have tried all governor/IO scheduler variations and max/mins as stated before, I helped test a kernel. With this ROM, I only had one issue and it was the kernel that I was testing's fault. I shall repeat, I want to know why everyone else is having issues. I tried to force reboots for testing purposes and couldn't have it happen.
[HTC Rezound] mschluss:
Tether

Native wifi thether is working with the HIRO 7/7 kernel (but does not work with the HIRO latest kernel). Also, much more stable with this kernel installed.
[HTC Rezound] mjh68:
I wish I knew...it ran great for 2 days then it rebooted 3 times in a row followed by multiple black screen freezes when attempting to wake phone up. I clean flashed , stock kernel with min set to 384. I have had the black screen freeze on every asop ROM though so not unique to infection.
[HTC Rezound] cryppie:
After reading the last few posts I'd like to mention that I've had none of the above issues and have been on this rom since latest release. The rom works great. I'm on twrp2.5 running stock kernel. I haven't touched the clockspeed. Exchange and built-in wifi tether have always worked without issue as has everything else.

I noticed after I messed with the clock I was not seeing as good performance as before I changed it no matter what I set it to. I also saw performance issues running FB kernel.

For those having issues wipe everything (I have always used cleanwipe v2) and give it a chance without touching the clock or kernel.

Edit... it also might be worth mentioning that I'm running radio 2.22.10.0801r / 2.22.10.0803r and hboot 2.27.
[HTC Rezound] Uzephi:
Okay, I tested KSM (Kernel Samepage Merging) and found running too many apps with my modified OOM groupings to lag the phone out and reboot it. This only happens when I use memory intensive apps and the phone almost runs out of memory. Turn off KSM and everything is happy. No OOM freezes, things close to free up space.

I used 768 aggressive setting in kernel tuner. I have never had this issue as I never tried KSM, never had memory issues on this phone to need it. Anybody who is having this issue enable KSM? It is found in performance - memory management.
[HTC Rezound] mjh68:
I will have to try that, because looking back on it I was streaming music and using navigation at the same time .
[HTC Rezound] Katmeat:
I consider myself a fairly heavy user of my phone, using it for work, and I have it loaded with over 200 apps. I have not had a single reboot with the stock kernal since upping the min to 384, and I am seeing great battery life unlike I have ever seen before with this phone. I couldn't be happier with this ROM.

On another note, I got in the habit several years ago with the original Evo of a daily reboot of my phone, using Tasker to reboot it early every morning. It always seemed to help that old phone starting fresh each day, and I kept doing so with the Rez. Does anyone have any thoughts as to whether that is a good or bad practice? I have never noticed any detrimental effects of that daily reboot practice. Then again, I am not sure that it helps much either.
[HTC Rezound] LOBBS:
I've always done this practice as well. I usually boot to recovery, clear cache and dalvik and reboot daily. I've always done it with my PCs as well which is probably what got me started on my phones.
[HTC Rezound] Rezinator:
I also reboot my phone every morning...2 reasons...If I don't, the fidelity in the headphones seems "not as dynamic"...and Play Store updates seem to get "pushed"....I can check the store for updates....see nothing...reboot, and sometimes an app will come done.

I chalk this up to pc type behavior....daily reboot....and all is good [FYI...Still running hiro 7/20 with 192 min....almost 2 full weeks - still no issue]. The headphone issue is odd, but it's a small price to pay to have it Infected :)
[HTC Rezound] tigerxchaos:
I didn't have a single reboot with 2.8.1, but with 2.9.1 I have had a couple reboots and some other issues, particularly app crashes. Notably, last night, the Phone app crashed immediately on accepting a call and would not function again til I rebooted.

I am on HIRO 7/20 for my kernel because of the additional governor options it offers. This is also because recent stock CM kernels have not worked well on my Rezound. It's been mostly stable (still more so than a stock CM install) with this kernel, despite my phone being insanely intolerant of anything but stock kernels.
[HTC Rezound] Uzephi:
It sounds like your data wipe didn't work right. Go back in recovery and do a full wipe, data/cache. If using twrp, use advanced option and wipe everything but your SD card (internal and external) and reflash. Cwm option is data/cache iirc
[HTC Rezound] jmichaels1982:
This is how i fixed tethering

So i had too many issues with tethering for this rom ( 2.9.1) .

1-when I used the innate tethering, 4g dropped the moment my computer connected to my phone . An age old bug that came back from the dead to haunt me.

2- Android wifi tether did not work , no matter which setting

3-had to revert back to the good old ADHOCK mode, which I detest for the lack of encryption and multiple device support.

So here is what I did , in case someone faces the same issues ( BTW I WIPED dalvik, cache, system , data and internal 3x before installing. )

1- install HIRO kernel released 7/7

2- install android wifi tether 3.4 experimental 1 found Here https://code.google.com/p/android-wifi-tether/downloads/detail?name=wifi_tether_v3_4-experimental1.apk&can=2&q=

3- and now the VERY VERY IMP settings :

I- profile is HTC rezound

ii-set up method : netd-ndc (master)

iii-check the the three boxes after and choose an appropriate passphrase WITHOUT symbols, letters and numbers are fine.

iv- check the following : dont disable bluetooth, wifi reload and wifi reload 2

v- then nothing else checked EXCEPT FOR routing fix, vibrate on connect and disable wake lock, please enable all of them

Hope this helps those that were stuck like me .

Thank you for a phenomenal rom !
[HTC Rezound] gris1016:
good morning everyone!

So i really need some help with setting the rezound up for att. What all works on att and what doesnt? can we get 4g , LTE, and MMS? What configuring needs to be done? Im stuck. Rezzy is S-off, unlocked and clockworkmod recovery with latest firmware. I am rocking this awesome rom as well! Any help will be great!!

Thanks
[HTC Rezound] Uzephi:
I popped my coworker's T-Mobile Sim in my Rezound a couple days ago. My area is refarmed 1900mhz... I got 4G. I think it depends on if your area has a high speed 1900 MHz band as that is what our GSM radio runs. Anyone correct me if I am wrong.

How to enable GSM radio? All I did was *#*#4636#*#* and changed radio from CDMA/LTE to GSM/LTE and APNs changed automatically for me.

I tested data, phone calls and SMS/MMS all worked here in Phoenix, AZ
[HTC Rezound] acejavelin:
Remember that "4G" isn't necessarily LTE to T-Mobile and AT&T, you will likely only get HSPA+ that many of the GSM carriers incorrectly refer to as "4G". That being said, I have not taken an actual post-paid 4G/LTE SIM from an AT&T or T-Mobile device and tried it in the Rezound so if the conditions are right... well, who knows, but my understanding was that the Rezound does not have the proper hardware to use AT&T or T-Mobile LTE networks.

But more to the point, yes, the Rezound can and does support GSM networks with current global firmware and on a custom ROM like Infection it works quite well (stock Global ROM works, but requires significantly more tweaking), with some SIMs you need to manually add the APN settings, and with some it's automatic. Many people have the Rezound working on AT&T, T-Mobile, Straight Talk, Net 10, Page Plus, and a host of other network providers other than Verizon, note that the GSM radios don't seem to be as tweaked as the CDMA radios in the Rez, some people have noted that the signal reception on GSM networks is not as good as with Verizon, others have no issues. MMS was originally an issue, but I believe that has been overcome with ability to add APN settings or the use of a custom ROM.
[HTC Rezound] jtio21:
No Issues

I don't why so many of you are having issues i have not a single issue with 2.9.1, which means no reboots or native wifi tether problems. In fact this is neo's smoothest release yet and the only version i did not have small issues with. The only thing i did was change to frequencies to what was recommended.

Thanks for the good work Neo!
[HTC Rezound] Rezinator:
Probably a dumb question.....Is there an easy way to go to back to the stock Kernel (Flyhalf's latest kernel) from Hiro 7/20 version. I'm a glutton for punishment and was thinking I want to go back to stock 2.9.1 and try a different min frequency. (I know it's probably in another thread but I I've asked about this Kernel twice already and still not got an answer :) )

Or should I just wait until 2.9.2(?) which is expected later this week???

Rez.
[HTC Rezound] bacon612:
Re: [ROM][JellyBean][AOSP][01.12.13] ┬─┬ ノ( ^_^ノ) v2.3 LINARO! [Android 4.1.2]

You do a full wipe? R u s-on or s-off?

If you are s-on you need to extract and flash the boot.img
[HTC Rezound] brenuga:
Well after testing one of Neo's early RAGE 2 builds, liking it, but ultimately going back to Simplistic (Sense 3.6) for stability...

I've made the quantum leap ahead to RAGE-2.3!!

Long story short, something borked my superuser privileges. I tried re-flashing su through amon ra etc. but had no luck. So I figured, what the hey?

"I'm back, *****es!"

How does RAGE 2 play with Funky Kernel 1.5? I saw where it got taken out but was just curious what the plans were. I need intellidemand and wheatley back :)
[HTC Rezound] ChuckZv2:
Re: [ROM][JellyBean][AOSP][01.12.13] ┬─┬ ノ( ^_^ノ) v2.3 LINARO! [Android 4.1.2]

Hey Neo, how do you compare your rom to All other AOSP JB roms? As far as stability with features, battery life, signal? Im S-On but I can handle fast booting the Kernel img through CMD.
[HTC Rezound] Neo:
Re: [ROM][JellyBean][AOSP][01.12.13] ┬─┬ ノ( ^_^ノ) v2.3 LINARO! [Android 4.1.2]

I have not run anyone else's AOSP roms so I can not give an assessment. However, I focus my aosp work on the latest material with excellent performance at no cost to battery life
[HTC Rezound] ChuckZv2:
Re: [ROM][JellyBean][AOSP][01.12.13] ┬─┬ ノ( ^_^ノ) v2.3 LINARO! [Android 4.1.2]

Can you kindly attach a link of the ROM for S-on devices.

Thanks
[HTC Rezound] TheBr0ken:
Re: [ROM][JellyBean][AOSP][01.12.13] ┬─┬ ノ( ^_^ノ) v2.3 LINARO! [Android 4.1.2]

Don't think that there is one for s-on devices, but you could always install snuzzo's funky kernel or Shrike1978 also has a good kernel. Both of those use the Aroma installer that will work for both s-on or off devices. Must use Amon-Ra recovery if you don't want issues
[HTC Rezound] ChuckZv2:
Re: [ROM][JellyBean][AOSP][01.12.13] ┬─┬ ノ( ^_^ノ) v2.3 LINARO! [Android 4.1.2]

What is the difference when flashing between a ROM or a Kernel? Is one better than the other?
[HTC Rezound] GoldenCyn:
Re: [ROM][JellyBean][AOSP][01.12.13] ┬─┬ ノ( ^_^ノ) v2.3 LINARO! [Android 4.1.2]

That made me chuckle a bit.
[HTC Rezound] SynisterWolf:
Kernel- "The kernel is a program that constitutes the central core of a computer operating system. It has complete control over everything that occurs in the system."

Rom- Is the OS of the device.

When you flash a ROM normally it is with a stock or pre-built kernel inside. This is done because it is the most generic and simplistic kernel that will run the OS.

Now that the source code is out for said generic kernel, people like to take it and improve on the code. Adding new features that the stock one never had, better battery life, better schedulers, and even over clock of the CPU/GPU.

If you are going to flash a kernel, you need to make sure it will work with the phone. ALWAYS read the entire OP if you are unsure if it will work or not. Dont rush anything when it comes to a kernel. It could leave you with a paperweight.
[HTC Rezound] brenuga:
You need to read a guide on flashing ROMs before you mess up your phone, so you will know what to do. Here's my favorite, easy-to-read guide, "S-ON and want to flash ROMS?" (the Rezound forum on androidforums) It shows you how to use adb and such.

But yes, all of Neo's ROMS are very stable. I've used some form of Neo rom since last August. This one is the best yet.

I am S-On and it's easy to flash this rom. You need to be able to use the command line, and use amon ra recovery.

1. Backup your current setup with nandroid

2. Clean wipe 3x

3. Flash RAGE 2.3 zip in amon ra

4. Reboot to bootloader command in amon ra

5. At bootloader, use adb command to do 'fastboot flash boot boot.img' <--To get boot.img, extract the RAGE 2.3 zip on your PC and copy it to the path of your adb

6. Reboot and give her some time to boot up

7. Enjoy!

I realize you said you were uncomfortable with doing the fastboot command, but it is really the only way to reliably flash ROMS while S-ON unless the ROM is specifically packaged for S-ON (most aren't.) And it's best to get some experience flashing and running the ROM before you play around with a kernel. A kernel is all the low-level, background code that interfaces with the hardware of your phone, such as the camera and audio and how the cpu runs. The ROM is the software layer built on top of the kernel and contains all of the files to make it a usable operating system for your phone.
[HTC Rezound] darienms1986:
Re: [ROM][JellyBean][AOSP][01.12.13] ┬─┬ ノ( ^_^ノ) v2.3 LINARO! [Android 4.1.2]

If I'm not mistaken thou don't you need to have a booting kernel for both snuzzo and shrikes to work, otherwise it won't boot? Thought it only replaced certain things from a booting kernel
[HTC Rezound] ChuckZv2:
Re: [ROM][JellyBean][AOSP][01.12.13] ┬─┬ ノ( ^_^ノ) v2.3 LINARO! [Android 4.1.2]

Lol, im new to all this but I actually enjoy learning about these things so i dont mind reading the 101. I guess you can say im fairly tech savvy, I really appreciate all the help Ive been receiving throughout the forums too with all this.

About using the CMD Prompt to boot the .img file I AM comfortable with it, its actually the only way i have been doing it since i flashed straight CM10.

I want to check out Neos version of CM10 the AOSP version for S-On. I want to make sure I download the correct file to FLASH as well as the corresponding Kernel to fastboot for that. Is that build ION or Pre-Ion. I would appreciate if someone can forward me the links i need to check out build. ^_^

Thanks you guys!

Sent from my ADR6425LVW
[HTC Rezound] darienms1986:
Re: [ROM][JellyBean][AOSP][01.12.13] ┬─┬ ノ( ^_^ノ) v2.3 LINARO! [Android 4.1.2]

It is pmem not ion
[HTC Rezound] shrike1978:
Yea. A fully booting boot.img is both a kernel and a ramdisk. We both use the same installer (thanks Snuzzo and con247) that extracts the ROM's ramdisk from the boot.img, and builds a new boot.img with it an our kernel. Without a booting kernel on the device (and thus, a working ramdisk), our installers won't work properly.
[HTC Rezound] brenuga:
Re: [ROM][JellyBean][AOSP][01.12.13] ┬─┬ ノ( ^_^ノ) v2.3 LINARO! [Android 4.1.2]

Download the main rom link (version 2.3) from first page of this thread. Copy it to your sdcard, then unzip it on your PC. The boot.img is in the top of the extracted folder. Flash rom zip in amon ra then fastboot flash boot boot.img. is all you need to do. The boot.img contains the kernel that goes with this rom by default. It works fine and I don't recommend changing it till you learn more.

Normally, to install an updated or different kernel, you have to go into amon ra, use wipe cache and wipe dalvik cache, then flash the kernel zip file. Funky Kernel, which is the most stable and featured one for the Rezound, does a lot of work behind the scenes for us s-on folks. But if you read the change log, neo swapped out funky kernel for another one a few versions ago for what I'm assuming are temporary compatibility issues. So like I said, just stick with the default kernel for now.
[HTC Rezound] ChuckZv2:
Re: [ROM][JellyBean][AOSP][01.12.13] ┬─┬ ノ( ^_^ノ) v2.3 LINARO! [Android 4.1.2]

Should I do a Wipe at any certain point?

Sent from my ADR6425LVW