Database Develop

Weird Bugs

Ive installed the latest cyanogen mod rom and i have been using it for a while. There are a few bugs i have noticed through my use of the phone and they are kinda getting annoying.
First of all i have noticed randomly while i am listening to music the music app that came with cyanogen will freeze up and then it will start again but after it does that there is no sound. And when i force close the application, i use the controls on the side of the phone to change the volume and it will only change the media volume not the ringer volume. to fix this when it happens i have been having to restart the phone and go on from there.
Another bug i have been noticing is when i turn the phone to vibrate mode using the controls on the left of the phone when i recieve a text i do not get a notification. I would excpect that it would vibrate as well.
Another one is that when i am listening to music and i recieve a text it will turn off the sound similar to the first bug i talked about. It says it is still playing but there is no sound coming from it. To fix it i have been having to restart the phone.
To listen to my music with my earphones i have an adapter and some times when i am using that the phone will go into a reboot loop until i take out the adapter and then once the phone is back up plug the adapter back in.
These are all quite annoying and i would like to see if you guys have any input on the matter. Thank you

I don't think that any of these are platform bugs, but rather are cyanogen bugs. I suggest you post bug reports to cyanogen's bug tracker.

lbcoder said:
I don't think that any of these are platform bugs, but rather are cyanogen bugs. I suggest you post bug reports to cyanogen's bug tracker.
Click to expand...
Click to collapse
Well i thought about that as well but i looked at the rules for the bug tracker and i am currently in the process of making more accurate bug reports for the bug tracker. I came here to see if i could get any quick fixes or to ask if these are common things or i may just have to format my phone and reinstall cyanogen. So yeah i hope i can get some feedback from other users. I may just have to format as i said but i hope that there could be something else i could do. dont want to just go to all that trouble to not get it fixed.
edit: I looked further into the bug tracker for cyanogen and i dont have the required materials to make a report as i dont have a log of the issue. its just something that tends to happen.

Its happening alot today and well yeah its getting really bad, i dont think there is anything wrong with my phone. So i think i am just going to format and reinstall a new rom. idk if i will stay cyanogen or not. anyone have any recomendations for the rom i should install?

Super D is pretty awesome. It's an improvement on the Cyan roms. So you get Cyan plus some extras.

Could i get a link to the correct version i should use?

Yep here is the link for Super D

thank you installed it and i am no longer having any issues. Wonderful

Weird phone freeze behaviour and other abnormalities! Is this normal?

Hi guys,
I'm on 2.1 Stock ROM, no taskkillers etc.
My homescreen is completely frozen as I type now and I can't open the apps menu (the app drawer with 3D conveyor belt effects) or slide to any other homescreen whether i lock/unlock the screen as many times i want!
On touching any homescreen icon absolutely unrelated apps are launching, eg, on touching messaging icon the stock camera launches (whose icon is on a different homescreen!)...on touching market icon...color flashlight launches (icon not on any homescreen...straight in app menu/drawer) etc etc! So cant launch maps or anything. 8 icons on homescreen and remaining space is taken by weather widget donation HTC style clock.
Wait a min...a call just came through fine and I could answer it...after hanging up I could touch all home screen icons and they were working but then suddenly my entire home screen rotated and went to landscape mode! Like all home menu icons, weather clock etc are in landscape/vertical direction and not alined/fitted to the entire screen...as in the ends of icons are cut off as the whole page looks magnified cos its obv not intended to be like that. Landscape orientation is not supported or needed on homescreens/app menu etc on the N1. Why is this happening (never came across this orientation change issues in any forums inc. xda) , why the hang?! Weird things regarding touch sensitivity and screen behaviour etc keep happening from time to time but I know about all that screen, touch sensor make and quality issues etc etc.
Also, I've noticed that everytime after a restart my phone takes atleast 20 mins to half hour plus to get everything working snappily and respond at full speed, eg, till then homescreen transitions are not smooth, all gallery pics dont load up to show for a long while (16 gig class 2 sandisk card). Is this normal?
Sometimes after switching to 3G my 3G watchdog (mobile data transfer measurement app) doesn't auto launch (app issue maybe?) and sometimes no mater how many times I choose wifi ON, it doesn't turn on! Switching it off from power control widget (i.e., 3G on) and then on again doesn't turn on wifi either even when good signal on my laptop!
Earlier today my phone was lying on the desk and it auto-restarted god knows why! The phone freeze happened like 10-11 hours after the restart today afternoon so memory etc wasn't so full or too many apps launched. The home screen rotation orientation has changed before in the past too so not first time to be clear.
I have still more than 80 mb app memory free in internal memory and dont overload my phone with crappy apps etc etc.
Pls advice and discuss.

