Related
But it randomly reboots itself? I didnt see this as a problem, unless I overlooked something. I can be texting and it just reboots itself or does it on its own without me doing anything to the phone.
Is this a known issue? I did a clean wipe with the most recent update install.
HELP!
No it's not a known issue at all. What rom were you coming from, also by "clean wipe" did you format system when coming from that rom?
Same here
Sent from my LG-P999 using XDA App
I came from the eagle rom but wiped data, cache, etc...
Sent from my LG-P999 using XDA App
I would reflash, I never had any reboots issues while using WeaponG2X.
Hercules, Hercules!!
I am having random reboots too.
Are you guys using cases? I haven't had a random reboot since I stopped using the speck case, and I've been running almost every version of weapon all the way up to 3.0
Running Weapon 2.8 with faux oc/uv kernel without any issues whatsoever. The only reason I'm not on v3 is because I really dig prepend/append battery text.
Same here - been with Weapon for some time now (3.0 currently). Have not had any random reboots. Stable rom.
My girl changed roms because of rebotes and she was coming an older version.
Edit older version if weapons, we thought it was theme so we did two clean wipes after. Formatted system also.
Sent from my LG-P999 using xda premium
I just did a fresh install of 3.0 coming from CM7.1.0.1 and had a reboot within the first hour. Oh boy...
edit: simply replaced "no" with "boy"
I was having random reboots on weapon g3x 3.0 r1 almost 10 times a day. I was using the rotary lockscreen, and custom notification icons. I wiped everything even formatted /system and did a clean install. I now use AOSP lock screen as well as custom notification icons (m00nman's) and have not had a problem since.
frescoraja said:
I was having random reboots on weapon g3x 3.0 r1 almost 10 times a day. I was using the rotary lockscreen, and custom notification icons. I wiped everything even formatted /system and did a clean install. I now use AOSP lock screen as well as custom notification icons (m00nman's) and have not had a problem since.
Click to expand...
Click to collapse
Op states rotary lockscreen is unstable. Cheers
Update:
**Been up all weekend with no reboot. Everything is fast and working as it should.
I am running Weapon 3.0r1 and using the ASOP lock (not rotary) and I am having occasional reboots as well (now true I have had some random re-boots from the debloated Froyo ROM as well), I have also noticed that Tethering is not working either. ( I do have the updated SU, and the permissions set to allow tethering, but neither the USB or the Wi-Fi Tethering option seems to work. It does connect to other devices but it will NOT transfer data. Not sure what is going on, I do like the Weapon ROM, lotsa nice features, quick, etc. Just need to figure out why the tethering is not working and also turn off that damn shutter flash sound, If it were a real SLR the noise wouldnt bother me but this thing is digital, I don't need any fake sounds.
Is anyone else having tethering issues with this specific ROM, (if I flash back to the Froyo ROM, I can get data transfer through either the USB or the Wi-Fi Tethering, but not this ROM, any help would be appreciated.
CM7 #190 seems to be it for me
I love weapon but I always get a black screen and the reboots at least 3 times aday and that doesn't happen with cm7. Or mui rom
Sent from my LG-P999 using XDA Premium App
I love the ROM cause of all its customized features but I also believe that is the cause of its issues. I ran the ROM from the beginning always doing wipes cause I don' trust flashing over frameworks and stuff, plus I only have a couple apps that I install. Overall I noticed that with each huge customization came another issue weather it was reboot or something else. I rarely get reboots ever, on lots of different ROMS but weapon's latest gave me lots at least once a day if not more, on aosp lock screen and no real custom things done to it. I just liked the pull down notification and status widgets he had... I believe 2.8 was my oldest backup that was a great stable ROM for me.
I did a clean install, meaning format, clear data, clear coach all the good stuff... And I have been using the phone for the last 4 days with out turning off the phone, I have no reboot no gps problem, no problem at all.
Edit, I did not use any lock screen at all. I use an app to disable the lock screen, since there is no option in weapon to disable the lock screen.
G2x Weapon 3.0 R1
I did have random reboots the first couple of days after flashing weapon 3.0 R1 but it has settled down and I actually had my phone running for 6 days straight without a reboot or the dreaded sleep of death. The biggest thing is that I only use the ASOP lockscreen and I haven't been using bluetooth connected to my car (Nissan Rogue) lately. It may have just needed some time to 'settle in'. This has been the most stable ROM I've tried but I've only tried a couple.
I have Galaxy S with Android 2.3.4 JVR and it works like a charm - with this one exception: sometimes (too often) phone, contacts and messages (sms) keep closing. This happens usually within a second or two after opening up them. There's no force close message, it just returns to the home screen without any warning. If I reopen it, it usually does the same a couple of times, but eventually I get it to open.
At first I thought this must be a memory issue. However, I have Autokiller installed (my phone is rooted) and I have usually >100M free memory. Then I thought it must be Autokiller killing the dialer, contacts or messages apps. BUT: this happened also before I had Autokiller installed, so it can't be that either. The strangest thing is that I tried installing GO SMS Pro and GO Contacts + Dialer, and even they do the same thing occasionally (close immediately after I open them), so it isn't a problem with apps either.
I am bedazzled here, could somebody please help me? This starts to get really annoying, since the dialer, contacts and messages are the feature you normally use most in your phone!
I have the exact same problem! Somebody, please help
the phone app and etc. seem to be corrupt or something
try reflashing.If you keep getting the problem then revert back to your previous rom =/
Is there any way to try to replace only the phone etc. apps without flashing the whole rom?
from my experience no but you can try replacing phone.apk sms.apk etc with the previous rom's apps
The funny thing is that I have a stock 2.3.4 JVR, so it should be stable.
Plus, did I mention that this happens only sometimes? Sometimes they work ok. But this happens often enough to be annoying. You know, when you would have to make a quick phone call you have to open the phone app like 3-4 times, only then you're able to make it. I wondered if the the problem could still be in the dialer, contacts and messaging apps even if the problem occurred only sometimes?
In addition, the calendar app has done this a couple of times. Could it be that there's a conflicting app that's causing this? If so, do you have any suggestion what it would be?
Autokiller made my phone do some really funny stuff. After installing it i was having random reboots and apps crashing so i uninstalled and problem solved. You said it was happening before you installed it though so im just guessing that you need to either wipe cache and dalvik then reboot or do a full wipe and reinstall of your rom. When you do the full wipe go into mounts and storage and wipe system too
Hi and thanks for your comment. What are the effects of wiping the cache and the dalvik cache? Do I lose important data? Or can I do it safely? Sorry, I'm a bit of a n00b with android. I suppose you wipe the cache in download mode, right?
I experience exactly the same issue as you-though I am on stock jvu.I come from 2.3.3, stock as well, using chainfire root both times.
Sometimes phone contacts and message s close immediately after opening them, often several times. and sometimes everythings fine
here you can find some information about dalvik and normal cache wipe..your data will be safe-only first boot will take longer.I will try wiping now, too-reporting back then.
Edit:
For now wiping seems to have worked well and fixed the problem here..I need some more testing though-will keep you up to date here
edit 2: damn! The issue's still there.anyone got more ideas?
G'day!
I have the exact same problem with JVU and I had this problem with 2.3.3 but less frequent. I have no choice but to reboot the phone when it happen. I suspect it's caused by one of the widget (email and Go weather) that I put on the desktop. Going to remove the two widgets from desktop and see if it's help.
Whitest said:
I experience exactly the same issue as you-though I am on stock jvu.I come from 2.3.3, stock as well, using chainfire root both times.
Sometimes phone contacts and message s close immediately after opening them, often several times. and sometimes everythings fine
here you can find some information about dalvik and normal cache wipe..your data will be safe-only first boot will take longer.I will try wiping now, too-reporting back then.
Edit:
For now wiping seems to have worked well and fixed the problem here..I need some more testing though-will keep you up to date here
edit 2: damn! The issue's still there.anyone got more ideas?
G'day!
Click to expand...
Click to collapse
earthman5678 said:
I have the exact same problem with JVU and I had this problem with 2.3.3 but less frequent. I have no choice but to reboot the phone when it happen. I suspect it's caused by one of the widget (email and Go weather) that I put on the desktop. Going to remove the two widgets from desktop and see if it's help.
Click to expand...
Click to collapse
Okay, that sounds interesting - though I am not sure wheter a widget could cause this...
I am still running JVU but now with Galaxian Kernel instead of Chainfires root Kernel - flashed with SGS Kernel Flasher and still got root - and it runs very stable and fast 'till now. No more closing of phone, contacts and messages so far -.- since 2 days.
I'll tell you when it happens again, but so far it seemed to be a kernel issue for me...
I've been having the same issues with my Samsung SideKick 4G. messages would keep closing as I was typing them, I would lag and the key I pressed would "press again" like 15 more times, sometimes I just couldn't open a conversation, other times I couldnt answer phone calls cause the UI lagged.
That was all on stock firmware, and I got fed up with it so I tried to flash a custom ROM on it, and before I did that I had it OC'd to 1.2GHz which was actually pretty great. Needless to say, I screwed up on flashing the ROM and now I'm looking for firmware to odin back to stock. =\
After about 4 months of being rock solid, my Transformer has started acting up this past week. After about a day of use, the homescreen will freeze up, stop responding to touch, and then have to be force-closed. After Launcher restarts, it will immediately crash again. During this crash cycle, I am unable to launch any new apps - however, I can switch between my already open apps using the "Recent Apps" button, no problem - they will even run perfectly for hours. But to launch new apps, I have to reboot. (NOTE: this is different than the well-known issue where the homescreen icons disappear, but swiping/touching still works. In my case, the icons and widgets are just "stuck" there.)
Things I have tried: Cold boot, wipe cache, wipe dalvik cache, change to static wallpaper. (problem still recurs)
I am using the same ROM/kernel/OC/UV settings that I always have (1.2 GHz, -25 mV on all).
I'm stumped. Anyone else see this?
I have the same kind of issue since 3 days ago. Launcher crashing, no icons on desktop but can switch between empty desktop. "Recent Apps" available. Cold reboot helps but problem will recurs. Stock Asus ROM, Android 4.0.3, kernel 2.6.39.4.
Hi slybin, yours is actually the more common issue - disappearing icons, but swipe/touch works. Mine is the opposite - the icons are visible, but swipe/touch does NOT work.
I'm guessing you are on stock kernel? Disappearing icons is fixed with Guevor's kernel, or possibly others.
Im on team eos JB and never faced any of the issues you mentioned above.. try flashing a different ROM after wiping everything...
Sent from my Transformer TF101 using xda app-developers app
zAlbee: Yes, I'm on a stock kernel. I just find it strange that it suddenly started Monday without any new kernel update from Asus.
udupa82: I saw that EOS is developed on the Xoom, did you had any other issue with that ROM? Which build did you use?
I am on CleanRom 3.0 right now, fresh install. Now, for the problem. Today while sitting in class I took my phone out to see it was booted into safe mode. So I rebooted it back, and noticed a lot of my downloaded apps were launching 10-25 seconds after I clicked to open them. So, I rebooted again. That didn't work. I cleared cache and dalvik cache. That didn't work. So, I dirty flashed CleanRom 3.0, which still didn't work. After driving and listening to spotify in my car, the apps launched completely fine, and still are. Does anyone know why this is happening? By the way, this happened on my rooted stock rom, that's why I switched roms. I don't know if this could cause any issues, but I do use Directory Bind.
Have you checked if power saver is on?
Another possibility could be a lot of applications running the background and just slowing your phone down.
Check your task manager by holding the home button for about 2-3 seconds.
Yea, power saving is off. And there isn't any apps running in the background when it's ran slow. Most stock apps will launch fast (settings, phone, clock), but downloaded ones won't (I funny, handcent sms). I seriously can't figure out what the issue is. I've even tried messing around with set cpu, but that didn't help.
Sent from my SCH-I535 using xda app-developers app
Try cache mate.
Sent from my SCH-I535 using xda app-developers app
I've got an odd problem with my p900. If I install any lollipop ASOP ROMs, the first time I reboot after initial install, the display mostly stops working. The first boot works fine, I go through the setup wizard, set everything up, and the tablet works and displays fine as long as I don't reboot.
Specifically, what will happen if I reboot is that the tablet will go through the normal boot, and get to the point when the wallpaper and status bar will come up, but no homescreen icons or anything. Then after a while, about 2-5 minutes, the display will go black except for the status bar. I can pull down the notifications drawer from the status bar, and it will display, as will the quick settings, but anything I tap to try to interact with will seemingly just do nothing. If I have 'show touches' on, then touches will display properly, anywhere on the screen, but they seem to do nothing. I've tried trebuchet, google now, and adwex, the home app doesn't seem to make a difference.
The problem first began in I want to say october, when I flashed a CM12 nightly update. I unfortunately no longer remember which nightly I was on nor which I flashed to. I of course immedately tried to flash back to the previous nightly when I discovered the problem, but it did no good. It took me a while to figure out the pattern to the problem after it first occurred, as I often don't reboot the device for a long while after a first install. I don't have a lot of spare time to devote to sitting down and just focusing on trying different things, so it wasn't until president's day weekend that I tried what I *thought* would fix it, ODINing back to stock and installing the latest CM12.1. Clearly that didn't work, or I wouldn't be posting.
I've tried the 20151104, 1029, 1006, and 0910 CM12.1s from http://forum.xda-developers.com/gal...nt/rom-cyanogenmod-12-lollipop-5-0-1-t2971945. I've also tried Civz lollipop, pacman, and resurection remix. Anything not stock based has the problem. I tried running stock, but I've been running CM since G1 days, and I just can't stand stock, even the stripped down and modded versions. It just doesn't work right, and I can't get used to it, even after forcing myself to use it for several days.
I've never encountered such a weird problem, and I can't seem to find anyone else having a similar problem. I have no idea how to troubleshoot this beyond what I've done already. I'm currently running thompatry's Cm12.1 20160212, having not rebooted after the initial install, and it's running mostly ok, but I live in dread of my battery dying, and of course I can't install any xposed modules like xprivacy or multiwindow, which is bothersome. I have the wifi only US model, v1awifi, and I'm currently running TWRP 3, tho I was on TWRP 2.8.something when the issues first started happening.
what's the last 3 characters of your bootloader version?
heldc said:
I've got an odd problem with my p900. If I install any lollipop ASOP ROMs, the first time I reboot after initial install, the display mostly stops working. The first boot works fine, I go through the setup wizard, set everything up, and the tablet works and displays fine as long as I don't reboot.
Specifically, what will happen if I reboot is that the tablet will go through the normal boot, and get to the point when the wallpaper and status bar will come up, but no homescreen icons or anything. Then after a while, about 2-5 minutes, the display will go black except for the status bar. I can pull down the notifications drawer from the status bar, and it will display, as will the quick settings, but anything I tap to try to interact with will seemingly just do nothing. If I have 'show touches' on, then touches will display properly, anywhere on the screen, but they seem to do nothing. I've tried trebuchet, google now, and adwex, the home app doesn't seem to make a difference.
The problem first began in I want to say october, when I flashed a CM12 nightly update. I unfortunately no longer remember which nightly I was on nor which I flashed to. I of course immedately tried to flash back to the previous nightly when I discovered the problem, but it did no good. It took me a while to figure out the pattern to the problem after it first occurred, as I often don't reboot the device for a long while after a first install. I don't have a lot of spare time to devote to sitting down and just focusing on trying different things, so it wasn't until president's day weekend that I tried what I *thought* would fix it, ODINing back to stock and installing the latest CM12.1. Clearly that didn't work, or I wouldn't be posting.
I've tried the 20151104, 1029, 1006, and 0910 CM12.1s from http://forum.xda-developers.com/gal...nt/rom-cyanogenmod-12-lollipop-5-0-1-t2971945. I've also tried Civz lollipop, pacman, and resurection remix. Anything not stock based has the problem. I tried running stock, but I've been running CM since G1 days, and I just can't stand stock, even the stripped down and modded versions. It just doesn't work right, and I can't get used to it, even after forcing myself to use it for several days.
I've never encountered such a weird problem, and I can't seem to find anyone else having a similar problem. I have no idea how to troubleshoot this beyond what I've done already. I'm currently running thompatry's Cm12.1 20160212, having not rebooted after the initial install, and it's running mostly ok, but I live in dread of my battery dying, and of course I can't install any xposed modules like xprivacy or multiwindow, which is bothersome. I have the wifi only US model, v1awifi, and I'm currently running TWRP 3, tho I was on TWRP 2.8.something when the issues first started happening.
Click to expand...
Click to collapse
Have you tried changing kernel? I mean in the case of civz lollipop rom you do get an option of 2 different kernels try choosing the opposite to the one you had chosen before. Thank you, hope it helps.
I won a year ago 2 Note Pro, one works flawlessly while the other is slow af and it has the same issue that you speak about. If I stay on stock everything is good more or less (sometime little slow), but if I install Lineage or any other Custom Rom is too slow and has the same issue you speak.
I changed both batteries, but nothing to do. If anyone knows, text please.
Thank you!