yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] Moster2:
Can you be more precise on how to reproduce this error (which apps, which order etc.)? I never had that issue.
[Galaxy S III Original Android Development] adripred:
I used the Snap camera, Google camera and CM camera. I took several photos and recorded videos with each of them. When I returned to Snap camera the video recording button no longer responded more. Tested CM camera and Google camera in sequence and also the record button stopped responding. I had no more "Can't connect to camera" error. Your i9300 is from what country? My I9300 is from Brazil. You are so lucky!!! Hahahahah
[Galaxy S III Original Android Development] guhvanoh:
22/5 nightly was the first nightly that was unusable for me. I need to a complete wipe and reinstall.
[Galaxy S III Original Android Development] kanjac:
For me 22/5 everything perfectly works
[Galaxy S III Original Android Development] ikerg:
I am very upset with the camera...apparently it seems to be working ok..each time i reboot or upgrade to new nightly...the photos that I could see previously on the gallery before (rebooting/upgrading) are black and not a valid photo... The system is always corrupting the photos taken.

Enviado desde mi GT-I9300 mediante Tapatalk
[Galaxy S III Original Android Development] miketino:
Thank goodness they're backed up then
[Galaxy S III Original Android Development] Maceee:
Why sms notifications disappear only after I click them twice or open Messaging twice? And how to increase vibration intensity and also sound level because it's much more silent than on stock Samsung ROM?
[Galaxy S III Original Android Development] danielalarcon:
Similar thing, seems like if I stick only to one camera, al works well, google camera, CM camera or jb+ if I keep switching between them I eventually get camera can't connect, I go stop, clear cache and clear data for the last app used, last time was google camera, and problem is solved.

Nevertheless, if any of three opens normally I can take pictures and videos all the time without trouble. Looks like it's almost there. Thanks for providing this.
[Galaxy S III Original Android Development] :
All perfect today and yesterday
[Galaxy S III Original Android Development] k4mr4n94:
Hi, where can i get this 'fix3' from? Thanks
[Galaxy S III Original Android Development] benthe:
Can you please link to the kernel profile?

Everyone could use a better battery life with this phone :).
[Galaxy S III Original Android Development] nitinvaid:
Old themes will work on new theme engine without any problems.

But

The themes made for new theme engine can't be used in old one

I tested myself
[Galaxy S III Original Android Development] adripred:
Here:

http://xdaforums.com/showthread.php?p=52890883

Regards!
[Galaxy S III Original Android Development] ikerg:
If no reboot/upgrade they hace corrupted as well

I take a photo...I can see it under gallery. I share it by whatsapp by selecting from gallery I once...after that it appears to be corrupted (not valid picture). It appears as black thumbnail and I can't share it anymore

Is anybody suffering the same?

