[ROM][BETA] Quattrimus ICS

[emburybrett1]

Okay now I got a question for you guys. I've been having a problem with reboots when i'm using 3G. I know a few of you mentioned different gov's and oc's that seemed to slow it or stop it, and i've tried a few market apps for signal tweaks and such, but I'm just not having any luck with it. That is really the only major problem i've had since I got the phone replaced last month though...even managed to get it to let me oc it without it rebooting constantly!

I wouldnt say some many thing are wrong with this rom they call it "Trolling" and its 10 point at 100 point they remove you from the site.

 

[Rudeco]

OK I've always used the same combination and have never had any of the reboot issues most complain about.
Flash rom
Flash gapps
Flash the egl patch
Then flash amphetamines
I run savagedzen with 480/748
Now as always, not all V's were created equal.
For mine, this has worked best.

Sent from my PC36100 using Tapatalk 2

What and where can I find the EGL patch?

Sent from my LG-VM670 using Tapatalk 2

 

[cbucz24]

http://forums.androidcentral.com/showthread.php?t=187973


Sent from my PC36100 using Tapatalk 2

 

[HavocX]

I'm starting to get frustrated....I cant seem to stop my whole battery drain or reboot issue with either cm9 or aokp....i have tried just about every cpu setting suggested....i went back to cm7 but honestly after cm9 and aokp i do NOT like cm7 because it is lacking the customization features i like....if anyone can help me figure out how i can make the battery last more than 3 hours and stop the reboots i would appreciate it...I barely have any apps installed so i dont think that i have one running to drain the battery

Mine lasts all day. Sometimes I forget to plug it in at night and its still half charged in the morning. Might be the hardware.

 

[strabo231]

OK I've always used the same combination and have never had any of the reboot issues most complain about.
Flash rom
Flash gapps
Flash the egl patch
Then flash amphetamines
I run savagedzen with 480/748
Now as always, not all V's were created equal.
For mine, this has worked best.

Sent from my PC36100 using Tapatalk 2

Actually just flashing that patch made a huge difference by itself made a huge difference. I'll just try to tweak some settings and stuff a little now. Thanks man

Sent from my LG-VM670 using Tapatalk 2

 

[reverendjoe]

Great battery life + stability with cm9 beta 2. However, I've never had success with any governers but interactiveX, and am wondering why I often hear savagedzen is recommended. I'm not contesting anyone, just curious as to what it is about that governer that makes it recommended. Always been very stable at 320/787 interactive and this gives excellent battery as well.
Love tdm and all devs, thank you for your time, effort, and contributions to this community.

 

[HurrrDurrrDURP]

TDM will you be making a new build with the lastest CM9 source? So we can rule out if it was the kernel glitching and not CM9?

 

[tdm]

TDM will you be making a new build with the lastest CM9 source? So we can rule out if it was the kernel glitching and not CM9?

I'll check but I don't think anything relevant changed from beta2.

 

[cbucz24]

Great battery life + stability with cm9 beta 2. However, I've never had success with any governers but interactiveX, and am wondering why I often hear savagedzen is recommended. I'm not contesting anyone, just curious as to what it is about that governer that makes it recommended. Always been very stable at 320/787 interactive and this gives excellent battery as well.
Love tdm and all devs, thank you for your time, effort, and contributions to this community.

http://forum.xda-developers.com/showthread.php?p=28647926

This thread explains all governors.

Sent from my PC36100 using Tapatalk 2

 

[HurrrDurrrDURP]

Good new everyone! I found the reason why voice search is broken on our phones!

It seems the AMR encoder(The software used to record our voice) seems to be throwing an error every time it is initialized!

tdm do you think this could be fixed or find a work around?

Full log cat

