I purchased an LG G4 H818P dual sim from Dubai. I've used the phone for about 2 weeks now and suddenly for absolutely no reason the left half of my screen has gone full black (split down the middle). The touch still works though. I have tried a hard reset which didn't work. On some forums people with the same problem said they removed the screen protector and it solved the problem. I did likewise but to no avail. Can anyone assist urgently please.
ads
Affichage des articles dont le libellé est gone. Afficher tous les articles
Affichage des articles dont le libellé est gone. Afficher tous les articles
lundi 21 septembre 2015
dimanche 20 septembre 2015
Why is the ambient display gone in some CM Roms?
I use Ressurrection Remix 5.5.5 on my Moto G and since the last update the ambient display is gone. I tried Bliss Pop, Stock CM, AOKP and none of the roms had the ambient display, will it come back in the future update? And if yes... when?
samedi 19 septembre 2015
Air View on lockscreen gone on lollipop? Any fix available?
The cool little feature on KitKat on the note 3 where you could hover your finger over the screen and it would make a trail without even touching it was really cool. Something that made all my iPhone pleb friends jealous of ( ͡° ͜ʖ ͡°) , but now it seems to be gone. About a year ago I tried out CM11 until I went back to TW earlier this year. I'm using AryaMod 7.2 on Lollipop 5.0 and I noticed this feature is gone. I've done some googling and found very little related results and none of them had a fix that worked or were for the "norm" owners that don't use custom roms etc. I was wondering if there was a fix out there that brings this feature back? I really loved it.
mardi 15 septembre 2015
touchscreen gone, ne way to make USB storage instead of charge?
I really need a guru here with this one! Dropped the phone last tuesday, screen cracked, and is no longer operable. Since the Nexus 4 has no SD card, I have no way of retrieving the data on it. When I plug the usb cable into the computer, it defaults to charging mode instead of mass storage mode to mount a drive on the computer. Screen is locked with my chosen pattern. Is there any way at all to make the the phone automatically mount the drive instead of going to charging mode?
vendredi 11 septembre 2015
Opo help no bootloader and recovery gone
I was trying to upgrade my opo and I found my bootloader was locked but to unlock it I needed a recovery installed and somehow it had dissapeared. Please help asap
jeudi 10 septembre 2015
Text message pop-ups gone?
I am probably one of the rare few that actually like the text message pop-up/preview when receiving a message. If I'm using another app or playing a game it enabled me to quickly reply without stopping what I was doing to go to the messaging app.
For some reason the pop-ups no longer work (I'm not sure they ever have since I got my G4). I have checked and unchecked the options in messaging settings several times, cleared cache and data of messaging app, rebooted, set lock screen to show all notifications etc. Even after doing all that the pop-up still does not show. All I get is the sound and the message symbol in the notification bar.
My phone is rooted, and I used the build prop edit to enable all apps in dual window. Other than that I haven't messed with anything else. Can someone give me an idea how to fix this? Is anyone else having the same problem? I really hope I can get it figured out without having to factory reset or something.
Sent from my VS986
For some reason the pop-ups no longer work (I'm not sure they ever have since I got my G4). I have checked and unchecked the options in messaging settings several times, cleared cache and data of messaging app, rebooted, set lock screen to show all notifications etc. Even after doing all that the pop-up still does not show. All I get is the sound and the message symbol in the notification bar.
My phone is rooted, and I used the build prop edit to enable all apps in dual window. Other than that I haven't messed with anything else. Can someone give me an idea how to fix this? Is anyone else having the same problem? I really hope I can get it figured out without having to factory reset or something.
Sent from my VS986
vendredi 4 septembre 2015
Touch screen gone whacky
After using the touch screen with wet hands, the touch sensitivity has screwed up on the left side of the display. Water had properly dried up but the touch wasn't working properly. But gradually the condition of the touch turned better but a long patch of the left side of the display doesn't detect touches properly/accurately/at all anymore. I have changed roms and all but it's a hardware problem so nothing fixes it. I used a developer option "pointer location" to give you guys an idea on how the condition of the touch is. Look at the left side. A long patch shows that touches aren't detected in that area. The patches are kinda circular.

What do I do now? :(

What do I do now? :(
jeudi 3 septembre 2015
TweetCaster has gone crazy! Any alternative Twitter app suggestion?
I have been using TweetCaster for over three years I think, it worked flawlessly for me, until now. Even when I disable app's notification, it still keeps notifying me, which is needless to say really annoying. So looking for an alternative. Could someone suggest me a simple twitter app, not with all the fancy animations or looks or anything, just a simple app with Twitlonger support and proper push notifications, that's all.
Thanks in advance.
Thanks in advance.
Updated to latest version of Xposed and notifications gone
I have done it 3 timmes and in every time the notifications when I swipe down completely lost.
Any with same problem?
Any with same problem?
lundi 31 août 2015
Volume down "click" gone
Hi guys! I'm from aus and bought a oneplus 2 from oppomart and I've had it for about 3 or 4 weeks. One day I pulled my phone out of my pocket and the volume down feels sticky. I'm thinking of opening it up but I just wondered if anyone has had this issue as well? Any tricks or anything? Cheers
[XT1527] Attempt to flash retUS into retLA has gone awry.
Hi all! I tried to flash 5.1 retus on a 5.0.2 retla variant (as the tutorial said it would work on all variants, and both are for XT1527) without unlocking the bootloader.
Sadly it won't boot (boots directly to bootloader) and can't go back to stock.
It says: 'version downgraded for boot' 'failed to validate boot image'
This is a problem because everything I find about it says that I should either unlock the bootloader or find a newer retla ROM to flash over. Sad part is that this version is not coming any soon.
I tried to unlock bootloader afterwards but since I've never checked the option inside Dev Options this is like a no-go.
Any ideas?
Sadly it won't boot (boots directly to bootloader) and can't go back to stock.
It says: 'version downgraded for boot' 'failed to validate boot image'
This is a problem because everything I find about it says that I should either unlock the bootloader or find a newer retla ROM to flash over. Sad part is that this version is not coming any soon.
I tried to unlock bootloader afterwards but since I've never checked the option inside Dev Options this is like a no-go.
Any ideas?
dimanche 30 août 2015
G Watch R Screen has gone very weird
Bad news. I dropped my G Watch R this morning from the bed on to a laminate floor, just a few feet, and now when I turn it on, I get this weird screen with a coloured snowstorm effect.
Any ideas if it's fixable or not?
Any ideas if it's fixable or not?
samedi 29 août 2015
Screwed up, need some help. (4.4.2 to 4.3 attempt gone bad)
Hello everyone out there! Long time lurker, first time poster.
So I've had what seems to be a soft brick on my verizon s3 (SCH-I535) and it is time to just lay it out here because (as always) I can't find the fix to MY problem (so selfish I know :eek:)
So let's start at the very beginning..
I have had my s3 for awhile now and I ended up rooting the phone to stay on 4.3. The biggest reason for this was to keep FoxFi working (I have no internet where I live and tethering is the only option). Once FoxFi was working for 4.4 I decided to go ahead and update but first I had to unroot which wasn't a big deal. I unrooted and voila! I was on 4.4.2!
Okay so I just tried ThePagel's methosd
When I upgraded, I noticed my FoxFi was VERY slow all of a sudden and being a gamer, I didn't like this one bit! So I thought to myself "Hey, just flash back to your 4.3 file."... as I hear all of your collective heads shaking in disappointment, followed by facepalms, I now see the error of my ways.. Attempting to flash back to 4.3 of course hung my phone up in Odin (It was stuck at SetupConnect I believe) and this led to my soft brick. Bummer...
So what have I attempted? Well I kept seeing this thread pop up, http://forum.xda-developers.com/show....php?t=2586319 but it's talking about the OTA for 4.3.... I was 4.4.2. I also attempted to fix the issue via this thread: http://forum.xda-developers.com/show....php?t=1840030 and alas, it fails me as well.
Now as far as errors for these trails, let's get down to what I see on my phone and what I see on odin..
When trying the Hero's method, Odin fails with this log:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> VRALEC.bootchain.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
On my phone, I get this log: (Under download mode of course)
ODIN MODE
PRODUCT NAME: SCH-I535
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
(In grey)
QUALCOMM SECUREBOOT: ENABLE
BOOTLOADER RP (or AP, can't tell) SWREV: 2
(in red)
SW REV CHECK FAIL : Fused 2 > Binary 0.
Right now I am downloading the file needed in ThePagel's fix but it is VERY slow (only dial up and satellite internet I **** you not, out here). When that gets done I will come back here and post the same logs for both the phone and ODIN should it not work.
I see there are a lot of fixes out there for various things but the problem is, I don't know exactly what is wrong with my phone. Of course if I try to turn it on normally I get the yellow triangle so the fact it turns on means it is a soft brick. I have also read a lot of threads talking about custom recovery but I don't know how this works. Does custom recovery get me back into recovery mode? Or is this only for when your phone is rooted. Anyway, I'd love to pick some brains on this matter and maybe someone sees something in the errors that I do not.
I apologize for my ignorance... all I wanted to do was go back to 4.3 and root it to stay there.. if this can not be done and I am forced to stay with 4.4.2, I will do so.. but any advice for either would be a great welcomed sight. Send links to threads and what have you if you don't want to type, other than to call me an idiot, I deserve it for not reading and understanding everything fully before attempting this flash.
Okay I just tried ThePagel's method and this is what I get:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_I535VRUCNC1_I535VZWCNC1_2198062_REV09_user_low _ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
On my phone, everything looks the same except the last line reads:
SW REV CHECK FAIL : Fused 2 > Binary 1.
So.....what do you guys think?
So I've had what seems to be a soft brick on my verizon s3 (SCH-I535) and it is time to just lay it out here because (as always) I can't find the fix to MY problem (so selfish I know :eek:)
So let's start at the very beginning..
I have had my s3 for awhile now and I ended up rooting the phone to stay on 4.3. The biggest reason for this was to keep FoxFi working (I have no internet where I live and tethering is the only option). Once FoxFi was working for 4.4 I decided to go ahead and update but first I had to unroot which wasn't a big deal. I unrooted and voila! I was on 4.4.2!
Okay so I just tried ThePagel's methosd
When I upgraded, I noticed my FoxFi was VERY slow all of a sudden and being a gamer, I didn't like this one bit! So I thought to myself "Hey, just flash back to your 4.3 file."... as I hear all of your collective heads shaking in disappointment, followed by facepalms, I now see the error of my ways.. Attempting to flash back to 4.3 of course hung my phone up in Odin (It was stuck at SetupConnect I believe) and this led to my soft brick. Bummer...
So what have I attempted? Well I kept seeing this thread pop up, http://forum.xda-developers.com/show....php?t=2586319 but it's talking about the OTA for 4.3.... I was 4.4.2. I also attempted to fix the issue via this thread: http://forum.xda-developers.com/show....php?t=1840030 and alas, it fails me as well.
Now as far as errors for these trails, let's get down to what I see on my phone and what I see on odin..
When trying the Hero's method, Odin fails with this log:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> VRALEC.bootchain.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
On my phone, I get this log: (Under download mode of course)
ODIN MODE
PRODUCT NAME: SCH-I535
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
(In grey)
QUALCOMM SECUREBOOT: ENABLE
BOOTLOADER RP (or AP, can't tell) SWREV: 2
(in red)
SW REV CHECK FAIL : Fused 2 > Binary 0.
Right now I am downloading the file needed in ThePagel's fix but it is VERY slow (only dial up and satellite internet I **** you not, out here). When that gets done I will come back here and post the same logs for both the phone and ODIN should it not work.
I see there are a lot of fixes out there for various things but the problem is, I don't know exactly what is wrong with my phone. Of course if I try to turn it on normally I get the yellow triangle so the fact it turns on means it is a soft brick. I have also read a lot of threads talking about custom recovery but I don't know how this works. Does custom recovery get me back into recovery mode? Or is this only for when your phone is rooted. Anyway, I'd love to pick some brains on this matter and maybe someone sees something in the errors that I do not.
I apologize for my ignorance... all I wanted to do was go back to 4.3 and root it to stay there.. if this can not be done and I am forced to stay with 4.4.2, I will do so.. but any advice for either would be a great welcomed sight. Send links to threads and what have you if you don't want to type, other than to call me an idiot, I deserve it for not reading and understanding everything fully before attempting this flash.
Okay I just tried ThePagel's method and this is what I get:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_I535VRUCNC1_I535VZWCNC1_2198062_REV09_user_low _ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
On my phone, everything looks the same except the last line reads:
SW REV CHECK FAIL : Fused 2 > Binary 1.
So.....what do you guys think?
vendredi 28 août 2015
Power Saver Mode Gone?
Hello all,
So as we all know, Verizon has removed the Power Saver feature from the htc m9 (but we still have access to Extreme Power Saver). To get around this limitation I was using Nova Launcher, creating a short cut to "Activities", and enabling the powersaver.activity (or something like that).
However, with the latest update from Verizon that option doesn't seem to work anymore...
Is there a way around this? I can't even root my phone to access it, and all I really want is access to the feature that is already on the phone!
Thanks!
So as we all know, Verizon has removed the Power Saver feature from the htc m9 (but we still have access to Extreme Power Saver). To get around this limitation I was using Nova Launcher, creating a short cut to "Activities", and enabling the powersaver.activity (or something like that).
However, with the latest update from Verizon that option doesn't seem to work anymore...
Is there a way around this? I can't even root my phone to access it, and all I really want is access to the feature that is already on the phone!
Thanks!
Newb Flashing Gone Wrong?????
Ok .... first attempt flashing with Odin.
Note Edge from Sprint ROM to UK Stock ROM.
Followed the following instructions:
Instructions
Extract (unzip) the firmware file
Download Odin v3.09
Extract Odin ZIP file
Open Odin v.3.09
Reboot Phone in Download Mode (press and hold Home + Power + Volume Down buttons)
Connect phone and wait until you get a blue sign in Odin
Add the firmware file to AP / PDA
Make sure re-partition is NOT ticked
Click the start button, sit back and wait few minutes
And this was the result:
<OSM> N915FYXXU1BOC3_N915FYOXA1BOC3_N915FYXXU1BOB5_HOME. tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<OSM> All threads completed. (succeed 0 / failed 0)
<OSM> All threads completed. (succeed 0 / failed 0)
Soooooooooooooooo still plugged in lol. Next Steps help please!!!!!
Note Edge from Sprint ROM to UK Stock ROM.
Followed the following instructions:
Instructions
Extract (unzip) the firmware file
Download Odin v3.09
Extract Odin ZIP file
Open Odin v.3.09
Reboot Phone in Download Mode (press and hold Home + Power + Volume Down buttons)
Connect phone and wait until you get a blue sign in Odin
Add the firmware file to AP / PDA
Make sure re-partition is NOT ticked
Click the start button, sit back and wait few minutes
And this was the result:
<OSM> N915FYXXU1BOC3_N915FYOXA1BOC3_N915FYXXU1BOB5_HOME. tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<OSM> All threads completed. (succeed 0 / failed 0)
<OSM> All threads completed. (succeed 0 / failed 0)
Soooooooooooooooo still plugged in lol. Next Steps help please!!!!!
mercredi 26 août 2015
Bootloader gone?
I downloaded the "Retail Canada (1GB)" firmware as listed in this post:
http://forum.xda-developers.com/2015...mages-t3169639
I went to install it via the guide linked at the beginning of the first post. The command mfastboot flash motoboot motoboot.img didn't complete because no such file (motoboot.img) existed in that archive. The guide said nothing of this, so I continued with the other steps until the end (every other one said 'okay'), finally issuing the reboot command.
Now the phone won't boot up because, I assume, I no longer have a bootloader. I just get a black screen. If I plug in the USB cable to my computer, I can hear the sound of a device being connected, but it just shows as a Qualcomm device in Device Manager. Pressing and holding the power and volume-down keys seems to reboot the device (I hear Windows chime that a USB device was disconnected, then reconnected) but nothing ever comes on the screen. ADB/Fastboot commands just say "waiting for device".
Is the phone done? If so, then that's pretty lousy that the archive for the stock ROM doesn't contain the bootloader file that I apparently need.
Yes, my bootloader was unlocked because I had installed TWRP to try out the CM ROM before deciding to return to the stock ROM.
http://forum.xda-developers.com/2015...mages-t3169639
I went to install it via the guide linked at the beginning of the first post. The command mfastboot flash motoboot motoboot.img didn't complete because no such file (motoboot.img) existed in that archive. The guide said nothing of this, so I continued with the other steps until the end (every other one said 'okay'), finally issuing the reboot command.
Now the phone won't boot up because, I assume, I no longer have a bootloader. I just get a black screen. If I plug in the USB cable to my computer, I can hear the sound of a device being connected, but it just shows as a Qualcomm device in Device Manager. Pressing and holding the power and volume-down keys seems to reboot the device (I hear Windows chime that a USB device was disconnected, then reconnected) but nothing ever comes on the screen. ADB/Fastboot commands just say "waiting for device".
Is the phone done? If so, then that's pretty lousy that the archive for the stock ROM doesn't contain the bootloader file that I apparently need.
Yes, my bootloader was unlocked because I had installed TWRP to try out the CM ROM before deciding to return to the stock ROM.
Spark symbol gone after update
How long has the little spinning spark symbol been missing up top? I did the ota 2 days ago im guessing that took it off? Or am i not getting spark? Can someone let me know if the spinning star is suppose to be gone?
Sent from my SM-G920P using XDA Free mobile app
Sent from my SM-G920P using XDA Free mobile app
mardi 25 août 2015
Update fail, then touchwiz gone - any hope?
Spring L720T "Spark" model Samsung S4 running 5.0.1 phone is rooted but running stock ROM.
This is wife's phone so I don't have every detail as she apparently didn't pay a ton of attention to what was going on.
Some sort of OTA update apparently came through and tried to install itself. It warned that there as not enough room to perform the install. She uninstalled a program, went back to the system update and hit 'try again'.
The next time she looked it had booted into recovery mode with the following errors:
Finding update package....
E:unknown volume for path [@cache/recovery/block.map]
E:Can't mount @/cache/recovery/block.map
E:invalid volume path...check recovery.fstab
It gave this message twice and then aborted installation. I didn't see that information until just now or I would have tried to find recovery.fstab already. As it is, I don't know where that file lives but I will go try to find it.
She rebooted the phone and now when it boots, it gives a "unfortunately, system ui has stopped error".
Because of that, Touchwiz doesn't seem to be working. Home button does nothing, the notification bar is gone, no swipe down, etc.
I tried rebooting.
I tried taking out SIM, sdcard, and battery, letting it sit for a minute, then reinstalling all three and rebooting - no luck.
I tried booting into recovery, clearing the cache partition and then rebooting - no change.
I decided I would install a new launcher and maybe that would fix it. I can't get a launcher to complete the installation process within the play store. It will download and get partway through installing and then just hang.
Any ideas about what we can do to fix the problem? Is there a touchwiz update somewhere that I can install to fix the issue maybe? Any other ideas?
Thanks in advance for your help!
This is wife's phone so I don't have every detail as she apparently didn't pay a ton of attention to what was going on.
Some sort of OTA update apparently came through and tried to install itself. It warned that there as not enough room to perform the install. She uninstalled a program, went back to the system update and hit 'try again'.
The next time she looked it had booted into recovery mode with the following errors:
Finding update package....
E:unknown volume for path [@cache/recovery/block.map]
E:Can't mount @/cache/recovery/block.map
E:invalid volume path...check recovery.fstab
It gave this message twice and then aborted installation. I didn't see that information until just now or I would have tried to find recovery.fstab already. As it is, I don't know where that file lives but I will go try to find it.
She rebooted the phone and now when it boots, it gives a "unfortunately, system ui has stopped error".
Because of that, Touchwiz doesn't seem to be working. Home button does nothing, the notification bar is gone, no swipe down, etc.
I tried rebooting.
I tried taking out SIM, sdcard, and battery, letting it sit for a minute, then reinstalling all three and rebooting - no luck.
I tried booting into recovery, clearing the cache partition and then rebooting - no change.
I decided I would install a new launcher and maybe that would fix it. I can't get a launcher to complete the installation process within the play store. It will download and get partway through installing and then just hang.
Any ideas about what we can do to fix the problem? Is there a touchwiz update somewhere that I can install to fix the issue maybe? Any other ideas?
Thanks in advance for your help!
Inscription à :
Articles (Atom)