yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] #illidan:
The 1st point is exactly what is happening.

Your 3rd & 4th points are completely correct & I'm not asking for backup of 2 .android_secure files, just the one on the internal storage that doesn't get backed up at the moment.

Ok so if cwm can't detected then is it possible to directed cwm as to where the .android_secure folder is. For example if there are two or even one of those folders then maybe there could be an option under backup to select the .android_secure folder that needs to be backed up so all the apps gets backed up & this would obviously just back up one .android_secure folder & there would be no problems with restoring the back up as well but I don't know if this would conflict with your third & fourth points as your the developer & not me.

The work round atm after searching for 2 hrs is that the sd card needs to be removed & then you need to manually mount /sdcard & nandroid, then only will .android_secure on the internal storage get backed up.

Sorry for all this rambling & for taking up so much of your time
[Galaxy S II Original Android Development] tolis626:
Gokhan,from what I gathered from what #illidan said,I think he is making a point.You could have four backup options instead of two,like "Backup to internal sd(with internal sd .android_secure)","Backup to internal sd(With external sd .android_secure)" etc.If it's possible,that's cool,because each time I backup the android_secure folder manually. :)
[Galaxy S II Original Android Development] johnbeetee:
I think Gokhan means: the main issue is compatability, because nandroid stores the full pathnames, meaning the backup would not be compatible, if used with another kernel (using standard nandroid)

but if this is a known fact, why not make sure .android_secure is in the right place? on your external sd...copy it manually before backing up or move all apps to internal storage before backing up
[Galaxy S II Original Android Development] #illidan:
I get what GM is saying & he is right but I was just wondering if anything could be done. If you create a back up you would expect the nandroid to restore no matter what happens & this is where compatibility comes in.
[Galaxy S II Original Android Development] gokhanmoral:
nandroid will restore .android_secure folder to the external sdcard...

and maybe I can create a CWM flashable zip in the backup folder for the .android_secure folder in the internal sdcard.

but then the restore operation will have 2 steps: nandroid restore then install int_android_secure.zip

and since I will make the script to mount the folder using block device directly flashing it will work in any kernel regardless of the mapping convention used in CWM recovery.

but it will take time. I am very busy again.

I was thinking about adding nandroid backup/restore for the 2ndROM and release 3.2.7 but I had no time to do that.
[Galaxy S II Original Android Development] tolis626:
Yep,that sounds cool. ;)

Do your work man.You have to make a living first,then cater for us.You have a nice project going on here,but don't apologize when your life doesn't permit you to work on this project.We will stay true and loyal even if you're away for some time,don't worry. :)
[Galaxy S II Original Android Development] Lady_Chloe:
Phone freeze

My phone completely froze, I rebooted it using the power button. The last_kmsg looks somewhat corrupt(??) but I am attaching it anyway. Version 3.2.6.4

I was just scrolling the homescreen when this happened.
[Galaxy S II Original Android Development] tolis626:
Look...You're right,it is kinda ****ed up.But since you have no specific problem(Can be a system crash,undervolting,you name it),it should fit better in the discussion thread,as do most of these I-have-a-problem-and-want-someone-to-solve-it-for-me posts.Don't get me wrong,I just have no better way of saying it.I have such problems too every now and then,but try to refrain from posting. :)

As for the last_kmsg...I don't think anyone can help you with that.It's...corrupted or something like that.The only normal part is where the bootloader restarts.
[Galaxy S II Original Android Development] ZVM75:
on firmware PARANOIDANDROID often get during a call "mobile network is not available" or reboot the phone.

Will see why this is happening in the file "last_kmsg"?

thanks
[Galaxy S II Original Android Development] JimboJoe:
Just got a SOD with 3.2.6.4 on CriskeloServanTeam V11 (Sammy LPW). Hope it helps!
[Galaxy S II Original Android Development] CamoGeko:
Sooo waiting on the restore from nandroid to 2nd ROM option! That's gonna rule all. :D
[Galaxy S II Original Android Development] gokhanmoral:
testing it now...

it takes a little more than a regular nandroid restore because of formatting 2ndROM data partition.

I saw some fallocate changes in n7000 fat driver.

I will try to create 2GB data file by using that (I am not sure if it is possible though) or we will have to wait 7-8 minutes more when doing a nandroid restore to 2ndROM.

