Database Develop

Freezing all the Time...

I've been using Incubus26Jc's Froyo v. 12 and My Vogue has been freezing over and over all the time. Seems not to be app specific, and seems to happen when its charging and when its on battery.
Any chance I've got a setting wrong? My guess is that my phone is dieing. Any advice?

I've had this problem on the earlier versions, but now on release 12, I have only had 2 freezes... Sometimes you just have to let the phone sit. I guess it kinda gets overwhelmed and needs a little rest :/

Is my situation the same? I'm running SagaROM Froyo Ultralite [v1.2.1, 7/28/10] and every time the screen goes to sleep and goes into lock mode, it reboots. What can I do to fix this? Please & thank you!

deltagamer said:
I've had this problem on the earlier versions, but now on release 12, I have only had 2 freezes... Sometimes you just have to let the phone sit. I guess it kinda gets overwhelmed and needs a little rest :/
Click to expand...
Click to collapse
i have to agree my phone was doing this all day today, after using gps and apps heavy
rebooted a few times and let it sit for a while working much better now

evilclosetmonkeynate said:
i have to agree my phone was doing this all day today, after using gps and apps heavy
rebooted a few times and let it sit for a while working much better now
Click to expand...
Click to collapse
Try going back to RLS10.5 with the 15-07-2010 version of Zimage. That eliminated the freezes for me. And it seems a lot faster.

evilclosetmonkeynate said:
i have to agree my phone was doing this all day today, after using gps and apps heavy
rebooted a few times and let it sit for a while working much better now
Click to expand...
Click to collapse
Try going back to RLS10.5 with the 15-07-2010 version of Zimage. That eliminated the freezes for me. And it seems a lot faster.

Thanks @richardk3 ... I have the NBH, but I didn't save the 10.5 install file. Anyone have a link?
Update: Searching the forum didn't find it but a Google Search did: http://www.mediafire.com/?ond2tmmzolggtmm

If you search the main Froyo thread, incubus put up a link to the archive of recent releases.
I went back to RLS10.5 and the 7/15 zImage per richardk3's suggestion. At first I did notice less freezing and overall better performance. But then I made a long call (over 5 min) with BT headset and the phone became unresponsive. BT and the call were still working fine, but the phone was unresponsive and had to be reset at the end of the call.
This is pretty consistent across all builds in Eclair and Froyo. I've reached the point where I basically accept that this is always going to happen and I'll need to reboot. It's worth the trade-off, though, since this build is so amazing and Android is so much better than WinMo.

Johndixon, if you're running from nbh then you may need to clear the dalvik cache from the boot screen menu. Worked for me when the freezes came fast and furious.

jstrom23 said:
I went back to RLS10.5 and the 7/15 zImage per richardk3's suggestion. At first I did notice less freezing and overall better performance. But then I made a long call (over 5 min) with BT headset and the phone became unresponsive. BT and the call were still working fine, but the phone was unresponsive and had to be reset at the end of the call.
QUOTE]
I'm having the exact same problem... always becomes unresponsive at the end of the call when using Bluetooth. I've tried combinations of RLS10.5 and RLS12, and a couple of zImages.
Other than this, it's super fast and stable... But it would be great to figure out what is causing the freezing.
Click to expand...
Click to collapse

eugene2007;7515857
I'm having the exact same problem... always becomes unresponsive at the end of the call when using Bluetooth. I've tried combinations of RLS10.5 and RLS12 said:
I'm having the same problem without using Bluetooth.
Can you gather the debugging info that DZO needs, as described here:
http://208.100.42.21/showthread.php?t=712310&page=180
Click to expand...
Click to collapse

Anyone else experiencing this on their screens?

Noticed a minor issue with my note running RR. My screen gets distorted (No image displayed, crazy moving vertical green lines on black background) when I power on the screen It happens only once in a while but just wanted to see if this was normal. The image moves but I can't do anything else with it, but after pressing the power button off and on again the whole problem is fixed! I've had my note for almost two months now and it has happened around 6x already. I've ran various versions of RR and they are all present, I cannot confirm if this is rom related because I've never really tried using other roms except for testing.
Can't make a screen shot because I can't seem to replicate the issue.

