Database Users

Project "Recycle smashed SII" (pair bluetooth mouse whilst pattern locked)

Hi all,
So, despite being careful I inevitably dropped my shiny Galaxy S2. I was more than unlucky though, and it fell in the path of a revolving door! End result is a smashed screen but working device. Nope, no insurance and I bought it without contract so I've lost a lot of pennies.
However, I am hoping to save something from this. I'm typing on my old desire so excuse the brief initial post bit I'm hoping I can at least not let the phone go to waste...
I have the MHL to HDMI cable and using this I can see the phone started ok and the pattern screen is displayed, so far so good!
However the screen doesn't respond to touch. Bummer.
So my thought is this: I've seen that you can hook up a Bluetooth mouse to the phone ... I'm wondering if I can pair a Bluetooth mouse before the pattern lock using adb and thus have a phone I can leave connected to the TV, use a mouse with and still get some use out of.
What do you guys think?
Cheers!

Its actually very doable.The problem is how to pair the mouse
Sent from my GT-I9000 using Tapatalk

Indeed, that is very much the problem! I would hope that once its paired it will all be plain sailing, but trying to get it paired in its current state is the crux of it

Why not buy a new screen?
Sent from my GT-I9000 using XDA App

Mostly because they are almost as expensive as the phone itself... That and it's not just the screen, the surrounding frame is also quite badly damaged. I figure if I wait till after xmas I can probably get a new S2 for a similar price as I would be paying for just the screen now. I have my old desire which is keeping me going in the meantime.

http://forum.xda-developers.com/showthread.php?t=971768
See if that works?

can't you just perform a hard reset? It can be done through recovery and only requires hardware buttons.
Should take care of the unlock code part, not?

sargorn said:
http://forum.xda-developers.com/showthread.php?t=971768
See if that works?
Click to expand...
Click to collapse
Thanks sargorn, however my phone doesn't have debugging enabled to I can't adb into the phone in anything other than recovery mode...

swiftshifter said:
can't you just perform a hard reset? It can be done through recovery and only requires hardware buttons.
Should take care of the unlock code part, not?
Click to expand...
Click to collapse
Hi swiftshifter...
Yes, this is an option to get rid of the unlock part but I'd rather not hard reset if there are alternatives. I'm keeping this as a backup.
I still need to figure out the send event stuff though because I'll probably need this to 'press' the buttons required to pair a mouse.
I think my biggest hurdle at the moment, or the biggest win if I can get it, is to enable debugging mode whilst the phone is on normally as suggested in http://forum.xda-developers.com/showthread.php?p=17910067 But I haven't had a chance to try this yet...

How about going into your market account from PC and remotely install VNC server? One problem though.. how to automatically start the VNC server...

MindToAsk said:
How about going into your market account from PC and remotely install VNC server? One problem though.. how to automatically start the VNC server...
Click to expand...
Click to collapse
A good idea! But yeah, hindered by the same issue. I think long term I'd prefer the bluetooth mouse but for the sake of setting everything up VNC on there would probably make life a lot easier! Can't believe I hadn't though of it to be honest!
Now just to work out how to get it started ;-)

Archos 101 - USB Dead - affected by Turbomode?

Hey guys,
sadly i have to mention - my external USB port also just died...
After contacting archos they told me to reset the revice completely and reinstall - but it didn't help.
As i dont have a recipe anymore - i can't send it in to fix
Well anyway - I never had problems with the device or the USB - but recently I switched my device to settings->deviceinfo->energy...->turbomode the 1st time.
Beside it's draining battery like hell now even with just being idle (suspended) it crashed 1 day ago - having LCD backlight on but showing a black screen (btw my usb keyboard was plugged in meanwhile and the charging-cable was also plugged in).
Next start the USB port didn't react to anything anymore...
(keyboard-lights just turn on shortly (<1s) on plug in and thats all)
(lsusb shows just the 3 default entries: 2 hsot controlers + touchscreen id)
So i assume its dead...
Anyway - after the shock I tried to figure out what I changed the past days an all I can remeber was the turbomode... did anyone make the same experience perhaps?
Eventualy we can figure out the acutal problem of dying USB ports... (if they are not just dieing randomly...)
I searched the internet alot regarding this problem:
Some ppl say its software affected - but i can't really believe since the reset should help obviously... (unless its something deeper in firmware...)
Also the fact that anyone who send in his/her device recieved another device after speaks for some hadware failure...
On the other hand there are 2 host controllers on our archos device (1 for the touchscreen as it seems) and the other 1 for external USB... why is just 1 of em dying all the time?

