yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] codeworkx:
What's the problem at all? Is it soooooo hard to follow some simple rules and not beeing an asshole?

Like our Mod said before:

1. Read the first two pages and the last five

2. Read the Q&A Thread -> http://xdaforums.com/showthread.php?t=1176411

After this, most of the questions are done.

Next:

If we loose joy on this, you'll lose it too because we'll simply stop developing because WE DON'T HAVE TO!!!

We're doing this for fun, for free and in our free time while you're enjoying the sun outside. Respect it!

Accept to use the Q&A thread for questions and this thread only for development related things and proper bug reports (including logs).

This saves us time, and saves your time.

Create a new post if you feel to need your own KANG and make sure to support your users. We'll not do it!!!

On some cm7 threads for other devices you'll not get a single answer from a device maintainer at all

because they've stopped reading xda a long time ago because they got pissed. i hope you're aware of this.

Seems i'm the last one of #teamhacksung here.

Coolya deleted his xda account and atinm will only read this thread every month once a time. gratulations.
[Galaxy S II Original Android Development] the_scotsman:
My ban hammer swinging arm is getting VERY itchy!

I suggest you all keep the discussion on topic, or the hammer WILL be swung...

NO more spamming, trolling, asking for ETAs or asking DUMB questions. Use the CM7 Q&A thread.

Pulser has already warned you, so this is just a reinforcement of what he said.

We're sick of seeing threads being cluttered up by USELESS CRAP. You will only drive the devs away, and have no ROMS left :rolleyes:

I DOUBLE DARE ANYONE to write a useless post....
[Galaxy S II Original Android Development] the_scotsman:
Ok, anything else not ON TOPIC will be deleted and the poster will be dealt with. If you have an issue with a post, or any member, please use the Report Post button or PM a mod.

DO NOT continue to argue in a ROM thread, as this helps no one, and quite frankly, we are f***ing sick of it.

It's here and about to strike ;)
[Galaxy S II Original Android Development] Mikey:
LOCKING THE THREAD DUE TO HOT-HEADS.

People step away, breath and when this thread is re-opened, it will be cleaned out.

Re-Think what you wanna post, cause there are good odds people will be taking short, long vacations.

Good night!!!!
[Galaxy S II Original Android Development] Mikey:
You my friend deserves a ban......since i have a gut feeling you DIDN'T read post 1.

Keep asking questions like that and *hint* you will be.
[Galaxy S II Original Android Development] the_scotsman:
Right,

I've just deleted SEVERAL HUNDRED posts from the thread.

ALL QUESTIONS SHOULD BE POSTED IN THE CM7 Q&A THREAD.

NO MORE OFF TOPIC CRAP, NO MORE FLAMING, NO MORE ARGUING.

Any OFF TOPIC posts will be deleted without notice and vacations will be handed out. It's not rocket science...follow these simple instructions.
[Galaxy S II Original Android Development] goldbergx:
(this is in reply to atinm's pm, he/his mailbox is probably not accepting pm's anymore)

I had 195 JPEG images, 13 PNG Images - removed all JPEG images and isolated it to 2 png images (attached) that seem to be the culprit (no issue with the jpeg images, other 11 png images seem to load correctly - there were no thumbnail images for the 2 offending files)

Another thing - the gallery also has trouble creating thumbnails (or previews?) for .mp4 files.

Separate issue - getting FCs every now and then when I try to receive or make a call, couple of logs attached.

Hope this helps.
[Galaxy S II Original Android Development] jazzor:
There is something amiss about the kernel code in the CM git repositories. I remember someone who had previously put up an unofficial build of CM complained that the vibrator is not fixed despite the commits saying it is.

This is indeed true. The current kernel sources in CM for c1 does not seem to match the one in the current nightly. If you look at the git code for tspdrv.c, the kernel dmesg strings do not exist:

<7>[ 64.567863] tspdrv: Enable time = 0 msec

<7>[ 64.569526] tspdrv: ImmVibeSPI_ForceOut_AmpEnable (1)

