yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] ephraim:
To Mods: Please give me a chance to say what i have to say to this person.

To You: Do you even realize that once in a while a person may post unintentionaly on a wrong thread? And who are you calling n00b? Compared to me you are the n00b, not just by the number of thanks or posts (which doesn't really mean anything) but by adding an even stupid and useless post. If codeworkx wants to close this thread then it is up to him not YOU or any of us. I have been following this thread without posting anything and now you bash me with a useless post pertaining i am a n00b? Typical.
[Galaxy S II Original Android Development] codeworkx:
This is worth a perma ban.
[Galaxy S II Original Android Development] roviati:
Hello codeworkx,

I tried to use Rom Manager but flash recovery only permit me choose Samsung Epic4G and GalaxyS i9000. Is correct this? beacose i cant see something like I9100

Thanks a lot
[Galaxy S II Original Android Development] codeworkx:
a) this is no Q&A thread

b) dont be lazy http://xdaforums.com/showpost.php?p=21718808&postcount=2844
[Galaxy S II Original Android Development] Net.silb:
I'm just trying to help people and to get them off your back codeworkx.

Please do not flame me for posting this!

Who ever did the following (Like I did):

- Install RomManager

- Wanted to download new build via RomManager

- Had to flash CWM

- Picked i9000

- Flashed

- And now can't get into proper CWM recovery

In order to get into proper, working CWM recovery do this:

- When phone is ON.

- Long press power button

- Press Reboot

- Choose Recovery

- Press OK

The phone should now reboot into a proper, working CWM recovery. :)

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

Also posted by codeworkx in the other thread:

"Fakeflash:

- press flash in rommanager: downloads a little zip which includes a special ramdisk and the recovery.

- flash a rom from rommanager: boot into current recovery, apply the downloaded zip which replaces the whole root filesystem

- restart recovery which boots into the recovery from the previous downloaded zip

- reboot: changes are done (ramdisk is ramdisk and not permanent)"
[Galaxy S II Original Android Development] codeworkx:
There's still no reason for spaming this thread with Q&A stuff.

MOEPMOEPMOEPMOEPMOEPMOEPMOEPMOEPMOEPMOEP

Kindergarden Police is here to close the thread.
[Galaxy S II Original Android Development] codeworkx:
To make it clear:

- ROMs and Modems are available via ROM-Manager now.

- If you're running ICS, your device won't be recognized as I9100. We're working on it. Be patient. ROM-Manager is handling around 80 Devices, we don't want to break something. ;-)

- If you're running GB, everything is fine.

Remind:

This is a development thread. If you got questions or want to tell us something which doesn't help development, use the Q&A Thread.

Link at first Post.
[Galaxy S II Original Android Development] biersoeldner:
Reverse-Engineered Mali GPU Driver

Open-Source Driver for Mali GPU http://www.phoronix.com/scan.php?page=article&item=arm_mali_reverse

I hope this will help the developer in the future.
[Galaxy S II Original Android Development] codeworkx:
Thanks for NOT READING.

http://xdaforums.com/showpost.php?p=21717593&postcount=2843
[Galaxy S II Original Android Development] YaviSGS:
Where is the download link?
[Galaxy S II Original Android Development] codeworkx:
New build will be available in a few minutes.

Read the whole 1st and 2nd post for download link and changelog.

Please use the User Discussion Thread for any Q&A:

http://xdaforums.com/showthread.php?t=1419102
[Galaxy S II Original Android Development] Phone_Guru:
Can someone please post the new kernel, preferably as a flashable zip?

Infracted.
[Galaxy S II Original Android Development] codeworkx:
Flash the full build.

Last three posts = FAIL!

Use the User Discussion Thread. Thank you.

http://xdaforums.com/showthread.php?t=1419102
[Galaxy S II Original Android Development] MariusWildfire:
what has changed with the new kernel ?

can't find some information about it..

Infracted. :)
[Galaxy S II Original Android Development] codeworkx:
Great decision to post here.

A mod will delete it, too. And you'll probably get a ban. ;-)

I'm no wizard. So please reproduce the problem, get logs and come back again.

In short: LOG OR GTFO!
[Galaxy S II Original Android Development] arekkaras:
All calls forwarded to VM

Hi Codeworkx,

It's a bit scary to post here now;)

Anyway, randomly I get notification in status bar that all my calls are being forwarded to voicemail.

My default network (Orange UK) setting are:

call waiting ON

forward calls to VM only when not available

Once I open the notification and click on Calls Forwarding, phone receives setting from network and everything goes back to normal.

