View source for User talk:Seanmcneil3

==What's new?==
This would be a nice area for a changelog.  What's new in the November 17th image?  Anything worth noting?

== Android running problems ==

I had flashed it now on my FR but it doesn't work. I see only a black screen.

It works, but you need 2 partition on your SD card. First about 8MB formated vfat, secound ext3. That partitions must be empty.

--

Hi Sean, how can the imgages be put on the GTA02? I also flashed my GTA02 and android will not start, only black screen.

Sean:
I've just begun adding more information to the page which explains what is necessary to bring up Android. Sorry for the delay.

--

Hi Sean I split sd card to 2 partition fat32 and ext3, noting in fat32(1.5g) and in ext3(2.2G) have lostxxfound directory,I never set boot flag to sd card's partition, now I flash image and rootfs according your "setup guide" but now it not start just black screen. what's wrong with it

--

Hi Sean,
same problem: I flashed the kernel and rootfs. My SDcard has a primary 100MB FAT16 and an other primay 400MB EXT3 partition. I only get a black screen.

--

Hi,
When using Android, some menu items are don't work. E.g. when trying to set the Phone Ringtone, the menu shows for a split second and then I'm back to the Sound settings. The log shows the following:
<pre>
I/ActivityManager(  855): Starting activity: Intent { action=android.intent.action.RINGTONE_PICKER comp={android/com.android.internal.app.RingtonePickerActivity} (has extras) }
I/ActivityManager(  855): Start proc android.process.media for content provider com.android.providers.media/.MediaProvider: pid=1385 uid=10003 gids={1006, 3003, 2001}
I/ActivityThread( 1385): Publishing provider downloads: com.android.providers.downloads.DownloadProvider
I/ActivityThread( 1385): Publishing provider drm: com.android.providers.drm.DrmProvider
I/ActivityThread( 1385): Publishing provider media: com.android.providers.media.MediaProvider
V/MediaProvider( 1385): Attached volume: internal
V/MediaProvider( 1385): /sdcard volume ID: -1
V/MediaProvider( 1385): Attached volume: external
I/ActivityManager(  855): Exiting empty application process android.process.media (android.os.BinderProxy@435052d8)
I/Process (  855): Sending signal. PID: 1385 SIG: 9
I/ActivityManager(  855): Killing app com.android.settings (pid 1377) because provider com.android.providers.media.MediaProvider is in dying process android.process.media
I/Process (  855): Sending signal. PID: 1377 SIG: 9
I/ActivityManager(  855): Killing app com.android.settings (pid 1377) because provider com.android.providers.drm.DrmProvider is in dying process android.process.media
I/Process (  855): Sending signal. PID: 1377 SIG: 9
D/ActivityManager(  855): Received spurious death notification for thread android.os.BinderProxy@435052d8
I/ActivityManager(  855): Process com.android.settings (pid 1377) has died.
I/WindowManager(  855): WIN DEATH: Window{434e8b10 com.android.settings/com.android.settings.SoundAndDisplaySettings}
I/WindowManager(  855): WIN DEATH: Window{434f1520 android/com.android.internal.app.RingtonePickerActivity}
I/ActivityManager(  855): Start proc com.android.settings for activity com.android.settings/.SoundAndDisplaySettings: pid=1396 uid=1000 gids={3001, 3003}
I/ActivityManager(  855): Low Memory: No more background processes.
D/dalvikvm(  855): GC freed 2248 objects / 104336 bytes in 727ms
W/SurfaceComposerClient(  855): lock_layer timed out (is the CPU pegged?) layer=1, lcblk=0x423800a0, state=0000000c (was 0000000c)
D/dalvikvm(  888): GC freed 167 objects / 6208 bytes in 958ms
D/dalvikvm(  894): GC freed 15 objects / 560 bytes in 998ms
I/ActivityManager(  855): Displayed activity com.android.settings/.SoundAndDisplaySettings: 2675 ms
</pre>
I was not sure if it is because I had relatively small space dedicated to teh VFAT and Ext3 partitions on the SD card (so I can have another distro on the 3rd partition), but it seems to be enough:
<pre>
/: 252544K total, 38468K used, 214076K available (block size 4096)
/: 252544K total, 38468K used, 214076K available (block size 4096)
/dev: 59952K total, 0K used, 59952K available (block size 4096)
/sqlite_stmt_journals: 4096K total, 0K used, 4096K available (block size 4096)
/data: 30985K total, 19413K used, 11572K available (block size 1024)
/sdcard: 31912K total, 1782K used, 30130K available (block size 2048)
</pre>
Other menu items do the same thing sometimes, but I forgot which one I found last time. In the log they also had the "Low memory" warning, so should originate the same place. --[[User:Imrehg|Imrehg]] 05:10, 20 December 2008 (UTC)

