Android Enthusiasts

« first day (855 days earlier) ← previous day next day → last day (4095 days later) »

4:56 AM

haha, yeah.

Well, I waited 9 minutes this time, still on the boot logo. I also tried de-odexing all of /system/framework, still on the boot logo. So, if anyone knows anything about de-odexing, hit me up. :D I'm de-odexing my android.policy.jar (works great--classes.dex inserted) on an odexed ROM, but every time I replace it, my phone (GSIII) gets stuck on the boot logo. :(

7 hours later…

Izzy

12:20 PM

@IbrahimKhanJadoon Well, I have no experience with deodexing -- all I know about it is pure theory to me...

6 hours later…

Ibrahim Khan Jadoon

6:34 PM

@Izzy No worries. I think I may have found my answer (in a warning present in dsixda's kitchen tool): if you de-odex the framework, you have to de-odex /system/app, too! So, I think you can only de-odex SystemUI.apk (and a few others) individually, but if you de-odex framework, you have to de-odex the whole ROM (which is just /system/framework and /system/app)! I shall attempt and report back. :D

Izzy

@IbrahimKhanJadoon Oh -- OK, that might keep you a little busy :)

I just did the craziest thing ever: My new device arrived from Amazon (LG Optimus 4X). So I unpacked, charged, rooted -- and only then started to take a closer look LOL Am I a nerd now? #D

1 hour later…

Stack Exchange

7:59 PM

Q: Merge 'storage-full' to 'insufficient-memory'?

I just encountered the storage-full (x9) tag. Its questions seem similar to those tagged insufficient-memory (x16). As Android's corresponding error message mostly reads "insufficient memory...", I'd suggest to merge the former to the later, and making storage-full a synonym then.