yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] ezterry:
Out of curiosity has anyone attempted the video/audio chat features of gtalk? (I've only looked so far as to see the option was disabled by default)

---

Also while I'm trying many values and ideas I'm still looking for optimal values for:

Compcache, minfree (fudgeswap seems about right but if you change minfree by a large amount may need a change..) other configurations.

(Most tweaks have little or no notable change)

Related "free" ram in the applications menu its in part using the readonly prop version of minfree in calculation.. I'll try next release to make it more dynamic thus you can see the minfree change more realtime.

----

My biggest problem at the moment is ram used by services..

Android has two types of services

1) those in use by a user visable applications or are "ongoing"

2) those running hidden in the background.. can be killed and will respawn as soon as possible.

Catagory 1 is working well.. but the second really has two group of services

2.a) those I want to be running

2.b) those I don't care about and wish the dev didn't make such a persistant service and just scheduled it to spawn at the next update .. or never if it was not intended to poll.

2.a is not really the problem but

2.b includes many apps I want installed but really don't want running when I don't need them.. this includes a ebook service, maps (yes even without lattitude..)

I am thinking of a way of flagging these apps (in the application settings).. The idea is when running they can run as is (even as a service) but if evicted will not respawn the service. And maybe to ignore them on the startup intent trigger..

The idea is let android memory management work.. just teach it my priorities and not what the apps dev with 5x the ram of the dream/sapphire hard codded the app to do.
[G1 Android Development] creezalird:
Andisa,

just saw that you've updated your build to ADS_magpie-20110510-signed.zip, but somehow I can't see any information in regard to the changes like before.

It is the same changes as in 20110509-1: GINGERBREAD-DS-Alpha-20110509-1.zip?
[G1 Android Development] creezalird:
Already tried the new video in gtalk but with no success, sometimes it closed with FC, sometimes with black screen only.
[G1 Android Development] AndDiSa:
Yes, changes are the same. As soon as I have access to my computer I will fix the problem with the changelog.
[G1 Android Development] sisterchick:
I agree. EZ's work is top shelf. Glad you have enjoyed my themes. I am working on a new website that will hold all my themes, screen shots and downloads for Froyo and Gingerbread. There are three or four themes up for Gingerbread now. I am using a metamorph base with instructions to build your own flashable with ZipThemer so they will work with most ROMS. Site is www.sisterbird.com.
[G1 Android Development] AndDiSa:
While booting up I found the following message in the logfile:

...
I/PackageManager( 229): /system/app/GoogleBackupTransport.apk changed; collecting certs
E/PackageManager( 229): Package com.google.android.backup has no signatures that match those in shared user android.uid.system; ignoring!
W/PackageManager( 229): Signature mismatch for shared user : SharedUserSetting{406f44b0 android.uid.system/1000}
...

is it related to the signature change?
[G1 Android Development] ezterry:
Yes and thus why you need the new gapps (or at least the GoogleBackupTransport from the new gapps..)

most gapps have an unmodified private signature from google that we do not have the key to.. the backup transport however appears to use the platform key)
[G1 Android Development] dhkr123:
Gmail is unnecessary. They provide IMAP access to your gmail account, so you can configure k9mail to get pushed at by your gmail account. k9mail is worlds superior to gmail.
[G1 Android Development] :
terry, would you take the helm of CM for D/S?
[G1 Android Development] ezterry:
For the moment no,

I think its more important to have a minimalistic "AOSP" type rom for gingerbread than the full CM Suite. (Obviously I don't mind adding in cheap features but this is intended to be very minimal for our low end phones)

I mention this because I find the CM base system seems to use 10-20MB additional memory.. On most newer phones this is very reasonable given the additional features packed in. However on the Dream/Sapphire sometimes it seems a better idea to use the ram for the apps I need not the core system.

Once this stabilizes and we start seeing RC releases of CM7 I may see if its possible to make a Dream build if no one else does.. but only if I don't have temporal problems. I'm a bit spread thin and keep getting accused of "dropping" the projects that are on the back burner.
[G1 Android Development] Firerat:
I've not looked at CM7 since gb first hit the repos

just have an occasional look at gerrit ,

but here we have plenty of stuff to play with :)

I've added in Magpie ( not had much chance to test it tbh )

https://github.com/Firerat/GB_system_core

