yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] Gilliland12:
I've yet to notice any slow down while running 3.9.7. I'm not running compcache. I've got a rather basic setup of just 3.9.7 and swapper. Things are moving a quick as they can. The phone has been up for days on end with no restart and still no noticeable lag.
[G1 Android Development] Bavilo:
I'm also on 3.9.7, no compcache, no swapper, no nothing, no "memory leaks" or slow downs. Perhaps its the apps you guys are running that is slowing the phone down? Check logcat
[G1 Android Development] ttabbal:
I honestly think compcache and swap get a bad rap because of stuff like this. I run compcache with backing swap and it works great. I've been playing with settings, but haven't settled on the best ones for me yet. I've also used plain swap and it works fine as well.

Looking forward to the new rom Cyano! One of these days I'll get the dev environment set up and submit some patches. I just have too many other projects in the way right now. I'll have to beer you for now. :D
[G1 Android Development] 4treyu:
I don't think the problems are compcache or swapper-related (I don't even use them) and I'm sure most of the guys having the same issues would agree.
[G1 Android Development] pershoot:
a bug to report:

htc_ime causes a forceclose in gmail app during the bar that comes up with sugestons of works when the hardware keyboard is being used.

nice rom. i look forward to the next updates:)

thx cy.
[G1 Android Development] temporizer:
Lets get with the picture!

I am running 32mb swap with swappiness at 20. I am having no slow downs. this is just as fast as when it came out.

Think about this: Phones are meant and built to run 24/7. Computers are not. That being said, when the G1 was released, it was released as a phone; built to run like a phone with some capabilities of a computer. With the wonderful minds here at XDA (too many names to list, but thank you all!) our G1's turned into a computer with a phone application.

my purpose for bringing this up? Reboot your damn G1 every once in a while. When your computer at home or at work starts to lag, what do you do? you reboot it. now that you are dealing with a computer rather than a phone, you need to take these measures.

I know all of you want to be able to run the G1 into a wall without ever rebooting it but try it once in a while. whats it going to hurt to reboot your G1?

When I go to bed at night, I plug my G1 into a wall charger. In the morning, 6-8 hours later, before taking the G1 off the charger, I reboot it and I'm good for the day.

I know i've been pretty silent the last couple weeks, that's because i am having no problems on my end, because i treat my G1 as a computer rather than a phone. I've been reading all the unnecessary posts and shaking my head. this thread has filled up WAY too fast, it's ridiculous, and i see no point in responding to those posts.

I have also been quiet because i have been doing research. And to my findings, people are trying to do way to much with way to little. I mean, I've seen and helped people that are trying to do EVERYTHING they see and hear about in these forums.

People need to pick 1 thing, master it, then move on to the next. I'm tired of people saying: X didn't work because i did a,b,c,d,e,f,g,h...etc. you need to understand that Cyanogens roms are built with stability and speed in mind. his latest ones are experimental (which will turn into stable roms), meaning that he changes things around to see how they work and how it would benefit the G1.

Summary: reboot your handheld computer, stop trying to do everything at once, understand that this is an EXPERIMENTAL rom, and things are going to mess up. Cyanogen doesn't need 300 posts repeating what the previous 300 posts said.

