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

Search This thread

Chezbel

Senior Member
Jan 16, 2011
1,979
1,664
Taipei
This sounds like the opposite issue that you have, but when I connect my phone to my work computer via USB and enable USB storage, I get a message from Windows 7 that my SD card need to be repaired. I just hit ignore and proceed as normal. I don't seem to have any SD card issues otherwise.

My home computers (Mac and Ubuntu) don't have any issues. On my Mac, the SD card mounts automatically. On Ubuntu, I have to 'mount /dev/sdc1...', I don't use the desktop much so I don't recall how it behaves, but I don't remember having any issues.

Similar for me, Win7 wants to repair the card instead of just viewing it. XP and Ubuntu are happy. Seems like a Win7 issue not a CM7 issue.

Sent from my abucus
 

nooge9

Senior Member
Nov 11, 2010
63
1
I get a FC on com.cyanogenmod.cmparts when going to CM Settings -> Input -> Long-press menu settings
Anyone else? I tried clearing cache & dalvik cache, and fix permission, but it doesn't seem to work.

EDIT: I flashed a KANG a while ago with the long-press menu feature cherry-picked. Since then, I've flashed a nightly (#102?) that didn't have the feature. Now on #112 and I get the FC
 
Last edited:

Fallen Spartan

Moderator Emeritus- Irish Pride, Spartan Legacy
I get a FC on com.cyanogenmod.cmparts when going to CM Settings -> Input -> Long-press menu settings
Anyone else? I tried clearing cache & dalvik cache, and fix permission, but it doesn't seem to work.

EDIT: I flashed a KANG a while ago with the long-press menu feature cherry-picked. Since then, I've flashed a nightly (#102?) that didn't have the feature. Now on #112 and I get the FC

My general rule of thumb is to backup and do a full wipe when swapping between kangs and official nightlies...............and every 4 or 5 nightlies I generally do a full wipe anyhow.

If I notice any errors or anomalies I do a superwipe if full wipe doesn't fix it.
 

DerIdiot

Senior Member
Feb 4, 2011
183
37
Nightly 112

Interesting bug: Flashing with USB plugged in, leaving it plugged in and booting shows battery at 100%, "life bar" at red almost-dead, and reboots don't fix it. Unplugging does though, and plugging it back in afterwards doesn't repeat the issue until I reboot.

Neat!
 

ptesmoke

Senior Member
Sep 23, 2008
2,961
795
Cold Lake
Well the latest pershoot seems to help with battery life as well. Can't wait for the final 7.1.0. Also are the issues with the new gapps still not resolved?


Ps it's a double rainbow! All the way!
View attachment 629121

Sent from my HTC Vision

Got one of my own! uploadfromtaptalk1308594746064.jpg

Sent from my HTC Vision using XDA Premium App
 

DJMartini

Senior Member
Oct 22, 2010
1,242
342
Denver
Maybe someone can help me.

#112 I was recently on and decided to do the SuperG2+ wipe for my GPS. Before I did this I had performed a nand backup (just in case) before wiping.

Issue: I SuperG2+ wiped than, re-flashed #112, re-flashed gapps, re-installed all my apps using Titanium backup...started configuring and now I can't get my screen lock to work. I have it configured in the settings, but when pressing the power button it won't lock. Trying PIN didn't work and attempted pattern and still didn't work. I even used a Power Widget to force the on/off of it to see if it'd work and still no go =( Anyone know how to fix this?

I'm re-flashing now and going to install #113 see if that might fix it.

Also, question if I restore my nand backup is it going to mess up my SuperG2+ flash with restoring the GPS fix I ran?

Thank you
 

schaggo

Senior Member
Jan 16, 2008
2,625
825
Zürich
Is there any way to tell the devs that the direction they were going was cool but isn't anymore...?
Since ever I had the problem of non-working MMS. Starting with build 80-90 something it magically started working and did ever since. Today on 110 or 112 don't exactly know, it stopped working again. I jumped a couple nightlies so I can't pinpoint at which exact nightly it stopped working.
So I'd like to let the devs know that BEFORE was good, now is BAD :D Bug reports are only allowed for RC's but I'm not on an RC, so I'm not allowed to report anyhting...
 

Fallen Spartan

