Database Users

Froyo (dk28) lockscreen weird reboot.

Ok after a couple of days with little to no problem I am having a weird problem that I just want to report. While locked my phone will do a weird reboot. No splash screen, no sound. The menu keys stay lit. When the screen comes back up everything is restarting and the phone is locked still.
Sent from my SPH-D700 using XDA App

Sounds like you are running Nebula ROM. Update it to 1.0.2
http://forum.xda-developers.com/showthread.php?t=863154

I am running stock update.zip, not even rooted.
Edit: I am going to be giving this ROM a try asap.. Looks like my type of ROM. None of that BS. Simple and professional.

Unbearable lag in Nero4.1 with voice calls?

Anyone else? Im not exactly sure if its Phone.apk, DialerTabeActivity.apk, or simply the act of voice calls that is causing it. But it seems as though whenever i make a call, or have an incoming call, my phone almost cant handle it. It lags out like crazy.
This morning, my phone started ringing. There was so much lag that i couldnt answer the phone in time. Also, when i go to hang up a voice call, it often takes the "end call" button almost 10seconds to respond. Lastly, just earlier, i ended a call with my buddy. It LITERALLY took 3 minutes between the time i ended that call, and started a new one. Thats how bad the lag was.
Anyone else experiencing this? Any ideas how to fix it? Maybe its the modem?
This lag is literally intolerable, and a major inconvenience to efficiency.
PS - No, im not running a lagfix. I experimented with and without, and i determined that overall my phone performs better without it.
PPS - This is not me being oCD about my phone or a ROM. Im not being that "never satisfied" guy. Everything else with the ROM is great, its just this one thing.
Im using Eugene's B_Stock_1120_100 kernel, found here: http://eb-productions.proboards.com/index.cgi?board=samsungsgs&action=display&thread=28

TopShelf10 said:
Anyone else? Im not exactly sure if its Phone.apk, DialerTabeActivity.apk, or simply the act of voice calls that is causing it. But it seems as though whenever i make a call, or have an incoming call, my phone almost cant handle it. It lags out like crazy.
This morning, my phone started ringing. There was so much lag that i couldnt answer the phone in time. Also, when i go to hang up a voice call, it often takes the "end call" button almost 10seconds to respond. Lastly, just earlier, i ended a call with my buddy. It LITERALLY took 3 minutes between the time i ended that call, and started a new one. Thats how bad the lag was.
Anyone else experiencing this? Any ideas how to fix it? Maybe its the modem?
This lag is literally intolerable, and a major inconvenience to efficiency.
PS - No, im not running a lagfix. I experimented with and without, and i determined that overall my phone performs better without it.
PPS - This is not me being oCD about my phone or a ROM. Im not being that "never satisfied" guy. Everything else with the ROM is great, its just this one thing.
Im using Eugene's B_Stock_1120_100 kernel, found here: http://eb-productions.proboards.com/index.cgi?board=samsungsgs&action=display&thread=28
Click to expand...
Click to collapse
I would try starting from stock and working back up to nero v4.1.
I appreciate eugenes work but thats where most of my problems come from. Using nero v3 and experimenting with eugenes kernals(I was bored) I had constant lag, random reboots, panic/safe mode, freezes, couldnt access external sd card etc... Try starting from stock. Are you using titanium backup with system info.

intruda119 said:
I would try starting from stock and working back up to nero v4.1.
I appreciate eugenes work but thats where most of my problems come from. Using nero v3 and experimenting with eugenes kernals(I was bored) I had constant lag, random reboots, panic/safe mode, freezes, couldnt access external sd card etc... Try starting from stock. Are you using titanium backup with system info.
Click to expand...
Click to collapse
It sucks because this particular kernel of his offers almost everything i want in a 2.2 kernel (BLN, bootup/shutdown animations, lagfixes, OC/UV, and i also love the recovery menu).....although, with this ROM at least, the only lagfix that works is Voodoo, and the OC is only clocked at 1120ghz.
I was wondering if maybe this was causing it. And im mildly depressed to learn that it very well may be. I like TW's kernels, but they just seem to be battery destroyers.
So are you saying not to use this Eugene kernel at all? Should I try a TW one instead? Sorry but stock kernels suck and i want to avoid them if possible.
PS - I dont know what youre asking in terms of TiBu

I just tried it while on Wi-Fi, call came in, no lag answering it, I browsed engadget website, and no out of ordinary lag.
Flash back to stock and go back to the ROM, see if it resolves the issue.
EDIT: I am using Voodoo though

had same problem and i had just come from a fresh odin to stock. couldn't take it and went back to axura latest rom. plus vringo and video tonez don't work with roms with voice start and shutdowns.

[Q] Phone Shuts Down Randomly

