yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] glitterballs:
For the moment, the lights.s5pc110.so isn't compatible. It's not an issue with making a compatible kernel.

Pretty sure this is on the issues list.

CyanogenMod settings --> User interface --> Render effect = A couple low power display options. Much easier on the eyes at night.

Also, in the browser menu, check "Invert Color", and instead of black text on white background, it's white text on black. Waaaay less battery use for our screens. AOSP FTW.

Shutdown is our problem, not Aery's. I'm trying to track down what's going on, but I've had logcat running all morning with my phone charging and I haven't had a shutdown. :confused:
[Captivate Android Development] Squeak22:
I didn't try it just plugged into a usb port, only with the wall charger. It may only occur if it's charging from the wall charger.
[Captivate Android Development] glitterballs:
Well, if that's the case, I can suggest a simple work-around in the meantime. :D
[Captivate Android Development] Squeak22:
Indeed. Without the OC/UV kernel I had no issues though, so I'm happy.
[Captivate Android Development] mkoby:
Not sure what's going on here, but when I turn on the Auto-Rotate Screen option in the Settings/Display, it will automatically switch to landscape mode and no amount of flipping seems to flip it back to portrait. If I turn the option off it reverts to portrait mode (but then I can't flip it on it's side and have it rotate correctly)

It's almost like the calibration of my accelerometer is off. Can anyone point me in a direction to attempt to fix this? Of course I didn't have this problem until I flashed Cyanogen and the appropriate kernel.

I doubt this is specifically an issue with the ROM, but can't be sure since I didn't have it before then.
[Captivate Android Development] jwlsinx:
The no-ocuv kernel has fixed some issues I have been having as well -- random freezes while using which keep the screen on, but require a battery pull to fix. I guess my phone just can't handle the oc.

As for questions about battery life - I left it unplugged last night, at 31% battery charge. When I woke up it was turned off. Turned it back on and it was at 4%. The best I ever had with some other roms/kernels was about 7% for the whole night (9 hours).

Still, an excellent rom which can only get better.
[Captivate Android Development] Squeak22:
There are still some things that don't standby properly when the phone sleeps. It will get fixed eventually.
[Captivate Android Development] glitterballs:
Which kernel are you using? I'm definitely not having this problem and I think we would have heard about it by now if others were. It sounds like you haven't flashed one of the kernels I posted.

There were some changes made to improve battery life for the i9000 which I might revert. Battery life is such a hard thing to pin down because I don't use my phone the same way each day.

edit - did you have wifi on? wifi sleep isn't working correctly atm.
[Captivate Android Development] Sebring5:
some minor issues

1-deleted my exchange accoumt from e mail

2-deleted a widget from the screen

3-force closed when fully charged (twice)

4-cannot install launcher.apk

5-had to adjust screen brightness manually (auto not bright enough)
[Captivate Android Development] mkoby:
I flashed the reorient-b2 kernel twice via ClockWork (just to make sure). Kernel version under the About Phone in Settings reads: 2.6.32.9 izwald@beermachine #6.

If that's not the right kernel than something is seriously wrong with my CW install (which is odd because it installed Cyanogen with no issues), and I'll need instructions on how to take the kernel out of the zip file and into something I can flash with Odin.
[Captivate Android Development] Smallsmx3:
Shutdowns after a full charge on beta 2 OC still happening. Going to flash the non OC kernel
[Captivate Android Development] loraque:
Flash the re-oriented kernel glitterballs has in the OP AFTER flashing CM. It will fix it. When I went to beta 2, the same thing happened to me (I flashed the new kernel FIRST, and then CM beta 2... which promptly over-wrote the kernel I flashed. Oops). I just flashed it again and it was resolved.

EDIT- Beermachine #7 is the latest.
[Captivate Android Development] Squeak22:
The kernel name won't change. GB pulls in the changes required to make the buttons/screen work correctly.

It should be #6. I'm running the no-ocuv kernel from yesterday.
[Captivate Android Development] Smallsmx3:
So I disabled OC using the VC app and have had plugged in for thirty minutes and no shutdown....so maybe The issue is in the oc itself.....ill keep trying to reproduce with oc disabled
[Captivate Android Development] Smallsmx3:
Mine says #7
[Captivate Android Development] mkoby:
After reflashing the cm61-b2-sgs-reorient1129-no-ocuv.zip file in clockwork, the issue still exists.
[Captivate Android Development] Squeak22:
Don't flash it in clockwork, just flash it in regular recovery. (either reboot into it or do the 3 button combo)
[Captivate Android Development] enkso:
I have downloaded the voltage control app but cannot get the superuser to open and ask for permissions. This is the same for all other apps like root explorer. Does anyone have any ideas as to why my superuser application is not acting like I'm rooted?
[Captivate Android Development] loraque:
That is a known issue with Beta1 of CM. Beta2 has it resolved.

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

