Database Info

Wifi calling, MIUI, and CM7

Okay so I Wifi calling doesn't work on MIUI because of the newer sim card, but CM7 does work and MIUI is CM7 based.
But the miui build for g2x comes from a native CM7. My guess is that something is done to CM7 to get it working in the g2x code tree that could be done to the miui g2x port?
I will research it, but there might be coders that have better resources than I do.
Either way, this has to be possible and we should make it happen.
Sent from my LG-P999 using XDA App

+1
Sent from my LG-P999 using xda premium

derekedw said:
Okay so I Wifi calling doesn't work on MIUI because of the newer sim card, but CM7 does work and MIUI is CM7 based.
But the miui build for g2x comes from a native CM7. My guess is that something is done to CM7 to get it working in the g2x code tree that could be done to the miui g2x port?
I will research it, but there might be coders that have better resources than I do.
Either way, this has to be possible and we should make it happen.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Sadly it doesn't work that way. Developers tried everything. But we're not stopping till we get it working.

G2x doesn`t get along with the newer sim cards! I changed 10 sims for 2 weeks until I found Sim TM9073. This is the right sim for our phone! Wifi Calling is flawless with it! I`ve been using CM7 since I got the phone last summer!
It`s not easy to find that specific sim card, when you tell the people at the store what you are looking for, they don`t really know what you are talking about....

all reps I spoke to months ago said they don't make the old sim cards anymore so you wont be able to get one from a store. I was able to grab a brand new old style sim fro. ebay and solved my wifi calling problem months ago hit up ebay and see if you can find one. make sure its brand new never been activated.

derekedw said:
Okay so I Wifi calling doesn't work on MIUI because of the newer sim card, but CM7 does work and MIUI is CM7 based.
But the miui build for g2x comes from a native CM7. My guess is that something is done to CM7 to get it working in the g2x code tree that could be done to the miui g2x port?
I will research it, but there might be coders that have better resources than I do.
Either way, this has to be possible and we should make it happen.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Wi-Fi calling is working perfectly on miui, it has nothing about newer SIM !

cgigate said:
Wi-Fi calling is working perfectly on miui, it has nothing about newer SIM !
Click to expand...
Click to collapse
You got Wifi calling to run on MIUI with new sim card? Please tell how...I have tried installing the wifi calling apk to /data/app and also tried pushing it to /system/app and got nothing but FC's either way...someone please enlighten me here. Thanks!

pettigrew95 said:
You got Wifi calling to run on MIUI with new sim card? Please tell how...I have tried installing the wifi calling apk to /data/app and also tried pushing it to /system/app and got nothing but FC's either way...someone please enlighten me here. Thanks!
Click to expand...
Click to collapse
I've heard that if you have a T-Mobile tech support rep use the command "Send MSISDN To SIM" which is located in IHLR (or it was when I used to work there years ago), that it will fix it. However, I have not wanted to navigate their now horrible phone support to get far enough to have someone do it.

Are you guys using t-Mobile wi-fi calling app or something else?
Sent from my MIUI LG-P999 using Xda Premium

"G2x doesn`t get along with the newer sim cards! I changed 10 sims for 2 weeks until I found Sim TM9073."
Mine is Tm9073 but MIUI is not working but its working for my wife's G2x.
So SIM TM9073 is not guaranteed.
So for now: I am using CM7 (nightly) until this is fixed.

