yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] stefanACM:
When I try to debug app over Eclipse I got error:

[2012-07-28 03:40:22 - HelloWorld] Uploading HelloWorld.apk onto device '4df171e347e94f4b'
[2012-07-28 03:40:22 - HelloWorld] Installing HelloWorld.apk...
[2012-07-28 03:40:22 - HelloWorld] Installation failed due to invalid APK file!
[2012-07-28 03:40:22 - HelloWorld] Please check logcat output for more details.
[2012-07-28 03:40:22 - HelloWorld] Launch canceled!

I attach LOGCAT.

BTW.

I try to chmode 777 "data" and "local" folder but without success...
[Galaxy S III Original Android Development] Brosa:
Yes but in the Video fix once you put the video to landscape and then switch back to portrait mode the video is raised about 1/4 of the size of the area where the video should be so the top 1/4 of the video is cut off. Here is a logcat.

http://pastebin.com/pxmHnivy
[Galaxy S III Original Android Development] Yusei:
Anyone can confirm that camera fw GDFF03 with CM10 doesnt't work?

Cumps
[Galaxy S III Original Android Development] onurerler:
Probably you are using siyah kernel. Use stock one.
[Galaxy S III Original Android Development] FadeFx:
Hi, can somebody test for me if samba filesharing app from market works on this rom? It does not work on i9000 jb rom and i want to know if it is a general jb incompatibility or it is a bug in i9000 jb rom

–—–—–—–—–—–—–—–—

tapatalked from Galaxy SIII
[Galaxy S III Original Android Development] treble4:
just flashed this i get audio crackling over calls is their a fix i have read through chunks of the thread but cant find anything also audio not working on videos recorded apart from that its great

wrong thread please delete
[Galaxy S III Original Android Development] bala_gamer:
did you use the correct level api for creating the apk?

---------- Post added at 05:34 PM ---------- Previous post was at 05:33 PM ----------

not at all
[Galaxy S III Original Android Development] Basil 123:
Did do a search - having a problem that Viber crashes.

Tried a restore from CM9, data wipe, clean install - all of which fail.

Using latest Siyah kernel.

Cheers

Baz
[Galaxy S III Original Android Development] Cyb3rGlitch:
I've had nothing but trouble with that kernel and CM10. Use the CM10 kernel!
[Galaxy S III Original Android Development] Warm_ice:
Just in case you didn't notice, this is the development section. Remember to discuss everything else here:

http://xdaforums.com/showthread.php?t=1779578

I don't want the thread to be locked up again and again.

Thanks

PS: Mods, please include this reminding post for cleaning.TIA
[Galaxy S III Original Android Development] jayharper08:
Seeing as how this is a DEVELOPMENT thread, please provide a logcat so the developers know what to do and what is happening. Also, this has been reported numerous times........

^^^^^This^^^^^ If you're not going to provide anything DEVELOPMENT related in here, then do not post in THIS thread.
[Galaxy S III Original Android Development] adyscorpius:
Viber crash is recognized app issue. Its incompatibility with JB, and the app devs need to fix it. No issues with CM10.
[Galaxy S III Original Android Development] Cyb3rGlitch:
I'm getting no audio in video recordings.

http://pastebin.com/sYE56Pnk
[Galaxy S III Original Android Development] stefanACM:
Fixed my problem with Debugging apps on Eclipse. Like somebody answer Siayah kernel is problem... I will report in topic for Siayah
[Galaxy S III Original Android Development] scarecrow2012:
Voice Dial Bluetooth

Whenever I try to use voice dial over bluetooth, the app doesn't seem to hear anything. Its like the mic on the bluetooth doesn't work. Calls however work fine, the mic works , other people can hear me.

Ive tried the CM10 voice dial app and also the google voice dial, by disabling the CM10 voice dial app and the results are the same.
[Galaxy S III Original Android Development] bvx89:
As first noticed by wolfboy1984, when you try to kill launched applications using the 'kill app back button' function the last instance of your launcher in the list will end in a start intent/kill launcher loop.

