ATI Mobility Radeon X1350 - General Questions and Answers

ATI Mobility Radeon X1350
How to install drivers in Windows 8 (x64), Windows 8.1 (x64) and Windows 10 (x64):
Disable Driver Signature Enforcement in Windows 8
Settings (right hidden panel)
Change PC Settings
General
Advanced start-up
Restart now
Troubleshoot
Advanced options
Start-up Settings
Restart
F7
Install drivers
Download drivers
Ectract drivers
Right click on desktop
Screen resolution
Advanced settings
Properties
Update drivers
---> go to extracted drivers ..\10-2-mobile_legacy_vista32-64_dd_ccc_mod\Packages\Drivers\Display\CH_95951.inf
GL :good:
Thx fort article: http://forum.xda-developers.com/showpost.php?p=34129161&postcount=22
Code:
ATI Mobility Radeon X1350
HP Compaq 6820s
Windows 8 (x64) / Windows 8.1 (x64) / Windows 10 (x64)

In addition If you get "Windows has determined your drivers are up to date" you need to click the "Have disk" option when updating drivers.

Installed Windows 10 last night om my 6820s. Works well, advanced setting are unavailable but resolution is changeable (and automatically set to optimal values).
So, working in Windows 10 :good: Stability might be an issue, I have some issues with energy saving modes. Never had it again after the first 2 days, so all good.

With the arival and installation of the new build of Windows 10 (v 10586) the system is reinstalled. Keep in mind that unsigned drivers are not activated after the 'upgrade' process. Store the drivers in a save place and repeat the process in the op after the upgrade.

Installed ATI mobility Readon on my Compaq 6820s ..though its running on Windows 8.1.. But the problem is that when I shut it down ..and power it on again, the system begins to heat up quickly.. So I always herbanate it now so that it wont be heating up like that l..so how can I helped resolve this issue thanks.

Dario4 said:
Installed ATI mobility Readon on my Compaq 6820s ..though its running on Windows 8.1.. But the problem is that when I shut it down ..and power it on again, the system begins to heat up quickly.. So I always herbanate it now so that it wont be heating up like that l..so how can I helped resolve this issue thanks.
Click to expand...
Click to collapse
I didn't have this problem. I had some thermal issues but these were solved by cleaning the system fan an applying new thermalpaste.

Related

[Q] HD2 as external display for pc

Is there a program with which I could use my HD2 as an external display for my laptop. I don't mean remote control software.
Try SideWindow.
I know I used something else with my old Artemis, something free but I can't find it anymore. I remember installing the driver on my Vista x64 and having a really small second monitor in my control panel, I think it was based on VNC but it did work through wifi without active-Sync
Tried to install it, but without any luck on windows7...
This is the soft I used:
ZoneOS ZoneScreen for Windows Mobile
I tried again with my HD2, and, yep it works against an XP (using the 32-bit display driver), but can't see to load the driver on my vista x64, even disable the digital certificates.
I managed to get a second display on my XP box with a rel of 800x480 using a wifi connections.
Have a look at their wedsite, maybe they have some new driver for Vista/Win7
http://www.zoneos.com/zonescreen.htm

Windows 7 SP1 problems?

