Well, they did it. Who, what? The CyanogenMod Team, Flyhalf, Neo, _litz and REV3NT3CH. We now have a KitKat for the ReZound. This Rom is CM11.0 which is currently built on  Android 4.4  "KitKat".

done.
Package Complete: /home/ctaylor/Android/cm11.0-rezound/out/target/product/vigor/cm-11-20150805-UNOFFICIAL-vigor.zip

real    60m1.423s
user    69m15.384s
sys     42m10.223s

 7 Reasons why KitKat is better than Lollipop   And on top of all that... I can not get the proper files or information from HTC in order to do it. I'm not smart enough to do it on my own and the people in the know are not interested. Phone is to 'old'.

Just for your information:

cy·an·o·gen
1. A colorless, flammable, pungent, highly poisonous gas, C2N2, used as a rocket propellant, an insecticide, and a chemical weapon.
2. A univalent CN group found in simple and complex cyanide compounds.

 June 10th, 2014  Well, I stuck with it long enough and now I have received the honor of the OP position for our ReZound Development Thread. The Lord has been good to me lately. Met a bunch of good guys who are now in our ReZound Team and I was blessed with the OP position. Thanks to the Lord and the guys on the team. Especially Neo, in this case. I've been creating these WebPages ever since I got the phone and now... and now, I get to create the new releases!! Wahooo!!

This device was/is also known as HTC ADR6425, HTC ThunderBolt 2, HTC Droid Incredible HD and
HTC Vigor

 June 30th, 2015 - UpDate  There is a claim that a latest and greatest CM11 is available. I had a hard time with the later ones in December of 2014. I am going to try this latest stuff. I know they did NOT include the ReZound in CM12 -and- I am hoping that they did NOT remove it from the latest CM11.
Well, whatever they did, they did not break it for our ReZounds. I "UpDated" my sources, built a new one and installed it on my phone. So far, so good.
    cm-11-20150701-UNOFFICIAL-vigor.zip
    7-2_GApps_Minimal_4.4.4_signed.zip
-AND- we have a new source for our Gapps. @BaNkS passed his on to @TKruzze who has passed his on to @hellowasif. A copy of the 4.4.4 version can be found at:
 reborn-gapps-t3074533   NO I have NOT tried them yet. July 5th, 2015/10:03pm They offer more size options -- soooo... you might want to check them out.

CyanogenMod consists of  three  four parallel and active major versions:
      CyanogenMod 10 (Android 4.1), 10.1 (Android 4.2), 10.2 (Android 4.3) and 11 (Android 4.4).

 April 30th, 2014  Well, we are getting closer -but- a lot of people are "Jumping Ship" and going over to the "New HTC One M8". They all seem thrilled -but- just because it is a new pnone?? I wonder?? Any who, on this date we:
    Installed the latest cm11 for the ReZound:
      - cm-11-20140430-UNOFFICIAL-vigor.zip along with 3-22_GApps_Minimal_4.4.2_signed.zip
      - and we let Google restore our apps... which took ±15 minutes. We were not paying close attention.

 December 5th, 2013/10:00pm  Well, we finally did it!! What?? We got our stuff together and completed a compile. It finished at this time whilst we were at work. We were finally able to get Java 6u45 installed and then ran into:
      /bin/bash: xmllint: command not found
which was fixed by finding it discussed in XDA Developers out on the Web.

Once again we have successfully compiled this and have not installed it... yet. Our excuse at this point is... my wife has to go in for surgery and I can not be without my phone. So, for a day or two, or more depending one the outcome, we will have to delay our joys.

 January 10th, 2014/9:52am  'Last today'... we were successful in compiling a 'Hybrid' version of the new KitKat. This is a compilation consisting of some pieces which use PMEM and others which use ION. Together they make the HYBRID. More details are elsewhere but this gives you a hint as to what is happening. Neo and _litz were the two developers from which I got the most help, and guidance.

From: _litz
All our work is on github under vigor ... http://github.com/vigor

Branches relevant here are the cm-11.0_hybrid ones

(see the various local_manifest files for the actual repos used for each type of build ... pmem, ion, or hybrid) 

And from Neo: 
That is our "Device Tree". You have rom source which comes from CyanogenMod, and then you have our device 
specific source that required to build with CM based roms on our team vigor git.

More from: _litz
As for the vigor github ... here's what's there

vigor/android -> our custom scripts and local manifests (note, this mounts to /vigor in your source tree)
vigor/device_htc_vigor -> all the vigor device specific settings/configs, special code, etc.
vigor/device_htc_msm8660 -> our customized version of the Code Aurora msm8660 device support stuff
vigor/kernel_htc_vigor-3.0 -> linux 3.0 kernel customized for vigor
vigor/vendor_htc_vigor -> vendor provided files (firmware libraries, etc)

In addition, there are also local copies of the following cyanogenmod projects, as we have customizations 
outside of their scope in these :

vigor/hardware_qcom_media-legacy
vigor/hardware_qcom_display-legacy
vigor/frameworks_native

Special note : you'll see in a lot of "build your own rom" instructions a reference to running a "extract-files.sh" 
script ... we don't do that; all our files provided by that script are already present in the various projects in the github. 

ok, my 18+ hours copy last-today ... forgot to make clobber first:
The size was: . 46GB .. 638,045 files .. 82,270 sub-folders.
After a clober    20.8GB ... 452,970 files ... 70,094 sub-folders.
Just in case you needed to know.

 December 25th, 2013   Flash Play On KitKat

Comments ... PMEM and ION are the Memory Allocators/Managers used in Googles Android. HYBRID is a combination of both. ION is supposed to be better... and the future component.
dalvik Virtual Machine, ART(Android Run Time), What is Android, Android Memory Analysis, More Info,

Those words are repeated from here. We are trying to make sure that this info doesn't disappear... -or- at least stays available to us. Had our phone for over a year and still haven't flashed in a different ROM. That is about to change. We like to investigate -and- re-write the instructions so that we... and possibly others... can understand things better and NOT screw up. Not that the current directions are not clear.. its... well... it is just us. Besides we would like to add our experiences and hopefully say that it works!! ... which BTW it does.

Thanks to wildstang83, Flyhalf205, Neo and REV3NT3CH for all their efforts.

• CM11.0
• Koush's SuperUser as default (built in)
• Android KitKat 4.4
• Root
• Apollo
• CM's "File Manager"
• cLock Widget
• Quick Settings Panel
• Swipe option for Quick Settings
• Quick Pull-down option for Quick Settings
• Notification Drawer Quick Access Ribbon
• New CM Wallpapers
• Theme Engine
• Scroll typed text with vol -/+
• Multi Language Support
• Zipaligned
• All images optimized

• Alarm/Clock/Countdown Timer/Stop Watch
• Audio (alarm, music, ringtones, ui)
• Automatic Screen Rotation
• Battery Stats
• Bluetooth Calling and Streaming
• Bluetooth Tethering
• Camcorder
• Camera
• Count Down Timer
• Data (3g/4g LTE)
• Data Transfer Arrows
• Developer Options
• Display (for the most part. See not working for further details)
• Exchange E-Mail
• Google Sync: Account/Calendar/Contacts
• Gallery
• Google Voice Typing
• GPS
• Hangouts (Gtalk replacement)
• LEDs
• Mms (sending/receiving)
• Performance Controls
• Phone (making/receiving calls)
• ScreenShot
• Security (Blacklisting /Privacy guard /Screen Lock)
• Signal Bars and dBm signal strength
• Simultaneous Voice and Data
• Sms (receiving /sending)
• Sms messaging via hangouts (new integrated sms ability)
• Sound Recorder
• Stereo Sound Headphones (some static present when screen comes on and goes off)
• Stereo Sound (rear speaker)
• Storage (external /internal)
• Superuser
• Swipe Keyboard and Auto Correct
• Terminal Emulator
• Torch/Torch Toggle
• USB Mass Storage (Access via pc connection): External /Internal
• USB Tethering
• Vibration (calls , haptic feedback, notifications)
• Vibrator Intensity settings
• Voice Dialer
• Voice Search
• Live Wallpapers /Wallpapers
• Weather from network location
• Widgets
• WiFi
• WiFi Hot Spot (native WiFi tethering)
• Youtube App/streaming video

• Netflix: However, there is a workaround for this via use of the Xposed module:
  [Xposed][HACK] Workaround for Netflix as of 06 Jun 2014 This was discovered by member @hochoch. Thanks be to him. I have attempted to place the install instructions here. However, IF you feel confused please refer to the Workaround site.
  
  To install Xposed:
  Download and Install the Xposed Installer APK http://dl.xposed.info/latest.apk.
  ... > move to the dir containing the file
  ... > adb install de.robv.android.xposed.installer_v32_de4f0d.apk
  You will be asked if you will allow this. Say yes.
  Switch to the phone and the app directory. Install the Xposed framework:
  ... Find Xposed Installer... Tap it... Tap Frameworks... Tap ok... Tap Install/Update...
      select Remember choice forever... Tap Allow... Tap ok to ReBoot
  Download and Install the APK linked in this post: linked apk
  ... > move to the dir containing the file
  ... > adb install XposedCM10.1NetflixWorkaround.apk
  Startup the Xposed Installer... Tap Modules.. Tap the check box.. Tap ret key twice
  After enabling the module in Xposed Installer ... Reboot your phone. Enjoy Netflix.
  If your PC hangs on one of the adb install commands... look at your phone and Tap the OK.
  And this works on our CM11.0 (4.4.4) xposed-framework
• Bluetooth Calling: It's hit or miss. Either doesn't work for some, or has bad quality for others.
  Now as for the Bluetooth calling... Well IF you want to say "Okay Google" and wake up your phone ... it won't. As far as I can tell ... it never will. The Motox has an extra low power processor that is always listening and that is how they do it. We do not have that type of hardware.
   July 14th, 2014/3:11pm  Open mouth... insert foot. I read that somewhere, and naturally I don't remember where. HOWEVER, "Okay Google" will work on our phones!! I appologize to all those I've offended.
   September 7th, 2014/3:10pm   Which should be no one. I was right the first time. You can NOT use "Okay Google" to wake up our ReZounds
  
  However, there is a "Voice Dialer" app that does work -but- you must first select it by tapping the icon. I have two others made by Cyberon and they both must be tapped before the voice call can be made. These are paid for apps and they have one other advantage that is "almost" an ok call. You can press a button on your Bluetooth device and they will ask you to say a command. One is "Speaker Independent" and the other is "Speaker Dependent". The first reads your textual contacts and the second compares your request to prerecorded voice tags. Now IF the included free one has any of these features ... I don't know. Haven't tested that part yet. Maybe next time. -OR- one of you can and let me know.
  Ok next time came and I tested it. With the default included Voice Dialer you can use the Button on your Bluetooth in order to start a call. After you tap the button the Voice Dialer will ask you what you want to do, just like the paid for ones.
• MHL/HDMI: This most likely will never work on AOSP and should be considered a "don't hold your breath"

• Display Issue: Can't view screen in browser or Gmail/Netflix (cm is working on this)
  -A current workaround is to use Firefox or chrome instead. Also for Gmail, check it through one of those browsers for now.
  
• MHL/HDMI: This most likely will never work on AOSP and should be considered a "don't hold your breath"
  

• Camera: May never be fixed
• Camcorder: May never be fixed
• MHL/HDMI: This most likely will never work on AOSP and should be considered a "dont hold your breath".
• ScreenShot: Comes out blank or fuzzed out (possible fix in the works)
  -A current workaround is to use a playstore app to do it for you. Trigger is a phone shake or an on-screen button press.
• Simultaneous Voice and Data: (Data while on a call)

• Phone Encryption
• Calendar Sync
• DSP Manager
• Video Messaging a.k.a. video hangouts, skype, etc.

