but if we don't add them to /system do they show up on the list?! i thought only ones placed at /system would show up.

Originally Posted by zicovsky

but if we don't add them to /system do they show up on the list?! i thought only ones placed at /system would show up.

no mine are in /mnt/sdcardaudio-resources\audio etc (legacy from my G1) the media scanner will find them, you might need to reboot to force a scan.

Originally Posted by zicovsky

but if we don't add them to /system do they show up on the list?! i thought only ones placed at /system would show up.

No, I have a few on my sd card in a folder called 'Ringtones'. I had to reboot when I added them and they were there.

Originally Posted by MasterJam882

hey

with the newest nightly and compass fix navigation is not working anymore and crashes all the time.
wiping dalvik and cache didn't work.
reflashed without fix and it's working again.
Interesting is that it started once and worked fine and with second trydidn't work anymore
was one of the first who flashed compass fix with previous nightly and used navigation on a 4 hour drive that day working perfectly fine.
now navigation is crashing right after opening it

someone can confirm that?

greetz

I was able to reproduce the problem.
without fix all is working fine...
but with fix it only works till u restart the phone. after restart navigation crashes. deinstalling and installing maps helps but again only till u restart ur phone.
also noticed that my statement from above saying it was working on previous nightly was false. right after I found that error on my phone with actual nightly my girlfriend with previous nightly called me to tell me that after a restart because of empty battery she's facing the same error.
on my phone I just havent recognized it before because between flashing fix and and newest nightly I havent restarted the phone.

nobody with similar problem?
latest nightly all stock

greetz

Gesendet von meinem GT-I9000 mit Tapatalk

Originally Posted by MasterJam882

hey

with the newest nightly and compass fix navigation is not working anymore and crashes all the time.
wiping dalvik and cache didn't work.
reflashed without fix and it's working again.
Interesting is that it started once and worked fine and with second trydidn't work anymore
was one of the first who flashed compass fix with previous nightly and used navigation on a 4 hour drive that day working perfectly fine.
now navigation is crashing right after opening it

someone can confirm that?

greetz

Read first post and provide all the needed info.

Originally Posted by xavierf

I tested it with SEMAPHORE 1.0 and YES it's working