Logcat: http://pastebin.com/R8E2FJgW
[Galaxy S II Original Android Development] codeworkx:
Your log is full of crashing ****:

- beautiful widgets

- com.nolanlawson.logcat

- google analytics

Didn't find anything helpful.

logcat -b radio would be more clever.
[Galaxy S II Original Android Development] arekkaras:
I'll try to reproduce the issue and use "logcat -b radio" next time.

Thanks.
[Galaxy S II Original Android Development] codeworkx:
New Build out, read 1st and 2nd post.

Gapps v10

If you're switching to GApps v10 from a previous version, do a full factory reset / data wipe, otherwise your account will not work.
[Galaxy S II Original Android Development] codeworkx:
CWM flashable GPS modules for testing:

KP8: Download

KPA: Download

LP2: Download

LP6: Download

User Discussion Thread:

http://xdaforums.com/showthread.php?t=1419102
[Galaxy S II Original Android Development] krzychuhtc:
Navigation from google maps doesn't work force closed.
[Galaxy S II Original Android Development] codeworkx:
Only for you, because you're special:

-----

new build out
[Galaxy S II Original Android Development] arekkaras:
Hi,

The issue has occurred few more times, I managed to pull the log (logcat -b radio) twice, here it is:

http://pastebin.com/2M50KHcS

http://pastebin.com/Nn7cZSZR
[Galaxy S II Original Android Development] codeworkx:
new build, new baseband firmware, new fun.

enjoy it!
[Galaxy S II Original Android Development] codeworkx:
new gapps. probably the final version.

faceunlock is a separate package because not every CM-Device has a front camera.
[Galaxy S II Original Android Development] codeworkx:
Build 02122012

- RIL: fixed 2g/3g toggle

- RIL: fixed network search

- RIL: cosmetic fixes

- Camera: additional focus, whitebalance and scene modes

- upstream changes

Problem with asec containers and big apps is still there.
[Galaxy S II Original Android Development] codeworkx:
Build 02172012

- updated kernel

- upstream changes

- problem with secure containers still exists

- video problems are still there
[Galaxy S II Original Android Development] codeworkx:
The CyanogenMod Project needs your help:

http://www.cyanogenmod.com/blog/cyanogenmod-needs-your-help
[Galaxy S II Original Android Development] codeworkx:
We've reached our goal:

http://www.cyanogenmod.com/blog/weve-reached-our-goal
[Galaxy S II Original Android Development] codeworkx:
Build 02202012

- Added Device Specific Settings

- mDNIe and gamma settings

- Touchpanel settings

- HSPA settings

- Gyroscope calibration
[Galaxy S II Original Android Development] codeworkx:
Build 20120225

- LP6 Kernel

- device settings: disable touchkey backlight

- built from cyanogenmod mainline repos

May contain more bugs than previous builds. ;-)
[Galaxy S II Original Android Development] codeworkx:
Build 20120228

- fixed screen flash on crt off again

- fixed video color issues (still a little line at the bottom which doesn't work properly)

Probably the best cm9 build for galaxys2 till now.

Enjoy it!
[Galaxy S II Original Android Development] codeworkx:
Build 20120229

- Upstream changes

-- Facebook sync

-- Interface Settings: signal status style

-- National data roaming

-- Configurable 0, 90, 180 and 270 degree rotation
[Galaxy S II Original Android Development] codeworkx:
Team up and ask samsung-mobile for sourcecode:

http://www.change.org/petitions/sam...t-achieve-full-potential-of-purchased-devices

SIGN IT!!!
[Galaxy S II Original Android Development] codeworkx:
We've merged any Galaxy S II specific sourcecode into CyanogenMod mainline.

Nightly builds should happen frequently now.

Nightly builds can be found at ROM-Manager or at

http://download.cyanogenmod.com

Google Apps

Get the latest Version from: http://goo-inside.me/gapps

Device specific changelog

http://cm-nightlies.appspot.com/?device=galaxys2
[Galaxy S II Original Android Development] codeworkx:
UNOFFICIAL BUILD

http://developer.clockworkmod.com/d...e-cm-9-20120303-CODEWORKX-galaxys2-signed.zip

- fixed hw codecs (videos smooth as butter)
[Galaxy S II Original Android Development] Net.silb:
Please help... http://xdaforums.com/showpost.php?p=23261355&postcount=10877
[Galaxy S II Original Android Development] codeworkx:
Dude, this is a development thread.

Cleary statet at OP.

Use the Discussion thread like advised.

And...

Everyone knows about your problem because you've posted it 20 times on the discussion thread, wrote two emails to me, wrote at irc to me, pm'ed me....

WTF is wrong with you?

I'm not your personal supporter, i'm a dev and there are more important things to do for me than careing about your problem.

If you don't get a answer then try to fix it on your own, get used to it or flash a damn samsung rom.

BUT STOP ANNOYING US!!!!
[Galaxy S II Original Android Development] codeworkx:
Same for you, this is a development thread.

Look at discussion thread, there's a link:

http://cm-nightlies.appspot.com/?device=galaxys2
[Galaxy S II Original Android Development] NeoS:
And here we go again. Let me spell this out for you guys.

T.H.I.S. I.S. A. D.E.V.E.L.O.P.M.E.N.T. T.H.R.E.A.D.

N.O. Q.U.E.S.T.I.O.N.S.

Infractions will be given out to people who ignore this warning. (again)
[Galaxy S II Original Android Development] jasonkx:
The sensor Gyroscope and Movement arent working when restarting the phone allways need to reinstall the ROM to get working again.
[Galaxy S II Original Android Development] XpLoDWilD:
Technically speaking reinstalling the ROM makes your phone reboot. Just tested and it works fine, you're holding it wrong.
[Galaxy S II Original Android Development] KSTu:
or,maybe,is not calibrated! :)
[Galaxy S II Original Android Development] codeworkx:
If someone wants to work on opensource camera or omx:

