So i was using happily my le max 2 for amost half a year, when this thing kicked in.... System services.... for no reason what so ever, it jumped to the top of the list in battery consumtion. It was devouring entire battery in less than 5 hours! + it made phone red hot (~41*C) with no apps running.
So i started to look for solution.... and i found that factory reset may help, and it did!.... But for a week... After that, guess who's back on top? This time is even worse, some days, it outruns screen in power consuption.
Now, I'm out of ideas on what to do, so Please, help, i really don't want to do factory reset every week or so
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have problem with battery drain too. But in my case it looks different. When I check fb, and messenger for a few minutes battery goes down to 96 or less percentage. I don't know what happened. Now, when I write this post battery goes down 3%...
BeeTrain said:
I have problem with battery drain too. But in my case it looks different. When I check fb, and messenger for a few minutes battery goes down to 96 or less percentage. I don't know what happened. Now, when I write this post battery goes down 3%...
Click to expand...
Click to collapse
maybe try to reinstall apps? On my device they all use less than 1%....
In my case core proces of System service is qfp-daemon, it runs every major and minor system process, like, Crash handler, key chain or Android system, so no way you can kill/hibernate it...
Mortill said:
maybe try to reinstall apps? On my device they all use less than 1%....
In my case core proces of System service is qfp-daemon, it runs every major and minor system process, like, Crash handler, key chain or Android system, so no way you can kill/hibernate it...
Click to expand...
Click to collapse
Which ROM do u use? I have stock 26s by C. B. G. And this is my System Service usage.
I use stock room, the one that came with the phone, and in 5 hrs. System services ate 1052 mah. I'll upload pictures as soon as I become normal member
Okay, looks like phone decided not to eat battery, system services is now really low on battery consumption and battery will last approx 1 day 16 hrs... Dunno what fixed it but it fixed itself overnight :v
How can I fix the same problem?
System service exploits too many batteries.
lazye53 said:
How can I fix the same problem?
System service exploits too many batteries.
Click to expand...
Click to collapse
factory wipe helps, also you may try to toogle gps on and off ( i noticed system service was going crazy when i launched gmaps and it could not locate my phone on map) or plug in charger and wait, maybe it will end.
For more permanent solution, i recommend to change system, there are plenty roms on this site so pick one and go for it
Mortill said:
factory wipe helps, also you may try to toogle gps on and off ( i noticed system service was going crazy when i launched gmaps and it could not locate my phone on map) or plug in charger and wait, maybe it will end.
For more permanent solution, i recommend to change system, there are plenty roms on this site so pick one and go for it
Click to expand...
Click to collapse
Deleting the factory is not helping.
I have no problems with custom rom (Aicp, Omni, etc.)
I am looking for a different solution. I want to stand a little on Eui.
I have problem with my cell phone Model "Le X829", the phone reboots itself, I have already restored the device, the error persists, Can anyone help me?
alannosr said:
I have problem with my cell phone Model "Le X829", the phone reboots itself, I have already restored the device, the error persists, Can anyone help me?
Click to expand...
Click to collapse
Google your issue, maybe someone already had this problem and found the solution. If no luck, try changing rom to different one.
I have a theory of what this could be. I have the same problem but my phone also vibrated in short intervals. As if I'd try to unlock it with the fingerprint but it was denied.
So I just disabled the fingerprint-unlock and it ceased vibrating already.
It was really unrealiable anyways so I unlocked it with the other method more often than not.
Just while writing this the phone also already cooled down and a check at the battery-drain shows that the steep downward-dive is now almost flat. So I guess I found it:
An error with the fingerprint-sensor reporting someone is trying to unlock all the time.
Xilmi said:
I have a theory of what this could be. I have the same problem but my phone also vibrated in short intervals. As if I'd try to unlock it with the fingerprint but it was denied.
So I just disabled the fingerprint-unlock and it ceased vibrating already.
It was really unrealiable anyways so I unlocked it with the other method more often than not.
Just while writing this the phone also already cooled down and a check at the battery-drain shows that the steep downward-dive is now almost flat. So I guess I found it:
An error with the fingerprint-sensor reporting someone is trying to unlock all the time.
Click to expand...
Click to collapse
Well fingerprint sensor on this phone is trash so it could cause some problems.
Related
My tablet will not boot any farther than the Viewsonic Birds screen. At first I thought this has to be a software-related issue. That being said, I've tried every single possible combination using nvflash to no avail. Today i decided to take a closer look into my tab and noticed on the docking station connector connecting to the system board, one of the wires were clipped. Now because of its position (fifth wire from the left) I at first assumed it came that way (not sure why I thought that but yeah...). Once I found a high-def picture of the tab's system board untouched I realized this was not the case and I somehow clipped it upon taking the tablet apart. I attached a picture of the one I found with a red arrow pointing to the wire in question here.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Does anyone know what exactly this wire is responsible for?
Is it possible that this wire being cut is causing my tablet to get stuck at "The Birds" screen?
Also, has anyone had any luck with getting their hands on any schematics or wiring diagrams of the gtab?
Has anyone done something similar to this, and how were you able to rejoin the cut wires (with them being such a small gauge)?
If this wire is the culprit (which I'm praying is the case, so I atleast know the problem), my best guess is because upon boot-up the OS goes through its checklist and once reaching the docking station connection, this wire being cut halts the boot-up process hindering me to go any further. That sound like an accurate assessment? I'm just trying to understand the issue as best I can.
Any insight would be greatly appreciated, Thanks!
I really don't see that as being an issue.
When did you open the tab up? Before or after boot issues?
Have you hit the internal reset button?
Have you double checked your nvflash files and stock image to make sure they are correct for your system/Gtablet?
Mantara said:
I really don't see that as being an issue.
When did you open the tab up? Before or after boot issues?
Click to expand...
Click to collapse
Both, first time I opened it everything went smooth and started right up after back together. Second time was so I could put a dab of MX4 thermal compound on the tegra2 chipset, and ONLY on the chip; none on the board. After back together, it turns on but freezes at 'the birds'. During this whole thing, I had BoS 5.2a loaded.
Mantara said:
Have you hit the internal reset button?
Click to expand...
Click to collapse
Since this started, only every time Ive tried anything related to formatting (format all.zip), or nvflashing.
Mantara said:
Have you double checked your nvflash files and stock image to make sure they are correct for your system/Gtablet?
Click to expand...
Click to collapse
I have tried flashing back to bekit's stock (pre 4349, how mine came) and stock 4349 1.2 (since I was on a 1.2 BL at the time). Between every flash, I've hit the hard reset, ran the FORMAT ALL.zip, then preceded to nvflash.
Its also hard for me to believe this is somehow a hardware issue. Seems to me if it was, the tablet simply wouldnt turn on or I atleast wouldnt get a picture. One interesting thing roebeet brought to my attention was that eventhough it freezes at the birds screen, the little black bar along the bottom still pops up meaning the kernel is even being recognized, then it freezes. It would be nice if I could know the order precedence when this tablet is turned, as in the checklist the soft/hardware go through. Maybe that could help with narrowing this problem.
Anything else you can think of, please let me know cuz I'm almost at wits end.
Dueces99 said:
Its also hard for me to believe this is somehow a hardware issue. Seems to me if it was, the tablet simply wouldnt turn on or I atleast wouldnt get a picture.
Click to expand...
Click to collapse
Actually, weird things tend to happen in regard to hardware issues.
I had a laptop that I dropped from 3 foot up. Drag and drop function stopped working. Half my keyboard stopped working, but only for certain programs. Some boots resulted in the taskbar not registering until I control alt delete to bring up the task manager window. At first, I really thought these were all software issues. But after reinstalling windows for 3 times the same damn things kept happening.
So, yeah, hardware issues do result in weird software issues. It's like hitting yourself on the head with a hammer. It's a hardware issue, but you might end up a little cukoo afterwards.
goodintentions said:
Actually, weird things tend to happen in regard to hardware issues.
I had a laptop that I dropped from 3 foot up. Drag and drop function stopped working. Half my keyboard stopped working, but only for certain programs. Some boots resulted in the taskbar not registering until I control alt delete to bring up the task manager window. At first, I really thought these were all software issues. But after reinstalling windows for 3 times the same damn things kept happening.
So, yeah, hardware issues do result in weird software issues. It's like hitting yourself on the head with a hammer. It's a hardware issue, but you might end up a little cukoo afterwards.
Click to expand...
Click to collapse
Yeah, hardware issues like that I'm accustomed to having 15+ years experienced working on/building oem/aftermarket systems and being a pc technician by day. But this issue is getting harder to believe it is hardware since A)The wire accidently cut belongs to the docking port and B)The symptoms its exhibiting are the exact same symptoms I've experienced with my tab in the past before opening it at all. But with that being said, I dont know what else I can try on a software level.
One thing I thought of last night that I'll try sometime today is just trying to install bekit's stock 1.1 ROM from my external sd. Read somewhere that the internal sd has gone bad on some gtabs. Dont know if this will work since nvflash seems to flash properly, it just doesnt reboot and I dont know what else to do at this point. Thanks for your input though.
A few weeks ago my Evo 3D started to turn off on its own at random times andwon’t turn on until took the battery out. I did some searching around andnoticed that many people are having the same problem. Also, I have noticed thatmany suggestions were that some app is killing the phone. Well after diggingaround in my phone and un-installing all apps, the phone was still doing it. Inthe last few days I accidently shut the phone off by just moving the batterywhile it’s in the phone. After some more messing around, the phone does shutoff when I push the battery away from where it touches the metal prongs on thephone. If anyone else having the same problem can test out my fix, it would begreat.
The fix:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you search around, a lot of people did have the same issue you had. Your solution should work and has already been confirmed by others.
aypanthony said:
If you search around, a lot of people did have the same issue you had. Your solution should work and has already been confirmed by others.
Click to expand...
Click to collapse
that sounds good, but i couldnt find this anywhere.
I guess I should have said "a few" people. I think a loose battery or bad connection can cause random reboots and shutdowns. If you search for those terms you may find some more threads. Here is the one I was thinking of.
http://forum.xda-developers.com/showthread.php?t=1196380
stas333 said:
A few weeks ago my Evo 3D started to turn off on its own at random times andwon’t turn on until took the battery out. I did some searching around andnoticed that many people are having the same problem. Also, I have noticed thatmany suggestions were that some app is killing the phone. Well after diggingaround in my phone and un-installing all apps, the phone was still doing it. Inthe last few days I accidently shut the phone off by just moving the batterywhile it’s in the phone. After some more messing around, the phone does shutoff when I push the battery away from where it touches the metal prongs on thephone. If anyone else having the same problem can test out my fix, it would begreat.
The fix:
Click to expand...
Click to collapse
i was having the same issue but i read on some posts that the radio was an issue
so i had the old radio on my phone i only flash the newest radio and since then i haven't got no reboots...already a month and my phone is working fine...
My problem is related to ambient temperature. If it is above 90 out it restarts randomly. I go inside and it is fine. This is related to nothing else.
I went to the park with my kids this weekend and had no restarts because it was 70 out. I was at the same park doing the same things a few weeks ago...it restarted every 5 minutes.
After 2 weeks of cool weather, it restarted today because I am wearing black jeans (it was in the pocket) and it is 80 out.
I am going to exchange it AGAIN--I had the same problem with the last one.
I had that problem with my 2nd EVO and they replaced it at the Sprint store. That was a couple days after my 30 days
Sent from my PG86100 using XDA App
Im having the same issues. Random reboots every hour on Vaelpak and eternity.
Camera failed after ICS update,
Both the cameras of the tablet failed to work after the latest ICS update which happend today morning. Does anybody have a solution for this ? I already logged a ticket with Asus but have very less hope they would ever care.
Thanks!
raghunm said:
Camera failed after ICS update,
Both the cameras of the tablet failed to work after the latest ICS update which happend today morning. Does anybody have a solution for this ? I already logged a ticket with Asus but have very less hope they would ever care.
Thanks!
Click to expand...
Click to collapse
I just tried using my cameras tonight and it doesn't work either. Already rebooted 5 times with no luck. Stock .28, this is all I get:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Mine works fine, Try one of the following:
1) Cold Boot: turn off unit, hold power and volume down until it boots and you see text on top. It should go into something just let it restart and cold boot. If this doesn't work try two.
2) Factory Default Wipe: Might help but idk. If it doesn't try 3?
3) Manual update to .28: If this doesn't fix the issue I am out of ideas.
HiddenSanctum said:
Mine works fine, Try one of the following:
1) Cold Boot: turn off unit, hold power and volume down until it boots and you see text on top. It should go into something just let it restart and cold boot. If this doesn't work try two.
2) Factory Default Wipe: Might help but idk. If it doesn't try 3?
3) Manual update to .28: If this doesn't fix the issue I am out of ideas.
Click to expand...
Click to collapse
Cold boot didn't work for me, I'll try a factory reset later I guess. This is disappointing.
Edit: I just decided to try the camera again, "cannot connect to camera" flashed up a few times and now I'm in a bootloop? I hate this maybe I'm just having a hardware problem. I hate RMA. The funny thing is that this worked fine for months on .21
How can I stop a bootloop without a battery pull? Hold the volume down button and power button while it tries to do a boot?
Yuhfhrh said:
Cold boot didn't work for me, I'll try a factory reset later I guess. This is disappointing.
Edit: I just decided to try the camera again, "cannot connect to camera" flashed up a few times and now I'm in a bootloop? I hate this maybe I'm just having a hardware problem. I hate RMA. The funny thing is that this worked fine for months on .21
How can I stop a bootloop without a battery pull? Hold the volume down button and power button while it tries to do a boot?
Click to expand...
Click to collapse
I am not sure but you can try that. Either that or wait for the battery to die. If you've got a hardware problem, no software solution is going to help you here. sorry =\
The green camera is hardware. Try gently squeezing the areas around the camera, it may fix it for a min. I had the same problem. You will probably have to RMA.
Argh.. Mine just went the same way!
lamboboy732 said:
The green camera is hardware. Try gently squeezing the areas around the camera, it may fix it for a min. I had the same problem. You will probably have to RMA.
Click to expand...
Click to collapse
Hey guys, having same problem since last update. But I don't see how it could logically be hardware. I can still use video on the back camera and that works fine. If i load my camera app i get the fuzzy screen, but when i switch to video and then back to camera i get clear photo, just when i take the photo it turns green. If it was hardware i dont think video would work to begin with. Any way of removing new updates? I have no dea
Hey guys,
recently my s2 died (wednesday). I suspect it was due to condensation.
anyway, today i put a battery in it after leaving it in rice, and it turned on.
however, the phone was hot, very hot actually and the battery life didnt seem consistant. eg. id put a battery in, itd say 80% then turn off the phone, turn it back on and itd say 9%. this is in the space of a couple mins.
ive got 3 batteries, and all showed similar things.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
the above photo shows where the heat is coming from. its too hot to touch. it wasnt like this before.
it doesnt even need to be turned on for it to heat up. once a battery is inserted, its almost instantly burning.
anyone know what that is which is circled, what the possible cause for the excess heat is, and any solutions?
thanks
Hi, I believe the IC you have circled is for battery charging/control which in the s2 is a max8627. The IC could have failed or maybe one of the caps near it (which do look like they have some sort of residue on them).
Short of replacing them there might not be much you can do i'm afraid. If you are feeling adventurous and have a good soldering iron (a steady hand can help too ) give it a try.
Mike.
ibnabatoot said:
Hey guys,
recently my s2 died (wednesday). I suspect it was due to condensation.
anyway, today i put a battery in it after leaving it in rice, and it turned on.
however, the phone was hot, very hot actually and the battery life didnt seem consistant. eg. id put a battery in, itd say 80% then turn off the phone, turn it back on and itd say 9%. this is in the space of a couple mins.
ive got 3 batteries, and all showed similar things.
the above photo shows where the heat is coming from. its too hot to touch. it wasnt like this before.
it doesnt even need to be turned on for it to heat up. once a battery is inserted, its almost instantly burning.
anyone know what that is which is circled, what the possible cause for the excess heat is, and any solutions?
thanks
Click to expand...
Click to collapse
Hi, thanks for the reply. makes sense why it gets so hot now.
should of mentioned, thats not my photo. i found it on another thread, but its the same place thats heating up on mine.
i think i might give cleaning that area with isopropyl a try, although not sure if thatll make much difference.
edit- using the ic part number you mentioned, i came across this thread http://samsunggalaxysforums.com/sho...age-overheating-u503-(USB-OTG)-and-Workaround
which is exactly what is happening to mine.
ibnabatoot said:
Hi, thanks for the reply. makes sense why it gets so hot now.
should of mentioned, thats not my photo. i found it on another thread, but its the same place thats heating up on mine.
i think i might give cleaning that area with isopropyl a try, although not sure if thatll make much difference.
edit- using the ic part number you mentioned, i came across this thread http://samsunggalaxysforums.com/sho...age-overheating-u503-(USB-OTG)-and-Workaround
which is exactly what is happening to mine.
Click to expand...
Click to collapse
Good find there. Sounds like this IC in particular is prone to failure after being shorted out. Will you be attempting this fix?
yeah, no other option really. getting a new phone soon, so thisll be handed down to a family member if it works fine after attempting the fix.
update-
just used a dremel with the smallest diamond tipped bit i could find, and wore the chip away.
the phone still turns on, and temps are not only feel different, but are reported as 31c (was 80c when the chip was present).
so a success!
Sorry for late reply glad it turned out to be that component and you managed to fix it.
Sent from my GT-i9100 using Tapatalk now Free
I get this message on several spro 2's that I have. You try to turn on the projector and again and again it gives this message. I have a few of these that have the same issue as I buy and fix these android projectors regularly as the fan is common to fail. I pull the actual projector unit out and put it in another known good unit and it works fine. So it has something to do with the motherboard or system files. I have tried to restore the system and it does not help. So either the motherboard has some bad component or there are some system files that do not change even after restoring. I think it is a failsafe thing zte put in to never allow you to run the projector as the fan has quit working.
So I have spent the past few days researching adb stuff. I rooted the device and can access the system folder. So as a last ditch effort I want to try pulling all system files from a known good spro2 and push/write over system files on the spro2 with this issue. Is this possible to do? Or would it freeze up the device or brick it or something?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Since I have an spro 2 with working projector is it possible to somehow flash all files like a recovery type thing. Then run it in the recover with sd card in recovery mode? Please any help would be so awesome, these things are just paper weights if the projector doesn't work, lol I am not so stupid that I won't figure out medium level stuff, I have been familiar with system level stuff since windows 95. Back then drivers would actually create problems that you had to manually fix, yes I am old.
Yes NEEDED
Did yo ever figure this out? that would be awesome. its frustrating, because i have a $400 paperweight.
metallicahq2007 said:
Did yo ever figure this out? that would be awesome. its frustrating, because i have a $400 paperweight.
Click to expand...
Click to collapse
Nothing yet. Hope someone here has some idea's.
I will be working on this as I just started getting a similar message but the problem with mine is not the fan, the dialog box I get says" the battery life-cycle limit reached. please contact after-sale support to change a new battery. projector will turn off in 5 minutes. this is ZTE using randsomware on their device to extort you out of more money to keep your device running. this is at the moment an unproven theory but is supported by the following information that has conflicting accounts given from different branches of ZTE USA support staff.
contacted ZTE USA support from live chat on the ZTE USA support site. The support assistant told me that the battery needed to be replace and that it would cost 150USD for me to ship it to the repair facility and have them change the battery, I asked if I could purchase the battery as I was fully capable of making the exchange myself since it is no longer under warranty. I was told that under no circumstances would ZTE make the battery available for purchase except through paying for them to replace it, I searched around and found an aftermarket battery for 30USD with the exact same specs and battery connector as the original. (ZTE does not make these batteries, they are Samsung cells as I found when I took the original out which had swollen so much I couldn't close the unit around it while I waited for my aftermarket battery to arrive so in a way cool points to ZTE for making sure your battery didn't explode after it had a fault) I purchased the aftermarket battery and was able to do the full teardown, battery replacement and rebuild in less than 10 minutes meaning they are charging over 250USD hourly for repairs when the techs that do these repairs make on average 12-14USD per hour.
after replacing the battery I powered up the device and the dialog and shutdown still happens. I reached out to ZTE USA on Twitter because it was a weekend and livechat was unavailable on the support page to request the reset code/software/jig that is used to reset the message and shutdown function and was told that no such thing exist, and was asked to send it in for repair if the following steps did not remove it, It was then detailed to me that all ZTE does at the repair facility when replacing a battery was to install the battery, do a master reset on the device and reflash the firmware. I downloaded the firmware from the link on the ZTE USA support site. because it was not labeled update.zip which is what the stock recovery requires to flash the firmware, I asked a support assistant through the live chat on the support site if the linked firmware was the signed zip since it will not flash an unsigned update.zip in the factory recovery environment, the support assistant came back with "unfortunately you will have to send it to us to have the firmware reflashed as ZTE will not allow support staff to send firmware or provide download links to official firmware and that the link on the support site was NOT the official firmware. The support assistant then quoted the same 150USD charge to flash the firmware and not replace the battery since I had already replaced it. I decided to try the flash anyway as if it was not a signed firmware file it would just fail to flash and I would still be in the same predicament. it flashed successfully (proof support staff is lying to get repair orders filled and sold)
I followed those steps, replace battery, master reset, reflash the firmware. power it up, the dialog and shutdown still persist.
what's interesting to me is if there is not a software/firmware reset code, why is there a root application in the google playstore that is capable of resetting this issue?
the developer of the app is charging around 30USD for a permanent reset, but you can use a temporary free reset to "make sure its going to work before you purchase the full reset"
this issue has affected so many people I have decided I will be rooting my device, to find this issue myself, I will then try to build a team of developers to help me create a custom recovery/ and up to date ROM as well as a custom bootloader (i'm not 100% sure but I've seen a few posts that say the bootloader can be unlocked) for this device that will remove ZTE's randsomware without getting rid of the protective features. PM me if you have any experience in development of custom TWRP builds, and Custom ROMS and would like to contribute to restoring the proper function of these devices for everyone that has one.
MotoDefier said:
I will be working on this as I just started getting a similar message but the problem with mine is not the fan, the dialog box I get says" the battery life-cycle limit reached. please contact
Click to expand...
Click to collapse
Sounds good! Let me know what you find out. I have wanted to mod the brightness to go even lower, low enough to use at night and not have the fan screaming or hopefully low enough to just stay off so I can sleep with it on.
It is strange you have this problem. I also had the swelled battery on my working spro2 and just removed it and use without a battery, I never get a warning. There are components next the the battery that I would think detect heat. I assume more of them for projector also which gives my error code. So I guess whenever it reaches a high enough temp there must be some chip that can not be wiped by firmware flashes, and it tells the software to not let the projector run. Come to think of it I should open my non working units again and see with my multimeter is there is some difference in them, maybe they are a fuse like thing, when they short to on it sends message to lock the unit down. That would be terrible to use those parts on a good working machine and get the permanent error code when nothing is wrong with it, lol. You know what, I would think maybe if your fuses did go out try opening it again and removing that whole battery compartment, or put tape over those connectors that press against the motherboard for them, maybe if there is no connection from them to the motherboard it will give the all clear and let you turn on the projector again.
My theory for the common swelled battery issue-- I would assume is from the battery sitting in the huge amount of heat that the projector gets to when running on high for a long time. I have my projector upside down mounted to my wall so I can control it while laying down in my bed. When it is upside down like this the heat gets even more, so hot that you can't keep your hand on the unit. A few months after using it upside down I hear a loud pop coming from it, the battery swelled so much that the case cracked open. I now have it all taped up because it damaged all the screw mounts.
BTW I made a full tear down video of the projector if you only made it to the battery part. Not too hard to pull it all apart, just takes a good hour or so.
https://www.youtube.com/embed/3VEwNGeXg5U?rel=0