AS the title says, phone has become really slow. Previously had no problems.
I did change the CPU settings in ROM management toolbox which seems to me to be the culprit, i changed it back but the phone is still really slow at loading app icons on homescreen and in app drawer.
I have reset permissions, scanned for viruses, cleared cache, etc. But still slow.
Anyone an idea what to do besides boot into recovery and resinstall Marvel? or is that really the best way????
Cheers in advance.
spagbol said:
AS the title says, phone has become really slow. Previously had no problems.
I did change the CPU settings in ROM management toolbox which seems to me to be the culprit, i changed it back but the phone is still really slow at loading app icons on homescreen and in app drawer.
I have reset permissions, scanned for viruses, cleared cache, etc. But still slow.
Anyone an idea what to do besides boot into recovery and resinstall Marvel? or is that really the best way????
Click to expand...
Click to collapse
Did you want to try the Marvel 12 Beta?
http://www.androidfilehost.com/?fid=9390362690511177071
Install, do a factory reset, set the governor, and see if it does the trick.
I recommend installing the Xperia Launcher 2.05b. Hopefully Tantrums will be including this in v12 Final:
http://forum.xda-developers.com/showthread.php?t=2103403
Your issue may also be related to a specific app you've installed. I ran into issues with a particular app after an automatic upgrade, and it took me a while to figure out the culprit. I contacted the developer and he was quick to fix the issue, but this stuff does happen. Many times you can figure out what's going on by reading the "1-star" reviews for your installed apps on the Play Store. I would message the developer if you find something.
Cheers.
I was thinking of installing v12, but thought id wait until it was officially released.
I guess i will uninstall all apps, to see if it makes a difference, then if not i guess i will reinstall v11 for now.
Actually, thats just too slow, i will ust reinstall v11 ROM.
Thanks.
androcraze said:
Did you want to try the Marvel 12 Beta?
http://www.androidfilehost.com/?fid=9390362690511177071
Install, do a factory reset, set the governor, and see if it does the trick.
I recommend installing the Xperia Launcher 2.05b. Hopefully Tantrums will be including this in v12 Final:
http://forum.xda-developers.com/showthread.php?t=2103403
Your issue may also be related to a specific app you've installed. I ran into issues with a particular app after an automatic upgrade, and it took me a while to figure out the culprit. I contacted the developer and he was quick to fix the issue, but this stuff does happen. Many times you can figure out what's going on by reading the "1-star" reviews for your installed apps on the Play Store. I would message the developer if you find something.
Click to expand...
Click to collapse
spagbol said:
Anyone an idea what to do besides boot into recovery and resinstall Marvel? or is that really the best way????
Click to expand...
Click to collapse
If you are on Marvel11 and want to reinstall Marvel11 cause you want to change anything in the settings or just cause there did anything go wrong just reboot to recovery and start the Aroma install package of Marvel11 without any whippe at all, that's all, should fix everything.
Sent from my LG-P970 using xda app-developers app
Yea thats what i did. All was ok.
but then i started to clean up files on my phone. I think i deleted some files i should not have and now i have a phone that i cant enter into recovery mode. It just boots up and shows the coloured X from the X-peria bootloader (for some reason cos i didnt install it) asks for SIM unlock, which i do, but it only shows a handful of apps, standard ones i imagine, but no fast rebbot, or ROM toolbox, or CWM app. So then how do i now enter recovery??????
AHHHHHHHH!!!!! LOL
Ah i found a possible way out of this conundrum i found myself in i think
i had access to play store, so as i couldnt see ROM toolbox in apps, i redownloaded it so i could enter recovery mode.
So that i have done, now i just need to see what i have when the phone has rebooted, but i think that will have worked.
I think i must have deleted the data files or something when cleaning up the phone :/
Yea. looks like i have to reinstall all apps. No biggy then. Phew!!
Just a little reminder: If you use Windows 'adb reboot recovery' will do the trick too.
Sent from my LG-P970 using xda app-developers app
Yea, im on mac, so ncd.
OK so now my process.com android.mms keeps closing on me, effectively i have no MMS.
Anyone a solution?
I have reset Darvik Cache and normal cache. Fixed permissions. Uninstalled the app through ROM toolbox, then reinstalled the ROM. Still no joy,MMS just will not run.
Ideas?
Or should i just install Marvel v12?
spagbol said:
Or should i just install Marvel v12?
Click to expand...
Click to collapse
A fresh install with v12 Beta will take less time than you've already spent. Just have your additional apps (outside the Play Store) in a folder on the SD card.
androcraze said:
A fresh install with v12 Beta will take less time than you've already spent. Just have your additional apps (outside the Play Store) in a folder on the SD card.
Click to expand...
Click to collapse
Should i preform a factory reset as well? I ask because i am on Mac, so performing any procedures where i need to hook up the phone to a computer, although not impossible, is a bit of a task. Will installing Marvel v12 actually fix the issue in itself?????
I have actually installed Go SMS Pro and Handcent, which work in terms of being able to retrieve MMS, but it hasnt done anything to fix the stock/Optimus G MMS app.
Hehe, I should install Marvel 12 i know, I am just holding back a bit.
spagbol said:
Should i preform a factory reset as well? I ask because i am on Mac, so performing any procedures where i need to hook up the phone to a computer, although not impossible, is a bit of a task. Will installing Marvel v12 actually fix the issue in itself?????
I have actually installed Go SMS Pro and Handcent, which work in terms of being able to retrieve MMS, but it hasnt done anything to fix the stock/Optimus G MMS app.
Hehe, I should install Marvel 12 i know, I am just holding back a bit.
Click to expand...
Click to collapse
I do a full factory reset after any ROM install.
I use Go SMS too. I liked Pansi soooo much, but the last update continually crashes on my Marvel ICS.
Remind me please, if the full factory reset means i will need a PC to fix anything, or if i can perform a full factory reset and install either Marvel v11 or v12 without needing a computer?
spagbol said:
Remind me please, if the full factory reset means i will need a PC to fix anything, or if i can perform a full factory reset and install either Marvel v11 or v12 without needing a computer?
Click to expand...
Click to collapse
You install the ROM, then you do the factory reset.
The factory reset returns things to a raw ROM state, getting rid of anything you've added since installing the ROM. So yes, it will wipe anything you download from the Play Store. I do it immediately after installing the ROM.
Put Marvel 12 Beta on the SD card (root directory), and any non-Play Store items you'd like to install in a folder on the card.
Hello,
my stamina mode (4.3 Stock ROM, see signature) doesn't work properly anymore. Usually, network connections were disabled shortly after locking screen and by unlocking screen, network connections were established again (connection symbol needed 1-2 seconds to appear).
Now my connections do not get disabled anymore. I receive Whatsapp messages even after an hour of not using my device e.g. and the connection symbol is already there like the device was never disconnected.
I do not have any exceptions in my stamina settings. I had Whatsapp in there for testing purposes, but removed it. I've got the feeling that this problem exists since I've once tested the Whatsapp exception...
The first and easiest way is a factory reset of your phone before doing anything else.
Have you ever made a factory reset after switching from android 4.1.2 to 4.3?
I came from CM to 4.3; first the leak versionn, then .199 and finally .210 - each with full wipe. That should not be the problem; stamina mode worked properly on every stock 4.3. It is broken for only one or two weeks now.
Of course i could do a factory reset or a CWM backup from a clean 4.3 installation, but I hoped to solve it another way, e.g. reinstalling a certain APK or editing sth. in the system
dyfk3l said:
I came from CM to 4.3; first the leak versionn, then .199 and finally .210 - each with full wipe. That should not be the problem; stamina mode worked properly on every stock 4.3. It is broken for only one or two weeks now.
Of course i could do a factory reset or a CWM backup from a clean 4.3 installation, but I hoped to solve it another way, e.g. reinstalling a certain APK or editing sth. in the system
Click to expand...
Click to collapse
You can flash .210 again via recovery WITHOUT any wipe.
The zip file will format and install a clean system (with all original apk, framework and so on)
istux said:
You can flash .210 again via recovery WITHOUT any wipe.
The zip file will format and install a clean system (with all original apk, framework and so on)
Click to expand...
Click to collapse
I prefer original FTF files when using stock ROMs, so that I can customize it according to my taste.
To topic:
I've restored a CWM-backup of the fresh installed stock ROM, but same problem... strange. We'll, the best way should be reinstalling the whole ROM *grrrrrr*
Thanks anyway!
dyfk3l said:
I prefer original FTF files when using stock ROMs, so that I can customize it according to my taste.
To topic:
I've restored a CWM-backup of the fresh installed stock ROM, but same problem... strange. We'll, the best way should be reinstalling the whole ROM *grrrrrr*
Thanks anyway!
Click to expand...
Click to collapse
Good choice.
By the way also with Flashtool you can flash only the system this way: uncheck all inside wipe box and check all inside exclude box, but system that has to be unchecked.
Been a long time Venom user but recently decided to try Insertcoin due to unimpressive battery and overall phone slowdowns (none necessarily related to Venom).
I have noticed in the Kontrol, there are tweaks such as DPI, remove NFC logo, etc. They all request root access as they should, and when the restart is forced the settings absolutely refuse to save. I've tried a fresh install with both superuser and superSU, neither seems to make a difference.
What am I missing here?
---
Edit - side issue, the front camera has not worked for months either, with any rom. It doesn't even show up as selectable in apps. Physical damage?
Thanks
nonameguy321 said:
Been a long time Venom user but recently decided to try Insertcoin due to unimpressive battery and overall phone slowdowns (none necessarily related to Venom).
I have noticed in the Kontrol, there are tweaks such as DPI, remove NFC logo, etc. They all request root access as they should, and when the restart is forced the settings absolutely refuse to save. I've tried a fresh install with both superuser and superSU, neither seems to make a difference.
What am I missing here?
---
Edit - side issue, the front camera has not worked for months either, with any rom. It doesn't even show up as selectable in apps. Physical damage?
Thanks
Click to expand...
Click to collapse
Ensure you have the latest custom recovery and SuperSU; then perform a full wipe then re-install the rom. If that didn't work you might have to re-flash your stock firmware then flash your custom recovery and SuperSU.
385
majmoz said:
Ensure you have the latest custom recovery and SuperSU; then perform a full wipe then re-install the rom. If that didn't work you might have to re-flash your stock firmware then flash your custom recovery and SuperSU.
Click to expand...
Click to collapse
Everything is indeed up to date.
Why do you think going back to stock would help with the issue(s) I described?
nonameguy321 said:
Everything is indeed up to date.
Why do you think going back to stock would help with the issue(s) I described?
Click to expand...
Click to collapse
Oftentimes that is the only way to clear out residual data. The other thing you could try is to go back to other rom and see if it is corrected.
majmoz said:
Ensure you have the latest custom recovery and SuperSU; then perform a full wipe then re-install the rom. If that didn't work you might have to re-flash your stock firmware then flash your custom recovery and SuperSU.
Click to expand...
Click to collapse
majmoz said:
Oftentimes that is the only way to clear out residual data. The other thing you could try is to go back to other rom and see if it is corrected.
Click to expand...
Click to collapse
Maybe I should have left out the part of the front facing camera not working.. or created that as a separate topic.
The one that I'm really having issue with is the Insertcoin Konfig settings not actually applying themselves.. tweaks on other ROMs worked without a problem..
Hello, I do have a problem with my front camera. When trying to switch to the front camera within any camera app, the app freezes. I do not know when the problem started, but I noticed first on OOS 4.1.3. At first I thought it had to do with the custom kernel or some Magix mods. Because of that, I clean installed OOS 4.1.6 and only installed Magix (no mods, no kernel). The problem is still there. Does anyone know how to solve this problem? Or is it a hardware issue and I should send the phone to repair?
My specs in short:
OnePlus 3t (64gb Rom)
OOS 4.1.6
Magix v12
Stock kernel
Thank you in advance
At first, try just to clear app data for camera app/gallery app and see if that helps. Else you should do a factory restore of phone to see if problem still persist, in that case it's probably hardware fault.
pitrus- said:
At first, try just to clear app data for camera app/gallery app and see if that helps. Else you should do a factory restore of phone to see if problem still persist, in that case it's probably hardware fault.
Click to expand...
Click to collapse
Thank you for the answer, I tried to use different camera apps (stock app, opencamera, snapdragon camera), they all crashed when trying to use the front camera.
I already did a factory reset when clean installing the newest OOS.
I really hope, this isn't a hardware fault. The "Phone tester" app shows the camera features as it should.
Could there be a problem with TWRP flashing the roms making a mistake? TWRP didn't show an error through. I am on TWRP 3.1.0-1
There could be something wrong in the persistent partition causing this, reflashing factory persist.img to partition might fix it (easy way is to use qualcomm restore method which restores everything).
Thank you, I will try it next weekend, when I am back home ?
It started to happen to my phone after I flashed only system.img to my rooted phone, tried to get the phone back to stock like some sort of a shortcut, to try to get OTA update.
I did not recognize it right away, but it started to happen from time to time and in all random occasions.
The phone will literally freeze for about 5-10sec and then everything will go back to normal.
The standard android message will appear that app is not responding do I want to kill it or wait.
I flashed the whole phone with stock images, temporarily rooted the phone again to enable camera2, uninstalled root, and it still happens from time to time.
Any suggestions, what can I do, what to check, where to look ?
I had kernel "Kernel Adiutor (ROOT)" previously installed, but I changed nothing major, just cpu governor to ondemand, and messed a little bit with entropy. This was installed on the phone before flashing.
minnuss said:
It started to happen to my phone after I flashed only system.img to my rooted phone, tried to get the phone back to stock like some sort of a shortcut, to try to get OTA update.
I did not recognize it right away, but it started to happen from time to time and in all random occasions.
The phone will literally freeze for about 5-10sec and then everything will go back to normal.
The standard android message will appear that app is not responding do I want to kill it or wait.
I flashed the whole phone with stock images, temporarily rooted the phone again to enable camera2, uninstalled root, and it still happens from time to time.
Any suggestions, what can I do, what to check, where to look ?
I had kernel "Kernel Adiutor (ROOT)" previously installed, but I changed nothing major, just cpu governor to ondemand, and messed a little bit with entropy. This was installed on the phone before flashing.
Click to expand...
Click to collapse
You may want to clean the dalvik-cache first. (Install TWRP and clean it from there) the system is storing tons of thing in there, and *for my case* wiping it was like a deliverance ?
minnuss said:
It started to happen to my phone after I flashed only system.img to my rooted phone, tried to get the phone back to stock like some sort of a shortcut, to try to get OTA update.
I did not recognize it right away, but it started to happen from time to time and in all random occasions.
The phone will literally freeze for about 5-10sec and then everything will go back to normal.
The standard android message will appear that app is not responding do I want to kill it or wait.
I flashed the whole phone with stock images, temporarily rooted the phone again to enable camera2, uninstalled root, and it still happens from time to time.
Any suggestions, what can I do, what to check, where to look ?
I had kernel "Kernel Adiutor (ROOT)" previously installed, but I changed nothing major, just cpu governor to ondemand, and messed a little bit with entropy. This was installed on the phone before flashing.
Click to expand...
Click to collapse
Is the phone writing big files to the disk like an automatic Backup? That's when my phone becomes unresponsive..
dodjob said:
You may want to clean the dalvik-cache first. (Install TWRP and clean it from there) the system is storing tons of thing in there, and *for my case* wiping it was like a deliverance
Click to expand...
Click to collapse
Hmm, i will try this when I get home from work, thanx.
Benjamin_L said:
Is the phone writing big files to the disk like an automatic Backup? That's when my phone becomes unresponsive..
Click to expand...
Click to collapse
No custom installed auto backup aps, only default Android syncs.
I think that it has to do something with the kernel, or something deeper then stock images, maybe dodjob is right, I will try with dalvik erase, and if I remember correctly twrp has another option to clean something else, will check it today...
Is there a way to flash default stock kernel again ?
minnuss said:
Hmm, i will try this when I get home from work, thanx.
No custom installed auto backup aps, only default Android syncs.
I think that it has to do something with the kernel, or something deeper then stock images, maybe dodjob is right, I will try with dalvik erase, and if I remember correctly twrp has another option to clean something else, will check it today...
Is there a way to flash default stock kernel again ?
Click to expand...
Click to collapse
Let us know!
dodjob said:
Let us know!
Click to expand...
Click to collapse
Nope, it did not work, freeze remains.
Now I need to check what Benjamin said, about internal storage, format system, and do all over again, but now without restoring backup, starting with fresh droid install.
minnuss said:
Nope, it did not work, freeze remains.
Now I need to check what Benjamin said, about internal storage, format system, and do all over again, but now without restoring backup, starting with fresh droid install.
Click to expand...
Click to collapse
That sucks big time ? the only time I got a freeze was as I wanted to empty chrome beta cache. After the reboot, all went back as it should be...
I did it, finally, flashed all images again stock, and then don't restored backup of the phone offered by google, but do the clean new phone installation.
It works now, everything is setup and works as it should be, except camera2api, I did not enable that one yet.
Maybe, just maybe, the problem was with the way how camera2 api was enabled, I did it via adb shell.
How did you guys did it, if you have it enabled ?
This has started to happen to me since yesterday. I've had the phone to a couple of weeks and it's completely stock and un rooted. I rebooted the phone last night cause I thought it was some ram issue but it remains today. I'll give it a few days and hope it fixes itself.
minnuss said:
I did it, finally, flashed all images again stock, and then don't restored backup of the phone offered by google, but do the clean new phone installation.
It works now, everything is setup and works as it should be, except camera2api, I did not enable that one yet.
Maybe, just maybe, the problem was with the way how camera2 api was enabled, I did it via adb shell.
How did you guys did it, if you have it enabled ?
Click to expand...
Click to collapse
Adb root shell. Can't think of a way this could damage anything if you just set the one property
hacktek said:
This has started to happen to me since yesterday. I've had the phone to a couple of weeks and it's completely stock and un rooted. I rebooted the phone last night cause I thought it was some ram issue but it remains today. I'll give it a few days and hope it fixes itself.
Click to expand...
Click to collapse
Did you have device rooted for a while, or it was always stock ?
Benjamin_L said:
Adb root shell. Can't think of a way this could damage anything if you just set the one property
Click to expand...
Click to collapse
Thanx, I needed that confirmation, then my problem was probably caused by some application that wanted to take root actions, without root enabled, and causing havoc to the system, because I was restoring backup last two times, backup from rooted phone.
I had rooted phone, then flashed only system.img, then the problem started, I don't know...
I will use the phone tomorrow for work without camera2, to make sure that I don't have any more problems.
minnuss said:
Did you have device rooted for a while, or it was always stock ?
Thanx, I needed that confirmation, then my problem was probably caused by some application that wanted to take root actions, without root enabled, and causing havoc to the system, because I was restoring backup last two times, backup from rooted phone.
I had rooted phone, then flashed only system.img, then the problem started, I don't know...
I will use the phone tomorrow for work without camera2, to make sure that I don't have any more problems.
Click to expand...
Click to collapse
It's always been stock.
I had never rooted this phone and I am on September security patch, from September 6th, but for 2 days, 1-2 times a day I get some freeeze for 1-3 minutes. Today I tried to clear manually the cache from Facebook, and it took me 1 minute after I click the button "Clear cache". And then I got everything freezing. After a black screen for 10 seconds I got an error as you can see in the screenshot attached. I will repeat, never touched the phone's system. Does anybody meet this problem???
kaiwanted said:
I had never rooted this phone and I am on September security patch, from September 6th, but for 2 days, 1-2 times a day I get some freeeze for 1-3 minutes. Today I tried to clear manually the cache from Facebook, and it took me 1 minute after I click the button "Clear cache". And then I got everything freezing. After a black screen for 10 seconds I got an error as you can see in the screenshot attached. I will repeat, never touched the phone's system. Does anybody meet this problem???
Click to expand...
Click to collapse
Yes this happens when lots of I/o is done on the internal disk. I hope this is just a missing optimization and not a hardware issue. But let's bug xiaomi with it. I assume you also have the 64GB version?
@kaiwanted, I had that, but not 2 times per day, but almost constantly and the stops were about 10-15 sec, not for a whole minutes.
Clean flash, clean new start a phone procedure when the phone boots, no restores of backup.
And erased Dalvik cache in TWRP.
Or, if you don't want to do this, try with uninstalling all unnecessary apps that you have in the phone, try the day use with minimum, to see what happens.
minnuss said:
@kaiwanted, I had that, but not 2 times per day, but almost constantly and the stops were about 10-15 sec, not for a whole minutes.
Clean flash, clean new start a phone procedure when the phone boots, no restores of backup.
And erased Dalvik cache in TWRP.
Or, if you don't want to do this, try with uninstalling all unnecessary apps that you have in the phone, try the day use with minimum, to see what happens.
Click to expand...
Click to collapse
I read a lot regarding how people brick their phone with TWRP and rooting, so for now I will not use this future. But to reset my phone I will think about. Anyway I need this phone to use all my applications, not only a couple of them, because of this freezing (.
Thanks for suggestions.
minnuss said:
@kaiwanted, I had that, but not 2 times per day, but almost constantly and the stops were about 10-15 sec, not for a whole minutes.
Clean flash, clean new start a phone procedure when the phone boots, no restores of backup.
And erased Dalvik cache in TWRP.
Or, if you don't want to do this, try with uninstalling all unnecessary apps that you have in the phone, try the day use with minimum, to see what happens.
Click to expand...
Click to collapse
So I uninstalled about 5-6 applications and freeze disappear. From which I remember, I uninstalled: Spendee, XDA Dev app, Zugo Wallpapers etc.
Still when I clear the cache manually from Applications in settings, it takes about a minute or more to clean 100-500mb. This is weird.
Anyway, thank you for the suggestion.
kaiwanted said:
So I uninstalled about 5-6 applications and freeze disappear. From which I remember, I uninstalled: Spendee, XDA Dev app, Zugo Wallpapers etc.
Still when I clear the cache manually from Applications in settings, it takes about a minute or more to clean 100-500mb. This is weird.
Anyway, thank you for the suggestion.
Click to expand...
Click to collapse
I did the same thing. Went through my application list, uninstalled everything I didn't need and the issue went away. I cleared like 5% of storage space with still over 50% left but it seems to have helped.
reflashed all stock, enabled camera 2 api using mi a2 toolkit (magisk method) and I have the same. Cleared everything and run flash_all.bat. enable cam 2 api again and still have the same issue. clean install of apps doesn't fix it. Any idea on how to fix the sudden freeze?
Thanks
---------- Post added at 07:52 PM ---------- Previous post was at 07:28 PM ----------
if I completely root the device, I will still have the random freeze?
also, if I factory reset the device in the settings, the camera 2 api will be gone? thanks
minnuss said:
Maybe, just maybe, the problem was with the way how camera2 api was enabled, I did it via adb shell.
How did you guys did it, if you have it enabled ?
Click to expand...
Click to collapse
I did it via twrp and adb shell setprop persist...
No issues here at all.