Has anyone noticed their status bar wiggling?
Notice, that besides my decrepit old man pulse, there is a side to side quivering going on there.
During the quivering period it refused to let me pull down the status bar menu, when I pressed the power button, to try to reboot the phone -it would only flash the menu pane for a split second (essentially not allowing me to shutdown or reboot). Additionally, the device got pretty hot, pretty quick.
I eventually used CWM to reboot the device. Upon reboot the device was functioning normally.
This is the second time I have encountered the issue.
The first time I was running the same ROM & Theme but I had Abyss Kernel 2.6; it had happened shortly after I installed Advanced Task Killer and I was running ATK simultaneously with Badass Battery Monitor and BetterBatteryStats. At which point I decided to wipe/factory reset & wipe cache then use CWM to flash the KL7 ROM in my sig; afterwards I installed the theme (also in my sig).
The second time occurred shortly after I received a phone call, which I fielded as I simultaneously received and sent a message through WeiXin (a Chinese chat client).
Given that the two instances appear to have been induced by seemingly unrelated triggers, I imagine something else is the culprit (my initial suspicion is that it's the theme I'm using -particularly the 14 toggle mod part of it).
Anyone have any ideas?
Related
Hi there guys, I have a few problems,
1.)
I have unusual problem (like no one had before )... Sometimes I get an error when I try to enable wifi over top toolbar (on my Samsung Galaxy S). Wifi is like frozen, no signs of activity or whatsoever. When I go to setting tab and see wifi state it is shaded button and after some time it states "Error" just below same shaded button. When I click on it after it states error sometimes it fixes it self (i.e. turns wifi on), and sometimes I have to reboot it to work.
2.)
This one is a more strange than unusual problem )... Sometimes as it is some kind of collision, when I scroll down my top toolbar it just remains opened as big as a little line no more than half an centimeter of a width. And I can't get it down to fully see information (since after installation of some widget or application or when I receive mail there is everything summarized up there). I don't know if I had installed some game or app or widget which interferes with standard top toolbar?
3.)
Some force closes when browsing Internet (via stock browser) or checking mail (via gmail app) are really annoying, but I was looking for related problems here on forum and it looks like "nothing unusual" for Froyo users....
Are there any solutions to these problems or any related thread that I have missed in my search so you can reference me to or if you can give me some solutions or at least explanations of these strange/unusual problems?
Thank you in forward . I really love this community and one day I will do Android programming too. I really need a kick start (this is not topic related question) ... can you tell me how can I get some applications fast up and running and which books/video tutorials to use to quickly become android developer / how much time is needed (I have devotion and zeal in my toolbox and I have some programming background in Java )?
Respect!
Factory reset?
Well I really want to avoid that solution any other suggestion?
Sent from my GT-I9000 using XDA App
I have all problems you describe as well, I did a factory reset (3 times in total since froyo - for these reasons. the last time I formatted the internal SD card as well, just to be sure) and they remain.
The notification bar might be caused by an app, I am still not sure, but I disabled my quick settings shortcut in the bar and the 3G watchdog notification which indicated I am using 3G and it has not happened since. Rebooting the phone also works.
I have the WIFI thing as well, it happens and works exactly like you say, I press it again and it fixes itself - or not. Weird.
Browser force close and gmail force close happens here as well.
I am contemplating bringing it to a service center but I am unsure if that will solve anything or if it's just buggy Samsung software? Any ideas?
Froyo - Galaxy S - Status Bar Problems
Any one guys? Are we only two people on the internet having this issue?
Can someone at least elaborate a bit?
For those with Droid 3s that love to randomly reboot. and crash/lag
and also crash on camera, here is a fix
1) FACTORY RESET PHONE (Erase all data)
2) When its back up and your signing back in, DO NOT CHECK 'Restore Data' or 'Keep Device Backed up'
3) Open settings later, and ensure they're both unchecked under Privacy
NEVER enable them
4) For safety incase wifi settings were restored:
Go to Wireless and Networks, Wifi Settings, Manage Network Settings, tap first option and itll say 'forget or erase wifi settings' , choose Yes
5) Reboot Phone
*If camera is still not up to your standards, use Camera360 from market.
Should be all fixed up, no more reboots or crashes, and fast.
I guess its a temporary fix until Moto serves an update.
Sucks if you rely on backup to get your apps back, but Titanium Backup is a nice app to backup settings/apps
I have random reboots also, but the strangest thing is that when I shut the phone off I can put it in my pocket or on a table and it will turn itself back on. Was wondering if this would help this as well?
Is it being charged when it turns back on?
Nothing is pressing the power button right
Not sure of your issue would be fixed by this you can try
Sent from my MB860 using XDA Premium App
not being charged when it turns back on,
nothing pressing power button. will try and let u now what happens.
Hey Guys,
I know this thread is ancient, but I couldn't find anything newer on that topic.
I'm having the random reboot issue since a while now and wondered if you could help me piece together what I've got.
I managed to find a way to provoke the reboots and that is by flooding the RAM. I opened up some random apps (doesn't seem to matter which ones, as long as they consume a lot of RAM) and it crashed rather quickly. I also managed to get a Logcat of that, but it seems pretty normal.
I attached the Logcat-Log of the last 15 sec before the crash.
But sometimes there are reboots that happen when I don't have anything intense running.
Also sometimes (often when I am using rather intense apps) the phone gets stuck with the screen turned off and it essentially acts like dead until I do a battery pull. Sometimes when it does that, it just reboots on its own after a minute or two. That could be what Cglocke might have been experiencing.
I am running an XT860 with System version 5.2.476.XT860.BellMobility.en.CA and Android Version 2.3.6
Does anybody have any ideas on that topic?
Try using rom toolbox to increase the memory management to aggressive
Sent from my DROID3 using xda premium
I've been dealing with an issue on the latest cm11 builds. I can't seem to remedy it. After using the tablet for a few minutes, the device would lock up, and the notification and navigation bars would disappear, and I get forced to the lockscreen with out any widgets. Trying to unlock the device causes a lock up again, requiring a force reboot.
I've tried clean installing and changing roms. I also noticed that pulling the quick tiles causes the crash often. However its difficult to replicate, as it randomly occurs.
I'm going to try flashing an older build.
Is this a cm11 issue?
Sent from my TouchPad using Tapatalk
Have had similar problems but they seem corrected now. I am using the latest Pac-man Shumash rom and on another TP, the latest Jcsullins.
Make sure to wipe the cache and Dalvik cache before installing. Also, use the latest gapps. I assume you are using the TPtoolbox for installing?
Also, set lock screen to off.
Same problem
I have the exact same problem. After a period of work, it just seizes up forcing me to lock screen and then just turning off the screen. Again it's most usually caused with the pull down tiles. A thing I noticed is when it seizes up you have some time before it locks you out. At that time I pressed the home button on the touchpad and it took me to the main screen. At that point the pull down tiles and the bottom 3 buttons (back, home, tasks) are unresponsive. I've now reset the Davik cache and cache, will see if this fixes the problem.
Edit: After the reset same thing is occurring, but this time there is no lockout. Just the menus becoming unresponsive. If I press one of the menu buttons everything becomes unresponsive, after a while it return to normal (except the menu buttons). If I press them again ... well just repeat the above. After a couple of times the tablet shuts down.
***I used the toolbox with pa_app, Cyanogenmode11 (the one from Jcssnuell (or something)) and Clockworkmod - all after deletion of previous systems. Before that I had Cyan9 which had the same issue i believe.
After some guesswork I believe I may have found the cause. I've tried resetting the cache and Dalvik cache a couple of times, problem persists...
Last reset I skipped the Google account thing and set the language to English (United States). I don't know what helped, but it seems to not be crashing any more.
I will add my google account after a little more time to see if it crashes or not and then see if it crashes with the account. It would be super funny and NOT FUNNY AT ALL if it was actually the language settings that are causing it.
I am having these exact same problems as well. Freezing up pulling down quick tiles. Nav buttons becoming unresponsive Also, sometimes is will just spontaneously do what looks like a "quick reboot" where is goes to the CM spinning boot animation for a few seconds, and then back to the home screen, usually followed by unresponsive buttons, etc.
I've tried jscullins 0625 and 0409, Milaq latest nightly, Shumash pac-man. All have the same issues. Gapps is gapps-kk-20140105.
I used TPToolbox to do the partitions and initial install. I think I'm going to try a full wipe and start over.
1905
I did some more searching and found that Google hotword detection can cause problems like these. I set that to disabled and my problems seem to have stopped, so far
Same problem here... Only all of my apps will not load before it crashes. Using latest milaq cm11. Wipe caches and problem persists. I rarely use googles hotword, believe its shut off...
Ideas??
Start from the beginning. Back a few weeks ago, when 4.1.5 was leaked but not officially announced, I downloaded 4.1.5 and flashed it through TWRP. Then 4.1.6 was released officially right after I've done my upgrading. So I CLEAN FLASHED 4.1.6 again on my phone.
Now the weird part: after 2 days of normal use (no flashing, no new apps installed), I left my phone charging today while went asleep. After I woke up, my phone is at 15% of battery. Although connect to the DASH charger, the phone doesn't charge at all with its LED showing red.
More weird is I can't open the notification center. I can pull the 5 toggles down, but can't open the whole menu.
Plus, notifications don't show up (no toast notification, no icons while in the homepage either).
My access to developer options is also blocked (says "Developer options is not available to this user").
The home button, recent apps button DOESN'T work - no matter if u switch the buttons in settings, or toggle the on-screen soft buttons. Although the "return" button and the fingerprint sensor DOES work.
Root access is still there (using Magisk).
While using TitaniumBackup, the app warns "This device's Android ID has changed". And a few apps have logged themselves out (I guess because of the ID change).
I think I can solve the problem by simply factory reset it. But Questions is : what's going on with my phone?
Its a common, not so common issue. I had exactly that same issue twice on two different fones. My old xperia L and my oneplus one. In my particular case, this was triggered when my settings were automatically restored from my google account (apps auto download, wifi settings, display settings etc.) After a factory reset.
After this, android id "crashes" showing that it has been changed, and statusbar only allows one pull down, along with the others bugs you described.
You should not allow google account to restore your settings (or at least that worked out for me) and restore manually your data. (Especially your display settings).
Hope it helps, i thought i was the only one.
elmarian756 said:
Its a common, not so common issue. I had exactly that same issue twice on two different fones. My old xperia L and my oneplus one. In my particular case, this was triggered when my settings were automatically restored from my google account (apps auto download, wifi settings, display settings etc.) After a factory reset.
After this, android id "crashes" showing that it has been changed, and statusbar only allows one pull down, along with the others bugs you described.
You should not allow google account to restore your settings (or at least that worked out for me) and restore manually your data. (Especially your display settings).
Hope it helps, i thought i was the only one.
Click to expand...
Click to collapse
Wow! I can't image someone had the same issue. So i actually re-flashed 4.1.6 and it's working.
But the charging problem persists. I've tried multiple power sources from the room, the kitchen, etc. None seem to be working.
Strangely, I was able to charge the device once a few hours ago at evening. And then it stopped charging again after I got the system working.
Any idea?
My N6 is running Android 7.0, have not had problems until a couple of days ago.
The right half of my display started scrolling while, the left side of the display was normal. I powered it off and back on a couple of times and, the issue was still there; I panicked and did a factory reset from the "Settings" menu hoping that would solve the problem, it did not; I still had a jacked up display.
Is this a failure mode that anyone else has seen?
I powered the phone off and, turned it back on with the volume control button pressed and, it booted into safe mode(?) then, I toggled the mode to "Restart" and, upon restart, my display was normal. This was not the end as, it will occasionally be split screen when I unlock it. I have discovered that sometimes if I receive or make a call the display will return to normal, if not, I just power cycle it into the safe-recovery mode (but not do anything else) then toggle to restart and, it's all good until next time.
Is it possible that another device (blue-tooth) in close proximity could cause my phone display to act up?
queensgate555 said:
My N6 is running Android 7.0, have not had problems until a couple of days ago.
The right half of my display started scrolling while, the left side of the display was normal. I powered it off and back on a couple of times and, the issue was still there; I panicked and did a factory reset from the "Settings" menu hoping that would solve the problem, it did not; I still had a jacked up display.
Is this a failure mode that anyone else has seen?
I powered the phone off and, turned it back on with the volume control button pressed and, it booted into safe mode(?) then, I toggled the mode to "Restart" and, upon restart, my display was normal. This was not the end as, it will occasionally be split screen when I unlock it. I have discovered that sometimes if I receive or make a call the display will return to normal, if not, I just power cycle it into the safe-recovery mode (but not do anything else) then toggle to restart and, it's all good until next time.
Is it possible that another device (blue-tooth) in close proximity could cause my phone display to act up?
Click to expand...
Click to collapse
So weird, but same thing has been happening to me the past few days. But I have a justified cause. It started immediately after installing Franco Kernel.
Sent from my Nexus 6 using Tapatalk
queensgate555 said:
My N6 is running Android 7.0, have not had problems until a couple of days ago.
The right half of my display started scrolling while, the left side of the display was normal. I powered it off and back on a couple of times and, the issue was still there; I panicked and did a factory reset from the "Settings" menu hoping that would solve the problem, it did not; I still had a jacked up display.
Is this a failure mode that anyone else has seen?
I powered the phone off and, turned it back on with the volume control button pressed and, it booted into safe mode(?) then, I toggled the mode to "Restart" and, upon restart, my display was normal. This was not the end as, it will occasionally be split screen when I unlock it. I have discovered that sometimes if I receive or make a call the display will return to normal, if not, I just power cycle it into the safe-recovery mode (but not do anything else) then toggle to restart and, it's all good until next time.
Is it possible that another device (blue-tooth) in close proximity could cause my phone display to act up?
Click to expand...
Click to collapse
It is a known hardware issue in some N6 phones, some have it and it only shows up on certain rom / kernel combos, even stock. One thing that helps is to use the interactive kernel governor and/or the down sampling factor. Of course you will need a kernel manager app for that.
https://forum.xda-developers.com/showpost.php?p=63249802&postcount=4602
Pkt_Lnt said:
It is a known hardware issue in some N6 phones, some have it and it only shows up on certain rom / kernel combos, even stock. One thing that helps is to use the interactive kernel governor and/or the down sampling factor. Of course you will need a kernel manager app for that.
https://forum.xda-developers.com/showpost.php?p=63249802&postcount=4602
Click to expand...
Click to collapse
That's good to know.
I inserted the Bluetooth question because, coincidentally or not this issue presented when I acquired a wristwatch ($19.00 from China) that connected to my phone via Bluetooth, It had it's own fitness app which I installed (which did not work). To me, there seems to be more "connection" than expected as, the fault thing only seems to happen when the watch was powered on (but not even connected via Bluetooth). If there was a bug caused by the companion app, that should have been taken care of by the factory reset.
I'm going to do some "scientific testing" by, not powering on the watch for a week and see if the issue reoccurs. Meanwhile, I will read up on kernel manager apps.
I've since flashed stock pn, and now elementalx. It's not acted up yet. Seemes to be a better performance kernel. We'll see how battery is. Sorry to hijack your thread!
Sent from my Nexus 6 using Tapatalk
queensgate555 said:
That's good to know.
I inserted the Bluetooth question because, coincidentally or not this issue presented when I acquired a wristwatch ($19.00 from China) that connected to my phone via Bluetooth, It had it's own fitness app which I installed (which did not work). To me, there seems to be more "connection" than expected as, the fault thing only seems to happen when the watch was powered on (but not even connected via Bluetooth). If there was a bug caused by the companion app, that should have been taken care of by the factory reset.
I'm going to do some "scientific testing" by, not powering on the watch for a week and see if the issue reoccurs. Meanwhile, I will read up on kernel manager apps.
Click to expand...
Click to collapse
Well, so much for "scientific testing" and wishful thinking.....didn't take long to eliminate the wristwatch, now to fix the problem.
.