yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] nkrick:
Atinm,

I noticed updates that will be in nightly 73 for "htc offmode charge." Do you know if there is any chance that some of that will be useful in enabling Samsung LPM charging? I know HTC hardware and Samsung hardware is very different, but I have no idea how similar or different HTC's offmode charging is the Samsungs LPM charging. Is LPM still an area that there is no chance to enable until Samsung releases some source code (or Google releases it for the NS)?
[Captivate Android Development] nkrick:
IF there even are problems in the current code base. All of the recent complaints have been from people using Glitch. I have not seen any of these issues reported by people using the team hacksung kernel or The Escapit's kernel. That alone should be a huge warning sign saying that the problem is in the Glitch kernel, NOT in CM7 or the team hacksung kernel.
[Captivate Android Development] shaolin95:
And the fact that many of use run Glitch and have no problem proves you are WRONG so enough already. Yes it is not for Glitch support, there is a thread for that but enough of your ranting.
[Captivate Android Development] nkrick:
How do you figure that various assorted inconsistent problems that are only being reported by people using Glitch is not a problem with the Glitch kernel? Just because the issue is not affecting everyone using Glitch does not mean the problem is not with Glitch. You have been reporting issues within the last few pages.

Adding 3rd party kernels adds another variable to the mix, especially when the 3rd party kernels are compiled against an older code base the what is current for the latest nightly. Combining the latest nightly with a kernel compiled against anything except for the latest nightly is a bad idea IMO. No one should be surprised when there are inconsistent issues and those problems should be relegated to the thread for that 3rd party kernel.

This thread is for team hacksung's CM7 support/bugs. If you are not running team hacksungs code (kernel) than you should not be reporting problems here until you have confirmed that the problem also exists in team hacksungs code/kernel. Period.

It would not be necessary for some of us to rant about this if those of you running 3rd party kernels would follow the request of Atinm (without whom CM7 for Captivate would not exist in its current form) and post your problems in the thread for your current 3rd party kernel. As long as you people can't follow simple instructions, someone will have to rant at you. If you don't like the rant, don't read it and don't post your glitched problems on the wrong thread.
[Captivate Android Development] nkrick:
To help you understand what you are doing, using a 3rd party kernel compiled against an old code base is like installing Ubuntu 10.10, then using dd to replace the kernel with a kernel from Ubuntu 10.04. Or installing Windows 7 and then booting from a bootable CD and replacing the Windows 7 kernel with the Windows Vista kernel. You should NOT expect this to work.

If you like a 3rd party kernel, you need to know what date it was compiled (against what code base) and then run the nightly CM7 from that date until the 3rd party kernel is recompiled against a newer nightly.
[Captivate Android Development] skeepon:
hmm. every time i flash a nightly (65-71), after my phone boots up, everything is really laggy. Even after a few reboots, its still the same. the only way this gets fixed is if i flash glitch or another kernel. But i would like to use the stock kernel. can anyone help me out please?
[Captivate Android Development] melbourne408:
If I had a back I'd lay down.

If I had a book I'd read it.

If I had a knife I'd butter toast.

On a good morning I usually like to read and chill, eat some toast and say man this is good! Not one those mornings, I'm off to read hop on pop, then some linus pauling.

Sent From My Swaggin 1.6 Son of Glitch
[Captivate Android Development] shaolin95:
I already said I agree that Glitch issues or questions should be in that thread but trust me it is not ANY MORE fun to keep reading your posts *****ing about the same thing over and over....both are quite annoying...at least the kernel questions have some purpose :rolleyes:

You made your point already...I dont think we need to read the same thing 100 times...so to reiterate..yes I agree...each section and thread is there for a purpose.

