yashsingh1/xdaforums huggingface dataset:
[HTC Rezound] channeldave:
After a recent update I lost Wifi capability. When I go into settings the Wifi 'on/off' switch is greyed out. Also my Wifi widget does not work. it just stays yellow. tapping it does nothing.

Does anyone have any ideas? I have restored my backup but that did not help
[HTC Rezound] Flyhalf205:
Your probably s-on. Have flashed the boot.IMG that comes with the zip?
[HTC Rezound] channeldave:
I used TWRP to flash the .zip file
[HTC Rezound] cristianpark:
I'm back to CM 10.1 after a short fight because of battery issues hehe (btw, as Flyhalf said it seems to be the governor, change it to ondemand and played music this morning with 4-7% battery loss against 20% previously). In response to your problem, I use the Rezound in a GSM network and I have to adjust the network type to WCDMA Preferred, when I try from system config to change it I get a FC and no luck most of the time, what I do is enter in INFO dialog (*#*#4636*#*#) and select the mode I need and turn off and on the radio, hope it works for you

So far I'm happy with this build, the only real issue I found is that incorporated proximity sensor wasn't functioning good but installed the app and it works like a charm.

Thanks Flyhalf for all your hard work
[HTC Rezound] HokieCoder:
You didn't make mention of whether you are S-ON or S-OFF. If you don't know, then you're most likely S-ON.

If you are S-ON, you will do like FlyHalf205 said and extract the boot.img file from the ZIP file you downloaded for this ROM and flash it

after

you have flashed the whole ZIP file (you will need to use fastboot to flash the boot.img). When you are S-ON, the recovery (in your case, TWRP) is not able to flash the boot.img image because of the security protections on your phone. Going S-OFF makes the whole process a TON easier by allowing your recovery to flash the boot.img in addition to the rest of the ZIP file contents.
[HTC Rezound] channeldave:
nsequih was

Ok, Thanks. What is the process for this? can I extract the boot.img on the phone? or do I have to extract on a PC and move it to the sd card?
[HTC Rezound] HokieCoder:
You will need to extract it on your computer so that fastboot can access when the phone is connected in USB debugging mode. The easiest method is to extract it to the same directory that you have adb and fastboot in (you did this at some point to get TWRP recovery on your phone). I found a great tutorial for flashing the boot.img here.
[HTC Rezound] fastecotec:
If you are using TWRP 2.5.0.0, you could also use the HTC Dumlock feature, easy to use, and you don't need to be next to a computer.
[HTC Rezound] tigerxchaos:
Got another question, and it's probably user error.

I found a setting in prior versions of this ROM that would flip the volume keys upon rotating the device, so the pressed direction matches the on-screen volume indicator. Can't find it in the newest build. Anyone able to point me towards it?
[HTC Rezound] bunchies:
Go to settings and click Display and click rotation its in there
[HTC Rezound] tigerxchaos:
That explains it. Normally I enable 180-degree rotation, this time I decided not to.

Thanks for the help!

Fly, no soft reboots yet. Everything is smooth so far, haven't run into any problems. I'm going to pick up a new battery soon to see if it sorts out my battery life problems and will report back when I get it. Thanks for all your work on this ROM.
[HTC Rezound] bunchies:
Have you tried re-calibrating https://play.google.com/store/apps/details?id=com.nema.batterycalibration&hl=en

EDIT: Btw camera tile was added in CM Changelog today. didn't wanna make another post to say something about it. but i hope its i the next build :D
[HTC Rezound] GMSweet:
I'm still poking around at the device encryption piece. I grabbed some details from aLogcat which is pointing me in some sort of direction. The log entry shows:

E/Cryptfs ( 122): Orig filesystem overlaps crypto footer region. Cannot encrypt in place.

I have not gone as far back as re-locking, running an RUU, and starting extremely fresh, but I may give it a shot. It looks like the primary partition is set to "encryptable" and I'm comparing a working Sense ROM's system/etc/vold.fstab to the included one on the JB ROM for any clues. I'm off to a meeting now, but I'll keep plugging later. If I turn up anything interesting, I'll post back.

