yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] radioactiveman:
todays andisa built give me this

W/libdbus ( 232): Failed to start message bus: Error in file /etc/dbus.conf, line 1, column 0: syntax error

unfortunately reproducible but i guess it is just a bad flash. could it be my flash is broken? I'm getting the weirdest errors again and again. i think the last version that worked for me is from march or april.
[G1 Android Development] jdb78:
I still use the ADS Magpie from 20110416, works best for me up to now. I use it as a daily ROM and I'm almost absolutely happy with it. My Dream never worked better with any other ROM. Why don't you try this version?

I also had issues with my sd-card once, are u sure ur card is still o.k.?
[G1 Android Development] arkara:
sometimes my phone crashes, when i try to transfer files through usb.
[G1 Android Development] ezterry:
If you get the chance if you can help us with the following we will be able to do more to help you in return:

Regarding the issue at hand: I know some people have had odd filesystem crashes .. some have even been so kind as to provide kmsg or last_kmsg output so I could attempt to look closer.. review between code bases noted a missing patch that i introduced in the kernel update I posted a bit back (link is in the second post in the notes of the latest build) but that patch relating filesystem access may or may not work or be relevant to the issue.

Thus my questions on this mater are as follows (to anyone having the issue):

1) is it (on the most recent build + kernel update) still happening

2) every time or sometimes; any theory to when it happens if not every time.

3) OS of the computer aiding the crash since its a USB mount.

4) did the crash happen before/after it appeared to mount on the computer

5) link to your last_kmsg of the crash so I can try to see what happened

6) if possible a logcat up to the time a logcat no longer worked because of the crash.. this is easier when the crash is always reproducible .. and harder if random .. so its understood if you can't find it.

We can't promise and instant response but with that list we have the tools to continue investigating
[G1 Android Development] jdb78:
Terry: I assume that testing the latest ADS_Magpie will help, too? So I'll install that right away (leaving my "safe and smooth" 20110416 install) and try to provoke the crash if possible.
[G1 Android Development] AndDiSa:
Latest ADS_Magpie has still the 1.0 kernel included, so you need to flash the kernel update from Terry on top of it to be on the "lastest" configuration.
[G1 Android Development] jdb78:
Ok, thx AndDiSa, I flashed ADS_magpie-20110504-signed.zip and the 1.1 Kernel on top. I'll let the system "burn in" for a while to let it determine the memory handling and stuff. Feels a bit sluggish like you already mentioned (I use your default values in setSwapSettings.sh) and not as smooth as the build from 20110416 but still o.k. I'll test it during the day.

I already recognized one advantage, though. Maps used to crash with no error message when I planned a route. With the new ROM/Kernel Maps took ages to start and said "not responding - kill wait report", where I said "wait" every time. And when it finally was started I could plan a route without a crash. Progress! :)

I can't thank you guys enough for the great work you are doing for the "grandpa" of Google phones. ;)
[G1 Android Development] hrk:
I'm testing the latest ADS + ezGB_1.1 kernel in order to understand if the new tree+fixes+minfree+memory help solve the "Lost SMS"-bug.

I'm using default CC, JIT on, no swap, CPU@614-128+interactive and the phone is still really, really, slow with an uptime of 14 hours. When I used the "echo numbers > /sys/.../minfree" using the old values, the phone became much smoother, but I am not doing it again since I'd like to test the current code "as it is from the tree". But... man, it's so painful. This feels like the first time I tried COS :) and I immediately reverted back to ADS.

I'd like to think that 14 hours is more than enough time for "memory settings to settle", and I can see in the "Running Services" that I have 30MB of free RAM (make it 36 MB now, GMail was killed in the meantime).

Since nobody else is complaining about this (except for jdb78) I wonder if it could be something wrong on my part. What could I test/report to understand if it's a bad setting on my part?
[G1 Android Development] roalex:
One thing's for sure, do not touch interactive guv ;)
[G1 Android Development] hrk:
Do you mean it as "Never change it" or "Never use it"? If you're against it, would you clarify why? I've felt (I know, feeling is not a benchmark) it made my phone snappier than ondemand or conservative. :)
[G1 Android Development] roalex:
It's faulty atm, sometimes it works and then the phone is crashing, sometimes it does NOT and its just like on demand !
[G1 Android Development] muldy:
Anyone having troubles sending MMS? :/
[G1 Android Development] arkara:
1)I had this on the kernel included with 20110502-CheckPoint by default. I did not upgrade for the camera crash since i did not have any camera problems.

