Jump to content

Android 2.2 Development

Guest eckengucker1

By Guest eckengucker1
in T-Mobile Pulse

 Share

Recommended Posts

Guest totiadrenalin

Guest totiadrenalin

Posted
Posted
As I can see in the build.prop it's FRF85B

And the cyanogen's rom is FRF91

Same old bug with the Gallery3D. and rotation.

Can we somehow port the Huawei's gallery from 2.1?

  • Replies 1.7k
  • Created
  • Last Reply

Popular Days

Popular Days

Posted Images

Guest Simon O

Guest Simon O

Posted
Posted (edited)
Same old bug with the Gallery3D. and rotation.

Can we somehow port the Huawei's gallery from 2.1?

You have working rotation?

Edit: Ah it's OK. I got mine working.. forgot to delete the old sensor files.

Edited by flibblesan
Guest Tom G

Guest Tom G

Posted
Posted (edited)
You have working rotation?

Yes, rotation is now working.

The gallery issue and live wallpaper issues look like they are related to egl (which I thought I had fixed a while ago).

Edited by Tom G
Guest totiadrenalin

Guest totiadrenalin

Posted
Posted
Yes, rotation is now working.

The gallery issue and live wallpaper issues look like they are related to egl (which I thought I had fixed a while ago).

git://android.git.kernel.org/platform/packages/apps/Gallery.git

This is the Non3D gallery.

Guest Simon O

Guest Simon O

Posted
Posted

Yeah I have the issues with the 3D Gallery too, Tom. I've just pushed the libEGL.so from the Sapphire to my phone and it works better but still has some slight bugs.

Guest totiadrenalin

Guest totiadrenalin

Posted
Posted
Yeah I have the issues with the 3D Gallery too, Tom. I've just pushed the libEGL.so from the Sapphire to my phone and it works better but still has some slight bugs.

Why not from Pulse 2.1?

Guest Simon O

Guest Simon O

Posted
Posted (edited)
Why not from Pulse 2.1?

Froyo won't boot if we use the libEGL.so from 2.1

Ok now that sensors are working, next big job is the camera. Any luck with this so far, Tom?

Edited by flibblesan
Guest Tom G

Guest Tom G

Posted
Posted 

I/Vold	( 1046): /dev/block/vold/179:1 being considered for volume sdcard

D/Vold	( 1046): Volume sdcard state changing 1 (Idle-Unmounted) -> 3 (Checking)

I/Vold	( 1046): Filesystem check completed OK

I/Vold	( 1046): Device /dev/block/vold/179:1, target /mnt/sdcard mounted @ /mnt/secure/staging

D/Vold	( 1046): Volume sdcard state changing 3 (Checking) -> 4 (Mounted)

D/VoldCmdListener( 1046): asec list

I found the vold bug. Its hard coded to mount partition 1 at the moment, but I will try to get to work with the partition number provided in vold.fstab.

JIT is now running, but I haven't done any testing.

Guest Simon O

Guest Simon O

Posted
Posted (edited) 
I/Vold	( 1046): /dev/block/vold/179:1 being considered for volume sdcard

D/Vold	( 1046): Volume sdcard state changing 1 (Idle-Unmounted) -> 3 (Checking)

I/Vold	( 1046): Filesystem check completed OK

I/Vold	( 1046): Device /dev/block/vold/179:1, target /mnt/sdcard mounted @ /mnt/secure/staging

D/Vold	( 1046): Volume sdcard state changing 3 (Checking) -> 4 (Mounted)

D/VoldCmdListener( 1046): asec list[/code]

I found the vold bug. Its hard coded to mount partition 1 at the moment, but I will try to get to work with the partition number provided in vold.fstab.



JIT is now running, but I haven't done any testing.



Fantastic. Hopefully this means that the Froyo A2SD will work. Is this just a replacement vold binary?



BTW I hate the Pulse Mini now... the U8150 Ideos 2.2 ROM seems to work for them with a very small number of cosmetic issues. Sadly the kernel image is way too big to flash onto the big Pulse.
Edited by flibblesan
Guest Tom G

Guest Tom G

Posted
Posted
Fantastic. Hopefully this means that the Froyo A2SD will work. Is this just a replacement vold binary?

