Root [LINARO] AWEstruck v1.04 12/14/14 | [3.4.107] v1.05b6 5/30/15

[edodson84]

Benches good will post back if reboot and about battery usage

 

[androidfanwinner]

Here is my last_kmsg. I had been oc'd for hours. The phone was not hot. I played a game for about 45 minutes and the phone was getting hot. Eventually it rebooted. This is with the regular 1.02 linaro.

 

[edodson84]

https://www.dropbox.com/s/7eiwfhfqnf6a7i4/last_kmsg.txt

Just had a reboot using maps at full clock 1.02 no mp

 

[spock1104]

Ya know, and just when I thought that I'd be able to release my gpu OC code... Who wants a 627MHz gpu? Well stop crashing the phone!

androidfanwinner, looks like you also hit an issue with mpdecision moving too quickly. can you switch to the no_mp kernel please?

brittnearl, I think you overheated. There's no kernel panic, but there is this just before the reboot:
[06-03 03:16:00.340] [0][22486: kworker/0:0]POWER_SUPPLY_HEALTH=Overheat

Thanks guys, appreciate the data, keep it coming!

 

[edodson84]

Ya know, and just when I thought that I'd be able to release my gpu OC code... Who wants a 627MHz gpu? Well stop crashing the phone!

androidfanwinner, looks like you also hit an issue with mpdecision moving too quickly. can you switch to the nomp kernel please?

brittnearl, I think you overheated. There's no kernel panic, but there is this just before the reboot:
[06-03 03:16:00.340] [0][22486: kworker/0:0]POWER_SUPPLY_HEALTH=Overheat

Thanks guys, appreciate the data, keep it coming!

Kool I will bump down to 1.5 and c how it goes

 

[edodson84]

U have a build with the GPU oc

 

[spock1104]

Let's get through the testing of this first, the GPU OC is in a local branch that doesn't have mpdecision removed. What I'm most interested is if the no_mp kernel will boot on Starkraving's phone.

 

[edodson84]

Let's get through the testing of this first, the GPU OC is in a local branch that doesn't have mpdecision removed. What I'm most interested is if the no_mp kernel will boot on Starkraving's phone.

Yeah I guess we shouldn't count our chickens before they are hatched lol

 

[spock1104]

My phone is claiming it hit 0.5%/h (no typo) last night.

 

[edodson84]

https://www.dropbox.com/s/7eiwfhfqnf6a7i4/last_kmsg.txt

Just had a reboot by waking with power button, I looked at log myself and shows same overheat?? No way I was over heating just picked up phone from a fresh reboot

 

[edodson84]

Could overheat temps be set too low??

 

[spock1104]

Could overheat temps be set too low??

This is ZTE we're taking about, anything is possible.

 

[edodson84]

This is ZTE we're taking about, anything is possible.

U should start editing their ui and framework lol its all coded and recoded over, we already know its redundant source code they probably changed it on ROM included kernel

 

[spock1104]

To help diagnose, would you be willing to use the curvefish battery life widget? I use it to track my battery temperature, and I'm interested in what your actual temps show up as.

I have seen one legit overheat on my wife's phone where it hit 120 degrees Fahrenheit while charging.

 

[androidfanwinner]

Spock1104, here is the last_kmsg from the no_mp kernel.

 

[edodson84]

Reboot at 99

 

[starkraving]

I'm having zero luck with any of the kernels at this point. The goggle build was stable for a couple hours then started getting multiple and immediate reboots. Will get you a kmsg as soon as I get a chance. I've been testing "something" for someone else for the past few days.

 

[jimsmith80]

I've got an oc table that runs up to 1.7 for the warplte on git hub. Pull the acpuclock-8930.c from it and there you go. I currently limit the device to 1.5.

 

[edodson84]

I've got an oc table that runs up to 1.7 for the warplte on git hub. Pull the acpuclock-8930.c from it and there you go. I currently limit the device to 1.5.

Will it solve the fake overheat??

 

[edodson84]

Just to inform charging batt temp went up to about 105

 

[jimsmith80]

Will it solve the fake overheat??

Honestly not sure, but sharing info across devices saves us all time.

 

[edodson84]

https://www.dropbox.com/s/i2wf6sjh1zook57/dmesg.txt

https://www.dropbox.com/s/7eiwfhfqnf6a7i4/last_kmsg.txt

I have had a couple deep sleep issues and had to pull batt?? At least that's what I think it is. Pulled logs after reboot as device was not recognized

 

[spock1104]

Honestly not sure, but sharing info across devices saves us all time.

Thanks for the info! What were your sources on values? Differences between our files are what i assume are multipliers, fsb, and voltage. I had to resort to previous work on the 8930aa and 8930ab to arrive at my values.

brittnearl - there's the potential to lower the heat output due to lower voltages but this won't have any effect on the false overheat, that's stock ZTE code. I'll have to do some digging, likely this weekend.

 

[spock1104]

https://www.dropbox.com/s/i2wf6sjh1zook57/dmesg.txt

https://www.dropbox.com/s/7eiwfhfqnf6a7i4/last_kmsg.txt

I have had a couple deep sleep issues and had to pull batt?? At least that's what I think it is. Pulled logs after reboot as device was not recognized

No crash info that time, thanks though!

 

[spock1104]

Spock1104, here is the last_kmsg from the no_mp kernel.

some hints of the voltage regulator not being happy when applying a voltage. I'll generate a kernel with values based on jimsmith80's code and we can see if that works out better.