Weird "soft restart" / force close??? - Galaxy S I9000 Q&A, Help & Troubleshooting

I am using JVQ Sensation Rom with the JVQ semaphore kernel atm.
I sometimes get some weird "soft restart" / force closes.. no idea how to better name this issue.. let me describe:
The Phone screen turns black, phone vibrates one time shortly, then it comes back to life - media scanner is running, my connection bars show a "stop sign" like they do before or when you don't enter your pin at start.. but shortly afterwards the normal connection bars are shown and I do not have to enter my pin.
If I listen to MP3 or had some other app open at the time of these "soft reboots" they are no longer open and the mp3 playback stops when this reboot occurs.
---
Does anyone have a clue what this could be? I dumped logcat into a file and looked through it myself, but couldn't really find anything on my own.
I cannot really reproduce this error, but it usually happens when I do had a few apps running or had recently used the phone it seems.
I am thinking maybe it could be the garbage collector / memory free thingy that then kills the launcher or something - could that be it?
Or is this known problem or smth? I don't really know what to search for in the search function - I'm sure anyone had this before, but no idea how to find a thread about this error.

Bump this. I was on a vibrant rom (revolution) I have a captivate. I used darkcore kernel and jk4 modem. Worked fine for a while...but did that a couple times a day while I was listening to Pandora on my bt headset.
Sent from my SGH-I897 using XDA Premium App

It's a problem, started from 2.3.3
This problem,affecting all 2.3.3 releases!!
There is also a thread in Q & A section but not many people paid attention to it.
Every 'now and then' phone slows down for moments, till the point that, it reboots itself or give force close or freezes so you have to turn it off.After reboot, it good to go again for ~3-4 days and then again same thing happens.
I read in some threads that darky rom also has this problem but I don't think its darky rom problem but stock Gingerbread itself has something wrong.
If it does not reboot and you don't power it off then you have to wait ~1-2 minutes before its comes back respond.
1. SD card formatting, already ruled out in thread in Q & A. I formatted the card but it simply happens again.
2. Less RAM can also be ruled out as I tried to open as many apps possible without closing them but Gingerbread was doing memory management very well and no freezes.
Expert please give your opinion, how can we get it fixed.

Related

The Boot Loop of Death (BLOD)

