yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] prodygee:
So you're saying the color banding is totally not a hardware 'issue', but a software 'issue'? Why is it there then? Performance?
[Galaxy S II Original Android Development] phunkycow:
Most probably, yes. For performance.
[Galaxy S II Original Android Development] assid2:
Brilliant!
[Galaxy S II Original Android Development] kursed:
Will you folks make CM7 multi-dpi friendly?
[Galaxy S II Original Android Development] infinityz:
You already can change the dpi! Manually, editing the build.prop or using LCD changer from market.

I set 192 and work like a charm :-)
[Galaxy S II Original Android Development] kursed:
I can change the dpi alright. But it renders certain areas of rom (notification bar when open, for instance) where you can see visual blocks etc.
[Galaxy S II Original Android Development] ZhuraYuk:
Of course it's software, Mali 400 capable to produce any color depth. Also read about Android a little, it's 16 bit by default.
[Galaxy S II Original Android Development] JupiterdroidXDA:
This will be fixed in Ice Cream Sandwich. It will happen;)

Sent from my Samsung Galactic Crusader S II
[Galaxy S II Original Android Development] JupiterdroidXDA:
@codeworkx

Do you plan to implement the "touchscreen fix" as an inherent part of the CM ROM?

Sent from my Samsung Galactic Crusader S II
[Galaxy S II Original Android Development] codeworkx:
touchscreen fix?!?!?!
[Galaxy S II Original Android Development] JupiterdroidXDA:
Yeah, there is a screen pause when swiping slowly, you really notice this in games more than anything. If you get the multitouch app and move your finger slowly across you will se there is a slight delay in registering the movement. A dude has created an app to change this to 0 or whatever you like best, the default is 15 i believe, you will find it in this dev section. Its reallt useful when making precise movements..

http://xdaforums.com/showthread.php?t=1161262
[Galaxy S II Original Android Development] cTrox:
I guess he's referring to this thread: http://xdaforums.com/showthread.php?t=1161262
[Galaxy S II Original Android Development] JupiterdroidXDA:
Yeah, it makes a massive difference, it would be better if it was integrated in the rom instead of running a server, integrated @0.:)
[Galaxy S II Original Android Development] codeworkx:
https://github.com/CyanogenMod/andr...mmit/deaf03c19accee8b2d036d318f9aca975a48c7e0

done
[Galaxy S II Original Android Development] cTrox:
Hm some say if you set it to 0 it will be to sensitive and if you are trying to scroll you click things. I heard 5 should be a good value.
[Galaxy S II Original Android Development] kawa636r:
I've recompiled the one from Samsung sources
[Galaxy S II Original Android Development] codeworkx:
http://wiki.cyanogenmod.com/wiki/Howto:_Gerrit

If you've problems with using gerrit, contact me via PM.
[Galaxy S II Original Android Development] JupiterdroidXDA:
0 is best mate as it acts like other OEM screens. There should not be any delay, i have been testing for about a week now and its fantastic, i have noticed no difference in swipe response or drag response, to be honest the more sensitive the better;)

@Codeworkx

You work fast dude, thanks, i'm sure it will be a nice addition;)
[Galaxy S II Original Android Development] Hayaa:
With builds #0 #1 & #2 when i untick the "confirm shutdown" option in CyanogenMod/Interface menu i can't acces to the "Recovery/Download/Bootloader" options when i choose "Reboot" in the extended power menu.

The telephone reboot directly.

when the "confirm shutdown" option is ticked i can choose "Recovery/Download/Bootloader"

