yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] RaptorOne3:
Well at least now you know where to focus your work... :D I'm many steps ahead of you brotha. Have you noticed my signature? It does not say CM7... It hasn't for about a week or so...

I am fully aware that it's a WIP. I have stated that multiple times. Which is also why when each update is released, I download, flash and test away. Each time, the issues I bring up here in this mysterious thread, are still the same. I'm curious as to why.

I fear that development priorities may be a little skewed here. Based on the few recent updates that have been established it seems that ROM stability and reliability are not of interest to you. Which is strange IMO. With all the logs and bug reports you've obtained in the past 2 weeks the few fixes we have seen seem a bit redundant to the actual functionality of the ROM.

Criticism is part of open source buddy. If you can't handle the heat then get out of the kitchen. I'm criticizing the flaws with the ROM (as a WIP) so you can work to perfect it and you're telling me to shut up basically?

If no one issue reported, what would you do?

If we're not permitted to discuss the issues we're having in this thread, then what is the overall GOAL of this thread? If not to enlighten other users/developers of the flaws with the ROM, then what? What types of discussions are MEANT to be had here? I'm a little confused with this right now.

I'm sorry if my criticism isn't the most constructive. I do apologize in that aspect and I'm aware that my ranting doesn't necessarily help. However, I have looked for constructive ways to say it. Quite honestly, there are none. WYSIWYG. The issues people seem to be having with the ROM seemingly do not show in Logs. And the issue reporting seems pointless when you don't address the issues...

IN MY OPINION, streamlining, stability, and optimizations should have been first on the list. Then all the other redundant little app bugs would be next. You guys fixed a Skype app bug before looking into ROM optimization? I may be alone on this but that just seems like bad prioritizing...

But it's not my baby to spank so best of luck to ya...
[Captivate Android Development] chasesavestheday:
please go away. if you want to rant and ***** go to the Q&A thread. this is obviously not for you. come back when its ready.

CM7 > you.
[Captivate Android Development] Zilch25:
This thread exists for community feedback, end user to end user support, and occasional helpful feedback from the devs themselves. It does NOT exist for end users to direct development. Hope this helps!
[Captivate Android Development] RaptorOne3:
And this post is more constructive than mine? How so?
[Captivate Android Development] RaptorOne3:
No one is directing anything...

I'm pointing out flaws. Just like you attempted to do.

Unfortunately the flaws I'm having the biggest issues with do not show up in logs. I have already looked at them myself.
[Captivate Android Development] atinm:
Looks like you've mixed and matched kernel and system. This isn't the stock kernel you are using, correct?
[Captivate Android Development] TheEscapist:
Yeah, your wifi driver doesn't match the kernel. Assuming you flashed the install correctly, the modules must not have updated correctly. Try redownloading the update and reflashing.

Or, you could just push the modules from the update to the phone, with out flashing, but you would need adb.
[Captivate Android Development] Zilch25:
Correction, you've been getting surly over the fact that the things you care about aren't prioritized over all else. Your feedback has been noted, you've even been personally addressed by a dev and told to step away from the ROM till it suits you, no need to continue pounding your points into the thread, we know you like Cog, enjoy it while we enjoy CM7.

/threadcrap
[Captivate Android Development] TheEscapist:
If you look, the kernel is atin@waltest9. That's certainly not my user/hostname, and probably not ytt3r's either. Id say it's yours.
[Captivate Android Development] chasesavestheday:
still running same kernal. havent changed since initial flash. ive installed newest updates on top of each other, and flashed from stock radio to kb1 and then jk4. how the heck would the kernal get mixed up?

went back to 3/11 once again and wifi worked first try. interesting.
[Captivate Android Development] TheEscapist:
Like I said, it probably just flashed the modules and/or kernel wrong. Redownload and reflash.
[Captivate Android Development] RaptorOne3:
And thus, the reason this project will never get finished.

Prioritization is important. In order to make something work, you have to focus on the things that make it work to begin with...

Skype functionality does not help optimize a ROM...

JUST SAYIN! lol And that's all I'm sayin really...
[Captivate Android Development] mcord11758:
Raptor one