I checked with both Nova Launcher and the stock launcher, both with the same result. The bug shows itself visually by making the screen black apart from the status bar, who are still showing information but the notification drawer won't appear when you slide down on it.

These are the logcats for both launchers:

Stock

Nova Launcher

And this is a summary of what happens:

--------- beginning of /dev/log/system

I/ActivityManager( 2197): Force finishing activity ActivityRecord{412d4440 com.android.launcher/com.android.launcher2.Launcher}

I/ActivityManager( 2197): START {act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10000000 cmp=com.android.launcher/com.android.launcher2.Launcher u=0} from pid 0

I/ActivityManager( 2197): Force finishing activity ActivityRecord{417e30b8 com.android.launcher/com.android.launcher2.Launcher}

I/ActivityManager( 2197): START {act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10000000 cmp=com.android.launcher/com.android.launcher2.Launcher u=0} from pid 0

I/ActivityManager( 2197): Force finishing activity ActivityRecord{413982c0 com.android.launcher/com.android.launcher2.Launcher}

I/ActivityManager( 2197): START {act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10000000 cmp=com.android.launcher/com.android.launcher2.Launcher u=0} from pid 0
[Galaxy S III Original Android Development] superfire71:
Since updating my camera to the latest firmware included in LG8, CM10 builds "cannot connect to camera" CM9 and stock connect no problem. I went from GDFD06 -> GDFF03

Here is log cat

http://db.tt/F40n5MlM

Update: replacing SlimISP_GD.bin file linked below into data/cfw in cm10 and setting permissions rwxrwxr-x fixed the issue!

Here is slim ISP from LG8

http://db.tt/pCyfbXWB
[Galaxy S III Original Android Development] pprice520:
someone tell me how to fix youtube from crashing
[Galaxy S III Original Android Development] mariusdroid:
Hit the logcat .....or the breaks.....
[Galaxy S III Original Android Development] bala_gamer:
front camera preview not working after taking a snap using front camera, working fine with other camera apps.

logcat attached
[Galaxy S III Original Android Development] gokussjx:
Preview #11,

FaceUnlock seems to break.

Logcat: https://dl.dropbox.com/u/27540592/FaceUnlock_LOG.zip

(Ignore if already known/reported)

UPDATE: Ignore. Its fine now. Works perfectly
[Galaxy S III Original Android Development] stefanACM:
And same problem again and again from build to build. I must write this here because nobody didn't (or don't want) see this in Discusion thread.

When headphones is pluged, mic is really really quite almost no sound!

Please do something about that problem because headphones are really important for driving car for ex...

I try LFB and LG2 and LG8 modems, Siyah and stock kernel and everything is same...
[Galaxy S III Original Android Development] ceo.mtcl:
Netflix issue only audio and no video.

https://www.box.com/shared/f95f2a43d92cb1b00a36

☞ sent from GS3 or Nexus
[Galaxy S III Original Android Development] kristofpetho:
Here is a link to the ROM Manager database of codeworkx with the updates:

LINK
[Galaxy S III Original Android Development] manook:
Disable hw overlay in developer options. Fixed it for me....
[Galaxy S III Original Android Development] mariusdroid:
I have this strange problem with sound the speaker remains on after playing ui sound ex when I type or press the app draw button ...this very strange because I remember this problem from my lg 2x day cm7. Logcat http://www24.zippyshare.com/v/25809349/file.html
[Galaxy S III Original Android Development] mcored:
This is fixed in the latest CM9 after 20120728 so hopefully in the next CM10 preview those fixed code will be incorporated.
[Galaxy S III Original Android Development] butcher211:
1.

I just tried this now. Configuration is the same in post 220.

Did call anyone and asked if my mic is getting quiter. I plugged my headphones (Sennheiser CX 300 II) and it was still the same. Are you using headphones with microphone?

2.