Do you recommend to reinstall last nightly in a clean way (wipes). Is the data wiping necessary... Or only with dalvik and cache is enough? (I don't want to reinstall everything again)

Many thanks in advance

Enviado desde mi GT-I9300 mediante Tapatalk
[Galaxy S III Original Android Development] neodraig:
After installing the cm-11-20140524-NIGHTLY-i9300, "OK Google" and bluetooth weren't working anymore.

Reverted back to the 22 and everything is working fine again (I made a cache wipe though, which I didn't when I installed the 24).

Also since the 21 Google Camera is working (yippie!!!) when it used to crash.

[MENTION=744370]ikerg[/MENTION]

In the instructions for updating, they say:

"If you did not do a factory reset, you may optionally choose to clear the cache. "

(the factory reset is necessary for a major update CM10 -> CM11)

Also for the Dalvik cache, I don't think it can hurt to wipe it, but as for myself, I wonder if it's necessary as I have ART activated :confused:
[Galaxy S III Original Android Development] george stamatos:
approved ! gongrats !
[Galaxy S III Original Android Development] Moster2:
Hehe, thx

http://review.cyanogenmod.org/#/c/64631/

Added the iso mode stuff, too. It was in the old wrapper and still works just fine.
[Galaxy S III Original Android Development] FadeFx:
[MENTION=4604352]Moster2[/MENTION] wouldnt you want to take over device maintainance? I mean you are able to as it looks...

tapatalked from i9300
[Galaxy S III Original Android Development] Moster2:
I dont think that I know enough yet.

[MENTION=3814993]RohanAJoshi[/MENTION] , where did you take those audio values from? I dont see them in the default_gain.conf from stock.
[Galaxy S III Original Android Development] tdcfpp:
Wrong repo or not. Cm has not taken teamhacksung's work. And now they are re-starting development from beginning. Re-correcting errors.

It worries me the way it is going. Try to spend some 100s of hours late in the night while your family sleeps, and look how your work is not even read.
[Galaxy S III Original Android Development] RohanAJoshi:
HPF values and noise suppression values are from default gain file, check deeply, 1st you need to understand it.

.

here : in that file check line 193 :

#Modifier : Incall

Modifier "Incall" {

SupportedDevice {

"Earpiece"

}

Enable {

{ "AIF2DAC2L Mixer AIF2 Switch", 0 },

{ "AIF2DAC2R Mixer AIF2 Switch", 0 },

{ "AIF2ADC HPF Mode", 1 },

{ "AIF2ADC HPF Switch", 1 },

{ "AIF1DAC1 Volume", 96 },

{ "AIF2DAC Volume", 96 },

{ "AIF1 Boost Volume", 0 },

{ "AIF2 Boost Volume", 0 },

{ "DAC1 Volume", 96 },

{ "Left Output Mixer DAC Volume", 7 },

{ "Right Output Mixer DAC Volume", 7 },

{ "Output Volume", 57 },

{ "Earpiece Volume", 1 },

{ "Speaker Mixer Volume", 1 },

{ "Speaker Volume", 0 },

here, with this HPF modes and HPF switch changes, later :

Modifier "Incall" {

SupportedDevice {

"Speaker"

}

Enable {

{ "AIF2DAC2L Mixer AIF2 Switch", 0 },

{ "AIF2DAC2R Mixer AIF2 Switch", 0 },

{ "AIF2ADC HPF Mode", 1 },

{ "AIF2ADC HPF Switch", 1 },

{ "AIF1DAC1 Volume", 96 },

{ "AIF2DAC Volume", 96 },

{ "AIF1 Boost Volume", 0 },

{ "AIF2 Boost Volume", 0 },

{ "DAC1 Volume", 96 },

{ "SPKL DAC1 Volume", 1 },

{ "SPKR DAC1 Volume", 1 },

{ "Speaker Mixer Volume", 3 },

{ "Speaker Boost Volume", 5 },

{ "Speaker Volume", 57 },

for speaker, same..later :

Modifier "Incall" {

SupportedDevice {

"Headset Out"

}

Enable {

{ "AIF2DAC2L Mixer AIF2 Switch", 0 },

{ "AIF2DAC2R Mixer AIF2 Switch", 0 },

{ "Speaker Mixer Volume", 1 },

{ "Speaker Volume", 0 },

{ "Headphone ZC Switch", 0 },

{ "AIF1DAC1 Volume", 96 },

{ "AIF2DAC Volume", 96 },

{ "AIF1 Boost Volume", 0 },

{ "AIF2 Boost Volume", 0 },

{ "DAC1 Volume", 96 },

{ "Headphone Volume", 49 },

}

same for headset..

That's why I made HPF changes..

I hope you understand now..

also at line 2547 For headset :

Modifier "IncallIn" {

SupportedDevice {

"Headset In"

}

Enable {

{ "IN2L Volume", 28 }, // IN2L= Headset Mic, value goes 28 for calls, so I made it 28, previously it was 18, too low gain..

{ "MIXINL IN2L Volume", 0 },

{ "DAC2 Left Sidetone Volume", 12 },

{ "AIF2ADC Volume", 96 },

{ "AIF2ADCL DRC Switch", 0 },

}

Disable {

{ "IN2L Volume", 11 },

{ "MIXINL IN2L Volume", 0 },

{ "DAC2 Left Sidetone Volume", 0 },

{ "AIF2ADC Volume", 96 },

}

}

for noise suppression, I was wrong, those values are fine in cm..

now check from line 2526 for noise suppression :

Modifier "IncallIn" {

SupportedDevice {

"Back Mic"

}

Enable {

{ "IN1R Volume", 25 }, //IN1R=Back Mic, when we are in call, value goes to 25.

{ "MIXINR IN1R Volume", 0 },

{ "DAC2 Left Sidetone Volume", 12 },

{ "DAC2 Right Sidetone Volume", 12 },

{ "AIF2ADC Volume", 96 },

{ "AIF2ADCL DRC Switch", 0 },

}

Disable {

{ "IN1R Volume", 7 },

{ "MIXINR IN1R Volume", 0 },

{ "DAC2 Left Sidetone Volume", 12 },

{ "DAC2 Right Sidetone Volume", 12 },

{ "AIF2ADC Volume", 96 },

}

}

that's all, this is not big change, but little..

also I made few changes in tiny_hw.xml, will make change for that..

.

I reverted to original noise suppression values..

https://github.com/RohanAJoshi/andr...mmit/8f6837a462f0a15fcf6c8088081530037ca71527
[Galaxy S III Original Android Development] Moster2:
Im rather asking regarding AIF1ADC1 HPF Mode and AIF1ADC1 HPF Switch. Aren't they already correctly set in tiny_hw.xml like in default_gain.conf? I'm sure yes.

You are totally right. I dont know why Ricardo didnt use the old one.
[Galaxy S III Original Android Development] RohanAJoshi:
Even those are correctly set in tiny_hw.xml, those values cant apply in call state (on My personal testing ), the tiny_hw.xml values goes for normal mode..

.

also I 1st I tried to edit tiny_hw.xml for headset mic gain, but it does not have any effect for calls or recorder, then i made changes in audio_hw.h file and it worked perfectly..

so, even HPF are corrected in tiny_hw.xml, I need to add them to audio_hw.h for feeling actual difference..

.

previously earpiece sound was muffed, but after adding those changes in .h, headset is clear n loud, for me..

[MENTION=3350694]tdcfpp[/MENTION] : will you please shed some light on this ?

.
[Galaxy S III Original Android Development] tdcfpp:
Have you pushed tiny_hw.xml to device after changing it? Have also in mind that that file needs to be renamed to m0.conf or similar before pushing.
[Galaxy S III Original Android Development] RohanAJoshi:
Yep..

Everything intact..
[Galaxy S III Original Android Development] adripred:
These fixes take much time to be available in CM?

Regards!
[Galaxy S III Original Android Development] Moster2:
It takes as long as it takes :P

Someone needs to review them, usually Ricardo Cerqueira. I dont know when he usually works/checks commits.
[Galaxy S III Original Android Development] adripred:
[MENTION=4604352]Moster2[/MENTION],

Continuing tests with Fix3: I didn't rebooted the phone since the patch installation yesterday, the camera hadn't crash yet to take pictures in all 3 camera apps. I hadn't the "Can not connect to camera" error yet. Only in video recording the record button stopped working. This is the best fix so far.

Waiting for a new version of this fix!

Thank you!

Regards!
[Galaxy S III Original Android Development] metalgearhathaway:
latest build says the following commit is included:

fix preview/camera crash after stopping video record (android_device_samsung_i9300)

running nandroid so I can test :)

EDIT - I HAVE NOW TESTED, THE FROZEN SCREEN ISSUE IS RESOLVED, THE SPEED BETWEEN RECORDINGS IS ALSO IMPROVED, HOWEVER AFTER A FEW VIDEOS THE DEVICE WILL NO LONGER RECORD AS BEFORE, AT LEAST WE ARE GETTING SOMEWHERE THOUGH!
[Galaxy S III Original Android Development] xela1989:
Nobody can help me?
[Galaxy S III Original Android Development] adripred:
It isn't normal. Have you tried a clean instalation with a full wipe?

Regards!
[Galaxy S III Original Android Development] xela1989:
Honestly I have not tried just because it annoys me to reinstall all applications, but I think that is a remote possibility ...
[Galaxy S III Original Android Development] MonsterMMORPG:
what major problem remains at current build ?

such as cant connect camera or

ui crash when you pull down notification bar etc

ty
[Galaxy S III Original Android Development] 213182:
:) yes i will do that workaround.BTW as you said its a great ROM that i have came across..

unable to enable ROOT permission for ES file explorer.any idea?i have installed Super SU.

what are the changes in today build?change log was not mention any idea?

seems i'm bothering you a little :cool:
[Galaxy S III Original Android Development] Z0R:
No problem mate. You can always read the changelog on the link mentioned in OP. :D

Changelog :p
[Galaxy S III Original Android Development] 213182:
thanks Mate :)
[Galaxy S III Original Android Development] Rahulrao:
I have the lastest cwm philz 6.0.4.4

Still it is happening. Tried 3 times!
[Galaxy S III Original Android Development] Z0R:
Redownload rom and check MD5 sums
[Galaxy S III Original Android Development] Rahulrao:
Checked ,redownloaded!

Still no luck! :(

set_metadata_failure its giving!
[Galaxy S III Original Android Development] Z0R:
Very strange. Never have had such problems earlier. Can you download other ROM flash it continue with first steps and then try again with this ROM. But please make a full wipe between. :)

Sent with LG-G2
[Galaxy S III Original Android Development] Ctrl+A:
1.Flash latest beta of xposed installer framework for cm11

(http://xdaforums.com/showthread.php?t=1574401)

2. Use file manager built into this ROM to turn the /system folder into rw mode and then update/install the framework once flashed.

3. Then install the module called Pictures2sd inside xposed.

This works a charm on this ROM.

-------------------------------------------

If I helped, simply hit the "thanks" button to reduce thread clutter.

---------- Post added at 07:14 PM ---------- Previous post was at 07:08 PM ----------

Root: go into super su settings and delete the es entry to force it to ask permission again.

Changes: read the 'review' link under change log heading in OP

edit: just saw this was answered above

-------------------------------------------

If I helped, simply hit the "thanks" button to reduce thread clutter.
[Galaxy S III Original Android Development] Rahulrao:
Did that

1) Installed omega 50.1.

2)full wipe ,wipe cache,wipe dalvik

3)Installed cm-11.

4)Installation aborted.

I give up :(

Really wanted to try kitkat!:crying:
[Galaxy S III Original Android Development] MmegaMac:
Try to flash official CWM (via ROM manager for example).
[Galaxy S III Original Android Development] Mostafa Wael:
any known issues???

I am curious to try it...

thanks great dev :D
[Galaxy S III Original Android Development] cink40:
None
[Galaxy S III Original Android Development] :
My WIFI is not working, ideas? Using build 04.12.2013 ;)
[Galaxy S III Original Android Development] CeesitarJet:
This ROM hasn't Color calibration setting.. It will be implemented?

Inviato dal mio GT-I9000 utilizzando Tapatalk
[Galaxy S III Original Android Development] calvinljh:
Hi All,

Can know how to do screen shoot on Kitkat Android?

Mind to share this function as where could i enable it?

TQ.
[Galaxy S III Original Android Development] MmegaMac:
Power + Vol.-
[Galaxy S III Original Android Development] :
Ideas what I could try to get Wifi working?
[Galaxy S III Original Android Development] blofse:
Guess you have tried doing a factory reset, cleaning all cache etc?
[Galaxy S III Original Android Development] Redscorpian:
Downloads...

Hi, I must be doing something basically wrong but I cannot download from either of the sites on page 1 via my mobile. I have registered and am using the Mega app but I can't see a way of getting my phone to link or synchronise with Mega and the Mediafire link just gets me a very small file which I can't do anything with - it's not a link.

So what am I missing?
[Galaxy S III Original Android Development] mircea89fzr:
install latest philz recovery. i had the same. it will work!
[Galaxy S III Original Android Development] simono_pl:
For me no UI crash and can't connect camera on leatest and earlier nightly. Most big issues was fixed some days ago.
[Galaxy S III Original Android Development] MonsterMMORPG:
awesome. it seems like time to reinstall :D

i had major problems during this vacation due to camera error :(
[Galaxy S III Original Android Development] Maceee:
Is it acceptable to flash newer nightlies (like 2 days newer) without any wipe? Or should I wipe something?
[Galaxy S III Original Android Development] DjoeN:
Not a problem at all, I only flash CM11 nightly once a week (mostly always on Sunday) and i just use the OTA for that.
[Galaxy S III Original Android Development] adripred:
[MENTION=4604352]Moster2[/MENTION]

In 20140526 nightly (full wiped before) I didn't have the crash when pressing stop video recording neither "Can't connect to camera" error, but after recording some videos or changing the camera app, the record button stops to respond and creates a TMP file in DCIM/Camera folder.

Is there any workaround for this? Because this problem seems to be the most important with the camera in AOSP ROMs.

Tested with Snap camera, CM camera and Google camera.

I am available for any test about it.

Regards!
[Galaxy S III Original Android Development] Moster2:
Can you maybe be as specific as possible what settings and app(s) you use and mayby provide a log with adb logcat.

Same for you. I cannot reproduce this non working recording button.
[Galaxy S III Original Android Development] adripred:
I've never done this, but if I can send you a log would help you to continue the quest for a solution?
[Galaxy S III Original Android Development] Moster2:
Yes, or you give me a good method to reproduce this error.
[Galaxy S III Original Android Development] Moster2:
Got the error now. Problem is that the crash does not come from the camerawrapper or camera itself, at least it does not seems so.

Cam_VideoModule is Java, so nothing low level, and OMXCodec is also not directly the camera. I need to test more and see how to reproduce this error reliably. It was just by accident this time

I/OMXCodec( 1931): [OMX.SEC.AVC.Encoder] allocated buffer 0x40ee4e48 on output port
E/OMXCodec( 1931): [OMX.SEC.AVC.Encoder] ERROR(0x80001000, 0)
E/OMXCodec( 1931): [OMX.SEC.AVC.Encoder] init failed: -2147483648
E/MediaRecorder( 3819): start failed: -2147483648
E/CAM_VideoModule( 3819): Could not start media recorder.
E/CAM_VideoModule( 3819): java.lang.RuntimeException: start failed.
E/CAM_VideoModule( 3819): at android.media.MediaRecorder.start(Native Method)
E/CAM_VideoModule( 3819): at com.android.camera.VideoModule.startVideoRecording(VideoModule.java:1638)
E/CAM_VideoModule( 3819): at com.android.camera.VideoModule.onShutterButtonClick(VideoModule.java:725)
E/CAM_VideoModule( 3819): at com.android.camera.ShutterButton.performClick(ShutterButton.java:142)
E/CAM_VideoModule( 3819): at android.view.View$PerformClick.run(View.java:18446)
E/CAM_VideoModule( 3819): at android.os.Handler.handleCallback(Handler.java:733)
E/CAM_VideoModule( 3819): at android.os.Handler.dispatchMessage(Handler.java:95)
E/CAM_VideoModule( 3819): at android.os.Looper.loop(Looper.java:136)
E/CAM_VideoModule( 3819): at android.app.ActivityThread.main(ActivityThread.java:5144)
E/CAM_VideoModule( 3819): at java.lang.reflect.Method.invokeNative(Native Method)
E/CAM_VideoModule( 3819): at java.lang.reflect.Method.invoke(Method.java:515)
E/CAM_VideoModule( 3819): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:795)
E/CAM_VideoModule( 3819): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:611)
E/CAM_VideoModule( 3819): at dalvik.system.NativeStart.main(Native Method)
V/CAM_VideoModule( 3819): Releasing media recorder.
D/MPEG4Writer( 1931): Stopping writer thread
D/MPEG4Writer( 1931): 0 chunks are written in the last batch
D/MPEG4Writer( 1931): Writer thread stopped
D/MPEG4Writer( 1931): Stopping Video track
E/MPEG4Writer( 1931): Stop() called but track is not started
D/MPEG4Writer( 1931): Stopping Audio track
E/MPEG4Writer( 1931): Stop() called but track is not started
W/AudioFlinger( 1931): session id 86 not found for pid 3819
[Galaxy S III Original Android Development] adripred:
Very good! We left the dead end!