I had my first unit replaced because the USB was dead after a few months, Board v6; the replacement was a v5 and the USB lived hardly 2 months, the died, too... I did not do anything particular that should have caused this; it really seems it is a weakness in the hardware design; Archos has never admitted that, always suggesting fixes that never worked for anyone and saying, they wouldn't know this is a common problem... I am not the only one having two devices in a row with that problem; I have given up on my USB now and also given up on Archos due to their response on this. Also FW-Updates seem to add more problems than fixes for months now and I downgraded to 2.1.08 recently to get a device that at least works smoothly with whats left... If iPad-owners can live without USB so can I, I suppose... There is always Dropbox, and several tools for filetransfer via WiFi, and the SD-Card-Slot to substitute for a USB-Drive etc. (For my next tablet I might even wait and see, what Windows 8 brings, could become interesting...) Archos as a manufacturer of Tablets has become a no-go for me after this experience. I don't like being lied to, if they made a mistake and admit it, I could trust that the next generation might be better, but like this I would presume to be lied to again so trust in the brand is gone even if they start making it better...

voom said:
I had my first unit replaced because the USB was dead after a few months, Board v6; the replacement was a v5 and the USB lived hardly 2 months, the died, too...
Click to expand...
Click to collapse
Got a v6 too, also replaced by a v5 which lasted at least over a half a year or something. ****ty stuff, srsly

Same here, usb port stopped working after about a year. Not that it mattered - it was useless, only a few usb devices would work correctly. I transfer all my files to the device using the microsd card now. I don't use the tablet very often but I'm very disappointed on Archos. And this isn't my only problem. It was supposed to support HD video playback (even bought the plugins - something which others offer for free) but only a few MKVs will play without stutter.
They won't even bother updating the console with android 2.3!
This is why companies close these days..

@FrEcP - if you registered your device when you 1st got it, and assuming it is still within it's warranty period, you should not need a receipt.
regarding the comments on video playback by other posters - the gen 8 Archos devices have the best video playback support inc HD bar all but the very latest high powered devices, and the plugin is not even required to enable any of the HD formats - it's for mpeg2 (dvd) and AC3 audio only. Providing the files are within the devices specification re resolution and profile, it plays pretty much anything asked of it.

Hi chulri, thx for your root - now that i downgraded to 2.1.08 via SDE anyway, I took the one simple step left to apply your permanent root - and could thus deactivate the daos.apk etc.
As for video, I noticed that 720p HD works perfectly with the Archos-Videoplayer but 1080 plays more like slow motion... 1080 I tried was a MOV or WMV though, not sure, and if I recode stuff for general use I convert anything to 720p MP4 264 with AAC Audio - resulting in up to half the size for similar quality-settings (720 to 720) and of course more significantly smaller going from 1080 to 720. What would be left to try is converting the "slomo"-1080 wmvs to 1080 mp4 264 and see how the 101 handles that... 1080 on the 101 is quite pointless anyway unless playing back via hdmi...

You don't have to try that, as it will not work.
The Archos is using the gpu for videodecoding and that can't handle 1080p/i so softwaredecoding is used.
And for all the people out there that still don't get it, Archos advertises [email protected] with a max of 5Mbs and not [email protected] 5 ( which is used in Animes these days).

fzelle said:
And for all the people out there that still don't get it, Archos advertises [email protected] with a max of 5Mbs and not [email protected] 5 ( which is used in Animes these days).
Click to expand...
Click to collapse
Advertise it where? I see no such thing on the box, in the instructions leaflet nor I've seen anything like that in any of the ads or information in their web site (at least there wasn't when I bought the tablet). The only reason people know of these limitations is because there were people disappointed of the HD capabilities of the device and started asking Archos support questions about it!! Not to mention that "supports the widest range of music and video formats up to 720p HD video" as it mentions on the box couldn't have been any further from the truth since for mkv (ac3) playback you have to pay for the plugins to even get the 3.1 profile support you've mentioned! "Supports a limited range of music and video formats and you have to pay for a few more" would have been truer..
Michael

I fail to see what this has to do with "Archos 101 - USB Dead - affected by Turbomode" which is the title of this thread...

@michpan:
http://www.archos.com/products/ta/archos_70it/specs.html?country=gb&lang=en
Read for yourself