And last but not least, people need to READ. i don't care if you don't want to read 300+ pages, at least read the last 20-25, most of your problems and answers are already repeated for you there (it would be nice if you read all 300+ pages, it would give you so much knowledge it's not even funny).

//VENT
[G1 Android Development] underamoon:
Things slowed down for me. I've rebooted several times. Rebooting didn't fix anything. I cleared some data, didn't help. I do not have swap. The phone became unusable. I eventualy re-installed 3.9.7. The re-install fixed the slowdown for now. 3.9.5 was running a lot better for me and didn't experience the drastic slowdown that I have in 3.9.7.
[G1 Android Development] devsk:
THIIISSSS ISSS LINUXXXXX! we don't reboot...:D:p;):D

PS: if you didn't figure the caps, I refer you to some spartan movie...:D
[G1 Android Development] nurre:
Windows isn't, computer are fine running 24/7. The thing breaking over time here is system_server, which is what deals with the cellphone backend stuff.

There's no reason this shouldn't run 24/7 with 0 issues, I've only run into this issue once, and when I do I'll hook it up to a debugger + ddms and see if I can figure out whats going on.
[G1 Android Development] temporizer:
you are correct, we are on linux, so we have to reboot way less often than Windblows, but still, the memory gets full, and until there is a foolproof way to have the memory purge itself periodically, say, when it gets 85-90% full, or people learn how to manage their applications a little better, there will still have to be reboots.

edit: i have some free time tonight, what would i have to do to help figure out whats going on?
[G1 Android Development] nurre:
Your not understanding how this works at all, purging memory isn't something you need to do here at all, it's not the problem.

Having more memory for io cache is great, but chances are from a clean boot your phone is gonna be preloaded with boot services and already have used 99% of your memory.
[G1 Android Development] temporizer:
You're right, i don't understand Linux, i'm a whiz at Windows, but not Linux, haven't had a chance to play with it a lot.

Nurre, can you pm me and help me understand what we're looking at? i'm always about learning something. maybe you can help teach me.
[G1 Android Development] Chahk:
1. This memory conversation is quickly heading in the off-topic direction.

2. I'm paraphrasing here, but someone a lot smarter than me said "Free memory is wasted memory." The idea is not to have as much memory free at any given time, but quite the opposite. The idea is to have the apps use as much memory as possible, but give it up when it's needed by other apps. It's all about memory management.
[G1 Android Development] temporizer:
1. You are right, it is getting off topic, hence the pm request.

2. I think cyanogen said that :)

3. Thank you all for your responses. Re-lurking. ;)
[G1 Android Development] jshickam:
Charging LED not going out

I haven't had any problems at all with slowing. Seems to be running fine. The only minor thing I have experienced is the charging LED does not turn off when I unplug it unless I unlock the phone.
[G1 Android Development] talltexan:
So those who remember i am having trouble with my SD card, it mounts whenever i take it out of my phone and plug it into a SD reader, my phone still charges, could it still be the SD card or is my port jacked up?
[G1 Android Development] miketaylor00:
Which SPL are you on? I don't know if this is the same issue, but some of the guys using the JACxROM could not get their phone to read their SD card until they updated to the 1.33.2005 SPL. xROM is based off of a Cyanogen build and it only started happening on the latest builds. I think the kernal was changed in those builds. So it might be worth a try.
[G1 Android Development] userfriendlyme:
I may suggest using another memory card to rule out what your issue is. If it does the same thing with another card then you no your phone is more then likely the issue.
[G1 Android Development] Blind Oracle:
Good point. I forgot to mention that too. I see the exact same behavior.
[G1 Android Development] talltexan:
Yes

Tried a spare 1gig micro SD same thing

Strange thing is that it was just like this this morning i had not installed or done anything diffrent. My stupid phone is not in warranty because i stopped working for Tmobile and they voided my warranty whenever i left and switched to a regular account.
[G1 Android Development] felixre7:
The phone seems to get slower and slower over the course of 3 days or so. As in every program is slower and the phone as a whole is responding much slower to inputs. then a reboot seems to clear up all the issues, restoring it to its original speed. Its not the end of the world, but could point towards some kind of issue some place?

not complaining or asking for a fix just letting you all know.

8gig class 6 memory card

3.9.7
[G1 Android Development] osho741:
Talltexan, were you using compcache with backing swap? I wonder if things like backing swap are not so much wearing out the sd cards as wearing out the sdcard hardware that is being used to read and write to the sd card?
[G1 Android Development] _nobody:
is anyone else still having wake issues? whenever the screen is sleeping, if i press End, the screen fades with different color bars and fades out. i have to keep pressing end or menu and with a little luck, the phone unlocks. did anyone pinpoint the cause of this, and what is the fix? i'm pretty sure im using the latest software for everything.
[G1 Android Development] TheGreenJester:
Eventual Slowdown

I too have experienced lag setting in after a few days.

