RK3066 AMPE A86 Frequent Freeze - Android Q&A, Help & Troubleshooting

I have a Tablet: AMPE A86 with following details:
Android Version: 4.1.1
Kernel version: 3.0.8+
My tab has a bad issue of frequent freezing and reboots. After searching for several months I found that, it has issue in it's kernel (or something like that) and CPU. I have used SetCPU and setting the governor "Performance" solves the freezing issue and works smoothly (No more freeze and reboots). Other governor setting cannot stop the frequent freeze issue. but problem is that setting the governor "Performance" it become too hot and drains the battery too fast. I have used "Profile" menu to control the heat like below:
Screen Off
CPU 1608-252, Governor powersave
Priority 100,Exclusive
Charging Any
CPU 1608-252, Governor performance
Priority 95, Exclusive
Battery <=35%
CPU 1608-252, Governor powersave
Priority 90,Exclusive
But it does not reduce the heating issue still in Screen off. Another thing is that, in my tablet it does not identify the Temperature of the CPU (always shows 0.0 C).
Can someone help to to resolve my issue as I am suffering with this tab for last 1 year. I also have tried the Oma's CM10.1 and AOSP 4.2.2 with no luck. Can anyone provide me any better kernel or any solution for my problem?

Related

My mini pro reboots by itself!! :-(

hello to everyone. I have a problem with my device. When I am running apps such as facebook, after 5 minutes of usage or after 10 15 minutes, the screen freezes, I cant press anything and after 8-10 seconds the phone reboots by itself:-(. I cant find the reason. Here are my device settings
CPU Settings:
Governors: ONDEMAND
Min CPU Freq: 122 MHz
Max CPU Freq: 691 MHz (i was using 729 I thought reducing this one, would fix my problem.)
About my phone:
Kernel Version: 2. 6. 29. [email protected] 1
Mod Version: Froyo MiniCM/CMv6 Hybrid by slade87 and owain94. v6.0
Where is the problem???
any background apps running?
you are using really outdated rom, probably you will have better overclocking possibilities with newer roms and kernels.
and try returning to default cpu values and see if it reboots.

[Q] SetCpu overwrited after few seconds on Xperia Go

Hi,
on my Xperia Go which has ICS and is Rooted. I installed Antutu CPU, Voltage Control, SetCpu and everyone of them doesn't seem to work.
The problem is this. When i change minimal frequency to 400MHz, aply this change and press home button. Then for a while (like 30sec) everything is ok. But after this time something overwrites the changed settings of those programs and it is again on default 200-1000MHz.
For getting information about actual Frequency usage i use "CPU Spy".
FYI i didn't use more then one of those programs at the same time. Just saying, that i tried more than one
What do you think could be the problem?
Am i doing something wrong?
Dunno if it'll help, but there is some info about my phone.
Model: Xperia Go (ST27i)
Android version: 4.0.4
Kernel version 3.0.8+
Build number: 6.1.1.B.1.10
Rooted with http://forum.xda-developers.com/showthread.php?t=1886460 version 12
SetCpu from http://forum.xda-developers.com/showthread.php?t=505419 latest version
Thanks!
I have pretty much the same setup and the same problem (only tested SetCPU, though).
Any changes to the frequencies are reset to 200-1000 after a short while, no matter if set by hand or profile. The only thing that works is specifying the 'Performance' governor to keep the frequency at 1000 all the time. Which, admittedly, is still better than having to use this phone with the remarkably sluggish default settings but takes its toll on the battery life.
Long story short: A bump for this topic in hope to find a solution to this...

[Q] Using Setcpu on razr xt910.

Hi all,
I couldn't find the relevant information anywhere else, so thought I should ask if someone has experienced this.
Well I'm using setcpu on my razr and it is quite a brilliant app to be honest, helps me save battery quite alot by setting up profiles.
But recently I've been having crashing problems with the phone whenever i set the scaling to hotplug.
Previously, i was just using the default scaling, I guess Interactive it was, and was working quite happily. And, then i read about advantages of using Hotplug scaling, that it enables/disables cores depending on the amount of load on the cpu, which is really good for saving battery.
And before how I was using the phone, was to set a profile for screen off to drop the cpu down to 300MHz, using the default scaling.
But as soon as I changed from default scaling to Hotplug, it starts crashing randomly, and I've to restart the phone using keys.
Scenarios tried:
- Main scaling: Hotplug -- Screen off scaling: Interactive, Ondemand, Performance, Hotplug -- Processor Max: 300MHz
Result: crashing as soon as u turn the screen on, or sometimes while the screen is off.
- Main scaling: Hotplug -- Screen off scaling: Interactive, Ondemand, Performance, Hotplug -- Processor Max: 600MHz
Result: crashing as soon as u turn the screen on, or sometimes while the screen is off.
- Main scaling: Interactive -- Screen off scaling: Hotplug -- Processor Max: 300MHz
Result: In process of checking, hasn't crashed yet for more than an hour. :fingers-crossed:
Can someone kindly point out the obvious mistake I'm making here?
I really want to use hotplug, both as main and screen off.
FYI: I haven't done anything else to the phone apart from gaining root access.
i had issues with setcpu, i recommend no frills cpu control, and setting it down that low more then likely is also an issue, the second core i couldn't see turning off at a low clock and also i think it would max out easily causing instability (especially ICS) and above id say. uninstall setcpu give no frills a try and let me know would be glad to help with what i can!
Thanks for ur reply, yes I'll try no frills, but
mr4r4n said:
setting it down that low more then likely is also an issue
Click to expand...
Click to collapse
I thought the same, but while i was using interactive scaling, it worked perfectly, no issues at all. Probably because both cores were active by default, so both on 300MHz when screen was off.
mr4r4n said:
the second core i couldn't see turning off at a low clock and also i think it would max out easily causing instability (especially ICS)
Click to expand...
Click to collapse
No, I've checked cpu usage visa adb shell, and if the screen off is in hotplug, like what it is right now, the phone stays at 300MHz with the second core turned off, most of the time. And the phone has been running now for more than 3hrs with screen off profile set to Scaling: hotplug -- Max: 300MHz, and the main scaling set to Interactive.
The problem I've seen is, when main scaling is set to hotplug. Doesn't matter whatever u set in screen off profile, it crashes if the main scaling is set to hotplug. But, if no screen off profile is set then, hotplug in main works flawlessly.
That's weird. I've been using SetCPU for a year or so on my RAZR GB/ICS and never encountered any crashes with hotplug or the default ICS's interactive.
I have even tried unofficial governers like smartass2, boostedassv2 and etc, no crashes.
I personally set my phone to use u/c 200-200 for screen off and I find it really saves a lot of battery, and even o/c to 200-1300 when it's on.
Are you using the setcpu from xda or from playstore? I'm using the one from playstore with Razr asia ICS.
Nikorasu said:
That's weird. I've been using SetCPU for a year or so on my RAZR GB/ICS and never encountered any crashes with hotplug or the default ICS's interactive.
I have even tried unofficial governers like smartass2, boostedassv2 and etc, no crashes.
I personally set my phone to use u/c 200-200 for screen off and I find it really saves a lot of battery, and even o/c to 200-1300 when it's on.
Are you using the setcpu from xda or from playstore? I'm using the one from playstore with Razr asia ICS.
Click to expand...
Click to collapse
I think I downloaded it from here.
But I think, they both are the same, from same developer
hsyasin said:
I think I downloaded it from here.
But I think, they both are the same, from same developer
Click to expand...
Click to collapse
This means that you're using an old July 2011 version.
Do make use of playstore's 15 min return policy to test the newer ver. Maybe it will solve your problem.

Phone slow after idle - how to setup governor

I have a rooted honor 5x with cm13. When I go to kernel adiutor and make sure all cores are running the phone is fast. after being idle it starts to be unresponsive but than gets better I think. I use interactive governor for both types of cores but can not change governor settings on little. How can I eliminate the lagging after idle? I have default governor settings. Is there a bnchmarking app which can set optimal settings?

Phone faster when touchscreen pressed.

Hello! I have an a32 5g and when I run intensive apps like emulators such as dolphin mmj and aethersx2, I can clearly see a drastic increase in performance when my finger are on the touchscreen. How can I ensure that my phone is running this fast all the time?
It's caused by "input booster", likely forcing CPU Freq at max_freq.
Try to tune CPU governor, e.g. set lower value for up_threshold.
Or you can use performance governor, but this will use max_freq all the time, draining battery very fast, except in deep sleep state of course.
I found Franco Kernel Manager and already have per app profiles set up to change when aether or dolphin launches. Thanks again!
*Completely fixed the problem btw!

Categories

Resources