2)Not every time. I think it happens the first time u plug in the phone. If you disc and reconnect it goes ok

3)Arch Linux using KDE

4)Before

5)My lasts_kmsg(not sure if it's the right one):

http://pastebin.com/4gDT6Bkt

6) I remember that i had no logcat

if you need anything else tell me.
[G1 Android Development] ezterry:
Just double check this value in settings if it says 8 you match the default.. if it says 18 you match the 4/25 build (if the roms default is 8 just uncheck+recheck+reboot)
[G1 Android Development] hrk:
It was 18. It's now rebooting, I really hope it works now. :)

Changing subject, I hope this weekend I'll get some time to fix the Gallery+Gallery3D DCIM incompliance. When I'm done, would you merge the changes? Should I push them to AOSP?
[G1 Android Development] ezterry:
I make no such promise..

I can't say I've yet to experience much benifit of DCIM .. in my experience the photos load on the camera the media is in.. the media while in theory could never changes cameras.. and if I put the media in a computer its just oddly named folders to open to get to the image files.

This means part of me says forget DCIM and just point it at /sdcard/camera/

But if you fix the standard in a way that fully matches the warnings on the bug report and its clean I will consider it.
[G1 Android Development] hrk:
It won't be "clean" -at least not the way I'd like it to be- 'cause I'm trying to make a patch which touches the original sources the very least possible (it currently changes around 6-8 lines in the original Camera code and adds a new class which does all the DCIM naming/work).
[G1 Android Development] jdb78:
May I ask which the "old settings" were? I'd like to make my phone smoother ;)

I found three versions of the minfree settings and I'm not quite sure, what they are for.
[G1 Android Development] ezterry:
The old settings are not optimal with 8mb comp cache.. just disable the comp cache if its still to slow for you at 8mb cc.. if you have >8mb cc however as I said below reduce it.

(Background tasks will take a high hit with either the old settings or no compche but that is what is being ballanced here .. how to keep any services and mayby the last task in ram used by the user without waiting forever for items to swap in/out)
[G1 Android Development] jdb78:
The "Disable 8Mb CompCache" option is ticked so I think I only use zRAM at the moment.

I recognized that opening apps take a long time. I received several messages recently and first Ghostly SMS popped up and approx. 10 secs. later the MMS/SMS app came up with the message. The UI is not very responsive at all. Sometimes I have to touch buttons several times before they realize they were pushed. But like I said, Maps now plans routes without crashing, I couldn't do that before. So I'm waiting for you experts to find the perfect balance :)

~ # free
free
total used free shared buffers
Mem: 112516 110684 1832 0 128
Swap: 8188 8184 4
Total: 120704 118868 1836
~ # cat /proc/swaps
cat /proc/swaps
Filename Type Size Used Priority
/dev/block/zram0 partition 8188 8180 -1

EDIT: another thing: I used ADB a lot today and did not reboot the phone. I didn't notice a heavy battery drain at all. All is normal (when using my phone a lot battery is approx. at 50-60% in the night when I go to bed, so in hours ~16h. When I don't use it a lot I possibly still got 65%. I still use the first battery that came with that phone)
[G1 Android Development] creezalird:
Andisa, just want to say that in your latest ads_magpie 0405... in init.d, I think there is a double copy of zram script, which I assumed because the old ones had a wrong name.

No biggie actually, i just delete from that manually and resign.
[G1 Android Development] hrk:
My experience, exactly. :)

Hmm... am I right in translating this into:

CC=18% + old minfree settings (2048,...) = Prioritize activities

CC=8% + new minfree settings (256,...) = Prioritize background services

?
[G1 Android Development] ezterry:
Pre my april 25 release I didn't have cc in the rom by default it was added to improve background task performance. (As it seems to help keep home in ram as well as other tasks.. but at some transition time costs if an app needs to be removed or added to comp cache (thus the change from 18 to 8MB to reduce the memory in this state.

Now remember all of the minfree values are in 4k blocks so:

2048 = 8MB must be free all times

256 = 1MB must be free all times..

