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,
I here made some terrible mistake with my Galaxy note3.
I rooted my device and then installed busybox on rails.
Then I installed layer manager.
Then installed theme from Google Play!
applied the theme and then reboot.
Now as my phone reboot.
I saw that now google play is not working it crashes everytime I install any app. Theme is very ugly.
Now as I open the layer manager to remove the theme I saw that it crashes again and again ..... everytime.
Their seems no hope, how I can remove this f****** theme from my device.
I would appriciate any help.
please suggest an alternative approach than flashing stock rom via odin!!!
Sent from my F1f using Tapatalk
Would a factory reset help?
audit13 said:
Would a factory reset help?
Click to expand...
Click to collapse
there was no way to reset rooted samsung note devices. So I flashed the stock rom.(which was the last option)
Sent from my SM-T231 using Tapatalk
Hi everyone, I have have a big trouble with my note 8.
I did a update today because Samsung was proposing that to me
After the update, I have a error message about system ui and I can do nothing with my phone.
Not rooted, nothing is modified in my phone. I have only installed substratum with swift black theme but not rooted.
I think it's because of this.
Someone can help me please, the secured mode change Nothing.
Help please
Substratum is probably your problem. I ended up doing a hard reset but I think I read that if you can get into safe boot, you can delete Substratum from there.
If you go the hard reset method, don't recover your apps with backup. You'll just drag the problem back.
Epic my Note was already loosing the ability to open apps and once I updated I could not get the phone to open just do a hard reset and everything will go back to normal mine is running great
Zarancar said:
Hi everyone, I have have a big trouble with my note 8.
I did a update today because Samsung was proposing that to me
After the update, I have a error message about system ui and I can do nothing with my phone.
Not rooted, nothing is modified in my phone. I have only installed substratum with swift black theme but not rooted.
I think it's because of this.
Someone can help me please, the secured mode change Nothing.
Help please
Click to expand...
Click to collapse
Don't update with Substratum theme installed, as stated by another member just boot into safe mode and uninstall all the substratum layers you have installed and reboot.
Hi guys..
I have recently rooted (supersu) my j7 prime g610f (7.0) after installing dm-veriry pypass and twrp and then flashed xpoosed framework and tried aome moudles out and everything seemed to be fine .
Untill i rebooted to activate a moudle and i found that the lock screen doesnt want to unlock although the pin is right( just stands still for 2 seconds and then screen turns off and i repeated the process and same thing ) ..
I managed to unlock my phone through the website and tried other lock methods and i found that every method isn't responding aswell !
I then disabled all the models and denies all root access apps and rebooted and same thing happens.
I really need some help as i cant leave my phone unlocked.
Thx.
Bassem AbdullMonem said:
Hi guys..
I have recently rooted (supersu) my j7 prime g610f (7.0) after installing dm-veriry pypass and twrp and then flashed xpoosed framework and tried aome moudles out and everything seemed to be fine .
Untill i rebooted to activate a moudle and i found that the lock screen doesnt want to unlock although the pin is right( just stands still for 2 seconds and then screen turns off and i repeated the process and same thing ) ..
I managed to unlock my phone through the website and tried other lock methods and i found that every method isn't responding aswell !
I then disabled all the models and denies all root access apps and rebooted and same thing happens.
I really need some help as i cant leave my phone unlocked.
Thx.
Click to expand...
Click to collapse
1) Easiest way is to wipe and restore a backup in TWRP from when your device was working properly if you've hopefully already made one.
2) Another option is to boot into TWRP and go into file manager and delete the folders of the Xposed Modules you installed that you think might be causing the problem(in "/data/app/", "/data/data/, etc)". Then reboot and see if that fixed the problem. You have to be very careful when installing Xposed mods, especially when they're meant to tweak the system in some way, that they are actually meant for your device, particularly with Samsung Touchwiz devices that have heavily modded software.
3) Make sure that you're using the correct Xposed version for Samsung too, as this can cause problems with properly booting up the device.
4) Last case scenario you might want to consider wiping and reflashing your rom. Then at least you can make sure your touchscreen digitizer still works and can redo everything one at a time to see what's causing the problem.
I hope one of these suggestions helps.
Sent from my SM-N920T using Tapatalk
bogarty said:
1) Easiest way is to wipe and restore a backup in TWRP from when your device was working properly if you've hopefully already made one.
2) Another option is to boot into TWRP and go into file manager and delete the folders of the Xposed Modules you installed that you think might be causing the problem(in "/data/app/", "/data/data/, etc)". Then reboot and see if that fixed the problem. You have to be very careful when installing Xposed mods, especially when they're meant to tweak the system in some way, that they are actually meant for your device, particularly with Samsung Touchwiz devices that have heavily modded software.
3) Make sure that you're using the correct Xposed version for Samsung too, as this can cause problems with properly booting up the device.
4) Last case scenario you might want to consider wiping and reflashing your rom. Then at least you can make sure your touchscreen digitizer still works and can redo everything one at a time to see what's causing the problem.
I hope one of these suggestions helps.
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
Unfortunately i dont hace a backup but i noticed something that the problem is a delay in responding to my pin , and i notice that the cpu usage goes 3% to 35% when i unlock my phone usinv the pin ... i managed to unlock it by entering the pin and tapping in the screen few times to keep it lit and prevent it from sleeping .. any ideas foe that delay or cpu usage ?
Bassem AbdullMonem said:
Unfortunately i dont hace a backup but i noticed something that the problem is a delay in responding to my pin , and i notice that the cpu usage goes 3% to 35% when i unlock my phone usinv the pin ... i managed to unlock it by entering the pin and tapping in the screen few times to keep it lit and prevent it from sleeping .. any ideas foe that delay or cpu usage ?
Click to expand...
Click to collapse
Truthfully, your best bet while you have your device up and running is to backup all your apps and data with something like Titanium Backup or even sync them with the Samsung Cloud. The cloud reinstalls everything and sets your device configuration back to the way it was. Then, if you have a custom rom installed, wipe it in TWRP and reinstall it. If you're running stock, then don't wipe. Just go to the Sammobile website, download the latest firmware for your specific device and reflash it to the device with Odin. This generally fixes all system problems with a device, while preserving your app data.
Alternately, you can also try searching XDA for kernels that are made for your device that have a higher performance and try installing one of those to see if anything improves. As far as the screen going off early too, you can always check in "Settings/Display/Screen Timeout" to see what it's set for and change it to the max screen on time. It really sounds like you may have broke something system wise with Xposed or an Xposed module though, which is very easy to do, so I would really recommend starting over fresh. If you're on stock especially, as you really have nothing(data wise) to lose.
Sent from my SM-N920T using Tapatalk
Hello guys i have s20 fe by mistakenly installed a corrupted theme now my phone isn't opening system UI error in normal mode stuck in safe mode
anyone has adb command to set the default Samsung theme?
did you use Substratum ? if so there should be guides to removing themes there in that thread
3mel said:
did you use Substratum ? if so there should be guides to removing themes there in that thread
Click to expand...
Click to collapse
ohh no substratum normal .apk theme
flash your current rom again via Odin but use HOME_CSC so that you keep your data.
if you are rooted patch it again.
edit: hmm, actually maybe this won't work if the bad theme is user data itself. where did you get it from ? there aren't any 3rd party themes for this device so you were taking a risk to try something at random.
didn't think an apk alone (without root) could do anything unless it's from Samsung store. if it is a Samsung theme I've no idea if uninstalling it and rebooting should make it go away.