• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [CDMA] Get ready for OTA's!

Installed xposed via recovery and now low space bug :(
uploadfromtaptalk1425875741332.jpg


Sent from my XT1031 using Tapatalk 2
 
Rolled back to 4,4,4 using my TWRP backup, didnt like Lollipop without xposed !
starkraving said:
Its not a bug guys, its a warning for your system partition being low on memory.
Click to expand...
It is a bug when you have more than 2GB of free space and someone tells you that you need minimum 250mb of free space and you are running out of it :P .
 
hitesh123 said:
Rolled back to 4,4,4 using my TWRP backup, didnt like Lollipop without xposed !

It is a bug when you have more than 2GB of free space and someone tells you that you need minimum 250mb of free space and you are running out of it :p .
Click to expand...
It is telling you you need 250mb free in system, not on your SD card. System storage is only just so big. Did anyone try the new Xposed installer and apk releases yesterday?
 
amarc78 said:
It is telling you you need 250mb free in system, not on your SD card. System storage is only just so big. Did anyone try the new Xposed installer and apk releases yesterday?
Click to expand...

Yes , that error came only after trying yesterdays update from XDA thread. same error comes without even installing single app on phone, no data no apps nothing at all.
and in Moto G all 8 GB is shared between app and data.
 
hitesh123 said:
Yes , that error came only after trying yesterdays update from XDA thread. same error comes without even installing single app on phone, no data no apps nothing at all.
and in Moto G all 8 GB is shared between app and data.
Click to expand...
It happened to me with the previous Xposed zip and seemed to only happen if I didn't wipe dalvik and cache after flashing it.
 
amarc78 said:
It happened to me with the previous Xposed zip and seemed to only happen if I didn't wipe dalvik and cache after flashing it.
Click to expand...
This worked, thank you :) Here are the exact steps I used to install Xposed for Lollipop:
  1. Download the zip and apk from here
  2. Reboot into recovery
  3. Flash zip
  4. Wipe cache
  5. Wipe dalvik cache
  6. Reboot
  7. Install apk
I have GravityBox again, woo hoo!!! :)
 
I am still wondering about these partitions. I did not update mine and the only issue I have so far is the screen glitches a bit while booting. It glitches on the splash and the boot animation until Android is booted and I turn the screen off once. After that, no problems at all.

So, what advantage/disadvantage is there to updating the partitions? Does the glitch go away if you update? Anything good at all come from updating?
 
starkraving said:
Yeah updated partitions but the "ripple" is only present in recovery. Disabling adaptive brightness in settings took care of it everywhere else.
Click to expand...
See, I think the partition update may be causing the ripple in your recovery. Does yours ripple on the splash and boot animation when booting?
 
SuperR said:
I am still wondering about these partitions. I did not update mine and the only issue I have so far is the screen glitches a bit while booting. It glitches on the splash and the boot animation until Android is booted and I turn the screen off once. After that, no problems at all.

So, what advantage/disadvantage is there to updating the partitions? Does the glitch go away if you update? Anything good at all come from updating?
Click to expand...
Well from my testing to modem patch has done some good. I was typically only at -90/-98dbm before the update...now I'm at -68/-80dbm so that's significant. I also noticed my PRL changed after having the same one since purchase.
 
SuperR said:
This worked, thank you :) Here are the exact steps I used to install Xposed for Lollipop:
  1. Download the zip and apk from here
  2. Reboot into recovery
  3. Flash zip
  4. Wipe cache
  5. Wipe dalvik cache
  6. Reboot
  7. Install apk
I have GravityBox again, woo hoo!!! :)
Click to expand...
Glad to hear. I just got it installed to. Hopefully, they make some good advancements with further development. Only 78mb system space free and no low storage warning. I'm pretty sure the dalvik/cache wipe after flashing has something to do with it.
 
I have 2 phones, one I updated with the OTA zip and the other with SuperR's ROM and partition updater, and they both have the flickering issue. I had the issue when I installed a Brazilian Stock 5.0.2 ROM for XT1032 from XDA and had the same flickering so I'm not sure about this flickering problem. I don't see anything to point a finger at. I'm wondering if we just need a graphics driver update. It wasn't updated with the OTA, was it?
 
starkraving said:
Only in recovery. Not present at all elsewhere.
Click to expand...
I wonder if I make a new flashable that updates everything except the bootloader if it would fix all the glitching. It's possible the new bootloader is causing the glitch in recovery and that the other partitions fix the glitch everywhere else.
 
amarc78 said:
I have 2 phones, one I updated with the OTA zip and the other with SuperR's ROM and partition updater, and they both have the flickering issue. I had the issue when I installed a Brazilian Stock 5.0.2 ROM for XT1032 from XDA and had the same flickering so I'm not sure about this flickering problem. I don't see anything to point a finger at. I'm wondering if we just need a graphics driver update. It wasn't updated with the OTA, was it?
Click to expand...
Hmmm. Have you disabled the adaptive brightness?
 
You must log in or register to reply here.
Back
Top Bottom