yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] {Angel}:
I dont care for any of those features as well and I'm sure I'm not alone here. There are more important issues right now that could use some work. But correct me if I'm wrong but bln and voodoo as in voodoo color are not in the main line kernel. If people want those there are other kernel options. I really hope youre not done with the sgs1!
[Galaxy S I9000 Android Development] Rat2000:
BLN is active in the latest build. you said that ther eis no bln but led notification.

Isn't led notification the program that makes a pixel red or some random color on youre screen, and bln the buttons from Menu and Bck? if so, then bln is active in the latest builds.
[Galaxy S I9000 Android Development] jose.celestino:
No. Search this thread.
[Galaxy S I9000 Android Development] hackeron:
Removed.10chars
[Galaxy S I9000 Android Development] beekay201:
I agree with everything that you said. When i posted the pictures, i did it in order to share what i think is a nice feature and addition to cm. it was wrong for me to post it unidentified as a kang feature still in review, in a cm7 nightlies thread. i am young, impulsive, dont stop to think sometimes, i am deeply sorry. won't happen again.

ps: can we have a kang thread then?

edit: i've re-edited the refered post with the screenshots. once again, i am sorry for all the confusion and deception caused.
[Galaxy S I9000 Android Development] sathkartha:
chaos?

All said and done,this has been a high-quality project/thread over so many nightlies that I have been using and have grown very fond of.I get the nagging feeling that this is slowly coming apart both in terms of the quality of the recent nightlies as well some unproductive exchanges taking place.

I really wish we would quickly get this back on rails and march ahead to get RC2 for starters and then on to CM8!

IMHO,we should rather stick to solidity and constant improvements however small than going for cosmetics...

Just a passing thought of a man in his mid-fifties...

May peace and tranquility prevail.
[Galaxy S I9000 Android Development] drakenabarion:
Eep. By that reaction I must have sounded very heavy handed. (And maybe like an angry old man - I am less than 30, too young to sound like that.)

Its very big of you to apologise. I am sorry that I may have posted in a slightly "heavy handed" kinda of way (Don't blame me :-) blame some of the news/politics related websites I sometimes post on :-D ).

The new lickscreen is somethink I look forward to! Hope it can happen.

Edit: stupid autocorrect. But I wont change the typo cause it makes me LOL. ;-)

Sent via my GT-I9000 running CM7 (GB 2.3.5) using XDA premium
[Galaxy S I9000 Android Development] matsuru:
Wow~!! New way to unlock phone~! When will it be added to CM7??!! :p

Sorry, Can't resist~! :D

btw, CM7 #127 with no prob so far.
[Galaxy S I9000 Android Development] drakenabarion:
Its a great feature. Comes in strawberry, vanilla or tutti-fruity flavour ;-)

Sent via my GT-I9000 running CM7 (GB 2.3.5) using XDA premium
[Galaxy S I9000 Android Development] rschenck:
I think as long as we are all careful to stick to the "stock only" rule in this thread things will be fine. As several people have suggested, if someone, even Pawitp, feels the need in the future to release their own Kang with features not added to the Nightly, then it should be treated as a CM7 based ROM and given its own thread accordingly. That way the people who wish to use it and comment on it can do so utterly freely without confusing the Nightly thread..open source in both fact and spirit.

I am sure in hindsight Pawitp would never have released his Kang if he had known the Nightly would arrive two days later. As it was it was like throwing a candy apple into a pit filled with starving mimes.

Now that the Nightlies are back on track I am sure things will become more orderly again. Also Pawitp will learn what all devs must accept eventually...coding is easy, user herding is hard.
[Galaxy S I9000 Android Development] Nexus Two:
hey guys im coming from milky rom, rooted with cwm installed.. so pretty much do the 3 button combo, nandroid, reset & flash? please let me know. ive seen other tuts that are wayyyyy different. thanks in advance!
[Galaxy S I9000 Android Development] rschenck:
Boiled down, that is all there is to it. If you want more words (and lord, I can ramble on), check my Install Guide in the general forum, but you have the crux of it.

Enjoy the cm7 goodness.
[Galaxy S I9000 Android Development] Karupan:
Is it just me or is GPS broken in 124? I've tried various modems, but no luck. GPS test says that NOT A SINGLE satellite is visible/connectable. Logs don't show any errors. Have tried the regular clear cache/dalvik cache/fix permissions/re-flash routine. Has anyone encountered this?
[Galaxy S I9000 Android Development] mgfjd:
I used to be able to play the videos on the KNWA app with the sammy rom's but I can't play the same videos with cyanogenmod. Anybody has any suggestions on how to make these videos play again? another app?

