yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] Firerat:
Well, it actually took a couple of hours to compile the damn thing :D

not flashed it yet, but had a peak

need to sort out some stuff with the init.rc ( mount points and init.d )

I think squishing xbin, and kernel modules would be a good idea

atm, I've not got system's dalvik-cache going to /cache

( useful for sapphire, no good for g1, redundant if you use customMTD )

I'll add that when I figure out what happened to the get_property

a2sdext _should_ work ( but no UI yet )

but tbh, as I haven't actually flashed it , I'm being optimistic

I'll do an AutoKernel for those that haven't got round to doing 2708 and 32As

( If I'm all inspired I see about adding it to the build system .. but may just use my dirty little scripts to shoehorn in for now )

anyone fancy doing a bootanimation?

( I don't mean kang one, make a new one from scratch ;) )

Wallpapers ?

( again no Kangs )

RingTones?

( " " " )

Themes?

if themes a just png based ( i.e. no messing with classes.dex ) , I have a script which can make them into a flashable zip ( smaller and _should_ be compatible with future builds )

errm, other stuff..

I'll try and get something for you to all flash before the end of the year ( GMT :P )
[G1 Android Development] tnpapadakos:
i got some wallpapers
[G1 Android Development] irisiris:
too many roms showed up as CM7 prefix.. which seems to have caused Confusion if its CM released or not.

for the time being it seems only stable beta will be first released by CM when made but till then anyone other than CM team will not have option to release unapproved version from the CM code base. ?
[G1 Android Development] tnpapadakos:
thanks, i needed a translation
[G1 Android Development] MrFrankfromCM:
@tnpapadakos Sweet wallpapers! Thanks!
[G1 Android Development] solca:
I tried both ezterry's 12-22-2010 version and your's 12-29-2010 GB colorized version on both my G1 and MT3G (32b) and this GB repo rocks!

It's just me or this GB ROMs are much faster than both CM6 and official MT3G FRG83D?

The only issue with the colorized version is that it needs a working DATA, ezterry's binaries boots fine with a wiped DATA, I realized that if I wipe everything then I need to boot ezterry's first, then just wipe system to flash the colorized version.

Just FYI GPS and Market doesn't work on both G1 and MT3G. WiFi doesn't work on G1 only. Everything else works great!

My humble recipe for tnp's colorized version:

1. Boot to recovery.

2. Wipe everything (via superwipe as stated on first post).

3.

Turn off

and boot again to recovery.

4. Flash latest ezterry's ROM from first post.

5. Boot normally and setup your preferences (like WiFi, etc).

6. Boot to recovery.

7. Flash tnp's wipe system and cache script.

8. Flash tnp's colorized ROM.

9. Flash tnp's update.

10. Flash latest pershoot's kernel.

11. Boot normally and Enjoy!

(sorry can't post links yet)

Many thanks to ezterry, tnp, etc.! great work!
[G1 Android Development] fineguy1:
Thanks for that, Solca.

I flash it finally, and everything's fine except for gmail that fc. GPS works great.

Thanks everyone for a job well done, and Happy New year from Bangkok.
[G1 Android Development] Firerat:
it will be just labelled kang unless you add to the buildspec
[G1 Android Development] mikesheadroom:
This is what finally allowed me to install successfully. I had wiped /data out of a need for completeness and was unable to install without bootloops.

I have 2.2.7 Market working after pushing the apk from here:

http://xdaforums.com/showthread.php?t=869652

Thanks for everyone's efforts on this project!

I'm really looking forward to some EZ-Rat Ginger-Pie :p
[G1 Android Development] jcarrz1:
yeah, they should fix this.
[G1 Android Development] lolmensch:
hm did i miss sth? :P

jk. waiting patiently =)
[G1 Android Development] djmeistro:
Error status 7...I know this has to do with my spoofed spl 13d...what should I do?
[G1 Android Development] lolmensch:
dont spoof it.

install new radio/spl

flash rom + pershoots 2708/ezterrys kernel

should work then
[G1 Android Development] Ohsaka:
Links add.
[G1 Android Development] giorgio130:
I'm trying to compile gingerbread for another device similar to g1, and I'm getting this:

I/DEBUG ( 75): pid: 122, tid: 122 >>> /system/bin/mediaserver <<<
I/DEBUG ( 75): signal 7 (SIGBUS), code 128 (?), fault addr 00000000
I/DEBUG ( 75): r0 00000001 r1 0000aebd r2 73622a85 r3 0000aeb9
I/DEBUG ( 75): r4 00000001 r5 0000aebd r6 bebe2bb0 r7 00000000
I/DEBUG ( 75): r8 00000000 r9 00000000 10 00000000 fp 00000000
I/DEBUG ( 75): ip 80328c98 sp bebe2b50 lr 802049f4 pc 802049f4 cpsr 00000010
I/DEBUG ( 75): #00 pc 000049f4 /system/lib/libcutils.so
I/DEBUG ( 75): #01 pc 00015b1e /system/lib/libutils.so
I/DEBUG ( 75): #02 pc 00015b70 /system/lib/libutils.so
I/DEBUG ( 75): #03 pc 0001ebac /system/lib/libbinder.so
I/DEBUG ( 75): #04 pc 0001f1dc /system/lib/libbinder.so
I/DEBUG ( 75): #05 pc 0001f690 /system/lib/libbinder.so
I/DEBUG ( 75): #06 pc 0001f6c2 /system/lib/libbinder.so
I/DEBUG ( 75): #07 pc 0001b7a8 /system/lib/libbinder.so
I/DEBUG ( 75): #08 pc 000089be /system/bin/mediaserver
I/DEBUG ( 75): #09 pc 00008aa8 /system/bin/mediaserver
I/DEBUG ( 75): #10 pc 00014edc /system/lib/libc.so
I/DEBUG ( 75):
I/DEBUG ( 75): code around pc:
I/DEBUG ( 75): 802049d4 e1853f92 e3530000 1afffffa e8bd8070
I/DEBUG ( 75): 802049e4 e92d4070 e1a04000 e1a05001 ebffffd4
I/DEBUG ( 75): 802049f4 e1950f9f e0802004 e1853f92 e3530000
I/DEBUG ( 75): 80204a04 1afffffa e8bd8070 e1a01000 e3e00000
I/DEBUG ( 75): 80204a14 eafffff2 e1a01000 e3a00001 eaffffef
I/DEBUG ( 75):
I/DEBUG ( 75): stack:
I/DEBUG ( 75): bebe2b10 000000a2
I/DEBUG ( 75): bebe2b14 00000000
I/DEBUG ( 75): bebe2b18 00000000
I/DEBUG ( 75): bebe2b1c 0000b948
I/DEBUG ( 75): bebe2b20 00000068
I/DEBUG ( 75): bebe2b24 0000c1e0
I/DEBUG ( 75): bebe2b28 000000a2
I/DEBUG ( 75): bebe2b2c afd14635 /system/lib/libc.so
I/DEBUG ( 75): bebe2b30 00000003
I/DEBUG ( 75): bebe2b34 0000b950
I/DEBUG ( 75): bebe2b38 c0000000
I/DEBUG ( 75): bebe2b3c 000000da
I/DEBUG ( 75): bebe2b40 00000000
I/DEBUG ( 75): bebe2b44 00000000
I/DEBUG ( 75): bebe2b48 df002777
I/DEBUG ( 75): bebe2b4c e3a070ad
I/DEBUG ( 75): #00 bebe2b50 0000aeb8
I/DEBUG ( 75): bebe2b54 0000aeb9
I/DEBUG ( 75): bebe2b58 bebe2bb0
I/DEBUG ( 75): bebe2b5c 80315b21 /system/lib/libutils.so
I/DEBUG ( 75): #01 bebe2b60 0000aeb8
I/DEBUG ( 75): bebe2b64 80315b75 /system/lib/libutils.so
I/ ( 125): ServiceManager: 0xad50

The fault seems to be in

['android_atomic_add', 'system/core/include/cutils/atomic-arm.h:184']

Did you get this as well? How did you fix it? thanks...
[G1 Android Development] ezterry:
hrm.. interesting.. I think I get it.

By default there is no /cache/dalvik-cache (or its unused even if its generated)

On the Magic however since there is significantly more cache space FR's patches as well as your own allow system's dex files to be generated there.

However remember the dex files must be read by the application users.. thus if any app is missing the cache read access permission (and most don't have it) it will fail.\

To fix the following two edits may be needed (change is red):

1) in system/code/rootdir/init.rc

mkdir /system
mkdir /data 0771 system system
[b]mkdir /cache 077[color=red]1[/color] system cache[/b]
mkdir /config 0500 root root

2) in system/core/include/private/android_filesystem_config.h

static struct fs_path_config android_dirs[] = {
[b] { 0077[color=red]1[/color], AID_SYSTEM, AID_CACHE, "cache" },[/b]
{ 00771, AID_SYSTEM, AID_SYSTEM, "data/app" },
{ 00771, AID_SYSTEM, AID_SYSTEM, "data/app-private" },
{ 00771, AID_SYSTEM, AID_SYSTEM, "data/dalvik-cache" },

(if its not there both files also need an entry for "cache/dalvik-cache" 0771 system system
[G1 Android Development] Effdee:
Ahh yes 771 makes sense

and looking at fr's 06Bindmount he has this

if [ ! -d $cacheDir/dalvik-cache ];
then
busybox install -m 771 -o 1000 -g 1000 -d $cacheDir/dalvik-cache
fi

but like you say if /cache dir doesn't have the world exec bit set not everything will read past it
[G1 Android Development] blackcuzz:
Ap mode rather than adhoc

Is there a kernel that works with this rom and for G1/Mytouch that allows root users to tether in access-point mode rather than ad-hoc mode
[G1 Android Development] Effdee:
since the /cache mount point is in memory it needs to be done each boot

so adding a script like this

#!/system/bin/sh
mount -o rw,remount /
chmod 771 /cache
mount -o ro,remount /

would do until the init.rc is fixed

I did think about doing a patch but the above is much easier
[G1 Android Development] AndDiSa:
You could try to copy the attached file to the phone

adb push 02chmodCache.txt /data/userinit.d/02chmodCache
adb chmod 555 /data/userinit.d/02chmodCache

I am not sure at the moment, whether it is executed early enough ... otherwise it's to be copied to /system/etc/init.d, but here you need to remount /system before.
[G1 Android Development] Effdee:
I think it should be

/data/local/userinit.d/02chmodCache
[G1 Android Development] AndDiSa:
You are right ... but in the meantime I updated the ROM with the correct permissions for /cache and /cache/dalvik-cache like ezTerry proposted. Should be available within a few minutes.
[G1 Android Development] muldy:
ADS_magpie-20110406-signed ? :)
[G1 Android Development] tcorless:
I tried the new ROM with the 200110406 date and my MT3G still didn't get past the boot animation, the same permission problem. I rebooted and using adb manually change the permission as soon as the phone connected and it worked, the ROM loaded.

Something must be changing the permissions back latter on. I noticed further down in the init.rc file the following:

# We chown/chmod /data again so because mount is run as root + defaults
chown system system /data
chmod 0771 /data

Do we need to add the chmod for /cache here too?
[G1 Android Development] AndDiSa:
Sounds strange ... I will check it. Thanks for your hint, especially because I don't have a MT3G and so I need some help.

Edit: You are right, the modification is included, but later on in the init.rc the permissions are changed back to 770 ... I will correct that.

Edit2: version from 20110407 has this bugfix included
[G1 Android Development] AndDiSa:
@people having a MT3G I need your feedback whether the new ADS_Magpie-20110407 is booting now ;) Thanks.
[G1 Android Development] tcorless:
I flashed ADS Magpie 0407 on my MT3G about 6 hours ago and it booted up just fine. And it been running great. Thanks!
[G1 Android Development] roccoadam32:
Latest magpie gave me a random reboot after 4 hours prior to the reboot everything I opened froze back on froyo for now battery life was dam good though
[G1 Android Development] muldy:
Installed ok.... (passed the boot animation)

Testing
[G1 Android Development] AndDiSa:
Was it a wipe or non-wipe installation? I could imagine, that some old dex-files were still located in one of the dalvik-cache directories, there are three:

/cache/dalvik-cache

/data/dalvik-cache

/sd-ext/dalvik-cache

A chance could be to clean them and to reboot afterwards.
[G1 Android Development] muldy:
Superwipe

reboot

Superwipe

reboot

flash
[G1 Android Development] AndDiSa:
Hmm ... what's the difference between them? :confused:
[G1 Android Development] Effdee:
use addr2line to see what code is running

hands up I've not used it in ages, so I'm rusty

or muldy needs to provide the human readable logcat so we can at least see what was going on before the dump
[G1 Android Development] AndDiSa:
why do you superwipe and reboot 2 times before flashing? :confused:

Can you pls provide with the logcat when booting?

adb logcat | tee logcat.txt

and wait until there is either the bootloop or the media scanner finished.
[G1 Android Development] creezalird:
just realized that even I ticked the sd-ext partition as preferred installation location, but sometimes the app will be installed in the sd-ext/app, but sometimes in the data/app. Is it normal like that? I'm using ADS_magpie_ezGB
[G1 Android Development] azrash:
certain apps must be installed in internal memory, check what those data/apps are and you will understand why
[G1 Android Development] creezalird:
Is it because the apps have widgets and need to be installed in internal memory?

As far as my knowledge goes, this should be the only reason right?
[G1 Android Development] AndDiSa:
... but even those normally you can move to sd-ext afterwards manually.
[G1 Android Development] hrk:
Since your code is the same in every block of the if-elseif-else block, you can put it outside and write it only once. HTH.
[G1 Android Development] hrk:
SMS woes - no moar!... ehm.. more!

Albeit later than I wished, "No Frills Gingebread Nasty SMS Bug Workaround" has been released under a nice name. I've added the discussion link to my signature, market url is this.

I've posted it in the G1 section, "spamming" the link on ezGingerbread and COS-DS threads, since they're the two I follow where I saw people complaining about lost messages. :)
[G1 Android Development] Effdee:
Very true

I'll go back and fix that
[G1 Android Development] muldy:
I will on next flash :)
[G1 Android Development] creezalird:
tested the 0904 version from Andisa and so far everything is working properly.

