yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] DvTonder:
Yes. I have been able to replicate it as follows

Screen off, message in, led on, screen on, led on, screen off, led on, screen on, led off every time.

Seems that after the second time you turn on the screen without clearing the notification causes the backlight to turn off when you turn on the screen. If you leave the phone for a while it seems that the cycle starts over again. I suspect it has to do with the suspend code.

I will attempt a fix this weekend and see if I can include backlight timeout as well.
[Galaxy S II Original Android Development] codeworkx:
i'll rewrite it tomorrow if i get time.

seems to be a little hacky.
[Galaxy S II Original Android Development] DvTonder:
Yes. Definitely a lot hacky. Is a combination of various pieces of code and I am using it to relearn c coding.

Has been 15+ years since I wrote serious code and I am more than a bit rusty :-)

If you are going to work on it I will hold off. Let me know if you are not and I will do a round 2 on it.
[Galaxy S II Original Android Development] chrysilis:
Yes, the one it comes with :)

By which I mean, argh go to the Q&A thread...
[Galaxy S II Original Android Development] DvTonder:
Ask in the Q&A Thread here http://xdaforums.com/showthread.php?t=1176411
[Galaxy S II Original Android Development] cTrox:
10 chars ...
[Galaxy S II Original Android Development] Fihlvein:
That's because the title of this thread is [ROM][GRJ90] CyanogenMod 7 [DEVELOPMENT/DEBUGGING ONLY].

General discussion and questions is basically happening on CM7 QA thread. Also, what I'm saying reads also in the OP, but who reads instructions anyway...
[Galaxy S II Original Android Development] Kikko2000:
Maybe because peoples who read previous posts have understood that things that are not related with developement should be addressed in QA post. Didn't you read previous posts or simply didn't you understand that?.
[Galaxy S II Original Android Development] sa_ma:
FM fixed :)

Hi,

I think FM issue is sorted out, I can listen to FM , still some bugs to hunt down.

for audio stream routing of FM more hacking was needed in the framework,

will try to make an account with the gerrit and upload my changes, will do this submission when i have some time, i hope before the end of this week
[Galaxy S II Original Android Development] SS2006:
-delete-----------------------
[Galaxy S II Original Android Development] unrealtb:
Delete?
[Galaxy S II Original Android Development] DvTonder:
I tracked the problem down to a combination of the CMParts LED Settings disable and the late_resume function.

Essentially:

When the phone is sleeping and a notification comes in, liblight returns a True if LED Notifications is enabled in CMParts (i.e. it is not in Quiet hours), the phone then turns on the Backlight and all is OK

When the screen powers on, liblight returns the LED Notification active as FALSE (dunno why) which causes the cypress_touchkey code to rurn the light off. Several seconds later, the touchkey late_resume function is called by the kernel which turns the LED on again - thus the Off/On behaviour.

This behaviour is present in all BLN implementations!

Somehow, the Enable LED Notification setting (from CMParts) is always set to OFF when the screen turns on. If this could be prevented somehow, it would fix the problem. Unfortunately, I don't know where to even start looking.
[Galaxy S II Original Android Development] DvTonder:
@KANG Builders ONLY!!

I've uploaded a simplified, less messy, version of my ported SGS2 CM7 LED Notification code. As before, it enables full CM7 Stock LED Notification support for the SGS2 without the need of Neldar's BLN app.

By building CM7 with these files, the LED Notifications settings within Cyanogenmod Settings (CMParts) is used to determine if LED Notifications is displayed or not. It respects Quiet Hours and will not turn on if Dim LED is selected.

Please note: This code, and all the BLN enabling code out there, uses a wake_lock which will prevent the CPU from going into deep sleep while a notification light is on. If you are worried about battery life, this code is not for you.

3 files are included

1) cypress.touchkey.c (kernel code)

Copy to the kernel/samsung/c1/drivers/input/keyboard/cypress folder, overwiting the file by the same name.

2) lights.c (liblights module for reading LED Notification settings)

Copy to the device/samsung/c1-common/liblight folder, overwiting the file by the same name

2) config.xml (to enable the LED Notification settings in CMParts)

Copy to the vendor/cyanogen/overlay/galaxys2/packages/apps/cmparts/res/values folder, overwiting the file by the same name

Build full Cyanogenmod including the kernel

