Jump to content

MoDaCo Custom r7 Beta discussion archive


Recommended Posts

Guest kevinha
Posted

USB Mode doesn't work for me. when i switch to host mode it doesn't reboot and logcat says:

I/ActivityManager( 1034): Starting activity: Intent { act=android.intent.action.

MAIN cmp=com.modaco.vegausbmode/.host }

E/su (19448): Couldn't open database

W/su (19448): request rejected (10059->0 /system/bin/sh)

I/ActivityManager( 1034): Displayed activity com.modaco.vegausbmode/.host: 6863

ms (total 6863 ms)

I had previously installed the apk on v1.08 and also z4root without any luck. maybe this problem is a hangover from that.

  • Replies 231
  • Created
  • Last Reply
Posted

Superuser is failing... do you have the Superuser app in the main menu?

If so, in Settings->Applications 'Clear Data' on Superuser and try again.

P

Guest NDroidB
Posted
I get these issues with games, can pretty much guarantee that at any given point during a game of Droid Words Free there will be some artefacts over the letter tiles and buttons beneath (and generally all over the place).

These issues started appearing after updating to the r2 kernel (running MCR 1.0.6 - gonna try this this evening or maybe hold off till there's more news on the glitches)

Paul, you're a fecking legend!

From reading through all the screen glitch threads and posts, I would say that the issues started with the stock 1.08 rom issued by Advent rather than the r2 kernel.

I cannot say for sure as I haven't checked it myself, but I suspect that the r2 kernel may not be the culprit.

Guest zzleezz
Posted
Many thanks for looking into this!

Easy way is try this Live Wallpaper, guaranteed corruption on demand just like the screenshot I posted earlier:

https://market.android.com/details?id=com.joko.lightgrid

Cheers

Yup. That wallpaper is a really good way to replicate the problem. My corruption is quite mild but its constant with that wallpaper.

Guest dannight
Posted
From reading through all the screen glitch threads and posts, I would say that the issues started with the stock 1.08 rom issued by Advent rather than the r2 kernel.

I cannot say for sure as I haven't checked it myself, but I suspect that the r2 kernel may not be the culprit.

Well considering I haven't made the move to the 1.08 rom yet I suspect it's not that, seems to randomly appear for different people after applying various updates etc. I've not seen anywhere that it's been narrowed down to a probable cause. Have also seen others on 1.06 with same issues

Guest Sir Gash
Posted
From reading through all the screen glitch threads and posts, I would say that the issues started with the stock 1.08 rom issued by Advent rather than the r2 kernel.

I cannot say for sure as I haven't checked it myself, but I suspect that the r2 kernel may not be the culprit.

I had it with stock kernel on 1.06.5 but it was so rare and unobtrusive that it didn't bother me. There was no difference between 1.06.5 and 1.08, for me it is down to the new kernel. Could also be caused by compatibility problems with nVidia graphics libs/drivers rather than a specific issue with the kernel itself.

It's a shame because r7 pre is the best ROM for Vega so far, everything else has been perfect for me!

Guest NDroidB
Posted
Well considering I haven't made the move to the 1.08 rom yet I suspect it's not that, seems to randomly appear for different people after applying various updates etc. I've not seen anywhere that it's been narrowed down to a probable cause. Have also seen others on 1.06 with same issues

Yes, sorry about that - just been reading back through and noticed that you and others are not on 1.08 ;)

Better go get another coffee to wake up!!

;)

Guest kevinha
Posted
Superuser is failing... do you have the Superuser app in the main menu?

If so, in Settings->Applications 'Clear Data' on Superuser and try again.

P

I have Superuser but on the Settings tab there is no 'Clear Data'. Superuser version is v2.3.6.1.

Guest Lennyuk
Posted
I have Superuser but on the Settings tab there is no 'Clear Data'. Superuser version is v2.3.6.1.

Menu> settings > applications >application management

locate SuperUser and click

then click clear data

NOT IN THE APP ITSELF!!

hope this helps ;)

Guest bakedecake
Posted

I love that wallpaper but my screen goes nuts too.

Guest kevinha
Posted
Menu> settings > applications >application management

locate SuperUser and click

then click clear data

NOT IN THE APP ITSELF!!

hope this helps ;)

