[ICS] [4.0.4] CyanogenMod 9.1 [ROM]

[Guest kyan31]

Is anybody else running cm9 on the 109808 baseband and having any problems with auto brightness?

On mine it seems it will dim the display OK when I come in from outside but refuses to brighten again until I do it manually.

Ben.

OK, how are you running CM9 on the GB baseband? I must of missed something :ph34r:

[Guest Redflake]

Something exciting (maybe) to share!

Since we're basically getting nowhere with an official bootloader unlock from Huawei, I've spent most of today reintroducing support for the 109808 baseband for CM. We obviously had this before, but the difference this time is the 3.0.8 kernel is running on that baseband, meaning we don't have a dodgy 2.6 kernel powering it, and everything is working as you would expect in CM9 R9.

The only differences behind the scenes are a minor kernel hack to provide us with enough framebuffer memory - the bootloader passes the start point and the size of the memory region to be used as framebuffer space, and as Gingerbread required less, the Gingerbread bootloader also provides less to the kernel, too little in fact. Additional changes are more obvious - bypassing a line in the RIL Java class, and replacing all the blobs related to the RIL with their equivalents from 109808.

Right now, this stuff is set up so it can be toggled when building CM9. I've got a test build available here: http://g300.thebrona...5-109808-A1.zip

Now, why would you use this? Well, it bypasses the problem plaguing custom ICS ROMs, the random 3G reboots, since a bootloader "unlock" is necessary to install them. Of course, if you don't have the reboots, then you have no reason to use it at all.

Maybe it's obvious but just in case: you need to be on the 109808 baseband to use the mobile network on it. For the vast majority of people, this probably means you need to downgrade to Gingerbread in order to use it.

...and one final point - don't install any recovery that uses a 3.0.8 kernel (yet) if you are downgrading, as it won't have the framebuffer hack in place that is necessary to bring the display up, so you'll be staring at the Huawei splash screen for quite some time.

Kyan31

Here. you missed this

[Guest kyan31]

Kyan31

Here. you missed this

Thanks :)

[Guest pearsonian]

i have installed the official update today for ics b952,rooted the phone and changed couple of lines in the prop build settings ro.max.fling_velocity 12000 and min 8000 which seemingly has the scrolling improved slightly on the browsers.Had some teething problems in getting 3g to work but resolved it by deleting the apn completely and typing in from scratch again.The phone seems to be alot more responsive than gb ,scrolling is still abit of an issue but in firefox is perfect,but on some apps it still sticks abit.

Can anyone tell me if its worth going ahead installing a custom rom or is b952 a decent build,as far as im concerned the phone is perfect apart from the scrolling issues.

Does jb custom roms offer any improvement or are they still in the experimental stages.

Comments much appreciated.

Edited February 27, 2013 by pearsonian

[Guest tyrol_gangster]

apologies if this has been answered but is there any hope the ultra annoying 'caller ID lag' will be fixed in this (or any other) ROM, please?

[Guest samjam]

Someone just posted a fix to the infusion thread. Modify contacts.jar so that contacts stay in memory.

It would probably fix my SMS compose problem where the recipient enters backwards because the caret keeps moving to the front until the contacts are all loaded

[Guest valy17400]

When i call sometimes i cant understand the other person, the speaker's too bad.

Edited February 28, 2013 by valy17400

[Guest Buffalo Soldier]

So guys are there any new problems with CM9 on 109808 baseband, or is it basically the same as on new baseband?

[Guest miguelf]

When i call sometimes i cant understand the other person, the speaker's too bad.

+1 needs to be fixed!

[Guest bentescort]

So guys are there any new problems with CM9 on 109808 baseband, or is it basically the same as on new baseband?

Running great here. The only issue I have is the light sensor isn't working so automatic display brightness doesn't work.

May be just my phone though as nobody else has reported the problem.

Ben.

[Guest dalyer]

Running great here. The only issue I have is the light sensor isn't working so automatic display brightness doesn't work.

May be just my phone though as nobody else has reported the problem.

Ben.

You might find an app that allows you to test your light sensor and other hardware if that's of any use. For example:

https://play.google.com/store/apps/details?id=dms.pastor.diagnostictools

Hope this helps.

[Guest bentescort]

Thanks for the link, I tried the test on the light sensor and it isn't responding. It seems to be stuck reading 10 lx.

Ben.

[Guest samjam]

I meant services.jar

[Guest dalyer]

Thanks for the link, I tried the test on the light sensor and it isn't responding. It seems to be stuck reading 10 lx.

Ben.

Actually come to think of it I seem to recall that diagnostic application reporting mine to be stuck at 10 even though it does work so maybe that test is not reliable? Sorry... Maybe there's another hardware/light sensor test app out there?

[Guest grmn]

Running great here. The only issue I have is the light sensor isn't working so automatic display brightness doesn't work.

May be just my phone though as nobody else has reported the problem.

Ben.

I got the same problem with auto-brightness since updating to R9.

[Guest yrxe]

Hi,

could someone share another link for download. Seems that original mirror is dead... :(

[Guest Pain_Deluxe]

yeah getcm is temporally offline

[Guest nitso]

thanks for the rom

[Guest antitauon]

I originally used CM 10.0, then 10.1, then I wanted a more 'solid'/stable ROM and went to CM9... but I'm still not quite happy with it.

Whenever I unlock my G300 after some idle period it's just so horribly slow... and yes, this does go away after a while (20 seconds... ish), but it often makes any snappy use of my smartphone impossible. (Like "Let me just quickly look that up... oh wait... not so quickly")

Maybe I'm just asking too much from a phone running ICS with 512 MB of RAM, but maybe you can fix it, and in that case, please do fix it... thanks!

Edited March 4, 2013 by antitauon

[Guest ficko98]

when lg gt540 (180mb ram for user) can run jelly bean very well then g300 can also, and daz is on that way to make it perfect.

[Guest dalyer]

Have you tried other ROMs such as Infusion, Stock+, Slim, Lightning, Meija etc.?

For what it's worth I don't notice such lag on Stock+ so far. I found CM10.1 quite laggy unfortunately.

[Guest Pain_Deluxe]

For Best Multitasking backgrade to Atomic or other GB rom.

But GB is not cool anymore right........

I have use all ICS and JB roms but gb are the fastes

[Guest intensedarkness]

I can confirm I'm also facing the automatic backlight setting not working. Light sensor is stuck at 10 lx too.

Call volume is fine here.

CM9 2030 baseband.

[Guest dalyer]

My light sensor works but I seem to recall Dom's Diagnostic Tools reporting it stuck at 10lux too...

[Guest intensedarkness]

No need for test apps. See Settings->Automatic brightness ->Light levels->Edit other levels in CM9. It tells you in the top left corner. Are people seeing varying readings here?

Also, when putting brightness on automatic, the brightness/backlight levels remain constant. To be clear, the light sensor seems to be reading low light levels, and therefore screen backlight levels remain at the lowest value.

Is anyone here on CM9 R9 actually using automatic brightness where it actually changes according to ambient lighting conditions?

To test this, put brightnes levels on automatic. Then hold it under a bright light and see if screen brightness (ie. screen backlight levels) increases.

Edited March 5, 2013 by intensedarkness