Even all apps now are installed/restored into the configured location.

Also tested hrk's ghostly sms fix, and so far mine is receiving sms properly with no killed.

Thank you so much
[G1 Android Development] jdb78:
I used version ADS_magpie-20110322-odexed-signed.zip up to today and I was very unhappy with it. I had the latest pershot kernel from that date installed. Phone was reacting real slow some times and I often had a black screen. I don't know what the advantage of odexed is supposed to be - but from my beginner's point of view the non-odexed versions run better.

Today I installed the ADS_magpie-20110409-signed.zip and this one runs a lot smoother. No lag up to now. I received a phone call while searching the market and the phone app got FC. Sorry, no logcat from that.

One more thing I noticed is that OI Filemanager is missing again. I still had it in the version before I assume. I deleted all caches before rebooting to recovery to flash the new ROM. So far I can say it runs good, will keep on testing.
[G1 Android Development] AndDiSa:
The reason could have been the gralloc / out of resources bug, it seems to be fixed now.

Did you wipe your dalvik-caches? I suggest to clean your caches when switching between odexed / non-odexed versions.

OI Filemanager is not included, you can download the latest version from the market.
[G1 Android Development] jdb78:
Hey AndDiSa,

my intention was not to criticize you. I just wanted to share my experience regarding the ROMs, I thought that could help improve them. Like I mentioned before I love the work of ezterry, Firerat, you and all the others contributing here. I highly appreciate everything you guys did so far.

