yashsingh1/xdaforums huggingface dataset:
[HTC Rezound] Quadman:
Neo I did some tinkering around to try installing jb 4.3 camera with no luck. Then I rebooted into recovery and wiped davlic 2x and flashed your NeoSphereCamera and wiped davlik 2x again before rebooting. After rebooting I gotta wild hair up my but and decided I was going to try installing 4.3 over yours. Too my surprise it said it will update it. After the update finished I closed es file explorer and opened up the camera and checked out pie. It's awesome. Took a video and it got stuck. Closed and tried to reopen it and got cannot link gallery to camera. So rebooted to recovery, wiped davlik 2x times and rebooted. Haven't tested everything but haven't gotten any errors or force closures. Videos and pics look great. Downloaded it from here http://galaxy-note2.wonderhowto.com/how-to/get-new-jelly-bean-4-3-camera-gallery-apps-your-samsung-galaxy-note-2-no-root-required-0147690/

Running 2.9.1 light inverted

Snuzzo's 3.8 funkybean kernel
[HTC Rezound] weaverinva:
Back to original 2.9.1 flyhalf kernel....

LOBBS et al You may not have to flash your entire rom to get rid of the soft reboots. :)

I had been using AR 3.16 (and 3.15) and using it to flash across the last 6 months of many ROMs. Perhaps the method of flashing has something to do with the soft reboots. I was skeptical.

I decided that I wanted to revisit using the original kernel from 2.9.1. So I decided to extract the .img from 2.9.1 and then flash via fastboot flash (the most pristine way to flash the boot image).

After I did that, I flashed TWRP (so I can script and queue multiple zips for flashing), and booted to recovery wiped cache and dalvik and rebooted.

All is well with no soft reboots even with 96/1620. I was pretty stoked that it has worked so well. I would not have any idea what small anomaly would cause such a problem.

Oh well, it seems success at the moment. I hope it is not placebo.....
[HTC Rezound] usefulidiot127:
2.9.1 definitely hasn't been one of the more stable roms I've been on, but the good has still outweighed the bad. At least until yesterday, when my phone just decided it was time to crap all over itself at Lollapalooza. What would be different about the usage at Lolla? Well the cell signal sucked, I was frequently turning the screen on/off, checking notifications very often, etc. It would get stuck on a black screen about every 4th time I tried to use it and this resulted in more soft/hard reboots than I can count. Also lots of system UI crashes and massive laggy slowdowns.

I think I need to go back to a stable ICS rom for the rest of the weekend. For what it's worth, I've always had a few more problems than your average Rezound flasher. Maybe my hardware is just finicky.
[HTC Rezound] crushme1:
This rom is great. I can use the rezound with a gsm sim card from Vodafone.
[HTC Rezound] mjh68:
I had a similar issue , when I went camping. Using navigation, streaming music and surfing the internet sent it into freezing and constant reboots. I just reverted to a sense backup for the rest of the trip.
[HTC Rezound] AtomicFizzle:
Man, that could really ruin camping!! Your 3D HDTV and bluray player still worked, right? :P hehe
[HTC Rezound] Quadman:
Just in case you haven't gotten this Neo. JB 4.3 kernel and framework for the one.

www.androidpolice.com/topics/android-os/jelly-bean-4-3-android-os/
[HTC Rezound] mjh68:
Hehe, sounded bad :o I was talking about driving to and from :)
[HTC Rezound] Dark Jedi:
Should always carry a map and I mean of the paper kind.
[HTC Rezound] netjetman:
screen keeps turning on

Been running 2.9.1 for awhile now and really liking it. I have, however, noticed that my screen keeps turning itself on fairly often. It could be a new app, or it could be failing hardware, but I just thought i'd see if anyone had any ideas.
[HTC Rezound] aznjosh:
I couldn't get native USB tethering working on Infection 2.9.1 running Funky 3.5 using Windows 8. The Remote NDIS driver from both Microsoft and HTC refused to install. I was able to get USB tethering working though using Clockworkmod Tether and it works great now!
[HTC Rezound] Neo:
Utill you cap out on your daily free allotment and have to buy it lol

