yashsingh1/xdaforums huggingface dataset:
[Vega Android Development] mad-murdock:
its possible both still got issues with the newly added overclocking. maybe this experience i had might help:

- setting overclocking with cm settings didnt work. frequencies were shown, but selecting them didnt change anything

- running setcpu worked - frequencies now changable

- after running setcpu, setting the frequency in cm settings now magically works

this shows, there still is something wrong with overclocking - or better the userland interface of sysfs and overclocking.

will surely look into this - but give us time - so much changing atm...
[Vega Android Development] harmohn:
That would be awesome fella- missing cyanbread ;)
[Vega Android Development] bob1369:
still big lags compared to corvus5 sorry love the features but cant live with the speed :(
[Vega Android Development] fused#1:
just flashed latest and it turns out I was a bit too flash happy. flashed the remove phone right after flashing the rom.

Now I'm stuck on the startup screen telling me to tap the android.

Running logcat reveals this:

W/SetupWizard( 1245): Ignoring touch event because phone interface was null

How can I reboot into recovery and reflash? I tired "adb reboot recovery" but it just does a normal reboot.

edit: tried killing setupwizard via shell but it just restarts :|
[Vega Android Development] jps1974:
Try "recovery_2 && reboot" in a terminal emulator to reboot into recovery
[Vega Android Development] fused#1:
Phew. Thanks. Was scared to death that I bricked it :)
[Vega Android Development] jps1974:
This thing is hard to brick if not unbrickable, AFAIK :)
[Vega Android Development] Bennji:
I'm in England, boss, I installed flash from the market, tried uninstalling and reinstalling, even downloaded and installed a version that was linked on modaco.

None seem to work, although it works fine on corvus
[Vega Android Development] fused#1:
Encouraging :)
[Vega Android Development] mad-murdock:
here you go:

mirror1: Cyanbread.apk size: 3.6M (3748359 bytes)

mirror2: Cyanbread.apk md5sum: a6963767a063a888536bc470569dcb54

mirror1: Androidian.apk size: 4.0M (4192665 bytes)

mirror2: Androidian.apk md5sum: 6657fa2e31c5a86ec5bdb03ac6e72a65

adding to first post

hmm, in rare cases upgrading doesnt work - wipe + install should fix that then.

can you try a full wipe and then fresh install and test if flash works? do a nandroid so you can jump back to it, if wipe doesnt help.

unbrickable - seriously (: nvflash can always rescue your device. and then there is fastboot and recovery.
[Vega Android Development] harmohn:
Thanks for the themes dude :D
[Vega Android Development] Dyonas:
Second the motion :) Cyanbread ftw!
[Vega Android Development] mad-murdock:
vega didnt build: http://mirror.teamdouche.net/?type=nightly

gotta ask chris, whats wrong. maybe he didnt add vega to the cron job yet.
[Vega Android Development] mingoid:
Does anyone else have a problem in portrait mode where none of the bottom half of the screen responds to touches other than the notification bar?
[Vega Android Development] Zebwen:
the setup wizard relies on Phone.apk to work correctly, your clicking on the android does nothing if this has been removed. To get around this you can disable the setup wizard in build.prop, this is what we did in Corvus5 to get around this issue.

Alternatively you can flash the rom and go through the wizard first then reboot to recovery and remove the phone files.

newbe5
[Vega Android Development] Pontifice:
When i put my vega in stand-by (with the power button) a blue led inside the device is still lit on, it's not the charging led, it's near the camera, you can see it in a dark room.