alright. i'm not a android dev (i am a programmer but another language than java). here is what i found in my testing and how i was able to get wifi to work..perhaps others can confirm. the problem is delvik cache and wifi being enabled when the phone is restarted.
here is how i was able to get wifi to work on mine consistently (some of the miui dev should take it from here and see if they can resolve the issue).
1) turn off wifi on the phone
2) shut down phone
3) boot into clockwork mod
4) clear delvik
5) reboot phone
6) enable wifi
7) wifi calling works
you will have to do this every time you reboot the phone otherwise wifi calling will not work.
i also tried to see if the issue was resolved by "fix permissions" and it was not. here were my test (also note..when i say reboot recovery...i shut down the phone then go to recovery..not recovery from restart script).
1) wifi on...reboot recovery..delvik clear..reboot-- no wifi calling (invalid sim)
2) wifi on..reboot recovery..permission fix..reboot -- no wifi calling (invalid sim)
3) wifi on..reboot recovery..delvik clear + permission fix..reboot -- no wifi calling (invalid sim)
4) wifi off..reboot recovery..delvik clear..reboot = WIFI calling
i going to also try the following
wifi off..reboot recovery..fix permission..reboot and see if that does anything.
**update** wifi off...reboot..-- just did this one and wifi calling doesn't work..invalid sim.
and i'm going to assume that if you do both with wifi off it will work.
a possible solution: someone create a script for shutdown/restart that turns off wifi (also save a variable stating that wifi was enabled) and also create a script for startup that clears delvik and enables wifi if it was on previously (not sure if you can save a variable on the next reload).
Update: this last go around was strange...i think there is also something with the state of wifi at the time the phone is rebooted. if you never turn on wifi then different settings need to be changed at bootup. i'll mess with it some more to confirm.

That didnt work for me......

lithivm said:
That didnt work for me......
Click to expand...
Click to collapse
what were your exact steps? did you have wifi ON when you turned off your phone? if not you will have to do a 2nd wipe with wifi OFF then turn on wifi. Its very finicky but it does work.
The last version 2.1.20 works the first time but messes up when you reboot unless you do wipe of delvik cache. I would also wipe cache aswell.
if you leave your wifi on, then just a single wipe works..if you are messing with your wifi to on and off state it sometimes require 2 wipes...with the same wifi state on the reboot (hope that makes sense).

jblah said:
what were your exact steps? did you have wifi ON when you turned off your phone? if not you will have to do a 2nd wipe with wifi OFF then turn on wifi. Its very finicky but it does work.
The last version 2.1.20 works the first time but messes up when you reboot unless you do wipe of delvik cache. I would also wipe cache aswell.
if you leave your wifi on, then just a single wipe works..if you are messing with your wifi to on and off state it sometimes require 2 wipes...with the same wifi state on the reboot (hope that makes sense).
Click to expand...
Click to collapse
This method confirm works.
The wifi calling can be turned on but could not be turned off.it still shows as invalid sim so i could not change the state of the on off switch.

What got to work for me was this:
With Wifi turned-off, Reboot straight into Recovery
Wipe Dalvik Cache in Advance Settings 3x (Three Times)
Hopefully when you reboot and you click on the Wifi Calling app it says either Turned OFF or Disabled. That's how you know you won't get the INVALID SIM error.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If it says Checking Sim, Then Repeat the Steps above again and it may take a couple tries which I had to do cause it didn't do it the first.
I remember back in the days of when MIUI first came out and I had a N1 & an NS the guys at MIUIandroid would recommend wiping 3x whenever you do updates. I guessing because a single wipe for some reason still leaves something behind.
Try That Out Fellows and Hopefully It works for some of you.

GFam4 said:
What got to work for me was this:
With Wifi turned-off, Reboot straight into Recovery
Wipe Cache 3x (Three Times) in CWM
Wipe Dalvik Cache in Advance Settings 3x
Format Cache 3x in Mounts
Hopefully when you reboot and you click on the Wifi Calling app it says either Turned OFF or Disabled. That's how you know you won't get the INVALID SIM error.
If it says Checking Sim, Then Repeat the Steps above again and it may take a couple tries which I had to do cause it didn't do it the first.
I remember back in the days of when MIUI first came out and I had a N1 & an NS the guys at MIUIandroid would recommend wiping 3x whenever you do updates. I guessing because a single wipe for some reason still leaves something behind.
Try That Out Fellows and Hopefully It works for some of you.
Click to expand...
Click to collapse
do you have problems on reboot? or does it stay consistent?
also when you say wipe 3x are you saying BEFORE you install the ROM or after you install it and see that you have "invalid sim"?

jblah said:
do you have problems on reboot? or does it stay consistent?
also when you say wipe 3x are you saying BEFORE you install the ROM or after you install it and see that you have "invalid sim"?
Click to expand...
Click to collapse
With MIUI Rom you kinda have to expect inconsistency. If you've been following any Wifi Calling topic for the G2X with MIUI ROM you know its 50/50.
My Scenario basically is saying that If you currently are running MIUI Rom and IF it worked after intial install. Then when you rebooted (for whatever reason) and you get the Dreaded "Invalid Sim" error then my Steps that i followed helped me to get my Wifi Calling to work again.
The 3x wipe is after the install of rom if you lost the ability to use Wifi Calling. Now it doesn't hurt to do it (3x wipe) before if It may help you get Wifi Calling to work.

