I have just recently flashed JVR guys, and what seems to happen with the phone if I turn on the WIFI from Touch Wiz slide menu on home screen sometimes phone gets rebooted.
Now, on the other hand if I turn on the WIFI from settings menu phone acts normal.
Phone was rooted with CF,
I then went back to JV5 with JVQ Euro version from Ramad same problem happens again, somehow touch wiz slide menu fails on WIFI.
Any ideas that I can rebuild this package with root commands or even fixing it.
By the way I already tried re-flashing so that does not work.
I went to the authorized dealer ) they were using the same Odin as I do same problem happened, no hardware problem they found.
tr posting in the right section and try changing the kernel
try galaxian
weird
I only face this wifi problem on JVS. It connects and disconnect from time to time. it's like every one or two mins, it disconnect by itself, which is annoying. doesn't happen tho when I flashed back to JVR using Odin.
I also flash JVR with CF-Root no issue at all for Wi-Fi. Try superclean script http://forum.xda-developers.com/showthread.php?t=1166954 and tick re-partition when reflash
Related
Hello all.
I hope this is in the right section. I have tried looking here:
http://forum.xda-developers.com/showthread.php?t=896213&page=447
For any answers, but at over 400 pages it's taking a while!!
I rooted via unrevocked the other day, and flashed Redux. I quite like it but am having the following issues:
WiFi, works fine at home, picked up the signal and signed in easy as. At work however it can't detect anything. On the stock 2.2 it was fine. This is a magor as 3g here is pretty slow. If I can't get WiFi working properly I'm going to have to look for another ROM.
Sound settings in menu. FC's every time.
Camera, may not be an issue as such, but does anyone know how to disable the camera sound? It's incredibly loud and annoying.
Cheers for your help, and if this is in the wrong place please point me to the right one!
Oh just point out what I have or have not done to try and fix this:
I have restarted WiFi router. No change. It was working fine until I flashed Redux.
Works fine at home, and can detect the neighbours WiFi.
I have flashed latest radio ROM 5.17.05.23
I have reflashed Redux. But did not to another complete wipe.
Have tried rebooting and hard reset (remove battery)
Fixed the sound menu issue with a full wipe and reset.
WiFi still not picking up at work. Have flashed a new Kernel 2.6.35.8 manu 1.4
Will see if that chnages anything
For me the screen flickers when I use Android Market and scroll up and down!
Very annoying!
Ok new kernel changed nothing.
Did full wipe are reflash. No change.
Flashed Leedroid 2.2 ROM. WiFi at work instantly working fine.
So flashed Oxygen 2.3 ROM. No WiFi at work.
There is something in those 2 GB ROMs that stops my Desire seeing my works WiFi net work. Any ideas??
I would try to flash radio:
http://www.mofirouz.com/ahp/?file=htcdesire/radios/32.56.00.32U_5.17.05.23.zip
I hope you know how to do this. No warrany for any damage.
Cheers for the reply.
I have that radio already.
It seems it is a very common issue in 2.3 and is to do with hidden SSID on the WiFi.
Not sure why it affects 2.3 and not 2.2 but lots are complaining about it.
Will have to find out the SSID to connect
I seemed to have cured my SSID issue
http://www.appbrain.com/app/wigle-wifi-wardriving/net.wigle.wigleandroid
Got me straight in. Once I had connected, reconnecting works fine. I even uninstalled the app to check and it's sweet as
Well, this sucks. Upgraded from the Hero to the Desire Z 1.5 weeks ago. Downgraded it, rooted it, tried out a few ROMs, settled on Virtuous Unity and all was happy.
I used the phone in the car this morning as a GPS, 3G data connection was working fine, etc. I had a couple of client meetings, after which I pulled out my phone to check for messages. I noticed there was no mobile signal at all. I figured it was building interference, so I went outside. Still nothing. Wifi was working fine, GPS was working fine. I enabled airplane mode, then disabled it again to see if that would kickstart things. Still no go.
I decided then to power cycle the phone to see if that would help. It went through the usual reboot cycle, displayed the lock screen, then the SIM unlock screen. Then no matter what I do or don't do, about 5 or 6 seconds later, the screen suddenly goes black and the phone reboots.
Now it just does the same thing over and over again. The phone boots up fine, displays the lock screen briefly, then the SIM unlock screen, then it crashes and reboots. Whether I unlock the SIM or not doesn't matter. Within 5 or 6 seconds, the phone will reboot. I can see notification icons popping up, so everything appears to be working fine otherwise.
I have not changed anything on the phone this morning: it was sitting in my pocket the entire time. Same ROM, same radio firmware. I restored last night's nandroid backup just in case, but it didn't help. I thought perhaps it was VU's built-in overclocking that wasn't agreeing with the phone, so I restored a MIUI-based backup. No go. I went all the way back to the stock (but rooted) Bell Desire Z image I took when I first got the phone. Still no go.
I've tried booting up without the SIM card, and without the SD card. Nothing works. I'm guessing the phone suddenly developed a hardware problem. It would be something that is triggered soon after the OS has successfully loaded. Maybe something to do with the 3G radio?
There are no obvious errors or kernel panic messages in logcat. Everything appears to be proceeding normally, until it just comes to a dead stop. Anyone have other suggestions I can try?
Search this forum for "boot loop" and you'll find some things to try.
Thanks, burtcom, but none of the threads I checked apply here. Other boot loop problems more often have to do with the phone rebooting while the boot animation is still playing. My phone successfully boots and is in the process of loading user apps when it crashes. Also, most reports come as a result of something attempting to root their phone and then installing a ROM. I've already made it past that stage. I am able to boot into CWM, do my nandroid backups and restores, etc. The ROMs have all been working fine up until some point this morning. The fact that several different ROMs now all have the same problem makes me suspect a hardware issue.
Moved my SIM and SD card back over to my Hero, and everything works fine there, so I strongly suspect some hardware just broke on the DZ this morning. I'll try flashing a new radio firmware, but I can't see how that would fix anything, since the old version was working just fine all along.
taob;15238893I'll try flashing a new radio firmware said:
Huh... so I flashed the latest Bell Canada 26.06.02.25_m2 radio.img, (up from my old 26.03.02.18_m3 firmware), and now the phone no longer crashes. I'm thinking maybe it isn't an issue with old vs new firmware, but that the old firmware was somehow corrupted during the course of the day. Re-flashing the original radio probably would have worked too, but now I have the latest one...
Hopefully this will help someone in the future with the same problem.
Click to expand...
Click to collapse
The phone no longer reboots, but I still had the problem of not picking up any signal whatsoever (voice or data), even though wifi and GPS work just fine. APN settings were verified to be correct. It turns out I had to go into Settings -> Wireless & networks -> Mobile networks -> Network operators -> Search network and manually re-register my phone on TELUS. Bizarre.
I had the same problem, update your radio and flash this zip on the Unity Thread
"For people experiencing random phone Freezes, this is due to overclocking, it's solved by lowering max speed.
Just flash this patch over: (link is on the thread)"
That's a different kind of problem, sengalang. My phone was working just fine overclocked to 1.2 GHz for over a weeks, so why would it suddenly start crashing like this? Problems due to overclocking tend to result in reboots at random times, and not at 100% predictable times like my problem. I did also boot with the MIUI and stock DZ ROMs, which do not overclock... same problem. Thus the root cause was not CPU speed.
So i have started encountering a problem in which about 3 minutes into a phone call my phone freezes and then ultimately turns off and only way to turn it back on is removing the battery and then power button.
I have had this problem on every rom starting on CM. After it happened on this rom i flashed juggs, beast, and da bomb (or whatever) and everyone it still happened. I wiped data, cache and delvik before every flash but this did not help.
I eventually just odin back to stock with the stock tar that is posted somewhere in this forum. This still has the problem. I found that it generally happens if i move from my ear and the screen turns on and then it wont turn back off and no menus are available (ak i cant get into dialer if i call bank or 800 number to input a number) and then it just completely freezes and turns off.
Any help with this would be great. I mean making phone calls is probably the most important part of a "phone" working. So i really need this to be fixed asap. thanks
jr8801 said:
So i have started encountering a problem in which about 3 minutes into a phone call my phone freezes and then ultimately turns off and only way to turn it back on is removing the battery and then power button.
I have had this problem on every rom starting on CM. After it happened on this rom i flashed juggs, beast, and da bomb (or whatever) and everyone it still happened. I wiped data, cache and delvik before every flash but this did not help.
I eventually just odin back to stock with the stock tar that is posted somewhere in this forum. This still has the problem. I found that it generally happens if i move from my ear and the screen turns on and then it wont turn back off and no menus are available (ak i cant get into dialer if i call bank or 800 number to input a number) and then it just completely freezes and turns off.
Any help with this would be great. I mean making phone calls is probably the most important part of a "phone" working. So i really need this to be fixed asap. thanks
Click to expand...
Click to collapse
Looks like it might be a kernal problem. Have you flashed back to the stock kernal? If not, I'd look there first
yeah i flashed stock kernal as well...problem still persist
uninstall Google+
no google + never have had it.
Have you tried flashing CM7 Alpha #2? I had that same problem with Alpha #1 release then flashed #2 fixed permissions. Then at first start up i rebooted with GPS on and voila! No more phone FC.
I started with Alpha #1 where the problem started flashed over #2 fixed permissions and same problem. thats when i started flashing the other roms to try to solve the problems but this hasnt helped. So i odin back to stock. flashed stock kernal and stock recovery. and i still have the problem.
What sucks is im just graduating college and im starting to receive calls from future employers and i cannot talk for more then 2 minutes before my phone decides to shut off.
So any other advice???
bump it up. Any help please...::
what it is doing now update: I click on a contact or type a number and press call and the screen turns black except the status bar. soft keys dont work, hard keys dont work. phone is a fail. people can still hear me and i can still hear them but the phone is unusable and i have to pull battery to get out of the black screen.
This was doing it on every rom and i have now put beastmod v2 4.0 still no luck :[
I just received my White GS2, finished the OTA update.
And yes, the dialer FC on me every single time once I push the hangup button.
I'm on CM10.1-20130526 Nightly. Often times, the softkeys (the ones at the bottom of the phone) don't work. This requires me to reboot the phone in order to get it to work. Also, the phone reboots (on its own) several times during the day (upwards of 3 times a day). Is there any way to fix these problems? Thanks.
thatlaoboi said:
I'm on CM10.1-20130526 Nightly. Often times, the softkeys (the ones at the bottom of the phone) don't work. This requires me to reboot the phone in order to get it to work. Also, the phone reboots (on its own) several times during the day (upwards of 3 times a day). Is there any way to fix these problems? Thanks.
Click to expand...
Click to collapse
Software keys is not a common issue so maybe you should change roms. The reboots are common with cm 10.1 builds since they are in testing phase still. A new RC3 build should be out late tonight or tomorrow at the latest maybe you should try that. Also did you use the odin update firmware it really helped with the reboots and screens of death for a lot of people. It just udgrade your firmware and radio to the newest available for this phone here is odin and the uvmc6 tar file if you need it. First hook phone up in download mode make sure odin sees it in (yellow) box for whatever port it's hooked up too. Then place tar file in PDA section and hit start. Once finished it should say PASS in (Blue) box. After phone reboots unplug from computer. This will not erase anything on your phone at all. It just upgrades it.
UVMC6 TAR
https://www.dropbox.com/s/3ccjzq3rkt3ylfg/UVMC6.aio.tar.md5
ODIN
https://www.dropbox.com/s/lczw3kg1s02g3ol/Odin3_v1.85.zip
soft keys and slow down to reboot
running new firmware and radio doesn't fix the soft key issue. It seems very random and rebooting doesn't always fix it. I've switched to uber stable 2.0 rc1 kernel and it hasn't happened for a day now. Still having what might be memory issues as the phone slows down to not doing anything then reboots. If I manage to look at the memory usage before it is unusable there is 30mb available which is almost nothing but it is still some. So is the slow down and reboot related to an inability to run the process to free up memory? I'm not sure since I'm not 100% familiar with the "garbage collection (.Net terminology, I know android has something similar for activities I think)" of android. The slow down/reboot seems to speed up with the number apps opened/activities started over time.
The only thing that fixed the SOD for me was using a different kernel than the cm10.1 kernel.
Update: just took a while but still have issues with soft keys and rr
My new T900 is having problem with WiFi unable to assosiate to AP.
Keeps coming back with AP error message.
Tried to apply forget to re-enter password, but didn't do the trick.
Chronological orders of mess I did tonight, to help troubleshooting:
1. Tablet is new, been runnign fine stock for 2 days.
2. Flashed openrecovery-twrp-2.7.1.0-viennaltexx.img.tar using ODIN.
3. Flashed CF-Auto-Root-v2wifi-v2wifixx-smt900 using ODIN.
4. Flashed openrecovery-twrp-2.8.0.0-v2wifixx.zip using ODIN.
5. Still working fine at this point.
6. Froze bloatwares.
7. Tablet came off its stand and fell on the table - <2" drop, just on 1 edge.
I didn't remember if the Wifi stopped working after the drop or the bloatware freezing.
Anyway, I defrosted all the bloats and it wasn't working still.
Finally did a factory reset, and it's still not working.
I highly doubt the problem came from the drop (more like a bump) on the table - that'd make this the least realible product I've ever owned.
I strongly suspect SW, but even factory reset doesn't seem to fix the problem.
I also checked my Wifi Router and it's not the problem.
Any suggestions or ideas would be appreciated.
Fixed by doing reflash to stock.
ODIN 3.09
T900UEUANI1_T900XARANI1_XAR.zip
Wifi works right away after this.
Closing thread.