On CM9 when i plugged my smartphone to the docking station (Samsung EDD-D200BE) than i could press in the clock app the menu button and choose "dock settings". The menu button doesnt work now. So i have to go to android settings > dock

...

...

Eeeehm... i see now that there are generally no dock settings !? o.O

Not sure if not exists or im just stupid..

Anyway. I wanted to set the dock settings so that the sound goes through my docking station to my speakers. On CM9 it worked. Just wanted to say that.

https://www.dropbox.com/sh/rj4e3ao3jjtkuh1/-Cv1Q3BeAL/LogCat_Default_02.08.2012_(testing_calls).txt
[Galaxy S III Original Android Development] butcher211:
Hi,

me again! ;)

When you are pressing the notification bar withouth moving it just to see the day, it looks like this. Isnt it possible that the space, so the widget buttons, wouldnt be seen?

German: Könnte man die Lücke nicht so verringern, dass die Benachrichtigungssymbole nicht mehr zu einem Viertel sehbar sind? Ich glaube, dass das einfach sein sollte. Falls ja, kannst du mir ein Tipp geben, wo ich nachgucken soll, um das zu ändern? Ich würde das gerne selber machen und dir dann den Code schicken. (jeder fängt ja mal klein an :P)
[Galaxy S III Original Android Development] K Rich:
Seems I have my no audio on calls issue back... Running build 8/1 and flashed newest kernel, camera and audio.zip

LOGCAT:

http://pastebin.com/YBteRRs0
[Galaxy S III Original Android Development] jnr21:
Turn on screen lock sound in settings/sound and reboot, now check if call audio is working.
[Galaxy S III Original Android Development] aHcVolle:
still got the "camera takes a few secs after switching front & rear cam" problem

pastebin:

http://pastebin.com/Tka6tf6R
[Galaxy S III Original Android Development] garyd9:
LED Issues (logcat would be meaningless here -- references to lights.c refers to hardware/samsung/exynos4/exynos4x12/liblights/lights.c)

I'm playing around with CM10 (self-compiled) and noticing that the notification LED is extremely dim under almost all circumstances. It's actually impossible to get a "bright" red or blue notification LED.

The issue appears to be that, in lights.c, that set_light_leds() is using the return value of rgb_to_brightness() to modify the brightness of the individual colors (colours) via get_calibrated_color().

I think this is a flaw in the current code...

rgb_to_brightness() is a function that seems to be intended to "translate" a RGB color to a monochrome brightness. In that case, a solid blue converted to greyscale would indeed be less bright than a solid green. By using rgb_to_brightness() as a modifier to get_calibrated_color(), however, the natural effect of "blue" being less bright than "green" is multiplied.