My phone will randomly shut down and will not power back on unless I pull the battery, I have 2 batteries and it happens with either one. It does not shut down while on charger/dock. I have wiped the phone multiple times with odin, I've used several different roms/kernals,same results every time. Just curious if anyone else has been experiencing this issue.

I've been experiencing this after I went to eb13 with the custom kernels that are out. But my.phone will either lockup and I have yo pull the battery or it will reboot itself. Never had what happens to u yet.
Sent From My Evo Killer!

This has been happening multiple times a day to me. Completely at random. its beginning to become unbearable. My phone will lock up like this about 8-20 times in a day. Someone save meee! hahaha

nalewis89 said:
This has been happening multiple times a day to me. Completely at random. its beginning to become unbearable. My phone will lock up like this about 8-20 times in a day. Someone save meee! hahaha
Click to expand...
Click to collapse
I'm averaging 10 times a day myself

Permanent sleep
I may have experienced a similar problem, running a DK28 based kernel with both Quantum 2.5 & 2.7 ROM's.
When the phone sleeps and you're not able to wake it, do the 4 buttons at the bottom of the screen still light up? If they do then I have had the same issue. I could only narrow it down to restoring apps+data or putting the phone in sleep while an app is running. Once it was the result of putting the phone in sleep after a FC.
I can only posit that it MAY be an ext4-only ROM related issue, considering I did not have the above situation occur with rfs ROM's or rfs/ext4 dual ROM's. In addition this was only limited to DK28 for me. I was off DI18 <16hrs after I bought the phone. The DK28 gps issue was a non-factor as well, occurred whether gps worked or not.

before updating to 2.2 - I did the DK28 and now the EB13 one - with 2.1 I would have my phone randomly reboot - I would be sitting there and here the music it makes when it starts up but I never turned it off?
other times it would just be turned off, but when I turn it back on the abttery is not low enough to cause it to turn off
all this went away with DK28 2.2 and hasnet happened since I installed EB13 2.2

This happeed to me the other morning. I wasn't able to boot until I reflashed the kernel. Twilight frozen btw.
Sent from my SPH-D700 using XDA Premium App

My first epic would randomly hard power off, even running stock ROMs. If you are running a stock ROM and seeing a hard power off at random, I suggest you go swap the phone. It's just broken.

Ive never had this problem and im on my first and only epic and ive had it since it came out,
Ive been very careful with my epic as it has been great to me, it hates me probaly tho for feeding it stuff while experimenting things that make it spit up FCS,
But my phone has been always working perfect, all the way back to d118.

CLazman said:
I may have experienced a similar problem, running a DK28 based kernel with both Quantum 2.5 & 2.7 ROM's.
When the phone sleeps and you're not able to wake it, do the 4 buttons at the bottom of the screen still light up? If they do then I have had the same issue. I could only narrow it down to restoring apps+data or putting the phone in sleep while an app is running. Once it was the result of putting the phone in sleep after a FC.
I can only posit that it MAY be an ext4-only ROM related issue, considering I did not have the above situation occur with rfs ROM's or rfs/ext4 dual ROM's. In addition this was only limited to DK28 for me. I was off DI18 <16hrs after I bought the phone. The DK28 gps issue was a non-factor as well, occurred whether gps worked or not.
Click to expand...
Click to collapse
the buttons don't stay lit, i'm using twilight kernal right now but was happening with genocide kernal too, going back to eclair just to eliminate 2.2, ext4, etc.. to see if it's a hardware issue

First try
dk18 update.zip flash
Restored apps and data with my backup pro root
Random reboots, FC
Second try
Odin to dk18
Wipe x3
Restored apps and data with mybackup pro root
FC, music player force closing (doubletwist, stock and musicmod, poweramp worked though?), fc when trying to change ringtone or notification.
Started reading about others with the same issues and thought data backups were a reoccuring theme. Did a third try tonight and so far so good. Music players working, no force closings, keyboards working correctly, gps lock indoors. Its still early, problems might still popup, thought id share...
Latest froyotempt
Fresh backup with mybackup pro root
Wipe x3
odin eb13 prerooted (ctsy xda forum) same file from attempt 2. Did this x3 as well, read it in a thread somewhere...
backup apps only with mybackup pro root
All attempts were with genocide kernal.
So far so good, none of the previous bugs are apparent, so far... Those of you that are on the fence regarding doing the same, so far its worth the time.
Sent from my SPH-D700 using XDA App

I was thinking back-ups were part of the problem also, so I used odin and started all over from dl18 without restoring any data, same problem still occured

Still messing with my phone, everything that was broken seems to be fixed. Hopefully it stays this way...
Sent from my SPH-D700 using XDA App