I heard somewhere that for windows 8, you should install HTC sync ans the drivers and then set up the ndis ans it should work
[HTC Rezound] aznjosh:
I tried that and it didn't work. Couldn't install any of the drivers in their HTC driver folder. I use mobilism.org so ;)
[HTC Rezound] Piercing Heavens:
I installed this fresh from a rooted RUU install and was wondering which kernel goes with this rom? I'm S-on so i extracted the boot.img and everything works fine but I was wondering if there is a better kernel for this rom at the moment. Looking for stability.
[HTC Rezound] tigerxchaos:
Keep in mind when doing this, if you don't have a program like Kernel Tuner that will allow you to set core speeds independently, only CPU0 can be changed from the Performance menu. CPU1 will remain at 96MHz.
[HTC Rezound] SteveG12543:
True! I actually forgot about that, just changed it now. Thanks!
[HTC Rezound] beezer94:
Reality my device is running great, but I am curious why your cpu float-point score is practically 4 times mine? I got up to 8160 score with both cores at 1836, performance, sio (seems always slightly higher score than row), but only 489 cpu float. Again I just did this for *hits & giggles, i normally don't have it overclocked.
[HTC Rezound] Neo:
If it's stability you want, then the included kernel is the best choice as it is the "stock" kernel that most of the other modified versions came from. The only thing I would do however is us your minimum frequency to 384 ans drop your max to 1512 (if going for stability).

Beats me. As I mentioned earlier, I was running a much older version of this rom. Major difference however is that I was using iHateWebOS's kernel before he changed it to Hiro which is most likely the biggest reason why the score was so high. That wasn't a first try test either. That was me trying to get the highest possible I could on my rom (legitimately)
[HTC Rezound] Dark Jedi:
Don't know why people are worried about benchmark speeds. Not like anyone will keep those settings for daily use. Guess boys still seeing who bigger well in this case faster speeds.
[HTC Rezound] tholmes8291:
Hey Neo how's Alchemy coming? Haven't heard mention of it lately.
[HTC Rezound] onthehole:
I've been running solid with no reboots (softies) that I am aware of for the past three days. The oy thing I'm doing different is using kernel tuner. Unrelated? Probably.

I just wonder what was causing it, or if it's still happening when I am not looking. Running smooth on HIRO with kernel tuner though.

Sent from my HTC Rezound.
[HTC Rezound] 3L3C7R0:
I believe he's shelving it for now.
[HTC Rezound] Dark Jedi:
He put it on hold beings 4.3 came out. Think he said he is going to rework the whole thing.
[HTC Rezound] LOBBS:
I keep my Rez at 1836 on both cores nearly 24/7. Currently using lulzactive as the governor. I've been doing that since the OC kernels first dropped. I've got chargers at home, work and my truck so I'm never overly concerned about battery life. The only time I dial it back to 1512 is if I know that I'm going to be away from a charger for an extended time. This is the first and only Rez that I've had and its been going strong since Feb of 2012. Of course, it is one of the good rev. B hardware Rezs that'll take anything you can throw at them.
[HTC Rezound] jagrave:
What is rev. B hardware mean?
[HTC Rezound] LOBBS:
There were a couple of different hardware runs with the Rezound. A, B and XA I know of for sure. It's been awhile since there was a discussion of it on here but the Bs tended to be the stoutest. There was the infamous "pink" button Rezs that had all kinds of problems and there were a bunch of those that came back around as refurbs. I forget which rev. they were but my wife has one. Either the A or the XA, which ever is not the "pink" button run, were hit or miss quality-wise.
[HTC Rezound] stankopp:
Actually, those are my daily driver numbers.

---------- Post added at 04:35 PM ---------- Previous post was at 04:27 PM ----------

How can one tell which rev he or she has?

Mine seems to be one of the stout ones. I have only ever had the re-boot, boot hang problem once and I believe that that was with one of the problem ROMs, 2.6 or 2.7, I believe.
[HTC Rezound] LOBBS:
It's on the sticker under your battery. IIRC, it's one of the last lines on the tag.
[HTC Rezound] NapalmDawn:
Couple softball questions. Using Ktuner-if I wanted a battery friendly setup, what would I set the govenors too? How about the same for performance? Currently both are on interactive and 384/1620.