Comments ...

Claimed fixes for some problems. Some I didn't even know that I had cause... I don't necessarily use all the features of this phone.

sms fix

Comments...

Ok we like to give credit where credit is due -and- the original poster for this fix was/is:  el Filou   at:
    (ROM)(01-14-15)(UNOFFICIAL)(4.4.4)CyanogenMod 11.0(GPL)(HYBRID) > Post #1977.

Quote:

Originally Posted by majedali611 1. Open the file /system/build.prop with a root-enabled text editor, then: - comment out the line " telephony.lteOnCdmaDevice = 1 " by inserting a "# " in front of it (you could try setting it to 0 instead, but just commenting out works fine for me) - find the line " ro.telephony.default_network = " and change its value to 0 instead of whatever it is now. 2. Save the file (you can open it again afterwards just to make sure the changes have indeed been saved) and reboot. 3. Go into Settings, Mobile Networks and re-do an automatic search for your provider, it should reconfigure the phone with the correct information. Please try to understand that: - This is an english forum, and it's difficult to help people when you don't understand perfectly what they mean. People are not ignoring you, but if they don't have any detailed information about the problems they can't help much. - The developers are providing these ROMs free and working on their spare time, don't ask for update dates or just complain of things not being perfect for you without providing information to help. - GSM is not the original market for this device, so problems with GSM may be harder and slower to troubleshoot and fix due to most people using this phone on Verizon or other CDMA networks, rather than on GSM.

(GSM)   Global Sys for Mobile Comm
(CDMA)   Code-Division Multiple Access
      Spread Spectrum Technology

Comments...

Yes, here we are almost 2 years later, and still not resolved with the OS and software on our phone. You can't, or most of us can't, just jump in and make changes to these phones. Not all the stuff is written for 'all' the phones. Ours is different than some of the others -and- it is NOT widely supported. Seems that within 3 months after purchasing it, it got orphaned. The hot ones were the Samsung and Motorola. Oh well, we like our phone anyway.

Now then, what brings this section about is ... what we want. Everything!!! Really, our phone has some pretty neat features and it will take a lot to get us to move. So far, the "newer" versions of this OS have not been impressive to us. Granted they are NOT from the original manufacturer -but- IF they are going to be presented as "improvements" then they should have some improvements -or- at least as good as the former. Camera, GPS and Phone Call Ops are the three that come to mind most readily. They were the reasons for our choice of this phone.

The "Developers" versions of the "Newer OS's" do NOT come with a lot of 'extra' software, often times referred to as bloatware. Unfortunately, we use 'some' of this 'Bloatware'. So, before we can switch to one of these Developer OS's, we need to see if an appropriate ap is available.

 Camera:  It appears that this apk, Snap Camera, might fit the bill. Needs further research... -BUT- it is Christmas ... annndddd... we need the phone -and- camera woking up to snuff. So any, and all, testing -or- experimenting, will wait till after. May try some things over the New Year Holiday... it is always cazy anyways. For now, we will just read and research on the Net.
Well, didn't listen to myself and wiped some Christmas pics!!
Another camera at: Camera Zoom FX and a Review at: Review

 February 3rd, 2014/4:28am - Camera Again Took a picture of some flowers on our kitchen table and my wife complained that the pic was to grainy. Well, Neo just realeased a new build and we would like to try it. -But- first we will go back to ICS and take the pic again to see if it is any better.
Might want to try Google Camera from the play store. There are claims that it works ... better. But then I sign on to the PlayStore and see nothing but complaints!!

 March 23rd, 2014/9:09am - The SD Card What brings this up is the Camera operations and the fact that Google made some drastic changes in SD Card operations. There are, naturally, fixes so's we can get back our NORMAL ops. What are we talking about?? Google has blocked 'third' party apps from writing to the SD Card. When using the Camera in one of our KitKat creations we wanted, and looked for, the ability to save the pics on our SD Card. Could NOT do it. So, we looked for, and found, a fix at: SDfix. Information on Google changes is at: SDcard Changes

Please notice the following requirements were for ICS, on October 23, 2011.

6GB of download.
25GB disk space to do a single build.
80GB disk space to build all AOSP configs at the same time.
16GB RAM recommended, more preferred, anything less will measurably benefit from using an SSD.
    5+ hours of CPU time for a single build, 25+ minutes of wall time, as measured on a workstation
    (dual-E5620 i.e. 2x quad-core 2.4GHz HT, with 24GB of RAM, no SSD).
Never had I imagined that ICS would require such heavy-duty machines to build. Folks, its time to upgrade your machines!     Refer: Slashdot

 June 26, 2014/6:24am  My Build of the Open Source KitKat took considerably longer...
        8 hours 27 mins 0.544 secs
The ccache was cleared and make was clobbered. It was, in essence, a new download of the source. The ccache was allowed to grow to 20GB and it only used 8.2GB. The swapfile was set at 20GB and it only used around 600MB.

Package Complete: /home/ctaylor/Android/cm11.0-rezound/out/target/product/vigor/
                  cm-11-20140623-UNOFFICIAL-vigor.zip (KitKat)

real    454m42.564s   -- 7.57hrs
user    706m43.646s
sys     59m26.809s

Things have changed: June 26, 2014

The source is now 9GB.
The disc space I don't worry about, since I have over 300GB available.
Swapfile set at 20GB
CCache set at 20GB
The RAM is a different story. I only have 4GB of RAM.
My processor is a Pentium D(2 Cores) at 3.2GHz. It was one of the first Multi Core CPUs.

With this system I was still able to Build a New Android 4.4.4 OS. Took a a long time, but we did it. The times for a Build will vary, depending on whether or not it is your first, -or- you have done a wipe and re-load, -or- you have done a 'make clobber', -or- if you have done a make previously and are just UpDating it. The time can be from 1 hour to over 8 hours. Of course the time also depends on the Power of your PC.
    The following is part of the monitoring that I did on a build of 6/26/2014. You will please notice that the swapfile never exceeded 700MB an the ccache only used 8.2GB. This was on a single user system with nothing else going on but the 'make'. The following commands were performed periodically during the compile. I'm not gona waste space showing all of them. Suffice it to say, I watched it grow to these values and then stop.

ctaylor@dusty-tr2:~
> swapon -s; date; du -hs .ccache_cm11.0-rezound/
Filename                                Type            Size            Used    Priority
/swapfile                               file            20971516        694852  -1
Thu Jun 26 23:50:18 MST 2014
8.2G    .ccache_cm11.0-rezound/

Well, another compile and a little larger use of the swap.

ctaylor@dusty-tr2:~
> swapon -s; date; du -hs .ccache_cm11.0-rezound/
Filename                                Type            Size            Used     Priority
/swapfile                               file            20971516        1145288  -1
Fri Jun 27 09:06:38 MST 2014
8.2G    .ccache_cm11.0-rezound/

Comments...

Android 4.4 will reportedly allow users to select which runtime they use. The available options will be Dalvik and Google's new runtime called ART. Google has stated on its website for developers that ART is a work in progress and is considered experimental at this time. Users wanting to give it a try can enable the new runtime in Android 4.4 via the Settings, Developer Options menu.

Dalvik uses a Just-In-Time compiler and a lot of the compiling is actually done on the user's device each time the app is run,

ART precompiles bytecode into machine language when the apps are first installed turning them into native applications. The process is called Ahead-Of-Time compilation.

ART is yet to become the default setting in Android 4.4.x so here is how you enable it:
1. Go to settings then 'About Phone'
2. Tap the 'Build Number' repeatedly until you get the announcement you're a developer
3. Go back to settings where you will see a new 'Developer options' section
4. In Developer options change 'Select runtime' to 'Use ART'

Your phone will reboot and it will take 10 to 20 minutes to convert your existing app installations to be ART compatible. You'll see a progress count during this. Don't worry, all your app data is safe. Should you wish to switch back just choose 'Use Dalvik' in Developer options. The process takes about 10 minutes to complete and again no app data will be lost.

And rather than the ODEX files read by the Dalvik VM, ART appears to use OAT files. Accordingly, Android 4.4 source also includes a dex2oat program to convert ODEX files into OAT files compatible with ART.

Comments ... Refer: Introducing ART - ART as alternative - Make Your Phone Faster -
What is Odex and Deodex ROM? - What are ART & OAT - new file format, OAT. Contrary to some reports, it doesn't appear to be a new bytecode, but rather a new file format for DEX bytecode. - What is Runtime

Ok. A little explanation here. There are a number of ways to do this. IF there was only one, then anybody could do it. Now it takes a little thought and IF you know a different way then you must translate this way to yours.

Anywho, we found, and use,  GooManager ... a lot. In fact it can, and is, used to install our favorite 'Recovery' TWRP. You also need to be UnLocked and 'root'ed. If you don't understand these then you need to STOP and do a little research. Which could start on one of our other WebPages at:
      Blend-HTCRezound.html#rootRez_ref.     There is a 'lot' of info on this WebPage.
And checkout our GooManager/TWRP Installation page.

These instructions can be considered to be, and are, a "CLEAN" install.

A dirty flash is only wiping cache and davlik then flashing your ROM....

It is recommended that users of this rom to be on the latest firmware and Hboot. Which is at this time (January 10th, 2014)

• HBOOT-2.28.0000
• RADIO-2.23.10.0123r/2.23.10.0124r

Also be better with an S-off device. If you are not on the latest global firmware: Here or Here.

NOTE: For recovery we use TWRP 2.7.1.0. but you can also use CWM Touch 6.0.3.6 Some wipe options below may not be included in other recovery options. Still wipe what is available the best you can.

1. Make sure your phone is in USB debug mode.
2. IF you didn't create one yourself, bring down a ROM from the Net.
3. Compare MD5 Sum
   Windows: MD5 Calculator
   LINUX: Open Terminal and type: md5sum [path to the rom on your sd card]
   Mac: Open a terminal and type: md5 [path to the rom on your sd card]
   
4. IF it's ok, put the ROM on the root of your SD Card
   
5. a.) IF you have GooManager installed:
       Select GooManager then select "Reboot recovery", then 'Yes'.
   b.) Else:
      In a terminal window enter 'adb devices'
           should return the serial number
      Next enter 'adb reboot recovery'
   At this point you should be in TWRP recovery. It is, erroneously or not, at this point, assumed that you are 'UN-Locked', 'rooted', and have a 'Custom Recovery' installed -and- that Custom Recovery is TWRP.
   
6. In TWRP select "Wipe"
7. Wipe the following:

   Swipe to Factory Reset
   ... wait for it to finish...
   Tap Back
   Tap Advanced Wipe
       Select /Dalvik Cache
       Select /cache
       Select /data
       Select /System
   Swipe to Wipe
   ... wait for it to finish...
   Tap Back
   Tap Return (curly at bottom right)
   Tap Return again (curly at bottom right)
   

8. Tap Install
9. Select the SDcard
10. Scroll down to the CM11.0 zip and select it.
11. Swipe to confirm Flash
    ... wait for it to finish...
    ... and hopefully say Successful.
    Now the  gapps  Install
    
12. Tap Home
13. Tap Install
14. Scroll down to the  gapps  zip, of your choice, and select it.
15. Swipe to confirm Flash
    ... wait for it to finish...
16. Tap Reboot System -
17. Wait for the ReBoot
    .... watch animation ....
18. At the Welcome Screen select your Language ... default is English... Tap Next
19. The available WiFi's will be presented. Pick One. Then enter the Password. Tap connect.
20. Now you will be asked to Set up a Google account. IF you already have one, you can Sign On to it.
    Now you'll get the Usual Terms of Service. Tap OK
