yashsingh1/xdaforums huggingface dataset:
[HTC Rezound] kpritchard:
Update 8 made wifi fail & restarts?

I'm currently running CM 10.1 version: 10.1-20130427-UNOFFICIAL-vigor. The build date was Sat Apr 27th. Through the OTA Updater I received notification of update 6, after installing CM 10.1 for the first time, so I updated to the previously listed version. I then received, a few days later, an update to version 8, cm-10.1-20130505-UNOFFICIAL-vigor. Upon flashing it through recovery I run the zip and it installs just fine and then reboot the system, when rebooting and it's optimizing the applications the counter goes up from 0 out of 127 or some number, goes up to about 10 or so, and runs the "cyanogenmod" splash bootup screen that it does with the circle going around, then comes back to optimizing applications but now with a lower counter of 0/80 or so, and this continues till about 0/13 and then finally restarts and starts up at my lock screen. I then notice the following; a) wireless is defaulted to OFF and will not turn on and if attempted to turn on the phone will then "reset" the homescreen as if the phone were just starting up from being off and then come back to the main lock screen. b) the phone then restarts multiple times until I reboot the phone and re-route myself back to version 6 of the update listed in the first sentence of this.

If there are any ideas on how I could go about fixing this and maybe making update 8 work for me that would be much appreciated. I'm assuming re-flashing everything would suffice? Although I'm fairly new to this and it's my first ROM flash that I've done, successfully by the way no real issues. Just figured I'd ask to see if others are having issues and what they've done to fix it.

TL;DR: Update 8 (cm-10.1-20130505-UNOFFICIAL-vigor) appears to have caused for my wifi to stop working and constant reboots until I reroute back to Update 6 (10.1-20130427-UNOFFICIAL-vigor). Any ideas?

Let me know if I need to include any other information.
[HTC Rezound] Flyhalf205:
You s-off? Make sure the new kernel is flashing. Newest build is 5/9
[HTC Rezound] wildstang83:
TBH, it would be my recommendation to just get rid of all OTA updaters and go back to having users manually install the rom. As we see, a few folks are still getting stuck here and there. There are to many variables to consider, ie; Is the user on the latest firmware? What recovery does he have installed? What version of the rom was installed when the user finally decided to update to the very latest version of the rom? The OTA updaters simply just cannot decipher all of these variables and then inject the correct patches or proper wipe processes, yet.

All this said, do not rely on the ota updater to be perfect. If it works good for you, then great. However, if it is not working properly for you, you MUST do a full wipe and manually flash the rom. Additionally if your device is still s-on, you must follow up flashing the rom by manually flashing the boot.img that is in the current version of the rom you are flashing. Even if you are updating through the ota updater. Do not just think you can get away with leaving on the kernel from last build.

Food for thought.
[HTC Rezound] Flyhalf205:
Definitely agree!...
[HTC Rezound] jetrobolas:
Noob question. Is the recent ota from Verizon for radios and whatnot included in your ROM updates? If not is there a way to apply the update (Verizon) through recovery? I downloaded the couple smaller radio update zip files that were linked from this thread and tried to apply them in recovery and they all all failed (even after renaming them). I'm guessing that I can only update the radios using a computer at this point.

I have access to the wife's laptop, it's just a pita with my schedule and hers not jiving.
[HTC Rezound] Flyhalf205:
Not included in the rom. Can't really do that. well could but very dangerous!

For question of the OTA. Please ask them here: http://xdaforums.com/showthread.php?goto=newpost&t=2250494
[HTC Rezound] a.mcdear:
5/11 + FunkBean 3.3.3 is the smoothest my Rezound has run to date!
[HTC Rezound] Luke1213:
agree! i do clean flash EVERY TIME. literally...
[HTC Rezound] kpritchard:
No I am s-on, I'm assuming that probably is the root to most of my problems. Kind of noob question but when its stated to have newest build 5/9 you're referring to the date it was updated I'm assuming? If so, that is simply gotten by re-downloadong the initial rom zip and just redoing the process yes? Sorry if these are basic questions :p