Regards
[Captivate Android Development] Haloruler64:
I really didn't want to flash any other kernel, but the colors made me. Everything is pink. All grays/blacks are reddish pink tinted. I tried getting used to it, but I couldn't stand it. The colors in Escapists Kernel are great. Any way that can be integrated into stock CM kernel?
[Captivate Android Development] z28james:
If I remember correctly, I believe the reason to not include voodoo color was because it is available through other kernels. I'm glad that was broken for voodoo sound, however. :cool:
[Captivate Android Development] nkrick:
And you have made your point. You should take your own advice because reading your posts is no more fun than reading mine. At least my posts are making a generally valid point. The point of you posts is to tell me to shut up.
[Captivate Android Development] melbourne408:
End it here please, anything can fall under equivocation if the mind isn't seeing the at hand. Here, maybe sightly misplaced but perception can dull with a closed mindset, taking in general terms. Shaolin and his contributions should bear some type of respect, time and experience doesn't easily evoke the animalistic part of our being, humane always my experience of it. Lets have some fun and put our game faces on :D

Sent From My Swaggin 1.6 Son of Glitch
[Captivate Android Development] sixstringsg:
You do know that not each nightly has a new kernel, right? CMSGS uses a prebuilt kernel that is updated when necessary.
[Captivate Android Development] nkrick:
I am aware that they started using a pre-built kernel a while ago, but since there is no information in the change logs indicating when new kernels are compiled, at best it is a gamble to use a 3rd party kernel that almost surely has not been recompiled within the last 24 hours (unless the 3rd party kernel specifically says it has been).
[Captivate Android Development] Malorkus:
I don't mind installing a new music app, but is there a way to make CM7's "integration" features work with the new music app? i.e. right now the CM7 music lockscreen controls don't work with the new Google Music app. Is there a way to make them work together?
[Captivate Android Development] Aztecbandit:
I think if u only use that music app for a while it'll work. I am pretty sure I got it to work. I know for sure UberMusic worked
[Captivate Android Development] FireRaider:
Bluetooth still not working with cm7 kernel on todays nightly. Rolling back to #66 again.

more information:

From the last three releases I cannot get a working bluetooth with the stock kernel.

If I attempt to tun on the bluetooth it changes color (fades) and then says turning on, but never turns on. If I roll back to #66 it works fine. Flash anything in the 70's it stops working. Flash back to #66 or even the RC1 it works fine again. This is all flashed from recovery so I am not restoring any apps or anything, just flashing the zip.

I have done this several times and the newer releases cause my bluetooth to fail each time.

Not complaining, I get by just fine with #66, just posting in case someone else running the stock kernel, has the same issue.
[Captivate Android Development] jwood55812:
hey guys, came back from the Samsung Gingerbread ROM's, and still not feeling the battery life(on the samsung roms) I used to get. Tried flashing at 100%, recalibrating etc, but not much luck, still about 13-15hours and 25% left with minimal use during the day. My cell standby is the highest process and 0% without signal, second is display with 30m2s, so I dont get it. Any recommendations on kernels or other suggestions?
[Captivate Android Development] halfsoul:
I know this is a late reply, but as a new CM7 user I struggled with this today. Here is what I've found:

1. /datadata contains app data

2. You can see how much data each app uses in Manage applications

3. You can clear data for an individual app with clear data

4. Moving the app to sd card does not reduce /datadata size

5. As mentioned previously, you can check the /datadata size with "df -h" in a shell

6. You can quickly see which apps are hogging the most space with "du -sk /datadata/* | sort -rn | head" in a shell

Why I didn't need to figure this out on other ROMs I don't fully understand. Anyone please correct/supplement as appropriate.
[Captivate Android Development] yguns76:
I just installed the latest nightly and the lockscreen works with Google music.
[Captivate Android Development] yguns76:
Is it possible to get the TV out feature for the Samsung Captivate with cyanogen?
[Captivate Android Development] RockRatt:
Not yet, but I know I have seen in the past that the devs would get to it at some point.

Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
[Captivate Android Development] skatcat31:
So been running 71, 27 hours of use, 8 hours of screen time. I'm going to do a movie stream test soon, do I might be back to report later

Sent from something from somewhere
[Captivate Android Development] goabunny:
I am wondering if anybody else experienced this issue with CM7.

After I watch a long streaming movie (about an hour) on my phone using flash player in stock browser, I lose the ability to charge my phone. I have to pull the battery and put it back in order to charge it again. This happened even with shorter videos as well in flash player.
[Captivate Android Development] Smasher816:
When watching videos my phone gets really hot.

It wont charge above I believe 50C.