I see, like I said the most recent ROM is running much better.

Yes, like I wrote before I deleted all caches you mentioned in a previous post but with the phone still running. I used adb shell to to a rm * within the three cache locations.

I thought ezterry included it in the source?

I did not install it manually and with one of the latest ROMs it was suddenly there :]
[G1 Android Development] seventyeight:
I'm running ADS_magpie 20110411. Whithin the WhatsApp messenger taking photos does not work. But choose one from the gallery works fine.

D/dalvikvm( 1079): GC_CONCURRENT freed 373K, 49% free 3230K/6279K, external 1024K/1038K, paused 9ms+8ms
D/dalvikvm( 1079): GC_EXTERNAL_ALLOC freed 7K, 49% free 3223K/6279K, external 1024K/1038K, paused 78ms
I/dalvikvm( 1079): Could not find method android.media.MediaMetadataRetriever.captureFrame, referenced from method com.whatsapp.z1.a
W/dalvikvm( 1079): VFY: unable to resolve virtual method 370: Landroid/media/MediaMetadataRetriever;.captureFrame ()Landroid/graphics/Bitmap;
D/dalvikvm( 1079): VFY: replacing opcode 0x6e at 0x0114
D/dalvikvm( 1079): VFY: dead code 0x0117-011d in Lcom/whatsapp/z1;.a (Landroid/app/Activity;Ljava/lang/String;Ljava/io/File;BLjava/lang/String;)Z
E/ ( 1079): can't open '/mnt/sdcard/WhatsApp/Media/WhatsApp Images/ccbeadf76f17a32f7fc05bea6c529d94.jpg'
I/ActivityManager( 189): Displayed com.whatsapp/.Conversation: +1s368ms
W/IInputConnectionWrapper( 1061): showStatusIcon on inactive InputConnection
I/ActivityManager( 189): Process com.android.camera (pid 1061) has died.
I/ActivityManager( 189): Low Memory: No more background processes.
D/dalvikvm( 189): GC_EXPLICIT freed 54K, 42% free 5748K/9863K, external 1316K/1828K, paused 198ms
D/skia ( 317): purging 13K from font cache [2 entries]
[G1 Android Development] creezalird:
Just tried on my magic..seems to be working using camera within whatsapp.

