Vegacomb 3.2 very unstable, crashes every few minutes

[Guest _falter_]

Hi guys, I'm new to the vega, and to this forum, so thanks to the devs for doing such cool work.

I installed Modstock 1.10 v2, and then VegaComb_HC3.2_Build8.1 - however I get constant crashes when using the device. The crashes aren't limited to a certain application or task - they seem to happen randomly, and it usually turns 85% of the screen black, and leaves the rest white.

I wondered if anyone else experienced this at all? I've tried Corvus5 and it worked fine, so this leads me to believe the hardware is ok (It is one of the £149 ebay curries/pc world deals). I've reinstalled Modstock as well as vegacomb (after redownloading them both) and I get exactly the same results. I wipe both the disk and the cache before installing vegacomb, so as far as I can tell, I'm doing everything correctly

Any help is much appreciated - I've read a lot of success stories about this mod, and I'd really like to make it my full time install :-)

Photo of the crash:

My installation steps:

1. Clean install (Advent 1.10 using Vega Tools), tested working ok - turned off

2. Hold in back button for 2 secs and press power button for 2 secs (Hear PC connect to it)

3. Run VegaModdedStock_v1.10_v2 - wait for completion and press enter... get android logo on screen briefly, then it powers off

4. Power on normally, get android logo, advent logo, run through setup wizard, press apps --> recovery

5. Boot into Clockworkmod v3.0.2.4, wipe data/factory reset, wipe cache partition, advanced-->wipe dalvik cache, install zip from SD-->choose zip--> choose VegaComb_HC3.2_Build8.1, reboot system now

6. Get vegacomb is free warning, logo, honeycomb logo, and boots into 3.2 ok. Disconect USB

[Guest rebeldx]

This happens to me a lot too ...... I just figured it was my Vega ( i too installed fully n wiped everything 1st)

my Wife's Vega does not have this issue though :s (i installed hers too, the same way i installed mine)

[Guest newbe5]

Try using ModdedStock v1, or manually increasing the system partition size before NVflashing Moddedstock (in flash.cfg) to make it larger. These issues tend to occur due to bad blocks within the system area. Alternatively, open the Zip in 7zip or similar, and remove any apps you don't want, like BooksTablet (kinda useless) or Maps, see if that helps you ;)

newbe5

[Guest _falter_]

Try using ModdedStock v1, or manually increasing the system partition size before NVflashing Moddedstock (in flash.cfg) to make it larger. These issues tend to occur due to bad blocks within the system area. Alternatively, open the Zip in 7zip or similar, and remove any apps you don't want, like BooksTablet (kinda useless) or Maps, see if that helps you ;)

newbe5

I Tried using Moddedstock v1, but I just got endless boot cycle with the 'if you have paid for vegacomb' screen

Could you explain further how you adjust the partition size manually please? Hopefully removing some apps might help. If not I guess I may return and see if I can get another one to see if it corrects the issue :-(

[Guest rebeldx]

Try using ModdedStock v1, or manually increasing the system partition size before NVflashing Moddedstock (in flash.cfg) to make it larger. These issues tend to occur due to bad blocks within the system area. Alternatively, open the Zip in 7zip or similar, and remove any apps you don't want, like BooksTablet (kinda useless) or Maps, see if that helps you ;)

newbe5

cheers Newbe, will try that :)

Edited September 9, 2011 by rebeldx

[Guest rebeldx]

i unzipped using 7zip, opened the system folder, then the app folder, then deleted BooksTablet.apk & maps.apk .............. then zipped the file back up, tried to install it and it comes up with 'installation aborted'

im obviously doing something wrong ...... what is it?? lol

[Guest newbe5]

i unzipped using 7zip, opened the system folder, then the app folder, then deleted BooksTablet.apk & maps.apk .............. then zipped the file back up, tried to install it and it comes up with 'installation aborted'

im obviously doing something wrong ...... what is it?? lol

Don't unzip and re-zip, just open it in 7zip and delete the stuff directly ;)

[Guest rebeldx]

Don't unzip and re-zip, just open it in 7zip and delete the stuff directly ;)

cheers dude, it's workin awesome, so far no crashes :)

[Guest princeotter]

Don't unzip and re-zip, just open it in 7zip and delete the stuff directly ;)

Working the other way round - can we just add certain APKs into the Zip file so that there are in System? (And I suppose if the answer is Yes - are there any advantages?)

[Guest newbe5]

