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 .
Related
Ok, so I flashed JT's Vanilla gingerbread rom using CWR 4 and everything seemed fine. I then flashed B Boy Blizzard theme and everthing ran fine for about twenty mintes, then I got what I thought was the sleep of death (only when I pressed the sleep button). I pulled the battery and powered the phone back on. The phone booted into recovery and I got and error 7 cache recovery unable to mount message. I really like what little of the rom I saw and the theme. I sure at this point I'll have to Odin back to stock as I can't do a recovery either (same error message). What I'd like to know is this just a problem I'm having or is there something wrong with the rom or theme? Please advise. Thx in advance.
I have had alot of problems with that rom aswell...not really sure whats going on. Sometimes the rom will install with cwm 4 other times it just boot loops. I have tried every install method for that rom and nothing yet seems reliable. I have no problems flashing other roms, so idk... just chillin with powerwash right now until the bugs get worked out w/ VGB(hopefully).
All of his themes (at this moment) are based on 080211 v2 VGB. And between v2 and v3 there were framework and other apk changes i.e. settings. So flashing that theme on top of v3 will surely lead to issues. Just reflash rom. And make sure the theme you try only says for v3.
good day.
Also, you wont boot into the right recovery using the 3 finger method. you need to use adb or the reboot options
Hey guys,
here is what is going on with my German Vodafone I9100
After using Sensation Rom for a few months, I finally decided to make the transition to Android 4.
The first rom I tried, was the Simplistic ICS by LegendK95
Installing from CWM worked like a charm, booting worked like a charm, but whatever I tried to do, the phone freezed in homescreen randomly after 5-30 seconds. Only a restart bring it back to work, only to make it freeze again after the mentionend time span.
Whatever I did (waiting in home screen, pulling down the statusbar, scrolling in app drawer) the phone always freezes.
After dozen of restarts, I installed the rom again, the problem stayed.
Then I decided to go to stock 4.0.3 (LP6). Installation via Odin worked like a charm. Booting worked like a charm, but the homescreen-freeze-problem got even worse.
I also tried to reinstall the stock LP6, but the phone now even froze in CWM mode, while data reset AND WHILE INSTALLING THE FW.
Now I got a soft brick in my hands.
So, I installed stock 2.3.3. via Odin. The phone now worked flawless again. No freezes, no no nothing. Just a working phone.
My final try was to install the latest CM9 build.
Guess what happend?
The legendary homescreen freeze. That nobody else appear to have. YAY
So, somehow my phone seems to be allergic to Android 4.
Can somebody please help me?
Regards
PS: Yes, I followed the instructions every firmware provided.
Honestly you want an honest answer. Stay clear of ICS leaks and yes that means even cm9. Reason being. Because of what they are. Leaks and nothing official. Not saying that they are not good but if you look at the original android development can you see any actual ICS roms? No. Why you asking? Because no kernel sources have been released and nothing is far from stable yet. Even cm9 builds codeworkx has on the thread title experimental. So my advice. Flash a Gingerbread custom rom slap on it the ICS by vertumus and your good to go till the official stuff get released.
Maybe before flashing ICS you should fully wipe your device to get rid of all previous ROM data from Gingerbread as they,I imagine,wont be very compatable.
Boot to recovery and go to "mounts and storage" and format System/Data/cache and then factory reset.Then flash the Rom via recovery(install zip).If its an Odin flash then reboot and flash via Odin.
Hi suarez,
thanx for your opinion. I read a lot of threads before updating and came to the conclusion that the current releases, even CM9 seem to be pretty stable.
Also I found no one having issues like that.
Hi cooza,
I did that.
Klammeraffe said:
Hi suarez,
thanx for your opinion. I read a lot of threads before updating and came to the conclusion that the current releases, even CM9 seem to be pretty stable.
Also I found no one having issues like that.
Hi cooza,
I did that.
Click to expand...
Click to collapse
No problem my friend. But I still stand by what I said though. For me to make the jump is a no go yet. Yes they might be stable but so far I still read problems regarding video forever, this is not working that does not work and that most issues will be solved once kernel source is available. Hence why still the experimental on cm9.thread.
Sent from my GT-I9100 using xda premium
Suarez7 said:
No problem my friend. But I still stand by what I said though. For me to make the jump is a no go yet. Yes they might be stable but so far I still read problems regarding video forever, this is not working that does not work and that most issues will be solved once kernel source is available. Hence why still the experimental on cm9.thread.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Yes, but if you're not that big into watching/recording videos on your SGS2, it's pretty freaking stable.
Installing the latest experimental build of CM9 is probably the best thing I've done to my SGS2 as of late. It's just so... Nice.
I cannot get rid of that problem.
I really need help on this.
Some new information:
I also tried to flash the leaked stock LP2. Same result.
This FW crashed on first start, when the Samsung Apps are installed.
Still some little success:
When flashing from stock BUGKJ2 straight to LegendK95's Simplistic ICS rom, I was able to get it to run, until I have to restart the phone.
But this was the only rom capable of doing so. Every other fw failed.
So, I now can have ICS on my phone but only until I restart the phone.
After reboot, the phone crashes again after some seconds.
Additionally the CWM Recovery doesnt work as long as I have a ICS rom on it.
It also occasionally crashes. Preferrably when I try to flash a new rom, leaving me a shiny brick
Here are the steps to get Simplistic ICS run until reboot:
1. Put the file on internal memory.
2. Go to recovery: wipe data/factoy reset, wipe cache, wipe dalvik, wipe battery, format system, format data, format cache
3. Flash from internal sd
4. Reboot
Klammeraffe said:
Some new information:
I also tried to flash the leaked stock LP2. Same result.
This FW crashed on first start, when the Samsung Apps are installed.
Still some little success:
When flashing from stock BUGKJ2 straight to LegendK95's Simplistic ICS rom, I was able to get it to run, until I have to restart the phone.
But this was the only rom capable of doing so. Every other fw failed.
So, I now can have ICS on my phone but only until I restart the phone.
After reboot, the phone crashes again after some seconds.
Additionally the CWM Recovery doesnt work as long as I have a ICS rom on it.
It also occasionally crashes. Preferrably when I try to flash a new rom, leaving me a shiny brick
Here are the steps to get Simplistic ICS run until reboot:
1. Put the file on internal memory.
2. Go to recovery: wipe data/factoy reset, wipe cache, wipe dalvik, wipe battery, format system, format data, format cache
3. Flash from internal sd
4. Reboot
Click to expand...
Click to collapse
Maybe the problem is the stock firmware you first flash.I searched for it but cant find it,is it carrier branded?..BUG sounds like it to me.Maybe you should fully wipe your phone (format System/Cache/Data) and first flash something like XWKL1 and then the ICS ROM.If the ICS ROM you are going to flash has a multi CSC package in it then it wont matter what F/W you flash first.
hello cooza,
i had to go back to stock 2.3.3 because my phone was a brick after flashing any ics rom.
i tried to flash simplistic ics and cm9 via cwm, i dont know if those contain multi_csc.
however, the leaked stock roms, lp2 and lp6 both contain multi_csc that i flashed via odin.
here are all the steps i tried:
fail 1: flashing from sensation rom 3 (2.3.6) to simplistic ics
fail 2: flashing from 2.3.3 to cm9/simplistic ics
fail 3: flashing from bricked ics to stock lp6
fail 4: flashing from 2.3.3. to 2.3.5. (latest official release via kies) to cm9/simplistic ics/stock lp6
fail 5: flashing from 2.3.3 to leaked stock lp6 inluding the pit-file provided
nevertheless, flashing from 2.3.5 to simplistic ics worked until restarting the phone. however, cwm was not working correctly then. so, surely i could have tried to let the phone on for forever, but as soon as i would want to flash a new firmware, i would have got a brick left, because cwm would crash during installation of the new one.
there must be some help out there
thanx for trying cooza. much appreciated.
You might have a damaged bootloader.Although its not needed you could try a JTag.A JTag is used to bring a hard bricked phone back to life.You dont have a hard bricked phone but what it also does is repairs any damage that the bootloader may have.Costs about 25 to 30 euros.As a last resort you could give it a go if your phone is going to give you constant reboot problems and not let you flash firmwares.It should also repair any repartition faults because it completely wipes the bootloader before repairing it.The phone will come back like the first day you got it.check the link below out and use it to find one close to you if you choose to do one.I had an i9000 done last September here in Spain and it came back perfect from a hard brick soo I know it works.I used the link below.
http://www.jtagbox.com/riff-jtag-bo...-bricked-phone-riff-box-owners-list/#comments
Seems like the very last option to me
Would a broken bootloader allow me to run 2.3.X flawless?
Question does Samsung stock firmware work .
As it seems all your problems are from using a buggy unreleased test rom not from using Samsung released firmware .
I would if it was my problem .
Clean Slate for those that balls up the firmware .Or need to return to service or decide if its hardware/firmware problem .
Backup data first if phone is working .
Boot CWM recovery
Mounts and Storage
Format cache data system sd card wiping everything on the phone .
Remove battery
Boot to download mode
Open Odin
Install correct Samsung stock firmware for your phone model .
Test phone works .
jje
hi JJ,
thanks for your post.
as i said, the phone is working fine on stock android 2.3.X as well as custom firmwares using 2.3.X.
However, all 4.0.X firmwares I tested, showed the same behaviour: crashing my phone in homescreen (or anywhere else after booting) AND in cwm after 10 to 30 seconds.
only simplistic ics custom rom worked fine until first reboot. then it crashed as well. everytime.
I tested 2 stock firmwares of samsung and 2 custom roms.
I also tested flashing 4.0.3 (CM9) on a friends SGS2 using the same procedure I used on my phone. It worked on first try and he`s now a happy android 4 user.
right now i`m running on CM7 but i wanna uprage to android 4.
edit:
up to this date there is no official released 4.0.3 rom for the sgs2 but how can it be that I have the only phone showing such a behaviour while everyone else has a 99% stable fw for the same phone using the same rom?
Mate,at least it works,thats the important thing.I can understand that its frustrating when the only Firmware/customROM you want doesnt work in your phone and only your phone but we are talking about BETA version ROMs.If there is something for some reason blocking the ICS ROM then it is possible that the JTag will clear it up as it wipes and repears the bootloader as I mentioned so any corrupt data will dissappear.Ive had a bricked phone done and it still works perfectly today but never a phone in your situation.Its possible but never having done so I cant guarantee it.If you want give it a go.You got nothing to loose except 20 or 30 bucks for your efforts.
I have exactly the same issue with a "german" Galaxy S2. I tried to install the {CWM}İCS REMİX ROM v8.4 ULTİMATE ONLİNE XXLP6 4.0.3 resurrection NO-WİPE
Version.
Followed ofcourse the installation instructions letter for letter. It doesn't go over the logo screen. ( And yes I am aware it takes several minutes for such an installation to finish)
I read in that thread of at least another 3-4 people with the same issue.
Going back to any 2.3.x works as usual.
If you take the time and read the various ICS posts one inescapable fact will arise .
ICS suffers from many varied problems with no two users reporting identical problems .
That is compounded by two factors one the boot loader and two as a beta test rom for some strange reason those with very little knowledge rush to install it .
But hey save money on the Samsung testing department just leak your Alphas and Betas .
For me i will play with a test rom for an hour or two but thats it i require a stable rom for daily use . It will need vast improvement for me to consider the final release of ICS for daily use .
jje
spytrek said:
I have exactly the same issue with a "german" Galaxy S2. I tried to install the {CWM}İCS REMİX ROM v8.4 ULTİMATE ONLİNE XXLP6 4.0.3 resurrection NO-WİPE
Version.
Followed ofcourse the installation instructions letter for letter. It doesn't go over the logo screen. ( And yes I am aware it takes several minutes for such an installation to finish)
I read in that thread of at least another 3-4 people with the same issue.
Going back to any 2.3.x works as usual.
Click to expand...
Click to collapse
GSMArena say that Samsung are launching ICS for the S2 in march
http://www.gsmarena.com/samsung_galaxy_s_ii_and_galaxy_note_to_get_ics_in_march-news-3752.php
with this I imagine that stable ICS custom ROMs are just around the corner so if you can wait a few months more you will be able to flash a stable safe ROM without any problems.Until then the BETA versions that are out at the moment are going to cause these types of things.
I had these same isues with KP8 on my s2. I fixed them by flashing LP6 directly over kp8 without wiping anything. I think it may have something to do with the phone drivers you have installed on your pc. They may be damaged and be producing some kind of error on the flashing proccess. I recomend that you hard reset to 2.3.x and reinstall kies on your pc. That should reinstall phone drivers too. And make sure kies is NoT running while using odin. Kies doesent like odin
Sent from my GT-I9100 using Tapatalk
I have patience As long as I fallback to a functional rom everyting is cool. As for the alpha-beta testing, I have nothing against it and I didn't complain about it. Till March I hope the S3 is out so I can pass my S2 to my better half ...
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?
Hi all, I flashed today Paranoid Android 3.99 - 29.08.2013 (I come from Vanilla RootBox) on my Samsung Galaxy SII, and I noticed that except for gapps everytime I flash something else the phone stuck on the bootscreen.
I flashed Dorimanx 9.39 and it worked at first but after a reboot it got stucked, after I kept the stock kernel of the ROM and try to flash PurePerformanceX and it got stucked again.
Procedure before and after flashing ROM and everything else:
1. Nandroid Backup
2. Wipe Data
3. Wipe Cache&Davlik
4. Flash PA 3.99
5. Wipe cache (just for safety )
6. Flash Gapps
(6.1. Flash PurePerformanceX the second time without installing the Dorimanx)
7. Flash GS2KernelWIpe2.09
8. Flash Dorimanx 9.39
I tried also to do point 7&8 before the 6, but it's the same.
Anyone else having this kind of problem?
Cheers!
Moae
Nope, I haven't tried that version of PA yet, it's on my to-flash list but testing something else right now. You mentioned using hawkerpaul's kernel wipe script...
What I would do (and personally follow every flash) is:
Flash ROMNuke script by hawkerpaul
Flash PA
Flash Gapps
Flash dorimanx
No other wipes other than the ROMNuke script. Then, see if it boots (& reboots). If it does, then flash your performance mod. If that causes bootloops, my guess is that the performance mod isn't updated for 4.3 yet. Either find a new performance mod, or tune dorimanx so you don't need one
See how you go.
Sent from a galaxy far, far away
at first I tried without PurePerformanceX, just PA+Gapps+Dorimanx. I actually use to flash the kernel before flashing gapps, 'cause a lot time flashing gapps before the kernel gave me some problem.
to answer to the other question, yes, I used the GS2KernelWipe by hawkerpaul
By the way, there is a guide for a good tuning of Dorimanx kernel?
Ok so have you tried his ROMNuke script? Never had an issue if I flash that before a ROM /kernel /gapps.
Hmm. Depends on what you want it for. I tune mine for battery, but not to the point of any lag. Someone else doesn't care about battery, and just wants s3 speed on a 2 year old phone. See what I mean? In saying that, read the last 5-10 pages of the Dorimanx discussion thread. That'll give you a pretty good idea of what works for performance. Obviously a god step is the 'performance' profile in Stweaks
Sent from a galaxy far, far away
I'm doing backups before trying . Let you know how it will go.
I'm actually looking for a good battery life but avoiding lags , anyway thanks for the tips
it seems working properly now! thx for all
Moae said:
it seems working properly now! thx for all
Click to expand...
Click to collapse
Good to hear! Re: tuning dorimanx, search for (it may even be linked in OP of dev or discussion thread) for a post by droidphile on governors, i/o schedulers etc. That's a great place to start. Wait I just found it, look here http://forum.xda-developers.com/showthread.php?t=1369817. Start reading up there :good:
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