I believe you have made your point. You do not appreciate what this rom offers. You enjoy a stock samsung froyo it is a preference I guess. Stick to what you like and understand, I can guarantee that no one using this rom is eating their time posting on the cognition thread

CM7
[Captivate Android Development] atinm:
Like I said - go away until this is done. This is a development thread for a kernel and ROM that is under active development and what you want is really something like a ROM built on top of Samsung Froyo code. Something like what you're already using. If you love it so, stay with it.
[Captivate Android Development] AJerman:
Well then learn something about coding and get to work yourself, otherwise stop complaining. These people are spending their free time to develop software for free for you. They can prioritize it however they want. Getting everything working is the first priority, then optimizing (by the way, this is how ALL development cycles work). If you don't like the process, then move on, like everyone has already said. Hopefully all the issues will be sorted out soon, then you can try it again, until then, offering bugs and logs of the bugs is helpful to the developers, telling the developers what to work on is not.
[Captivate Android Development] Zilch25:
Kay. You heard it here first folks. CM7 will never be finished, time to pack up our extra batteries and go home!
[Captivate Android Development] chasesavestheday:
well if it makes any difference here's the dmesg & log now back running the 3/11.

as in re-download and flash everything. meh.

dmesg:

http://www.mediafire.com/?8viuk95mop6nw4p

log

http://www.mediafire.com/?ki0b20hl8qvnzbp
[Captivate Android Development] RaptorOne3:
LOL That's because Cognition 4.1.1 doesn't have any optimization issues... It's fully optimized. designgears does great work. Why? Because he prioritizes his work properly.

First and foremost is ROM functionality and optimizations. Afterwards you work on the smaller stuff like application compatabilities and what not... These guys are jumping all over the place fixing little redundant bits here n there.

JUST SAYIN!
[Captivate Android Development] mcord11758:
Sheep.....

CM7
[Captivate Android Development] chasesavestheday:
you've obviously never head of cyanogenmod. this is a huge step for the captivate community. huge step.

member since dec 2010? really 3 months and you're complaining?!
[Captivate Android Development] Zilch25:
You're right. Cog is optimized, that's what cog is. Vanilla Samsung firmware made less terrible. This is a completely different beast, perhaps you should learn a little background on roms before you start trying to be the creative director...

JUST SAYIN
[Captivate Android Development] atinm:
True. But somehow his .ko doesn't match. Maybe a reflash to make sure . . .
[Captivate Android Development] TheEscapist:
I think for once, a thread's tags are actually relevant.
[Captivate Android Development] TheEscapist:
Yeah, like I said, it probably was just a bad flash. If he had adb, he could just push them, but *shrugs*.
[Captivate Android Development] RaptorOne3:
It was merely a suggestion. I never told anyone what to do. Am I not entitled to that much? I mean, you all seem to have your opinions just as well as I.

I'm fully aware of everything you have all stated. And I am already on a stable functional ROM of my liking and have been for a while...

But I frequently check back on CM7 and test out the updates. I fully appreciate what work goes into it.

I was just pointing out that from my testing and observations from what has been done so far, it seems that the priorities are a bit skewed. Thats all. Sheesh... You guys act like I'm insulting the ROM...

If I didn't appreciate the ROM, the developers working on it, or enjoy it at least a little bit, I wouldn't be in here at all. The problem is, I do. I want to see it work properly. I want to see it get done properly...
[Captivate Android Development] chasesavestheday:
if you go up a bit i posted the logs after going back to 3/11. maybe a little comparison of the 2 will show something. idk. thanks for the help though.
[Captivate Android Development] RaptorOne3:
Maybe I'm more aware of the process than you think. And maybe you shouldn't let this affect you in a personal manner...
[Captivate Android Development] TheEscapist:
It just shows that your wifi is working, which you had already told us. :p
[Captivate Android Development] chasesavestheday:
heh, i have it now. just need to grab a JSK file to install. could you explain what i need to do to push the items? either here or a pm would be great. thanks!
[Captivate Android Development] atinm:
Just sayin' too, DesignGears uses other people's code for his ROM and builds on top of them. He has even used my kernel before when I was the first one out with lagfix and BLN for Captivate and from Unhelpful when he was the first out with OC. He is developing on top of an optimized substrate that was open sourced by Samsung and has greated a generally very usable ROM. But do not confuse that with kernel or even App development. We don't have the same luxuries for CM7 - we are doing a lot of stuff new and are having to work off code that wasn't actually written for our phone (Nexus S is similar, but not the same at all) and optimization is the very last thing that gets done during ALL development. Please don't actually try to teach us development . . . you just look like a fool and irritate the heck out of us . . .
[Captivate Android Development] TheEscapist:
Pretty simple. Unzip the update somewhere. Then, type in "adb push /path/to/update/system/modules /system/modules". You'll probably require a reboot.
[Captivate Android Development] Zilch25:
If you're comparing CM7 to Cog I sincerely doubt it.
[Captivate Android Development] pparavas:
wish the camera could be improved a bit more than the existing...
[Captivate Android Development] Zilch25:
Yeah that last post pretty much completely outted you as clueless. Perhaps your time would be better spend asking people in general when 2.2 is coming out for Captivate