Is there a stable kernel for this device that has a working wifi tether AND the ability to do a fast charge? On 2.5, I was able to do both but now that I upgraded to 2.9.1, I noticed trickster is reporting that FC is not available. The reason I like fast charge is that at work or at home, I have the Rezzy in a dock. I like to keep it up for glances at notifications (which wake my device anyways) and time/weather/LWP. My tbolt could definitely gain charge in this scenario. My rezzy is a bit more tempermental. Sometimes it can, sometimes the charge goes down. I noticed the other day that antek quick settings took top spot in battery time so I turned it off. It's not helping much with it being off.
[HTC Rezound] gleggie:
I can't speak for Wi-Fi tether or fast charge as i don't use them frequently enough but as for governors, this is what i've heard:

Lulzactive is a great all around governor for balance between performance and battery life.

Wheatly is a solid, stable governor if you don't have a lot of screen on time.

Lionheart is a fast ramping, performance tuned conservative governor for awesome UI smootheness and fluidity

I usually do First Core: 384 MHz/1.2 GHz (slightly UC), Second Core: 384/1.6 (slightly OC). That has guaranteed me rock solid stability, but some of the newer kernels like Snuzzos 3.8 i can go down to 96 first core, 222 second core and still have rock solid stability and performacne, that just takes some testing on your own as each Rezound is different.

Logic behind this is simple. (thanks to [MENTION=4498729]brenuga[/MENTION]) Your phone will handle most easy tasks on the Underclocked first core, with the second core shut off. When you move to more intensive tasks, the fast ramping second core will ramp on quickly to fulfill the task and then shut off (saves battery)
[HTC Rezound] carngeX:
Last line on the P/N tag under your battery. It's at the very end (separated from the P/N by a tabbed space). Should be A, B, or XA.
[HTC Rezound] stankopp:
Many Thanks.

---------- Post added at 06:49 PM ---------- Previous post was at 06:35 PM ----------

Nope. Mine is a Rev A. (but still stout).
[HTC Rezound] NapalmDawn:
Is SDcard0 our internal memory and SDcard1 the physical SDcard?
[HTC Rezound] Neo:
Wasn't feeling like releasing it just yet due to not having a working camera.
[HTC Rezound] acejavelin:
Nope, other way around... at least in Infection 2.9.1 (and I think most CyanogenMod ROMs for the Rez)

Open a terminal window and type "df" without the quotes, and you will see the free space on all mount points... you will see the size of the volumes and can tell that way for sure.
[HTC Rezound] Gornul:
Still on 2.8.1 but been having the same soft-reboot-on-screen-on problem as a lot of other users, getting progressively worse the past few days. And this was with my min/max settings as recommended repeatedly in this thread, no crazy themes or widgets or anything. I run a very minimalist phone. Tried installing CWM Touch to see if that solved it, and I wound up at a boot-animation loop. Going to take this opportunity to get upgraded to 2.9.1 and hopefully recover the work texts from today I hadn't backed up since this morning's TiBu backup.
[HTC Rezound] acejavelin:
Make sure you flash the boot.img or flash the ROM via "fastboot boot recovery.img" if you S-ON or you will really have trouble.

Sent from my Infected Rezound
[HTC Rezound] Gornul:
I'm S-OFF.
[HTC Rezound] sn2hotty:
Thanks for this- that answers my earlier question regarding setting two different sets of min/max. That makes perfect sense. I never experimented like that. I've always used SetCPU, going all the way back to my days with the OG Droid, and SetCPU is a much simpler CPU app that doesn't allow for control of each core separately. I will try Trickster or Kernel Tuner and give this a shot! Do you use the same governor on each? I'm using Intellidemand now with pretty good battery life.
[HTC Rezound] Gornul:
Further results: absolutely no improvement on 2.9.1. Soft reboots a few times per hour, constantly dumping my wallpaper, etc.

[phoneposting]
[HTC Rezound] calvinb1:
You can also use the HTC Dumblock functionality in TWRP to flash the ROM. That way you won't need a computer to fastboot boot the recovery. Works great for S-On folks.
[HTC Rezound] 3L3C7R0:
The soft boots ate rally bad on this ROM. I've never had this many on any ROM ever. I've tried multiple kernels as well. I'll try reflashing again to see if I can get better stability but I'm pretty sure it's this ROM.
[HTC Rezound] abby_nitewolf:
I haven't had any soft rebooting problems. I'm running this with hiro 7/20 at 1.83 Interactive on row scheduler. Only thing i noticed is the random freezes but only last about 5 seconds.
[HTC Rezound] nimbice:
Not many people using infection experience a lot of soft locks so it isn't likely the Rom. You might think otherwise from all the complaints but I get the impression they are the squeaky minority. Maybe I'm wrong?