Considering the frequency in which Cyanogen has been releasing the builds, most of us have not had phone uptime of more than a day or two in quite a while. It has been 6 days since 3.9.7 was released, before that the longest interval was 5 days between 3.9 and 3.9.1.

I downloaded and installed 3.9.7 shortly after it was posted on the 4th. After about 48-50 hours of moderate use, the system as a whole began to become sluggish and would take several seconds to return to the home screen (with an android.process.acore fc/wait dialogue waiting for me). It would also lag when rotating between horz/vert. Typing, clicking, dragging and scrolling all lagged behind input. Nothing was eating cpu or hogging memory, and a reboot fixed the problem.

Since then (~90 hours later) my system has been as speedy and stable as ever.

I am using a 16GB Class 6 card (A-Data) with no themes, no compcache, no swap. The last time I wiped was several stable builds ago.
[G1 Android Development] aceo07:
I've noticed a couple of issues on 3.9.5 and haven't seen it as fixed in the later versions or mentioned in other posts.

1. In the 'my downloads' in the market, it will time out and blank screen after the set idle time (1 minute). This is even if I move around that screen with touch or trackball to prevent idling. Very minor issue and I've rarely there but I was able to reproduce it.

2. My ringer volume seems to have decreased by 50% today. Even when I go to max, it sounds like it's at 50%. I usually lower it from 60% to vibrate while I'm at work and raise it again when I'm out. Today I noticed that the volume sounded a lot lower than usual and double checked to make sure. I rebooted and that seems to have solved that problem. I've only noticed this once.
[G1 Android Development] talltexan:
No Compacache havent quite gone down that path yet i still have swap on my sd card but its not being used. whenever i type free in terminal it comes up as 0
[G1 Android Development] epicphotoeye:
Can someone help me figure out how to tell the browser in this rom to put downloaded files in a specific folder? I've got another thread going about not being able to find files I downloaded from the internet (mp3's) and none of the suggestions are showing me anything.

They are not in:

/system/media (or subs)

/system/sd

/sdcard

/sdcard/media (or subs)

/sdcard/download

they did not show up using:

#find -name 'wakeup.mp3'

or several variations of that.

when mounted on the pc, no search finds these files.

Not using compcache or a userint.sh

They will not show up in the music app, but can be used as ringtones/notifications.

Sorry if this is off topic, but I've spent hours searching, gotten several suggestions, and can't find any answers...
[G1 Android Development] AGunz82:
Any chance this will come out without the advanced launcher? It is a lot slower than the regular launcher.
[G1 Android Development] lotherius:
Have been having some pretty bad audio issues myself. I lose audio at times while music is playing, and also anytime I connect my bluetooth headset the audio goes dead. Restart is required to restore audio.
[G1 Android Development] All~G1:
no compcache

no swap

wiped

brand new SD-card

NO LAG... maybe a little in the last couple hours after HEAVY usage

Overall phone is consistently running strong. Running for 48hrs+ with 1 reboot.
[G1 Android Development] lancealtar:
I'm experiencing this as well, on my secondary phone that upgraded from 3.6.8.1 to 3.9.7.
[G1 Android Development] dwang:
I would have to agree with the others here. Even without compcache or swap, the phone gets very sluggish after a couple of days of use without rebooting.

There must be a memory leak somewhere.
[G1 Android Development] itp:
It's almost certainly not a memory leak, since free continues to report no problems with available memory. The high CPU utilization that people are consistently seeing (and if you can check system_server via top next time your phone is sluggish to confirm, that'd help) makes it seem like some other resource is being leaked inside system_server, which is causing system_server to waste more and more cycles as the system stays awake.

I originally thought it'd be tied to GC activity, but I haven't been able to demonstrate that to my satisfaction. It might be related to the number of threads/processes spawned, etc. -- some sort of list that system_server is iterating over? Without knowing anything about the internals of that process, I'm just speculating, of course.

Regardless, I've found that restarting the system_server via ddms causes the Android runtime to restart without rebooting the phone, and results in a fast and responsive phone once again. So despite some speculation, it's not an OS level problem -- the problem isn't at kernel level, but user level.
[G1 Android Development] dwang:
It may very well be related to garbage collection.

