Originally Posted by pongster

Nope. Just flash straight away from CWM.

What build are you coming from? That determines the partitions you set for NAND and may affect how much free space is left for Internal Storage.

I'm using JDMS 1.7 atm (which has the USB mass storage working properly btw...maybe you could hook up with those guys to figure out this little issue)

As far as i can remember i flashed a 250mb partition...i didn't mess with ext3 or ext4.

Is there anything i should do prior flashing your rom?

Originally Posted by ghostdog276

I'm using JDMS 1.7 atm (which has the USB mass storage working properly btw...maybe you could hook up with those guys to figure out this little issue)

As far as i can remember i flashed a 250mb partition...i didn't mess with ext3 or ext4.

Is there anything i should do prior flashing your rom?

JDMS is Gingerbread or Froyo? 250MB is way too big a system partition for this build.

You get more free space with 150MB.

Originally Posted by pongster

JDMS is Gingerbread or Froyo? 250MB is way too big a system partition for this build.

You get more free space with 150MB.

It's Gingerbread...

Ah, that's why i had such little space left Thank you...

Can i flash a 150mb partition over the existing partition? Sorry for being a pain in the butt, bro...

Maybe you could point me in the right direction...so much going on since NAND has been released...never had a chance to catch up

Another problem I've noticed.. The task bar/status bar turns white when you open an app. Eg. Market etc.. Makes it hard to read signal etc..

Sent from my HD2 using XDA App

Bluetooth battery drain issue

---

Hi Pongster,

i have also the bluetooth issue with a battery drain of ~60ma in standby.
At the moment this is pretty normal for stock roms. Only in Sense Roms that issue isnt. It is not a kernel problem, because i used the same Kernel in stock and in sense roms. For me it seems an issue of the lib-files or the firmware for the BCM4329.
You can reproduce the problem very simple - switch Bluetooth on, put htc in standby mode, wait 1 or 2 minutes until the BT autoscan is finish, switch htc on and have a look on currentwidget - you will see something around 60ma drain. Same procedure with BT off will show a current of 3 to 5.

I had done also some tests to change the relevant libs, bins and bt firmwarefiles from a sense rom to your's but i seems that i can't handle all dependencies.

Changed files are:
/lib/bluetoothdroid.so
/lib/bluetooth.so
/lib/libbluetoothd.so

/bin/bluetoothd
/bin/btld <- that file exists only in sense roms

/firmware/BCM4329B1_002.002.023.0511.0538.hcd
/firmware/fw_bcm4329.bin
/firmware/fw_bcm4329_apsta.bin
The firmware files will loaded through /bin/btld deamon in sense environment.
In the stock environment it seems that firmware will loaded through
"service hciattach /system/bin/brcm_patchram_plus --enable_hci --patchram /etc/firmware/bcm4329.hcd /dev/ttyHS0"

The hciattach deamon is commented out in sense firmware.

By changing all that files i get, when i start bluetooth, an error from org.bluez.Adapter and the bluetooth stack never come up.

If you want to do something on the problem, i will be happy to support you!

Best regards

trilu

Originally Posted by trilu

Hi Pongster,

i have also the bluetooth issue with a battery drain of ~60ma in standby.
At the moment this is pretty normal for stock roms. Only in Sense Roms that issue isnt. It is not a kernel problem, because i used the same Kernel in stock and in sense roms. For me it seems an issue of the lib-files or the firmware for the BCM4329.
You can reproduce the problem very simple - switch Bluetooth on, put htc in standby mode, wait 1 or 2 minutes until the BT autoscan is finish, switch htc on and have a look on currentwidget - you will see something around 60ma drain. Same procedure with BT off will show a current of 3 to 5.

I had done also some tests to change the relevant libs, bins and bt firmwarefiles from a sense rom to your's but i seems that i can't handle all dependencies.

Changed files are:
/lib/bluetoothdroid.so
/lib/bluetooth.so
/lib/libbluetoothd.so