<7>[ 64.569706] tspdrv: Enable time = 30 msec

<7>[ 64.577291] tspdrv: set_vibetonz (0)

<7>[ 64.577979] tspdrv: set_vibetonz (1)

<7>[ 64.600225] tspdrv: set_vibetonz (0)

<7>[ 64.600554] tspdrv: Enable time = 0 msec

<7>[ 64.600926] tspdrv: set_vibetonz (0)

Indeed, replacing any AOSP/CM build with the current nightly kernel will make vibrations work, but a kernel built from sources will not work (phone sleeps, but vibrations dont happen after).

Could the devs please update the kernel code to the same that used in the current nightly (no. 6)?
[Galaxy S II Original Android Development] L10nH34Rt:
When you "repo sync" doens't it download the latest

precompiled

kernel by default?

http://review.cyanogenmod.com/#change,6998
[Galaxy S II Original Android Development] codeworkx:
That's not true.

Our kernel is built from latest sources available on CyanogenMod github repo.

It's everything there you need to make it working.

i would say the logging is created by using a simple printk to print out the function name + arg so you cannot easily grep for them.

there's only one little kernel change to make the vibrator working. the rest is done in userspace.
[Galaxy S II Original Android Development] jazzor:
Okay thanks. I will do further investigation on the kernel code side.

Speaking of which, i find that the userspace vibrator code can be simplified significantly and still work:

int sendit(int timeout_ms)
{
int nwr, ret, fd, tspd, tspret, actuators;
char value[20];

tspd = open(TSPDRV_DEVICE, O_RDWR);
if(tspd < 0) {
LOGE("failed on opening /dev/tspdrv\n");
} else {
LOGV("opened device /dev/tspdrv\n");
}

if(timeout_ms > 0) {
/* enable tspdrv amp */
tspret = ioctl(tspd, TSPDRV_ENABLE_AMP, 1);
if(tspret != 0) {
LOGE("TSPDRV_ENABLE_AMP error\n");
} else {
LOGV("TSPDRV_ENABLE_AMP success\n");
}
}

fd = open(THE_DEVICE, O_RDWR);
if(fd < 0)
return errno;

LOGV("timeout_ms: %d\n", timeout_ms);
nwr = sprintf(value, "%d\n", timeout_ms);
ret = write(fd, value, nwr);

if(timeout_ms == 0) {
/* disable tspdrv amp */
tspret = ioctl(tspd, TSPDRV_DISABLE_AMP, 1);
if(tspret != 0) {
LOGE("TSPDRV_DISABLE_AMP error\n");
} else {
LOGV("TSPDRV_DISABLE_AMP success\n");
}
}

close(tspd);
close(fd);

return (ret == nwr) ? 0 : -1;
}

It seems to me that the MAGIC and TIMER stuff is only applicable for write() calls into the device to feed custom sample rates etc. All we need to do is enable the amp before set_vibetons, and disable it before the kernel sleeps.

Edit: you can clean out some of the unused variables etc
[Galaxy S II Original Android Development] codeworkx:
http://wiki.cyanogenmod.com/index.php?title=Howto:_Gerrit
[Galaxy S II Original Android Development] DvTonder:
Yes it does.

