Wake from sleep issues - Xiaomi Redmi Note 3 Questions & Answers

Hi all,
I keep running into the same issue on different roms.
When i wake up the device, double tap to wake or the power button, sometimes the screen comes on black with no further. I lock and unlock the device and it doesn't move onto the lock-screen. All i see is the notification bar on LOS17.1, the rest of the screen is black.
I have to hard reset it, and then the device comes back on normally until the issue re-occurs.
Anyone have any idea what kind of hardware issue this is?
Thanks

w1ll1m said:
Hi all,
I keep running into the same issue on different roms.
When i wake up the device, double tap to wake or the power button, sometimes the screen comes on black with no further. I lock and unlock the device and it doesn't move onto the lock-screen. All i see is the notification bar on LOS17.1, the rest of the screen is black.
I have to hard reset it, and then the device comes back on normally until the issue re-occurs.
Anyone have any idea what kind of hardware issue this is?
Thanks
Click to expand...
Click to collapse
Disable Double tap to sleep on lockscreen and check if it happens.

Yes, this bug is in several or probably all Android 10 based ROMs.
Try turning of pocket detection and see if that solves this issue for you.
I am using Havoc OS 3.4, i have kept turn off pocket detection and it does happens to me once or twice in a day or two and that to if i use device heavily with multiple apps.
This bug could be solved but the problem is that bug/crash report is not getting created when black screen occurs and hence it became difficult to resolve.

Black_Stark said:
Disable Double tap to sleep on lockscreen and check if it happens.
Click to expand...
Click to collapse
metelhammer said:
Yes, this bug is in several or probably all Android 10 based ROMs.
Try turning of pocket detection and see if that solves this issue for you.
I am using Havoc OS 3.4, i have kept turn off pocket detection and it does happens to me once or twice in a day or two and that to if i use device heavily with multiple apps.
This bug could be solved but the problem is that bug/crash report is not getting created when black screen occurs and hence it became difficult to resolve.
Click to expand...
Click to collapse
Hey guys,
Just to let you know, i disabled double tap to sleep and pocket detection and i haven't ran into the issue once.
This solved it.
Cheers

Related

[Q] CM7.1 Screen off reboot?

Couldn't find much relavent information to this, but has a quick Q.
On CM7.1, After the screen timeout delay, where the screen automatically turns off (1, 2, 5 mins..), or if i even turn off the screen (not power down), sometimes it simply won't wake back up and i need to reboot by holding the power button down.
Anyone else experiencing this or know how to fix it, or simply a known issue?
try this site it has almost all the answers http://viewsonic-gtablet-for-dummies.webs.com/rom.htm
dada1111 said:
try this site it has almost all the answers (url)
Click to expand...
Click to collapse
Thanks bro, thats actually where i started but found nothing at all related.
I had the same problem when running this, turning off wifi sleep and the on/off animations seemed to fix it.

S3 Lock Screen Issues - Getting Stuck