Thanks,

Matt
[HTC Rezound] GMSweet:
It looks like I'm barking up the same tree the FlyHalf and hceuterpe were working on in http://xdaforums.com/showthread.php?t=2113140&page=246.

I'm going to re-flash a Sense based ROM and take a look at the mount points.

The mount for /data in CM 10.1 is showing up as in fstab.vigor:

/dev/block/mmcblk0p35 /data ext4 noatime,nosuid,nodev,data=ordered,noauto_da_alloc wait,encryptable=footer

Mount shows...

Filesystem Size Used Free Blksize

/data 2.3G 774.2M 1.6G 4096

If anyone can confirm the encryption was working after the late May conversation that would be great; I'd really like to stay on an AOSP ROM.

Thanks,

Matt
[HTC Rezound] Flyhalf205:
[MENTION=4121169]polarEskimo[/MENTION]

Here is the cm-10.1.0.. CLICK ME
[HTC Rezound] HokieCoder:
Had another random reboot right after taking a picture with the camera. The phone locked up while still in the camera app, rebooted after about a min, and then when I got back in to the OS, the picture I had taken was corrupt.
[HTC Rezound] :
Thanks a lot!
[HTC Rezound] tigerxchaos:
Allrighty, another camera question.

Being that the default Sense camera apps snap pictures in wide-screen and CM uses a more conventional 4:3 ratio, are we wasting some of the camera sensor's real estate?
[HTC Rezound] el Filou:
Actually, it's Sense that is wasting sensor space with camera set to widescreen; it just crops to 16:9. The sensor is 4:3 (you can verify this in Sense camera app by switching between 4:3 and 16:9 while previewing).
[HTC Rezound] tigerxchaos:
Sneaky. I was hoping that was the answer. Thanks!
[HTC Rezound] rgnicholas:
Hey there... I downloaded this too to check it out but in doing so, I noticed that the MD5 is different. I look at the files in the OP mirror. Just want to be sure things are smooth before I flash it. Thanks! And thanks for doing this, by the way.
[HTC Rezound] scy1192:
The new Gallery3d.apk from the Nexus Experience phones seems to work just fine with the Rez on this ROM. Photosphere does not work, however. If you had photosphere flashed previously, it might though.

Download here, [mirror]

the instructions on the post don't exactly work for us, so follow these instead

Instructions:

CyanogenMod File Manager

Download the apk on your phone

Open File Manager, make sure root access mode is enabled in Menu -> Settings -> General settings -> Access mode

Navigate to /storage/sdcard0/Download

Click the check box next to com.google.android.gallery3d.apk

Navigate to /system/app

Hit the 8-dot buttton in the lower left

Click "Paste selection h..." ("Paste selection here")

Long-press com.google.android.gallery3d.apk, choose Properties, then choose the permissions tab

Change the permissions to: rw, r, r

Rename Gallery2.apk to Galler2.apk.bak

You will lose the HDR feature from CyanogenMod

Reboot. The Camera app will be the new Camera.

After updating CyanogenMod, you will need to delete Gallery2.apk from /system/app. Instructions on how to do it in TWRP below

TWRP

Download the apk on your phone

Reboot to recovery

Go to Mount, checkmark System, and hit the home button

Go to Advanced, choose File Manager

Navigate to /sdcard/Download

Tap com.google.android.gallery3d.apk

Choose Copy File

Navigate to /system/app

Tap the Select button in the bottom right

Swipe to confirm

Go back to /system/app via the File Manager

Tap com.google.android.gallery3d.apk

Choose chmod

Type in 0644, press Go

Swipe to confirm

Find Gallery2.apk, tap it

Tap Rename File

Rename to Gallery2.apk.bak Hit "Go", then swipe to confirm.

Hit the home button, then tap Reboot, then System

When it boots up, Camera should be replaced with the new one

You will lose the HDR feature from CyanogenMod

After updating CyanogenMod you will need to delete Gallery2.apk. Instructions below.