If you then do a local build of just CM7 (i.e. don't re-compile the kernel locally) it will use the prebuilt kernel and blobs.

I use the TeamHacksung buildscript without the kernel parameter to use the prebuilt kernel files. If you use the kernel parameter, it will re-compile the kernel locally and overwrite the prebuilt files from the git.

From that moment on, and until you either delete them and re-sync or new ones get uploaded to git and the sync pulls them down, you are using your locally compiled kernel and blobs even if you don't use the kernel parameter.

For the SGS2 I exclusively use the prebuilt kernel. For the SGS I compile my own version as I have made some changes to enable LED notifications.
[Galaxy S II Original Android Development] Novek:
There's a bug with the flashlight switch for the notification bar. When using the flashlight from the app itselfs everything runs fine. When using the notification toggle it works fine as long as your phone doesn't time out - if it does it's locked (flashlight turns off, and phone freezes in deep sleep) until you do a battery pull/long press the power button. For this reason I couldn't get a logcat eighter.

A solution would be to prevent the phone from going to sleep while that toggle is on (acting the same way as the app), but I couldn't find which file that would be added to atm.
[Galaxy S II Original Android Development] codeworkx:
happens on other phones too. wakelock needs to be added.

will be fixed soon.
[Galaxy S II Original Android Development] leedavis:
Simply stunning work fellas. This rom makes the SGS2 complete. If there are any instabilities it's in a part of the OS I don't use.
[Galaxy S II Original Android Development] atinm:
Thanks - you can actually do the changes yourself and send them up to us using Gerrit: http://wiki.cyanogenmod.com/wiki/Howto:_Gerrit to that it gets included in CyanogenMod.

This would help us to concentrate on other things, and give you credit for the work you did as well. We welcome contributors who can contribute code very much.
[Galaxy S II Original Android Development] atinm:
Thanks, this is very helpful. Let's see what we can find. Having two files to test on is ideal. Movies is a different issue, we just don't recognize a lot of formats but for me media and bluetooth are the biggest things left that we need to fix so we're on it.

I am looking in XDA again now because I was told this forum has been cleaned out and has quietened so I can see what I need to see. Now for this forum to be ideal for us, even the compliments and thanks will be in the Q&A thread, or maybe a general thread (which I refuse to create . . .) ;-)
[Galaxy S II Original Android Development] codeworkx:
black screen after phone call should be fixed now.
[Galaxy S II Original Android Development] goldbergx:
OK I just tried to download the files from the link I put up and I think XDA resizes or reformats them as I got jpgs of a much lower resolution

Please take it from here - mediafire link
[Galaxy S II Original Android Development] atinm:
In case it wasn't clear from all the moderator's posts - this belongs in Q&A as it doesn't meet any of the criteria for posting in this thread. If you ask in the Q&A thread, another user will be able to help you get around this because this is most likely a user error (you didn't wipe things, restored more than you should have, something along those lines) and has nothing to do with development.
[Galaxy S II Original Android Development] california6006:
since cm7 there is no possibility for me to connect ober Tapatalk...I go to Favorites and choose for example XDA and it requires my Login Data..After typing in it has server connection problems...if i use my bank app it ahs problems to refresh my bank account...is there someone who has the same problem?

i have to say that this problem exists only with mobile internet ...over wifi no problem.
[Galaxy S II Original Android Development] codeworkx:
a) use this thread for Q&A http://xdaforums.com/showthread.php?t=1176411

b) no problems here

c) if you're on KG3, try switching to KG2
[Galaxy S II Original Android Development] lolmensch:
better ask for an answer in the q&a thread of cm7 http://xdaforums.com/showthread.php?t=1176411
[Galaxy S II Original Android Development] FRLinux:
Logcat to the rescue...
[Galaxy S II Original Android Development] jcrompton:
For me KG2 much better as well on CM7
[Galaxy S II Original Android Development] js8:
Great build. Almost everything working very nicely.

Having a problem waking the screen from sleep. Using standard CM settings, no mods.

Logcat attached for reference. The recurrent error seems to be

E/SurfaceFlinger(2657)GL error 0x0506
[Galaxy S II Original Android Development] GuestK00150:
hey! First of all - great work! Love cyanogen - already used it on desire for nearly a year ;)

Two feedbacks:

1 What is this bluetooth issue about? I can confirm working file transfert with osx 10.7.

2 Please lower the incoming call volume. Even on the lowest possible volume I have to hold the phone with a biiiiiig distance to my head :D

THANKS to the whole cm-team!!!

QUESTION: Is this post o.k. here or am I supposed to post stuff like that in the q&a thread?