---------- Post added at 08:50 AM ---------- Previous post was at 08:44 AM ----------

Thanks for the response! Alright I'll start manually flashing the latest, ROM zip file I'm assuming. I'm running amon-ra, thought about switching to the one recommended in step one but haven't dome that just yet. I feel that if I were to flash the rom all the time wouldn't it wipe my settings? Like apps etc. I'm sure there are forum posts about loading up a different recovery tool just need to go dig for it when I get home and take it from scratch. Or if I download the latest ROM do I just flash it like an app through flash a zip file and it updates?
[HTC Rezound] Flyhalf205:
Same here. Only new thing in 5/11 is cm changes and https://github.com/Flyhalf205/andro...mmit/e3d55a93bb54bec3ae976a09dc2156eca250d8ac
[HTC Rezound] zkrp5108:
Hey.......Mangos are delicious. Lol:D

I always clean flash it is just all around the best way to avoid pesky errors. Here is my question through I have used titanium back up for years, but restoring data and stuff just leads to problems. I'm fine getting settings back manually but what about apps like tasker. How can I back up my profiles? Or game data (I don't play many) stuff like logins for banking all that good stuff? Does anyone have a reliable wadi to go about keeping that backed up
[HTC Rezound] wildstang83:
Probably not the best thread to ask such a question ;)
[HTC Rezound] bunchies:
I tend to be posting this alot. But I use an app called helium, I do clean flash every 2-3 weeks or on new android versions
[HTC Rezound] zkrp5108:
Sorry stang you are right. :( my bad, this Rom basically is the only thread I use since I've been on this Rom for like a good 5 months.
[HTC Rezound] V0latyle:
I am getting really frustrated with these System UI crashes. Happens even without ANY data restore or app restore. Seems to have to deal with the keyboard (Chrome kept crashing when I was trying to search something, so I force killed it, then reopened and while I was typing, System UI crashed) or the windowshade (get a text message, wake up phone, drag down windowshade to tap on message, System UI crashes).

This is all on the stock kernel.

Also, eMMC has been corrupting repeatedly.

Starting to think maybe it's time for a new phone...
[HTC Rezound] ssb13:
I was having some pretty serious crashes a while back and I decided to back up everything to my computer and format EVERYTHING on the phone. Just a possible suggestion.
[HTC Rezound] wildstang83:
Its alright, no harm.

I have a feeling the aging 20130301 gapps aren't doing us any favors. Probably about time to get an update out for them. It might fix a lot of these issues. Especially considering how its gotten to the point where you have to delete search and then redownload the latest search from google play to fix stuff.
[HTC Rezound] Flyhalf205:
What crashes? I run clean install and flash gapps 20130301 and I don't get crashes with google search? Someone please help me crash?
[HTC Rezound] twolasrnames:
Mine crashes when the screen rotates. It's not every time, but it seems like if I have a cursor in a text box, but the keyboard is not up and i rotate my phone, that's when it happens.
[HTC Rezound] brenuga:
Like stang said, make sure you update Google search in market.

Fixing permissions in recovery and wiping dalvik cache sometimes helps with system ui crashes.

---------- Post added at 09:42 PM ---------- Previous post was at 09:38 PM ----------

Before updating Google search, pressing microphone icon in keyboard crashes kb.

The fix before the update was to put Google search in /data/app. Ask neo, he was very familiar with that issue.
[HTC Rezound] HowardZ:
I went back to stock.

Nothing compares to a phone that just plain works reliably.
[HTC Rezound] twolasrnames:
So I don't know s&!t about code, but is that ion stuff important?
[HTC Rezound] Flyhalf205:
Only if we use ion.
[HTC Rezound] RebelShadow:
Is the 5/11 build from goomanager ion or pmem? I lost track.
[HTC Rezound] Flyhalf205:
pmem. There are only two cm10.1 ion builds . I think last one is dated at 5/4
[HTC Rezound] tigerxchaos:
I got one of these today for the first time, on the 5/7 build.

---------- Post added at 10:59 PM ---------- Previous post was at 10:57 PM ----------

I'm not very familiar with ion. Is it a step up from the pmem build you've been working on? If I wanted to try it, do I need to do anything special to set my phone up for it?
[HTC Rezound] Flyhalf205:
It's a big set up from pmem. But don't expect ion for a while. One day yes. But we aren't ready for it.
[HTC Rezound] brenuga:
Nothing special you have to do, but the ion build doesn't have a working camera AT ALL currently, just be advised.

Its fast and smooth otherwise, however.
[HTC Rezound] gleggie:
Just curious, what's the advantage of ION over PMEN? All the PMEN roms have been great so far for me.

Thanks Flyhalf for all the recent commits :D
[HTC Rezound] brenuga:
ION memory manager is the jellybean successor to PMEM, which Google used in previous versions of android.

I don't know the technical details, but ION is generally considered to be part of the reason jellybean is so much smoother on nexus devices. Project Butter, which deals with triple video memory buffering, being the other.

Unfortunately, since we don't have an official jellybean update, devs are having to backport ION to the kernels for our device.

Fly's ion build is to me even a little bit snappier than infection (sorry neo). No lag at all. Night and day better than stock ICS ROM. And has been mentioned, the current ion builds for rez aren't even complete implementations of ion.

If/when ION puzzle gets put together, you will potentially have a much faster, better multi tasking ROM.
[HTC Rezound] Flyhalf205:
rabbits vs turtle...

ion...... vs pmem...

Right now. It does look like we can cheat ion so to speak. We won't be using full ION but ion and pmem both. ion for data but everything else like camera and audio will be using pmem. It still will be faster than full pmem.
[HTC Rezound] brenuga:
Wait a second, shouldn't ion be the rabbit and pmem be the turtle?

Unless we are literally talking about the story the tortoise and the hare, when the tortoise win the race cuz the rabbit napped lol
[HTC Rezound] Flyhalf205:
lol

That is how it is. I matched the colors together... haha
[HTC Rezound] brenuga:
My bad. I sleepy and got my analogy crossed. :eek:
[HTC Rezound] Flyhalf205:
ha I have to stay up till my ion build finished. Either hope or failure :fingers-crossed:

We are so taking this thread off topic lol I feel like I can though. :laugh:

EDIT: If I do get ION working fully with camera. Do I just start building it without telling anyone or make a new thread?
[HTC Rezound] brenuga:
Hmm, that's a tough one. As long as there were no other technical issues with ion, then basically, for purposes of user support , it will be same ROM, only faster.

If there are any remaining 'gotchas' with ion after camera fixed, I would stay start a new thread. Already we have to ask ppl , s-on or s-off , having to determine ion or pmem build of your ROM would get messy. :)