- checkout cm sources

repo init -u git://github.com/CyanogenMod/android.git -b ics

- create .repo/local_manifest.xml

[B].repo/local_manifest.xml[/B]

<?xml version="1.0" encoding="UTF-8"?>
<manifest>

<project path="device/samsung/galaxys2" name="codeworkx/android_device_samsung_galaxys2" remote="github" revision="ics"/>
<project path="bionic" name="codeworkx/android_bionic" remote="github" revision="ics"/>
<project path="frameworks/base" name="codeworkx/android_frameworks_base" remote="github" revision="ics"/>
<project path="hardware/libhardware" name="codeworkx/android_hardware_libhardware" remote="github" revision="ics" />
<project path="hardware/samsung" name="codeworkx/android_hardware_samsung" remote="github" revision="ics" />
<project path="vendor/samsung" name="codeworkx/proprietary_vendor_samsung" remote="github" revision="ics" />

</manifest>

- repo sync

HAL

https://github.com/codeworkx/android_hardware_samsung/tree/ics/exynos4/hal

OMX

https://github.com/codeworkx/android_hardware_samsung/tree/ics/exynos4/multimedia
[Galaxy S II Original Android Development] StevenHarperUK:
Bug with AudioService

Hi codeworkx,

Firstly thanks for all the hard work.

I have found two bugs with the Audio Control on my i9100P

When listening to Music with headphones, if another audio stream need to be heard (incoming notification), the headphones are muted and the interrupting audio plays on the phones speaker (not on the headphones).

Also when the 2nd audio stream is finished, the Headphones are always returned to Audio volume 1 - instead of the previous volume. On the next track the volume reverts back to normal.

E/AudioHardwareYamaha( 1690): setHeadphoneVolume: Set Headset Analog Volume control(1)
V/yamaha::media::CManager( 1690): setHeadphoneVolume(volume=1)
V/yamaha::media::VolumeCtrl( 1690): VolumeCtrl::setAnalogVolume(id=1, volume=5)
V/yamaha::media::VolumeCtrl( 1690): VolumeCtrl::createVolume()

I have a full checkout / build working - but I am too new to Android Rom development to debug this any further (I can code in C and Java).

Here is a full logcat
[Galaxy S II Original Android Development] tlkh:
Just wanted to add on something the post above missed.

If one presses the volume buttons, the volume "resets" itself and goes back to normal.

Sent from my Samsung Galaxy S II running CM9
[Galaxy S II Original Android Development] StevenHarperUK:
Another Sound Event Bug

Hi Again,

Another bug.

If you have music playing in the foreground, then insert some headphones the sound is defaulted to level 1, however when you attempt to adjust the volume, the sound jumps to its correct (remembered) setting.

Looking at the logcat it appears to be a problem with the parameters sent to setParameter method.