That may be your problem. Pulling it to let it cool down.
[Captivate Android Development] EnemyOfGlaDOS:
Yup :)
[Captivate Android Development] melbourne408:
Haha my homies had a party and wanted to better the mood with a movie as duhcked up our minds could contemplate, my homie used his cappy; my spare masterpiece. Had it hooked to a ps3 and mounted the internal storage, put up a hotspot and was attempting to...(idk why,) normally connect it as a psp through bluetooth. Went to icefilms or w/e the sites called and downloaded a serbian film (srpski film for the directors cut.) After that was done, the 700mb file copied to the ps3 he had the same issue haha

Sent From My Swaggin 1.6 Son of Glitch
[Captivate Android Development] :
I can also report this problem. I've had it on 72. the gmail app also will not send an attachment. It says it does but when the email is reopened its not there and the recipient doesn't get it either.
[Captivate Android Development] Johnnie5000:
Thought it was just me there for a bit. The length of the video doesn't really matter on my end though. 5-10 minutes of youtube and it won't charge until I pull the battery
[Captivate Android Development] Mortem Tuam:
nice ROM guys...thanks
[Captivate Android Development] EnemyOfGlaDOS:
Lol :D.. that's awesome!
[Captivate Android Development] XsceneXhippieX:
Running nightly #71, bluetooth works flawlessly, sent multiple files from my phone to my girls with no issues or corruption in the process, maybe bluetooth issues are from a corrupt download of the rom somehow?

Sent from cyanogen mod 7
[Captivate Android Development] littlewierdo:
Regarding bluetooth, the last build that worked was 68 (for me anyways).

Now, it is possible that removing all bluetooth pairs while on 68, then flashing upwards may work (or even doing a factory reset while on 68 or even possible, on a higher build) might work, my phone is currently on its way to samsung for repairs for the second time so I cant test this. And most likely, by the time I get it back, the CM peeps will have fixed all of these issues anyway.

As a side note, when I was on 68, I flashed up to 69, noticed bluetooth was not working and reverted back to 68 and voice calls mysteriously started working (they never have worked correctly in the past for me).

Regarding talk of other kernels with CM. A brief mention of another kernel in my opinion is fine but what often tends to happen is, people start to use the wrong forum thread to talk about problems they are having with said kernel or external app (one not included with the rom) and instead of the actual topic the thread was created for being discussed, a thread gets derailed.

In general, this does not really help the person(s) that need to know about said problems the most, the developer (unless the developer is following both their own thread and the thread where the discussion is occurring).

Then, when someone mentions that a thread is getting out of hand because things are being discussed that are off topic, people get defensive (and often times, over-react).

We all have our reasons for running modifications on our phone, some of us like to modify the modifications (MIUI over the top of CM, Glitch kernel over CM, etc.). We are all entitled to do whatever we want.

But, this is not the place to justify why we are using a modification of CM, nor is this the place to discuss any modification of CM we are using unless (in my opinion) it addresses a specific problem someone else is having and is being mentioned as a possible solution to said problem.

We are all human beings here, lets try to be a bit more respectful of each other...

KK, so, hopefully we are returning to our regularly scheduled program, yea?
[Captivate Android Development] melbourne408:
Loving the new nightly, I like turtwlrs!

Sent From My Swaggin 1.6 Son of Glitch
[Captivate Android Development] FireRaider:
Assuming you are running the stock kernel (your signature would suggest stock), do you flash from recovery or from CWM and then restore all your apps?

I havent tried flashing right from CWM yet. I know its not that hard to restore the few apps I have, but wow, I sure like the 10 second update and the being up and running again that you get with recovery.
[Captivate Android Development] FireRaider:
I jumped from #66 to #69 so thats why I always revert back to #66. I havent done a factory reset or cleared pairings yet. I tend to think its in the update since it works fine on a #66 recovery flash every time after failing to work with the higher numbered nightlies.

Add to that the fact that bluetooth works with a different kernel that hasnt been updated in a while and it leads me to think something changed in CM7.

I would run the other kernel but I started to get black screen lockups and as someone alse stated, mixing and matching and then complaining helps nobody.