With that ratio and the overhead of compcache .. if you want to keep 8M compcache but increase the min value to 8.. it seems wise just to disable the compcache.

Of course I am hearing and need to test some more values in between.. reports also indicate pushing higher some of the other values may help.
[G1 Android Development] AndDiSa:
Thanks for the hint. There should not be any problem, even with both scripts inside. I think it's only due to the fact that I didn't clean the output directory completely before starting the new build.
[G1 Android Development] farmatito:
I/ActivityManager( 190): Starting: Intent { act=android.intent.action.MAIN cmp=com.android.settings/.battery_history.BatteryHistory } from pid 973
E/AndroidRuntime( 973): FATAL EXCEPTION: main
E/AndroidRuntime( 973): android.content.ActivityNotFoundException: Unable to find explicit activity class {com.android.settings/com.android.settings.battery_history.BatteryHistory}; have you declared this activity in your AndroidManifest.xml?

I'm seeing a crash in SpareParts app when trying to check Battery usage history. Let me know if more info is needed.

It is on self compiled ezGinger. I'm repo syncing, cleaning and recompiling right now to see if it goes away. Also

downloaded SpareParts from Market crash so there must be something faulty in my framework.... I suppose.

UPDATE:

there is an issue for that at http://code.google.com/p/android/issues/detail?id=14898

and it seems to persist in 2.3.4 and a patch:

$ git diff

diff --git a/apps/SpareParts/res/xml/spare_parts.xml b/apps/SpareParts/res/xml/spare_parts.xml

index 524092e..0d06e26 100644

--- a/apps/SpareParts/res/xml/spare_parts.xml

+++ b/apps/SpareParts/res/xml/spare_parts.xml

@@ -26,7 +26,7 @@

android:summary="@string/summary_battery_history">

<intent android:action="android.intent.action.MAIN"

android:targetPackage="com.android.settings"

- android:targetClass="com.android.settings.battery_history.BatteryHistory" />

+ android:targetClass="com.android.settings.fuelgauge.PowerUsageSummary" />

</PreferenceScreen>

<PreferenceScreen android:key="battery_information_settings"
[G1 Android Development] AndDiSa:
I do not have any problems with ADS_Magpie from 20110504. What version do you have installed?
[G1 Android Development] ezterry:
I know this was mentioned before.. but Settings.apk as of gingerbread removed that battery history screen..

The problem is unlike the *#*#INFO#*#* menu .. SpareParts is not part of settings.. but a bunch of hackish links into settings

(edit: ah that is where that patch went .. I saw it a while back but was probably drowning in kernel code at the time)
[G1 Android Development] arkara:
Can we use the

"Settings --> About Phone --> System updates"?
[G1 Android Development] danielgek:
Hello, I'm having some problems

I have a htc magic 32A and already compiled several times however when I flash the rom it does not start up

I turn on logcat but keeps saying "waiting for device"

could someone help me???

ps:"i see auto kernel working when i'm flashing"
[G1 Android Development] ibraheeemz:
have you completely wiped before flashing? and how much you wait ???
[G1 Android Development] danielgek:
yes i have wiped everithing

i wait dust a little bit and then the device reboots in recovery

:confused:
[G1 Android Development] ezterry:
WHat radio + SPL?

Did you try the official binaries or only your own build?

Did you modify any code or build your own kernel if its your own build.
[G1 Android Development] danielgek:
SPL 1.33.2010 and the old radio(3.22)

yes i have tryed the official binaries and they have worked

and i haven't modified any file and build kernel
[G1 Android Development] ezterry:
I'd make sure nothing strange is happening to the kernel in your build.. your description sounds like a bad or missing kernel.

Unfortunately I don't have much to go on unless it was a bad copy. (and I did have one of those in my fonts.sqf today.. confused me to no end.. many skia errors.. And i'm thinking I did nothing to skia)
[G1 Android Development] arkara:
When i plug in my handsfree i get sound from the headphones but the phone does not have a headphone icon on the notification bar and also does not stop the playback from the speakers.
[G1 Android Development] ezterry:
Ask google if that is a bug or feature.. from what I gather it s a feature
[G1 Android Development] arkara:
I don't get it. Could you please explain?
[G1 Android Development] ezterry:
I don't think the headset notification icon has been in AOSP since donut

