Guest vulpy Posted July 23, 2011 Report Posted July 23, 2011 I am amazed with the updates in the latest firmware 1.10 from Advent... Touchscreen issues are defo fixed as well as the deep sleep issues. Somebody did a quick root/modded version (was it Paul?) but... WHAT ABOUT an update for the fast (yet prone for freezing) Corvus ROM or Paul's R8? COUNT ON YOU GUYS !!!!
Guest vulpy Posted July 23, 2011 Report Posted July 23, 2011 Someone was mentioning a 1.11 firmware... I could not find it on the Advent Vega page...
Guest lesd Posted July 24, 2011 Report Posted July 24, 2011 I am amazed with the updates in the latest firmware 1.10 from Advent... Touchscreen issues are defo fixed as well as the deep sleep issues. Somebody did a quick root/modded version (was it Paul?) but... WHAT ABOUT an update for the fast (yet prone for freezing) Corvus ROM or Paul's R8? COUNT ON YOU GUYS !!!! Hi Vulpy, At the mo, the big push for developers is Vegacomb. One part of this development is a modified version of the 1.10 firmware, referred to as the modded stock ROM which is preferred for Vagacomb. I'm using the modded stock ROM as base, with Corvus5 and SP1 on top of that. It isn't prone to freezing.
Guest BlackTigerX Posted July 24, 2011 Report Posted July 24, 2011 Hi Vulpy, At the mo, the big push for developers is Vegacomb. One part of this development is a modified version of the 1.10 firmware, referred to as the modded stock ROM which is preferred for Vagacomb. I'm using the modded stock ROM as base, with Corvus5 and SP1 on top of that. It isn't prone to freezing. If you installed Corvus5 after having the modded 1.10 base installed, then nothing is left from that base! Apart from the partition sizes. So you don't have 1.10 running but 1.08 (that's what Corvus5 is built on afaik).
Guest lesd Posted July 24, 2011 Report Posted July 24, 2011 If you installed Corvus5 after having the modded 1.10 base installed, then nothing is left from that base! Apart from the partition sizes. So you don't have 1.10 running but 1.08 (that's what Corvus5 is built on afaik). Really? I don't have any information about the structure of an Android installation, I'm just taking Newbe5 at his word. Anyway, the point is, if you install the modded stock ROM you'll have a stable ROM manager, and su status, so you can download and install whatever you want on top, or over the top, using the ROM manager instead of the PC.
Guest xathras Posted July 24, 2011 Report Posted July 24, 2011 Really? I don't have any information about the structure of an Android installation, I'm just taking Newbe5 at his word. Anyway, the point is, if you install the modded stock ROM you'll have a stable ROM manager, and su status, so you can download and install whatever you want on top, or over the top, using the ROM manager instead of the PC. I'd be most grateful if you could provide a reference (thread and post number) for where Newbe5 uses the term "on top of" in relation to installing a new ROM, since it is such a misleading term. Flashing a new ROM completely replaces the previous ROM; there is no top of, underneath, to the side of, or any other direction involved.
Guest lesd Posted July 24, 2011 Report Posted July 24, 2011 (edited) I'd be most grateful if you could provide a reference (thread and post number) for where Newbe5 uses the term "on top of" in relation to installing a new ROM, since it is such a misleading term. Flashing a new ROM completely replaces the previous ROM; there is no top of, underneath, to the side of, or any other direction involved. Newbe5 did not use that term. In this post , he said " The main reason for this, is to be used as a ROM base for Vegacomb (and any other ROM you wish to use). I read somewhere (I think it may have been in Simonta's instructions) that strictly speaking, you are installing an update to the ROM. Also, I've just checked my system, and I have Corvus5 SP1, but the kernel is Vegacomb. EDIT I can confirm It was in Sinonta's instructions. Edited July 24, 2011 by lesd
Guest xathras Posted July 24, 2011 Report Posted July 24, 2011 (edited) Newbe5 did not use that term. In this post , he said " The main reason for this, is to be used as a ROM base for Vegacomb (and any other ROM you wish to use). I read somewhere (I think it may have been in Simonta's instructions) that strictly speaking, you are installing an update to the ROM. Also, I've just checked my system, and I have Corvus5 SP1, but the kernel is Vegacomb. EDIT I can confirm It was in Sinonta's instructions. Well, I stand corrected. I assume you mean this passage:- This seems to boil down to flashing a "ROM" completely replaces what was there before, but "flashing" an "update" doesn't. The confusion arises between the strict and loose interpretation of "ROM". It would seem that Corvus5 is, from the strict point of view, an "update" for Froyo and so doesn't change the kernel. So when you went from VegaComb to Corvus5 the VegaComb kernel was left intact. Does this cause you any problems? What is the difference in performance, if any, between you and someone using Corvus5 with the original kernel? I went from the stock Advent1.08 to Modaco r8 on the day of purchase, and from there to CM7 and finally to VegaComb, so I got used to the idea that flashing a "ROM" changed everything. Edited July 24, 2011 by xathras
Guest lesd Posted July 24, 2011 Report Posted July 24, 2011 (edited) Well, I stand corrected. I assume you mean this passage:- This seems to boil down to flashing a "ROM" completely replaces what was there before, but "flashing" an "update" doesn't. The confusion arises between the strict and loose interpretation of "ROM". It would seem that Corvus5 is, from the strict point of view, an "update" for Froyo and so doesn't change the kernel. So when you went from VegaComb to Corvus5 the VegaComb kernel was left intact. Does this cause you any problems? What is the difference in performance, if any, between you and someone using Corvus5 with the original kernel? I went from the stock Advent1.08 to Modaco r8 on the day of purchase, and from there to CM7 and finally to VegaComb, so I got used to the idea that flashing a "ROM" changed everything. Subjectively, I think Corvus 5 with SP1 may be more stable on the vegacomb kernei than on the Advent 1.10 kernel. I base this statement on the number of times the CPU clock has stuck at 216MHz. A while back, there were a lot of reports of this problem on Corvus 5, so I resolved to keep track of the specific conditions when it happened to my Vega. The thing is, it only happened once (this morning) after a week or so. I think I flashed the modded stock ROM about then. EDIT: Corvus 5 SP1 names the kernel 2.6.32.35VegaCombKernel-gf6a57e8-dirty homer@homer-desktop#10 It's nothing to do with installing Vega Edited July 25, 2011 by lesd
Guest lesd Posted July 25, 2011 Report Posted July 25, 2011 (edited) I am amazed with the updates in the latest firmware 1.10 from Advent... Touchscreen issues are defo fixed as well as the deep sleep issues. Somebody did a quick root/modded version (was it Paul?) but... WHAT ABOUT an update for the fast (yet prone for freezing) Corvus ROM or Paul's R8? EDIT. I don't think the original instructions posted in this thread Yesterday can work because a full Nandroid restore will completely overwrite the system image. Modified instructions below may work, see later post. 2nd EDIT: IMPORTANT:- When using recovery mode to install a ROM or CWM to install an update make sure that your battery is well charged and that you have the power lead connected. The implication of the last few posts is that anyone using MCR8 or Corvus 5 who wants the features of the 1.10 firmware, should do this: Using CWM, delete the cache and Dalvik cache. Do a Nandroid backup Flash the 1.10 firmware or modded stock ROM using the instructions in the download section of www.myadventvega.co.uk. Do a clean install of your preferred ROM. Restore your backed up data with CWM (advanced restore). Edited July 26, 2011 by lesd
Guest simonta Posted July 25, 2011 Report Posted July 25, 2011 Well, I stand corrected. I assume you mean this passage:- This seems to boil down to flashing a "ROM" completely replaces what was there before, but "flashing" an "update" doesn't. The confusion arises between the strict and loose interpretation of "ROM". It would seem that Corvus5 is, from the strict point of view, an "update" for Froyo and so doesn't change the kernel. So when you went from VegaComb to Corvus5 the VegaComb kernel was left intact. Does this cause you any problems? What is the difference in performance, if any, between you and someone using Corvus5 with the original kernel? I went from the stock Advent1.08 to Modaco r8 on the day of purchase, and from there to CM7 and finally to VegaComb, so I got used to the idea that flashing a "ROM" changed everything. If you read my doc, it refers ONLY to mcr (the Modaco ROM kitchen) which is poorly named and a source of much confusion because it is not a ROM, it's an update. The only reason modded stock ROM is required before Vegacomb is that it changes the partition sizes which is a requirement of Vegacomb 1.7.
Guest lesd Posted July 25, 2011 Report Posted July 25, 2011 If you read my doc, it refers ONLY to mcr (the Modaco ROM kitchen) which is poorly named and a source of much confusion because it is not a ROM, it's an update. The only reason modded stock ROM is required before Vegacomb is that it changes the partition sizes which is a requirement of Vegacomb 1.7. I think the issue is that some people have not updated the firmware since installing MCR8 or Corvus5 and are using the kernel from firmware version 1.08. In your instructions for XP, you provide a general discription for both ROM and 'add on'. Corvus5 falls into the addon category. I wonder how many users who haven't caught onto this business and are still using old firmware. I wonder if it's worth promoting firmware upgrades because, in the recent past, I've noticed fault reports that I can't reproduce with 1.10 firmware. I think it would be better to upgrade to the modded stock ROM because I reckon most people will want to upgrade to Vegacomb at some point, and it saves flashing two ROMs.
Guest premieral Posted July 25, 2011 Report Posted July 25, 2011 I think the issue is that some people have not updated the firmware since installing MCR8 or Corvus5 and are using the kernel from firmware version 1.08. In your instructions for XP, you provide a general discription for both ROM and 'add on'. Corvus5 falls into the addon category. I wonder how many users who haven't caught onto this business and are still using old firmware. I wonder if it's worth promoting firmware upgrades because, in the recent past, I've noticed fault reports that I can't reproduce with 1.10 firmware. I think it would be better to upgrade to the modded stock ROM because I reckon most people will want to upgrade to Vegacomb at some point, and it saves flashing two ROMs. just to throw another curve ball in the pot Corvus5 is based on corvus original rom which in turn used Bumblebees new kernel (so not an update with original advent kernel) which addressed and fixed a lot of issues in earlier vega models :) so i cant honestly see any point in flashing back to stock. And obviously if you want vegacomb 1.7 stock is not an option
Guest lesd Posted July 25, 2011 Report Posted July 25, 2011 just to throw another curve ball in the pot Corvus5 is based on corvus original rom which in turn used Bumblebees new kernel (so not an update with original advent kernel) which addressed and fixed a lot of issues in earlier vega models :) so i cant honestly see any point in flashing back to stock. And obviously if you want vegacomb 1.7 stock is not an option Hi. I've spent some time trying to determine what the situation is, without any real conclusion. I'd have to check through all sorts of stuff to get to the facts. I'll tell you what I think is true, and why. I think that: Corvus 5 is an update. It includes a complete kernel which is derived from the same source as the Advent Vega Stock Kernel. It updates parts of the installation on your device which are; Not standard for the stock image, or Less up to date than the version in the Corvus 5 custom ROM. It is difficult to determine how much of an installation is replaced by an update because the updater simply renames the Kernel when it is finished. I believe this is so because: That's the sensible way to control configuration of software updates, and My copy of Corvus 5+SP1 is both stable and functional. Subjectively, I think it is much more stable than before I flashed the modded stock ROM. That is to say, it is much more stable than when I first installed it, and I think the change happen when I installed the modded stock ROM. Best Regards LesD
Guest vulpy Posted July 25, 2011 Report Posted July 25, 2011 Thanks guys, I think all it's left to do is empirically try combintions of stock FWs and custom ROMs and see how far we can go. My preference would go for Corvus on modded 1.10 base, will try and get back with my findings.... My main targets are uber stability and USB host mode.
Guest lesd Posted July 26, 2011 Report Posted July 26, 2011 Thanks guys, I think all it's left to do is empirically try combintions of stock FWs and custom ROMs and see how far we can go. My preference would go for Corvus on modded 1.10 base, will try and get back with my findings.... My main targets are uber stability and USB host mode. Hi guys. After some serious searching for information, I think the original instructions in post #10 won't work because a full nandroid restore completely overwrites the system. I've edited post #10 to replicate the way I've installed Corvus 5. To save you going back, I'll repeat the instructions here. Using CWM: wipe the cache and the Dalvik cache. Backup your current ROM. Install the modded stock ROM in recovery mode Using CWM install the Custom ROM of your choice. Restore the data from your backup (advanced restore) I have actually done this, and my Vega is operating in that state. I've had no problems so far and I appear to have all the facilities I had before including 'uberstabilty' and usb host mode. I'll continue trying to break it today, and get back to you tonight.
Guest vulpy Posted July 26, 2011 Report Posted July 26, 2011 are you sure you haven't touched the "base" by updating the data part?
Guest lesd Posted July 26, 2011 Report Posted July 26, 2011 (edited) are you sure you haven't touched the "base" by updating the data part? No. However, I am sure that I carried out the procedure in my previous mail last night and have been trying to break my Vega, unsuccessfully since then. The only problem I had was with Flashplayer, which had to be reinstalled. But that happens whenever you install a new ROM or update. I am also sure that I have USB host mode, I have no touchscreen issues, that flashplayer works properly, that the battery level is reported properly when I shut down and reboot, that I haven't had a 216MHz problem despite leaving the tablet in standby for a long period, and that all the apps I have work exactly as they did before I started. But, you see, I started from the 1.10 stock ROM when I bought my Vega, and have never had problems with any of the stuff above. The point is, if you are having problems with your installation, the procedure in my prevoius mail will take you 10 - 15 minutes. If it doesnt work, you can do a full restore from your backup. Edited July 26, 2011 by lesd
Guest vulpy Posted July 27, 2011 Report Posted July 27, 2011 Did a couple of trials myself, so far: Corvus data restore on a 1.10 modded base runs smothly, no reoccurence of any of the the old issues: - frozen screen - jumpy keyboard - cpu 216MHz issue all these seem to be fixed That's all great, now one issue I had with the clean 1.10 modded base was that every once in a while the tablet won't wake at all... only flashing the FW would get in back to work. Currious to see if Corvus restore will get rid of this.... This and an ugly FC on the AWD EX but this may be a hazardous port I've done for the launcher Will keep you posted...
Guest lesd Posted July 31, 2011 Report Posted July 31, 2011 (edited) Did a couple of trials myself, so far: Corvus data restore on a 1.10 modded base runs smothly, no reoccurence of any of the the old issues: - frozen screen - jumpy keyboard - cpu 216MHz issue all these seem to be fixed That's all great, now one issue I had with the clean 1.10 modded base was that every once in a while the tablet won't wake at all... only flashing the FW would get in back to work. Currious to see if Corvus restore will get rid of this.... This and an ugly FC on the AWD EX but this may be a hazardous port I've done for the launcher Will keep you posted... Hi, Vulpy. I've been away for a few days in a wifi free zone. Glad to hear you've resolved some of the old issues. I'm using launcherpro, so no problems with ADW EX. I think I'd try re-installing ADW EX from the market. I think I might have had a couple of occasions when the Vega has switched itself from sleep mode to OFF, but I can't be sure, and I'm not sure that's a bug. I haven't needed to reflash though. Edited July 31, 2011 by lesd
Guest Kevrae Posted July 31, 2011 Report Posted July 31, 2011 (edited) Someone was mentioning a 1.11 firmware... I could not find it on the Advent Vega page... just to reply to this from a week ago there is now a v1.11 on new vega's now, i performed a setup instore on one and noticed the version number. i must say i haven't used stock since about feb and it has improved a hell of allot very smooth but am still very happy with cm7. Edited July 31, 2011 by Kevrae
Guest BlackTigerX Posted July 31, 2011 Report Posted July 31, 2011 Can anyone with a 1.11 rom create a backup (f.e. with cwm) and share it?:o
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now