Sorry for my english :(

And the backlight buttons shutdown only when the screen shutdown (but i think is a know issue?)
[Galaxy S II Original Android Development] Novek:
That's normal from the latest CM7 bulds I've used on HTC Desire Z, LG 2X and this one... I believe it's a confirm what type of shutdown (reboot) you want. If you don't want to specify it, reboot is reboot.
[Galaxy S II Original Android Development] cTrox:
Ok, just compiled and seems to work great! It doesn't jump anymore while scrolling now :)
[Galaxy S II Original Android Development] FRLinux:
Problem with swiftkey keyboard

I am on latest nightly (2011-07-23 13:38:00) and still have an issue when trying to select swiftkey instead of the gingerbread keyboard, it doesn't happen. I am attaching logcat, let me know if/how I can help some more.

As mentioned before, thanks for your hard work, i love that ROM better than any other custom I have tried for the sgs2.

Thanks,

Steph

UPDATE

: I removed the app, rebooted the phone and re-installed the app, all working now, sorry for the noise.
[Galaxy S II Original Android Development] codeworkx:
Did you recompile the kernel?

Because the fix isn't in actually because gerrit code review is ****ed up.

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

just look into the first post...all links are there
[Galaxy S II Original Android Development] lindsaytheflint:
I haven't had that problem with these builds, but I used to have a similar issue back on my HTC HD2 with some ROMs. Try toggling "signature verification" in CWM. If that doesn't work, try unzipping the contents of the zip, re-zipping the contents into a new zip, then flashing the new zip.
[Galaxy S II Original Android Development] Caspian3011:
There isn't a toggle for signature verification in the rommanager. The weird part is that when I download the recovery via manager and reboot the device into my current recovery (cw 4.0.0.2) it flashes the update.zip, but the first time I reboot the device to recovery again it says that the recovery version is 4.0.0.2.
[Galaxy S II Original Android Development] kawa636r:
We are going to fix it. I'm working too on it but its not simple because only ad2p was fixed but without skip and next featuring control.
[Galaxy S II Original Android Development] mbroeders:
It has happened to others as well. Check Osmonitor to see if a process kept the CPU at 100%. But this should either be posted in the Q&A thread or you should have attached a logcat. Like the devs say, without proof such as a log, there is no bug ;)
[Galaxy S II Original Android Development] swatsbiz:
From Clockwork recovery switch signature verification off
[Galaxy S II Original Android Development] codeworkx:
bad download, redownload and try again.
[Galaxy S II Original Android Development] bikeracer4487:
Is anyone else having issues with setting wallpapers that aren't officially included Cyanogenmod Wallpapers? Every time I try to set a wallpaper from my gallery it appears blurry, like it's been blown up, even if it's a picture I downloaded that's exactly 960x800 pixels. Also, where did the stock wallpapers go (especially the hidden ones unlocked by certain ROMs). There were several that I really liked, and the CM wallpapers leave much to be desired, I just can't seem to find any wallpaper packs that don't appear blurry.
[Galaxy S II Original Android Development] mixailo:
I think this is generally the issue when stock gallery sets wallpapers. They get poorly resized, no matter what resolution they are in. A workaround is to use a wallpaper app like Zedge. Perhaps QuickPic also has better resizing, I'm not sure.
[Galaxy S II Original Android Development] phunkycow:
Get "Wallpaper Set and Save" from the market. It's lite and gets the job done. Or Zedge/Flikie like the previous poster mentioned.
[Galaxy S II Original Android Development] Tamil92:
Try This One

1st : Flash i9100XXKG1 Firmware with odin

2nd : Flash Backslash-1.3-CF-Root-XXKG1 Kernal(include ROOT, CWM..)

3rd : Boot in to CWM(Vol up + Home + Power) Go To MOUNTS and STORAGE & select FORMAT system then data

Now Install ROM :) it must Work
[Galaxy S II Original Android Development] california6006:
Im on cm7 since yesterday and i dont want to miss it now...which launcher is that adw or adw ex?am i the only one or are there some people too whose menu scrolling ist not smooth..its only on adw
[Galaxy S II Original Android Development] codeworkx:
It's adw. Yes, adw is laggy.

adw ex is much smoother.
[Galaxy S II Original Android Development] xmRipper:
What about the stock gingerbread launcher? Does anyone tried to flash it?

It should be the smoothest launcher.
[Galaxy S II Original Android Development] codeworkx:
yes, without any features like custom dock icons. xD

stock launcher is fully useless.
[Galaxy S II Original Android Development] Sebring5:
Try Sony Home for a launcher. Works like a charm. Simple and to the point. Adds folders if you wish. You can sort app drawer by date installed, alphabetically, recently used or your own custom configuration. App drawer as well as dock has a transparent back ground in the version I use. Widgets are scrollable. I got it from one of the XDA threads. There were quite a few different versions. Mine is a .apk that I can click on in Root Explorer to install. I use it on just about every rom I flash.
[Galaxy S II Original Android Development] aliander:
With GTalk definitely no

With G3 I only tried with Stock ROMs - worked there, but as I have to pay for those extra, I didn't tried 'til now.

