Jump to content

VegaComb CPU speed adjustment


Recommended Posts

Guest simonta
Posted
Thank you again, Simon,

It is very good to recieve not only an informative reply, but a real treat to get written in proper Enlish, rather than misspelled forum speak.

If I may ask an additional question - how does one wire Dalviz using CWM to do a rom clean installation? When I re-boot into CWM Recovery it only offers mer Wide Data/Factory Reset and Wipe Cache. Or is this the dreaded Dalvig? (As you know, a little knowledge is a dangerous thing!).

Mikhail.

And to add the missing answer to your questions ;)

The long answer is quite technical and perhaps best left to Google for those whose curiosity nags their itchy gland.

The short answer is that one of Androids' tricks, actually a trick of most mobile operating systems, is that every application you run runs in it's own mini version of Android. In this way, all applications are separated from each other except in ways that Android allows and developers take advantage of. The end result as far as we are concerned is a more stable, more secure platform. The mini version of Android is called a "virtual machine" and the software which runs it is called Dalvik. Out of interest, there are many links to Iceland in Android. Dalvik is the name of an Icelandic fishing village. Google for "Smali" for more links to Iceland and information about the guts of Android.

In order to provide higher performance, Dalvik does a "first time run" optimisation of the code inside the application which it uses to know how to load and run the application more effectively the next time you use it. The results of this optimisation are stored in the "Dalvik cache".

The reason you should clear it as that when you change ROMs, a system application may have had significant changes to it's code and therefore, significant changes in the way in which it should be optimised. If such changes are not made, then instability can result, perhaps even crashes. Because the system is involved, these crashes may appear in apps which actually haven't been changed and are extremely hard, if not impossible to figure out. In many case, developers will insist that you clear the cache and try again before they will investigate issues.

If the cache is cleared, Dalvik will simply re-create it the next time an app is run. All you will see, if anything, is a second or two delay while the app loads. If you uninstall an app, then the cache for that app is also cleared. However, when you swap ROMS, and the cache is not cleared, there is no way for the new system to know if the cache is good or not. Actually, there is but Android isn't designed to have ROMs swapped from under it's nose and to add checks would take more memory and CPU so why bother?

Hope this explains why you should clear the cache before swapping ROMs. For people who tinker, it's good advice to clear the cache if you are experiencing strange behaviour and seemingly random/unrelated freezes or crashes as part of the troubleshooting.

Cheers

Simon

Guest premieral
Posted
And to add the missing answer to your questions ;)

The long answer is quite technical and perhaps best left to Google for those whose curiosity nags their itchy gland.

The short answer is that one of Androids' tricks, actually a trick of most mobile operating systems, is that every application you run runs in it's own mini version of Android. In this way, all applications are separated from each other except in ways that Android allows and developers take advantage of. The end result as far as we are concerned is a more stable, more secure platform. The mini version of Android is called a "virtual machine" and the software which runs it is called Dalvik. Out of interest, there are many links to Iceland in Android. Dalvik is the name of an Icelandic fishing village. Google for "Smali" for more links to Iceland and information about the guts of Android.

In order to provide higher performance, Dalvik does a "first time run" optimisation of the code inside the application which it uses to know how to load and run the application more effectively the next time you use it. The results of this optimisation are stored in the "Dalvik cache".

The reason you should clear it as that when you change ROMs, a system application may have had significant changes to it's code and therefore, significant changes in the way in which it should be optimised. If such changes are not made, then instability can result, perhaps even crashes. Because the system is involved, these crashes may appear in apps which actually haven't been changed and are extremely hard, if not impossible to figure out. In many case, developers will insist that you clear the cache and try again before they will investigate issues.

If the cache is cleared, Dalvik will simply re-create it the next time an app is run. All you will see, if anything, is a second or two delay while the app loads. If you uninstall an app, then the cache for that app is also cleared. However, when you swap ROMS, and the cache is not cleared, there is no way for the new system to know if the cache is good or not. Actually, there is but Android isn't designed to have ROMs swapped from under it's nose and to add checks would take more memory and CPU so why bother?

Hope this explains why you should clear the cache before swapping ROMs. For people who tinker, it's good advice to clear the cache if you are experiencing strange behaviour and seemingly random/unrelated freezes or crashes as part of the troubleshooting.

Cheers

Simon