EDIT: using nightly 8, radio KG3
[Galaxy S II Original Android Development] jcrompton:
this volume issue is weird. My volume isn't loud enough
[Galaxy S II Original Android Development] naddie:
Right, I don't have that volume issue either. As for BT, BT Audio isn't working. File transfers should be ok.
[Galaxy S II Original Android Development] Cangir:
Please read OP every one knows that BT audio is not working
[Galaxy S II Original Android Development] wanam:
Is this list updated?
[Galaxy S II Original Android Development] Cangir:
I think its not updated but vibrate works. Please use the question and answer thread
[Galaxy S II Original Android Development] codeworkx:
- Bluetooth Audio

- Video playback - some formats are not recognized

- TVout

- FMRadio

- Some users report photos on the external SD-card seem to get deleted

- Issues when using the 2G/3G-Switch
[Galaxy S II Original Android Development] Goddchen:
oh, yes just experienced this again when i flashed nightly #8 :( it didn't appear with all the other nightlies from #3-#7, but when i flashed #8 they got deleted again :(
[Galaxy S II Original Android Development] mi3x:
Hmmm, that's nearly perfect :) :p
[Galaxy S II Original Android Development] TotalCrisis:
Any chance atinm could edit the second post? It might clear up a bit of confusion with new users. :)
[Galaxy S II Original Android Development] fmurillo:
cm7 once installed deleted all my jpg and png archives

happend twice... do not really know why but happened wit the wm7 version 8 and 9 and also the [ROM] insanity ii [29.07.2011] whit the same "core".... CM7.... for me has been a real "tragedy"... coz i have lost all my jpg and png files from the whole microsd card (more than 6 gb from a 32 class 4) except the ones hidden with a .nomedia file in the folder. Thanks 4 all the efforts 2 the cm7 team but it is a trouble to deal with asap.
[Galaxy S II Original Android Development] Zedonite:
Mediafiles (except folders with .nomedia) from external SD got automatically deleted when I turned off USB storage. (Tested it twice)

Logcat attached.
[Galaxy S II Original Android Development] blickmanic:
If your files have been deleted use a recovery software to recover the images aa they are not permanently gone
[Galaxy S II Original Android Development] vijaysivakula:
Could the problem of media files being deleted have anything to do with the make of the memory card? I use a Sandisk 16 gb.
[Galaxy S II Original Android Development] Goddchen:
taking back my hint to the nightly versions. remounting after USB mount is a very possible cause of the images getting deleted. I have not mounted it a long time but when the images were gone i have just copied some mp3s to the sdcard some minutes ago...
[Galaxy S II Original Android Development] Goddchen:
just another bug report that i havent read here in the thread so far:

many times when i wake the phone from sleep via the power button i see the crt on animation and right after that the crt off animation and the screen is black again. yet the soft keys stay on. when i press power again the soft keys go off and when i press power again the crt on animation start and i see the lockscreen.

just wanted to create a logcat but i'm not able to reproduce this behaviour when switch the phone off and on repeatedly. maybe has to do something with deep sleep? It only seems to happen when i don't use the phone for some time...
[Galaxy S II Original Android Development] codeworkx:
disable crt on animation and everything is fine.
[Galaxy S II Original Android Development] rulleeeee:
can comfirm mounting phone for usb storage and then unmounting deleted my images from the external-sd, internal sd images still left.
[Galaxy S II Original Android Development] Dactylion:
1.is it possible that samsung ril dbm values are are differently interpreted than on stock? im getting 4-6 mbit/s download at -95 dmb.

stock shows total different dbm values at the samme place. as far as i remember eg -60 vs -90 dbm. i guess its an easy fix because u just need an other formula for interpreting the value from the radio. if you point me to the sourcecode file i guess i can work out a coorect conversion.

2.Furthermore gps fix is fast, but does not go below 10m accuracy. even with 10 satellites as shown in the picture.

3. the last problem is about button backlight. no matter whcih setting i use for the buttons (0 -255) they dont change in any way.

