Results 1 to 18 of 18
Like Tree3Likes
  • 3 Post By tagscuderia
  1.    #1  
    Out of the blue yesterday, the slider wouldn't close; wasn't dropped or knocked, just picked it up off a desk and attempted to close... wouldn't say "brute" force, but it needed some persuading to close -- no cracks or creaks when it did close and the mechanism appears fine.
    However, whenever you close the slider, the volume decreases! Anyone else suffered a similar issue, has a solution: hardware or software?
    Cheers, much appreciated.

    P.S, I do have the patch to use the volume buttons as the camera shutter, I take it that this wouldn't have affected it?
    Last edited by tagscuderia; 09/06/2012 at 10:46 AM. Reason: Added detail.
  2. #2  
    It sounds physical in nature. Maybe the ribbon cable is getting pinched.

    I would try not to manipulate the slider if at all possible until investigating.

    Google Pre 3 disassemble for help. Check Internals as well...
    Lumia 1520.3 (the Beastly Unicorn): Windows 10 Mobile

    Windows Central Senior Ambassador

    Mobile Nations Devotee
  3. #3  
    I would (sad to say) pretty much guarantee it's hardware and your ribbon cable is going. I know of a few folks all Pre3s that have had their ribbon cables break completely and prior to breaking they had some slider resistance.
    Last edited by OldSkoolVWLover; 09/06/2012 at 04:19 PM. Reason: clarified device type
    I love physical keyboards... but there is two devices that would make me consider a slab, one is something running a full version of Open webOS. The other is an iPhone!!!! HA HA just kidding (about the iPhone that is)...
  4. #4  
    Quote Originally Posted by tagscuderia View Post
    Out of the blue yesterday, the slider wouldn't close; wasn't dropped or knocked, just picked it up off a desk and attempted to close... wouldn't say "brute" force, but it needed some persuading to close -- no cracks or creaks when it did close and the mechanism appears fine.
    However, whenever you close the slider, the volume decreases! Anyone else suffered a similar issue, has a solution: hardware or software?
    Cheers, much appreciated.

    P.S, I do have the patch to use the volume buttons as the camera shutter, I take it that this wouldn't have affected it?
    I've had same problem with my legacy Pre! Cant remember now was it related to some patch, custom loaded modem or metadoctored webOS 2.1. But, it was software related for sure.
  5. #5  
    I've had exactly the same problem you're describing.

    My advice? Do. not. force. it. open.

    From my first hand experience from doing this, it resulted in shearing the ribbon and pretty much jamming the slider. Oh, and I couldn't control the volume with the physical hardware buttons.

    Like others have said, the only way back is dissassemble and repair, or get a replacement - I was lucky, I got a straight up replacement as they didn't even bother to repair my broken Pre3.
  6. #6  
    I had this issue too. Eventually I closed the slider hard enough to where it started sliding fine again. But it must have severed the audio cable in the process since my volume buttons stopped working entirely after that.
  7. #7  
    Just to clear things - I've had problem with decreased volume with closed slider and it was software related. Never had problem with jammed slider.
  8.    #8  
    Thanks for the replies, greatly appreciated.
    Taking the back off you could see that the slider mechanism was contacting the ribbon cable -- as to why it only decreased volume and only on closing... beats me.
    All I did was push the cable flat clear of the slider, problem solved and the buttons still work, success! I was lucky not to be in the same boat as "FenrirWolf," no doubt mine has been partially damaged though.

    N.B, for anyone suffering from a jammed slider: leave it and get a T5 driver, take the back off so that you can safely move the ribbon cable clear.
  9. #9  
    Good to know! Glad it appears you have fixed yours and didn't suffer the fate that others have. This is really the only hardware defect I have heard of with the HP built phones.
    I love physical keyboards... but there is two devices that would make me consider a slab, one is something running a full version of Open webOS. The other is an iPhone!!!! HA HA just kidding (about the iPhone that is)...
  10. #10  
    If it's that simple to fix I might as well open mine up and see if it's salvageable in some form. lol
  11. #11  
    wait a minute lsanduck. Where did you get a replacement pre3?
  12. #12  
    Quote Originally Posted by ctrain1 View Post
    wait a minute lsanduck. Where did you get a replacement pre3?
    Look at his location, he is in a place that got an official release... (meaning he got an actual warranty, I think EU standard, or requirement is 2 years)
    I love physical keyboards... but there is two devices that would make me consider a slab, one is something running a full version of Open webOS. The other is an iPhone!!!! HA HA just kidding (about the iPhone that is)...
  13. #13  
    Quote Originally Posted by ctrain1 View Post
    wait a minute lsanduck. Where did you get a replacement pre3?
    As OldSkoolVWLover says, I'm in the UK, so it was released here (I bought mine on contract from the Carphone Warehouse). I think at that point it was still within 90 days, so I could get it repaired for free.
  14. #14  
    Hi,

    I have a similar problem. When I touch the part of the device near the volume buttons while sliding down the device.

    I did "erase apps and data" but it didn't help.

    Is this hardware or software problem. Can it be easily fixed (I'm in an unsupported country, Poland)

    Thanks!
  15. #15  
    I would guess hardware problem, and at this point I don't think there is a device worldwide still under warranty (just saying we are all in unsupported countries now)
    I love physical keyboards... but there is two devices that would make me consider a slab, one is something running a full version of Open webOS. The other is an iPhone!!!! HA HA just kidding (about the iPhone that is)...
  16. #16  
    in my case it was software problem.
  17. #17  
    Quote Originally Posted by chalx View Post
    in my case it was software problem.
    And what did exactly cause it?
  18. #18  
    it was long ago and cant remember. I think it was some of advanced phone patches.

Tags for this Thread

Posting Permissions