yashsingh1/xdaforums huggingface dataset:
[HTC Rezound] Flyhalf205:
You would loose WiFi unless you pulled and replaced the modules with it also.
[HTC Rezound] Neo:
Gonna test the ion rom in a bit to see if it's fixed there as well.
[HTC Rezound] _litz:
Oddly enough, I still have flicker in maps ... but it doesn't seem to do it anymore inside navigation ...

Plus the "hash" on the popup menu in navigation is now fixed when overlays are enabled.

I still have to wonder how much of this is the rom, and how much is this godawful crappy new version of Maps.
[HTC Rezound] brenuga:
Solution to all of these maps issues is for someone to post a backup of previous maps update, before the glitches began. I accidentally overwrote my backup. :(

Using titanium backup pro you can detach apps from market so it won't update. Then when Google gets their act together, you can install new version.

Somebody have backup?
[HTC Rezound] manchucka:
6.14.4

http://db.tt/ipx4HyIM
[HTC Rezound] DCnovicky:
Don't know how to do that.. But not really an issue since I never use wifi.

Verizon 4G network + unlimited data = NO WI-FI :)
[HTC Rezound] Talguy:
I installed the 7/23 update on my phone last night and so far so great. With regards to the new google maps, flickering has been significantly reduced to the point that its actually usable. It still flickers here and there but its not that bad. I haven't tried out navigation yet, but it sounds like thats even more stable.

Thansk flyhalf for keeping this phone alive.
[HTC Rezound] greenhead916:
Upgrading/Optimizing Apps

Sooo...this is probably a rookie question.

Any time after I update, my phone takes a few minutes or so updating/optimizing the apps on my phone. But, it only happens one time. I assume that is expected that it only happen once. It would suck to do that every boot.

I can't say I really understand what it is doing, but, is there a way to force the phone to do it periodically (besides updating)? I remember in ICS, if you took the phone off fast boot it would do it every time. Anyway with CM?
[HTC Rezound] mjones73:
Wipe cache, that's what it's rebuilding.
[HTC Rezound] ssb13:
I tried this once, but try setting your phone to Expanded Desktop and see if flickering still happens in Maps?
[HTC Rezound] brenuga:
Don't wipe cache, wipe dalvik cache. The preferred way to do it is in a custom recovery you might be using. If you don't know how to use a recovery, try an app like ROM Manager that lets you do it from within android.

Dalvik cache is basically like a set of data that helps applications load faster than they would normally if they had to start from scratch. Windows and Mac PCs do the same thing, you just don't notice it. It's called pre-loading or pre-caching. Every time you do a significant update to your ROM or kernel, you should wipe dalvik cache if your update script doesn't already do it for you. (If it does it automatically, you will see the screen that says "Android is upgrading...")

Wiping Dalvik Cache + Fix Permissions in recovery is one of the best regular maintenance tasks you can do to keep your ROM stable.

---------- Post added at 12:22 PM ---------- Previous post was at 12:21 PM ----------

Thanks dude!
[HTC Rezound] Talguy:
Just tested it out. Its a lot smoother if expanded desktop stays disabled.
[HTC Rezound] scy1192:
Whelp, Android 4.3 is releasing today and CM10.2 development is starting. Hopefully this will be easy for the devs to port over.
[HTC Rezound] manchucka:
Re: 7/24 experimental build

Flyhalf, can you spare a word about today's (7/24) experimental build?
[HTC Rezound] Flyhalf205:
A few kernel experimental commits basically.
[HTC Rezound] a.mcdear:
So, whats the deal with the 10.1.2 build? I was using that for awhile and was never getting update notices... Switched to the latest build and now it gives me the 10.1.2 build as an upgrade option. Should I have just stayed on 10.1.2?
[HTC Rezound] cmichaelt:
10.1.2 is the latest stable build. The build you just flashed is either a nightly or experimental build which can be buggy and my not be suitable for daily use.
[HTC Rezound] underdog01:
I am finding the latest builds (including experimental) to be more stable. I have not had a random reboot since the 21st build. That includes using the 23rd build and now the experimental.
[HTC Rezound] bacon612:
Anyone kind enough to link the latest gapps wlto go best with this ROM? Perhaps maybe even a link in the OP? I am hungover and struggle to find them....
[HTC Rezound] manchucka:
These work great: http://xdaforums.com/showthread.php?t=2012857