Thanks.
[Galaxy S I9000 Android Development] psynapse:
One strange bug - battery usage itself is great, but the combined percentage of various processes does not add up to 100%. Much higher in fact!

E.g >> http://t.co/JguXFnCw
[Galaxy S I9000 Android Development] aoprea:
i think it's good to add to "quiet hours" option to disable haptic feedback

is useful especially when sleeping next to you girlfriend or child :)
[Galaxy S I9000 Android Development] beekay201:
offtopic:

some more news on kernel.org, for those interested :)

external link
[Galaxy S I9000 Android Development] mobidzid:
Another observation. I was very pleased with #125, I even posted about this couple of days ago. Then the weekend came and the hell started. We were away from the city and driving, so chnaging cell towers often and getting out of the range from time to time (thanks to crappy EPlus coverage). Once we almost reached our destinations I needed to call and found my phone stuck at CM animation and quite hot. Ok, it happens, just rebooted with power-for-10s, called, everything was fine. On Sunday morning I already got the reboot-and-stuck-on-CM-animation twice at least :( And that was time when I needed to check the maps for my way back home :( I flashed #129 as soon as I made it back. But I fear the problems will come back after a while.

I kinda noticed that more less from the time, when we got GB BL support, the Nightlies like deteriorate over time: everything seems to be ok right after flashing and for couple of days after, but then they start going down the slope rather quickly. What can it be? A problem with corrupting Dalvik? Perhaps simple wipe of the caches would help? I'll try it next time....
[Galaxy S I9000 Android Development] rschenck:
Thanks BK, very interesting.

It looks like the long delay was due to kernel.org trying to find a less vulnerable solution or at least one that limited access to the actual database, not just plugging the hole the hackers used.
[Galaxy S I9000 Android Development] beekay201:
autocorrect does that sometimes. :D yeah, i hope it gets merged too. more important things will come first, i hope.

cheers

---------- Post added at 07:26 AM ---------- Previous post was at 07:22 AM ----------

If all goes well, the guys are saying that broader access will be available again in early October, too.
[Galaxy S I9000 Android Development] melorib:
Good decision... :D

Those things are what cause problems in custom kernels...
[Galaxy S I9000 Android Development] mobidzid:
I'm really surprised that you don't. There are lots of people around who do not like their phones to make any noise. Also, I don't have the phone on me at all times. BLN/LED-notification is essential then. I had it in my late Nokias (6230(?) and 5800) and learnt to appreciate this small functionality. It's actually one of my major complains about... iPhone - the lack of any notification of a missed event is simply infuriating for me. OK, granted, on Android NoLED does the job nicely, too, but is more battery-hungry - and battery life is my second priority.

BLN/LED-notification is the reason I went for custom kernels and I'm really happy having it in stock now. Please do help solving the problems with it rather then dismissing it just because you think no one should need it.
[Galaxy S I9000 Android Development] rschenck:
I think part of the problem is that CM7 is first, last and always an AOSP creation. Neither VooDoo or BLN are native to AOSP, each are independently created apps that run ON the OS, not as part of it. They have become so common and widespread that people often think they are native Android functionality, but they aren't...and they therefore introduce a whole lot of variables when they are supported by an AOSP build. Variables almost always cause problems.

Samsung ROMs are often simply collections of whatever third party add-ons and modules, such as BLN and VooDoo, some individual happens to like with a theme slapped over them. Therefore one more extra doohicky bolted onto the side is not going to make much of a difference. If Darky's is going to blitz your phone, it will do it regardless of VooDoo or BLN. The same can't really be said of CM7.

I support the original decision to keep CM7 for SGS AOSP pure, and exclude VooDoo Color and BLN, especially since they can be found in custom kernels. Their exclusion is not a "bug" as some people keep claiming it is, it is a choice. If fixing such "bugs" require introducing third party software into CM7, then I say leave them unfixed. I am willing to give up some possible functionality in return for stability and performance...and I think most CM7 users would agree.
[Galaxy S I9000 Android Development] mobidzid:
Thanks, rscheck. I obviously missed that point and you are right. Again.