weird and terribly disappointing. Once in atleast 15 unlocks, when I press the power/wake button, screen just doesnt respond. I try to swipe, but no response. But when I press wake button to turn off screen and press it again, theres no issues. This happens only during unlocking screen. Did anyone face this issue?
rest all is good..no lag..once unlocked phone works perfectly...no lag..no getting stuck..again, let me tell u this issue happens once in 15-20 lock/unlocks.
I think I have the same issue as you, but in case I don't I will post what I am seeing on my device.
In about the same frequency, say once in every 15 unlocks from phone sleeping, the screen will come on but will be completely unresponsive. Doesn't matter if it is swipe unlock or pin code etc, there is no response to touch input on the screen. In fact, I think the screen is just frozen or the operating system is causing the lock screen to hang.
If the lock screen is hanging, pressing power will:
(a) sometimes make the phone sleep again
(b) make the phone screen kind of glitch/blip and then it takes input again
(c) does nothing and the screen remains on and hung/frozen
Occasionally mashing both the volume key and power key will help fix it, but usually if it is completely stuck I have to do a hard reset (holding HOME+VOL UP+POWER and then selecting reboot from the menu).
Now - I think this could be an app, but not sure.
When I first got the phone, set it up with my Google account etc, it went ahead and downloaded ALL the apps I had installed on my previous phone (HTC Sensation running Android ICS). So if it is an app, it is having issues with this phone, not the OS, imo.
I uninstalled all those automatically downloaded apps, and used the phone for a bit without my normal stuff installed. Then started installing apps singularly.
I think it is either Facebook or Alarm Clock Xtreme. The latter makes more sense given it would be polling the system to find out when to go off, so it is doing more in the background I would expect than Facebook or any other non-system app.
Other apps I have installed/running:
Swiftkey X
3G watchdog
Dolphin Browser HD
ES File Explorer
Winamp (locks without this running or running at all in lock screen mode, so that is not the issue)
Real Calc
Google Drive
Facebook
Alarm Clock Xtreme
It is quite frustrating for a brand new phone to have these issues. Not sure if it is hardware related, and if it is, I want to find out soon so I can take it back to carrier within their 28day device swap RMA period.
Thoughts?
So others may try to help or identify the possible cause / fix .......
What is your firmware version?
Are you rooted, custom ROMs or Mods etc?
Stock ROM,Baseband : XXLE8. Build No :XXALE9.
But my screen responds after i press wake button again. You are right seems to be issue with the app. i will just compare your apps and below are the ones which are common between us.
Facebook
3G watchdog
Dolphin Browser HD --i never use
Google Drive
a fix that worked for me
Steps to the solution that worked for me (so far) were to uninstall:
1. Alarm Clock Extreme (no noticeable result but I wasn't needing that application anyway)
2. I had WIFI Fixer installed because of the problems I experienced with the WIFI connectivity on my Galaxy S3.
I disabled that application and problems seemed to go away for a time, but every so in a while they resurfaced. Much less often than before, though.
I was still stuck with my WIFI problem anyway, so I looked into solutions for that problem and since I could not find a workable solution I uninstalled Wifi Fixer and started tweaking my WIFI settings.
While doing that I noticed that disabling "Network Notification" under the Settings -> WIFI -> Advanced tab fixed both my problems.
Now I can't be 100% sure this solution works for all, but I am pretty sure the application that created the problem was "WIFI Fixer".
It's been more than 4 hours now without the "disabled unlock screen from hell", and I’m very happy.
LOOOL
Actually...
My WIFI problem was not solved.... but I found a solution on another forum , which you can read below:
I dialed *#0011# then pressed menu button, then selected WIFI, and pressed the button to turn off the "WIFI power save mode". Hit back until I was back in the homescreen. WIFI has worked to my satisfaction ever since.
This is not a solution, this is a work-around....
It will remove the standby wifi.... My phone was at 0% battery in one night... But actually yes, the phone doesn't hang up when unlocking.
Someone who had replaced the phone could tell me if the problem is solved with a new one ?
calint said:
My WIFI problem was not solved.... but I found a solution on another forum , which you can read below:
I dialed *#0011# then pressed menu button, then selected WIFI, and pressed the button to turn off the "WIFI power save mode". Hit back until I was back in the homescreen. WIFI has worked to my satisfaction ever since.
Click to expand...
Click to collapse
Sadly having the same issue! and only sing LG6 and LG8 of the UK firmware was release.. out the box was LG4 if I am not mistaken... have been putting off custom roms due to the fact stock one is so far good..
This fix seems to be working..Thanks! will live with battery drain as data is expensive in SA!
khan.dharvesh said:
weird and terribly disappointing. Once in atleast 15 unlocks, when I press the power/wake button, screen just doesnt respond. I try to swipe, but no response. But when I press wake button to turn off screen and press it again, theres no issues. This happens only during unlocking screen. Did anyone face this issue?
rest all is good..no lag..once unlocked phone works perfectly...no lag..no getting stuck..again, let me tell u this issue happens once in 15-20 lock/unlocks.
Click to expand...
Click to collapse
This looks like a bug from wifi, i had the same problem and i found a fix:
On the dialer type: *#0011#
Then press menu -> wifi, there is a button ON ( power saving or something ), change it to OFF.
let me know if it solves ur problem
It worked!!
douglasurbano said:
This looks like a bug from wifi, i had the same problem and i found a fix:
On the dialer type: *#0011#
Then press menu -> wifi, there is a button ON ( power saving or something ), change it to OFF.
let me know if it solves ur problem
Click to expand...
Click to collapse
This worked for me!!! Thank you!! I was about to take a hammer to this phone! :good:
I seem to have another problem. When unlocking the phone the screen turns on in a quite ok amount of time, but then when I touch it immediatelly after it turns on it doesn't react to touch. This moment when touch is not working is getting longer and longer depending on how long the system is running, anybody else sees this?
RhavoX said:
I seem to have another problem. When unlocking the phone the screen turns on in a quite ok amount of time, but then when I touch it immediatelly after it turns on it doesn't react to touch. This moment when touch is not working is getting longer and longer depending on how long the system is running, anybody else sees this?
Click to expand...
Click to collapse
Not sure what ROM and kernel you are using, but at a big guess, try reflash another kernel or with less aggressive settings.
Sent from my GT-I9300 using xda premium
hey guys. I have a problem with my s3's lock screen similar to the described. whenever I press the power button to unlock, it takes 2 second for the screen to turn on. Anyone got any ideas on that?

Fingerprint sensor always active.

Greetings,
Does anyone have this issue? Phone wakes up when fingerprint reader is touched (with any finger) even when it's not set up? Is there any workaround?
Nope. In my case the phone just vibrates when touched with non-registered finger, but the screen remains dark.
katoda_ltd said:
Nope. In my case the phone just vibrates when touched with non-registered finger, but the screen remains dark.
Click to expand...
Click to collapse
That happens to me as well if I have a fingerprint set up.
But if there is absolutely no fingerprint is set up, the phone still wakes up whenever the scanner is touched.
To see if you have this issue, delete all your fingerprints from your f1, turn off the display and touch the fingerprint sensor and see what happens.
Yes, then it works like in your case, the phone wakes up.
As I'm using the fingerprint reader, it is not an issue for me. In your case, maybe just add a fingerprint hard to use, e.g. thumb, phone will vibrate when touched but at least will not wake up.
katoda_ltd said:
Yes, then it works like in your case, the phone wakes up.
As I'm using the fingerprint reader, it is not an issue for me. In your case, maybe just add a fingerprint hard to use, e.g. thumb, phone will vibrate when touched but at least will not wake up.
Click to expand...
Click to collapse
It's not a big issue. I was just wondering if it's only a problem with my specific unit.
If its a software issue probably get fixed with updates or maybe a different rom.
You never know if it's a bug or a feature
katoda_ltd said:
You never know if it's a bug or a feature
Click to expand...
Click to collapse
If the FP lock gets triggered without having it activated/registered, it's a major bug and posses a huge security threat.
Rowdyy Ronnie said:
If the FP lock gets triggered without having it activated/registered, it's a major bug and posses a huge security threat.
Click to expand...
Click to collapse
Do you also have this bug?
Windoors said:
Do you also have this bug?
Click to expand...
Click to collapse
Nope I don't have any such issue on miui beta 9.4.26
I would suggest you to do a factory reset if you continue to have this issue.
My phone came with oreo, it had this issue.
Now using 10.3.4 stable (prerooted) the issue persists.
Haven't tried lineageos.
This is a software feature from miui, my mi max used to also light up when no fingerprint is registered. It can be turned off somewhere in settings iirc.
If you don't have a finger print set up, then the finger print sensor acts a bit like the power button to wake the screen. I don't see why you would consider this to be a bug but I've seen this in a few other phones as well. Doesn't strike me as being a problem but maybe that's just me.
srahman53171618 said:
If you don't have a finger print set up, then the finger print sensor acts a bit like the power button to wake the screen. I don't see why you would consider this to be a bug but I've seen this in a few other phones as well. Doesn't strike me as being a problem but maybe that's just me.
Click to expand...
Click to collapse
Well, if you accidentally touch it phone will wake up without you knowing. It can happen while its in your pocket.
Anyone using non-MIUI rom, do you also have this problem?

Always on Display doesn't stay on

I purchased my S21 about 5 weeks ago and I am not sure if I have been experiencing this issue since I bought it but in the last week, I have noticed this issue. When my phone is locked, the AOD will either show for a few seconds to a minute or just won't show. I've ensured it is set to always show, power-saving not set to turn it off, no Bixby routines and any updates are installed for phone/AOD. I've even factory reset my phone and removed the case and screen protector and the issues are still persisting. Does anyone else experience this issue?
Disable all power management... it screws up all kinds of things.
Does AOD show if you tap the screen?
I have disabled all power management that I am aware of and still experiencing issues. I've set it to show on tap and while it worked the first time, subsequent taps do not show the AOD
Video demonstrating AOD tap to show issue
Sounds like a firmware glitch or the flash was corrupted.
Double check all AOD and screen lock settings.
Try turning AOD always on.
Try disabling screen lock... a lock out is the last thing you want anyway.
Play with it... Android's wuv attention.
The case or screen protector won't do this more than likely.
blackhawk said:
Sounds like a firmware glitch or the flash was corrupted.
Double check all AOD and screen lock settings.
Try turning AOD always on.
Try disabling screen lock... a lock out is the last thing you want anyway.
Play with it... Android's wuv attention.
The case or screen protector won't do this more than likely.
Click to expand...
Click to collapse
I normally use AOD always on, I'd tried the tap on the option to test. Going to try flashing it today to see if that helps despite the factory reset not helping.
So I've flashed the stock firmware back onto my device and the issues are still persisting. I've contacted support through the Samsung Members app and it's been escalated to the Research and Development team and am just waiting to hear back.
Did you update any Samsung apps after the reload before testing it? Go with the factory app loads.
Try disabling the lock screen... they tend to end up locking out the intended user anyway, sooner or latter.
If no one else is having this issue it very well maybe a hardware issue.
Did you ever wonder what happens when one or two micro transistor junctions out of the millions in a phone fail? Yes, well...
Unfortunately I can't recall if Samsung apps updated before I tested. I've already factory reset a few times so I'd rather avoid that for now. I've noticed the issues occur when using auto-brightness on AOD in lower light settings. When I say lower light, I mean in my study during the day which I never experienced issues with on my S20 FE. I've sent a report to Samsung Members and am waiting on them to come back to me.
The you
brodieb321 said:
Unfortunately I can't recall if Samsung apps updated before I tested. I've already factory reset a few times so I'd rather avoid that for now. I've noticed the issues occur when using auto-brightness on AOD in lower light settings. When I say lower light, I mean in my study during the day which I never experienced issues with on my S20 FE. I've sent a report to Samsung Members and am waiting on them to come back to me.
Click to expand...
Click to collapse
Did you ever get this fixed. I have the exact same issue on my s20 ultra
Edit: Nevermind just fixed it after 3 days troubleshooting. Oddly it was the the disable AOD while in power saving mode that needed to be disabled even though I don't use power saving mode. Samsung never seem to amaze me with these dumb persistent bugs.
Glad to see you solved the issue. I'd already confirmed this setting was off for me. It's still happening. Looks like it's something to do with the level of light detection as the issue only happens when I have auto brightness set for the AOD. The problem is it's not even that dark when it's happening and never occurred with my S20 FE.

General Why must unlocking my phone be so cumbersome?

The simple user experience of unlocking the device on is so bad on Pixel 6. There's just no winning option.
Smart Lock randomly kicks in, so I can't be sure that a single tap of the screen will turn on the phone.
The fingerprint sensor sucks, and requires a tap on the screen just to bring it up. And sometimes I don't even get the option to use my fingerprint.
I don't even like the single-tap gesture to begin with. It means I'm accidentally turning my screen on all the time just when carrying the phone. It almost started a call with my deadbeat father, who I haven't talked to in 20 years
I could go with no screen lock but then I'm locked out of several key features (like viewing my account passwords). Also, pressing the Power button at all on a phone this big is cumbersome, since I then have to reposition my entire hand to go from pressing it to then interacting with the screen.
I'm already rooted because I absolutely needed the Back button to be on the right side. Now I'm hoping modders can fix the unlocking experience because it's the next big issue in my mind.
The fingerprint scanner is actually very good if you set it up right, and will always be displayed with always on display... No tap required. Problem solved
turbosrrgood said:
The fingerprint scanner is actually very good if you set it up right, and will always be displayed with always on display... No tap required. Problem solved
Click to expand...
Click to collapse
Or lift to check turned on rather than AOD.
turbosrrgood said:
...and will always be displayed with always on display... No tap required. Problem solved
Click to expand...
Click to collapse
This is not my experience at all. Sometimes I get a fingerprint sensor icon. Other times my phone is unlocked via Smart Lock and I get an Unlock icon in place of the fingerprint sensor. Other times I get a Lock icon indicating Smart Lock is expired. Other times I get no icon there at all.
If the fingerprint sensor is there and I'm on the dimmed screen, sometimes it'll just light up and deny, and other times it won't even acknowledge that I've put my finger on the sensor.
If the Unlock icon is there, it requires a tap to unlock (no holding!). So that means I have to actually look at the screen and discern which icon is there to know whether I need to tap or hold.
And Lift to Check Phone would be even more problematic for me, since I'm trying to avoid accidental screen interactions and this would only cause more.
On all my other Pixel phones I just touch the back fingerprint sensor and the phone is on. I don't have to think about a dozen different possible states the phone could be in every time I want to turn it on.
Have you tried to recalibrate it via the Pixel tool thing Google has?
Google Pixel - Update and Software Repair
gavingt said:
The simple user experience of unlocking the device on is so bad on Pixel 6. There's just no winning option.
Smart Lock randomly kicks in, so I can't be sure that a single tap of the screen will turn on the phone.
The fingerprint sensor sucks, and requires a tap on the screen just to bring it up. And sometimes I don't even get the option to use my fingerprint.
I don't even like the single-tap gesture to begin with. It means I'm accidentally turning my screen on all the time just when carrying the phone. It almost started a call with my deadbeat father, who I haven't talked to in 20 years
I could go with no screen lock but then I'm locked out of several key features (like viewing my account passwords). Also, pressing the Power button at all on a phone this big is cumbersome, since I then have to reposition my entire hand to go from pressing it to then interacting with the screen.
I'm already rooted because I absolutely needed the Back button to be on the right side. Now I'm hoping modders can fix the unlocking experience because it's the next big issue in my mind.
Click to expand...
Click to collapse
It sounds like smartlock working as intended (which I find useless, and poor security). It will give you an unlock icon instead of the fingerprint. Maybe you simply don't want smart unlock, which is more useful for password only. This seems like more of a matter of figuring out what features you want to use.
If you changed the Animation Scale in Developer Settings then the AOD fingerprint icon can disappear.
turbosrrgood said:
It sounds like smartlock working as intended (which I find useless, and poor security). It will give you an unlock icon instead of the fingerprint. Maybe you simply don't want smart unlock, which is more useful for password only. This seems like more of a matter of figuring out what features you want to use.
Click to expand...
Click to collapse
I never used to use Smart Lock, but on this phone it means I don't have to deal with the inconsistent fingerprint sensor as often.
gavingt said:
I never used to use Smart Lock, but on this phone it means I don't have to deal with the inconsistent fingerprint sensor as often.
Click to expand...
Click to collapse
Try setting up the fingerprint scanner again, slightly moving your finger with ever press during set up to get every angle and view of the print. It's been pretty much perfect for me. I suppose Google could have helped instruct people to do that better in the process.
turbosrrgood said:
It sounds like smartlock working as intended (which I find useless, and poor security). It will give you an unlock icon instead of the fingerprint. Maybe you simply don't want smart unlock, which is more useful for password only. This seems like more of a matter of figuring out what features you want to use.
Click to expand...
Click to collapse
I just restarted my phone, and then repeatedly unlocked and locked it (sometimes by fingerprint, sometimes by tapping). By the end of the video, the fingerprint sensor icon disappeared completely and wouldn't come back until after another restart:
Streamable Video
Watch this video on Streamable.
streamable.com
This is just one example of the inconsistencies. I haven't changed the animation settings either.
I did see it happen a couple of times in your stream. I don't recall seeing that on mine, but I haven't been looking for it. The only other thing I can suggest is make sure you have the latest updates and/or factory reset.
Edit - I tried to replicate your stream, and the sensor showed in all 30 attempts for me. For whatever it's worth, so might be something specific to your device, maybe settings or software issue
turbosrrgood said:
I did see it happen a couple of times in your stream. I don't recall seeing that on mine, but I haven't been looking for it. The only other thing I can suggest is make sure you have the latest updates and/or factory reset.
Edit - I tried to replicate your stream, and the sensor showed in all 30 attempts for me. For whatever it's worth, so might be something specific to your device, maybe settings or software issue
Click to expand...
Click to collapse
It could be a bug related to my specific settings:
Rooted device, still on the October update
Lock after screen timeout: 30 minutes
Power button locks instantly: Off
gavingt said:
I just restarted my phone, and then repeatedly unlocked and locked it (sometimes by fingerprint, sometimes by tapping). By the end of the video, the fingerprint sensor icon disappeared completely and wouldn't come back until after another restart:
Streamable Video
Watch this video on Streamable.
streamable.com
This is just one example of the inconsistencies. I haven't changed the animation settings either.
Click to expand...
Click to collapse
what are you going on about lol. this is the kind of nonsense that is so irritating. you had 100% success rate unlocking your phone. what's the problem. looks to me like it works. so what's the big deal. and then you have the gall to complain that the sensor icon disappeared after you repeatedly locked and unlocked your phone? yea. try starting your car repeatedly. see what happens with the engine.
kramer987 said:
what are you going on about lol. this is the kind of nonsense that is so irritating. you had 100% success rate unlocking your phone. what's the problem. looks to me like it works. so what's the big deal. and then you have the gall to complain that the sensor icon disappeared after you repeatedly locked and unlocked your phone? yea. try starting your car repeatedly. see what happens with the engine.
Click to expand...
Click to collapse
Sure, ignore my multiple posts on the subject. It's not nonsense. I have no idea why you're trying to minimize this, and why you feel the need to be so combative.
gavingt said:
I'm already rooted because I absolutely needed the Back button to be on the right side.
Click to expand...
Click to collapse
You know gesture navigation is a thing now right? Back buttons are so "last decade".
sic0048 said:
You know gesture navigation is a thing now right? Back buttons are so "last decade".
Click to expand...
Click to collapse
Yes, I know and I hate it. It's extra motion that tires out my hand and I often trigger the gestures when I don't mean to.
gavingt said:
Sure, ignore my multiple posts on the subject. It's not nonsense. I have no idea why you're trying to minimize this, and why you feel the need to be so combative.
Click to expand...
Click to collapse
i will just apologize and go on with my day. good luck with the phone.
I went ahead and updated to the November firmware, and wiped my data as well. Now my phone won't show the fingerprint sensor while unlocking under any circumstances. I also found an interesting bug wherein I'm still able to turn my screen on by tapping it repeatedly even with "Tap to check phone" disabled:
screen-20211102-164842[1]
Watch "screen-20211102-164842[1]" on Streamable.
streamable.com
EDIT: And, of course, as I was typing this the fingerprint sensor just magically came back. And it still doesn't work unless I tap the dimmed screen to wake it first. Watch as it straight up ignores my finger the first time:
screen-20211102-171057[1]
Watch "screen-20211102-171057[1]" on Streamable.
streamable.com
I can recreate this 100% of the time by just setting my phone down for a second and picking it back up, then trying to unlock it. And you can't see it in the video, but the sensor doesn't even light up the first time I touch it. This is clearly a software bug.
gavingt said:
I went ahead and updated to the November firmware, and wiped my data as well. Now my phone won't show the fingerprint sensor while unlocking under any circumstances. I also found an interesting bug wherein I'm still able to turn my screen on by tapping it repeatedly even with "Tap to check phone" disabled:
screen-20211102-164842[1]
Watch "screen-20211102-164842[1]" on Streamable.
streamable.com
EDIT: And, of course, as I was typing this the fingerprint sensor just magically came back. And it still doesn't work unless I tap the dimmed screen to wake it first. Watch as it straight up ignores my finger the first time:
screen-20211102-171057[1]
Watch "screen-20211102-171057[1]" on Streamable.
streamable.com
I can recreate this 100% of the time by just setting my phone down for a second and picking it back up, then trying to unlock it.
Click to expand...
Click to collapse
but at least we know you like dunkin donuts, dominos pizza, and your mom forgets stuff
kramer987 said:
try starting your car repeatedly. see what happens with the engine.
Click to expand...
Click to collapse
Guess you don't know anything about cars. You can start and stop a fuel injected car until the battery dies, and nothing will happen to the engine or fuel system. (Yes, the battery will die if you keep starting the car and tuning it off right away) Just as proof of this, most modern cars shut off the engine when you come to a stop, and restart when you let off the brake. If you're in stop and go traffic, the engine will shut off and turn on repeatedly in a short amount of time nd distance.
Now with classic cars and motorcycles, you my flood the carb with repeated starts. Not a big deal, and not any kind of damage.
The only "damage" in repeatedly starting a car would be normal wear and tear on the starter. They do have a finite lifespan. But again, not damage, just use.

Categories

Resources