Just tried it again with just Wiping Dalvik Cache 3x in Clockwork Recovery. It was a success!! This is the 5th time I've tried it and hasn't failed yet.
I am currently running Stormmagedon's MIUI 2.1.20 with Faux .48 kernel and I have sim card # TM9073
Hope This Helps Someone.

GFam4 said:
Just tried it again with just Wiping Dalvik Cache 3x in Clockwork Recovery. It was a success!! This is the 5th time I've tried it and hasn't failed yet.
I am currently running Stormmagedon's MIUI 2.1.20 with Faux .48 kernel and I have sim card # TM9073
Hope This Helps Someone.
Click to expand...
Click to collapse
Are you wiping after each reboot? also at the time of reboot are you leaving wifi on or off? i got it to work but i think i'll have to keep wiping at every reboot. also since we are on miui...i don't have a camera app anywhere (using stock miui.us)..what is everyone using as their camera app for miui?

jblah said:
Are you wiping after each reboot? also at the time of reboot are you leaving wifi on or off? i got it to work but i think i'll have to keep wiping at every reboot. also since we are on miui...i don't have a camera app anywhere (using stock miui.us)..what is everyone using as their camera app for miui?
Click to expand...
Click to collapse
Yes if you reboot your phone you will have to do the 3x wipe of dalvik cache again. I usually just leave my phone on all the time. I've been doing this with Wifi Off dunno if it makes any difference if ON or OFF. As far as camera, i have both CM7 & MIUI cam. Check the other Roms out there. Im on Stormageddon 2.1.20 and he has both cameras and Wifi Calling. Some MIUI roms leave out the Wifi Calling because of the issues.
Hope This Helps.

just installed latest cm nightly from rom manager

just installed the latest cm 10 nightly from rom manager now when i boot my phone get a screen says system software not authorized by verizon wireless has been found on your phone please turn off your phone and go to the nearest verizon wireless store for help.

mikeew83 said:
just installed the latest cm 10 nightly from rom manager now when i boot my phone get a screen says system software not authorized by verizon wireless has been found on your phone please turn off your phone and go to the nearest verizon wireless store for help.
Click to expand...
Click to collapse
Did you unlock your bootloader?

yep
I rooted it then i used ezunlock went thru successfully it stated i then backed up my stock rooted and did the rest of of normal wen in to rom manager downloaded did a full wipe dalivk cache data etc and then phone installed and rebooted to that verizon warning screen talk about big brother much.

Had the same issue setting up my bro's galaxy yesterday. I had to flash back to stock via Odin and then I just redid root and unlock boot loader and haven't had issue since. Running the new d2vzw euroskank right now with no issues.

yea
I figured as much i was downloadin the files had to run out so just switched devices real fast while i fix it figure ill just start from scratch once i odin back to stock.

Marcismo55 said:
I wouldn't run the official nightlies for the time being until the data and MMS fixes get approved and merged. CVPS (Austin Dickenson) posted an Alpha 2 on his G+ with those fixes above so you would be better off running those.
Click to expand...
Click to collapse
sent from my unlocked bootloader Verizon Samsung galaxy s III

mikeew83 said:
I rooted it then i used ezunlock went thru successfully it stated i then backed up my stock rooted and did the rest of of normal wen in to rom manager downloaded did a full wipe dalivk cache data etc and then phone installed and rebooted to that verizon warning screen talk about big brother much.
Click to expand...
Click to collapse
You need to UNLOCK your bootloader not just root. the official CM is a non kexec kernel and you are still running with your locked bootloader

and fixed
just funny to me how far verizon will go to feel like big brother so to speak.