So, I'm convinced now and I also 'vote' for keeping BLN/LED-notif away from stock. At the same time I do hope Zach will do it right eventually :)
[Galaxy S I9000 Android Development] insanedreamz:
It seems like my notification volume were all messed up. All volume settings were set to zero after clearing battery stats and fixing permission (had some apps FCs specially Market) or maybe even before that.

I didn't even touch them at all, neither did I set my phone to vibrate or on silent mode. Still LEDs were doing their job perfectly. So first I tried to-

set Ringing vol to full, use ringer vol for notifications, alarm vol from zero to max, increased media vol.

Still when I receive texts, all d things i set above doesn't work! So Again I increased ringer vol with vol up key, and finally it worked...

I'm on #127, never had this problem before. Was there anything I missed?
[Galaxy S I9000 Android Development] nrg:
I don't understand why there is a discussion about these features. If Pawitp (according to some, currently the only active SGS1 dev) can bring them back without issues why not have them? If they seem to be causing issues over time I'm sure they will be removed again.
[Galaxy S I9000 Android Development] Rat2000:
And why is that? i had no problems with this... same battery usage, phone is just...normal with them or without them.
[Galaxy S I9000 Android Development] matsuru:
OK. heads up guys~! CM7 #130 is here~!:D
[Galaxy S I9000 Android Development] siky_dude:
Kaik TL;DR
[Galaxy S I9000 Android Development] burakgon:
Ok flashed 130 but bootloops?
[Galaxy S I9000 Android Development] rschenck:
Thanks for the look into the thinking behind some of the decisions that have shaped CM7, Kaik. You clarified the relationship between AOSP and CM7 very well. As a non-dev, I have always worked from the "marketing" description of CM7, which is as basically an AOSP implementation. Once we accept the difference between an outsider's and an insider's view, we really don't disagree to extensively.

I have nothing against code that can be incorporated seamlessly (and as you noted, transparently) into CM7. You mention LED Notifications, but I have always that was a worthy addition since, as you rightly stated, it is controlled utterly and totally from within the existing Settings menu. Bringing in functionality in such a way is how any code base grows and matures....just as you mentioned that CM7 sends code and features upstream to AOSP. Those changes have to come from somewhere.

Where I feel that things get dicey (and you apparently agree) is in those features that require a third party app to work properly, such as BLN and VooDoo. It is worth mentioning here again that LED Notification is NOT BLN, no matter how many people in this forum choose to confuse them. In order for features such as BLN or VooDoo Color to be incorporated, CM7 effectively has to "license" them, and the developer allows it to be done for free since they are reasonably confident they will see some profit from people buying their control apps down the road. They do the same for all ROMs that boast that they are "Whatever Enabled". I am all for paying for apps I use, but not when their inclusion in my OS requires that I buy something to "get the most out of them" in the OS.

So while I obviously concede the point that CM7 is not pure AOSP, I do argue that it functions from a kind of AOSP ethic, which features like VooDoo Color or BLN is not compatible with currently. If Pawitp or any authorized dev can add features such as VooDoo-like color options without requiring third party apps, or damaging the current performance, then they will do what they think fit...as is right and proper.

---------- Post added at 09:34 AM ---------- Previous post was at 09:33 AM ----------

Reboot....if that doesn't solve it, reflash.
[Galaxy S I9000 Android Development] burakgon:
Hey this doesn't solve my problem. I afraid I must format system.
[Galaxy S I9000 Android Development] ionuts:
#130 working great, also the ring lockscreen is damn nice
[Galaxy S I9000 Android Development] burakgon:
Hey I wonder it! I will make a clean install. Which kernel you using?
[Galaxy S I9000 Android Development] siky_dude:
System is already wiped at every nightly flash. :)
[Galaxy S I9000 Android Development] rschenck:
Did you try to flash a custom kernel before booting up the new Nightly? I strongly advise you boot up a Nightly with stock kernel, and then if you are so inclined, flash a custom kernel later.
[Galaxy S I9000 Android Development] burakgon:
No it's not. All gapps stay after flashing?

---------- Post added at 09:47 AM ---------- Previous post was at 09:46 AM ----------

Ok nice to know this. I tried it but I reflashed with no kernel again same problem. I will use your method after this experiance. Clear install. Do I need flash a stock rom via odin as first? (for a great partition or is it matters?) Thanks!
[Galaxy S I9000 Android Development] rschenck:
If you flashed the Platypus kernel before even booting up, then at this point you need to run a kernel cleaning script, or, just wipe the damn thing and start again.