Hi FrEcP!
FrEcP said:
Next start the USB port didn't react to anything anymore...
(keyboard-lights just turn on shortly (<1s) on plug in and thats all)
(lsusb shows just the 3 default entries: 2 hsot controlers + touchscreen id)
So i assume its dead...
Click to expand...
Click to collapse
What does it mean didn't react to anything.... really nothing?
Have you already inspected dmesg output?
May try with USB stick instead of your keyboard.
Some sticks also claim to use more power than others...
You might examine this with lsusb as well, most "tell" the host they will consume 200mA.
FrEcP said:
Anyway - after the shock I tried to figure out what I changed the past days an all I can remeber was the turbomode... did anyone make the same experience perhaps?
Click to expand...
Click to collapse
I don't think there's a side effect with turbomode... though i can't tell for sure.
FrEcP said:
Eventualy we can figure out the acutal problem of dying USB ports... (if they are not just dieing randomly...)
Click to expand...
Click to collapse
From what i found out during hardware investigations is, that there's a DCDC voltage converter that is responsible for the 5V power supply of the type A USB connector. Maybe the converter is to weak for currents above 200mA.
E.g. the kernel hack used on Uruk allows to switch on the USB power for devices claiming up to 500mA (as specified for USB).
There's nothing wrong with this at first sight, but maybe Archos did choose some of the components to weak to deliver this current.
My suspicion is that this converter might die slowly or there's some kind of inrush current while activating a device.
This might kill the chip.
Unfortunately i was not able to identify the manufacturer and model of the chip, i only know the location on the mainboard.
I'm sorry that i can't really help on this issue, but maybe some day there will be light
You might try one thing:
Use a self powered hub and connect it to the Archos, then insert USB device again...
Any difference?
Good luck!
scholbert

I would suspect, that it does not have to do with the power-consumption, since the same hardware that used to work all the time suddenly stops working...
Also, when the USB is dead the port still delivers power, but does not recognize any devices any more. It seems whatever gets broken has more to do with dataflow than with power-supply...

always nice to hear for u scholbert
>What does it mean didn't react to anything.... really nothing?
Well - as i said - the power light light up for about 20ms then noting happens anymore
>Have you already inspected dmesg output?
neither "dmesg" nor "lsusb" show any different output while plug in.
>May try with USB stick instead of your keyboard.
tried a wireless keyborad, a wired keyboard and a usb-stick all just seem to have power for some milliseconds.... then noting else can be noticed.
The only interseting difference i noticed is:
If i have my Keyboard plugged in while startup all lights (capslock,...) light up and STAY ON. Till i pull the plug. Then its like before...
Sadly an USB-Hub (powered) will neiter be recognised... (same bahaviour)
What i noticed - if i resome the device (after is was powered on) there are several wake up commands in dmesg for the screen and the usb hubs...
But it doesnt seem to me that the 2nd hub will get resumed proper... unless those command invoke both of em at once.
What does it tell for u when resuming the device?

voom said:
I would suspect, that it does not have to do with the power-consumption, since the same hardware that used to work all the time suddenly stops working...
Click to expand...
Click to collapse
If it operates at some limit point it might work for while without any problems.
Then it might suddenly stop working...
This is typical for hardware defects (overheat, ESD, other weird things...)
Anyway, i never got these problems, so it's just a kind of "feeling".
voom said:
Also, when the USB is dead the port still delivers power, but does not recognize any devices any more. It seems whatever gets broken has more to do with dataflow than with power-supply...
Click to expand...
Click to collapse
This is new information for me... sounds logic to me.
BTW have you measured the voltage at the port?
It might also be that the device sticks in enumeration at some point.
Let me point out the following thesis:
1. USB device gets plugged into the port
2. OMAP gets an interrupt and is told there's something happening at USB
3. OMAP listens
4. USB device send identifier, power request for full operation.... (enumeration)
5. OMAP gets it, tries to enable power to match requirements and waits for ACK
6. USB device didn't get enough current for operational state and fails
7. ???
There should be something in dmesg though, so just a thesis
FrEcP said:
always nice to hear for u scholbert
Click to expand...
Click to collapse
Thanks, great honour
FrEcP said:
>What does it mean didn't react to anything.... really nothing?
Well - as i said - the power light light up for about 20ms then noting happens anymore
>Have you already inspected dmesg output?
neither "dmesg" nor "lsusb" show any different output while plug in.
>May try with USB stick instead of your keyboard.
tried a wireless keyborad, a wired keyboard and a usb-stick all just seem to have power for some milliseconds.... then noting else can be noticed.
Click to expand...
Click to collapse
O.k., got it... so in fact there's nothing.
FrEcP said:
The only interseting difference i noticed is:
If i have my Keyboard plugged in while startup all lights (capslock,...) light up and STAY ON. Till i pull the plug. Then its like before...
Click to expand...
Click to collapse
That really sounds that there's still some power... like voom already pointed out.
Any measurements if there's some voltage drop or something?
Will need some equipment to do so, i guess.
FrEcP said:
Sadly an USB-Hub (powered) will neiter be recognised... (same bahaviour)
Click to expand...
Click to collapse
FrEcP said:
What i noticed - if i resome the device (after is was powered on) there are several wake up commands in dmesg for the screen and the usb hubs...
But it doesnt seem to me that the 2nd hub will get resumed proper... unless those command invoke both of em at once.
What does it tell for u when resuming the device?
Click to expand...
Click to collapse
I must admit, right now this tells me nothing...
Have to think about it.
Maybe we should compile a kernel with full debug output, at least for the USB part. This way we might get a clue what happens...
I wish a day would have some extra hours
Anyway i'll try to have a look in the kernel sources... looking for debugging as well.
Might take some time though, so you might try it yourself.
Regards,
scholbert