https://github.com/Firerat/GB_dalvik

https://github.com/Firerat/GB_packages_apps_Settings

https://github.com/Firerat/GB-device_htc_dream-sapphire

https://github.com/Firerat/GB-framework_base

included is boot script support ( /system/etc/init.d )

I've also Kanged TINY_TOOLBOX from CM, so we use some of the better busybox utils instead **

I'll upload a test ROM soon

Included with magpie is support for system dex files on cache.

But atm its 'turned off'

removing

dalvik.vm.dexopt-data-only=1

from build.prop will put system dex in /cache/dalvik-cache

No good for dream *, but good for sapphire ( unless /cache is at min with customMTD :)

Could do with Kanging Kali-'s verify_cache_partition_size.sh

* depends on number of gapps

if

du -hcs /data/dalvik-cache/system@*

is less than the 27mb 1.33.0013d /cache size

it will free up space on data

** seems to be a bug were system doesn't get formatted, so old symlinks remain and 'breaks' stuff

never noticed it before, just had a quick look, not sue why the format is passing yaffs2
[G1 Android Development] nomadman:
after installing the latest of any rom i end up stripping it down to the miniumal.. no anim, no sounds, minimal gapps services, and hardly any widgets.. so i have to agree with terry that on my machine, minimalistic is the way to go.

once gb final is released for this machine, i'll finally have the funds for a dual processor phone with ample memory.
[G1 Android Development] irisiris:
Totally agree.. Minimal version with maximum possible RAM is what is needed.

Don't want apps to be killed when out of RAM..
[G1 Android Development] sparksco:
Your the man!
[G1 Android Development] Firerat:
just to annoy you I'm going to quote your whole post !!
[G1 Android Development] sparksco:
Awesome thanks will have a look! Also does this have the any spl installer like the old magpie rom that causes a green tint issue for sapphire's/new spl and radio's?
[G1 Android Development] bestofrhcp:
not to sound noobish, but how does the tnp update bypass it? does it use 2.2.1 gapps or something?
[G1 Android Development] lolmensch:
btw you should eventually mention that just the kernel allows different phones. normal 32b on danger isnt supported by default. fails at the spl check.

removing spl check already solves that.

btw was Automagically an intended pun? :D
[G1 Android Development] Firerat:
you know, I didn't even look at the assert checks

Spoof as 1.33.0013 will resolve that :)

And yeah, I like AutoMagic
[G1 Android Development] jaychym:
I have a mytouch 3g 1.2 and i can't get this to boot....I don't get it does not even allow logcat so its the kernel giving me issues, any ideas?
[G1 Android Development] Firerat:
what radio/spl?
[G1 Android Development] sparksco:
Well if you get annoyed over a post that's not really that long then you have issues. It was never my intention to annoy you, but it seems you let yourself get annoyed with things quite easily. Not to mention you completely avoided my question about the any spl installer for mytouch 32b 2708, which was the whole point of my second reply in the first place. Not sure how a second reply even occurred, think my internet was being wacky at the time
[G1 Android Development] jaychym:
radio 2.22.23.02

hboot 1.33.0013
[G1 Android Development] blahbl4hblah:
I'm pretty sure you need the new radio 2.22.27.08 or 2.22.28.25
[G1 Android Development] ascadian:
Thanks for the gingerbread.

In the third alpha release i followed these steps[1] to get SIP/VOIP. Outgoing and incoming calls are working as expected.

Basically its adds the missing xml files:

android.software.sip.voip.xml

android.software.sip.xml

from AOSP to /system/etc/permissions/

During my research however i noticed there was no "android.software.sip.xml" file in the rom for the desire (oxygen-2.0-RC5). So maybe this one is not needed.

[1] im not able to post links: http:/ / xilard.hu
[G1 Android Development] Firerat:
hmm,

well it should be flashing the EBi0 boot.img ( I think that works on the MT 1.2 )

if you have adb , you can confirm which kernel with

adb shell ls -l /tmp/

after the flash

you should see something like this

lrwxrwxrwx 1 root root 17 Jan 5 02:58 2708-boot.img -> /dev/null
lrwxrwxrwx 1 root root 9 Jan 5 02:58 EBi0-boot.img -> /tmp/boot.img
lrwxrwxrwx 1 root root 9 Jan 5 02:58 EBi1-boot.img -> /dev/null
[G1 Android Development] creezalird:
Just tried ADS_magpie-20110510-signed.zip , but nandroided back to backup.