So I am back to stock #66 and then flashing nightlies to see if its fixed yet.
[Captivate Android Development] cbasse:
??? turtwlrs ??? please explain... :confused:
[Captivate Android Development] XsceneXhippieX:
I updated from 59 to 71 only wiping dalvik, keeping my bluetooth pairings in place, nothing special, standard flash, and my bluetooth works flawlessly... Not seeing what is going on for every body, but I can report fully functional 100% working bluetooth for sending files, phone calls, music playback on the radio in my car, everything works here
[Captivate Android Development] bugity:
I'd guess "I Like Turtles." Haha
[Captivate Android Development] melbourne408:
Hahaha you got it there :D

Sent From My Swaggin 1.6 Son of Glitch
[Captivate Android Development] andi br:
The Quick Unlock is not working for me , by the way never seen it worked since the first CM7 I used.

(Cm7 Settings > LockScreen > Unlock Options > Quick Unlock.)

Still have to press 'OK' to unlock.

Thanks for the excelent rom!
[Captivate Android Development] dabels1961:
Works fine for me, been running CM7 since the 20's and never had a problem with it.
[Captivate Android Development] Jemack:
It works for me. I use pin based code. Haven't tried it with pattern.
[Captivate Android Development] andi br:
Oh I just noticed what is not working is the screen to unlock the SIM card.

Think the Quick Unlock doesn't work with that.

Thanks!
[Captivate Android Development] prayii:
Thread title needs to be updated. [GRJ22] -> [GRJ90]
[Captivate Android Development] nkrick:
I have used a BT handsfree with CM since the first public CM build that team hacksung released. The only issue I have had with bluetooth was that when updating to nightly 69 (which included some BT fixes), I had to clear my handsfree pairing info from CM. I also cleared the pairing from my handsfree, but I am not sure if that was strictly required.

The change in nightly 69 affected the MAC address for the BT network adapter in the phone. For those people reporting BT issues, have you tried clearing the pairing information on both the phone and the other BT device? It is quite possible that the pairing is failing because the other BT device has a bad information for the BT MAC address of your phone and until you clear that info you could have problems. For a large part, whether or not you would need to clear the pairing information for the other device depends on the other device itself and how many concurrent pairs it can support.
[Captivate Android Development] FireRaider:
My issue has been that it wont even turn on the bluetooth. The box fades like it is trying to do something but it never turns on. I am going to try your suggestion though. I will clear out the pairings, reboot, flash, reboot again and report back.

Edit:

Didn't work. Flashed to #73 from #66. As soon as I tried to turn on the Bluetooth the box showed a checkmark briefly and then the phone crashed and rebooted itself. I let it do its thing and then tried to turn on bluetooth again. The box fades and says turning on bluetooth but nothing ever happens.

The odd thing is that as soon as I flash back to #66 everything works fine again.

I can try a factory reset next I guess. I hate reinstalling my apps and passwords though. I know, I know, its not that hard. I will try it this afternoon when i get time.

I guess after that its flash all the way back to 2.2 and start over completely. If that doesnt fix it i will just wait until someone wiser than me figures it out.

Edit again:

I'll be damned, the factory reset seems to have fixed it (the one in recovery with clear all data). I will give it a while to be sure but I have the Bluetooth on right now. Now i just have to reinstall all my apps and hope I can remember the passwords to such important apps as Opentable and Urban Spoon. :-)
[Captivate Android Development] thesuffering:
would i be correct in assuming i can use the glitch kernel with nightlies?
[Captivate Android Development] nkrick:
Wrong thread. Try asking over in the Glitch thread.
[Captivate Android Development] melbourne408:
Yes, if you want to look into that head over there :)

(edit-I must insist tho, read further into the op and what is going on,best wishes.)

Sent From My Swaggin 1.6 Son of Glitch
[Captivate Android Development] XsceneXhippieX:
Well, your "sent from" tag at the end of this post is kinda explanation enough for his question isnt it? i would have just said yes... and for any further info to look to the kernel's respective thread :D i love glitch on cm7 though
[Captivate Android Development] nkrick:
Factory reset was going to be my final suggestion. I am glad it worked, but it makes me wonder what was being stored where that was causing BT to not work right.

