yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] Tungstwenty:
When creating a nandroid, using tar format I just noticed that under 4.1.5 the files are no longer gzipped but rather stored in uncompressed <partition>.tar.a, .b, .c files (~1mb per file).

Is this by design, or something that slipped through when re-introducing tar as an alternative to CWMR 6's dup format?

Also, sometimes the "choose backup format" menu entry will flash the screen but return to the same menu. It's not a "double-click" problem because the selected method remains as my previously selected 2nd option.

(hope the big tar files still restore properly if needed :D)
[Galaxy S II Original Android Development] bluepratham:
BUG REPORT@ GM

alpha version

i booted DILIBAN ICS based on stock samsung 4.0.3

camera not working

video player hangs..unable even to start videos

i changed the kernel back and camera and video started working fine..so accordin to me,for now it is a kernel bug

thnk u gm
[Galaxy S II Original Android Development] gokhanmoral:
I forgot to increase ion mem to cm10 values. I only tested it with cm10 cam taking a single shot. Noted.
[Galaxy S II Original Android Development] bluefa1con:
time to upgrade to a 4.0.4 rom :)
[Galaxy S II Original Android Development] Heroeagle:
camera & video recording are not working in stock samsung xwlpx 4.0.4 only black with buttons
[Galaxy S II Original Android Development] Tungstwenty:
The same in 4.0.3 (stock xwlpg)
[Galaxy S II Original Android Development] bluefa1con:
just booted with cm10 nightly 17/10

will report back
[Galaxy S II Original Android Development] PedroMRP:
In cm10 when pressing the back button in the camera app the flash turns on.
[Galaxy S II Original Android Development] wis1152:
I think that cm10 rom bug:)
[Galaxy S II Original Android Development] PedroMRP:
With cm10 stock kernel that don't happens
[Galaxy S II Original Android Development] -angel*:
I hope Gokhanmoral reads this...

Are the objects on your TODO-List sorted of their priority? I'm really waiting for B2G support in Siyah, because I think there's no kernel for the new builds atm and the one from the other guy bricked my phone :(

But guy, you're really, really doing well! :good:
[Galaxy S II Original Android Development] gokhanmoral:
oh great.. I was thinking about only mali would be a problem and now we have that ion/fimc problems...

and I am not sure if I can get it working in both ROMs.

anyway.. now I know that I have to test cam on samsung rom as well :)
[Galaxy S II Original Android Development] d_Schizzo:
Hi GM,

I had several reboots with alpha1.

In Setcpu there are shown some weird voltage levels. For example 200mhz has 838mv. Dont know if this is a bug or a feature:p

Over all the voltage levels are to low. The problem is that i cant encrease them.

But 5 gpu-steps are working fine!:good:

Now changing back to 4.1.5

Edit: running CM10
[Galaxy S II Original Android Development] robertobsc:
Same camera problem with me.

Also the wifi didn't work with me at the cafe I was in, and it was working before install.

Did you included the wifi driver?

Also screen more yellow...

Touch sensitivity seems unchanged, but very few tested.

Enviado de meu GT-I9100 usando o Tapatalk 2
[Galaxy S II Original Android Development] peterlimonade:
@GM

Just wanted to share my findings until now: http://xdaforums.com/showthread.php?p=33004886#post33004886

Thank you for doing this!
[Galaxy S II Original Android Development] Tungstwenty:
Wifi still working fine (at least so it seems) on my corporate network.

No issues on bluetooth.
[Galaxy S II Original Android Development] bombaybadboy:
I'm using 5.0a on 17/10 nightly and haven't found any problems so far
[Galaxy S II Original Android Development] bluefa1con:
cm10 17/10 nightly

siyah 5a1

played video with hw codecs with sound on 0

still the sound was playing from the speakers