'''Update:''' the menu works fine from the contact list, when trying to change the ringtones for individual contacts. --[[User:Imrehg|Imrehg]] 10:03, 24 December 2008 (UTC)

--

Sending message breaks network connection.
When I'm trying to send a message, the network disconnects (without sending the SMS) and won't work even with reboot, until I delete the message thread and reboot (sometimes even need reboot a few times after message delete). Receiving a message works just fine.
The log of the message send (after clicking the send button):
<pre>
D/SmsProvider(  888): insert url=content://sms/outbox, match=8
I/ActivityManager(  855): Stopping service: com.android.mms/.transaction.SmsReceiverService
I/ActivityManager(  855): Stopping service: com.android.mms/.transaction.SmsReceiverService
I/NotificationService(  855): enqueueToast pkg=com.android.mms callback=android.app.ITransientNotification$Stub$Proxy@435bc740 duration=0
</pre>
Not sure whether it matters, my network is TWN GSM (Taiwan) --[[User:Imrehg|Imrehg]] 05:34, 20 December 2008 (UTC)

--

Volume during call is too low. When not in call, the soft-keyboard has the Vol+ and Vol- buttons, but of course they don't do anything. During call, the volume is too low, I can hardly hear anything. On the receiving end they can hear me perfectly clear. If trying to bring up the soft-keyboard during call with the Menu (the Power button at the moment), then instead of the previously mentioned menu (which has the keyboard option) the Contacts menu comes up... Thus no way to adjust the volume and making the phone almost unusable for calls, unless I'm in a perfectly silent environment. --[[User:Imrehg|Imrehg]] 05:38, 20 December 2008 (UTC)

'''Update:''' Could access the keyboard as: Pressing Menu (power) button once -> Phone displays contacts menu -> Menu button again -> Soft-keyboard key. The displayed Vol+/Vol- buttons (and probably the rest of the function buttons) don't have any effect on the call, it is still the same low sound level. --[[User:Imrehg|Imrehg]] 07:18, 20 December 2008 (UTC)

== Android doesn't accept the pin ==

I have flashed my GTA02 and android will boot but it does not accept the pin code for my SIM-card.
Jofry

Sean:
Hi Jofry, I've never really tried a locked SIM, so I don't know if the dialpad comes up to let you type in the code. Does it? If so, then I can probably fix the issue. Otherwise, we are kind of stuck until a virtual keyboard is developed.

Jofry: Yes, the dialpad comes up and ask for my pin number. But if i type in the number the application means that it was the wrong number. But it is the right one.

Skamster: i've got the same problem. i could enter the pin as much as i want but it doesn't let me in. normaly, it lock the sim after 3 try's (i try 4-6 times), but here it doesn't. i flashed with qtopia again and don't need a puck. maybe it doesn't "send" the pin to the simcard?

That's a known issue. For more information about the things you have to do, before you can successful use Android, look at http://onlinedev.blogspot.com/2008/11/getting-started-with-android-on-neo.html [[User:Dolfje|Dolfje]] 12:03, 5 November 2008 (UTC)

I got the same problem but can not fix it through disabling the pin, because my sim does not allow to disable the pin neither with qtopia, nor with my other mobile phone.

== Android rootfs for µSD boot ==

Treviño: Could you set-up a rootfs for running Android from MicroSD?
Radek: You can download one from http://activationrecord.net/radekp/openmoko/android/ More info in this mail http://lists.openmoko.org/pipermail/community/2008-December/038677.html

== Android and replying calls ==

Actually it is not possible to reply to a call due to the missing hardware "accept" button.

Treviño: So, what about adding a workaround to it by using the AUX button as an "accept" button if pressed briefly (below 0.5 second), while keeping it to the "reject" (home) button when pressed longer?!

ahk05: It seems that Yann neveu-2 has managed to modify the Phone app to allow you to answer phone calls with the power button. Maybe his apk should be included in your image?
http://n2.nabble.com/-Android--Soft-keyboard-td1518369.html
http://gabuzomeu.fr/openmoko/Phone.apk

== Android Misc requests ==



--

dilersam:  thanks for having added more informations to the page. It helps a lot.

-

fate: thanks for all your great work. i was wondering when will the next flash image be released?

== u-boot environment changes for large kernel ==

I'm using [[neocon]] to connect to the u-boot console.  What env variable should we change and to what values?

Thanks!

- I'm using Kermit, and this is what I change in the console

      setenv bootargs ${bootargs_base} ${mtdparts}; nand read.e 0x32000000 kernel; bootm 0x32000000