I noticed that there was a recent commit to the master branch changing the strategy for freeing objects.

http://android.git.kernel.org/?p=pl...it;h=dde8ab037540aaec554a471d67613b959cc0e9f4

I think the other issue is that 3.9.7 uses up more RAM due to all the enhancements cyan added (vpn, power settings, modified launcher, dialer etc). That might be contributing to the sluggishness as well. I noticed that the settings.apk is always running in 3.9.7, which wasn't the case in the stable branch.
[G1 Android Development] borodin1:
Try re-flashing your radio, it may sort things out... It's been know to help in the past.

Good luck
[G1 Android Development] nurre:
this is the info I pulled when I saw elevated system_service cpu usage on my phone, I jumped the gun a bit and pulled data when it was around 5% constant cpu usage, I might have gotten more interesting results with 50% cpu usage.

threads:

android.server.ServerThread

java.lang.object

android.os.MessageQueue

android.os.Looper

com.android.server.ServerThread

SystemServer.java - Looper.java - MessageQueue.java

Allocation tracker shows a ton of android.os.SystemProperties allocated from native_get

Path:

SystemProperties.java

Settings.java

LocationManagerService.java - This is where I'm thinking the problem lies.

Can people try disabling google latitude and see if that improves things at all?
[G1 Android Development] Faud:
I am trying to figure out why I cannot flash this on my wifes phone. Everything worked perfectly on my phone. She currently has the basic JF1.51with no theme. I install this rom and it loads up and then I hit menu button and every apk force closes. Any ideas?
[G1 Android Development] kyleds:
dont forget to wipe when switching roms and do a fix_permissions also.
[G1 Android Development] christian246:
The last version work but anytime the "home" crash and If you don't close the application it's very slow
[G1 Android Development] cliffrowley:
I just thought I'd offer my experiences to add to the "memory leak" observations. Obviously I'm not speculating that it is a memory leak, my knowledge and experience doesn't qualify me to make that assumption.

However I just wanted to point out that it wasn't until I enabled the backing swap for compcache that I also found that after an indeterminate amount of time my phone became laggy, eventually to the point that everything started to crash (including Better Keyboard, which has never crashed for me before), and ultimately to the point that it stopped responding entirely and I had to pull out the battery to recover.

Edit: funnily enough, just after posting this I picked up my phone, and despite the battery being at ~50% last time I looked at it (less than an hour ago), it had run out of power and turned itself off. Something is definitely up.
[G1 Android Development] Faud:
Thanks, its driving me nuts, I think because it was so easy on my phone so

Root Phone - ok

Install JF1.5 CRB43 - ok

Install Cyrogen's Recovery 1.4 - ok

Nandroid backup - ok

Install Cyrogen 3.9.7 - loads up but everything force closes

Install JF1.5 ADP - it just loops on the boot screen and never loads.

Good God

My wife really loves this on my phone though so I keep trying...
[G1 Android Development] maxisma:
Did you wipe?
[G1 Android Development] pascanu:
You need to attach a log.
[G1 Android Development] itp:
I saw the same thing. I'm assuming this is related to being connected to the phone with debugging mode on, though?

Ooh, that's a good one. I saw the same thing as well, a staggering number of allocations from that thread, and when I fetched new data a few seconds later the number had increased dramatically.

I've disabled Latitude and killed off system_server to allow it to respawn, and I'll try to test it out over the next little while. Although, now that I think of it....

I used to have serious problems with phone slowdown while using the Locale app to turn my ringer on/off when in certain areas. That was also waking up every 10 minutes to check my location, which would have been using the same code in system_server, in the end. Removing Locale made the problem better, but not fixed. It makes perfect sense that Latitude would trigger the same problem.

Unfortunately, that makes it more likely that the problem is something upstream, in the AOSP code, that would need to be tracked down.

What would be ideal would be to get confirmation from other people with slowdown that they're using Latitude (or Locale, or something that's regularly finding location), and confirmation from those without slowdown that they're not.