P.D. some problems (FC's) with apps that opens "maps" seems to be related with CyanogenMod 56, it happens in more devices
[Vega Android Development] mad-murdock:
nightly 60 is up on http://mirror.teamdouche.net/?device=vega

just testing it - but size-wise it looks correct this time

thanks for this note! since i rarely wipe myself, i didnt notice - will update instructions on first post (:

thats odd - tun support is inside the kernel for sure this time. CONFIG_TUN=y is inside /proc/config.gz. please attach a log of logcat, dmesg and openvpn output (if possible by invoking it yourself)
[Vega Android Development] mattykellyuk:
http://cm-nightlies.appspot.com/?device=vega

Haven't seen this mentioned on this forum. Its a changelog for nightlys. Heard about it on the Nexus one nightlys forum.

Just incase anyone has not seen it
[Vega Android Development] mad-murdock:
sure - adding it, too...

igor.tonky from ace nightly thread developed it. i guess we will use that list officially somewhere in the future. its much better than just watching gerrit or cmsrc on twitter
[Vega Android Development] mad-murdock:
nightly #60 running like expected! go ahead, enjoy the first official nightly.

edit: new rom manager offers to install cwm 3.0.2.7 - but seems to fail - says its successful, but rebooting to it i still got 3.0.2.4.

anyone here got it working with rom manager installation?
[Vega Android Development] scanno:
Updated my post with logcat info. Is there a way to get more info from the openvpn client ?
[Vega Android Development] mad-murdock:
*cough* - finally integrated my tablet into my openvpn structure (hadnt signed keys for a long time) and it works flawlessly.

so - its a bug in your setup, not a bug in cm7. i just connected to the wlan of a neighbour, then openvpn'ed in, no errors, can fully access my network... using "openvpn settings" from market as gui

i posted my openvpn config somewhere - *searching*

ah, here you go - my server and client config which worked right now: http://xdaforums.com/showpost.php?p=12427403&postcount=3856

edit: you use the system settings to connect to openvpn? thats probably the reason - since openvpn binary in latest version is included in cm7, try the free openvpn settings from market - no need to toggle any option, just put your key, crt and config to /sdcard/openvpn and done...
[Vega Android Development] mad-murdock:
was able to register for nightly update notifications on settings->cm settings->system - looking forward to see if it works.
[Vega Android Development] scanno:
Hmmm not really a bug in my setup. Using the openvpn settings from the market it worked first time trying... Using the build in openvpn settings included in CM7 does not work.....

But hey it works now... i am happy.
[Vega Android Development] 318vert:
Ive downlaoded the new rom tried to update from old version 3 times, every time it says installing... and after a min or 2 it just re boots and loads up with old rom???
[Vega Android Development] todd69:
Make sure you've got a full charge, I had the same issue :)
[Vega Android Development] brotbuexe:
There is another way. You can skip the wizard by touching all the screen corners clockwise on the first screen.

http://pocketnow.com/how-to/android-quick-tip-how-to-bypass-touch-the-android-to-begin-video
[Vega Android Development] sugar0:
Yes ,me.

The first time i rebooted in recovery it booted up normally but the second time it went fine.

EDIT: the recovery is still the old one even if rom manager says otherwise
[Vega Android Development] nickwarn:
This official nightly is runing smooth. Its just that damn lag on wake up. Its not there every time, but often enough its there. I dont know why but everytime when i wake up my device it looses its sync with google, icons turn white, and lag often appears. I have set wifi policy to never sleep. but still it looses sync. Its been like this on all Vega nightlies and some nightlies for Nexus S for a long time. Would be nice if that could be fixed. Anyhow im super pleased with all the hardwork you devs have put in for the rest of us. Thank you
[Vega Android Development] mad-murdock:
woot woot! veeeeeery usefull easteregg i never knew before (:

99% percent probability: your download is borked! check size and md5sum from first post. to be honest, this is ALWAYS the reason for such wierd thingies happening. the other 1% might be borked sdcard.
[Vega Android Development] scanno:
ROM manager

Hi,

I could alway start backups using ROM manager, but starting with nightly #8 that does not work anymore. If i start a backup of the ROM it boots, quickly shows CWM and then boots again into CM7. If i select reboot into recoveey i get into recoveey and can then backup normally. This happens with 3.0.2.4 and also with 3.0.2.8, with nightly #8 and the last official nightly 60.

Anyone seeing the same ???

Oh well, a full wipe saves the day......
[Vega Android Development] Dyonas:
The phone removal script - is it supposed to leave the Phone and Messaging icons in the launcher drawer? If not then something is amiss because I ran nightly 60, Google apps addon then the phone removal script and they're still showing. If it's normal for them to stay there then..... carry on >_>

Looking in the script I see what it removes. I'll go in with Root Explorer and take them out.
[Vega Android Development] Bennji:
Murdock,

Did a full wipe and fresh install, still doesn't work I'm afraid :-(
[Vega Android Development] mad-murdock:
no idea then - you are the only person complaining about flash - for all the others, it works. if you just did a wipe and fresh install, i got no idea whats wrong.

what exactly isnt working? no flash playback at all with 10.2? or just no movies?
[Vega Android Development] mad-murdock:
it is indeed. even though you got no gsm, you might wanna access your contacts you synced via your phones google account. for that, you need that phone app thingie.
[Vega Android Development] scanno:
mad-murdock can you tell me what you fixed regarding ROM Manager? I see that in the new nightly (61) a fix regarding vega and rom manager is included. What did it fix. The problem i was having with rom manager and CWM or the problem that the revovery image is not installed correctly.
[Vega Android Development] ed.dark:
Cpu scaling seems to die on a reflash to a new nightly. If I install SETCPU, it works again. I can then uninstall setcpu and native scaling works ok....
[Vega Android Development] just_nos:
hey just new here :)

got cm 7 running on my POV mobii

very nice :) works great accept voor playing avi files etc

anyway

cm_vega_full-61.zip is up ? can i update normal ? true rom manager or do i have to flash thru x recovery :)
[Vega Android Development] scanno:
You can update through ROM manager. I did that 1 hour ago. But i have CWM 3.0.2.8, do not know if it works with the previous versions (never tested flashing through rom manager with other versions of the CWM)
[Vega Android Development] kinkade:
same problem on #61

EDIT: sorry forgot to quote ed.dark. i also had to install setcpu to be able to change the governors in cyan settings also weirdly this also allowed me to change which notification widgets i had selected which before would not toggle in settings
[Vega Android Development] jps1974:
Just to share my experience: this didn't work for me this morning... I was on 60 with CWM 3.0.2.8. Recovery came up for a sec, then it booted back into Android, so I rebooted back into recovery and flashed 61 from there. I was then able to "downgrade" recovery to 3.0.2.7 from ROM Manager ;) Out of curiosity tried to flash 61 again from ROM Manager and it got stuck on rebooting (just a black screen with the backlight on), so I turned the device off and back on. It proceeded to boot into recovery and the flash went through.
[Vega Android Development] scanno:
I had the problem that when i wanted to start a backup through rom manager it booted to CWM and rebooted directly back to CM7. After i did a full wipe, flashed #60 again (61 was not out yet :-) ), everything worked again for me. Backup and flashing ROM's.
[Vega Android Development] ed.dark:
Buggered up the vega by rebooting into recovery using rom manager after the update to 61. Device would not turn on or respond to ADB. Had to NV flash back to original then did a clean install (no recent CWM backup!! :-( )
[Vega Android Development] just_nos:
i have CWM 3.0.2.7. installed can i upgrade then ?

or is it saver thru xrecovery :) just install zip right ?

i wil test tonight
[Vega Android Development] Bennji:
Videos on websites run really fast and there is no sound. I can't understand it, when I restore to Corvus all works perfectly?
[Vega Android Development] ASD2003ru:
How add Russian language? Or please add it to night builds. :rolleyes:

I install last build and install gapps, but i no see gmail and etc.

Remove Phone patch no remove phone program. :confused:
[Vega Android Development] ed.dark:
Add a gmail account and wifi access to get gapps.

Phone program remains so you have access to contacts. GSM protocols removed though.
[Vega Android Development] ASD2003ru:
Thxx.

Sent from ViewSonic 10s Pad...
[Vega Android Development] rebeldx:
i have been using the cm7 nightlies for about a month, but had to reflash the original rom n then r8 etc, i have done everything that i did when i 1st installed everything, but this time when i get to rom manager i get an error when i attempt to flash it.

Basically fresh install of rom manager from AM .... notifies me that i need 2 flash the recovery, but when i try to it just comes up with this error message 'an error occurred while flashing your recovery'

it's probably something simple and easy 2 solve, but atm i'm at a loss ...... anybody no what i shud do??

thanx :)
[Vega Android Development] scanno:
Try to flash the latest CWM recovery from http://xdaforums.com/showpost.php?p=13216267&postcount=25. You can download the recovery image from there or choose to download a zip with the recovery image and a windows / mac / linux script to install it on your tablet. It also installs a reboot utility so you can reboot into recovery without using rommanager. But selecting reboot into recovery from rom manager does the same thing.