Also, when Siky said that /system is wiped when flashing a Nightly, he was referring specifically to the /system directory, which is overwritten with each Nightly install.

Lastly, some people reflash gapps with each nightly, others do not..it is a matter of personal choice.
[Galaxy S I9000 Android Development] burakgon:
Thanks for great info. I will remember all during flash. I wonder new lockscreen style much!

I got a question. When I play with haptic feedback back menu longpress and keyboard settings, lock screen haptic is gone. What I do wrong?
[Galaxy S I9000 Android Development] Zatta:
Thanks Kaik, I was waiting for someone to say this. Look at the emulators in SDK, that its not what we want at all ( but that is ASOP).

Taptalked u see
[Galaxy S I9000 Android Development] format:
Updated to 130. Great.

I'm a fairly new CM7 user and I have to say this is an impressive work.

My battery recharge pattern is now stable and consistent. The phone does easily 24/26h on a normal day use. 3G, Wifi, you name it, ON.

On weekends it could go up to 2 days if I don't bother it much. Of course if keeps everything ON as usual.

On weekdays I stop recharging when I go to bed. During the night the phone spends 8%. The remaing 92% is enough to arrive home around dinner and put it to charge, sometimes still with >30% bat remaining.

I never had this much capacity on my SGS with any ROM.

A quick question to all you CM7 veterans. The shutter sound now has a setting to remove this sound in Cyano settings... but it doesn't work right? I still get shuttet sound. There was already a few nithglies since that setting appeared but the sound remains. Has this been reported? Where can we contribute whit feedback about these small persistent bugs?

Oh and the infamous 2G/3G bug. Boy this is a nasty one, just waiting for some lost soul to install the widget button and ruin your phone. I now know how to edit the database and solve the problem without having to factory reset... but the first time didn't search for a solution.
[Galaxy S I9000 Android Development] alinescoo:
Well yeas, +1 from me... having Data toggle working from notification widgets would make it close to perfection. Ah, also not to forget the 720p video recording...
[Galaxy S I9000 Android Development] melorib:
Lately, last 3 or 4 nightlies, after instalation, when phone reboots, I get an error on ROM manager premium, with force close option... :confused:

With #130 I got it twice... :rolleyes:
[Galaxy S I9000 Android Development] extralife:
just you?

i don't.
[Galaxy S I9000 Android Development] Zatta:
So did i, all normal tricks failed. Only format /datadata fixed that. But last time

I did that I lost my home button so I ended up formatting /data and / system also.

Are you using a custom kernel with new ext4 stuff (fugu, Zach's)?

Taptalked u see
[Galaxy S I9000 Android Development] toddmworth:
Same. I'm about to try 130,we'll see if I also get two. I used to get this in nightlies around 70,but haven't seen it since, until buildbot returned last time.
[Galaxy S I9000 Android Development] toddmworth:
I was using fugu, and thought maybe it was the ext4 thing, but I like a clean install on occasion so instead of formatting, I went a bit further ... But even get it after a clean reflash of JVS stock with repartition - speedmod flash - install nightly - restore apps from titanium ....
[Galaxy S I9000 Android Development] drakenabarion:
Changelog twitter says its added :-) Downloading now!

Sent via my GT-I9000 running CM7 (GB 2.3.5) using XDA premium
[Galaxy S I9000 Android Development] rschenck:
I don't usually go in for the AOK posts, but as there have been some problems reported....

I have 130 running fine, no bootloops or problems, followed my normal update pattern (Enter Recovery, Flash Kernel Cleaner, Flash Nightly, Flash Gapps, Fix Permissions, Sacrifice Goat to Baal, Reboot).

BTW: Ring lockscreen rocks.
[Galaxy S I9000 Android Development] lunasea:
LOST.DIR files

Guys, once in a while I get files inside sdcard LOST.DIR. I know that means file corruption during forced mounts/umounts but I could swear that I always turn off usb storage before disconnecting from PC. And I don't have SOD and forced reboot for ages to.

Does anyone have this issue?

BTW, using stock kernel and latest nightllys.

Thanks.
[Galaxy S I9000 Android Development] hartyshow:
Hello,

I have a similar problem since 2 release !

After downloading new nightly rom from Rom Manager, the GS doesn't boot on Recovery Mode but I have a yellow triangle with a penguin on the screen :confused:

