In an effort to keep SCOMs dev thread clean and streamlined please post all of your questions here.
Thanks
No luck with your suggestion hechoen. Running GR again (even though I did that before this flash) and will reflash. Checked the MD5 and that's good.
im still experiencing lagging with scrolling. i did gremlin remover then flashed ROM and it was smooth, but when i rebooted the phone, it started lagging with scroling again. if i do a factory reset from CWM, do i have to reflash the ROM or just reboot after the do the factory reset?
native
Just reboot. I'm running into some issues as well. It seems to only happen after I power down and reboot. Very odd. So factory resest from CWM, reboot and play with the phone. Don't restore any apps yet. If it seems smooth reboot the phone. Let me know whether the lag reappears after the second reboot.
hechoen said:
native
Just reboot. I'm running into some issues as well. It seems to only happen after I power down and reboot. Very odd. So factory resest from CWM, reboot and play with the phone. Don't restore any apps yet. If it seems smooth reboot the phone. Let me know whether the lag reappears after the second reboot.
Click to expand...
Click to collapse
i already restored the apps at the beginning with TB and it was smooth, but after the reboot, it started lagging with scrolling again.
Kyndig66 said:
No luck with your suggestion hechoen. Running GR again (even though I did that before this flash) and will reflash. Checked the MD5 and that's good.
Click to expand...
Click to collapse
That's what worked for me. One other thing that I think has worked for some on other ROMs with this issue is to turn on bluetooth and while it's doing it's thing reboot the phone. If that doesn't work get a log to erikmm and he'll let you know what else to try.
hechoen said:
That's what worked for me. One other thing that I think has worked for some on other ROMs with this issue is to turn on bluetooth and while it's doing it's thing reboot the phone. If that doesn't work get a log to erikmm and he'll let you know what else to try.
Click to expand...
Click to collapse
Tried that before posting my Q in the SCOM thread. Tried a myriad of combinations also. It used to be a problem for a lot of people at one time. It never occurred with vb final fixed or unnamed. If this next go doesn't work, I'll get a log.
native
I'm having the same thing happen. After second reboot laggy and super unresponsive. If someone else running this wants to reboot and see if they pick up lag as well it would be appreciated. If no one else is having this issue it has to be one of the apps that we are restoring causing it. I'm still trying to figure it out myself.
hechoen said:
Where do you get this stuff? I've reset from inside the OS on plenty of occasions and never had anything bad happen. My next suggestion to native if this doesn't work was gonna be to factory reset it from inside the phone.
Click to expand...
Click to collapse
Every phone I have had the devs state to never do a factory reset from the setting menu. My last phone there was many people with broken phones because they used the privacy menu reset. I dunno I just prefer not to waste 300bucks wiping data improperly. I also would hate to see somebody post doing it broke their phone.
If you can safely wipe data from the privacy menu then I stand corrected.
Kyndig66 said:
Tried that before posting my Q in the SCOM thread. Tried a myriad of combinations also. It used to be a problem for a lot of people at one time. It never occurred with vb final fixed or unnamed. If this next go doesn't work, I'll get a log.
Click to expand...
Click to collapse
I just tried bluetooth with wifi on and it hung on turning on. Rebooted and it worked. Both wifi and bluetooth. Now if I can figure out why restoring and rebooting is causing lag I'll be really happy.
just had my first reboot and its lagging again. the reboot happened by itself
hechoen said:
I just tried bluetooth with wifi on and it hung on turning on. Rebooted and it worked. Both wifi and bluetooth. Now if I can figure out why restoring and rebooting is causing lag I'll be really happy.
Click to expand...
Click to collapse
Wierd. Im lagging also and i havent restored anything. Only apps i installed are log this and xda. Working on logs for eric.
Sent from my SGH-T959V using xda premium
hechoen said:
Now if I can figure out why restoring and rebooting is causing lag I'll be really happy.
Click to expand...
Click to collapse
What method are you using to restore?
When I updated to unamed v2 I had three reboots after restoring some apps. I wiped reflashed and installed them one at a time until it rebooted. Then removed that app and continued. No reboots. So I wiped ran gremlin remover. Flashed again installed the offending app. No reboots. I installed the app prior to the offending one and bam reboot. Come to find out the issue was created by a update to the two apps not properly updating. I did a fresh install from the market and have had no problems.
Anybody having issues with little to no volume in calls? I have tried data/factory reset from cwm and also fixed permissions.
FYI, I just flashed the rom again to see if that will fix it. soaking in now.
OK so here's what I've come up with to fix the lag issue for me. Flashed the rc2 kernel and lag is gone. I've rebooted a number of times to make sure this is the case and every time quad runs at full FPS. I've restored all my apps with TB and have this running perfectly smooth. So a guess would be something with the new kernel or SuperSU. Again this is a guess. But if you want to run SCOM V3 lag free and have TB restore all your stuff for now reflash the RC2 kernel.
EDIT: Scratch that theory. Lag is back. I should have never doubted are kernel devs. For those of you getting logs that use ADB here's a great guide.
http://forum.xda-developers.com/showthread.php?t=1378491
This may work in terminal emulator as well. I'm short on time today so I'm going to reflash and not reboot anymore! Just hang in there and it will get figured out.
Thanks for the info on the Kernel being the possible culprit.
Sorry about all the problems guys but im running v3 no lag but im checking on it still
for bluetooth issue raver just told me to try turn bluetooth on and reboot phone
---------- Post added at 05:48 PM ---------- Previous post was at 05:37 PM ----------
{
"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"
}
check it out just reflashed and got both to turn on ok
and no lag after 3 reboots
erikmm said:
check it out just reflashed and got both to turn on ok
(
Click to expand...
Click to collapse
Not sure why, and I don't care why, but both bt and wifi are working concurrently for me after the 3.5 flash. The bt device doesn't connect unless i go into bluetooth setting and press the paired device, which is fine. Thanks erik!
Edit: Device connects like usual now. Guess I didn't wait long enough.
v3.5 installed
Downloaded and installed v3.5 on my phone last night. All functions seem normal and working great. I have OC'd to 1.3 and have no issues with battery temp.
If I may, Erik has been especially patient and extremely helpful. I did have an issue with a previous version of SCOM and he was readily available and willing to help out. It is very comforting to know that as some great dev's leave the SGS4G community some other good/great dev's are coming in to fill the void. Erik, I appreciate your hard work and your ROM reflects your passion and hard work. You ROCK!
After a horrific 15 hour period of pulling my hair out, I finally got my phone out of a hardbrick apparently initiated by installing Sweet Child O Mine v3.5. Here's how I got there:
1. When flashing SCOM v3 (following OP precisely), the phone randomly rebooted (around 90% of Aroma installation).
2. When attempting to flash again, Aroma Installer gave a warning saying it did not recognize my phone as a SGS4G. I clicked the checkbox and installed anyway. ROM worked.
3. When trying to upgrade to SCOM v3.5 late last night, I wiped all data and flashed. Got the same warning as before. This time, didn't install.
4. Tried using Gremlin 1-Click before attempting again... Kept getting stuck on factoryfs.rfs. Had to pull the battery multiple times to try to get it to work, but eventually it caught.
5. Tried flashing SCOM v3.5 again... crapped out before Aroma Installer could finish. I started again, got the unrecognized device warning again.
6. Went back to Gremlin 1-Click again... this time, could not get it to catch! Phone was stuck in softbrick.
7. After multiple attempts, decided to try Heimdall 1-Click, to no avail. Checked off "flash bootloaders" and after 3rd attempt, phone went hardbrick (screen wouldn't turn on no matter what I did).
Stayed up until 5 am trying to fix it, but put it aside to work on it again today. Here's how I finally fixed it:
1. Found RaverX3X's 1-Click somewhere on the forums... removed CWM and put me back on Samsung Utils
2. Downloaded all the files from FB's GB Ext4 starter pack page.
3. Managed to get the phone to yellow triangle by: Pulling and replacing battery->Holding Vol + and Vol - ->Inserting USB
4. Ran Odin as Admin, but had to use a different cable and port to get computer to see the phone
5. Finally back on stock KJ6.
Hopefully all that info above will help someone in trouble like I was.
Now I have a new problem: I want to flash SCOM v3.5 again, but I'm afraid of getting soft/hard-bricked again!
To be honest, I dislike the color scheme and the mismatched icon set in SCOM, but it has two things going for it:
1. Smooth as butter (surprisingly, smoother than RaverX3X's VB final for me)
2. Battery life when NOT using phone is amazing (left the phone for a few hours yesterday, didn't move a single percent). The battery drains fairly quickly when phone is in use, however.
So, how do I instally SCOM v3.5 without falling into the same problems? Or, alternately, what other ROM is comparable in terms of smoothness and idle battery life?
Related
Some users are noticing GPS issues after flashing to EC05. The issues include the inability to lock on satellites after extended period of up-time and terrible accuracy. The phone would have to be rebooted to get GPS working again. These issues are affecting users with stock and custom ROMs.
Following these steps will get your phone to a perfectly working EC05, with fully functional, bug free GPS:
1) Flash your phone back to stock DI18 via Odin (the .tar belongs in the PDA slot and your phone must be in download mode)
2) Follow steps 1-8 on this post.
3) Update to EC05 via OTA update or Flash Stock EC05 with Odin.(if you want to stay stock and unrooted, jump to step 7 after this step)
4) Install latest One click Root and Recovery + ClockworkMod v3.0.0.5/6 for EXT4 (optional) (Warning: this will format your NAND to EXT4 the first time you boot to recovery. If you do install this version, you must install an EXT4 ROM after booting to Recovery the first time. The stock ROM will not boot afterward.)
or
4B) Install One Click Root and Recovery + ClockworkMod v2.5.5 for RFS (optional)
5) Perform a backup, in clockworkmod (optional)
6) Install a custom ROM (optional)
7) Install all of your apps and enjoy a fully functional GPS
Calibrate your battery by following this thread (I suggest the second or third option)
I suggest to not restore apps from a previous flash. It might cause some issues. If you do encounter any issues, at least you won't have that to blame for it.
buggerritt said:
Some users are noticing GPS issues after flashing to EC05. The issues include the inability to lock on satellites after extended period of up-time and terrible accuracy. The phone would have to be rebooted to get GPS working again. These issues are affecting users with stock and custom ROMs.
Following these steps will get your phone to a perfectly working EC05, with fully functional, bug free GPS:
1) Flash your phone back to stock DI18 via Odin (the .tar belongs in the PDA slot and your phone must be in download mode)
2) Follow steps 1-8 on this post.
3) Update to EC05 via OTA update or Flash Stock EC05 with Odin.(if you want to stay stock and unrooted, jump to step 7 after this step)
4) Install latest One click Root and Recovery + ClockworkMod v3.0.0.5/6 for EXT4 (optional) (Warning: this will format your NAND to EXT4 the first time you boot to recovery. If you do install this version, you must install an EXT4 ROM after booting to Recovery the first time. The stock ROM will not boot afterward.)
or
4B) Install One Click Root and Recovery + ClockworkMod v2.5.5 for RFS (optional)
5) Perform a backup, in clockworkmod (optional)
6) Install a custom ROM (optional)
7) Install all of your apps and enjoy a fully functional GPS
Calibrate your battery by following this thread (I suggest the second or third option)
I suggest to not restore apps from a previous flash. It might cause some issues. If you do encounter any issues, at least you won't have that to blame for it.
Click to expand...
Click to collapse
Dont take this wrong but you are compelty incorrect. that particluar "old solution" was for the early test versions of eb13 froyo which had other different GPS issues from the cache issue. EB13 was actually fixed and had perfect GPS by the time of its official OTA.
What users (and Sprint advanced device) are seeing is a return of the assistance cache issue. All that flashing etc is obviously clearing the assistance cache which is why you had a problem and don't see it yet.
aero1 said:
Dont take this wrong but you are compelty incorrect. that particluar "old solution" was for the early test versions of eb13 froyo which had other different GPS issues from the cache issue. EB13 was actually fixed and had perfect GPS by the time of its official OTA.
What users (and Sprint advanced device) are seeing is a return of the assistance cache issue. All that flashing etc is obviously clearing the assistance cache which is why you had a problem and don't see it yet.
Click to expand...
Click to collapse
You sir are incorrect. This fix was actually from DK28 (pre EB13). It has fixed my GPS. Perhaps your GPS has had no issues. If so, I am very happy for you. I never had problems with EB13. I did with DK28 and fixed it with this (while many others were still bumbling around and wishing for the official Froyo because they were scared to use a beta). Afterward my DK28 had perfect GPS. I also did with EC05. Others have had issues with EC05, as well. The problems seem to be from the same cache problem that DK28 had. If not, then this would not have solved the issues. I now get lock on satellites all the time and have accuracy of 1-2 meters.
I followed the steps over 4 days ago so, your theory on clearing the assistance cache does not apply.
{
"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"
}
This was after over 9 hours uptime. The lock took 2 seconds for the first satellite and full lock on all within 10 seconds. Use of wireless networks disabled. This was not possible before following the steps in the OP. Previously, I was unable to get a lock after 3-5hours uptime. I would have had to reboot.
Sent from my SPH-D700 using Tapatalk
buggerritt said:
You sir are incorrect. This fix was actually from DK28 (pre EB13). I.
Click to expand...
Click to collapse
OMG you are posting a copy of my fix from Sept and don;t even realize it!
aero1 said:
OMG you are posting a copy of my fix from Sept and don;t even realize it!
Click to expand...
Click to collapse
Please link me to your original fix. I would love to give you the credit for fixing my GPS, instead of ahmgsk, if yours is the original one. If you are the original poster, I find it very silly for you to deny that it fixes EC05 GPS issues, too. It does, indeed.
But, if you are referring to this thread, where your OP states:
"TESTED AND FUNCTIONING WORKAROUND:
Enter GPS debug/settings application by typing *#1472365#
click "Setup" tab
click "position mode"
Click "starting mode
Enable "Cold Start"
Back out.
Epic GPS will now call on data network for fresh valid ephemeris and almanac at every programing invocation of GPS and aGPS fixes will be very fast (usually less than 10 seconds)."
then, it is not the entire workaround. It doesn't mention anything about locking on satellites in each startup mode. It doesn't mention locking on satellites in any mode, as a matter of fact. It also doesn't mention anything about flashing any updates after the workaround. I hope your upcoming link, to the complete workaround that actually works, will shed some light as to who I truly owe my thanks and appreciation for. If it is you, then I will applaud you with a plethora of golf claps.
Hey there
I wasn't able to find whether the person you asked to do a nandroid restore; after Odin to DI18 steps to fix the GPS issue you were able to clear up.
Just today I have experienced what you describe. I've never had anything more than 4 minutes MAX to lock. I just tested and it didn't lock after 10 minutes.
Anyhow, did they restore or just do everything as stated in the OP??
Thanks!!
Well now that I see results I will forsure have to try now
jdelano said:
Hey there
I wasn't able to find whether the person you asked to do a nandroid restore; after Odin to DI18 steps to fix the GPS issue you were able to clear up.
Just today I have experienced what you describe. I've never had anything more than 4 minutes MAX to lock. I just tested and it didn't lock after 10 minutes.
Anyhow, did they restore or just do everything as stated in the OP??
Thanks!!
Click to expand...
Click to collapse
Here is how the conversation went:
(fnordsnafu replied to what I asked carnivalrejectq)
buggerritt said:
Perhaps, you could do us both and others a favor, then. This would be an experiment. You could create a nandroid backup, perform steps 1-4, flash midNIGHT 5.2, and perform a complete restore and see if that will also fix it. the worst case scenario would be that you are right back where you are, now. It might actually fix it and you could help others with that bit of experience. It's up to you, of course. I know it is a lot to ask, since it takes time and there is no guarantee.
Click to expand...
Click to collapse
(11th April 2011, 11:30 PM)
fnordsnafu said:
I actually just did this. So far so good. I will keep testing to see if I get a lock over the next several hours and then days. Fingers crossed that this worked. Uber tired of the GPS issue.
Click to expand...
Click to collapse
buggerritt said:
Thanks for giving it a go. I hope it does work. There were no promises for it, with restore.
Click to expand...
Click to collapse
(12th April 2011, 09:46 AM)
fnordsnafu said:
So far so good. Got a lock within 2 or so seconds and a full 12/12 within 10 seconds and I'm inside. A definite success so far. Will continue to update.
Click to expand...
Click to collapse
buggerritt said:
If it still works after 8 hours of uptime, I'd say you have a winner
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
buggerritt said:
What are your findings, now, after so many hours of uptime?
Click to expand...
Click to collapse
(12th April 2011, 07:16 PM)
fnordsnafu said:
It's still going strong. Fast, solid fix every time. Very, very happy. Thanks sooooo much!
Click to expand...
Click to collapse
There are still no guarantees but, restore worked for this user.
BTW, mine is still going strong and it has been a week running. I always get lock within 2 seconds and always get 10-12 satellites within 10 seconds. Within 15-20 seconds, accuracy improves to 1 meter. This happens every time, whether I have just swapped my battery or if I've got 18 hours uptime. It makes no difference and I don't have to clear cached GPS data or download GPS assistance data. It just works every time all the time.
Anon9mouz said:
Well now that I see results I will forsure have to try now
Click to expand...
Click to collapse
I hope it works for you, too. Please post your results.
Well like I said in the Midnight thread, I never had an issue with gps other than it taking forever to lock. After doing this I'm locked in in about 5 to 10 seconds at or around 20 to 30 meters. Its only a few seconds after that I'm locked at 9 to 10 meters. This work around has my vote of helping get a faster lock. I can't comment of any other results becuz as I stated my only issue was wait time with locking but now I'm locked in in no more than 15 seconds. That is faster than any. Gps lock I've ever gotten on this phone and I've had it since it came out. Thanks for this one once again.
Sent from my SPH-D700 using Tapatalk
That's good enough for me.
First of all, I appreciate this thread, the OP, and all of the suggestions listed here.
Unfortunately, I just thought I'd mention that I tried this fix [using the restore method], and GPS continued to crap out on me after a day or so--by which I mean it would become completely nonfunctional, without even an icon showing in the notification bar.
I am currently trying the "GPS crash" fix that was added to the following thread yesterday:
http://forum.xda-developers.com/showthread.php?t=1029152
I'm hopeful about this one, as the explanation behind it seems pretty well-reasoned and thought out.
Hopefully the fix in this post will continue to help people, but I'm going on record as saying it didn't work for me.
Cash Machine said:
Hopefully the fix in this post will continue to help people, but I'm going on record as saying it didn't work for me.
Click to expand...
Click to collapse
The two are complementary. The crash fix should be tried first since that's well-investigated problem at this point. If you continue to have GPS issues (icon comes up, but can't find satellites after 5 hours of uptime), it's possible this method may help. We're still not quite certain what it does exactly, likely changes something in the baseband NVRAM, but beyond its only known that it does help some folks.
Also, the restore method is not suggested, it worked for a couple people but, generally restores have a tendency to restore problems, as well as everything else.
Sent from my SPH-D700 using Tapatalk
9 hours of uptime is not long enough for the original problem to show.
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.
This started occurring last night when I was using Winamp to sync music files to my phone. Every 10% or so the phone would reboot itself and I'd have to start the entire process over. Since then, I've been getting random reboots while doing anything from typing an e-mail to closing an app and haven't been able to narrow it down to anything specific.
So far I've tried
1) Removing my external sd card
2) Uninstalling numerous apps to try an pinpoint one causing an issue
3) Underclock from the 1.9 ghz the rom comes with
4) Removing the battery
5) Reflashing the latest nightly, clearing cashe and dalvik
Anyone have any idea on how I can try to resolve this? I love the phone and the ROM, but I can't deal with random reboots while just using my phone normally.
Thanks in advance.
jdubsss said:
This started occurring last night when I was using Winamp to sync music files to my phone. Every 10% or so the phone would reboot itself and I'd have to start the entire process over. Since then, I've been getting random reboots while doing anything from typing an e-mail to closing an app and haven't been able to narrow it down to anything specific.
So far I've tried
1) Removing my external sd card
2) Uninstalling numerous apps to try an pinpoint one causing an issue
3) Underclock from the 1.9 ghz the rom comes with
4) Removing the battery
5) Reflashing the latest nightly, clearing cashe and dalvik
Anyone have any idea on how I can try to resolve this? I love the phone and the ROM, but I can't deal with random reboots while just using my phone normally.
Thanks in advance.
Click to expand...
Click to collapse
I had this problem too with the latest release, even after reflashing it, and it even popped up randomly like your issue after using the ROM for a while. All of the sudden random reboots all the time. I went back to R64. I think there is a different kernel in some of the newer releases or some change, I don't really know, but R64 has been running perfect all around and hasn't rebooted once on me. You may be able to dirty flash back to 64, I don't know if it will work because I didn't try it, but I do know a clean flash fixed it for me. If it's just kernel issues then dirty flash should work as usual.
adoublearonn said:
I had this problem too with the latest release, even after reflashing it, and it even popped up randomly like your issue after using the ROM for a while. All of the sudden random reboots all the time. I went back to R64. I think there is a different kernel in some of the newer releases or some change, I don't really know, but R64 has been running perfect all around and hasn't rebooted once on me. You may be able to dirty flash back to 64, I don't know if it will work because I didn't try it, but I do know a clean flash fixed it for me. If it's just kernel issues then dirty flash should work as usual.
Click to expand...
Click to collapse
Thanks for the reply. I flashed leankernel tonight and so far so good... time will tell though.
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
Hi,
there is a new release of MM 6.01 -firmware available, from July 27th.
Has anyboy checked it? Are any wellknown issues solved (i.e. fingerprint/backup password request, random reboots)?
Thnx for any info.
Chris
I'd also like know what this update is doing. ...
---------- Post added at 05:30 AM ---------- Previous post was at 05:30 AM ----------
Random reboots are the bain of my life at the moment. ... #firstworldproblems
I have it for 3 days now and i must say that the batterylife has improved a little. It all runs a little smoother also.
MSK1 said:
I'd also like know what this update is doing. ...
---------- Post added at 05:30 AM ---------- Previous post was at 05:30 AM ----------
Random reboots are the bain of my life at the moment. ... #firstworldproblems
Click to expand...
Click to collapse
I have installed it via odin yesterday, no wipe, just cleared cache after installation. All settings kept as they were. Up to now very snappy, no reboots, no backup-password-entry requested (only after manual restart, of course). So, if it stays that way it seems that the bugs have been removed. Keep fingers crossed.
I'm just downloading the same firmware....will install later (dirty install) and give my feed back here.....
After a day there was no soft reboot. For me usually in Messages happened when i wrote a new one, until now there was no event
I hope we can forget that finally, i really liked fingerprint until the issue...
edit: i updated via OTA, no wipe etc.
Hi, Can anyone deodex and debloat this stock rom DPG1 please?
Installed N915FYXXUDPE1 (N915FYXXU1DPE1_N915FYOXA1DPD1_N915FYXXU1DPC3_HOME.tar.md5) the phone is noticeably faster and no soft reboots / password requested (unless on hard reboot) much better!
I did a dirty flash then reinstalled custom recovery (TWRP), re-rooted and xposed....
Link to my firmware
http://www.sammobile.com/firmwares/database/SM-N915FY/BTU/
{
"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 SM-N915FY using XDA-Developers mobile app
Stripester said:
Installed N915FYXXUDPE1 (N915FYXXU1DPE1_N915FYOXA1DPD1_N915FYXXU1DPC3_HOME.tar.md5) the phone is noticeably faster and no soft reboots / password requested (unless on hard reboot) much better!
Click to expand...
Click to collapse
This is all about the new N915FYXXS1DPG1, so why are you talking about this old version? Please stay on toppic!
charly-whiskey said:
This is all about the new N915FYXXS1DPG1, so why are you talking about this old version? Please stay on toppic!
Click to expand...
Click to collapse
My bad! Apologies
I'm still getting soft reboots... albeit less frequently. ..
Mainl after ending calls and pressing home key
MSK1 said:
I'm still getting soft reboots... albeit less frequently. ..
Mainl after ending calls and pressing home key
Click to expand...
Click to collapse
How did you install? OTA? Wipes?
Where did you come from?
I was on 5.1.1 and flashed dirty via Odin, just wiped cache, and until now no single reboot, night clock is working, very fast response, no lags, no signal drops. Feels like a new phone.
Okay Dirty Flashed N915FYXXS1DPG1_N915FYOXA1DPD1_N915FYXXU1DPC3_HOME.tar (Which I believe is the most recent!)
Wiped cache/Dalvik, re-rooted and Xposed with Nova Launcher.
Did not loose any information or settings (phew)
Certainly faster, no reboots......fingers crossed....also a bit quicker on AnTuTu 68372...
Will keep updated over the next few days
confirmed
MSK1 said:
I'm still getting soft reboots... albeit less frequently. ..
Mainl after ending calls and pressing home key
Click to expand...
Click to collapse
i confirm that. Happened only once until now. After a call it soft reboots.
But i can live with that if happens very rarely, in past it was very frequent... Otherwise the phone is really smoother, battery is also better a bit. So i am happy...
bobace said:
i confirm that. Happened only once until now. After a call it soft reboots.
But i can live with that if happens very rarely, in past it was very frequent... Otherwise the phone is really smoother, battery is also better a bit. So i am happy...
Click to expand...
Click to collapse
But, again, please let us know how you flashed it, cause could make the difference. So, OTA or Odin, wipes, where did you come from?
I am on it since four days now, my phone runs through, no reboots or whatever. I came from 5.1.1 stock, no root. Flashed via Odin, just wiped cache. Feels like a new phone.
charly-whiskey said:
But, again, please let us know how you flashed it, cause could make the difference. So, OTA or Odin, wipes, where did you come from?
I am on it since four days now, my phone runs through, no reboots or whatever. I came from 5.1.1 stock, no root. Flashed via Odin, just wiped cache. Feels like a new phone.
Click to expand...
Click to collapse
I've already did. On page 1 i wrote: OTA with no reset. Only deleted some unnecessary apps and clear cache.
It was going so well..... In 8hrs had one soft reboots (typical as it was when I was driving) ... Phone is definitely faster and runs cooler.....
May be worth noting that I do use lots of features, 5 email accounts (1 exchange), Bluetooth (Various paired devices), stream music via Google play....
I will see if there is any correlation between reboots...
Sent from my SM-N915FY using XDA-Developers mobile app
charly-whiskey said:
How did you install? OTA? Wipes?
Where did you come from?
I was on 5.1.1 and flashed dirty via Odin, just wiped cache, and until now no single reboot, night clock is working, very fast response, no lags, no signal drops. Feels like a new phone.
Click to expand...
Click to collapse
In installed the standard way. ...
It's still quite frequentl... the main one now is wn exciting maps (after its auto started with tasker)
I have cleared cache.
---------- Post added at 11:21 PM ---------- Previous post was at 11:21 PM ----------
charly-whiskey said:
How did you install? OTA? Wipes?
Where did you come from?
I was on 5.1.1 and flashed dirty via Odin, just wiped cache, and until now no single reboot, night clock is working, very fast response, no lags, no signal drops. Feels like a new phone.
Click to expand...
Click to collapse
I installed the standard way. ...
It's still quite frequentl... the main one now is wn exciting maps (after its auto started with tasker)
I have cleared cache.
MSK1 said:
In installed the standard way. ...
It's still quite frequentl... the main one now is wn exciting maps (after its auto started with tasker)
I have cleared cache.
---------- Post added at 11:21 PM ---------- Previous post was at 11:21 PM ----------
I installed the standard way. ...
It's still quite frequentl... the main one now is wn exciting maps (after its auto started with tasker)
I have cleared cache.
Click to expand...
Click to collapse
You see, I've been on MM several times, the reboots made the phone unusable. Then I made a full wipe, got back to 5.1.1, and then flashed directly to the new rom. I suspect that coming from an older MM-rom, the buggy ones, and flashing just dirty the new firmware may leave some buggy files unchanged. So when you came from MM and have problems now with the DPG1, it could be helpful to go my way. That was the reason I've asked you where you came from, which wasn't answered. Give it a try.
charly-whiskey said:
You see, I've been on MM several times, the reboots made the phone unusable. Then I made a full wipe, got back to 5.1.1, and then flashed directly to the new rom. I suspect that coming from an older MM-rom, the buggy ones, and flashing just dirty the new firmware may leave some buggy files unchanged. So when you came from MM and have problems now with the DPG1, it could be helpful to go my way. That was the reason I've asked you where you came from, which wasn't answered. Give it a try.
Click to expand...
Click to collapse
Okay....Phone did a soft reboot this morning, whilst I was starting the Car, IE it connected to Bluetooth, then as I started the car it soft rebooted.....I am thinking that this issue may be to do with WIFI/BLUETOOTH connection/handover only a thought..