[ROM][NIGHTLY] CyanogenMod 7 for vendor Vision (HTC Vision)

Search This thread

fermunky

Senior Member
Jun 11, 2007
1,163
59
Tampa, FL
Man, just came back to these roms after torturing myself with various ICS roms. Nice to have a snappy phone again, AND a working ".com" button!

Quick question since I am certainly not going to find it within the 12,325 posts prior to mine... I think I remember previuously being able to simply flash the new nightly over top of my current one, that still accurate?
 
Last edited:

tun4f1sh

Senior Member
Dec 27, 2010
662
699
Thanks for replying.

I've been doing the factory reset, cache partition wipe and dalvik wipe before every flash. I've just flashed once again without restoring any mybackup pro settings and the home button still doesn't do much. If I click on the clock, the home button closes it and takes me to the homescreen but any other app and the home button does nothing. Also a long press of the home button doesn't take me to recent apps. A bit strange.

Flash this:

http://db.tt/xoO4fHpM

It will properly format all your partitions for a fresh install of a new ROM. (Superwipe)

then flash the CM nightly followed by gapps. As soon as the phone boots and you gwy through the setup prompts, test your home button. CM should work fine with your phone.

Sent from my HTC Vision using xda premium
 
  • Like
Reactions: Chem23

tun4f1sh

Senior Member
Dec 27, 2010
662
699
Man, just came back to these roms after torturing myself with various ICS roms. Nice to have a snappy phone again, AND a working ".com" button!

Quick question since I am certainly not going to find it within the 12,325 posts prior to mine... I think I remember previuously being able to simply flash the new nightly over top of my current one, that still accurate?

Correct

Sent from my HTC Vision using xda premium
 

Chem23

Senior Member
Apr 30, 2011
74
7
Flash this:

http://db.tt/xoO4fHpM

It will properly format all your partitions for a fresh install of a new ROM. (Superwipe)

then flash the CM nightly followed by gapps. As soon as the phone boots and you gwy through the setup prompts, test your home button. CM should work fine with your phone.

Sent from my HTC Vision using xda premium

I'd love to be able to test this but I've now got meXdroidMod installed, spent a few hours configuring it to my liking and it's running wonderfully well. I will, however, use Superwipe next time I experiement with CM7. Thank you :)
 

fermunky

Senior Member
Jun 11, 2007
1,163
59
Tampa, FL
Flash this:

http://db.tt/xoO4fHpM

It will properly format all your partitions for a fresh install of a new ROM. (Superwipe)

then flash the CM nightly followed by gapps. As soon as the phone boots and you gwy through the setup prompts, test your home button. CM should work fine with your phone.

Sent from my HTC Vision using xda premium

Interesting. I had a Q&A thread about going from ICS back to GB and someone mentioned formatting my partitions to ext4. Since I onyl really root my devices to do wifi hotspots, I did not remember doing anything special to get my partitions to ext4. However, mine were already. Is that because I have always used Superwipe when wanting to clear out my phone?
 

gee one

Senior Member
Jul 29, 2010
1,979
865
linux command line
Ok, I think the kangs should be back on the usual schedule. I had some weirdness with repo that would cause the sync to hang forever. I saw there was a new version of repo available and all seems well after upgrading. We'll find out tonight. Of course, I'm travelling again this weekend, but I set up ssh before I left. If I read the commit properly, there should be a new version of busybox installed tonight.

A bit off topic, but I used to have an overnight virus scan run and my computer would email me the results. Every once in a while, the email command would get messed up and it would send the same email over and over and over... Of course, this happened one weekend when I was away, and I woke up with over 400 emails and it was still sending! I had ssh set up, so I was able to log in and stop the emails. I thought my isp was going to shut me down for spamming. I've since added a counter to the script to stop it if it starts to get out of hand.

sent from my transformer
 
  • Like
Reactions: sisterchick

gee one

Senior Member
Jul 29, 2010
1,979
865
linux command line
Forgive my ignorance, but the kangs released on the same day that the "official" nightlies come out are generally the same thing, right?
They should be. My script will repo sync at 12.01 central time, so any changes before that should be included. That being said, I'm a bit surprised to see RC3 is out, while the gingerbread source is still on RC1?? I think these are set with flags, so perhaps they are set manually for the RCs. I didn't see any updates to bump the RC version in the changelog/gerrit review.

Thank pfak for the server space. Every thing on my end is completely automatic as long as my computer is on and the internet is working. ;)
 

gee one

Senior Member
Jul 29, 2010
1,979
865
linux command line
They should be. My script will repo sync at 12.01 central time, so any changes before that should be included. That being said, I'm a bit surprised to see RC3 is out, while the gingerbread source is still on RC1?? I think these are set with flags, so perhaps they are set manually for the RCs. I didn't see any updates to bump the RC version in the changelog/gerrit review.