and a reminder: kernel will be backed up but it is not going to be flashed back if you restore nandroid backup to 2ndROM.
[Galaxy S II Original Android Development] CamoGeko:
Yeah 2nd ROM data partition is huge... when I first set that up it was a bit of a mission. However, I wouldn't really care so much about how much time it will take to restore nandroid to 2nd ROM partition. The gains outweigh the negatives.

I've been waiting to get my CheckROM V6 backup restored for a while (simple because of OTG / MHL).

EDIT: Also, did you revert the WiFi driver for 3.2.6.4? Yesterday codeworkx posted a cm9 kernel with an old driver and it seems to fix that lockscreen issues people were having and some WiFi wakelocks.
[Galaxy S II Original Android Development] gokhanmoral:
no I did not revert the wifi driver. updating mmc part seems to fix (or at least make it happen rarely) the problem.

I had more problems with the previous driver, so I will try to keep this one if the lockscreen issue doesn't arise again with another change.
[Galaxy S II Original Android Development] michyprima:
you added lvm?!

sounds nice. I think I'm gonna experiment to merge the internal sd card with the external one, and have one partition.

(yeah yeah, I know the risks and I don't care :D)
[Galaxy S II Original Android Development] lambstone:
One for all and all for one. Let us know how it goes.
[Galaxy S II Original Android Development] michyprima:
@Gokhan, do you know any way to modify the internal sd card partition to a LVM partition?
[Galaxy S II Original Android Development] ShimaMiku:
When I load CM9 on my phone and replace the kernel with Siyah's awesome kernel, anytime I install anything from recovery, this is what my image looks like. Anyone know how to fix this?
[Galaxy S II Original Android Development] KennyLegend:
Still no wifi/lockscreen issues here GM since I flashed the test version a few days ago, on default hot plug mode. Also tried it on dual core for a while.
[Galaxy S II Original Android Development] gokhanmoral:
it is fixed in v3.2.7.1

I removed those images from the recovery.

lvm is for 3.3beta's :)

it's been years since I have configured lvm... for now Talustus is working on it and he managed to run it but there are some problems.

I did not have any time to contribute to his experiments.

he managed to use lvm with cache and merge it with preload but it did not work with system partition.

the main purpose is to merge system with preload (optional) to have 1GB system partition.

anyway.. v3.2.7.1 is up...
[Galaxy S II Original Android Development] Evollution:
I know how to underlock but the rest are new to me.. I never used ExTweaks..
[Galaxy S II Original Android Development] gokhanmoral:
sorry but I could not stop myself and updated wifi drivers to i9300 sources.

so, 3.2.7.2 is up.
[Galaxy S II Original Android Development] sinancetinkaya:
LOL

do both devices have the same chip ?
[Galaxy S II Original Android Development] shadowofdarkness:
It always reminds me why I love open source since I had the idea for LVM and suggested it to you then it actually happens! Thanks for that.

I have been trying and so far I can make the LVM partitions but on reboot you have not setup the system to scan for them and add then to /dev so I have to manually run "lvm vgchange -a y" to add the /dev entries.

Also everything is hard coded to use /dev/block/mmcblk0p* and I don't know how to change that, to actually use the new LVM partitions.

Looking forward to when you get time to finish working on LVM.
[Galaxy S II Original Android Development] Phistachio:
Something interesting that I've noted...

Came from CM9 29 build kernel with DSPManager confiigured. I started music, it was quite loud. Started configuring the settings (thus overwritting old settings), DSPManager stopped working.

I didn't pull off a logcat because it was something unexpected... GM, I recommend you take a look at that, I don't have time right now to flash/test/reflash siyah...
[Galaxy S II Original Android Development] Nerenye:
Flashed 3.2.7.2 Yesterday

cm9 0529

and got a big SOD while sleeping tonight wich sucked my whole battery(from 90 percent).

i couldn´d even start my phone had to get another battery

i hope you can fix these anoying crashes

alogcat log and last_kmsg attached
[Galaxy S II Original Android Development] edangel:
I think new wifi drivers is weaker than previous syiah..i dont get strong signal..using 3.2.7.2!3.2.6.4 was better...classic samsungs wifi modules as it was on gingerbread :D

But at least it works ok without problem :)
[Galaxy S II Original Android Development] vizdak:
Im having the same issue. But post it another thread.
[Galaxy S II Original Android Development] johnbeetee:
yep,

signal is weaker (at least it's reporting that)

and I think the connecting problem is back (not connecting sometimes)

must be embedded in samsung's code somehow...

...just hope this doesn't bring back the unlock-freeze again

(@GM : reverted back to test2 ver. (sdhci interface mod)...that one still flawless)
[Galaxy S II Original Android Development] JimboJoe:
Just got a SOD with 2.3.7.2, default profile, on CriskeloServanTeam 11.1 (LPW Sammy).
[Galaxy S II Original Android Development] swnt:
My wifi issues extended to constant connection loops in 3.2.6 so had to go back to 3.2.5 which had better signal as well.

I haven't had a chance to test 3.2.7.x extensively but wifi does seem slightly better than 3.2.6.x

I did move between them a few times to make sure it was only the kernel's wifi driver causing the difference.
[Galaxy S II Original Android Development] dandan_00000:
I've had no sod no battle drain since latest update and crashes. I'm using thebyani rom 4.3. Could it be compatability issue the issues I keep seeing I've not suffered.

Sent from my GT-I9100
[Galaxy S II Original Android Development] mathsmart:
No problems here on wanam 11.9

swagga baby
[Galaxy S II Original Android Development] Gammelgustav:
mDNIe negativ profile is really nice but what about waiting for the 4 clicks on Home instead of (how it is now) the Home button acting like a normal Home Click at the first click of the four?
[Galaxy S II Original Android Development] Entropy512:
I've heard that they supposedly have the same loading/unloading issue that I9100 Update4 had.

As to variations in signal strength - don't bother with such stuff unless you can find a definitive repeatable performance (transfer rate/latency) regression. Signal strength calculations and displays are always arbitrary.
[Galaxy S II Original Android Development] Nerenye:
same problem as yesterday.

SOD while I was sleeping

siyah 3.2.7.2

cm9 0530

last_kmsg. Attached

ps. :

can somebody please reply what's eventually the problem or if he/she can find some problems in the logs?

I can't read them as posted in general thread and i like to know if my logs were helpful ore only spam because there is nothing helpful in them
[Galaxy S II Original Android Development] bernard134:
after using USB OTG and remove the thumb drive, a bug will be trigger which cause wakelock = "USBunmounter" service keep draining the battery, is the firmware or siyah v2.2.7.2 fault?
[Galaxy S II Original Android Development] vBB:
I'm not sure if my problem is related to this topic or discussion thread, but I post it here and there:

How to change mDNIE setting at "/sbin/ext/tweaks.sh"

so they will not change to default after reboot?

For e.g., I change this (for more blue, because my screen is yellowish):

echo "132" > /sys/devices/platform/samsung-pd.2/mdnie/mdnie/mdnie/user_cb

to this:

echo "132" > /sys/devices/platform/samsung-pd.2/mdnie/mdnie/mdnie/user_cb

And after reboot, I still get the same what was first:

echo "132" > /sys/devices/platform/samsung-pd.2/mdnie/mdnie/mdnie/user_cb

How to change this permanently? Thanks for any help, regards
[Galaxy S II Original Android Development] MistahBungle:
1) This doesn't really belong in the dev thread, but, anywho...

2) Make a script in init.d with just this line in it which will run at boot time. Easiest way is to get Script Manager from Google Play & follow the "Guide To Init.d Scripts" here.

Any further questions, ask in the discussion thread
[Galaxy S II Original Android Development] crachel:
*MOD POST*

We're getting more and more reports from this thread. Like I've said previously, I'm subscribed and deleting posts basically my entire time I'm online. Part of the problem here is a lot of you guys that know better are being nice and answering questions, requiring more posts to be moderated.

I don't mind having a discussion thread and a development thread a la CM9, but we have to work together to keep them separate and on topic. The CM9 development thread might get a couple posts per day, while this one is getting 20 or 30 still. Just ignore or report the OT posts. and occasionally remind people of the discussion thread.

Thanks
[Galaxy S II Original Android Development] Phistachio:
To those who have 3.2.8 : how much RAM do you have displayed in "About Phone"?

I used to have 832MB, but now I have 799...

Checked build.prop, no changes in RAM amount or any RAM related entries.
[Galaxy S II Original Android Development] ggogolewski:
I have 799 too...
[Galaxy S II Original Android Development] PedroMRP:
I have 799 also.
[Galaxy S II Original Android Development] CamoGeko:
v3.2.7.2 was showing 832mb, now my phone shows 799mb as well. After flashing v3.2.8.
[Galaxy S II Original Android Development] dandan_00000:
Mine is showing 800

Sent from my GT-I9100
[Galaxy S II Original Android Development] mathsmart:
Me too