You asked the same question on the modaco forum, so took some info from there. Try to boot into a working ROM. Flash the recovery from the link i gave you (you have to flash from your pc). This will install CWM and a utility to reboot into recovery. Boot into recovery from this utility and before you flash a new ROM do a complete wipe. Then flash the ROM.
[Vega Android Development] rebeldx:
edit******

so i downloaded rom manager from AM and cannot flash a recovery image so i get the error, n when i boot into recovery from rom manager i get the android next to the triangle image ................... if i use the vega recovery tool from pauls rom, i can access what appears to be an older version of the recovery ....... i used this 2 install the cm_vega_full-61 zip, but again I'm stuck on the CM7 splash screen (7 mins so far n counting)

is it possible that there is no recovery image 4 the vega on the updated rom manager?? i mean it was working fine yesterday before it updated

does anybody have an older version of rom manager apk?? just so i can see if that will work

soz just saw the above post .... will look at that now lol
[Vega Android Development] scanno:
The script will install the recovery tool from Paul ;)

And yes ROM manager does not install the recovery image correctly. So that you see the old recovery is correct.

But please wipe before you flash... i had some troubles with ROM manager after updating to/from nightly 60. After a full wipe my problems were gone. So just to be sure...... wipe ..... ;)
[Vega Android Development] rebeldx:
thank u soooooooo much, that was awesome n worked like a dream
[Vega Android Development] v_ghelani:
Just wanted to say i've installed Nightly 61 and i'm loving it.. Almost everything i've played around with works flawlessly.. The only issue is a little bit of lag here and there.. Well done.. It is now my primary rom.. At what stage does this become Experimental?
[Vega Android Development] ed.dark:
I removed pure calendar widget from my homescreen......> fewer lags
[Vega Android Development] just_nos:
totaly agree :D love it with the new update :D