After updating CyanogenMod

edit: you must repeat the steps above and fully reinstall Gallery3d. A ROM flash will wipe /system/app.

--------------------------------------------------

The Sun Beam live wallpaper also works, but is much easier since you only need to enable third-party sources from Settings->Security, then install it like any other apk.
[HTC Rezound] gleggie:
Yea my md5 is also different, i keep getting f986dab23d02f50059cb09d4797e16a8 for the 10.1.0 Milestone in the OP. However, 6/25 is running great and Fly said they're basically the same
[HTC Rezound] Luke1213:
a little puzzled. so is Cm10.1.0 is consider a final and stable release built from original source code??
[HTC Rezound] gleggie:
Yea I think CM10.1.0 is basically a finalized version of 6/25 can anyone confirm this? I'm currently running 6/25 and so far its rock solid stable, no issues whatsoever
[HTC Rezound] Flyhalf205:
Yeah the MD5 is messed up. I can fix that tonight...But it is safe to download and flash.

I am making the every 4 builds into nightlies instead of stable. So in CMUpdater you will have to switch to include nightlies.
[HTC Rezound] wickedgames:
6/26 build

Hey buddy I just wanted to say thanks for all your work first of all. However, I wanted to inquire if the 10.1.0 build is better or the same as the 6/26 build. Nevertheless, I received the 6/26 build as an update yesterday but I do not seem to find it in the snuzzo mirror. Once more thank you very much.
[HTC Rezound] lukester01:
works

I gave it a try. It seems to work well. There are hardly any config settings or scene modes. I think like 4 scenes now. Sports, Night, Sunset, and party. Not sure what party does. I hope it is fast shutter so kids are not always blurred. The current CM camera has serious problems with shutter speed. Looks like there is no burst mode anymore, but that was almost useless anyways since it was extremely slow to fire off shots. No HDR, like the description says. I'll miss that because it actually really worked well when taking photos that were dark with a light sky in the background. I wish someone would get continuous shooting and continuous focus working.
[HTC Rezound] rgnicholas:
Thank you for the verification... I will be flashing this for sure later today. Also, if this is not too much of a newbie question, how do you determine which builds they consider to be "stable?" Is it a milestone set by the CM team? Just curious. Thanks again!
[HTC Rezound] dfox123:
I just had a reboot myself. I just laid the phone down after looking at an SMS that just came in. Still on 6/25 release
[HTC Rezound] Flyhalf205:
The 6/26 is special build. Not on snuzzo server. Can only download from cmupdater.

Cm-10.1.0 build is sorta like a milestone. It's their final build. fully stable code. I'd say its more stable than 6/26.
[HTC Rezound] Flyhalf205:
I don't have a username in the email but thanks Maurice. :D

Edit: thanks wickedgames
[HTC Rezound] wickedgames:
6/26 build vs 10.1.0

Thank you for your response it clarifies things for me I hope my donation helps. It is not much but I really appreciate your help and work.
[HTC Rezound] Flyhalf205:
Thanks for donation underdog
[HTC Rezound] ANDR0lD:
These settings on the 6/26 build are working quite nicely for me :)

Sent from my ADR6425LVW using Xparent Cyan Tapatalk 2
[HTC Rezound] HowardZ:
I am using CM10.1 6/26 version with HIRO 6/25 and it is very stable without any bootlooping. I have used lulzactive, badass, and scary governors. I use the voltage table from HIRO 4/7. Thank you for making cm10.1 so stable.

I have a question. I have read of new SMS security coming to CM10.1 soon. Is it better to use goSMS, or not to use it?
[HTC Rezound] bunchies:
The SMS encryption will only work between 2 phones that are using CyanogenMod. Which should apply to stock SMS app
[HTC Rezound] lukester01:
CM10.1.0