EDIT: I cannot get the voltage control app to retain settings upon reboot, but I see several posts about that in the app thread. Still being worked on.
[Captivate Android Development] glitterballs:
I'm aware there is an sleep death issue with the OC/UV kernels. I don't need everyone to post saying so. It's an issue with, as far as I can tell, every i9000 kernel using this. People report it in raspdeep's thread, people report it in setiron's thread, etc. There are a couple suggestions I can make in the meantime:

1 - Don't use a OC/UV kernel

2 - Don't leave your phone plugged in for hours after it's fully charged

3 - Charge via USB.

#6 and #7 are both the ones from yesterday, one is the OC/UV, one is the no OC-UV. They're both current.

Clearly something went wrong somewhere. I have my suspicions, but I'd suggest rebooting to recovery, then factory wipe & reinstall ROM + kernel. Make sure you know what data will be lost by factory wiping and backup what you need to.

Upgrade to a b2 kernel.
[Captivate Android Development] Smallsmx3:
The 2g/3g toggle spent work right. I can get into 2g but can't reverse without a reboot
[Captivate Android Development] glitterballs:
Known issue. Have a look here for other problems you are likely to experience that are already known:

http://code.google.com/p/samsung-gt-i9000-cyanogenmod/issues/list
[Captivate Android Development] jwlsinx:
Yeah I had wifi on. I'll turn it off tonight and test it again. I agree about how hard it is to test battery life. That's why I like to test it at night. I have the same apps running in the background, and typically get the same amount of email's, so it is a good indicator of battery life. If there are any settings you would like me to test, feel free to PM me and I'll do what I can.
[Captivate Android Development] Smallsmx3:
Thanks for the link....
[Captivate Android Development] NiXXeD:
It seems there is a lot of confusion on how to install this properly for the Captivate. Being that there is no 'official' Captivate thread yet, I figured I'd toss together the proper way to install this. Glitterballs: probably copy/modify this and put it in OP to prevent all the questions.

Needs a proofread/test please!

Note: if this stuff doesn't make sense, you probably shouldn't be doing this beta install yet! Wait for an official CM6.1 Captivate release!

Initial Install:

Read the issues log before installing. We don't want to hear about existing bugs here! (http://code.google.com/p/samsung-gt-i9000-cyanogenmod/issues/list)

Download the following items:

-JK3 Modem (http://xdaforums.com/showpost.php?p=9134289&postcount=1)

-Initial kernel (Latest beta from OP of this thread)

-Captivate Reoriented Kernel (Latest beta from OP of this thread). NOTE: the OC/UV kernel has a "sleep death" issue.

-Latest matching beta to the Captivate kernel from the i9000 CM6.1 thread.

-(optional, recommended) Google apps package from the i9000 CM6.1 thread.

Flash back to stock with one-click Odin.

Using Odin, flash the initial kernel and boot into recovery.

Install JK3 Modem.

Install CM6.1 latest beta zip. This will take a while, be patient!

Install Latest reoriented Captivate kernel.

Install Google Apps package.

Reboot phone

Update from previous CM install:

Reboot to recovery

Install latest CM6.1 Beta zip

Install latest MATCHING reorient Captivate kernel.

Reboot phone

If you have issues with busted apps do a data reset from recovery.

If you are missing google apps here, install that package again.
[Captivate Android Development] glitterballs:
Do you guys want backlights that work now, but you can't control, or backlights that you can control later?
[Captivate Android Development] NiXXeD:
I say ones that work is fine, to start. I won't complain either way =)
[Captivate Android Development] zerojay:
Agreed. Having bln working isn't something that MUST be done now. Just being able to match features with the default Samsung stuff should be more of a priority at this point, I would say.
[Captivate Android Development] jwlsinx:
Good idea. I'll start from stock again tonight (have one app that isn't working). I'd think that the best place to link the modem is http://xdaforums.com/showpost.php?p=9134289&postcount=1
[Captivate Android Development] ice3186:
weird, just strange

