my phone dropped (50cm not that big of a deal i would say).
Since then however i am not able to boot it up .
I can get to twrp ,and there the temp is shown as 105°C i assume that due to this the termal protection of any system kicks in and doesnt boot up.
I checked other thermal zones and those show more reasonable temps around 35-45C
Do i have any option to turn off the check for that thermal zone to circumvent the problem ?
Related
Is there any way to configure SetCPU so it normally runs with the 'conservative' governor (the only one the Epic 4G apparently supports right now), but instantly kicks the CPU up to max and keeps it there whenever a soft keyboard (specifically, Graffiti) is active?
For anybody who's never tried it, Graffiti's accuracy is nearly perfect when the phone is in 'Performance' mode... and, er, a bit more... um... "variable and inconsistent" when it's not. The thing is, my battery life is getting totally nuked by keeping the phone in performance mode all the time.
For me, at least, kicking it to 100% whenever any soft input area is active (without worrying whether it's Graffiti or some other one) is more than good enough.
Failing that, is there a setting that translates to "Performance profile when the screen is on, Conservative profile when the screen is off" so it's at least not running full-bore when the phone is just sitting in my pocket or idle and dark on my desk?
Is there any speed-governor app for the Xoom that can be configured to lock the CPU to 1000MHz whenever the soft input area is active (or better yet, whenever Graffiti input is active), and/or a way to increase the digitizer sample rate?
Historically, Graffiti has been totally unusable on my Xoom. Literally, so low of a sample rate, and so many errors, that I just couldn't use it. I finally got around to unlocking and reflashing my Xoom to CM10 last night, and locking the CPU to 1000MHz makes it work a lot better... but the accuracy is still a cruel joke compared to even my creaky, old Hero overclocked to 711MHz.
It's pretty sad, actually. On the Hero, the digitizer seems to be reporting samples at least 4-16 times as often, and I can get nearly 100% accuracy without even trying. On the Xoom locked to max speed, it seems to do a tiny bit better than my S3 gets with stock, but the sample rate still appears to be absurdly low compared to what it was on the Hero, and feedback seems to lag the actual touch by at least 100-200ms. On the Hero, feedback was literally instant... stroke, and see the pixels turn white INSTANTLY under my fingertip. On the Xoom (locked to max), they start turning white a fraction of a second after I touch the screen, and I can see the last bit of the stroke render a fraction of a second after I lift my finger away. With the stock Xoom rom, it was more like, "draw the character, and see a jagged impression of it sputter into existence about a half-second later... maybe, MAYBE even getting recognized correctly about 70% of the time".
I'm guessing that either the Xoom's digitizer has a limited sample rate, or something in the kernel or driver is limiting the sample rate... but I'm still trying to find a straight answer somewhere about whether/how you can build a custom kernel without losing your ability to run paid Market apps. Or whether it's even necessary to go to that extreme, as opposed to something like a setting that tells Android to increase the sample rate, or not throttle the CPU when an input area is active, or maybe a way to let something like SetCPU identify "soft input area active" as a profile-triggering condition. I'm also pretty sure that the Xoom's kernel (if not recent versions of Android itself) try to treat the existence of a soft input area as an excuse to massively throttle the CPU, on the theory that it's just displaying a picture of a keyboard and waiting for a blunt press. HOWEVER, I'm SURE there HAS to be an equally-official way of defeating that behavior, if only because it would also screw up Android's ability to handle east Asian input methods.
hi,
Unfortunately I've got a well known problem with bootlooped LG G4. I was able to recover it from the bootloop, and switch off cores manually using standard linux shell:
echo "0" > /sys/devices/system/cpu/cpu4/online
echo "0" > /sys/devices/system/cpu/cpu5/online
I've backed-up all my data but I've noticed that my G4 works perfectly without "big" cores so I thought that maybe I can disable them during SoC configuration when the phone boots, so I can use ma mobile. I've tried to edit /etc/init.qcom.post_boot.sh in section for 8992 SoC and I've disabled lines: 791 and 828:
#echo "1" > /sys/devices/system/cpu/cpu4/online
#echo "1" > /sys/devices/system/cpu/cpu5/online
But it almost bricked my phone after reboot - It was just hanging up after LG welcome screen, no LED blinking...
Thankfully, somehow, it was able to boot with cpu4 on when battery was low (but of course bootlooped) so I was able to undo changes in /etc/init.qcom.post_boot.sh
Have you got any ideas how I can disable cores 4 & 5 during the boot?
I need the same.... I think modify a kernel could do that but i dont know who do it.
Did you find a solution?
no, but it was a temporary solution - my G4 worked like that for 2 months and then died completely, literally 2 days ago....
The solution to make it usable for 12h is to treat the SoC using hotair for 60 seconds @ 250°C and low air flow, or in the oven. You have to remove the motherboard - follow instructions on iFixit and the the metal cover on SoC (the biggest one). If you haven't got access to hotair gun, try to put motherboard in oven @ 200°C (not 250°C!) for 2 min, but you can damage it.
Then after it boots switch off big cores and upload your private data, make backups and buy new handy
In my opinion the hardware bug is quite trivial - the black protective paint around SoC is not covering it completely so the humidity and dust can go between BGA balls...
im reading a lot and trying learn how to edit a kernel on boot and early boot to get disable big cores like ilapo fix. My idea is modify a kernel and flash it by twrp.
I think that it can be possible and, surely a developer can resolve it easily. But well still i have no idea..
Use a hair dry or put the phone in the oven unfortunately it is not a lasting solution
Hey guys,
is it possible to disable the warning when the device gets too hot?
It is very annoying when I use my OP6 for navigation or music in my cabriolet and the screen brightness gets reduced so much, that I can't see anything or some apps get closed.
Thanks in advance
The warning is there for a reason. It is not a good idea to disable it, even if it were possible. Eventually the phone will shut off once it reaches a certain temperature to prevent damage to the battery and internal components
So, like every other thing out there, stuff fails. I woke up this morning and checked my phone to check the time. Nothing unusual. I go to get changed and I come back to my phone and it just shows the Verizon boot logo. I thought "Ok, it must have just crashed somehow and it'll reboot!" And so I waited...and waited....and waited. It seems to be half-booted, but stuck somewhere along the way. The screen is dimmed (indicating the auto-brightness feature is working) and it has the orange hue over the white text (indicating the night-light mode is still on). I had medium Power Saver mode on to keep the battery overnight, and the CPU cap was enabled. I've noticed that some apps don't like to start with that setting enabled, so I'm inclined to believe that the 70% CPU cap is somehow messing up the system and keeping it from fully rebooting. I'm currently waiting for the battery to die since I can't remove my battery in the Note 5. I've checked the device temperature by hand every now and then, and it doesn't feel warm so the CPU isn't cycling up like it should. I don't have access to my computer until I finish moving and unpacking my new house, so I can't use ADB to try and do anything. What should I do?
BluSpectre said:
So, like every other thing out there, stuff fails. I woke up this morning and checked my phone to check the time. Nothing unusual. I go to get changed and I come back to my phone and it just shows the Verizon boot logo. I thought "Ok, it must have just crashed somehow and it'll reboot!" And so I waited...and waited....and waited. It seems to be half-booted, but stuck somewhere along the way. The screen is dimmed (indicating the auto-brightness feature is working) and it has the orange hue over the white text (indicating the night-light mode is still on). I had medium Power Saver mode on to keep the battery overnight, and the CPU cap was enabled. I've noticed that some apps don't like to start with that setting enabled, so I'm inclined to believe that the 70% CPU cap is somehow messing up the system and keeping it from fully rebooting. I'm currently waiting for the battery to die since I can't remove my battery in the Note 5. I've checked the device temperature by hand every now and then, and it doesn't feel warm so the CPU isn't cycling up like it should. I don't have access to my computer until I finish moving and unpacking my new house, so I can't use ADB to try and do anything. What should I do?
Click to expand...
Click to collapse
Ok, so I fixed my own problem. I tried a variety of small post-boot tricks like trying to force the device into a different boot mode (ex: Power+minus=safe boot, power+home+VolDown= Download Mode) and forcing it into Download mode worked. It overrode the issue and I was able to tell it to reboot again. This time it rebooted normally. This was really weird. I've never had this happen before on any other device I've ever owned. I hope this might help someone in the future.