I/AudioHardwareYamaha( 1690): setHeadphoneVolume: We don't need to set Analog volume
I/AudioHardwareYamaha( 1690): ### setDeivceInCall = 00400000h mEnabledDualMic 1
I/HeadsetService(12515): Headset=true; Bluetooth=false
I/HeadsetService(12515): Selected configuration: headset
I/EventHub( 1814): New device: id=19, fd=247, path='/dev/input/event9', name='sec_jack', classes=0x1, configuration='', keyLayout='/system/usr/keylayout/Generic.kl', keyCharacterMap='/system/usr/keychars/Generic.kcm', builtinKeyboard=false
I/InputReader( 1814): Device added: id=19, name='sec_jack', sources=0x00000101
[B]E/HeadsetService(12515): Invalid argument error in setParameter(1000, (short) 10000) == -4[/B]
I/AudioHardwareYamaha( 1690): AudioHardware::setDevices(devices=00000004h, mask=00023FFFh)
V/yamaha::media::CManager( 1690): setDevices(devices=00000004h)
V/yamaha::media::VolumeCtrl( 1690): VolumeCtrl::createVolume()

This is not effected when you pull out the headphones, as the music stops and the event that is caused when you hit the play button seems to fix the volume again.

Here is a bigger logcat - The first part is me inserting the headphones (while music is playing) after the gap is when I push the volume button.
[Galaxy S II Original Android Development] StevenHarperUK:
More digging

Hi again,

I have done a bit more digging:

The DSPManager.java is where the event is getting generated

packages/apps/DSPManager/src/com/bel/android/dspmanager/service/HeadsetService.java

private void updateDsp(SharedPreferences preferences, EffectSet session) {
session.mCompression.setEnabled(preferences.getBoolean("dsp.compression.enable", false));
EffectSet.setParameter(session.mCompression, 0, Short.valueOf(preferences.getString("dsp.compression.mode", "0")));

session.mBassBoost.setEnabled(preferences.getBoolean("dsp.bass.enable", false));
session.mBassBoost.setStrength(Short.valueOf(preferences.getString("dsp.bass.mode", "0")));

/* Equalizer state is in a single string preference with all values separated by ; */
session.mEqualizer.setEnabled(preferences.getBoolean("dsp.tone.enable", false));
if (mOverriddenEqualizerLevels != null) {
for (short i = 0; i < mOverriddenEqualizerLevels.length; i ++) {
session.mEqualizer.setBandLevel(i, (short) Math.round(Float.valueOf(mOverriddenEqualizerLevels[i]) * 100));
}
} else {
String[] levels = preferences.getString("dsp.tone.eq.custom", "0;0;0;0;0").split(";");
for (short i = 0; i < levels.length; i ++) {
session.mEqualizer.setBandLevel(i, (short) Math.round(Float.valueOf(levels[i]) * 100));
}
}
[B]EffectSet.setParameter(session.mEqualizer, 1000, Short.valueOf(preferences.getString("dsp.tone.loudness", "10000")));[/B]

session.mVirtualizer.setEnabled(preferences.getBoolean("dsp.headphone.enable", false));
session.mVirtualizer.setStrength(Short.valueOf(preferences.getString("dsp.headphone.mode", "0")));
}

This method gets dealt with by the AudioEffect object

frameworks/base/media/java/android/media/audiofx/AudioEffect.java

public int setParameter(byte[] param, byte[] value)
throws IllegalStateException {
checkState("setParameter()");
return [B]native_setParameter(param.length, param, value.length, value);[/B]
}

/**
* Operation failed due to bad parameter value.
*/
public static final[B] int ERROR_BAD_VALUE = -4;[/B]

The Native method returns a -4 (see above) this is a bad parameter

E/HeadsetService( 2300): Invalid argument error in setParameter(1000, (short) 10000) == -4

Now I suspect its the second parameter of the call param, the ones that gets handed to the native method.

The value is 1000

However in the file

./frameworks/base/media/java/android/media/audiofx/Equalizer.java

The Statics for the Params in there are small numbers - 0-9.

This is as far as I have got, a comment in the top of Equalizer.java says

// These constants must be synchronized with those in

// frameworks/base/include/media/EffectEqualizerApi.h

But the frameworks/base/include/media/EffectEqualizerApi.h is missing.
[Galaxy S II Original Android Development] StevenHarperUK:
Car Dock

Hi Codeworkx

I have today received an Official Samsung SII Car Dock.

The dock has 1 USB connector (that goes into the phone) that is then split out into a USB power input and a Audio Jack input.

Currently the Audio Jack does not work. The expected behaviour is that the AudioService class should get an appropriate intent when it senses the Audio connection being connected.