That used to happened to me on eclair when I set my setcpu profiles too low when screen off. You wouldn't happen to be using setcpu would you?

actually I am, I have my minimum down to 200 MHz, going to raise it and see if that helps
@400 MHz did it again, trying 800

I'll add to this thread. I seem to be having the same problem and I believe it started when I installed quantum rom... but I'm not sure. The symptoms i had were random reboots, where the screen would shut off and the 4 lights would stay on. Then I would have the sound of lost signal as if my phone rebooted and was starting over. Also, the most recent problem I get is my phone completely shuts off and I need to battery pull to get it to start up, and it loops on the splash screen of my rom. I have tried doing a complete odin wipe and not restoring anything and I believe it is still happening...

joedig52 said:
actually I am, I have my minimum down to 200 MHz, going to raise it and see if that helps
@400 MHz did it again, trying 800
Click to expand...
Click to collapse
Any update?
Also, make sure the governor isn't "powersave". If you have 100-400MHz powersave governor, it still ONLY runs at the lowest speed (100MHz), even if it's 100-400MHz.

Still happening, not on powersave, doesn't matter what settings I have in set cpu. Did a hard reset back to 2.1 and it still happens, bringing it in for repair.

Safe Mode

Is there any way at all to disable the Fascinate from ever loading into safe mode again? It's really annoying when it happens because I have to reset all my widgets.
I've flashed my phone several times and it happens with every rom that I've had on it so is it part of the baseband kernel?

Get rid of the conflict that puts you in safemode. Safemode has to be better than your phone bricking.

johnnyplaid said:
Get rid of the conflict that puts you in safemode. Safemode has to be better than your phone bricking.
Click to expand...
Click to collapse
X2
List off the steps you used when flashing these last few roms (and what rom specifically) that you say are making you boot into safe mode...I've only seen it once on my phone and 1 reboot fixed it and I never seen it again, but that was months ago and I just chalked it up to me missing a step?! I have flashed many roms since and never see safe mode again.
Sent from my SCH-I500 using XDA App

Im starting to think that it's more a problem with my Fascinate than anything else. It usually happens when I have to pull the battery due to it locking up. Sometimes pulling the battery out a second time still doesn't get me out of safe mode and I have to continuously do it until it does.
For the past few months I've been using CM7 and updating with nightlies. On Monday I updated to the stable GLITCH kernel and so far it seems to be running much better. It's always had a problem with randomly bringing up my keyboard and backing out of apps and I have not had that problem yet since putting the GLITCH kernel on it.
Figured I'd also note in here that the GLITCH kernel is not currently working with the newest Cyanogen nightlies. It bootloops and I found that out the hard way.
For now im running GLITCH v11.1ML and CM7 Nightly 35 and it's been great so far.

so glad I havent run into safe mode

Nexus 4 Lockscreen Lag

I've had this issue with lag on the Nexus 4 lockscreen for quite a while.
The problem is that occasionally when I go to the unlock the phone, I press the lock, but the lock will freeze. Sometimes I have to turn the screen off, and turn back on a couple of times before I can unlock the phone.
I've had this issue running CM10.1 and stock rooted android 4.2.2. I've tried doing a complete wipe and re-flashing everything.
Has anyone else had this issue? I've asked a couple of people I know who have Nexus 4's and none of them have had this problem.
Did I do something wrong, is this a common issue, or this an issue with my phone?

nmunro said:
I've had this issue with lag on the Nexus 4 lockscreen for quite a while.
The problem is that occasionally when I go to the unlock the phone, I press the lock, but the lock will freeze. Sometimes I have to turn the screen off, and turn back on a couple of times before I can unlock the phone.
I've had this issue running CM10.1 and stock rooted android 4.2.2. I've tried doing a complete wipe and re-flashing everything.
Has anyone else had this issue? I've asked a couple of people I know who have Nexus 4's and none of them have had this problem.
Did I do something wrong, is this a common issue, or this an issue with my phone?
Click to expand...
Click to collapse
I also get this occasionally from time to time. I honestly have no clue what it could be, since the screen is completely dry as are my fingers when it happens. Its a minor bug so it doesn't bother me that much

brandonc0526 said:
I also get this occasionally from time to time. I honestly have no clue what it could be, since the screen is completely dry as are my fingers when it happens. Its a minor bug so it doesn't bother me that much
Click to expand...
Click to collapse
I also sometimes get lag when I do manage to unlock, scrolling through my screens is very laggy for 5-10 seconds, then it is usually fine.
I have a problem with lockscreen lag on a phone with a quadcore CPU and 2 GB of RAM.

Flash a custom kernel. You'll be less likely to experience lag

Don't get any lockscreen lag on my stock Android.