http://review.cyanogenmod.com/#change,7025 does not seem to fix dbm values. using nightly 9
[Galaxy S II Original Android Development] Klyupp:
sorry wrong thread
[Galaxy S II Original Android Development] codeworkx:
1. https://github.com/CyanogenMod/andr...om/android/internal/telephony/SamsungRIL.java

3. Button Backlight = on or off

4. http://review.cyanogenmod.com/#change,7025 = CDMA, SGS2 = GSM
[Galaxy S II Original Android Development] Dactylion:
thanks im going to dig into it.

additional findings:

are those 2 lines useful in build.prop?may iths worth changing them in next nightly.

debug.sf.hw=1 (hardware accelerated ui) --missing--

ro.ril.hsxpa=2 (1=hsdpa 2= hsdpa+hsupa) --default is 1--

speed is the same and upload over 1mbit.so i guess its hsupa no matter what build.prop says. ui does not seem to feel different too.

can i contact you by g+ or irc?
[Galaxy S II Original Android Development] codeworkx:
HSPA = High Speed Packet Access

HSDPA = High-Speed Downlink Packet Access

HSUPA = High-Speed Uplink Packet Access

HSDPA + HSUPA = HSPA

1= only fat downlink ???

2= fat downlink and fat uplink ???

Haven't looked at it, but would say it's fine like it is.

IRC: #cmsgs at freenode
[Galaxy S II Original Android Development] Dactylion:
y hsdpa is ok. but what about ui hw acceleration?

here are my tests to make sure the dbm values are bad.

stock:

indoor:

gsm: 79-83 15-17 asu

umts: 89-91 11-12 asu

outdoor:

gsm: 65-67 24 -26 asu

umts: 77-79 17-18 asu

edge gives full speed and umts between 4 and 6 mbit/s down and 1.3 mbit/s up

cm7:

indoor:

gsm: 89 12 asu

umts: 89-95 9-12 asu

outdooor:

gsm: 89 12 asu

umts. 89 12 asu

speed is same on stock and cm. indoor is more at 4mbps and outdoor 6mbps. but cm reports same values for gsm and umts and does not lower dbm at outdoor reception.

to me it looks like samsung ril reports signal bars and they get converted into dbm. shouldnt it be the other way round?

protected Object

responseSignalStrength(Parcel p) {

int numInts = 7;

int response[];

/* TODO: Add SignalStrength class to match RIL_SignalStrength */

response = new int[numInts];

for (int i = 0 ; i < numInts ; i++) {

response = p.readInt();

}

/* Matching Samsung signal strength to asu.

Method taken from Samsungs cdma/gsmSignalStateTracker */

if(mSignalbarCount)

{

//Samsung sends the count of bars that should be displayed instead of

//a real signal strength

response[0] = ((response[0] & 0xFF00) >> 8) * 3; //gsmDbm

} else {

response[0] = response[0] & 0xFF; //gsmDbm

}

response[1] = -1; //gsmEcio

response[2] = (response[2] < 0)?-120:-response[2]; //cdmaDbm

response[3] = (response[3] < 0)?-160:-response[3]; //cdmaEcio

response[4] = (response[4] < 0)?-120:-response[4]; //evdoRssi

response[5] = (response[5] < 0)?-1:-response[5]; //evdoEcio

if(response[6] < 0 || response[6] > 8)

response[6] = -1;

return response;

}
[Galaxy S II Original Android Development] codeworkx:
Can you please use code tags?

Yes, Samsung reports the count of bars to be displayed. No real signal strength.

Sometimes they're doing things nobody understands.

We cannot change this. We have to use it like it is.
[Galaxy S II Original Android Development] Dactylion:
but how ist stock rom able to get proper dbm then?i guess smn needs to dissasemble binariess to get an answer....its fixable but im not skilled enough for it.
[Galaxy S II Original Android Development] codeworkx:
i'm getting:

HSPA: 95dbm, 9 ASU

HSPA: 89dbm, 12 ASU

HSPA: 101dbm, 6 ASU

HSPA: 107dbm, 3 ASU

EDGE: 95dbm, 9 ASU

EDGE: 89dbm, 12 ASU