cant wait on the new update.

i hope they fix 3d soon :) theres no 3d and hardware rendering
[Vega Android Development] mad-murdock:
this is a long one. added warning about rom manager not working yet to first post.

what i fixed is the list of devices you get, when chosing to flash recovery. before that patch you got a looooong list with all supported devices. now you only get 4 devices listed.

i noticed that. cm oc not working, use setcpu once, cm oc working. repeats on reboot. will be sorted out in the future - but since the (xda) free setcpu works, not that important atm.

really? since all the other guys said, flashing doesnt work. cwm version should not matter as long as it is cwm 3.x (might even work with cwm 2.x - not sure if koush changed the command interface from rom manager to cwm)

did you try a full wipe and fresh install yet? since for the rest, it works flawless. so it must be an issue at your side - borked download of flash or of the rom itself? i just tested it (again) on a fresh install, works like it should.

imperfect widgets and live wallpapers are the most common source for slowing down homescreen etc. i found a lot of those making my desire hd lag (which got no other lag issues) when i played around with gingerbread in the beginning.

fix... 3d... ??? it works for me... fluent smooth and fast 3d rendering all over the place. its one of the fastest 3d devices i had so far. even beats my adreno205 based desire hd
[Vega Android Development] DiamondGar:
totally agree too this rom is great now my primary too. only real complaint is some apps not full screen ie touchdown email app.
[Vega Android Development] scanno:
I will try again as soon as there is a new nightly out. I upgraded nightly 60 to 61 this way and it was running the update-script and booting afterwards. So this was with ROM manager 4.x and CWM 3.0.2.8.

But as said before when there is a new nightly out (newer then 61) i will try it again. Perhaps my memory is failing.

What does not work is flashing the recovery image through ROM manager...

EDIT:

I had some problems with ROM Manager making backups. It would boot into recovery and then reboot back to CM7. After a full wipe and a fresh install of nightly 60, i was able to upgrade to nightly 61 through ROM manager.
[Vega Android Development] mad-murdock:
about 3d: just flashed 61 to make sure - and yes - full 3d support.

about rom manager: in nightly 61, rom manager is 4.2.0.1 - it was 4.2.0.0 in older nightlies. i talked to koush some days ago about rom manager troubles on vega. he said he would push an update - 4.2.0.1 is probably that update.

i just flashed cwm 3.0.2.7 with rom manager - it worked. i just (re) flashed nightly 61 with rom manager - it worked.

so rom manager in nightly #61+ is okay. will update first post.
[Vega Android Development] brunsbanjo:
Got a strange issue... flashed 61 tonight,

first time init doesn't work (so i touched clockwise the corners)

but then i cannot add an google account (in order to use the market, it opens and closes)