Also, camera working on ion would be a game-changer for rezound. Only other issue with jb is that annoying blue screen flicker.

Get it working, and every ROM and kernel dev will pretty much have to state up front if they use pmem or ion. If there were custom kernel issues with ion, I would almost lean toward a new thread to keep ion issues straight.
[HTC Rezound] Flyhalf205:
Yeah. It's either HD playback or annoying blue screen flicker...Your choice lol

And I hear BT audio isn't great. Probably needs to be looked into but I can't. BT/Wifi is broke.
[HTC Rezound] highdro:
Yeah the blue flicker drives me nuts but I can deal with it. I'll be up with you guys to hopefully get some ion goodness. By the way, what causes the flicker?
[HTC Rezound] brenuga:
I will take HD playback ftw. :D heck, if I didn't need my camera for my job as a newspaper reporter , I would probably consider using a phone without a camera.
[HTC Rezound] Flyhalf205:
Either somewhere in the kernel or in the display-legacy. I haven't looked into it. reminds me of the good ole days of when the ICS leaks were coming out...

My HHD is going to sleep which I do my builds on! :(

Getting so many errors for no reasons! I'll try this tomorrow!

EDIT: Still no luck with ion :( Just can't figure out camera.
[HTC Rezound] bunchies:
How to get WiFi tether app to work on this rom

---------- Post added at 05:50 AM ---------- Previous post was at 05:37 AM ----------

Nvm
[HTC Rezound] tigerxchaos:
Just flashed to the 5/11 build. Panoramic camera is still broken. :(

Is there a place where I can download your ion build, Flyhalf? I'm just curious about how it changes the responsiveness of the UI, which has been a major issue for me ever since I moved away from Apple.
[HTC Rezound] Luke1213:
this is why i stick on REZ. i see the possibility of all-functional ION build. just wait for your good news.
[HTC Rezound] Flyhalf205:
This isn't the smoothest ion build but here is the latest.

http://www.androidfilehost.com/?fid=22946563261203787
[HTC Rezound] V0latyle:
I'm strongly considering going to the ADR6435...very solid, powerful, and well rounded phone...I just don't want to do without an SD card slot. Anyone know why a lot of newer phones don't have SD card slots?

Edit: Might get the Note 2...but I really want that 1080p screen, plus Samsung screens aren't that great...
[HTC Rezound] kpritchard:
so I just rolled over to the 5/09 build and it appers that my wifi no longer wants to turn on. "turning wi-fi on..." endlessly and won't connect. any ideas on how I could go about fixing it? I had the similar issue when I went to update 8 from the OTA updater while under the 4/20 build.

EDIT: the wifi region code was stating europe for some reason; changed to US and as soon as I left the advanced tab it switched right back. rebooting phone. may have to re-flash in a few here..
[HTC Rezound] power950:
Did you try making a nand and then do a fresh install wipe everything then install the latest pmem build? If not I'd advise doing that probably not what you wanted to hear but I get allot of problems after 6 or 7 dirty flashes so give that a try and if there's still a problem I'm sure someone with more knowledge than me will be glad to help
[HTC Rezound] kpritchard:
I'm relatively new to this so I'm not gonna lie in stating that what you mentioned was rather gibberish to me =P although I did find out, or think I found out, that nand is re-rooting the phone? and latest pmem build would be something else...I'm assuming the downloadable zip at the front page of this forum? If so..I have not re-rooted the phone but I am re-flashing the ROM at the moment. I guess I may have to do the nand thing..granted I'll go find a forum that has more of a how-to portion on doing that I guess =P unless others have insight? the bluetooth appeared to be working just the wifi was messing up.

EDIT: Looks like it's working after another flash of the ROM. Thanks for your quick response though power950!! much appreciated. I'll be back if something is wrong again i'm sure =P learning guys I promise =P
[HTC Rezound] power950:
I'm just glad I could help doing a nand isn't rerooting in your recovery its just clicking backup its called a nandroid backup cuz it coppies every little thing on your phone settings apps rom almost everything to a zip to backup later in case that's not the problem so you can go back to your old settings if you are on a custom rom rooting is not necessary because custom ROMs come prerooted only time you'll need to root is when you're stock and a fresh install is factory resetting then wiping system / data/boot/cache/dalvick cache/ I may have forget one or some of them may not he available in some recoveries so just wipe what you can then flash the rom and that usually takes care of 99% of problems but if you're on the same rom and just want to update it you can dirty flash which shouldn't give you a problem which is just wiping cache and dalvik cache and then flashing the rom in turn will keep all settings and data and nothing should go wrong I hope I explained everything clearly and I hope this helps I do apologize for taking this off topic but I thought it would save him some time and he'd get his questions answered much better like this hope you will forgive me flyhalf and stang I know you're still watching too :P
[HTC Rezound] RebelShadow:
I don’t know if it’s me or the latest roms but signal strength seems way down. I was running the 5/1 rom and I had 4 bars at home and the signal was -93 to -95dbz. 40 asu. I tried both the 5/9 as well as the 5/11 roms and now I have only 1 bar with -105dbz. And 4 asu in the same exact spot. Was using Hiro 5/1 kernel on both.
[HTC Rezound] stoffelck:
Happens to me too. Not ROM related, all of the ones I have ran are blow. I blame the latest radio.
[HTC Rezound] RebelShadow:
Don't think it's the new radios as I am using the same radios on all three ROM's. The three ROM versions are the only things that changed.
[HTC Rezound] Flyhalf205:
I did add a build.prop line that is suppose to keep the signal icon up top to stay sync with the -dbm... So that is why your icon up top isn't blue anymore for signal..
[HTC Rezound] Flyhalf205:
Build 5/12 looks like panoramic might be fixed...Maybe?
[HTC Rezound] LunaticSerenade:
I can verify that my signal has gotten progressively worse as the ROM versions have gone up.

I also don't care, because even at -103 dBm, its sufficient, and this ROM is totally worth it.

Sent from my CM 10.1 HTC Rezound.
[HTC Rezound] Flyhalf205:
I'm cleaning up the device tree a little bit. Noticed this big change!! https://github.com/Flyhalf205/device_htc_vigor/commit/9a78cb135009906f0ab53b7ec5a306c5d9128e2c

We were at

PRODUCT_PROPERTY_OVERRIDES += \

dalvik.vm.heapstartsize=5m \

dalvik.vm.heapgrowthlimit=48m \

dalvik.vm.heapsize=128m \

dalvik.vm.heaptargetutilization=0.75 \

dalvik.vm.heapminfree=512k \

dalvik.vm.heapmaxfree=2m​

Now at:

PRODUCT_PROPERTY_OVERRIDES += \

dalvik.vm.heapstartsize=8m \

dalvik.vm.heapgrowthlimit=64m \

dalvik.vm.heapsize=256m \

dalvik.vm.heaptargetutilization=0.75 \

dalvik.vm.heapminfree=2m \

dalvik.vm.heapmaxfree=8m​

I hope this helps us...
[HTC Rezound] Neo:
Beats modifying it in build prop after rom build. One less thing to have to worry about
[HTC Rezound] tigerxchaos:
Just installed 5/12. Panoramic camera appears to be mostly fixed. The viewscreen is still flickering and jumping occasionally, but it's no longer distorted and the wrong orientation, and it properly saved a picture to my gallery. Thanks Flyhalf for working on this. :)

I am now getting gapps errors though that didn't happen on 5/11.

At some point I'm going to do a clean wipe and play with the ion build you linked earlier. Do I need to stick with the stock kernel in order to use it?

Thanks again!
[HTC Rezound] Flyhalf205:
Did you clean wipe to the 5/12? I didn't get any gapps errors. I always clean flash though.

Use the kernel that the rom comes with. No other kernel will work with that ion build. But remember. You won't have camera...
[HTC Rezound] ssb13:
I hope this is the appropriate place to post this, but for me the camera works the absolute best in the 5/1 build. The latest ones (up to 5/11 add I have not tried 5/12 yet are very choppy for me using the camcorder. With 5/1 I am not worried if the recording is going to be freezing, unplayable, or cause a reboot. I try different kernels, but can't be sure of which kernel was running when reach symptom occurred. I can say with a fair amount of certainty I was running a fairly stock configuration with Wheatley and noop.
[HTC Rezound] Flyhalf205:
I need a brave flash addict to test this for me. http://www.androidfilehost.com/?fid=22946563261203919

It boots. Standard stock rom. I just need to know WiFi and BT works.

EDIT: Build has been tested. WiFi is broke. BT works.
[HTC Rezound] Snuzzo:
Today's a good day for flashing. I have another rom I want to test too. What exactly is in this? Any changes to kernel source?
[HTC Rezound] Flyhalf205:
Nah. Haven't had much time to play with kernel lately. I cleaned up the device trees and got rid of the HTCVigorQualcommRIL...Just wanting to make sure those two items worked since I moved their codes a little.
[HTC Rezound] Snuzzo:
Did you play with SUPPRESS_EMMC_WIPE? I don't want a surprise brick. Just playin with you ....
[HTC Rezound] Flyhalf205:
Ummm...Maybe :).. Nah..

Here is my clean up...https://github.com/Flyhalf205/android_device_htc_msm8660-common/tree/cm-10.1-testing and https://github.com/Flyhalf205/device_htc_vigor/tree/cm-10.1-testing

I'm running the build right now. But I just can't test those two things.
[HTC Rezound] Deathbyfugu:
Just did a clean flash with the supplied test build. WiFi does not work. Flashing 5/12 instead now :)
[HTC Rezound] Snuzzo:
Can confirm, no wifi. Probably forgot to update msm-8660 common.
[HTC Rezound] Flyhalf205:
One more brave flasher to test this. Snuzzo said he is 99% sure that wifi should work :fingers-crossed:

http://www.androidfilehost.com/?fid=22946563261203947
[HTC Rezound] Deathbyfugu:
Downloading now. I'll report back in a bit.

---------- Post added at 06:11 PM ---------- Previous post was at 05:48 PM ----------

WiFi is broken. Back to 5/12 again.
[HTC Rezound] Flyhalf205:
thanks. I'll have the real OTA 5/13 build out in a few hours

I'm debating to buy another Rezound ....:confused:
[HTC Rezound] Deathbyfugu:
I know it would be nice to be able to test WiFi on your own but it's not worth the investment IMHO.
[HTC Rezound] Flyhalf205:
5/13 is up. I forgot to include gapps in it.

Has CM changes. Small device changes. And I added in Kernel USB Headphone support.. Not sure if that works. But I hope it does for my sake :)

Well better spending $100 than $700 on a new phone. I'm not going to loose my Unlimited
[HTC Rezound] lukester01:
update without Gapps

If I apply this over the 5/9 build, will I still have my Gapps from the previous build? or will I need to reinstall Gapps package?
[HTC Rezound] _litz:
That's pretty much exactly what I did ... $100 for a rezound to replace the old thunderbolt.
[HTC Rezound] Flyhalf205:
You should still have them.
[HTC Rezound] Deathbyfugu:
True - $600 saved is substantial. I'll download the latest 5/13 and flash it when I can - won't be until later though. Any changes big enough to warrant doing another full wipe or would system/dalvik/cache be sufficient for 5/12 > 5/13?
[HTC Rezound] LunaticSerenade:
So, when I had stated signal was worse? This is true for me at home. At work, its a few dBm's better. Weird.

Also, with using Funky kernel, is it worthwhile for to update daily, or should I just chill on the current build?

Sent from my CM 10.1 HTC Rezound.
[HTC Rezound] Flyhalf205:
Not worth updating daily. Stick with the 4 days. I am on the next release changing the RIl from HTCVigorQualcommRIL to HTCQualcommRIL. So maybe signal may be different.
[HTC Rezound] Flyhalf205:
Nothing major really. Panoramic is more stable but still not perfect. It does work good though. When you upgrade to the next release after 5/13 I would reccommend full wipe
[HTC Rezound] LunaticSerenade:
Man, you respond quick. :D

Sent from my CM 10.1 HTC Rezound.
[HTC Rezound] _litz:
If the rom doesn't have gapps built-in, then you will need to reinstall gapps.

Installing the rom wipes /system ... which is where most of the gapps go.
[HTC Rezound] Flyhalf205:
You would think you would have to reflash gapps but you don't.
[HTC Rezound] a.mcdear:
My Wifi works fine on the 5/13 build.... but I'm using FunkyKernel 3.3.3.... didn't even try it with the stock kernel supplied with the rom.