Assuming your bootloader is unlocked. I had the same thing happen the first time. Tried to use CWM, missed the suggestion of flashing TWRP from EZ Recovery. Made all the difference. Watch the video from DroidModd3rX:
Verizon Galaxy S3 Cyanogen Mod 10 Unofficial NONKEXEC Install (I can't post links yet, sorry)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SCH-I535 using xda app-developers app

is it suitable for daily use??

jasembiz said:
is it suitable for daily use??
Click to expand...
Click to collapse
Depends on what you use the phone for. NFC still isn't working, which affects me. I hear NFL Mobile and some of the video apps like netflix aren't working.
Other than that, it's stable and fast.

I had more then just those issues, apparently my phone was sending doubles text messages, also WiFi struggled to keep a solid signal, data also dropped in and out and last but not least screen would flicker. Did a clean install of the nightly build and alpha build and had the same issues.
Sent from my SCH-I535 using xda app-developers app

jasembiz said:
is it suitable for daily use??
Click to expand...
Click to collapse
I am happy with it. It has rebooted twice on me, once after an hour and a half phone call with Dell tech support, I was tired of talking to the guy anyway . But jelly bean is nice, if you don't need NFC, MMS, or Flash (can't get my side load to work). Guess it is all in the eye of the beholder, if you don't mind some of those issues is suitable.
Sent from my SCH-I535 using xda app-developers app

Mms is working fine as well as flash. What build are you on?
SGS3 production

zxsix said:
Depends on what you use the phone for. NFC still isn't working, which affects me. I hear NFL Mobile and some of the video apps like netflix aren't working.
Other than that, it's stable and fast.
Click to expand...
Click to collapse
Not quite stable. It suffers from reboots for some during/after calls..... Me for one. The original alpha build never showed that symptom. Also a lot of people are saying that they are having echo problems on calls.
TAPPED in on my (now unlocked bootloader) Verizon S3

Did the same thing
jasembiz said:
is it suitable for daily use??
Click to expand...
Click to collapse
I'm hosed. I have been trying to fix it with Odin but I don't know Odin well enough. I ran the stock root rom and then synergy. Last night I locked it by using the CW app instead of the manual method. Dang. How do I return to stock? Anyone? I used Odin to download the rooted rom, and had no issues with TWRP. I should have known better than to use CW recovery app and the CW recovery.

Nice !

same issue
bluetoast said:
I'm hosed. I have been trying to fix it with Odin but I don't know Odin well enough. I ran the stock root rom and then synergy. Last night I locked it by using the CW app instead of the manual method. Dang. How do I return to stock? Anyone? I used Odin to download the rooted rom, and had no issues with TWRP. I should have known better than to use CW recovery app and the CW recovery.
Click to expand...
Click to collapse
Hi. I downloaded and installed the nightly CyanogenMod 10 build and on reboot I'm getting the same error: System software not authorized by Verizon. How did you get past this?

rmcneely said:
Hi. I downloaded and installed the nightly CyanogenMod 10 build and on reboot I'm getting the same error: System software not authorized by Verizon. How did you get past this?
Click to expand...
Click to collapse
derp....unlock your bootloader!

droidstyle said:
derp....unlock your bootloader!
Click to expand...
Click to collapse
but how?? can't get past this unauthorized software screen

[Q] Have IMEI number, but lost phone number after flashing

I did a full wipe and flashed the CM10.1 nightly released for the d2vzw this morning. When it rebooted I had no cell service. Looking in settings i have the proper IMEI number but my cell number is listed as 000-000-1361, MIN is 1361, PRL is 1. what can I do to fix it? I tried restoring a nandroid but the result is the same. Any help would be greatly appreciated!

RESOLVED
james3kral said:
I did a full wipe and flashed the CM10.1 nightly released for the d2vzw this morning. When it rebooted I had no cell service. Looking in settings i have the proper IMEI number but my cell number is listed as 000-000-1361, MIN is 1361, PRL is 1. what can I do to fix it? I tried restoring a nandroid but the result is the same. Any help would be greatly appreciated!
Click to expand...
Click to collapse
Okay so i believe this was my fault for flashing the latest cm 10.1 nightly with my build.prop edited to galaxy nexus values to allow google wallet functionality. removing sim card, starting phone, shutting down phone, inserting sim card, and starting phone fixed the problem