BUT: How the hell did you figure, that the development forum would be the best place to post such a question?
[Galaxy S II Original Android Development] Goddchen:
i have seen a severe problem with airplane mode. I have installed nightly 3 and the search function didn't turn up any reports of this bug.

When i activate airplane mode it activates just fine. But i have no way to disable it again. On the power menu is grayed out and can't be selected, and in the settings it is not marked as active.

Did anyone else see this bug?
[Galaxy S II Original Android Development] aliander:
Hi there!

Had the same issue... seems that mode changes just need some time - maybe getting hung up in a state??

so just try to give it some time ...

EDIT: And/Or provide Logs ;)
[Galaxy S II Original Android Development] avetny:
updated prebuilt kernel and modules, touchscreen fix by vitalij (android_device_samsung_galaxys2)

probably haptic feed back will be fix too (vibrator.ko)
[Galaxy S II Original Android Development] avetny:
Its not issue my friend.

Samsung working like that to save your battery (deep sleeping)

For nonCyanogen rom's it takes 1-2 second to wakeup.
[Galaxy S II Original Android Development] atinm:
Funny, I was gone from XDA for about three days. Came back to many pages on this thread. Found no need to respond to even one so basically this thread is useless to us.

Just so people understand - bug reports: we're ok with seeing logcats/dmesg for crashes, even straight out bug reports where you've done *some* analysis ("It doesn't work!" isn't a bug report). When we talk about "no bug reports", we actually mean don't send official bug reports into the CyangenMod bug tracker. Those will just get deleted if they're about a nightly.

Changelog - the changelog link is good - a device's changelog includes everything that is specific to the device + everything that happened in common code that is included in the build for that device. Sometimes the common code change is due to something changing on another device, but because it is common code, we get the change too because the code is shared and so we want that to get tested as well to make sure it doesn't break anything for us.
[Galaxy S II Original Android Development] Stonos:
The extract-files.sh script seems to put the proprietary files in the wrong directory. You'll have to manually move them to the correct directory. Check the make script for the correct directories.
[Galaxy S II Original Android Development] codeworkx:
fix it and send a patch to gerrit.
[Galaxy S II Original Android Development] atinm:
Take a look at the extract-files.sh script, it pulls the files off your phone into the appropriate directories. Based on the errors you are seeing, you should be able to fix up the extract-files.sh script. Once you fix it, send it to gerrit and we'll pull it (leaving you as the author, so you get your name on CyanogenMod's source repo ;-) ) - and it'll be fixed for the next person to try.

Thanks,
[Galaxy S II Original Android Development] atinm:
It would be if there were no bugs, but sadly, this isn't true . . . we know of most of them tho', so in fact, no bugs is good. But if it is *new*, it would be useful to see the logcat/dmesg output as well as an explanation of how to reproduce the bug.
[Galaxy S II Original Android Development] atinm:
No - CM7 comes with the default Android Mail app, we don't usually change the apps unless there is someone who is willing to work on it and own the application, and it enhances functionality. That is how come we use ADW as our launcher instead of the stock launcher as well, the code was open source, and it was better than the stock launcher.
[Galaxy S II Original Android Development] avetny:
cm_galaxys2_full-4.zip

http://mirror.cyanogenmod.com/?device=galaxys2

update:

*video camera not working

*haptic feedback still laggy (after deepsleep)
[Galaxy S II Original Android Development] atinm:
We haven't changed the partitions from stock - you can, in fact, go back and forth between CM7 and stock (or any other ROM based on Samsung stock -- which is all of them except MIUI basically) just via ROM Manager/CWM. Just make a backup and restore whichever one you want. The partitions do not change.
[Galaxy S II Original Android Development] atinm:
Do not use any other kernel unless your kernel developer says that his kernel is compatible with CM7 (we do not track what other kernels are compatible or not). For now, I'd say don't use any other because the kernel is still in active development and the other kernels will usually be behind. If you do use another kernel, do not post anything about said kernel (or CM7 in general while using that kernel) on a CM7 thread.
[Galaxy S II Original Android Development] nickwarn:
having big problems with gallery, the scan is taking forever. Newest nightly released today, and i havent had this problem on any of the other nightlies and i tried them all. Also this was the first nightly that didnt sync from market on set up, it only synced settings and restored wallpaper. So i wiped clean and formated all options and flashed again, didnt help had to install 100+ apps manually. But other then that it feels tiptop.
[Galaxy S II Original Android Development] adyscorpius:
Delete the .thumbnails folder inside /sdcard/DCIM.

