• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [ROM][ALPHA] Triumph CM9 v0.6.17.0 [FINAL]

Anyone have any luck changing the PRL for CM9? I tried the method that requires flashing to stock. I was able to change the PRL in stock and it stuck, verified by status listing. However, when I flashed back to this CM9 alpha, it did not stick: stock PRL was listed in status.

I tried the CM7 quick change. It did seem to put the phone into diagnostic mode when in CM9, but QPST could not write to the phone, always returns the following NV write error: NV_UE_IMEI_I NV_READONLY_S

It could read data from the phone though.

Anyone have success updating the PRL for this ROM? Thanx.
As Mantera said, CM9 is not reading your correct prl.
Flashing a ROM does not change your prl.
If qpst could read from your phone, it almost certainly successfully wrote the prl file to it.
... And you will always get that NV write error. Ignore it.
 
Hey mantera, what's the point to all these tiny kernel version jumps? More features? Are you prepping us for a 3.0 kernel? Thanks for your work.
 
Alpha 0.6.12.1
-enabled btwlancoex for those that want it.

I added this build for those that want the btwlancoex enabled. Only use this build if you want that.
 
Mantera how's the camera development going?

I haven't looked at camera. Not sure if anyone else is. I assume that edowar is still looking into it.


Been looking into a new kernel with most of my time. and updating the current kernel whenever I get tired of playing with the new one.

Hey mantera, what's the point to all these tiny kernel version jumps? More features? Are you prepping us for a 3.0 kernel? Thanks for your work.

I like having the latest versions of stuff and the 2.6.32 kernel's latest version is .59. So just working towards that. There's a lot of fixes in the little increments to to improve the performance/stability of the 2.6.32 kernel.


BTW, in case you all haven't noticed, with the latest improvements in version 0.6.11.x and current, our nenamark2 scores have improved to about 26+ fps from the 23 fps in previous builds.
 
I haven't looked at camera. Not sure if anyone else is. I assume that edowar is still looking into it.


Been looking into a new kernel with most of my time. and updating the current kernel whenever I get tired of playing with the new one.



I like having the latest versions of stuff and the 2.6.32 kernel's latest version is .59. So just working towards that. There's a lot of fixes in the little increments to to improve the performance/stability of the 2.6.32 kernel.


BTW, in case you all haven't noticed, with the latest improvements in version 0.6.11.x and current, our nenamark2 scores have improved to about 26+ fps from the 23 fps in previous builds.

Lolz I totally agree on having the latest versions of stuff. just wish we could get a 3.0 kernel :-)
 
Well we don't exactly need msm 3.0 kernel to get camera, we just need the sources so we can port the drivers(and other stuff) back to our 2.6.32 kernel(soon to be 2.6.35).
Oops mantera, just accidentally spoil your future surprise.
 
As Mantera said, CM9 is not reading your correct prl.
Flashing a ROM does not change your prl.
If qpst could read from your phone, it almost certainly successfully wrote the prl file to it.
... And you will always get that NV write error. Ignore it.

Actually, I just tested this. I used QPST under CM9 Alpha to write 60676 prl using the debug script in terminal emulator. I then restored stock rom. Status indicated that the prl was 60686. This was the file that I first installed using QPST through the stock rom originally. This confirms what you and mantera said about status in CM9 not identifying the actual prl file installed. Unfortunately, it also shows that QPST is not able to write prl files in CM9 - at least not version 6.11. Regrettably, this means the quick perl change for CM7 will not currently work for CM9.
 
i just noticed something very strange and i hope its just me. maybe it's the build, or a little bug in the bigger ics. maybe i did something wrong. i've corrected the problem, but:

i'm using the default email program and just put gmail in there. when i was sending email from my phone the other end saw it as coming from:
MY_PASSWRD <MY_GMAIL_ADDY>

the problem was fixed with a simple look at settings. but, it seems a little scary.

much thanks to mantera and the whole team for all of your work.
 
Is there a way to disable auto-brightness somewhere? I've checked in all the settings and can't find a way to disable it.

Funny, I'm looking for the check box to enable that. Let me know if you find it.
 
Funny, I'm looking for the check box to enable that. Let me know if you find it.

I enabled it when I added the brightness control to the power widget in the status bar. The problem is though, even when I disable it via the widget, CM9 still believes it's turned on so it won't let me enable changing the brightness via dragging across the status bar until I disable it.
 
i just noticed something very strange and i hope its just me. maybe it's the build, or a little bug in the bigger ics. maybe i did something wrong. i've corrected the problem, but:

i'm using the default email program and just put gmail in there. when i was sending email from my phone the other end saw it as coming from:
MY_PASSWRD <MY_GMAIL_ADDY>

the problem was fixed with a simple look at settings. but, it seems a little scary.

much thanks to mantera and the whole team for all of your work.

I just sent an email to myself to and did not encounter a problem like this. It would be a huge problem though if there was such a glitch. Hopefully, it is just an isolated event.
 
Do you mean the android keyboard? If so, activate your desired keyboard from "Language and Input" in settings.

thanks anyways but I meant the setting for the on screen keys like the galaxy nexus has but I figured it out there's a mod on xda that let's me enable it again
 
Back
Top Bottom