Related
I recently upgraded to wm6 from the t-mobile site. At first it was running flawlessly and very fast. I have installed windows live, resco and tcmp and still things were quick. after a few weeks, strange things started happening. When i went to my SMS/MMS and began to write a message, the flashing cursor would move along as i typed but no letters would show up on the screen. If i saved this message inot drafts then opened it again, i could then see all the text i had written and was previously hidden.
Soon aftet this started happening, the same began in windows live, then word etc...
recently, my athena has started to crash within an hour of a reset. Most of the time, if i start a program, just the bar at the top will load and nothing else, this is most serious in SMS/MMS. also, when this happens and i got to memory (the start menu and setting tab are still quick) it shows that i always have over 50 meg of ram left. Although, if this helps at all, the device runs slowest when turned on from sleep mode. Before i put the device in sleep mode, when i goto file explorer i can hear the microdrive fire up and this programme runs slow. after if has been in sleep for 20 mins or so, file explorer will never boot up properly and there is no noise from the microdrive.
I have tried hard rest, starts fast again, then slows to nothing after few days. I have tried various tweaks i have seen on here, such as disabling autooff and disabling the x-button programme. I have run spybot and antovirus software and nothing. Anyone got any ideas? thank you in advance
more
not sure if this is related but using pocket hack master; firstly, this programme hangs on all bu the last speed test. also, in the processes, there is one with a large red x picture with it. not sure if this is normal but jus thought id mention it
ballsquid said:
not sure if this is related but using pocket hack master; firstly, this programme hangs on all bu the last speed test. also, in the processes, there is one with a large red x picture with it. not sure if this is normal but jus thought id mention it
Click to expand...
Click to collapse
There are many many programs out there which hangs my devices and cause the behaviour you described. pocket hack master is one of them, which strangely works for others but not my device. Anothe is Touch Commander.
I usually uninstall the software once they cause freezes.
Try installing and testing your software one at a time to isolate it.
got a feeling it could be windows live. Unfortuantly, this is probably the programme i use the most. Is there any known issue with this?
ballsquid said:
got a feeling it could be windows live. Unfortuantly, this is probably the programme i use the most. Is there any known issue with this?
Click to expand...
Click to collapse
I personally have had no problem with it, but sometimes one person's experience is not definitive. Try turning it off and see what happens.
mysterious double post deleted
i uninstalled all programmes and it seemed fine but when i put windows live back on. the problem started again. im using build 10.00026 i think. is there a later version than this that could help?
ballsquid said:
i uninstalled all programmes and it seemed fine but when i put windows live back on. the problem started again. im using build 10.00026 i think. is there a later version than this that could help?
Click to expand...
Click to collapse
I think PK ROM is likely to have the latest version, but Powell is the one who could confirm this.
eaglesteve said:
I think PK ROM is likely to have the latest version, but Powell is the one who could confirm this.
Click to expand...
Click to collapse
yes my roms have the latest build(18533 even though theres newer builds not available to public or been ported yet to athena) and the aboslute latest live 33.600 which is still latest in the roms i have from latest devices like polaris and dual
Hi guys!
I'm experiencing a serious problem with my X10: Using the stock camera app causes (50% and more of times) a reboot of the device
I'm still stuck with the R1FA016 firmware (Spanish, Movistar) and i thougt this could be the problem since nobody seems to have a so bad experience
Today i tried the Vignette app on the market and the bug is still there... what could be the problem?
Thank you.
sleepyManX1 said:
Hi guys!
I'm experiencing a serious problem with my X10: Using the stock camera app causes (50% and more of times) a reboot of the device
I'm still stuck the R1FA016 firmware (Spanish, Movistar) and i thougt this could be the problem since nobody seems to have a so bad experience
Today i tried the Vignette app on the market and the bug is still there... what could be the problem?
Thank you.
Click to expand...
Click to collapse
I know it is painful, but have you tried formatting the device (restore factory settings)?
mmmm... i was thinking about it... do you think it could be a solution?
sleepyManX1 said:
mmmm... i was thinking about it... do you think it could be a solution?
Click to expand...
Click to collapse
If you're using a task killer, check out you are not killing any camera app.
No i'm not killing camera app... (anyway, atk is set to kill apps every half hour)
I just formatted the phone and the bug seems to be still here... rebooting occours even if, in Mediascape i try to view taked photos!!!
sleepyManX1 said:
No i'm not killing camera app... (anyway, atk is set to kill apps every half hour)
I just formatted the phone and the bug seems to be still here... rebooting occours even if, in Mediascape i try to view taked photos!!!
Click to expand...
Click to collapse
Then, try one more thing: uninstall ATK, reboot the phone and let it handle the RAM as it is supposed to.
Perhaps ATK is the culprit! I know it caused me a great deal of problems in the past, until I finally realised that task managers do more harm than good on android operating systems.
@sleepyManX1
the update is out already try OTA update......
I also tried to insert photo app and some services (such as facerecognition) in atk ingore list... the bug is still here
So i'm trying this way: disable atk from autostart...
junexyz said:
@sleepyManX1
the update is out already try OTA update......
Click to expand...
Click to collapse
Not according to my phone
(Movistar firmware)
arh!!!!
ATK disabled and the bug is still here!!!!!
My_Immortal said:
Then, try one more thing: uninstall ATK, reboot the phone and let it handle the RAM as it is supposed to.
Perhaps ATK is the culprit! I know it caused me a great deal of problems in the past, until I finally realised that task managers do more harm than good on android operating systems.
Click to expand...
Click to collapse
I've tried a lot of task killers/managers and at the end something started not to work properly. Since i don't use them everything is always ok! I recommend not to use them!!
Hi guys!
Any suggestion about this issue?
(I restored factory settings again and did not install any task manager/killer... still the bug is here )
Try to re-install firmaware using SEUS Wish you all the best
Yes... seems to be the only way... and i think i will flash the phone with a generic italian firmware... maybe the problem is in the movistar brand...
I just need a windows pc... (i've a ppc ibook... so no virtualization possible!)
sleepyManX1 said:
Yes... seems to be the only way... and i think i will flash the phone with a generic italian firmware... maybe the problem is in the movistar brand...
I just need a windows pc... (i've a ppc ibook... so no virtualization possible!)
Click to expand...
Click to collapse
I also have this problem with my desire, apparently after a search in XDA, problem exists in Nexus one (which is like HTC desire anyway) and HTC G1, G2.
seems no solution yet, I flashed my phone and installed the latest radio and a custom rom, still no solution.
hope someone can fix it
sleepyman x1 i too am on the same firmware as u and get the exact same problem im on three network uk, iv tried everything and nothing seems to solve it,,,, the only thing iv found that helps the camera bot up next time is when finished using the camera is to press the back button to exit camera mode and not to use the home button,
hope this is some help to you,
any updates of this would be great, the update doesnt seem to be there for my reigon yet, ( According to SE anyway ) they pretty much told me to sit tight and wait for he 2.1 in the last 4 mths of this yr
Shonan_ said:
sleepyman x1 i too am on the same firmware as u and get the exact same problem im on three network uk, iv tried everything and nothing seems to solve it,,,, the only thing iv found that helps the camera bot up next time is when finished using the camera is to press the back button to exit camera mode and not to use the home button,
hope this is some help to you,
any updates of this would be great, the update doesnt seem to be there for my reigon yet, ( According to SE anyway ) they pretty much told me to sit tight and wait for he 2.1 in the last 4 mths of this yr
Click to expand...
Click to collapse
I'll try this... but i'm really going to flash my x10 with a generic or an italian firmaware.
Thank you.
PS. Just today forced SEUS to reinstall my original firmware and the bug is still here... in the next days i'll try with an X10i_Generic_Italian (X10i_Custom_IT_Release_R2BA026)...
Let me kno how u get on bud. ?? Would like to see the out come
Sent from my X10i using XDA App
Be sure that i'll keep you informed
I also have "reboot" problem, but my phone reboots random - sometimes when I use Google Maps, sometimes when finish phone call, even sometimes when the phone is idle. I tried factory reset several times, updated to latest firmware (currently R2BA026) but no luck.
These days I will go to my local SE support center, I have no choice ...
I already charge my battery to 100%, when the update download to 128m/128m, it stop at there and wait for a long time, it say your phone did not have enought battery.I already try many times already, everytime fail to update it. plzzz..... help me..
exander87 said:
I already charge my battery to 100%, when the update download to 128m/128m, it stop at there and wait for a long time, it say your phone did not have enought battery.I already try many times already, everytime fail to update it. plzzz..... help me..
Click to expand...
Click to collapse
Use xp instead of seven/vista
Yeah, that is correct..... and freaking weird! Damn SE, we all use Win7 by now and none of the pcs I tried (many!) worked! Only with my old Laptop with XP, I can update these crap phones!
michaelthemage said:
Yeah, that is correct..... and freaking weird! Damn SE, we all use Win7 by now and none of the pcs I tried (many!) worked! Only with my old Laptop with XP, I can update these crap phones!
Click to expand...
Click to collapse
well thats not true i have always updated my phone using windows 7 only and it works
[email protected] said:
well thats not true i have always updated my phone using windows 7 only and it works
Click to expand...
Click to collapse
Yes sometimes it works, but if you want a thing that "always works", XP (even virtualized) is the os to use, to flash Xperia, and to flash anything else.
[email protected] said:
well thats not true i have always updated my phone using windows 7 only and it works
Click to expand...
Click to collapse
Calling me a liar, Punk??? I said I (!) tried and none worked! How the freak can you say this is not true???
i still can't update even using winXP. The result still same."when the update download to 128m/128m, it stop at there and wait for a long time, it say your phone did not have enought battery." i'm very very very disapointed buying X2.
i can't make a video call,can't playing video file perfactly. there is other way to fix that?.... or should i just burn the phone in flame....
Try a different PC, to see if there's somethying wrong in the your usb port.
If even that desen't fix the problem, I'm afraid that your only option is to bring back the phone to SE for repair.
What is the predicted exlorer? If u connect to the SE Update page with Mozilla, it doesn,t work properly. I dont,t know why, but during the proces of upadting screen wrote me, that it is not possible to make update.
When i change Mozilla by Microsoft Explorer it work perfectly and update has been downloaded cerrectly.
My advice - use Microsoft Explorer, and don.t care about battery capacity. /if is more than 50 %./
By and write me.
Why use a browser for update ?
Just download SEUS and install it.
Hi.
I have got the same problem. I have R1BA023 on my X2, but I want MR2. SEUS downloaded software and started upgrading. Status bar is empty and skips at one moment to full. Then add-on says "your phone did not have enought battery", but battery is fully charged. I tried on XP and Win7, downloaded SEUS on Explorer and Firefox browsers, but it's the same. Is it a SEUS bug or is it my X2's fault ? Is there any other way to install MR2 (without using SEUS) ?
I hope it is OK to start such a general thread and that this is the correct sub forum for it.
I am an owner of a 2012 Nexus 7 who also purchased the 2013 Nexus 7. While there are many improvements in the new 2013 nexus 7 (speed, display, etc.) there seem to also be frustrating problems that a number of users (including myself) have all encountered with no satisfactory solution resulting in much wasted time. I thought it would be useful to put them together in one thread and see what they may possibly have in common.
1. Usb connection to a pc. The device is not recognized to permit usb file transfers. Many potential solutions have been suggested (mtp/ptp off/on, usb debugging off/on, etc.) but these have not worked for me and many others.
(Potential work around: flash stick and stickmount work for me for file transfers. Another slower method is wifi transfer using ES Explorer, or email attachments).
2. Adb device is not recognized when using WugFresh toolkit. Faulty drivers, user error, etc have been blamed. I've tried them all with no benefit. Still can't get the Nexus recognized despite numerous attempts and methods.
(I'm no expert but I suspect the problem is probably related to #1. The pc cannot detect the adb device in those cases because it cannot detect the Nexus in the first place).
3. GPS problems. Supposedly helped (or worsened) by latest update. Don't know because I don't use GPS much and have not installed the latest OTA update, afraid it will mess up my root and I won't be able to get WugFresh to detect the Nexus again. (Took me days of attempts the first time).
There are probably other problems but the above are the most common ones.
If the moderators agree, I think this thread might be useful.
Just the tip of the iceberg.
With the exception of your #3, most users won't see the issues that you've listed.
Check this thread out - an interesting read ....
https://productforums.google.com/forum/#!topic/mobile/mG4JXaT-SHs[1-25-false]
danvee said:
Just the tip of the iceberg.
With the exception of your #3, most users won't see the issues that you've listed.
Check this thread out - an interesting read ....
https://productforums.google.com/forum/#!topic/mobile/mG4JXaT-SHs[1-25-false]
Click to expand...
Click to collapse
You are correct. I did not want to overload the list.
I too have had the random freezes and occasional reboots.
I have something to add here. I keep my nexus 7.2 (2013) in a moko case and often use it with the case folded back all the way. When the freezes occur, I noticed that if I move the case cover slightly away, the freeze stops, and when I bring it back, it freezes again. So, in my opinion, the freezing is magnet related. If so, a weaker magnet or more back padding might help with that. I've had no freezing when I use the Nexus out of the case. Have not yet tried additional shielding.
Try a different USB cable / port.
And toolkits are lame. Use fastboot.
#1 and #2 have to do with older drivers confusing your installation. If you work on it, almost everyone that has posted has eventually gotten both to work.
#3 GPS issue is fixed. There's an update you can use to just get the GPS fix and nothing else, no OS upgrade, no loss of data, etc.
http://forum.xda-developers.com/showthread.php?t=2421373
beware of the "the problems only represent a small vocal group blah blah" posts you'll get. I ended up returning mine to best buy for good today. I couldn't find myself dealing with and trying to replace this unit x amount of times to get a properly working one. Back to the drawing board I go.
I don't think any other device in the history of Android devices I've owned has a more 'vocal' group of problems in the General/A&A forums. It's ridiculous how bad the quality control for this tablet is.
I experienced #1 with my original N7.
And that was USB driver issue. I fixed it by, really, removing all kind of drivers that are on my pc (Win7 64).
I remember uninstall all the drivers as well from the device manager, right click uninstall.
I tried removing drivers from WugFresh and it did not work.
Then #2, I managed to use the PDAnet driver.
Now, it's working for both MTP and ADB
Anderson2 said:
I hope it is OK to start such a general thread and that this is the correct sub forum for it.
I am an owner of a 2012 Nexus 7 who also purchased the 2013 Nexus 7. While there are many improvements in the new 2013 nexus 7 (speed, display, etc.) there seem to also be frustrating problems that a number of users (including myself) have all encountered with no satisfactory solution resulting in much wasted time. I thought it would be useful to put them together in one thread and see what they may possibly have in common.
1. Usb connection to a pc. The device is not recognized to permit usb file transfers. Many potential solutions have been suggested (mtp/ptp off/on, usb debugging off/on, etc.) but these have not worked for me and many others.
(Potential work around: flash stick and stickmount work for me for file transfers. Another slower method is wifi transfer using ES Explorer, or email attachments).
2. Adb device is not recognized when using WugFresh toolkit. Faulty drivers, user error, etc have been blamed. I've tried them all with no benefit. Still can't get the Nexus recognized despite numerous attempts and methods.
(I'm no expert but I suspect the problem is probably related to #1. The pc cannot detect the adb device in those cases because it cannot detect the Nexus in the first place).
3. GPS problems. Supposedly helped (or worsened) by latest update. Don't know because I don't use GPS much and have not installed the latest OTA update, afraid it will mess up my root and I won't be able to get WugFresh to detect the Nexus again. (Took me days of attempts the first time).
There are probably other problems but the above are the most common ones.
If the moderators agree, I think this thread might be useful.
Click to expand...
Click to collapse
albundy2010 said:
Try a different USB cable / port.
And toolkits are lame. Use fastboot.
Click to expand...
Click to collapse
Used a different cable, different pc, different port. No difference.
I would use fastboot but am a newbie and it is over my head to do that. Afraid I'll really mess things up.
gogol said:
I experienced #1 with my original N7.
And that was USB driver issue. I fixed it by, really, removing all kind of drivers that are on my pc (Win7 64).
I remember uninstall all the drivers as well from the device manager, right click uninstall.
I tried removing drivers from WugFresh and it did not work.
Then #2, I managed to use the PDAnet driver.
Now, it's working for both MTP and ADB
Click to expand...
Click to collapse
#1 I believe the Nexus connected fine before I used WugFresh which made me uninstall a bunch of drivers. I now think maybe I uninstalled some essential driver but have no way to restore things because the restores don't go back far enough.
#2 where do I get the PDAnet driver?
sfhub said:
#1 and #2 have to do with older drivers confusing your installation. If you work on it, almost everyone that has posted has eventually gotten both to work.
#3 GPS issue is fixed. There's an update you can use to just get the GPS fix and nothing else, no OS upgrade, no loss of data, etc.
http://forum.xda-developers.com/showthread.php?t=2421373
Click to expand...
Click to collapse
I've been working on it for several days now. Hours and hours of wasted frustrating time. Tried everything suggested (which may be part of the problem). Need someone to talk me through it once. There really should be a direct download of the necessary windows 7 drivers I could just download and install on the pc and solve the problem.
#3 I'm rooted with stock rom. I don't use GPS much so that is not a major problem.
The major problem is that though I'm rooted I can't do a Nandroid backup and without it it's scary for a newbie to do anything that could mess things even further. Took me days to get WugFresh's adb recognized and finally root in a few minutes after that.
"Wish you were here...... "
Anderson2 said:
I've been working on it for several days now. Hours and hours of wasted frustrating time. Tried everything suggested (which may be part of the problem). Need someone to talk me through it once. There really should be a direct download of the necessary windows 7 drivers I could just download and install on the pc and solve the problem.
#3 I'm rooted with stock rom. I don't use GPS much so that is not a major problem.
The major problem is that though I'm rooted I can't do a Nandroid backup and without it it's scary for a newbie to do anything that could mess things even further. Took me days to get WugFresh's adb recognized and finally root in a few minutes after that.
"Wish you were here...... "
Click to expand...
Click to collapse
Hmm you could download the goomanager app and then install TWRP, by then you can do a nandroid backup without any hassle.
Envoyé depuis mon Nexus 7 en utilisant Tapatalk 4
You can install the PDAnet driver from WugFresh. It's option no. 3 if I am not mistaken.
Anderson2 said:
#1 I believe the Nexus connected fine before I used WugFresh which made me uninstall a bunch of drivers. I now think maybe I uninstalled some essential driver but have no way to restore things because the restores don't go back far enough.
#2 where do I get the PDAnet driver?
Click to expand...
Click to collapse
Update : SUCCESS!!
It was the cable stupid!
I can't believe the hours I wasted because of this stupid cable. This must be the cable I had used when I finally successfully rooted the Nexus after multiple tries (including different cables, etc). I own several USB cables and in my hours and days of trying to get this to work I went through them all at one time or another.
I now labeled this cable as the one to use for connecting between the Nexus and the PC. It is hard to believe that a cable could make that much difference! I was of course aware that the cable could be a problem but this much of a problem?! Unbelievable. What could be so different with this Asus cable? What could be missing in the other cables?
For the record this is the cable that came with the original Nexus 7 charger. Now I have it labeled to avoid going through all this again.
I'm one happy camper! You guys have no idea how frustrating it is to follow every ones advice and still have no success. You start to feel really stupid.
Thank you all for your wonderful and patient support. You guys (and gals) are great. Sorry to have wasted your time too.
thats happens cause you probable have another android service on your machine, bluestacks is the most used. just check if you have more than one phone plugged, remember to disable/close all others emulators, remove and plug again your phone, if it persist, reboot your machine and try agian.
rafaelsartori said:
thats happens cause you probable have another android service on your machine, bluestacks is the most used. just check if you have more than one phone plugged, remember to disable/close all others emulators, remove and plug again your phone, if it persist, reboot your machine and try agian.
Click to expand...
Click to collapse
Just go to your task manager and kill adb.exe
Should clear that right up.
This is more of a General Android questions then a G2 Question.
Barsky said:
Just go to your task manager and kill adb.exe
Should clear that right up.
Click to expand...
Click to collapse
killing adb do not solve in this case.
and i post this here cause i have an G2 and it happens with me now, but of course, it can happen with any other phone, and i want to help people using the same phone as i have, i cant help all people of xda, just making my job.
rafaelsartori said:
killing adb do not solve in this case.
and i post this here cause i have an G2 and it happens with me now, but of course, it can happen with any other phone, and i want to help people using the same phone as i have, i cant help all people of xda, just making my job.
Click to expand...
Click to collapse
Bummer. Always has for me. Perhaps completely uninstalling the LG drivers and reinstalling them would help...but I am just stabbing in the dark, now.
Barsky said:
Bummer. Always has for me. Perhaps completely uninstalling the LG drivers and reinstalling them would help...but I am just stabbing in the dark, now.
Click to expand...
Click to collapse
the case i explain here, will have more then one emulator, no mater how many times you uninstall/install the drivers, no mater how many times you remove and start adb.exe again, you will always have more than one emulator.
my intention was just warn people to check if they have bluestack or any other kind of emulator opened, in my personal case, i use bluestack for whatsapp and hay day on my pc, and just remembered that bluestack is an emulator after many hours trying to fix, but theres nothing to be fixed in this case, just close bluestacks, do whatever you need to do, and open it again.