It helps me sort it out...
[Galaxy S II Original Android Development] Stonos:
Ok, fixed :)

I also added the missing files that I described here.
[Galaxy S II Original Android Development] codeworkx:
thank you. ;-)

gives us time to focus on important things.
[Galaxy S II Original Android Development] atinm:
Thanks! Merged. *This* is what the thread is meant for!
[Galaxy S II Original Android Development] atinm:
They are readable yes. Were you continuously plugging and unplugging the USB? It seems to be in a cycle, and I want to make sure this isn't an artifact of your test method. The files are fine.

We aren't actually looking at this bug - think of posting dmesg/logcat as useful in that we'll look and if it is something obvious, it'll get fixed quickly. If it is not obvious, then it gets on the queue of things to get fixed and will get fixed in time. This is not an obvious fix (most things aren't).
[Galaxy S II Original Android Development] codeworkx:
plugin -> vold does mounting -> mediascanner starts doing -> unplug -> vold gets confused -> mediascanner killed -> plugin -> vold mounts again -> mediascanner starts again -> unplug -> vold gets more confused -> mediascanner killed again -> plugin -> vold says "f**k you!"

that's what i would do xD
[Galaxy S II Original Android Development] DvTonder:
Has this code been put up on github yet? I cannot find it.

I want to see if I can help with the fix but need a place to start.
[Galaxy S II Original Android Development] brujoand:
The SMS bug

SMS and android.

Scenario 1: Stock Andriod on SGS2, not even rooted

- Recieved an sms from gf.

- Replied to sms.

- Sms was sendt to wrong person. (My uncle :S)

- Tried to reply to my gf sms again

- Sms is still sendt to my uncle.

- Try to create a new sms (not reply) to my gf.

- Success!

Scenario 2: Cyanogenmod nightly 3

- Same exact ****...

Now, the bug in it self is ofc not a CM bug. But a fix could be. I haven't looked into the internal DB structure for sms but as i understand it there is a unified sms db that all sms apps use. Has any of the devs heard of this bug before, and tried to look into it?

A google search shows that there are quite a few people with this issue on the android platform. --> http://www.google.no/search?q=android+sms+bug

Now this article has a possible description on how to reproduce the bug -> http://www.androidguys.com/2011/01/03/android-sms-bug-real/

Also there is a bug report for it here --> http://code.google.com/p/android/issues/detail?id=1233

I'm just saying that it would be a pretty nice PR-stunt for CM to fix this before google ;)

So for now, my dirty texts to my gf, go by email, and not sms XD
[Galaxy S II Original Android Development] atinm:
Think of CM7 as a new phone - a Nexus S if you really want to think of it as similar to something else. It is *not* a Samsung phone anymore. If you want Kies or any Samsung apps etc to run, you need to be running a Samsung or Samsung derived ROM. This is not it.
[Galaxy S II Original Android Development] Nathalex27:
Just wanted to say thanks for all the great work!

Not on cm7 yet becouse I use a lot of "low priority stuff" like bt streaming all day in my company van and HD camera to film the dogs in my group ( dog walk service ) for my clients.

I think if that "lp"stuff is working a lot more people would use this rom and you would get alot more usable feedback.

No question here, just an idea.
[Galaxy S II Original Android Development] atinm:
Those are actually not low priority per se - we are working on HD camera now (and play for that matter). BT is high on my list, but below what I am currently working on - the hope is that someone else will get to it before I do. bmarko82 on MIUI is also working on it and has been in touch with me, so we'll see.
[Galaxy S II Original Android Development] jimmy72:
Thank you

Hi,

Thank you for your quick reply !

The adventure of CyanoMod will be more excited !!! GREAAATTTTTT WORKKK

Please all CM7 users donate to these fantastic devs !!!!!!
[Galaxy S II Original Android Development] avetny:
never see this before

in upcoming build 5:

updated prebuilt kernel and modules (android_device_samsung_galaxys2) updated prebuilt kernel and modules (android_device_samsung_galaxys2)

2 times change the kernels