everytime i want to add an account, i just can add an exchange account.

cpu overclock also doesnt work

reboot into recovery doenst work
[Vega Android Development] mad-murdock:
did you flash latest gapps? this sounds like stuff i read when people used the january gapps.

about the first time init - when fresh installing, you may not use the phone removal until you did a first boot and the setup wizard is done - see first post for install instructions
[Vega Android Development] brunsbanjo:
flashed with newest cwm

full wipe

flashed 61

full wipe

flashed latest gapps (the one in your last post)

first boot up....first time init doesnt work

no chance to add a google account

maybe i can start with an earlier build, add my gaccount, flash 61 and gapps..
[Vega Android Development] scanno:
What exaclty does not work with the first time init ???
[Vega Android Development] brunsbanjo:
cannot touch the android, it blinks but nothing happens
[Vega Android Development] scanno:
And you did not flash the vega-phone-removal.zip. And what happens when you try to change the language ? Does that work?
[Vega Android Development] brunsbanjo:
didnt removed phone parts,

also tried that, nothing happens... *sad*
[Vega Android Development] scanno:
There is a change you might have a bad download. You could check the checksum if that matches. If the checksum matches, perhaps try nightly 60 to see if it works there.
[Vega Android Development] rvdgeer:
I flashed #61 yesterday (or the day before), but am not quite sure it updated correctly...

(Didn't keep my eyes on the screen dureing the install, so did not look out for errors or success reports :))

Any way to determine which nightly I'm on now?

EDIT: about screen says:

Mod version: CyanogenMod-7-04

26

2011-NIGHTLY-Vega

Should this be 04

27

2011?
[Vega Android Development] scanno:
I updated also to nightly 61 and i have also 04262011. And not 04272011. But i do not know how long a build takes. If you look at the time, it is 2:02, so i a build takes longer then 2 hours and 2 minutes then the build would have been started on 26-04-2011 and that might be the cause why there is 04262011 in the Mod version instead of 04272011.

EDIT:

Checked the ZIP file.... and looked in the system_build.prop. It says there that the build date is 26 april. Also the ro.modversion states 26 april. So it is correct...
[Vega Android Development] mad-murdock:
i agree. most probably a broken download. with a very small chance something blew up without we noticed. please re download both files and report back.

Morsed by hitting a plastic pipe with my Desire HD. Excuse typos.
[Vega Android Development] mad-murdock:
there might also be a difference between build time and upload time. you see only the upload time. build time can be seen if you open the zip and check file dates.

as a matter of fact we cannot include build number into the rom. file is simply renamed after building. original name of nightlies is update-squished. zip

Morsed by hitting a plastic pipe with my Desire HD. Excuse typos.
[Vega Android Development] scanno:
Sorry i meant MOD Version instead of buildnumber :D

I edited my previous post.
[Vega Android Development] just_nos:
Strange ? i dont se textures in quadrant and have only 35fps ;)

can u explain that ?

* edit ;) reinstalled quadrant just got the textures back :) and still 35fps

only quadrant score is not that high ? 1827 ?
[Vega Android Development] mad-murdock:
quadrant is crap to be honest. it got issues since gingerbread release and the author doesn't seem to be fast with fixes. there are lots of games and other benchmarks available which all work fine. the classic Neo core (remember, its limited to 60 fps maximum) as well as... what's its name? smart bench iirc.

note: to test a hardware function, you shouldn't usea benchmark. test it with a proper app and only use

benchmark to determine the speed

Morsed by hitting a plastic pipe with my Desire HD. Excuse typos.
[Vega Android Development] mad-murdock:
by the way: building takes 10 minutes here. 20-30 minutes are common. on low end hardware (notebooks, vm and the like) you can end up with 2-4 hours

we talk about 135k files to be processed. for froyo google stated the size at 30 million lines of code. its probably a lot more now with gingerbread plus cm extras.

Morsed by hitting a plastic pipe with my Desire HD. Excuse typos.
[Vega Android Development] just_nos:
just removed quadrant and installed neocore for 3d etc

getting a 50.5 fps

Edit* murdock eny reason why i cant play avi ? thru the standard movie app ?

i hear the first seconds audio from video and then it stops
[Vega Android Development] rvdgeer:
Thanks for checking!

Was about to reflash, just to make sure, but no need for it now...

:)