swagga baby
[Galaxy S II Original Android Development] Gammelgustav:
Yep 799 in "About Phone"

And 800 in TaskManager...

Where are my 23MB :D
[Galaxy S II Original Android Development] d3l1:
799Mb here, too

Sent from here using Tapatalk
[Galaxy S II Original Android Development] minidou-77:
I think the 799mb problem is enough reported ;-)
[Galaxy S II Original Android Development] CamoGeko:
Just turn your phone upside down...

I think your posts is more suited for this thread:

http://xdaforums.com/showthread.php?t=1658647
[Galaxy S II Original Android Development] tghandour:
Excellent suggestions mate specially number 1 for smooth screen back lighting transitions..

I also like your observations about CPU and percentual increase, they are worth discussing and waiting for GM comment on that :thumbup::)
[Galaxy S II Original Android Development] gokhanmoral:
Ram is 800 because I increased video buffer size a little. I hope that you will have smoother video playback.
[Galaxy S II Original Android Development] Phistachio:
Ah, alright! Does it also have an impact on gaming performance?

IF ANYONE IS STUCK IN THE BOOTLOGO OF THEIR ROM AFTER FLASHING 3.2.8, PLEASE DO A DATA WIPE
[Galaxy S II Original Android Development] CamoGeko:
Data wipe?? Surely going that far isn't necessary, probably just emptying the init.d folder and flashing Siyah again should be enough...
[Galaxy S II Original Android Development] Phistachio:
When I was stuck, I :

- Wiped cache

- Wiped Dalvik

- Re flashed the kernel

- Re flashed the ROM

Nothing worked. Only wiping data worked.

Although I forgot to try and reset ExTweaks profiles :o
[Galaxy S II Original Android Development] CamoGeko:
Yeah that could be it, however I always leave my settings intact when flashing new Siyah. Haven't had any issues so far.

Something wen't wrong there lol
[Galaxy S II Original Android Development] Phistachio:
Yup, maybe perhaps it was due to my undervolt... -50mV in the CPU and 900/950/1000mV in the GPU.
[Galaxy S II Original Android Development] CamoGeko:
Hmm... I think it was your ROM more than anything.

I have my undervolts even lower than that, -100mV CPU and 800/800/900 on GPU frequencies.
[Galaxy S II Original Android Development] Phistachio:
Well, prior of having that, I got a major system fore close. Everything was crashing. Rebooted, and BAM.

Woah, are they safe? Do they give you a considerable amount of added battery juice?
[Galaxy S II Original Android Development] karlesg:
Nice suggestion about auto brightness but i especially liked this one. :) I'd also want an outdoor mode quickly available, it could prove very useful under direct sunlight now in the summer. except different mdnie settings maybe it could be also combined with an extra gamma shift? +10 or +20 for example or user configurable?

And maybe it could be applied with a different key combo so that the existing "4 times home -> inverted mdnie" won't be lost.

"hold down home for 3 seconds -> outdoor mode" for example
[Galaxy S II Original Android Development] CamoGeko:
Visit my MagicConfig thread mate, don't wanna clutter gokhan's thread any more than it already is.

Sent from my 80GB CyanogenMOD 9 + Siyah ICS powered beast. Booya!!
[Galaxy S II Original Android Development] droidphile:
-About percentage rise of CPU, i guess it may require introducing a new variable all together. There exist something already which is sort of what you're talking about - it's freq_step(In conservative, ondemand and pegasusq). But it's a percentage increase w.rt policy maximum every time up_threshold is encountered. If a new symbol is to be introduced which replaces increase as a percentage of policy max to precentage of current_freq, it will do what you suggested.

- Regulators set to voltage of 800mhz while scaling up from a freq to 500mhz happens only on GB kernels. With ICS kernels, 500mhz uses it's own voltage - whether scaling up to it or scaling down to it.

- About home button multi click mapping to outdoor mode, (outdoor mode is +50 gamma shift if i'm right), if our rom supports mapping of home button double click to an app/activity, we can set the activity to run a script that toggles 0 gamma and max gamma. This is a work around from user space. Just an opinion.
[Galaxy S II Original Android Development] droidphile:
Here. From about line 145.

Code in GB was this

if (freqs.new == ARMCLOCK_500MHZ) {

regulator_set_voltage(arm_regulator,

s5pv310_volt_table[4].arm_volt,

s5pv310_volt_table[4].arm_volt);

}
[Galaxy S II Original Android Development] gokhanmoral:
I have uploaded v3.2.8.2 (reverted fs and block related changes)

today I will have my sgs3 (in an hour).

from now on, I will try to stabilize sgs2 kernel and there will be no experimental changes because my wife is going to use my device. any instabilities will give me headache :)
[Galaxy S II Original Android Development] karlesg:
you are right. a very simple script like