Yep, just a new binary. I'm not sure if things like format will select the right partition (actually I'm fairly sure it won't).

vold.zip

Guest totiadrenalin

Guest totiadrenalin

Posted
Posted (edited) 

## add a mount entry for each mount point to be managed by mountd

volume_sdcard {

	media_path	/devices/platform/msm_sdcc.1/mmc_host/mmc0

	media_type	mmc

	mount_point   /sdcard

	ums_path	  /devices/platform/usb_mass_storage/lun0

}


# /*<BU5D07302 qinwei 20100413 begin */

#volume_sdcard2 {

#	media_path	/devices/platform/msm_sdcc.4/mmc_host/mmc2

#	media_type	mmc

#	mount_point   /sdcard

#	ums_path	  /devices/platform/usb_mass_storage/lun1

#}

# /* BU5D07302 qinwei 20100413 end > */

[code]

vold.conf from 2.1

And 

[code]



volume_sdcard {

	## This is the direct uevent device path to the SD slot on the device

	emu_media_path /devices/platform/goldfish_mmc.0/mmc_host/mmc0

from froyo

and ther is no goldfish_mmc.0 file in /sys/devices/platform/ folder

Maybe that would sold our mount problem and apps to sd

Edited by totiadrenalin
Guest Tom G

Guest Tom G

Posted
Posted (edited) 
## add a mount entry for each mount point to be managed by mountd

volume_sdcard {

	media_path	/devices/platform/msm_sdcc.1/mmc_host/mmc0

	media_type	mmc

	mount_point   /sdcard

	ums_path	  /devices/platform/usb_mass_storage/lun0

}


# /*<BU5D07302 qinwei 20100413 begin */

#volume_sdcard2 {

#	media_path	/devices/platform/msm_sdcc.4/mmc_host/mmc2

#	media_type	mmc

#	mount_point   /sdcard

#	ums_path	  /devices/platform/usb_mass_storage/lun1

#}

# /* BU5D07302 qinwei 20100413 end > */

[code]

vold.conf from 2.1

And 

[code]

volume_sdcard {

	## This is the direct uevent device path to the SD slot on the device

	emu_media_path /devices/platform/goldfish_mmc.0/mmc_host/mmc0

from froyo

and ther is no goldfish_mmc.0 file in /sys/devices/platform/ folder

Maybe that would sold our mount problem and apps to sd

vold.conf is from older versions. Vold is totally different in Froyo and doesn't use vold.conf. The issue is not a simple configuration problem, it looks like a real bug in how the volume is selected.

PS. anything that refers to goldfish is for the emulator. A rom can be made so that it will work both on a real device and in the emulator by using the goldfish options, but for a real device they don't need to be there.

Edited by Tom G
Guest Simon O

Guest Simon O

Posted
Posted

Ok that seems fine

09-04 03:33:12.434: INFO/Vold(1064): Vold 2.1 (the revenge) firing up

09-04 03:33:12.454: DEBUG/Vold(1064): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media)

09-04 03:33:12.454: ERROR/Vold(1064): type='dev_mount' label='sdcard' mount_point='/mnt/sdcard' part='auto' sysfs_path='/devices/platform/msm_sdcc.1/mmc_host/mmc0'

09-04 03:33:12.454: ERROR/Vold(1064): type='dev_mount' label='sdcard' mount_point='/mnt/sdcard' part='auto' sysfs_path='/devices/platform/msm_sdcc.1/mmc_host/mmc0'

09-04 03:33:12.704: DEBUG/Vold(1064): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)

09-04 03:33:12.704: DEBUG/Vold(1064): Volume sdcard state changing 2 (Pending) -> 1 (Idle-Unmounted)

09-04 03:33:55.404: INFO/Vold(1064): /dev/block/vold/179:1 being considered for volume sdcard

09-04 03:33:55.404: DEBUG/Vold(1064): Volume sdcard state changing 1 (Idle-Unmounted) -> 3 (Checking)

09-04 03:34:03.334: INFO/Vold(1064): Filesystem check completed OK

09-04 03:34:03.364: INFO/Vold(1064): Device /dev/block/vold/179:1, target /mnt/sdcard mounted @ /mnt/secure/staging