I installed SP1 x86 and my Captivate no longer was recognized by the computer. I tried reinstalling the drivers to no avail. Restored a backup of pre-SP1 and all was well again. Has anybody else come across this?
I was able to connect my wifes Captivate to my Win7 x64 SP1 machine last night.
no problems for me on Win 7 64x. did SP1 last week.
No Win7 x64 SP1 problems here, either.
Sent from my SAMSUNG-SGH-I897 using XDA App
Have you tried mounting it mass storage mode or debugging mode yet? That might kick it into action.
^^^ Ditto! ^^^
No Captivate issues here on SP1 (64 Bit) - a couple of other crashes though (might be more related to FF beta 12 though). Recognizes the Captivate just fine, but must admit I have only tried that in mass storage mode (usually connect in debugging).
You are tryin to connect with Debugging turned on right?
digger42 said:
I installed SP1 x86 and my Captivate no longer was recognized by the computer. I tried reinstalling the drivers to no avail. Restored a backup of pre-SP1 and all was well again. Has anybody else come across this?
Click to expand...
Click to collapse
After you restored, did you reapply SP1 to see if you could reproduce the problem? If not, you should reapply the service pack and see if the issue comes up again.
I run Win7 x64 SP1 and have no issues with connecting my Cappy.
I've noted it messes up the Windows Mobile Device Center (particularly the rndis driver) sync on 32-bit Windows7 after SP1 is installed. I've tested with 64-bit Windows7 and it works fine after SP1. I'm testing with Sony Ericcson X1.
bravo_3 said:
I've noted it messes up the Windows Mobile Device Center sync on 32-bit Windows7 after SP1 is installed. I've tested with 64-bit Windows7 and it works fine after SP1.
Click to expand...
Click to collapse
Was no issue for me and my WinMo phone, but that would have nothing to do with an Android phone since it doesn't use MDC.
Win 7 x64 with SP1 working fine with my Captivate
I have a special copy of Windows 7 Ultimate 64 bit SP1, no problems.
Sent from my Captivate
I started a thread about this a month ago and got laughed at.
The best thing I found was to turn off all non-essential updates after a system restore. What model of computer btw?
Miami_Son said:
Was no issue for me and my WinMo phone, but that would have nothing to do with an Android phone since it doesn't use MDC.
Click to expand...
Click to collapse
Android phones have nothing to do with Windows Live Essentials, but on my PC, it conflicts. ????
I duuno. There is something weird going on with some folks machines.
I had to re-install my drivers a few times to get it to take... but no issues after a reboot on a Win 7 x64 box.
avgjoegeek said:
I had to re-install my drivers a few times to get it to take... but no issues after a reboot on a Win 7 x64 box.
Click to expand...
Click to collapse
And that's probably what it is, a driver conflict. But I'll be damned if I can figure out why.
If it matters I run on my wifes HP Pavilion DV6 Windows 7 64.

Bluetooth Drivers for Windows 7 64 bit

Is there a Windows 7 Bluetooth driver for the G2x or LG phones in general? I've searched here and on Google with no luck.
I have two PC's with varying results:
Windows 7 32 bit with built in Bluetooth: Pairs fine, lets me browse files
Windows 7 64 Bit with USB Bluetooth: no driver found for Bluetooth Peripheral Device, same result on another 64 bit machine
Somehow the 32 bit machine has the drivers already?
Thanks!
no bluetooth peripheral driver on windows 7 64 bit
I Had The Same Problem
Solved as follows
installed windows mobile device driver 64 bit for windows vista 64 bit and windows 7 64 bit off windows mobile site
then i did the following
Install Windows Mobile Device Center.
The first step may solve your problem automatically. If it doesn't, however, Right Click on Computer Icon and Choose Manage.
Go To Device Manager.
You'll see an Unknow Device named Bluetooth Peripheral Device. Double Click it to open its properties.
Click "Reinstall Driver" on the first tab.
Click "Browse My Computer for Driver Software" button.
Cick on Buetooth Radio.
Click "Let Me Pick from a List of Device Drivers on my computer".
Now the next page will show a list of drivers with Company Names in one list and Drivers in another. In the Company List choose Microsoft Corporation, not only Microsoft. Please confirm this twice that you dont choose Micorosoft but Micorosoft Corporation.
Now in the drivers list there may be one or more drivers with the name "Windows Mobile-Based Device Support" with different driver versions. I cant tell you which will work for you, but start with the newest version.
Click next. Ignore any warnings and keep pressing next and then Finish at last. If all goes well, the last screen will show the message that device driver is properly installed.
If the last screen shows that device is not configured properly repeat the above steps choosing a different driver version this time.
it's ok with me.Thanks a lot my friend....

Problem with Driver Installation (Win. 7 64 Bit)

