[ROM][BETA] Quattrimus ICS

**tdm** · 07-03-2012, 05:02 PM

Quattrimus ICS
Android 4.0 "Ice Cream Sandwich" for the Vortex.
Flavors: CM9 and AOKP (AOSP on the way).

Latest release
beta2

Official Page

Please read the official page before reporting issues.

Do not use link2sd, mount2sd, or any other 2sd script with this ROM.

**James7344** · 07-03-2012, 05:39 PM

So, without sounding like an a hole. What can I do to help to get auto rotate working? I'm running AOKP beta and like stated before, my lights stay off whenever auto rotate is not working.

side note: I can over clock at much higher than cm7, almost to max, but when I come out of a deep sleep, no matter what low level it is, 122-480, I'll go into a boot loop that won't stop until re flash. This will happen after any changing of oc but operates perfectly and no freezes happen during stress tests

**tdm** · 07-03-2012, 05:45 PM

Originally Posted by James7344

So, without sounding like an a hole. What can I do to help to get auto rotate working? I'm running AOKP beta and like stated before, my lights stay off whenever auto rotate is not working.

side note: I can over clock at much higher than cm7, almost to max, but when I come out of a deep sleep, no matter what low level it is, 122-480, I'll go into a boot loop that won't stop until re flash. This will happen after any changing of oc but operates perfectly and no freezes happen during stress tests

I will need to research this. My guess is that it's a kernel issue.

The Vortex build is currently running a kernel based off of the LS670 Gingerbread sources and then modified to support ICS. This works splendidly for the VM670 because the hardware is identical. But since the Vortex model number is VS660, I suspect the hardware is a bit different (and a bit older). So the kernel driver may not be driving the hardware properly.

**James7344** · 07-03-2012, 05:51 PM

Originally Posted by tdm

I will need to research this. My guess is that it's a kernel issue.

The Vortex build is currently running a kernel based off of the LS670 Gingerbread sources and then modified to support ICS. This works splendidly for the VM670 because the hardware is identical. But since the Vortex model number is VS660, I suspect the hardware is a bit different (and a bit older). So the kernel driver may not be driving the hardware properly.

I believe that AOKP still does not work for our VS660 now. This is because no matter what is changed, I recieve a boot loop now. Whenever I so much as touch my phone now to unlock, it freezes then boots either to lg or unicorn splash. I suppose cm9 is what I should be on for now

**tdm** · 07-03-2012, 06:09 PM

Originally Posted by James7344

I believe that AOKP still does not work for our VS660 now. This is because no matter what is changed, I recieve a boot loop now. Whenever I so much as touch my phone now to unlock, it freezes then boots either to lg or unicorn splash. I suppose cm9 is what I should be on for now

Thanks. I wasn't aware of this issue. Can you get a logcat output and, if the phone does a full reboot to the LG logo, a copy of /proc/last_kmsg?

**kappacat** · 07-03-2012, 06:22 PM

Okay, First off. Excitement for Beta! WOOOT!!!!
anyway, The few problems, not really major I don't think, but still there.
Screen Rotation - Yes, I did read the post right before this and I actually did figure that was the reason. especially since the cm7 rom had the same problem. Had to use the Froyo kernel (GetItNowMarketing) on that cm7 build just to get it to work.
Bluetooth - just the reboot when it's turned off. (same as the VM670)
Panarama - A common problem from what I hear.
Speakerphone/Mic volume - Too low, can only be heard when speakerphone is clicked. When speakerphone is clicked only raises mic volume doesn't actually turn on speaker phone.
Cm7 had the same problem. (Had to use the froyo kernel for that as well)

Not sure if the info helps, But there it is.
All I have for now. Keep up the good work.

EDIT: Oh, and the roaming thing too.

**Powmining** · 07-03-2012, 06:24 PM

Originally Posted by James7344

I believe that AOKP still does not work for our VS660 now. This is because no matter what is changed, I recieve a boot loop now. Whenever I so much as touch my phone now to unlock, it freezes then boots either to lg or unicorn splash. I suppose cm9 is what I should be on for now

That's weird! I tested AOKP and it worked fine on my Vortex it was even faster than CM9..

**MWisBest** · 07-03-2012, 07:08 PM

AOKP is running for me just fine, minus the screen rotation (motion sensors in general) and mic volume issue of course. Bluetooth reboot isn't an issue for me as I don't use bluetooth, and I'd never use the panorama feature.

EDIT: I tried copying the ami304d out of the working version I had with the Froyo kernel on CM7 to this and it was a no-go. Must be that it isn't compatible with ICS or something more is needed.

**James7344** · 07-03-2012, 08:42 PM

Originally Posted by MWisBest

AOKP is running for me just fine, minus the screen rotation (motion sensors in general) and mic volume issue of course. Bluetooth reboot isn't an issue for me as I don't use bluetooth, and I'd never use the panorama feature.

EDIT: I tried copying the ami304d out of the working version I had with the Froyo kernel on CM7 to this and it was a no-go. Must be that it isn't compatible with ICS or something more is needed.

Well i mean if everyone elses AOKP is working, maybe I had flashed wrong somehow but my cm9 is working correctly. Whenever i flash to new roms, i remove sd and wipe all then re insert and wipe cache and dalvik cache then flash, reboot phone into android, mess with it a bit, then reboot to recovery, flash gapps, then done. If you are all confident that AOKP works, I suppose I will attempt a new download of it and try flashing once again probably in a few days

**James7344** · 07-03-2012, 08:43 PM

Originally Posted by tdm

Thanks. I wasn't aware of this issue. Can you get a logcat output and, if the phone does a full reboot to the LG logo, a copy of /proc/last_kmsg?

I flashed back to cm9 already. If this is still needed i can flash back and do it if you tell me the steps to do so.

