yashsingh1/xdaforums huggingface dataset:
[Galaxy S II General] titanic_fanatic:
Just a word of caution to everyone using philz latest 6.07 cwm recovery. There is a know issue where the update-binary has now been updated as of kk and the recoveries built with kk like the new philz 6.07 are now giving assert errors (error 7).

There are two ways to fix this:

1) Revert to the older 6.01 version of philz.

2) extract the updater-script from the rom zip file, delete the assert lines and replace the old updater-script with the new one.

If you're new to all this, or consider yourself inexperienced, I recommend you go with option 1 and revert to the older philz as it's a less risky method of doing things ;)
[Galaxy S II General] titanic_fanatic:
Here's the link to the older philz 6.01. You can use either the 6.01.0 or 6.01.2.

http://d-h.st/users/philz_touch/?fld_id=29076#files
[Galaxy S II General] slushee:
I consider myself inexperienced so I will ask the question. I'm using your "Philz Touch Recovery 6 (CWM 6.0.4.5) compatible with CM10.1/CM10.2/CM11.0" from the Original Post, does that mean I should revert to an older recovery or am I safe to continue flashing your ROM's as is.

EDIT - I just checked my files and i see that i downloaded "philz_touch_6.01.2-celoxhd". CWM About also shows PhilZ Touch 6 Build 6.01.2 base v6.0.4.5. I will assume I'm safe to continue flashing your CM 10.2's.
[Galaxy S II General] titanic_fanatic:
Yes, your still safe as your on a version lesser than the 6.02 in which this was implemented.
[Galaxy S II General] titanic_fanatic:
So I'm thinking about symlinking the system dalvik cache to /system/dalvik-cache since there is 1GB total space and only about half is used up for system apps and files. Currently our cache only has 100MB and system apps are fighting for space in the dalvik-cache. I'm not sure how much more space is needed, but will find out after some testing.

Is there any opposition to this? It means the cache partition essentially becomes unused. I can't see a drawback unless it starts to eat up the whole partition but I don't think that will be the case as I've only moved a handful of apps to the data partition to fix this currently.
[Galaxy S II General] Socim:
I find the dalvik cache at /data/dalvik-cache in cm11 and it is very large especially in art mode. I managed to dexpreopt system apps and it seems help, I am not sure.

Also there is another 126MB can be used, mmcblk0p27.
[Galaxy S II General] formercontra:
Once I take out all the stuff I don't use, I'm only using ~375mb... If it helps performance, then I'm all for it.
[Galaxy S II General] slushee:
Just an update to the ongoing saga of my foray into Cyanogenmod:

Backed up my solid CM10.2 dated Dec 1st and downloaded your Dec 31st version.

As expected i had a couple Force Closures during install, and rebooted wiping the Dalvik cache. I had to do this 3 times after installing a few apps each time.

After the 3rd time, everything seems running rock solid. I am still missing my VM notification LOL but everything else worked. I initially had my text message tell me that it couldn't send and it would re-try when the service became available. This was after i was switching back and forth from H+ to LTE and running speed tests.

A quick reboot fixed the SMS problem.

So, I am still stumped why I dont get the VM notifications like the rest of you. Its a very very small complaint. I am very happy with your work Titanic. I was going to post a logcat of the VM issue but i can't seem to get a logcat smaller then 1MB, and xda and pastebin both wont allow anything greater then 500 kB.

The FC's during install are a little nerve wracking for us noobies, so I for one be all for moving the dalvik cache to the larger partition. After i've installed everything i'm looking at 694 MB used with 1.3 GB free Internal Storage and 440 MB used with 294 MB free RAM.
[Galaxy S II General] irenek:
I pushed new Dec 31 build to my phone and keep getting FC errors on every restart. I've done Wipe Dalvik Cache at least 5 times ...

I use PhilZ 6.01.2 version of recovery; Clean install; what is interesting - I'm getting "E:unknown volume for path [/sd-ext]" message on confirmation screen, but then, after confirming - "Dalvik Cache wiped"

Anybody else has this issue? Any advice is much appreciated :)

After reading the previous post I have a thought to confirm :) : should I wait until all my apps are back before Wiping the cache?

P.S. System does say "Android is upgrading"
[Galaxy S II General] titanic_fanatic:
Alright guys, the upload at androidfilehost.com is done. I still need to update the files in the xda download section, so just use the links below for now:

Download

Please re-download both files as they have both been updated ;)

*** For anyone interested, I'm also posting my new ParanoidAndroid build today if you want to hold off on this one ***
[Galaxy S II General] irenek:
Thanks! I will sure let you know if it's compatible.