EDGE: 101dbm, 6 ASU

EDGE: 107dbm, 3 ASU
[Galaxy S II Original Android Development] Dactylion:
at least you get different values for gsm and umts.

which radio ar u using? im on kg3 will test kg2 soon. eit: no difference on kg2
[Galaxy S II Original Android Development] codeworkx:
i'm using KG2. Got disconnects with KG3.

but your 89dbm should be 5 bars.

are you living near a transmitter? could be the reason.
[Galaxy S II Original Android Development] Dactylion:
y im living in bonn. schöne stadt..

-89 dbm signal level just look quiete bad if i compare it to wlan signal levels and signal/noise ratio needed for proper troughput.some times i get up to -50 dbm in the city.

however i almost understand the calculation with its bitwise comparison and shifts.the only question left is what

p.readInt(); does.

response = new int[numInts];

for (int i = 0 ; i < numInts ; i++) {

response = p.readInt();

}

sorry if its anoob question im not familiar with java at all and just using old c skills.
[Galaxy S II Original Android Development] eatonjb:
does this still hold true? I need BT, and deleting pictures is kinda of a bummer..

but this was an old post?
[Galaxy S II Original Android Development] Dactylion:
y it was updated recently. only the last item is unknown to me.
[Galaxy S II Original Android Development] RockRatt:
All phones running CM7 will AUTOMATICALLY reboot the phone or actually turn it on. It is NOT a bug but HOW CM7 WORKS since it.is based.closest to the Nexus S which is the way it does not power off while.plugged in.

Sent from My 2.3.3 or 2.3.4 Captivate Test Phone depending on what Gingergurl I am testing.
[Galaxy S II Original Android Development] MartyHulskemper:
Well, it seems the picture delete bug is still present. Yesterday evening I noticed that all image files in jpg format had been deleted from my external sd card. Most had been backed up already on my desktop system and some had been uploaded (against my wishes, lol) by Google+. So, I'm back to VR for now, but I'm will miss both the kill feature and being able to boast about running 2.3.5, hahaha!

Squish that bug, guys, please. ; )
[Galaxy S II Original Android Development] :
Tested cyanogenmod and that bug SUCKS like HELL!!!! it's the main bug and the reason why i'm not using cyanogenmod and will keep using cognition rom until this bug is solved! Anyway keep up the good work guys :)
[Galaxy S II Original Android Development] Illicit Hero:
Camera freezes when I record, eventually will unfreeze after a few seconds but the sound will be late by however long it was frozen for.

http://pastebin.com/zQE5DMgD
[Galaxy S II Original Android Development] Dactylion:
new kg6 modem out

http://xdaforums.com/showthread.php?t=1194550&page=10

http://www.multiupload.com/454AQ3UOAL

Password: nightly@ghostworker

hope you package it into a flashable zip
[Galaxy S II Original Android Development] kursed:
Camera freezes for a few seconds at the start and end of video recording.

http://pastebin.com/pu9K4kv7
[Galaxy S II Original Android Development] leedavis:
Data issues

I'm experiencing 2 issues. Neither are show-stoppers.

1. When I leave my phone charging overnight, in the morning it's disconnected from my carrier and nothing I can do except rebooting will reconnect it. Not sure why. I get a little x above the signal strength bars (which are all off)

2. I keep having to use the widget to toggle wifi off and on to get it to reconnect to the wifi network after the phone has been on standby for > 15 minutes. Happens on both home and work wifi networks.

I've scanned back through the posts and cannot see anyone else with similar issues. I am on nightly-full-7. I'll try upgrading to 9 tonight, but the changelog doesn't mention any changes to do with the radios.
[Galaxy S II Original Android Development] Fihlvein:
I'm sorry to sound harsh, but if you've scanned through posts, you really should know this is a wrong thread to post your questions. Check QA section CM7 thread.
[Galaxy S II Original Android Development] jonny68:
christ that is not good and not something i wanna have to do either.

anyone else have any trouble like this please report it here!!