Most aosp kernels for rezound default at dangerously low voltages to try to balance out the massive battery drain introduced with ICS that left the rezound dead in half a day even at idle. Since rezound has a famously varied level of hardware quality from one device to another some users experience a lot of instability using a Rom packaged with such a kernel. Since this Rom is built for performance it defaults to a kernel set to more risky settings.

You should find a lot of suggestions in this thread urging those having issues to bump their min cpu up a notch until stability is regained. I myself have to do this every time I touch a kernel since my phone doesn't handle the aggressive under volt settings so well.

If that doesn't work then you might try a few other suggestions such as completely wiping the phone and reloading from scratch not using any restore apps like tibu and maybe switching away from amonra recovery if you're using that. Then restart with the cpu tuning process again.
[HTC Rezound] 3L3C7R0:
I've been using neo's rom's since ics. I've tried every one. I'm active on the forums every day. I've tried every kernel, all the cpu suggestions. Nothing fixes the stuff boots on this Rom. If you read this thread, you will find that there are many others with the same issues. I know what I'm doing. I've yet to have this problem with previous rom's.
[HTC Rezound] nimbice:
You've used every infection version and only have significant issues with this particular rev? Have you checked the md5 and/or tried downloading it again?
[HTC Rezound] sn2hotty:
I'm on 2.9.1, with Hiro from 7/7. No issues at all, and smooth as butter. I think Nimbice has some good suggestions for you. I had one soft reboot a few days ago, but I dismissed it as par for the course, especially since I was beating the hell out of my phone at the time (experimenting with Showtime Anytime). LOL

Sent from my Infected Rezound
[HTC Rezound] stankopp:
Have you added or updated any apps recently? When you flash a new ROM, how do you restore apps?

After a ROM flash, following a wipe, I always allow Google to restore my apps. I do not even have TiBU or any other backup/restore app on any of my Android devices. The only backups I do are Nandroid from recovery.

I have been running 2.9.1 since release without any kind of problem.
[HTC Rezound] unconfuse:
I couldn't even imagine not using some form of app restore. Using tibu is a must for me. I get black screen or reboot a couple times a day maybe. From my experience I feel it's more of what I'm doing at the time that pisses the rez off. I have recently defected to liquid smooth and hiro kernel. That has been the most stable for me.
[HTC Rezound] replica9000:
Think it depends on the ROM / kernel / firmware combo. When I was on Neo's Adrenaline ROM with Funky Kernel and GB firmware, it was stable with good battery life. I had my min set to 192mhz -150mv without issues. One of the governors though would always cause reboots, so I didn't use that one. I haven't been able to undervolt that much since being on JB though.

Tron 2.1 has been pretty solid for me also. I haven't tried Infection in a while. I've had issues with settings failing to set until a reboot with the last few releases prior to 2.9
[HTC Rezound] acejavelin:
App restore could be the issue here actually, restoring app data into some ROMs via TiBu/UltiBU/MyBU can cause issues that make the phone, well, misbehave. This was very common going from GB to ICS but can also be an issue going from one ROM to another that uses a similar build. If you are having issues it is always preferable to reinstall from the Play Store rather than restore, there could be something there causing an issue that you don't foresee.

I have been running Infected 2.9.1 for a while now (since the day after release, just to make sure nothing was really hoky), no reboot, softboot, freeze, etc, for over a week straight and I use my phone frequently. My only changes to the core system settings from the original ROM are upping my minimum CPU speed to 384MHz, prior to that I was getting occasional wake-up reboots, but since then nothing, as solid as stock Sense ROM from HTC!
[HTC Rezound] kodiak799:
I'll agree with TiBu restore causing problems. I had a few apps causing freezes even after re-flashing 2.91, which shouldn't happen but maybe because I went from developer to light or something.

And the biggest was the 96mhz min cpu setting, which would keep coming back unless I hit "restore on boot" (I have my phone auto reboot every night).