Hey Guys,
Ever since I first experienced this bug, it seems more and more people are coming forward explaining the same symptoms.
Connection drops, OS becomes unresponsive, freezes, and then you are greeted by the 'X' animation. After the phone reboots, it freezes once again and returns you to the 'X' animation and the process repeats until you pull the battery.
There seems to be no direct trigger as it can occur when on a call, when browsing or even when the phone is idle.
I've read through various threads on different forums in an attempt to reveal some kind of pattern, yet reports are coming from users on different ROMs with different kernels and different apps. I've created this thread in the hope that if people contribute their experiences, we can draw some kind of reasoning behind the development of the bug and offer some hope for resolving the issue in then future.
So guys, what are your experiences of the BLOD? What ROM were you running? What kernel were you running? Do you overclock, underclock or remain at stock? Anything you think may contribute to this annoying bug.
Thanks in advance.....
Reserved for future use
My experience began after updating to Kang-o-Rama 0.6 final (CM 5.0.6) after using Kings Desire Port aswell as using Paul's Desire ROM and Cyanogenmod previously. Originally it happened to me in the gym. While listening to music I recieved an SMS and the phone suddenly crashed and went into the BLOD. I had to pull my battery for it to stop. Since that occasion, I began to suffer the BLOD 3-5 times a day, sometimes when on a call and other times when the phone was idle. I tried wiping and reinstalling countless times, flashed stock Cyanogen and the later versions of K-o-R which would give my phone a slight reprieve ,however eventually the BLOD would hunt me down and return.
Eventually I believed it was a Cyanogenmod specific bug, especially after reading this thread,
http://forum.cyanogenmod.com/index.php?/topic/43-odd-crash/
Since I thought it was CM specific I went away and flashed Enom's ROM which again gave me a reprieve but only until I charged the phone at night. I awoke in the early house to find my phone rebooting away as I slept. This pattern continued for 3 nights until last night which was my first BLOD free night.
Now i'm not 100% sure as to what cured my looping last night but I flashed a new kernel yesterday (IR .33.5) and also on the advice of this thread,
http://www.google.co.uk/support/forum/p/android/thread?tid=2711ea74ef3d9aee&hl=en
I wondered whether the fact that I'd started using the stock alarm clock app could have triggered this so called 'notification bug'. I returned to using Gentle Alarm from the market and cancelled my stock Androdid alarm.
Right now i'm waiting to see how long I go without a BLOD before investigating if it was specifically the new kernel or changing the alarm which got me through the night. Will report back if anything changes.
I'm pretty sure this is a form of a kernel panic. I know Cyanogen had made some type of tweet or post regarding this. I'll try to find it and edit this post when done
wesbalmer said:
I'm pretty sure this is a form of a kernel panic. I know Cyanogen had made some type of tweet or post regarding this. I'll try to find it and edit this post when done
Click to expand...
Click to collapse
Cyanogen posted something regarding it being a system_server crash in the CM thread and that we needed logs of the event occuring before he could draw any conclusions. I managed to dump and adb logcat of the event while it was happening, although it was just a panic loop of which a segment was posted on the Cyanogenmod forum I posted above. Has anyone managed to capture a log of the BLOD as it starts? That would be a great help.
I got my N1 about 4 weeks ago and it worked OK until I flashed the Froyo radio. from that point on I could not get any rom to run in a stable way - my reboots happened 3 - 4 times a day and got to the point where I would get stuck in the boot loop. Pulling the battery did not always solve the problem although I found that if I kept the battery out for several minutes my chances of getting the phone to boot into either the ROM or recovery would be better.
I noticed at the same time that once the boot loop started I could not get into recovery until my phone had at least booted into the ROM successfully once.
Flashing back to the 4.04 radio reduced the random reboots to about once a day - usually at night after I had just plugged my phone in to charge. I was using the stock alarm app as a bedside clock.
After many days of frustration and the help from several people here at XDA, I finally came to conclusion that the problem must be hardware related and am returning my current device to HTC and am getting a new one.
I don't have a boot loop but I definitely experience the initial stages of this problem on a stock (unrooted, locked) N1 (at&t).
50% of the time when the N1 loses the connection (e.g. due to going into a garage) it will not re-acquire the signal. Searching for networks will hang, putting the phone in flight mode and then disabling flight mode will still result in no signal.
The only way to get a cell signal back is rebooting the phone.
Usually, searching for a network and/or enabling and disabling flight mode will result in the phone turning black and then rebooting.
I have the problem, too.
Just a few notes:
didn't have it on stock rom and Cyanogen 5.0.6, nor an Enomther's 1.8.1, started with Enomther's 1.9.2
This is not really a reboot, because a real reboot always helps. Other than a reboot, it starts directly at the X animation, not with the unmoving X before.
Seems to be a kernel panic.
I currently suspect that the panic happens when the RAM is full, especially if there is one single process that uses up massive amounts of RAM (could be in the background, of course).
I yesterday found that Sytrant (periodically sets time using internet time server) has a memory leak, and on closer inspection today found that it queries an ad server every few seconds and thus switches from sleeping to running state every few seconds. Also, it spawns root processes when setting time, which might lead to the system not wanting to kill it.
So, here's my current suspection (I'm not at all sure if that's true!):
The reboot loop only happens when the system runs out of memory.
In this case, Android should normally kick out other programs: First apps that are not running anymore, but are still in memory, second background jobs, and third services.
I guess there's some error in the killing logic in newer Cyanogen kernels and others that use Cyanogen parts (or maybe even in the orginal code from Google).
This somehow leads to a state where the kernel has no memory left and can't kill a process, too. -> Kernel panic
Maybe this is more probable if there is one big memory hog the kernel doesn't want to kill (because it's a service, or maybe because it has children running as root).
So, everyone who has this problem, please get a process monitor or task manager where you can see how much memory an app uses. OSMonitor is a very good one, and it can also sort the processes by memory usage. Start it periodically to find out if a process is constantly growing.
If you found such a process: Is it one that requires root? Does it run as a service? (Unfortunately, OSMonitor can't tell you if a process runs as service, or at least I didn't find it if it can. ES Task Manager can show that information, though, for example.)
Personally, I threw Sytrant off my phone now and will watch if that helps. I had reboot loops every two or three days, so I can't tell yet if it really will make a difference. I really hope so …
Edit: Of course, this theory does not really explain why the network drops before the boot loop starts. It could be, though, that the kernel tries to kill just anything to gain meomry, which might also be a system process that it responsible for the network. As the networks always seems to drop before the loop starts, maybe killing that process is what leads to the panic in the end.
Maybe, could … well, yes, this is just a theory. But at least it sounds good, doesn't it? ;-)
The more I read about this problem here and in other threads, the more I am convinced that my problem is probably not hardware related. My replacement phone arrives today but now I am wondering if I should return my original or not. Argg!
Is there a way we can all band together to try and get to the bottom of this problem? I am more than willing to do whatever testing those that know what to look for tells me to do.
Would one of the Guru's here be willing to guide us through a coordinated troubleshooting excersize?
Maybe we can start by trying to find out what we all have in common?
I have an AT&T/Rogers version of the N1.
I typically have the Facebook, Calendar Widgets on home screen.
Power Widget on 2nd screen
Use gmail but via the standard email client, not the gmail client.
Use the native alarm clock app in the dock at night
16GB ADATA MicroSD card.
I also install:
- ChompSMS (with icon widget on home screen)
- NewsRob (with Widget on home screen)
Did not get the reboots initially running the stock rom but they started the moment I installed paul's version of Froyo. I tried several of the other roms and had the same instability and BLOD's until I reverted back to stock and things stabalized again although I was still getting random reboots once a day or so.
While a hardware issue (especially RAM failure) could cause this issue, I don't think that it is the cause in most of the cases here. The fact that some don't experience it anymore after trying one or another software-related measure makes a hardware failure highly improbable, at least in their cases.
I won't rule that out, but until I tried everything else I can't conclude it must be a hardware faliure.
Please get OSMonitor and watch your processes. If after some days you still can't find a process using more than, say, 65 M, and still get the issue, you can be pretty sure that a memory leak isn't the problem for you.
The memory leak + killing bug guess is a good one and is quite probable. So let's check that first.
I think my FroYo rom problems are the same problems you guys are having. I think it's something with an app or an element of the OS or something.
http://forum.xda-developers.com/showthread.php?t=703508
I get the exact same issue on a handful of roms. Everything starts to force close, then it goes into boot loop, but, as someone said, doesn't really fully reboot, it just starts at the boot screen.
I've also noticed when things get funky, plugging in the USB cable makes it immediately go into a boot loop.
I start having this problem after I install the Quadrant Standard program, I was using the Kang-o-rama - Froyo when this happened. But after going back to Paul's Froyo everything is working perfectly again.
cmarti said:
I start having this problem after I install the Quadrant Standard program, I was using the Kang-o-rama - Froyo when this happened. But after going back to Paul's Froyo everything is working perfectly again.
Click to expand...
Click to collapse
I deleted quadrant, signed into market and all so it knew i uninstalled it, flashed a baked modaco R17, and it still boot looped on first reboot.
I suspect it is related to the 4.06 radio. My first boot loop started just after I installed the radio and before I updated the ROM itself.
DvTonder said:
I suspect it is related to the 4.06 radio. My first boot loop started just after I installed the radio and before I updated the ROM itself.
Click to expand...
Click to collapse
That doesn't explain mine though. I get the boot loop on some roms but not others, with the same radio.
MSigler said:
That doesn't explain mine though. I get the boot loop on some roms but not others, with the same radio.
Click to expand...
Click to collapse
Which ROMS are safe for you - I will flash one of them tonight and see if it works on my device as well - maybe we can narrow it down to a specific ROM.
Would also appreciate a list of the apps you use - I am thinking we should set up our phones as close to identical as possible to begin with and then start adding things to see what causes it. Thoughts?
DvTonder said:
Which ROMS are safe for you - I will flash one of them tonight and see if it works on my device as well - maybe we can narrow it down to a specific ROM.
Would also appreciate a list of the apps you use - I am thinking we should set up our phones as close to identical as possible to begin with and then start adding things to see what causes it. Thoughts?
Click to expand...
Click to collapse
The only roms that screw up for me are modded froyo roms. LeoFroyo works fine for some reason, as does the stock FRF50. I'll screenshot my apps in a minute and post them.
I have this on stock 2.1u1 EPE54B
I was getting some pretty random boot loops when running CM 5.0.7.1 and 4.04 radio. Noticed two things could (almost) cause it every time:
1) Not so much a cause, but Google Listen was running almost every time I went into a BLoD.
2) Something that WAS causing it.. I keep my phone on airplane mode at work with WiFi on, since I don't get a reception in the building. Reboot + turn off airplane mode when the phone is to that point = BLoD.
I actually flashed Kang-o-Rama and the 4.06 radio earlier, no problems now.
tjsimmons said:
I actually flashed Kang-o-Rama and the 4.06 radio earlier, no problems now.
Click to expand...
Click to collapse
Did you flash the Froyo version with SP3?