Thanks for the reply- well we are a bit further now as it seems.
Since archos released the lastest firmware .82 wich fixes this"bug" partialy
Anyway - the USB is working again with this version - but just until the device goes into standby without having an usb-device connected. Then u have to reboot to get it working again.
(all is fine if the device goes into standby with device connected)
So the big question is - what happens in between?
Well at least we know its software related now
I will check back dmesg again with this new firmware - and repost.
So the full debug kernel would be a nice idea - can u give me some adives how 2 start? I really have no clue about that yet.
I already compiled kernels in old suse 6.0 days but I think it will be different for "external" devices - I remember having read something about toolchain,...

tried a wireless keyborad, a wired keyboard and a usb-stick all just seem to have power for some milliseconds.... then noting else can be noticed.
Click to expand...
Click to collapse
With the dead port if I plug in a USB-Stick that has LED it lights up and then the light stops, while if it works (as it used to with working USB-Host on the Archos or when used with the PC) the LED stays on and constantly changes brightness. This LED behaviour is related to functioning dataflow.
On the other hand if I plug in a mouse with decorative LEDs in the dead port, the decorative LEDs, not related to dataflow, stay on, even though the mouse is not recognized. If I plugin a device that can be charged by USB it even shows that it is charging, though energyflow is probably not high enough to make that a practical use. Again in this case only the energyflow is relevant but no data activity.

I think I cooked my USB functionality.

Hey gang. Wondering if you can help me with a strange issue I've got. I can't seem to connect my phone to my computer via USB. Wondering if anyone could help determine if there's a possibility of repair or not.
==Possibly relevant info==
Samsung Vibrant
Android 2.2 Froyo
Kernel version: 2.6.32.9
Build number: FROYO.UVKB5
==End relevant info==
So, my USB is acting up. Has been for the last few months, where although it charges when I plug into a computer, it's not connecting to allow data transfer. I haven't been too terribly worried, this happened before then cured itself when I did a factory reset. The thing that usually triggered it was when I tried connecting to my linux box in media player mode. The phone would just kinda lock up, I'd have to restart it and then USB wouldn't connect. But after doing the factory reset it was fine the first time. THIS time however, since I'd just left it stock now I'm itching to flash a custom rom but even though I've wiped the whole stupid phone totally clean, it still won't connect. I'm trying to follow a method on an article on dkszone.net called "Bypass E - Signature Verification Fail Issue On Vibrant Android 2.2".
So it seems I need USB for the debug mode.
What I think my main problem is, and where I need some help, is that I had purchased a super cheapwad USB car charger off of amazon for like 35 cents. Every time I connected to it, my phone would ask me if I wanted to connect using kies, media player mode, or data storage mode. I thought it was annoying but didn't really think it would harm anything. But now that I'm thinking about it, it's probably been pumping 5v into each pin on the USB port, whereas the USB functionality uses probably 3.3v, and I'm afraid I cooked something.
The random part here though is that about 5% of the time it does (sortof) connect. It brings up the USB options when I want to connect, brings up the icon saying it's using debug mode, etc. But my machine just reports that it didn't recognize the USB device. So, I'm thinking it's on the fritz, but figured I'd check here to see if I could possibly find a ray of hope.