I/AudioHardwareMSM72XX( 1745): do input routing device 400000
I/AudioHardwareMSM72XX( 1745): Routing audio to Speakerphone
D/AudioHardwareMSM72XX( 1745): doAudioRouteOrMute() device 0, mMode 0, mMicMute 1, mBuiltinMicSelected 1, muted
I/AudioService( 1863):  AudioFocus  requestAudioFocus() from android.media.AudioManager@40de8e38com.google.android.voicesearch.speechservice.GrecoRecognizer$1@40dea608
I/AudioHardwareMSM72XX( 1745): do input routing device 400000
I/AudioHardwareMSM72XX( 1745): Routing audio to Speakerphone
D/AudioHardwareMSM72XX( 1745): doAudioRouteOrMute() device 0, mMode 0, mMicMute 1, mBuiltinMicSelected 1, muted
I/ConnectionFactoryImpl( 2608): Opening SSL connection: vs.google.com:14259
I/MicrophoneInputStream( 2608): #close - audio release
I/AudioHardwareMSM72XX( 1745): do input routing device 400000
I/AudioHardwareMSM72XX( 1745): Routing audio to Speakerphone
D/AudioHardwareMSM72XX( 1745): doAudioRouteOrMute() device 0, mMode 0, mMicMute 1, mBuiltinMicSelected 1, muted
I/AudioHardwareMSM72XX( 1745): set device to SND_DEVICE_SPEAKER device_id=0
I/AudioHardwareMSM72XX( 1745): Enabling post proc features with mask 0x0000
D/dalvikvm( 1863): GC_EXPLICIT freed 593K, 43% free 5370K/9351K, paused 8ms+38ms
I/RecognitionEngineRetrier( 2608): #onError - notify
I/AudioService( 1863):  AudioFocus  abandonAudioFocus() from android.media.AudioManager@40de8e38com.google.android.voicesearch.speechservice.GrecoRecognizer$1@40dea608
E/UberRecognizerController( 2608): onError
E/UberRecognizerController( 2608): com.google.android.voicesearch.speechservice.connection.AudioRecognizeException: Error thrown by AMR encoder
E/UberRecognizerController( 2608): 	at com.google.android.voicesearch.speechservice.NetworkRecognitionEngine.startSendLoop(NetworkRecognitionEngine.java:153)
E/UberRecognizerController( 2608): 	at com.google.android.voicesearch.speechservice.NetworkRecognitionEngine.internalStartRecognition(NetworkRecognitionEngine.java:129)
E/UberRecognizerController( 2608): 	at com.google.android.voicesearch.speechservice.NetworkRecognitionEngine.startRecognition(NetworkRecognitionEngine.java:84)
E/UberRecognizerController( 2608): 	at com.google.android.voicesearch.speechservice.RecognitionEngineWrapper.startRecognition(RecognitionEngineWrapper.java:50)
E/UberRecognizerController( 2608): 	at com.google.android.voicesearch.speechservice.RecognitionEngineRetrier.startRecognition(RecognitionEngineRetrier.java:93)
E/UberRecognizerController( 2608): 	at java.lang.reflect.Method.invokeNative(Native Method)
E/UberRecognizerController( 2608): 	at java.lang.reflect.Method.invoke(Method.java:511)
E/UberRecognizerController( 2608): 	at com.google.android.voicesearch.util.ThreadChanger$1$1.run(ThreadChanger.java:63)
E/UberRecognizerController( 2608): 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442)
E/UberRecognizerController( 2608): 	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:305)
E/UberRecognizerController( 2608): 	at java.util.concurrent.FutureTask.run(FutureTask.java:137)
E/UberRecognizerController( 2608): 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:150)
E/UberRecognizerController( 2608): 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:264)
E/UberRecognizerController( 2608): 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1076)
E/UberRecognizerController( 2608): 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:569)
E/UberRecognizerController( 2608): 	at java.lang.Thread.run(Thread.java:856)
E/UberRecognizerController( 2608): Caused by: java.io.IOException: couldn't start recording, state is:1
E/UberRecognizerController( 2608): 	at com.google.android.voicesearch.endpointer.MicrophoneInputStream.ensureStarted(MicrophoneInputStream.java:92)
E/UberRecognizerController( 2608): 	at com.google.android.voicesearch.endpointer.MicrophoneInputStream.read(MicrophoneInputStream.java:127)
E/UberRecognizerController( 2608): 	at com.google.android.voicesearch.endpointer.BluetoothAwareMicrophoneInputStream.read(BluetoothAwareMicrophoneInputStream.java:82)
E/UberRecognizerController( 2608): 	at com.google.common.io.ByteStreams.read(ByteStreams.java:806)
E/UberRecognizerController( 2608): 	at com.google.android.voicesearch.audio.reader.Tee.fillBuffers(Tee.java:257)
E/UberRecognizerController( 2608): 	at com.google.android.voicesearch.audio.reader.Tee.get(Tee.java:171)
E/UberRecognizerController( 2608): 	at com.google.android.voicesearch.audio.reader.Tee$TeeInputStream.read(Tee.java:368)
E/UberRecognizerController( 2608): 	at java.io.InputStream.read(InputStream.java:163)
E/UberRecognizerController( 2608): 	at com.google.android.voicesearch.speechservice.AudioSource.captureLoop(AudioSource.java:89)
E/UberRecognizerController( 2608): 	at com.google.android.voicesearch.speechservice.AudioSource.access$000(AudioSource.java:25)
E/UberRecognizerController( 2608): 	at com.google.android.voicesearch.speechservice.AudioSource$1.run(AudioSource.java:63)
E/UberRecognizerController( 2608): Got error after recognizing []
I/AudioHardwareMSM72XX( 1745): set device to SND_DEVICE_SPEAKER device_id=0
I/AudioHardwareMSM72XX( 1745): disabling post proc features with mask 0x0000