I've had almost no issue with any of these roms (aside from that min cpu setting) when allowing the market to restore all my apps.
[HTC Rezound] sn2hotty:
Titanium restores never gave me a problem until recently, BUT you have to make sure to restore user apps and user app data ONLY (white items). NO system apps (red items) or system data (green or yellow items). Then you are asking for trouble.

The problem I am having recently, at least with Infection 2.8.1 and 2.9.1, is that TiBu freezes during the restore process, at varying points in the process. Can't figure out why. Happens on both mine, and my wife's Rez (YES, I infected the wife's Rez too! LOL). I found a good work-around though: I create a flashable zip with TiBu of the apps to restore (TiBu has this option in the menu), and flash the zip in recovery (TWRP). Then when the system reboots, TiBu kicks in and begins restoring the data for the restored apps. Works fine, and after one more reboot, all good again. :)
[HTC Rezound] NapalmDawn:
I know I personally can't stand flashing without at least SOME restores. Once you get an app and such setup the way you want, it becomes such a pain to think about doing it ALLLLLL over again. Even launchers. LIke apex has a backup/restore thing but it's not like it puts the widgets back when you had it.

That being said, I found that app restores are a bit of a pain. I love the ambiance app. Awesome for grabbing nice background sounds if you need some white noise. Each sound you want is its own download. If I restore from TiBu, ambiance THINKS I have the sounds and shows it in my library but it will play silence until I redownload the sound. Notifier Plus also seems to be a tad sketchy via a restore. XBMC also won't restore with full settings via a TiBu. You just have to experiment with which ones work and don't. For those with the soft boot issues, have you looked a few pages back to check on the hardware revision you have and see if you have the more notoriously twitchy models?

---------- Post added at 07:01 PM ---------- Previous post was at 06:59 PM ----------

I've had this happen with some tablets using TiBu. Some apps just get stuck and won't restore. My most recent case was taking an Acer 500 up from ICS to JB. I'm talking even some Acer based things....on an Acer tablet LOL.
[HTC Rezound] kodiak799:
Same here, but even user apps and user data have given me a few problems.

Best solution I've found is to let market restore the apps and then restore data only for those apps it matters (i.e. apps with login passwords and/or extensive settings like Locale).

Yeah, it's a pain but I've only flashed about 6-7 Infection roms in the past year.
[HTC Rezound] acejavelin:
I had this problem on and off with AOSP ROMs on the Rezound using TiBu, that is why I switched to UItimate Backup (plus the Pro version is significantly cheaper than TiBu Pro), I have also heard My Backup works as well.
[HTC Rezound] Rezinator:
Thanks for the tip about the zip.

I was in the EXACT same situation as you [no issues until 2.9.1]....Then i was getting constant freezing during TIBU restores, and reboots during the TIBU backups. [That BTW was my only issue I had with 2.9.1] Once I changed the min frequency to 384 like Neo suggested, TIBU worked perfectly....I've been testing this "theory" about 1/2 dozen times since changing the min freq about 1.5 weeks ago and it's working great. What's also weird is that change also made TIBU much faster. Have you changed frequencies and tried that?

Rez.
[HTC Rezound] unconfuse:
I'm sorry but I still have trouble believing that restoring user apps and data regrades the os. The only problem I ever had going from one android os to another was the location of the restore. Until I get some concrete evidence I will continue to use tibu or some form off restore. I think there is just too much instability in these current releases. But for me to stay on the bleeding edge it's worth it! Neo and the rest do a great job building and supporting us.
[HTC Rezound] Uzephi:
Mine is an XA model and have had No issues (except doing TiBu restores, but that is across the board). Mine must have been one of the good "sturdy" ones.
[HTC Rezound] sn2hotty:
In a manner of speaking, yes. What I mean is, yes, I have upped the min frequency to 384, BUT, up until now, I only did that once my apps were restored- specifically, once SetCPU (my kernel control app of choice) is restored. So that means that between the time I reboot the ROM for the first time, and the time SetCPU is restored, and while TiBu is restoring, the min is set at whatever the default is (96 or 192). The next time I flash a ROM update, I will up the min to 384 immediately using the Performance menu in the ROM. Thanks for making me aware of this!

Weird though- now that I think about it, while TiBu is running, you wouldn't think the CPU would be at the minimum level, would you? I would think it would be close to max while running a restore. :what: