Hello,
I have some strange problem with my Wallaby - after some time after restart it stops to respond (or better said if it responds veeeeery slow), display backlight turns off. Sometimes it recover and work fine, but sometimes reset is required. When reseted it sometimes shows only first letters from the boot screen version info (the red text in bottom left corner).
Also when making call it usually lasts only for few (max 2-3) and then it goes silent (again - reset required)
After reading this forum I think should be because of incorrect GSM soft version, but what confuses me is that it happens randomly (from my point of view). Should I try other versions of ROM (so this is "known bug") or is it normal behaviour or can be there some HW bugs?
thanks, Krovak
Related
This phone has never been modified, no custom ROMS, never rooted, using the latest OS from AT&T ...
And today, for whatever reason, when making originating a phone call, and once I've hit "dial" ... the phone screen goes completely black except for the status bar at the top (the one you can swipe down). I'm saying that whereas usually, after hitting "dial" and as the phone dials, you can actually see a screen full of information (hang up botton, number/name of who your dialing, etc.) ... in this case and now, there is just a black screen.
Though there is a black screen (other than the status bar at top), I can still hear the phone ring and even have a conversation should somebody answer. But when the call is over (the person on the other end has to end the connection because I have no screen interface to do such), the screen remains blank (other than the status bar at top) and none of the bottom, permanent keys are operative either ("home" / "back" / settings / etc.). To get back to the home screen, I have to pop the battery and re insert it and re start the phone. But even then, it's acting weird: when booting, at the "Reimagine Possilbe" screen (I think that's what it says) it hangs there for about 45 seconds (usually only about 5 when functioning correctly) and will eventually end up at the home screen.
But if I originate a call, the cycle repeats.
I've completely reset the phone to factory defaults at least three times, formatted the USB storage and the whole nine yards but it remains glitched as described above.
...
So... has anyone seen/heard of this?
I'm thinking of just warrantying the phone as it's only about 5 months and I figure AT&T should have no issue as it's such a replicable problem and it certainly doesn't seem to be software related as it's completely stock and multiple factory resets have not worked but wanted to put a line out here first to see if anyone else has experienced this.
Thanks in advance for any information.
Best,
Joel.
I think the network is fugazi right now, as I had issues with the phone, and read about another user having same troubles. I'd give it a little time.
rangercaptain said:
I think the network is fugazi right now, as I had issues with the phone, and read about another user having same troubles. I'd give it a little time.
Click to expand...
Click to collapse
I sure hope so. Even though I've reset the phone (which sucks) ... I'd prefer that over having to go to the store and all...
Odd that a network problem could cause such, though ....
Thanks for the word ...
Best.
.joel
Just a llittle update ...
I changed the "Proximity Sensor" to OFF and now the normal iin-call screen appears but it never goes away, which can be problematic.
In general, I've always had the proximity sensor set to ON as this allows the in-call screen to blank after a few seconds (complete blank with no status bar at top) and then reappear when I remove the phone from my ear.
But when I re enable the proximity sensor, now ... the screen blanks immediately (excepting the status bar at the top) and never comes back ... even after my call recipient ends the call ...
I'm just gonna warranty at at the local service center; at this point (two days now with all my friends AT&T phones working fine) I'm pretty sure something is glitched with the internal sensor that manages the proximity settings ...
Thank God for warranty.
I just installed AOKP Unofficial 4.2.2 from this thread.
If I simply make a call, the proximity sensor functions as expected and near perfectly (I think there's slightly too much lag between removing the phone from one's ear and the screen coming back on... but not unbearable). With the keypad shown, I've found the behavior to be quite unpredictable. On my first call with the new ROM, I called my company voicemail and between inputting my password and cradling the phone, I could hear a bunch of key presses occurring. It ended up disconnecting the call. This is quite reproducible for me.
I'd like to know if this is a reproducible issue, intended function, and/or bug (which I will report if others can verify).
Method:
- Dial a number
- Set phone on table
- Put hand in viscinity of top of the phone
- Observe screen turning off and on as you move your hand over the sensor and then away
- Pull up keypad
- Repeat hand test and observe that the screen is not predictable
In trying this several ways, there's either a lag in detecting proximity, or it's just flaky. I actually find it really hard to reproduce consistently. Sometimes it actually will turn off (I can see peripherally that if I put it to my ear), however if cradling (with phone still well within what I could call "proximity" to my face/ear), it will dial numbers. In putting my hand in various positions over the phone, sometimes it turns off, sometimes not. With the keypad hidden, it turns off reliably 100% of the time.
The biggest difference I can reproduce is that if you put a single finger over the full width of the top of the phone (over the HTC logo -- the sensor is just to the left of the logo), it will reliably turn off the screen without the number pad, but not with it. I get that the sensor probably needs to account that one's fingers will be pushing on the screen to enter numbers, but something directly over the sensor (simulating an ear pressed to it) should turn it off even with the number pad shown, I would think.
Thanks for any suggestions of if you'd like any further information.
----------
ETA: S-off, unlocked bootloader, AOKP: aokp_jewel_unofficial_Mar-12-13, baseband 1.12.11.1210, Android 4.2.2.
[Q] Phone get stuck with screen locked. Rebooting starts an endless "startloop"
(I posted on the wrong location first time, sorry)
Hi, I have this Galaxy S3 i9300, with Wanam ROM and Boeffla-Kernel 2.12.
Sometimes, when I lock the screen, it just freezes in there. I'm unable to wake it up, and the LED keeps flashing the last notification.
Most of the time, I get notice of it when I receive a notification (it rings) and the phone cannot wake up. Calling and trying to trigger another notification does not wield any results.
The weird part is this: When I restart it, the OS starts as it should, but it "skips" the lockscreen (when I restart my phone, first thing I'm presented is the pattern lockscreen, all Android default), and it goes directly to the home screen. The touch screen is unresponsive (but it does vibrate when I press any of the two bottom buttons), but phone is still alive (few animations plays smoothly).
Then it restarts. The startup LED (fading blue to bright blue) doesn't turn off (normally it would turn off even before the lockscreen is presented).
Disabling the lockscreen wouldn't solve the problem, nor does starting on "safe mode". Same issue.
Booting into CWM and wiping data/cache folders solves it, but resets my phone. Restoring a backup (data folder only) also works.
Funny fact is that even with a fresh backup (which works), it might just hang up like before (although I didn't modify/install anything).
Logging files should give me some info, but I don't know how to retrieve them, let alone on this condition.
The only step I did so far to try to solve it was to disable a notification program (Logical, it seems to hang up when I receive a notification, and as a wipe to the data folder solves it, I presume it's an rogue app. But never, ever I had a problem with this app, but who knows if on an update, it's crashing my phone)
Does anyone have any information regarding to this? I've never seen something like that.
How do I recover my logfiles during an emergency?
-----------
Had another lock-up. No notifications received and the notification app was disabled. How do I get the log file?
For a week or two now,* I have been having some funny things happen with my Redmi Note 4 (Qualcomm, Global) phone.
Before that it had gotten water in it and basically shut down entirely, but they fixed it and got it up and running. When I picked it up they showed me watermarks on the screen, saying that the screen had frozen only once but that it may just be lagging.
Since then I have had a few symptoms of an issues, perhaps hardware issues, but potentially something that I can fix without paying more for parts.
Here are the things that happen:
- Music stops suddenly (screen on or off) and the music app has to be reopened (DoubleTwist, Miuiu's Music app, etc); Somes while in Doubletwist, if I click to visit home screen (square button) than the music stops. (this is the first issue that I noticed).
- 1-2 seconds of white screen before already-open apps appear after selected; Sometimes problems with apps loading or screen goes black when loading
- When closing apps or returning to home screen, it looks like the desktop(?) background comes up and then a second after is is re-populated with icons as if system is refreshing the home screen
- Once any of these issues begins, it usually worsens and the cell phone gets slower, behaving more and more strangely until not even useful to me; Reboot clears it right up for an hour or two or whenever this wierd stuff starts to happen again
-It seems like if I make a point of using the phone modestly, slowly, I can avoid these issues from starting up
- Sometimes reboot rometimes hangs on initial black loading screen
- Sometimes if I hit the power button to turn off the display, I can not turn it back on with that button (neither does the battery-dead orange light flash), so I have to reboot.
-When I turn the phone screen off while it has been working fine, I come back later, turn on the screen to find that it is now on the boot logo screen and it stays until I hard-reset the phone.
So, these are potential issues I have guessed at:
* Screen damaged? So far, other than watermarking at the top and some backlight bleed, sensistivity is perfect on the phone, and symptoms involving screen always seem to be triggered more by apps or pressing buttons.
* Apps or Android corrupted/internal memory damaged? I backed up via Settings and did a Hard/Factory Reset, then restored from backup. I still have the problems.
* RAM partially damaged? I test RAM with two apps and none of them showed issues. Namely my available RAM and used RAM reported always add up to the 4GB my phone has.
*Other Hardware Components failing? I used 3 apps to check all of the hardware devices and sensors that I could think of. Vibration is the only thing that does not work, and honestly, I don't care much about vibration.
Today I have suspected that settings may being at fault, and/or battery savers turning off my audio. Battery savers often identify my music apps as using "excessive amounts of power," perhaps because the speakers at involved, but it does make me think... I removed any battery-related and security apps, then turned off all battery saver options in settings earlier today. In 2 hours of music listening after that, I have not had any shutdowns, but I am not convinced I have solved the problems. In the weeks after this, the issue is back and the audio issue is always followed by the phone operating very sluggishly.
I have done a factory reset and restore, and the issue persists. Do you think there's any point in trying to do a clean reflashing of MIUI? Could it be a software issue or definitely hardware?
What advice can you give me?
Thank you for reading.
You can try booting in safe mode and then check if the problems still persist. Other than that, I suggest you to get advice from senior members of the forum.
Lazy_Pickachu said:
You can try booting in safe mode and then check if the problems still persist. Other than that, I suggest you to get advice from senior members of the forum.
Click to expand...
Click to collapse
Miui 9 does not have safe mode to boot in.
I have a Xiaomi Redmi Note 9S which has the following behaviour: it works normally until the moment it goes under the sun, then (apparently only) the backlight of the screen is turned off and never turns on again until I restart the smartphone, where it works normally until the very moment it "detects" a bright light like under the sun, then the screen goes black. When this happens, sometimes you can still see the shape of what was on screen, but most times it only goes totally black.
When the screen is black, the telephone keeps working normally (music keeps being played, receives calls, vibration responses keep working, etc...(confirmed it using scrcpy and all is working normally)), only that the backlight is turned off and it keeps totally black. During the night, i.e. with artificial light, the telephone works normally (I was able to replicate the error using a strong flashlight above the telephone, the screen also went black the very moment I turned it on).
What I tried to resolve: restarted many times, disabled every auto brightness (also one that I think is a Xiaomi MIUI only, sunlight detector, something like this) settings that are in the configuration menu, restarted using vol up + power button. Factory reseted the smartphone. Disabled pocket mode before and after factory reset.
Any idea how to proceed? What is killing me is that it seem to be a software issue, like, why the screen don't turn on back after a while, but every time you restart it, or why the phone works all night long (i.e. there no strong light on it)?
How to capture the telephone log (logcat perhaps?) and be sure of what is the exact event that is disabling screen? Maybe I can manipulate it to prevent from happening, or to make screen goes back to normal after a while, as I work as a software developer.