21. Google Services are presented and you select the ones you want. By default they are ALL selected. Tap the arrow at the bottom. It will say Restoring. and the your account is being contacted.
22. Now you are asked for your CyanogenMod Account. Existing -or- New. After entering it Tap Login.
23. Next is Location settings ... you decide. Then Tap Next.
24. Next is Personalize... you decide. Then Tap Next.
25. Now we have the Date and time settings... do what you want. Then Tap Next
26. And finally ... we have Setup is complete. Tap Finish.
27. You are presented with some Welcome Screen messages. Just Tap OK at the bottom.
28. IF you had previously saved your apps, contacts and people details to Google, you will see download arrows in the upper status bar. It can take up to ten minutes for all of the info to be downloaded.
29. Aug 6th, 2015 - Upon re-installing ... again ... I found that I did not mention a couple of settings that you/we would be interested in, IF you play with developing and the OS. My original verbiage can be found at:  Usage  . Two things; USB settings for transfers between PC and Phone and Developer options enabled.

     USB : Settings -> Storage -> Menu Key: upper right ->
            tap on: USB computer connection -> Check: Mass storage (UMS)

     Developer Options : Settings -> About Phone -> Scroll to Build number ->
            tap on 'Build number' seven(7) times
    Tap the back button -> Developer options -> Scroll to 'DEBUGGIN'
            Ensure 'Android debuggin' and 'USB debugging notify' are checked.

30.     Enjoy

Probably should jump to SDcard and check out the changes -and- fixes.

adb install _____.apk   Installs apk file in your device. Replace dotted space with an actual name of the apk file (Place the apk file in the same folder where ADB & fastboot files are located).

 Back to Stock  

============== for S-on ===========================
9. Install Rom and gapps (in that order) from SD Card
11. Return to the main menu of the recovery and select "Developer Menu".
12. Select "Reboot to bootloader
13. Ensure your device is connected to your computer and that your device is now in fastboot mode. This is a white screen and it says fastboot on it.
14. Open a Terminal (OSX or Linux) or CMD window (Windows) and cd to the platform-tools directory of the Android SDK's install directory.
15. Issue this command to flash the boot.img we placed in the platform-tools folder earlier:

Code:

fastboot flash boot boot.img

16. Watch the output of the terminal, it should say something like "sent successfully".
17. Finally send this command:

Code:

fastboot reboot

This command reboots your device into Android. Wait for it to boot up and enjoy your new freshly installed CM11.0

 Upon the ReBoot - April 11th, 2014/3:52am  Now then, after performing the above install of the New Android, you ReBooted into the System. Upon the First Startup, one of the Options was enabling automatic backup and restore through Google.

  BACKUP & RESTORE
     Back up your data to a Google Account.
     Restore previous backups to this device.
  Data includes apps, app settings, system settings
  and Wi-Fi passwords.

For the most part I had NOT been using this feature. Something haunted me about saving and restoring 'old' data and apps. However, IF you are 'playing' with your phone and ReLoading/ReInstalling the OS... a lot... then this feature can come in very handy. It can be a Big PITA to reload 'all' your favorite apps when, IF you had this enabled, it would be done for you. Yep, it takes some time -but- doing it yourself takes more. It is done in the background so you can use your phone whilst it restores. Naturally, IF the app you want to use hasn't been restored ... yet... you will have to wait. Just go git ur coffee.

Now be aware... that unless things have changed, this is NOT seamless between phones. In otherwords, IF you use the same phone -or- a new one just like it... you should be ok. However, IF you changes phones all bets are off.

Comments ...

Well, things are looking up. Today I created my first Public GitHub. It was/is a fork of the vigor kernel. That is what is need to fix the Camcorder Problem. Bunchies and REV3NT3CH helped me get things setup so that I could accomplish this.

Kernel 3.0 Creation

 October 2nd, 2014  For this particular kernel compile, I received help from Bunchies xda and Reven Tech.

1. We created a vigor dir in my home dir.
2. So after cd to /home/vigor and execute:
3. git clone https://github.com/chucktr/vigor_aosp_kernel.git
   Reference:  vigor_aosp_kernel  
4. It should make a folder vigor_aosp_kernel
5. Which has the kernel files inside
6. So it would end up being:   /home/vigor/vigor_aosp_kernel
7. Then when your ready to build just do the command:   ./vigor
8. Inside the /home/vigor directory
9. If you get an error about executing you may need to do sudo chmod +x *
10. To set all build scripts to executable
11. After a build completes the flashable kernel zip will be in:
        /home/vigor/kernels/updates/
12. And that's if it builds smoothly the first time, we still haven't tried the build scripts on your setup yet
13. But yes that's it

 Kernel_Build_Tools  

Kernel Flashing

1. Copy the kernel ZIP to your phone.
2. Power off your phone... IF necessary.
3. Boot into recovery.
4. Wipe cache.
5. Wipe Dalvik cache.
6. Choose Install Zip from sd card.
7. Browse to the ZIP you copied.
8. Wait while it installs.
9. Reboot.

The following is being used because there is a claim that it is being used by another group on their 8660 stuff. We should just need to make changes for the ReZound.

Kernel 3.4 Creation

 February 4th, 2015  This one was mainly with help from Snuzzo -and- other members of the RezTeam (listed at the top of this page). And now here it is days later and I am trying to further Document it -and- incorporate it into CM11. Information on accomplishing that task is NOT readily available... especially for our ReZound. As mentioned befor, Sultan xda, has made some fantastic accomplishments on his Sensation/Pyramid. We may see IF we can "borrow" some stuff from him.

The first half of this was a combination of converting the stuff Bunchies and Reven Tech showed me, and they created, concerning my compile of the 3.0 kernel. I modified the scripts.

1. We created a vimsm8960 dir in my home dir.
2. So after cd to /home/vimsm8960 and execute:
3. git clone https://github.com/vwmofo/android_kernel_htc_msm8960
   Reference:  android_kernel_htc_msm8960   This was/is the 3.4 kernel that Keith was/is working on.
4. It should make a folder android_kernel_htc_msm8960
   Which has the kernel files inside
   So it would end up being:   /home/vimsm8960/android_kernel_htc_msm8960
5. Then when you're ready to build just do the command:   ./vimsm8960
   from inside the /home/vimsm8960 directory
   Which is a script that Bunchies created.
6. If you get an error about executing you may need to do sudo chmod +x *
   To set all build scripts to executable
7. After a build completes the flashable kernel zip will be in:
       /home/vimsm8960/kernels/updates/
8. And that's if it builds smoothly the first time, we still haven't tried the build scripts on your setup yet
9. But yes that's it
11. From Izzae:
    ok i am in process of trying to compile it for ya
    just to confirm steps
    so what i did was just goto the root of the kernel dir, i did:
    export ARCH=arm
    then i set my toolchain which is from shaun's github
    export CROSS_COMPILE=path to toolchain -- example:
        /home/ctaylor/Android/cm12.0-rezound/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8/
    it broke using his sabermod chain so im guessing a diff one is needed
    but anyways once i did that i do:
    make vigor_aosp_defconfig
    that should make your config for you then make -j#
    
12. Copied /home/ctaylor/vigor/vigor to /home/ctaylor/vimsm8960/vimsm8960 and made appropriate changes inside the script.
13. Inside /home/ctaylor/vimsm8960 I created: kernels dir.
14. Inside the kernels dir I created dirs: kernel, keys, update and updates.
    Which was kinda silly since the script is going to remove them!
15. During the cleanups in vimsm8960 script, it moves into android_kernel_htc_msm8960 dir.
16. After the cleanups we execute build.sh from within android_kernel_htc_msm8960.
17. Which will execute make.sh which needs a proper CROSS_COMPILE.
18. Basically, I copied the necessary files/programs/scripts from the vigor 3.0 kernel dir to the new 3.4 kernel dir and made changes so it would work. Or at least attempt to..
    From inside the vigor/ dir TO vimsm8960/ dir - and modified:
        vigor script to vimsm8960 script - Changed the dir name
       
    From inside the vigor/vigor_aosp_kernel dir TO vimsm8960/android_kernel_htc_msm8960 dir - and some modified:
        build.sh - same as 3.0
        make.sh - same as 3.0
        board-config - changed Toolchain and version number
        sha1.sh - same as 3.0
        update-binary - same as 3.0
        signapk.jar - same as 3.0
        updater-script - same as 3.0
       
       
    
19. February 4th, 2015. Finally created a kernel. Don't think it will work -but- it compiled.

 Kernel_Build_Tools  

Comments...

 May 10th, 2015 / 8:34pm   Ok... I was a little on the ignorant side on this one. There are some propriatary files in a Vendor folder that concern the kernel. These, as the name suggests, come from the Vendor, HTC. They are NOT interested in advancing the ReZound. Therefore, we will NOT get the needed files. So, this particular section is a "dead project". I am keeping it for reference -and- maybe, just maybe modifying the files myself later on.

Now I was getting all set to continue this in the previous section and then decided that it needed its own. So here we are... Now then, the following information is what I was using to "compare" my CM11 build on the HP 7480 Pentium D with the CM11 build on the HP 500-277c i7. On the HP i7 I was getting a whole bunch of    warning: "__GLIBC__" is not defined     in my build.err file. In the end it was determined that it was because of what I was getting from CyanogenMod in the UpDates. Soooo... no more updates. This one is from February 25th, 2015 -and- it was copied over from my HP 7480, I did NOT do another "repo sync".
In the following, ctaylor@dusty-tr2 represents the HP 7480 and ctaylor@Tipper-i7 is the HP i7.

===== after a make clean on the 7480
ctaylor@dusty-tr2:~/Android
> du -hcs cm11.0-rezound
26G     cm11.0-rezound
26G     total
===== after a make on the 7480
ctaylor@dusty-tr2:~/Android
> du -hcs cm11.0-rezound
54G     cm11.0-rezound
54G     total

===================================================================
ctaylor@dusty-tr2:~/Android/cm11.0-rezound/out/target/product/vigor
> ldm
total 892568
-rw-r--r--  1 ctaylor users       132 Feb 24 22:57 cm-11-20150225-UNOFFICIAL-vigor.zip.md5sum
-rw-r--r--  2 ctaylor users 225434962 Feb 24 22:57 cm-11-20150225-UNOFFICIAL-vigor.zip
-rw-r--r--  2 ctaylor users 225434962 Feb 24 22:57 cm_vigor-ota-944c135787.zip
-rw-r--r--  1 ctaylor users 397576232 Feb 24 22:54 system.img
-rw-r--r--  1 ctaylor users     79958 Feb 24 22:54 installed-files.txt
drwxr-xr-x 19 ctaylor users      4096 Feb 24 22:53 obj/
drwxr-xr-x  2 ctaylor users      4096 Feb 24 22:53 fake_packages/
-rw-r--r--  1 ctaylor users   6752256 Feb 24 22:35 recovery.img
-rw-r--r--  1 ctaylor users   2979667 Feb 24 22:34 ramdisk-recovery.img
-rw-r--r--  1 ctaylor users   4549120 Feb 24 22:34 ramdisk-recovery.cpio
drwxr-xr-x  3 ctaylor users      4096 Feb 24 22:34 recovery/
-rw-r--r--  1 ctaylor users   4147200 Feb 24 22:33 boot.img
-rw-r--r--  1 ctaylor users    372940 Feb 24 22:33 ramdisk.img
drwxr-xr-x  8 ctaylor users      4096 Feb 24 22:32 root/
drwxr-xr-x  5 ctaylor users      4096 Feb 24 22:26 symbols/
-rwxr-xr-x  1 ctaylor users   3769544 Feb 24 22:23 kernel*
-rw-r--r--  1 ctaylor users  42775288 Feb 24 22:21 userdata.img
drwxr-xr-x  2 ctaylor users      4096 Feb 24 22:21 data/
drwxr-xr-x 16 ctaylor users      4096 Feb 24 22:16 system/
drwxr-xr-x  4 ctaylor users      4096 Feb 24 21:53 external/
-rw-r--r--  1 ctaylor users        12 Feb 24 21:52 android-info.txt
-rw-r--r--  1 ctaylor users       766 Feb 24 21:48 previous_build_config.mk
-rw-r--r--  1 ctaylor users     38739 Feb 24 21:48 clean_steps.mk
==================================================================================
===== before a make on the i7
ctaylor@Tipper-i7:~/Android
> du -hcs cm11.0-rezound
26G     cm11.0-rezound
26G     total
-- wiped ccache before make
-- then checked that cookie was done
ctaylor@Tipper-i7:~/Android/cm11.0-rezound/frameworks/av
> git fetch https://github.com/vigor/android_frameworks_av cm-11.0 && git cherry-pick 1dd29957a2292c0398923ffff8e2aca47c5931ac
From https://github.com/vigor/android_frameworks_av
 * branch            cm-11.0    -> FETCH_HEAD