Just a heads up for those installing the CM10.1.0. I installed the CM10.1.0, but now I have no contacts. Looked into that and found it is because there is no Google account synced. And when I go to add accounts. I cannot even add a google account. So I reinstalled gapps. That brought it back. So it looks like installing the official CM10.1.0 erases the google account on the phone.
[HTC Rezound] gleggie:
Did you dirty flash or clean flash?
[HTC Rezound] lukester01:
dirty flash

dirty
[HTC Rezound] bunchies:
huh? what build. im running the latest 6/26 and still have mine, lol im not trying to start a back and forth of whom has the issue or not but there's nothing wrong with the build
[HTC Rezound] lukester01:
official 10.1.0

Sorry, I should have been more clear, I installed the official 10.1.0 from the link fly gave. It is not the same as the 6/26 (but very close as fly states)
[HTC Rezound] ChuckZv2:
GAPPS

Where can I get the latest GAPPS apk? I need to install my apps!!

thanks haha
[HTC Rezound] Flyhalf205:
If you look about 3 or 4 pages back. We posted it about 3 times ha
[HTC Rezound] ChuckZv2:
Can you please direct me I cant seem to find it. Sorry for the trouble.. I went 5-6 pages back. and did a thread search.

I must be retarded lmao

---------- Post added at 06:46 PM ---------- Previous post was at 06:44 PM ----------

nvm!!!!! Thanks
[HTC Rezound] tigerxchaos:
I went ahead and recalibrated. So far I'm not seeing anything hugely different than before regarding my battery life, but we'll give it a few days and see how it goes. Thanks for the suggestion.
[HTC Rezound] ChuckZv2:
Applying Update after flashing 10.1.0

Sorry if this has been asked before. I saw someone mention something similar earlier.

After applying the latest CM10 update, and starting the ROM for the first time. The CM Updater runs and mentions that there is an update.

What do you recommend to do for the ones that are S-ON? Last time I did the latest update it killed my wifi.
[HTC Rezound] wildstang83:
Just to be sure, you know that as an s-on user you must manually flash the boot.img after updating?
[HTC Rezound] HowardZ:
The CM10.1.0 does not match the md5 in snuzzos mirrir
[HTC Rezound] J D A:
If we flash the 10.1.0 CM stable build that you linked to for polarEskimo (sorry if I got the name wrong), can we still update as usual through the CMUpdater app (skip over build 6/26 or?!?!!?!?!)?

I might try to S-OFF again, I failed miserably last time and spent a couple of days fixing everything, but it was due to me using a non-MHL cable that was loose and wouldn't stay in unless in a certain position.
[HTC Rezound] adavit:
Last I knew fly was aware and was going to be fixing it tonight.
[HTC Rezound] svh105:
If I flash this rom with TWRP HTC dumlock, why does the OP say to fastboot the boot.omg for S-ON devices.
[HTC Rezound] brenuga:
Because there are multiple ways of doing the same thing.

Personally, I fastboot boot recovery , which let's me flash ROMs as if I were temporarily s-off.

In addition to dumlock, there's also snuzzo's lunar tools.

Check link in my signature on xda site for more info on fastboot boot if you are interested.
[HTC Rezound] gleggie:
+1

---------- Post added at 11:34 PM ---------- Previous post was at 11:23 PM ----------

Anyone got the md5 for 10.1.0? Im still not getting a match.

Sry I just like to be meticulous when flashing
[HTC Rezound] mavpts:
I got

28a8e78d1fdda100d22534ab249e494a
[HTC Rezound] Flyhalf205:
28A8E78D1FDDA100D22534AB249E494A is the correct md5
[HTC Rezound] gleggie:
Thanks! Flashing now..

Edit: bootlooped after restoring apk's, gonna wipe and reflash
[HTC Rezound] bunchies:
I hate to ask. But when's the next build?

Wanting to try out camera tile lol

Cyanogemod has been adding a lot of features the last 2 weeks
[HTC Rezound] Flyhalf205:
Ehh. Whenever I wake up in morning... lol... It is actually going to be cm-10.1.0.1

I am re-uploading cm-10.1.0-vigor so it will have a new md5.