yeah i had already tried that, that's why i was looking elsewhere. didn't help.

Guest Tony Williams
Posted
Well considering I haven't made the move to the 1.08 rom yet I suspect it's not that, seems to randomly appear for different people after applying various updates etc. I've not seen anywhere that it's been narrowed down to a probable cause. Have also seen others on 1.06 with same issues

I`m on 1.065 with MCR addon and PP and have only had the screen glitches since installing the R2 kernel. Not annoying enough to make me want to revert back to the stock kernel though. Other than the screen glitches the setup I have at the moment seems very stable and responsive, clockworkmod working ok etc so I`m leaving it as it is for now ;)

Guest Lennyuk
Posted

Paul have you decided if your going to add a2sd to this rom yet?

Posted
re: speed, i'm not finding this slow once it's done it's initial sync bits (and I've replaced the stock launcher which is notoriously bloated!)

Paul, what launcher are you using?

On my vega, with a fresh install of the stock 1.8 image and this Pre7 over the top, I'm returning a quadrant of 1887.

Thanks for all your work on this. Modaco has completely freed the Vega! ;)

Guest wipeout140
Posted

Feeta, I replaced the default launcher with ADW Launcher and this clean install of 1.08 and r7 is working the best it has ever been, so thanks again

Posted
Paul have you decided if your going to add a2sd to this rom yet?

As a kitchen option in due course, yeah.

P

Posted
Paul, what launcher are you using?

On my vega, with a fresh install of the stock 1.8 image and this Pre7 over the top, I'm returning a quadrant of 1887.

Thanks for all your work on this. Modaco has completely freed the Vega! ;)

ADW Launcher EX.

P

Posted

Thought I'd give this a go now that I'm an expert in getting into recovery mode ;)

Fresh install of Advent Vega 1.08 Final

Install r7-pre7-vega-update-modacocustomrom-unsigned

No apps installed / changed apart from adding Google account info; reboot & leave for 5 mins after installing any apps

Install Quadrant Standard& ran full benchmark;

- stock browser & launcher 1968

- stock browser & ADW launcher 1888 (minor glitching on some screens & Quadrant restarted itself at score screen then FC)

- Dolphin HD & ADW Launcher 1620 (Quadrant restarted itself at score screen then FC)

Hmmm

Posted

Quadrant results seem a bit variable and unreliable unfortunately!

For example, second time you run it = much better results!

P

Guest Lennyuk
Posted

if we can get a fix/improve the graphic issue I would say this rom looks ready for an "official" release.

Posted
From reading through all the screen glitch threads and posts, I would say that the issues started with the stock 1.08 rom issued by Advent rather than the r2 kernel.

I cannot say for sure as I haven't checked it myself, but I suspect that the r2 kernel may not be the culprit.

Can't be, as I get them 0n 1.06.5 . I can see them on the tabs on Dolphin HD on the text that is scrolling in the tab itself. If I remove the kernal, they are gone.

Guest kevinha
Posted

Still having USB Mode switch problems. Flashed stock 1.08, added r7 pre7 still logcat says

I/ActivityManager( 1060): Starting activity: Intent { act=android.intent.action.

MAIN cmp=com.modaco.vegausbmode/.host }

E/su ( 5040): Couldn't open database

W/su ( 5040): request rejected (10050->0 /system/bin/sh)

I/ActivityManager( 1060): Displayed activity com.modaco.vegausbmode/.host: 5847

ms (total 5847 ms)

anybody got any straws i can grasp at ?

Posted
Quadrant results seem a bit variable and unreliable unfortunately!

For example, second time you run it = much better results!

P

Just as well I don't rely on benchmarks ;)

Posted
From reading through all the screen glitch threads and posts, I would say that the issues started with the stock 1.08 rom issued by Advent rather than the r2 kernel.

I cannot say for sure as I haven't checked it myself, but I suspect that the r2 kernel may not be the culprit.

I first saw the screen corruption after applying the PP to 1.06.5, long before the kernel was available. While testing my bluetooth/wifi issue last night I saw them on a stock 1.08 install, which I am led to believe has the PP code included. Seems to me the PP code is the culprit, but that's just my experience.

Guest
This topic is now closed to further replies.

×
×
  • Create New...

Important Information

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