09-04 03:34:03.374: DEBUG/Vold(1064): Volume sdcard state changing 3 (Checking) -> 4 (Mounted)

My vold.fstab:

# Copyright © 2009 The Android Open Source Project

#

# Licensed under the Apache License, Version 2.0 (the "License");

# you may not use this file except in compliance with the License.

# You may obtain a copy of the License at

#

# http://www.apache.org/licenses/LICENSE-2.0

#

# Unless required by applicable law or agreed to in writing, software

# distributed under the License is distributed on an "AS IS" BASIS,

# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.

# See the License for the specific language governing permissions and

# limitations under the License.

## Vold 2.0 fstab for HTC Dream or Sapphire

#

## - San Mehat ([email protected])

##

#######################

## Regular device mount

##

## Format: dev_mount <label> <mount_point> <part> <sysfs_path1...>

## label - Label for the volume

## mount_point - Where the volume will be mounted

## part - Partition # (1 based), or 'auto' for first usable partition.

## <sysfs_path> - List of sysfs paths to source devices

######################

# Mounts the first usable partition of the specified device

dev_mount sdcard /mnt/sdcard auto /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.1/mmc_host/mmc0

But Froyo A2SD doesn't work. Tried to install Angry Birds (which tries to install to SD)

09-04 03:36:05.414: ERROR/Vold(1064): Error opening devmapper (No such file or directory)

09-04 03:36:05.414: ERROR/Vold(1064): ASEC device mapping failed (No such file or directory)

Guest Simon O

Guest Simon O

Posted
Posted (edited)

Update. Swapped the SD with my 8GB SD with the 1st partition FAT and 2nd partition ext2. Froyo correctly found and mounted the fat partition :P

09-04 03:40:20.084: DEBUG/Vold(1064): Volume sdcard state changing 4 (Mounted) -> 5 (Unmounting)

09-04 03:40:21.084: INFO/Vold(1064): /mnt/secure/staging/.android_secure sucessfully unmounted

09-04 03:40:21.084: INFO/Vold(1064): /mnt/secure/asec sucessfully unmounted

09-04 03:40:21.084: INFO/Vold(1064): /mnt/secure/staging sucessfully unmounted

09-04 03:40:21.084: INFO/Vold(1064): /mnt/sdcard unmounted sucessfully

09-04 03:40:21.084: DEBUG/Vold(1064): Volume sdcard state changing 5 (Unmounting) -> 1 (Idle-Unmounted)

09-04 03:40:21.084: DEBUG/Vold(1064): Volume sdcard state changing 1 (Idle-Unmounted) -> 0 (No-Media)

09-04 03:40:33.805: DEBUG/Vold(1064): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)

09-04 03:40:34.844: DEBUG/Vold(1064): Volume sdcard state changing 2 (Pending) -> 0 (No-Media)

09-04 03:40:34.974: DEBUG/Vold(1064): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)

09-04 03:40:34.984: DEBUG/Vold(1064): Volume sdcard state changing 2 (Pending) -> 1 (Idle-Unmounted)

09-04 03:40:34.994: WARN/Vold(1064): Duplicate state (1)

09-04 03:40:35.084: INFO/Vold(1064): /dev/block/vold/179:1 being considered for volume sdcard

09-04 03:40:35.084: DEBUG/Vold(1064): Volume sdcard state changing 1 (Idle-Unmounted) -> 3 (Checking)

09-04 03:40:39.764: INFO/Vold(1064): Filesystem check completed OK

09-04 03:40:39.774: INFO/Vold(1064): Device /dev/block/vold/179:1, target /mnt/sdcard mounted @ /mnt/secure/staging

09-04 03:40:40.424: DEBUG/Vold(1064): Volume sdcard state changing 3 (Checking) -> 4 (Mounted)

Don't worry about the unmount in the middle of that. I didn't push the SD in all the way lol

Edited by flibblesan
Guest Gjole86

Guest Gjole86

Posted
Posted
BTW I hate the Pulse Mini now... the U8150 Ideos 2.2 ROM seems to work for them with a very small number of cosmetic issues. Sadly the kernel image is way too big to flash onto the big Pulse.

ur wrong. i would say its same as pulse's froyo but with .32 kernel, half things are broken, i hope easy to fix :P