[GApps][Unofficial][4.2.2/4.3 Testing][7-25-2013]

? ?
[HTC Rezound] power950:
Any reported problems with the "experimental" build I usually jump from nightly to night without a second thought but I the the word experiment is kinda scaring me?
[HTC Rezound] bunchies:
Is it just a 4.3 gapps?

CyanogenMod has put 4.3 in there source code today so that and the "official gapps" should get released soon.
[HTC Rezound] Flyhalf205:
It is up. But just not ready to build yet. Excited :)
[HTC Rezound] bunchies:
They said not to build with it yet lol I can't wait any longer, been fallowing 4.3 since November even though its not a big update

Hopefully they fix the build errors soon so I can get it off my mind :rolleyes:
[HTC Rezound] manchucka:
Both 4.3 and 4.22

That link has both 4.3 and 4.22 GAPPS.
[HTC Rezound] kkozma:
I tried to build a hybrid of CM10.1 with the 4.3 bluetooth stack today since all I really care about is if AVRCP works. I got it to build and it connects and streams to my headunit no problem, but no AVRCP.

I did dirty flash over the top of my CM10.1 ROM though, so it's possible that may have been what kept AVRCP from working. I may mess around with it some more tomorrow.

On an unrelated note, my build did fail when it tried to build VoicePlus though... Is that working in the current builds?
[HTC Rezound] bunchies:
Hate to bring this up again. But did you use a powered otg cable or just a regular otg cable being powered by your phone when you we're testing it?

Also I think I read somewhere that you can mount a flash drive with otg in twrp, Is that true?
[HTC Rezound] Flyhalf205:
Not sure who you were directing that to but I tried a powered usb hub

Just for fun. Going to build 4.3 and see what errors I can find!
[HTC Rezound] kkozma:
I can save you at least 2 minutes. In libhardware/modules you'll need to get rid of camera. Both the directory and in the android.mk.

Iirc, camera is declared somewhere else. Msm8860-common I think.
[HTC Rezound] Flyhalf205:
Yep Yep. I'm at C2DColorConverter.cpp:37:28: fatal error: linux/msm_kgsl.h: No such file or directory.... That error I don't understand. I am looking at that file. It exist!!!
[HTC Rezound] bunchies:
it was toward you lol and ok well I made an otg powered one a min ago, hopefully someone can figure it out. Otg would be insanely useful

And awesome :thumbup: hopefully CyanogenMod can figure it out soon, I also heard 4.3 was breaking root
[HTC Rezound] TheBr0ken:
Chainfire SU works for root ;)
[HTC Rezound] Flyhalf205:
I can't get it to build. May try tomorrow when they get more bugs sorted out.
[HTC Rezound] bacon612:
Dirty flashed the 7/26 build and lost camera and gallery. Reverted back to nandroid
[HTC Rezound] _litz:
I got to the same point ... something isn't referencing it, I guess ...
[HTC Rezound] Flyhalf205:
Got past that error last night. Updated my git with the fix for it.
[HTC Rezound] kkozma:
I've been trying like hell today myself... So many issues. I think even at this point if I get it to build I might be too afraid to try and flash it. lol

Looks like the hangup is really going to be the audio-caf for us. Mine dies at AudioPolicyManager.cpp. I tried a couple things to get around it and it's been running for a while, but it's crapping out elsewhere and I don't know if it's even tried to get back to AudioPolicyManager yet.
[HTC Rezound] Flyhalf205:
Building DNA at the moment. I think we got a successful build. Have a few ideas of how to get passed the AudioPolicyManager for the Rezound then who knows what errors after that. Well I know 1 error after that. The recovery.fstab will need to be updated.