I know you're on a stock rom now, but have you previously unlocked the bootloader and flashed anything else like recoveries, roms, etc?
If you have and you just reverted back to a stock rom, you could've downloaded a bad rom.
Have you dropped your phone? banged it around a bit?

mrandroid said:
I know you're on a stock rom now, but have you previously unlocked the bootloader and flashed anything else like recoveries, roms, etc?
If you have and you just reverted back to a stock rom, you could've downloaded a bad rom.
Have you dropped your phone? banged it around a bit?
Click to expand...
Click to collapse
Nope...none of those...fresh as a daisy!

Ok, well 2 options...
Option #1 - Return your phone for a new one if it's under warranty.
Option #2 - Unlock the bootloader, upgrade your recovery, flash the new radio and upgrade to a new rom like cyanogenmod. Come to the Dark Side young skywalker.

mrandroid said:
Ok, well 2 options...
Option #1 - Return your phone for a new one if it's under warranty.
Option #2 - Unlock the bootloader, upgrade your recovery, flash the new radio and upgrade to a new rom like cyanogenmod. Come to the Dark Side young skywalker.
Click to expand...
Click to collapse
So returning or rooting are my only options??? Why does the screen rotate weirdly? Is there any explanation of what's gone wrong?!
See if its a hardware n I root then I'll cry later due to voided warranty n in UK we get a 2 year warranty.
As far as bumps or knocks are concerned...ofcourse the phone takes normal hits or once or twice falls from my laptop to my carpeted floor but that's all.
There has to be logic behind this!