Moderator Emeritus- Irish Pride, Spartan Legacy
schaggo said:
Is there any way to tell the devs that the direction they were going was cool but isn't anymore...?
Since ever I had the problem of non-working MMS. Starting with build 80-90 something it magically started working and did ever since. Today on 110 or 112 don't exactly know, it stopped working again. I jumped a couple nightlies so I can't pinpoint at which exact nightly it stopped working.
So I'd like to let the devs know that BEFORE was good, now is BAD :D Bug reports are only allowed for RC's but I'm not on an RC, so I'm not allowed to report anyhting...

Actually mms works for me fine on latest nightly

...........................
Sent from my DZ using the improved version of Tapatalk, better known as Forum Runner ;)
 

DJMartini

Senior Member
Oct 22, 2010
1,242
342
Denver
Does anyone use the 'power widget' for Toggle Lock Screen and it work?

on #113 now and if I click it off and turn off screen it still pulls lock-screen for me to use =(
 

userfriendlyme

Senior Member
Well not sure what's wrong with my phone but I've updated mostly every nightly and #113 and the one before it I have been unable to install. Just bootloops for me and I have no clue as to why. I can reflash #110 and boot right back up with no problem. Reading the thread I don't see mention of anyone having the same problem with the last nightlys.

Sent from my CM7 powered G2
 

XxFerociouS

Senior Member
Feb 13, 2011
152
6
Riverside
How are people getting over 30+ hours using this rom
I'm on the nightly 112 and I let my phone charge fully , unplugged it and went to sleep
I woke up and it had 50% battery left
Phone has only been on for 10 hours!

I'm using the .30 radio with Umaro Kernal overclocked to 906

Sent from my HTC Vision using XDA App
 

G1ForFun

Retired Forum Moderator
Feb 1, 2010
2,975
294
How are people getting over 30+ hours using this rom
I'm on the nightly 112 and I let my phone charge fully , unplugged it and went to sleep
I woke up and it had 50% battery left
Phone has only been on for 10 hours!

I'm using the .30 radio with Umaro Kernal overclocked to 906

Sent from my HTC Vision using XDA App

Uninstall setcpu or anything like that, dont use profiles.

Instead use the built in stuff with CM which is in Settings/CM Settings/Performance.

I recommend flashing Umaro 1.04 kernel or Eugene's StreamlineV2 kernel.

Both are excellent when not using any setCPU style program. NO wake issues on either one. Great battery on both but StreamlineV2 is the absolute best battery life I have ever gotten. Umaro's performs a little faster but also uses a bit more battery.
 

carquote

Senior Member
Jan 20, 2011
90
9
How are people getting over 30+ hours using this rom
I'm on the nightly 112 and I let my phone charge fully , unplugged it and went to sleep
I woke up and it had 50% battery left
Phone has only been on for 10 hours!

I'm using the .30 radio with Umaro Kernal overclocked to 906

Sent from my HTC Vision using XDA App

Did you wipe battery stats after you flashed the phone with the battery fully charged? I'm not using this ROM but I know it's recommended to do so after flashing a ROM. Also to properly calibrate the battery HTC recommends:

"For the first three charge cycles, fully charge the battery overnight and allow it to fully discharge before recharging. Extensive overcharging may damage a Lithium-ion battery or if it is left on the charger for more than 24 hours. If your battery is at 70-90%, you can charge it back up to 100%, but I would not leave it on the charger for after it reaches 100%.

Lithium-ion batteries operate more poorly at low temperatures. Temperatures below freezing can cause the battery to lose its discharge levels and sputter out more quickly. While these batteries do not suffer from memory effect, they should be fully charged and discharged every 30 uses."

Good luck.
 
Last edited:

xsteven77x

Senior Member
Jul 2, 2010
3,423
768
Pittsburgh
Uninstall setcpu or anything like that, dont use profiles.

Instead use the built in stuff with CM which is in Settings/CM Settings/Performance.

I recommend flashing Umaro 1.04 kernel or Eugene's StreamlineV2 kernel.

Both are excellent when not using any setCPU style program. NO wake issues on either one. Great battery on both but StreamlineV2 is the absolute best battery life I have ever gotten. Umaro's performs a little faster but also uses a bit more battery.

Where is this streamline kernel you speak of?

Sent from my HTC Vision using XDA Premium App
 

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