Crashes all the time on TF300T - Omni Q&A

I recently updated from the final omnirom build of android 4.4 to the 8/27 omni rom nightly. I updated the gapps package and rooted the tablet as well. Everything would be working fine if the os didn't crash and restart all the time. I updated to today's nightly and that did not help. Is there anything that can be done to fix this?

Related

[HELP] GAPPS not installing

Hello,
I'm running last Quarx update (January 7th). I installed the latest Gapps in the custom recovery, everything seems to work fine but I finally end up with no new application in the dash...
Can someone help me ?
Thanks a lot !

[Q] Gapps freezes my N7100

OK so after much trouble shooting, I found that Gapps from Paranoid Android, which supports 4.4, is the culprit. I ran plain old OMNI ROM all day without a single freeze.
Then I decided to try installing ONLY Gapps and bingo.
As soon as I had it all set up, everything froze.
So, how do I get Gapps on my phone without having it freeze?
Phone is N7100
Omnirom is 11/28 nightly
Gapps is 11/26 Full from Paranoid Android.
Thank you thank you thank you....

MoKee OS Official 5.1.1 Nightlies

For anyone who doesn't know; MoKee Nightlies are available for Thea, if anyone wants to try. It's pretty good.
http://download.mokeedev.com/?device=thea
Their original dev (and unkwon) must create a post for more detailed information...! But thanks for the advice.
Obviously. They haven't yet! Just telling people it's there.
It's pretty good, but at the moment Bluetooth is not working, can't connect to my Android Wear, so back to CM12 but I'll keep trying =)
hugoprh said:
It's pretty good, but at the moment Bluetooth is not working, can't connect to my Android Wear, so back to CM12 but I'll keep trying =)
Click to expand...
Click to collapse
Were you using a nightly or release build? Bluetooth is working fine for me. I'm on the latest release build. Smooth and stable.
mej0248 said:
Were you using a nightly or release build? Bluetooth is working fine for me. I'm on the latest release build. Smooth and stable.
Click to expand...
Click to collapse
Yep it was nightly 2015-05-23 , later I'll try the new nightly and if that does not work, then I will try the release build. Cheers for the info =)
How good is it? Is it better than CM?
I prefer it to CM. The release builds are great. No issues for me.
I4ve been on this ROM for a day now and it works like a charm. Mokee is really great. No buigs or FC for now
EDIT : GPS works for You ? I can't get a fix.... Did a clean flash of Mokee but still no GPS Fix
EDIT #2 : OK now it works, just have o erase modemst1 and modemst2 with fastboot
Hi everyone,
I've been enjoying Mokee for a week, flashed nightlys every two days and just discovered that their OTA system just download the changes from the rom installed to the new build. I tried to DL it and flash but I've an endless bootanimation after.
Is it the same for you too? Thanks
metalmoot said:
Hi everyone,
I've been enjoying Mokee for a week, flashed nightlys every two days and just discovered that their OTA system just download the changes from the rom installed to the new build. I tried to DL it and flash but I've an endless bootanimation after.
Is it the same for you too? Thanks
Click to expand...
Click to collapse
I don't use OTA.
I heard that it broke ever, then they fixed. I'll link to him.
Try using the Release builds instead. More stable and OTAs are every week or so.
Yes but releases are odexed and xposed does not work with odexed roms
Ok, I don't ever use Xposed with custom roms. Just stock.
Caution ! The 28/06 nightly doesn't work !
I will go back to CM because the 29/06 crashes when I use a theme.
Great rom but I honestly can't see the advantage over CM. Ota would be a plus but it fails.
Back on CM with Cyandelta for incremental updates
Another update on Mokee on Thea :
- OTA works great but you must not remove /system apps and modify build.prop however the phone will bootloop.
- OTA doesn't work with Xposed as well, bootloop
- Release versions (odexed ROM) are really smooth and seem to be more battery friendly than nightly releases...
- The ROM is bugfree, I've been using Mokke for two weeks now and no reboot, no freeze, perfect experience
metalmoot said:
flashed nightlys every two days and just discovered that their OTA system just download the changes from the rom installed to the new build. I tried to DL it and flash but I've an endless bootanimation after.
Click to expand...
Click to collapse
Same here, I'm really happy with Mokee (running release version), no bugs so far and smooth performance. However I tried as you did to download incremental update through Mokee Center and automatically flash through recovery (TWRP), but got endless boot animation, had to download full ROM and flash after wiping system/data/cache/dalvik.
Does anyone know if Mokee can be upgraded simply by flashing full ROM zip without wiping system and data?
Tried again updating through Mokee Center, this time downloading full ROM. Didn't get endless bootloop, but performance was really bad, moto g suddenly rebooted 2 times, very unstable. I decided to wipe all and reflash manually through TWRP. Working fine now... it seems that auto-update are not working very well. Anyone who didn't get those problems and successfully updated through Mokee Center?
I managed to have incremental updates working on release versions. You must not touch anything in /system (you can freeze apps however)
I've been updating like that for two releases and it works
Just a quick for OTA updates on nightly builds with Xposed.
Ota works if you uninstall xposed with the uninstaller zip before flashing OTA !