Maybe you're running too many background apps/widgets and causing the camera app to be killed when called.

Just for info,I have an average of 20mb free ram with whatsapp running background
[G1 Android Development] jdb78:
20 MB? I got ~2MB usually according to SetCPU Memfree. "free" in the terminal emulation says 2036 also. Varies from 2000 to 6000 but never 20000.
[G1 Android Development] creezalird:
yep..if i kill whatsapp, i can even get up to 30mb on average

These are my configs/apps:

no-frills cpu : 128/595Mhz

Compcache : 50% VM : 16

Widgets : Colorize Widget (Timeline) , Power Widget

Tasker : To automate everything else.

Autostarts : disable almost everything except no-frills,droidwall,automemory manager

Auto Memory Manager : 5, 5, 5, 15, 20, 25

Chat usually with Whatsapp and sometimes Gtalk too

Battery life on average with medium usages about 24hours. If on standby/lite usages, up to 40hours sometimes

p/s : I don't use setcpu because of large memory use
[G1 Android Development] ezterry:
NEVER listen to 'free' on a linux based system. Free ram is wasted ram.. However data read from SD/Flash cached in ram but not in use by anything is effectively free. If an app needs more space just drop the disk cache reference and give it. On the other hand if any running code needs the cached file(s) it can just provide the pointer to the cached memory no need to re-read from storage.