So i ran the whole process and I lost all my TB files and everything on my internal sd card was all oddly named. But here is the weird part. Almost, not all, of my apps that i had in TB started auto downloading from the market!!!! Anyone care to explain!?
[Captivate Android Development] NiXXeD:
Thanks, link added and instructions modified slightly (I used Odin for my modem).
[Captivate Android Development] NiXXeD:
Read up on CM! Your internal/external SD cards are mapped differently.

Also the google backup feature actually works on CM (it doesn't on samsung roms). So it's restoring your apps/data for you automatically.
[Captivate Android Development] ademejia:
nightly build is out

Changelog

++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++

REPO

- added btld for bluetooth

- removed iptables from kernel and added iptables kernel modules to /system/lib/modules/2.6.32.9/

- added cifs kernel module to /system/lib/modules/2.6.32.9/

- added tun kernel module to /system/lib/modules/2.6.32.9/

- added aosp dhcpcd

Nightly Build 30-11-2010: http://www.codeworkx.de/download/cya...yS-NIGHTLY.zip

DANGER: VERY EXPERIMENTAL, ONLY FOR REAL DEVELOPERS!!! NO SUPPORT
[Captivate Android Development] jwlsinx:
The zip files posted there can be used with CWM or with Odin (just extract the modem.bin ...).
[Captivate Android Development] votum:
GPS seems touchy reading through the thread, what modem are you guys using that have GPS working?

I can't figure out which modem I have either, I think its JG8 because I remember flashing it during the install process to get 850 working, is there a way to find out? Does CM install a new modem during flash?
[Captivate Android Development] Athailias:
Flashing beta 3 nightly build... where is the glitterballs beta 3 kernel... j/k I know its not done yet. I am flashing the oc/uv kernel over the nightly build. Will see what happens.

Update: GB's beta two kernel works so far. It said welcome to beta 3 when I flashed the update injected into the beta two zip file, but my "about phone" still says beta 2 *shrugs*
[Captivate Android Development] enkso:
I am using JPM is it better to run JK3 or another one? How can I update just the firmware if I'm already on cm6.1 b2
[Captivate Android Development] Squeak22:
Looking over the changes, you flashing the Beta 2 GB kernel probably reverted all the changes made.
[Captivate Android Development] darkamikaze:
mmm mounting issues are poo.. adw restore settings are found in /sdcard/ when /sdcard is /mnt/emmc :(.. gallery is same issue lamee ( I know this is in their google code report page just wanted to vent a little lol)

:x can't wait for moar updates!

and since /sytem is ext4.. what would the procedure be to uninstall? I can't just Odin back to jf6?
[Captivate Android Development] Smallsmx3:
You would revert through Odin...
[Captivate Android Development] darkamikaze:
if anyone finds a working swype :D lemme know!
[Captivate Android Development] glitterballs:
Did you try copying your adw files from your internal to your external? Should still work, I'd think. And, per your request (ok, not really your request, I wanted them too), I have the backlights working, I'd just like to figure out why the app doesn't recognize the liblights as being compatible (and be able to turn them off and on, etc).

Odin one click back to stock works fine. I did it yesterday to get JPM modem working again on CM6.1.
[Captivate Android Development] Smallsmx3:
GB you went back to jpm modem after using jk3? Any reason y? I know in aerys post he says to use jpm but I've been rocking jk3. Should I switch?
[Captivate Android Development] Athailias:
I too have been using jk3 for several days (since the first ports over to captivate actually) now with cm 6.1 with no problems.
[Captivate Android Development] mkoby:
Just an update. I ended up messing up my phone trying different things in an attempt to fix this issue of landscape, it's not the kernel or rom, because when I did an Odin Master Clear, the issue still existed in the stock ROM. So it's something I did (maybe when I had another ROM installed).
[Captivate Android Development] ademejia:
does bluetooth work on beta2 or the nightly build, cant get my bluetooth headset to work.
[Captivate Android Development] ademejia:
found this on the cyanogenmod forums it seems this nightly build has a date 12/1

Changelog

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

REPO

- removed iptables from kernel and added iptables kernel modules to /system/lib/modules/2.6.32.9/

- added cifs.ko kernel module to /system/lib/modules/2.6.32.9/

- added tun.ko kernel module to /system/lib/modules/2.6.32.9/

- added aosp dhcpcd

- added wifi scan fix

- bluetooth WITH_A2DP := true

- wifi ap fix from GuiPer at netd

- added mainline changes

- added brcm_patchram_plus at init.rc for bluetooth

- some additional changes at init.rc

NIGHTLY BUILD

Build date: 01-12-2010

Download: http://www.codeworkx...xyS-NIGHTLY.zip (su is missing: adb push su and set permissions 06755)

DANGER: VERY EXPERIMENTAL, ONLY FOR REAL DEVELOPERS!!! NO SUPPORT

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
[Captivate Android Development] darkamikaze:
can anyone compare if the low volume output could be attributed to the modem (JK3 or JPM)?

I'm using JK3 and it's quite low on speaker..

I saw that it was an issue in CM .. but maybe it could just be the modem? I dunno I'm not sure :x

and thx gb for quick replies :o.. I found an old external SD hanging out somewhere and did just that haha
[Captivate Android Development] Athailias:
flash a 2.2 rom (cog or stock jj4 leak or ji6) and recalibrate your sensor under menu/settings/display. I think that will fix it.
[Captivate Android Development] mkoby:
No need to go through that much trouble, The instructions in this post seem to have fixed the issue.
[Captivate Android Development] tjsooley:
does anybody else see that the camera doesn't take pics at 5 mp and sound recording doesn't work.
[Captivate Android Development] BL4zD:
when you rebuild this kernel will you please change the value of SD_EXT_DIRECTORY (in init.rc) from sd-ext to sdcard?

or anywhere...maybe /mnt/emmc but I think that sdcard is now going to be the official external sdcard
[Captivate Android Development] Squeak22:
That's the way it is already.

internal SD = /mnt/emmc

external SD = /mnt/sdcard

If you aren't seeing this here then something went wrong when you flashed.
[Captivate Android Development] darkamikaze:
haha yea its only 3MP for me and it's 24/7 black and white
[Captivate Android Development] tjsooley:
WE may have a fm radio when everything is done.

you run the fm radio with a set in and everything works but sound.

i checked the bug log and its a known problem with the sound stack.
[Captivate Android Development] Smallsmx3:
I thought the hardware for a radio in the cappy was not present
[Captivate Android Development] tjsooley:
Then one would think with all the api's and **** you would get some kind of hardware error.

i dont i have the same problem that other gti9000 users do.
[Captivate Android Development] ademejia:
update: i just installed the latest nightly build dated 12/1 from the cyanogenmod forum and bluetooth does work but when i flashed the 6.1 beta 2 kernel for captivate bluetooth no longer works. so im guess we need a new kernel again and also there is no root acess.
[Captivate Android Development] NiXXeD:
Most of the big issues they're fixing are in the kernel, so we can't participate in the nightlies unless we also have nightly compiles.

The SU bug is mentioned in the nightly changelog. =(
[Captivate Android Development] spiritssight:
CM on Cappy!!!

Hello,

I am wondering could someone please write a simple order of doing things to get this to work on the cappy? Also could you put a link next to each item so that its easer to know which file to download and do what with. I have read this thread and a number of the other threads that are link to this one and have got a little confused as one of the threads talk about different device and files that I guess don't belong to the cappy?

Thanks again!!!

Christopher
[Captivate Android Development] plasticdarlow:
Thanks for all the hard work/effort put into bringing this to us. Much appreciated.....

I've been on this for a couple days, and love where this is going....

For those interested I've put together a quick theme in the Captivate section.... Enjoy...
[Captivate Android Development] Squeak22:
Are you serious? There's several sets of step by step instruction lists in this thread. With links and everything.

OP

or

http://xdaforums.com/showpost.php?p=9510708&postcount=315
[Captivate Android Development] spiritssight:
Hello

I have read most of this thread, I missed a few pages it seems sorry!

OK, when doing the kernel which feild should I use in odin and also which feild for the modem.bin?

I have finished one-clicking back to stock

Christopher
[Captivate Android Development] ademejia:
put the kernel in the pda slot

put the modem in the phone slot
[Captivate Android Development] glitterballs:
No. I've always kept an eye on my battery and JK3 seems to suck up more than I'm used to, so I flashed back to see if there was much of a difference, and if not, try to get a logcat of what's going on. Short version of the story, there's effectively no difference in battery use.

What does that last line say again?

Stuff like this is exactly why I didn't write out a step by step guide.

All that aside:

Yes, I'm aware there is a new build out. But, partly out of respect for codeworkx, partly because it just makes sense, I'm not going to release a new kernel every single time there is a change in the code.

Ok, so, like I've mentioned, I do have BLN working, but at this point, neither neldar (BLN dev, go buy his app btw, it's hella cheap, like $.67 or something, he deseves it) nor myself know why the app doesn't recognize the liblights file, so at this point, there's no way to control them, ie turn them on or off. So...if BLN is that important to anyone, I can post both OC/UV and non-OC/UV kernels with BLN working.

Finally, I think I have a solid workaround to sleep death while charging with the OC/UV kernels which several users are currently testing. Check back later. (I don't want to post that I have a solution and then have to come back and edit that I am fail :) )
[Captivate Android Development] BL4zD:
No, this isn't anything to do with my flash. It's coded into init.rc and needs to be fixed since we can't change the boot image.

cat /init.rc | grep SD

or

echo $SD_EXT_DIRECTORY

It needs to be changed in init.rc to "" [blank] so we can change it in /system in userinit. It's pointless the way it is now because we can't put any scripts in sd_ext.

Personally, I think you should have checked this yourself before "correcting" me.

@glitterballs

I can test. I don't use my phone for an alarm and have no where to be in the mornings anyway :)
[Captivate Android Development] PuffinNugz:
If you read the thread on the i9000 board, you would see why the two cards are reversed. The internal card is something that samsung basically hacked in and CM is not set up to see it that way.

So, until something is resolved by the CM team, be happy that they both just work.

if that's not what you are talking about, disregard.
[Captivate Android Development] BL4zD:
I'm not talking about the two memory cards.

If you look in the root of your phone, you'll notice a directory called sd_ext. That's where our scripts are hard-coded to be read from. But since it's part of the boot image, it's not writeable and is clean upon re-booting.

We (users) can't change the location of sd_ext because init.rc (where it's coded) is also part of the boot image. Any changes to init.rc are restored to the image upon reboot. Someone building the image can do one of two things: either code it to look somewhere we can write to or leave it blank and allow users to define it themselves in userinit (my preferred method because some people will want their scripts on their internal card and others on their external card and perhaps some people who want it in their /system, etc.)
[Captivate Android Development] PuffinNugz:
Right on. Before your edit I was still confused as to what you were talking about. Is that something to be fixed in kernal then? Or the rom?
[Captivate Android Development] BL4zD:
It's not really something that needs to be "fixed" in either the ROM or the kernel in the sense I think you're thinking about the problem. All that needs to be done by whomever is building the kernel is edit init.rc before making initramfs.
[Captivate Android Development] jwlsinx:
Tried it again last night, started at 94%, woke up it was at 52% (with wifi turned off). There are definitely some other battery bugs. Using the JK3 modem.
[Captivate Android Development] jwlsinx:
Can you control it through advanced recovery options?
[Captivate Android Development] spiritssight:
SD Card not Mounted

Hello All,

I have installed and am using very successfully CM 6.1 b2 and I am loving the speed and smoothness, I don't think I ever had this with any rom I have used, it boots faster and overall is great.

I do wonder if this is a bug that has been overseen or is on the know list, I did not see it in the list of know bugs.

I have tryed to open ROM manager and install the latest CWM and its saying can not install to SD Card as its not mounted, I also get this with the TTS installing its data, and also under SD Card & Phone Storage it only shows one aspect and the other one.

Hope this is helpful to the devs, keep up the great work!

Christopher
[Captivate Android Development] spiritssight:
USB Storage - Ubuntu

Hello Devs,

I also did not see this in the know list of bugs and just wanted to inform that when connecting the USB cable to the phone while connected to Ubuntu computer system its not showing up on the phone as being connected and able to copy/move/etc files on the devices internal SD Card which makes it impossible to say install apk that are on the computer thats needs to be moved to the phone.

Look forward to the next update :-) keep up the great work!!!

Christopher
[Captivate Android Development] Ranatsu:
Where on the phone are the cyanogen mod wallpapers stored? Id like to extract the pacman eating the apples
[Captivate Android Development] cckidquick:
I was having massive battery drain as well so I flashed the jpm modem...problem fixed...a few hours later I reflashed the jk3 modem and have had better battery life...may want to give it a try.