Configure the LED Notification settings and Enjoy!

Files are available at: https://github.com/DvTonder/SGS2-CM7-LED-Notifications
[Galaxy S II Original Android Development] RockRatt:
Hopefully this can be enabled again to all CM7 devices. Will your fix work with the sgs1 captivates running CM7? When we had it before it seemed to work for me on the captivate without the issues at least that I noticed.

Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
[Galaxy S II Original Android Development] DvTonder:
No, this code is for the SGS2 only. Try the glitch kernel for the SGS.
[Galaxy S II Original Android Development] RockRatt:
Thanks. I have been using the Escapist kernel for a long time with the bln app and no issues. It uses the bln app. I was just asking if this is something that CM7 will end up putting back into their code at some point now that you have seemed to fix it. Thanks again.

Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
[Galaxy S II Original Android Development] DvTonder:
I have not fixed anything. I have just ported the original led notify code from the SGS1 together with components from Cream's BLN enabling code to CM7 for the SGS2.

The code will not make it into mainline cm7 in its current state. It will take a much better developer than I am to get this into mainline.
[Galaxy S II Original Android Development] atinm:
Codeworkx is trying to make this work - we'll see.
[Galaxy S II Original Android Development] RockRatt:
Atmin that would be great to have that back into all the cm7 devices. I have always used a different kernel with OC/UV mainly to have led notifications (on SGS CAPTIVATE). BUT lately they haven't updated recently so I have been pretty much been using the stock kernels, so this would be awesome. Go for it codeworkx's.

Another feature that would be great is a speed dial from the dialer, I hate having to use another dialer for it. I know this doesn't really belong here but just throwing it out there since I do not know how to develop (though I would love to learn) and 2 CM7 is pretty much bug free and those are the ONLY things I feel it is missing. You all have kicked ass with this thing and look forward to having this on my next phone whenever damn att decides to release the SGS2.

Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
[Galaxy S II Original Android Development] mani0608:
Hi,