(and if the speakers are still playing I recommend you check your headset.. functionally its working fine here)
[G1 Android Development] arkara:
That's kinda ridiculous. Why did it bother them to have a headphones notification?

Checked it again, played fine this time. Maybe i did not put it all the way in. :confused:
[G1 Android Development] danielgek:
so what should i do???
[G1 Android Development] hrk:
A minor/cosmetic/kang issue: the info screen reports version 2.3.4-ez, but build GRI40 in place of GRJ22.
[G1 Android Development] ezterry:
Um..

BUILD ID = 'GINGERBREAD' unless someone is changing it on another build.

GRI40/GRJ22 seems related to gapp packages and google builds.. since the base build has no gapps and gapps only cares about the forged fingerprint being on a whitelist i can't say I care much

If you are seeing GRI40/GRJ22 in a fingerprint unless you dig up another whitelisted fingerprint leave alone.. if its in a gapp version it is probably true.. and if its somewhere else its not my codebase
[G1 Android Development] roalex:
something like this, the GRJ22 is the "code" of 2.3.4_r1
[G1 Android Development] ezterry:
Um ,, but this isn not following tag 2.3.4_r1 aka google build GRJ22.

Its following the branch gingerbread aka GINGERBREAD

Thus the ID by default in ezGingerbread is GINGERBREAD.. the only thing I override is the fingerprint and only because if its not on a google whitelist we don't see "Protected" apps in market.
[G1 Android Development] farmatito:
ezterry could you please apply this patch to your tree,

it fixes a race condition that prevents the sdcard fat

partition beeing mounted correctly on boot.

It is triggered more easily when using BFS kernels

but could happen also with non BFS kernels.

From 030bc88b4c09a41b0d7dbe249aec55f33d6b8b8a Mon Sep 17 00:00:00 2001

From: anga <anga@syntronic.com>

Date: Tue, 1 Feb 2011 14:10:25 +0100

Subject: [PATCH] Fix a race condition in NativeDaemonConnector

MIME-Version: 1.0

Content-Type: text/plain; charset=UTF-8

Content-Transfer-Encoding: 8bit

Fixes a race between the onDaemonConnected callback and setting the

mOutputStream in NativeDaemonConnector.

MountService connects to vold using the NativeDaemonConnector.

Throws a “NativeDaemonConnectorException: No output stream!”

when the onDaemonConnected callback in MountService calls the doListCommand.

Change-Id: Ib895bab37f7df680e4362df6366198c0a673c5e9

---

.../com/android/server/NativeDaemonConnector.java | 3 ++-

1 files changed, 2 insertions(+), 1 deletions(-)

diff --git a/services/java/com/android/server/NativeDaemonConnector.java b/services/java/com/android/server/NativeDaemonConnector.java

index 7b68d68..c0c6c36 100644

--- a/services/java/com/android/server/NativeDaemonConnector.java

+++ b/services/java/com/android/server/NativeDaemonConnector.java

@@ -97,11 +97,12 @@ final class NativeDaemonConnector implements Runnable {

LocalSocketAddress.Namespace.RESERVED);

socket.connect(address);

- mCallbacks.onDaemonConnected();

InputStream inputStream = socket.getInputStream();

mOutputStream = socket.getOutputStream();

+ mCallbacks.onDaemonConnected();

+

byte[] buffer = new byte[BUFFER_SIZE];

int start = 0;

--

1.7.4.1
[G1 Android Development] ezterry:
Some things to double check but most likely I'll drop it into my next build. (Today or tomorrow as I have some security patches to push to public binaries.. most already in git)
[G1 Android Development] ezterry:
Alpha build 20110509-1

Note the security fix is blocking the platform key from being used outside system, The new platform key is just an extra precaution, it is still public so can be forged like any test key, however this will mean if any additional future attack is found ezGingerbread (and derivative roms) will need to be targeted specifically, and not with the same file as cyanogen/aosp..

However you will need to use the updated gapps, and any custom made gapps package will require Google Backup Transport to be re-signed with the ezGingerbread platform key. (Otherwise nothing special about the gapps package [updated apps aside].)
[G1 Android Development] ibraheeemz:
with every alpha/binary release excitement of final version is increasing!! good work. I was thinking if it can be merged with CyanogenMod so to have a CM7 for G1, but you must be having some better ideas than that!! :-)
[G1 Android Development] farmatito:
Is there any caveats if we build from source? or is this only for the precompiled binaries?

