AD-41 headset volume regulation sensitivity !

Hi! I own Nokia 3250 and what's really annoying me is the headset's volume adjustment. It works terrible ! The sensitivity of buttons is so high that it's very difficult to change volume only one level up or down. I don't know if it applies only to this model, but I checked it on N70 and it worked fine. When the button is pressed, volumes goes one level up, then short pause and then up again. That's how it should work! But now there're no pauses, it changes so quickly that I can't adjust volume accurately when i'm in move. My firmware is 3.24. Maybe it's fixed in 4.14 ? I wish it is, otherwise I won't upgrade my phone, I don't want to lose high sound volume.
Has someone similar observations ?

He is not telling the truth. The headset is faulty.

Similar Messages

  • AD-41 headset volume adjustment sensitivity too hi...

    Hi! I own Nokia 3250 and what's really annoying me is the headset's volume adjustment. It works terrible ! The sensitivity of buttons is so high that it's very difficult to change volume only one level up or down. I don't know if it applies only to this model, but I checked it on N70 and it worked fine. When the button is pressed, volumes goes one level up, then short pause and then up again. That's how it should work! But now there're no pauses, it changes so quickly that I can't adjust volume accurately when i'm in move. My firmware is 3.24. Maybe it's fixed in 4.14 ? I wish it is, otherwise I won't upgrade my phone, I don't want to lose high sound volume.
    Has someone similar observations ?

    He is not telling the truth. The headset is faulty.

  • N73 ME Headset volume Problem

    Hi All Nokia Users
    I have a Problem with my N73 ME Headset volume
    it's too low with music player
    even when connect it with any speakers its too low compared with any other mobile
    but when i try to make a call its and play musics it's so loud (i loved it) but i can't do a call every time i hear music on the speakers.
    so i hope there is a way to keep the speakers loud like in the call
    i think the problem is not the speakers (it's amazing with other mobiles)
    and not the headset because in calls it's perfect
    i think there is a limit or something should be modified
    i tried to maximize the equalizer and turned on the stereo, loudness and the 3d tunes
    the same thing
    i thought ME is made for Musics and the Musics needs a speakers
    and thanks for anyone can help me by a way or another (but pls don't say go to nokia center)
    (sorry for the bad language)
    My Device Details
    V 4.0839.42.2.1
    27-09-2008
    RM-133
    Nokia N73  (08)
    Message Edited by gendows on 06-Jun-2009 08:01 PM

    Nokia has decreased the volume level due to European Union health regulations. Apple's new iPods are also coming with decreased volume.  I know this really sucks,
    ok, But this is my phone and my ears, Right?
    i know that it shouldn't be loud
    so i well make the loud low
    but some times i need to make it loud, for just me i'm free of doing wut i want
    just like cigarets and alchol
    finally i'm not under the European Union health regulations
    i'm from egypt

  • Volume regulation problems

    Hi, I have a problem with volume regulation. When I leave my MacBook Pro and I restart working after the stand-by black screen, if I try to turn up or down the volume pressing F11 and F12 it doesn't work... I can see only the amplifier logo with the interdiction symbol. The only solution I found is to reboot the system.
    My MacBook Pro version is OS X Yosemite 10.10.1 and it happens if earphones are connected or disconnected. This problem didn't happen when I had Snow Leopard.
    Has anyone an idea about that?

    1. Reset PRAM.  http://support.apple.com/kb/PH14222
        Do this twice
    2. Reset SMC.     http://support.apple.com/kb/HT3964
        Choose the method for:
        "Resetting SMC on portables with a battery you should not remove on your own".

  • N73 - headset volume

    Hi can anybody help me I have just received my N73 happy with it so far but then tried to watch tv on it to find that the volume was so low I could not hear anything - I had maxed all the volume settings including the headset.
    also the headset is not great due to the mic being so low down that you have to hold it near your mouth to speak on it has anybody used an alternative particularly with less wires to tangle.
    I also have tomtom 6 for windows and symbian - will this run on a n73?
    Thanks
    Sam

    Nokia has decreased the volume level due to European Union health regulations. Apple's new iPods are also coming with decreased volume.  I know this really sucks,
    ok, But this is my phone and my ears, Right?
    i know that it shouldn't be loud
    so i well make the loud low
    but some times i need to make it loud, for just me i'm free of doing wut i want
    just like cigarets and alchol
    finally i'm not under the European Union health regulations
    i'm from egypt

  • How to adjust bluetooth headset volume in mediapla...

    Hi,
    I've a problem with lovely E75. I just got a new bluetooth headset (HBH-IS800 SonyEricsson) without any volume control. In a normal call the volume adjust works perfect, but in the mediaplayer the volume is to loud even if I press the lower buttom to it says 10% in the display.
    I also have the same problem with systemsounds (lika SMS) that plays in the BT headset, they are to load.
    Is it possible to change the output volume from this media applications? I cant find any help in the manual or menusystems.
    Rgds
    Olof
    Headset:
    http://www.sonyericsson.com/cws/products/accessories/overview/hbh-is800?lc=sv&cc=se

    I beg to differ. If SE implements the basic BT protocol set and Nokia will recognize this, and connects, then Nokia's work is done. Nokia is not required to support SE headset but is required to support the BT standards. The idea is to get you to purchase an SE phone over a Nokia phone and vise versa. To not understand this is to miss out on the basics of business fundamentals. 
    While it may be a great headset, personally I like the fact that I can use my much better headphones (Shure SE 530's) with the Nokia BH-214. I had the SE HBH-DS220 but got rid of it because it too had a very strange BT protocol that would not allow it to connect until music was streaming from the phone. The guys at the SE shop acknowledged this as normal behavior between manufacturers. If you do not believe this, go to and SE shop, or Nokia, or both and ask them to explain it to you.
    Show the KUDOS button some love.... Hit that bad boy.... It don't hurt....
    Apple iPhone 5,
    Retina MacBook Pro, iPad Mini, Nikon D4

  • Headset volume down key problem with STH30

    Hello!
    I just bought a Sony STH30 Stereo Headset for my Xperia Z1.
    But when pressing the "Volume down" button on my headset, the key is hold for 5 to 10 seconds.
    This only happens on the Xperia Z1, it's working fine on other phones.
    It also works pretty fine when changing the volume of an active call - it only happens when trying to lower the volume of the phone or music.
    Greetings from germany,
    Daniel

    i have the same problem with my zenfone 5, 3 key is notworking, when i press pause/play my music player is pause and don't play again until i'm reset my phone, as the same volume up / down is nerver work, but it's work fine on samsung, sony devices ( i'm not try on Xperia Z1 )
    Please tell me another way to use the three button, i have try "Headset Button Controller" app, "Smart key " app by Sony, but all is missing something like this:
    - 1 click play / pause button to play / pause: OK
    - 2 click play / pause button to next : OK
    - 3 click play / pause button to previous : OK
    - Volume Up / Down key : not working.
    Please advices.
    thanks.

  • N95 Bluetooth Headset Volume Control

    Hi,
    I've got an N95 and a Jabra BT135 bluetooth headset. I love the phone and they work well together, except for one problem. Every time I make a call I have to turn the volume up full. Is there any way I can set the phone to return to full volume automatically each time I make or receive a call using the headset ?

    Have a look here: http://www.nokia.co.uk/A4221246
    What I suggest is that you get one that Nokia has defined as compatible, I have one that came with my Nokia 8800 Sirocco, the Nokia Bluetooth Headset BH-801 and it doesn't work properly, sound quality is awful, however its not listed as being compatible with the N95.
    Shunts...
    I will mostly be communicating with a Nokia E72 Zodium Black
    Nokia E72-1 with Vr 051.018.207.04 Software
    If this post helped... Add some kudos!!

  • Headset volume too low

    I just bought an iphone for wife, she said the earphone volume is too low, I have set the volume to max, any idea? Thanks Alex

    The volume issue WAS a problem. Apple fixed it for most people a number of software releases ago. Most of the volume complaints stopped a long time ago after the fix. Now, with the 3G iphone, my volume is very loud and much better than even the fixed first version iphone. I think if you read the many initial reviews of the 3G version, most mentioned how much better the handset, speaker and speakerphone quality and loudness is. I know this is not solace for someone with a problem now, but I don't think it is widespread. You could just have a defective phone. Take it in the Apple Genius bar and see if they will get you a new one.

  • Sound Blaster Arena Headset Volume Buttons Not Working

    Just as the title says. The Volume control buttons on the cord are not working. The lock and unlock for the mic is working, but I've tried all the suggestions I could find in the support website, but the volume buttons just arn't working. Any help would be greatly appreciated.

    Kakiro wrote:
    Just as the title says. The Volume control buttons on the cord are not working. The lock and unlock for the mic is working, but I've tried all the suggestions I could find in the support website, but the volume buttons just arn't working. Any help would be greatly appreciated.
    they are not faulty mine are doing the same thing on windows 7 64bit. try it on xp they work fine. it is the stupid driver support of creative. They don't care about the customer

  • *Ridiculously* loud headset volume!

    Yeah... This is starting to bug the crap out of me, so any responses are appreciated.
    I have a 2011 15" macbook pro. I've been listening to a lot of music on my laptop lately; the speaker volume is fine, but it's when I plug my headphones in (I'm using apple headphones that came with my 4G ipod touch)... The sound is unbelievably loud.
    One tiny point above "mute" is loud enough! When I put it halfway to max, I can hear the headphones in the other room, and it's like being front-row in a rock concert. I don't even want to know what it'll sound like on max - I'm guessing it would blow the headphones up.
    Any solutions? The noise even one point above mute is loud, so when I do video editing I always have to adjust the volume of the actual audio file. When I'm done the video, I always forget to up the volume so I end up importing a really hard-to-hear project.
    Can anyone suggest a fix for this? The sound is really loud and I'm already getting ringing in my ears from it.

    Any solutions? The noise even one point above mute is loud, so when I do video editing I always have to adjust the volume of the actual audio file. 
    Can anyone suggest a fix for this? The sound is really loud and I'm already getting ringing in my ears from it.
    You can try shift+option+volume key combination. This will increment the sound level by sub one point intervals.
    Try different headphones (even Apple's stock ear plugs). Some headphones have a higher "gain" which means that they player softer at any given mac volume.
    If you are getting ringing in the ears, this is a sign of (usually temporary) hearing damage. Please take care of your hearing.
    As for the "hiss" this is due to complex internal circuits causing interference. This has been an issue on all Macbook Pro's I have owned. The only solution is to buy a break out box, which separates the output from the enclosure. And example can be found here.

  • How can I backup data from a case-sensitive volume to a NON-case-sensitive volume?

    The case-sensitive volume in this instance being a desktop-mounted disk image volume.
    A tragi-comedy in too many acts and hours
    Dramatis Personae:
    Macintosh HD: 27" iMac 3.06GHz Intel Core 2 Duo (iMac10,1), 12 GB RAM, 1 TB SATA internal drive
    TB1: 1 TB USB external drive
    TB2: 2 TB USB to Serial-ATA bridge external drive
    Terabyte: a .dmg disk image and resulting desktop volume of the same name (sorry, I don't know the technical term for a .dmg that's been opened, de-compressed and mounted -- evanescently -- on the desktop)
    Drive Genius 3 v3.1 (3100.39.63)/64-bit
    Apple Disk Utility Version 11.5.2 (298.4)
    Sunday morning (05/08/11), disk utility Drive Genius 3's drive monitoring system, Drive Pulse, reported a single bad block on an external USB2.0 1TB drive, telling me all data would be lost and my head would explode if I didn't fix this immediately. So I figured I'd offload the roughly 300 GB of data from TB1 to TB2 (which was nearly empty), with the intention of reinitializing TB 1 to remap the bad block and then move all its data BACK from TB 2. When I opened TB1's window in the Finder and tried to do a straight "Select All" and drag all items from TB1 to TB2, I got this error message:
    "The volume has the wrong case sensitivity for a backup."
    The error message didn't tell me WHICH volume had "the wrong case sensitivity for a backup," and believe me, or believe me not, this was the first time I'd ever heard that there WAS such a thing as "case sensitivity" for a drive. I tried dragging and dropping some individual folders -- some of them quite large, in the 40GB range -- from TB1 to TB2 without any problem whatsoever, but the majority of the items were the usual few-hundred-MB stuff that seems to proliferate on drives like empty Dunkin' Donuts coffee cups on the floor of my car, and I didn't relish the idea of spending an afternoon dragging and dropping dribs and drabs of 300GB worth of stuff from one drive to another.
    Being essentially a simple-minded soul, I had what I thought was the bright idea that I could get around the problem by making a .dmg disk image file of the whole drive, stashing it on TB2, repairing and re-initializing TB1, and then decompressing the disk image I'd made of TB1, and doing the "drag and drop" of all the files in resulting desktop volume to TB1. So I made the .dmg of TB1, called "Terabyte," stashed that .dmg on TB2 (no error messages this time), re-initialized and then rebooted the iMac from my original Snow Leopard 10.6.1 disks and used Disk Utility to erase and initialize TB1 -- making sure that it was NOT initialized as case-sensitive, and installed a minimal system on TB1 from the same boot. Then I updated that 10.6.1 system to 10.6.7 with System Update, and checked to see that Disk Utility reported all THREE drives -- internal, 1TB, and 2TB -- as Mac OS Extended (Journaled), and no "case sensitive" BS. I also used Drive Genius 3's "information" function for more detailed info on all three drives. Except for the usual differing mount points, connection methods, and S.M.A.R.T. status (only the Macintosh HD internal, SATA 1TB drive supports S.M.A.R.T.), everything seemed to be oojah-***-spiff, all three drives showing the same Partition Map Types: GPT (GUID Partition Table.) Smooth sailing from here on out, I thought.
    Bzzzzt! Wrong!
    When I opened the Terabyte .dmg and its desktop volume mounted, I tried the old lazy man's "Select All" and drag all items from the desktop-mounted drive "Terabyte" to TB1, I got the error message:
    "The volume has the wrong case sensitivity for a backup."
    I then spent the next three hours on the phone with AppleCare (kids -- when you buy a Mac ANYTHING, cough up the money for AppleCare. Period.), finally reaching a very pleasant senior tech something-or-other in beautiful, rainy Portland, OR. Together we went through everything I had done, tried a few suggestions she offerred, and, at the end of three hours, BOTH of us were stumped. At least I didn't feel quite as abysmally stupid as I did at the beginning of the process, but that was all the joy I had gotten after two solid days of gnawing at this problem -- and I mean SOLID; I'm retired, and spend probably 12 hours a day, EVERY day, at the keyboard, working on various projects.
    The AppleCare senior tech lady and I parted with mutual expressions of esteem, and I sat here, slowly grinding my teeth.
    Then I tried something I don't know why I was so obtuse as to not have thought of before: I opened Apple's Disk Utility and checked the desktop-mounted volume Terabyte (Mount Point: /Volumes/Terabyte), the resulting volume from opening and uncompressing the .dmg "Terabyte".
    Disk Utility reported: "Format : Mac OS Extended (Case-sensitive)." Doh!
    Obviously, TB1, the 1 TB USB external drive I'd actually bought as part of a bundle from MacMall when I bought my 27" iMac, and which I had initialized the first day I had the iMac up and running (late November 2009), had somehow gotten initialized as a Case-sensitive drive. How, I don't know, but I suspect the jerk behind the keyboard. Whatever the case, when I created the Terabyte disk image (the drive's original name: when I erased and re-initialized it -- see above -- I renamed it "1TB" for quick identification), the original drive's "Case-sensitive" format was encoded too. So when I tried to drag and drop EVERYTHING from the desktop-mounted volume "Terabyte" to the newly initialized and "blessed" (now THERE's a term from the past!), the system recognized it as an attempt as a total volume backup, and hit me with "The volume [the desktop-mounted volume "Terabyte" -- BB] has the wrong case sensitivity for a backup." And, of course, the reinitialized TB1 was now correctly formatted as NOT "case-sensitive."
    Well, that solved the mystery (BTW, Disk Utility identified the unopened Terabyte.dmg as an "Apple UDIF read-only compressed {zlib}, which is why the .dmg file could be copied to ANY volume, case sensitive or not), but it didn't help me with my problem of having to manually move all that data from the desktop-mounted volume "Terabyte" to TB1. I tried to find a way to correct the problem at the .dmg AND opened-volume-from-.dmg level with every disk utility I had, to no avail.
    Sorry for the long exposition, but others may trip over this "case-sensitive" rock in the road, and I wanted to make the case as clear as possible.
    So my problem remains: other than coal shovel by coal shovel, is there any way to get all the data off this case-sensitive desktop-mounted volume "Terabyte" and onto TB1.
    Not that I know whether it would made any difference or not, one of the things that got me into this situation was my inability to get "Time Machine" properly configured so it wasn't making new back-ups every (no lie) 15 minutes.
    Philosophical bonus question: what's the need for this "case-sensitive," "NOT case-sensitive" option for disk initialization?
    As always, thanks for any help.
    Bart Brown

    "Am I to understand that you have a case-sensitive volume with data that you want to copy to a case-insensitive volume? And the Finder won't let you do it? If that's what the problem is, the reason should be obvious: on the source volume, you may have two files in the same folder whose names differ only in case. When copying that folder to the target volume, it's not clear what the Finder should do."
    Yes, I understand all that... NOW.
    What I had (have) is a USB external 1TB drive (henceforth known as "Terabyte") that I bought with my 27" iMac. I formatted, and put a minimal (to make it bootable) system on Terabyte the same day back in late November 2009 that I set up my 27" iMac. Somehow -- I don't know how -- Terabyte got initialized as "case-sensitive." I didn't even know at the time that there WAS such a thing as "case-sensitive" or "NOT case-sensitive" format.
    Sunday morning (05/08/11), Drive Pulse, a toolbar-resident utility (that's Part of Drive Genius 3) that monitors internal and external drives for physical, problems, volume consistency problems, and volume fragmentation, reported a single bad block on the volume Terabyte, advising me that it would be best if I re-formatted Terabyte ASAP. I thought I could open Terabyte in a Finder window, Select All, and drag everything on the drive to ANOTHER USB external drive of 2 TB capacity (henceforth known as TB2). When I tried to do that, I got an error message:
    "The volume has the wrong case sensitivity for a backup."
    First I'd heard of "case sensitivity" -- I'm not too bright, as you seem to have realized.
    Oddly enough (to me), I could move huge chunks of data, including a folder of 40GB, from Terabyte to TB2 with no problem.
    Then the scenario unfolded per my too-convoluted message: several hours of trying things on my own, including making a .dmg of Terabyte (henceforth to be known as Terabyte.dmg) -- which left me with the exact same problem as described in the previous 4 paragraphs; and my 3 hours on the phone with AppleCare, who at least explained this case-sensitive business, but, after some shot-in-the-dark brainstorming -- tough to do with only one brain, and THAT on the OTHER end of the line --  the very pleasant AppleCare rep and I ended up equally perplexed and clueless as to how to get around the fact that a .dmg of a case-sensitive volume, while not case-sensitive in its "image" form (Terabyte.dmg), and thus able be transferred to TB1 or TB2 with no problems whatsoever, when opened -- either by double-clicking or opening in Disk Utility -- produced a desktop-mounted volume (henceforth known as the volume "Terabyte," the original name of the case-sensitive volume from which TB1.dmg had been made) that had the same case-sensitivity as the original from which it was made.
    In the meantime, having gotten the data I needed to save off the physical USB "case-sensitive" volume Terabyte in the form of Terabyte.dmg, I erased and re-initialized the physical USB "case-sensitive" volume Terabyte, getting rif of the case sensitivity, and renaming it TB1. But it all left me back at square one, EXCEPT I had saved my data from the original "Terabyte" drive, and reformatted that drive to a NON- case-sensitive data now named TB1. The confusion here stems from the fact that problem case-sensitive drive, from which I made Terabyte.dmg, was originally named "Terabyte". When I re-initialized it as a NON case-sensitive drive, I renamed it TB1. I'm sorry about the confusing nomenclature, which I've tried to improve upon from my original message -- usual text-communication problem: the writer knows what he has in mind, but the reader can only go by what's written.
    So, anyway, I still have the same problem, the desktop-mounted volume "Terabyte" still cannot be transferred in one whole chunk to either my internal drive, TB1, TB2, as the Finder interprets it as a volume backup (which it is), and reads the desktop-mounted volume "Terabyte" as case-sensitive, as the original volume -- from which the disk image Terabyte.dmg was made -- had been at the time I made it. 
    "As long as that situation doesn't arise, you should be able to make the copy with a tool that's less fastidious than the Finder, such as cp or rsync."
    I'm afraid I have no idea what "cp or rsync" are. I'd be happy to be educated. That's why I came here.
    Bart Brown
    Message was edited by: Bartbrn
    Just trying to unmuddy the water a bit,,,

  • Volume control on usb headset doesn't work.

    I got myself the Logitech ClearChat Pro USB headset. I've got it to work with the help of http://alsa.opensrc.org/index.php/Hotpl … es_(Howto).  I can change the headphone volume with gnome-alsamixer.  However, the volume controls located on the headset doesn't work.  The controls works in Windows so either it's a configuration issue or it is simply not supported in Linux.  Does anyone have experience with this headset or with USB headsets in general?
    Thanks.

    Mr Green wrote:
    http://forums.logitech.com/logitech/boa … ge.id=4655
    You may have already seen this.... but
    No, I hadn't seen this. As it says that it worked out of the box in Ubuntu, I downloaded the LiveCD and it works indeed as it should after seleting the headset as sound output in the control panel. Afterward, I tried it on my laptop but the controls change the master volume on the onboard soundcard instead of the headset one. So it's just a matter of configuring it. From the articles that  I found at http://alsa.opensrc.org/index.php/Main_Page, it seems to be quite complicated from the first glance. I'll try to find an example asound.conf (or ~/.asoundrc). The Ubuntu LiveCD doen't contained these files so I don't know how they did it.
    R00KIE: Thanks, but I already found that out and I can change the headset volume from alsamixer. What I want to do is to change it with the volume controls on the headset: http://www.logitech.com/repository/530/jpg/4838.1.0.jpg

  • "No such file or directory" errors on Time Machine backup volume

    I remotely mounted the Time Machine backup volume onto another Mac and was looking around it in a Terminal window and discovered what appeared to be a funny problem. If I "cd" into some folders (but not all) and do a "ls -la" command, I get a lot of "No such file or directory" errors for all the subfolders, but all the files look fine. Yet if I go log onto the Mac that has the backup volume mounted as a local volume, these errors never appear for the exact same location. Even more weird is that if I do "ls -a" everything appears normal on both systems (no error messages anyway).
    It appears to be the case that the folders that have the problem are folders that Time Machine has created as "hard links" to other folders which is something that Time Machine does and is only available as of Mac OS X 10.5 and is the secret behind how it avoids using up disk space for files that are the same in the different backups.
    I moved the Time Machine disk to the second Mac and mounted the volume locally onto it (the second Mac that was showing the problems), so that now the volume is local to it instead of a remote mounted volume via AFP and the problem goes away, and if I do a remote mount on the first Mac of the Time Machine volume the problem appears on the first Mac system that was OK - so basically by switching the volume the problem switches also on who shows the "no such file or directory" errors.
    Because of the way the problem occurs, ie only when the volume is remote mounted, it would appear to be an issue with AFP mounted volumes that contain these "hard links" to folders.
    There is utility program written by Amit Singh, the fella who wrote the "Mac OS X Internals" book, called hfsdebug (you can get it from his website if you want - just do a web search for "Mac OS X Internals hfsdebug" if you want to find it ). If you use it to get a little bit more info on what's going on, it shows a lot of details about one of the problematic folders. Here is what things look like on the first Mac (mac1) with the Time Machine locally mounted:
    mac1:xxx me$ pwd
    /Volumes/MyBackups/yyy/xxx
    mac1:xxx me$ ls -a
    . .DS_Store D2
    .. Documents D3
    mac1:xxx me$ ls -lai
    total 48
    280678 drwxr-xr-x 5 me staff 204 Jan 20 01:23 .
    282780 drwxr-xr-x 12 me staff 442 Jan 17 14:03 ..
    286678 -rw-r--r--@ 1 me staff 21508 Jan 19 10:43 .DS_Store
    135 drwxrwxrwx 91 me staff 3944 Jan 7 02:53 Documents
    729750 drwx------ 104 me staff 7378 Jan 15 14:17 D2
    728506 drwx------ 19 me staff 850 Jan 14 09:19 D3
    mac1:xxx me$ hfsdebug Documents/ | head
    <Catalog B-Tree node = 12589 (sector 0x18837)>
    path = MyBackups:/yyy/xxx/Documents
    # Catalog File Record
    type = file (alias, directory hard link)
    indirect folder = MyBackups:/.HFS+ Private Directory Data%000d/dir_135
    file ID = 728505
    flags = 0000000000100010
    . File has a thread record in the catalog.
    . File has hardlink chain.
    reserved1 = 0 (first link ID)
    mac1:xxx me$ cd Documents
    mac1:xxx me$ ls -a | head
    .DS_Store
    .localized
    .parallels-vm-directory
    .promptCache
    ACPI
    ActivityMonitor2010-12-1710p32.txt
    ActivityMonitor2010-12-179pxx.txt
    mac1:Documents me$ ls -lai | head
    total 17720
    135 drwxrwxrwx 91 me staff 3944 Jan 7 02:53 .
    280678 drwxr-xr-x 5 me staff 204 Jan 20 01:23 ..
    144 -rw-------@ 1 me staff 39940 Jan 15 14:27 .DS_Store
    145 -rw-r--r-- 1 me staff 0 Oct 20 2008 .localized
    146 drwxr-xr-x 2 me staff 68 Feb 17 2009 .parallels-vm-directory
    147 -rwxr-xr-x 1 me staff 8 Mar 20 2010 .promptCache
    148 drwxr-xr-x 2 me staff 136 Aug 28 2009 ACPI
    151 -rw-r--r-- 1 me staff 6893 Dec 17 10:36 A.txt
    152 -rw-r--r--@ 1 me staff 7717 Dec 17 10:54 A9.txt
    So you can see from the first few lines of the "ls -a" command, it shows some file/folders but you can't tell which yet. The next "ls -la" command shows which names are files and folders - that there are some folders (like ACPI) and some files (like A.txt and A9.txt) and all looks normal. And the "hfsdebug" info shows some details of what is really happening in the "Documents" folder, but more about that in a bit.
    And here are what a "ls -a" and "ls -al" look like for the same locations on the second Mac (mac2) where the Time Machine volume is remote mounted:
    mac2:xxx me$ pwd
    /Volumes/MyBackups/yyy/xxx
    mac2:xxx me$ ls -a
    . .DS_Store D2
    .. Documents D3
    mac2:xxx me$ ls -lai
    total 56
    280678 drwxr-xr-x 6 me staff 264 Jan 20 01:23 .
    282780 drwxr-xr-x 13 me staff 398 Jan 17 14:03 ..
    286678 -rw-r--r--@ 1 me staff 21508 Jan 19 10:43 .DS_Store
    728505 drwxrwxrwx 116 me staff 3900 Jan 7 02:53 Documents
    729750 drwx------ 217 me staff 7334 Jan 15 14:17 D2
    728506 drwx------ 25 me staff 806 Jan 14 09:19 D3
    mac2:xxx me$ cd Documents
    mac2:Documents me$ ls -a | head
    .DS_Store
    .localized
    .parallels-vm-directory
    .promptCache
    ACPI
    ActivityMonitor2010-12-1710p32.txt
    ActivityMonitor2010-12-179pxx.txt
    mac2:Documents me$ ls -lai | head
    ls: .parallels-vm-directory: No such file or directory
    ls: ACPI: No such file or directory
    ... many more "ls: ddd: No such file or directory" error messages appear - there is a one-to-one
    correspondence between the "ddd" folders and the "no such file or directory" error messages
    total 17912
    728505 drwxrwxrwx 116 me staff 3900 Jan 7 02:53 .
    280678 drwxr-xr-x 6 me staff 264 Jan 20 01:23 ..
    144 -rw-------@ 1 me staff 39940 Jan 15 14:27 .DS_Store
    145 -rw-r--r-- 1 me staff 0 Oct 20 2008 .localized
    147 -rwxr-xr-x 1 me staff 8 Mar 20 2010 .promptCache
    151 -rw-r--r-- 1 me staff 6893 Dec 17 10:36 A.txt
    152 -rw-r--r--@ 1 me staff 7717 Dec 17 10:54 A9.txt
    If you look very close a hint as to what is going on is obvious - the inode for the Documents folder is 152 on the local mounted case (the first set of code above for mac1), and it's 728505 in the remote mounted case for mac2. So it appears that these "hard links" to folders have an extra level of folder that is hidden from you and that AFP fails to take into account, and that is what the "hfsdebug" shows even better as you can clearly see the REAL location of the Documents folder is in something called "/.HFS+ Private Directory Data%000d/dir_135" that is not even visible to the shell. And if you look closely in the remote mac2 case, when I did the "cd Documents" I don't go into the inode 135, but into the inode 728505 (look close at the "." entry for the "ls -la" commands on both mac1 and mac2) which is the REAL problem, but have no idea how to get AFP to follow the extra level of indirection.
    Anyone have any ideas how to fix this so that "ls -l" commands don't generate these "no such file or folder" messages?
    I am guessing that the issue is really something to do with AFP (Apple File Protocol) mounted remote volumes. The TimeMachine example is something that I used as an example that anyone could verify the problem. The real problem for me has nothing to do with Time Machine, but has to do with some hard links to folders that I created on another file system totally separate from the Time Machine volume. They exhibit the same problem as these Time Machine created folders, so am pretty sure the problem has nothing to do with how I created hard links to folders which is not doable normally without writing a super simple little 10 line program using the link() system call - do a "man 2 link" if you are curious how it works.
    I'm well aware of the issues and the conditions when they can and can't be used and the potential hazards. I have an issue in which they are the best way to solve a problem. And after the problem was solved, is when I noticed this issue that appears to be a by-product of using them.
    Do not try these hard links to folders on your own without knowing what they're for and how to use them and not use them. They can cause real problems if not used correctly. So if you decide to try them out and you loose some files or your entire drive, don't say I didn't warn you first.
    Thanks ...
    -Bob

    The problem is Mac to Mac - the volume that I'm having the issue with is not related in any way to Time Machine or to TimeCapsule. The reference to TIme Machine is just to illustrate the problem exists outside of my own personal work with hard links to folders on HFS Extended volumes (case-sensitive in this particular case in case that matters).
    I'm not too excited about the idea of snooping AFP protocol to discover anything that might be learned there.
    The most significant clue that I've seen so far has to do with the inode numbers for the two folders shown in the Terminal window snippets in the original post. The local mounted case uses the inode=728505 of the problematic folder which is in turn linked to the hidden original inode of 135 via the super-secret /.HFS+... folder that you can't see unless using something like the "hfsdebug" program I mentioned.
    The remote mounted case uses the inode=728505 but does not make the additional jump to the inode=135 which is where lower level folders appear to be physically stored.
    Hence the behavior that is seen - the local mounted case is happy and shows what would be expected and the remote mounted case shows only files contained in the problem folder but not lower-level folders or their contents.
    From my little knowledge of how these inode entries really work, I think that they are some sort of linked list chain of values, so that you have to follow the entire chain to get at what you're looking for. If the chain is broken somewhere along the line or not followed correctly, things like this can happen. I think this is a case of things not being followed correctly, as if it were a broken chain problem then the local mounted case would have problems also.
    But the information for this link in the chain is there (from 728505 to the magic-135) but for some reason AFP doesn't make this extra jump.
    Yesterday I heard back from Apple tech support and they have confirmed this problem and say that it is a "implementation limitation" with the AFP client. I think it's a bug, but that will have to be up to Apple to decide now that it's been reported. I just finished reporting this as a bug via the Apple Bug Reporter web site -- it's bug id 8926401 if you want to keep track it.
    Thanks for the insights...
    -Bob

  • Volume is too low on the dictation indicator

    When I tap the microphone icon to dictate anything into my phone, the tone it makes to let you know that it is taking your dication is very very low.  The same when I tap the "done" button at the end of dictating.  The volume of the tone is so low, that I cannot tell when dication recognition has started or stopped.

    Hello there, new iphone 5s.
    The following link from the iPhone User Guide provides some useful steps for increasing the volume setting on your iOS device:
    Volume controls - iPhone
    http://help.apple.com/iphone/7/#/iph3bd01180
    Volume controls
    When you’re on the phone or listening to songs, movies, or other media, the buttons on the side of iPhone adjust the audio volume. Otherwise, the buttons control the volume for the ringer, alerts, and other sound effects.
    WARNING: For important information about avoiding hearing loss, see Important safety information.
    Lock the ringer and alert volumes. Go to Settings > Sounds and turn off “Change with Buttons.” To limit the volume for music and videos, go to Settings > Music > Volume Limit.
    Note: In some European Union (EU) countries, iPhone may warn that you’re setting the volume above the EU recommended level for hearing safety. To increase the volume beyond this level, you may need to briefly release the volume control. To limit the maximum headset volume to this level, go to Settings > Music > Volume Limit and turn on EU Volume Limit. To prevent changes to the volume limit, go to Settings > General > Restrictions.
    You can also use either volume button to take a picture or record a video. See Take photos and videos.
    Thanks for reaching out to Apple Support Communities.
    Cheers,
    Pedro.

Maybe you are looking for

  • Font-Reprensation in CS 5.5 for mac

    Hey, i am new her and me english ist bad. But my new installation from CS 5.5 on a new macbook pro retina makes me unhappy. The viewing of all porducts (Acrobat, indesign, photoshop etc) is bad. I mean not only a page in indesign for example, but als

  • A way of making window look transparent

    I'm using the following method to make a window look transparent: whenever a frame is moved, it makes a screenshot of the underliying area and displays it as its background but, unfortunately, this doen't work in this example ???? public class MyFram

  • Embed Tag Issue

    Can I somehow pass variables into Embed attributes?  e.g.: [Embed(source=variable, mimeType=<type>)]  I tried, but It always said that Unable to transcode 'variable' Thanks & Regards Virat Patil

  • Can't Connect to SMP 3.0 server from Client

    Hello All , I am trying to connect SMP 3.0 server but i am getting error like Requesting Public Key from Server Communications error (14) Connection failed Ending transmission and i also checked with url as per my knowledge its  working fine because

  • IPhoto and TimeMachine

    Since iPhoto 9.1.5 release, iPhoto can't restaure a single photo from a TimeMachine backup anymore. The only solution is to restaure the whole iPhotoLibrary. I thought it was a bug that Apple would rapidly fix, but I've just read this support page: h