First link doesn't work yes (file not found); gapps link is good

EDIT: Both are good now
[Galaxy S II General] titanic_fanatic:
There was a problem with that upload, I had to re-upload. I've updated the links in my previous post and the OP and tested both ;)
[Galaxy S II General] slushee:
Seeing as I just installed the the ROM right before you updated it, would it be worth the trouble to reflash or can I keep running it if there are no problems?

One other question, can i update CWM to "philz_touch_6.07.9-celoxhd.zip" while still using the CM 10.2 that i flashed on version 6.01.2?
[Galaxy S II General] titanic_fanatic:
If you are having no problem with FC's, you don't need to update ;) Nothing has changed other than the location of certain system apps.
[Galaxy S II General] titanic_fanatic:
ParanoidAndroid for SGH-I757M Released

Alright, for those of you who are waiting for my PA build, it's up. This is a JB4.3 build of ParanoidAndroid and I have added back the performance settings from CM to allow changing the governor and io scheduler as the defaults have sucky performance.

[ROM][PA-JB4.3][RECOVERY][KERNEL][DEV][SGH-I757M]UNOFFICIAL CM10.2 For Bell SGH-I757M

Enjoy!!!
[Galaxy S II General] Socim:
AFAIK, the simple way to relocate dalvik-cache is using init script, google and there are many.

And please take a look at my filesystem usage, I think maybe I should mount the 126MB preload partition as cache and symlink app-libs to old cache partition, and leave dalvik cache in DATA.
[Galaxy S II General] jreay:
Hey TF,

Thanks for all the work your doing
[Galaxy S II General] Socim:
I will try to modify init.target.rc with below code:

mkdir /app-lib 0771 system system
wait /dev/block/mmcblk0p26
mount ext4 /dev/block/mmcblk0p26 /app-lib nosuid nodev barrier=1
wait /dev/block/mmcblk0p27
mount ext4 /dev/block/mmcblk0p27 /cache nosuid nodev barrier=1

Also for init.rc:

exec /system/bin/sh /init.applib_reloc.sh
mkdir /data/app-lib 0771 system system
symlink /app-lib /data/app-lib

init.applib_reloc.sh:

#!/system/bin/sh

export PATH=/system/bin

