Hello everyone!
I request your help please, because sometime my phone goes stuck and I have to reboot each time.
First, here is my configuration :
XWLSW NeatRom Lite 4.8 installed with full wipe (Philz kernel) + Blue Ginger Plus Theme + Apex Launcher + Fancy Widget (clock + weather) on my main page.
I have to precise, that before installing the NeatRom, I had an older ICS ROM (CriskeloServanTeam V12), and this kind of stuck used to happening on my device, that's why I decided to install a new ROM.
Here is the 2 last situtations when my phone was stuck :
- I'm charging my phone just before going to sleep (in fly mode), and in the middle/end of the night, surely after my battery reach 100%, I'm looking to the clock of my phone : it display 2h31 (instead of the real time 5h23), probably at the time when my phone goes stuck.
Symptoms : Time was stuck, Apex Launcher close, Status bar is missing on the lockscreen, impossible to goes through the lockscreen, but it is possible to reboot (luckily!).
- In the daily use of my phone, I decided to activate the data by the status bar on the lockscreen, then I switch off the screen. 15-20 min later, I want to unlock my screen, but impossible, it is stuck.
Symptoms : Status bar is missing on the lockscreen, impossible to goes through the lockscreen, but it is possible to reboot (luckily!).
So my questions :
Why this is happening?
Is anyone else already have this kind of stuck with this configuration?
What can I do to fix that?
Thanks a lot!
Sound like a sod to me. What kernel are you using? Did you do format before you changed to neat rom from ics rom??
Kernel is responsible for these actions.I had so many and also random freezes with DorimanX kernel...ahh ...Now I have Apolo Kernel and eveything is okay.No freezes,and awesome battery.Try out Apolo kernel And also do a factory reset,and don't install themes or mods...run it clean for a few days,see iif it still presists.
First, thank you both for your answers.
Then, my kernel is the one that goes with the NeatRom Lite version 4.8 : XWLSW-5.06.1-PhilZ.
I think my problem is a Sleep of Death too. Yes I did a wipe data, wipe cache, wipe dalvik cache, format system, and format preload before installing the Rom. Is it normal I have a SoD after I did all of this?
Else ok for the Kernel, I will try the Apolo. Is it ok to install it with the NeatRom lite 4.8 ?
Well you did the install ok so I dont see the problem philz kernel is good for neat rom. You should try apollo kernel reg first. But I would say test the rom with out the mods and then flash mods one by one. But like I said philz is good for neatrom. Try factory reset which will clear the mods and test it with philz first.
Ok thanks I will try that.
Just another question, is the Apex Launcher is considered as a "mod" and should I use the TW launcher some days instead, or can I still use the Apex Launcher (the freeze cannot come from this app) ?
I shouldn't think apex would cause this. Probably, clock widget is but not to sure.
I just noticed I had the debug mode activated on my phone (I don't know why? maybe I activate it by mistake? but I don't remember). Could the recurring Sleep of Death happens because of this?
Nope. SOD's are not caused by usb debugging. Follow andrewwright's advice, he knows what he's talking about.
Sent from a galaxy far, far away
simply go back to stock rom
Yes but ... no I like custom Roms, so I will try all I can before going back to a stock Rom
I did some research and I think this is not really SoD that happening to to my phone.
Effectively I read that SoD is the behavior in which the phone goes into "sleep" mode... typically screen off, and then won't wake up with power button.
However, when my lockscreen is frozen, I can still push the power button and access the power menu to reboot my phone, I don't have to remove the battery.
So if this is not a SoD, what is it?
So what did you try? If its still happening and it was me I would now format the lot,reinstall the rom with nothing on it. No mods and no apps and see if it happens again. So no apex no widget and no flashing of any mods. Then test that for two days. If problems are still there I would try a different rom to rule out software. I no neat is solid and so is philz kernel. Im
I changed the battery (it was recent, less than 1 year, but you never know, maybe defective).
I reinstalled the same rom, but with no mods, no themes, and no restoring apps from Titanium (but I installed them by downloading them by the Playstore).
Almost 2 days fine, but yesterday it froze again.
So now I will try to format, but before, do you think a scandisk plus a defragment on my SD Card could help?
Yes that help clear out any crap left over from different roms.
andrewwright said:
Yes that help clear out any crap left over from different roms.
Click to expand...
Click to collapse
I did a chkdsk/scandisk on my intern SD Card, and installed the last version of Philz kernel (5.11.2).
Atm, I still had no freeze. If I have one, I will try to format the lot and reinstall the rom with nothing on it as you said.
Fingers crossed mate :thumbup:
that`s happened with the problem with the base rom i mean the stock rom that`s i flashed with odin i changed it an every thing is ok now
I finally format my phone, not because I had freeze again, but because some of my app had strange behavior.
So now I just have the NeatROM Lite version 4.8 installed, with no mods nor theme. Waiting some days to see if it is still stable.
Hard thing to do if you have it set up the way you want but the best way mate. You should find neat Rom is solid. Do you have stock kernel? Philz?
Related
I'm on Gobstopper 2.3.4 and I've recently been modding my phone with faux123's OC kernel, juwe11's ram optimizer, the Webtop hdmi hack and so on, but I recently ran into a problem. Whenever I reboot my phone the widgets don't load and just display as "Problem Loading Widget" in LaucherPro. It might not be because of any of the mods, but it only started happening after I installed them so it's lead me to believe it might be one of them. Please help!!
lexx210 said:
I'm on Gobstopper 2.3.4 and I've recently been modding my phone with faux123's OC kernel, juwe11's ram optimizer, the Webtop hdmi hack and so on, but I recently ran into a problem. Whenever I reboot my phone the widgets don't load and just display as "Problem Loading Widget" in LaucherPro. It might not be because of any of the mods, but it only started happening after I installed them so it's lead me to believe it might be one of them. Please help!!
Click to expand...
Click to collapse
Fix permissions with Rom Manager, or in CWM under advanced, then set up your widgets again. You shouldn't have problems after doing that.
I Also noticed in ADW if I installed a backup configuration within ADW I ran into this problem. If I loaded my widgets after re-loading ADW I did not run into this problem. Caelan's post is also spot on!
I just tried doing that and it came back up as "Problem Loading Widget". I'm using romracer's CWM. Would that make a difference? Should I flash tenfar's? Also, when it boots it seems to almost freeze for a second as my internal storage and sd card are being mounted and then I can slide the bar to unlock.
lexx210 said:
I just tried doing that and it came back up as "Problem Loading Widget". I'm using romracer's CWM. Would that make a difference? Should I flash tenfar's? Also, when it boots it seems to almost freeze for a second as my internal storage and sd card are being mounted and then I can slide the bar to unlock.
Click to expand...
Click to collapse
Fix permissions, reboot, then set up widgets again if you lose them. You shouldn't have any more problems unless you flash another ROM, and possibly another kernel.
Then just do the same thing again if you happen to do that.
This is probably stupid, but you don't have the Widgets installed on the sdcard do ya?
No I have nothing installed to SD. I just tried to fix my permissions and it didn't work CaelanT. They still don't show on a reboot. If I reflash my Gobstopper or another ROM would that work? Should I try fixing the permissions with tenfar's CWM instead of romracer's? Oh and there's a little vibration I feel when the phone boots up right before it displays the lockscreen. Is that normal?
UPDATE: I just noticed that every time I reboot my appwidgets.xml file gets reset!! Please someone help, nothing seems to be working...
lexx210 said:
No I have nothing installed to SD. I just tried to fix my permissions and it didn't work CaelanT. They still don't show on a reboot. If I reflash my Gobstopper or another ROM would that work? Should I try fixing the permissions with tenfar's CWM instead of romracer's? Oh and there's a little vibration I feel when the phone boots up right before it displays the lockscreen. Is that normal?
UPDATE: I just noticed that every time I reboot my appwidgets.xml file gets reset!! Please someone help, nothing seems to be working...
Click to expand...
Click to collapse
Same problem here and only after faux's kernel...I tried all the fixes (fix permissions, wipe cache first before flashing kernel) and the only the thing that worked is to go back to the stock kernel.
Oh man, you may be on to something because EVERYTHING was working fine before last night when I flashed faux123's OC kernel. I'm gonna try and go back to stock and see. Thanks man!
Holy hell that worked!! Back on stock kernel and they are loading fine! I knew it had to be one of the modifications I recently did to my phone and it was the kernel after all. Thanks again!!
P.S. Show we contact faux123 and let him know that his kernel causes widget loading on boot issues?
lexx210 said:
Holy hell that worked!! Back on stock kernel and they are loading fine! I knew it had to be one of the modifications I recently did to my phone and it was the kernel after all. Thanks again!!
P.S. Show we contact faux123 and let him know that his kernel causes widget loading on boot issues?
Click to expand...
Click to collapse
Last couple of posts on his thread already mention it.
Sent from my MB860 using XDA Premium App
Swiftks said:
Last couple of posts on his thread already mention it.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Ok perfect then I'll just wait for his next version and hope that fixes the problem. I need his kernel to flash ROM's since I'm on a international phone. It's weird saying that since I'm just in Canada...
lexx210 said:
Holy hell that worked!! Back on stock kernel and they are loading fine! I knew it had to be one of the modifications I recently did to my phone and it was the kernel after all. Thanks again!!
P.S. Show we contact faux123 and let him know that his kernel causes widget loading on boot issues?
Click to expand...
Click to collapse
No problem man....yeah I've made some comments on the the kernel thread about the issue. Hopefully it gets fixed in an updated version.
in the kernel thread (dev) faux is asking INTL users about this issue, for INTL users on his 1.6 unified kernel. some report the widget issue, others do not. its the kernel causing. I am using unified OC 1.6 kernel and am lucky enough to have no issues, and WAY better batter life then stock kernel.
I also encountered this issue, however I don't have an international version of the Atrix.
Using 2.3.4 (pudding version for AT&T) with Alien ROM #4 and faux123's 1.6unified kernel.
Also using Launcher Pro.... I just reinstalled everything after doing a hard reset to try and isolate the problem, and it did occur after the kernel flash.
Same problem here, luckily I just reboot my phone few time a month..(why do I need a reboot, anyways?)
The widget is left blank white with Problem loading widget warning..
I'm not using an INT Atrix, only AT&T (I don't know if there's any other Atrix version) using faux123 1.6, piecrust, romracer cwm ..
any luck, guys?
would there be an update of 1.8 of faux?
I think I'm going partially nuts over this problem. I have tried every thing mentioned in any post. Fix permissions with different CWM's.
I thought was going to win today today when I formatted everything, installed gobstopper 2.3.4 w/ deodex update then setting up my screens with ADW it glitched and would go to the screen preview whenever I touched the screen. a reboot and those damn black boxes are all over the place.
Order of operations:
- format internal/external
- factory reset
- fastboot flashed tenfars CWM which wouldn't mount the internal sd so I couldn't flash
- fastboot erase/flash romracers CWM
- installed Gobstopper 2.3.4
- reboot and used it for an hour or so to let it level out
- installed the deodex update
- reboot and another hour of use with a bunch of reboots to make sure everything was cool (it was)
- used Diviances EXT4 User Journal script
- used it for a few more hours without issue
- installed ADW Ex and while setting up my screens it glitches and goes to the screen preview with every touch.
- reboot... no widgets with a string of expletives
so now what...
Same problem here. I am using latest Aura Rom with latest faux Kernel for International users.
I did everything: Wiped cache, reseted factory, installed rom again, changed kernel to older versions, stock versions, fixed permissions and always lose my widgets configs after a reboot.
i have Slim's latest on my I777. i am having constant shutdowns & SOD's, like every few minutes. the twist is that i have had the same release of Slim on the phone before, several times in fact, and i had the occasional SOD, but not constantly like now. i have installed Slim a number of times because i like to try new ROMs, and i keep coming back to Slim cus i like JB.
this must be diagnosed, because i believe now that something was messed up a bit along the way of flashing ROMs, mods, and kernels, but our awesome ROM supporters in their threads have their limits they have told me, and i should ask here since this is a general question about the phone & system. i am seeking help here relating to the rest of the phone and system that may become damaged somehow, and i want to clean up my system to end this problem. logcat & last_kmssg linked below.
to be clear: i am rooted correctly, am running the right software for the I777, always check my MD5's from the phone before flashing, clear my caches when needed, wipe dalvik before flashing kernels, etc etc.
interestingly, i fully wiped/factory reset, formatted system, dalvik, wiped batt stats, and fixed permissions, then reinstalled stock Slim last night because i thought maybe my settings were trouble, so i decided to run an out-of-the-box Slim, changing only the dpi and launcher. no change.
i've tried Siyah's latest after running Jkay's kernel cleaner as well. no change. something is making my phone shutdown/SOD constantly, and it may not be the ROM. others don't seem to be having this issue. i have little running on the phone. just accuweather, Date in Tray Pro, and Apex Pro. no overclocking/voltage changes... nothing fancy at all. so i'm just perplexed.
here's the latest logcat: http://davidb.net/logcat_and_device_info(1).zip
here's the latest last_kmssg: http://davidb.net/last_kmsg
if any of you guys can help with this, then thank you in advance.
VR32 said:
i have Slim's latest on my I777. i am having constant shutdowns & SOD's, like every few minutes. the twist is that i have had the same release of Slim on the phone before, several times in fact, and i had the occasional SOD, but not constantly like now. i have installed Slim a number of times because i like to try new ROMs, and i keep coming back to Slim cus i like JB.
this must be diagnosed, because i believe now that something was messed up a bit along the way of flashing ROMs, mods, and kernels, but our awesome ROM supporters in their threads have their limits they have told me, and i should ask here since this is a general question about the phone & system. i am seeking help here relating to the rest of the phone and system that may become damaged somehow, and i want to clean up my system to end this problem. logcat & last_kmssg linked below.
to be clear: i am rooted correctly, am running the right software for the I777, always check my MD5's from the phone before flashing, clear my caches when needed, wipe dalvik before flashing kernels, etc etc.
interestingly, i fully wiped/factory reset, formatted system, dalvik, wiped batt stats, and fixed permissions, then reinstalled stock Slim last night because i thought maybe my settings were trouble, so i decided to run an out-of-the-box Slim, changing only the dpi and launcher. no change.
i've tried Siyah's latest after running Jkay's kernel cleaner as well. no change. something is making my phone shutdown/SOD constantly, and it may not be the ROM. others don't seem to be having this issue. i have little running on the phone. just accuweather, Date in Tray Pro, and Apex Pro. no overclocking/voltage changes... nothing fancy at all. so i'm just perplexed.
here's the latest logcat: http://davidb.net/logcat_and_device_info(1).zip
here's the latest last_kmssg: http://davidb.net/last_kmsg
if any of you guys can help with this, then thank you in advance.
Click to expand...
Click to collapse
Nothing jumps out at me but you need to backup your data and SDCARD to a PC, flash back to stock..... when stock boots up perform a factory reset and test with the stock firmware... if it work fine.... root and install the ROM fresh and clean and test without installing anything else. If it again is fine then install every app from the Market. if you want to restore your recent data afterwards that is up to you but There are so many variables that could be causing your issue and you need to step back and try to find the cause one step at a time.
shoman94 said:
Nothing jumps out at me but you need to backup your data and SDCARD to a PC, flash back to stock..... when stock boots up perform a factory reset and test with the stock firmware... if it work fine.... root and install the ROM fresh and clean and test without installing anything else. If it again is fine then install every app from the Market. if you want to restore your recent data afterwards that is up to you but There are so many variables that could be causing your issue and you need to step back and try to find the cause one step at a time.
Click to expand...
Click to collapse
thanks shoman. much appreciated for the tips.
You wouldn't happen to be using an aftermarket phone charger would you? I was working on a phone behaving like that and it was the charger. If you lifted up on the plug a little while plugged in, it would wake the phone from sleep and constantly restart it. It also did something to the ROM or possibly the Kernel cause it started restarting while not plugged in and the power button quit working. I used a known good Samsung charger and installed AOKP JB with the kernel that came with and it fixed everything. I replicated this problem with two different chargers. It is possible that the USB port on the phone was worn. However, no matter how I moved the cable with a Samsung charger, nothing bad would happen.
beaverslayer said:
You wouldn't happen to be using an aftermarket phone charger would you? I was working on a phone behaving like that and it was the charger. If you lifted up on the plug a little while plugged in, it would wake the phone from sleep and constantly restart it. It also did something to the ROM or possibly the Kernel cause it started restarting while not plugged in and the power button quit working. I used a known good Samsung charger and installed AOKP JB with the kernel that came with and it fixed everything. I replicated this problem with two different chargers. It is possible that the USB port on the phone was worn. However, no matter how I moved the cable with a Samsung charger, nothing bad would happen.
Click to expand...
Click to collapse
no I've never used one.
but it appears this was all caused by the app Screen Off And Lock by Katecca. I had the donate version. its always worked for me on every ROM up through ICS, but it seems to wonk out JB. I changed to Lock Screen App by Kenneth Cheng and have had zero problems in days now, which is a first.
Sent from my SGH-I777 using xda premium
Guyz I recently install jb v5 with phantom kernel. I had some problems with led,sound and battery.. I was charging the phone everyday..I install v4 but same any help?
Sent from my ST25i using xda premium
Hi,
First things first, don't panic!
I have the same setup as you and I'm currently @ 67% after 24 hours so it definitely isn't a problem with the ROM.
Did you follow the instructions from the first post?
Flash custom kernel Phantom[1.0.7]-Performance-CWMTouch
Boot to recovery and flash ST25i_6.2.A.1.100_unofficial.zip..
Full wipe recommended when flashing the first time.
Wipe caches when updating
Reboot to system
Wait for POWER OFF button when you did full wipe if not then just turn off
Flash latest Phantom kernel
Reboot to system
Everything should work now
For point 3/4 above, what did you wipe?
Also what ROM did you have on your phone previously?
Re
MagicMagicD said:
Hi,
First things first, don't panic!
I have the same setup as you and I'm currently @ 67% after 24 hours so it definitely isn't a problem with the ROM.
Did you follow the instructions from the first post?
Flash custom kernel Phantom[1.0.7]-Performance-CWMTouch
Boot to recovery and flash ST25i_6.2.A.1.100_unofficial.zip..
Full wipe recommended when flashing the first time.
Wipe caches when updating
Reboot to system
Wait for POWER OFF button when you did full wipe if not then just turn off
Flash latest Phantom kernel
Reboot to system
Everything should work now
For point 3/4 above, what did you wipe?
Also what ROM did you have on your phone previously?
Click to expand...
Click to collapse
Let me tell you exacly.. I had a problem with the phone .. About led so i decide to change the version and use v4 .. But i recharge it full and i had it on my desk w/o using it for 3 days. The battery was at 40 % and i use it only 1 time for 1 call .. Nothing more...
I flash the kernel wth flashtool. Wipe everything.Install Jb wipe cache and then use the phone. Wait for power off buttom then open again..
I don't know what is the recovery mode btw.. I search it but i didn't find something usefull .I still don't know if i will use Jb Unofficial yet...
I haven't tried v4 of that ROM but I can say for sure that the LED bar doesn't work very well on V5, at least nowhere near as well as DevSwift1's V3 ROM with the latest Phantom kernel.
It does seem to be quite good on battery though; I'm on 1 day, 12 hours uptime with 47% charge left, although I don't use it a whole lot to be fair -- mostly just for music during the day.
I guess you must have used a recovery to flash the ROM zip file... as in CWM (ClockWorkMod)? The Phantom kernel comes with one installed; 1.0.7 has CWM Touch whereas 1.1.0 (the latest version) has a non-Touch version.
The only thing I can suggest is that you try reflashing it again; I'll tell you exactly what I did...
Using Flashtool, put Phantom kernel 1.0.7 on the device and then go into CWM Touch by restarting the phone and repeatedly pressing the Volume Down button when you see the LED bar light up.
Once there do a wipe of data and cache and then go in to the advanced menu and wipe Dalvik cache too.
Next go back to the main CWM menu and flash the zip, then reboot and wait for the phone to start up (should take a while).
Once it has settled down restart it and let it start up again (should take less time)
Finally, use Flashtool to put the latest version of the Phantom kernel on, restart and you're done.
With all that said, I expect I'll be going back to V3 of DevSwift1's JB ROM this weekend as although it's not quite as smooth as pipi14's ROM, the LED bar does work a lot better and for me that is quite important.
Good luck, keep us informed how you got on.
A
Thanks a lot for the informations mate. You help me a lot . But i'm the only one who have this problem with led and battery?
What Jb version you suggest me to use? (link )
What kernel you suggest me to use ? (link)
Any other good apps who will help me ?
Again Thanks a lot .
Btw what is "recovery flash" . I read at pipi's site flash in recovery. What exactly is this?
I've personally tried two Jelly Bean roms:
DevSwift1's V3 ROM (it's now up to V4 which is based on an Xperia Go firmware and has lower-res graphics and some other issues compared to V3, which was ported from the Xperia P).
link
pipi14's V5 ROM (which you have tried and are currently using.)
link
As for kernels I've only used the one that came included with DevSwift1's V3 ROM and Phantom kernel's from v1.0.7 upwards. I know that a number of people have used the Experimental v8 kernel with success on JB but it looks to be more complicated than Phantom.
Experimental v8 kernel
Phantom kernel
From my own experience I will say that I think pipi14's V5 ROM is smoother but I can't get the LED bar working how I want and although it still had a few issues on DevSwift1's V3 ROM it was definitely better.
As far as apps go, it seems the fewer apps the better if you want to stick with JB on your Xperia U -- it doesn't have enough memory and the more apps you have running the worse it will be. Task killers will not help and will probably end up draining your battery more than they help.
A custom recovery is basically a low-level program that you can use to flash new kernels, ROM's and other things on to your phone. ClockWorkMod (CWM) is the most common but others are available. You must have used a recovery to flash JB to your phone before, and if you have a Phantom kernel it comes bundled with one. To get in to recovery mode you need to restart your phone and then press the Volume Down button when you see the boot logo (e.g. Phantom).
a
That's the reason why sony will not send the updates to official JB version .
I will not use Jb now . If they fix it about the bugs i will use . Thanks for the info mate
Btw i use something custom like tera check this http://forum.xda-developers.com/showthread.php?t=2141726&highlight=tera
It's nice based on the ICS w/o so much battery drain and leds bug. I suggest you use this .
This is my first post here so please excuse any violation of rules.
So, I was running CWM recovery + Siyah kernel + CM10.1 + Touchwiz 4.1.2 (dual boot setup) perfectly fine on my Galaxy s 3 for almost a year. But yesterday I decided to update all of those and updated to latest CWM using ROM manager, then changed the kernel to googy max2 and installed CM11. Everything worked properly except that my phone would freeze or hang up randomly at any time(whether swiping through homescreens or updating apps or even during standby). So I changed my ROM to S4 Revoution ROM (tried with both googy max2 and devil kernel). However, even this ROM gave me same hangup problems. So I moved onto TWRP recovery+ OmniRom but still encountered the same problem multiple times. After getting tired of wasting so much time, I came back to my original setup of CWM+Siyah kernel+CM10.1 thinking I wouldn't face this problem again, but to my aghast, the phone would still freeze randomly. Only a power button reboot would help. Please help, I have no idea what might be causing the problem as I have successfully tried every combination of recovery, kernel and ROM but to no avail. And no, I never manually tinkered with any CPU/GPU frequencies or voltages. Your time and help is greatly appreciated, Thank you.
PS: One more very important thing I forgot to mention, CPU-Z shows most of the time all 4 cores of the CPU stay at 1400MHz even though minimum speed is 200MHz. I have noticed this in S4 revolution ROM with googy max2 kernel and pegasusq governor(currently using this setup on my phone). Also, the "devil kernel" app on this ROM shows CPU either stays in deep sleep mode or 1300-1400MHz frequency.
Can't take screenshot for some reason in this ROM otherwise I would have uploaded those too. Thank you.
newoverhere said:
This is my first post here so please excuse any violation of rules.
So, I was running CWM recovery + Siyah kernel + CM10.1 + Touchwiz 4.1.2 (dual boot setup) perfectly fine on my Galaxy s 3 for almost a year. But yesterday I decided to update all of those and updated to latest CWM using ROM manager, then changed the kernel to googy max2 and installed CM11. Everything worked properly except that my phone would freeze or hang up randomly at any time(whether swiping through homescreens or updating apps or even during standby). So I changed my ROM to S4 Revoution ROM (tried with both googy max2 and devil kernel). However, even this ROM gave me same hangup problems. So I moved onto TWRP recovery+ OmniRom but still encountered the same problem multiple times. After getting tired of wasting so much time, I came back to my original setup of CWM+Siyah kernel+CM10.1 thinking I wouldn't face this problem again, but to my aghast, the phone would still freeze randomly. Only a power button reboot would help. Please help, I have no idea what might be causing the problem as I have successfully tried every combination of recovery, kernel and ROM but to no avail. And no, I never manually tinkered with any CPU/GPU frequencies or voltages. Your time and help is greatly appreciated, Thank you.
Click to expand...
Click to collapse
Did you do a complete wipe before installing all these roms? Wipe Dalvik Cache and Cache partition. I am running WanamLite 7.3 with stock kernel and Wanam Xposed. Here is the link to the rom - http://forum.xda-developers.com/showthread.php?t=1705866
Reboot into custom recovery. Do a full wipe, even though this rom says that it is not necessary but it is always a good idea to do a full wipe before flashing. Try this out and let's try to fix your problem.
Hamza18 said:
Did you do a complete wipe before installing all these roms? Wipe Dalvik Cache and Cache partition. I am running WanamLite 7.3 with stock kernel and Wanam Xposed. Here is the link to the rom - http://forum.xda-developers.com/showthread.php?t=1705866
Reboot into custom recovery. Do a full wipe, even though this rom says that it is not necessary but it is always a good idea to do a full wipe before flashing. Try this out and let's try to fix your problem.
Click to expand...
Click to collapse
Yes, and not just once, but every time I flashed a new ROM. I'm thinking my only option now is to unroot and go back to stock but i am unable to find my country's rom. (found one on sammobile but the download speed refuses to go beyond 2-3kbps).
One more very important thing I forgot to mention, CPU-Z shows most of the time all 4 cores of the CPU stay at 1400MHz even though minimum speed is 200MHz. I have noticed this in S4 revolution ROM with googy max2 kernel and pegasusq governor. Also, the "devil kernel" app on this ROM shows CPU either stays in deep sleep mode or 1300-1400MHz frequency.
Can't take screenshot for some reason in this ROM otherwise I would have uploaded those too. Thank you.
newoverhere said:
One more very important thing I forgot to mention, CPU-Z shows most of the time all 4 cores of the CPU stay at 1400MHz even though minimum speed is 200MHz. I have noticed this in S4 revolution ROM with googy max2 kernel and pegasusq governor. Also, the "devil kernel" app on this ROM shows CPU either stays in deep sleep mode or 1300-1400MHz frequency.
Can't take screenshot for some reason in this ROM otherwise I would have uploaded those too. Thank you.
Click to expand...
Click to collapse
Try WanamLite 7.3. Use the link I gave. And install it after doing a complete wipe. See if that makes a difference.
Hamza18 said:
Try WanamLite 7.3. Use the link I gave. And install it after doing a complete wipe. See if that makes a difference.
Click to expand...
Click to collapse
Thank you for the suggestion but i'm afraid that would not help as i have already tried 4 different roms, one of which i used for a year without any problem, but still facing the hangup only since yesterday. plus, I have gone through enough trouble restoring my accounts/apps/contacts and all (especially whatsapp) again and again for the whole of yesterday every time i flashed a new rom. the problem is not related to the rom. thank you, again.
pertsky makes
newoverhere said:
Thank you for the suggestion but i'm afraid that would not help as i have already tried 4 different roms, one of which i used for a year without any problem, but still facing the hangup only since yesterday. plus, I have gone through enough trouble restoring my accounts/apps/contacts and all (especially whatsapp) again and again for the whole of yesterday every time i flashed a new rom. the problem is not related to the rom. thank you, again.
Click to expand...
Click to collapse
See, most of the things in your phone are software related. It is very very rare that you might have damaged the hardware. I see mismanagement of the resources by the ROM or kernel in your phone. What are the steps you are doing when installing a new ROM and which custom recovery are you using?
Full wipe flash stock rom and test ,
Read the FREEZING sticky and SDS sticky .
JJEgan said:
Full wipe flash stock rom and test ,
Read the FREEZING sticky and SDS sticky .
Click to expand...
Click to collapse
I did a full wipe, flashed everything again, did the emmc check as well as the dummy file generator thing....the hangups have reduced to 2-3 per day from 2-3 per hour but are still there. Should I downgrade my cwm recovery?
If you are rooted try the COMPLETE unrooting procedure mentioned at various places by flashing the latest stock firmware available from sammobile. This is to make sure your device software is like brand new. Test it for at least a day. Do a mega wipe (erasing everything even on internal SD card) before which can fix it in some cases.
When rooting again make sure you have the most bug free version of the recovery. CWM 6.0.4.4 is known to have minor problems here and there but nothing concerning to this topic.
~DemonLord~ said:
If you are rooted try the COMPLETE unrooting procedure mentioned at various places by flashing the latest stock firmware available from sammobile. This is to make sure your device software is like brand new. Test it for at least a day. Do a mega wipe (erasing everything even on internal SD card) before which can fix it in some cases.
When rooting again make sure you have the most bug free version of the recovery. CWM 6.0.4.4 is known to have minor problems here and there but nothing concerning to this topic.
Click to expand...
Click to collapse
Hi guys, I experience the same problems: I'm in any app and I press home to go back to the home menu => my phone's freezing for 5 seconds and then I see all my icons/folders/widgets slowly appearing. I would like to know how to complete format my internal SD card like you said. Thanks in advance.
by pressing the powerkey+homebutton+volume up for about 8-10 seconds you are taken to a recovery menu. You can choose to factory reset over there. That fixed problems in most cases. The only way to wipe the internal partition as well would be to install stock firmware which is a part of unrooting, this will erase everything and put a original rom in your phone.. You can follow the unrooting processes written in many posts in xda
Ok thanks for this quick answer ! So the only way to erase the internal SD card is the unrooting method?
Radder124 said:
Ok thanks for this quick answer ! So the only way to erase the internal SD card is the unrooting method?
Click to expand...
Click to collapse
As far as i know yes. Its not any trouble at all, wont take much time, except the firmware you would have to download. Its not needed in most cases. As i said before you may only need a factory reset so try that before! And just hit the thanks button
Hello,
please help me with my S3 ( I9300 ).
Since 8 days I´m encountering a strange behaviour with my S3.
I assume it hast to do with partitions and / or false use of TWRP.
I´ve already flashed numerous times with different phones and recoveries and odin. I Never had any issues before.
Discription : Wiping partitions by recovery does not seem to work. When installing a new rom by TWRP or CWM I end up with two mingeld systems and old apps or I have a clean system but there are absolutely no widgets. When formatting system with TWRP / CWM I sometimes get an error "
I´ve already installed JB stocfirmware with odin with pitfile, repartition and nand erase and that system worked. Fusion rom KK worked too ( installed through recovery ).
But installing omnirom lollipop failed again. Resetting through android factoryreset left my with a clean system but with no widgets at all again.
WTF is going on ?
I think it all started when I used TWRP and did the "fix permission " thing. But I´m not sure there.
I can´t pinpoint what makes installing a rom fail or work . Pehaps I need to completly delete all partitions and rebuild my S3 from scratch ?
Slimkat and Fusionrom ( both KK ) worked at one time and Fr can be restored by TWRP.
Any help would be greatly appreciated !!!!!!!!!!
I just want to be able to try out new roms without running into these problems again.
@Skyfire1:
1. Missing widgets aren't caused by corrupt partitions.
2. FacoryReset from settings maybe not executed correctly in connection with TWRP - reset from TWRP.
3. Try another LP-ROM, if there are still errors.
Thank you. Then what causes the missing Widgets effect? Installing Slimkat worked one time and then again not the other time ? Maybe I have ore than one problem ?
@Skyfire1: I didn't saw/read anything about this. Test gradually. Make shure that JB-Firmware +TWRP 2.8.6.1 work correctly (download all files freshly to avoid fe 9305-choice). Then try a slim LP-ROM, fe Euphoria whithout GApps or other apps (SlimROM is outdated atm) .
Installed euphoria by twrp and no widgets again. But they are there , they just don`t show when using appdrawer button. Longpress on screen makes them available. Is this just a change in Android or what ? I´d feel pretty stupid if that was all
@Skyfire1: I usually don't use stock launcher, but shall flash the actual build from today and will look at your issue.
To whom it concerns: on HomeScreen long tap opens the available widgets. Long tap on a widget and move to place it on HomeScreen.
rp158 said:
@Skyfire1: I usually don't use stock launcher, but shall flash the actual build from today and will look at your issue.
Click to expand...
Click to collapse
I don`t as well. Nova works fine for me
rp158 said:
@Skyfire1:
To whom it concerns: on HomeScreen long tap opens the available widgets. Long tap on a widget and move to place it on HomeScreen.
Click to expand...
Click to collapse
I knew about that. It´s only that I never used that method. I always went to the appdrawer and swiped to the right...
When that didn´t work anymore and the problems with the wiping occured I thought it to be one problem with different effects.
So everything seems to be fine again . I`ll do some testing and flashing .
What I learned from this is that wiping may or may not work and that changes in behaviour of the launcher can have more than one reason.
Thanks a lot for all your help!!!!