Guest Simon O

Guest Simon O

Posted
Posted
ur wrong. i would say its same as pulse's froyo but with .32 kernel, half things are broken, i hope easy to fix :)

You got it booting. It didn't want to boot for me on my Pulse. :P

Guest Simon O

Guest Simon O

Posted
Posted
I'm not sure if things like format will select the right partition (actually I'm fairly sure it won't).

selecting Unmount in the Settings unmounts the partition correctly but the system isn't made aware of this (the setting doesn't change in the Settings panel). Doesn't matter if the SD has one or two partitions.

09-04 03:50:23.139: DEBUG/Vold(1064): Volume sdcard state changing 4 (Mounted) -> 5 (Unmounting)

09-04 03:50:24.207: INFO/Vold(1064): /mnt/secure/staging/.android_secure sucessfully unmounted

09-04 03:50:24.207: INFO/Vold(1064): /mnt/secure/asec sucessfully unmounted

09-04 03:50:24.604: INFO/Vold(1064): /mnt/secure/staging sucessfully unmounted

09-04 03:50:24.604: INFO/Vold(1064): /mnt/sdcard unmounted sucessfully

09-04 03:50:24.604: DEBUG/Vold(1064): Volume sdcard state changing 5 (Unmounting) -> 1 (Idle-Unmounted)

Vold certainly seems to be doing it's work.

Guest Tom G

Guest Tom G

Posted
Posted
Swapped the SD with my 8GB SD with the 1st partition ext2 and 2nd partition FAT. Froyo correctly found and mounted the fat partition :P

I think you mean FAT first ext2 second. It shouldn't work with the ext2 first.

Guest totiadrenalin

Guest totiadrenalin

Posted
Posted (edited)
You got it booting. It didn't want to boot for me on my Pulse. :P

Guys!

Finaly some progress!

Just use the cyanogen's vond.fstab!

I Can move my apps to sd now via setting>applications>Manage applications

EDIT:

But now it can't read the partiton at all

Edited by totiadrenalin
Guest Simon O

Guest Simon O

Posted
Posted
I think you mean FAT first ext2 second. It shouldn't work with the ext2 first.

Ah that's correct. I always assumed when a recovery asks for the size of the EXT2 partition first that it makes this the first partition. I just checked the SD and the fat is, indeed, the first partition.

Guest totiadrenalin

Guest totiadrenalin

Posted
Posted
Guys!

Finaly some progress!

Just use the cyanogen's vond.fstab!

I Can move my apps to sd now via setting>applications>Manage applications

EDIT:

But now it can't read the partiton at all

It's mount successfully, but can't use it.

I can see all of my files on the sd, but Total space unavalible, and avalible space Unavalible.

Guest Simon O

Guest Simon O

Posted
Posted
Guys!

Finaly some progress!

Just use the cyanogen's vond.fstab!

I Can move my apps to sd now via setting>applications>Manage applications

EDIT:

But now it can't read the partiton at all

The Cyanogen I have lists the partition in vold.fstab as this:

dev_mount sdcard /mnt/sdcard auto /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.2/mmc_host/mmc1

Is that the same in your vold.fstab?

Guest totiadrenalin

Guest totiadrenalin

Posted
Posted
The Cyanogen I have lists the partition in vold.fstab as this:

Is that the same in your vold.fstab?

No

# auto attempts to mount the last partition. This fails if the last partition is not fat (although the vold source includes ext2/3 support?)

#dev_mount sdcard /mnt/sdcard auto /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.1/mmc_host/mmc0

dev_mount sdcard /mnt/sdcard 1 /devices/platform/msm_sdcc.1/mmc_host/mmc0

Guest Simon O

Guest Simon O

Posted
Posted

Ok. Well if you are using the new vold binary then it has the values hard coded. The vold.fstab isn't read by the new binary right now. But Tom is working on it.

Guest Tom G

Guest Tom G

Posted
Posted

The Cyanogen vold.fstab is for different hardware. The correct sysfs path for our device is /devices/platform/msm_sdcc.1/mmc_host/mmc0. The vold binary still uses vold.fstab, I'm just hardcoding the partition number (which doesn't work correctly in the aosp implementation).

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
 Share
Go to topic listing
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.

  I accept