Database Info

[Q] Display Failure 1 Month after flashing CM 10.1 - any ideas as to the cause?

Hi Everyone,
I bought an S3 at the end of May, rooted and flashed cm 10.1 about a week later (and flashed firmware required to get the camera working a few days after that).
Earlier this week, the display suddenly shifted green and started to die - no amount of resetting, wiping, or unrooting and flashing stock would fix it (the screen ultimately came back on, but with a permanent blue-green tint and low resolution). Although I've basically chalked it up to a hardware failure (maybe gpu?), I got a replacement and am a little hesitant to flash CM again for fear that this might be a common issue.
Has anyone here experienced something similar? Is there any way that flashing and running a custom rom for a month could put undue stress on the motherboard, gpu, or other hardware? Would a custom kernel address the issue?
Just basically looking for thoughts from people who are way more experienced with this stuff than I am. Sorry if this has been posted before; I browsed the forums briefly and the display issues I saw didn't quite seem to match what I experienced.

purudaya said:
Hi Everyone,
I bought an S3 at the end of May, rooted and flashed cm 10.1 about a week later (and flashed firmware required to get the camera working a few days after that).
Earlier this week, the display suddenly shifted green and started to die - no amount of resetting, wiping, or unrooting and flashing stock would fix it (the screen ultimately came back on, but with a permanent blue-green tint and low resolution). Although I've basically chalked it up to a hardware failure (maybe gpu?), I got a replacement and am a little hesitant to flash CM again for fear that this might be a common issue.
Has anyone here experienced something similar? Is there any way that flashing and running a custom rom for a month could put undue stress on the motherboard, gpu, or other hardware? Would a custom kernel address the issue?
Just basically looking for thoughts from people who are way more experienced with this stuff than I am. Sorry if this has been posted before; I browsed the forums briefly and the display issues I saw didn't quite seem to match what I experienced.
Click to expand...
Click to collapse
A co-worker of mine had an S3 T999 on tmobile that did this same exact thing on the stock unrooted rom. I'd say its unrelated to CM, and glad you got a replacement. It should not do it again, so CM is safe to run on it.

Not a Rom issue. Sounds like just bad luck of the draw. I am on my 3rd or 4th s3 and i haven't had a Rom kill my phone yet.
Sent from my GT-P5113 using xda premium

Problems with Lollipop

Ok, I am on the OTA Lollipop upgrade on non rooted S5. Ever since I have gotten the Lollipop update, my phone has been VERY laggy, battery life is half as it was, and today I noticed the phone getting REALLY hot. I am not sure what is going on. Is anyone else having these issues? What could I look at to be the cause of the issue?

djprotege said:
Ok, I am on the OTA Lollipop upgrade on non rooted S5. Ever since I have gotten the Lollipop update, my phone has been VERY laggy, battery life is half as it was, and today I noticed the phone getting REALLY hot. I am not sure what is going on. Is anyone else having these issues? What could I look at to be the cause of the issue?
Click to expand...
Click to collapse
Same exact thing going on over here. Since Lollipop, exact same issues on my Sprint Sammy S5

Note Edge Lag and Icons linger for hours!

I have the Sprint Note Edge and its lagging like crazy and the headphone and S pen icon stay at the top until restart....

Lag and icons remain
I am having this exact same issue ever since update to 5.1.1. Also have gotten substantially more bug reports. Actually I'm not sure that I've ever had one before this. Kinda crazy!

Good, I thought i was the only one. Are you rooted?

I am having the same issue on my Note 4 running 5.1.1. I am also seeing various threads on the same issue outside of xda. Has anyone managed to fix this? From the looks of it this is a software issue.

Was anyone able to find a solution to the lingering icons? It is driving me mad...

S-Pen not working but touch

Hi,
I already did a lot of research the last few days but could not solve my problem, maybe somebody hat the same problem.
The problem is as simple as in the title. My Note 10.1 GT-N8010 does not respond to my S-Pen anymore but to my fingers.
The problem occured after I didn't use the tablet for a few days. The only thing i noted was that it ran out of battery and switched off (vibrating). When I wanted to use it, the tablet date was reset to 2012.
I already replaced the S-Pen and the Digitizer glass as well as rooted to cyanogen and switched back to stock rom 4.4.2.
Any suggestions what i could do next?

Hi,
Having the same problem. When I use the stylus of my Note 3 it works perfectly. Very strang.
Have absolutely no clue what's wrong with my Note 10.1
You already have more luck with yours?

Hey,
no I were not lucky.
I figured out how the whole stylus works. On the mainboard is a chip that generates an electromagnetic field that tracks the styles. So i guess this chip might be damaged and it is not possible to replace that without replacing the whole mainboard. For information see androidauthority[dot]com/break-it-down-how-does-the-s-pen-work-154435/

SM-365 Firmware Overheating issues

Hi All,
So I have come across a rather large issue when having the charging pins on my Samsung Gear Fit 2 Pro replaced due to corrosion(know defect :/). The watch charges, that's fine, however, upon first boot, it got extremely hot at the power button and HR sensor. Upon researching I discovered this was an issue with Samsung gear devices after roughly June 2018, so I decided to try and downgrade the firmware. I initially downloaded the stock firmware for SM-R360 (by mistake) and updated the watch. The overheating issue was gone and the watch worked fine however none of the sensors worked, which was to be expected as it was the wrong firmware for the device, which actually need SM-R365. So I then arrived at the post "SM-R365 Stock firmware and Combination firmware" by deadman96385. The technique for updating firmware is perfect, no issue there. However, upon uploading the stock firmware to the watch, the horrible overheating issue returned but all the sensors are functioning beautifully. So I am a tad confused? Is it hardware related and time to abandon this watch??
Any assistance will be greatly appreciated.

Hi ?
TRadioactive said:
Hi All,
So I have come across a rather large issue when having the charging pins on my Samsung Gear Fit 2 Pro replaced due to corrosion(know defect :/). The watch charges, that's fine, however, upon first boot, it got extremely hot at the power button and HR sensor. Upon researching I discovered this was an issue with Samsung gear devices after roughly June 2018, so I decided to try and downgrade the firmware. I initially downloaded the stock firmware for SM-R360 (by mistake) and updated the watch. The overheating issue was gone and the watch worked fine however none of the sensors worked, which was to be expected as it was the wrong firmware for the device, which actually need SM-R365. So I then arrived at the post "SM-R365 Stock firmware and Combination firmware" by deadman96385. The technique for updating firmware is perfect, no issue there. However, upon uploading the stock firmware to the watch, the horrible overheating issue returned but all the sensors are functioning beautifully. So I am a tad confused? Is it hardware related and time to abandon this watch??
Any assistance will be greatly appreciated.
Click to expand...
Click to collapse
I think it's some bug on firmware, I have similar problem with Gear Fit 2 Pro, it's overheating after detecting intensive training, like I think, and battery is discharging superfast, about 3 hours…
I think it will be fixed in new firmware version ?

D_Vovan_238 said:
I think it's some bug on firmware, I have similar problem with Gear Fit 2 Pro, it's overheating after detecting intensive training, like I think, and battery is discharging superfast, about 3 hours…
I think it will be fixed in new firmware version
Click to expand...
Click to collapse
I fixed it by disabling dynamic training detection…
Now everything works perfectly