james3kral said:
Okay so i believe this was my fault for flashing the latest cm 10.1 nightly with my build.prop edited to galaxy nexus values to allow google wallet functionality. removing sim card, starting phone, shutting down phone, inserting sim card, and starting phone fixed the problem
Click to expand...
Click to collapse
I ran into the same problem but after trying you fix I still have no service. ?????

TheBurgh said:
I ran into the same problem but after trying you fix I still have no service. ?????
Click to expand...
Click to collapse
I am having the same problem. The phone wont still activate. Please help!!

james3kral said:
Okay so i believe this was my fault for flashing the latest cm 10.1 nightly with my build.prop edited to galaxy nexus values to allow google wallet functionality. removing sim card, starting phone, shutting down phone, inserting sim card, and starting phone fixed the problem
Click to expand...
Click to collapse
Any one try Odin back to stock?

I have a similar issue and I have been going around and around with it without any luck. I restored my latest backup and I still have 000-000-3257 with a PRL of 1. I will try the ops recommendation and will report back.
Odin to stock is my next move unless someone else can think of something else to try.

Try clearing dalvik cache in recovery. Fixed it for me on AOKP. Had the exact same thing where my phone number was a bunch of zeroes. Still had service though when I hit the home button to bypass the activation screen.
Sent from my SCH-I535 using Tapatalk 2

I tried to remove the sim, and boot, and readd the sim and boot but no go. I will try it again but then I think I am going back to stock to see if that works.

Everything still works fine. No need to get worried......it just doesn't report your phone number accurately. Its not like it actually effects functionality. I ran it with an f'ed phone number for 3 days. Everything ran fine. Don't sweat it. If its a problem, wait until tomorrows official nightly comes out tonight and you'll be set.

TechSavvy2 said:
Everything still works fine. No need to get worried......it just doesn't report your phone number accurately. Its not like it actually effects functionality. I ran it with an f'ed phone number for 3 days. Everything ran fine. Don't sweat it. If its a problem, wait until tomorrows official nightly comes out tonight and you'll be set.
Click to expand...
Click to collapse
My issue is it is affecting my functionality. My phone is not working and whenever I call out I get a generic message saying my phone is not active.
I restored a backup from when I first rooted. Now my phone number is listed properly and when I get into a 4G coverage area I can get data, but I still can't call out and it shows I am roaming when I am in a 3G area.

OP on CM10.1 says that dirty flashing Unofficial 10.1 build 12/17/12 will restore data. Any luck with this fix?
Sent from my SCH-I535 using xda app-developers app

dknell said:
OP on CM10.1 says that dirty flashing Unofficial 10.1 build 12/17/12 will restore data. Any luck with this fix?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
you can try that or mastamoons both have been reported to work
mastamoon said:
Here is my unofficial 10.1 build as of 3:00pm EST.
Has working data and increased MMS picture size mod. Otherwise is stock CM10.1
http://bit.ly/12yrtcw
Click to expand...
Click to collapse
Droosh said:
Thanks for sharing! I did a full data wipe and installed this and it activated right away.
Click to expand...
Click to collapse

I was very unlucky and the dirty flash didnt work for me. However, I did have a backup of my IMEI and was able to flash it back to my phone.

I ran into the same problem after flashing 10.1... lost IMEI and stuck on roaming, had no backup.
To fix it i did the following
1) Odin back to stock
2) use this tool http://forum.xda-developers.com/showthread.php?t=1867442
3) reprovish the phone using this code in the dialer *2767*3855#
IMEI restored and no longer on roaming

brandao.gabe said:
I ran into the same problem after flashing 10.1... lost IMEI and stuck on roaming, had no backup.
To fix it i did the following
1) Odin back to stock
2) use this tool http://forum.xda-developers.com/showthread.php?t=1867442
3) reprovish the phone using this code in the dialer *2767*3855#
IMEI restored and no longer on roaming
Click to expand...
Click to collapse
THANK YOU!. I could not get the IMEI/ERI tool to work, but I did get *2767*3855# code to work. I had to roll back to a older version of the official rom (I think rolling back the radio would have been OK) but I am not up and working.