once a while it happens. you havnt mentioned on which rom n kernel you are. dont think a big issue.

Yeah it's a minor annoyance but doesn't affect the phone's usability. So this is perfectly normal?

happened to me a lot of times, i forgot app what caused this.

Pixel Salad. Usually cause by franco kernel.

If I'm imagining what you're describing correctly, this happens to my Note whenever I watch video of any kind. Even YouTube.

I had it too few times when i get sms
Sent from my GT-N7000 using xda premium

I´ve had it happen to me a few times also. I get worried every time it happens because I think my screen is packing up. I started to think that it was ROM related(Alliance_ICS_v1) but NOW from reading your posts I realize that it´s NOT rom OR kernel related(NoteCore kernel) because it´s happening to people with different ROM´s and different kernels.I suspect that it´s a app related issue and Andrew0811 reported that IT WAS an app that was causing it.I hope he can remember what app it was because it would certainly be of great help.Could it possibly have been a Live Wallpaper,Andrew0811?
---------- Post added at 08:19 AM ---------- Previous post was at 08:02 AM ----------
kingofthebraves said:
Yeah it's a minor annoyance but doesn't affect the phone's usability. So this is perfectly normal?
Click to expand...
Click to collapse
To me it´s a major annoyance and it most certainly is NOT normal.This should NOT be happening to a €700 phone and I for one believe that over time it will F-up your phone.Please guys,lets try to resolve this issue

jp.esteban said:
If I'm imagining what you're describing correctly, this happens to my Note whenever I watch video of any kind. Even YouTube.
Click to expand...
Click to collapse
If I remember correctly it happened once when I got an sms and once while I was playing music and powered on the screen. This rarely happens to me though so it's just a minor inconvenience for me. Don't know about you guys though. Right now I'm on RR7 with speedmod 3-6

Happened to me only once. Pressing the home button when screen was off.
Franco kernel indeed. Pixel salad is a nice description.

It did not came from my mind. That is the term they use if you read the threads in franco kernel and it happens to me also once when im on franco.

luckyluis said:
Could it possibly have been a Live Wallpaper,Andrew0811?
Click to expand...
Click to collapse
Nope, I don't like live wallpaper. not kernel either, because i only use cf, must be chainfire 3d or screen filter.
edit: well i tried franco kernel once, maybe it is franco's fault.

Zhoreb said:
Happened to me only once. Pressing the home button when screen was off.
Franco kernel indeed. Pixel salad is a nice description.
Click to expand...
Click to collapse
The few times that it happened to me was also pressing the Home button when the screen was off BUT I don´t use the Franco kernel(Ficeto´s NoteCore 0.6) so again I don´t think it´s Kernel related but rather a app that causes this. I stopped using a Live Wallpaper and haven´t had it since.I hope that was the cause and it won´t happen again.I´ll keep you posted.I´m determined to find the culprit that causes this.:fingers-crossed:

SGS Running CM10 Turns off automatically

Hey I hope one of you guys can help me.
I have a galaxy s running cm10 and I have had this persistent problem with my phone turning off automatically.
When I use it, I press the side button to turn off the screen and it is fine for a minute or so, but if I leave it any longer than that it turns off.
I have heard of something called Deep Sleep, is this the problem?
Is there a way to change how long it has to be locked to go into deep sleep?
Please help
I am losing hope
Cheers

HazzaGalaxy said:
Hey I hope one of you guys can help me.
I have a galaxy s running cm10 and I have had this persistent problem with my phone turning off automatically.
When I use it, I press the side button to turn off the screen and it is fine for a minute or so, but if I leave it any longer than that it turns off.
I have heard of something called Deep Sleep, is this the problem?
Is there a way to change how long it has to be locked to go into deep sleep?
Please help
I am losing hope
Cheers
Click to expand...
Click to collapse
Sounds interesting i know this from the first custom roms i tried a year ago!
Which build of cm10 are you using? Any "faulty" app installed? for me dropbox made cm10 instable and laggy, so i stopped using it.
Have you checked the md5-sum of the .zip file of your downloaded rom? Maybe the download was faulty... Happened to me twice on cm-nightlies.
Cheers
EDIT: Which kernel are you using? For me Stock-Kernel ist aboslutely rocksolid! My phone had 140 hours ontime this morning, before i flashed the newest build.