/bin/bluetoothd
/bin/btld <- that file exists only in sense roms

/firmware/BCM4329B1_002.002.023.0511.0538.hcd
/firmware/fw_bcm4329.bin
/firmware/fw_bcm4329_apsta.bin
The firmware files will loaded through /bin/btld deamon in sense environment.
In the stock environment it seems that firmware will loaded through
"service hciattach /system/bin/brcm_patchram_plus --enable_hci --patchram /etc/firmware/bcm4329.hcd /dev/ttyHS0"

The hciattach deamon is commented out in sense firmware.

By changing all that files i get, when i start bluetooth, an error from org.bluez.Adapter and the bluetooth stack never come up.

If you want to do something on the problem, i will be happy to support you!

Best regards

trilu

Yeah, mixing and matching bt libs are hit and miss... hopefully once Nexus One gets 2.3.1 OTA BT issue will get solved.

Originally Posted by lippa

Another problem I've noticed.. The task bar/status bar turns white when you open an app. Eg. Market etc.. Makes it hard to read signal etc..

Sent from my HD2 using XDA App

Mine stays black... are you on all defaults?

Is there anyway to move the dalvik cache to sd-ext the same way darktremors a2sd+ works. Tried installing the patch but it won't work as apps2sdext is already preinstalled.

Very good build. my new daily driver.

Sent from my HD2 using XDA App

Hey I just wanted to try your build but a general process crashes immediately after booting. I could enter the key for sim card but not more!!!
I use now about 2 weeks a cyanogen mod what runs very good and I have a ext4 partition on sdcard.
What I saw after your build boots is for example the background image from the cyanogen build.
It seems that a lot of stuff from the sdcard and ext4 partition will be integrated when trying an new build and this could disturbe each other???!!! and maybe is
the rason that you build crashes?
So it is not so easy to flash a new build simply for trying or do I something wrong? Better to use 2 sdcards or formatting the disk?
But how to save the content on the ext4 partition than? If it is like that, it will not be easy to jump between builds!!!!

Maybe someone could clarify this a bit for me, or what you are doing when you want to try a different build cwm(zip)?

Originally Posted by idcom

Is there anyway to move the dalvik cache to sd-ext the same way darktremors a2sd+ works. Tried installing the patch but it won't work as apps2sdext is already preinstalled.

Very good build. my new daily driver.

Sent from my HD2 using XDA App

It would be possible but I'd need to install the original apps2sd mod by DT. I prefer the sd-ext method as modded by AdamG as it allows for slower sdcards to use the script as well.

Maybe you could try deleting the contents of init.d before installing the patch. Let me know how it goes.

Originally Posted by sascho

Hey I just wanted to try your build but a general process crashes immediately after booting. I could enter the key for sim card but not more!!!
I use now about 2 weeks a cyanogen mod what runs very good and I have a ext4 partition on sdcard.
What I saw after your build boots is for example the background image from the cyanogen build.
It seems that a lot of stuff from the sdcard and ext4 partition will be integrated when trying an new build and this could disturbe each other???!!! and maybe is
the rason that you build crashes?
So it is not so easy to flash a new build simply for trying or do I something wrong? Better to use 2 sdcards or formatting the disk?
But how to save the content on the ext4 partition than? If it is like that, it will not be easy to jump between builds!!!!

Maybe someone could clarify this a bit for me, or what you are doing when you want to try a different build cwm(zip)?

Its easy to jump between builds... use CWM and do a Nandroid backup before testing another build. If you don't like it, do a Nandroid restore. That's how I do my tests. If I like what I have I keep it and improve; if not I restore my last Nandroid Backup. Easy Peasy.

The crashing happens because you probably did not do a full wipe of data, cache and dalvik-cache before installing.(which I highly recommend)

Personally, I've had not a single crash from the time I've released the build... The version I have on is about 7 days old and I just do incremental updates as I have released on the first page.

I suggest you do a Nandroid backup and Install everything fresh.