I have the latest build (#16) of CM on my galaxy s2.

My phone was able to send files through bluetooth, but not able to receive files...

Kindly let me know whether this is an open issue. Sorry if i have repeated this question.
[Galaxy S II Original Android Development] stoney73:
Look at the buglist in the cm thread in q&a.
[Galaxy S II Original Android Development] Dactylion:
i cant find anything in the logs about fast dormancy like on stock rom. is this battery saving feature missing from cyanogen?

i checked the system directiories for the specific files too and even buidprop does not contain any information.

then i took all servicemode and testing apps from stock and put them into cyanogen. ofc it was a toal fail and messed a few small things up.

so i just want to know the general state of fast dormancy on cyanogen and exspecially on galaxy s2.

and last but not leas are u suing the latest propieritary files for the mali-400?because at least 2d performance suffered in several test compared to stock.
[Galaxy S II Original Android Development] derBeukatt:
No bug there. Lets say u search for a title. Go to title in the top row. Long press menu button. Keyboard opens up. Simply type song ur looking for. Long pressing menu button is almost allways for the search button.
[Galaxy S II Original Android Development] Dactylion:
awesome.im using cyanogenmod since over a year....

i was already starting to deal with the sources. i hope someone knows more about fast dormancy status
[Galaxy S II Original Android Development] DvTonder:
Gentlemen,

These belong in the Q&A thread that can be found here: http://xdaforums.com/showthread.php?t=1176411

This is the development thread.
[Galaxy S II Original Android Development] slikkie:
I just tested build 16 on my SGS2 but noticed a problem with auto-rotate in video playback.
[Galaxy S II Original Android Development] idi0t:
i want to flash this rom but it says :

E:failed to verify whole-file signature

E:signature verification failed

need help on this
[Galaxy S II Original Android Development] tjjensen23:
http://xdaforums.com/showthread.php?t=1176411

Logs? Only Way Devs can know

also http://xdaforums.com/showthread.php?t=1176411
[Galaxy S II Original Android Development] archer797:
Please post this in Q&A thread. This question has been answered already.
[Galaxy S II Original Android Development] SS2006:
the instructions say start with a rooted device (usually use CF root)

then say install rom manager

but rom manager doesnt work with CF-rooted phones what gives?
[Galaxy S II Original Android Development] chrysilis:
Have you tried the Harder Way?

Also this is a question, please ask questions in the Q&A thread. Report issues with logs etc here.
[Galaxy S II Original Android Development] the_scotsman:
I think the OP needs something in big red letters, along the lines of:

PLEASE ASK ALL ROM RELATED QUESTIONS IN THE Q&A THREAD. DO NOT ASK QUESTIONS IN THIS ONE because the noobs just don't seem to be able to read well :rolleyes:
[Galaxy S II Original Android Development] lauslein:
Can't we rename the thread? More "NO QUESTIONS", less "CyanogenMod"…

Most people just seem to read "[ROM] CM7" in the title and click the "Reply" button without further reading.

And I think every developer and everyone who is interessted in the developement (as a silent reader) already has subscribed to this thread (or will subscribe again after the annoying questions stop), so there's no need for a meaningful title to find this thread :o
[Galaxy S II Original Android Development] codeworkx:
OP says you should install my cwm kernel, not CF!!!

Just read the instructions carefully.
[Galaxy S II Original Android Development] kammiz:
i have an sgs2 with nightly build #16. i hope i am in the right thread.

i know about the bluetooth audiod issue not beeing solved yet, but it also seems my sgs2 isnt recognized as the same device when my car handsfree tries to reconnect. if i turn bluetooth off and on it resets the bluetooth name to sgh-i9100 and i when i try to reconnect after changing back to the correct name it connects but it is recognized as a new device with the exact same name as the one that is allready paired, so it is stored as a new device with the same name.

is this a known bug?
[Galaxy S II Original Android Development] the_scotsman:
No you're not.

Try reading post #2
[Galaxy S II Original Android Development] tjjensen23:
Beaten

///
[Galaxy S II Original Android Development] rudolf895:
Just tied the latest built

this is the error i get

http://img828.imageshack.us/img828/1584/20110812215418.jpg

Any idea on what went wrong?

Dont complain about the camera this was a basic phone camera(Galaxy 3 3.2MP)
[Galaxy S II Original Android Development] cTrox:
Are you kidding me? It states you are a "Recognized Developer" and still you are not able to read the damn thread title?
[Galaxy S II Original Android Development] rudolf895:
Oh, i'm sorry i had this thread bookmarked just posted this without reading the title, Though it would have been better if you had a solution than..

Anyways posting it in QnA thread.

Edit: Being a "Recognized Developer" does not make me any special, i do make mistakes some time.
[Galaxy S II Original Android Development] Slick_42:
To me it looks like you are using an unrecognised device. What is its exact product code? (GT-I91xxx)
[Galaxy S II Original Android Development] marvi0:
True that matey no one is perfect.
[Galaxy S II Original Android Development] rudolf895:
i had a bad download, fixed it by re-downloading :)

Thanks anyways :)
[Galaxy S II Original Android Development] kammiz:
i am sorry, i thought debugging meant this was the thread to report bugs.
[Galaxy S II Original Android Development] break1:
delete please ;[
[Galaxy S II Original Android Development] zuettu:
if got a problem on my sgs2, but I don't know when it all beguns.

I've installed nightly 20 (and tried every version before) with baseband-vesion KG6 and every time I start my camera or the flashlight all I get is a black screen and an error-message saying no connection to the camera possible. I've allready treid full wipe and also format /data /cache /system but nothing helps
[Galaxy S II Original Android Development] tjjensen23:
But to help you, you will need to provide logcat of your error.
[Galaxy S II Original Android Development] sa_ma:
FM changes uploaded

Hi,

Here is the changes to have FM working , changes were in the FM application "to proper route audio path", framework "FM stream and changes in the JNI to proper support Si4709 and the driver" and in the driver"just to change from /dev/radio0 to /dev/fmradio as this is hardcoded in the yamaha library" ,

with my testing FM works fine , the only remaining this for now is to control the volume , right now the volume is fixed and can not change,

I have 2 choices for this

1) to overload the onKeyDown events to capture the volume change

2)to have service running in the background when the application is active, this running service is to keep checking the media/FM stream volume level , and then send the commands to to the FM hardware to change the volume level

in both cases I need to change the FM jni and add more functions to support the audio change of the hardware.

also the audio can not be routed to the speaker phone in clean way so i just disable it for now,

my problem that i am certain for sure that the changes will break compatibility of other hardwares and devices for FM , I will submit my changes to the Gerrit and i hope someone can make the necessary change so it only apply to SGS Galaxy S2,