B7CD63F19686B1591C29B9025D166795
[HTC Rezound] bunchies:
Lol awesome :thumbup:
[HTC Rezound] wickedgames:
issues with 10.1.0

I got to say I tried 10.1.0 and it gave me issues with my signal strength it would always stay greyed out unlike the other builds which would turn the normal aqua color. Nevertheless, I am really enjoying your 6/26 build it is very smooth and I have even noticed better reception with it unlike 10.1.0. :D
[HTC Rezound] Luke1213:
you mean the previous cm10.1.0 has some glitches or you just want to get a correct md5?
[HTC Rezound] gleggie:
He just wanted to get the correct md5
[HTC Rezound] GMSweet:
Just in case anyone finds this by means of search, here's where I ended up:

I found the Jelly Bean shifted the way partitions are mounted, so that research didn't provide any answers. Cyanogenmod Issue 87 shed the most light on the subject indicating that the partitions need to be formatted differently at install. I was able to verify that the recovery.fstab on this build doesn't have the flag set to create space for the encryption footer, but even after fully wiping the device and adjusting the recovery.fstab through ADB shell, I wasn't able to create the partition in a correct way for encryption to work.

I had to fall back to a working Sense ROM so I could get access to corporate data again. When I have more time, I'll probably set up a build box and see if I can figure out where the partitions are being formatted during install and see if I can format the /data partition with the flag "length=-16384". Of course, this may already exist in the source code since FlyHalf and hceuterpe were already on the case last month. I'm a complete hack at this stuff, but it's good to learn new things.

I miss AOSP already.
[HTC Rezound] HowardZ:
In CM10.1.0 I do not see the per app security settings.

I also find the screen is brighter, and need to change the auto brightness values.

Not complaining.

Just observing.
[HTC Rezound] rgnicholas:
Actually, mine did the same under these circumstances: wiped everything 2x, clean install -BUT- allowed the restore of apps on first boot. I think maybe this can overwhelm things a bit (my opinion). So, I believe I will repeat the process and install everything from the Play Store fresh. We'll see.

----- edit -----

Just to add to this thought process... I am using TWRP 2.5, by the way... I did another clean wipe, formatting everything except the SD Card (micro), I installed the 10.1.0 ROM and then GAPPS... after booting up, it seemed OK but I didn't immediately jump in to set it up. I just let it sit there for a moment and after about 10 secs, it rebooted... it did this twice. I then jumped into do the initial setup (before it could reboot again) and updated with CPupdate to 10.1.0.1 and it seemed OK... but since the update, it has rebooted once. All of this was in the space of less that 10 minutes. I will setup my typical apps and see how it goes.

----- edit -----

Yet more info... Ok, I just installed about 10 apps directly on the phone from the Play store and as I closed the Playstore app, the Rom rebooted. Odd... I am wondering if I did anything to cause this or possibly there is an oddity in the Rom itself? Ideas?
[HTC Rezound] Flyhalf205:
cm-10.1.0.1 is uploaded. Now remember. These last two builds cm-10.1.0 and cm-10.1.0.1 and stable builds. They aren't like the every 4 days which are nightlies. So CM does have code/features left out which I guess they didn't find to be that stable.
[HTC Rezound] Flyhalf205:
[MENTION=4723162]GMSweet[/MENTION]

I've been reading your post about the encryption. I may pick it up later in time. Going on vacation next week so might be a while before I start on it.

I might have to remake the recoveries with that adjusted fstab with "length=-16384" added and a few small changes to the device.
[HTC Rezound] kpritchard:
are we supposed to see 10.1.0/10.1.0.1 through the CMUpdater? The last that I've seen are labeled as: cm-10.1-20130626-UNOFFICIAL & 621 in respect to the previous label. Or are these available in another location?
[HTC Rezound] Flyhalf205:
Yes. Should be able to. I see them in mine. Is your CMUpdater set to nightlies or stable?
[HTC Rezound] kpritchard:
It's set right now to "New versions (incl. Nightlies). I have also gone through all of the updates checking for any new ones, and the newest one for me is only the cm-10.1-20130626-UNOFFICIAL
[HTC Rezound] Flyhalf205:
Did you select All versions?
[HTC Rezound] kpritchard:
Yeah, I just set it to "All versions (incl. Nightlies)" and nothing has shown up.