The system is even smart using "swap" to page out active pages cached from files if more ram is needed.

When people say free hopefully they are looking at Settings->Applications->Running Services

This calculates what is free based on the above, minfree levels, and android apks that are in ram but no in use (background tasks; not services) ... this gives a indication of what is really available instantly to an application

[maybe not perfect as swap has an interesting behavior on android systems.. and a few different methods of that have been made.. and the settings app is not always in sync with the kernel's calculations.]
[G1 Android Development] creezalird:
Thanks for the info.

Btw I'm using the "Settings->Applications->Running Services" to check my free ram.

Made a shortcut to that on the desktop.
[G1 Android Development] jdb78:
Phew, thank you Terry for that explanation. I used to use Linux based systems before (Debian and Ubuntu) but I never got that deep into the system.

Settings->Applications->Running Services tells me I got a whole lot more free RAM.
[G1 Android Development] highlandsun:
The only thing to pay attention to in "free" is the amount of swap in use. Ideally swap usage should always be zero. Maybe make an exception for a very large foreground app.

Tuning Android's low memory killer is a bit of a pain. It seems to always look at the total of swap+ram when it checks how much memory is available, and will spawn background jobs until that total is full. It ought to exclude available swap from this calculation.
[G1 Android Development] AndDiSa:
The method which is called from WhatsApp (android.media.MediaMetadataRetriever.captureFrame) does not exist, i.e. this version of WhatsApp is incompatible ... either there is another version of WhatsApp or there is an update to MediaMetadataRetriever which is not merged yet.

Edit: captureFrame is no longer supported fromthe SDK, to you need a newer version of WhatsApp ...
[G1 Android Development] AndDiSa:
I didn't take it as critizism, excuse me if I answered in such a way ;)
[G1 Android Development] muldy:
If you are using swap...

ezGingerbread has no swap whatsoever...

Swap comes from compcache(AndDiSa rom) or swap on sdcard.
[G1 Android Development] hrk:
Just a sidenote[1]: ADS_0409 has been losing more messages than previous builds (in fact I haven't been losing SMS messages in a couple of weeks). It lost two messages in less than 24 hours. I'm going to update to 0411, and I'll keep my Gingerbread Ghostly SMS firmly installed, to be on the safe side ;-)

[1] Not complaining, it's Google's own bug.
[G1 Android Development] ZilverZurfarn:
Agree - Up until 1 1/2 week ago, I've had absolutely no lost messages, but last week (and start of this) was a disaster. Latest ver I don't know, but I don't think I've lost anything since last update (0411). Hard to log, as you don't know when a message is lost...
[G1 Android Development] AndDiSa:
Running 0411, too, but up to now no lost messages.

(I've installad Ghostly SMS, too, and got always notifications from system and Ghostly SMS)
[G1 Android Development] creezalird:
Same here and lost not even one message. Maybe lucky me :)
[G1 Android Development] muldy:
Never lost a message myself...

On any rom, since first versions of cyanogen
[G1 Android Development] hrk:
It's a bug introduced with Gingerbread. :-) Up until CM6.1 it didn't exist.

@ZilferZurfain: give a look to Gingerbread Ghostly SMS in my signature about how to find out if you're losing messages. If you don't lose them, the app will be a burden 'cause you'll have to dismiss useless notifications, but if you lose them, you'll love the "Move to INBOX" button :D
[G1 Android Development] hrk:
Since it's very likely due to low RAM, I guess it really depends on what you (user) are doing with the phone when the message is received. I was replying to a thread with the XDA-Developer forum app... I always thought it was bloat, this is the proof :joking:

The second one was lost when I was in the subway and I got a "glimpse" of signal. I guess phone changing state may bring CPU in a busy state... I'm just pulling straws here...
[G1 Android Development] ZilverZurfarn:
Installing - Thanks!
[G1 Android Development] creezalird:
a short question because i'm curious :

if i'm flashing my phone to the latest rom version, for example from 1104 to 1304 version of ADS_ezGB, should I be doing the battery calibration? Thanks in advance

And it is a no wipe update
[G1 Android Development] AndDiSa:
Depends on you ;)

To be honest, every time you have connected your phone with USB, but not running a ROM, the battery statistics will be no longer valid. You can see it also in the graphics: a small hole and a jump up.

More worse is a nand restore, because here you are restoring values which are completly outdated.
[G1 Android Development] roalex:
Losing sms= people who confuse their old G1 with their Desktop computer and load it up with 100 widgets, 200 apps and so on. I never notice this bug on either Android phone i use.
[G1 Android Development] ZilverZurfarn:
Beg to differ. Running a very bare bones AnDiSa_Magpie - Even removed some of the default apps I don't use (like VoiceSearch and stuff) - Still, last few weeks I've been missing texts. Thanks to Ghostly SMS I can now verify that is a fact, rather than a feeling. Luckily, this may be the last day my G1 is my daily driver... :) Up until last week, I'd have agreed with you - Now I don't.
[G1 Android Development] roalex:
So up until last week you would agree with me in this matter but installing some random application which messes with your SMSs made you think different, funny id say :) As if one doesn't know if he's missing a SMS.
[G1 Android Development] ZilverZurfarn:
What's funny, is you think you know what I have installed on my phone. I can assure you nothing new has been installed. The difference is I've been keeping up with AnDiSa's great rom releases. Nothing else.