strange sceen happenings...
I've had the same ghost in my machine. In addition, my nexus would lose communication with the network and the cool startup screen with the streaming x would show. I had to pull the battery to get things back to normal. Enom suggested to watch my apps, he thought maybe one had a memory leak.
I found that moving my apps to my sdcard made my phone shot my phone to the streaming x about twice a day. Since wiping and not doing this, I haven't had that problem. I also found that my fav craigslist app was causing my screen to go unresponsive. I think the craigslist app was checking it's update and monopolized the cpu. Since my wipe i havent' installed it and the phone is working better.
Last, I installed nextheme 1.8.1. It also seems to quell the errant screen happenings. The screen still has it's moments, but if i press the off button and turn the phone back on again, i have control back.
I still have problems, but i've gotten them managable. I don't think it's a hardware problem because my rom choise and app selection really affect it. If it were hardware, it would be more consisitant regardless.
Hope this helps...

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] About ready to flush my captivate.. can you help? LOL [Rantish i'm sorry =( ]

I got my captivate on launch day (well 2 days after due to shipping) I stayed with stock for awhile and just did the lag fix.. it was ok.. i think the first rom i did was cognition.. or perception one or the other then did the other after that.. ran those for a bit.. tried CM7 (i think that was in january?) then firefly then something else and then netflix hit.. and i went to Continuum (v5.4.1) and thats where i sit now.. and i'm about really to go back to a iphone (also i REALLY REALLY hate that idea.. i like the iphone it self but i cant stand apple)
heres my main issues. lockups and slow downs. my phone hasnt ever been prone to locking up. until about a month or so ago (a week or 2 after flashing continuum_) so i'm guessing its something i installed that continuum dosnt like or its continuum it self.. with way it looks like i'm probably gonna be flashing something else no idea what.. what ever it is i want to to support netflix (Suggestions?) as far as slow downs.. the away it sits now if i open up the browser and do a search then back out of that to my home screen it takes it a good 5-10 seconds to load the icons and widgets on my home screen.. very annoying might not seem like much very it dose get VERY old
i know most of that is due to the rom.. but that also brings up another concern i've having..
I like android.. i really do love the live wallpapers altho halk the time i dont have one selected due to it might be slowing down my phone (see above).. when updating apps on my phone (say having 2-3 apps to update and clicking the update all button) makes the phone SOOO laggy (had this on all roms i've used) that i cant even receive a phone call untill its done downloading and installing them all.. thats annoying but i can live with it.. another issue.. turning on wifi/bluetooth.. i turn off my wifi every day when i goto work np.. get off at 6am come home goto bed.. wake up and usually check my email ect.. and before that i turn on my wifi.. about 15% of the time it wont turn on.. it says error in the setting menu.. try a few times.. still error.. do i have to reboot the phone.. just to turn wifi on.. bluetooth does the same thing.. except alot less often (mainly because i only use bluetooth for my stereo headphone and thats maybe once a week)
now alot of that can probably be traced back to roms.. but.. if i want to keep using android am i going to have to constantly be changing roms to try and find whats the best? so far i'm flashing a new rom about every month (i know some of you do it every week)... and really i just want one thats gonna work.. all the time.. i know wheres gonna be bugs every now and then even teh jesus phone has them and has to be updated..but when it take my 15 seconds to unlock my phone because i just gotta text message and the screen fade out right as i pull it outta my pocket is getting old
now for hardware side LOL.. main issue.. the damn capacitive buttons i've made a post about this before.. and i know theres not much that can be done.. but MAN are they annoying.. 1/2 i have to repetatly hit the buttons just for them to see that i've hit them at all... some times its 10-20 times before i picks up that i hit the back button at all (i use back the most) The gps.. well at first (stock) was HORRIBLE 20 minutes to get a lock.. the last few roms i've used have worked better (usually gets a like in under 30 seconds but some times loses it.. for no real reason like i drive under a tree for 1 second.. but i RARELY use the gps.. last time i used it was months ago so not sure how i would work actually driving now.. usually use it for google maps and such
apps.. (here is the only point i'm gonna compare apple and android).. we all know apple has more apps blah blah blah.. BUT android isnt THAT far behind in number or apps.. my issue with them is 'polish' or quality of apps.. not sure if this is that iOS is easier to make thinks look 'good' or what but.. if you look at.. say HD wallpaper apps on android .. thes a ton of them and they all have a very.. plain GUI nothing special about them.. iOS seems to be better looking.. no necessarily better content but been GUI to the apps i do like the openness of the android market just about anything and everything is all in 1 market (altho i am liking amazons market free app a day) when as iOS you have the app store and cydia (and installious if you choose). your not gonna find any SNES emulators on the app store but you can find them on cydia where as on android they are all in the market (altho they did just purge them a bit ago but i'm starting to see them come back)
One thing i have noticed sence i got my andoid i play less games on it then i did my iphone
I know this has been kinda a rant and hopefully you can help me.. i do like my captivate.. but at the same time i am due for a upgrade anytime i want.. and i dont really see anything coming out on ATT that is really any better then my captivate (captivate runs everything i've tried just fine.. excpet needing certian roms for netflix and no hulu app support yet)
I guess i'm just looking for the fence see the greener grass.. logicly i know its no better... but the idea if just using it and not having alot of the issues i'm having now sounds VERY nice...

Sounds like you should wipe your system. I would recommend using Titanium Backup, especially the Pro version as it can automate the backup/restore process. Search around the forums and you can find how to go back to either stock 2.2 or 2.3. See if that makes a difference for ya.

I can understand your frustrations with the phone, especially in the lagginess area. Just out of curiousity, what launcher are you using? Sometimes that can have an effect on your overall perceived speed. Also, if you haven't already done this, go into display settings and change your screen timeout to something longer. That might stop that particular annoyance.
I don't know what widgets you're using, but in general, the more widgets you have going, the more sluggish your phone will be. You could also try switching background data off (or at least auto-syncing), as that can slow things down, too.
As far as stability goes, if you're in the Gingerbread world, right now, things aren't going to be ultra-stable. Development of roms overall right now is going well, but it's still in an earlier stage of development. If you need stability, it might be best to head to Froyo for a while, where there are a lot of good, solid roms that would probably suit your needs. (Can't comment on netflix, as I don't use that app.)
You may find that your capacitive buttons become more responsive as you remove other lag factors, but I can't guarantee that. It's a little bit of the nature of the beast.
The gaming area on Android isn't as developed as the iOS version, but there are still some good quality games out there. Give Dungeon Defenders a shot (if that's your sort of thing), or Backbreaker, or Robo Defense. All of these look pretty good and are a lot of fun.
Ultimately, just like the previous poster said, a system wipe and restart might do you some good. Just back up the things that are crucial, and see where a "format internal sd" gets you.

jmtheiss said:
I can understand your frustrations with the phone, especially in the lagginess area. Just out of curiousity, what launcher are you using? Used a few AWD launch, twiz, sony erricson, launcher pro Sometimes that can have an effect on your overall perceived speed. Also, if you haven't already done this, go into display settings and change your screen timeout to something longer. That might stop that particular annoyance. Current screen timeout is 1 minute.
I don't know what widgets you're using, but in general, the more widgets you have going, the more sluggish your phone will be. You could also try switching background data off (or at least auto-syncing), as that can slow things down, too. only using 2 Fancy widget for clock and weather and the power widget oh and a widget for screen filter set to 20%
As far as stability goes, if you're in the Gingerbread world, right now, things aren't going to be ultra-stable. Development of roms overall right now is going well, but it's still in an earlier stage of development. If you need stability, it might be best to head to Froyo for a while, where there are a lot of good, solid roms that would probably suit your needs. (Can't comment on netflix, as I don't use that app.)
You may find that your capacitive buttons become more responsive as you remove other lag factors, but I can't guarantee that. It's a little bit of the nature of the beast. i have been a issue really from the start..
The gaming area on Android isn't as developed as the iOS version, but there are still some good quality games out there. Give Dungeon Defenders a shot (if that's your sort of thing), or Backbreaker, or Robo Defense. All of these look pretty good and are a lot of fun.
Ultimately, just like the previous poster said, a system wipe and restart might do you some good. Just back up the things that are crucial, and see where a "format internal sd" gets you. Yeah.. i've done this.. many times.. thats one issue i have.. is this gonna be a never ending cycle?
Click to expand...
Click to collapse
10charters =P

Also remember that restoring data saved from a 2.2 based rom can cause issues if you are restoring to new GB based rom. If you want a rom that just works then u would say stay stock. As for your apps reloading I see this alot when people load way tooo many shortcuts on their homescreen. With the folder programs and app drawers there is no real reason for having more then say 5 or 6 shortcuts on a single page of the launcher.

zelendel said:
Also remember that restoring data saved from a 2.2 based rom can cause issues if you are restoring to new GB based rom. If you want a rom that just works then u would say stay stock. As for your apps reloading I see this alot when people load way tooo many shortcuts on their homescreen. With the folder programs and app drawers there is no real reason for having more then say 5 or 6 shortcuts on a single page of the launcher.
Click to expand...
Click to collapse
I have maybe 5-6 short cuts spread on 2-3 screens i keep everything other then handcent, mail, market, amazon market, gallery and camara in teh app tray

^ What zelendel said.
You could also try Zeam launcher. I've used that one in the past, and it's pretty snappy. Also, try turning the weather updates off on the fancy widget for a couple of days and see if that helps.
It doesn't have to be a never-ending cycle. In the same vein as what zelendel is suggesting, it might be worthwhile just to see how much you can simplify your interface and still live with how it works. I recently went from having 5 screens of shortcuts to 3, and I've noticed that the phone seems snappier overall.

Flash to stock KF1 Gingerbread and remove the bloatware. It runs Netflix great and I don't have many lag problems. If I do its when I'm trying to run music while browsing the internet while texting and having games open in the background. Other than that it really is a solid build since its straight from Samsung and isn't having to use a reoriented kernel. If that isn't what you like then try Serendipity 7, I tried GR-12 when Serendipity was in its early stages and it was nice, but I like the idea of having the *proper bootloaders (whether it really makes a difference, I don't know, but placebos are powerful).
sent from my KF1 Galaxy S Captivate

Trackball constantly flashing

Recently my trackball started flashing constantly. It started around the same time browser started crashing constantly on one of the newer CM7 nightlies. I tried a lot of the nightlies and it still happens so I went back to the RC1 which I knew didn't have this problem.
I have a feeling its not the rom because it happens even when I am installing a new rom. It flashes all different colors and almost seems like its monitoring CPU usage. Any ideas?

chrisoaf said:
Recently my trackball started flashing constantly. It started around the same time browser started crashing constantly on one of the newer CM7 nightlies. I tried a lot of the nightlies and it still happens so I went back to the RC1 which I knew didn't have this problem.
I have a feeling its not the rom because it happens even when I am installing a new rom. It flashes all different colors and almost seems like its monitoring CPU usage. Any ideas?
Click to expand...
Click to collapse
Do you have a LED app? I know this happened to me when I had an app (forgot the name of it) installed. I also use CM7.

I don't have an led app. I flashed a sense rom and it is still doing it. I downloaded a couple led apps and they weren't able to control it. It is just green now and is even on when the phone is off. Only removing the battery turns it off.

Seems like I have read about a green flashing trackball before. You might want to search on it... but I'm pretty sure it's a hardware problem. Ship her off to HTC for repair.

Thanks. That will be my last resort. I'm pretty sure it's not under warranty anymore. It's an annoyance but I don't want to pay to fix it. I wonder how much it would cost to get them to fix this problem and my purple led flash.