I get off work in 1hour. No girlfriend tonight. My goal is to get this thing built by midnight :)
[HTC Rezound] xjbhx:
I did not have that issue. Dirty flashed and is running just fine.
[HTC Rezound] Flyhalf205:
Was hoping no one ran into the problem. Download it again. I had to re-upload the file because of camera changed I was making in 4.3 that I forgot to revert for 4.2.2. It's good to go if you want to give another try.
[HTC Rezound] bunchies:
Does this mean 4.3 is ready for building?

https://plus.google.com/app/basic/stream/z12qtfdovqnpid3kx221hl44tznvd3hhv04

Its running on arm7 device
[HTC Rezound] TheBr0ken:
Just need to get our device tree updated, which sometimes is easier said than done
[HTC Rezound] Flyhalf205:
We have build and boot on the HTC DNA. But the dependencies it uses are a higher priority of getting fixed than ours. Updating our device tree is the easier part.
[HTC Rezound] TheBr0ken:
looks like Google changes things, just to change. recovery.fstab went from needing to list from

# mount point	fstype	device	[device2]

to

#<src>	<mnt_point>	<type>	<mnt_flags and options>

so for example from this:

# mount point	fstype	device	[device2]

/recovery	emmc	/dev/block/mmcblk0p23
/boot	emmc	/dev/block/mmcblk0p22
/cache ext4 /dev/block/mmcblk0p36
/data ext4 /dev/block/mmcblk0p35
/sd-ext ext4 /dev/block/mmcblk1p2
/sdcard	vfat	/dev/block/mmcblk1p1
/system ext4 /dev/block/mmcblk0p29
/misc emmc /dev/block/mmcblk0p24
/internal_sdcard vfat /dev/block/mmcblk0p38

to

# Android fstab file.
#<src>	<mnt_point>	<type>	<mnt_flags and options>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
# data partition must be located at the bottom for supporting device encryption

/dev/block/mmcblk0p23 /recovery	emmc
/dev/block/mmcblk0p22	/boot	emmc
/dev/block/mmcblk0p36	/cache	ext4
/dev/block/mmcblk0p35	/data	ext4
/dev/block/mmcblk1p2	/sd-ext	ext4
/dev/block/mmcblk1p1	/sdcard	vfat
/dev/block/mmcblk0p29	/system	ext4
/dev/block/mmcblk0p24	/misc	emmc
/dev/block/mmcblk0p38	/internal_sd	vfat

I'd be nice if they could leave the stuff that works alone, but that's why they get paid the big bucks.
[HTC Rezound] power950:
Idk if its just me but I'm on your 24 build and the Google maps navigation still spazzes
[HTC Rezound] TheBr0ken:
I think it's doing that for everybody to some extent
[HTC Rezound] mhamann:
Using the nightly from 7/26, my Rezound occasionally seems to freeze while the screen is off. Attempting to turn it back on causes the red soft keys to light up, but nothing will show up on the screen, forcing a battery pull.

I'm really looking for more of a daily driver than bleeding edge. Should I be using the latest from 7/26 as I am, or the "cm-10.1.2-vigor.zip" version from July 12? Which should be better / more stable?
[HTC Rezound] bacon612:
I can second the screen freeze issue on the 7/26 build. I think something changed the Prox sensor in this build.
[HTC Rezound] TheBr0ken:
Some say that changing your minimum CPU speed to 384 MHz, clears up those issues
[HTC Rezound] ravkal:
I get this same issue, and have had it for quite a while. However, if I just let the phone sit for a moment it'll run the boot animation for a couple seconds and then everything is fine.