Scooterx3 said:
So it seems I need USB for the debug mode.
Click to expand...
Click to collapse
You can use ADB over tcpip. There's many a free widget to enable it on google play or Do it manually

Thanks for that, I had been wondering if there wasn't a way to do that over wifi. My issue is that sadly I haven't even rooted the phone. ADB over WiFi requires root, whether I do it manually or use one of those super sweet apps.

So anyways, guess what?
My brother in law has the same phone I do, and I grabbed his phone one day and plugged it into my computers and had the same problem as with my own, and I know he hadn't plugged into the same charger I had, hadn't tried the media mode on Linux like I had (which were what I thought were the big contributing factors). SO, I kept digging, found that I hadn't quite yet cleaned it properly. I'd tried my best to clean it but until I swabbed it well with some rubbing alcohol it wasn't as clean as it should've been.
Long story short, I'm backing everything up so I can start flashing roms.
Moral: just clean the dang thing really well

Google knows I'm rooted....

I have a rooted Nexus 7 running JDQ39. It is no longer recognized by my laptop or desktop, regardless of the cable I use. I have used the same laptop/desktop for months without issue. I think it's a hardware failure but I'm open to suggestion.
Anyway, I bought it through the Playstore so I called them for support and they said they could see that I "may be using a rooted device" and told me that I would have to contact the manufacturer or carrier but if unroot and still encounter the issue they will be glad to "take a look". They followed the conversation with the email below.
So it's interesting (but not surprising) that they can tell remotely.
Anyway, any suggestions on how to get back to stock/unrooted without a PC connection?
Thanks
[email protected]
X:XX PM (7 minutes ago)
to me
Hey there Xxx,
Thanks for contacting Google Play! According to our records, it appears you may be using a rooted device. Unfortunately, our ability to troubleshoot issues with rooted devices is limited. They may have altered functionality depending on how the device has been modified and we're not able to see what's happening with the device. For assistance with rooted devices, we recommend contacting your device manufacturer or carrier. However, if you unroot your device and still encounter this issue, please let me know and I will be happy to take a look.
If your device isn't rooted, please let me know, and I'm happy to see what I can do to assist you further. Thank you for your understanding.
Thanks,
Click to expand...
Click to collapse

I dont know about "calling in". But if you downloaded any app requiring root from the play store to that device, it would be a dead giveaway. Titanium backup, super su, rom manager............and the list goes on. That is most likely the reason the last line says "If you're not rooted". They are not "calling in", but simply looking at thier records (app history).
To the main problem, have you tried an alternate cable? I see you have tried multiple pc's, so the cable is the next step. That possibility needs to be eliminated before you can move on to a hardware and/or software failure.
Sent from my Nexus 7 using xda premium

junksecret said:
I have a rooted Nexus 7 running JDQ39. It is no longer recognized by my laptop or desktop, regardless of the cable I use. I have used the same laptop/desktop for months without issue. I think it's a hardware failure but I'm open to suggestion.
Anyway, I bought it through the Playstore so I called them for support and they said they could see that I "may be using a rooted device" and told me that I would have to contact the manufacturer or carrier but if unroot and still encounter the issue they will be glad to "take a look". They followed the conversation with the email below.
So it's interesting (but not surprising) that they can tell remotely.
Anyway, any suggestions on how to get back to stock/unrooted without a PC connection?
Thanks
Click to expand...
Click to collapse
I'd agree with the person above: they likely flagged some root-requiring apps you have on your device and went by that. Google's policy on roots is pretty forgiving, though, to say the least.
In any event, there are some on-device methods you could pursue, but we need to know more about your setup on that side as well. In a similar vein as to what previous poster asked (namely about testing computers and cables), could you link us the method you used to root your device and also post what recovery you're using (stock, TWRP, CWM, etc.) and if you have your bootloader unlocked?

Rirere said:
I'd agree with the person above: they likely flagged some root-requiring apps you have on your device and went by that. Google's policy on roots is pretty forgiving, though, to say the least.
In any event, there are some on-device methods you could pursue, but we need to know more about your setup on that side as well. In a similar vein as to what previous poster asked (namely about testing computers and cables), could you link us the method you used to root your device and also post what recovery you're using (stock, TWRP, CWM, etc.) and if you have your bootloader unlocked?
Click to expand...
Click to collapse
Thanks for the reply, I think I've exhausted the cable and usb port/pc/drivers as the cause. I actually now remember I hooked it up to my stereo and plugged into a cheap charger and got a pretty good spark at the micro usb and the tablet shut off. I left it plugged in and powered back up and thought all was fine. I now think that may have fried something in the micrco usb although it does charge thru it.
I think I rooted using wugfresh's rootkit, this is my 3rd N7 so not positive. I do have the bootloader unlocked and am running CWM Touch recovery.
Any links to a no-pc back to stock would be great!
Thanks

