Jump to content

[ICS] [CM9] [4.0.4] CyanogenMod 9 for the Huawei Ascend G300 [ROM]


Guest Dazzozo

Recommended Posts

Guest maritimesbob

I tried this out last week, very nice. I put the Modaco rom back on, however does anyone find this CM9 port stable enough for every day general use? I appreciate the camera does not work.

Link to comment
Share on other sites

Guest ugnius40

Hi,

I'm using CM9 since it came out, no crashes so far. Minor annoyance - chrome browser exits if you open another tab. Messaging and voice calls are fine.

Link to comment
Share on other sites

Guest Matty-p

I know @skull_fcuk seemed to have got this but I got the following email from android.com shortly after I flashed the rom and registered my account I assume this is normal right as it is a modified nexus s base if it is normal then I think it needs to be noted in the OP so has anyone else got this email even though they haven't got a nexus s?


Google and Samsung have partnered to bring you Nexus S, a pure Google
experience phone. Learn more:
* Register your Nexus S at http://www.samsung.com/us/support/account/regist
* Visit http://www.google.com/nexus/#/help for a full list of help resources
* Watch Nexus S on our YouTube channel at http://www.youtube.com/googlenexus
Once registered, you can contact Samsung directly at +1 855-EZ2NEXUSS
(+1 855-392-6398) for support.
Sign up to to receive updates and promotions about Nexus S at
https://services.google.com/fb/forms/nexussupdates/
Enjoy!
The Android Team at Google
Google, Inc.
1600 Amphitheatre Parkway
Mountain View, CA 94043
----------------------------------------------------------------------
(We sent you this one-time welcome message because you recently
purchased a Nexus S phone)
[/CODE]

Link to comment
Share on other sites

Guest Davidoff59

Yes its fine for everyday use. I'm back on gingerbread at the moment. I flashed ics reloaded which didn't work, then my calls were being routed to external speaker so went back to gingerbread.

Link to comment
Share on other sites

Guest Matty-p

I got that email from Google on the blade ics builds.

Thanks, did you get it on this build? (I need to be sure before adding the warning/notice in the OP)

Link to comment
Share on other sites

Guest Dazzozo

I've flashed this 3 times now in varying different versions and not had the email, though I had it in a build for another phone.

It is not a modified Nexus S base, it is built from source. If more people are encountering this I am capable of adding a "warning" to my own OP. I'm not entirely sure why it needs to be warned, however.

The next build will probably use the B926 market fingerprint, which should eradicate all crespo references.

Link to comment
Share on other sites

Guest Left_hand

New build will probably land today, all being well.

you mean today you will release a new build? if so ,that really a good news!!
Link to comment
Share on other sites

Guest Davidoff59

Can't say I noticed it on this build either. It never bothered me anyway, just made me smile, congratualations on your Nexus purchase lol.

Can't wait Dazzozo

Link to comment
Share on other sites

Guest omegamoon

New build will probably land today, all being well.

Thumbs up! Is this new build based on the B926 image? And if so, does that mean that we got all hardware working? Just curious, that's all :P
Link to comment
Share on other sites

Guest Jekle

Thumbs up! Is this new build based on the B926 image? And if so, does that mean that we got all hardware working? Just curious, that's all :P

Just the appropriate files etc from B926 and the footprint from B926 so its still CM9

Link to comment
Share on other sites

Guest Dazzozo

Not yet, sadly it seems a lot of the hardware issues lie in the kernel which the B926 release can't really help us with. I've updated all the proprietary files with ones contained in B926 though, and it seems to bench a little higher.

I imagine I'll be tracking down some OpenGL problems and Bluetooth for the next build.

Link to comment
Share on other sites

Guest Dazzozo

Has there been any progress on the camera?

Progress, but it's not working yet. B926 gave us updated libs which will come in handy but again problems seem to originate in the kernel.

Link to comment
Share on other sites

Guest omegamoon

Progress, but it's not working yet. B926 gave us updated libs which will come in handy but again problems seem to originate in the kernel.

I haven't looked into this any further, but is this camerawrapper of any help to us?

Logcat output of starting the camera app gives...

D/16:26:25.569 dalvikvm( 1951)

GC_EXPLICIT freed 379K, 20% free 9386K/11591K, paused 3ms+13ms

I/16:26:25.209 Process ( 2469)

Sending signal. PID: 2469 SIG: 9

D/16:26:25.209 AndroidRuntime( 2469)

Shutting down VM

D/16:26:25.209 CameraHAL( 114)

CameraHAL_GetNum_Cameras: loading libcamera at 0x0

W/16:26:24.949 ActivityManager( 205)

Force finishing activity com.android.camera/.Camera

E/16:26:24.939 AndroidRuntime( 2469)

at com.android.camera.Camera$4.run(Camera.java:1167)

E/16:26:24.939 AndroidRuntime( 2469)

at com.android.camera.CameraHolder.instance(CameraHolder.java:66)

E/16:26:24.939 AndroidRuntime( 2469)

at android.hardware.Camera.getCameraInfo(Native Method)

E/16:26:24.939 AndroidRuntime( 2469)

FATAL EXCEPTION: Thread-195

E/16:26:24.929 CameraHAL( 114)

FATAL ERROR: could not dlopen libcamera.so: Cannot load library: load_library[1120]: Library 'libcamera.so' not found

I/16:26:24.749 ActivityManager( 205)

Start proc com.android.camera for activity com.android.camera/.Camera: pid=2469 uid=10009 gids={1006, 1015}

I/16:26:24.659 ActivityManager( 205)

START {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10000000 pkg=com.android.camera cmp=com.android.camera/.Camera} from pid 1951

I/16:26:24.649 AudioPolicyManager( 114)

startOutput() output 1, stream 1, session 125

Edited by omegamoon
Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

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