if [ `cat /sys/class/lcd/panel/user_gamma_adjust` = "0" ]; then

echo "+50" > /sys/class/lcd/panel/user_gamma_adjust

else echo "0" > /sys/class/lcd/panel/user_gamma_adjust

fi

can do the job. For "0" and "+50" someone can set his own preffered gamma shift values for indoor and outdoor.
[Galaxy S II Original Android Development] TheRplima:
I put this script in a text file and using ScriptManager I created a shortcut for it. Now I have one click outdoor mode widget.

thanks
[Galaxy S II Original Android Development] Frozenthunder:
Hey GM,

I think that I found a bug. Or at least it's some unusual behaviour. Using 3.2.8.2

When I wipe the cache and dalvik cache my system starts as usual, without saying that it optimizes the apps. Usually it always did that and it took over 2 minutes, now it just starts normal like I would never have wiped the Dalvik cache.

Could wiping dalvik cache be broken?

Edit: Also my apps randomly crashed and that was the initial reason why I wiped both caches. Now I am unable to update my apps. Just tried to update Busybox but it hangs at 47% and when I want to stop it Play Store crashes.

I then tried to reinstall root but Superuser and Playstore keep crashing. When I change things with Extweaks I get some error which shows me some folderpath and at the end "no such file or directory". A similar folder path seems to be shown on settings like scaling frequencies: /res/uci.sh line 45: can't create /data/.siyah/.config.tmp: Read-only file system cp: can't stat '/data/.siyah/.config.tmp': no such file or directory

Edit 2: Just reinstalled kernel version 3.2.7.2, reinstalle root and wiped cache and dalvik cache. Same result, phone instantly boots.

But now it got even worse, it tells me that a bunch of apps crashed (bloatware and other stuff that starts on boot) all the time. It's almost impossible to use the phone properly now. All apps which I tried to start just crash, except ExTweaks. When I start Extweaks it tells me that superuser crashed. Even the background disappeared.

Edit: I went back to 3.2.5.2 and have had no crashes so far. Also ExTweaks seems to work, I can change stuff without getting any errors. But still when I wipe cache and Dalvik cache the phone boots within seconds without showing the "optimizing apps" message which is weird.
[Galaxy S II Original Android Development] blaex:
Hey gok! Had several crashes with 3.2.8 today morning. Twlauchner and google.app.provider halted. I could not start my device. Before this i got a system message: out of system memory.

My last kmsg will follow when i back home.
[Galaxy S II Original Android Development] blaex:
Found this in my latest log afzrr boot, what does this mean?

06-04 18:00:52.410 E/DirectVolume(1818): Partition '/devices/platform/dw_mmc/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p8' has a different major than its disk!

06-04 18:00:52.415 E/DirectVolume(1818): Partition '/devices/platform/dw_mmc/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p9' has a different major than its disk!

06-04 18:00:52.420 E/DirectVolume(1818): Partition '/devices/platform/dw_mmc/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p10' has a different major than its disk!

06-04 18:00:52.420 E/DirectVolume(1818): Partition '/devices/platform/dw_mmc/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p11' has a different major than its disk!

06-04 18:00:52.425 E/DirectVolume(1818): Partition '/devices/platform/dw_mmc/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p12' has a different major than its disk!
[Galaxy S II Original Android Development] Tungstwenty:
Following the 3 previous posts, I've experienced something similar which could point to a bug.

I've flashed 3.8.3.2 last night (don't remember which version I had before, but no problems). I barely used the phone but this morning after a reboot - possibly installed something through CWM (re-installed JKay Deluxe I think) - there were FC's on virtually every application. Booted back to recovery, restored the original files, same thing.

After some steps, I finally saw that mounting /data through adb in recovery, it ended up in RO mode possibly due to corruption.

When booting normally, it was also RO. I didn't find fsck anywhere so my only option was to flash a previous Siyah - currently 3.2.8 - restore the nandroid including /data, and everything is fine so far.

There might be something that could lead to corruption in /data, and the fact that other guys mentioned it could mean it wasn't something wrong I did, which I thought was the case.

EDIT: Wiping cache and dalvik-cache was also something I did a couple of times, like Frozenthunder mentioned.