junksecret said:
Thanks for the reply, I think I've exhausted the cable and usb port/pc/drivers as the cause. I actually now remember I hooked it up to my stereo and plugged into a cheap charger and got a pretty good spark at the micro usb and the tablet shut off. I left it plugged in and powered back up and thought all was fine. I now think that may have fried something in the micrco usb although it does charge thru it.
I think I rooted using wugfresh's rootkit, this is my 3rd N7 so not positive. I do have the bootloader unlocked and am running CWM Touch recovery.
Any links to a no-pc back to stock would be great!
Thanks
Click to expand...
Click to collapse
Sent from my Nexus 7 using xda premium
Now we are getting somewhere. It seems you may have shorted a data pin when you plugged it in. I personally never use cheapo chargers. You could try replacing the USB port. If i am not mistaken, it is not soldered to the motherboard, but instead is soldered to its own harness and connected to the mobo via flex cable.

USB connection not seen at all, in system, fastboot or recovery,

Hi all,
Have just started to connect my device so i can pull the patched boot image for my thread and it won't see the computer, tried on several laptops and nothing, no adb, no fastboot.
It charges just fine but does not show the android usb system notification.
Really annoyed by this as i'm kind of stuck.
I'm on 7.7 but on a custom ROM / Evo X 5.9.1, doesn't look like anyone else has this issue besides me, have seen the odd user complaining about the same thing but haven't seen any fixes come up], if anyone has any ideas then i'd be grateful to get your two cents.
Will test MSM but it's not looking good, fearing a return to oneplus as i do have a good unit with none of the issues anyones ever listed like green screen and overheating problems.
It's usually me helping others but this time i need you guys help

Check USB cable / clean the Charging port? sometimes it helps.

dewa5227 said:
Check USB cable / clean the Charging port? sometimes it helps.
Click to expand...
Click to collapse
Aye I've cleaned it up mate.
Tried different cables, I think EDL mode is working.
Means I could maybe return to OOS but it wouldn't let me back up..
Shame, I'm just downloading MSM now... Really annoyed..will give the usb socket another clean

dladz said:
Tried different cables, I think EDL mode is working.
Click to expand...
Click to collapse
well, it's a good sign , hopefully, it will be resolved out.

dewa5227 said:
well, it's a good sign , hopefully, it will be resolved out.
Click to expand...
Click to collapse
Yea I'm dreading it being hardware. Never had this issue on OOS.
I think it may be Evo X but I don't know.
Bad luck I guess
Cheers anyway.

So MSM did indeed work, it's booting now, obviously couldn't back up any of the info on the device so i'm super annoyed at that but so long as usb connectivity works then i'll be happy with that.
USB Connectivity does NOT work now so i CAN connect to EDL mode but not normal usb conenctivity.
Anyone have any ideas???

Cannot root, install anything via ADB or even delete apps via ADB. Shocking problem to have man

I'm RMA'ing my phone, just getting it set up now.
Very painful process, they absolutely need the purchase order for warranty, things have changed with 1+
3-10 days apparently, used to be 5 when i've sent it in the past.

On connecting a USB hub i can read USB sticks and i can control my phone with an xbox pad??
Am i missing something? How is all this working yet i can't mount my phone?

Best bet, probably you broke the charging port. did you by any chance use like force usb charging like that?

dewa5227 said:
Best bet, probably you broke the charging port. did you by any chance use like force usb charging like that?
Click to expand...
Click to collapse
I did use the force USB charging yes.. wishing I hadn't now..
I also connected to a usb-c to hub to connect a screen.
Issues kind of started after that.
Physically I haven't damaged it from movement. But could be from the forced charging

UPDATE:
Erm ok this is confusing???
I just connected my phone to a charger that is clearly not rated for it, in the hope it would shock the device, i then connected my phone and made a cup of tea, when i got back my phone showed me this (screenshot attached)
??? Lol what the hell? I've already booked my RMA lmfao
anyway, i shall keep an eye on it, i'll thoroughly test it and get it back up and running.
Strange, very strange.