Android Messaging App

[mafro]

I think the Messaging app could be a bit cleverer with parsing number
prefixes when it comes to threading up messages. I've got a UK G1
where the country code is 44.

In Messaging, if I send a message to a 07.. number it goes in a new
thread. The reply will always (I think) come back with +447.. as the
prefix. This means it starts its own new thread! Annoying at best.

I would recommend everyone change their numbers to use the correct
+blah.. country prefix.

Is there a bug tracker for Android that I could post this on?

Also, does anyone know where I can edit my SMS messages saved on the
phone? I would like to 'clean up' some of the 'Sent To' / 'Received
From' numbers so my messages display in the thread form correctly.

Cheers all
mafro

[Mark Murphy]

mafro wrote:
> Is there a bug tracker for Android that I could post this on?

http://b.android.com

> Also, does anyone know where I can edit my SMS messages saved on the
> phone? I would like to 'clean up' some of the 'Sent To' / 'Received
> From' numbers so my messages display in the thread form correctly.

This is a discussion list for building and extending the Android
firmware, so you may not get much of an answer here. You might try the
[android-discuss] Google Group:

http://groups.google.com/group/android-discuss

--
Mark Murphy (a Commons Guy)
http://commonsware.com
Android Training in Sweden -- http://www.sotrium.com/training.php

[mafro]

Thanks for your response Mark. I've noticed you leaving a few helpful
links for people on the lists recently, so perhaps could help with
another problem - do you know where I could get help building Android?

I've posted this in a few places with no response:

http://groups.google.com/group/android-platform/browse_thread/thread/f701da5ade1127a2

Thanks
mafro

On Mar 12, 10:58 am, Mark Murphy <mmur...@commonsware.com> wrote:
> mafro wrote:
> > Is there a bug tracker for Android that I could post this on?
>
> http://b.android.com
>
> > Also, does anyone know where I can edit my SMS messages saved on the
> > phone? I would like to 'clean up' some of the 'Sent To' / 'Received
> > From' numbers so my messages display in the thread form correctly.
>
> This is a discussion list for building and extending the Android
> firmware, so you may not get much of an answer here. You might try the
> [android-discuss] Google Group:
>
> http://groups.google.com/group/android-discuss
>
> --

> Mark Murphy (a Commons Guy)http://commonsware.com

[Mark Murphy]

> Thanks for your response Mark. I've noticed you leaving a few helpful
> links for people on the lists recently, so perhaps could help with
> another problem - do you know where I could get help building Android?

I am afraid that I know nothing about building Android from source. I work
at the SDK level, not with firmware.

--
Mark Murphy (a Commons Guy)
http://commonsware.com

_The Busy Coder's Guide to Android Development_ Version 2.0 Available!

[Fred Grott]

Google search got the link in 10 seconds, very first link:

http://source.android.com/download

[mafro]

Thanks for the response Mark, less so Fred ;)

Did you read the post I linked to..? Of course I've RTFM, and I
obviously needed the link you so cleverly provided to even download
the source in the first place! I appreciate you must get a fair amount
of people posting who don't bother to search Google first, but if you
read the thread I linked to, you would've realised I was not one of
them. But that would've taken more than 10 seconds! Much like this
worthless response.. Hah. Been a long day.

Adios

On Mar 12, 2:08 pm, Fred Grott <fred.gr...@gmail.com> wrote:
> Google search got the link in 10 seconds, very first link:
>
> http://source.android.com/download
>

> On Thu, Mar 12, 2009 at 8:26 AM, mafro <mafro...@gmail.com> wrote:
>
> > Thanks for your response Mark. I've noticed you leaving a few helpful
> > links for people on the lists recently, so perhaps could help with
> > another problem - do you know where I could get help building Android?
>
> > I've posted this in a few places with no response:
>

> >http://groups.google.com/group/android-platform/browse_thread/thread/...

[deg]

You need, in broad strokes, to do the following:
1) Get the Android sources
2) Modify the tree to build images for the G1, rather than generic
images.
3) Build
4) Install the .obj files on your phone

The fourth step is the trickiest, and depends on whether you have a T-
Mobile G1 or an ADP1.

In the ADP1 case, the process is relatively straightforward; for the
G1, you need to get root access first.

I've not found a single source that gives all the steps, but here is
the best set of docs I've seen to date:

- Instructions to get root and install an ADP1-equivalent bootloader
on a G1: http://forum.xda-developers.com/showthread.php?t=442480.
(Once you do this, you can effectively treat your G1 as an ADP1).
- Instructions for steps 1, 3, and 4, for an ADP1:
http://antonmelser.org/open-source/backup-install-restore-adp1.html.
- For step 2, see http://source.android.com/documentation/building-for-dream
and http://groups.google.com/group/android-platform/browse_thread/thread/798f406d0a17cb1e