Hi,
Is you IMEI ok ? I had this problem with CM10 too but now my IMEI is ok I have no pb at all

have you overclocked your phone? i had the same thing happening with other roms...as soon as i had overclocked and turned the screen off, my phone got stuck after a while. try cleaning nstools settings. if that doesn't work, you might try turning off deep idle if it's active, could also be the reason

SKArabaeus said:
have you overclocked your phone? i had the same thing happening with other roms...as soon as i had overclocked and turned the screen off, my phone got stuck after a while. try cleaning nstools settings. if that doesn't work, you might try turning off deep idle if it's active, could also be the reason
Click to expand...
Click to collapse
Hey
Where is deep idle?
I have no idea where it is and ive looked everywhere in settings.
Do you have photos?
That would help.
Cheers

ThrashJan said:
Sounds interesting i know this from the first custom roms i tried a year ago!
Which build of cm10 are you using? Any "faulty" app installed? for me dropbox made cm10 instable and laggy, so i stopped using it.
Have you checked the md5-sum of the .zip file of your downloaded rom? Maybe the download was faulty... Happened to me twice on cm-nightlies.
Cheers
EDIT: Which kernel are you using? For me Stock-Kernel ist aboslutely rocksolid! My phone had 140 hours ontime this morning, before i flashed the newest build.
Click to expand...
Click to collapse
Hey
I would not know the first thing about what to look for?
How do i know its faulty?
Cheers

HazzaGalaxy said:
Hey
I would not know the first thing about what to look for?
How do i know its faulty?
Click to expand...
Click to collapse
Okay, let's start from the beginning :silly:
Whats the exact name of the rom you flashed?
How do you flashed it? (Wipe, etc.)
Have you flashed any other stuff? (Inverted Gapps, Battery mod, Kernel, etc.)
Have you many apps installed?
If i where you, i would flash the newest build with a full wipe, so you got a new, bugfree and stable system

same issue
I have been having the same issue ever since switching to CM10, I have been installing nightlies hoping it will end, but appears to be isolated. Would it help to manually flash boot for each ROM? It cuts off randomly and won't turn on unless charged by a wall charger, or other high-power input (doesn't turn on or charge from car outlet). It doesn't appear to be caused by an app.

Did you wipe when installing nightlies?
If you try to go stock with Odin, and the issue is exactly the same, I think you should consider it could be battery malfunction.
Sent from horseback.

[Q] I need help establishing a wakelock please?