If i understand it correctly the updated gapps package is mandatory only

due to the re-signed Google Backup Transport?

Just to make our lifes easier what is the path to ezGingerbread platform key?

TIA
[G1 Android Development] ezterry:
Correct all you need to do is either pull the new gapps package Google Backup Transport into your custom gapps package, or sign the one in your package with the platform key.

All the keys for an AOSP build are in build/target/product/security I just dropped the precious google created test platform key into a self created test platform key.

(of course the updated gapps package is an update but I don't really want to stop anyone from making a "better" package

Edit: fyi building from source produces the same binary with the same key. Thus anthing needing to be signed by the platform key must use the ezGingerbread platform
[G1 Android Development] arkara:
Can we update both the rom and the apps without wipe?

EDIT

Also, can we get updates for the gapps from the market?
[G1 Android Development] ezterry:
Yes, no wipe from earlier versions of ezGingerbread will work fine.

Um nothing needs an update yet from the apps in the new gapps package, its still a minimal set so gmail, maps, ect are to be downloaded from market.

If an update to the apps appears in market it can be updated as usual.

From an end user perspective the securitiy updates ought to be 99% transparent..
[G1 Android Development] newellj79:
After lots of searching I wasn't really able to find any themes to use with the ads-magpie. ThdDude has been kind enough to hook his theme up for me to use with ads for the last few nightlies. He said to share. I hope this isn't against forum rules but here is a link to download the theme. Flash in recovery as usual. https://www.dropbox.com/s/pgvjhniho8k3wno
[G1 Android Development] sisterchick:
Just installed latest ezGingerbread and I am truly surprised by how well it is running and how much available RAM I still have. Great job and thank you.

I'm close to finishing a batch script that will take much of the suffering out of porting Froyo metamorphs to Gingerbread.
[G1 Android Development] jubeh:
Is there any way to view the full commit history on Github? I'm building 2.3.4 for Dream, but I'm running into many problems. I'd like to port some of the fixes on your repo to my platform (it's personal use), and following an actual timeline helps me better understand the commits rather than scavenging through all the projects to find the information I'm interested on.

Mostly, I'm trying to make as pure an AOSP build as possible with the only changes being related to making most Dream hardware as possible work and make all Google App features work too (on froyo I'm having trouble getting location to work too).
[G1 Android Development] ezterry:
The history button at the root of a git tree will show the log for the entire git repo; the history button on a subdir shows for the subtree, and a file for the files.

The link is the top right of the content (directory listing or source code)

When corss referencing I usually use a combo of browsing git and using 'git log' and add the alternative git repo as a remote to my local git instance.

This way I can also diff my version with the alternitives; and blame the remote version to find that (missing from my version) patch I'm looking at in the diff.. and of course cherry-pick to drop the patch into my working tree retaining the original commits metadata.
[G1 Android Development] ibraheeemz:
Of course EZ's work is great!! I was wondering why people are still using FROYO on their tiny G1's,

Sisterchick I have been using your themes for biffmodl! please do some work for this build as well!! will be greatfull.
[G1 Android Development] ibraheeemz:
will love to use themes, but can we have some screen shot first???
[G1 Android Development] hrk:
Out of ignorance... I've been pushing my own Camera.apk for the past two weeks, so that I can test my changes. Do I need to repackage it with the new keys after I flash the new ROM or will it work?

I know that I can just give it a try, but I'd rather avoid using NANDROID to perform the test. I can wait another couple of days before flashing if repackaging is needed (I won't be able to repackage earlier than that).
[G1 Android Development] ezterry:
Just sync and rebuild

'repo sync -j 10'

'make Camera'

Its best to develop built in apps from the ezgb source tree.. and if you keep the code in sync with mine thus changes. Including keys.
[G1 Android Development] hrk:
... keep my...?
[G1 Android Development] ezterry:
Tapatalk's submit button is sometimes a fail... you edit the text or choose a word, brush the screen near it and off the message goes ready or not..
[G1 Android Development] hrk:
That's what I do. :) Ok, this means I'll have to wait a couple of days. Thanks!