Reason is somehow Titanium Backup keep on FC'ing on start. I've tried repair permissions and with no luck. However I forgot to keep my logcat in check. This was on fresh fully wiped install.
[G1 Android Development] AndDiSa:
Strange, because I flashed the new gapps on top, but I didn't wipe nor cleared dalvik-cache ... so probably on startup it was still reading the old version from vendor/app (the location where the backupscript is locating gapps). I will keep an eye on it.
[G1 Android Development] ezterry:
Many of the packages have the same version so if there are two copies it will get confused..

Dalvik will correct its self as well as signatures otherwise

(Maybe wipe system either 'fastboot erase system' or format system in clockwork before upgrading to the new signature version)
[G1 Android Development] Effdee:
I find

git whatchanged -p <file(s)>

quite handy

without the -p you get a github like history view

with the -p you also get the diff inline

lol, I never use git log just tried it

log is same as whatchanged

makes no real difference to typing with bashcompletion
[G1 Android Development] AndDiSa:
Current settings are running well for me. I do have multi tasking and also the lag when starting new apps has decreased. Probably it needs some minor optimization, but it's the right way.

Interesting idea ... probably this will help also to reduce the amount of CC usage. At the moment on my phone it's used almost always at 100%.
[G1 Android Development] Telemaniaka:
The app itself works great

But Voice doesn't :\

http://pastebin.com/Pgz5vMc9
[G1 Android Development] ibraheeemz:
Thanks for the themes will try. Was facing download error from this theme:

http://dl.dropbox.com/u/6409094/Sisterchick/MinimalBlue_GB_MM.zip

I think the file was not uploaded properly, gives error 404, not found sort of...
[G1 Android Development] ibraheeemz:
perhaps the home app other than ADW is not supported with these ROMs!! I am using launcherpro!!

also I wanted to share a little problem I have been facing with the latest build!! I am unable to add favourite contacts!! even if I mark a contact favourite, it does not appear in the favourite tab!!
[G1 Android Development] sisterchick:
You probably caught it in the middle of a reload. I updated today, so please try again. Also, I created a thread in the theme section for comments so as not to clutter this thread. http://xdaforums.com/showthread.php?t=1074762
[G1 Android Development] ibraheeemz:
yeah, I was also thinking so that this thread should not be used for such discussions, though information only stuff may be put on board!
[G1 Android Development] creezalird:
somehow i found out why the crash/FC from titanium backup, the vm heapsize 18m seemed to be not compatible with titanium backup, if i changed that from 18m to 16m back.. the app will be running normally.
[G1 Android Development] ezterry:
That makes no sense... but what do we expect from app that seems 2/3 snake oil..

really install app normally.. copy data into place and run fix permissions on that app.. that is the idea..

Maybe a little more for contacts and SMS/MMS but other free apps have such logic.

yes a gui for it all (and that is important) but it seems to have more edge case behaviors than that core operation ought to have.

-=-

regardless I just did some testing here.. no problem with the new default 18.. You have the latest version?
[G1 Android Development] AndDiSa:
Hmm ... having still the same problem. I am sure I installed your latest gapps. All other gapps are accepted, only GoogleBackupTransport is signed with an unknown key.
[G1 Android Development] ezterry:
um .. just looked in your ADS_magpie-20110510-signed.zip package.. and settings.apk is still signed with the old key

check in build/target/product/security:

dc51923f7c868283db1bd9ab8c78dee0 platform.pk8

6dc8b8430ec90cb9e8095f73f587dfc3 platform.x509.pem

Otherwise all I can say is 'make clobber'
[G1 Android Development] dm5530:
I'm using ADS_magpie and updated from 20110504 to 20110510 version a couple of days ago; did NOT flash gapps.

Seems to work alright but my take from your posts (and an edited post from AndDiSa) is that I should wipe the system then flash the 20110510 version and then your latest gapps. Do I understand correctly?

I'd be willing to try and report my results if you think it would help.

And thanks for ezGB. Much appreciated. Enjoy it MUCH better on my G1 than CM's Froyo.
[G1 Android Development] ezterry:
When you change gapps versions its best (if on an update anyway) to wipe system and then flash rom+apps (and re-add/remove any custom apks you may have on system via adb or in console if you have RA for the dream) .. if you do all of this before you boot again you don't need to wipe your userdata as its just a version update.