HEAD detached from ebdbd54
You are currently cherry-picking commit 1dd2995.

nothing to commit, working directory clean
The previous cherry-pick is now empty, possibly due to conflict resolution.
If you wish to commit it anyway, use:

    git commit --allow-empty

Otherwise, please use 'git reset'
===== after a make on the i7
ctaylor@Tipper-i7:~/Android
> du -hcs cm11.0-rezound
54G     cm11.0-rezound
54G     total
=====================================================================
ctaylor@Tipper-i7:~/Android/cm11.0-rezound/out/target/product/vigor
> ldm
total 892572
-rw-r--r--  1 ctaylor users       132 Feb 28 07:41 cm-11-20150228-UNOFFICIAL-vigor.zip.md5sum
-rw-r--r--  2 ctaylor users 225436002 Feb 28 07:41 cm-11-20150228-UNOFFICIAL-vigor.zip
-rw-r--r--  2 ctaylor users 225436002 Feb 28 07:41 cm_vigor-ota-9453cf4b2b.zip
-rw-r--r--  1 ctaylor users 397576232 Feb 28 07:40 system.img
-rw-r--r--  1 ctaylor users     79958 Feb 28 07:40 installed-files.txt
drwxr-xr-x 19 ctaylor users      4096 Feb 28 07:40 obj/
drwxr-xr-x  2 ctaylor users      4096 Feb 28 07:40 fake_packages/
drwxr-xr-x 16 ctaylor users      4096 Feb 28 07:33 system/
-rw-r--r--  1 ctaylor users   6752256 Feb 28 07:32 recovery.img
-rw-r--r--  1 ctaylor users   2979669 Feb 28 07:32 ramdisk-recovery.img
-rw-r--r--  1 ctaylor users   4549120 Feb 28 07:31 ramdisk-recovery.cpio
drwxr-xr-x  3 ctaylor users      4096 Feb 28 07:30 recovery/
-rw-r--r--  1 ctaylor users   4147200 Feb 28 07:27 boot.img
-rw-r--r--  1 ctaylor users    372941 Feb 28 07:27 ramdisk.img
drwxr-xr-x  8 ctaylor users      4096 Feb 28 07:26 root/
drwxr-xr-x  5 ctaylor users      4096 Feb 28 07:25 symbols/
-rw-r--r--  1 ctaylor users  42775288 Feb 28 07:08 userdata.img
drwxr-xr-x  2 ctaylor users      4096 Feb 28 07:08 data/
-rwxr-xr-x  1 ctaylor users   3769544 Feb 28 06:58 kernel*
drwxr-xr-x  4 ctaylor users      4096 Feb 28 06:23 external/
-rw-r--r--  1 ctaylor users        12 Feb 28 06:22 android-info.txt
-rw-r--r--  1 ctaylor users       766 Feb 28 06:20 previous_build_config.mk
-rw-r--r--  1 ctaylor users     38739 Feb 28 06:20 clean_steps.mk

Now you will notice that there are differences in the sizes between the two systems. I really think that they should be the same size -but- they are not. The HP 7480 is on openSuSE 12.3
    -rw-r--r-- 2 ctaylor users 225434962 Feb 24 22:57 cm-11-20150225-UNOFFICIAL-vigor.zip
and the HP i7 is running on openSuSE 13.2
    -rw-r--r-- 2 ctaylor users 225436002 Feb 28 07:41 cm-11-20150228-UNOFFICIAL-vigor.zip.

 March 3rd, 2015/11:33pm   On BOTH machines I wiped the "ccache", did a "make clean" -and- just for good measure did a "make clobber". Did NOT do a "repo sync" on either PC. It is the same "exact" code on both. The HP 7480 will take 8 hours, plus or minus, to compile. My HP i7 will take an hour±. The "Old" machine was started at 11:26pm and we will start the "New" machine just before we hit the sack. Which is: 1:54am
= = = =
HP 7480 real 476m8.356s
    -rw-r--r-- 2 ctaylor users 225442428 Mar 4 07:22 cm-11-20150304-UNOFFICIAL-vigor.zip
HP i7 real 77m34.403s
    -rw-r--r-- 2 ctaylor users 225435938 Mar 4 03:12 cm-11-20150304-UNOFFICIAL-vigor.zip

Sultanxda references

 March 5th, 2015/12:33am    Sultanxda KitKat    CAF 3.4 Kernel    SebastianFM kernel  
Source code:
Kernel (cm-11.0 branch): https://github.com/sultanxda/sultan-kernel-pyramid
Device tree (cm-11.0_3.0 branch): https://github.com/sultanxda/android_device_htc_pyramid
Vendor binaries (cm-11.0 branch): https://github.com/sultanxda/android_vendor_htc
My manifest (cm-11.0 branch): https://github.com/sultanxda/Android

Building the code

 building custom Android Kernel    the porting guide  

Ok... I've looked and can not find info on properly incorporating a new kernel into my ROM. So, I am just gona have to do as I usually do ... shotgun it!! I don't even remember where I/we got this version of the 3.4 kernel that I am sticking in the ROM.(Yes I do!! From Keith thru Shaun.) But here goes:

1. First we setup a CM11 area to modify. ~/Android/cm11.0-rezound-3.4
2. Next, we open 2 Dolphins. One for the ROM code and the other for the Kernel code. Have named the ROM code dir: cm11.0-rezound-3.4 and the kernel code dir: android_kernel_htc_msm8960.
3. In the ROM dir we have ../kernel/htc/vigor-3.0 which we are going to change to vigor-3.4. Actually, we are going to create a new dir in which to copy the new kernel code. The 3.0 kernel dir and the 3.4 kernel dir have the same sub-dirs. Copied over the 3.4 kernel code and deleted the 3.0 dir.
4. Changes needed in ../device/htc/msm8660-common/BoardConfigCommon.mk
   # Kernel
   TARGET_KERNEL_SOURCE := kernel/htc/vigor-3.4
   I changed the 3.0 to 3.4.
   
5. Changes needed in: ../device/htc/vigor/BoardConfig.mk
   # Kernel
   BOARD_KERNEL_BASE := 0x48800000
   BOARD_KERNEL_PAGE_SIZE := 2048
   BOARD_KERNEL_CMDLINE := console=ttyHSL3 androidboot.hardware=vigor \
     no_console_suspend=1 androidboot.selinux=permissive
   TARGET_KERNEL_VERSION := 3.4
   TARGET_KERNEL_CONFIG := vigor_aosp_defconfig
   TARGET_KERNEL_SOURCE := kernel/htc/vigor-$(TARGET_KERNEL_VERSION)
   
6. After the above changes we did a make clean and wiped our ccache. Fired off first make... and got these results: well, on the tail end.
   

   target thumb C++: copybit.msm8660 <= hardware/qcom/display-legacy/libcopybit/copybit_c2d.cpp
   target thumb C++: copybit.msm8660 <= hardware/qcom/display-legacy/libcopybit/software_converter.cpp
   target thumb C++: libmemalloc <= hardware/qcom/display-legacy/libgralloc/ionalloc.cpp
   target thumb C++: libmemalloc <= hardware/qcom/display-legacy/libgralloc/alloc_controller.cpp
   build/core/binary.mk:432: recipe for target '/home/ctaylor/Android/cm11.0-rezound-3.4/out/target/product/vigor/obj/SHARED_LIBRARIES/libmemalloc_intermediates/ionalloc.o' failed
   build/core/binary.mk:432: recipe for target '/home/ctaylor/Android/cm11.0-rezound-3.4/out/target/product/vigor/obj/SHARED_LIBRARIES/libmemalloc_intermediates/alloc_controller.o' failed
   
   real    24m38.451s
   user    78m36.071s
   sys     35m24.720s
   ctaylor@Tipper-i7:~/Android/cm11.0-rezound-3.4
   > 
   

    Make Text Functions  

   ---