[Q] eclair live wallpapers

Just got my Galaxy S up and running on AT&T. It's the unbranded phone - not a captivate.
What is the best stable rom right now? I read about the official version codes, but I'm confused as to JR, JP, JM, etc.
At this point I just want something that's fast and works, so probably something 2.1 based. Later when I have more time I'll play with Froyo.
[Q] SGS South American Version will come whit DIGITAL TV reception
Guys, d u think there is gonna be a way to do it whit software changing, like flashing the SA firmware, or the phone needs a hardware part to receive the T signal ?
[Q] Laggy pinch-to-zoom
Hi everybody!
When i use the pinch-to-zoom function in my browser (the default browser on SGS), it's very slow. It is very laggy and not fast at all. Is there a fix for this or have I missed something?
please help!
Think you've answered your own question there.
If you want it on 2.1 install launcherpro or something.
Sent from my GT-I9000 using XDA App
[Q] Battery Drain on Mimocan Lag Fix
Hello all
I have noticed that my battry drain very fast after I applyed the Mimocan lag fix with a Sandisk 16 gb card Class 2 (all thanks to Mimocan for this lag fix. Apps run much smoother).
The main problem is when the phone goes in to standby. Last night it drained 22% even with all sync action diabled and all apps killed. Before the lag fix I did only see a 2-4% drop in battery over night.
To compare it drained more then a 15 min call I made before I went to sleep (35% vs 25% of total battery used. I pulled it out of the charger 5 min. before the call, so the data should be correct)
When the phone is activated, it seem like the battery drain is about normal.
I wonder if all/most ppl have this problem or is it just me?
My guess is that the SD card is activated all the time to acces apps data, and thus drain the battery.
Im on the m2 software, but I dont know if its the software or just a common issue when doing this lagfix?
Give a comment, Thx.
[Q] What drivers are needed for Odin?
Like other people, I'm having extreme difficulty connecting my SGS to PC with USB. I have tried just about everything mentioned in the forums, including:
-USB drivers from Kies and other sources (like the ATT Captivate drivers). Usually the Kies downloaded package installs all, but it cannot find the samsung modem driver when I plug in the phone. The Captivate drivers could not find "USB gadget". I tried installing both.
-Reformatting SD card (actually allows me to connect to 91 Panda PC Helper in -debug mode... but that's it)
-Erasing all references to Nokia and Motorola using Regedit. However I did not erase references to Samnsung or Windows Mobile)
-Praying to the creator
-Sacrifice of chicken
-Starting phone while connected to USB
-turning off antivirus.
I tried flashing phone using odin, in download mode, but it seemed that odin could not see my phone. Nothing happened.
Anyone have other ideas?
[Q] Lagging in ALL KINDS of music player after flashing samset1.9
I dont know if it is just an issue only to me, but I am having lags in any music player i tried after flashing samset 1.9.Generally the device runs other apps really fast but the sound and music lags all the time except when I leave the device be to just playing the music. I am using ext4 for a2sd fix. Dont know anyone is having the same problem
[Q] open img files from ClockworkMod Recovery?
Does anyone know a way to open the backup img files created by ClockworkMod Recovery?
[Q] Is the latest fix completely safe for device longterm?
Some people are wary of the stress caused by the latest fix, I am very very new to smartphone's in general and wanted the honest opinions of those who truly know android/device hardware.
There is a lot of well intentioned misinformed posters in any forum. But these things are important to get correct, I would much rather wreck my external 32GB card than the actual phone internal memory.
[Q] Busybox not installing
Hey all,
I am having a problem with busybox. According to the 1.18 installer, I have 1.15.3 installed. But the installer won't let me upgrade because 'the nand is not unlocked'. When I try the older 1.17 version, I suddenly have no busybox installed and have the same message with the failed instalation. What can I do....
Running jm5 with samset 1.9 (ext 3/4 fix not applied).
Alvast bedankt.
[Q] Wake the phone using Menu, Home or Back button?
Like the title says. Does anyone know if there's a way to wake the phone up using the Menu, Home or Back button like they've been able to do with the Desire and Nexus One?
Reference:
http://forum.xda-developers.com/showthread.php?t=696907&goto=newpost
Samsung placed the power button at an awkward place. I assume it wouldn't be too hard to accomplish this. Probably using an app or coded into custom ROMs?
EDIT: Don't have the phone yet but so I assumed it couldn't do it like the Desire. it seems you can wake the phone with Home and Power. I think the thread above details how to enable/disable the other buttons in waking the phone as well. Looks like a simple editing of the keyboard layout and then pushing it back. Thanks.
[Q] Still lag in Contacts and Phone even with Quadrant score 2106
I am now having Quadrant score of 2106 after using RyanZAEXT2Lagfix Alpha1. It is a huge increase. However, i still notice the annoying lag in CLOSING of application such as CONTACTS and PHONE. Opening of these application is also not as seemless as in Desire HTC sense which I previously own.
Can anyone tell me how to fix this?
[Q] No missed calls, sms, emails showing on icons
Last rom to work was a froyo rom, now any rom i put on dose not show a numeric sign to how many sms, emails or missed calls have not been read, please dose anyone know why?
[Q] ODIN questions
Hi there,
Could anyone tell me what will happen if I did the following:
I checked around but I don't think these minor questions have been covered in the big FAQ
Is it necessary to apply repartitioning when updating to a new firmware?
Will you corrupt data if you upgrade just 'modem' or 'csc' on ODIN?
Will you retain all your data if you don't go for repartition when updating to new firmware?
I've successfully flashed 2 new firmwares. One of them was Russian (jm5) and I was told a bit after than I can just apply the jm1 csc. Anyway, I got over it and just reflashed back to JM2 as it was stable enough.
Thanks
[Q] Headphones and micro issue
Hi,
I am the happy owner of HiDefDrum (+micro) - by atomic floyd - headphones I bought originally for my iPhone. It worked great with the iPhone 3G 16Go (sound, microphone and button).
Now I bought a Samsung Galaxy S last week, and I have problems with my headphones.
If I plug the headphones completely, the sound is weird when I listen to music (as if I heard only an echo of the sound, I don't even hear the voice of the singer) unless... I press the headphones button ! Then the sound is normal.
I can listen to a normal sound when I do not plug the headphones completely (leaving the last part of the plug outside).
And in any case, the microphone does not work.
I thought it was a hardware problem, until I saw that we can access many configuration settings using the code *#*#197328640#*#*
I guess the problem can be solved by modifying some settings in this menu, but I have no idea which !
Can anyone help ?
[Q] Question before drastic measures :) experts please
Hi Guys
I have tried all sorts of lag fixes on this forum, but after installing a couple of apps (10 to 15 in my case). The telephone is sluggish and laggy.
Yesterday i got fed up oflag fixes and firmware flashing hoping that the next version will be the solution so i put it on one of the online selling websites
I really like the way the phone looks and its amazing hardware but i am really not sure whether to keep it or sell it
Everyone keeps saying that the froyo 2.2 update will solve all the problems, so would you guys recommend holding on to the phone till end of september till the froyo is released, or should i sell it now and minimize my losses and try some other mobile phone
Is it true that 2.2 is gonna do its magic regarding lag and the time it takes to load an app, or am I having high expectations
[Q] Couple of newbie questions :)
Greetings fellow Friends from Galaxy
I just moved myself from the HTC Magic section to this one.. It was quite a jump, the Galaxy S Camera and 4inch screen are AWESOME =)
I have a few noob questions that I don't want to spread through many posts, so i've chosen to get them all here, without polution this forum section. Also they might come in handy for future Galaxy S buyers!
My phone is: 2.1-update1 @ I9000XXJF5
Question #1
Well at first glance everyone's trying to fix the "LAG PROBLEM"... I haven't noticed any lag!! What are we talking about? If its a fix.. i want it too
Question #2
The phone came with Android 2.1, but at samsung-firmwares.com and at this dev section of the forum, i saw the JP3 Froyo release. How stable is this? Is it already a daily driver or a total beta? As an Android lover, i'd love to have the latest
Question #3
I've used the One Click rooting solution and then the ROM Manager Clockwork to boot into clockwork rom and make a full-system backup. In my HTC Magic i had the recovery ROM (Amon_RA) flashed into the internal phone memory, so even if i didn't have a ROM installed, i was ALWAYS able to boot into recovery. That was a safety plus. How can i flash the Clockwork Recovery directly to my phone, without the ROM Manager? I'd feel more secure if i could count on recovery even if, for example, i flashed a non-working system ROM.
Question #4
So what is YOUR favourite ROM? My stock has some unwanted apps, and even worse, it's Eclair. I'd like to switch soon, but i don't know these Galaxy S ROMs Tell me what's the best ROM for you!
Thanks guys, XDA is indeed the #1 place for mobile stuff
Cheers
Phk
[Q] Galaxy S stops syncing corporate calender after upgrading it to firmware JG4
Anyone else having issue with syncing stock calender with corporate calender on exchange 2007??
[Q] Restoring File to /system/lib Without Root
I accidentally broke my phone by accidentally removing libgps.so now it won't boot.
I can get into recovery mode and see the device under devices, but I am unable to obtain root:
$ su
su
link_image[1728]: 2453 could not load needed library 'libandroid_runtime.so' fo
r 'su' (link_image[1728]: 2453 could not load needed library 'libui.so' for 'li
bandroid_runtime.so' (link_image[1728]: 2453 could not load needed library 'lib
pixelflinger.so' for 'libui.so' (link_image[1728]: 2453 could not load needed l
ibrary 'libhardware_legacy.so' for 'libpixelflinger.so' (link_image[1728]: 2453
could not load needed library 'libgps.so' for 'libhardware_legacy.so' (load_lib
rary[1058]: Library 'libgps.so' not found)))))CANNOT LINK EXECUTABLE
I can't cat the file, mv the file, remount /system.
Any wild and wacky work arounds in an emergency like this?
[Q] May I have the latest 2.1's official camera.apk
May I have the latest 2.1's official camera.apk
Just missing this file due to some unexpected problem.....
Could anyone help me a bit

