yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] Telemaniaka:
+1 for the people experiencing the clock being behind issue. I Usually just run ClockSync in the morning when I'm on Wifi (My carrier is either a moron or a jerk. NTP requests time out.).

Anyway, I wanted to ask how can I see what applications get killed when I run out of memory? I want to try running without CompCache and see if anything important gets killed.

If I understand correctly, turning off CompCache will make the phone slightly more responsive since it won't have to compress and decompress part of the Ram, right?
[G1 Android Development] JtotheC:
The default on my G1 is north-america.pool.ntp.org, which works fine for me. I've never experienced any time lag whatsoever.

Sorry, this ended up in the wrong spot. I bit out of context now. :)
[G1 Android Development] ezterry:
You are over simplifying things..

Ok for seeing what minfree is killing run:

adb shell
cat /proc/kmsg | grep send\ sigkill

The lower the adj number the more important android considered the killed task.

Keep in mind many things on our phone are not able to be killed as they are the core of android and launcher, or services and have a low adj number.. Its easy for most of this to have unused/rarely used ram that can be compacted into the default 8M compcache. Thus provide some more ram for more importaint tasks.

That said if your compcache is too high yes things will slow down was it needs to decompress ram to use it.. On the otherhand if a service keeps restarting because its killed and needs to restart much more cpu/lag is made by respawning the background service. Of if an app is killed just before you use it again.

2.3.7 is behaving a bit better in low ram I've actually was able to reduce from 20m compcache to the default 8.. and things are running well.. also getting some more help from KSM, still ballancing that in terms of scanning slowly to save some ram but not at a high cost of CPU/Battery.
[G1 Android Development] tom0769:
Hi Terry,

always a great pleasure to follow your explanations on how android is supposed to work.

Thank you
[G1 Android Development] Maxamillion:
One question, has the mms bug been ironed out, or are people still experiencing lost messages? I just want to make sure before I go back to this rom, I can't risk losing any messages.
[G1 Android Development] ezterry:
I can tell the following:

1) I will not guarantee messages won't be lost on this or any other rom I distribute.. if it has a known bug or not.

2) AOSP gingerbread's method of forking a service when a message arrives; rather than storing it instantly then dealing with gui elements will always allow for lost SMS/MMS messages as the confirmation is returned before the message is saved to persistent memory. This is true for all android phones running the current AOSP code; as they will loose the message if power is lost or the process somehow terminated at the right point in time.

---

Now I've done what I can and we are nearly never seeing this as of late; however you may still wish for Gingerbread Ghostly SMS to be absolutely sure..

This is mostly being prevented by locking the MMS app in ram for a period of time after a message arrives.

The exceptions to the above usually happen when your system is extremely overloaded (nearly crashing) and a message arrives, in this case MMS sometimes fails to launch and thus we see no message even if it whould be locked in ram if it actually launched.. (Usually this includes something with the web browser about to crash the memory with or without the message.. or trying to interact with the system while start up items are still loading.

I believe this is amplified with Gingerbread Ghostly SMS as then two apps needs to be both in ram when a message arrives (thus has a potential larger memory footprint) this may also be an issue with other 3rd party MMS apps. (of course in the case of Ghostly its trivial to get back the message)

----

Keep in mind CM7 based roms are also not immune to this, just on most devices there is the ram needed to make this highly unlikely particular if the user locks MMS in ram.
[G1 Android Development] creezalird:
cant wait for the next build compiled from 2.3.7!
[G1 Android Development] ezterry:
I'm in the middle of various features... once these stabilize there will be a build.. I was hoping this weekend as I will not be able to next.. but its not ready now.. and I spent too much time on this yesterday.. so it may need to wait.

Still feel free to build it yourself, the code in the public repo builds into something that seems stable; but I'm testing compressed libraries and binaries.. that I need to verify (a) work and (b) don't slow the phone down to a crawl.
[G1 Android Development] lacus88:
I know that this is not that important, but can you change the sms notify icon to the gray one, in the next release? it is difficult to notice a black icon in a black background.

Thank you.
[G1 Android Development] hrk:
Unless I'm mistaken, in Gingerbread the HDPI icon is grey whereas the MDPI one is black-ish. I based Ghostly SMS' icons on the official ones and I recall that difference.
[G1 Android Development] ezterry:
BTW for anyone interested I need the following:

5 or 6 testers of this new 2.3.7 build; The build is not complete but some very large changes in structure have been made; The stability of this needs some runtime by me and others who can provide a details bugreport and logs if something goes wrong.

I'm still working on cleaning up some of the ezgb features so this is not final; but if some testers are interested drop me an pm with your email (or email me directly) and I can provide a link to the test build and some additional information.
[G1 Android Development] Maxamillion:
@andisa

Could you please share the wallpaper you have on your screenshots on the ADS Magpie dropbox page?

http://dl.dropbox.com/u/9870397/android/ADS_magpie/index.html
[G1 Android Development] lacus88:
You are right, but cyanogen has it in MDPI res, in his sources.

There you go
[G1 Android Development] ibraheeemz:
Flashed the test build and using it for a while. Speeds seems improved, with around 75 MB free internal memory for apps.

one thing I am facing and I want to get rid of it is: "The Market" itself updates without any confirmation and the newer version is heavier. I dont want it to update automatically. Any help???

and its not with the newer build, I was facing same auto update of Market with the 2.3.5 version too
[G1 Android Development] AndDiSa:
You need to remove MarketUpdater.apk and you should not have any longer the market automatically updated.
[G1 Android Development] ezterry:
Yes rmcc manually scaled the image them and added them it to CM7.. now merged into ezgb as well:

https://github.com/ezterry/GB-packages_apps_Mms/commit/383b702b1119a758dc84b7a670a32c4038f7236c
[G1 Android Development] hrk:
I so hate you... now Ghostly's notification icon will look wrong! :P
[G1 Android Development] ezterry:
.. well yes that it does (actually I'm so used to the old icon I'm not sure it just dosn't look wrong regardless.. but it fits the gingerbread style more now)..

Of course in your case it already looks wrong to users of cm7 or at least cm7.1
[G1 Android Development] tvall:
2nd day running ezterry's test builds. Run great! Feels faster than latest beta and is significantly faster than firerat's cm7.

60-75mb ram used according to the running apps menu (cm7 used 70-80mb).

Only rebooted once so I could upgrade.

odexed framework saves time on first boot and I havent noticed performance difference.
[G1 Android Development] AndDiSa:
I do agree fully. I am actually running an yet unreleased ADS_Magpie build based on Terry's latest changes and the ROM seems to be more responsive than before, even if Quadrant Score is a bit lower when KSM is enabled. The overall performance is really impressive, especially when you consider the 3 year old hardware of our G1.
[G1 Android Development] hrk:
I'm wondering: how does KSM help our devices? Is it because it claims pages belonging to Dalvik VM? It's a feature thought for virtualizing servers, with examples of "This Red Hat can run 52 Linux guests with a 40% RAM reduction!"...
[G1 Android Development] zamc:
Can i make a stupid question ? in gingerbread when you want to put in screen power control widget, you were able to choose whitch power controls to put (bluetooth, gps and light for exaple). When i try to put power control it didn't give me this choice. Also in phone list i can't make it to show call button in the list.

These two seems froyo to me? I am wrong?

(Forgive my English)

:D
[G1 Android Development] AndDiSa:
I asked the same question to Terry some days ago and he told me, that dalvik vm is lauched several times and so KSM can merge same pages. He expected a reduction of memory usage of about 4-5 MB. At the moment I have reduced zram to 12 MB and enabled KSM and it runs very well ;)

---------- Post added at 11:11 AM ---------- Previous post was at 11:06 AM ----------

Go to Menu > EzGingerbreadExtras > Configure PowerWidget > Widget Buttons

There you can configure which buttons are shown and in what sequence they will be shown.
[G1 Android Development] zamc:
Thanks a lot! About phone lists? (i thought gingerbread gives you the choice for these two by default)
[G1 Android Development] erotser:
Is there a chance for us magic users to see this new Ice-cream sandwitch? I recall reading something about it being somewhat possible but with a different launcher(?)
[G1 Android Development] tvall:
Ask again when we have the source and have an idea of what we would be dealing with.

Someone will probably port the sdk soon and it'll probably run terribly like other versions. Once we get the source cyangen will merge it and work on the next cm and someone will probably build it for us.

I'm hoping ezterry will make an awesome rom like this one when we get the source. But he is human and has a life and doesn't owe us anything, so don't just expected him to.
[G1 Android Development] ezterry:
Also I'm not thinking there is much point in porting the 4.0 api to our phones.. most of the new api we can't support.. And most apps using bits we can will likely keep gingerbread support. (There is less interesting low level features in ICS than compaired to the ones in gingerbread).

Also our phones have very bad 2d hardware accel. (Now required and expected by many of the new non optional api components) 1) the graphics chip uses cpu time on the arm11, 2) download the original build if you forget what the framerate was like prior to adding froyo software 2d copybit rendering back into this gingerbread rom.

That said I will be working on ICS code on at least my tab and prob a new TBD phone (so If it proves easier than I expect to port to the DS I will).

Also I hope to back port some of the new features bug fixes ect if possible to ezgb even if I keep it overall API at gingerbread levels.
[G1 Android Development] repast:
After enabling KSM, is a reboot required? TIA.

I've run it with no KSM (default) for a night and things seem to run reasonably smooth, except I got a bit more FCs here and there (after fix_permissions but I did not wipe data/factory reset, only did wipe cache(s) before flashing, that could be it).

1. It feels more capable when i open/switch between apps.

2. I got a positive surprise in battery usage. The slope of the battery decline seems to be more graduate. In the list of apps I have WIFI 48%, DISPLAY 27% cell standby 17%, phone idle 4%, maps 4%. This is with 20M CC.

3. I constantly have more free RAM available, currently mine is at 58M used, 31M free, previously more like 20M free. I guess that explains why it feels better when switching between apps? (I am also running a SetCPU with 3 profiles so it takes 2.7M memory)

One more comment is that after flash this 2.3.7 rom, during 1st reboot the phone stayed significantly longer in "ANDROID" screen than I expected before booting completed.

After boot I used to get a black screen and had to FC on zeam launcher in order for it to become usable, however, reflashing zeam launcher and fix_permissions, followed by 1-2 reboots seems having solved the problem of FCs on the zeam launcher.
[G1 Android Development] d3vilskid:
Reading a few pages back what is this KSM or what does it stand for? And ezterry any plans on adding zcache to your kernels? Or is that for newer phone/kernel.

PS: miss being an old g1 user, mines broke and had to upgrade.
[G1 Android Development] AndDiSa:
@repast: did you clean dalvik caches before the first startup? FCs indicate to me, that you probably forgot that.

After enabling / disabling KSM there is no need to reboot.
[G1 Android Development] creezalird:
testing ads latest build and so far can say much better,reduce zram to 12mb with KSM enabled.

Sent from HTC Magic ezGingerbread
[G1 Android Development] ibraheeemz:
Using test build for 2 days and it seems OK. same observations as that of others.

So far, used it with default settings i.e. 8MB zram, no KSM and seems almost similar or may be fractionally improved in speed. Just enabled KSM module and will observe it further.
[G1 Android Development] repast:
@AndDiSa: I think I did remember to wipe "dalvik cache" and "cache" from the recovery before flashing the zip file. But I did not flash them again before the first reboot after the flash. Neither did I do a super wipe. Not sure what exactly is the culprit. Thanks for letting me know that a reboot is not needed after enabling KSM.
[G1 Android Development] tom0769:
Is KSM a feature of the kernel, so that it can be used with other roms (maybe froyo)?
[G1 Android Development] AndDiSa:
Yes, it's a kernel feature, but it's included only within kernels >= 2.6.32. Some additional infos can be found on http://www.linux-kvm.com/content/using-ksm-kernel-samepage-merging-kvm
[G1 Android Development] ibraheeemz:
My gmail is not auto syncing, although auto sync is enabled!! previously it was working perfectly but after the test build I never received any email automatically, I have to manually sync all the time!! any help???

Edit:

I deleted Market Updater after flashing the test build, but I don't think it will have any connection with emails.
[G1 Android Development] Bladyle:
I use latest AndDiSa version and everything work except sometimes when I turn off display button lights continue to work. And other problem is led indicator don't work when I have missed calls.. I think this is kernel issues but I'm not sure

My phone is HTC Magic 32a.
[G1 Android Development] ximmox:
I am a bit confused, everyone is talking about how good the "test builds" work, has everyone flashed the one released from AnDiSa or am I missing a link that ezterry posted for ezGingerbread itself? :o
[G1 Android Development] punshkin:
:O itself?

haha
[G1 Android Development] ximmox:
The ROM itself ... or do you suppose it to be male or female? :rolleyes:
[G1 Android Development] AndDiSa:
No, most likely not. I suppose it's a memory problem. How much zram do you have configured Are you running with or whithout KSM?

I had the problem, that calendar didn't remember me to appointments when I was running the ROM with 12MB of zram and KSM switched off. So either increase zram or enable KSM, but KSM is experimental! I had a random reboot when KSM was enabled.

---------- Post added at 06:34 PM ---------- Previous post was at 06:32 PM ----------

Terry invited some people to test a build which is not released yet. Other people probably compiled it from the sources, because you can find everything you need for the latest build on Github ;)
[G1 Android Development] punshkin:
my fault, i thought you were referring "itself" to ezTerry (what would have made him neutrum ^^)
[G1 Android Development] greeneyes2910:
Kernel

Hi to all.-.

I following this thread since terry started to develop for our devices.

I´m already imagine about his/your kernel Devlopment so far.

I´ve must say, that I donßt have any knowledge about Kernels ~ so my ask to you all ~ is there a chance to compile a 2.6.38.8 or perhaps any kind of 2.6.39 Kernel for our devices, or wouldn´t it bring any advantages of performance?

Greets
[G1 Android Development] ibraheeemz:
well you were right. I was using default 8MB zram and sometimes Gmail synced and sometimes not, so I have increased it to 16M and it is working super fast now, and KSM is enabled to and I haven't observed any reboot since the flash. About 4 days or so... :)
[G1 Android Development] psychosonic:
Well, I just now starting having a problem after a month and a half of no issues.

I'm currently installed on the 8/28 binary btw.

Tonight, while on the My Apps page of the market, I decided to update the Terminal Emulator app. However, after pressing Back after the update, the market force closed. And every time I tried to open the market after that, it would force close. So I tried the market "fix" that tablets have to do, where you clear the Market's cache and force stop it, and then clear the data for Google Services Framework. Then open the Market, see a server error, restart the device, open Market. I got to this point, and as you normally do for the fix, you then restart one last time. During this last restart, my phone stopped getting past the G1 splash. I left it there for 15 minutes, with no change. I also tried restarting.

So I then I went into CWM recovery, wiped data/system, and then restored from my last backup. It went through, I restarted, and now it still has the exact same problem of now getting past the G1 splash. It just sits there.

What the hell can I do here? It won't go past the bloody splash even after a restore.

EDIT - Welp, seems that there was just a problem with the backup I made or something. I superwiped and restored back to an older (although practically worthless) backup, and it loaded fine. Tried with the relevant backup and the same problem continues. Ugh, seems like that backup is just lost to the winds. I guess I can use this as an opportunity to try a new ROM. Or something.
[G1 Android Development] psychosonic:
Sorry for the double post, but I have a question about A2SDext.

I'm actually checking out a couple other roms to compare to this one now, but a lot of them don't have A2SDext out of the box. A brief googling led me to Simple2ext app in the market, but it only gives the option to put ALL apps or none on the EXT, it doesn't give a choice for each app, like this rom does. Would I just install Magpie and its 002 hotfix from firerat's post over at Cyanogen, or would that not accomplish what I'm trying to get here?
[G1 Android Development] Unrelashade:
Psychosonic, you seem to have experienced a similar problem to what I have experienced a couple of times. It startet with apps force closing one time and when started again had their data reseted. It also happened to a.core.process an the launcher didn't work anymore until it only booted up to the shiny ANDROID logo and being stuck in a boot loop. I fear that my good ol' G1 is finally too old... Maybe the flash memories don't work anymore and stuff gets corrupted? So it force closes and resets the data because it can't be read anymore? That's the only explenation I got... And it would explain your problem also. However it seems to work for some weeks when I wipe again.

Other problems I have with my old phone is that the battery life is really bad, even if I don't use my phone, it still runs out of half the capicity a day because of cell standby :( And a reload cycle takes more that 10 hours sometimes...

And my space-key is kind of broken, does not recognize presses sometimes.