7. The ReZound Build:
   1. Check out the ../vigor/neofy.sh script... and it's description at:  Neofy descript  
   2. ctaylor@Tipper-i7:~/Android/cm11.0-rezound-3.4
      > ./TRmake.sh
   3. Actually the make file excutes this environment setup first:

      ctaylor@Tipper-i7:~/Android/cm11.0-rezound-3.4
      > . build/envsetup.sh 
      including device/generic/armv7-a-neon/vendorsetup.sh
      including device/generic/goldfish/vendorsetup.sh
      including device/generic/mips/vendorsetup.sh
      including device/generic/x86/vendorsetup.sh
      including device/htc/vigor/vendorsetup.sh
      including vendor/cm/vendorsetup.sh
      including sdk/bash_completion/adb.bash
      including vendor/cm/bash_completion/git.bash
      including vendor/cm/bash_completion/repo.bash
      

   4. The following is inside TRmake.sh   Don't know who created the make script originally, -but- I am claiming it now.
            { time brunch vigor 2>build.err ; } 2>&1 | tee build.log
   5. Now then, the follwing function is in the envsetup.sh script that gets executed at the begining of TRmake.sh:

      function brunch()
      {
          breakfast $*
          if [ $? -eq 0 ]; then
              mka bacon
          else
              echo "No such item in brunch menu. Try 'breakfast'"
              return 1
          fi
          return $?
      }
      

      Ok, we went into breakfast and then got invited to lunch.

      -TR envsetup.sh- Entering brunch ---
      -TR envsetup.sh- Entering breakfast ---
      including vendor/cm/vendorsetup.sh
      -TR envsetup.sh- Entering lunch ---
      Device vigor not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
      Found repository: android_device_htc_vigor
      Default revision: cm-11.0
      Checking branch info
      Default revision cm-11.0 not found in android_device_htc_vigor. Bailing.
      Branches found:
      cm-10.1
      jellybean
      Use the ROOMSERVICE_BRANCHES environment variable to specify a list of fallback branches.
      
      ** Don't have a product spec for: 'cm_vigor'
      ** Do you have the right repo manifest?
      
      -TR envsetup.sh- Leaving breakfast ---
      

   6. The following is an excerpt from the build.log file. I was having problems understanding just what it was trying to tell me. It didn't make sense. So I stuck more and more comment/info statements in the mk and the sh files. After an increase in confusion, we finally realized that the problem was... the variables that we were trying to display were NOT getting set!! -And- that was because we were NOT getting the "ToolChain"!! Looks like we have a mix of 4.7 and 4.8 toolchains. I can say that now because of all my trials and tribulations. I am in the process of figuring them out...

      -TR envsetup.sh- Entering brunch ---
      -TR envsetup.sh- Entering breakfast ---
      including vendor/cm/vendorsetup.sh
      -TR envsetup.sh- Entering lunch ---
      Trying dependencies-only mode on a non-existing device tree?
      
      -TR envsetup.sh- Product: cm_vigor ---
      -TR envsetup.sh- Varient: userdebug ---
      -TR envsetup.sh- Setting stuff for Environment ---
      -TR envsetup.sh- Entering settitle ---
      Can't find toolchain for unknown architecture:  -TR -Entering TARGET_linux-arm.mk -- - 
      arm
       -TR -Entering TARGET_linux-arm.mk -- - 
      ============================================
      PLATFORM_VERSION_CODENAME=REL
      

   7. Mostly what I have been doing is ... putting in $(info -TR-) and echo "-TR-" to tell where things are in the make process... -and- fix things -and- try to remember to document it!!
      March 9th, 2015 -- Well we are on another go around... lost count on which one.

      ---

   8. ../build/core/tasks/kernel.mk -- Need to fix the CROSS_COMPILE. I made a "temporary fix".
      March 9th, 2015 -- On this go, we are gona fix it properly. It has been, as we have learned, our biggest problem.
      

      cm11.0 will use 4.7 unless you define TARGET_KERNEL_CUSTOM_TOOLCHAIN flag
      in boardconfig
      thought it was in envsetup
      it is but you can change it with a quick boardconfig flag now
      rom for cm11.0 ius 4.7 by default
      and kernel's doesnt have to be the same
      TARGET_KERNEL_CUSTOM_TOOLCHAIN := arm-eabi-4.8
      prebuilt/linux-x86/toolchain/arm-eabi-4.8
      &&
      TARGET_KERNEL_CUSTOM_TOOLCHAIN := arm-eabi-4.8									
      

       Change Color in echo  
      $(TOP)is ~/Android/cm11.0-rezound-3.4
      $(BUILD_SYSTEM) is build/core
      TARGET_DEVICE is vigor
      -Annndddd... what we have here ... is a failure to communicate. Turns out my biggest problem has been all those echo statements that I placed in envsetup.sh. Don't know why or how the proper values were being replaced or added to by my echo commands ... -but I will find out.

      ---

   9. These are the makefiles and scripts that I have put "extra comments" in, in order to learn and find the problems.
      These may still get changed ... again.. but they were what helped me find the above problem... the toolchain.

      ./frameworks/av/media/libstagefright/Android.mk
      ./frameworks/av/services/camera/libcameraservice/Android.mk
      ./frameworks/av/camera/Android.mk
      ./device/htc/msm8660-common/msm8660.mk
      ./device/htc/msm8660-common/BoardConfigCommon.mk
      ./device/htc/vigor/BoardConfig.mk
      ./build/target/product/core_minimal.mk
      ./hardware/qcom/display-legacy/libgralloc/Android.mk
      ./hardware/qcom/display-legacy/Android.mk
      ./hardware/qcom/display-legacy/common.mk
      ./hardware/broadcom/wlan/bcmdhd/config/Android.mk
      ./system/core/uncrypt/Android.mk
      ./bootable/recovery-cm/Android.mk
      ===
      ./kernel/htc/vigor-3.4/build.sh
      ./kernel/htc/vigor-3.4/build-vigor.sh
      = = =
      ./kernel/htc/vigor-3.4/AndroidKernel.mk
      ./external/exfat/Android.mk
      ./build/core/tasks/kernel.mk
      ./build/core/combo/TARGET_linux-arm.mk
      ./build/core/qcom_target.mk
      ./build/core/static_library.mk
      ./build/core/base_rules.mk
      ./build/core/droiddoc.mk
      ./build/core/version_defaults.mk
      ./build/core/main.mk
      ./build/core/Makefile
      ===
      ./build/envsetup.sh
      ./ndk/build/tools/rebuild-all-prebuilt.sh
      ./ndk/build/tools/dev-defaults.sh
      

      Now then, in my first attempt, I made some changes in addition to the comments.
      BAD - BAD. Didn't properly investigate -nor- document. So, I put them all back and we will start again.
      As mentioned in the previous section ... I was causing almost ALL of my problems!!!
   10.  March 11, 2015 / 1:19am  We have another compile going and it is getting a lot farther with the "Normal envsetup.sh". Now to properly troubleshoot it and get that ToolChain setup.
       

       Example from G2 in BoardConfigCommon.mk -- in the Rez it is BoardConfig.mk
       # Custom toolchains
       TARGET_GCC_VERSION_EXP := 4.8-sm
       TARGET_GCC_VERSION_ARM := arm-eabi-4.9-ln
       TARGET_KERNEL_TC_SUFFIX := arm-cortex_a15-linux-gnueabihf-
       

       TARGET_ARCH_AND :=4.8
       and is the rom
       which equals android
       arm is always kernel
       a good example
       of how im defining what i want my g2 to build at for desolation
       https://github.com/DesolationRom-Devices/android_device_lge_g2-common/blob/lp/BoardConfigCommon.mk#L49-52
       ====
       one calls for android (exp) where as one calls for the kernel (arm)
       boardconfig of main device tree
       for you
       in here
       https://github.com/vigor/device_htc_vigor/blob/ill_kk/BoardConfig.mk
       which has none
       ====
       Ok ... so I need to add those lines to that file in my Rez???  -OR- do I look to see where and if they
        are set already and then change them??
       3 mins
       Chuck Taylor
       Reven Tech
       Well 2 things
       In the manifest file in the .repo folder
       You need to see if any other toolchains are being brought in first
       Say 4.6 or 4.7 maybe even 4.8
       If the one you want is not there
       Then you'll need to make one for it in local Manifest for it to clone in when you sync from the source its at
       Keep in mind though
       ====
       A lot of this stuff I'm gonna start cramming into learning videos so you will be able to watch as I demonstrate it
       A lot of how you build android is 2 big key factors
       Source being synced...which for cm uses Git ( and all the Git tools and functions) and the scripts said source uses
       Say I changed "build" folder in my ROMs source to "building" and the "envsetup.sh" to just "romsetup.sh"
       The command to then run would be
       . building/romsetup.sh
       See the difference
       The knowledge of just that can teach alot
       Within the envsetup.sh though
       Usually
       Shows how it calls for kernel and ROM toolchains in the whole build
       ====
       i just showed
       https://github.com/CyanogenMod/android_build/blob/cm-12.0/envsetup.sh#L147
       prime example
       taken from cm themselves
       TARGET_GCC_VERSION
       ====
       straight from their build/envsetup.sh
       So
       What I linked way back
       TARGET_GCC_VERSION_EXP
       And
       TARGET_GCC_VERSION_ARM
       in device sources boardconfig.mk
       Will override the ROMs call for them always
       So of you have said 4.8 synced
       And want to change either or
       Add those calls
       So long as they are being pulled in from ROM themselves or a local manifest
       Do you see where I'm going on this
       Follow the breadcrumb trail
       And it will lead you to what you want to get to
       Always
       ====
       OK... so IF I use those earlier statements in mine ... then I will be using that ToolChain??
       ===
       So long as they are pulled proper
       Yes
       If you want
       ====
       Wasyou mean "pulled proper"??
       ===
       We can do a team view session in the next few days
       Called via manifest or local manifest and placed in proper directory on said sync
       Which ends up somewhere in prebuilts/gcc
       ====
       ctaylor@Tipper-i7:~/Android/cm11.0-rezound-3.4
       > fgrep -rl TARGET_GCC_VERSION *
       art/build/Android.common.mk
       build/core/dumpvar.mk
       build/core/combo/TARGET_linux-mips.mk
       build/core/combo/TARGET_linux-x86.mk
       build/core/combo/TARGET_linux-arm.mk
       build/envsetup.sh
       build/TR-envsetup.sh
       build/tools/adbs
       development/scripts/symbol.py
       packages/inputmethods/LatinIME/native/jni/Android.mk
       ====
       

   11.  March 12, 2015 / 11:45pm   At this point I had been conversing with Rev on setting up the configuations. I also copied arm-eabi-4.8 from CM12 to CM11. In the kernel build I was pointing to it. So I moved it to CM11, where I am working at the moment.
   12. ../hardware/qcom/display-legacy/libgralloc/alloc_controller.cpp --
       We are failing here cause some 'vars' are out of scope!!

Comments...

 July 15th, 2014/3:15am  The following Error was received trying to Flash Standard Gapps. Ones created by CyanogenMod themselves. At this time, my only way around this is to use the Gapps created by Banks.
Message page 231 in the Rez Thread.

Installing files...
Cleaning up and setting metadata...
set_metadata_recursive: some changes failed
E: Error executing updater binary in zip '/sdcard/gapps-kk-20140606-signed.zip'
Error flashing zip '/sdcard/gapps-kk-20140606-signed.zip'

Its in the source but the flag isn't being set
https://github.com/vigor/device_htc_vigor/commit/89c39d2a61133a79aa3bae1691ed66cbe978f647

 A Definition  Users of data must be able to put their data in context before the data becomes useful as information. Metadata describes data, providing information like data type, length, textual description, and other characteristics of the data. So, for example, metadata allows the user to know that the customer number is a five digit numeric field, whereas the data itself might be 53781.

From December 10th, 2013 TRComputing

Thought we had experienced this problem before, and we had. Only on this one it was a problem installing the ROM itself. You will notice that the error message is NOT quite the same. After discussing things with Neo we got a "cherrypick" fix that took care of the problem. Shortly thereafter it was fixed so that the cherrypick was no longer needed.

We finally got our copy of the source to compile. -But- could not get a successful install:

set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/sdcard
Error flashing zip '/sdcard/sideload.zip'
Updating partition details...
        Failed

Anytime you see the set_metadata_recursive error, that's the METDATA flag that's 
packaged in the build. You either need a recovery that supports METADATA, or apply 
this cherrypick : http://review.cyanogenmod.org/#/c/53559/

 _litz on the Forum   There are all kinds of nice friendly scripts to help you out in the "Build Scripts" folder, which if you used initrepo.sh, will be located in the /vigor directory under your build root.

One of those is "cherrypick.sh" which can be used to apply the cherrypick.

Copy this script to your build root, then "./cherrypick.sh check" to verify your list of picks, and if they are new, merged, abandoned, etc.

Then "./cherrypick.sh auto" to apply. Do this AFTER a repo sync, and BEFORE you initialize a build.

 And finally proper guidance from the Man:   Neo Directions

Comments...

 USB - Settings -> Storage -> Menu Key: upper right ->
        tap on: USB computer connection -> Check: Mass storage (UMS)

 January 10th, 2014/10:49am  Have compiled and installed the "latest" KitKat developed for the ReZound. After installation of the OS, we need to enable the "Developer Options". Which brings up that I do not like the default screen setup. Not really associated -but- at this point in time that is the way we feel. It comes up with 3 screens. The 'Left' screen is the one that comes up and it has the 'Music' player as it's default. Slide the screen out to the left and you see the 'Middle' screen which has the 'Clock and Weather'. We feel this should be the default and maybe there are settings to make that happen.

Slide the screen once more to the left and we get the last one. It contains 'Messaging', the 'Gallery', and 'Settings'. Which is what we need to enable the 'Developer Options'. You tap on the 'Settings' icon and then scroll all the way to the bottom to the 'About phone'. Next we 'tap' the 'About phone' and scroll down to 'Build number'. This you 'tap' on Seven(7) times in order to 'Enable' the 'Developer Settings'. Now press the 'return key' to get back to the previous screen and 'tap' Developer options. Scroll down on the newly present screen and 'Tap' on Android debugging. Tap OK in response to the question. Tap the 'Return key' a couple of time to exit out of all this. Now with 'Debugging options' enabled we can use the USB connection to our Computer and use 'adb' and 'fastboot'. You 'may' or 'may not' have to unplug your phone USB from the computer and then plug it back in IF you had it connected in the first place. JFYI