Edit: SS included
[HTC Rezound] mjones73:
Seeing the same thing here (sticking to the nightlies though) :)
[HTC Rezound] Flyhalf205:
I see 6/16...6/21...6/25...6/26...cm-10.1.0...cm-10.1.0.1...

Could you guys go into manage apps and clear the data if any for CMUpdater?
[HTC Rezound] kpritchard:
yeah I just did that. Same thing shows as image I posted above. :crying:
[HTC Rezound] HowardZ:
I think fly mentioned he might have broken CMUpdater in 6/25 or 6/26.

I had to download CM10.1.0 from Snuzzo

http://vp-zp.com/snuzzo/roms/flyhalf205/cm10/

And also flashed gapps.

Then today CMUpdater worked again and told me about CM10.1.0.1

But I downloaded from Snuzzo again.

I like having control over TWRP to also flash gapps and to wipe the caches.

A new variable fly introduced with CM10.1.0 is uncertainty whether or not a dirty flash requires reflashing gapps.
[HTC Rezound] bunchies:
Manual installed 28 build. Lock screen is bright again and no camera tile lol I'm gunna read some changelogs

Was 10.1.0.1.zip a new build?
[HTC Rezound] Flyhalf205:
I did break it in 6/26 so that could be the problem there.

I also had a problem when I flashed cm-10.1.0 with my gapps. But every other one worked fine. cm-10.1.0.1 worked fine dirty flashing.

[MENTION=4581832]HowardZ[/MENTION] What if I don't upload to snuzzo server :confused: lol You can download it from CMUpdater and just click no to don't install.

[MENTION=5035862]bunchies[/MENTION] it will come soon! :) cm-10.1.0.1 is a new build. It's full stable cm code. Not nightly source.
[HTC Rezound] kpritchard:
So would you recommend downloading the 10.1.0.1 from snuzzo and clean flashing that and using CMUpdater after that? Since CMU will still be talking to your uploads correct? I just wanna get back on the correct update train =P
[HTC Rezound] Flyhalf205:
Ehh. I would just wait till my newest build. 6/29. It's only a day away
[HTC Rezound] kpritchard:
Okay :( seems like forever =P Thanks!
[HTC Rezound] HowardZ:
Snuzzo mirror is not essential, but it is nice that the md5 is posted there. I do not know if CMUpdater checks any checksum. CMUpdater does work well with TWRP, but I also do not know if it clears the caches.

Regards

Howard

For years we've been told to check the md5,and also clear both caches after a dirty flash. It's like looking both ways before crossing the street.
[HTC Rezound] Flyhalf205:
CMupdater does check md5
[HTC Rezound] scy1192:
CM 10.1.0.1 eh? All the way up to CM21 now?
[HTC Rezound] GMSweet:
Enjoy your vacation. If I get anywhere I'll post back. Thanks for all the effort to keep our phones relevant.

Matt.
[HTC Rezound] Flyhalf205:
Build 6/29 is out. Guys on 6/26 might need to manually download it. I might have broke CMUpdater in that build. Seems like this build is a lot more stable than the previous ones.
[HTC Rezound] bunchies:
Woot Woot :victory:

EDIT: yay camera tile and darker lock screen again lol
[HTC Rezound] Flyhalf205:
Just a small poll. Do you feel like the auto brightness levels basically suck?
[HTC Rezound] bunchies:
I edited my brightness lux levels a while ago. But if you wanna test something with the auto brightness I wouldn't mind having it in a nightlie.

Idk if they suck. I don't really have other smart phones to compare it to just Layin around
[HTC Rezound] wildstang83:
IDK about the Rez since I can't find the stinking thing anymore, but on the latest nightly for my Note 2 I am noticing some wonkiness.

Not sure if coincidence or a real cm bug...