[Rom][3.4 Kernel][4.4.4/5.0.2] LiquidSmooth [21st February]

[asefjamil]

I trying to fine out what I changed to get a star in my statusbar running latest build.

may be u have turned on the screen saver through "action & utilities" widget. But sorry can't say the solution as I had to flash the rom for an experiment, the star disappeared automatically!

 

[secretmetalsinger]

I trying to fine out what I changed to get a star in my statusbar running latest build.

lol just press volume keys up and set the priority to all

 

[andy hall]

I was also thinking to revert but rather only moving App to sd-ext was better solution for me to keep this white theme

So, just for a giggle I tried the Dalvic move on CM12 and exactly the same results, and have reported it on their too.
This is really confusing as diskinfo is reporting a reduction in the used space on the SD-EXT but only after rebooting the device some time after the Dalvic has already been moved.
So fo the time being I am going to install 2015-01-24 and install less rubbish.
This is because I like the look and feel of this rom.

 

[pbazw]

latest build

I've running the latest since release and yesterday is started rebooting and sometimes just shutting down and not booting backup strange.

 

[zybach]

Memory leak still present.still can't play games w/o it force closing after 3-4 mins :'(

 

[pbazw]

update

I've running the latest since release and yesterday is started rebooting and sometimes just shutting down and not booting backup strange.

not sure what took care of problem cleared cache and haven't had a reboot.

 

[andy hall]

Nah. I have tried 3/4 times to move dalvik cache on both kind of flashing. So finally I came to a point where I am only moving my application to SD-Ext. Found no lagging yet. Running good.

Looking in the M2SD debug it has a line stating the Device is S-ON (HBOOT attached)
Also after the reboot, the second after dalvic is moved that does the damage, it appears there are a lot of messages about bot being able to move all items from the source.
Have had a suggestion to check the SELinux status annd make sure it is not set to "Forced".
Going to get logs on an older non LP rom now to see the differences
If anyone has any suggestions about updated FW, I can flash anything as have no problems am in UK for location ref.
I am using 4EXT for the recovery, 1.0.6 RC3 and Smartflash is not enabled.

 

[rolay07]

Sorry if it is already answered, but I've installed this rom (coming from vipers 5.2) and I can't make cell calls (it says call cannot be started, or something like that)

Also tried unorom, same result.

Is it a lollipop bug ?

(btw at buttons customization you might add "force close" to longpress back button, and toggle flashlight for longpress any button).

The rom is awesome except the gsm call bug i've experienced so far with the lollipop roms.

 

[andy hall]

When I try to do the build for 2015-01-24 this is what I am seeing on the initial stages.
This is showing many more errors than previous builds.
Any ideas?

 

[czguy]

When I try to do the build for 2015-01-24 this is what I am seeing on the initial stages.
This is showing many more errors than previous builds.
Any ideas?

I saw same prompts, however, the ROM runs very smoothly for me.

 

[andy hall]

I saw same prompts, however, the ROM runs very smoothly for me.

Agree, the Rom is excellent. Excellent work by LS team and Sajito.
Only issue I get is moving Dalvick cach was just wondering if these prompts could be an indicator to folder issues later on.
Think I might be reaching a bit.

 

[Sajito]

When I try to do the build for 2015-01-24 this is what I am seeing on the initial stages.
This is showing many more errors than previous builds.
Any ideas?

Don't worry about that, the rom will run fine anyway.

Agree, the Rom is excellent. Excellent work by LS team and Sajito.
Only issue I get is moving Dalvick cach was just wondering if these prompts could be an indicator to folder issues later on.
Think I might be reaching a bit.

Thank you, but I only changed some some lines and some file names.
Rom is all by LS team and device/kernel trees are from ivanich, not from me.

I didn't experience issues with moving dalvik, but it's been some time since I did it. If possible not to move dalvik cache, because it'll slow down app starts and it might get frustrating.

 

[andy hall]

Thank you, but I only changed some some lines and some file names.
Rom is all by LS team and device/kernel trees are from ivanich, not from me.

I didn't experience issues with moving dalvik, but it's been some time since I did it. If possible not to move dalvik cache, because it'll slow down app starts and it might get frustrating.[/QUOTE]

I can cope with the odd bit of lag, used to have a desire running KitKat roms, lag PAH.
I have one last build to do and then I think I might have the root cause nailed.
I have a really nast feeling that it is down to 5.0.2 breaking a M2SD script and causing a duplication of the Davilk move (looks like it to an enthusiastic amateur anyway), this in turn causes an issue on free memory identification.
Move the Dalvick back and it all looks good.
The hardest thing is there are no log errors in M2SD since installing 1.29 HBOOT.
happens the same on CM12 Roms too I hasten to add.
I think this is a sensible question, is it time to do a logcat on this, and would it help?

---------- Post added at 08:26 PM ---------- Previous post was at 07:29 PM ----------

Well another theory bites the dust.
It is not the move to 5.0.2.
The only other thing I am aware of it the inclusion of the Theme Engine which would be rediculous.
ho hum, looks like to move forward I shall have to limit the number of installed apps, maybe learn about logcat before giving up.

 

[hinxnz]

I can cope with the odd bit of lag, used to have a desire running KitKat roms, lag PAH.
I have one last build to do and then I think I might have the root cause nailed.
I have a really nast feeling that it is down to 5.0.2 breaking a M2SD script and causing a duplication of the Davilk move (looks like it to an enthusiastic amateur anyway), this in turn causes an issue on free memory identification.
Move the Dalvick back and it all looks good.
The hardest thing is there are no log errors in M2SD since installing 1.29 HBOOT.
happens the same on CM12 Roms too I hasten to add.
I think this is a sensible question, is it time to do a logcat on this, and would it help?

---------- Post added at 08:26 PM ---------- Previous post was at 07:29 PM ----------

Well another theory bites the dust.
It is not the move to 5.0.2.
The only other thing I am aware of it the inclusion of the Theme Engine which would be rediculous.
ho hum, looks like to move forward I shall have to limit the number of installed apps, maybe learn about logcat before giving up.

Dalvik2SD
I made this Dalvik2SD script for you and whoever else that wants to use it.

It will move your Dalvik-Cache to SD-EXT.

Just call the script in Terminal Emulator with SU permission.
eg. Place Dalvik2SD.sh on root of SDcard and enter code below:

su
/sdcard/dalvik2sd.sh

Warning: Once Script has completed your device will reboot and will take some time because Dalvik-Cache has to be re-built.

After this has been done, don't wipe dalvik-cache in recovery when updating ROM just delete the contents of /sd-ext/dex-cache/ then reboot into recovery, you can do this by calling Dalvik2Delete.sh in terminal:

su
/sdcard/dalvik2delete.sh

Download
Dalvik2SD.sh - https://mega.co.nz/#!vZFg0BRY!K12yqNHI-x3bg89YC1AOkEpr_rSPlBqkdlpPbTSFxac
Dalvik2Delete.sh - https://mega.co.nz/#!TUMx2ZhR!qls6B-e1DSEgkm2Q0QDcX9BQZ92tVi9PNmFGmhZHGi8

 

[SlideR270295]

Will moving dalvik to sd make the device faster, or just to free up space from internal storage ?

 

[hinxnz]

Will moving dalvik to sd make the device faster, or just to free up space from internal storage ?

Read some previous posts but best to judge yourself I guess.
Edit: Easy to revert back, just enter code in terminal:

su
rm -rf /sd-ext/dex-cache
rm -rf /data/dalvik-cache/arm
reboot

 

[tom0769]

Will moving dalvik to sd make the device faster, or just to free up space from internal storage ?

In general, moving internal things to external sd card will never speed up things since access to sd card is slower than access to internal memory.

 

[andy hall]

In general, moving internal things to external sd card will never speed up things since access to sd card is slower than access to internal memory.

I have reinstalled 2015-01-24 and added the dalvik script. It seems to be working like a charm. The phone does seem to get a bit bogged down after doing a lot of installs on the trot however a reboot all is good. It is always difficult to assess lag as I use Greenify a lot and that means the apps are not cached to start with.

Sent from my Sensation using XDA Free mobile app

 

[andy hall]

Read some previous posts but best to judge yourself I guess.
Edit: Easy to revert back, just enter code in terminal:

su
rm -rf /sd-ext/dex-cache
rm -rf /data/dalvik-cache/arm
reboot

Am up to 90 apps and no issues so far script doing well.
Well done. :thumbup:

Sent from my Sensation using XDA Free mobile app

 

[hinxnz]

In general, moving internal things to external sd card will never speed up things since access to sd card is slower than access to internal memory.

If you want to compare app startup times, use adb with the code below.

adb shell logcat | grep Displayed

Note: You will have to probably open apps several times and calculate the average for the apps you test including the apps initial startups.

Am up to 90 apps and no issues so far script doing well.
Well done. :thumbup:

Sent from my Sensation using XDA Free mobile app

Sweet, glad it helped.