Just do not understand why, if the camera is not the problem, why only a part of the S3 have this problem?

Regards!
[Galaxy S III Original Android Development] Moster2:
I dont know yet how it exactly happens. It seems to be random and most likely not everyone uses the camera (video recording) a lot. I usually never use it.
[Galaxy S III Original Android Development] adripred:
[MENTION=4604352]Moster2[/MENTION]

I generated these logs when the record button was no longer responding, may be why it did not yield much to complete. I will make a stress test to reproduce the exact moment when this error happens.

Regards!
[Galaxy S III Original Android Development] adripred:
Finally managed to catch the exact moment when this error happens here, follows the log:

Edit: incomplete log, see it in following post;

Attached a screenshot of the generated TMP file in dcim/camera too...

Regards!
[Galaxy S III Original Android Development] adripred:
Sorry, the last log is imcomplete, please see the follows:

Edit: incomplete log, see it in following post.

Regards!
[Galaxy S III Original Android Development] Bäcker:
please put your logs into quote tags :) That makes it easier to read.
[Galaxy S III Original Android Development] adripred:
[MENTION=4604352]Moster2[/MENTION],

Sorry for the last 2 posts, I was trying to copy / paste from the ES explorer editor, but he was cutting the text, now is attached the full log.

Regards!
[Galaxy S III Original Android Development] XeLLaR*:
Hey Guys..