However wait for AndDiSa to rebuild with this commit:

https://github.com/ezterry/GB-build/commit/5c5acb1790674fd280ac2252893f473906618a7b

Then the new gapps will fully work.. well advanced new features of talk aside anyway
[G1 Android Development] AndDiSa:
Thank you very much ... don't know why I've always these problems with git / github. It happened to me already several times, that I am getting only a part of the commits when I am doing a repo sync. But the same is with Github: For example your latests changes, you committed to framework/base and device/htc/dream-sapphire. First I got only the changes from device/htc/dream-sapphire some hours later with a second repo sync there were also the other changes ...:confused:

Edit: synced again, merged, made a new full clean build ... but still the same :( Have to analyze it more deeply.
[G1 Android Development] Effdee:
if you are on a local branch that has uncommitted changes the repo won't sync those branches

make certain all of the branches you are on are committed or stashed before you repo sync
[G1 Android Development] AndDiSa:
I am almost sure that from that side there is no problem. Unfortunately this weekend I don't have much time, but I will have a look soon.
[G1 Android Development] AndDiSa:
I've checked everything again and again ... the new keys are included, the build is fine, there are no conflicts or other problems ... but still GoogleBackupTransport.app is not accepted. :confused:
[G1 Android Development] roalex:
You have to sign it with your platform key:
[G1 Android Development] AndDiSa:
... this would be one possibility, but I was expecting that when I configure ezTerry's platform key, the gapps would install wthout problems.
[G1 Android Development] roalex:
it just need uid:1000, if you read the logcat, its just this apk with issues from all the gapps.
[G1 Android Development] AndDiSa:
Yes, I know, it was always in this way, but Terry told me, that the reason for it was the wrong key ... so it was the same for you?
[G1 Android Development] roalex:
I think its signed with AOSP platform key when you change that you have to resign this also.
[G1 Android Development] ezterry:
The new gapps package I have on the second post will work with a rom with the new key.

AndDiSa:

Nandroid backup; wipe; then test.. its possible you just confused your package file between this and other tests..

Otherwise unzip your Settings.apk and look at the signature (open in hex or text editor META-INF/CERT.RSA)

if you see references to 'Toronto, Ontario' and 'ezGingerbread' its the new key.. if its 'Mountain View, California' and only references to android then its the old one.
[G1 Android Development] AndDiSa:
After wiping GoogleBackupTransport is recognized and installed, but I loose all my data and preferences ... is there a way to initialize the package list / package file newly without loosing all data?
[G1 Android Development] ezterry:
Well two ways usually:

> One remove GoogleBackupTransport from system and reboot.. the will hopefully clean the old version so if the then erase system, install the rom, then install new gapps it be corrected.

> Another idea is remove the entries manually from /data/system/packages* (one is a text file.. one is a xml) .. if you do this run fixpermissions after boot.

I know originally my version upgraded cleanly for me but only when all the keys changed at the same time.
[G1 Android Development] newellj79:
Very disappointed to report that after flashing ads 5/17 I was stuck at splash screen. Back to 5/10 for now. Anyone else with this problem? Md5 checked out.
[G1 Android Development] creezalird:
Nope, running 1705 smoothly, wipe clean install and flash the new gapps
[G1 Android Development] newellj79:
Yah, i don't want to do a full wipe unless absolutely necassary. Ill play around more tomorrow. Thanks though.
[G1 Android Development] ezterry:
Well try the usual then:

1) 'fastboot erase system' or format system in clockwork recovery (this just wipes the system partition not your data)

2) also (format/wipe cache) [while we are poking usually not needed]

3) clear dalvik-cache

4) install rom + new gapps and take a log cat in case problems happen again.

When not changing gapps this is less of an issue.. but if the rom backs up gapps and you are changing the gapps package its cleanest to wipe system first..