for the brave hearts you can find the repo diff so you can apply the changes yourself and test things yourself , also i have the fm ko file ,

my target for next week to have the volume control up and running and with some luck maybe we can get the RDS data to the FM app,

Regards

Edit: any tutorial of how to push the changes into the kernel branch with git ? , so far i am not successful with it,
[Galaxy S II Original Android Development] Stonos:
Tried this?

http://wiki.cyanogenmod.com/wiki/Howto:_Gerrit#Kernel_Patches
[Galaxy S II Original Android Development] codeworkx:
you cannot push to cyanogenmod repos.

only to your own repo.
[Galaxy S II Original Android Development] sa_ma:
then how can i commit the changes to the Si4709 driver of the kernel ?
[Galaxy S II Original Android Development] lauslein:
One of the CM7 maintainers might pull your code to the official repos after reviewing…
[Galaxy S II Original Android Development] codeworkx:
- create a github account

- fork our kernel repo

- push it to your forked kernel repo

- send a pull request
[Galaxy S II Original Android Development] sa_ma:
pull request is done,

as for the other changes in the framework and the fm_app , it have been rejected as it will break support for other devices , what should be the way forward ?
[Galaxy S II Original Android Development] codeworkx:
Find a way, where you don't break other devices. ;-)
[Galaxy S II Original Android Development] sa_ma:
:) very funny,

do you have an example where such change was done specifically for S2 so i could follow its step,

the way i see it , it is impossible not to break support of other devices,
[Galaxy S II Original Android Development] codeworkx:
read the comments on gerrit from kolja and danny.

xml changes can be done at device/samsung/c1-common/overlay

if you have to add stuff on framework or fmapp -> hint: if ro.samsung_fmradio == true { do ugly stuff } else { do stuff }

or something like this.

read about system properties.
[Galaxy S II Original Android Development] atinm:
Use overlays - each device has specific stuff, and we use overlays for the stuff related to menu options etc. And we use system properties related to the BoardConfig to do device specific stuff if it *has* to be done in the app but frequently the idea is that the App is written to work with "standard" Android, and therefore any changes have to be done in a layer below like libaudio, or a libaudio wrapper. Look in the device/samsung/c1-common directory for the wrappers that are already there for Galaxy SII, and look at device/samsung/aries-common/libcamera for a good example of how the camera wrapper was written for the aries phones to support Camera App for Samsung because Samsung has many more features that the stock android framework doesn't have. No one said this was easy, and writing wrappers is a pain, but we do this to isolate device stuff to device specific things. Otherwise the code become a total hack, and is no different from what the manufacturers do . . .
[Galaxy S II Original Android Development] alexalbion:
Can you please insert the service mode in cm7
[Galaxy S II Original Android Development] NickoPulver:
Service mode?.....you mean add samsung code back in cm7 then and get a stock rom with the only change is the name......cause all service commands are in samsung rom........cm is cm and therefore the phone is no longer a samsung device ......only in hardware.......why do i know that? ......can it be because i read up and learn by reading maybe ........if you want samsung features use stock rom......its that simple ......sorry for writing this here. But i have read every single page in both threads and now i couldnt hold it in anymore.........once again sorry but it pains me to read stuff here that everyone can google......i have.....and i am no genious .........
[Galaxy S II Original Android Development] alexalbion:
Sorry , but i read a lot, my question for service code is simple, i need the option to stop wdcma and get only hsdpa. Have o2 germany my g2 Changes between hsdpa and wdcma a lot of times an hour. It drains my battery. I search for a solution. So i thought a opinion like service mode can bring it. Before g2 i had a i7500 with gaosp configurator
[Galaxy S II Original Android Development] NickoPulver:
Hit the menu button and choose settings.....wireless and networks ......and then mobile networks and art the bottom of that you find the setting to lock it from choosing and set what you want used yourself.......
[Galaxy S II Original Android Development] vijaysivakula:
Sorry. My bad. Going to the right page.
[Galaxy S II Original Android Development] alexalbion:
In the settigs i didnt find a way ti switch hsdpa/wdcma to hsdpa only, that is the only way to solve my battery problem. But the codes from service mode wont work on cm7. Please give us the opinion to change the mobile network settings
[Galaxy S II Original Android Development] LuffyPSP:
Should i post in here? Or the Q n A section? But here i go then. Does anyone experience FC or hang or stuck at video HD or High recording mode? Pressed the record button, record for few seconds and video become static, and crashed. Tried recreating and yes it happens again. Latest build 24.