any idea? logs required ?
[Galaxy S II Original Android Development] Tungstwenty:
Auto-rotation not working on XWLPG
[Galaxy S II Original Android Development] Rick Roll:
please merge CRT fix from dorimanx kernel
[Galaxy S II Original Android Development] CamoGeko:
Most likely rom issue and nothing to do with kernel.

Spun out from my RenovateD and NCX'd HTC One X!
[Galaxy S II Original Android Development] Christiancs1969:
:rolleyes:

s2 aopk 412 dori 73 pitch perfect
[Galaxy S II Original Android Development] gokhanmoral:
4.0.3 roms and cm roms require some tiny hack in accelerometer but I removed it for samsung roms.

is there any reason to run 4.0.3 instead of 4.0.4?
[Galaxy S II Original Android Development] Christiancs1969:
Testing:D

s2 aopk 412 dori 73 pitch perfect
[Galaxy S II Original Android Development] Scarface1991:
Testing 5.0a with the 17.10 CM10 Nightly and so far no problems at all.
[Galaxy S II Original Android Development] pangiotis24:
my only problem so far is that on paranoid android 2.22 when i try to video record camera fc's
[Galaxy S II Original Android Development] bluefa1con:
try a media file

mp4 or avi with volume at 0 and see if the speaker bug is present
[Galaxy S II Original Android Development] d_Schizzo:
This also happens on CM10
[Galaxy S II Original Android Development] Scarface1991:
I tried several mp4 and mkv files with MX Player and speaker was silent (no sound) on 0 volume. I tried both the H/W and the H/W+ decoder and both work fine

What video player do you use?

EDIT:

