Hi guys, I am so happy that the Zenfone finally have root solutions & Xposed. But the problem is, if I try use boost mode + Xposed, my phone keep on freezing and reboot. Is there anyway to solve that? Else that's pretty waste if unable to use boost mode.
Is it probably x86 CPU limitation?
soralz said:
Hi guys, I am so happy that the Zenfone finally have root solutions & Xposed. But the problem is, if I try use boost mode + Xposed, my phone keep on freezing and reboot. Is there anyway to solve that? Else that's pretty waste if unable to use boost mode.
Is it probably x86 CPU limitation?
Click to expand...
Click to collapse
Root mode is equal in functionality to boost mode. So till your issue gets sorted out, use root mode.
Related
Hello everyone,
I have a problem with my Optimos One, when I reboot my mobile phone it always enters in Emergency Mode. If I remove my battery for ~2 minutes it boots normally again.
I dunno what the cause might be. I'm using a custom rom (ICS 4.0.3 by lupohirp) but I experienced this with other roms in the past.
Does anyone know what the problem might be and how to fix it?
Thanks!
Not long after I enabled the power saving mode on my S2 the device suddenly shutdown (while in my pocket, battery around 60% full) and couldn't turn on again. After 2 days the S2 suddenly booted again but still won't start up all the time when I want to.
My S2 device never had this issue before (I know it is a well known issue but apparently it should have been fixed in JB?)
Software I use:
- Apolo 4.12 kernel (Regular)
- Neatrom Lite
I am thinking of either hardware starting to fail or maybe the Apolo kernel has a bug that was triggered by enabling the powersafe mode?
I am not sure, anyone that can help/advise me?
It's probably a software issue, JB has tons of bugs. What kinda advise do you want? You need to re-install the rom (and clear cache ofc) and if that doesn't work re-install the stock rom via odin and then install neatrom if you want. And just don't use power save mode until you get an update? It's useless anyway... You can also try another kernel, this seems like a kernel problem.
Power saving actually just have a few advantages like turning of un-needed things like haptic feedback and some other stuff which you could do manually, and the main power saving feature is that it limits the CPU to use only 800Mhz max, this might be having some issues with Apollo kernel (as it works fine with stock or stock based kernel like Philz), but Apollo is a powerful kernel and will let you manually adjust the CPU limits even at your preferred limits manually, so if you want to save battery just manually adjust the settings instead of using Power Saving mode.
Sent from my GT-I9100 using Tapatalk
Perphide said:
Not long after I enabled the power saving mode on my S2 the device suddenly shutdown (while in my pocket, battery around 60% full) and couldn't turn on again. After 2 days the S2 suddenly booted again but still won't start up all the time when I want to.
My S2 device never had this issue before (I know it is a well known issue but apparently it should have been fixed in JB?)
Software I use:
- Apolo 4.12 kernel (Regular)
- Neatrom Lite
I am thinking of either hardware starting to fail or maybe the Apolo kernel has a bug that was triggered by enabling the powersafe mode?
I am not sure, anyone that can help/advise me?
Click to expand...
Click to collapse
It may be a bug in that rom. try another rom
Thank you!
Thank all of you for the help and advise!
I will no longer use the powersafe feature and start using the Apolo kernel again, since that kernel gave me the best battery life.
It might have been a coincidence of course that my S2 died/didn't want to start up no more shortly after using the powersafe feature... however from all of the above advise it seems that I don't need that feature anyway so I feel safe to switch back to the Apolo kernel again with my new installed NeatROM SuperLite 2.4.
If the problem returns I'll be here to post it, it might still be a bug in the Apolo kernel of the NeatROM ... I am not sure. Time will tell, or not if it had to do with the powersafe feature which I won't be using any more.
Thank you all!
Hi everyone, I have a problem with the bluetooth of my acer liquid e1 (chipset mtk6577), with android 4.1.1.. Since a few days ago I can’t anymore use it. Explaining better: when I try to switch on Bluetooth, the toggle immediately comes back to off. The strange thing is that I didn’t install anything new since the last time bluetooth worked. I’ve already tried to delete the application data of the bluetooth app. I also tried to replace MtkBt.apk file in the /system/app folder with some apk found over internet. I used root explorer to do it. Is there anything else I can try? Consider that this problem started without any relevant change in the configuration of the phone.
Thanks a lot
No one of you can help me?
Up
Up
I tried restarting in safe mode, and then happened a very strange thing: restarting normally after the restart in safe mode, bluetooth worked. But then, after another restart, it didn't work again. Restarting again in safe mode isn't useful. I can't anymore activate it using the safe mode. Any solution?
Hi,
I have had my phone in a bootloop for the last week where I could not access download mode. However, I finally managed to flash stock firmware 4.2.2. It booted up fully and I thought it was all solved when... it started crashing and getting into a bootloop which would be fixed by removing and reinserting the battery.
What I noticed when I went into settings and looked at running apps, was that I was using 0.95gb-1gb of the phones 10GB of RAM!!!!!! Obviously this is not the real amount of the i9300's ram (which is 1GB).
I am now suspecting that I have some sort of problem with my Kernel....?? I am also guessing that the crashes and bootloops come from the phone trying to access an amount of ram which it thinks it has, but is simply not there.
Currently I am in a bootloop where I can access recovery (CWM) for a second and it immediately crashes and reboots. Same for download mode.
Any help is appreciated. I've not found any, but if you happen to know of any other thread which solved this problem, please link. Thanks in advanced.
alexdelrio7 said:
Hi,
I have had my phone in a bootloop for the last week where I could not access download mode. However, I finally managed to flash stock firmware 4.2.2. It booted up fully and I thought it was all solved when... it started crashing and getting into a bootloop which would be fixed by removing and reinserting the battery.
What I noticed when I went into settings and looked at running apps, was that I was using 0.95gb-1gb of the phones 10GB of RAM!!!!!! Obviously this is not the real amount of the i9300's ram (which is 1GB).
I am now suspecting that I have some sort of problem with my Kernel....?? I am also guessing that the crashes and bootloops come from the phone trying to access an amount of ram which it thinks it has, but is simply not there.
Currently I am in a bootloop where I can access recovery (CWM) for a second and it immediately crashes and reboots. Same for download mode.
Any help is appreciated. I've not found any, but if you happen to know of any other thread which solved this problem, please link. Thanks in advanced.
Click to expand...
Click to collapse
Flash 4.3 or 4.4 if available and use optiin nand erase all in odin with pit file and repartition
Hi All,
I had some issues with the Tab S3 being stuck in a typical reboot loop. I managed to enter Odin Mode and Flash the Firemware via samfw.com and Odin Tool.
The Tablet installed the new firmware and then starts the usual setup mode. The tablet is REALLY slow and hangs up when I hit 'next/skip' etc. for terms and conditions, join WIFI network etc.
Then it just crashes and reboots. Sometimes it gets stuck on the device unlock screen when I try to enter pattern, sometimes it allows me to enter the pattern and restart the 'first time setup' process' only for it to fail again.
It's as if the CPU (or something else) is working too hard and glitches out and restarts the tablet.
I'm really not sure what else to do, anyone else had any similar issues to this?
EDIT: I managed to complete the first time setup wizard. Now it boots to the home screen. I can scroll a little to the apps, but when I try to do anything like open settings or an app, it just reboots....
johnsmithtetley said:
......
I'm really not sure what else to do, anyone else had any similar issues to this?
Click to expand...
Click to collapse
Not when on LOS19.1.
Stock ROM behaviour is to long ago.
johnsmithtetley said:
EDIT: I managed to complete the first time setup wizard. Now it boots to the home screen. I can scroll a little to the apps, but when I try to do anything like open settings or an app, it just reboots....
Click to expand...
Click to collapse
Is there a chance to install "cool tool statistics"?
This app I use on all devices.
It shows in the statusbar CPU load and frequency plus many other things and you can monitor that second steps.
Standard is every 2 secs.