This is a Samsung Galaxy S4 Value Edition (GT-i9515), not a very common version of the S4.
ROM: Lineage OS 13 by sombree (jfvelte)
Recovery: TWRP 3.0.3
Status: custom
Generally the phone does not start at all, behaves like a brick. Sometimes it does, though.
In this case, the phone crashes after a few seconds or minutes: The screen freezes, weird patterns (stripes, magenta flickering) appear after ~half a minute or less. Buttons don’t work anymore and I have to remove the battery.
This happens regardless of what the phones state:
Properly booting the phone, using apps, etc. → crashes.
Showing the boot screen → crashes.
Using the recovery → crashes.
Starting download mode → crashes.
Not booted, just showing the “shutdown”-battery charge progress bar while charging → crashes.
This all happens regardless of the state of charge of the battery, or if the phone is connected to a charger. Of course, I already tried clearing dalvik, cache, etc. TWRP shows reasonable CPU temperatures.
Further observations: If I put the phone (without battery, of course) into the freezer for a few minutes, I can greatly increase both the probability that it will boot, and the time before it crashes again.
Is there still a way to repair this phone? I guess it is not a software bug, but is there anything else I could try?
What possibilities do I have to fix the hardware? Replacement parts of this version of the S4 (and especially the motherboard) are not that easily available, unfortunately.
r7el said:
This is a Samsung Galaxy S4 Value Edition (GT-i9515), not a very common version of the S4.
ROM: Lineage OS 13 by sombree (jfvelte)
Recovery: TWRP 3.0.3
Status: custom
Generally the phone does not start at all, behaves like a brick. Sometimes it does, though.
In this case, the phone crashes after a few seconds or minutes: The screen freezes, weird patterns (stripes, magenta flickering) appear after ~half a minute or less. Buttons don’t work anymore and I have to remove the battery.
This happens regardless of what the phones state:
Properly booting the phone, using apps, etc. → crashes.
Showing the boot screen → crashes.
Using the recovery → crashes.
Starting download mode → crashes.
Not booted, just showing the “shutdown”-battery charge progress bar while charging → crashes.
This all happens regardless of the state of charge of the battery, or if the phone is connected to a charger. Of course, I already tried clearing dalvik, cache, etc. TWRP shows reasonable CPU temperatures.
Further observations: If I put the phone (without battery, of course) into the freezer for a few minutes, I can greatly increase both the probability that it will boot, and the time before it crashes again.
Is there still a way to repair this phone? I guess it is not a software bug, but is there anything else I could try?
What possibilities do I have to fix the hardware? Replacement parts of this version of the S4 (and especially the motherboard) are not that easily available, unfortunately.
Click to expand...
Click to collapse
If it is a hardware issue then all you can do is repair/replace the hardware.
DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Related
I love the Angry Team rom v3.6 no issues whatsoever. But now after flashing Angry ROM v4.2 I am feeling certain issues which are very isolated incident (not reported by any of the users so far, i guess). And the bugs are
1. The charging has just gone mad. I would charge it for 100% but once rebooting the phone says that there is absolutely no power or very less (~10% - 15%). Actually I tried to wipe the battery stats, but I could not able to find that option in Philz's Kernel. Can any of the techies help me on how to wipe the battery stats and how can I get the proper stats and correct battery level again. This is very annoying for me, because I dont know even if I see the phone is fully charged, it still may not be so actually.
2. My Note phone mysteriously flickers and automatically shuts down as such flickering intensifies. If I try to connect the phone immediately to charge the flickering stops and be stable for the next 30 mins. This flicker happens even when there is sufficient charge in the phone.
3. At times I see the phone gets hanged.
3. Contacts have a horizontal stripe at top making it difficult to read the recent dialed numbers. (Probably an issue in ROM or something needs to be changed).
Any help is greatly appreciated.
Your battery is dead.. Buy a new battery
Sent from my GT-N7000 using Tapatalk 2
So I have four issues with the nexus 6.
Using stock ROM, not rooted.
1. The remaining charging time shown on the phone is incorrect. It normally takes around 30min more than it states on the lock screen. Using the provided turbo charger.
Battery life and charging is not a problem, the information is.
2. My dialer, or better yet, calling capabilities, don't work sometimes, I need to reboot for it to work.
3. Camera stops working and says: Can't connect to camera. I need to reboot to make it work again.
4. If the flashlight is turned on it turns off automatically after like 15sec and the icon disappears from the quick setting menu. Need to reboot to make it work again.
Anyone else with these issues?
1. that is just an estimate. your phone changes how much voltage goes in when charging, with much less voltage going in after 90%. your phone doesnt count this. it estimates according to where you are in the charging cycle.
2. no idea, havent seen that before.
3. casn be an app or a hardware issue. if it keeps happening, even without any apps installed, id get it exchanged.
4. seems like your phone has a hardware issue, id get it exchanged.
Well, been checking up on things a little, and the dialer problem seems to be on Googles part: https://code.google.com/p/android/issues/detail?id=82949
I think the camera issue as well.
I thought about the same thing with the voltage, since it's a turbo charger, however one would think that it's a thing that could/should/would be implemented on a phone with quick charge technology.
Will try with another non-turbo charger.
The flashlight I'm not sure about, will wait for another update for lollipop, if the issue is not fixed I'll change the phone.
Sent from my Nexus 6 using XDA mobile app
Ever since my update to nougat, my tablet freezes for a second or two several times per hour. I have cleared cache from recovery with no effect. This was a standard OTA update - no root or custom anything.
Is anyone else experiencing this? Any suggestions for a solution?
If problem persists factory reset might do the trick
Updates..
in my experience 80% of them do compromise the performance.
Thus I avoid them like the plague.
I have just bought this table and so far it didn't freeze. However, my computer does not detect the device at all. Massive storage option never appears, and no matter what I change it seems to be forced with mtp. The only thing that can do when connected to computer is charge the battery.
Hello,
In the recent few months, my phone keeps rebooting by itself, even when it is on the desk for hours without getting bothered.
The funny thing is that this is a soft reboot, because there isn't any Google splashscreen. The problem persist through different ROMs and kernels.
Things I tried already:
- swap ROM (PureNexus 7.1 -> NitrogenOS 8.1)
- swap kernel (Franco kernel -> ElementalX kernel)
- factory reset, wipe caches
- decrypt device
- use 3G instead of 4G
- swap radio
- increasing and decreasing CPU voltage and clock
- changing CPU governor
I attach two logs from two different reboots, also the related .rc file.
In the logs, you can see a line similiar to this:
Code:
[310842.492056] init: processing action (sys.shutdown.requested=*) from (/init.shamu.rc:578)
What causes the reboots? Could it be a defective battery issue?
Not a defective battery, but a tired one. Batteries wear out after being used constantly for two years. I know this because I too get the random reboots, though mine does not occur daily like yours apparently does. You can clear the bootloader logs and immediately recharge for a temporary fix, but you will eventually want to replace the battery.
I just replaced my battery yesterday with a new OEM one. Had my phone for 2.5 years so I thought why not. When I took my old one out, it was actually in very good condition but there were some bubble marks around it indicating it overheated at some point.
Nevertheless, I've had random reboots, but the new battery so far hasn't rebooted m phone yet. The process to replace very pretty simple, just need a tool to pry the back cover off and carefully make sure you don't pull it off with too much force. Then there are 22 T4 torx screws.
In my case I'm simply going to live with it, because I plan on switching to a Pixel 2XL later this year. In any event I can't be certain mine is a battery issue as I only encountered this after using Android 8.x ROMs. I just haven't bothered to delve into it.
Oh, I forgot to mention that I tried to wipe the bootloader logs too. No success so far.
I think I order a replacement battery and try to sell the phone with that.
I also plan to switch to a newer model. It seems it is time to switch.
Thanks for the help, guys!
I have a T713 on Android 7. Once the battery level is below about 80%, the tablet will often crash into a bootloop when switching between screens/apps (not while using one app).
When the battery is below 45% it will always crash as above (e.g. wake the tablet to home screen, see that battery is 45%, launch an app = bootloop).
The only way to stop the bootloop is to plug in the tablet. On mains power, the tablet doesn't crash.
I've done a factory reset, wiped cache (after using it a while, of course), tried Safe Mode. Makes no difference. The crash is always reproducible below 45% battery. Battery charge logging does not show any sudden drop in battery reading immediately before/at/after the crash.
The Accubattery app says the battery is at 82% health.
There are reports of similar phenomena in other threads and sites, usually attributed to the battery, but I am sceptical that this is the issue because there is little evidence that people actually solve it by replacing the battery (and the symptoms don't seem to support the basic assumption that there is a loss of power). Any experiences/ideas?
bloomer2011 said:
I have a T713 on Android 7. Once the battery level is below about 80%, the tablet will often crash into a bootloop when switching between screens/apps (not while using one app).
When the battery is below 45% it will always crash as above (e.g. wake the tablet to home screen, see that battery is 45%, launch an app = bootloop).
The only way to stop the bootloop is to plug in the tablet. On mains power, the tablet doesn't crash.
I've done a factory reset, wiped cache (after using it a while, of course), tried Safe Mode. Makes no difference. The crash is always reproducible below 45% battery. Battery charge logging does not show any sudden drop in battery reading immediately before/at/after the crash.
The Accubattery app says the battery is at 82% health.
There are reports of similar phenomena in other threads and sites, usually attributed to the battery, but I am sceptical that this is the issue because there is little evidence that people actually solve it by replacing the battery (and the symptoms don't seem to support the basic assumption that there is a loss of power). Any experiences/ideas?
Click to expand...
Click to collapse
Have you reinstalled the factory image with Odin? That would be the logical place to start.
sliding_billy said:
Have you reinstalled the factory image with Odin? That would be the logical place to start.
Click to expand...
Click to collapse
Thanks for your suggestion. The device is currently stock, unrooted. Could you tell me why using a factory image could help? (The last official update to firmware on the device was a long time before this problem appeared in March this year.)
bloomer2011 said:
Thanks for your suggestion. The device is currently stock, unrooted. Could you tell me why using a factory image could help? (The last official update to firmware on the device was a long time before this problem appeared in March this year.)
Click to expand...
Click to collapse
Like any device, who knows what has managed to get jumbled up in the image. Security patches and other updates can only overwrite so much since they are doing in place updates. Even a factory reset has to be pulling the image from the device itself where a factory image is completely clean. I know it is a PITA to set a device up again, but the fact that you can do the system stuff before installing any apps or files or anything and then see if the problem shows up immediately after imaging. If so, then you pretty much have narrowed it down to at least a hardware problem and you have less places to look (the battery for example). The last time I flashed the stock image a month or so ago, it took a security updated Feb 2019 (maybe) before I rooted and such putting it in the "modified OS" world where it will not get updates again until I flash stock again. The last actual OS update might have been around the end of 2017 beginning of 2018. Too bad since the device can clearly run builds past Nugat and has never been deprecated.
sliding_billy said:
I know it is a PITA to set a device up again, but the fact that you can do the system stuff before installing any apps or files or anything and then see if the problem shows up immediately after imaging. If so, then you pretty much have narrowed it down to at least a hardware problem and you have less places to look (the battery for example)
Click to expand...
Click to collapse
Thanks for the extra info! I'll look into doing that.
A preliminary update, in case anyone visits this thread before I finish thorough testing:
The cause is emphatically NOT the battery. After reflashing firmware and then doing a factory reset, as sliding_billy suggested above, I am unable to reproduce the problem. The tablet appears to be working fine in its current fresh state, even running on low battery power. I'm now planning to gradually reinstall apps and system updates (if any) and continue testing.
bloomer2011 said:
A preliminary update, in case anyone visits this thread before I finish thorough testing:
The cause is emphatically NOT the battery. After reflashing firmware and then doing a factory reset, as sliding_billy suggested above, I am unable to reproduce the problem. The tablet appears to be working fine in its current fresh state, even running on low battery power. I'm now planning to gradually reinstall apps and system updates (if any) and continue testing.
Click to expand...
Click to collapse
Glad that at least the initial solution is working. We'll see as you reinstall apps and complete any settings if it really was that "simple."