Thats why i have grown to love this forum, even at 50 i am still learning fascinating pieces from bright people

Guest MikhailM
Posted
it is "laugh out loud" Mikhail and judging by your name even though your location flag is english i would hazard a guess you are not.

If that is the case me bad for poking fun at your attempts to write correctly in the previous posts when no matter what language i tried it would not appear as clear as yours did, my apologies ;)

Yes, I am Russian, but born in China, have lived most of my life in England, but travel constantly. My apology was in fact sent from Moscow airport, while waiting for a plane back to London, from where this one comes. Which has nothing to do with Vega or the roms, so back to the matter in hand.

How does one get rid of an unwanted widget from the Home screen. On my Desire HD you can drag the unloved widget to the convenient waste bin, which appears at the bottom of the screen. Have not worked out how one does it on the Vega.

Mikhail.

Guest simonta
Posted
Thats why i have grown to love this forum, even at 50 i am still learning fascinating pieces from bright people

You young whipper snapper. I'm a year ahead of you ;)

Guest premieral
Posted
Yes, I am Russian, but born in China, have lived most of my life in England, but travel constantly. My apology was in fact sent from Moscow airport, while waiting for a plane back to London, from where this one comes. Which has nothing to do with Vega or the roms, so back to the matter in hand.

How does one get rid of an unwanted widget from the Home screen. On my Desire HD you can drag the unloved widget to the convenient waste bin, which appears at the bottom of the screen. Have not worked out how one does it on the Vega.

Mikhail.

exactly like that Mikhail, hold until it loosens then drag it to the waste bin that appears.

Guest MikhailM
Posted
exactly like that Mikhail, hold until it loosens then drag it to the waste bin that appears.

Thanks again, Premieral,

In my old age I am obviously getting less observant. I have tried "holding down" the widget and looked for the Wastebin, but failed to notice it in the top right hand corner. Now I found it, thanks.

I also take back all I wrote earlier about the slowness of Vegacomb. Once Mxbob has told me where to find Darvik (Thank you, Mxbob!) and I have done a full wipe of Darvik, data and cache and re-installed Vegacomb, it has been running smoothly and fast (perhaps a touch slower than Corvus 5, but hardly so).

Actually, I should have said "install", as I have now taken advantage of Newbe's latest and installed 1.6 as a new clean installation. This may have something to do with it as well, but perhaps it is the result of wiping Darvik.

The Browser again suggested I need to install Flash 10.3 and once I did that, YouTube now runs both small screen and full screen. BBC I Player also works, but only full screen and with the orange band along the bottom (reference to which I found in some thread).

In case anyone is interested and has not been able to get I Player running, in my case, when you launch it, select a programme to watch, click on it, the page comes up with the small inset playback screen blank and the video not running. Sometimes the image flashes on for a second, but then goes blank. By trial and error I have found an invisible button about 1/3 up along the right hand side of the small blank screen. When one clicks on it, the full screen playback begins, with a misleading message appearing for a few moments about pressing the back button to get a full screen image. If you actually do press the back button, it of course simply takes you back to the previous screen.

My only regret is that under Vegacomb 1.6 the WiFi does not automatically re-connect to a Remembered service, as it invariably does in Corvus 5. Does anyone know, if there is something under settings to make it re-connect automatically? I could not find it.

Anyway, thank you Newbe5, Simon, Premieral and Mxbob - with your help and advice I have finally got VC working beautifully.

Mikhail.

Guest MikhailM
Posted

Thanks again, Premieral,

In my old age I am obviously getting less observant. I have tried "holding down" the widget and looked for the Wastebin, but failed to notice it in the top right hand corner. Now I found it, thanks.

I also take back all I wrote earlier about the slowness of Vegacomb. Once Mxbob has told me where to find Darvik (Thank you, Mxbob!) and I have done a full wipe of Darvik, data and cache and re-installed Vegacomb, it has been running smoothly and fast (perhaps a touch slower than Corvus 5, but hardly so).

Actually, I should have said "install", as I have now taken advantage of Newbe's latest and installed 1.6 as a new clean installation. This may have something to do with it as well, but perhaps it is the result of wiping Darvik.

OK, Everyone, I have finally learned to spell Dalvik and will not misspell it again, promise, especially as I also now know it is a fishing village in Iceland!

Mikhail.

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.