CPU adjustments don't seem to help. I downloaded a couple different kernels the other day but I've been too lazy to trial and error it.
[HTC Rezound] heleos:
I've had the same thing happen to me with every rom and every kernel I've tried in the last month. While it usually is only a soft reboot, it's really killer on my battery when it happens, sometimes dropping ~10%
[HTC Rezound] TheBr0ken:
What recoveries are you guys using?
[HTC Rezound] HowardZ:
Cyanogenmod 10.2 is unofficially available for the VZW Samsung Galaxy S4. It's not perfect, but is a start. I imagine the rezound will get it soon.
[HTC Rezound] kpritchard:
TWRP 2.25
[HTC Rezound] Chucktr:
TWRP 2.6 is available

For recovery, TWRP 2.6 gets installed when you use GooManager. One of the first things we get installed after the OS is Google Play Store and then GooManager IF it is not already there and then use it to install TWRP. Oh forgot, you must be 'root' in order to use GooManager. So really the first thing after system install is to UnLock and root IF you are not already.

Question was asked a while back as to whether or not TWRP 2.6 works -and- the answer is -- YEP. In both ICS and JB.

Take care,

Chuck
[HTC Rezound] KnightDavid:
I was running happily on the 10.1.2 version for several weeks, then I updated to the 7/26 build and after a few hours started getting terrible lag. Had to reboot my phone to clear it, had to do a battery pull once, but even after reboots the lag would return after a few hours. I was just about to revert to the 10.1.2 again last night when I saw there was a 7/30 uploaded, so I tried that first. The lag didn't wait a few hours, it was almost instantaneous. Back on 10.1.2 again now and completely lag-free after several hours.

I think the 10.1.2 "stable" release didn't have the CPU governors, is that right? Is that what is causing these issues?
[HTC Rezound] bacon612:
I've been getting random reboots on 7/26 and also 7/30. Stock kernel stock clocks (384 - 1512) and stock voltages. Anyone else? I'm wondering if I need to do a clean wipe or if its ROM related.
[HTC Rezound] scy1192:
I find the performance governor to be so smooth. I know it reduces battery life, so I disabled the second core to compensate and it's still just as fast. Could there maybe be a bug in the other governors that make it slow?

edit: I'm on 7/26 if it matters. The choppiness seems to have been in all the CM10.1 roms though.
[HTC Rezound] Flyhalf205:
Those who have lagging issues on latest few builds. Download and try it again.

Thanks
[HTC Rezound] 302skinny:
Tried to download 10/30 from 10/26 via OTA Updater and md5 verification failed 5 times in row just now.
[HTC Rezound] Flyhalf205:
Its a good md5 I just haven't updated it in cmupdater so it will fail. You'll need to download from the download link in OP.
[HTC Rezound] Flyhalf205:
Those getting bad lag. Does it happen when you wake your phone from sleep? I am wondering if that is why we getting so many reboots when waking the phone up.
[HTC Rezound] Talguy:
Yes. That's when it happens to me on the 7/23 build. Especially when I wake the phone and boot Pandora. Hasn't happened yet today since I upped the min frequency to 300+MHz.

Keep up the good work
[HTC Rezound] tigerxchaos:
I updated my girlfriend's Rezound to 7/26 a couple nights ago (she was still on 5/05). Clean flash. She started getting the lag effect not long after updating, but didn't mention the issue til tonight. It was so bad, the phone was nearly unusable most of the time. Rebooting the phone did no good. Finally I went in and changed the minimum CPU speed back up to 384 from 96 and it fixed the issue right away. Time will tell if it comes back.

I am switching out my Rezound for a Galaxy S3 due to some repeat defective replacement phone issues from Verizon, so I won't be around much any more except to eyeball updates for my GF. Flyhalf, I want to thank you especially and the rest of the Rezound developer community so very much for all the work you've put into our phones. I know you will do amazing things with your skills. Who knows... you might be the one to bring a fully functional ION build to the Rez. :) Good luck!
[HTC Rezound] nameiner:
That's when I get the lag too.