fowen said:
THANK YOU!. I could not get the IMEI/ERI tool to work, but I did get *2767*3855# code to work. I had to roll back to a older version of the official rom (I think rolling back the radio would have been OK) but I am not up and working.
Click to expand...
Click to collapse
I flashed back to stock as well and then used the same number to reprovision. After that everything worked fine it fixed the roaming, incorrect number, PRL, and all. I never lost my IMEI so I didnt do that step. but if you flash back to the cm 10.1 before they fix the data it will happen again :laugh:

Please read forum rules before posting
Questions go in Q&A
Thread moved

Just change CDMA subscription to ruim/sim and toggle airplane mode...
I've never found a reason to have to Odin to anything.
Sent from my SCH-I535 using xda app-developers app

ajrty33 said:
Just change CDMA subscription to ruim/sim and toggle airplane mode...
I've never found a reason to have to Odin to anything.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I can't remember for sure, but I think that is something that the VZW tech had me do, and it didn't work. Maybe someone else who is having the issue can test and comment.

ajrty33 said:
Just change CDMA subscription to ruim/sim and toggle airplane mode...
I've never found a reason to have to Odin to anything.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
This fixed it for me! Thank you very much!
Sent from an unlocked Galaxy S 3! Screw you Verizon!

[Q] Screenlock not working?

Hey all,
first of all I would like to say thank you for all for the great job you do in here. It's really awesome I don't have to depend on mobile carrier companies (who always a year late with updates ) and i can take care of my phone myself.
The reason I'm posting here is a problem what I can simply cannot resolve, however i search over the forums.
My problem is lockscreen / screenlock simply not working. Its working on 2.3.6. but not on 4.0.4, I did try I9103XXLQ7 as it is originaly and with flashed over with MAZEL's great rom but no luck. Also i flashed I9103XXLQ9 and tried and after screen lock not worked here either i flashed over BlueBerry ROM 2.1a, but again, no luck. I always do factory reset, wipe cache and dalvik cache still, simply not working.
I did try other locker softwares like holo locker and go locker but I came across a very interesting problem with them, they work fine until my morning alarm would start since somehow the 3rd party locker softwares blocking the alarm clock to start. Simply nothing happening, no wake up sound no light nothing until I touch the phone then suddenly it wakes up. It's not a good way, i get late from work a few times of because of this problem not to mention i miss the snooze option
Can anyone help me please and let me know if this a factory software issue and if it is how to get over it (even with 3rd party software which is not affecting the alarm clock)?
I live in Hungary, got this phone from a friend.
Thanks for everyone and sorry if this was posted elsewhere, i was searching but did not found.