I/AudioService( 1863): AudioFocus abandonAudioFocus() from android.media.AudioManager@40de8e38com.google.android.voicesearch.speechservice.GrecoRecognizer$1@40dea608
E/UberRecognizerController( 2608): onError
E/UberRecognizerController( 2608): com.google.android.voicesearch.speechservice.connection.AudioRecognizeException: Error thrown by AMR encoder

 

[tdm]

Thanks, I'll take a look.

 

[drm1992]

Havent been on for a while but I guess mms is broken on nightly 7/31 aokp. Go SMS as a work around. Could it be a bad flash caused by a dirty flash?

Sent from my LG-VM670 using Tapatalk 2

 

[jccjr1982]

I think I uncovered another bug: When you try to send a text message over 160 characters, it will attempt to send, but error out instead of automatically sending multiple texts (as stock or IHO roms did). So basically truncate or cut n paste half the message to new text. This issue is on AOKP; haven't tested it on CM.

I absolutely love this ROM. I tried going back to IHO roms until at least the video and deep sleep problems are fixed, but I've gotten too accustomed to and came running back. Seriously once the current known bugs are fixed, this rom will be PERFECT for this phone and I can't see why anyone would want to use anything else. Keep up the great work tdm!

 

[strabo231]

I think I uncovered another bug: When you try to send a text message over 160 characters, it will attempt to send, but error out instead of automatically sending multiple texts (as stock or IHO roms did). So basically truncate or cut n paste half the message to new text. This issue is on AOKP; haven't tested it on CM.

I absolutely love this ROM. I tried going back to IHO roms until at least the video and deep sleep problems are fixed, but I've gotten too accustomed to and came running back. Seriously once the current known bugs are fixed, this rom will be PERFECT for this phone and I can't see why anyone would want to use anything else. Keep up the great work tdm!

Maybe a dumb question, but did you select the split setting for messages over 160 characters in the messaging settings?

Sent from my LG-VM670 using Tapatalk 2

 

[drew_t]

Great battery life + stability with cm9 beta 2.

Same here, for what it's worth. Battery life is at least as good as stock or Backside. I don't overclock; I leave the performance settings at the defaults. AFAIK, no spontaneous reboots since I flashed the Beta 2.


Sent from my LG-VM670 using Tapatalk 2

 

[bennettg]

Did the final cm fix the hotspot problem?

 

[chcub1]

Uh, just wondering how do we know if there's an update to the ROM? And how do you install it?

 

[rmwutr]

my phone freezes up at random things like checking messages, or email, etc and I have to take the battery out to restart. pressing power button doesn't help. This also happens when it's on sleep and I get a text or a call or something.

Is this a known bug and is there any fix? any help would be appreciated. I love this ROM and want to keep it.
Thanks

 

[nitestalkr]

Uh, just wondering how do we know if there's an update to the ROM? And how do you install it?

You install it just as any other rom, and you check the host sites for updates.

sent from my G-T-R Reloaded V

 

[andrewnelson23]

@tdm. Is there any chance you could make a button combo for screenshots?