Jump to content

[ICS] [4.0.4] CyanogenMod 9.1 [ROM]


Guest Dazzozo

Recommended Posts

Guest Feahnor

I'm not hacking the CM source unnecessarily for some dumb gimmick. If it was soooo good, it would be in CM by default.

Comprende?

Well, it IS so good. Did you try it?. It's as smooth as iphone's.

Maybe a patch?

Edited by Feahnor
Link to comment
Share on other sites

Guest Dazzozo

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.thebronasium.com/tmp/cm-9-20130220-EXPERIMENTAL-u8815-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.

Link to comment
Share on other sites

Guest jsevi83

Thank you very much, Daz. The new build for 109808 baseband is working perfect, at least as good as CM9 R9. I recommend it to all those who have reboots in ics. You can use IMEI-Hack-Tool to downgrade to B895, then install CWM5, and then install this. Also, kra1o5 made a new test build of TWRP using Daz patch to make it work in 109808 baseband. I just tried it and it is working very good also, so thanks to kra1o5 and Daz again for this. Here is the zip http://www.mediafire.com/?ztjey5dxwjoo4eq

Link to comment
Share on other sites

Guest hippy dave

Yes this cm9 build does seem very good. I haven't tried any of the more recent builds, since cm10 came out, but the performance of this one seems very good so far, haven't yet encountered the random crippling lags I was getting on jellybean, and the keyboard & multitasking are behaving well. So far it's almost as responsive as cm7, and is much nicer for features, so gonna stick with it and hope it stays that way. :)

Link to comment
Share on other sites

Guest Dazzozo

Regarding 109808, I'm not sure of the best course of action regarding builds. I obviously can't put both builds (for 109808 and 2030) under the same device on GetCM as that would cause chaos with OTA updates. I think it's a bit unreasonable to expect everyone to downgrade, but clearly it's unreasonable for people to have to put up with the 3G reboots (and they have been some time, and for that, I congratulate you :P)

All I can think of is splitting the device in two on GetCM and having u8815_2030 and u8815_109808, so people are in their separate channels and updates are pushed out simultaneously, but that seems unnecessarily complex.

Of course the best solution would be Huawei providing us with an official bootloader unlock method in the first place. :P

Link to comment
Share on other sites

Guest jsevi83

Splitting the device in two on GetCM would be the best solution, I hope that's not too much work for you. Once again, Huawei fails and Daz comes to the rescue!

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

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