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

Search This thread

sino8r

Senior Member
Sep 7, 2006
3,551
735
Birmingham, Alabama
First problem I've noticed: when using the dialer with the keyboard open the numbers are wrong. if you press 1234567890 you get 7937898467. If you press the alt button before each number, as in ALT 1, ALT 2, ALT 3, ... then you will get 1234567890. Double pressing the ALT button, as you normally would to lock the keyboard to the ALT options for each keypress does not work and gives you 1937898467.

Eeeek! You gave me a headache with that one... numbers make me angry:) weird bug though..

About the alarm clock, maybe it has to do with am/pm being added on? Has anyone tried pushing back the clock.apk from last nights build or trying a 3rd party alarm like klaxxon to see if it works? Its late but those are my guesses right now...
 

yogi2010

Senior Member
Dec 22, 2010
2,130
320
Los Angeles, CA
Eeeek! You gave me a headache with that one... numbers make me angry:) weird bug though..

About the alarm clock, maybe it has to do with am/pm being added on? Has anyone tried pushing back the clock.apk from last nights build or trying a 3rd party alarm like klaxxon to see if it works? Its late but those are my guesses right now...

strange, I do not have the am/pm back in my status bar.... I guess that has to do with using the darkginger theme(I didn't wipe when flashing build 79)? and curiously, I am not having the alarm clock bug, mine is working fine.
 

philosophics

Senior Member
Can't confirm dialer issue but can confirm that the clock force closes everytime I try to turn on, edit or add an alarm. Something that is very important for the morning. I have to open my shop tomorrow.
Pretty sure I'm going back 78 until 80 is released...

Sent from me CM7 Nightly HTC Vision using XDA App that needs to show signatures
 

userfriendlyme

Senior Member
Eeeek! You gave me a headache with that one... numbers make me angry:) weird bug though..

About the alarm clock, maybe it has to do with am/pm being added on? Has anyone tried pushing back the clock.apk from last nights build or trying a 3rd party alarm like klaxxon to see if it works? Its late but those are my guesses right now...

Klaxxon is working fine. Stock app also force closes for me when trying to change or add a new alarm. Dialer with the keyboard open is also still and issue for me on #79.



Sent from my CM7 powered G2
 

philosophics

Senior Member
I'm stickin with 79 and here's why,
I solved the issue by installin alarm clock plus and actually, I feel better with this alarm clock cause I sometimes hit the dismiss button instead of snooze.
With alarm clock plus, it makes me do a math problem to dismiss and as anyone knows, doing math when waking up is pretty much impossible...

Sent from me CM7 Nightly HTC Vision using XDA App that needs to show signatures
 

J-Hop2o6

Senior Member
Aug 24, 2009
2,870
269
Seattle, WA
First problem I've noticed: when using the dialer with the keyboard open the numbers are wrong. if you press 1234567890 you get 7937898467. If you press the alt button before each number, as in ALT 1, ALT 2, ALT 3, ... then you will get 1234567890. Double pressing the ALT button, as you normally would to lock the keyboard to the ALT options for each keypress does not work and gives you 1937898467.

Same here

10char

Sent from my HTC Vision using XDA App
 

boogie1077

Senior Member
Jan 29, 2008
67
2
Chicago, IL
First problem I've noticed: when using the dialer with the keyboard open the numbers are wrong. if you press 1234567890 you get 7937898467. If you press the alt button before each number, as in ALT 1, ALT 2, ALT 3, ... then you will get 1234567890. Double pressing the ALT button, as you normally would to lock the keyboard to the ALT options for each keypress does not work and gives you 1937898467.

[/QUOTE]

I'm pretty sure that's not an issue but a feature. The numbers correspond to the letters on a regular touch tone phone. 1-800-Cyanogen = 1-800-292-66436 (I know there's an extra digit, its for demonstration purposes only)

Its also pressent in #78 and I bet its always been like that.
 
Last edited:

G1ForFun

Retired Forum Moderator
Feb 1, 2010
2,975
294
The numbers have always behaved like that in landscape mode...that's nothing new.

And if your home button doesn't work....the first thing you should do is wipe and reflash.

Sent from my HTC Vision using XDA App
 

izanagi

Senior Member
May 1, 2008
99
5
fyi, I flashed #79 this morning from #68 (no wipe) and my google account settings are gone, with no way to re-add thus I cannot access gmail or any other sync features...

wiping.
 

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.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone