yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] ezterry:
reboots when ram is stretched thin I've seen.. I've not tried copilot on here.. If you have maps + faceboot widget + other active services try killing them .. and maybe increasing compcache to see if you can find a better balance.... The way to see this is last_kmsg after the system boots again.. you can run it as root on the command line for later review if you wish: 'cat /proc/last_kmsg > /sdcard/kmsg_1.log' then the file on the sdcard can be looked at... if its in free_pages I've probably seen it.. (feel free to post your copy.. but no need to post 100s) if its something else its new

I've not seen much issue with gps (slow to find a signal aside) however.. there are some patches I need to add in from the creator of the shim in Cyanogenmod's repo.

The biggest problem I run into is I can't get to the google api for locaiton data via https on the rogers wireless network.. (I have some hacks to force it to http via a sql into google services I posted a while back for the froyo roms)
[G1 Android Development] creezalird:
i have the same thought too. Every navi app i tried sometimes will reboot my phone after 5-10min.

Regarding dalvik.vm.heapsize value in build.prop, and there is also vm heapsize option in spareparts, if i set both differently, which will be used? for example in build.prop i set heap 16m and in spareparts 24m

add : i've increased my zram size as needed by observing in terminal (free) to 16m , i do not have maps + fb widget but i do have other services such as tasker and whatsapp which maybe consuming a bit more memory, will try to kill all for more effective test.
[G1 Android Development] jdb78:
I don't use those fancy animations, I turned them off or switched to fast where off is not possible. So when I realize that the phone is not responsive, I mean "I push on the touchscreen and wait for seconds until a reaction takes place" or there is an incoming phone call and it takes 5 seconds to ring and another 5 seconds to show the caller ID on the display. I don't use facebook either, I don't even have an account.

But I agree with you that maps is a "killer" app. I use Autostarts to prevent apps from starting up for some weird reasons but I use Google Maps occasionally. As soon as I started Maps my device begins getting even slower due to the huge amount of memory the "Google Services" need then. Thanks to autostarts I don't have that many apps running in the background.

Nevertheless due to the security updates I guess I have to stay with the latest build ;) The one without zRAM (ADS 20110416-1) was running best up to now. Responsive like hell, very few FC's... But I'll give ADS_magpie-20110517 a try now.

I'll try your advice "setprop persist.zram.size 24"... Maybe it helps :)
[G1 Android Development] jdb78:
Hm I might be wrong but didn't change Google the Api recently because user hashs and ID's were transmitted in clear ASCII? I think they allow https only now.
[G1 Android Development] ezterry:
Well remember I'm also going for well rounded settings.. I don't know if you are better off with 0, 8, 12, 16, 20, or 24mb of compcache (maybe 28,32,36 are also in that list..).. A phone without all the gapps may be faster at 0.. with min gapps and gmail 8 is about right.. but as I said with all the apps on my phone 24 is winning..

You want the value low so you don't spend all your time decompressing ram.. and high so you don't spend all your time killing/starting the background services.. and maybe keep that last common app in ram.

The original minfree settings may be correct for you .. but failed to run the background services for many.

For me and many the new setting are much closer to the optimal ballance than the original.. but maybe this is not the case for you.

Of course the problem is minfree is that it isn't a yes or no but multiple values so you need to figure out what value is impacting your current operation. The first values ought to be lowish so apps that you see don't die.. but still leaving some breathing room; and the latter numbers low so backgroud apps stay in ram so they don't repawn.. but high so the impact to the visable apps is minimal.

The google location service has been over https for a while.. but has not been working everywhere..

I'm not sure what info the include.. but the location service worked without logging into google so I'm unsure what is transmitted other than the local wifi accesspoint essids and cell tower ids.

I'm also trying to get more info on the security hole as saying 2.3.4 is fixed but we don't have a full set of armv6 compiled gapps is a problem.. (so I can't be possitive that the issue is fixed)

Nor am I sure what to do with google location service... over wifi it works fine with https.. its just an issue with the natted wireless carrier.. Yet I hear t-mo is fine

Edit: just looked again seems to have in the last week returned to https and is working.. maybe google/rogers fixed it.
[G1 Android Development] HyeProfile:
Something tells me Google/Rogers read your posts with great interest... :D
[G1 Android Development] ezterry:
maybe.. but I know various German users also had such issues with their carriers..

I suspect it is something silly since these are large nats.. maybe google just thought it was an attack from the IP. Since I had no problem with other https services from the phone or tethering be odd if it was deliberate.
[G1 Android Development] ibraheeemz:
Can anyone please help me how to flash ezGB latest kernal over a rom? I want to try it on some other ROM. Will the zip from github be flashable directly? or I will have to do some work, I have SDK setup, adb and fastboot working fine. If something needs to be done, please help me out.

Edit:

I just read the first post of thread and it made my life easier. Will build the kernel soon for me :)
[G1 Android Development] ezterry:
gtalk2

Anyone testing voice/audio chat.. here is something to try (I'm working on other things atm so I leave one of you to test this):

This assumes you are using gapps-mdpi-gb-20110508_b_S.zip

1) Get: libtalk_jni.so

MD5: 0a7b7d40d6c0144219ea90082ec88104

2) adb remount

3) adb push libtalk_jni.so /system/lib/libtalk_jni.so

4) adb shell chmod 0644 /system/lib/libtalk_jni.so

5) adb shell sync

then reboot and test gtalk

Note: This library is a bit large (3Mb) and my not be entirely intended for our old CPU thus some or all of it may not work 100%

Also its not really intended for our devices.. most people will find Talk works fine (as long as you avoid audio/video chat) without this
[G1 Android Development] roccoadam32:
I use autostarts to disable google maps on startup and on other events solved issues with it for me
[G1 Android Development] AndDiSa:
I am running the latest ADS_Magpie with a zram size of 16MB now and I have the impression, that it's as snappy as the version from 16th of April. This means to me, that Terry's settings are not too bad. :)
[G1 Android Development] hrk:
Ok, I'll toss a couple of questions, then! I've been running the latest ADS_Magpie / default settings, which means i don't change the minfree and I am running the default 8MB cc/zram. The only difference is my 128/614/interactive CPU settings. It works fine but for two issues:

1. When receiving a call, phone starts ringing but I cannot answer or see the caller until around 5-10 seconds have passed. Often it's time enough for people to guess I'm not available (since I tend to answer almost immediately).

2. Occasional "clean" reboots. :(

3. Occasional "weird" reboots. :(

Yesterday I was preparing a new release of NoFrills and the phone rebooted three times after the "Starting activity on device ...". I saved the last_kmsg. These are the "clean" reboots.

What I call a "weird" reboot is that sometimes the phone becomes unresponsive, and then it look slike it is "too much" unresponsive. Indeed, if I wait a little more, I see the bootanimation fire up. No carrier/first logo, it goes straight to the bootanimation (my guess is that all the unresponsiveness was the initial reboot without carrier logo being displayed) and then, after it has completed booting, my Nofrills tells me that it detected an unclean shutdown and did not set the frequency values, but when I open the GUI I see that the values have been applied. Now, knowing my code, I can trust my own messages :D so the frequencies and governor seem to have been "kept" during the reboot. And this is where I say "WTF?". I don't have a last_kmsg of this, because it often happens to me while I'm busy and can't lose any time (ah! the irony of getting a reboot right when you're following google navigator in an unknown place and someone calls you!)

Has it happened to somebody else? I'll try getting a last_kmsg next time (I know there'll be a next time.........)

The last_kmsg for yesterday's two reboots while uploading the app to the phone: http://pastebin.com/RJHT9Vk5 and http://pastebin.com/GwFEzaRD
[G1 Android Development] farmatito:
Could this eventually be pushed to /data/data/com.google.android.talk/lib/ instead?
[G1 Android Development] creezalird:
by increasing the lowest freq cpu to 245mhz, the lag for incoming calls is a little bit decreased. But still noticeably slow to show who is calling..
[G1 Android Development] ibraheeemz:
I think the reboots are because of 614 CPU, whenever I set CPU highest to 614 it reboots occasionally and I have to lower it down to a max of 595, but the rest is same observed that it does not show caller name/number untill 4,5 seconds.
[G1 Android Development] ezterry:
No not in any sane package that hasn't serious considerations.. Unless Google is nice enough to release a market version anyway.. then its easy (just download the market version and drop it from the gapps package)

A) we can't re-sign Talk.apk in case google ever releases an update on market. So I can't just install it all to /data with the modification for embedding the lib.

B) If embedded into a /system talk.apk you will have the library both in the apk (50% compressed) and on the data partition

C) if I install talk to system, and pre-populate data.. if the system is nice not to purge it on me I break wipe userdata.. since if you reset to factory settings you will purge the lib.

Now you can come up with ideas such as lzma squashfs to put some gapp files into to shrink its system size by nearly 2/3 or leave it optional so it only eats the space of those that really care.

But why care /system or /data .. the partition lines are virtual so its really the same MTD device space.. you don't get a speed reading from one or the other or both.
[G1 Android Development] farmatito:
It was just about free space on system....

would it be possible then to move the big lib

to /sd-ext/lib/libtalk_jni.so and symlink to /system/lib/ ?
[G1 Android Development] ezterry:
If you are manually installing the lib and are short on /system space by all means put it somewhere in /cache /data or /sd-ext and symlink it.

For all I know you can manually put it into the apk's data and it will work in a manual install.
[G1 Android Development] ringochan:
You mean the softreboot? Yeah, I've had similar experience with GB roms from time to time. 90% of the time, though, my phone recovers without soft rebooting (after a bunch of ANR's, I think). It's like 'oom panic' I read somewhere.

When it recovers without rebooting, I sometimes check 'running apps' and find no user process/services are running (they must have been killed by Android), but it says I have no ram left. But, somehow Anrdroid seems to restore the 2 Maps services and Google Voice no matter how limited my ram is.

What I don't understand is that it even happens when the phone has been asleep for a while, not just during or after heavy use. So the incoming call lag issue people are complaining may be related to this.

I also wonder if it can cause battery drain, where our phones don't 'sleep' well and eat battery. Or maybe not.

And, you're right! It happens when you really need to use the phone bad.:o But it doesn't happen often enough so it's hard to analyze what is happenning. Murphy's Law is at work here.
[G1 Android Development] jdb78:
I can't confirm this totally. zRaM size of 16MB is doing better than 8MB but it is still not as snappy as 20110416-1. Could it be that custom MTD is doing some performance tweaks with your phone? I do not use custom MTD... Or might be the installed apps?
[G1 Android Development] AndDiSa:
For sure it's not custom MTD, more likely it's the kind of apps / widgets installed. For example I do not have installed/enabled any syncing application.
[G1 Android Development] jdb78:
Ok, well, I use the Google Software very heavy, so I sync address book, mail and calendar automatically. I can't imagine that this makes my system that slow since I didn't change the way of syncing since 20110416-1. Hm, well, might be the installed apps.

Maybe you can take a look at my phone in June when I'm around :]
[G1 Android Development] farmatito:
BTW: voicesearch is available in the market and contains

libvoicesearch.so so could it be dropped from gapps

or is it needed?
[G1 Android Development] ezterry:
let us know your results
[G1 Android Development] jdb78:
Same here. I use zRAM size of 16MB like AnDiSa does. 8MB is even slower, 24MB shows strange behavior. I use Dazzle as long as I can't set up the power bar widget for my needs and the Business Calendar with a small widget showing the next three appointments. When using zRAM=24MB Dazzle shows a lot of tiny icons but not what it is supposed to show and the calendar widget stays black and shows nothing. Switching back to 8 or 16MB both work fine.

I did see the first boot screen ("G1" logo) and no frills did not set the clock. I use 128 - 528 MHz and after the reboot it was set to 245 - 528 MHz.

I had my first sudden reboot today. I just wanted to start the app "atrackdog", touched the icon and I saw the "G1" boot screen, then the bootanimation, PIN request and so on. So my phone did not skip the "G1" first boot screen like your "weird" reboots. I got a last_kmsg at pastebin from right after the reboot.
[G1 Android Development] farmatito:
So i did it. Removed libvoicesearch.so from /system/lib

and installed VoiceSearch.apk including lib in /data.

Moved also libtalk_jni.so to /sd-ext/lib and symlinked

to /system/lib/.

System boots fine, voicesearch seems to work, talk

starts without FC but I cannot test it.
[G1 Android Development] tvall:
Well I tried to get on facebook this morning, it took me to a t-mobile web page telling me that I need a different data plan cuz mine doesn't support my device... On cos-ds, however, data works flawlessly. I think they might be reading the build fingerprint to detect devices...
[G1 Android Development] jscriv:
I had the same thing this morning (I'm on latest ADS Magpie) however it seemed to resolve itself - data working again fine now.
[G1 Android Development] tvall:
Working here now too. Wonder why they did that then fixed it..
[G1 Android Development] ezterry:
While a may not be entirely convinced the kernel dosn't need a poke.. most of these crashed I'm getting kmsg for are overutalizing ram.

Also the 'wired' reboots are a sign of zygote being killed via oom thus effectivly restarting the Android layer, without fully restarting the phone/linux.

Really a good time to see what services are running on your phone.. and drop any task killers even ones that just kill startup rarely do so cleanly. You are talking about problems I have with huge webpages/games, with ebuddy gtalk, maps, facebook, plume all running in the background.

Now some patches are in the pipe to make this work better and this is in part what I mean when I'm looking for more tuned minfree (the low numbers seem correct and the background task number seems correct.. but I'm not so sure about some of the ones in between. However while I can hopefully make the rom more forgiving.. its best to make sure your normal tasks fit into your phones memory footprint for smoothest operation and longest battery life.
[G1 Android Development] AndDiSa:
Latest patches improved the time until I can see the caller very much. In my latest tests it was less than 1 second. Even with wlan enabled and installing an application from the market while receiving a call it was less then 4 seconds.
[G1 Android Development] hrk:
Nice, I didn't know that.

No task killers, they happened mostly when using Google Maps, maybe I had a couple of notifications for GMail or SMS/MMS. And then a phone call came in :D
[G1 Android Development] jdb78:
I tried your last build for a couple of minutes now. I can confirm that the caller ID shows up a whole lot quicker than with the build before. The phone seems to be a tiny bit more responsive, too - but not really much.

So do I get you guys right when I understand that I should get rid of "Autostarts" which prevents aps from even being started? I don't use task killers, I have the Free Advance Task Manager installed but it is not set to do anything automatically. I'll get rid of it anyway since I don't use it anymore.

Thank you again for your hard work!
[G1 Android Development] ezterry:
Auto start is not really preventing things from starting as far as I can tell.. it just starts on boot and tries to kill all the other tasks starting on boot.

I want a real way to prevent apps that indicate they want to know your phone is booting from starting but in the core system.. It may be better in some cases but still best atempt to be hands off untill all the startup tasks are done

That or go after the app developers
[G1 Android Development] jdb78:
AFAIK Autostarts does indeed prevent apps from being started. There are several scenarios like "after booting", "network connectivity changed", "app installed", "sdcard full" media mounted", "timezone changed" and so on. And every event can trigger an app to start if the developer decided it could be useful. And you can allow or deny each and every app to start or not to start when these events happen.

So it is not killing apps. When you start them manually they run - they won't get killed. It just prevents them to be started from triggers like "timezone changed"... and so on.

But nevertheless it is not really important I guess. The progress you guys are doing is important and I really do respect your good work.
[G1 Android Development] ezterry:
And how do you stop an intent from triggering? I fail to see the logic in framework to cancel the startup event.. it make adding an "evil" flag for apps easier if the function is already there
[G1 Android Development] jdb78:
I ain't a programmer but the sources are available - maybe that helps to see if it kills apps or prevent them from being started :]
[G1 Android Development] ezterry:
ah.. interesting..

pm enable/disable of sub components .. after parsing out the manifest of the apk..

so now my biggest fear for that app is state maintenance.

Continue to use it if you will .. still want something cleaner in the rom
[G1 Android Development] jdb78:
Like I mentioned before, I have no programming skills at all. I trust your skills and if you told me the app is crap, I would believe you.

All I know is what I read about that app: it prevents apps from starting. And TBH I thought that's a good thing, I am doing this with my WinXP system as well to speed up the boot process.

So do you think I should get rid of it because it's doing harm to my system?
[G1 Android Development] ezterry:
There is nothing wrong with the app I can see.. a bit overly complex.. but that is only because it needs to update the state of information android dosn't make easy to collect (what intents and what java classes are those linked to in an app?)

If an application gives you some issues.. before reporting.. ensure its features Autostarts is not modifying its behavior, then uninstall/re-install the app before thinking its a bug.

Any blocking of intents, or permissions has the ability of creating unexpected resuts.. in rom or not.
[G1 Android Development] hrk:
Doing a "ls -lha /vendor/app" on ADS_20110517 (yep, gimme some minutes and I'll update to 20110523) I can see that some apks are different from the ones in the latest gapps-mdpi (20110508).

These are the apks with different sizes:

GoogleBackupTransport.apk

GoogleContactsSyncAdapter.apk

GoogleFeedback.apk

GooglePartnerSetup.apk

GoogleQuickSearchBox.apk

GoogleServicesFramework.apk

NetworkLocation.apk

Talk.apk

Vending.apk

I'm wondering if this could be due to the certificate change and if this means I'm still running old gapps in place of new ones. Since I've seen that even after pushing libtalkjni.so I couldn't see any difference in the Talk app, I think I should manually "adb push" them on the ROM. Should I?

This is a listing of the current gapps in vendor/app, showing only the above apks:

/system/vendor/app # ls -l
-rw-r--r-- 1 root root 36561 Aug 1 2008 GoogleBackupTransport.apk
-rw-r--r-- 1 root root 121647 Aug 1 2008 GoogleContactsSyncAdapter.apk
-rw-r--r-- 1 root root 61343 Aug 1 2008 GoogleFeedback.apk
-rw-r--r-- 1 root root 9301 Aug 1 2008 GooglePartnerSetup.apk
-rw-r--r-- 1 root root 382076 Aug 1 2008 GoogleQuickSearchBox.apk
-rw-r--r-- 1 root root 748426 Aug 1 2008 GoogleServicesFramework.apk
-rw-r--r-- 1 root root 105787 Aug 1 2008 NetworkLocation.apk
-rw-r--r-- 1 root root 480734 Aug 1 2008 Talk.apk
-rw-r--r-- 1 root root 1886058 Aug 1 2008 Vending.apk
[G1 Android Development] AndDiSa:
Looks to me, that these are the old ones ...

If you want to update, I suggest to do a

fastboot erase system

and then flash rom + new gapps otherwise you could mess up like I did ...
[G1 Android Development] jdb78:
AndDiSa: what is your "feeling" about the snappyness of the latest ADS? If it's still as snappy as 20110416-1 for you I'd like to know why mine is reacting that slow. I did not erase system before flashing ROM and gapps - might this be an issue? Oh well, I'll give it a try :D I'll be back in an hour or so *g*
[G1 Android Development] hrk:
Well, being hasty, I just pushed them all... guess what? There was a single one failing........ good ol' GoogleBackupTransport.apk!

Having done this... do you recommend doing the fastboot erase system + flash + gapps? I think this should not delete any data (... no "data" in "system"...) so it should be safe. What went wrong so that you messed up?

EDIT

LOL! (:confused:) looks like I messed up. The phone thinks there's no google account... stupid me pushing the apks on a running system... without doing a nandroid backup first. Guess I can't complain!
[G1 Android Development] AndDiSa:
I installed the new gapps via adb push, too. This seems to mess up something in the settings.db and all further trials to install GoogleBackupTransport.apk didn't succeed. The only way I found, was deleting /data/system/packages* and /data/data/com.android.providers/settings/databases/settings.db.

Probably somebody who knows settings.db a bit better is able to eliminate only those entries, which are causing the problem, but I did it the "hard" way ...
[G1 Android Development] AndDiSa:
Yes, it's still as snappy as before. At the average I have 2 MB of RAM free, 10 MB as cached files/blocks and 3-4MB of compcache free.

Erasing system before flashing rom/gapps has no influence on the snappiness, there must be another reason.
[G1 Android Development] hrk:
Android is sync-ing again all my accounts, as they seemed to be lost. I don't mind... the cloud backup was always active ("Said the man before checking his empty contact list"). Everything seems to be fine, QuickSearchBox looks a bit different but I guess it is an updated one... everything went fine in the end. :) Thanks for the help and suggestions. Waiting for 20110525 w/ the property cleanup ;)
[G1 Android Development] ezterry:
Who knows updated or not.. its the open source one I dropped the gapps one.
[G1 Android Development] hrk:
Hmm... considering that my /system/app/vendor had a GoogleQuickSearchBox.apk and I was still using the old gapps... I guess that the open source one couldn't work, because the other was still present. Looks like the fastboot erase system really helped this time. Thanks to you too, Terry. :)