And yesterday I got a call and couldn't pick it up. The call screen came and whatever I did it didn't pick up. Then the boot animation came for two or three second and after that everything was fine again. I'm running 384 MHz min frequency and it doesn't happen very often. But still it happens. Doesn't seen kernel related as I had it with three different ones.
[HTC Rezound] tigerxchaos:
GF has been starting to get random reboots on 7/26. Happened to her this morning when she opened her browser.

Can anyone running 10.1.2 speak to whether or not they are running into reboots on that build? Thanks!
[HTC Rezound] castrand1:
I had random reboots on the 7/26 build. Can't really pin it down to something specific, though. I am currently on the 7/30 build since yesterday and so far, it has been working great.

The 10.1.2 stable build, I had no issues.
[HTC Rezound] Jonman409:
IIRC they all use flyhalfs kernel as a base, so it still could be unfortunately.
[HTC Rezound] Talguy:
its been 24 hours since I went from 96MHz to 384MHZ minimum frequency and absolutely zero lag, freezes or reboots from waking the phone up. This is all on the stock 7/23 kernel
[HTC Rezound] kpritchard:
I'm running 10.1.2 and have been for some time with no issues other than a reboot here and there. The reboots that happen though are only when on min CPU of 96 MHz. I'm generally running INTERACTIVE governor and Min CPU frequency of 384 and a Max of 1728. Everything runs smooth as can be. Also if you want an even smoother ride you can turn off (as I have) the Window/Transition/Animator scales and it helps just a little bit, I don't need as much aesthetics =P waiting until 4.3/CM 10.2 before I go anywhere else since I'm content with 10.1.2 for now :)
[HTC Rezound] kook1:
Beats & SRS Audio

will i still have beats and srs audio:confused:

---------- Post added at 07:00 PM ---------- Previous post was at 06:09 PM ----------

Does Beats and SRS Audio work with this root?
[HTC Rezound] jagrave:
Is twrp the recommended recovery for all current roms? And dumb question, but if a Rom has aroma installer I'm assuming it won't work with twrp correct?
[HTC Rezound] bunchies:
Twrp is recommended. And no the aroma scripts work in twrp

Aroma also has less features
[HTC Rezound] jagrave:
Oh ok. I think I'm still on amonra 3.15. The last time I tried to flash a recovery it wouldn't work. I ended up with no recovery And when I did manage to get my old recovery back it couldn't access anything so I had to use that update script that everyone used to update radios to finally get it to work. Could you post the correct way to flash it? Thanks.
[HTC Rezound] iamwalterwhite:
The correct way to flash it is to rename it PH98IMG, place on the root of your SD, and flash in your bootloader. However, the method that I used to change my recoveries recently was Snuzzo's lunar tools. If you check out that thread you will find the simplest way to flash a recovery and you can do it all from the rom side.
[HTC Rezound] bunchies:
I use fastboot to flash recoverys, In my experience you can flash recoverys on top of other recoverys with no problems because all it does is just re-wright the IMG file. I am s-off but I'm not completely sure if that matters because I didn't start flashing anything till I was s-off. So I am not a experienced S-on user when it comes to flashing things in bootloader

But if you place the .IMG file of the recovery in your adb folder and put the phone in fastboot while connected to the PC run adb and type:

Fastboot flash recovery recovery.img

Assuming the recovery img file is named recovery.img
[HTC Rezound] tigerxchaos:
So, I updated my GF's Rezound to the 10.1.2 build.

For some reason, she doesn't have the option to turn off the CRT animation. Of course, because the option isn't there, she doesn't like the animation and wants to turn it off.

Any thoughts on this? I am running Infection 2.9.1 and it does have the option to turn off the animation, and I think it's based off of 10.1.2, so I'm a little confused.

Thanks!
[HTC Rezound] Flyhalf205:
[MENTION=4203241]IAmTheOneTheyCallNeo[/MENTION]

That might be something Neo could answer. cm-10.1.2 doesn't have it. But Neo does not build stock 10.1.2. He does add a few commits in. Could have been one of them. But no way to turn it off really. I am going to turn it off by default cause I don't even like it
[HTC Rezound] _litz:
So anyone got any ideas on the v7 Maps flickering issue?