But yes I can confirm that video recording doesn`t work, taking photos does work.
[Galaxy S II Original Android Development] illuminato 67:
+ 1
[Galaxy S II Original Android Development] It_ler:
Not for me.

Maybe some users feel saver with 4.0.3 because only 4.0.4 has the "brick-bug".
[Galaxy S II Original Android Development] ShadowSkills:
Unfortunately latest MIUI is still using 4.0.3 for the base :(

Oh and video recording isn't working too on MIUI (With 5.0a1)

Sent from my GT-I9100
[Galaxy S II Original Android Development] pilgrim011:
+1. I don't use 4.0.4 for that reason.
[Galaxy S II Original Android Development] bombaybadboy:
+1 video recording not working here to, gallery stopped responding but camera works on nightly 17/10
[Galaxy S II Original Android Development] Pumpino:
+1. The last few days on Dorimanx 7.3 have been great. The CRT animation works every single time, even with wi-fi off. So nice to have that little annoyance gone after so many months.

On the positive side, it's nice to see a jump to kernel 3.0.31 in Siyah, just like official Jelly Bean. Maybe we'll see 3.0.46 in the future and it would be a bonus to have the latest v6.1.0.5 of recovery, too.
[Galaxy S II Original Android Development] CamoGeko:
Brick bug is nothing to do with the rom itself.

As long as you're running Siyah you will be safe.

Spun out from my RenovateD and NCX'd HTC One X!
[Galaxy S II Original Android Development] bluefa1con:
i tried mobo player

mx doesnt have hw acceleration for all formats thats why i prefer mobo or bs player
[Galaxy S II Original Android Development] gokhanmoral:
no, we will not have any 3.0.46. if there is something really useful, we will have it in 3.0.31...

I will not add extra sleeps just to make CRT animation work.

they just delay the screen off, and I do not think it is worth to have. and I didn't like that solution when I was using s2. you like to watch CRT animation but I like my screen off as soon as possible.

but if there is a better fix recently that I don't know about please send me a link so that I can cherry-pick it.

I will update the recovery, but not because of the increased version number, I will only fix the apps on sdcard not being backed up.
[Galaxy S II Original Android Development] Tungstwenty:
Personally, I'm on 4.0.3 not due to MIUI but JKay Mod.

LOL, considering the thread :)
[Galaxy S II Original Android Development] Scarface1991:
Orbot (transparent proxying) is not working on latest CM10 nightly (17.10), it would be great if you could make it work.

It gives me this error when I try to enable Orbot: WARNING: error starting transparent proxying
[Galaxy S II Original Android Development] RovG:
Yep. Language not yet supported on a stock 4.0.4 rom.
[Galaxy S II Original Android Development] Bartapuce:
+1
[Galaxy S II Original Android Development] d_Schizzo:
Hi,

why cant i set voltages like 840mv or 980mv in setcpu with the alpha1? Its only possible to use 25mv steps but no 20mv steps.
[Galaxy S II Original Android Development] AlkaDragos:
Really? Does that 0005 mv really matter? You can do that manually if you want btw.
[Galaxy S II Original Android Development] d_Schizzo:
If you ask me, then yes it matters. For example: 500mhz with 925mv freezes my device, but with 930mv it runs absolutly stable. So, there is no need to use 950mv.
[Galaxy S II Original Android Development] Ogy77:
You are great dev,thanks God for you,beta 7 its nice and awesome,big thanx,noe is beta and so cool.
[Galaxy S II Original Android Development] It_ler:
You seem to be right.

Good work !

P.S.:

I posted my latest (benchmark and battery) test results in general discussion thread => http://xdaforums.com/showpost.php?p=24094830&postcount=11
[Galaxy S II Original Android Development] gokhanmoral:
I set pixel sensitivity to 3. you are right it causes that problem.

I will set it back to 5.

you can use extweaks to set it to 5.
[Galaxy S II Original Android Development] Goku80:
not really sure if this is a kernel issue or rom issue but i will try here first.

when flashing the kernel on latest nightly everything works smoothly. i could change dpi with dpi changer to 182 and go on about my everyday business and use my phone like normal. now something went wrong and i needed to reflash the nightly again. this is what happens when i go into recovery

installing update : assert failed: getprop(ro.product.device") error in emmc/android/update-cm9 the nightly build

im wondering could it be that when flashing siyah while i am on 182 dpi conflict at all with recovery? i mean it should not really should it

anyway hope i am making sense and someone could kinda explain to me what is going on please thanks
[Galaxy S II Original Android Development] digeddydogg:
I was also experiencing the screen trembling and changed the vitalij settings to 5 pixels but sill experiencing screen trembling. Tried rebooting, but same results.

rice and pea(ce)
[Galaxy S II Original Android Development] Vaedryn:
change dpi with explorer and no problem. I think it is a app problem. I change my dpi with density modder app. Than in recovery status 7 error when i will flash. Delete the modder app, change dpi with explorer, no status 7 error.

SGS II Cyanogen Mod 9 Tapatalk
[Galaxy S II Original Android Development] Goku80:
cheers mate. do it the good old fashion way then i take it..many thanks...knew i could always count on you dude;)
[Galaxy S II Original Android Development] gabx:
USB mass storage is working with CM9
[Galaxy S II Original Android Development] Vaedryn:
I don't know it works for you , for me it remove the problem. Old ways are the best ways:) test it and give a feedback if it work.

SGS II Cyanogen Mod 9 Tapatalk
[Galaxy S II Original Android Development] gabx:
?? My vitalij is set to 2 with no problem !!
[Galaxy S II Original Android Development] digeddydogg:
That's strange then. Mine used to be two with no problem. Then someone mentioned screen trembling (when scrolling and leaving your finger on the screen, most noticeable on notification pull down) which I then noticed. Gok mentioned to change pixel sensitivity to 5 and it should fix it. Which I interpreted as vitalij. But still trembling. Am I confusing screen sensitivity with vitalyj then?

rice and pea(ce)
[Galaxy S II Original Android Development] sachs:
+1...no problem here.

wanam 9.9 rom
[Galaxy S II Original Android Development] vassalle:
Happy to report that b7 works with stock deodexed lp3.

Keep up the good work gm!
[Galaxy S II Original Android Development] digeddydogg:
Well, took the battery out for a few mins. Put it back in and jittering is sorted. Hurray!

Edit: can someone who hasn't experienced jittering, plug their phone in and pull the notification bar down half way and hold it there and report back? Jittering only when device is plugged

rice and pea(ce)
[Galaxy S II Original Android Development] gabx:
Exactly as you describe it. Jitter when pluged.
[Galaxy S II Original Android Development] A380:
Yes, confirmed here too.
[Galaxy S II Original Android Development] Entropy512:
Yeah the problem is pissing me off... Nothing useful shows in /proc/last_kmsg when it happens - the log just stops with no indication of why.
[Galaxy S II Original Android Development] gokhanmoral:
today, we tested it with droidphile a little.

I think he had more than 50 SOD just in the morning :)

it doesn't happen when we set frequencies using adb shell.

it happens with setcpu and screenstate scaling script which waits at wait_for_fb_sleep and wait_for_fb_awake. so, it happens if we set the cpu just after turning the screen off (just after we have "sleeping" from wait_for_fb_sleep)

we tried to put sleep 1's after catting those wait sysctl interfaces. it worked... no SOD.

I compared cpu setting and idling parts with the previous repository but I could not find anything worth, but obviously we have a race condition here...
[Galaxy S II Original Android Development] revaz:
First TNX for your job done! I used your kernel since GB and now for ICS.

Today installed Beta 7 but had to back up for Beta 6 cause had a problem whith a camera (hang up) and data communication. Had any idea? ROM stock LP2
[Galaxy S II Original Android Development] vivmar:
Strange problem

until 1 hour ago ,my phone set up was: CM9 (build 25-03) + siyah b6 ,a nd all work well...

so i have updated cm9 to build 26-03 (wiped both cache's),rebooted and all work well (with stock kernel)

then i have rebooted and flashed siyah b7 (wiped both cache's),and now start the problems:

phone is veery hot (over 40°),it seem like is stucked @ 1200mhz both core's ever....and if i try to change frequencyes (underclock)or change governor,my phone will be "freezed" so i have to pull out battery.Also if i wait until phone goes to sleep (screen-off) i can't no more put screen-on,so battery pull-out.

so,i have flashed latest cm9 build over,and now is back all ok...

any idea :confused:
[Galaxy S II Original Android Development] gokhanmoral:
although I haven't checked the code again I am nearly sure that 930 sets the voltage to 950.

steps are 25mV but they are not used. as far as I remember, the number of steps from a voltage level (750 I guess) is found and that number is rounded up to the nearest integer.

and if you are after 5mV you are in the wrong thread...
[Galaxy S II Original Android Development] d_Schizzo:
Ok, thanks for the answer. I didnt know that the voltage levels are rounded up or down. I was only confused, that i cant use the settings like i did in previouis versions..
[Galaxy S II Original Android Development] Tungstwenty:
I also noticed this but it went away as soon as I reset the ExTweaks profile
[Galaxy S II Original Android Development] RovG:
Hi Gokhan,

Will we be able to create "image.zip" for 1st & 2nd rom with the updated recovery?
[Galaxy S II Original Android Development] gokhanmoral:
No.
[Galaxy S II Original Android Development] Christiancs1969:
Nice job ;)

s2 aopk 412 siyah pitch perfect
[Galaxy S II Original Android Development] confusedmuse:
0005 mV? :eek: It's 5 mV or 0.005 V.
[Galaxy S II Original Android Development] Tungstwenty:
Any chance of adding a true/false setting to remember your last booted rom and use that as the default on future boots?

If active, a small control file could be stored in the main /data/.siyah with the last selection and update it whenever the override button is pressed at startup or explicitly requested from STweaks.
[Galaxy S II Original Android Development] AlkaDragos:
+1 for that. Would be in handy for most flashaholics around here ( and not only...) :) - testing alpha build

@confusedmuse - lawl! Thanks captain obvious ( 0.000005 kV and 5000 μV ) ... Instead of acting like some smart guy, please come with some feedback about new kernel release or some suggestions and keep the off-topic away.
[Galaxy S II Original Android Development] PedroMRP:
Can anyone test if adb works? My eclipse don't detect my device with 5.0a1.

At least with CM10. Not tested with other roms.

Mass Storage don't work in OS X.
[Galaxy S II Original Android Development] asterisko:
+1 This is really a good idea!
[Galaxy S II Original Android Development] Jaco2k:
Will we get dual boot with CM9? Right now I have CM9 latest as first room and CM10 latest as second and then cannot boot CM9
[Galaxy S II Original Android Development] Scarface1991:
No we won`t:
[Galaxy S II Original Android Development] Ok_Kaleidoscope5109:
This is the part that I think is a huge deal for many. CM10 for a long time hasn't been ready yet til the memleak got fixed. I think many of us still use CM9 as a daily driver and CM10 as an experimental. Is it difficult to keep CM9 support? I think a lot of us would really appreciate it if you stuck it in still :(
[Galaxy S II Original Android Development] Jaco2k:
In my case is even worse... I want to move to CM10 completely but unfortunately none of the 4 track logging softwares I use is playing well with JB due to the external memory mount point changes. Since the software is use most has been abandoned by the developer and won't be fixed, I either buy a new device or stick to ICS.