S3 Neo (I9300I) Bootloops randomly

Hi guys! my s3 neo started randomly bootlooping after 1 year, I had RR 5.5.9 on it. I noticed that if I press button_vol_up when bootlooping the phone starts to access recovery, but suddenly continue rebooting so I tried to wipe ALL in the s3 neo from TWRP and with Odin I reflashed a new version of TWRP. After that, I clean installed the RR 5.5.9 and for a few days started working good.
Yesterday night the problem seems reappeared and then I soldered a new power button thinking it was the problem ( even if it's a random problem, it seems) but without fixing this problem. So I decided to desolder the power_button and starting using without it, and the phone was working very good, after 6 hours booom! the bootlooping is still here.
Can anyone help me? Thanks in Advance
When your RR is based on CM12.1 then the bootloop occurs when you install some new updated apps. You have 3 choices.
1) avoid these apps
2) Inform the developer of the apps, that with the new update your cm12.1 version gets a bootloop. The bootloop occurs, when the updated Version of the app was build with the new android build tools. The Solution is to use aapt instead of aapt2
3) upgrade to cm13 or cm14.1 . Theres also a RR based on 14.1. I didn't try this version, but i think with this rom you will not have the bootloop
same problem.
I have tried to flash it with many firmware without any success.
any help
alaa92 said:
same problem.
I have tried to flash it with many firmware without any success.
any help
Click to expand...
Click to collapse
What exactly is your problem?
Meanwhile there are quite stable Custom Roms that would be there:
- CM 12.1 from December 2017 (no more bootloops!)
- LOS 14.1 from August or also December 2018
- crDroid from November 2018

Solution to Android 7.x.x lagging for some devices.

As you may know, even if it's rare some Tab 2 devices just won't accept Android 7. When you install any ROM that is based on Nougat device will just refuse to work properly. It will lag so bad you won't be able to do anything and forcefully return to Marshmallow.
I'm happy to announce that I found issue: Busybox. Yes, it appears Busybox somehow messes the Android 7. I've also found it messes with Android 6. So, I decided to test all latest 7.1.2 custom ROM's made by Andi.
LineageOS 14.1: Latest 2020 build with OC kernel, lagged after Busybox install.
Unlegacy project 7.1.2: Same as above, however system lagged after boot so I can't test it
Omnirom 7.1.2: Worked like charm until I decided to update it's busybox.
So, I decided to stick on Omnirom 6.0.1 and used it's native busybox instead of updating it. The problems I suffered while I used LineageOS 13.1 is gone. My wifi works properly and no constant app crashes.
I have no idea why Busybox would mess system up, but something between 1.22.1 (the version Omnirom comes with) and 1.30.1 (current Busybox version on Busybox Pro) is definitely not compatible with Andi's ROMs

Categories

Resources