Thank pfak for the server space. Every thing on my end is completely automatic as long as my computer is on and the internet is working. ;)
This is quite curious... there seem to be three gingerbread branchs... gingerbread, gingerbread-release, and gb-release-7.2. The bump to RC3 is in the gb-release-7.2 branch. The change shows up in github, but not in the gerrit review.

I'm building the gingerbread branch, which seems to have most of the changes, but not the bump to RC3. Holler if anyone has any insight on what the different branches are for.

EDIT: and what's the deal with get.cm - I tried a few downloads and they were all empty files??? maybe I should see what's shaking on google+ :smart:
 
Last edited:

gee one

Senior Member
Jul 29, 2010
1,979
865
linux command line
The latest nightly didn't upload. I'm correcting that now. It should be uploaded in an hour. It takes about 15 mins to build and 40 mins to upload. I guess my cpu is faster than my internet connection.

It seems like the output zip file changed names, which confused the script I use. It didn't find the file it was expecting so it skipped the upload. Everything else completed, inluding the clobber!
 
  • Like
Reactions: .A.J.

fermunky

Senior Member
Jun 11, 2007
1,163
59
Tampa, FL
Hmm, not sure if anyone else tried the rebuild or 467, but when I tried to flash the 467, mine hung at the HTC boot image. Restored without issue, but I may have to wait for a post 467 build.
 

gee one

Senior Member
Jul 29, 2010
1,979
865
linux command line
I'm trying something new tonight. I'm using the new "UNOFFICIAL" naming convention that has been committed recently. The file names will change to cm-7-<build-date>-UNOFFICIAL-vision.zip, which is the file name that the build generates. I believe the build dates are based on UTC. I will also upload the md5 hash which the build spits out. I'll load the zip file first and the hash second, so when you see the hash, the zip file is already completed.

http://r.cyanogenmod.com/#/c/17347/

Also, it appears that the official cm7 is being built weekly and the downloads are working. The next build *might* be this Sunday, so we'll see what happens. I'll give it a few weeks to make sure things are actually going.
 

gee one

Senior Member
Jul 29, 2010
1,979
865
linux command line
Not sure if it is the same thing when installed, but I just flashed the nightly from June 10 and in About Phone, the build date says "Sun Jun 10 04:51:12 PDT 2012"

There are two dates in the about phone, the build date for the rom, and the date in the kernel build. The build date in the rom is in the /system/build.prop.

The official nightly from get.cm has the build date that you posted. In terminal, type "grep ro.build.date /system/build.prop" and you will see the actual build date. I'm not sure where the CM build farm is located, but they seem to have PDT as their local time zone.

Here's the jenkins output http://jenkins.cyanogenmod.com/view/All/job/android/2624/

Note the build time is xx:49:06, so the rom started building 2 mins later.

---------- Post added at 07:16 PM ---------- Previous post was at 07:06 PM ----------

It looks like the cm-7 weeklies are running. If all goes well with the official cm-7, I'll probably stop building after the 6/24 build. The changes are trickling in and I suspect 7.2 stable is around the corner.

I should throw out a free ad for Audacity by the Andromadus team. It's pretty smooth and great for a daily driver. They are merging a lot of the cm-9 commits, so it feels a lot like cm ics. They are also using parts of the linaro kernel to speed things up.
 
Last edited:

robuser007

Senior Member
Jan 7, 2010
1,245
95
But ICS has the wifi to data issue (after 2hours or more) for european users.
If you ignore that bug both andromadus or aokp is great (both are faster then cm7).

There are two dates in the about phone, the build date for the rom, and the date in the kernel build. The build date in the rom is in the /system/build.prop.

The official nightly from get.cm has the build date that you posted. In terminal, type "grep ro.build.date /system/build.prop" and you will see the actual build date. I'm not sure where the CM build farm is located, but they seem to have PDT as their local time zone.

Here's the jenkins output http://jenkins.cyanogenmod.com/view/All/job/android/2624/

Note the build time is xx:49:06, so the rom started building 2 mins later.

---------- Post added at 07:16 PM ---------- Previous post was at 07:06 PM ----------

It looks like the cm-7 weeklies are running. If all goes well with the official cm-7, I'll probably stop building after the 6/24 build. The changes are trickling in and I suspect 7.2 stable is around the corner.