So im using this rom for quite a few days now and im wondering why the transition effects while closing and opening apps are so laggy compared to stock 4.3 and the port of the Note2's 4.4.2 touchwiz rom.

I also have a other phone to compare to (GT-i9001) and the transtions are much smoother there.

How come this happens on a highend device, but not on a low end one?

Gz

X

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Original Android Development] jan922:
Try to edit the transition speed in Developer Options, or just reflash the Rom, my GT-I9300 never had some Ui lags on CM :)
[Galaxy S III Original Android Development] Moster2:
We dont have a correctly working hardware composer. The hwcomposer is used to display surfaces on the screen, etc. I think that's why we also have no working vsync. So it does not look 100% smooth. This is true for all aosp roms.

Ok, its the same error that I get. Its still hard to produce it as it seems random.

So far it looks like it fails at encoding/decoding of the video or at least somewhere between that.
[Galaxy S III Original Android Development] adripred:
Is there anything else I can do to help you?

Regards!
[Galaxy S III Original Android Development] Moster2:
If you can, find a way to always produce this error. The randomness makes it hard to debug.
[Galaxy S III Original Android Development] adripred:
Ok,

To reproduce this error I have to use quite a camera, start and stop the recording several times, shot some pictures and come back for recording videos. Sometimes the error happens quickly and sometimes it takes just to happen or not happen. It happens more when I use a camera app and then go to another camera app.

Thanks for your attention.

Regards,
[Galaxy S III Original Android Development] XeLLaR*:
Aw man, thats really messed up! Wouldnt it be possible to take it from the Note2 KK kernel sources? it uses the same SoC.

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Original Android Development] ayoubij:
with latest nightly im having the google camera stuck when I switch between camera and video .. is anyone experiencing the same?
[Galaxy S III Original Android Development] Moster2:
This is unfortunately not kernel related. Its on the rom's side and samsung is not willing to release sources there.
[Galaxy S III Original Android Development] adripred:
I found a way to happen the error here!

Using the CM camera, I get alternating several times between taking pictures and recording videos.

Take a picture, move to video recording and record a video and I switch to the mode of taking pictures again taking another picture, move to video recording and record a video...

I had the impression that the error happens when generating the snapshot.

The action of taking pictures keeps running, only the video recording stops responding. Sometimes it happens quickly and sometimes it takes longer.

Regards!
[Galaxy S III Original Android Development] XeLLaR*:
Damn....so basically there is no way to get it working? This is a evidence of incapacity on samsungs side right there if you ask me.

Gesendet von meinem GT-I9300 mit Tapatalk 2