sigma392 said:
Flash a custom kernel. You'll be less likely to experience lag
Click to expand...
Click to collapse
Have any recommendations?

nmunro said:
Have any recommendations?
Click to expand...
Click to collapse
The latest trinity kernel (125) has perfected the lockscreen lag, It definitely unlocks instantly for me.

username8611 said:
The latest trinity kernel (125) has perfected the lockscreen lag, It definitely unlocks instantly for me.
Click to expand...
Click to collapse
Trying this out now. I especially liked how it told me my system was corrupted once it finished flashing...
First thing I've noticed is that the colour is a lot different. Do I need to play with any settings, or do I only need to have the kernel installed?
Also how often do updates come out?

Messing with the settings is totally up to you. It works great "right out of the box." I don't like the stock color settings, I use trickster mod to change them to rgb 255, 255, 255 and everything else at 0 except saturation and blacks all the way up. This kernel is underclocked to 1026mhz by default, I set it to stock clock speeds. It's also undervolted by default so if you are having stability problems, try bumping up the voltage on all steps by 25mv. Updates come out pretty often, prolly a few times a month.

username8611 said:
Messing with the settings is totally up to you. It works great "right out of the box." I don't like the stock color settings, I use trickster mod to change them to rgb 255, 255, 255 and everything else at 0 except saturation and blacks all the way up. This kernel is underclocked to 1026mhz by default, I set it to stock clock speeds. It's also undervolted by default so if you are having stability problems, try bumping up the voltage on all steps by 25mv. Updates come out pretty often, prolly a few times a month.
Click to expand...
Click to collapse
The colours bothered me so I'm trying the latest franco nightly. It seems to be at the stock clock speed, no weird colours, and it makes the haptic feedback when unlocking feel more like the GNex.

I'm still having this issue with franco kernel. I've been looking around a bit and people seem to say this is related to auto brightness. I'm going to turn auto brightness off for a bit and see if it still happens.
Also, does anyone know if using a 3rd party app for auto brightness would make any difference?

Okay, turns out auto brightness wasn't the issue. Still getting lockscreen lag. Help please.
If I put 5 fingers on the screen (when the screen is off), then press the lock button, when the screen comes on it will be completely unresponsive, some of the time. I'm not always able to replicate this.

for me, some releases of Franco have lockscreen lag, some don`t, try flashing the M2 or other post r121 builds, they are all great performers and maybe you`ll get lucky with one.

if ur using paranoid android, then its a stability issue i guesa cause the same thing used to happen with me...... or else try franco kernel... or update franco kernel if ur using franco, cause an older version had the lockscreen bug, which is now fixed!!!

sigma392 said:
Flash a custom kernel. You'll be less likely to experience lag
Click to expand...
Click to collapse
Flash a stock kernel. You'll be less likely to experience lag

I'm running CM 10.1 and the latest version of franco's kernel.
I've tried using a rooted stock and I had the same issue with lag.
I'm going to try franco's milestone build, see if I still get issues.
Would increasing the minimum clock likely help at all?

I had this problem no matter what custom ROM or kernel I would use I would get this problem I got a replacement phone and don't have this issue anymore
Sent from my Nexus 4

Good Guy Mark said:
I had this problem no matter what custom ROM or kernel I would use I would get this problem I got a replacement phone and don't have this issue anymore
Sent from my Nexus 4
Click to expand...
Click to collapse
I'm thinking this may have been the issue.
How does the replacement process work?
If I save a nandroid backup of my phone, can I just unlock it and restore from there?

Flash the reset kernel from _motley 's kernel thread, it replaces a lot of files that might of got changed via various other kernel flashes with stock ones.
the one that causes a lot of lock screen lag is the /system/lib/hw/power.msm8960.so file
N4_422_stock_kernel_and_components.zip

meangreenie said:
Flash the reset kernel from _motley 's kernel thread, it replaces a lot of files that might of got changed via various other kernel flashes with stock ones.
the one that causes a lot of lock screen lag is the /system/lib/hw/power.msm8960.so file
N4_422_stock_kernel_and_components.zip
Click to expand...
Click to collapse
Can I just flash this with CWM? And then flash back to franco m2?
I actually just got an RMA for my phone, because of this issue and that the back glass panel is a little loose and makes creaking noises. When I send the phone back to google, if I follow all the steps here and lock the bootloader, it should be fine to send back to them?
Google's RMA process was amazing. Took me all of 10 minutes. They're shipping a new one in 3-5 days, and they pay for the return shipping of my old device. The replacement is brand-new, not a refurbished device. My dad's iPhone 4S had a bunch of issues and he would have to book an appointment at the Apple store, which happens to be an hour away, and they would only replace his device with a refurbished one.