Apache WM6.1 Kitchen CE OS 5.2.19716 (Build 19716.1.0.0) - UPDATED 20080308

[bpiermat]

I am getting an invalid password as well

[colonel]

Originally Posted by tinycandi

We have tun into a problem with the 6.1 upgrade.

For some reason when making the device choices in the kitchen, under bootloader v1.04 you cannot choose NoID under the RUU...the only choice is standard. However, it doesn't work under standard...it ends in error 120: country id error.

So far we haven't been able to find ANY remedies to this.

Sorry I missed you in chat. You can always click Here in my signature and join the ppckitchen room. Find me tomorrow and we will get you going.

[buttter]

Just to say thanks, works like a charm and i´m using it fine in Mexico with Iusacell.

[Gervy]

Originally Posted by gguruusa

I expect new builds hourly. The developer sucks, however, so I get let down a lot.

LULZ


...

[jnjn]

confirmed, resco explorer in the recent kitchen cannot access cifs (samba/windows share) shares. install resco explorer manually, and everything is accessible. could somebody check and fix this?

[edufur]

Originally Posted by gguruusa

While talking on the phone you're going to have high usage, and it's independent of OS. It's the idle usage we want to know. Yours sounds kind of high. Check if you have a data connetion active, remove any today items, or as a last resort, build a bare rom and see if it doesn't drop substantially. If it does, add your OEMs back in slowly and see when it picks back up.

No. he is seeing the problem that soooo many others are seeing with this build. myself included. Current theory is that it is a Bluetooth drain and it is especially problematic when a BT device is not in range. this is just a one area of a problem. my battery life isnt that good even when BT is off. I have a new hi-cap battery that has worked fine with previous builds. we have developed a thread specific to this battery drain issue. i suggest the devs have a look at that thread and start experimenting / asking questions.

[sscholar]

Originally Posted by edufur

No. he is seeing the problem that soooo many others are seeing with this build. myself included. Current theory is that it is a Bluetooth drain and it is especially problematic when a BT device is not in range. this is just a one area of a problem. my battery life isnt that good even when BT is off. I have a new hi-cap battery that has worked fine with previous builds. we have developed a thread specific to this battery drain issue. i suggest the devs have a look at that thread and start experimenting / asking questions.

Indeed. With a bare bones setup, no today items, no backlight and a 6-month old stock 1350 mAh battery, acbPowerMeter averaged about 40 mA idle. If I charge the battery completely, make a call and leave the phone connected with the backlight and bluetooth off until the battery dies, power usage averages 350 mA and drains in 50 minutes. Again, I did not see this kind of battery drain until I moved to 6.1.

Any help is indeed appreciated, but it may just be a sign to move on to a new device...

[ran-o-matic]

Originally Posted by sscholar

Indeed. With a bare bones setup, no today items, no backlight and a 6-month old stock 1350 mAh battery, acbPowerMeter averaged about 40 mA idle. If I charge the battery completely, make a call and leave the phone connected with the backlight and bluetooth off until the battery dies, power usage averages 350 mA and drains in 50 minutes. Again, I did not see this kind of battery drain until I moved to 6.1.

Any help is indeed appreciated, but it may just be a sign to move on to a new device...

So at 350 mA draw while connected voice only (and power meter running too, of course), you drain a 1350 mAh battery in 50 minutes? How can that be?! The power has to be going somewhere...

[edufur]

Originally Posted by ran-o-matic

So at 350 mA draw while connected voice only (and power meter running too, of course), you drain a 1350 mAh battery in 50 minutes? How can that be?! The power has to be going somewhere...

I am not sure if I know what you are asking... but I will say this (about my calls)... I have a lite build and I shut down all tasks, ran the power meter, started a call, and it was running at 323mA for the call. I dont know if this is normal, but that is what I am seeing. Has anyone else checked? Maybe I should roll back to 5.0 and run power meter on a call in that build.

[digit]

What's he's saying is that 350 mAH would drain a 1350 mAH battery in around 4 hours, not 50 minutes.