It's being reported on literally dozens of devices (including, interestingly enough, the Nexus 7) ... and nothing but dead silence from Google on the issue.

I reverted back to 6. Between the flicker, and the "we don't think you need this anymore" removed features, v7 is pretty much useless to me.

Looks pretty (when it's not flickering), but if it doesn't do the handy stuff it used to, what good is it?
[HTC Rezound] d.kozzer:
I don't have any flickering issues with maps on my N7. And on the vigor, I open maps, see the flickering, back out of maps, re-open it and there is usually no longer any flickering. So it's basically only a minor annoyance for me at this point, and aside from there not being any distance legend on screen any more I quite like the new maps.

I'm running the stable 10.1.2 with Funky 3.8.
[HTC Rezound] jtio21:
Is the stable release the only zip on snuzzo's mirror that doesn't have nightly beside the name of the zip?
[HTC Rezound] ravkal:
I don't like being a bother but is anyone else finding their capacitive crazy unresponsive?

Mine have gotten so bad that I've put an app launcher in the notification drawer.
[HTC Rezound] Flyhalf205:
Correct yes.

I have noticed sometimes mine acts funky and vibrator randomly softens to a light vibrate but comes back few minutes later.
[HTC Rezound] Chucktr:
gapps 4.3

Hello,

We have noticed that a number of you are talking about 'Gapps 4.3'. So we started an investigation. As it turns out, it is NOT for use in Android version 4.2.2. Therefore, IF some of these problems we have seen being reported are from individuals using the new 4.3 Gapps, that may be the problem.

Refer: https://plus.google.com/107979589566958860409/posts/RAZtivDzEhV -and- http://www.teamandroid.com/gapps/

Thanks to all and hope this helps,

Chuck
[HTC Rezound] _litz:
If you're referring to the google maps flicker issue, that isn't in gapps; it's acquired directly from the play store.

so the gapps version should not be relevent for that issue.
[HTC Rezound] Chucktr:
Not really anything specific

Was not referring to anything specific, just noting the information that we found -and- IF it might possibly be a problem to some that are using it. Do not know enough about the system to point any fingers at anything specific. Just what we read.

Thanks for noticing,

Chuck
[HTC Rezound] KnightDavid:
Here's another oddity. While on 7/26 or 7/30, when using the Torch widget (flashlight I use while letting the dog out to pee at night) only the bottom LED would light, and very dimly at that. I thought I had a dead LED and a dying LED and was a bit pissed. After going back to the 10.1.2 stable both LEDs are quite bright again.
[HTC Rezound] _litz:
I believe the dim Torch is actually a feature, and it now has progressive brightness levels ...
[HTC Rezound] Flyhalf205:
Like _litz said.. It's a feature that we never used until now. There is an option for high brightness in torch to make both LED's turn on.
[HTC Rezound] adavit:
Idk if its just me, but my signal is constantly bouncing around (I know cm displays differently from sense). Normally I will have one or two bars in my house but it will drop out to the empty triangle. Them even when I'm at work with 4bars it'll sometimes drop out to the triangle. I switched back to 7/17 for the last 12 hours and didn't have any problems until I switched back to the 7/30 build. I didn't know if there was a change to the software or something. Thanks :)

Edit: after a fresh install it doesn't appear to be happening as often.
[HTC Rezound] bunchies:
Do you think the new GPU graph overlay in android 4.3 can help diagnose what's causing game lag in our jellybean ROMs?
[HTC Rezound] highdro:
I was having some issues with games while I was running beanstalk and liquid but I haven't had any since switching back to Flyhalfs builds.
[HTC Rezound] bunchies:
Hmmm, well I've tried every jellybean 4.2.2 build and its laggy games on all and its always been like this.

I'm using liquid right now and I think its based off flyhalfs cm10.1 source so they should be the same

But I just thought the new GPU graph may help understand what the problem is.