I would gladly accept any help/ tipps or just hear from you guys if you seem to have the same problems.

To Apps2SD I cannot say much. ADS Magpie is said to feature it and also be a good rom. Haven't really tried it. Or of course, use Androids native support, but I suppose you want to move apps that the system does not let you move, like purchased apps?
[G1 Android Development] kanttii:
Do anyone have more recent builds compiled that 0828? What are those ksm and zram you're talking about? Github repo seems to be quite active but OlI can't compile it myself :/

I'd love to try it out.

Device: HTC Magic 32A, radio 6.35.26.19, hboot 1.76.2007
[G1 Android Development] tvall:
Ezterry currently has a few test builds. latest is from 17 Oct. Email him and he ill probably give you a link.

AndDiSa has some newer builds too. You could try those
[G1 Android Development] psychosonic:
Agh. Made a backup after getting everything to be perfect. Flashed a UOT theme which didn't work for some reason, and I got stuck on the G1 splash. So I restored from the backup I made and... stuck at splash still. I'm nearly ready to throw this thing out and use some crappy 20 dollar phone. ;_;
[G1 Android Development] AndDiSa:
I suggest you to do a

fastboot erase system -w

and to wipe dalvik-cache (even on /sd-ext, if you have a sd-ext partition), then restore your backup.

If the backup was fine, your phone should startup again.
[G1 Android Development] ibraheeemz:
Using the test build, I have an observation that, after a standby for sometime, all apps respond very slow when I re-open them. I have zram=12MB and KSM module is enabled and GPRS/Edge connected all the time . Although it is a hell stable but responsiveness seems an issue sometime,

I only use gmail, gtalk, messaging and phone apps frequently which I feel were more responsive previously. I don't use GPS/Maps etc..
[G1 Android Development] AndDiSa:
I've noticed the same behaviour. In my opinion it's because of re-activating apps and they have to be either re-started or at leaset swapped in. This takes time, especially when there is additionally KSM enabled.
[G1 Android Development] ezterry:
KSM is not real-time, it runs slowly all the time in the background.

It will slow you phone overall (few quadrent points) but nothing special on load.

Where things are different in the new build is more apps and libs are compressed ... if too many shared libs are compressed it takes longer to load .. this is why I only moved some of the libs to xlib.. when the largest were there the phone slowed to a crawl

Also compcache (zram) can slow things down, 8mb is good for the little bit of extra nearly never used memory after startup.. but here you need to ballance things, its useful if you stop services from stopping / respawning constantly in the background when you start a new app. Its not so good when you are waiting for ram to decompress so already loaded apps can continue. This can feel even slower if you are also re-loading many zlib libraries in either of the above scenerio.

My biggest puzzle with the build was why my phone rebooted and kept rebooting everytime it connected to AT&T's 3g service near the capital beltway in Maryland. (was fine in/north of Baltimore, and further south in VA.. also worked after I forced it into 2g service with the sim card out, then returned it)
[G1 Android Development] AndDiSa:
Thank you very much for your explanation, it's very helpful to understand what's going on behind the curtains.

Since several weeks now I didn't had a reboot. It's very stable, but I am always on 2G or WiFi. The overall performance for me is acceptable, I can live with it. It's not comparable to a Galaxy Nexus, but still sufficient for most of my daily needs.
[G1 Android Development] psychosonic:
When you say to wipe the dalvik, do you mean to wipe it in amon ra after the fastboot wipe, or to use a fastboot command? Also, how would I wipe the ext dalvik?
[G1 Android Development] AndDiSa:
If you do a

fastboot erase system -w

, your dalvik cache on /data should be clean already.

But to be sure that ther are no leftovers from old ROMs, *after* restoring I would do (either with shell from AmonRA or via adb shell in recovery mode):

mount /data
rm /data/dalvik-cache/*
mount /sd-ext
rm /sd-ext/dalvik-cache/*
umount /sd-ext
umount /data

Now reboot your phone.

Another hint: as Terry wrote in his last post, there might be problems that enabling 3G in certain areas may cause reboots ...
[G1 Android Development] psychosonic:
Awesome, thanks, I'll give that a go after work tonight. I'll update you guys on if it works.

EDIT: It worked. I love you. Thank you.