Im having trouble installing installing the zip file and i think its because my phone model isnt included in the update script, if im correct can anyone help me with editing the script to get this to install? I dont mind losing my NFC features as its absolutely no use to me anyway.
Need more info just ask cheers
Jay M
btw I installed the latest nightly no problem but MMS wont work on it.
Welcome to CyanogenMod
![]() |
Welcome to our forum. Like most online communities you must register to post, but don't worry this is a simple free process that requires minimal information for you to signup. Be a part of the CyanogenMod Forum by signing in or creating an account. You can even sign in with your Facebook or Twitter account.
|
Guest Message by DevFuse
7 replies to this topic
#1
Posted 15 February 2012 - 01:24 PM
#2
Posted 15 February 2012 - 07:48 PM
Hi,
I had an issue sending mms on my gs2 on O2(uk).
What is actually happening when you try to send an MMS. also what country are you in and network. I have read mms problems are attributed to the kernel being mis matched. Also check the setting for the APN's. the smallest detail can be the cause.
Hope this helps
I had an issue sending mms on my gs2 on O2(uk).
What is actually happening when you try to send an MMS. also what country are you in and network. I have read mms problems are attributed to the kernel being mis matched. Also check the setting for the APN's. the smallest detail can be the cause.
Hope this helps
#3
Posted 22 February 2012 - 02:00 PM
Hello.
First I am new to the forums. Secondly not a coder, but I see you're having the same problem as me. I actually had my Samsung Galaxy S2 delivered this morning, an Orange handset update as it happens, and it turns out the model no. is the same. Therefore, the Cyanogen Mod update I was hoping to install straight away, isn't going to be happening any time soon. Obviously, this sucks immensely, as the stock software is a little bit crap.
Naturally I don't want to be using a nightly build on it if it makes MMS fail, as I literally just switched the SIMS on the network and don't want to be without MMS when out and about.
Any idea when its likely a stable update will be rolled out?
Thanks in advance,
Stew.
First I am new to the forums. Secondly not a coder, but I see you're having the same problem as me. I actually had my Samsung Galaxy S2 delivered this morning, an Orange handset update as it happens, and it turns out the model no. is the same. Therefore, the Cyanogen Mod update I was hoping to install straight away, isn't going to be happening any time soon. Obviously, this sucks immensely, as the stock software is a little bit crap.
Naturally I don't want to be using a nightly build on it if it makes MMS fail, as I literally just switched the SIMS on the network and don't want to be without MMS when out and about.
Any idea when its likely a stable update will be rolled out?
Thanks in advance,
Stew.
#4
Posted 23 February 2012 - 07:41 PM
My handset barely lasted 10 hours today, and most of that was spent in my coat pocket in my works' staff room. I shouldn't have to turn it off, but thanks to Orange's shoddy Android overlay, I might well have to!
Bring on Cyanogen for Samsung Galaxy S2 i900P!
Bring on Cyanogen for Samsung Galaxy S2 i900P!
#5
Posted 24 February 2012 - 10:59 AM
Yesterday, I tried taking the stable build for the GT-i9100, and modifying it by extracting the files, changing the 'assert()' command at the top of META-INF/com/google/android/updater-script to:
And then rezipping.
The resulting package installed correctly, and I have been using it quite heavily since then with no noticeable problems.
Quote
assert(getprop("ro.product.device") == "galaxys2" || getprop("ro.build.product") == "galaxys2" || getprop("ro.product.board") == "galaxys2" ||
getprop("ro.product.device") == "GT-I9100" || getprop("ro.build.product") == "GT-I9100" || getprop("ro.product.board") == "GT-I9100" ||
getprop("ro.product.device") == "GT-I9100M" || getprop("ro.build.product") == "GT-I9100M" || getprop("ro.product.board") == "GT-I9100M" ||
getprop("ro.product.device") == "GT-I9100T" || getprop("ro.build.product") == "GT-I9100T" || getprop("ro.product.board") == "GT-I9100T" ||
getprop("ro.product.device") == "GT-I9100P");
getprop("ro.product.device") == "GT-I9100" || getprop("ro.build.product") == "GT-I9100" || getprop("ro.product.board") == "GT-I9100" ||
getprop("ro.product.device") == "GT-I9100M" || getprop("ro.build.product") == "GT-I9100M" || getprop("ro.product.board") == "GT-I9100M" ||
getprop("ro.product.device") == "GT-I9100T" || getprop("ro.build.product") == "GT-I9100T" || getprop("ro.product.board") == "GT-I9100T" ||
getprop("ro.product.device") == "GT-I9100P");
And then rezipping.
The resulting package installed correctly, and I have been using it quite heavily since then with no noticeable problems.
#6
Posted 24 February 2012 - 07:15 PM
I may have to try this...
FOR SCIENCE!
FOR SCIENCE!
#7
Posted 25 February 2012 - 12:18 AM
I tried this.
Science Failed me. Stuck with the Orange animation followed by the Samsung Galaxy S2 logo on loop D: My phone is borked :'(
Science Failed me. Stuck with the Orange animation followed by the Samsung Galaxy S2 logo on loop D: My phone is borked :'(
#8
Posted 07 March 2012 - 09:05 PM
Crisis averted a few weeks back. Put ICS on the machine and now it purrs like a kitten.