Now we want to install  Gapps ... BUT which one??

 Gapps Selections:   Official Gapps; Banks GApps; Slim GApps; and PA GApps
Which gapps work the best? -and- RootsWiKi

 February 3rd, 2014/10:33am   Neo produced a new CM11 and we downloaded it. Through our other 'investigatios' we have decided that we are gona use the  PA Gapps  this go-around.

 April 11th, 2014/3:12am  New findings on the Gapps situation. Gapps is a package and NOT a unit. Therefore, there is nothing on your phone stating which Gapps you have installed. The 'main' thing you have to be sure of, is that the Gapps you installed is for the 'Current Version of Android' that you have installed. GingerBread, JellyBean, KitKat.
Refer: Determine Gapps

 USB Storage  

First, connect the phone to the PC and select USB storage mode. Next, copy your chosen  Gapps  zip file to your phones SD card. AFTER the copy take it out of this mode. Because of my own failings, I can't believe that I am gona say this -but- if you don't understand how to do this... then you shouldn't be messing with your phone. There is a 'charge' mode and a 'storage' mode. (Normally, the default connection is 'charge' mode.) -And- once again, we are assuming you are using TWRP.

1. Connect the phone USB to PC USB... in charge mode.
2. Open a command -or- terminal window... on the PC.
3. In the terminal window enter - adb devices to see IF we are connected.
   IF we are, it will display the phones serial number... in the terminal window.
4. Next enter: adb reboot recovery. This will take you to TWRP.
5. Select Install
6. IF /sdcard in not the default dir, listed at the top, then Tap Up a Level and then Select sdcard
7. Scroll down and Select the gapps kk file.
8. Check that file is correct and then Swipe to Confirm Flash ..
9. Wait for finish...
10. Wipe the Dalvik & cache
11. Tap Back
12. Reboot System and enjoy... February 16th, 2014/5:54am

Full Complete PA GApps includes the Core Google Base* plus the following Play
Store Apps

Gmail | Google+ | Google Calendar | Google Drive | Google Earth | Google Keep 
Google Keyboard (replaces AOSP Keyboard) | Google Play Books | Google Play Games
Google Play Magazines | Google Play Music | Google Play Movies | Google Play 
services
Google Search | Google Wallet | Hangouts | Maps | QuickOffice | Sound Search for 
Google Play
Street View on Google Maps | TalkBack | YouTube
* Core Base includes core Google system base as well as FaceUnlock, Google TTS,
and the News & Weather Widget?

   Some Serious Usage April 4th, 2014/5:46pm    
Allllllrighty now... we have created a new build with the latest software and need to check it out. Found out later that Neo also created one on this same day, April 3rd, 2014. However, today, the next day, we are trying to examine everything. Some is working OK and other stuff is not. -But- what makes matters worse is the facts that it works... and then it doesn't!! So we will start a list of what we did and what we found.

• Naturally the first thing is to Build -or- Compile the OS. That was accomplished successfully yesterday. A 198.2MB file.
• Next is to install the OS and Gapps. We chose the PA minimal gapps.
  Right off we have a problem. No contacts -and- it says it can't find the contacts on the SD card that we know are there. Think that this has something to do with the changes in the SD card Ops by Google. We tried to make a phone call to a Med facility and upon answer the screen went black. We could not respond cause there was no screen. We had to wait till they hung up. Immediately went into the settings and set it to HangUp when the Power Button is pressed. During this I had to register my existing Google Account. After that registration I got my contacts back cause they were saved on my Google Account
•  6:37pm   Turned on and paired up my Bluetooth. Tried another call. This time the screen did not black out -but- could not get the keypad up and could not hangup via the Red Bar with a phone on it. Had to use the Power Button. Letting it set...
•  6:52pm   Call still not successful.   Went back to ICS... IT WORKS!!
•  April 11th, 2014/5:17pm  Been one heck of a week. Bounced around several ROMs and have finally settled on the one I built on February 10th, 2014. Any of the 'later' ones, including the one I built on the 9th, will loose their data and Internet connections when you get away from your 'Home Site'. Yes! Distance is a problem and it is NOT my phone. I can install the Feb 10th version and it will work... no matter how far away you are. Any of the March or April ones fail.
      The auto phone call problem turned out to be the Proximity Sensor. Even though it worked in ICS it would not work in the newer KitKats. Turns out that the 'default' setting for the Proximity Sensor on versions is different -and- the Prox Sensor controls the Touch Sensor... or at least it sure looks that way.
• As of April 10th, 2014 we are using cm-11-20140210-UNOFFICIAL-vigor.zip with 2-27_GApps_Minimal_4.4.2_signed.zip

Comments ...

IF you click on the 'icon' in any of the following, it will take you to the WebPage of the 'app'. Now then, wanting to keep the following single line entries, we'll make our comments here. You will notice there are two calculators. The comments on the first one should explain it, IF you read between the lines. I found it first. Not only that, the keys are bigger... for my 'Senior Moments'.

Well, the single line concept got waylaid. I just had to add some commentary.

1. HD Widgets - Clock and Weather.
2. Apollo - This is "Normally" included with CyanogenMod.
3. Hangouts
4. RPN-16C - Well, this one is closer... it is an emulation of the HP-16C.
5. App List Backup Pro - This is used to help me get back all my apps.
           Google Restore sometimes misses one or two.
6. Battery Doctor - Good information and has its own indicator, with percent. Well, this one went downhill. Ads and other junk, and it got confusing.
7. Avast Battery Saver - Works great and doesn't have all the ads. And I understand it better.
8. Avast Clean Boost - a highly effective cache and junk cleaner app for Android.
9. File Explorer
10. File Explorer (Root Add-On)
11. Recovery Reboot
12. Rezound Prox Sensor Calibrator
13. Hardware Detection
14. Root Checker installed even though 'root' is included. I just like that 'Root Checker' app.
15. Kernel Tuner and we have XDA Info
16. Next Switch Widget - Wifi, Ringer, Bluetooth, Brightness, MobileNetwork, GPS, Auto-sync,
            Airplane mode, Vibrate, ScreenTimeout, Lock screen, Ringer volume, Media volume
            (Because of this one, the other 3 were removed.)
17. Network Monitor Mini
18. Camera Fx - Editor's Choice on Google Play.
19. Voice Speed Dial
20. Gallery - CyanogenMod
21. Google Maps for directions and finding places.
22. Netflix
23. Simple Stopwatch & Timer free
24. System Diagnostic Event Logs
25. Tip Calculator- AD FREE
26. Easy Uninstaller App Uninstall
27. Calendar Widget: Month+Agenda
28. Next Launcher 3D Shell Lite - Really neat effects.. in 3D and they work on our ReZound!!
            Bought the regular one.
29. Next Launcher 3D Manuals
30. Next Time Tunnel 3D LWP - This is not exactly an app and you won't find it in your
            apps drawer. It is a Live Wallpaper inside Next 3D Launcher.
31. ai.type Keyboard Plus
32. ai.type Emoji Keyboard plugin
33. TWRP - Team Win Recovery Project, released a touch-based recovery for the HTC Rezound.
34. Firefox Browser for Android
35. Quick Boot (Reboot)
36. Sensible Missed Call Reminder
37. Purchased Apps - This is also used to help me get back all my apps and it tells me
            which ones I spent money on.
38. TWRP Manager (ROOT)
39. RealCalc - Closest thing to my HP-35 and HP-16.
40. Fancy Widgets - Again, closest thing to HTC Weather Clock.
41. Fancy Widgets UNlocker - Unlocks premium features in Fancy Widgets.
42. SkyDroid - Golf GPS - What impressed me most about this is that it has my course!!
43. KitKat - Battery Overlay Percent
44. WiFi ON-OFF - Allows you On/Off your WiFi with only 1 click.
45. Mobile Network ON-OFF - Enable/disable (switch on/off) data with a single click
46. Bluetooth ON-OFF - A simple icon for turning blue tooth on/off
47. Android Sensor Box
48. Cyberon Voice Commander(US)
49. Absolute RC Plane Simulator
50. Clean Master Phone Boost
51. TouchRetouch Free
52. SIM Card Manager
53. Android Terminal Emulator
54. Pydio Put Your Data In Orbit Went out of business.
55. build.prop Editor
56. GooManager Use for "Buttonless" operations and installation of TWRP.(No longer supported.)
57. Logcat Extreme Pro
58. Volume Unlock Power Button Fix Didn't work for me -and- you are still using buttons.
59. Gravity Screen - On/Off This one has promise.
60. Wakelock Detector [Root]

 Monday/Tuesday January 27/29th, 2014  Over these three days, cause we started late, we installed Neo's latest:  cm-11-20140127-UNOFFICIAL-vigor.zip ... and our own:  cm-11-20140129-UNOFFICIAL-vigor.zip .

 Settings -27jan14  Already we don't like the change. Our 'Menu Button' does not give us the settings like it used to. It only provides a few meager things. The main settings, like we use to get, requires an entry into the apps drawer and selecting the settings gear there.
Partial self and partial forum.

 Set Home Screen -27jan14 
Finally figured this one out. It comes up with 3 screens by default and the first one, or screen 0, is the Home Page. In order to make the Middle one the Home Page you must Press the Menu Button, then Press the Settings Gear, then Press the Default Screen, then Slide the number 1 into the middle selection. Then press ok. Now when you press the Home key the middle screen will show up if it is not there already.
Figured this one out myself.

 How do you screenshot -27jan14 
Hold 'Power' and 'Volume Down' at the same time and wait for the animation, and if your ring volume is up high enough, a shutter sound. From: kcipopnevets on page: 99
Well it didn't work. All I managed to get was my Volume Off -or- the Power Off dialog. Probably didn't have my tongue on the correct side.

From Neo: You gotta press down on both buttons at the exact same time and hold them down for at least 2 seconds or until the animation/shutter sound takes place. If you end up with power options or volume changes then they're not being pressed at the same time .

 Calendar Syncing... 
Flashing the "calendar sync" zip took care of it. You can find it here: Calendar Sync Zip
From: dbchristensen on page:     Just info I obtained. Haven't tried it yet.

 A Better Gapps 
A better gapps to use is probably 20140105. Can be found at: http://wiki.cyanogenmod.org/w/Google_Apps
direct link http://itvends.com/gapps/gapps-kk-20140105-signed.zip
From: Flyhalf205     Just info I obtained. Haven't tried it yet.

 Phone Contacts -27jan14 
Well, IF you exported your contacts to your SD card then you can import them from there. Or if you have them on your SIM card you can import them from there. Otherwise, it is anybody's guess.
Figured this one out myself. And there is also the "Restore" from Google...duhhh.

 Making a Phone Call -27jan14 
This proved to interesting the first time. After I got my contacts imported I tried to call my wife. Now how do you see/select from your contacts?? Well, first thing is, from your Home Page you tap on the blue phone in the lower left corner. Then you get a screen with a Clock, a People and a Star. And up at the top of the screen it claims you can type a name -or- a number. Well, a couple of times that I tried it, it interpreted my letter entries as numbers!! Not sure where that was comming from. Eventually got it to realize that I was typin' in names... and not numbers. But once in a while it will get confused... and I will have to start over. It is good on the number pad. When I start typing a number it starts listing my contacts in the upper background. IF the number is one of my contacts it will show them. Improvement?? Need to use it more.
Figured this one out myself.

 Music -27jan14 
Ah one of the things I like about these newer phones. They include an MP3 player. This means you don't have to carry two devices. Of course IF you're listening to much, your battery will go down... and then no music -or- phone. So, it depends on the situation. Didn't think I was gona like the player with this CM11 -but- I like it a lot. It is going out on the Web and getting the Album covers to display 'with' my songs.
Figured this one out myself.

 USB -29jan14 