**jonny5449** · 07-03-2012, 09:15 PM

Forget music

Here's good alternitive for aokp

Looking for good cm9 or cm7 themes??? visit this site for good themes.

**MWisBest** · 07-03-2012, 09:21 PM

Originally Posted by James7344

Well i mean if everyone elses AOKP is working, maybe I had flashed wrong somehow but my cm9 is working correctly. Whenever i flash to new roms, i remove sd and wipe all then re insert and wipe cache and dalvik cache then flash, reboot phone into android, mess with it a bit, then reboot to recovery, flash gapps, then done. If you are all confident that AOKP works, I suppose I will attempt a new download of it and try flashing once again probably in a few days

I always do this:

1. Make a full nandroid backup.
2. Wipe:
- Data/Factory Reset
- /data
- /cache
- /sdcard/.android_secure
- /system
- Dalvik-Cache
3. Flash ROM.
4. Flash gapps (make sure you get a version the dev recommends if they recommend one, which this dev has one on the ROM page).
5. Reboot.

I have no idea why you flash your ROMs like you do, seems really strange. I wouldn't doubt if that was the cause if your issue.

**MWisBest** · 07-03-2012, 09:30 PM

BUG REPORT:
The power button is wonky. One press on it gets registered as two. When I try to shut the screen off by pressing the button (not holding), the screen shuts off, but it then will make the sound of the screen unlocking and I would attribute this as to why the display is using so much battery as it is running even when I try to shut it off. Also, when I HOLD the power button, I end up with two (2) option screens coming up, the ones for turning phone off and whatnot (duplicates).

Current partial-workaround:
- Letting the display shut itself off after the time limit seems okay, although I haven't tested this extensively it at least doesn't make the unlocking sound when the screen shuts off.

So yeah, battery life is terrible with this.

Tested with AOKP-beta1, have not tested CM9 yet.

**tdm** · 07-03-2012, 10:05 PM

Originally Posted by MWisBest

BUG REPORT:
The power button is wonky.

Thanks, I'll add that to the known issues. It's been that way since the first ics build. Same story with the clock lag.

**MWisBest** · 07-03-2012, 10:23 PM

Originally Posted by tdm

Thanks, I'll add that to the known issues. It's been that way since the first ics build. Same story with the clock lag.

Just to add to that, I'm not sure if this is intended behavior or not but once the power option screen comes up (both, actually) you can let go of the power button and then hold it down again to bring up another power option screen (again, two of them). I haven't messed with a phone with official ICS on it so I wouldn't know if that is something ICS allows you to do or not, but I don't remember this on Gingerbread at all.

**kappacat** · 07-04-2012, 11:13 AM

Okay, this is on cm9. It's happened a few different times that when I leave the google+ app the screen no longer lets me touch. The menu button still worked. but that was all. Until a battery pull. then everything boots back to normal.

A logcat of it happening,

EDIT:Same thing just happened in market with the market. I'm going to try re-flashing.

Second Edit: okay, decided against re-flashing just to see if I could tweak the settings to fix it. So I raised my overclocking to 825, enabled "Don't keep activities", and disabled "surface dithering". Haven't had a problem since.

**MWisBest** · 07-04-2012, 11:40 AM

Would this be of any help for the deep sleep issue?:

EDIT: Nevermind, looked at the source and I see this is already added.

**tdm** · 07-04-2012, 11:42 AM

Originally Posted by MWisBest

Would this be of any help for the deep sleep issue?:

I'll read it thx.

**tdm** · 07-04-2012, 11:55 AM

That article looks spot on, I'll have to try it. Thanks!

**MWisBest** · 07-04-2012, 12:08 PM

Originally Posted by tdm

That article looks spot on, I'll have to try it. Thanks!

Read my edit, I checked your source code and that fix is already in there. :P

**RidDleZ** · 07-04-2012, 02:35 PM

AOKP has been running fine for me here. Absolutely no problems (except for the known

) About the flash Today's build.

**lesheifner** · 07-04-2012, 05:30 PM

I'm doing running my first AOKP, and I'm loving it so far. Next step is to unplug from the charger, install more apps, reboot a few times and see if I can't find some problems.

So far, this little ******* is smokin' fast.

**lesheifner** · 07-04-2012, 06:36 PM

I've encountered my first couple of hiccups. After successfully installing multiple Google Apps from the Play Store including Play Music, Drive, Google +, Maps, etc, an attempt to install YouTube ended in "Package is invalid." Now the attempt to update Superuser is ending the same way.

Other than that, this thing is going so well, I'm wondering if I'm actually still asleep.

**tdm** · 07-04-2012, 06:45 PM

Originally Posted by lesheifner

I've encountered my first couple of hiccups. After successfully installing multiple Google Apps from the Play Store including Play Music, Drive, Google +, Maps, etc, an attempt to install YouTube ended in "Package is invalid." Now the attempt to update Superuser is ending the same way.

Other than that, this thing is going so well, I'm wondering if I'm actually still asleep.

This usually indicates a space issue. Do you use sdext? If not, its time to.

**lesheifner** · 07-04-2012, 07:02 PM

Originally Posted by tdm

This usually indicates a space issue. Do you use sdext? If not, its time to.

For the first time, I formatted to SD-Ext today so I'm a newb to this. Did it with GNM's recovery with a 2GB card. Chose no swap and 1GB for EXT2. Under Storage it shows the following...

Int. Storage 185mb, 142 mb Apps, 90.51 Available
SD Card .91GB, 67.61mb Apps, (then small stuff,) 537mb available.

I'm wondering if I did something wrong. I think it said it formatted it as Fat32. Don't know if that's a problem. The only reason I used GNM's recovery is because I don't have a card reader.

Tips?