CM7 Nightlies Topic [Nightly 28- 21/03/2011]

[Guest Scoopading]

Good morning guys. Is there a possibility to backup with all my apps Titanium Backup before the full wipe? Running JJ9 atm

Thank you very much

As said, you will run into issues if you want to restore the data with the apps. However you can use Titanium just to back up the actual apk files (which it places inside a gzip file) and just ignore the extra data files (which it places in seperate gzipped files). You can then choose to add the apk's to the install zip, so that your apps will install automatically. Then you're just left with configuring them again, but you won't need to redownload them from the market etc.

[Guest Maxxo]

Nope, when upgrading from FroYo to Gingerbread (or from one version to another in general)

you'll get yourself into trouble when you just do a full restore.

You can try to restore bits selectively, but chances are high you'll end up with incompatible

stuff causing issues, so to be on the safe side reinstall the apps.

Allright, thanks. Do I still have to use an alternative kernel (like this one http://android.modaco.com/content/zte-blad...al-cm7-kernel/) or is this fixed with N19?

[Guest targetbsp]

Nightly 19 with the fixes we were all looking forward too the past few days, rom manager back working, clockwork 3.0.1.4, Swype supporting UK English... It's like Christmas. :D

Edited March 14, 2011 by targetbsp

[Guest alex1alex2alex3alex4]

I believe the procedure is to report it on the Cyanogenmod nightly builds thread

Thanks, reported there.

[Guest alex1alex2alex3alex4]

Allright, thanks. Do I still have to use an alternative kernel (like this one http://android.modaco.com/content/zte-blad...al-cm7-kernel/) or is this fixed with N19?

All of this is said to be included in N19, afaik.

[Guest Scoopading]

The battery being better is because the serial port support was dropped. And now, bluetooth's broken. I hope a balance can be found somehow.

How come you're so sure it's because of that? I would've assumed the battery is a lot better because the CPU's ondemand governor is now behaving correctly and not keeping the clock higher than need be whilst sleeping? Seems a more likely reason to me...

[Guest alex1alex2alex3alex4]

Would anyone know if bluetooth worked on N18? Ive just upgraded from N15 to N19 and sadly depend on bluetooth in my car.

Dunno, I upgraded from N17 to N19, but as I absolutely can't live without BT I'll probably revert

to N18 and apply the alternative kernel and let you know, but I assume it does work with N18.

[Guest css771]

How come you're so sure it's because of that? I would've assumed the battery is a lot better because the CPU's ondemand governor is now behaving correctly and not keeping the clock higher than need be whilst sleeping? Seems a more likely reason to me...

TomG mentioned something about it causing wakelocks. And in any case, I'm still on RC2 with the new kernel. I don't have those ondemand cpu fixes. Still standby battery life seems to be fixed and bt is not working. So I assumed it has to do with the kernel and the serial port stuff.

[Guest fonix232]

Just to mention, I'm still on N17, with t0mm13b's first kernel. What I got this night:

Phone was left with 83% shown battery at 23:18. Put into sleep mode (both the phone and myself) and woke at 9:30. Battery was at 75%. So approx. 10 hours discharge was 8%. What makes, 0.8%/hour. Pretty good, isn't it? Now let's see N19 :D

[Guest alex1alex2alex3alex4]

TomG mentioned something about it causing wakelocks. And in any case, I'm still on RC2 with the new kernel. I don't have those ondemand cpu fixes. Still standby battery life seems to be fixed and bt is not working. So I assumed it has to do with the kernel and the serial port stuff.

Thanks for the heads up, I can forget about trying N18 + new kernel then :D

[Guest LordKickapoo]

Messing with the DSP manager didnt help, in phone call volume still annoyingly loud :D

Edited March 14, 2011 by LordKickapoo

[Guest Odes1]

How is the proximity in R19? Do we still need the workaround?

[Guest forney27]

Dunno, I upgraded from N17 to N19, but as I absolutely can't live without BT I'll probably revert

to N18 and apply the alternative kernel and let you know, but I assume it does work with N18.

Ive downgraded to N18 and bluetooth does work.

[Guest DonJamal]

How is the proximity in R19? Do we still need the workaround?

works

[Guest css771]

Ive downgraded to N18 and bluetooth does work.

Are you using the new kernel from N19 or the old one?

[Guest forney27]

Are you using the new kernel from N19 or the old one?

Old one

[Guest Acathla-]

Here a log of the bluetooth problem in N19 in case anything fancies working on it:

03-14 10:53:58.616: DEBUG/BluetoothService(202): Bluetooth state 10 -> 11

03-14 10:53:58.636: VERBOSE/BluetoothEventRedirector(674): Received android.bluetooth.adapter.action.STATE_CHANGED

03-14 10:53:58.646: INFO/bluedroid(202): Starting hciattach daemon

03-14 10:53:58.656: INFO/ActivityManager(202): Start proc com.android.bluetooth for broadcast com.android.bluetooth/.opp.BluetoothOppReceiver: pid=884 uid=10005 gids={3003, 3002, 3001, 1015}

03-14 10:53:58.766: ERROR/qcom-bluetooth(894): /system/etc/init.bt.sh: Bluetooth QSoC firmware download failed: exit code 1

03-14 10:53:58.896: DEBUG/szipinf(884): Initializing inflate state

03-14 10:53:58.956: INFO/ActivityThread(884): Pub com.android.bluetooth.opp: com.android.bluetooth.opp.BluetoothOppProvider

03-14 10:53:58.996: INFO/ActivityManager(202): No longer want com.google.android.apps.uploader (pid 726): hidden #16

03-14 10:53:59.006: DEBUG/SettingsAppWidgetProvider(674): Widget is from a previous version... Let's update

03-14 10:53:59.006: DEBUG/SettingsAppWidgetProvider(674): No instances yet... Wait for at least one instance to exist before adding global settings

03-14 10:54:06.746: DEBUG/WifiService(202): acquireWifiLockLocked: WifiLock{NetworkLocationProvider type=2 binder=android.os.BinderProxy@408e7110}

03-14 10:54:08.376: INFO/wpa_supplicant(282): CTRL-EVENT-SCAN-RESULTS Ready

03-14 10:54:08.846: ERROR/bluedroid(202): bt_enable: Timeout waiting for HCI device to come up

03-14 10:54:08.846: DEBUG/BluetoothService(202): Bluetooth state 11 -> 10

03-14 10:54:08.866: VERBOSE/BluetoothEventRedirector(674): Received android.bluetooth.adapter.action.STATE_CHANGED

[Guest The Soup Thief]

Anyone else having problems connecting their phone via USB to a PC?

This has worked fine previously (all drivers on the PC are installed) all through the ROMs I've used before, but I was just gonna squirt some files over (after installing N19) and the computer's not recognising the phone. Orange android showing on the phone as it should, indicating USB storage in use, but the computer won't play ball

Anyone else found this?

[Guest andycanada]

Anyone else having problems connecting their phone via USB to a PC?

This has worked fine previously (all drivers on the PC are installed) all through the ROMs I've used before, but I was just gonna squirt some files over (after installing N19) and the computer's not recognising the phone. Orange android showing on the phone as it should, indicating USB storage in use, but the computer won't play ball

Anyone else found this?

I am able to connect and the sd card shows as being mounted on my computer. files are also accessible

[Guest Deepeh]

Hey guys is the new kernel included in N19?

Cheers :D

[Guest targetbsp]

I am able to connect and the sd card shows as being mounted on my computer. files are also accessible

Same. Windows installed it a new driver for it so something has obviously changed in the way it identifies itself to the PC but it worked fine.

Now carrying out a standby battery life test. :D

[Guest forney27]

Anyone else having problems connecting their phone via USB to a PC?

This has worked fine previously (all drivers on the PC are installed) all through the ROMs I've used before, but I was just gonna squirt some files over (after installing N19) and the computer's not recognising the phone. Orange android showing on the phone as it should, indicating USB storage in use, but the computer won't play ball

Anyone else found this?

I did have a bit of a problem too, just remove the usb from your phone and put if back in and that should work.

[Guest The Soup Thief]

I am able to connect and the sd card shows as being mounted on my computer. files are also accessible

Thanks andyincanada - must be a problem this end rather than w n19

I'll get fiddling!

EDIT

Unplugged and plugged in again and all's good - thanks tagetbsp and forney

Edited March 14, 2011 by The Soup Thief

[Guest devilkazuya]

Hello,

Im on N19, fresh install coming from Froyo and can confirm:

works:

proximity sensor

usb file transfer

dont work:

bluetooth

Just to point out in CM settings there is option for trackball wake which probly needs to change to menu wake for obvious reasons.

[Guest chimas]

Messing with the DSP manager didnt help, in phone call volume still annoyingly loud :(

use your headset. :D

problem solved.