Hello all. I am writing about my wife's Note1 (N7000, 16Gb).
The phone functions just fine except for one thing. At about 50% battery, it will just go to deep sleep and will require a long press power to wake up. Happens with any battery and have tried a few different ROMs (custom and stock). A SECOND Note we have (my sister's; I have a Note2) doesnt do any of this with same batteries and same ROMs, so does seem to be weirdness with this one.
I DO have a solution which has been proven to work with a scientific cause/effect relationship:
I installed THIS app from the PlayStore:
https://play.google.com/store/apps/details?id=eu.thedarken.wl
Now I dont fully understand wakelocks, but I reckoned the CPU was going into deep sleep so I set the wakelock to be FULL (see screenshot 1). This 100% solves the problem and the phone is fully normal now, and my wife says she cant tell any loss of battery life.
SO....
Looking to do one of two things:
1. is there a way we can have this app AUTORUN on boot cos she keeps forgetting to run it when she swaps battery (which is once a day cos she is heavy outside house user) and then wakelock not running then phone sleeps! DOH! If autoruns, then she can at least SEE the wakelock screen and press the lock to be active (we are still testing how LOW a wakelock can we get away with but for now using 7)
2. even better, is there a KERNEL I can flash her to that will give me same functionality so she never even needs the app? Something where I can set a minimum CPU level in a similar fashion and it is now a set-it-and-forget-it even surviving a reboot?
See pic2 for the stock ROM she is on now and is great. Given that phone is otherwise fabulous and all else is stable and functional, I would like to keep to this ROM if at all possible so as not to introduce new weirdness. Also, given that this is such an easy software fix, I am not looking to hardware repair the phone as just want to fix this and get on with life.
Hope this is enough info for an informative and educational discussion and looking forward to some good advice.
Thanks to all, and kind regards,
Asif

So are you wanting to prevent the phone from going into deep sleep?

maskerwsk said:
So are you wanting to prevent the phone from going into deep sleep?
Click to expand...
Click to collapse
Correct, yes. Need to stop the phone from sleeping so deeply that it is effecttively off now as wife misses critical reminder alarms, as well as phone calls etc. As it is (without the wakelock) the phone is pretty useless. WAS actually my sister's but had to swap and now SHE has the wife's old one. Sister is a surgeon and when phone was deeply asleep, hospital could never contact her so not good. So swapped and sister has wife's good one so that is off my back. Wife's (sister's old one) is here and easier to test out as sister lives in England and I am in Glasgow. Easier to take dodgy one and work on it here.
So need phone to remain functional until such time as battery is dead, like you would expect any normal phone to do.
So need wakelock to remain in force as described above, as WITH the wakelock active, the phone is perfect.
Thanks.

Is the phone rooted?
If so you could flash this mod i made. It prevents deepsleep.
http://forum.xda-developers.com/showthread.php?p=39915561
Only works on xxlsz though

maskerwsk said:
Is the phone rooted?
Click to expand...
Click to collapse
Yes it is. Sorry forgot to mention.

See edited post above

maskerwsk said:
See edited post above
Click to expand...
Click to collapse
Looks like the kind of thing I need, thanks.
Was very much not keen on switching ROMs tho as this one just working perfectly, and we all know that every ROM has it's quirks. Didnt want more headaches with the wife giving me daily anecdotes of weirdness!
What do you reckon would happen if I were to try flashing this on LSO ROM? I suppose the worst thing is a bork and then I just wipe and reflash LSO fresh? Is this just a typical CWM zip?
Or is there anything just like this (kernel or mod) that could be flashed on LSO?
Appreciate your time and help so far.

The mod is in the androidpolicy.jar so i doubr it will work. Worth a try as long as you backup first

maskerwsk said:
The mod is in the androidpolicy.jar so i doubr it will work. Worth a try as long as you backup first
Click to expand...
Click to collapse
OK, thanks.
Before I do, will wait to let the thread cook a wee bit and see if any other alternatives emerge.
Cheers.

asifanwaruk said:
OK, thanks.
Before I do, will wait to let the thread cook a wee bit and see if any other alternatives emerge.
Cheers.
Click to expand...
Click to collapse
Bump.
Any other ideas before I try the above?
Thanks.

Just a follow up if anyone is following this.
I DID flash the LSZ ROM and the zip patch and phone still died that night and failed to ring the morning's wake up alarm. To be honest, I am not sure what is going on with it. I have done a 'deep clean' (actually too much and I bricked it and then recovered it! Code Brown!!) and now flashed Slim Bean 4.2.2 to try something totally different and get away from a Sammy based ROM.
We shall see by tomorrow if phone can sleep at night without going into a coma, and then wife's wake up alarm can still ring.
If not then I think it is time for a service.
But wanted to come back on here and thank you for your time and efforts anway.
Kind regards.

[Q] Need to wait a while for the screen to turn on

Hey,
So my dad isnt exactly satisfied with the custom ROM I flashed on his device, he needs to wait about 4 - 5 seconds (!) when theres an incoming call for the screen to turn on. The ringtone will keep on going off during that few seconds, but the screen will be black.
So I tested it on my Nexus 4, and no such issue has been spotted by me. Although, on his device, no matter how many times I tried, the issue was never gone and I had to wait a couple of seconds for the screen to turn on so I could see who's calling.
I'm not sure whether it is a kitkat issue or not, I tried 2 different roms, first BeanStalk, and now CyanFox, both had the same issue.
I also tried to flash CM10.1, but the keyboard kept on crashing after a fresh flash, wipes didnt help (maybe someone could give me a hand here?).
Another question is, where can I find some good call recording app? the ones from the play store aren't good, they only record one side of the call, never both
tl;dr:
is there some setting that I should change for the screen to turn on quicker when theres an incoming call on kitkat?
what to do if I want to downgrade from kitkat to jellybean?
is there some GOOD call recorder app around?
thank you

Pawelss said:
Hey,
So my dad isnt exactly satisfied with the custom ROM I flashed on his device, he needs to wait about 4 - 5 seconds (!) when theres an incoming call for the screen to turn on. The ringtone will keep on going off during that few seconds, but the screen will be black.
So I tested it on my Nexus 4, and no such issue has been spotted by me. Although, on his device, no matter how many times I tried, the issue was never gone and I had to wait a couple of seconds for the screen to turn on so I could see who's calling.
I'm not sure whether it is a kitkat issue or not, I tried 2 different roms, first BeanStalk, and now CyanFox, both had the same issue.
I also tried to flash CM10.1, but the keyboard kept on crashing after a fresh flash, wipes didnt help (maybe someone could give me a hand here?).
Another question is, where can I find some good call recording app? the ones from the play store aren't good, they only record one side of the call, never both
tl;dr:
is there some setting that I should change for the screen to turn on quicker when theres an incoming call on kitkat?
what to do if I want to downgrade from kitkat to jellybean?
is there some GOOD call recorder app around?
thank you
Click to expand...
Click to collapse
If you still on cm10.1 then download keyboard from market and you are good to go Also stock 4.1.2 has this lag issue when incoming call its pretty annoying really

tuncay_93 said:
If you still on cm10.1 then download keyboard from market and you are good to go Also stock 4.1.2 has this lag issue when incoming call its pretty annoying really
Click to expand...
Click to collapse
hey, thanks for your reply
actually no, STOCK 4.1.2 didnt have this issue, it started to show when I flashed 4.4.2 on it, is there some sort of fix for this or do I have to downgrade to JB? I'd rather stick to KK as I prefer it more.
on the other hand my dad hated google hangouts and he wants the stock messaging app back, I guess I can only go with CM
also I cant install a keyboard from the market, because I cant even log in to my google account, I cant get through the setup without a few things crashing over and over again, every second or so. the keyboard doesnt even show up

delete the latinIme.apk from the zip file you are trying to flash and substitute it with one from the other roms you tried flashing.
I know how to control the delay with which the ringer starts but not screen :s
These commands I think only help when call ends but it doesn't hurt to try, add them (or check the values if already present)
to build.prop in zipfile before you flash it
Code:
ro.lge.proximity.delay=5
mot.proximity.delay=5
I am on kitkat right now and have no lag issue...have you tried changing kernel?

Rudjgaard said:
delete the latinIme.apk from the zip file you are trying to flash and substitute it with one from the other roms you tried flashing.
I know how to control the delay with which the ringer starts but not screen :s
These commands I think only help when call ends but it doesn't hurt to try, add them (or check the values if already present)
to build.prop in zipfile before you flash it
Code:
ro.lge.proximity.delay=5
mot.proximity.delay=5
I am on kitkat right now and have no lag issue...have you tried changing kernel?
Click to expand...
Click to collapse
hey, thanks for your reply
I flashed Nameless ROM and surprisingly the lag issue is gone, and due to stripped gapps I flashed, I got the old messaging app back, which is quite the perfect combo, now the only thing I am missing is a good call recording app, is there a chance you can suggest one to me?
thanks again!

Pawelss said:
hey, thanks for your reply
I flashed Nameless ROM and surprisingly the lag issue is gone, and due to stripped gapps I flashed, I got the old messaging app back, which is quite the perfect combo, now the only thing I am missing is a good call recording app, is there a chance you can suggest one to me?
thanks again!
Click to expand...
Click to collapse
Still havent tried nameless but i did red the thread about it. Seems everyone likes it. It should be good

tuncay_93 said:
Still havent tried nameless but i did red the thread about it. Seems everyone likes it. It should be good
Click to expand...
Click to collapse
well I tried it out, the rom is nice and all, but my phone is extremely slow, the lag issue with phone calls is back, sometimes turning the screen off is impossible, or takes up to 2 minutes (!). turning it back on isnt much better either, I dont know what the problem is, the same thing happened on the BeanStalk ROM so I assume it isnt a software issue, but a hardware one, do you have any ideas what could be the problem and how can I solve it?

I want to tell you my experience about custom roms.
I don't know if you tried this combo: CM11 + kicos kernel (modified iodak's kernel) + minimal PA gapps
I works for me very well.

LGaljo said:
I want to tell you my experience about custom roms.
I don't know if you tried this combo: CM11 + kicos kernel (modified iodak's kernel) + minimal PA gapps
I works for me very well.
Click to expand...
Click to collapse
yeah, but shouldnt all the 4.4.2 ROMs be quite snappy? doesn't kitkat reduce the hardware requirements? why would JB work fine (or so I think, I'll go back to stock in a few mins and see) and KK be laggy as hell?
I've got a theory, I'm not a hardware guy and I dont know if I'm right or not, but:
could be that one of the cores is damaged and the system tries to switch some tasks to the damaged core (if android handles different cores the way I think) and that core doesnt really work the way it should, causing the entire system to work like a granny?

