[ Kitchen ][ 3-5 ][ v1.6 R3 ][28232 / 23542 / 21893 / 21056] Calkulin's WVGA Kitchen

[TMartin]

Originally Posted by boodaka

i cooked a 21888 with manila 2.1 and the black slider, and the slider looks like this....anyone else have this issueof it being offset?

Did you use a Manila Options - 2.1 EXT or a Manila Options - 2.1.19xx EXT for the slider??

[shad0w77]

Originally Posted by TMartin

Did you use a Manila Options - 2.1 EXT or a Manila Options - 2.1.19xx EXT for the slider??

or Manila Options - 2.5 - Slider - Transparent?

[TMartin]

Originally Posted by shad0w77

or Manila Options - 2.5 - Slider - Transparent?

Because only only the Manila Options - 2.1.19xx - Slider EXT's will work with Manila 2.1.19213017.1

[froader]

Originally Posted by mswlogo

You don't have to turn it off and on all the time. Shut it off and on ONCE after reboot and power drain will go back to normal. Your right something is not right on the bluetooth but it seems stuck spinning it wheels on something at boot time. But by cycling bluetooth once it has normal battery drain. You can clearly see it using battery monitor. After boot it will drain 150ma forever. Toggle bluetooth and it drops to 50ma.

28014 booted right to 50ma.
23518 boots to 150ma and 50ma after you manually toggle BT.

It may be an ordering issue at startup. Perhaps if Bluetooth startup at boot could be delayed it work correctly out of boot.

I'm curious if this "spinning it's wheels" at boot is also the reason for it's fussy behavior I see when pairing. If I flash this again. I'm gonna try pairing after I toggle bluetooth.

When using the battery monitor you need to wait for things to settle down a bit. It's very repeatable and much quicker than waitng a day or two see if battery is good.

Battery should be anywhere from 40-60ma drain for good standby battery life.

Originally Posted by froader

Good input there. That's very strange.
"28014 booted right to 50ma." -are you saying this is with the new drivers also?
I am on 21888 and have the battery drain also. However, I did notice that a 23518 I built was extremely worse.

We will get this sorted soon!

Just built up a 21518 ROM and I see the drain even w/out BT on.
BT aside, this is strange, it wont drop down to 50mA like it does w/ 21888.
I even tried older BT drivers/stack and same result.

I still stick to my findings that the new BT drivers/stack are a battery drain compared to the older ones.

These are 2 separate issues.

[icon123]

Originally Posted by froader

Just built up a 21518 ROM and I see the drain even w/out BT on.
BT aside, this is strange, it wont drop down to 50mA like it does w/ 21888.
I even tried older BT drivers/stack and same result.

I still stick to my findings that the new BT drivers/stack are a battery drain compared to the older ones.

These are 2 separate issues.

You should try building a 23508 with the old bt drivers

[froader]

Originally Posted by icon123

You should try building a 23508 with the old bt drivers

I am happy with 21888 and the old drivers. No abnormal battery drain there.

I am interested in the threaded e-mail and 23508 doesn't have it.
From what I understand 23508 is similar to 23014, which is the last 6.5.3 ROM I built.

Edit: will do just to see if there is a diff w/ batt drain.


WAIT: Do you mean 28205 that was included in v1.33?

[Snager]

Originally Posted by morganlowe

Weird, mine blew up overnight... 23518 Sprint build, pretty bare. It was frozen and I popped out the battery to reset, now it wont get past the HTC boot screen. Going to try again, reflashing and redownloading the ROM to be sure its got all the right parts.

EDIT:

Looks like this is sorta the random hard reset thing listed in the Stickies, but not really. More of a hard freeze and no boot. I actually went back to my Modded 1.33 build for now. Going to flash 1.4 again later. It just sat on charge overnight, yesterday it seemed fine with everything. I only have resco explorer and I-nigma as extras installed so far.

your not the only one ...something seems to be wrong with 1.4 kitchen for me ...i get the random hard resets with 23xxx or 28xxxx ...I'm back to 1.33 kitchen and have not had a single auto hard reset

[icon123]

Originally Posted by froader

I am happy with 21888 and the old drivers. No abnormal battery drain there.

I am interested in the threaded e-mail and 23508 doesn't have it.
From what I understand 23508 is similar to 23014, which is the last 6.5.3 ROM I built.

Edit: will do just to see if there is a diff w/ batt drain.


WAIT: Do you mean 28205 that was included in v1.33?

I meant to say 23518, which does have threaded messaging. Sorry, damn build numbers.

[froader]

Originally Posted by froader

Just built up a 21518 ROM and I see the drain even w/out BT on.
BT aside, this is strange, it wont drop down to 50mA like it does w/ 21888.
I even tried older BT drivers/stack and same result.

I still stick to my findings that the new BT drivers/stack are a battery drain compared to the older ones.

These are 2 separate issues.

Originally Posted by icon123

I meant to say 23518, which does have threaded messaging. Sorry, damn build numbers.

Gotcha! Thats the build that I was reporting on.

Well, I brought in 28205 from the previous kitchen and built a ROM using consistent selections and the battery drops back to 50mA.

Like I said earlier - 23510 has battery issues compared to other builds

As well - The new BT drivers/stack drains the battery much faster than previous BT drivers/stacks

[icon123]

Originally Posted by froader

Gotcha! Thats the build that I was reporting on.

Well, I brought in 28205 from the previous kitchen and built a ROM using consistent selections and the battery drops back to 50mA.

Like I said earlier - 23510 has battery issues compared to other builds

As well - The new BT drivers/stack drains the battery much faster than previous BT drivers/stacks

Got it. I didn't think you tested a 23518 with the old bt drivers.


I think the Verizon provisioning in this (1.4) kitchen has some problems. I think I saw someone report that some pages back. I received a country code error and I couldn't get data working at all even after a *228. I replaced the VZW provisioning files with the ones from the 1.33 kitchen and it worked as usual. Any other Verizon folks running into problems with 1.4?