The whole thing with GoogleBackupTransport won't stop the rom from booting.. just the one app from functioning .. You can always check if its working or not from the settings->Application->All Applications menu, it won't be listed if the signatures are confused.
[G1 Android Development] AndDiSa:
Unfortunately neither of the two solutions worked for me ... I tried also to edit these files, but either the key could not be found, or it reported an invalid signature. Seems to me, that I really need to wipe :(
[G1 Android Development] jdb78:
It doesn't seem to work using a Dream yet. ezterry and creezalird tried it already I guess. But that video chat is way the least important issue here I'd say. At the moment AnDiSa has problems with the keys and ezterry is still trying to figure out the best way of memory handling - besides other important stuff as you can read within the github of ezterry or AnDiSa.
[G1 Android Development] AndDiSa:
The problems with the keys I could solve in the meantime, but I had to delete /data/system/packages* and /data/data/com.android.providers/settings/databases/settings.db. After re-booting, the packages were installed newly and also GoogleBackupTransport was accepted.

Unfortunately almost all app did get a new id, so I needed to run fix_permissions, but even after that, almost all apps were force closing.

Another pm install -r for almost all apps solved these problems, so that finally I only had to re-sync calendar and contacts ...

In short: a wipe probably would have been more easy ;)

Btw: If you want to update to ADS_20110517 you should be aware that probably a wipe is needed or

- fastboot erase system

- flash rom

- flash new gapps immediately

- reboot
[G1 Android Development] jdb78:
And which minfree settings would you suggest at the moment? I just need a reliable phone, hence I still use 20110416-1. I'll try to get a 2nd G1 to play with... ;)
[G1 Android Development] hrk:
The new-new settings (the ones currently in the ROM) seem good for me. More or less like the old values, way more responsive than the prevoiusly-new ones.

If you are not confused yet, I'll try being more confusing.

By the way, I updated ADS to *10 and then *17 and everything seemed to install/work. GoogleBackupTransport is listed in the installed apps, I got this is the way to check if everything worked fine.
[G1 Android Development] jdb78:
I agree, the *17 is more responsive than i.e. 0504 or 0510. It seems to be usable. Nevertheless it's still not as responsive as the 0416-1 build. I realized that the latest build does only use zRam, no CompCache. Is this correct?

cat /proc/swaps
Filename Type Size Used Priority
/dev/block/zram0 partition 8188 8184 -1

CC is disabled by design, I didn't change this setting.

I installed the 0510 without wiping or system erasing over the 0416-1, installed gapps, rebootet, let the phone settle down, flash 0517, flash gapps again, rebootet and everything seems to be ok so far. My SU lost all it's apps that were already allowed to su but thats not a problem. No further issue up to now but the responsiveness. I could not answer the first incoming phone call for example because the phone did just not react to the buttons. When it startet showing the caller ID and reacting to the button the caller was diverted to the mailbox already. The next call came in ok.
[G1 Android Development] ezterry:
zram *is* compcache..

I've been seeing very odd behavior with memory usage.

1) Maps is horrible.. its just not playing by Googles own recommendations.. and thus causing problem on a low ram device: If like me you only use it on rare occasions.. maybe mapquests app will work better for you.. as it will not run any background process... and maps sometimes seems to have 3 seperate processes running in the background even with latitude disabled. (uninstall maps if you try this .. as otherwise it will still spawn in the background)

2) amount of compcache.. default is 8.. seems good for lighter users.. but may not match your case.. large improvement for me at 24mb (at root command line you can set a custom value with 'setprop persist.zram.size 24' for example.. then reboot... you can double check in the settings->Applications menu or with 'getprop persist.zram.size' Turning compcache off may also speed things up but leaves less room for apps that need ram. The more things you want to run at the same time the more you need.. since otherwise you will get delays and slowdowns as services are killed/spawned

3) JIT - If balanced right above it will be very smooth as is .. if the number of active services keeps pushing eachother out it will act slower. Turning off jit may make the phone more forgiving to recalibration. But you will likely loose some batter life and be running slower once the app is loaded.

4) If you are one of those who think the phone is slow because you feel you are waiting for a transition animation you can still disable them or set them to fast in Spare Parts

5) ditch the faceboot widget [if in use].. particularly if it seems to fail to keep up to date (by all means keep facebook app/sync.. and if you have problems with the latest market one uninstall and flash the one from the op.. [the newest versions seems to be causing some people problems on all phones]
[G1 Android Development] creezalird:
speaking about maps, yesterday and before this i always got reboot from running gps navigation such as copilot, i assumed this is due to too low memory right? or the gps is a bit buggy? trying to get a logcat, but this thing seemed to be quite random