Related
Hello, been a while since I posted here.
Something of interest came up while making some changes to the android [ICS] launcher using apktool. I have Team Blaze ICS preview 4 and was meesing with android.policy.jar, to make some personal changes to the lockscreen. The changes seemed to work fine, but something interesting came up when I pushed the android.policy.jar (edited) back to the device and then I rebooted it to have this screen popup. Take a look for yourself. HERE
Has anyone come accross this screen? I guess even more important what kind of 'OPTIMIZING' was/is it doing during this 'Android upgrade'.
Just an FYI, I was too lazy to sync with the source so I was smali-ing the compiled code to change the camera intent on the launcher to open my gmail instead of the camera, since the camera's drivers haven't been completely setup yet.
i saw this when i first loaded deck's ics..... must be part of it...
crstfr said:
i saw this when i first loaded deck's ics..... must be part of it...
Click to expand...
Click to collapse
If you boot into recovery and wipe cache and dalvik, upon boot up it will optimize all your apps.
I suggest flashing decks ics, rebooting to ics and give a min to settle. Back to recovery and flash gapps. Reboot and give a min to settle. Restore apps, back to recovery and wipe cache and dalvik.
This way ics optimizes all your apps. I have noticeably better performance and less fcs and problems in general.
As with the Black Bean ROMs, this will now have it's own thread to keep confusion down and information easier to obtain.
I present to you Paranoid Android for the Thrive!
Built from source
Includes Balthesaur 2.7x series kernel
Includes ALL fixes implemented into the Unified builds as of U5
Working Storage
Paid Apps
Sensors
GPS
WiFi
BT
Hardware decode
Hardware acceleration (UI / Project Butter)
WiFi LED
Current known issues:
Like all CM based ROMs it suffers EGL memory errors, which will result in lockscreen "blinking" and needing a hard reboot. Best way to prevent this currently is to not enable any lockscreen, it impacts a lot of devices and is still being looked into.
Uses the Balthesaur JB kernel
Change log:
Resuming from Kuroikaze Threads Build 1 - Build 2
Storage works
Paid apps work
WiFi LED works
Memory management tweaked yet again
Glitches:
Internal SD will appear smaller then normal, this is due to a shift from internal sd to /data, while it may suck to lose some of that internal sd space, it does allow more apps to be installed and requires less use of hacky method to move apps/data to sd to save space for app installation. It seems to be a ratio vs a set amount, IE the bigger the internal sd, the more it moves to /data. A 16GB model will show 10GB internal sd and 5GB available for data/apps. This appears even in stock ICS, I'm not sure of the issue.
Downloads:
Paranoid Android Build 2
Instructions:
For Build 2 a FULL WIPE MUST BE DONE!
Each build after 2 may be dirty flashed if you choose.
Generic flashing instructions - this assumes you have flashed at least one custom ROM in CWM/TWRP at some point.
Download ROM from the link above
Download Gapps provided by Indest at the CM10 Wiki HERE
Reboot into your CWM/TWRP Recovery
Make a full backup/nandroid before proceeding
-For first use of this ROM, a full wipe should be done, regardless of previously installed ROM, this applies for B2, and any version after if you are not on at least B2. A Full wipe means Factory reset, dalvik, system, cache.
-For second flashing (B3 or higher) you may choose to wipe only cache and dalvik and flash just the ROM and Gapps.
After flashing is done (you flashed Gapps after the ROM, right?) reboot system
Allow up to 15 minutes to boot to UI
Once the welcome setup wizard shows up, let it sit for 10 minutes
After the 10 minutes complete the setup of the tablet then reboot
After reboot let it sit 5 minutes
Proceed setting up the device with your apps.
Restore only user apps, and data only if you need to (like game saves, book marks, etc)
Never restore system apps or data! This is red in Titanium Backup
After restoring what you will, reboot one more time
Let sit 5 more minutes
Use device as normal.
Thanks to:
Tybar
JBettcher
Indest
Paranoid Android
Google
Cyanogenmod
Linaro
I installed B145 with the kat 80b kernel and the v3 battery patch and everything looks good. I had to swipe as I was using build 81 before. Quite honestly, since I'm not running any synthetic benchmarks nor overclocking the proc, I'm hard pressed to find any difference in performance from EOS 3. Mind you, the buttery feel on this ROM (and EOS 3, for that matter) is day and night when compared to Asus's stock code. So if you're like me and waited this long to root your Transformer (I popped its cherry just a month ago, after having it for 1 year), don't be afraid to try this ROM... the best thing to have happenned to the og transformer.
One question I have is, what are you guys using to constantly restore your apps and/or settings after repeatedly flashing new ROMs? It's a pain in the neck having to reinstall all the apps and setting them up! Thank you and special thanks to Timduru and his minions This thing is awesome...
Sent from my Transformer TF101 using Tapatalk HD
I use Titanium Backup, but I let Google install all my apps, then restore the data.
There are a few apps I have to install using Titanium (from Amazon) that I have to restore using Titanium. Those apps I have to tap the Install button and Done for each one.
I tried using the App Backup in the ROM Toolbox by Jrummy, but it did not restore all the data correctly (mainly thumb keyboard).
I also make nandroid backups using TWRP so I can quickly restore a working ROM without having to reinstall stuff if something goes south.
I also use Titanium Backup but with some reservations. If you're going to go back to the ROM you're running, you're much better off with a nandroid backup. TB is cool for a few reasons: batch backup/restore, system apps or just apps, etc... however you have to be careful with it.
- Make sure you always verify your backups (often). Never assume "they'll work", cause they most likely won't - that's a known issue that it fails to parse its own packages once in a while, so batch restores just lock up the entire operation and you have to forcibly kill it to start where it left off.
- Always keep a copy of the backups elsewhere than on the tablet
- Just because it backs up a system app or an app doesn't mean it can restore it, even on the same rom.
- Some stuff like contacts need to be exported then imported back especially if you're upgrading to another android version.
- System apps will almost always fail to install on another android version unless they were "hacked" to make them work.
So yeah it's a really good and powerful tool but to use with caution. Always redo full backups and verify them before you wipe/flash and always have a complete nandroid backup to restore in case of issues, like Frederuco said.
Edit: Once you're on Team EOS's roms, I dount think you have to do a full wipe anymore. I just wipe cache, dalvik and system, then flash the new rom, that way all my apps are still there. I only do a full reset if I experience issues after doing this, to make sure it's the rom and not apps, and to report to Tim from a fresh flash.
Thank you both. I'll give Titanium a try whenever I try another ROM. In the meantime I decided to go back to EOS3 build 81. I *really* don't like the new status bar on top. It specially bugs me when browsing the web since it's eating up screen real estate.
[Edit]
This is probably a known issue, but for those going back from EOS 4 to EOS 3: the directory /sdcard was copied to /sdcard/0 after installing EOS 4; so, when I restored EOS 3 from nandroid backup, the system wasn't responding as it should and some apps were very slow (I guess expecting to find their data under /sdcard). Copying /sdcard/0 back to /sdcard and rebooting made everything work much better. Thanks.
landous said:
[Edit]
This is probably a known issue, but for those going back from EOS 4 to EOS 3: the directory /sdcard was copied to /sdcard/0 after installing EOS 4; so, when I restored EOS 3 from nandroid backup, the system wasn't responding as it should and some apps were very slow (I guess expecting to find their data under /sdcard). Copying /sdcard/0 back to /sdcard and rebooting made everything work much better. Thanks.
Click to expand...
Click to collapse
From what I've read this is an issue with CWM. I saw frederuco mention it on the EOS 4 thread.
I had the same problem, went from build 92 to preview 145 and Titanium Backup couldn't find anything. I was pulling my hair out until I saw his post
If you use TWRP 2.3.2.3 the /0 directory issue goes away.
Also, TWRP IMO is much better than any CWM to date.
I start with a fresh wipe of my phone and then install BeanStalk with gapps (I'm currently using BS version 4.4.275 with gapps 20140105. Everything is fine for months. Then a couple of apps will start to crash a few times (the camera, dialer, browser and google apps). I've stopped using titanium backup and clockwork mod to restore my data because they were causing issues. Then the force closes become more and more frequent. I ran fix permissions and i have know clue if it helped or not. Then finally all hell breaks loose and everything begins to force close and give errors of no space left on phone. No launcher will stay open everything just bugs out. This seems to be an on going matter. It doesn't seem to resolve no matter what rom I run. I've gone through every folder sizing it and my phone is not out of space. I am getting very frustrated with my Infuse. I don't understand what some of the stuff means in my catlog file. If someone could help I'd greatly appreciate it.
i found out that Google+ and Google Drive might be the cause (such as when you upload or backup your photos to those clouds)
if you have time, go read those last 10 pages of BeanStalks, you will see what others have offered to resolve this issues
as for me, I'd do full wipe, specially format the sdcard0 (keep the Rom and Gapps to your SDcard1), and stop using the two Google services mentioned above. and use another Gapps (I am using the minimal one) Good luck!
Same problem with Unofficial CM 11.2 also
Exactly the same issue I am having with Unofficial CM 11.2 from scott.
I have been using Scott Harts Unofficial CM from 10.1 to 11.2 on my Samsung infuse and each time i notice a pattern.
Each of the above ROMs start out pretty smooth, and the phone works without any issues for 6 months or so. Then occasionally and app or two start crashing. Then in a weeks time all hell breaks loose and almost all apps start crashing such that the phone becomes unusable. Especially trebuchet starts crashing and that is the end of story.
In the past i have noticed this happens a month or so after an updated rom has been released and I used to upgrade to the new one and the cycle continues.
I am currently on the latest Unoffical CM 11_2 (Kitkat) and the appropriate Gapps installed and the same issue has happened twice.
I have tried the following to fix the issue and nothing helps
1. Clear data for trebuchet and a bunch of other apps.
2. Reinstall Gapps
3. Wipe Cache >> Wipe Dalvik Cache
4. Wipe Cache >> Wipe Dalvik Cache > install Gapps
5. Wipe Cache >> Wipe Dalvik Cache > install custom Rom >> install gapps >> wipe cache and dalvik again
The only way I have been able to get it working in the past is
1. Wipe data/factory reset > Clear Cache > clear Dalvik cache and possibly reinstall ROM and gapps (not sure, but I guess factory reset also does the trick)
So my phone is stuck in this mode and I would like to help debug the situation. Can someone help with the next steps? So that I can capture all required information before I do a factory reset .
Unable to get RSA prompt
Well I went ahead with a factory reset, installed Unofficial CM11_2 from Scott. Got the latest gapps from goo.im and phone seems normal again. But that is the expected behavior untill it starts acting up again.
I tried a lot to connect the phone through ADB and each time it remains unauthorized.
I tried on 2 different laptops, Windows 7, Windows Vista as well as Ubuntu - it always remained unauthorized and no matter what i tried ... changing USB ports , OS machines...nothing helped.
I never got the RSA signature prompt on my phone so could not do anything with ADB.
Any body has any ideas ?
hemen_kap said:
Well I went ahead with a factory reset, installed Unofficial CM11_2 from Scott. Got the latest gapps from goo.im and phone seems normal again. But that is the expected behavior untill it starts acting up again.
I tried a lot to connect the phone through ADB and each time it remains unauthorized.
I tried on 2 different laptops, Windows 7, Windows Vista as well as Ubuntu - it always remained unauthorized and no matter what i tried ... changing USB ports , OS machines...nothing helped.
I never got the RSA signature prompt on my phone so could not do anything with ADB.
Any body has any ideas ?
Click to expand...
Click to collapse
This has been an issue for a while, if the problem is showing up like this:
http://forum.xda-developers.com/showthread.php?t=2175261
Honestly haven't tried ADB with the newer stuff (namely Beanstalk), I just know that ADB as been a problem in the past for Scott's ROM's.
joel.maxuel said:
This has been an issue for a while, if the problem is showing up like this:
http://forum.xda-developers.com/showthread.php?t=2175261
Honestly haven't tried ADB with the newer stuff (namely Beanstalk), I just know that ADB as been a problem in the past for Scott's ROM's.
Click to expand...
Click to collapse
Yes, it is the same problem. Any suggestions ? How is the AOSP based Carbon ROM, any idea if it has the same issue too ?
hemen_kap said:
Yes, it is the same problem. Any suggestions ? How is the AOSP based Carbon ROM, any idea if it has the same issue too ?
Click to expand...
Click to collapse
Not sure about the other ROM's. I could go on a flashing journey, but I have two new devices I'm getting adjusted to right now. If you are not tied down to CM (don't know if it's your DD), I would suggest trying Carbon or CyanFox.
Me, I didn't need ADB that much at the time so I stuck with what I have. Not a solution, but I hope you find a ROM that works (partnered with a minimal gapps).
joel.maxuel said:
Not sure about the other ROM's. I could go on a flashing journey, but I have two new devices I'm getting adjusted to right now. If you are not tied down to CM (don't know if it's your DD), I would suggest trying Carbon or CyanFox.
Me, I didn't need ADB that much at the time so I stuck with what I have. Not a solution, but I hope you find a ROM that works (partnered with a minimal gapps).
Click to expand...
Click to collapse
Unfortunately the infuse is the only phone I have (so my DD)...but the lure to test the ADB on carbon is also compelling for me. Let me try moving to a non smart phone and try this out.
OK. So i installed the Carbon KK nightly, and encountered the same issue. adb devices always lists the phone as
0123456789ABCDEF unauthorized.
Also i never received the rsa prompt...
Moreover the device key seems to suggest it is some default value as compared to an actual device key.
Got it Working !!!
Ok so finally got it working.
I moved away from Scott's Unofficial CM11_2 on my daily driver and moved to Carbon ROM. Loving the new rom so far.
Once i moved to this ROM, I started adb on my desktop (adb kill-server, adb start-server) and was waiting
then on phone enabled Developer options and Android debugging over USB and connected the phone to desktop, and zingggg I get the RSA prompt.
One important thing it read is that you phone should be unlocked when you connect it to your desktop, so in case you have things like PIN or gestures that lock your screen....ensure that your screen is not locked when the phone is being connected.
Not sure if this was the issue or if it was the CM rom,,,but issue is resolved, I am loving Carbon...so not going back to CM to check the lockscreen theory....but worth a try for someone who is pulling his/her hair out like i was.
Ciao !!!
---------- Post added at 05:00 PM ---------- Previous post was at 04:41 PM ----------
missed mentioning that do not worry about the device id of 0123456789ABCDEF....i noticed it does not change for me even when adb connects properly.
It is the unauthorised state that needs to change to device.
What's the default launcher on Carbon, or does it give you a choice like Beanstalk?
Will be retiring the Infuse soon, so am thinking on what ROM to put on when I go to sell it (or give away). The requirement is that is not overwhelming to a new user. Cyanogenmod has a lot of customization, but it doesn't necessarily get in the way. I'd call it borderline overwhelming. Beanstalk is quite overwhelming, because you are forced to pick a launcher right from the beginning (even though I like it for the Jellybean qualities).
Because of these, I just may return it to stock, but have it rooted and with CWM.
joel.maxuel said:
What's the default launcher on Carbon, or does it give you a choice like Beanstalk?
Will be retiring the Infuse soon, so am thinking on what ROM to put on when I go to sell it (or give away). The requirement is that is not overwhelming to a new user. Cyanogenmod has a lot of customization, but it doesn't necessarily get in the way. I'd call it borderline overwhelming. Beanstalk is quite overwhelming, because you are forced to pick a launcher right from the beginning (even though I like it for the Jellybean qualities).
Because of these, I just may return it to stock, but have it rooted and with CWM.
Click to expand...
Click to collapse
I do not see any option to select a launcher like Scotts CM had. So i guess there is no direct option to select it.
Quick search in the running apps shows Launcher 3 running, and apk also available in the priv-app folder in rom, so can conclude launcher is Launcher3.
I did not find it overwhelming in any way.
-Hemen
hemen_kap said:
I do not see any option to select a launcher like Scotts CM had. So i guess there is no direct option to select it.
Quick search in the running apps shows Launcher 3 running, and apk also available in the priv-app folder in rom, so can conclude launcher is Launcher3.
I did not find it overwhelming in any way.
-Hemen
Click to expand...
Click to collapse
I flashed it last night (latest nightly), and it gave me the option of either Launcher3 or Google Now Launcher. I think if someone who was new to the device would be stumped a little by this, but would probably select the Google Now one (the question would be would they press once or always) and be done with it.
Having something recognizable runs at an advantage here compared to Beanstalk, where, unless you know CyanogenMod (or have played with a lot of launchers) you wouldn't know what to select. That would be overwhelming.
Anyway, I wiped the data again, breezed through setup (skipped everything but language and time zone), so it's all ready to go. If need be I can get them set up with a network and Google account before I throw them to the wind.
EDIT:
I see why I got the prompt ... I used the Paranoid Android micro apps package, which includes ... the Google Now Launcher.
hemen_kap said:
Exactly the same issue I am having with Unofficial CM 11.2 from scott.
I have been using Scott Harts Unofficial CM from 10.1 to 11.2 on my Samsung infuse and each time i notice a pattern.
Each of the above ROMs start out pretty smooth, and the phone works without any issues for 6 months or so. Then occasionally and app or two start crashing. Then in a weeks time all hell breaks loose and almost all apps start crashing such that the phone becomes unusable. Especially trebuchet starts crashing and that is the end of story.
In the past i have noticed this happens a month or so after an updated rom has been released and I used to upgrade to the new one and the cycle continues.
I am currently on the latest Unoffical CM 11_2 (Kitkat) and the appropriate Gapps installed and the same issue has happened twice.
I have tried the following to fix the issue and nothing helps
1. Clear data for trebuchet and a bunch of other apps.
2. Reinstall Gapps
3. Wipe Cache >> Wipe Dalvik Cache
4. Wipe Cache >> Wipe Dalvik Cache > install Gapps
5. Wipe Cache >> Wipe Dalvik Cache > install custom Rom >> install gapps >> wipe cache and dalvik again
The only way I have been able to get it working in the past is
1. Wipe data/factory reset > Clear Cache > clear Dalvik cache and possibly reinstall ROM and gapps (not sure, but I guess factory reset also does the trick)
So my phone is stuck in this mode and I would like to help debug the situation. Can someone help with the next steps? So that I can capture all required information before I do a factory reset .
Click to expand...
Click to collapse
Hi,
I was using CM 10.1 from Scott for like a year and didn't have any trouble at all, really the best ROM. Only had two small problems: wouldn't film on 720p without bugging, and MHL to HDMI was not working.
Now I installed CM 11, with latest gapps ( didn't know there was a CM11.2 ), and camera issue on filming is the same. But now it's worse, battery life is lasting half the time it was before, and gallery is crap, bugging every time. Did you have the same issues? Tell me the post of CM11.2 please..
Sent from my SGH-I997 using XDA Free mobile app
jloibman said:
Now I installed CM 11, with latest gapps ( didn't know there was a CM11.2 ), and camera issue on filming is the same. But now it's worse, battery life is lasting half the time it was before, and gallery is crap, bugging every time. Did you have the same issues? Tell me the post of CM11.2 please..
Click to expand...
Click to collapse
Not sure about this, but I think CM 11.2 is referred to as KitKat 4.4.4, which would be latest in the CM thread. So you are probably already running it.
Sent from my Asus MeMO Pad 8"
jloibman said:
Hi,
I was using CM 10.1 from Scott for like a year and didn't have any trouble at all, really the best ROM. Only had two small problems: wouldn't film on 720p without bugging, and MHL to HDMI was not working.
Now I installed CM 11, with latest gapps ( didn't know there was a CM11.2 ), and camera issue on filming is the same. But now it's worse, battery life is lasting half the time it was before, and gallery is crap, bugging every time. Did you have the same issues? Tell me the post of CM11.2 please..
Sent from my SGH-I997 using XDA Free mobile app
Click to expand...
Click to collapse
apart from the issues that i mentioned - my experience with CM 11.2 has been great. There are some obvious things like MHL etc that do not work, but those are known issues.
joel.maxuel said:
I flashed it last night (latest nightly), and it gave me the option of either Launcher3 or Google Now Launcher. I think if someone who was new to the device would be stumped a little by this, but would probably select the Google Now one (the question would be would they press once or always) and be done with it.
Having something recognizable runs at an advantage here compared to Beanstalk, where, unless you know CyanogenMod (or have played with a lot of launchers) you wouldn't know what to select. That would be overwhelming.
Anyway, I wiped the data again, breezed through setup (skipped everything but language and time zone), so it's all ready to go. If need be I can get them set up with a network and Google account before I throw them to the wind.
EDIT:
I see why I got the prompt ... I used the Paranoid Android micro apps package, which includes ... the Google Now Launcher.
Click to expand...
Click to collapse
You can download the Nova Launcher from the google play store if you want to have the same experience as with Scotts Beanstalk. I love the carbon ROM but I am so accustomed to the Nova launcher that I cant live without it.
hemen_kap said:
Exactly the same issue I am having with Unofficial CM 11.2 from scott.
I have been using Scott Harts Unofficial CM from 10.1 to 11.2 on my Samsung infuse and each time i notice a pattern.
Each of the above ROMs start out pretty smooth, and the phone works without any issues for 6 months or so. Then occasionally and app or two start crashing. Then in a weeks time all hell breaks loose and almost all apps start crashing such that the phone becomes unusable. Especially trebuchet starts crashing and that is the end of story.
In the past i have noticed this happens a month or so after an updated rom has been released and I used to upgrade to the new one and the cycle continues.
I am currently on the latest Unoffical CM 11_2 (Kitkat) and the appropriate Gapps installed and the same issue has happened twice.
I have tried the following to fix the issue and nothing helps
1. Clear data for trebuchet and a bunch of other apps.
2. Reinstall Gapps
3. Wipe Cache >> Wipe Dalvik Cache
4. Wipe Cache >> Wipe Dalvik Cache > install Gapps
5. Wipe Cache >> Wipe Dalvik Cache > install custom Rom >> install gapps >> wipe cache and dalvik again
The only way I have been able to get it working in the past is
1. Wipe data/factory reset > Clear Cache > clear Dalvik cache and possibly reinstall ROM and gapps (not sure, but I guess factory reset also does the trick)
So my phone is stuck in this mode and I would like to help debug the situation. Can someone help with the next steps? So that I can capture all required information before I do a factory reset .
Click to expand...
Click to collapse
OK the exact same problem has started again today on Carbon ROM. Wonder if this is a Cyanogen thing, as that seems to be common between the two.
Anyone else facing this ?
-Hemen
hemen_kap said:
OK the exact same problem has started again today on Carbon ROM. Wonder if this is a Cyanogen thing, as that seems to be common between the two.
Anyone else facing this ?
Click to expand...
Click to collapse
Hmm, don't think I kept a ROM on my Infuse long enough to encounter this problem (except for my several months with CM 10.1, no issues). As for other phones, I use Jellybean on my semi-retired HTC and did not have this problem (closest I came was when I tried out Fly-On mod - lag closures often). But I don't think It's a Jellybean problem.
I think (and this may have been covered already) this has to do with the piddly datadata partition filling up. One way to check is open a terminal emulator (app on the phone of adb shell) and type:
Code:
df
Look for datadata in that listing. If it is in the 90% range, that spells trouble. If that is the case, you could try one of two solutions.
I don't know what possessed the developers to separate the data partitions in KitKat (I know, for "performance reasons") but leave 1/2 a GB for it. Lower end phones these days give you twice that.
Over the past few years or so I've installed ROMs going back to ICS. 99% of the time there was absolutely no issue. I habitually do a (1) factory wipe, (2) dalvik wipe, (3) system format, (4) sdcard0 format, (5) install ROM zip, (6) install gapps, (7) wipe cache and (8) wipe dalvik.
In the hundreds of ROMs I've installed and tested, 1 or 2 were bad compiles, and everyone soon knew it. They were immediately removed from any host site. So, if you're having issues, (1) install you ROM as above, (2) perhaps install a smaller gapps, and/or (3) check that you're not overloading your phone from the PlayStore.
The last and rarest issue could be your phone, but rule of thumb that works 99% of the time is: (1) assume it's always your fault first, and (2) read, read, read, read, read.
Hello,
I'm hoping someone can help me troubleshoot an issue I'm having with my TF700T taking a long time to load (but is working well in all other respects).
I'm running bootloader 10.6.1.14.10, TWRP 2.8.0.1, CrombiKK, and have just done a fresh clean wipe (from TWRP, I selected wipe, factory reset (didn't do an advanced wipe or format data).
When I first booted up with minimal apps, the device booted up in 2:18 minutes (1:18 system, 1:00 other items).
However, now that I've restored apps using TiBu (restored missing apps with data, exclude system apks), it's taking a long time to boot the device (10:49, system 9:49, startup items 1:00), and I haven't even activated xposed yet, which is mandatory in my view
I've reverted to the old Android ID when TiBu asks me whether I'd like to revert to an old version. This seems to have worked because some apps (such as Viber) don't require me to enter new details. Others (such as Dropbox) force me to enter my login details again, not sure why.
Can anyone suggest what may be causing the issue? Have included the latest logcat with this post.
RedDemon said:
Hello,
I'm hoping someone can help me troubleshoot an issue I'm having with my TF700T taking a long time to load (but is working well in all other respects).
I'm running bootloader 10.6.1.14.10, TWRP 2.8.0.1, CrombiKK, and have just done a fresh clean wipe (from TWRP, I selected wipe, factory reset (didn't do an advanced wipe or format data).
When I first booted up with minimal apps, the device booted up in 2:18 minutes (1:18 system, 1:00 other items).
However, now that I've restored apps using TiBu (restored missing apps with data, exclude system apks), it's taking a long time to boot the device (10:49, system 9:49, startup items 1:00), and I haven't even activated xposed yet, which is mandatory in my view
I've reverted to the old Android ID when TiBu asks me whether I'd like to revert to an old version. This seems to have worked because some apps (such as Viber) don't require me to enter new details. Others (such as Dropbox) force me to enter my login details again, not sure why.
Can anyone suggest what may be causing the issue? Have included the latest logcat with this post.
Click to expand...
Click to collapse
Does the ROM take that to boot on a new install, before you restore your apps ?
Thx Josh
lj50036 said:
Does the ROM take that to boot on a new install, before you restore your apps ?
Thx Josh
Click to expand...
Click to collapse
No, it only takes a little over two minutes before restoring the apps, something to do with the restore process is giving me grief. However, I didn't think the amount of apps I had was excessive (I have way more on my phone), and I've been careful not to restore system apps etc.
You first boot times seem normal.
So factory reset again
restore a few apps in TiBu
Reboot and check
restore a few more
reboot and check
etc
Yes, sounds like a good approach. I was hoping someone could suggest certain apps that are known to cause this sort of issue based on the logs, but it sounds like trial and error is the best way to determine the issue I'll report back once I've worked it out...
lj50036 said:
Does the ROM take that to boot on a new install, before you restore your apps ?
Thx Josh
Click to expand...
Click to collapse
berndblb said:
You first boot times seem normal.
So factory reset again
restore a few apps in TiBu
Reboot and check
restore a few more
reboot and check
etc
Click to expand...
Click to collapse
Have spent several frustrating days, and I don't feel much closer to resolving the issue. Been progressively installing apps from clean install and thought the problem was the XPosed module XPrivacy (because initially when I enabled/disabled it, the system start time alternated between about 2 minutes and 8 minutes). However, even after removing this module, the system time has jumped back up and even doing a nandroid restore to the previous known 'stable state' still results in a long startup time. The timing even seems a bit random/unstable.
I've also tried other things, like using the permissions manager to rebuild permissions (ie typing "for app in *.apk; do pm install -r $app; done" in /data/app), but this actually uninstalled a heap of apps!
Unless anyone has any ideas, it looks like I'm stuck with an unstable boot process. I guess I should be thankful that once booted things are pretty smooth.
RedDemon said:
Have spent several frustrating days, and I don't feel much closer to resolving the issue. Been progressively installing apps from clean install and thought the problem was the XPosed module XPrivacy (because initially when I enabled/disabled it, the system start time alternated between about 2 minutes and 8 minutes). However, even after removing this module, the system time has jumped back up and even doing a nandroid restore to the previous known 'stable state' still results in a long startup time. The timing even seems a bit random/unstable.
I've also tried other things, like using the permissions manager to rebuild permissions (ie typing "for app in *.apk; do pm install -r $app; done" in /data/app), but this actually uninstalled a heap of apps!
Unless anyone has any ideas, it looks like I'm stuck with an unstable boot process. I guess I should be thankful that once booted things are pretty smooth.
Click to expand...
Click to collapse
Pull another logcat do they match ?
Post so we can take a look,,,,
Thx Josh
lj50036 said:
Pull another logcat do they match ?
Post so we can take a look,,,,
Thx Josh
Click to expand...
Click to collapse
Sorry, I hadn't included logcats because it seemed to cloud the issue. Not sure what you mean by "do they match", but certainly the logcats are showing some consistent messages that seem problematic.
However, these occur even after a fresh install even when bootup times are OK. For example, in the bundle of logcats attached, 2014-11-04-14-57-55-fresh-install-2.32.txt is a logcat for a fresh install where the system bootup (not apps) was about 2 and a half minutes, but it still contains lots of things that don't look great to my untrained eye:
Failed on audit_set_pid with error: Protocol not supported
Unknown permission ....
Not granting permission android.permission....
lj50036 said:
Post so we can take a look
Click to expand...
Click to collapse
Not sure if you had a chance to look at the logs? I'm also wondering if Odexing the ROM will help? I've read that it will break theme-ability, does this extend to things like the XPosed framework?
RedDemon said:
Failed on audit_set_pid with error: Protocol not supported
Unknown permission ....
Not granting permission android.permission....
Click to expand...
Click to collapse
That's because I disabled SELinux in my kernel, should not lead to bad performance, just annoying lines in the log.
RedDemon said:
I'm also wondering if Odexing the ROM will help?
Click to expand...
Click to collapse
No. After dalvik-cache has been built there is no performance difference at all.
You could try running fstrim (aka Lagfix) or format /data in TWRP.
_that said:
That's because I disabled SELinux in my kernel, should not lead to bad performance, just annoying lines in the log.
Click to expand...
Click to collapse
OK thanks, good to know. I'll stop worrying about those messages then
_that said:
No. After dalvik-cache has been built there is no performance difference at all.
Click to expand...
Click to collapse
OK, I guess I'll refrain from ODEXing
_that said:
You could try running fstrim (aka Lagfix) or format /data in TWRP.
Click to expand...
Click to collapse
These are good ideas, I've already tried both those approaches. I'm at a loss to explain why bootup takes about 8 minutes on average
Just clocked an incredible 28:40 system boot up, anyone have any suggestions for resolving based on the attached logcat? I'm running lag fix on all partitions on a nightly basis, but this may in fact be hindering.
RedDemon said:
Just clocked an incredible 28:40 system boot up, anyone have any suggestions for resolving based on the attached logcat? I'm running lag fix on all partitions on a nightly basis, but this may in fact be hindering.
Click to expand...
Click to collapse
I can see you still have the Xposed framework installed, maybe try running without that.
_that said:
I can see you still have the Xposed framework installed, maybe try running without that.
Click to expand...
Click to collapse
Have disabled and the startup time has increased to 45 minutes. Not really sure how it's possible to take so long? Logcat attached if this helps.
I'm guessing you did a clean wipe and have reflashed the rom again? I don't know if you tried f2fs but that shortened my boot time to less than a minute.
agentkalaw said:
I'm guessing you did a clean wipe and have reflashed the rom again? I don't know if you tried f2fs but that shortened my boot time to less than a minute.
Click to expand...
Click to collapse
I've done plenty of clean wipes but when I rebuild it usually results in a long bootup time. I'm going to do another clean wipe and reflash. Thanks for the tip re f2fs, haven't used it before but I see that TWRP supports it and so does Crombi-KK. Did you convert all partitions to f2fs or were you selective about which partitions to convert? I'm tempted to convert all of them across.
I' m running zombie right now but I think both of them only support data f2fs. Yeah with twrp its pretty easy to just format the data partition and then reboot.
BTW did you see that post about an xposed module for long boot times?
agentkalaw said:
I' m running zombie right now but I think both of them only support data f2fs. Yeah with twrp its pretty easy to just format the data partition and then reboot.
BTW did you see that post about an xposed module for long boot times?
Click to expand...
Click to collapse
OK, I guess I'll restrict to just the data partition then. Shame, because the bootup delays seem to be system related, so I thought converting the /system partition would provide the most benefit.
Not sure exactly which post you're referring to for an xposed module for long boot times. I'm using BootManager etc, is that what you mean or something else?
From the crombi-kk thread:
"For those of you suffering long boot times, You may want to check out this xPosed module
[XPOSED] Xposed Media Scanner Optimizer
http://forum.xda-developers.com/xposed/modules/xposed-xposed-media-scanner-optimizer-t2942609
I was able to reboot in about 1 minute.
Note: you may get the message "unfortunately process media scan has stopped" - But just click okay a couple of times and it will go away.
Cheers
tyfoxx"
agentkalaw said:
From the crombi-kk thread:
"For those of you suffering long boot times, You may want to check out this xPosed module
[XPOSED] Xposed Media Scanner Optimizer
http://forum.xda-developers.com/xposed/modules/xposed-xposed-media-scanner-optimizer-t2942609
I was able to reboot in about 1 minute.
Note: you may get the message "unfortunately process media scan has stopped" - But just click okay a couple of times and it will go away.
Cheers
tyfoxx"
Click to expand...
Click to collapse
Thanks, I had actually seen that recently and applied to my phone, but ironically the woeful startup has prevented me from applying to the tablet. Am rebuilding now after applying F2FS to the data partition, hopefully applying the media scan optimiser will help reduce bootup times.