I should throw out a free ad for Audacity by the Andromadus team. It's pretty smooth and great for a daily driver. They are merging a lot of the cm-9 commits, so it feels a lot like cm ics. They are also using parts of the linaro kernel to speed things up.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 29
    Have a question or an issue? Try this before asking something silly:
    searchi.jpg


    This thread is reserve for nightly build of @Cyanogen Mod Rom for HTC Vision
    You can report and discuss all issue you are having with nightly build here.

    What are Nightly build ? : auto compil build from the CyanogenMod github, each time there are new corrections on it. This version change each night, and aren't support officialy, if you find bugs/issues you can/must discuss here.

    Warning : Not for new user, flash this build only if you know what you are doing !!!

    There are no Google Apps bundled with CM ROMs, because Google asked Cyanogen to remove copyrighted apps from his roms, after flashing rom don't forget to flash Google Addon package if you want it.

    Gfree is needed to flash a Rom onto your phone!!!!
    or
    Perm Root with hboot-eng.....is needed to flash a custom ROM (still REQUIRED for the moment):

    Lastest version:
    Download: http://mirror.teamdouche.net/?device=vision
    MD5Sum: check the md5 under the files named associate with your build version

    Google Addon: 20110828: http://goo-inside.me/google-apps/
    Check the lastest package available on top

    Recovery needed: 3.0+
    vision-cwm3src3.0.0.5-1-16-11.img

    Rename the .img to recovery.img and have it on the root of the sdcard

    For reference-More detailed
    Code:
    su
    flash_image recovery /sdcard/recovery.img
    reboot recovery
    Wanna follow current modifications to builds?? http://r.cyanogenmod.com/#q,status:open,n,z
    11
    Work In Progress F.A.Q.

    Work In Progress F.A.Q.


    No this ROM is NOT an official stable. No support other than community is offered for it so if you cannot live without the features that aren't available, keep the stock ROM. If you ask questions that are covered here then you will be ridiculed relentlessly and admonished, you've been warned.

    An important thing to remember is that this is an ALPHA, and as such has some issues which can't be foreseen, others that are actively being worked, and some that have work arounds.

    If you are asking yourself the following questions, rethink this, learn some more, then come back:
    What is root?
    What is a recovery?
    What is Cyanogenmod?

    What works (besides the obvious stuff):
    Most things
    Wifi
    Bluetooth
    Wifi Calling
    Wifi tether (built-in or third party)

    What doesn't work:
    None at this moment

    Common issues and FAQs:

    • Recovery version issues:
    You MUST use Clockworkmod recovery v3.x. You CANNOT use recovery versions 2.5.x and below as Android 2.2 used ext3 file structure and Android 2.3 uses ext4. If you ask why you can't flash this ROM and you are using Clockwork 2.x, you will be ridiculed relentlessly for not reading thoroughly.

    Clockworkmod is the official recovery supported by Cyanogenmod. However, since this is an alpha release, the current 3.x version of Clockworkmod is a little buggy while it's still in development.

    If you wish to flash back to Android 2.2, you MUST flash Clockworkmod recovery 2.5.x or below (or compatible). If you try to flash a Android 2.2 version ROM with recovery 3.x, it WILL NOT work!!!


    • Wifi Not Working
    Reboot

    • If you are sending or receiving blurry photos:
    Open Messenger->Settings->Custom User Agent->select Default Android

    • Trackpad wake:
    This is currently a hack developed by the CM team while they find a permanent solution. Consequently, it causes some unexpected behavior sometimes. But it mostly works.
    Menu->Settings->CyanogenMod settings->Input settings->select Trackball wake

    • CRT (cathode ray tube) Screen-on/Screen-off animations:
    In progress of being added

    Menu->Settings->CyanogenMod settings->User interface->Screen-on animation/screen-off animation

    • How do I set up ADB/Fastboot?
    See thread here for Windows 7:
    http://forum.xda-developers.com/showthread.php?t=897368

    See thread here for Linux:
    http://forum.xda-developers.com/showthread.php?t=537508

    Generalized Windows info:
    http://forum.xda-developers.com/showthread.php?t=500196

    • How can I compile Cyanogenmod for myself?
    See gridlock32404's post here:
    http://forum.xda-developers.com/showthread.php?t=915435

    • My [insert favorite app name] doesn't work right, what are you going to do about it?
    Probably nothing. If it isn't Cyanogenmod's then they don't offer direct support for it, generally just service level issues that may need code changes. In CM7, it's based off Android 2.3 which some developers haven't offered full support for. Officially there's only one phone running 2.3, the Samsung Nexus S. Some known non-working apps include, but are not limited to:
    Quadrant Standard

    • How do I install boot animations/boot splash/any other add on?
    See other threads in the theme section.

    • What if I'm having random issues such as freezing, stuttering, force closes, or anything else?
    Try these steps before posting a question about any issues to see if any of them fix it:
    1. Reboot
    2. Perform fix permissions, from recovery mode
    3. Do a nandroid backup and then perform a complete data/factory wipe and flash again
    4. Politely ask if anyone has had this issue in the thread

    • Do any overclock (OC) kernels work with this?
    There are a few in this thread. Be warned that the CM team offers no support whatsoever for these kernels, you must ask the dev of that particular kernel about any issues you have.

    • What settings should I use in SetCPU?
    There's really no reason to overclock your phone on a regular basis, so your safe bet is at a minimum:
    Max: 1017, Min: 245, Scaling: ondemand
    Screen-off: Max:768, Min. 245, Scaling: ondemand

    • I can't find my random issue/concern/question in this faq, what do I do now?
    First, try the “search this thread” function at the top of the screen. Then try a quick google search with the device name and a general idea of what's wrong, it will probably point you back at this thread. Then do what any good tinkerer does and play around with different things and read up a little bit. If none of these gives you any results, politely ask the question on the thread and wait patiently for someone to answer who may have the same problem. It is no one's responsibility to support you in any way. After all, you bought the phone and then started screwing with it. The least you can do is be patient and try to solve the problem yourself. Who knows, you might learn something and be able to help someone else out.

    Credits: To the original writer from the Glacier Thread
    11
    There are a couple of new commits with fixes for the T9 dialer (not directed at the question about Chines chars).

    Sent from my Desire Z running CM7.
    I'm syncing the t9 changes and building.... I'll update after it's uploaded.

    ---------- Post added at 08:03 AM ---------- Previous post was at 07:12 AM ----------

    This includes gingerbread commits up to Change I5867f82b: Dialpad: T9 Dialer - Fixes

    The dialer layout is better. It seems as if it stays in portrait mode unless you open the keyboard. It might be my rotation settings?

    http://www.mediafire.com/download.php?5vo5tjm1qzf8yh2
    943433ab544fa7338d7da611122f1725 update-cm-7.2.0-RC0-vision-KANG-signed.zip

    The solstice kang- it took 14 minutes to build and 20 mins to upload!

    Merry Christmas!
    11
    ####
    New Server - http://crash.pfak.org/~gee_one/
    ####

    FYI about the kanged nightlies- pfak offered to host these on his server, which has a faster download speed. The new download page will be http://crash.pfak.org/~gee_one/

    Tonight's nightly (build 331) will be hosted there.

    One restriction is file space, so there will only be a few weeks worth of nightlies and older ones will automatically be deleted. Since these are nightlies, I don't see a strong reason to keep older versions unless the builds start to break.

    Be sure to thank Niksie for offering his server space and check out the other offerings he has on his site. I will miss the download counter- it was nice to see the activity.


    sent from my cyanogen(mod) vision
    9
    CM9 progress update from http://www.cyanogenmod.com/blog/cm9-progress-update

    Good to see MSM7x30 in the list of probable initial devices, that's us ! :)

    Also, 7.2 is still coming.


    We’ve been hard at work on CM9 since Google released Android 4.0 (Ice Cream Sandwich) into the wild last month, and things are slowly starting to come together. Google did a great job with ICS and added some really awesome features which in some cases replace or deprecate functionality that we had in CM7, so we are reevaluating all of our customizations. A number of devices are already up and running with CM9, and the focus is currently on getting as many devices ready as we can. The first devices (besides the Nexus S, which you can already get from Koush’s section on ROM Manager) that we’ll have ready will mostly likely be devices based on OMAP4, MSM8660/7X30, and Exynos. We also have some Tegra2 tablets in the pipeline such as the Galaxy Tab 10.1 and Asus Transformer. Our goal is to provide continued support to all CM7 devices back to the QSD8250 series of devices such as the Nexus One. I don’t want to make any promises at this time, but that is the plan. And sorry Droid1 owners, we’re dropping support for you. Time to upgrade

    There are a number of challenges that we are up against. Google has made some pretty major changes to the Android framework that break compatibility with older proprietary camera and graphics drivers in order to achieve some pretty insane performance, but I am confident that the team will be able to overcome these issues like we have in the past.

    For those of you who like to build CM from source yourself, you probably know that the spin-up time when starting a CM7 build is absurdly long due to the high number of devices in our repository. Koush and Arcee have put together a solution to this problem that adds new devices on-demand to your local repository, saving on both bandwidth and the long startup time. Some other great enhancements are coming too, like a completely overhauled music app, a new file manager, and a new launcher based on stock 4.0.

    If you have a Nexus S, you can check out the code and build for yourself today. More devices are on the way, and I’ll send out these status updates as we make more progress.