|
||||
I am using 1.6. It works fine with 3.3, the issue is bluetooth and vc1.6 with 3.3 . It will work the first time, but if you turn bluetooth on and off via comm manager a few times, then soft reset, the bluetooth becomes unresponsive (stuck on or off).
We think this is only an issue in Kitchen burned roms, not Helmi's .exe build. Which are you using? |
|
||||
I think your assumptions are correct. I did not have this issue with helmis build at all.
I now flashed to colenels with vzw ext rom. I think it may have too much included for me. Now there is this on the FTP helmi_Apache_kitchen_3.5rev1.zip rev1.. what was changed at this point. |
|
||||
There are no changes in the content of that file from the one I uploaded earlier. I am just trying to determine the appropriate naming for aku 3.5 as i do not want to take more credit than is due. I am awaiting Helmi's response to see if that is more appropriate. If so i will update the link in the first post and delete the other file from the FTP.
|
|
||||
VC must be overwriting a .dll or something. IMCOKEMAN said he would try to take a look at it when he gets around to it (trying to resolve USB is a priority). I will poke around and see if I can figure it out as well.
|
|
||||
The only use for USB on this device is WM5storage to use it as a mass storage device. Other than that USB syncing is prehistoric with exchange and push. I can however understand why it should work.
Thanks for all the work IMCOKEMAN. |
|
||||
To those trying to figure out the USB issue, can you give us a better description of what is happening (for those of us who are still tinkering with 3.3).
For example, when you plug into the USB, is it trying to obtain a lan ip address, but unable to, or is it simply doing nothing? If it is trying to obtain a lan ip but can't, then the work around is to put the phone in flight mode, soft reset, and try to sync with it in flight mode. |
|
|
|