if [ -d /data/app-lib ]; then
cp -rf /data/app-lib/* /app-lib
rm -rf /data/app-lib
fi

I am not sure if it works.
[Galaxy S II General] m54:
Installed your latest Dec31 build with the new packaging, no FC's during install, running smooth so far after restoring everything.
[Galaxy S II General] irenek:
I installed the updated ROM and can confirm it works without FC and compatible with version 6.01.2 of PhilZ recovery.

Thanks TF! Appreciate all the work you have done! :)
[Galaxy S II General] titanic_fanatic:
Awesome, It's excellent that they are compatible. That means I don't have to manage two sets of downloads ;)
[Galaxy S II General] titanic_fanatic:
I see that your cache partition has a generous 300MB and is barely used. Are your system apps not cached to the cache partition? Mine are and they fill up my tiny 100MB cache.

To your post with your configuration, I'm going to try something similar and will let you know if I am successful ;)
[Galaxy S II General] danrobi:
Is it just me or battery life is better with the dec31 build? I got 2 and a half hour screen on time and still had 30% juice left. :victory:
[Galaxy S II General] manfromgta:
Its not just you. TF tweaked the kernel for latest ROMs to improve battery life. It seems to have worked quite well. :)

Sent from my SGH-I757M using Xparent Cyan Tapatalk 2
[Galaxy S II General] titanic_fanatic:
It's not just you. With the changes I made to the kernel and how it charges, it seems to have had a side effect I was not expecting... better battery life ;) this is implemented in all of my kernels now ;)
[Galaxy S II General] danrobi:
Greatest inventions and discoveries throughout history where also made by accident. ;) Great work Titanic.
[Galaxy S II General] titanic_fanatic:
Alright, so I think I have tracked down and fixed the vibrator loading issue.

It seems that Google made a commit that broke the registering of char devices in some cases. They applied a fix to the char dev driver in their Google msm kernel, and that fix was not present in our kernel. I've added that fix to our kernel and have been testing a little. I have not yet lost my vibrator on boot. I rebooted 10 times in a row and usually this causes the vib not to load, but I never lost it.

For now, I'll call this fixed, but it still needs more testing from you guys.

Here is a link to the new kernel. You do as always need to take a nandroid backup, but this fix is like the other kernel fixes, you should just be able to flash it from cwm without wiping anything. The nandroid is only if something goes wrong.

DO NOT FLASH THIS ON MY OTHER ROMS, YOU MIGHT END UP IN A BOOTLOOP

If all goes well for a week or so, I'll add the fix to my repo so all the kernels can benefit from this.

boot-ONLY-VIBFIX-cm10.2-20140107.zip (5.8MB)

If you have a situation where the vibrator does not load, please send me your dmesg log to titanic.fanatic.xda@gmail.com.

To take a dmesg log, open your terminal and type the following:

This will place a dmesg.txt file at the root of your sdcard. Send that to my email so I can review it for errors ;)

On another note, I'm moving towards the new cache. I have it successfully mounting with an init.d so I know it works as I expected, but I need this to happen when the other partitions are mounted and before the system tries to create the dalvik cache. This should allow us to use unmodified gapps packages.

I'll be testing some things out with the init (not init.d) scripts as suggested earlier by Socim. I'll let you all know how that goes.
[Galaxy S II General] big_biso:
Hi TF,

I am on your latest full build 12/31 CM10.2. it has been running for 2 weeks rock solid. so far I noticed the following problem on my daily usage:

1- if i lose BELL signal for any reason like going in the metro, then I get out I do not get signal back until I disable and re-enable communication like flight mode on and off. BTW, on this topic I noticed signal bars or strength is weaker than it was before on stock but did not notice that I am missing calls or call drops.

2- Viber messenger loses sound after 5-6 minutes in call. you just hear static noise but the call is still on and the they are still hearing me on the other side.

3- lockscreen widget does not detect if I am using the widget or not and just lock. for example if you add a calculator widget on the lockscreen and start use it, even if you are clicking and 30 seconds passed the screen will shut again as if it was idle.

Thanks for all your hard work.
[Galaxy S II General] Socim:
Thank you, I have just realized the difference, I thought our internal partitions are identical before.

FYI, dalvik cache of cm11 is located in /data/dalvik-cache by default.
[Galaxy S II General] GrAt_On:
Issues so far

Only issue I have experienced so far is the screen randomly turns black 1-2 times a day. The lights on the bottom works, the sound even works, except there is no video display. Obviously, I had to reboot the phone. This is the only problem I have, great job and thank you very much on everything else especially the vibration fix! :)
[Galaxy S II General] formercontra:
Just tested and found out this is fixed in version 12.1.2013.
[Galaxy S II General] titanic_fanatic:
[MENTION=4896139]Socim[/MENTION], check out my latest kernel commit on both cm-10.2 and cm-11.0 branches. It's the commit that fixes this issue with vibration. I'm going to submit it as a patch to gerrit when I figure out how to do that since the instructions on cyanogenmod's wiki was vague about submitting kernel patches.
[Galaxy S II General] Socim:
init.target.rc

wait /dev/block/mmcblk0p27
mount ext4 /dev/block/mmcblk0p27 /cache nosuid nodev barrier=1

#Relocate applib
mkdir /app-lib 0771 system system
wait /dev/block/mmcblk0p26
mount ext4 /dev/block/mmcblk0p26 /app-lib nosuid nodev barrier=1
exec /system/bin/sh /init.applib_reloc.sh
symlink /app-lib /data/app-lib

init.applib_reloc.sh:

#!/system/bin/sh

export PATH=/system/bin

if [ -d /data/app-lib ]; then
cp -rf /data/app-lib/* /app-lib
rm -rf /data/app-lib
fi

I have just tested and it is not enough, because there is no related selinux policy so our system denied the app installer's access to that location. So I think I should add this line to file_contexts, but haven't test yet.

/app-lib(/.*)?	u:object_r:apk_data_file:s0

Otherwise, I think mount it directly to /data/app-lib should be all right if I can do a clean installation or move those files via aroma file manager.

FYI, I found there is also a line for dalvik-cache:

/cache/dalvik-cache(/.*)? u:object_r:dalvikcache_data_file:s0

---------- Post added at 03:11 AM ---------- Previous post was at 03:05 AM ----------

Hi [MENTION=4859152]titanic_fanatic[/MENTION], can you please let me know what is the issue with vibration? I haven't read through all the posts in this thread.

---------- Post added at 03:19 AM ---------- Previous post was at 03:11 AM ----------

Maybe I can split init.applib_reloc.sh to two files like below, so I will be able to mount it directly:

#!/system/bin/sh

export PATH=/system/bin

if [ -d /data/app-lib ]; then
mv /data/app-lib /data/app-lib-tmp
fi

wait /dev/block/mmcblk0p27
mount ext4 /dev/block/mmcblk0p27 /cache nosuid nodev barrier=1

#Relocate applib
exec /system/bin/sh /init.applib_reloc_1.sh
mkdir /data/app-lib 0771 system system
wait /dev/block/mmcblk0p26
mount ext4 /dev/block/mmcblk0p26 /data/app-lib nosuid nodev barrier=1
exec /system/bin/sh /init.applib_reloc_2.sh

#!/system/bin/sh

export PATH=/system/bin

if [ -d /data/app-lib-tmp ]; then
cp -rf /data/app-lib-tmp/* /data/app-lib
rm -rf /data/app-lib-tmp
fi
[Galaxy S II General] formercontra:
Thanks! Glad to be of help. This is the specific link for the zip, & flashing that will install the app and the binaries.

http://download.chainfire.eu/351
[Galaxy S II General] bijon440:
Thanks for those scripts, the worked as the should. On another note, the phone never goes to deep sleep at all, and one of the reasons is my launcher. And gsam is saying the battery drain has a lot coming from "kernel (android os )" and my battery is pretty rough. Everything is greenified and minimal usage aside from Gmail syncing. Everything else is turned off from sync. Thanks guys! Busy thread lately, I love it!
[Galaxy S II General] RukusX7:
Reboot after every charge. It's the process that keeps your phone awake while charging . it's supposed to turn that wakelock off but it won't.
[Galaxy S II General] titanic_fanatic:
Rebooting after charging only fixes the vbus_present wakelock. The Kernel (Android OS) wakelock is comprised of many services that I need to sort out to see if I can disable any of them without adverse effects. I count 76 different processes under Kernel (Android OS) wakelock. I'm sure many of them don't need to be running and that could save some juice. I'll see what I can find out about these 76 processes ;)
[Galaxy S II General] FuryriderX:
Just a note, seems that most of the times when I get the black unlock screen I have a notification waiting, and the LEDs are flashing. Lots of other times it just comes on like normal.
[Galaxy S II General] bijon440:
And if anyone's interested I haven't had an issue using the volume rocker wake. Screen has come on every time using the volume buttons.
[Galaxy S II General] Zippy Dufus:
ONDEMAND = better battery stats

Attached are a couple of screen shots:

Battery statistics with ONDEMAND CPU governor and device was idle.

CPU Spy - now deep sleeping. (Not shown is 36% at highest 1512 MHz)

This is much better that my previous post with INTERACTIVE governor.

== edit ==

Wow! This fixed my Talkatone issue noted in my previous post too.

.
[Galaxy S II General] jonnyjb:
That is some awesome numbers, what I/O scheduler are you using?
[Galaxy S II General] RukusX7:
My notifications lights won't stop flashing after I've cleared my notifications. They did stop after some time. Other strange issue is they worked without being enabled. Bln has no effect.
[Galaxy S II General] titanic_fanatic:
It's strange, the bln commit that I applied was for cm10.1 and required a patched liblights which was already in the repo. Changing the values that control bln located in this dir produced strange results.

/sys/class/misc/backlight notification

blink_control controls the bln it causes it to go on when the value inside is 1 and off when it is 0. blink_interval controls the interval at which the light is on and then off, values inside are separated only by a space and are in milliseconds. blink_timeout is the amount of time in seconds that the bln will be active.

Since the liblights was already a patched version, I'm wondering if bln was implemented in cm10.2 natively. Changing the blink_interval works if you change the interval, then change the value in blink_control to turn it on, then the interval works, but if I send a text, the interval gets reset to 1000 1000 (1 sec on, 1 sec off). This heads me to believe that it was implemented natively and that applying the bln commit may be working against whatever is implemented natively.

I'm running a fresh build to test this theory. I'll let you know how it goes.
[Galaxy S II General] Tronith:
Hey guys. This isn't about this room it'd just generally what has happened for the past bit. My storage says it's full always. I removed everything that I could. Pictures backups music everything, but my storage is alway 0kb of 11gb free. In addition my camera corrupts many images. Now I do have versions that I can send out and show if an example is needed. How do I wipe the phone so that there isn't any error from the Storage? (yes I did go through the entire phone and deleted any folders that were left over from old apps)
[Galaxy S II General] bijon440:
I had this happen a ffew times and I believe it was because of nandroids actually. Cwm is supposed to clear any unused backup data when you take a new nandroid, but I had so many saved to my SD card that wasnt being recognized it was hard to track down what the space hog was. If you have a whole whack of backups try deleting a few old ones, they take up a lot of room.
[Galaxy S II General] Tronith:
As I said I deleted a lot of them but it still says 0kb of 11gb free. I deleted everything, but what I am not sure. Is there a way to format the phone clean and then reinstall the roms on a clean drive? Because when we delete cache, system, and data, a lot of leftovers stay
[Galaxy S II General] Zippy Dufus:
row - this was the default upon factory reset/flash.
[Galaxy S II General] titanic_fanatic:
I also had a similar issue at one time. I backed up what was important to me onto my computer. Formatted both my internal and external sdcard. I then downloaded the original stock GB from Samsung and factory reset it right to how it came from the store. Then I rooted and flashed my custom Rom and all was well after. I think this is the best way to "clean" the device since the download from Samsung will replace all of your partitions and not just /system and /data like the custom ROM's do.

Make sure you do the backup and format of your sdcard's though. It's important that gets done before you flash the Samsung Rom.
[Galaxy S II General] RukusX7:
Anyone listen to music using the headset yet? It sounds like your listening to only the left and right channels of a Dolby prolific stream. There is no centre and it sounds like you're underwater

---------- Post added at 04:08 PM ---------- Previous post was at 04:06 PM ----------

Unless its my headset. Gonna test more.
[Galaxy S II General] titanic_fanatic:
Yeah, I use it everyday at work. I use poweramp and have no issues here. What player are you using?
[Galaxy S II General] RukusX7:
I was trying to watch a movie with xbmc and then listen to music on tunein. I use tune in everytime when I'm in my truck I'm about a half hour from my truck now, I'll test when I get into it.
[Galaxy S II General] titanic_fanatic:
Haven't used tunein for a while although I still have it installed. I'll try it and let you know if I get the same.

EDIT:

So I tried tunein, and audio quality was normal. Did you try changing the stream? Sometimes you get a bad stream and switching fixes the problem.

Have you tried playing an mp3 with a music player? Does that work?
[Galaxy S II General] titanic_fanatic:
I was able to get a response from car vs driver of TeamChopsticks. He tells me that the bln patch is not complete, so I will have to fix that. There is a workaround, open the following file in a text editor and change the value to 0 when the bln sticks, this will turn it off.

/sys/class/misc/backlight notification/blink_control

You also have the other option of turning it off until I can fix it.

car vs driver also gave me a good idea of what the issue could be with the unlocking of our display. That's where my focus is right now.

Haven't figured out the vibrator issue yet, but still looking into that as well.
[Galaxy S II General] titanic_fanatic:
[MENTION=4896139]Socim[/MENTION], I thought about it a bit and think we're looking at this from the wrong angle. I think init scripts are probably unnecessary although the seandroid perms would most likely still need to be added. In the next few days, I'm going to try adding the following to my fstab.com file:

You could probably do the same. I will just include a blank placeholder file in /system/dalvik-cache inside the zip so the folder extracts so that it's ready for binding when everything gets mounted.

I'll let you know how that goes ;)
[Galaxy S II General] Socim:
Thanks, I'll also give it a try.
[Galaxy S II General] Socim:
I don't know why but it won't mount for me if I only put an entry in fstab.qcom. However, the workaround in my previous post works.
[Galaxy S II General] titanic_fanatic:
That's awesome. I also re-thought about using the system partition. It probably shouldn't be mounted rw always, so I'm going to have to try the mmcblk0p27 and hope that 127MB is enough, or I will still have to do a bind mount using a script in the same way you did.

No, unfortunately it doesn't. This commit fixes a bug introduced by Google that would cause certain devices to register with the char dev minor 1 and that driver does not mark 1 as used so the next device that tries to register (the vibrator in my case) fails to load as it is also assigned a minor of 1 and gives a cannot create duplicate filename /char/dev/10:1

This seemed to happen randomly.
[Galaxy S II General] RukusX7:
Had a wake lock issue involving Audioout_2 causing my phone to discharge quicker than it could even charge. Looked up some solutions and one was for a galaxy s 3 to place it on vibrate and reboot the phone. So I updated the kernel first, then followed the directions. I went to bed at midnight with 91% battery, woke at 630 and I had 89%. 2% drain over 6 hours is damn great.

I just wanted to share if anyone else experienced severe battery drain or wake lock issues.
[Galaxy S II General] slushee:
Is this safe for your first CM 10.2 build dated Dec 31st that does not have the re-worked GAPPS package, and using CWM 6.01.2?
[Galaxy S II General] titanic_fanatic:
Yes, it's safe ;) Make sure you take a nandroid though just in case.