[Q] [q] need quick help jvq

okay so i have installed JVQ on my phone seemingly successfully except after about a day of having the ROM installed I have started getting issues such as force closes. I cannot remember what forcecloses off the top of my head but also problems with messaging, quite frequently i will open it up and it will just shutdown no forcle close nothing and i will have to keep clicking messaging and it will show me all my threads not load peoples names then close. same with my dialler i will open it, have enough time to type a few numbers then it will close, no force close notification though. Also randomly my phone will freeze and i will either have to take out the battery or wait till the screen timer runs out and it goes black then turn the screen on, which usually doesn't work. The browser also sometimes forcecloses. I had some troubles a while ago with partitions which i never resolved i don't think but when i installed this rom (i have re-installed a few times) i tick repartition and it repartitions it supposably. I JUST WANT A FLAWLESS ROM WHERE I CAN MESSAGE, DOWNLOAD APPS, HAVE GOOD BATTERY, NO MASSIVE OR FREQUENT LAG AND NOT HAVE INTERNET ISSUES, GOOD RECEPTION AND NO RANDOM INTERNET ISSUES SUCH AS DATA CONNECTION NOT WORKING FOR NO REASON. Sorry for the long post I just wanted to thoroughly give information first go as it's urgent, driving me mad! I haven't had an almost flawless ROM apart from the ROM the phone come with.. which is now goone and 2.1 doesn't work with all apps
Try any custom rom blockbuster or hybrid rom much stable then that
Sent from my GT-I9000 using XDA App
I've tried darkys I just wantthe most stableand best battery rom is that what you'd recommend? Also does my problem seem like its flashed wrong? Caused by root or partition problem?
Did u use a pit file when u ticked repartition?
As for a rom, blockbuster is good, but I would recommend milkyS - you can flask this rom with Odin, full flashing instructions included with download. Very fast, very stable.
Sent from my Galaxy S using XDA Premium App
yeah i did man could that be why??