Where can i leave feature suggestion btw? The haptic is fixed but its too strong. Wish to have the option to lower or higher the values. And also tilt to zoom feature in gallery and browser too.

Nuked from Samsung Galaxy S2 GT i9100 using XDA Premium app
[Galaxy S II Original Android Development] FRLinux:
Include logcat when reporting a problem.
[Galaxy S II Original Android Development] LuffyPSP:
fixed after flashing gapps again. dont know how it is related but its fixed.
[Galaxy S II Original Android Development] FRLinux:
Doubt it is related.
[Galaxy S II Original Android Development] uppon2:
I have had CM/MIUI/AdamG I seem to get MAJOR radio issues. People constantly telling me my phone is switched off and that I'm not answering calls or sms messages (That I am never receiving mind you) - I have tried MIUI/CM/InsanityCM on my i9100 with the same result and I have tried MIUI/CM/AdamG/InsanityCM on my SGS2 With the exact same issue. Nobody can explain why this is happening to me. I have tried multiple modems (All which work PERFECTLY on non AOSP ROMs)

I have never ever had any issues on Samsung ROMs but I would much prefer to run something else but I take a lot of important calls for my business.

Anybody else in Australia experience the same issue?
[Galaxy S II Original Android Development] tangiers:
I didn't when I tried the first few nightlies. I'm on Cognition 1.42 now with Telstra and all is working fine. I'm a big Cyanogenmod fan (been on it for a long time with previous phones) but I think we have to be patient with this build and wait a while before using it as a daily driver (I too can't afford to miss business calls or emails).

Edit: BTW, count to 10 and you will see some happy soul pointing out that you should post this in the Q&A thread and berating you for not doing so. An unhappy trait of this strand of Cyanogenmod I'm afraid...
[Galaxy S II Original Android Development] yohanevindra:
is anyone's vibration/haptic feedback not working? I am on 08152011 and when i restart the phone, vibration comes back for a bit but then goes again...is this still an insolved issue?
[Galaxy S II Original Android Development] chrysilis:
From the changelog at https://cm-nightlies.appspot.com/?device=galaxys2

Update to latest nightly before reporting issues.
[Galaxy S II Original Android Development] Pacifiste95:
why the changelog is blank for cm_galaxys2_full-25.zip ?

http://cm-nightlies.appspot.com/?device=galaxys2
[Galaxy S II Original Android Development] Mike_52:
This is development thread : [ROM][GRJ90] CyanogenMod 7 [DEVELOPMENT/DEBUGGING ONLY]

Not Q&A thread ... the Q&A thread is here : http://xdaforums.com/showthread.php?t=1176411
[Galaxy S II Original Android Development] lauslein:
Srsly, could you all stop asking questions that are completely out of place in this thread?!

This thread is dead and I guess most devs won't even read new posts because 95% of it are questions that don't belong here… so annoying!

⇒ Q&A-THREAD
[Galaxy S II Original Android Development] dontomate:
1. Read the ****ing OP

2. If you want to post it here there should be a Logfile included

3. If you haven't any Logfile then this is the thread to ask your question: http://xdaforums.com/showthread.php?t=1176411 :)
[Galaxy S II Original Android Development] atinm:
*sigh* no -- I do read it, but unless it is development related, I don't answer. And neither does any other developer. Maybe that would fix it . . .
[Galaxy S II Original Android Development] DimICE:
What about soundpool bug?

Issue: http://code.google.com/p/android/issues/detail?id=17623

My log in attachment.
[Galaxy S II Original Android Development] Mr. Clown:
Did some thread cleanup, back on topic and stop posting unrelated posts in here.

@ all, search!
[Galaxy S II Original Android Development] FRLinux:
My previous comment got deleted but I was asking a legitimate question.

Compared to stock rom, the auto dimming when unlocking the phone in sunlight takes 3 to 5 seconds too long. Can you fix this please?
[Galaxy S II Original Android Development] goldbergx:
Got deleted for a reason. Please goto the Q&A thread.

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

Can't imagine this issue would be top priority either (if it is an issue)