after a Power off, I enter manually in recovery mode and the process of rom install start !
[Galaxy S I9000 Android Development] rschenck:
Unless you get thousands in there, they are no big deal...just delete 'em. They could be from a thousand different things.
[Galaxy S I9000 Android Development] lunasea:
Nop... 3 to 5 files normally.

I do that, but its kinda messy because you never know if you lost a file from SD. I'll trust that if it is common and haven't been addressed, doesn't bring problems.

Thks 4 the reply, cheers.

EDIT: one think I've noted is that usb storage unmounting is way faster than on sammy roms. Hope that's just performance :)
[Galaxy S I9000 Android Development] neoxyrel:
Just flashed 130 and everything is fine and no issues except for the mute camera shutter which is still not working.
[Galaxy S I9000 Android Development] drakenabarion:
It sure does!

I thought it would be more like the ripple lockscreen from the market (based on the description) but ring is definately my new lockscreen! (Anyone else using find that you are bobbing the rings back and forward when bored? :-) )

Sent via my GT-I9000 running CM7 (GB 2.3.5) using XDA premium
[Galaxy S I9000 Android Development] alinescoo:
I have isseues with Galery since one nighly before: I can enter it, sometimes watch pictures but when play a movie I get android.media FC. This als ohappens when I try to crop a image for wallpaper. I tried: clear data, fix permissions, reinstall ne w nightly with wipe dalvik/cache... no luck. It get's really annoying
[Galaxy S I9000 Android Development] extralife:
fc, if you want to edit profiles - settings -

but it's possible to create & edit new one.

#130
[Galaxy S I9000 Android Development] melorib:
Pure CM7... :rolleyes:

This FCs happen right after installation, and dont affect anything else, the phone doesnt even reboot, actually I have not had a forced reboot since 104...
[Galaxy S I9000 Android Development] mobidzid:
Same here!

logcat
[Galaxy S I9000 Android Development] xero2002:
CM7 for the SGS has never been as awesome as it is today. Really appreciate the latest steps in development. :)
[Galaxy S I9000 Android Development] DerTeufel1980:
there seems to be a bug in the "profiles" since #130. In german forum people are reporting fc if you try to edit or change a profile. creating of new profiles is working
[Galaxy S I9000 Android Development] thaBuzzed:
I was initially on 129 and I started getting the odd FC or two with increasing frequency. So I thought I should flash 130 to resolve the problem but I ended up with even more FCs. After a reflash, gapps flash, fixing permissions, cache and dalvik wipe and much crossing fingers I was hitting bootloops. Finally backed out by restoring a backup of buildbot #123 -seems ok so far.

What next from here?:confused:
[Galaxy S I9000 Android Development] guijarrelson:
This release looks pretty! I don't have any FC and from gallery, works fine.

I see some FC when I launch cam apk and then,pulse vol up for 5secs or something like.
[Galaxy S I9000 Android Development] nop56773:
Just to add that I was using pawtip 105 version and updated today to 130. Radio FM was working fine on Friday and is also ok today. That's a change from a few months ago when it didn't work.

Other than that and the time I lost my game's saves, I haven't had any significant issue. Sometimes the browser acts strange, but nothing too serious.

I must say that this CM7 is definitely very fast and, more than that, keeps running very fast over the days, something that Samsung ROMs usually don't.

Edit: I forgot to add that battery is also great and I see no difference from Samsung ROMs.
[Galaxy S I9000 Android Development] lemmy_0:
also using 130

other than the camera shutter sound bug, i think all is well.
[Galaxy S I9000 Android Development] mermigas:
The new "Ring" lockscreen is fantastic !!!

CM Ring Lockscreen Demo

http://www.youtube.com/watch?v=VnQzT9QyJFQ&feature=player_detailpage
[Galaxy S I9000 Android Development] bremkins:
Do you think its ok switching everyday to a most-updated noghtly rom?? Im asking because i believe it will not let the battery to settle down completely, which cause an obvious poor battery life experience. Correct me if im wrong..
[Galaxy S I9000 Android Development] format:
The camera shutter AND the 2G/3G widget switcher....

I think this one is still a dreadfull trap (although there is a solution besides Fact Reset)
[Galaxy S I9000 Android Development] Zatta:
I think you are wrong and that battery calibration is a myth.

Taptalked u see
[Galaxy S I9000 Android Development] :
Where can i find that kernel cleaner script? Thanks!
[Galaxy S I9000 Android Development] wojtaz131:
How fix bootloop on 130?!

When I wipe data/factory reset I lost my apps, games, messages?