(Not you pparavas lol)
[Captivate Android Development] atinm:
Noted. I've yet to see any code from you when all you have to do is a cut/paste from Nexus S to get CM7 working. You should definitely do it. Heck, we'd be in awe if you even just managed to get the sound working with Captivate modems so we can use the Audience chip. Or even GPS, compass, 2G/3G toggle. How about just going into the battery stats and making it scale for the battery's actual capacity? Or even just making the thing recognize multiple sd cards given that Nexus S doesn't have them? C'mon - we'd be eternally grateful. If you can't, don't tell us what is easy or hard.

This is tiring, I have work to do. /ignore
[Captivate Android Development] pparavas:
General CM7 experience.

I used the kernel developed by escapist and changed the voltage values and actually reduced the clock speed to 800MHZ as i dont need to worry about faster computing. The phone runs like "O hell yeah" along with the battery life better than stock... 19 hrs of moderate usage... dream come true for my phone... thanks cmsgs developers and escapist for providing a kernel that supports OC/UV:o.

I use goggles a lot. But i somehow get FCs when i open goggles, is anyone else facing the same problem, or is it a known bug?
[Captivate Android Development] RaptorOne3:
I was comparing battery drain.

Both ROMs are based on stock firmware.

2.3.3 for captivate is a port from Nexus S.

You would think at this point they would have had something that simple figured out already...
[Captivate Android Development] zelendel:
Ok guys enough of the bickering. CM has been known to be leading the way in android dev, and if you dont believe me then do a search and read for yourself. Please do not come in here and degrade the great work they are doing.

Think it is so easy to do this stuff. Lets see your own custom build. Oh wait thats right your running Cog (someone elses rom) cant be as easy as you say
[Captivate Android Development] AJerman:
Alright guys, lets get back on topic. If people are being annoying, just ignore them. We've wasted the last 5 pages or so on this now. Thank you zelendel.

Edit: And Mr. Clown :)
[Captivate Android Development] Mr. Clown:
Did some thread cleaning. Back to topic please.
[Captivate Android Development] TheEscapist:
Thanks for using it. :)

And yeah, it's a known bug. Goggles is broken, and it breaks camera as well.

Logcats and kmsgs are always helpful, though.
[Captivate Android Development] jhernand1102:
Yes fully optimized by Samsung, all DG did was take out the bloat and inject voodoo into the kernel... This ROM is a whole different beast and it's working great for me. JUST SAYING....:D
[Captivate Android Development] techmik67:
Wow.....zilch lives!!! Good to see you....
[Captivate Android Development] Roof King:
Many thanks to Atinm and the dev team for bringing us the best rom experience to date. I mean we are talking Gingerbread here which we'll probably never see if we wait on Samsung and AT&T.

You are appreciated!
[Captivate Android Development] ytt3r:
Its just a port? then by your logic, Android itself, on any phone besides the G1, is a port.
[Captivate Android Development] zelendel:
Ok guys I have said to let it drop and another mod as also cleaned this thread to remove some of it. I will say this one last time. DROP IT!

Back on topic.
[Captivate Android Development] ytt3r:
The AOSP. Not from any OEM. That's all. I'm done with any arguing that this might have caused. And you say they didn't appear out of thin air? Google made them, codeworkx and coolya modified them. :)
[Captivate Android Development] shaolin95:
Hello shaolin95,