It works on stock kernel, do not confuse other people with mentions of other kernels (so maybe they think they need to change their kernel, which they don't). Discussion of other kernels goes in the discussion thread, not this one.

Originally Posted by pawitp

Do you know how many mA does the dock supply?

EDIT: As far as I can see from the picture, it doesn't seem to always supply power, so I can't just tell it to display charging whenever the dock's plugged in either. So you'll just have to live with it. (Correct me if I'm wrong - Does the phone detect the dock if it does not supply power?)

There is a socket in the back of the dock to plug the charger into, so it supplies however many mA the charger supplies.

The phone does detect the dock even if the charger is not plugged in, but in the Samsung Gingerbread firmware it does display the battery status in the status bar as charging if the charger is plugged in, and not charging if it isn't.

The power management IC detects that the charger is plugged in independently of the FSA9480 dock device detection, that is why
"cat /sys/class/power_supply/battery/status = Charging".

So in the callback for the car dock (fsa9480_cardock_cb) just do the same as the desk dock callback:
mach-aries.c

static void fsa9480_deskdock_cb(bool attached) {
....
	set_cable_status = attached ? CABLE_TYPE_USB : CABLE_TYPE_NONE;
	if (charger_callbacks && charger_callbacks->set_cable)
		charger_callbacks->set_cable(charger_callbacks, set_cable_status);
}

It looks like the charger callback in s5pc110_battery.c, function max8998_set_cable, checks whether there is actually DC voltage coming in and adjusts the charger status accordingly. It is possible for the desk dock detection to fire without there being DC input voltage, because it is triggered by a resistor in the same way as the car dock detection, so that should work reliably for the car dock too.

In Samsung's Gingerbread kernel source a USB charger is considered plugged in if the power management IC has detected that it's charging and a USB cable or a dock is detected. Specifically from the JPX kernel source:

max8998_function.c:
	if(Get_MAX8998_PM_REG(VDCINOK_status))
	{
		if(curent_device_type == PM_CHARGER_NULL)
		{
			UsbStatus = FSA9480_Get_I2C_USB_Status();
			if(UsbStatus){
				//printk("maxim_USB_connect~~~ \n");
				curent_device_type = PM_CHARGER_USB_INSERT;
			}

fsa9480_i2c.c:
u8 FSA9480_Get_I2C_USB_Status(void)
{
	u8 device1, device2;
	
	fsa9480_read(fsa9480_i2c_client, REGISTER_DEVICETYPE1, &device1);
  	msleep(5);
	fsa9480_read(fsa9480_i2c_client, REGISTER_DEVICETYPE2, &device2);

	if((device1==FSA9480_DEV_TY1_USB)||(device2==FSA9480_DEV_TY2_JIG_USB_ON)||(device2==FSA9480_DEV_TY2_JIG_USB_OFF))
		return 1;
	else
		return 0;
}

When the car dock is connected the fsa9480 device2 register is set to FSA9480_DEV_TY2_JIG_USB_ON, this is the 0x4 in the kernel logs I posted.

Originally Posted by TheBeano

There is a socket in the back of the dock to plug the charger into, so it supplies however many mA the charger supplies.

The phone does detect the dock even if the charger is not plugged in, but in the Samsung Gingerbread firmware it does display the battery status in the status bar as charging if the charger is plugged in, and not charging if it isn't.

The power management IC detects that the charger is plugged in independently of the FSA9480 dock device detection, that is why
"cat /sys/class/power_supply/battery/status = Charging".

So in the callback for the car dock (fsa9480_cardock_cb) just do the same as the desk dock callback:
mach-aries.c

static void fsa9480_deskdock_cb(bool attached) {
....
	set_cable_status = attached ? CABLE_TYPE_USB : CABLE_TYPE_NONE;
	if (charger_callbacks && charger_callbacks->set_cable)
		charger_callbacks->set_cable(charger_callbacks, set_cable_status);
}

It looks like the charger callback in s5pc110_battery.c, function max8998_set_cable, checks whether there is actually DC voltage coming in and adjusts the charger status accordingly. It is possible for the desk dock detection to fire without there being DC input voltage, because it is triggered by a resistor in the same way as the car dock detection, so that should work reliably for the car dock too.

In Samsung's Gingerbread kernel source a USB charger is considered plugged in if the power management IC has detected that it's charging and a USB cable or a dock is detected. Specifically from the JPX kernel source:

max8998_function.c:
	if(Get_MAX8998_PM_REG(VDCINOK_status))
	{
		if(curent_device_type == PM_CHARGER_NULL)
		{
			UsbStatus = FSA9480_Get_I2C_USB_Status();
			if(UsbStatus){
				//printk("maxim_USB_connect~~~ \n");
				curent_device_type = PM_CHARGER_USB_INSERT;
			}

fsa9480_i2c.c:
u8 FSA9480_Get_I2C_USB_Status(void)
{
	u8 device1, device2;
	
	fsa9480_read(fsa9480_i2c_client, REGISTER_DEVICETYPE1, &device1);
  	msleep(5);
	fsa9480_read(fsa9480_i2c_client, REGISTER_DEVICETYPE2, &device2);

	if((device1==FSA9480_DEV_TY1_USB)||(device2==FSA9480_DEV_TY2_JIG_USB_ON)||(device2==FSA9480_DEV_TY2_JIG_USB_OFF))
		return 1;
	else
		return 0;
}

When the car dock is connected the fsa9480 device2 register is set to FSA9480_DEV_TY2_JIG_USB_ON, this is the 0x4 in the kernel logs I posted.

If you can code, just fork the code, fix it, test it and make sure it detects if there's power or not properly, then send a pull request.

I think I found something:
- Turn on auto-rotation via toogle in notification drawer
- Turn the phone in landscape mode and turn off the toogle
Now, the screen must turn to portrait but it's not. You must turn on the toogle to have a portrait screen again.
It's a small bug, not a big deal though

Originally Posted by FadeFx

Pawitp, i think the occassional bootloops are caused by offline charging, i just rebooted my device and unpluged it from charger while offline charging was starting and bam, bootloop...

Pawit, you read this?

------------------------------
tapatalked from Galaxy S

Originally Posted by nguyen47

I think I found something:
- Turn on auto-rotation via toogle in notification drawer
- Turn the phone in landscape mode and turn off the toogle
Now, the screen must turn to portrait but it's not. You must turn on the toogle to have a portrait screen again.
It's a small bug, not a big deal though

Why should this be a bug? If you turn auto-rotation off, it just doesn't rotate any more. I'm on slim and I also have this 'bug'.