Hello. Just yesterday I had received my new Dell Inspiron 17R Notebook in the mail, which is running Windows 7 Home Premium 64 Bit (Other specs: 500 GB HDD, 8 GB RAM, NVIDIA GEFORCE GT 525M 1GB Graphics Chip, Intel Core i7 2.2GHz Quad Core CPU), and I went to go plug my Milestone into the USB port to copy all my music to this PC, and it wouldn't install the drivers. So I manually got them from the Motorola site, installed them, and still, nothing. And whenever I view the status of the installation of drivers when I click the bubble saying, "Found New Hardware, Installing Device Drivers" (Or whatever), it says MTP USB Device................Installing Driver Software. And it hangs there for a while, and then it has an X right next to the word, Failed. I've tried numerous suggestions, but nothing has worked. I really need these drivers to be installed!! Can anyone help?
Your problem is not connected to the MS or the Notebook.
If you have the debugging switched on ( Titanium suggests that for ex ) the MS wants to connect in Debug mode and you need the ADB drivers.
after connecting the phone, pull down the bar, select USB mode and select massstorage mode or switch of debug mode.

[Q] Nexus/Android with Win 8 is a pathetic story

Hello
:crying:
I got my N5 today, and like my wife's N7 and my N10, NONE of them will show up on windows explorer (windows 8.1)
I can unlock, root, install custom recovery, all good, but as far as actually SEEING my device on the computer so I can drag and drop stuff, well, I literally have been spending almost a day trying to sort that out and have not got any closer at all. It is really pathetic.
I've changed the windows Unsigned drivers thing (though the drivers must be ok if I can do all that other rooting etc)
But yet when I uninstall the drivers to try installing them again, win8 says "Android ADB Interface. The third party INF does not contain digital signature information"
But I'm pretty sure that when I reinstall them AGAIN, I will still nto be able to see any of my Nexus devices on Windows explorer... despite them showing up in the Windows Notification under USB, and they are mounted there... I can UNmount them!
Something is way off kilter here, its with 3/3 devices, perhaps win8.1 is completly Android unfriendly, or?
Advice/help MUCH appreciated for someone who is going nuts here.
tx
Mark.
Did you turn MTP off to install the drivers to make sure ADB is working correctly? If so, did you check it to turn it back on? I am having no issues with Windows 8.1.
Same in Windows 7, I can't see my mates N5 on my Windows 7 machine but it's fine on his (he got the generic drivers from Windows update whereas I had mine from the Google SDK so that might be something to do with it?...)
It's just hit-or-miss. It's not Windows 8.
My work computer got a fresh image about 2 months ago. I've plugged other Android devices in, but haven't plugged in a Nexus device (or one that utilizes MTP the same way). I plugged in the N5 when I got it, and it worked flawlessly. My gaming PC at home has the Android SDK installed and it worked perfectly there. My HTPC does not have the Android SDK installed and nothing shows up in My Computer at all.
It's a weird android thing.
Hello guys,
lowandbehold said:
Did you turn MTP off to install the drivers to make sure ADB is working correctly? If so, did you check it to turn it back on? I am having no issues with Windows 8.1.
Click to expand...
Click to collapse
I did turn it iff to ADB but do not see where I would turn it back on, but that may be it with my N5...
EddyOS said:
Same in Windows 7, I can't see my mates N5 on my Windows 7 machine but it's fine on his (he got the generic drivers from Windows update whereas I had mine from the Google SDK so that might be something to do with it?...)
Click to expand...
Click to collapse
I really dont know. I have 4 PC's in the house, and sometimes my old dell laptop (also 8.1) seems to be the most reliably connect-able.
hotleadsingerguy said:
It's just hit-or-miss. It's not Windows 8.
My work computer got a fresh image about 2 months ago. I've plugged other Android devices in, but haven't plugged in a Nexus device (or one that utilizes MTP the same way). I plugged in the N5 when I got it, and it worked flawlessly. My gaming PC at home has the Android SDK installed and it worked perfectly there. My HTPC does not have the Android SDK installed and nothing shows up in My Computer at all.
It's a weird android thing.
Click to expand...
Click to collapse
There has to be a physical reason for it (unless we are to consider the metaphysical - past lives, re-incarnation of gadgets, Steve Jobs curses and stuff...) and it does amaze me that it still seems so hit and miss. When I first got onto android a few years back, you just plugged your phone into USB, ANY ONE ON ANY COMPUTER and whammo, you'd get both Ext SD adn Int SD mounted... reliably. I'm sure that was causing security and stability issues so all manufacturers seem to have snuffed that out.
so that MTP toggle is at settings > Storage > settings in storage
but it makes no difference still not vis in WinExplorer
Cheers
Mark.
Settings/Storage then hit the advanced menu button on the top right to enter "USB computer connection" and make sure MTP is checked.
lowandbehold said:
Settings/Storage then hit the advanced menu button on the top right to enter "USB computer connection" and make sure MTP is checked.
Click to expand...
Click to collapse
Tx mate, yeah I tried but alas, makes no diffs...
Thanks, but sadly this is a really abysmal part of android... and used to be a major + of the platform.
Mark.
fredphoesh said:
Tx mate, yeah I tried but alas, makes no diffs...
Thanks, but sadly this is a really abysmal part of android... and used to be a major + of the platform.
Mark.
Click to expand...
Click to collapse
I had this problem extensively, when trying to Root my Nexus, I went through uninstalling and re-installing drivers repeatedly, it was obnoxious, but i did end up getting it to work, so don't necessarily give up. I am running Win 8.1 though, eventually i had to go through Wug's Root Kit, and into the advanced driver installation settings, and install the raw drivers. (By booting windows into disabling secure driver certs.) Once i did that it gave me significantly more access, also try toggling your camera one on, the PTM or something, and switching back and forth with MTP.
ZeroAlphawolf said:
I had this problem extensively, when trying to Root my Nexus, I went through uninstalling and re-installing drivers repeatedly, it was obnoxious, but i did end up getting it to work, so don't necessarily give up. I am running Win 8.1 though, eventually i had to go through Wug's Root Kit, and into the advanced driver installation settings, and install the raw drivers. (By booting windows into disabling secure driver certs.) Once i did that it gave me significantly more access, also try toggling your camera one on, the PTM or something, and switching back and forth with MTP.
Click to expand...
Click to collapse
I must say, I did leave that part out of my replies. I too installed the raw drivers using Wugs toolkit. Maybe that is the x-factor.
Enable USB debugging in developer options.
Sent from my Nexus 7 using Tapatalk
Nexus Root Toolkit includes a variety of USB drivers you can try, as well as a few utilities to help you diagnose and fix android driver problems. That's where I would start. You don't need to use it to root or anything (unless you want to) but the driver utilities in the toolkit have fixed a number of problems I've had with android drivers over the years. I currently have my nexus 5 / 7 / galaxy working fine on two computers with windows 8.1
Not really the same at all but I had a hard time getting my S3 to be recognized on my computer at work running XP.
In the end the problem was the generic USB drivers that were installed had to be manually removed; even the official Samsung drivers wouldn't overwrite them. After a bit of digging and prodding I got it to work.
My Nexus was recognized without issue on my Win 8 machine.
You'll have to try a variety of different drivers to get it to show up properly. My N4 and Note 3 had no issues showing up, but the N5 wouldn't. I had to uninstall all the old drivers and started with brand new Google drivers to get the N5 to show up. Now it's there.
This happens to me every single time with a new device so I know exactly what to do now. It's not a driver issue, it's a problem with windows 8 and how it searches for drivers.
If you have the Android SDK installed properly just open up device manager > right click on android device > Update driver software > browse my computer > Let me pick from a list of device drivers on my computer > select the google adb driver from here.
Another problem I had was remembering to accept the ADB on my phones end, I never had to do that with my HTC one, so when going through rooting the raw drivers were likely unnecessary, I just hadn't noticed the primly on my phone when the first drivers I installed worked.
Hello guys, thanks for the various responses...
ZeroAlphawolf said:
Wug's Root Kit, and into the advanced driver installation settings, and install the raw drivers
--------also try toggling your camera one on, the PTM or something, and switching back and forth with MTP.
Click to expand...
Click to collapse
lowandbehold said:
I too installed the raw drivers using Wugs toolkit. Maybe that is the x-factor.
Click to expand...
Click to collapse
I did initially install the raw drivers as they sounded like they would be best... will try the camera toggle and MTP toggle
rabidfurball said:
I currently have my nexus 5 / 7 / galaxy working fine on two computers with windows 8.1
Click to expand...
Click to collapse
Encouraging!!! I know from my SGS3 and 4 and some generic chinese tablets ive had that the driver installation can be a major PITA but eventually you do the same thing for the 5th time, and it works, with no (seemingly) logical reason.
Stories said:
I had to uninstall all the old drivers and started with brand new Google drivers to get the N5 to show up. Now it's there.
Click to expand...
Click to collapse
I did a fresh install of windows 8.1 just yesterday... so it was pretty clean!
KiNG OMaR said:
It's not a driver issue, it's a problem with windows 8 and how it searches for drivers. If you have the Android SDK installed properly just open up device manager > right click on android device > Update driver software > browse my computer > Let me pick from a list of device drivers on my computer > select the google adb driver from here.
Click to expand...
Click to collapse
Yeah, i have tried that and it says I have the best drivers already installed. Oddly I can use Nexus Root Toolkit fine, so there has to be something right about the drivers... just not the part that shows up on a computer.
I'm convinced there HAS to be some scientific way of doing this, its such a common problem, it would be great to really figure it out. The problem is, one has to try 100 things before it works, so it becomes almost impossible to know which actions to attribute as the solution!
tx again,
Mark.
a solution - possibly useful...
Hello guys
Following Wugfresh's instructions to the T...
I tried drivers Option 1, (Universal) and the result was exactly as with the Raw (Option 4) drivers... So I uninstalled the drivers, ran ran USBDeview and uninstalled 7 devices like "Google Nexus ADB Interface" and "USB Composite device" and "Nexus 10".
Then tried Option 2.
The installation did not go exactly according to Wugfresh visual guide, so I cant be certain, but I do know that installingPDANET drivers only work if you select MTP, otherwise it will not find the tablet/phone.
After the instalation, the app called PDANET installed on computer, not on my tablet. My PC showed a pop up notification when tablet USB debugging is turned on, but again, it was not visible in windows explorer.
I then was going to try Option 4 again, and Uninstalled drivers in device manager WHILE I STILL HAD THE TABLET STILL PLUGGED IN, so I am guessing though PDANET uninstalled, the drivers remained (which I think is what Wugfresh's process would have done if it had run according to plan. I ran USBDeview and uninstalled the same 7 devices.
Then
Plugged tablet back in to attempt Raw drivers, but all of a sudden, the device was recognised and for the first time visible fully in Internet Explorer!
So basically it seemed to be the PDANET drivers that worked, though I have no idea if that would have worked had I tried these drivers in the first place.
I hope that helps someone!
Cheers
Mark.
OP, are you running W8.1 64 bits or 32 bits ??
I had my Sony Viao running W8 64 bits & hated it, downgraded to W7 64 bits and it's very happy getting along with Nexus 7 - going to play with N5 later on. Good old Dell Latitude is running W7 32 bits and it's my main machine to unlock, root & flash and so far so good - yet, I was reading about someone running Vista and had issues with the usb drivers.
I have 2 fully licensed W8 safely tucked away and the way it's looking, I might never get out of W7 - let alone then upgrading to 8.1 for free - getting reminders from $S a few things already.
Most of the time, the mess are caused by conflicting drivers installed & loaded - I keep a clean & lean desktop to do these bench work, and even though it is a PITA, starting clean with minimal programs (and apps) installed is often a good start - turn off antivirus & firewall, especially if connectivity is not needed - enabled access only if it is required and/or necessary.
I've also noticed that on my Nexus 4 I can only access adb in PTP mode, doesn't work at all with MTP enabled.
Hello guys
Letitride said:
OP, are you running W8.1 64 bits or 32 bits ??
Most of the time, the mess are caused by conflicting drivers installed & loaded
Click to expand...
Click to collapse
64 on the two PC's in the same room, HTPC's and laptop are 32 I think, but I have not tried them. I did a fresh Win 8.1 install on Tuesday and had no drivers from any devices other than the ones I manually installed with Wug.
KiNG OMaR said:
I've also noticed that on my Nexus 4 I can only access adb in PTP mode, doesn't work at all with MTP enabled.
Click to expand...
Click to collapse
Yeah, well try the PDANET (worked for me, though was my last resort as I don't like to install stuff that is a/ meant for something else, b/has some software I dont need that comes with it... but I did manage to keep the drivers and UNinstall PDANET software by keeping the tablet plugged in when I uninstalled PDANET... try it.
tx
Mark.

Categories

Resources