I tested this for you and it worked!

It also works awesome with the Trident kernel at 1.4Ghz :D
[Captivate Android Development] shaolin95:
Thanks for testing mate...btw, you are very handsome! :D :p

PS I think I am losing it :eek:
[Captivate Android Development] TheEscapist:
Well, technically ytt3r, the Nexii also got their code direct from Google, but yes, you are right.

Well, if they didn't come from any other devices, then *gasp* it can't be a port, now can it?

The CM7 sources came from where all the cm sources have ever come. The AOSP team, and the CyanogenMod team.
[Captivate Android Development] RaptorOne3:
Yep. They ported it to the device of their choice. Which is what the guys did for the Captivate.

Haves a look - http://source.android.com/porting/index.html
[Captivate Android Development] n0stalgia:
Is anyone else getting really bad call quality with CM7?
[Captivate Android Development] xpakage:
Damn

I was looking for a new ROM to try but I am afraid if I tried this one, my phone would break out in *****es and then would need some anti monkey-butt powder (real stuff-even has calamine to stop friction http://www.antimonkeybutt.com/ ).:p
[Captivate Android Development] Carver1:
I had this rom for a few minutes lol. It was smooth as hell. But for some strange reason I couldn't sync to google. I might have missed something somewhere. But that was my main gripe. I might try it again later down the road as it seemed like it was smooth paging through the windows and what not. I liked the theme that came with the package.
[Captivate Android Development] kschumake83:
did you miss installing gapps maybe??
[Captivate Android Development] Kaik541:
I'd like to think I've been almost nothing but helpful and informative through 90% of this thread. but I can't hold my tongue... what. the. almighty. *expletive*?

this might be the dumbest thing I've ever read. you must be confusing this CM7, built from source by 4 or 5 very intelligent people for the old "Nexus S on SGS" ROM that supercurio put out. if you can't understand that having to modify tons of source code just to make the phone even BOOT as compared to serendipity/cognition/phoenix/etc where it's the relatively easier "let me add and remove some files, deodex, pngoptimize, zipalign, add a hosts file, optional themeing and put it in a noob friendly zip" (these other ROM's are good and do what they intend to, but the scale of work that's different is like comparing building a car to playing with hot wheels... they're not even in the same ball park).

jesus christ almighty.
[Captivate Android Development] citrit:
Thanks, well put!
[Captivate Android Development] techmik67:
Try the different modems.... =)
[Captivate Android Development] zas0006:
To all the devs working on this:

Thank you for the awesome rom and if there is anything I can do to help as far as testing and the like please let me know. Also PLEASE do not let a few bad apples ruin it for the rest of us. I enjoy reading over what all has been done both here and on the cm7 forum and would hate to see development get walled off because of a few people who can't listen to the devs and mods.

Thank you for making my phone a kick ass, gingerbread running, Samsung-**** free work of art.
[Captivate Android Development] nkrick:
What modem are you using? Try some others, but stay away from KB1 unless you have one of the 1006 or 1007 revision phones that does not like i9000 modems. The KB1 modem depends on the audience chip for voice processing and CM7 for captivate doesn't include audience support (yet).

I have a 1007 and had issues with i9000 modems in the past, but either by luck or by flashing the modem twice (there has been a report that flashing the modem twice works for some people who have stubborn 1007 revs), JL3 works fine.
[Captivate Android Development] peachpuff:
Its painful listening to his drivel i know, but i think i found the solution :D
[Captivate Android Development] mnjm9b:
There once was a man from Nantucket...........
[Captivate Android Development] krazyphire:
Reported.

Fairly certain 2 mods have already had to come in here and clean up. I'd suggest if you're not interested in the ROM being worked on by these great devs that you just leave.
[Captivate Android Development] techmik67:
One mod cleaned the thread and told you to drop it..... another mod told you TWICE.... you just wont listen, huh?
[Captivate Android Development] insaneturbo13:
Very well put :)

And to atinm: your doing a really good job of being professional through all this
[Captivate Android Development] techmik67:
<uncover mouth>

can you say "closed source drivers"?