I use TiBU to backup and restore only app data from specific apps that I want to keep things such as save game info or account/password info. It seems to work fine as long as I don't restore entire apps to CM7 with TiBU.
[Captivate Android Development] hernan078:
hi im using cm7 since yesterday, i came back from miui and now my time is being displayed incorrectly, i set up my phone with the current hour (6:44pm here) and when i send a text message the message said that it was sent at 10:00pm, i have tried to change the time but it continues to display it wrongfully.
[Captivate Android Development] melbourne408:
HAHA :p

True true, is a good day today and I actually slept hahaha, thought i'd guide and not stir up anything with one stone lol :D
[Captivate Android Development] gabby131:
if another service app wont hurt you, install SMS time fix from Market. i have the same issue in my location on every smartphone i use,
[Captivate Android Development] hernan078:
but this problem persist in my twitter app, i use twicca and i cant use it if i put the right hour, i have to set my phone 4 hours in advance for twicca to work, do you know any other solution?

edit: i also use text plus app and the time is not synced with the time the phone has for example, i send a message and it says i sent 4 hours in advance (the hour here is 10:56 pm and it says i sent it at 2:56 am of august 2) please help!
[Captivate Android Development] SweetwaterBurns:
Have you tried setting the time correctly and letting it sit for four hours, maybe overnight? I've not had it happen on my phone but some computer programs won't let you modify data if it perceives it as having been created or modified in the future. Not sure if that's the case here, but might be worth trying.
[Captivate Android Development] jel7:
Hey guys, I was searching but couldn't find a direct answer.

If I am on CM7 and need to return to stock, for warranty purposes, can I just load up odin3 regularly and just do it like we did when on 2.2 roms? Or do we have to do something different?

Thanks :)
[Captivate Android Development] melbourne408:
Just like how you said it, no bad bootloaders here :)

Sent From My Swaggin 1.6 Son Of A Glitch
[Captivate Android Development] Haloruler64:
Make sure repartition is checked. If it's One Click, then that'll work fine.
[Captivate Android Development] nkrick:
nightly 75

Looks like nightly 75 has some important updates for us. There are some orientation sensor fixes for all the Galaxy S devices that includes sensor usage tracking. There are also some Captivate specific updates to the kernel and several binary modules: bcm4329.ko (wifi and bt chip), cifs.ko, fuse.ko, and tun.ko.

Before anyone asks, 3rd party kernels are not going to work properly with this until after they are updated. They may "work," but they definitely won't see all the benefits as this update includes a newly compiled kernel.
[Captivate Android Development] shaolin95:
Thanks for the clarification.

I always wonder what changes do require a new kernel update as well. :)
[Captivate Android Development] Kaik541:
the fuse.ko is the only new module (and not even used by default, only if someone actively wants to use it). every nightly includes those other modules all the time, they are only ever rebuilt when a kernel is rebuilt (which only happens every once a while). it was only rebuilt last night for the sdhci driver a few defconfig changes. third party kernels will still work just as well as most of them already had the sdhci driver included (in fact, we actually pulled that commit from the FuguMod kernel). The orientation sensor fix is in userland and thus, not affected by kernels.

I don't support the use of third party kernels, but please, do not spread misinformation. if you don't know what you're talking about, please don't try to add to the conversation just to appear knowledgeable.
[Captivate Android Development] shaolin95:
Thanks bro! :-)
[Captivate Android Development] KohjiNagata:
When did this thread get so hostile?

I think all posters should just have a battle royal and get it over with
[Captivate Android Development] melbourne408:
Ah, this some good coffee today!

Thanks :)

Sent From My Swaggin 1.6 Son Of A Glitch
[Captivate Android Development] nkrick:
In this case, the biggest clue was the change log showing that a new "kernel" file was included: http://review.cyanogenmod.com/#change,7120 ;)

While only the experts can tell us exactly what the kernel updates were and whether there is an impact on 3rd party kernels, it is at least a place to look and know when the team hacksung kernel in the nightly has been updated.

While overall I like the nightly builds, I do miss the more "human readable" change logs that used to be posted before the build bots took over.