As many PDA2k users might have noticed by now, a file named BtTrayLog.txt found in the main directory on the device keeps expanding endlessly and thus eats every bit of memory you might have. There is no setting that you can change to solve this nor does deleting this file keeps it from popping back again.
I found a temporary solution and it has been working perfectly for the last few days. You can replicate my solution by following these steps:
1) Turn your Bluetooth on.
2) Start your "File Explorer" on your device and go to the main folder "My Device".
3) You will find a file named BtTrayLog.txt (when I first discovered this file it was 32 MB big!). Delete this file.
4) Close your File Explorer and wait for a few minutes.
5) Start your File Explorer again and you will find the same file again, although this time it should be very small (the smallest I could get it was 866 B only.)
6) Click and hold on it until the submenu appears and then select "Properties".
7) Check the "Read only" box and click "Ok".
Voila! The file will remain but its size will not change. The solution is a little primitive but it will spare you the effort of having to delete the file every couple of days. I list it here for the benefit of other users until CD fixes this issue in its upcoming ROM upgrade, whenever that may arrive.
Related
Hi all
a recent issue seems to be affecting my xda artemis (o2 branded). None of my reminders, appointments , alarms and tasks are alerting me when I have set them to. The sounds and notifications are on as is the display message set to on. The volume is also on and in all other respects the device seems to be working accurately.
I have made no changes to the ROM or Directory, no new applications have been added and none removed or altered.
Further symptoms appear to be that when performing a soft reset about 1x a week the device will sound all manner of alarms and reminders, but fails to display any notification of what they are for. I have to wait 10 - 15 minutes for this annoyance to stop before I can continue to use my device normally.
I use wisbar advance 2.8.0.3 beta and have had no problems with it so far. The above problems occur whether or not wisbar is running.
Thoughts comments and solutions as always welcome.
Cheers
Pete
Please look into the \Windows\StartUp folder and write down the list of LNK files you have there. Maybe something is missing.
BTW: which PIM application are you using?
The .lnk folders showing in the Windows\StartUp folder are:
services - 29b
SpbBackupRunner - 51b
WisBarAdv - 65b
I am using SPB Pocket Plus v3.2.0 - Build 5561 as my PIM
Pete
Strange, just 3 LNK files there? But OK, try this...
Attached you can find ZIPed poutlook.lnk file.
Unzip and put "poutlook.lnk" into \Windows\StartUp\ folder.
Finally do soft-reset of your device and check if it helps or not.
Stranger and stranger....
the last list I posted was generated through Resco file explorer, but when I looked in the start ups folder via activsync the following list appeared...
btdwake - 25b
CapNotify - 27b
poutlook - 14b
sddaemon - 26b
services - 29b
SPBbackupRunner - 51b
WiFiInit - 26b
WisBarAdv - 65b
so I guess this means I dont need to put poutlook in there after all huh?
Any more thoughts please?
Cheers
Pete
Try this trick:
1. Go to Settings -> Power and set your device to NOT switch automatically off in <amount> minutes. The goal the to avoid the sleep mode into which the device is automatically put in after few minutes of innactivity.
It means, now your device will not go to sleep (display off etc.) automatically - we need it for our test. You can revert to current values after test.
Also note: not not switch the device off during tests (do not press Power button etc.)
2. Set the date to some date in the past e.g. to 10.1.2006 and the time to 23:45. Say OK and let say after 2 minutes do soft-reboot (restart).
3. The device will re-start and the time should be ca. 23:50. That's fine. Now wait (the device must not sleep still - don't forget, so do not switch it off etc.) until midnight i.e. 0:00 and better to 0:10 (10 mins. past midnight).
4. Now set the date back to NOW back, wait few minutes and do the soft-reset again. When you are back perform the last step.
5. Using some FileExplorer run following EXEcutables:
- CLOCKNOT.EXE located in \windows (hidden ROM file) - this will resync the clock with the CPU
- CALNOT.EXE in \windows (hidden ROM file) - this resync the calendar (and notification database)
6. Wait few minutes. Go to Settings -> Power and set your device back to switch automatically off in <previous value> minutes.
7. Pray.
Any progress?
Ok I finally found the time to sit down as you suggested and it works!!! I didn't have to do the run executables bit at the end as it all just seemed to work straight off, and I'm well chuffed.
Many Thanks
Pete
Fine, you are welcome.
- Hi. I bought recently an s620 locked on BT. I unlocked it using an internet
service. My problem is that a "BT Set Up" pops up when I turn on the phone and
it sends an sms to BT, trying to get the total broadband setup.
How can I stop it ? thanks
AlexNet! said:
- Hi. I bought recently an s620 locked on BT. I unlocked it using an internet
service. My problem is that a "BT Set Up" pops up when I turn on the phone and
it sends an sms to BT, trying to get the total broadband setup.
How can I stop it ? thanks
Click to expand...
Click to collapse
2 options hard-reset as you don't need the BT software on there, the better option follow this guide UPGRADE to 6.1 with PICS & LINKS
Or if you really want to keep the BT Bloatware that uses up RAM and slows down the phone then here you go:
Go into File Explorer (Start > File Explorer) press the Up command (left soft key) then navigate to 'Program Files' then to 'BTNetworks' in the folder there is an app called "HandsetSetupWizard" rename the file by pressing the right soft key > edit > rename. Rename it to something like 'HandsetSetupWizard.old" this will stop it running on boot up.
stylez said:
2 options hard-reset as you don't need the BT software on there, the better option follow this guide UPGRADE to 6.1 with PICS & LINKS
Or if you really want to keep the BT Bloatware that uses up RAM and slows down the phone then here you go:
Go into File Explorer (Start > File Explorer) press the Up command (left soft key) then navigate to 'Program Files' then to 'BTNetworks' in the folder there is an app called "HandsetSetupWizard" rename the file by pressing the right soft key > edit > rename. Rename it to something like 'HandsetSetupWizard.old" this will stop it running on boot up.
Click to expand...
Click to collapse
thanks!!!!!!
The problem solved very easily after all. Just removed the BTSetupWM6 from the programm files.
Every time I tempt to browse to this directory via ActiveSync or Mobile Device Center, the attempt hangs explorer and I have to disconnect the PPC, next I have to reset it as it is almost 100% non-responsive. I can browse any other directory without issue, but I need to get to Start Menu to adjust and sort the programs as the default arrangement sucks.
ERIC
egandt said:
Every time I tempt to browse to this directory via ActiveSync or Mobile Device Center, the attempt hangs explorer and I have to disconnect the PPC, next I have to reset it as it is almost 100% non-responsive. I can browse any other directory without issue, but I need to get to Start Menu to adjust and sort the programs as the default arrangement sucks.
ERIC
Click to expand...
Click to collapse
The \windows root dir does take forever to load, be patient especially on older PC.
Hello all
A little bit of background info:
I have owned my Desire for over 2 years now & recently decided to s-off/root/flash (primarily to gain some memory space- the only real short coming of the Desire in my opinion).
I went from stock Gingerbread 2.3.7 to Cyanogenmod 7.1 & so have taken my first step into a larger world!
In that world I encountered problems - no signal, no gps, no bluetooth, radio flashing etc. - all of which I managed to find solutions for by reading the excellent resources of xda-developers.
So having collated the enormous & varying wealth of info & getting my Desire fully functional - I wanted to give something back.
It's not much (though I haven't seen it anywhere as a solution?), but it may help someone somewhere :fingers-crossed:
## If you just want to cut to the chase- the procedure that worked for me is at the end of the post! ##
About my phone:
Android version 2.3.7
Cyanogenmod version 7.1.0
Baseband Version 32.56.00.32u_5.17.05.23
Kernel Version 2.6.37.6-cyanogenmod-geb50077
As stated, gps & signal were fixed with a simple radio flash from 5..11.05.14 - 5.17.05.23
but bluetooth remained unable to connect. My 2 devices were in the list showing as 'Paired but not connected'
Clicking on them they would say 'connecting' but that process would end with no error or message & no connection made.
The only long press option on them was 'unpair' - so no option to delete & try again.
I then found a potential fix which is I assume is fairly well known BUT I could not get it to run:
SOLUTION (copied from external site)
I ran the Terminal app and entered
'su'
(App requests root permissions, grant them). Then I went to the device's bluetooth settings with
'cd /data/misc/bluetoothd'
(Note the 'd' at the end). There I found a directory named by the bluetooth chip's ID, in my case '38:E7:B8:45:21:a4'. I renamed this directory
'mv 3* hidden'
Turned bluetooth off and back on and could use bluetooth again.
Every time I ran the terminal I could get su to work, with permissions granted as confirmed in the toast message that would pop up- BUT whenever I typed 'cd /data/misc/bluetoothd' I only ever got 'Permission Denied'.
All the fix posts I read about this pointed towards root & su permissions not working correctly but mine certainly were. I had tried all the usual fixes of un-applying/re-applying SU permissions, root etc.
I also tried the same commands through adb, all with the same result.
It then occurred to me that the Terminal was only changing a folder property so I used 'ROM Toolbox Pro' -> 'Root Browser' to find the folder in question ('38:E7:B8:45:21:a4' in my case).
It became apparent that the path given in the 'fix' was incorrect (for my Desire GSM at least).
The folder I was looking for was actually in 'd/data/bluetoothd' - so the 'permission denied' error was because the path was incorrect, not that SU permissions were not granted!
Before I actually tried that correct path though- I noticed that to make files hidden the '.' (full stop) prefix is added to the start of the file or folder name.
I used Root Browser to long-press on the '38:E7:B8:45:21:a4' folder & then 'rename' from the menu - making the folder name '.38:E7:B8:45:21:a4' (note the full stop at the start.)
I then re-enabled bluetooth - this time noticing that both my paired devices were no longer there (this is good!). I made the Desire discoverable then did a scan...success!
Both my devices paired & connected exactly as they should. I now notice in Root Browser that the file structure has also changed with there being no 'bluetoothd' folder at all.
I also imagine that entering the correct folder path in terminal or adb would produce the same results, though I cannot confirm this as the procedure described had already worked for me.
So, long story short:
1. Make sure bluetooth is turned OFF then open Rom Toolbox Pro -> Root Browser (or any root browser with su permissions I guess?)
2. Navigate to the folder d/data/bluetoothd/38:E7:B8:45:21:a4 (#Note: your '38:E7:B8:45:21:a4' folder will probably be named differently)
3. Long press on the '38:E7:B8:45:21:a4' folder. (or whatever yours is called)
4. From the pop up menu - select 'Rename'
5. Add a full stop '.' at the beginning of the folder name Eg '.38:E7:B8:45:21:a4' (Keep the rest of the name as it was)
6. Turn on Bluetooth - in 'Bluetooth settings' make your device discoverable & note that if any paired devices were present, they should now be gone from the list.
7. Scan for bluetooth devices, obviously making sure they are also switched on & discoverable! (if it doesn't automatically)
8. Your devices should now show up, ask to pair, ask for pin numbers if needed & then connect automatically.
If this has been covered elsewhere please accept my apologies, & delete the post if it's deemed as clutter- I was merely trying to help
Dog909 said:
Hello all
A little bit of background info:
I have owned my Desire for over 2 years now & recently decided to s-off/root/flash (primarily to gain some memory space- the only real short coming of the Desire in my opinion).
I went from stock Gingerbread 2.3.7 to Cyanogenmod 7.1 & so have taken my first step into a larger world!
In that world I encountered problems - no signal, no gps, no bluetooth, radio flashing etc. - all of which I managed to find solutions for by reading the excellent resources of xda-developers.
So having collated the enormous & varying wealth of info & getting my Desire fully functional - I wanted to give something back.
It's not much (though I haven't seen it anywhere as a solution?), but it may help someone somewhere :fingers-crossed:
## If you just want to cut to the chase- the procedure that worked for me is at the end of the post! ##
About my phone:
Android version 2.3.7
Cyanogenmod version 7.1.0
Baseband Version 32.56.00.32u_5.17.05.23
Kernel Version 2.6.37.6-cyanogenmod-geb50077
As stated, gps & signal were fixed with a simple radio flash from 5..11.05.14 - 5.17.05.23
but bluetooth remained unable to connect. My 2 devices were in the list showing as 'Paired but not connected'
Clicking on them they would say 'connecting' but that process would end with no error or message & no connection made.
The only long press option on them was 'unpair' - so no option to delete & try again.
I then found a potential fix which is I assume is fairly well known BUT I could not get it to run:
SOLUTION (copied from external site)
I ran the Terminal app and entered
'su'
(App requests root permissions, grant them). Then I went to the device's bluetooth settings with
'cd /data/misc/bluetoothd'
(Note the 'd' at the end). There I found a directory named by the bluetooth chip's ID, in my case '38:E7:B8:45:21:a4'. I renamed this directory
'mv 3* hidden'
Turned bluetooth off and back on and could use bluetooth again.
Every time I ran the terminal I could get su to work, with permissions granted as confirmed in the toast message that would pop up- BUT whenever I typed 'cd /data/misc/bluetoothd' I only ever got 'Permission Denied'.
All the fix posts I read about this pointed towards root & su permissions not working correctly but mine certainly were. I had tried all the usual fixes of un-applying/re-applying SU permissions, root etc.
I also tried the same commands through adb, all with the same result.
It then occurred to me that the Terminal was only changing a folder property so I used 'ROM Toolbox Pro' -> 'Root Browser' to find the folder in question ('38:E7:B8:45:21:a4' in my case).
It became apparent that the path given in the 'fix' was incorrect (for my Desire GSM at least).
The folder I was looking for was actually in 'd/data/bluetoothd' - so the 'permission denied' error was because the path was incorrect, not that SU permissions were not granted!
Before I actually tried that correct path though- I noticed that to make files hidden the '.' (full stop) prefix is added to the start of the file or folder name.
I used Root Browser to long-press on the '38:E7:B8:45:21:a4' folder & then 'rename' from the menu - making the folder name '.38:E7:B8:45:21:a4' (note the full stop at the start.)
I then re-enabled bluetooth - this time noticing that both my paired devices were no longer there (this is good!). I made the Desire discoverable then did a scan...success!
Both my devices paired & connected exactly as they should. I now notice in Root Browser that the file structure has also changed with there being no 'bluetoothd' folder at all.
I also imagine that entering the correct folder path in terminal or adb would produce the same results, though I cannot confirm this as the procedure described had already worked for me.
So, long story short:
1. Make sure bluetooth is turned OFF then open Rom Toolbox Pro -> Root Browser (or any root browser with su permissions I guess?)
2. Navigate to the folder d/data/bluetoothd/38:E7:B8:45:21:a4 (#Note: your '38:E7:B8:45:21:a4' folder will probably be named differently)
3. Long press on the '38:E7:B8:45:21:a4' folder. (or whatever yours is called)
4. From the pop up menu - select 'Rename'
5. Add a full stop '.' at the beginning of the folder name Eg '.38:E7:B8:45:21:a4' (Keep the rest of the name as it was)
6. Turn on Bluetooth - in 'Bluetooth settings' make your device discoverable & note that if any paired devices were present, they should now be gone from the list.
7. Scan for bluetooth devices, obviously making sure they are also switched on & discoverable! (if it doesn't automatically)
8. Your devices should now show up, ask to pair, ask for pin numbers if needed & then connect automatically.
If this has been covered elsewhere please accept my apologies, & delete the post if it's deemed as clutter- I was merely trying to help
Click to expand...
Click to collapse
I can't find folder *data* in folder *d*. I have a separate folder *data*. There is a folder named *bluetooth* in folder *d*. It also didn't work for me.
EDIT: SOLVED. Read below under the magenta EDIT: section.
---------------------------------------------------
Followed engine95's rooting guide to root ZV9 LGOG. Initially I sought out to root the LGOG only to turn off the camera shutter sound from sharkboy0901's thread here. But you have to root it first. I've spent over 3 hours trying to figure this stuff out before bothering you guys.
I rooted the device but am unsure if it worked. I went through fiddy619's directions here:
1. Unzip the zip file
2. Make sure USB Debugging is on, and your are in Charge only Mode
3. Run the CurrentRoot.bat, wait for the prompt.
4. Change to MTP Mode
5. Just ignore when your computer asks how to view files on your device.
6. Press enter in the CMD prompt to continue.
7. Done
Click to expand...
Click to collapse
And I thought I was set. Checked apps and SuperSU was not installed. Does it have to be? I was confused on what directions needed to be followed after this. By the way, I did install the drivers beforehand. The prompts appeared to work and the phone rebooted but SuperSU was not there.
I opened up ES File Explorer anyway to see if I can edit the file to disable the camera shutter sound. Went under settings to allow "Root Explorer" but keeps telling me, "Sorry test failed. This feature cannot run on your phone." If I can't check that box, I cannot allow it to check "Mount File System" which will allow me read and write permissions to turn the camera shutter sound off as related to sharkboy0901's thread. Any help would be greatly appreciated.
---------------------------------------------------
EDIT:
Solved! All that I needed was a simple restart from my PC. Before I didn't restart after I installed the drivers which I guess was a necessary thing after all. Perhaps some users didn't have to restart but I did. After the restart, ran through fiddy619's directions to root it again (properly this time) and afterward, saw that SuperSU was installed which is also necessary to make sure that it worked.
Opened up ES File Explorer to change the settings to enable "Root Explorer" and "Mount File System" which worked this time without fail... Then went ahead and followed sharkboy0901's direction to change the code to disable the camera sound. Saved the changes.. Rebooted the phone and made sure the sound profile was set to either Silent or Vibrate, snapped a picture, silent! It also disabled the shutter sound in Instagram which is great. (Note: If your sound profile is on to enableall sounds, you will hear the shutter sound.)
Excellent, I hoped this helps someone else.