[Q] Doc's Master ICS V5

I looked at the posts in the dev section to see if anyone else had this problem, also noticed there is no Q&A for this ROM otherwise I'd post it there, I'd also post this there but I have less than 10 posts ;(. But around 2 days ago I flashed this ROM and all of a sudden the screen itself started to glitch, like half of the screen would split and disappear completely for a few seconds then reappear, then it would do it again but to the other half of the screen. Also restarted my phone to see if this would continue but it got stuck in a boot loop so I just flashed another ROM on the phone and it's been working fine so far, any ideas on how this happened? Would be appreciated..
cOld1 said:
I looked at the posts in the dev section to see if anyone else had this problem, also noticed there is no Q&A for this ROM otherwise I'd post it there, I'd also post this there but I have less than 10 posts ;(. But around 2 days ago I flashed this ROM and all of a sudden the screen itself started to glitch, like half of the screen would split and disappear completely for a few seconds then reappear, then it would do it again but to the other half of the screen. Also restarted my phone to see if this would continue but it got stuck in a boot loop so I just flashed another ROM on the phone and it's been working fine so far, any ideas on how this happened? Would be appreciated..
Click to expand...
Click to collapse
It might have been a bad flash. Try redownloading the rom and flash again. Also, make sure that you do not have too many apps installed. How much free space do you have on system?
The only apps that I had were the ones that came with the ROM itself, didn't download anything before or after flashing it.
may i know does this rom support audience cancelling noise?
thx
I wanted to know which kernel is the best to flash with thi ROM other than glitch kernel that comes with the Rom.
The glitch kernel has a problem that you can't make a NANDROID backup with it. What other kernels does this ROM support can anybody post a link to one. I tried searching but couldn't find one
scrypt said:
I wanted to know which kernel is the best to flash with thi ROM other than glitch kernel that comes with the Rom.
The glitch kernel has a problem that you can't make a NANDROID backup with it. What other kernels does this ROM support can anybody post a link to one. I tried searching but couldn't find one
Click to expand...
Click to collapse
ICS ones, but the Dev thread tells that & more.
I don't miss Nandroid when I'm backing up with Super Manager, Super Backup for data, apks, call logs and SMS.
cOld1 said:
I looked at the posts in the dev section to see if anyone else had this problem, also noticed there is no Q&A for this ROM otherwise I'd post it there, I'd also post this there but I have less than 10 posts ;(. But around 2 days ago I flashed this ROM and all of a sudden the screen itself started to glitch, like half of the screen would split and disappear completely for a few seconds then reappear, then it would do it again but to the other half of the screen. Also restarted my phone to see if this would continue but it got stuck in a boot loop so I just flashed another ROM on the phone and it's been working fine so far, any ideas on how this happened? Would be appreciated..
Click to expand...
Click to collapse
When my screen first appears after a reboot it does that, too, shows half the screen, then the other half, but only for a couple of seconds, I figured it's because it's still reading media, loading widgets, screen, etc. Doesn't last more than 2 seconds, fortunately.
cOld1 said:
I looked at the posts in the dev section to see if anyone else had this problem, also noticed there is no Q&A for this ROM otherwise I'd post it there, I'd also post this there but I have less than 10 posts ;(. But around 2 days ago I flashed this ROM and all of a sudden the screen itself started to glitch, like half of the screen would split and disappear completely for a few seconds then reappear, then it would do it again but to the other half of the screen. Also restarted my phone to see if this would continue but it got stuck in a boot loop so I just flashed another ROM on the phone and it's been working fine so far, any ideas on how this happened? Would be appreciated..
Click to expand...
Click to collapse
Were you still running the Glitch kernel that installs with the ROM?
It's odd that it went from working to not working. It sounds like something changed something which caused a conflict or corruption... it wouldn't have boot looped otherwise.
If not had any issues like this...
It was a fresh install of the ROM itself, was running for ~ 5 minutes. I didn't install anything via the Market or anything like that....
Un-invert Calendar?
I like Doc's V5 ROM a lot. Best I've used so far. However, I don't care for the inverted apps and am using the "Revert Inverted Apps to Stock" tweak mentioned here. It works just as expected except for the Calendar app - it remains inverted.
Can anyone else confirm so I'll know it's not just me?
Does anyone have a solution?
Thanks!
Bob
Only quirk I had with V5 was Gmail force closed constantly, even though I never use it. It would just notify me repeatedly that Gmail, an app I never touched, was force closing. Wiped caches and fixed permissions. It's been money ever since. Could use stronger battery life, but hey. Beggars can't be choosers.
Sent from parts unknown.
Anyone have vibration issues when receiving texts?
battery life
Battery saving settings - LiveOC 126%, MaxCPU=800*1.26=1008MHz. Nexus KB3 Modem. No deep idle sleep, no screen state settings, no internal voltage settings, ARM voltages are OC/UV. Power saver in ROMSettings enabled.
Boraltis said:
Only quirk I had with V5 was Gmail force closed constantly, even though I never use it. It would just notify me repeatedly that Gmail, an app I never touched, was force closing. Wiped caches and fixed permissions. It's been money ever since. Could use stronger battery life, but hey. Beggars can't be choosers.
Sent from parts unknown.
Click to expand...
Click to collapse
has any one experienced having a feedback loop in either your end or their end when using either the speaker phone or a headset?
Sent from my SGH-I897 using XDA
I am having an issue with the system time. It won't update automatically. Just gets stuck at a particular instance like 3:45 and won't update until I manually change the clock from 24 hours to 12 or vice versa. The happens after long sleep periods like two hours. After this the problem is persistent until I flash a new kernel.
---------- Post added at 04:19 PM ---------- Previous post was at 04:17 PM ----------
xThe Enforcer said:
Anyone have vibration issues when receiving texts?
Click to expand...
Click to collapse
Yes I am having this same problem no vibration with texts
no vibration with texts
Yeah. Same here. No separate vibration for SMS. But if you turn "Vibration only" system wide - it works for SMS.
Awkward.
scrypt said:
Yes I am having this same problem no vibration with texts
Click to expand...
Click to collapse
For guys having SMS problems with vibration. Go to SMS app, press the menu soft key, then settings, and scroll all the way down and enable vibration
Well anybody having an issue with time???please read my previous post^^ and tell me if it's sounds familiar , thanks
It happens when you switch a kernel as well? Try switching ROMs and see if it does it then go back to this, I haven't used this ROM since this incident ( OP ), using DK3 atm =p
b-eock said:
For guys having SMS problems with vibration. Go to SMS app, press the menu soft key, then settings, and scroll all the way down and enable vibration
Click to expand...
Click to collapse
I love you.
Sent from my SGH-I897 using xda premium

Weird Problem

Obviously I have an N7000 and I am noticing a peculiar problem for the past 2 days.
When I use the Power / Home button to wake the phone up, it takes close to 10 seconds to wake up.
When the phone is sleeping and I receive a call, it takes 10 seconds to wake up again.
When the phone is awake and someone calls, and I slide to Answer, the slider gets stuck and the phone is answered after 10 seconds.
I tried various ROMs, did a factory reset as well.
Interesting bit - All these problems vanish when am charging the phone. These problems occur only when am on battery. Could this be a battery issue ? Will replacing the battery help ?
Thanks,
Amit
So have you tried different kernels? Imho, I would flash a rom that is stable. I assume you are 4.0.4. After you fully wipe and install the rom of choice, check if you still have the lag. There are so many reasons that could cause it. Cable you're using, kernel, rom, etc. Do you use setcpu? You can actually set it to change when and how the cpu acts while screen off, on etc etc. In the past if I had a lag like that it was a problem with thte rom itself or an app that was causing the lag. If you need more help just PM me. Please post your results here so we can all follow the symptoms until we find a cure.
Thanks DBY,
I tried AbyssNoteKernel 4.2 and CF-Root. Both are showing the same issues. I am going to try another battery today. If the problem persists, I will let you know.
Thanks,
Amit
Which various ROMs ?
Please post the ROM name,version and the kernel which you are using.
Check your power save settings.
Disable all power saving and see if this resolves your problem.
Sent from my GT-N7000 using xda premium

Categories

Resources