My wife has this phone and I have CM10 on it currently. This issue seems to have been consistent throughout all the ROMs I have used. It's had the stock ROM, ParanoidAndroid and CM10 on it and it will still occasionally lock up the phone and restart itself.
I don't know if it's software related or hardware related, but I do know that it continues to happen after clean wipes with different ROM's.
Any advice on what we can try to get it resolved or are we SOL?
Thanks
Flash the official JB or the Padawan JB.
Related
Hi,
We have 2 Vibrant phones. 1 is on Paranoid Android 2.54 (via stock eclair, ICS Passion, Slim Bean 2.9 & 3.0) and works perfectly.
The second one was on ICS Passion for a long time and I have finally got around to (trying LOL) to update it.
Here is where the weirdness begins - Flashed PA 2.54 no problems, flashed and booted up, but no wi-fi, well no wi-fi icon, and it can find a couple of wi-fi networks belonging to my neighbours, but won't find my network, 2 rooms away. The network is obviously all good, I am sending this from my laptop through said network.
Obviously I need an internet connection to get through the phone setup, so I power down, throw the SIM back in and boot up only to find no cell data either.
Skip the google account setup and get to the home screen to check things further and I find:
Calls in/out work, and most things are running, but wi-fi won't co-operate, and nothing in the APN list? Baseband and IMEI all look normal, too.
Try to flash Slim Bean 2.9 as I put the zip on the phone at the same time as a fallback and I get EXACTLY the same thing...
Anyone able to shed any light on what would cause this? Anything else worth trying? I'd like to avoid Odin as it honestly scares me reading all the problems people on here have with it...
At this point I've tried flashing both ROMs a few times with exactly the same results, I also can't go back to the ICS nandroid as the partition setup has changed and the restore doesn't work...
Thanks in advance for any help anyone can give.
Cheers...
I ended up flashing a 4.2 ROM (slim 4.2 beta 1) and it made the problem go away, I'm guessing something in the 4.1 base was broken and not getting overwritten on new installs?
ROM seems pretty sorted for a beta, few minor things not working, but hopefully it gives us a clean upgrade path...
Thanks.
I had the same issue with Slim 4.2 Beta 2. If anyone has a solution other than flashing the modem, please post.
Weird. The phone I was having this problem with now has that ROM on it and is working 100%.
I have a suspicion that flashing a ROM that uses a different kernel is what fixed it for us. I guess it just overwrites/replaces more stuff?
Maybe try hellybean 4.2 and see if it makes a difference, and if it does flash back to slim 4.2 and see if the problem comes back?
I have installed slim and other ROMs but not had this issue. Currently on jellybam
Sent from my GT-I9300 using xda premium
wendleburger said:
Weird. The phone I was having this problem with now has that ROM on it and is working 100%.
I have a suspicion that flashing a ROM that uses a different kernel is what fixed it for us. I guess it just overwrites/replaces more stuff?
Maybe try hellybean 4.2 and see if it makes a difference, and if it does flash back to slim 4.2 and see if the problem comes back?
Click to expand...
Click to collapse
The weird part is that every other Slim Bean has worked great. I'll keep my fingers crossed for beta 3.
Hi, i've been experimenting this problem for 2 months. I've got CyanogenMod 9, but before I flashed Cyanogen Resurrection 4.0.3 and I formated everything as possible (Wipe Data, Cache, Dalvik and format /system). The battery doesn't lose charge when I restart it.
Thanks!
So, what is your question..?
Sent from the Matrix
If any of you have the same problem and know the solution. I've read other messages like mine, but I'm not in the same circumstances. I haven't got any apps except social (whatsapp, twitter...) none of my apps it's draining the battery I simply don't know why my phone shuts down by itself
You're running stock kernel right? Have you changed anything at the Performance-menu at Settings? And when do this reboots occur?
Have you tried flashing for example CM10.1 to see if the same problems come up? You could make a Nandroid backup to try this.
Sent from the Matrix
Thanks for the answers. I have the stock cm9 kernel. I don't touch anything at the performance settings. Actually, this problem comes from a couple of roms more. AOKP, ParanoidAndroid, and another one 4.2.1 which I don't remember the name. I've tried a stock ROM before but the performance was not good at all, freezes and slow work at general. Thanks.
Make a full wipe (4) and go as stock as you can. Try it for a day or two and then go back to custom.
You wanna see if it keeps going off on its own, don't worry about performance just yet.
If it does it on all roms you've tried its obviously a hardware issue.
Try a different battery, if that doesnt help then send it for repair.
SGS2 power off issue
Hiya,
I have been running and updating Resurrection Remix and Siyah/Dorimanx kernels for awhile now and this worked fine up until last week. After an update to Dorimanx 7.50 my phone started dropping its network connectivity and powering off randomly, i then updated the Kernel to a new verison hoping the issue had been address (8.3 to be specific) after which my phone wouldnt even go through the boot sequence properly.
After a bit of fiddling i have managed to install an Official JB ROM, (details in the image attached) and network connectivity now seems to be ok, but the phone still powers off...ALOT. Anyone else experience similar issues and find a solution?
Note: I have ordered a new battery in case that is the issue as suggested above, but just checking incase theres something im missing while I wait. Also, the phone is about 16 months old.
Sv: [Q] SGS2 turns itself off
Check your fuel gauge chip. Reset it with siyah or dorimanx kernel.
Skickat från min GT-I9100 via Tapatalk 2
I *had* an un-rooted e970 with the standard 4.0.4 installed. I saw an update and updated to 4.1.2. I don't know if this is coincidence or if 4.1.2 just sucks with the Optimus G, but ever since I updated the phone:
(1) Data signal works half the time and decides randomly when it wants to work. (Toggling Airplane-mode and restarting does nothing). I've also factory reset this thing twice and it still has issues.
(2) Now the phone can't auto-rotate even though the option is clearly clicked to ON in the display settings.
Since then, I rooted my phone hoping something might trigger it, but no luck. Ultimately I want my issues fixed, but I think downgrading to 4.0.4 might fix the issues but I have no idea how to do that. Can anyone help?
Have you tried or considered flashing 4.1.2 stock meaning a complete flash of the latest available stock ROM using the LGNPST tool? I don't mean flashing 4.0.4 and then doing the OTA to 4.1.2, I mean completely flashing the LGE970AT-01-V20j-310-410-MAR-08-2013 build direct to the device in download mode using LGNPST... that might help alleviate some of the issues you noted, it might not, but it probably can't hurt to take that step. If it doesn't, you can then flash back to 4.0.4 which is out there as LGE970AT-00-V10o-ATT-US-SEP-29-2012-0. I think there's a V11c build as well posted someplace by SnowLeopardJB too.
As for the auto-rotate thing, I know one of the radios has been noted to have an effect on that, perhaps somehow that could be related. Flashing the stock 4.1.2 fully should help since it'll flash the stock JB AT&T radio, or at least it should, that might help with the auto-rotate too.
hi, my samsung galaxy s2 started making problems, if i reboot, most of the times I get a black screen which, curiosly, if I press the menu and back buttons, they light up! still, I have to reboot it several times (removing the battery does not help) untill i get a "successful" boot. I'm rooted and I am using omega v13 AOKP, based on JB 4.2.2 but this problem started some time ago, when i was using Omega v24 based on 4.1.2.
My phone is in warranty, but I woud like first to determin if it is a software or hardware thing, because if it is a hardware problem, I have to figure out a way or restoring to stock without leaving traces, so I can use it...
any ideas what the problem might be? the kernels on both versions I used were different, so it has to be something different...
thanks
Clean install of stock first. Test for a few days. Problems persist, then you send it in for warranty service. If the problems go away, then it's obviously something on the firmware you were using side. Try different custom roms/kernels in that case & see if you can reproduce the problem. If you can't reproduce it with other custom firmware, then it's an Omega problem - talk to the dev.
thanks
MistahBungle said:
Clean install of stock first. Test for a few days. Problems persist, then you send it in for warranty service. If the problems go away, then it's obviously something on the firmware you were using side. Try different custom roms/kernels in that case & see if you can reproduce the problem. If you can't reproduce it with other custom firmware, then it's an Omega problem - talk to the dev.
Click to expand...
Click to collapse
thanks, that is was i was thinking, although i hate to waste such an amount of time.. anyway, thanks for the advice, I'll guess I'll have to do it.
Hello Folks,
Forgive me if i have posted the thread in the wrong section or of any other reason. I am a new member.
I have an issue since i start installing custom ROMS. So, straight to the point.
What have I done so far?
is not my first time installing a ROM. I have installed stock ROM's in the past. However, not custom ones. I have rooted my device in the past and even now before installing a custom ROM. I have installed through TWRP recovery various custom ROMS such as Omega, AOSP, ARROW, WanamLite, Google Edition and CyanogenMod but none of them worked fine for me.
What Issues I experience?
In some ROMS I might not have reception (don't worry the IMEI is the same and backed up). However, in EVERY ROM my dialler crashes; for example, when im trying to make a call it freezes and the screen goes black without seeing anything. On the other hand, when I receive a call, screen takes ages to appear and show the caller or even accept the call. In addition, I have NO SOUND at all in every ROM as well.
What I think the problem is?
I believe that the kernel might be the problem. This is because when i am booting the phone I always see the following:
kernel is not seandroid enforcing
set warranty bit: kernel
I have tried clearing cache, dalvik, removing battery, installing stock ROMS etc.... and nothing changed!
I would much appreciate if you could help me with my problem as my phone is not usable at all like this.
Many thanks,
expl0r3r
expl0r3r said:
Hello Folks,
Forgive me if i have posted the thread in the wrong section or of any other reason. I am a new member.
I have an issue since i start installing custom ROMS. So, straight to the point.
What have I done so far?
is not my first time installing a ROM. I have installed stock ROM's in the past. However, not custom ones. I have rooted my device in the past and even now before installing a custom ROM. I have installed through TWRP recovery various custom ROMS such as Omega, AOSP, ARROW, WanamLite, Google Edition and CyanogenMod but none of them worked fine for me.
What Issues I experience?
In some ROMS I might not have reception (don't worry the IMEI is the same and backed up). However, in EVERY ROM my dialler crashes; for example, when im trying to make a call it freezes and the screen goes black without seeing anything. On the other hand, when I receive a call, screen takes ages to appear and show the caller or even accept the call. In addition, I have NO SOUND at all in every ROM as well.
What I think the problem is?
I believe that the kernel might be the problem. This is because when i am booting the phone I always see the following:
kernel is not seandroid enforcing
set warranty bit: kernel
I have tried clearing cache, dalvik, removing battery, installing stock ROMS etc.... and nothing changed!
I would much appreciate if you could help me with my problem as my phone is not usable at all like this.
Many thanks,
expl0r3r
Click to expand...
Click to collapse
having the same problem. Did you figure out?
expl0r3r said:
Hello Folks,
Forgive me if i have posted the thread in the wrong section or of any other reason. I am a new member.
I have an issue since i start installing custom ROMS. So, straight to the point.
What have I done so far?
is not my first time installing a ROM. I have installed stock ROM's in the past. However, not custom ones. I have rooted my device in the past and even now before installing a custom ROM. I have installed through TWRP recovery various custom ROMS such as Omega, AOSP, ARROW, WanamLite, Google Edition and CyanogenMod but none of them worked fine for me.
What Issues I experience?
In some ROMS I might not have reception (don't worry the IMEI is the same and backed up). However, in EVERY ROM my dialler crashes; for example, when im trying to make a call it freezes and the screen goes black without seeing anything. On the other hand, when I receive a call, screen takes ages to appear and show the caller or even accept the call. In addition, I have NO SOUND at all in every ROM as well.
What I think the problem is?
I believe that the kernel might be the problem. This is because when i am booting the phone I always see the following:
kernel is not seandroid enforcing
set warranty bit: kernel
I have tried clearing cache, dalvik, removing battery, installing stock ROMS etc.... and nothing changed!
I would much appreciate if you could help me with my problem as my phone is not usable at all like this.
Many thanks,
expl0r3r
Click to expand...
Click to collapse
You have the modem issue.. flash the proper modem and corresponding wifi fix from here http://forum.xda-developers.com/showthread.php?t=2192025
illikkalshahid said:
You have the modem issue.. flash the proper modem and corresponding wifi fix from here http://forum.xda-developers.com/showthread.php?t=2192025
Click to expand...
Click to collapse
Hi there,
I have exactly the same problem, have you fixed? How?
Thanks
Q] Galaxy S4 Custom ROM's Issues (no sound, black screen on call)
Omg I was getting to be a little nervous. Still gotta flash but fingers crossed. This is for an att galaxy s4