To access it as, and use it as, storage, you first connect the USB cable to the ReZound and to the computer. You will then see a USB symbol in the notification line at the top -and- a Cyanogen head IF you have Debugging enabled. Next you need to scroll down the notification line and tap on the 'USB connected'. This will present you a green Andy screen with a 'Turn on USB storage' button at the bottom. After you tap the button you will get another screen with an orange Andy that says 'USB storage in use' and another button at the bottm that says 'Turn off USB storage'.
Figured this one out myself.

 Obtaining another Screen -29jan14 
This was a benificial accident. When you install something from PlayStore, it puts it in your drawer -and- on the screen that you are on at the time. I wanted it moved. Normally, I would delete it from the screen where I didn't want it and then re-install it on the proper screen from within the drawer. However, I decided to try moving it from one screen to another. It did -but- I went to far -and- it created another screen!! So the 3 became 4.
Figured this one out myself.

 Selecting another Screen -01feb14 
Instead of double tapping the Home key you press the Menu key. You can then 'slide' through the screens and select the one you want.
Figured this one out myself.

Comments ...

 Launcher - Settings -> Home -> Launcher choices: Launcher3 -or- Trebuchet
Also Refer: Android Central

Launchers are the 'Desktop Environment' of the the phones.  Android  provides defaults -and- you can chose from some others created by some developers. The launcher usually is considered to be the homescreens and app drawer.

To start of with, similar to our SuSE Linux which offers two desktop environments, KDE and Gnome, we are given two Launchers to choose from. In our latest install, we initially chose Launcher3. It worked ok so we decided to try out Trebuchet. Well, that was a failure!! We were trying to make the choice at the 'Home Key' press but all we got was:

Unfortunately, Trebuchet has stopped
             ok

ANDROID_PACKAGES_APPS_TREBUCHET 2014-02-01 04:50:20
Fix L3 and old Trebuchet migration...
There can only be one original-package tag. Go with com.android.launcher3
for now, and move Trebuchet back to com.cyanogenmod.trebuchet. This will
allow for workspace migrations from both CM10.2 Trebuchet and from CM11 Launcher3

Now we have an interesting aspect in this latest CM11 creation. IF you have NOT locked in a Launcher you will get a choice of the available ones by Tapping the Home Screen key. And IF you make your selection and then tap 'Just once', the next time you tap the Home key you will get the choice again. This will make it convenient for testing... IF it continuse through ALL Launcher versions.

Alllllrighty now... We started at the bottom with number 3, the SMART Launcher. It is interesting and we like it already. -AND- we still get the choices upon tapping the 'Home' key. This is starting to look like fun. Think we are gona have to make individual sections for each... cause there is going to be a lot to say, or discuss.

 1.) NOVA Launcher   Developer's comments: "Highly customizable, performance driven, home screen replacement for  Android 4.0+  Accept no substitutes! Nova Launcher is the original and most polished customizable launcher for  Android 4 ."
In some of our previous dealings with these Custom ROM's, we had chosen this Launcher because of the reviews. For the short time we used it, we liked it. So, we are going to install it on our new CM11. Refer: Nova Launcher for all the details.

 PA Gapps  Well, hold on here. Before we tried to install NOVA we intalled PA Gapps and it removed Launcher3 and installed Launcher. -AND- Trebuchet stopped failing. Possibly a Launcher conflict??

 2.) GO Launcher  Ok, we found another. This one looks really interesting and we liked all the "Eye Candy". Don't know what it is gona do to our Battery -but- we really like the way it looks -and- appears to perform. Of course, this is only from viewing it on the PlayStore. Still have to install it and see.
Refer: GO Launcher for all the details.

 3.) SMART Launcher  And yet another. Smart Launcher is an innovative launcher, minimalist design, low resource and user-friendly interface which allows you to launch any application in a few keys. It's currently the only launcher of Play Store, which has a function of automatic sorting and cataloging of installed applications!
Refer: SMART Launcher for all the details.

Well now, in searching the Web for Launcher information, we found:
        10 Best Android Launchers For Spicing Up Your Home Screen
and the Launchers we have picked were the top 3 in his list!! With NOVA being number 1, GO being number 2 and SMART number 3.

 4.) Next 3D Launcher   Over time things, and our mind/likes/desires, change. That is what happened here. This Launcher has made our phone seem like a new one!! It is one of the first things installed on all of our New Builds. Even though this one is listed as number four it is number 1 in our minds.
Refer: Next 3D Launcher

Comments ...

Now then, here we are at the number one, and it is the last ot the three that we are testing. Primarily cause we have used this one before - and we wanted to see the improvements, or enhancements as we moved up the list. -But- upon first use this time... we are a little disappointed. Doesn't seem to have the 'pizzazz' of the other two... and we believe that is cause... it looks like what we have been using!! Believe that this one and the default are a lot alike... at least in appearance.

It does have Widgets -and- they are free. So we get our clock! Annnnddd it is velly intelesting. The cloud animation at "UnLock" - that we enable, will show up in the other two -even though- they claim to NOT have, or support, Widgets!! ??

Well, well... strange things happen when you read the docs!! The default install has 5 screens -and- 3 dock pages that can have 7 icons on each page. -BUT- I do believe that depends on what phone you are using. The 'Home' page of our dock has 5 icons on it -and- there is no more room for more... unless it makes them smaller. And it doesn't. Tried to add another and it said, "No more room on this Home screen." Think it should have said 'Dock' page -but- we save memory by using the same messages IF possible.

 Screen selection  Swipe from side to side for 5 screens. By default the middle one is the home screen and IF you are already on the home screen it will show the 5 screens in minature for a pick... just like the 'Stock ICS' for the ReZound.

 Prime Version $4.00   NovaLauncherPrime

Key Features

• Fully customizable home screen and app drawer grids
• Reverse wallpaper scrolling for stronger parallax effect
• App drawer transparency control option
• Varied scroll speeds
• Widget overlapping for effective resizing and placement
• Gesture support for different launcher actions (Prime only)
• Unread message and miss call count badge (Prime only)
• Ability to add multiple app shortcuts in one go

Comments ...

Well, we just 'left' SMART Launcher and the very first pass at this one shows us 'SMART Launchers' claim to fame. Minimalism and ease of use... which, in our first encounter, this one is NOT. The '10 Best' guy claims otherwise -but- we'll have to use it some more to get a better opinion. I believe it all depends on your familiarity with phone operations.
My, my look what I found... Instructions!!

Ok now. We are making a little headway. There were four bars of advertisement for some of their other apps and they were throwing confusion my way. Couldn't understand ... till I understood. Promptly removed them and things got a little clearer. However, the screens they showed and the screens that we saw on our phone did not agree. Primarily cause it looks like the phone they are using is a Samsung and we have an HTC ReZound. However, there is an FAQ that helps.

 Screen selection  

Themes.. A phone theme or phone skin refers to the general look and feel of a mobile phone's user interface (UI). It includes color schemes for menus and highlights, background images and, for Series 60 (S60) themes, user and folder icons. A theme package contains graphics for one or many changeable components of a mobile phone's UI. Changing a theme only affects the look and feel of the UI and not the entire phone's functions or features. Borrowed/Stolen From: WiKi
They say ya gota install from the GO Launcher themes in electronic markets -but- we just selected "Menu and themes" and there were some there already. However, you can also go to GO Launcher Themes and pick from some more.

Well, there are pros and cons. It looks nice but to get some of the 'better' features it will cost you. To which I say ... SO??? Excellent work should be paid for. Everybody wants all this Hi-Tech stuff for free. I mean the developers are giving it away with a few ads. You don't want the ads, then pay the one time cost. The only other way out of the cost is to program it yourself. I personally have worked in the Hi-Tech industry for a number of years -and- I have paid some very high prices for some of the equipment I used. Most will pay 2 or 3 hundred dollars for a phone, but them balk if they are asked to pay 5 or 6 dollars for software that will make it worth the hundreds of dollars they paid originally. Just puzzling.

Ok, after all of that am I gona keep this Launcher??? The jury is still out on that. I personally believe that SMART Launcher is easier to start with -but- GO Launcher will offer more features. Which to use will depend on what kind of phone junky you are. For me??? Right now, for usage I'm leaning towards SMART Launcher. But I'm also wanting the Widgets...

Speaking of which, we were able to add the "Fancy Widgets" Weather/Clock to our main home screen.

 Prime Version $5.99  GO Launcher Prime is NOT a stand-alone app! It is a license key to unlock Prime features in GO Launcher EX. No sponsored messages or Ads
GoLauncherPrime

Key Features

• Support for over 10,000 themes and 25 home screen scrolling effects
• Multi-touch to instantly access core functions (Pro only)
• Over 15 free default widgets for weather, calendar, clock etc.)
• Loads of customization options
• Super smooth and fast
• Frequent updates

Comments ...

Even though this one was 'last' in the list, we are making it first in our testing. Already had 'some' experience with NOVA back in CM10.1 or 2. So we'll start at the so called bottom and move 'up' to see IF there are any improvements.

Well now, at first look, it doesn't have a weather clock. IF you read other portions of our stuff you would know that the 'Clock' is one of the things that we 'must' have. After all, it was one of the main things that attracted us to this phone in the first place. This Launcher doesn't allow you to use Android widgets unless you shell out for the Pro version. That's bad cause... we won't be able to install the 'Fancy Widgets' which got us closest to the HTC clock of anything we tried.

On the bright side, Smart Launcher boasts a beautiful interface and a clean looking app drawer that automatically categorizes your apps under different groups. This was very interesting... a very interesting way of handling the apps. It also has a 'Plus app' that presents 'other' applications that you can install. This is a dim square with a plus in it. One is presented with each category. Almost enough to get us to switch -but- first we'll check out the others.

 Screen selection  

 Pro Version $3.99  We get Widget support in Pro. -But- it is on a secondary screen. SmartLauncherPro. We bought it. Wanted our 'Clock'. Only problem is... the area allowed for it is to small. We can get Big Numbers 'only if' we do not include the 'Weather' portion. IF we include the 'Weather' the 'Clock' portion is almost half in size!! But it may be a blessing in disguize. Think the Weather/Location may have been part of our battery drain.

However, the 'Lock Screen' shows the time -and- weather. Go figure. Well, I just read on their home site that the Lock Screen is Customizable. We'll have to look into that. ... Did. Another money grabbing thing. All it is, is some Wallpapers that you pay for!!

Key Features

• Gorgeous, minimalistic interface
• One home screen that comprises of uniform icon shortcuts
• App drawer is organized into categories called Communication, Internet, Media, Utility and Settings
• Support for icon packs from mainstream launchers
• A separate home screen for Widgets (Pro only)
• Variety of themes and wallpapers

Comments ...

Started using this Launcher a lot sooner than the above date implies but, just forgot to put it here in the list. That's my trouble forgetting.

Next Launcher 3D Shell-- Best 3D Launcher Ever. + Brand new UI3.0 Released!
Next Launcher 3D Shell shows you how 3D dynamic effects and highly customizable Android home screen replacement app could redefine your Android device. Time to get rid of the flat traditional launcher and embrace REAL 3D Launcher!

Works great with my 2 year old+ HTC ReZound As it says in the title, we are enjoying our 2+ year old ReZound. Have been 'offered' a chance to 'UpGrade' -but- turned it down. Can't see that the newer phones offer anything to pull us in. This is still a fabulous phone!! Now that the "ReZound Development Team" has produced "Jelly Bean" -and- "KitKat" for our ReZounds, they are even better. -And- best of all lately... we found this app and it presents a whole new exciting atmosphere on our phone. It makes it like new again. Thanks to both the ReZound Developers -and- the Developers of this app. To us... it is worth the price!! It has helped to revived our phone!!