Did you look into Settings->Security->Screen Lock? (I'm not sure if this is that option on stock ICS, but it should be.) Maybe it's set to 'None'. It should not be set to none if you always wipe data.

Adam77Root said:
Did you look into Settings->Security->Screen Lock? (I'm not sure if this is that option on stock ICS, but it should be.) Maybe it's set to 'None'. It should not be set to none if you always wipe data.
Click to expand...
Click to collapse
yeah, i did check there, i can set anything still nothing happens, if i set pin or pattern or even password it will be still nothing asked when closed and opened the phone.
If i set for example PIN and i lock the phone with button and open it again still no pin pass asked (immediatelly goes to home screen) but when i go to settings / security the default setting shown is pin... its like totally ignore anything i set
I did try to set none the reboot then set pin then reboot, same results... also same results with even and pattern security.

应该是软件冲突了。你把锁屏软件的都卸载了。然后在锁屏里从新设置试试。我以前也碰到过，

This guy is saying that "I've come across, this Should be a software conflict. You uninstall software lock screen. Try and set new lock screen."

Maybe..
Go back to Stock GB.
Then reflash your phone to stock ICS??
Tried this??
Sent from my GT-I9103 using xda premium

mj.vikram said:
This guy is saying that "I've come across, this Should be a software conflict. You uninstall software lock screen. Try and set new lock screen."
Click to expand...
Click to collapse
Ty for translate the strange is even a full clean 4.0.4 install has no working screen lock so i dont really know what to uninstall then.

DeepankarS said:
Maybe..
Go back to Stock GB.
Then reflash your phone to stock ICS??
Tried this??
Sent from my GT-I9103 using xda premium
Click to expand...
Click to collapse
yeah, did try, on GB it's working fine...the strange thing is when is reflash GB it starts with the usual welcome screen (flashing GB with odin) set up account etc etc. but when i flash ICS (even after factory reset/cache wipe) it starts the system without the usual start screen... no welcome set you google acc or anything (i flash ICS in Odin too). somehow i got the idea it has something to do with the screen lock.
But is there any cleaner install then flash with ODIN? or should i try other factory FW to flash?

No. Use Odin v1.85
Maybe you should try downloading the STOCK ICS again.
Buddy try XWLP2 POLAND stock rom. As it is one of the latest and most stable stock ics rom with some bugs being corrected.
Our buddy kataria.vikesh has made a thread regarding this too "FROM WHERE TO DOWNLOAD" AND "HOW TO FLASH"
Maybe it will help.
Sent from my GT-I9103 using xda premium

DeepankarS said:
No. Use Odin v1.85
Maybe you should try downloading the STOCK ICS again.
Buddy try XWLP2 POLAND stock rom. As it is one of the latest and most stable stock ics rom with some bugs being corrected.
Our buddy kataria.vikesh has made a thread regarding this too "FROM WHERE TO DOWNLOAD" AND "HOW TO FLASH"
Maybe it will help.
Sent from my GT-I9103 using xda premium
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1983262
[FAQ][GUIDE] "How to Flash" & "From where to Download"
Sent from my GT-I9103 using Tapatalk 2

Thanks for everyone for the tips. I did flash XWLP2 yesterday, the screenlock situation is the same (no mather what i set, not working) however the 3rd party locker apps seems to work now. I did try a few times and it looks the alarm can work together with the locker app so at the moment it looks like the problem is at solved to a level where I can live with it
I do continue to experiment, strange no one came accross this problem. Also interesting and don't know why happening, there is no welcome screen at fresh install at ICS and I think that is part of the problem. It starts and GB and there the lock working fine. On ICS the system just loading like it was loaded before or something.

dodoka313 said:
Thanks for everyone for the tips. I did flash XWLP2 yesterday, the screenlock situation is the same (no mather what i set, not working) however the 3rd party locker apps seems to work now. I did try a few times and it looks the alarm can work together with the locker app so at the moment it looks like the problem is at solved to a level where I can live with it
I do continue to experiment, strange no one came accross this problem. Also interesting and don't know why happening, there is no welcome screen at fresh install at ICS and I think that is part of the problem. It starts and GB and there the lock working fine. On ICS the system just loading like it was loaded before or something.
Click to expand...
Click to collapse
if you can then flash MIUI locker for the same. it has tonnes of themes for locker & has great theme.
Here is mine
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Still not working 100% but i'm getting there one thing came to my mind, is there any ICS firmware with .pit and other files? i just use md5 file in pda at Odin, maybe thats causing the problem (which doesn't make sense since the GB software is md5 too but im desperate to find a solution).
I do found flasher+pit file in sammobile, odin 1.87 and a pit file was in the package but not sure I can use .pit and md5 file without the modem and csc...
Lock screen working (go locker now) but still the alarm clock not always working or if it does start few minutes +- as set and snooze not working at 50% of the time..

Buddy pit files are for advanced users who want to play around with their partition table. It could mess up your partitions if you don't know what you are doing. Be careful.

The-Droidster said:
Buddy pit files are for advanced users who want to play around with their partition table. It could mess up your partitions if you don't know what you are doing. Be careful.
Click to expand...
Click to collapse
Yes buddy, I did that with my Samsung Galaxy 3 aka apollo (indian version with i5801 like i9103 for R). I have changed it with Europe's Galaxy 3 ( i5800). Hence my warranty void for life time.

Buddy go to the SSC then.
They will solve this problem for sure
Only if your phone is still under warranty
Sent from my GT-I9103 using xda premium

what is it happen ?
---------- Post added at 12:47 AM ---------- Previous post was at 12:43 AM ----------
what is the slove choice

[How to] Get rid of the samsung custom boot image

I used Triangle away to reset custom flash counter, both on a stock rooted rom and on goldeneye rom, and both times I was able to get rid of the stupid samsung custom logo with the picture of an unlocked lock.
1. Install triangle away
2. Click reset flash counter (even if it says counter: 0) i think this happens when you have only flashed 1 rom, sometimes under status is shows official but when it boots it says custom.
3. Reboot and enjoy looking at the official S4 logo
4. Profit
It was really bothering me so I found a way to get rid of it, and I thought that I'd share it with you guys.
Edit: Added img
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

insaneshan3 said:
I used Triangle away to reset custom flash counter, both on a stock rooted rom and on goldeneye rom, and both times I was able to get rid of the stupid samsung custom logo with the picture of an unlocked lock.
1. Install triangle away
2. Click reset flash counter (even if it says counter: 0) i think this happens when you have only flashed 1 rom, sometimes under status is shows official but when it boots it says custom.
3. Reboot and enjoy looking at the official S4 logo
4. Profit
Not sure if this will help anyone or if the boot logo was there to let you know that you can use a custom boot image, but it was really bothering me so I found a way to get rid of it, and I thought that I'd share it with you guys.
Click to expand...
Click to collapse
While obviously keeping in mind that bad things MAY occur with Triangle Away, of course. Use at own risk.

Could I use ktoonsez kernel with this or?
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

insaneshan3 said:
I used Triangle away to reset custom flash counter, both on a stock rooted rom and on goldeneye rom, and both times I was able to get rid of the stupid samsung custom logo with the picture of an unlocked lock.
1. Install triangle away
2. Click reset flash counter (even if it says counter: 0) i think this happens when you have only flashed 1 rom, sometimes under status is shows official but when it boots it says custom.
3. Reboot and enjoy looking at the official S4 logo
4. Profit
Not sure if this will help anyone or if the boot logo was there to let you know that you can use a custom boot image, but it was really bothering me so I found a way to get rid of it, and I thought that I'd share it with you guys.
Click to expand...
Click to collapse
+1 It worked for me after using CASUAL on my S4 (CUAMDL) right out of the box! {removed the "open lock" almost instantly!}
Thanks for the tip!

alternatively, install SuperSU as your su app, let it install binaries, then uninstall whatever other app you were using (it does this automatically), and reboot a few times. Unlocked icon will go away.
No risk of issues from triangle away.

Will this work on non-stock?
Sent from my Galaxy Nexus using Tapatalk 4 Beta

jova33 said:
Will this work on non-stock?
Sent from my Galaxy Nexus using Tapatalk 4 Beta
Click to expand...
Click to collapse
Only if the non-stock you are running identifies the device properly. In other words, if you run triangle and it says a different model, do not continue, it will brick, but if it shows the correct device model, go for it.

No dice. I'm on VZW, SCH-I545, it identifies the device properly, says it's going to reboot into Odin mode, reboots, get the blue text at the top that says booting into recovery, then skips to boot animation.
Sent from my SCH-I545 using Tapatalk 4 Beta

cegna09 said:
alternatively, install SuperSU as your su app, let it install binaries, then uninstall whatever other app you were using (it does this automatically), and reboot a few times. Unlocked icon will go away.
No risk of issues from triangle away.
Click to expand...
Click to collapse
Tried this and no luck.
How well known and acknowledged is this procedure?
Anything I can do differently?

seanpr123 said:
Tried this and no luck.
How well known and acknowledged is this procedure?
Anything I can do differently?
Click to expand...
Click to collapse
I found it through a google search, and it worked perfectly for me. Took about 3-4 reboots, and then the lock icon went away. I'm just running stock rooted software, not sure how it works with other software.
here's the thread
http://forum.xda-developers.com/showthread.php?t=2257058

cegna09 said:
I found it through a google search, and it worked perfectly for me. Took about 3-4 reboots, and then the lock icon went away. I'm just running stock rooted software, not sure how it works with other software.
here's the thread
http://forum.xda-developers.com/showthread.php?t=2257058
Click to expand...
Click to collapse
Ahh ok, do you have a custom recovery?
I'm running TWRP & custom ROM, that must be why.

seanpr123 said:
Tried this and no luck.
How well known and acknowledged is this procedure?
Anything I can do differently?
Click to expand...
Click to collapse
That method seemed to work for some and not for others, with no discernible reason why.
I was stock rooted with stock recovery when I tried it and never did manage to get the custom screen to go away. Thankfully, I realized I could care less about it and went on with my life!