Systematic cleanup of errors in 2.1Vanilla

[Guest gusthy]

I started checking logcat systematically for a few days in Vanilla 2.1 upd6.

It seems that there are issues that are not (only) memory-related, and probably fixable.

One is the change of sqlite3 binary to G1 Eclair's version. I did it, currently I have an uptime of 7 hours, we shall see...

Other is the acore within gmail setup. This one is a security issue, there is a java exception behind it, it does not seem to be hard to fix.

Third one is an error at startup, it complains about the content of framework.apk, it says there is no framework.dex in it or something like this.

Fourth is that no group / passwd file exist, and some init scripts miss users / groups.

There are a few more typical errors too in logcat.

You guys what do you think about this track of having a more stable 2.1?

(PS: currently I dont use AutoKiller, since it drastically changes the phone's behaviour. I think, better first to fix the rom itself, AutoKiller comes up after. btw, it is generally not slow without it)

Edited May 23, 2010 by gusthy

[Guest bounty123]

Very good idea, I encourage you to keep working on this :rolleyes: Who knows if there will even be an official update... Maybe this will be our only chance to have a decent fresh rom on our phones.

[Guest gusthy]

Very good idea, I encourage you to keep working on this :rolleyes: Who knows if there will even be an official update... Maybe this will be our only chance to have a decent fresh rom on our phones.

Thank you, i mean köszi a biztatást :D

I think I will make a build in 48 hours.

[Guest rulerofkaos]

WPA Enterprise isn't working aswell, don't think it is a memory issue

[Guest Josh04]

Hey, definitely some good catches then. My phone is always on best behaviour when I've got logcat on, then reboots the rest of the time : /

[Guest Sh4d0w940]

You guys what do you think about this track of having a more stable 2.1?

I think it's a good start if Huawei doesn't release the final rom (or if they are also reading this topic :rolleyes:)

Sh4d0w940

[Guest jonathonf]

One is the change of sqlite3 binary to G1 Eclair's version. I did it, currently I have an uptime of 7 hours, we shall see...

How have you done this? I've downloaded a Cyanogenmod ROM and the only sqlite file I can find is /system/lib/libsqlite.so

[Guest Basher52]

I started checking logcat systematically for a few days in Vanilla 2.1 upd6.

It seems that there are issues that are not (only) memory-related, and probably fixable.

One is the change of sqlite3 binary to G1 Eclair's version. I did it, currently I have an uptime of 7 hours, we shall see...

Other is the acore within gmail setup. This one is a security issue, there is a java exception behind it, it does not seem to be hard to fix.

Third one is an error at startup, it complains about the content of framework.apk, it says there is no framework.dex in it or something like this.

Fourth is that no group / passwd file exist, and some init scripts miss users / groups.

There are a few more typical errors too in logcat.

You guys what do you think about this track of having a more stable 2.1?

(PS: currently I dont use AutoKiller, since it drastically changes the phone's behaviour. I think, better first to fix the rom itself, AutoKiller comes up after. btw, it is generally not slow without it)

Great work at all. As we all just got the same aims, we should focus on the beginning of your work.

My questions:

How do i log my stystem to file? Which software do you use?

What about exchanging the defective .apk with older/newer/other one? Any results?

[Guest gusthy]

How have you done this? I've downloaded a Cyanogenmod ROM and the only sqlite file I can find is /system/lib/libsqlite.so

and /system/xbin/sqlite3

i dunno if it is the same g1 eclair, its name is Eclair_v2.1-v1.5.zip, filesize 74249516 bytes

* Edit: this is the one I used:

http://db.androidspin.com/androidspin_rele...p?releaseid=145

Edited May 23, 2010 by gusthy

[Guest gusthy]

WPA Enterprise isn't working aswell, don't think it is a memory issue

thx, goes to todo

[Guest gusthy]

Great work at all. As we all just got the same aims, we should focus on the beginning of your work.

My questions:

How do i log my stystem to file? Which software do you use?

What about exchanging the defective .apk with older/newer/other one? Any results?

adb logcat V >logcat.txt

[Guest jonathonf]

Ah ha! Found sqlite3 in your linked download in /system/xbin/

OK, I did an

adb push libsqlite.so /system/lib/

adb push sqlite3 /system/bin/ <-- this bit is not be necessary

adb push sqlite3 /system/xbin/

(probably could have made a symlink instead but this was a quick test.)

Phone definitely seems quicker, e.g. when pressing menu when the screen is off. Last.fm loads and plays almost instantly now. This looks like being a must-have fix.

Edited May 23, 2010 by jonathonf

[Guest gusthy]

Ah ha! Found sqlite3 in your linked download in /system/xbin/

OK, I did an

adb push libsqlite.so /system/lib/

adb push sqlite3 /system/bin/

adb push sqlite3 /system/xbin/

(probably could have made a symlink instead but this was a quick test.)

Phone definitely seems quicker, e.g. when pressing menu when the screen is off. Last.fm loads and plays almost instantly now. This looks like being a must-have fix.

Why did you push it into /system/bin too?

[Guest gusthy]

DownloadProvider.apk seemed to crash constantly too (this is why Market worked strangely), so i pushed it too:

adb remount

adb shell

# rm /system/app/DownloadProvider.odex

# exit

adb push data/app_s/DownloadProvider.apk /system/app/

And Market seems to work correctly.

[Guest jonathonf]

Why did you push it into /system/bin too?

That's where you said it was. :rolleyes:

and /system/bin/sqlite3

So I can delete it from /system/bin ? I'll give it a go.

Edited May 23, 2010 by jonathonf

[Guest gusthy]

That's where you said it was. :D

So I can delete it from /system/bin ?

Oh, sorry, it was a typo, it is in xbin :rolleyes:

So yes, you can delete. I will fix the comment above now.

[Guest robertopero]

Very good idea! Keep up the good work, we'll wait the first release! :rolleyes:

[Guest thisweb]

DownloadProvider.apk seemed to crash constantly too (this is why Market worked strangely), so i pushed it too:

adb remount

adb shell

# rm /system/app/DownloadProvider.odex

# exit

adb push data/app_s/DownloadProvider.apk /system/app/

And Market seems to work correctly.

These fixes are looking promising. Well done. Any chance of being able to create a rom with this and the sqlite3 fix?

Is it still running without reboot?

[Guest gusthy]

These fixes are looking promising. Well done. Any chance of being able to create a rom with this and the sqlite3 fix?

Is it still running without reboot?

yes, probably tomorrow - until that lets collect fixes.

dunno about reboots, i had to do many test reboots.

meanwhile i replaced picotts, since it also crashes a lot.

[Guest gsk]

I'v done these two updates.

I then rebooted and get the following Logcat Errors (attachment).

Hopefully might help a little.

log.txt

Edited May 23, 2010 by gsk

[Guest gusthy]

I'v done these two updates.

I then rebooted and get the following Logcat Errors (attachment).

Hopefully might help a little.

thx, looks interesting!!

otherwise did the patches work?

[Guest Simon O]

These fixes are looking promising. Well done. Any chance of being able to create a rom with this and the sqlite3 fix?

Is it still running without reboot?

It's easy to create the rom. Unzip the original rom, make the changes, zip it up again and sign it.

[Guest Josh04]

I've been following these, they seem to be doing good.

[Guest Simon O]

I'v done these two updates.

I then rebooted and get the following Logcat Errors (attachment).

Hopefully might help a little.

The biggest issue in that log file is with WPA_Supplicant. I can see that the wifi driver loads and starts the supplicant service but it's unable to connect to eth0.

I'm not going to pretend I know how to fix this, but I bet one of you guys do.

[Guest gusthy]

The biggest issue in that log file is with WPA_Supplicant. I can see that the wifi driver loads and starts the supplicant service but it's unable to connect to eth0.

I'm not going to pretend I know how to fix this, but I bet one of you guys do.

we will do our best, but now i dont use wifi.

strange, i got a reboot.

my long rebootless period was when I only updated sqlite3 and used original libsqlite.so.

now i will recheck it. unfortunately it takes time.

Edited May 23, 2010 by gusthy