Cyanogen, I know you're just back from your weekend away, but any chance you've been following this minithread?
[G1 Android Development] bhilgeman:
Regarding this "memory leak" or "performance lag" I found something interesting last night.

I have 3 partitions on my SD card

1. Fat32

2. Ext3

3. 32MB Linux-Swap

I have the new Compcache .6 with backing swap enabled.

I mounted my SD card in my card reader to Ubuntu and opened gParted

When I right clicked on the Linux-Swap partition there was an option to turn Swapping On, I thought what the hay and turned it on.

I was having lag before as you all have mentioned. I didn't have it in the previous builds, just 3.9.7.

I'm not saying this did anything more than create a placebo effect, but it really seems to be running alot faster than it was prior to making that change....

I'm no dev nor do I know much about Unix (I'm reading Unix for Dummies right now :)) so take this with a grain of salt...
[G1 Android Development] jackkerouac:
I am running a Rogers Dream (three partitions: FAT32, ext3 and linux-swap) with 3.9.7 and Swapper (128 MB) installed and running. The phone runs great, no real problems. Very peppy and it doesn't really slow down at all.

One, admittedly minor, concern. When listening to music, audiobooks, etc. and a call comes in, the music stops but the phone doesn't ring. Weird.
[G1 Android Development] senab:
What you did was let Ubuntu use the swap partition, not enable swap while using your phone.
[G1 Android Development] bhilgeman:
See I haven't got that far in my book yet haha. Thanks
[G1 Android Development] thfoster:
I can attest that re-flashing the radio will fix the audio crashing problems. I had the same thing going on.
[G1 Android Development] Fingerlickin:
I had the same problem on my phone going from stock to 3.8.6.1. Try Uninstalling all the programs, wipe using recovery, and reinstall them. That worked for me.
[G1 Android Development] fuchsmi:
Hi guys,

I really appreciate your work and your feedback and I love this ROM.

But is it possible to set up some project page? This is a slow forum and not a developer plattform, bug tracking system, mailing list, etc.

It would be really handy to have an overview on open issues, feature requests, releases (with a release date!) and some more verbose information on the change log lines "some bugs fixed".

Thanks,

Michael
[G1 Android Development] ajthornton52:
Just to add my 2 cents with playing around with 3.9.7 (no Theme). As a lot of other people, the phone lags after 4-5 hrs.

Also-I am getting a process error message when trying to dismiss Calendar tasks. Has this issue been reported yet or is this just me?
[G1 Android Development] Bavilo:
If you had taken the time to read the first page of this thread you would have seen that it specifically asked you to READ. I assume you didn't, therefor you don't know that cyanogen mentioned doing EXACTLY what you just asked for only a few pages back.
[G1 Android Development] Blind Oracle:
for those complaining about slow, chronic slow down, I found the following bug in the Android bug database. Turns out it might be a new Android feature. :rolleyes:

http://code.google.com/p/android/issues/detail?id=3453
[G1 Android Development] pinetreehater:
Yes, I too will be grateful for the switch to the google code page. I love XDA, but keeping abreast of this thread is very difficult unless you devote a lot of time.

Its not just reading...you can read all 2000 something posts and not comprehend. The nature of the bulletin board lends itself to answers being separated from questions. If only this board had the thread style...perhaps that would be better. I know for a fact that I have read, but there have been times when my questions got lost in the background chatter.

And have you ever really tried to search for an answer on XDA, its really anything but simple...to get a single answer you first have search forum-wide, subforum-wide, and then thread-wide (really, I guess you could just start at subforum wide). And that's assuming you entered the correct booleans and terms to get you close to your answer.

@blindoracle....that is interesting, but no one has picked up on it yet...does it have status as a confirmed bug, or did someone just turn it in as one and it hasn't been assigned a status yet?
[G1 Android Development] cyanogen:
I did a heap dump of system_server and the majority of objects on the heap are char arrays in AutoText objects. Not sure what this means yet.
[G1 Android Development] brios86:
im currently using your ROM and its great but i have one suggestion when typing a txt message it shows you a few suggested words thats fine but when selecting the word it wont put a space after it like other ROM's do i just find it a little annoying, great ROM