<covers it back up before i say something bad>
[Captivate Android Development] h0ckey10:
i think we all know who's won this argument. here's a question on the side note:

if we are on the most up to date nightly there is no need to flash newer version of the initial kernel and initial.zip correct? this is just for people doing a fresh flash i take it?
[Captivate Android Development] Kaik541:
yes to both the comment and the question
[Captivate Android Development] atinm:
That's right - it's for fresh installs only. Some people were having trouble with updating on top of previous version due to bad blocks in the boot partition.
[Captivate Android Development] RaptorOne3:
That's precisely why you have to look at the other official builds.

It's all there... If it wasn't they wouldn't function.
[Captivate Android Development] techmik67:
do you know what CLOSED source means???
[Captivate Android Development] h0ckey10:
thanks for the quick reply.

that's what is great about CM7 not only do you great support on the forum from the devs and everyone else (well most), u also get extremely frequent updates. and as someone mentioned earlier, these people are doing what they do FOR FREE and are not obligated to do so by any means. just appreciate that and dont waste time arguing with them over something that wont do you or them any good.
[Captivate Android Development] Kaik541:
ah so you're saying we should use the closed source drivers that we can't find open source alternatives to? wow you must be a friggin genius and the first person to ever come up wi--*someone whispers in my ear* what's that? that's what cyanogenmod does already? oh, my bad
[Captivate Android Development] TheYar:
Settings.Secure

Not sure if this is the right thread, but before I go trying to post a bug or feature request I wanted to mention it and see if anyone can clue me in.

Does CM offer the ability to enable app access to Settings.Secure class values? I think apps like Widgetsoid used a loophole or something in other builds to access settings like enabling GPS or turning on wifi. Android ID Changer on most builds seem to be able to get to the ID, if properly rooted and busyboxxed. But on CM these apps fail or bug out. Widgetsoid defaults to just opening the settings page for Settings.Secure stuff like GPS, even though CM offers other widgets that can enable/disable GPS directly. Can anyone help me learn / understand this better so that I can even form my question coherently? I'm wondering what is necessary to allow direct modification of certain system secure values by applications.

JUST SAYIN' :)

P.S. Even if we get rid of the troll, please don't feel compelled to compensate by filling the thread with, "just want to say thanks, love your work." Those are almost as bad and will turn this into a Cog thread in no time. I do what I can, I've beta tested for app devs and ROM chefs, created how-to threads, and now I'm trying to show my love for CM by seeing if I can legitimately log some issues and help resolve them. Just posting that you love their work is,

literally

, the least you can do.
[Captivate Android Development] mcord11758:
My solution is all nightlies must be approved by raptore one going forward.

CM7
[Captivate Android Development] shaolin95:
Guys is there a better way to change the LCD Density for this ROM? I used LCD Density app and it worked but while performance of benchmarks is the same..scrolling of the home page looks strange...not smooth as it was at 240. I never saw that with other roms so maybe the app is not quite right for this rom.

Thanks

PS I was trying to do 182 density in case someone knows how to.
[Captivate Android Development] Zilch25:
We look forward to seeing your masterstroke, good sir.
[Captivate Android Development] h0ckey10:
all of this arguing should really stop. it defeats the point of the thread. when i was done with school today i pulled out my phone and saw there were about 10 unread pages on the cm7 page. i thought maybe something had been fixed or there was a substantial update. wrong. it was 10 pages worth of back and forth arguing between raptor and everyone else. keep this thread the way it was meant to be, about cyanogen mod 7. while i agree he is wrong on most of what he says, all of the responses he's getting just keeps fueling him to post more and more.

if you really want to keep this going, start a "raptor vs the world" post in the off-topic section. not here

just my opinion
[Captivate Android Development] capita:
You coul go about altering the build.prop which should have the same effect. http://xdaforums.com/showthread.php?t=760805

I'm running on 200 density and haven't noticed any difference in smoothness of scrolling. Could be the launcher you're using. I use LPP since I found ADW to be kinda laggy and sluggish.
[Captivate Android Development] Mr. Clown:
You didn't let go this right, we have warned you 3 times (2 different moderators).

@ OP. I will close this thread temporary to do some heavy cleaning. Please understand. I will open this later.