Working the other way round - can we just add certain APKs into the Zip file so that there are in System? (And I suppose if the answer is Yes - are there any advantages?)

You could, but I really wouldn't add any more size. The system size on VC3.1b8.1 is already 150mb, and thats the limit of MSv2 (hence why people with bad blocks have issues). ModdedstockV1 had a 155mb size, so thats why that helps some people. After the kernel was changed a while ago, you can actually tweak this value to anything you like inside the moddedstock package (in flash.cfg) so technically you could increase the system partition size to 200mb if you wanted and add more apps to /system.

Thats how most people create "custom" roms, they just change the .apk's in /system/app and rename the rom :P

newbe5

[Guest _falter_]

You could, but I really wouldn't add any more size. The system size on VC3.1b8.1 is already 150mb, and thats the limit of MSv2 (hence why people with bad blocks have issues). ModdedstockV1 had a 155mb size, so thats why that helps some people. After the kernel was changed a while ago, you can actually tweak this value to anything you like inside the moddedstock package (in flash.cfg) so technically you could increase the system partition size to 200mb if you wanted and add more apps to /system.

Thats how most people create "custom" roms, they just change the .apk's in /system/app and rename the rom :P

newbe5

I've tried deleting books and maps apk, and it was fine for about 10mins before crashing again :-( I'll try again with modstock v1 - but last time it just gave me a never ending boot cycle

Tried again with v1, got the same results. I think I may be forced to use something else :-(

Edited September 11, 2011 by _falter_

[Guest richardmlea]

Hi falter,

Off subject, is your Vega a refurb or something? You mention a £149 deal.

[Guest _falter_]

Hi falter,

Off subject, is your Vega a refurb or something? You mention a £149 deal.

Yes it's a refurb from Curries, which I thought might be the reason for the crashes - however I've been using corvus5 for the past 24 hours, and it's not crashed once, so I believe the hardware seems ok

[Guest richardmlea]

Is the screen plastic or glass?

[Guest _falter_]

Is the screen plastic or glass?

I'm pretty sure it's glass - but you've made me doubt myself so I'll double check when I get home!

What difference might this make?

[Guest newbe5]

Yes it's a refurb from Curries, which I thought might be the reason for the crashes - however I've been using corvus5 for the past 24 hours, and it's not crashed once, so I believe the hardware seems ok

It is the hardware, it's all down to bad block avoidance on the NAND. Corvus5 is a much smaller ROM in terms of size and so it avoids these blocks, wheras VC uses all 150mb that ModdedStockv2 allocates to /system, so if you have bad blocks it can't avoid them. You can try either using MSv1, or manually increase the size of the system partition when you flash ModdedStock by editing flash.cfg. This might be something I do as standard in the future to avoid issues.

newbe5

[Guest Dan-Dare]

Hi i get the same random crash prob also, and have tryed modded stock v1 v2 and the build 9 thats floating about still the same crash prob noo change.

I have also tryed removing apps and trying bigger size system partition still no luck same random crash prob.

I have no probs running corvus5 rom or vegacomb beta 1.7 so it looks like i will have to go back to corvus rom for now.

If this prob is to do with the NAND and bad blocks wouldnt the format mark out all the bad blocks so the system would not use them like it dose with a hard drive on the pc ?

Also if there was programs being writen to a bad block it would be that one program that would crash when you tryed to run it but my system crashes are random not the same programs are running ?

[Guest richardmlea]

I'm pretty sure it's glass - but you've made me doubt myself so I'll double check when I get home!

What difference might this make?

Cheers falter, I was curious whether the refurbished units have plastic or glass screens. I have a plastic screen on mine I am happy with it but my bro is getting one in a few days and would prefer a glass screen. I would also like him to get a glass one so I can compare it with mine.

[Guest _falter_]

FYI - the vega is back on ebay currys/pcworld store for £140 again (refurbished) I just ordered another one to see if vegacomb will run on it or not - if it does i'll be returning the original one! (damn internal memory!)

[Guest Dan-Dare]

Well after going back to the corvus rom which runs with no probs i thought i would give the vegacomb another go seeing as there was a new update out 9n update 3 still the same here random crashes lockups.

Ive have seen quite a few other users are having the same probs over at the tabletroms forum and one user said to install cpumaster and try limiting the cpu to 1000mhz so i gave it a try and it seems to work better still locks up now and again but not anything like it used to why ??????

Also i know that my vega is not a good overclocker as i have tryed to overclock it before and it would lockup above 1100mhz maybe there is a bug in the vegacomb cpu manager.