Key Features

• Extremely fancy 3D effect with buttery smooth experience
• Real 3D Home Screen Transition Effects (Crystal, Cloth, Folding and more coming soon)
• Stunning 3D screen preview with dazzling animation of screen switching
• Build unique icon style by changing its size, angle, style and label (Icon Editor)
• Combine all good parts from different themes into a single theme you really love (Theme Mix Mode)
• Efficient and powerful batch apps management with gestures
• Up to 8 different gestures available in home screen and app drawer
• See how cool your phone could be by blowing all the icons and the widgets to air space (Floating Mode)
• Enhanced shining border effects for home screen transition
• Up to 7 rows on dock to shortcut all your favorites
• Keep releasing 3D Next widgets, 3D themes and live wallpapers special designed by GO Launcher Dev Team

 Next 3D Prime $16.99  

Comments...

Info from the Google Android Page: Battery Monitoring

 January 16th, 2015 / 9:27am  Now then, we have discussed -and- many have complained about the Battery consumption on this phone. To be honest, it depends. Some of the builds have been better than others. Right now I wish that I had paid more attention on which ones. But for the most part I have NOT had that much of a problem. I seem to be experiencing trouble now-a-days -BUT- my battery is 3 years old!!

 From hochoch on XDA  In response to a battery complaint:
I'd check to make sure you're running the most recent google play services. I had wicked battery drain last week that seems to have been fixed with the most recent updates. You can find them here (rezound is 320 dpi i believe): http://www.xda-developers.com/androi...play-services/
Actually the Rez is 342 DPI but the next one up is 480, so the 320 should work.

Forgot to say that I have the Extended Battery installed. It is, like me, old. Purchased shortly after I got the phone. However, I did not install it right away. In fact, it wasn't installed until a couple of months later. Probably June or July of 2012. So, the Extended Battery in my phone is over 2 years old. These tests are bein made with this battery. Just a side note; when at home my phone is plugged into AC almost all the time. Course it isn't when I'm testing battery life...

A Test: (cm-11-20140701-UNOFFICIAL-vigor.zip)

• 1:43am 100% charge - on Batt
  Bluetooth off, WiFi off, Data off
• 8:09am -- 70% -- forgot to turn off GPS!! -But- otherwise it was just idle.
  6hrs 26min... Back on charger!!
• 11:00am 100% charge - on Batt
  Bluetooth off, WiFi off, Data off... and GPS off!   Idle time, just sitting there.
• 3:15pm -- 81% -- idle time.
• 3:17pm -- 80% -- used 1% showing a couple of pics. Back on idle.
• 5:23pm -- 70% --
  6hrs 23min... relatively no diff with GPS off.

A Test: (cm-11-20140704-UNOFFICIAL-vigor.zip)

• 6:14am 100% charge - on Batt
  Bluetooth on, WiFi on, Data on... and GPS on!
  And combo of idle and use.
• 8:41pm -- 50% -- one phone call -- in airplane mode for 2hrs.
  14hrs 27min...
• 8:42pm -- back on charger.

A Test: (cm-11-20140704-UNOFFICIAL-vigor.zip)

• 1:15pm 100% charge -- on Batt
  Bluetooth on, WiFi on, Data on... and GPS on!
  Have Hangouts going with a mesg to Neo.
  Expanded the mesg to anyone that knows.
• 3:20pm -- 86% -- had a couple of phone calls.
• 8:15am -- 57% -- This is the next morning.
  14hrs 55min...
• 8:16am -- back on charger
• 9:54am -- back up to 93%
  on service call. All still on.
• 6:44pm -- 71% -- mostly idle. 8hrs 50min... Back on charger.

 Wednesday July 9th, 2014/7:05am   Now then, yesterday and last night, we built this ROM twice. The first time had problems and one of them was the touch screen... it didn't! When an app was touched in the app drawer... nothing happend. This second build was/is more successful. We are gona do another Battery test but first we need to get Xposed installed. We want the Battery test to be true and from 100%. When the phone is connected to our 'Puter it is getting a charge. So once Xposed is installed we can disconnect and start our testing.

A Test: (cm-11-20140709-UNOFFICIAL-vigor.zip)

• 7:46am 100% Charge -- on Batt
• First we setup the Bluetooth: 7:51am Paired and connected.
• 7:52am -- Netflix test -- watched movie for 6 min.
• 7:59am -- 96% -- Turning on Music and going cross street to test Mobile data.
• 8:13am -- 95% -- Turned off music. Mobile data test a success.
• 10:47am -- 83% -- Just went to McDonalds. Used WiFi and Mobile data there. The default Browser would NOT connect with the WiFi -but- would connect with Mobile Data. Firefox connected with both.
  went to the Bank and while traveling there (wife driving) enabled maps and it showed us at the Bank.
• 11:07am -- 80% -- Took some still pics of mushrooms in our backyard... in Phoenix, AZ!! Dry heat?? It's Monsoon season and I had been over watering to get grass for the 4th picnic.
• 12:30pm -- 70% -- idle from pic time till now.
• 12:52pm -- 66% -- Made a voice call thru Bluetooth. Naturally, I had to Tap the button on my Bluetooth first. Then the Voice Caller asked for a command.
• 1:00pm -- 65% -- Sent a Text mesg.
• 1:03pm -- 64% -- Looked at map and it showed me at home. Messed with it a little to get larger view.
• Since about 10:30am had Hangouts going and have recieved a few. None sent. And all this time we have had WiFi, Mobile Data, Bluetooth, and location enabled. There were a few times that one of them was off to test the others. But most of the time all have been on.
• 1:10pm -- 63% -- After all of the above.
• 1:19pm -- 60% -- Was just looking at PlayStore and my apps. Checking GooManager and ROM Installer.
  Going idle -- well let screen go off and it just sit there... doing nothing -but- all services still on.
• 2:00pm -- 55% -- Doing nothing, just looked at Battery Doc to see percent.
• 7:03Pm -- 21% -- and we have essentially done nothing with the phone in these past hours.
  11hrs 21min -- back on charger

 Thursday July 10th, 2014/3:55am  I was gona do another test with a lot of stuff turned off. But I have decided not to do it. Instead I am going to work on more important stuff. Batteries can be, and are a problem in all of these Smartphones. It depends a lot on how you use them. IF you have everything it does going, then your battery life is going to be low. However, IF you turn some things that you don't use often Off, it will last a lot longer. I had everything going in my above test and I got almost 12 hours of use with power left. Granted it was not a heavy use, but then, niether was the use of some of the complainers.

 August 30th, 2014 Snuzzo Can give you some input on what it could be...

The panel in the phone at the time was the best you could get DPI wise. Claiming to be better than the iPhones retina display. Now with this in conjunction with mixing adreno 205, its destined to pull some extra battery.

 September 8th, 2014/2:56am  OK, due to the number of complaints and sorrowful stories, I did one last series of battery tests -using my 2 year 8 month old Extended Battery-. Please view the test on our XDA Form at message: 2429 Phone and Battery specs are in the message signature at the bottom of the message.

Comments ... Refer: App Ops and Batt Life and Six Things to Know

Started with this:   xdadevelopers   and proceeded to this:
          [Guide] How to get Viper4Android working on 4.3.1+ Roms

Comments ...

The following was copied from a forum at:   xdadevelopers  . The app will work on any  Android  device which meets the requirements listed below.

• Change CPU Governor, I/O Scheduler and Clock Speed
• Battery information + Fast Charge setting + Battery Life eXtender setting
• Change Voltages Assigned to each CPU frequency
• Customize MinFree Task Killer (set the amount of RAM the minfree taskiller will keep), Not Killable Processes feature
• Customize SD read-ahead
• VM Settings such as: Dirty Ratio, Dirty Backgroud ratio, Dirty expire centisecs, Dirty writeback centrisecs, Minfree kbytes, Overcommit ratio, Swappiness and VFS Cache pressure, Dynamic Fsync, Backlight timeout, Backlight on touchscreen, Phantom Key Presses Filter
• Integrated CPU Spy
• Linux Kernel informations, CPU Informations, Memory Informations
• Disk Informations
• Tools: Custom shell command, Wipe cache+dalvik cache, Flash kernel or recovery (img files), Clean residual files, Optimize DBs

• Root
• Busybox
• CM or other AOSP like ROM based on 4.0+ (tested only on 4.2.2.& 4.3)

Changelog:
    Can be found at:   xdadevelopers  

Comments ...

Guide to Android Camera

Comments...

1. Q. Does the kernel for this rom support fast charge?
   A. Yeup.
   Credit: Bunchies
   
2. Q. Multiple Repeats of Contacts - How Do I Delete the Duplicates?
   A. Go to your Google account on a computer and delete all your duplicates on there. Then on your phone re-sync and all the duplicates will be gone.
   Credit: Rick James Remove Dupes
   
3. Q. How can I fix the dialer? No response when I touch the numbers or hang up bar.
   A. Rezound Prox Sensor Calibrator   Chad's Rezound proximity sensor app is your friend.
   
4. Q. When I make a call my screen goes blank after a minute and I can't hang up.
   A. See Prox Sensor above. Also see: Prox Settings
   
5. Q. It seems that normal camera pics come out more red than what would seem natural.
   A. The redness comes from bad white balance detection. CM is terrible with it and HTC was too until they had finally fixed it at some point in their builds (and then I believe broke it again shortly afterwards). Chances are manually setting white balance to incandescent will fix it.
   
6. Q. Where would one find the manual setting for this white balance?
   A. For the CM camera: Choose the middle option for more settings, and then it's the light bulb option to the right of picture size. Incandescent is the left-most option.
   Need images here...
   Credit: Hobox10
   
7. Q. The Reson for the SD card Problem
   A. March 23rd, 2014/9:09am - The SD Card What brings this up is the Camera operations and the fact that Google made some drastic changes in SD Card operations. There are, naturally, fixes so's we can get back our NORMAL ops. What are we talking about?? Google has blocked 'third' party apps from writing to the SD Card. When using the Camera in one of our KitKat creations we wanted, and looked for, the ability to save the pics on our SD Card. Could NOT do it. So, we looked for, and found, a fix at: SDfix. Information on Google changes is at: SDcard Changes
   Another from: Bunchies
   
8. Q. What is MAX size for SD card??
   A. SanDisk 128GB with their special tool.
   
9. Q. How do you backup apps with google so they automatically install?
   A. Using Google backup.
   • Go into the settings
   • Scroll down to the Accounts
   • Tap on Google
   • Tap on your gmain address, that should be listed.
   • Three items will be listed:
   1. App Data................x
   2. Contacts................x
   3. People details.........x
   • All three should be checked...-OR- have sync circles by them. Tap the menu item in upper right corner and then tap on sync now. They will then get placed on your Google account.
   • Tap the ret key the proper number of times to exit.
   Now then, technically this is done automatically IF you selected the Google restore when you Flashed the ROM. AFTER Flashing you must sign on for the first time. During that first sign on, you are asked for your Gmail address. AFTER entering that it will say that it is signing on and gathering info -- or some such thing. However, one of the screens presented contains for Google items to check -or- uncheck. The first, or top one, is the Google Restore. All of the four items are checked by default. I leave them that way EXCEPT for the last one. Now when I get signed on ... I will see all my apps, and my contacts, getting restored. You will to IF you have left the first 2 items checked -and- you sync'd your phone. It doesn't save the "normal" apps -- only the ones you have installed. They will not be restored to any of your screens but will be restored to your app drawer. It will sync automagically -but- before you Flash another ROM use the above procedure to make sure that all of the ones you have installed have been sync'd.
   
10. Q.
    A.
    
11. Q.
    A.
    
12. Q.
    A.
    
13. Q.
    A.
    

Comments...

Comments ...