I bought device in Europe with German Vodafone 2.3.4/4.5.2A rom.
I get reboots with all roms i tried as well as all custom kernels i tried while these all stuff work on other peoples devices with no issues whatsoever..
Before flashing rom i wipe device with moto-fastboot and cwm like anyone else who is familiarized with the procedure.
I follow all instructions and all but somehow i end up with issues not many people have.
What the hell doing wrong if anything at all?
well this is the wrong section to post in, but have you tried factory resetting from the phone?
Wrong section. It might be that your CPU is getting very hot, so it keeps rebooting.
Tried factory reset off course but i don't have any single issue with stock software. Just with custom ROM's and kernels i want to play with.
Also, I haven't noticed it gets hot that much.
how come it doesn't get hot and reboot that much to other people?
What problems beside the reboots?
Sent from my MB860 using Tapatalk
@schwarzlichtkind, something like widgets missing after reboots, display staying turned on (when talking) when it needs to turn off.. annoying stuff like that..
Which CWM are you using?
Sent from my MB860 using XDA App
when you install a rom do u wipe data, cache, and dalvik cache before flashing the rom?
then do you fix permissions after flashing?
i recommend you do this when you flash a NEW rom, if you are installing an update just wipe cache and dalvik before flashing, then fix permissions after.
latest romracers..i always tend to run latest software, hence the topic
I'm having a similar issue since I got my phone back from repair, no matter what I do faux's kernel 0.2.2 and 0.2.3 cause random reboots and the phone not turning on and heating up. So far 0.2.1 hasn't caused me any problems, hopefully 0.2.1 fixes this and 0.2.4 (in the future) doesn't give problems.
First of all, please post question on the Q&A forum, not on the Android Development one.
Second, please organize your things before asking, and ask a serious question to get a useful answer. Based on your question, 90% of the answers will be guesses.
I reccomend you pick a ROM you like, try it without any custom kernels for a while and see if you get the same reboots. If so, then post a question on the appropriate ROM's discussion thread, don't create a new one just because.
Edit: Post reported btw
Sent from my MB860 using xda premium
Are you sure you fully wiped? data cache and dalvik? if you did you can try using rom manger and official CWM
everytime a flash a rom i use this tool without fail. option 10. then i do the appropriate wipe in recovery. have never had a bad flash. i am anal like that. : )
http://forum.xda-developers.com/showthread.php?t=1314607
I have problems with faux's latest kernels also. Just stick to the stock cm7/blur/MIUI kernels and you should be fine.
Sent from my MB860 using XDA App
try under volting using setcpu. i too had this random reboot issue. but did an undervolt of 100mV (for 1.45GHz). i use faux's 1.45ghz kernel v2.3
have fun!
a possible radio issue i think...
Which radio works better? I have N_01.100.00R
Related
I'm running the newest SC and I keep running into this prblm. I've unrooted and rooted thinking that would fix it. I've ran a pacth file hoping it would be fixed.
I have been reading some post about it and really haven't found the fix or I just missed it. Can some one point me in the right direction.
Sent from my SCH-I500 using Tapatalk
The right direction would be asking your questions in Q&A.
Sent from my SCH-I500 using Tapatalk
First off, wrong section... should be in Q&A.
One way to fix it was to get SetCPU, and make sure the minimum CPU speed is 200MHz
You should also give more information. Have you flashed eb01 with odin before installing SC? How often do these sod's happen? Do you use the clock app?
Sent from my SCH-I500 using XDA App
Questions go in the Q&A subforum.
Here is the only answer that you will probably get that will work (taken from the CWM thread):
GizmoDroid said:
[SIZE=+1]Most Thorough Method of Fixing Every Problem You Might Have[/SIZE]
If you have an issue with applications force closing or a continual boot loop, a lot of times you can fix this issue by running the Fix Permissions option.
If you would like to see your phone be able to have fully functioning Nandroids, and less problems with permission related errors when flashing different ROM's, I encourage you to do the following (this will make your phone as clean and healthy as possible):
ODIN the full stock EB01 package in PDA, the atlas_v2.2.pit in PIT, and "Re-Partition" checked
Let your phone fully boot into the OS and verify everything is working correctly
Remove your battery
ODIN the CWM Recovery package ROM from this post
While reinserting your battery, hold both the volume keys and the power button down until a second after you see the Samsung boot logo
You should see CWM recovery now
Flash the SuperClean ROM from this post, Wipe Cache/Dalvik Cache only.
Reboot. If you have installed the Voodoo ROM, then you should hear a Sexy Robot lady telling you that she is converting your partitions. This process will take 10 minutes or so. If you pull the battery, you will have to start all over again.
Let your phone fully boot into the OS and verify everything is working correctly
If you need to install a theme, reboot, enter CWM and flash theme, Wipe Cache/Dalvik Cache only.
Make a fresh nandroid backup. If you try to restore a Nandroid made with the old CWM, you will probably have problems.
Click to expand...
Click to collapse
If you do this and it still happens, install your apps one at a time. A lot of times it is a faulty application that's doing it (apps that mess with cpu speed/voltage, apps that control power settings, a clock app, and even youmail have all been blamed for it).
Another issue some people have is a certain lockscreen mod with music controls.
str8havoc said:
I'm running the newest SC and I keep running into this prblm. I've unrooted and rooted thinking that would fix it. I've ran a pacth file hoping it would be fixed.
I have been reading some post about it and really haven't found the fix or I just missed it. Can some one point me in the right direction.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
Are you running setcpu ? And if u are and u have a profile for when the screen is off, disable it. That should to the trick
Sent From My Samsung Galaxy S Fascinate Using XDA Premium App - Running Superclean 2.9.1 - 2.2 Froyo
sneakysolidbake said:
The right direction would be asking your questions in Q&A.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
Way to be the post police, but that post was completely uncalled for. You didn't help in the slightest bit. At least the person under you had the courtesy to try and give him a solution, while telling him its in the wrong section.
Thacallmehess said:
Way to be the post police, but that post was completely uncalled for. You didn't help in the slightest bit. At least the person under you had the courtesy to try and give him a solution, while telling him its in the wrong section.
Click to expand...
Click to collapse
Your post isn't helpful to the forum at all, at least there's some community members who like to help keep our forums organized and clean so our Mods aren't overwhelmed. (See how easy that was)
@ OP, there is definitely a SOD patch somewhere in the Fascinate forums that Adrynalyne put out a bit back. I apply it along with the Camera mod every time I flash any new version of Superclean based on EB01/EB16. I'll see if I can post a mirror later when I get back home and you still haven't found it.
The SOD patch is already incorporated in to the latest SC. Gizmodroid's process (based on Adryn's solution to problems with SC2.7 iirc) is your best bet at this stage and worked for me. I would also recommend avoiding TiB as much as possible based on Adryn's comments in the SC2.9.2 thread. If you use Gizmodroid's process, please post your results in the relevant thread. I'd be interested in finding out the degree to which that process solves the issues generally.
I had the same problem. Follow the directions above flashing the stock and then upgrading and avoiding the apps noted above (I think youmail was a big part of my problem) and you should be good to go.
GizmoDroid said:
Questions go in the Q&A subforum.
Here is the only answer that you will probably get that will work (taken from the CWM thread):
If you do this and it still happens, install your apps one at a time. A lot of times it is a faulty application that's doing it (apps that mess with cpu speed/voltage, apps that control power settings, a clock app, and even youmail have all been blamed for it).
Another issue some people have is a certain lockscreen mod with music controls.
Click to expand...
Click to collapse
Thanks everyone for the fast replies even the one telling me i was in the wrong section. Sorry about that
I use both Youmail and the clock app all the time, so thats probbealy why i'm getting the SOD. I also install my apps from my SD card using Astro File Manager and it sounds like that could be causing my problem to.
I installed SetCPU and set the min. to 200mhz, hope that will fix my problems if not
Q1: can I download another clock app and be ok or will it do the same thing
Q2: is there any way of fixing the Youmail app or should I use another voice mail app.
Just want to thank everyone that keeps XDA up and running you guys rock. Love this Forum!
its funny this was posted today since i was literally coming to the forums to post about this very issue.
i have never had the SOD until i followed the instructional to flash back to EB01 with the new CWM.
it started waking slow a day after the wipe and reload, progressively getting worse. i started getting it yesterday bad where i had to restart the phone 4 or 5 times a day to wake it up. then by last night the phone would either freeze, or the 3G or wifi would show as working but i got errors saying no network connection then it would freeze.
PREFACE : FROM MY OWN experience it must be caused by one of 3 things. either the CWM itself, superclean rom, or something with the EB01 file. i have not installed any new programs since the ODIN flash, i did not restore data with TIBU, and i dont use Youmail.
i have also tried reflashing the modem and tried a nandroid restore from the instant i got it running after new cwm proceedure.
its still doing it and has never done it before the flashing.
EDIT: by the way i just realized that my signature here is wrong - forgot to change it.. running stock superclean 2.9.2 with the included kernel, no theme
Samsung Fascinate
SuperClean 2.9.2 & 3/30 -50 Voodoo
Nitro Vivid 1.0 Theme
Member of Android Anonymous, as a recovering Android bricking addict. I have been brick free for over 30 days.
mrjake1970 said:
its funny this was posted today since i was literally coming to the forums to post about this very issue.
i have never had the SOD until i followed the instructional to flash back to EB01 with the new CWM.
it started waking slow a day after the wipe and reload, progressively getting worse. i started getting it yesterday bad where i had to restart the phone 4 or 5 times a day to wake it up. then by last night the phone would either freeze, or the 3G or wifi would show as working but i got errors saying no network connection then it would freeze.
PREFACE : FROM MY OWN experience it must be caused by one of 3 things. either the CWM itself, superclean rom, or something with the EB01 file. i have not installed any new programs since the ODIN flash, i did not restore data with TIBU, and i dont use Youmail.
i have also tried reflashing the modem and tried a nandroid restore from the instant i got it running after new cwm proceedure.
its still doing it and has never done it before the flashing.
EDIT: by the way i just realized that my signature here is wrong - forgot to change it.. running stock superclean 2.9.2 with the included kernel, no theme
Click to expand...
Click to collapse
Are you using the voodoo lag fix?
I think the majority of the incompatibility people are seeing with the fixed cwm is might be some broken compatibility with rfs. It's supposed to be able to handle both, but I think changes in jt's initramfs or changes in the project voodoo files in the kernel that CWM is put into are the root of the problem.
Maybe I'll get some time this weekend to look at it.
In the meantime, everyone should go voodoo/lagfix
yeah giz, im using the superclean "stock" voodoo...
r
tonight im going to go flash happy with the original odin file i used to bump to froyo, and the other old cwm with the broken fixpms and the non fixed superclean 2.9.2 and see if that helps.
i cant be late for work again tomorrow with no alarm from a frozen phone lol
Samsung Fascinate
SuperClean 2.9.2 Voodoo
Member of Android Anonymous, as a recovering Android bricking addict. I have been brick free for over 30 days.
What is the sleep of death?
Update...
I reflashed the original EB01 tar file, modem and the 3/30 red CWM, along with the original copy of the non-fixed superclean 2.9.2 ROM and i am running fine so far with no SOD issues.
As long as this holds true for the remainder of the day I'm going to flash the updated CWM tonight to try and narrow down which of the 3 things i suspect in my previous post is causing it.
Samsung Fascinate
SuperClean 2.9.2 & 3/30 -50 Voodoo
Nitro Vivid 1.0 Theme
Member of Android Anonymous, as a recovering Android bricking addict. I have been brick free for over 30 days.
I downloaded setcpu and put it to 200mhz and been running fine since yesterday. I hope it will last the rest of the day.
Sent from my SCH-I500 using Tapatalk
created a sleep of death..
so, guess what? i created the sleep of death on my phone, and i know exactly what caused it.. not only that, but remembering back to my last sleep of death experience - it was the same exact scenerio..
i was running EC10 debloated, jt's 4/8 voodoo.. i flashed a theme to check it out.. didnt like it, so i re-flashed EC10 over it, with wiping dalvik and reg cache..
booted fine, however i started to notice clock lag almost immediately.. screen went off, and next time i tried to open the phone, i had to hit the power key 4 times before it would light up.. sounded familiar to me from last time, so i let it go about 1.5 hours.. sure enough, would not wake up.. had to pull battery to get it to boot..
i did a nandroid back to prior to the theme flash, and seem to be running ok.. however i am going to do the "clean" flash again tomorrow back to EB01 again just to be sure..
im convinced that is what caused mine both times..i will also be doing that every time i get tired of a theme instead of just flashing a new ROM..im guessing themes are leaving pieces parts behind somewhere that don't play nice with a ROM reflash over it..
I have been having SOD issues ever since I rooted and got set up on SC 2.9.2. However today, I decided to leave my GPS on and since I did that I have not had any SOD. Granted today is not a perfect example because not 45 minutes went by without using my phone, but it seems to have made things better for now, except my battery drains because of it.
Here is the Tutorial I used for Root
http://www.fascinateforums.com/foru...21-how-root-your-fascinate-install-froyo.html
Then I used this tutorial for SC 2.9.2 (non Voodoo, yes i got the right zip)
http://forum.xda-developers.com/showthread.php?t=983395
I'm running
Firmware Version
2.2.1
Baseband version
S:i500.04 V.EB01
Kernel version
2.6.32.9
Build Number
SCH-I500.EB01
I did TiB but have since uninstalled and used My Backup (free). I'm using GoLauncher and related apps. I do use YouMail and will not stop. I know its redundant but I installed the SOD patch too.
I'm going to try all the bandaid fixes first before re-flashing everything.
Search adrenalyne's threads. He had one with a sod patch.
Sent from my SCH-I500 using XDA App
Hi, everyone. I'm used to rooting/ROMing/etc. on the Samsung Epic, but I'm very new to the Thunderbolt. I rooted my girlfriend's phone and had some problems with the data connection being inactive following a kernel install. I went back to as close to stock as I could in order to get everything working again, but new problems have surfaced:
1. GTalk crashes
2. Camera fails to open
3. Documents fail to open, as in Word
4. Phone fails to update, though it indicates an update is ready
Right now, she's on a pretty much stock Froyo ROM and what I believe is the stock kernel, or something very close.
I've read a bit about the camera and gtalk problems. I saw a link to a CWM flashable zip that apparently fixes the date problem that causes the closes. However, it wasn't clear if that zip was only for GB for if it also works for Froyo. Please advise on that.
I haven't seen any reference to the document opening problem, unfortunately.
As far as the update thing goes, I'd rather keep her on a custom ROM, as I assume the update will kill her root.
Basically, I'm looking for a stable and reliable kernel, ROM (preferably GB), and radio combination that is known to run without issues. Last time I tried to pick a combo myself, it ended up killing the data connectivity, so I'm trying to figure out the "best" combination that is known to work. Also, if there are any Thunderbolt-specific flashing procedures that tend to cut down on force closes and errors following a flash, please let me know.
Thanks a lot,
-Rob
When you say update, you mean OTA? If so, you have to be 100% stock to get an OTA to install. You can't have a custom recovery installed.
Pretty much all the GB ROMs out there are pretty stable. The question is, do you want a Sense ROM, or AOSP?
As far as kernels go, Imoseyon's kernels are top notch. I prefer jdkernel for AOSP ROMs though.
I use the latest OTA radio and have 0 problems, and it works for both froyo and GB ROMs.
...
Thanks a lot for the response. I'd like to keep on the Sense side of things, just to keep the user experience sort of like stock for the girl.
So, to go one step at a time:
First, the radio. Is this the latest OTA radio that you mentioned (MR2?): http://forum.xda-developers.com/showthread.php?t=1154010
Second, the kernel. It looks like nerozehl has a great kernel that's based off of Imoseyon's leankernel. There are so many versions, though. Would the latest Sense kernel 2.3.6 (from http://forum.xda-developers.com/showthread.php?t=1099996) be appropriate, considering the ROM below?
Last, the ROM. It looks like SynergyROM is a good place to start. I believe the latest one is found off the download link near the top of this page: http://infectedrom.com/showthread.p...IGHTLYS-2.3.4-SENSE-3.0-★-☆-★?p=4368#post4368 Any thoughts on SynergyROM?
Does that combination seem like one that should work correctly?
Also, just so I have the steps correct for installation:
1. Flash radio in hboot.
2. Wipe in CWM (cache, dalvik cache, anything else?)
3. Flash kernel in CWM.
4. Flash ROM in CWM.
5. Reboot.
Thanks again for any help. It is definitely much appreciated. Can't go around breaking the girlfriend's phone, after all...it just looks bad!
-Rob
There is an issue with the lib files for the Camera ,which is messing up Gtalk. There is a fix in several threads, something HTC did on the new base.
Here is the fix:
http://themikmik.com/showthread.php?8436-Flashable-G-talk-Camera-Fix
...
Thanks, fillyo! I assume this works for both GB and Froyo ROMs?
-Rob
If you flash the kernel before the ROM whatever kernel comes built in to the ROM will overwrite the kernel you just flashed. I would say ROM, kernel, radio.
Oh and when you wipe I would do:
1. Wipe data/factory reset
2. wipe cache
3. Advanced, wipe dalvik cache
4. Under mounts and storage select format /system
Sent from my HTC Thunderbolt
JBO, thanks for the advice. That makes a lot of sense. Do you have any comments on the radio, rom, kernels I've selected above? Particularly the radio. I was told the latest OTA radio works well, but is that the one also knows as MR2?
Thanks,
-Rob
Sent from my SPH-D700 using XDA App
Yes the MR2 radio will work with that ROM as well as any leaked radio that is newer than the MR2. What radio works best is kinda subjective and seems to vary from person to person. I don't know if the kernel you linked is compatible you would need to ask in the Synergy thread. Honestly as far as the kernel goes I would just use the one built into synergy. I hear its quite good and has a great set of features.
Sent from my HTC Thunderbolt
I've used SynergyROM and it is an awesome ROM. It comes with Ziggy's kernel, which is an awesome kernel. The OTA Radio basebands are 1.39.00.0627r, 0.01.69.0625r
I hope you find a ROM/kernel/radio combo that works for you!
That's exactly the info I needed. I'll just stick with the built-in kernel and the MR2 radio. Thanks for all the help, guys.
-Rob
Sent from my SPH-D700 using XDA App
I saw that there was a similar thread in the Epic 4G forum, but I wanted to make sure before I start trying something that might mess up the phone even further. My wife's vibrant will start having everything force close on her after a few weeks. This has happened on 2 or three different ROMs, and I'm not sure what's causing it. I saw the similar thread where it might be related to "journaling", but we don't change her battery out at all or even reboot the phone that often, so I'm not sure if its the same issue. I've done a reset of her phone a few times, but I'm on a GB ROM so it doesn't go completely back to factory. Should I try to ODIN to stock? Any ideas why this happens? Thanks in advance.
Try fixing permissions in CWM first and see if that helps.
Sent from my SGH-T959 using xda premium
Fix permissions worked for a while, but not anymore. Everything's force closing again. Will the journaling fix help?
Anybody have any ideas? Gonna wipe then install a newer ROM, but I want to make sure this doesn't happen again.
Only titanium the "necessary" apps that you wanna keep your data from. Then uninstall it - often I find that this helps for some odd reason.
Sent from my SGH-T959 using xda premium
chairhome said:
I saw that there was a similar thread in the Epic 4G forum, but I wanted to make sure before I start trying something that might mess up the phone even further. My wife's vibrant will start having everything force close on her after a few weeks. This has happened on 2 or three different ROMs, and I'm not sure what's causing it. I saw the similar thread where it might be related to "journaling", but we don't change her battery out at all or even reboot the phone that often, so I'm not sure if its the same issue. I've done a reset of her phone a few times, but I'm on a GB ROM so it doesn't go completely back to factory. Should I try to ODIN to stock? Any ideas why this happens? Thanks in advance.
Click to expand...
Click to collapse
Get into recovery:
wipe dalvik
wipe cache
fix permissions
reboot
wait 10 mins reboot into recovery again
fix permissions
reboot
open rom manager [worth its weight in gold!]
fix permissions
reboot
Thats what I did with my cm7.1.0.1 but I also installed eugenes streamline 110411 ver and [knock on wood] havnt had any more issues with fc's.
And yes even if you follow the installs to a "T" some of us still have the FC issue!
Good luck!
3 weeks later and I'm back to square one. I'll try the above, if it doesn't work, i'll have to wipe and reinstall. thanks. What's eugene's streamline?
Id flash to stock, flashing different roms wont help if theres a ghost in the machine, what launcher are you running...touchwiz sucks on my wimpy replacement phone.
Sugartibbs said:
Id flash to stock, flashing different roms wont help if theres a ghost in the machine, what launcher are you running...touchwiz sucks on my wimpy replacement phone.
Click to expand...
Click to collapse
MIUI's launcher. I'll probably try flashing to stock soon. :-(
No go. I'll have to look into Eugene's streamlined 110411
ok just for future sake, 3 rule's of flashing,
it's better to reinstall your applications manually then to trust titanium when bouncing between roms with different frameworks, versions, partitions, etc.
always flash from stock unless your updating a weekly rom ie cm7/miui
after flashing power off screen and have a cup of coffee/beer/shower. give the OS time to do all it's background configurations and setup.
now if you follow those 3 rules you "should" have no real issues.
Hi,
Not sure where to report this kind of thing but I seem to be getting frequent lockups on my S2 with the Resurrection Remix 3.1.3 that I wasn't getting with the previous 3.1.2.
abc.mikey said:
Hi,
Not sure where to report this kind of thing but I seem to be getting frequent lockups on my S2 with the Resurrection Remix 3.1.3 that I wasn't getting with the previous 3.1.2.
Click to expand...
Click to collapse
You mean freezes and/or fc's? You actually have to ask in the RR-thread, but I understand you only have posted 8 posts for now.
Remember RR 3.1.3 is still very new and under development, and isn't as stable as 3.1.2 is. If you want more stability, flash the 3.1.2-version.
And did you flash it with a full wipe? It's a must.
Sent from the Matrix
abc.mikey said:
Hi,
Not sure where to report this kind of thing but I seem to be getting frequent lockups on my S2 with the Resurrection Remix 3.1.3 that I wasn't getting with the previous 3.1.2.
Click to expand...
Click to collapse
The normal procedure would be to first read through the posts on the roms dev thread and see if others have had same issue and what (if any) solution is. if you dont see any comments then make one of your own explaining issue (You wont be able to do this until you have 10 posts).
Before leaving any replies on topic you should try doing a wipe/factory reset in recovery then boot to system see if you have same issues. Its advised to wipe recovery before each rom flash (Unless you have stock kernel, If you have stock rom/kernel you need to flash custom kernel before wiping. You can mostly ignore wiping if you are updating to new version of same rom however its still advised as somtimes can lead to issues.
You dont need to worry about apps/appdata and sms etc as you can easily backup them with Titanimum Backup Pro and SMS Backup etc. Get pro version of TB as you can batch backup/restore app/appdata in one go.
Donnie Sins said:
You mean freezes and/or fc's? You actually have to ask in the RR-thread, but I understand you only have posted 8 posts for now.
Remember RR 3.1.3 is still very new and under development, and isn't as stable as 3.1.2 is. If you want more stability, flash the 3.1.2-version.
And did you flash it with a full wipe? It's a must.
Sent from the Matrix
Click to expand...
Click to collapse
Thanks for the replies!
It freezes as in apps start becoming more and more unresponsive, sound if playing starts to stutter more and more until it ceases playing at all and phone us completely unresponsive except to a long hold if the power button. Sorry but I don't know what FC is.
I upgraded because the notifier informed me that there was a new ROM; I see now that it's a good idea to wait a bit now. I've downgraded to 3.1.2 which I've been very impressed with the responsiveness and stability of.
My first attempt at installing 3.1.3 was an attempt at an upgrade but didn't work very well as I think I followed the wrong procedure. But the issues I was having were with a wipe and reinstall following all the steps in the manual plus an undocumented one to install the keyboard patch for the S2 to make the keyboard work at all.
TheATHEiST ok will try reporting there next time, hopefully my post count will allow it by that time
TheATHEiST said:
The normal procedure would be to first read through the posts on the roms dev thread and see if others have had same issue and what (if any) solution is. if you dont see any comments then make one of your own explaining issue (You wont be able to do this until you have 10 posts).
Before leaving any replies on topic you should try doing a wipe/factory reset in recovery then boot to system see if you have same issues. Its advised to wipe recovery before each rom flash (Unless you have stock kernel, If you have stock rom/kernel you need to flash custom kernel before wiping. You can mostly ignore wiping if you are updating to new version of same rom however its still advised as somtimes can lead to issues.
You dont need to worry about apps/appdata and sms etc as you can easily backup them with Titanimum Backup Pro and SMS Backup etc. Get pro version of TB as you can batch backup/restore app/appdata in one go.
Click to expand...
Click to collapse
I can confirm that I have followed all the procedures (flashed at least 20 differet roms by now) and can also confirm that I have been facing a laggard and slow responsiveness throught out the rom, with couple of FCs and lockups as well. At least thrice I had to force reboot. Also I have done an extensive search and the only thread I could see on the similar issue was this.
I am posting here because of same reason as OP as I have a low post count but I have been following xda for over 2 years now.
I know the obvious answer is to downgrade to 3.1.2 or not install RR at all. This is "just reporting", you know!
Thanks!
Hey, I am also experiencing the same thing as the OP and 7mojo. My S2 would randomly freeze and the only way to get it working is a hard reboot. It happens randomly but quite often, I would say atleast 3 times a day. I have done a full wipe and re-install but no luck. Like 7mojo said, I too have searched the web and the only thing relating to this issue is this thread. Anyone else having this problem? any solutions? I hope there is an update soon.
Nevethen5 said:
Hey, I am also experiencing the same thing as the OP and 7mojo. My S2 would randomly freeze and the only way to get it working is a hard reboot. It happens randomly but quite often, I would say atleast 3 times a day. I have done a full wipe and re-install but no luck. Like 7mojo said, I too have searched the web and the only thing relating to this issue is this thread. Anyone else having this problem? any solutions? I hope there is an update soon.
Click to expand...
Click to collapse
I've had similar problems.. am guessing its due to bugs in the unstable rom. Will have to wait for the dev to release an update. For the time being, better stick with 3.1.2.
As for me, I switched to JellyBAM. And then to CM10.1. And then to Omega.
"To err is human, to forgive is divine"
Sent from my SGS II
i have flashed the latest version of RR 5.0.8 rom but for some reason my internet is not working though wifi is connecting properly ..i have tried factory reset and re installing the rom but the problem still persists ..can someone please help me out ?
hej
try full wipe
A longer friendly answer
tr!ckst3r said:
i have flashed the latest version of RR 5.0.8 rom but for some reason my internet is not working though wifi is connecting properly ..i have tried factory reset and re installing the rom but the problem still persists ..can someone please help me out ?
Click to expand...
Click to collapse
ROMs are tricky things in my experience.
I've tried most of them and most of the ones I tried have really bad flaws - for my phone.
When one doesn't go so well for you - like the RR ROM, it's time to move on and try another.
After following the instructions of course, like full wipe, cache, blah blah blah. Try it twice, the second time following instructions really closely.
I found the PA and offspring to work really well - for my phone.
In the end, play and learn. It's fun and really difficult to completely wreck your phone.
Pete
^^^
Might be a longer friendlier answer but the answer is essentially nonsense. The OP has a specific problem. Posting waffle like you just did smacks of wanting to get your post count up because it doesn't help the OP one bit.
OP - You haven't given us anywhere near enough info to help you. Connectivity normally just doesn't go away all of a sudden unless you've made changes to your setup, or there's a carrier-side issue causing the problem.
What have you done with the phone recently setup-wise, have you been messing around with RIL's or modems ? If it's the latter, then you need to try more modems. If it's neither, I'd be going back to stock (a rom for your carrier, so you get a modem that should work), then reinstall the rom you're using. If that doesn't work, flash the 3 part firmware in Hopper8's 'Odin troubleshooting' thread stickied in General (this will wipe your phone, backup first), then flash stock for your carrier, then reinstall custom rom.
If the problem persists after all that, then you're looking at carrier-side issues or perhaps even a hardware issue. WiFi working & data not have no bearing on each other as WiFi drivers are in the kernel & separate to data connectivity.
We would need more information as to how did you flash the new ROM? Are you using a separate Kernel? Which GAPPS version did you flash?
I am also on the RR 5.0.8 with Dorimanx kernel. Also, I used the light version of GAPPS for flashing. Try using the light version if you have not used it.