Pawelss said:
well I tried it out, the rom is nice and all, but my phone is extremely slow, the lag issue with phone calls is back, sometimes turning the screen off is impossible, or takes up to 2 minutes (!). turning it back on isnt much better either, I dont know what the problem is, the same thing happened on the BeanStalk ROM so I assume it isnt a software issue, but a hardware one, do you have any ideas what could be the problem and how can I solve it?
Click to expand...
Click to collapse
This is probably some wake/lock problem with software. Also on my o2x i've noticed strange lag when i press the power key it has lag until the screen comes on buttons below the screen light and after a couple of seconds the screen. It has 4.3 CM rom there if your father is using this phone i would suggest you some stock based rom with custom kernel. They should not have problems like these.

tuncay_93 said:
This is probably some wake/lock problem with software. Also on my o2x i've noticed strange lag when i press the power key it has lag until the screen comes on buttons below the screen light and after a couple of seconds the screen. It has 4.3 CM rom there if your father is using this phone i would suggest you some stock based rom with custom kernel. They should not have problems like these.
Click to expand...
Click to collapse
That still the best sollution for him - optimized kernel with stable ROM. He probably isn't techno freak?

tuncay_93 said:
This is probably some wake/lock problem with software. Also on my o2x i've noticed strange lag when i press the power key it has lag until the screen comes on buttons below the screen light and after a couple of seconds the screen. It has 4.3 CM rom there if your father is using this phone i would suggest you some stock based rom with custom kernel. They should not have problems like these.
Click to expand...
Click to collapse
could be, however, it isnt only for the power button, when the screen is off and a call is coming, it needs a few seconds for the screen to turn on, after the call is done, the system is all choppy and laggy. Turning the screen off after that is also nearly impossible, due to power button malfunction. I went back to stock for now and I'll see if the lag is gone, if it isnt, then its probably a hardware issue.
edit:
yeah, I'm on stock 4.1.2 and the issue isnt gone.
crap.

sounds like a problem in the timing the processor uses for scaling frequencies...
hav no idea what could be causing it unless you have some kernel tweak app and set wrong values

Have you tried clean flashing the Roms you installed? Have you Factory-Reset, Cleared cache, cleared Dalvik cache, and maybe did a system partition format before flashing?
Inviato dal mio GT-P3110 utilizzando Tapatalk