So, attempting to display the blue LED at full brightness (0x000000FF) results in rgb_to_brightness() returning ((29 * 255)>>8) == 28. That 28 is then passed to get_calibrated_color() which first modifies the blue color to ((0xFF * 0.8) == 204 and then modifies with the brightness value to ((204 * 28 / 255) == 22 (or 0x16). My original 0x000000FF is zapped down to 0x00000016.

So, when I ATTEMPT to get a full brightness blue notification (0xff), what I'm really getting is a LED lit to only 11% of full brightness.

I agree that some "dimming down" of the full power notification LED's is needed, but that is extremely drastic. It's a notification LED and so should be somewhat noticable.

What I've found by "playing around" with the second parameter to get_calibrated_color() is that reducing the LED power to about 80% seems to give a desirable result. (Passing a hardcoded 52400 as the second parameter to get_calibrated_color() is how I tested that.)

Take care

Gary
[Galaxy S III Original Android Development] codeworkx:
No, that's not the cause.

Samsung has limited the LED to < 2mA with update 3.

https://github.com/CyanogenMod/andr...1182796f6475b8cb2ff1781dad873a744b3197#L33L77

brightness = (brightness * LED_R_CURRENT) / LED_MAX_CURRENT + 1;

Trying to use max brightness (255) results in:

brightness = (255 * 40) / 255 + 1;

brightness = 41;

That's the cause of the low led.
[Galaxy S III Original Android Development] garyd9:
That might be contributing to the overall brightness issue, however it completely ignores my point. It will never be (255 *40)/255+1 for blue, as code path before it ever gets to the kernel is reducing the 255 to 22. liblights is artificially reducing the max allowable brightness of the notification LED before it's even being passed to the kernel - and it's doing it based on a formula designed to convert RGB visible light values to grey-scale.

On the other hand, if I attempt to have a max-bright green LED, I'm able to at least come closer as the rgb_to_brightness() will return a "brightness" 5 times greater than that of a blue color.

Being more blunt, my point is that rgb_to_brightness() should not be involved when applied to an LED that does multiple colors.

Take care

Gary

Edit: Here's an interesting FAQ style document on color. Q9 references a similar formula used to convert RGB to brightness: http://homepages.inf.ed.ac.uk/rbf/CVonline/LOCAL_COPIES/POYNTON1/ColorFAQ.html#RTFToC9

Edit2: Here is the origination of the formula used in rgb_to_brightness(). This is taken from the comments at the beginning of the light_state_t structure in android's hardware/libhardware/include/hardware/lights.h:

[I][COLOR=#408080] * Do your best here.[/COLOR][/I]
[I][COLOR=#408080] * - If your light can only do red or green, if they ask for blue,[/COLOR][/I]
[I][COLOR=#408080] * you should do green.[/COLOR][/I]
[I][COLOR=#408080] * - If you can only do a brightness ramp, then use this formula:[/COLOR][/I]
[I][COLOR=#408080] * unsigned char brightness = ((77*((color>>16)&0x00ff))[/COLOR][/I]
[I][COLOR=#408080] * + (150*((color>>8)&0x00ff)) + (29*(color&0x00ff))) >> 8;[/COLOR][/I]
[I][COLOR=#408080] * - If you can only do on or off, 0 is off, anything else is on.[/COLOR][/I]
[Galaxy S III Original Android Development] :
Problem solved! :victory:
[Galaxy S III Original Android Development] gapone:
Face unlock crashes.

I have the latest CM10 installed with the latest kernel (inc. update4). Face unlock crashes when trying to start it from the settings. Here is my logcat...
[Galaxy S III Original Android Development] jnr21:
Cm10 discussion thread: http://xdaforums.com/showthread.php?p=28926143

Cm10 experimental builds: http://www.clockworkmod.com/rommana...t&name=codeworkx&deviceName=Samsung Galaxy S3
[Galaxy S III Original Android Development] AndyCr15:
I have an Eye-Fi card in my DSLR camera, it effectively sets up a WiFi hotspot within the SD Card, the app on my phone connects to the SD Card and downloads photo's as they are taken. Works great on stock and on past phones, but with CM10 it causes a reboot every time.

I've attached a logcat, I don't know how these work, do the log details last through a restart?

If there is any better info I can give, please let me know as it's the only think that doesn't work for me on CM10 and I'd love to know a fix.

Thanks.
[Galaxy S III Original Android Development] BattleCat:
Internal SD Card now not mounting

Using latest nightly (4th Aug). Worked perfectly then this morning a widget said it couldnt locate the SD (internal). Checked in Root Explorer and doesnt look like it was mounted. Rebooted and couldnt mount (even in clockwork recovery). Potentially a corrupted filesystem but logcat attached just in case! :)

https://dl.dropbox.com/u/23985333/logcat.rtf

edit: Reflashed with same build, wiped dalvik all ok. Remembered I might have been running Siyah Kernal not CM, so will leave on CM and see if problem repeats
[Galaxy S III Original Android Development] superfastmonkey:
Hi guys, just having an issue trying to install swype beta on 08.03 (full wipe) and 08.04v2 (upgrade)... it just times out on 'checking installer version' at the start... another member confirmed the bug. logcat attached if anyone gets time for a look. Cheers, Gav
[Galaxy S III Original Android Development] jnr21:
There was some broken build (sdcard not found) yesterday, codeworkx uploaded new build arter that. Maybe you has that broken one installed.
[Galaxy S III Original Android Development] dboechat:
Since the latest CM10 preview my home button stopped working for the third time now. When I press it, the notification bar blinks for a second and there's a touch sound but nothing happens. I have to reflash the ROM to make it work again.
[Galaxy S III Original Android Development] TecQuality:
I can't use the camera with 0804, nothing happens from the lock screen and i haven't any icon into the drawer

http://db.tt/1Qkpp6Ny

Sent from my Taptalked GT-I9300 using Jelly Bean
[Galaxy S III Original Android Development] debenham:
Mine was doing the same thing.

The logcat indicated that the keyguard was getting in the way here.

By disabling then re-enabling the lock screen I was able to get the home button working
[Galaxy S III Original Android Development] Biertje_:
front facing camera error

Current cm10 build info is shown in the screenshot, my front facing camera freezes after a photo is taken. Also see my logcat.
[Galaxy S III Original Android Development] brian6685:
I can confirm this happens to me also.
[Galaxy S III Original Android Development] gapone:
Settings crash when testing memory leak

I was testing the memory leak by going to apps--->active--->back to desktop and by going to settings--->about phone--->status--->back to desktop. After a while I was making those cycles and my memory decreased, settings also crashed. Here is the logcat...

This happened with the 04082012 build and I'm using LF5 modem.
[Galaxy S III Original Android Development] K Rich:
Call audio still being an issue after completely wiping the phone and going back to stock (LG8).

First logcat is with screen lock sound enabled and sound volume up.

http://pastebin.com/e0DYmEWC

Second logcat is with screen lock sound disable and phone on vibrate.

http://pastebin.com/ehjhaf7f

Reboot was done between logs to create the issue. I hope its just a simple fix.

Edit: forgot to mention that with volume up and screen lock sound enabled is when call audio works until a reboot with phone on vibrate and screen lock sound disabled. Which makes me feel it isn't a modem issue, as I am able to get call audio, I just have to "jump through hoops" to get it. Let me know what you think codeworkx or xploidwild.

Should also mention that I tried LFB & LEA with the same result.
[Galaxy S III Original Android Development] TecQuality:
try to change your modem, try the LFB :)
[Galaxy S III Original Android Development] ss2i9100g:
Launcher FC continuously, reboot resolve the issue.

http://pastebin.com/MBrBWfmx

Latest cm10 0806
[Galaxy S III Original Android Development] sodeknetters:
Well known bug, also affects cm10 on other devices, search this thread & discussion thread for "memory leak" for more info.
[Galaxy S III Original Android Development] binaryanomaly:
SIM Toolkit Issues (crash)

Hi devs

There seems to be an issue with the SIM Toolkit crashing, which I need for work and therefore prevents me to use CM :(

Any chance this gets fixed? ;)

thx
[Galaxy S III Original Android Development] debenham:
dock audio not working

When I connect to a car-audio dock the phone is recognising that it is plugged into the dock (can tell from tasker and from logcat) - but dock audio isn't being re-routed to the cable.

If I go to the dock section in settings the Audio option is greyed out and can not be toggled.

logcat output has the following noted:

E/WiredAccessoryObserver( 2172): Ignoring dock event as Audio routing disabled {SUBSYSTEM=switch, SWITCH_STATE=2, DEVPATH=/devices/virtual/switch/dock, SEQNUM=8788, ACTION=change, SWITCH_NAME=dock}

full logcat output can be found at http://pastebin.com/0rBRguDD
[Galaxy S III Original Android Development] DvTonder:
The code is not ported yet
[Galaxy S III Original Android Development] ss2i9100g:
Can't turn on WiFi, the button looks like its disabled. Suddenly works

Latest build 08 modem XXLH1

pastebin.com/s4ZwGWi5
[Galaxy S III Original Android Development] garyd9:
liblights issue...

attention and notification LED's are still conflicting. The following sequence will result in no LED being illuminated:

turn on attention LED, turn on notification LED, turn off attention LED.

(expected: notification should be on)

This only happens in rare cases (logcat has nothing meaningful.) I know you folks are busy trying to deal with other BS, so I'll whip up a fix tonight, submit to gerrit with my own -1 (in case you want to review the code before I'm done testing) and test it tomorrow while at work.

Take care

Gary

Edit: I'm not going to be able to finish this tonight - in the middle of a nice size thunderstorm that knocked out power. I'll work on it in the morning (GMT-5 morning)
[Galaxy S III Original Android Development] gapone:
Possible Media scanner problem

2 nights ago my phone didn't sleep at all because of media scanner (this was with 10-20120810-EXPERIMENTAL-i9300-CODEWORKX) and the last night it kept my phone alive (this was with 10-20120810-EXPERIMENTAL-i9300-CODEWORKX) for about 30mins (don't know if this 30mins is normal). Seems like log is full of media scanner ignoring that blobs folder which clockworkmod creates. Here is the logcat...
[Galaxy S III Original Android Development] butcher211:
When i press the red area of that picture google now starts. I have deactivated the search bar.

http://pastebin.com/ybkqH9zJ

PS: I moved the widget for a test and it still happens.
[Galaxy S III Original Android Development] Daelyn:
Media Scanner is a load of crap, even Sammy original one. Use app "Rescan Media Root" to disable it.

Who needs scan anyways? I know where my files are and can find/browse them myself. :)
[Galaxy S III Original Android Development] codeworkx:
reported to koush.

Workaround:

adb shell touch /storage/sdcard0/clockworkmod/.nomedia

adb shell touch /storage/sdcard1/clockworkmod/.nomedia
[Galaxy S III Original Android Development] butcher211:
Hi,

when i reboot the phone (not shutdown and start) the apn settings get lost.

What i did:

clear logcat file

reboot phone

take screenshot

activate airplane mode

take screenshot

deactivate airplane mode

take screenshot

dump logcat file

Eplus, Germany (LH1 Modem)

Logcat: https://www.dropbox.com/s/y15njf6ar2zbnj9/2012.08.11 APN settings.txt

(pastebin has a limit of filesize for freeusers -.-)

*EDIT*

Next problem:

when i plug my phone to dock station the dock settings will be grey (before they arent and a dialog says to me that i have to plug my device to the docking station) and i cant press them. on cm9 i could press them and choose the option that the sound of my smartphone goes through the dock station plugged aux cable and i cant listen to the music from my speakers. now i have to to plug the speaker cable like my head phones to the top of my device.

(4th picture)

Logcat: http://pastebin.com/Y483mrP8
[Galaxy S III Original Android Development] :
don't have clockworkmod folders at all, but had mediascanner wakelock, sent you pm yesteday with link to pastebin, but have no idea if it is useful as i am on holidays so did it via terminal emulator on phone and with commands from my head.. sorry.
[Galaxy S III Original Android Development] codeworkx:
wasn't helpful because you've cut the log.

always provide full logs!!!
[Galaxy S III Original Android Development] ss2i9100g:
I install latest 10082012 since day 1 only now it got crazy and kept FC launcher continuously a reboot solve it. Maybe it the memory issue .

pastebin.com/nWr2ytt7

Thanks
[Galaxy S III Original Android Development] 90paolo:
i'm on latest cm10 20120810 and i found this little bug

seems related to italian tranlation of aosp keyboard auto-correction

it's off, media, massima, massima but should be off, MINIMA, media, massima
[Galaxy S III Original Android Development] DocRambone:
No wifi bug: install CM10 gives "can not connect" if a samsung JB rom has been installed. (full wipe before install of CM10)

Logcat:

http://speedy.sh/9sRHh/alogcat.2012-08-19-17-09-16-0200.txt