http://cm-nightlies.appspot.com/?device=galaxys2
[Galaxy S II Original Android Development] norpan111:
Can someone tell the name to put in my circles ?:)
[Galaxy S II Original Android Development] aliander:
http://gplus.to/codeworkx

http://gplus.to/atinm
[Galaxy S II Original Android Development] goldbergx:
After installing the latest build, I opened the Gallery and a particular wallpapers folder with 208 pictures. The phone went berserk - hot + DownloadManager at 48%.

alogcat file for that moment (first time "bug" reporter - be kind!)
[Galaxy S II Original Android Development] StarF:
running nightly build 4 here, running pretty good i must say. Phone feels fast, and after 2 days of use, i havent had any isues at all. Only thing was the phone dident start to restore my apps, like it would normaly do, instead i had to do it manualy, but else, i would say its pretty usable already now. tnx for the hard work!
[Galaxy S II Original Android Development] Alienfreak:
Probably an issue with unrecognized media again.

Give them the link to it on Twitter or Google plus. They won't read it here anymore ^^
[Galaxy S II Original Android Development] norpan111:
Thanks!

Edit: doing that from the phone was impossible
[Galaxy S II Original Android Development] codeworkx:
You really don't know what are you talking about.

Hardware acceleration is very hardware specific.

There's no soution which will work on all cm devices.

And doing so would take a lot of time, nobody of us have this time because we're doing this for free and in our free time.

Pay us, give us the needed documentation for the hardware (you'll not get it from samsung), give us some training and we'll do it. :-P
[Galaxy S II Original Android Development] codeworkx:
did a fresh build to make sure. haptic feedback is working.
[Galaxy S II Original Android Development] :
edit the source code not the apk, please and sent it to r.canogenmod.com for review. Then we can improve your solution together.
[Galaxy S II Original Android Development] codeworkx:
http://wiki.cyanogenmod.com/index.php?title=Main_Page
[Galaxy S II Original Android Development] :
The best page to see what the changes are between the nightlies is: http://cm-nightlies.appspot.com/?device=galaxys2
[Galaxy S II Original Android Development] pulser_g2:
Oh come on... Are you guys scaring devs away again?

If you are gonna ask questions, consider this as a workflow. I still follow it when I post :p

1) Am I about to make a post requesting a timeframe for completion or progress of something which people are doing for free in their spare time? If yes, abandon post.

2) Is this post going to ask something already asked in the last hundred odd pages? If I have a problem, it is likely answered by others doing the same as me. If answer is yes, abandon post.

3) Have I searched this thread using the button above the first post? Have I read the results?

4) Have I read the first 2, and last 5, pages of this thread in full, to get an idea of the tone... And if this post doesn't seem right, abandon

5) Is asking this going to make me look stupid? Such as asking what a nightly is... If it's a question of terminology, use Google. It's your friend, as well as mine :)

6) Am I just not meant to have the ability to post on a technical forum? If you think you are unable to contribute and discuss without pissing off everyone around you, it's not them at fault... It's you! Contact the nearest moderator and explain how you thought this was someplace else which allowed pointless and annoying demands for ETAs. They will be happy to remove your posting abilities, to preserve the sanity of the rest of us.

If you reach this point, you search again, and finally start to post. Notice all that thinking there? It's important and stops you looking like an uneducated dyke when everyone laughs at you.

So quit pissing off devs. It's not everyone, in fact it's not most people. But that special few, who just insist on spoiling it for everyone... Mark my words... I am onto you. (no really, I am!)

That's all.
[Galaxy S II Original Android Development] pulser_g2:
You called? ;)

If people are acting like animals, report their posts or pm me or another of the mods.

I like a trip to the zoo as much as anyone else, but I don't recall this thread being a zoo...

So if you see escaped 'animals' posting and making a nuisance of themselves, hit report post or drop me a PM and I'll come hunting for them and send them to the zoo on a one-way trip via bansville...

Dev forum requires ten posts. Perhaps that needs increased, but manual processing of people just isn't an option unfortunately :(
[Galaxy S II Original Android Development] pulser_g2:
If you send it to me I can give you a very quick assessment of feasibility, as I have worked on modifications to the site before...

Due to the size of XDA, many search related things fall down due to the immense loads that would be involved...
[Galaxy S II Original Android Development] norpan111:
Done, just dropped a mini version in pm