As much as it sucks, I understand the reasons why it won't be supported.

Now... one thing that I can look into and if I understood correctly, is that I can dual boot with a Samsung stock ICS? Any limitations there?
[Galaxy S II Original Android Development] RovG:
:(

May I please know why?
[Galaxy S II Original Android Development] kalpik:
This is the commit that fixes CRT: https://github.com/dorimanx/Doriman...mmit/cdf48f045a1d5f6a0cdffc30832ad7eb45ac79d9

I really don't feel any difference in screen off time. Maybe you can see for yourself?
[Galaxy S II Original Android Development] qqqqqq0:
V5.02a2 link?

GT-I9100 cihazımdan Tapatalk 2 ile gönderildi
[Galaxy S II Original Android Development] nitinvaid:
Means we cannot dual boot cm9 and Mali cm10:(
[Galaxy S II Original Android Development] peterlimonade:
Except for limitations in space, no. You can even flash a ROM that is based on stock ICS, I used NeatROM to test. Otherwise you would have to go to the trouble of flashing stock through Odin, moving it to 2nd ROM and flashing CM10 (I guess that's what you would want).

SGS2 // RB 20121018 // Dorimanx 7.3
[Galaxy S II Original Android Development] bluefa1con:
Just symlink the mount points to the old positions
[Galaxy S II Original Android Development] roozbeh158:
Camera not working.

Rom: VK 5.4.2 ANDROID 4.0.4

TKS
[Galaxy S II Original Android Development] gokhanmoral:
yes, it is hard. but if anyone else can do that I can happily cherrypick the commit.

it is doable, but I don't want to spend any time on that.

and after the new mali patch there should not be any memleak in cm10.

yes, I feel the difference. I have no sleep in my kernel now and I don't feel any lag when turning my screen off.

if you have the animation of course you won't feel the difference. I don't have crt animation and I feel it. try it yourself.

and FYI, it is not dorimanx's, it is codeworx's commit originally. I see that dorimanx changed the sleep duration a little but I have already tried to have a comfortable value but none of them worked.
[Galaxy S II Original Android Development] kalpik:
Ah, well yeah, I do have the animation on. No chance this could be configurable? Either way, this is a tiny thing that doesn't even matter. Whatever you decide is fine :)
[Galaxy S II Original Android Development] nitinvaid:
Correct me if I am wrong dual boot is possible only with Cm10 and stock ICS ROM

Not cm10 and cm9
[Galaxy S II Original Android Development] THE RED BLUR:
Correct :thumbup:

PHONE : SGSII

Sent via: Tapatalk 2

Main ROM: RootBOX jb 2.9 mali (ONLINE) 17-10-12

2nd Rom: RR ics 2.7- Not accessible

KERNEL : Dorimanx 7.3 Mali

MODEM : LPS

GAPPS : JusTunBean aroma 3.2
[Galaxy S II Original Android Development] Jaco2k:
I thought that symlinks in Android was a bit of black magic and they did not really work?

Last time I searched I did not find a conclusive working solution.
[Galaxy S II Original Android Development] bluefa1con:
mount points are already symlinked to extSdcard and sdcard from storage/sdcard0 and storage/sdcard1 aswell

i am sure its doable there is an app called directory bind although i am not sure if that app will work in your case but you can take it as a proof of concept that its doable
[Galaxy S II Original Android Development] Jaco2k:
Well... so was I, but when I tried to change these locations on the config file that is in sys folder (or was it system) the phone did not.boot. And yes, I created the new folder to symlink to and gave it the correct permissions. It seems to have to do more with the system itself.

---------- Post added at 11:33 AM ---------- Previous post was at 11:20 AM ----------

I don't think the app you are talking about on your edit behaves in the same way as a symlink. From what I understand what it does is not visible to the system so for all accounts the system only sees and thinks you are still using the original location. I will nonetheless give it a try, but I don't think this is the solution.
[Galaxy S II Original Android Development] bluefa1con:
it might be hard but anything is possible with android

and being opensource u can compile cm10 with ur required changes

i lack the knowledge of editing the source for mount points but if u find a patch or a developer assist me i can compile it just for u

btw anyone considering xperia T be warned sony wont update it anytime soon

source
[Galaxy S II Original Android Development] Jaco2k:
So, in other words, you are simply assuming without knowing for sure ;)

...and if by compile, you mean edit the build zip file before flashing, that is what I did and did not work ;)
[Galaxy S II Original Android Development] ROX77:
Is it already implemented the mic sensivity gain?
[Galaxy S II Original Android Development] AlkaDragos:
By going to Gokhans blog you will see the new version of kernel ( v5.0 ). Changelog means that those modifications are already included in the actual version of kernel ( or in the version specified after that modification. ex xxxxxxx (v5.0a2) ), and those modifications writed under TODO means that they will be included in next versions / releases of kernel, so no. Please stop asking informations that can be found around with a bit of searching. ;)
[Galaxy S II Original Android Development] ROX77:
Yes, I know the blog and I know to read, but my question was more that a simple question... Because people ask for the "very important" CRT animation, while with this phone it's impossible to do a decent video without audio distorted... :rolleyes: and I read that mic sensivity is the last on the list :rolleyes:
[Galaxy S II Original Android Development] profetul:
Camera not working

Same here - stock ROM - 4.0.4- BVLPH & Siyah-s2-v5.0a1.

Camera shows only black screen - options are accessible for a short time - and then FC's

Anyone has an idea?
[Galaxy S II Original Android Development] bombaybadboy:
Deleted

---------- Post added at 12:52 PM ---------- Previous post was at 12:50 PM ----------

I installed s2-v5.0a1 yesterday on nightly 17/10 + new official gapps + Google picasa gapp add on and one or all of the combination killed video camera. I reflashed nightly 17/10 and stayed on stock kernel and still no video camera. Only when I went back to 4.0.3 Sammy's then installed nightly again vid camara worked again. I don't dual boot and wondered if anyone had this problem?
[Galaxy S II Original Android Development] profetul:
So an idea would be to reflash 4.0.3 stock - check if it is working, and then flash 4.0.4 ?
[Galaxy S II Original Android Development] bombaybadboy:
That's what I said I did and now back on nightly + stock kernel and video camera working fine again
[Galaxy S II Original Android Development] cdaarif:
1+
[Galaxy S II Original Android Development] d_Schizzo:
GPS is not working on CM10 and alpha1

Greetz,

Schizzo