(I hit a few other snags along the way too, that were not mentioned in
those docs. But, I'm not 100% sure of what went wrong, so I don't want
to muddy the water with false info. Give a shout if you get stuck).

Please keep notes as you are doing this, and send them back to the
community. I was in your boat a few weeks ago and managed to collect
this info before I got everything working and started to forget the
birthing pains. If we each continue to describe our build attempts,
we should converge on a good document soon.

Good luck,
David

[mafro]

Thanks for this David, a really clear and helpful response. I'm not
trying to build Android to install on my phone, just build Android so
I can use the cross-compilation toolchain to build C libraries. I use
the CodeSourcery compiler at the moment, but would obviously prefer to
use the 'official' toolchain!

More info on this here:
http://android-tricks.blogspot.com/

For the record, I used the stuff on xda-developers to get my
production G1 (T-Mobile UK) rooted and updated to RC9 (RC33 equiv). It
can then be used as a developer phone.

My problem still is that I can't build the Android source. It fails on
my Debian Lenny machine, even with the additional steps of targeting
the Dream as per number 2 in the comments above. If I can get this to
work, I might just install the latest on my phone as per your
instructions..

Error:
external/qemu/skins/skin_window.c: In function
`skin_window_trackball_press':
external/qemu/skins/skin_window.c:964: warning: implicit declaration
of function `send_key_event'
make: *** [out/host/linux-x86/obj/EXECUTABLES/emulator_intermediates/
skins/skin_window.o] Error 1

Complete build log:
http://mafro.net/build.log.tar.gz

Original thread:
http://groups.google.com/group/android-platform/browse_thread/thread/f701da5ade1127a2

I can't find anyone else who's having this issue..
Thanks for any help, that anyone can offer!

mafro

On Mar 12, 11:04 pm, deg <d...@degel.com> wrote:
> You need, in broad strokes, to do the following:
> 1) Get the Android sources
> 2) Modify the tree to build images for the G1, rather than generic
> images.
> 3) Build
> 4) Install the .obj files on your phone
>
> The fourth step is the trickiest, and depends on whether you have a T-
> Mobile G1 or an ADP1.
>
> In the ADP1 case, the process is relatively straightforward; for the
> G1, you need to get root access first.
>
> I've not found a single source that gives all the steps, but here is
> the best set of docs I've seen to date:
>
> - Instructions to get root and install an ADP1-equivalent bootloader
> on a G1:http://forum.xda-developers.com/showthread.php?t=442480.
> (Once you do this, you can effectively treat your G1 as an ADP1).
> - Instructions for steps 1, 3, and 4, for an ADP1:http://antonmelser.org/open-source/backup-install-restore-adp1.html.
> - For step 2, seehttp://source.android.com/documentation/building-for-dream

> andhttp://groups.google.com/group/android-platform/browse_thread/thread/...

[deg]

I've not seen that problem here.

I do see that send_key_event is defined in external/qemu/
android_main.c and is only used in that file and in external/qemu/
skins/skin_window.c.
Perhaps you have something inconsistent (incomplete checkout??) in
that directory?

Good luck,
David

On Mar 13, 4:08 pm, mafro <mafro...@gmail.com> wrote:
> Thanks for this David, a really clear and helpful response. I'm not
> trying to build Android to install on my phone, just build Android so
> I can use the cross-compilation toolchain to build C libraries. I use
> the CodeSourcery compiler at the moment, but would obviously prefer to
> use the 'official' toolchain!
>
> More info on this here:http://android-tricks.blogspot.com/
>
> For the record, I used the stuff on xda-developers to get my
> production G1 (T-Mobile UK) rooted and updated to RC9 (RC33 equiv). It
> can then be used as a developer phone.
>
> My problem still is that I can't build the Android source. It fails on
> my Debian Lenny machine, even with the additional steps of targeting
> the Dream as per number 2 in the comments above. If I can get this to
> work, I might just install the latest on my phone as per your
> instructions..
>
> Error:
> external/qemu/skins/skin_window.c: In function
> `skin_window_trackball_press':
> external/qemu/skins/skin_window.c:964: warning: implicit declaration
> of function `send_key_event'
> make: *** [out/host/linux-x86/obj/EXECUTABLES/emulator_intermediates/
> skins/skin_window.o] Error 1
>
> Complete build log:http://mafro.net/build.log.tar.gz
>

> Original thread:http://groups.google.com/group/android-platform/browse_thread/thread/...

[mafro]

Another 'repo sync' command should pick up an incomplete checkout,
right?

I decided to just delete the lot and download all the source again.
We'll see how that pans out later today. Will post in further detail
with my results!

Thanks all
fro

[deg]

Any luck?

David