private class AudioServiceBroadcastReceiver extends BroadcastReceiver {
@Override
public void onReceive(Context context, Intent intent) {

I have added some extra logging into the AudioService.java and while connected to adb via wireless, plugged in the dock.

I do get this intent (ACTION_DOCK_EVENT)

V/AudioService( 2028): Broadcast Receiver: Got action = android.intent.action.DOCK_EVENT
V/AudioService( 2028): Broadcast Receiver: Got ACTION_DOCK_EVENT, dockState = 2

The Extra dock state is Intent.EXTRA_DOCK_STATE_CAR which is right - infact on the device I can see the dock Icon.

However the current code in that block sets the Audio to be the BT Car Dock.

I had hoped that this may be the reason why I was getting no audio - so I changed the default to the USB Analog Dock

//config = AudioSystem.FORCE_BT_CAR_DOCK;
config = AudioSystem.FORCE_ANALOG_DOCK;

This didn't seem to work either, so I noticed that the config for the force is actualy set for each type - so I added the following after the AudioSystem.FOR_DOCK

AudioSystem.setForceUse(AudioSystem.FOR_MEDIA, config);

Again this did not work.

So I had an Idea - the dock event is not the same as an audio plug even - when I pug into the normal audio jack I get a new Intent (for the top jack).

I dont get anything for the dock audio.

Further down the same class I see the following

} else if (action.equals(Intent.ACTION_USB_ANLG_HEADSET_PLUG)) {
int state = intent.getIntExtra("state", 0);
Log.v(TAG, "Broadcast Receiver: Got ACTION_USB_ANLG_HEADSET_PLUG, state = "+state);
synchronized (mConnectedDevices) {

This seems to be what I am looking for.

So what is stopping the intent event being fired?

Is there something missing from the Kernel to support the USB Analog Headset?

My Java debugging is pretty good, but my lack of Kernel & Android experience is stopping me get any further.

Thanks

Steven
[Galaxy S II Original Android Development] tugler:
Regarding the SMS problem:

My SMSC is +43676021 (T-Mobile Austria)

If I enter the PDU

AT+CMGW=19

059134760612110000910000AA0CC8F71D14969741F977FD07

in *#*#4636#*#* i can send SMS till next reboot.

SMSC is stored on the SIM, i can read it in GB and on other Handys but CM9 does not read the SMSC at startup? If i press update it shows me update error.

I have no SIM PIN.

Please Codeworkx have a look at this problem because it is really anoying and it prevents me from using CM9.

thanks in advance tugler
[Galaxy S II Original Android Development] gladiac:
Finally, I'm not the only one. I experience that problem since the first releases in december. Some wicked crap goes on in TMA's network. I tried RILs of newer samsung roms, old sbl, new sbl, pretty much all modems and a lot of other things. Interestingly it works on sammy-roms without a problem. Fyi you cannot enter +43676021 since that is the normal human readable format but sammy modems seem to only accept the PDU-format (059134760612).

You should still post in the user discussion thread.
[Galaxy S II Original Android Development] codeworkx:
About video recording...

On 640x480 video frames are coming up fine, but no video is saved because of:

E/MPEG4Writer( 1856): Missing codec specific data

E/MediaRecorder( 3007): stop failed: -1007

I've zero clue why this happens.

If we change to a higher resolution the fimc scaler doesn't get informed about the higher resolution and still asumes we're on 640x480. If we start recording it gets bombed with a huge amount of data and fails because it didn't expect the amount of data from the higher resolution.

It's possible to hack it very dirty in the kernel driver. But that's no fix.

With these dirty hack the same thing as on 640x480 appears:

E/MPEG4Writer( 1856): Missing codec specific data

E/MediaRecorder( 3007): stop failed: -1007

What to do now?

Inform the fimc scaler about the higher resolution. Must be something on the camera app we're missing.

But we don't know what.

And find out why

E/MPEG4Writer( 1856): Missing codec specific data

E/MediaRecorder( 3007): stop failed: -1007

happens.

I'm stuck and sick.
[Galaxy S II Original Android Development] Phistachio:
What if you change the codec which cm9 is using? Instead of using MPEG4, you could use h.264 and 3GPP format.

But, regarding the storage and why it fails, that renders me clueless aswell.
[Galaxy S II Original Android Development] alangrig:
Please advice if this might be helpful:
[Galaxy S II Original Android Development] phi770:
@tugler

I've the same problem with t-mobile austria. For now I use the "go sms pro" app, where you can enter the smsc number manually, which is saved in the configuration file... Better than entering it on every reboot, but repairing this would be best, so i could use the plain stock sms app.

I'm not able to repair it...
[Galaxy S II Original Android Development] kroat999:
i have the exacte same problem with Drei 3 Austria also using the go sms workaround
[Galaxy S II Original Android Development] StevenHarperUK:
Audio Dock Fixed

http://review.cyanogenmod.com/#change,14046

Found that the dock usb analogue device (dock) emits the status 2 (which is the value for usb digital for (usb_audio)

Best solution was to add another observed device.

Submitted.