yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] koflem:
It has not been resolved, and is not a bug.

Edit: looks like you've asked that questions in other threads too... Oh well... here we go:

It is not a bug. The SD Card is simply mounted in /emmc instead of /sdcard/external_sd.

Mounting it there would be technically impossible, and only samsung does that. Most if not all apps should be able to work with the external SD data on /emmc, else they're just badly coded, and that's not the cm7 devs' fault.

You will still be able to use the external SD normally, it's just not at the same place.
[Galaxy S I9000 Android Development] claudio8:
thanks!

you're right, I posted in another thread, but there are too many threads with the same arguments!

I'll be more careful.thks
[Galaxy S I9000 Android Development] Aqua1ung:
Here's one issue on nightly #46: phone seems to be taking a helluva long time to switch from HSPA to WiFi when awaken from sleep. Sometime it doesn't even switch at all. Anyone?
[Galaxy S I9000 Android Development] FadeFx:
It is suggested to set wifi sleep policy to never

----------------------------------------

tapatalked
[Galaxy S I9000 Android Development] siky_dude:
what?..a next rc?...that will be a long long long long time to wait...

and codework already said that not sure that there will be one :)
[Galaxy S I9000 Android Development] Daneshm90:
Woot, in app screenshot capability just got merged :)
[Galaxy S I9000 Android Development] xero2002:
Looking forward to build 48!
[Galaxy S I9000 Android Development] atinm:
Well, not all of CM is Vibrant specific. So even if I don't do anything, the rest of the CM that works on all of CyanogenMod is still hard at work and so new fixes do come in. Check the changelogs to see if they matter to you.
[Galaxy S I9000 Android Development] atinm:
Can't - that wouldn't be "standard" and that code is standard across the phones. Need it to just work in the kernel. Maybe Glitch's latest fixes it. If you guys notice a dropoff in the complaints about touchkey freezes, let me know so I can go take a look at the code.
[Galaxy S I9000 Android Development] atinm:
No. The two are unrelated - different drivers.
[Galaxy S I9000 Android Development] atinm:
It's not a bug - Samsung's implementation is the bug in that they're the only ones who do it that way. Forget that you had a Samsung ROM before, you are not on a Samsung phone anymore when you are running CM7.
[Galaxy S I9000 Android Development] siky_dude:
atinm...will sgs 2 have the same ril as the sgs ?...cuz its kinda "****y"..cuz of the battery drain i mean...signal wise and all of that...perfect :)
[Galaxy S I9000 Android Development] claudio8:
Juwe RAM Script

what is this??

thanks!!
[Galaxy S I9000 Android Development] siky_dude:
Its nothing...cm7 doesn't need this...
[Galaxy S I9000 Android Development] Rat2000:
I've been reading a little back something about the sd card fix.

We can use gingerbread bootloaders now and stil have a working sd card? or was he talking about something else?
[Galaxy S I9000 Android Development] atinm:
No, different. And I am running it, and no drain (and I mean no more than stock that I can tell).
[Galaxy S I9000 Android Development] atinm:
Something else.
[Galaxy S I9000 Android Development] tjpthomas:
Does anyone have problems with the mobile AP?? My computer sees the AP and tries to connect - but it does not get an ip... Am on #46
[Galaxy S I9000 Android Development] Vogie:
I changed DPI to 200 and everything is ok

Just Dial pad and keyboard are small.

Any idea?

Sent from GT-I9000 CM7 #46
[Galaxy S I9000 Android Development] J_Force:
:confused: HELP! What just happened to my galaxy s? I was so happy on #19 but just needed to get the newest cm ;). Now I am experiencing a heavy drain of the battery so I've looked in CPU Spy and found that it is running on 800 Mhz for 61% of the time (22:25:23), and not goïng into Deep Sleep. On #19 it was in deep sleep most of the time and when not it was running on 1000 Mhz. Did I do something terribly wrong? Is it a known bug? Really need help here guys, girls, devs, anybody!?!?
[Galaxy S I9000 Android Development] Herman76:
Have you tried wiping the caches?
[Galaxy S I9000 Android Development] J_Force:
I did a fresh install by going back to JPU, formatted en cleaned everything then flashed the cm-rom. Should I clean anything again?
[Galaxy S I9000 Android Development] chrome6boy:
I had the same problem around #27. I used a task killed because I figured it was a rogue program preventing the phone from going into deep sleep and the problem disappeared. But the problem seemed to go away by itself after a few reboots and now I don't have this problem even without a task killer. I'm on #45.
[Galaxy S I9000 Android Development] oaia:
RAM optimization, free memory, multitask ... you don't have to use Task Killer again ;)
[Galaxy S I9000 Android Development] oaia:
You should not use it !!
[Galaxy S I9000 Android Development] melorib:
The only thing I know for sure is that wifi reception varies when I change modem, some more than others, and that many people report this... :rolleyes:

Other than that, I have no idea how it works... :o
[Galaxy S I9000 Android Development] jaikat:
unable to change modem

hi guys,

i'm on nightly #46, i'm trying to change the modem, under menu/settings/about-phone my baseband says its xxjvk, i tried flashing through recovery, i got the modems from a thread in the captivate forum, naturally i flashed the cw3 versions, they flash alright, but the baseband in the phone's settings stay the same (jvk) no matter which modem i flash..

can anyone comment on this?
[Galaxy S I9000 Android Development] scottietohottie:
First off, are you on froyo bootloaders? If not our you don't know what I mean. Back to the instructions.

If you are there was a known bug that caused android os to run high. I heave been searching to no avail to find if this is sorted. I have seen it pop up recently, so I guess its still around. Reboots generally help. I am on an sgs and found that the glitch kernel helped new solve it. Saying that I've been on it 2 days no 800 mhz issue.

Any one have more info gladly received :).
[Galaxy S I9000 Android Development] hensk:
I`m still on 45 build,behave exelent

battery after first day also awesome

not having any problems

wait to flash new 48 build with camera touch foцus
[Galaxy S I9000 Android Development] J_Force:
YES I am on froyo bootloaders (noticed I wrote I started off by flashing JPU ;)). I did a search on 800 mhz but did not found anything to solve it. Rebooted my phone twice and now it goes into deep sleep and yes android OS was running high (also my navigation software was running high but I didn't use it recently so that was strange too). You say glitch kernel is the way to go? Can I flash that over the latest nightly? Because it is based on a date before the RC1 and newer nightlies.

edit: when I look at battery use right now I see that "display" is 33%, "mobile maps" (the navigationsoftware that I did not start since the reboot :S) is 22% (wtf!? the app did not even run since reboot) en Android OS is 20% (still high?). Some advise please...should I do something about the navisoft? Is the percentage for OS still to high? Should I switch to glitch kernel?
[Galaxy S I9000 Android Development] Bork84:
i dont think those modems are for CM7...

check this link and flash a modem from there.. it will work

http://codeworkx.de/download/cyanogenmod/
[Galaxy S I9000 Android Development] scottietohottie:
I would live to say 100% yes, but there is always the exception. I have not had any issues. So for me yeah go for it. Just have a rom on your sd incase you ned to reflash.

The glitch thread is very active, if you get any issues.
[Galaxy S I9000 Android Development] siky_dude:
Why not use the same ril in this sgs?

Or you will implement it after the work is done in sgs2.
[Galaxy S I9000 Android Development] scottietohottie:
Rouge apps. Uninstall them to confirm the issue. Some times a simple uninstall - reinstall will sort it. I would uninstall, flash glitch. (i prefer non voodoo color as I had issues with colors etc). See what happens. On sammy stock adroid os is about 4-8% by all accounts.if this solves the android os. Start to reinstall the rouge apps again one at a time.
[Galaxy S I9000 Android Development] eeyunopper:
What he said...

Sandstorm did this to me, very annoying... However, reinstall didn't work for me. Luckily I backed before... As I always do before changing anything..

Currently on #43, fugumod 103v, my OS is 2% after 13hrs battery on. OS is always higher when first turned on, but then reduces as other things are used.
[Galaxy S I9000 Android Development] J_Force:
What rouge apps do you mean? If you mean the navigation app I've had it for a long time and many nightlies, never any problem. Should I just remove and install? Should I do anything more like move to SD perhaps (just guessing).
[Galaxy S I9000 Android Development] eeyunopper:
Did you restore apps + data using titanium? Have you any new apps? I'd assume any app that was ok before should be ok now, but knowing how volatile CM seems to be on some phones, maybe this isn't the case.

If it was me, I'd factory reset, flash froyo (with the bootloaders, obviously) and install newest nightly... make sure all worked, make a nandroid backup, then restoring apps without data.
[Galaxy S I9000 Android Development] eeyunopper:
Just remembered, I use Co-pilot, this also runs high even if I haven't used it.. I don't use it often, so uninstall and reinstall when I need it, however, Titanium backup can "freeze" apps, might work...
[Galaxy S I9000 Android Development] ethanfel:
i'm back on CM7 after 2 weeks of stock. (not that bad anymore btw)

#47 i don't have cyanogenmoid settings (crash) and theme choser.
[Galaxy S I9000 Android Development] scottietohottie:
Apologies, got into work and had some urgent stuff to cover. A rouge app is one that its misbehaving. This could have been working for ages then all of a sudden get a glitch.

Alternatively, flashing a new rom could mess with it. An example. Your have navigation. This uses gps (obviously), you flash a new rom or a revision, one of the changes is that the satilite pool had changed. If the app is looking for a different pool, it will be sluggish and use more power. A number of apps open on boot, to check for crap like that, normally they get the data and close. But if something has changed they could get stuck in the open state. Re-installing normally sorts this type of thing out.

If your getting problem best remove the stuff causing it and put it back one at a time. It could also be a glitch caused by one if the changes. By re installing one at a time your be able to raise this "bug". :) hope that clears it up
[Galaxy S I9000 Android Development] jaikat:
ouch.. thanks for the tip, i sensed there was something wrong, but my supernatural abilities were somehow being held down for some reason :D

flashed a couple to test, yes it works now

thank you
[Galaxy S I9000 Android Development] Red_Vex:
Installed #48 didn't see touch to focus :confused:

How it works?
[Galaxy S I9000 Android Development] J_Force:
No new apps and no restore. Just installed everything from scratch. Should I just close the navigation by long pressing the back-button?
[Galaxy S I9000 Android Development] junkyhlm:
Nightly #48

CWM: 4.0.0.5

Flashing via ROMManager with dalvik wipe and GApps. No problems yet, have'nt tried to restore a backup to see if that bug is still present, will report as soon as I know. Of course the phone is snappy as hell and the most eye catching change to the ROM is that they included a screenshot app (goodbye "shoot me") and touch to focus in the camera app. Will test this out and report back.

For some people the GApps is kept after just flashing the ROM but i have to reflash it every time to not loose my precious google apps :)

Edit:

I don't understand how to use the touch to focus function. My camera settings got "Pre-focus" or "Long press to focus". I know that the pre-focus function were there previously but i dont know about the long press stuff. Maybe that is what the changelog is speaking about.

Regarding the screenshot funtion the button is located in the Power Menu and works like a charm:
[Galaxy S I9000 Android Development] Red_Vex:
I see screenshot in power menu but how work touch to focus...i touch screen but nothing happens.
[Galaxy S I9000 Android Development] junkyhlm:
I did not get touching the screen to focus to work either, just long-press focus. But that could have been from previous build.
[Galaxy S I9000 Android Development] strickyy:
U'r a hero man, i couldn't stand stock for 2 days lolz :rolleyes:
[Galaxy S I9000 Android Development] eeyunopper:
Never worked for Co-pilot, even after freezing it still showed under battery use, and GPS was switched off..

Is it definately the navigation giving you the 800mhz bug?
[Galaxy S I9000 Android Development] atinm:
I should have said, they're different in that one works, the other doesn't. The underlying software is different. You can't mix and match things - modems for SGS2 will not work on SGS or vice-versa.
[Galaxy S I9000 Android Development] siky_dude:
Ohhh...that makes me sad :(...

Damn you samsung...damn you all to hell :(
[Galaxy S I9000 Android Development] J_Force:
Don't know that now. Since reboot 1000Mhz 2%, 100 Mhz 5% and Deep Sleep 90%. Will try what happens after some navigation use.
[Galaxy S I9000 Android Development] ethanfel:
Actually iwas on gingerreal 6.4 it was quite good, as smooth as cm7. But a ugly theme and some freeze made me comeback to cm7. It's unstable too but i know why and i expect it to improve, with stock rom i can't say that.

I tried MIUI on my way back, (that was because of that i had some issu with cyanogensettings) i can't say i like it, too much a iOs clone for me.
[Galaxy S I9000 Android Development] jurguh87:
Hey guys,

Im on a early build #28 i think ( was away for long holiday) but now i want to update to the latets build using rommanager but the sdcard wont mount how can i fix this orlet it mount

Thnks in advance
[Galaxy S I9000 Android Development] hensk:
becouse of that updete I flashed #48.but maybe we need fresh install

wipe data/factory reset
[Galaxy S I9000 Android Development] Herman76:
Where doesn't it mount? In CWM or in CM?

If in CWM there was a issue back at #23 which made it not mount the SD-Card in ClockworkMod.

Under is the way to fix the CWM problem (taken from the Nightly Resource page).

Fix (method #1):

Flash this kernel as PDA using Odin without repartition:

http://www.multiupload.com/YGGZNR0NZ1

Ref: http://xdaforums.com/showpost.php?p=14624998&postcount=8842

Fix (method #2):

ADB fix: http://xdaforums.com/showpost.php?p=14595225&postcount=8652
[Galaxy S I9000 Android Development] atinm:
Touch to focus: Only on supported devices. SGS phones are not supported yet.
[Galaxy S I9000 Android Development] jurguh87:
Yes in cwm when the update proces starts youll get first waiting to sdcard to mount 20s and then it counts down to zero and tells me cant mount and the update is aborted.

Ill try to flashthe kernel and try it again

Thnx
[Galaxy S I9000 Android Development] liranvaknin:
What is the best kernel to go with this rom? (Im on rc1)

By the way the kernel that comes with cm7 is a stock kernel or modded one?
[Galaxy S I9000 Android Development] Munszu:
USSD Codes

Hey!

I've installed CM7 recently and everything looks fine, except a battery drain bug wich I've managed to solve by installing the JVP modem and setting the CPU behavior to Conservative. But now I ran into another, this time minor bug. I can't run any USSD codes, like the code for accessing AngryGPS. Does anyone met with this bug and managed to solve it?
[Galaxy S I9000 Android Development] junkyhlm:
This aint a bug. most of the codes are removed. Why would you like to use them?
[Galaxy S I9000 Android Development] atinm:
Modded - we fix whatever we need to make the stock kernel source work with AOSP, as well as any bugs we can fix. The only major thing that other kernels add that stock CM7 kernel does not is OC/UV - we think they are unstable and do not want to support them. None of the stock CM7 kernel across the devices support OC/UV. Everything else is minor stuff, that we would support if we could do it cleanly, or had time.
[Galaxy S I9000 Android Development] Munszu:
Oh.. I see.

I just wanted to adjust a few things in AngryGPS, and wanted to turn off HSUPA.

With the JPO modem the GPS works just fine, I just got used to tinker around the GPS settings after I install a new ROM.
[Galaxy S I9000 Android Development] Red_Vex:
Someone can explain me how to work touch to focus?.

What is the orange theme similar to cyanbread?
[Galaxy S I9000 Android Development] ock:
From a page back: "Touch to focus: Only on supported devices. SGS phones are not supported yet."
[Galaxy S I9000 Android Development] frauhottelmann:
AngryGPS is not used in CM7, if you wish to use a different ntp server, use FasterFix, otherwise there isn't anything that needs tweaking.

Why turn of HSUPA? You can disable 3G in settings... I can't see the point of disabling just HSUPA (except you don't like high upload speeds...)!
[Galaxy S I9000 Android Development] jaiiscool:
I came back today after a month on stock, never ever going back.
[Galaxy S I9000 Android Development] sugar 7:
Ah ok but there is in the changelog :cool:
[Galaxy S I9000 Android Development] Munszu:
Bah, I've changed the ntp server by editing the gps.conf file with Root Explorer, I wanted to tweak other things.

Turning off HSUPA and using only 3G can improve the battery life even more.

OFF:Sorry I didn't used Quote. I haven't used this forum for a while, I kinda forgot that I'm supposed to use Quote when I'm replying to someone.
[Galaxy S I9000 Android Development] Red_Vex:
Tnx...at least i get screenshot function.
[Galaxy S I9000 Android Development] atinm:
"Touch-to-focus is implemented on supported cameras." is what the changelog actually says. What you read is just the first line in the full changelog message. You can click on the link to see the full explanation, including the code that changed.
[Galaxy S I9000 Android Development] sugar 7:
Done !

working...touch 2 time on the screen it's ok...:)
[Galaxy S I9000 Android Development] atinm:
Luck ;-) - we didn't do anything specific for this and auto-focus was still iffy from when we last did it.
[Galaxy S I9000 Android Development] codeworkx:
T2F doesn't work on sgs.

What you mean is Touch 2 Zoom. xD
[Galaxy S I9000 Android Development] sugar 7:
Ah ok thanks sorry..:o
[Galaxy S I9000 Android Development] jaju123:
Does the kernel have any mem settings/is it compatible with memory scripts? And have the changes from yesterday i.e. the new kernel and FM radio stuff etc been merged yet?

Thanks, went to JVQ today and the battery life is actually the same on CM7 tbh, apart from when data is turned on.
[Galaxy S I9000 Android Development] ristokoo:
Sorry to keep nagging about this but as the devs now seem to be around I ask again this:
[Galaxy S I9000 Android Development] deconfrost:
did everything first post say for first time flashing, downloaded Bootloaders + Froyo + Speedmod from first post, rooted it, then install cwm from rom manager which is 2.5.1.2, nandroided it, wiped then flash, and no cm7, just back to stock rom
[Galaxy S I9000 Android Development] atinm:
This is more a general CM thing - not specific to Vibrant. Not something we can help with, and requires someone on the CM team as a whole to look at. Most probably we just don't have a developer from Finland, and so no one has got around to fixing the keyboard.
[Galaxy S I9000 Android Development] Herman76:
What did you flash?

Which ROM did you download?

Did you download from http://download.cyanogenmod.com/?device=galaxysmtd?
[Galaxy S I9000 Android Development] frauhottelmann:
So you want to turn of HSPA... (HSUPA is just the upload part of the HSPA standard ...) Don't know if that is possible in CM7.

What else would you like to change about GPS settings? (when you flash like every nightly, you don't want to edit the servers manually ;-))
[Galaxy S I9000 Android Development] deconfrost:
thanks for reply, nevermind my last post :)

got it working now. instead of using froyo rom as first post stated, I flashed stock JVH 2.3.3 rom then flash CF-Root JVH with CWM 3.2, reboot to CWM 3.x.x.x wipe everything and CM7 goes on perfect.
[Galaxy S I9000 Android Development] ristokoo:
Thanks atinm! Yes I think it is a general problem. I'll try through other channels but it seems we could use a Finnish developer to get attention to this. Unfortunately I'm not one;)

But if I find the time it would be interesting to take a look at this and learn something new on the way. It seems an easy one to fix as the correct keyboard already exists (the Swedish is also the Finnish layout). So I think it's only a matter to combine the Swedish layout and the Finnish dictionary (which also is there already). So far I have no idea how to actually do this :D
[Galaxy S I9000 Android Development] mr_at_sgs:
CM is getting better and better!

I have to say thank you to all Cyanogenmod Developer, since #46 the batterylife is equal to samsung stock roms with stock cm7 kernel. My second donating will be with a final release.
[Galaxy S I9000 Android Development] J_Force:
Since I have flashed the #48 nightly my day became much better ;). Battery used much less, no 800 mhz issue anymore, still quick as only cm can be :)! Hope to be able to bluetooth connect to my car and than it would be like perfect.
[Galaxy S I9000 Android Development] Herman76:
I read on the Cm forum the following.

Might this be the cause of the trouble some people have to pair their bluetooth devices?

Just my 2 bucks on the matter (crazy inflation guys!).
[Galaxy S I9000 Android Development] opher50:
Hello Everyone ..

after many many troubles trying install Miui Roms and CM7 that every time when it finished it would just give com.android.phone crash I figured out the problem .. and its not only my phone ..

the problem is weirdly inside the typical SIM our company hands out .. Cellcom company in Israel gives a Sim-card that wont work with MIUI / CM7(since CM7 11 or something like that ) .. from what I know since version 11 of CM7 (and MIUI ofcourse because it's source is CM7 pretty much i think ) you started working On samsung's RTL/RIL .. So I think that our sims somehow wont work with the RTL fix?

You think you could somehow check it out and figure out how to fix it?

I know now many friends with galaxy S and that specific Yellow Sim-Card of cellcom and for everyone there is the same problem .. its a 3.5G sim i think .. my sister has a purple sim which is probably 3G (but not below ) and it works perfectly with it ..

Any idea?

Thanks alot , Opher!
[Galaxy S I9000 Android Development] katsooba:
WAT?

i have two galaxy S devices, one on pelephone [my personal phone] and one on orange.

they both work great with CM7 #46
[Galaxy S I9000 Android Development] opher50:
thats what i'm saying!

Cellcom's Specific yellow SIM won't work with the newest CM7 / MIUI

* I've read a little more on google .. and apparently the Yellow sim card wont support the new BASEBAND .. and not only for Galaxy S .. also for Motorola Milestone and others ... can the sim be really old? O_o
[Galaxy S I9000 Android Development] siky_dude:
The new (i think) JHJV6...

Don`t let the name fool you...its just a typo...

its jhjv6 and its awesome...:)
[Galaxy S I9000 Android Development] coffeeboy:
Anyone have DXJV9 modem for CM7,thanks
[Galaxy S I9000 Android Development] siky_dude:
here you go...
[Galaxy S I9000 Android Development] liranvaknin:
Is there any reason why I get only 72 mb link speed over my wireless n network?
[Galaxy S I9000 Android Development] Leegalaxy:
Hey everyone, I have been getting the dreaded battery drain. I'm in Canada. I have been using KC1 since the first nightly (with the exception of the bastard which didn't support it). But now I'm trying the JL2 modem that codeworkx posted on the main page as a compatible CM7 modem. Anybody else have any thoughts on these two modems? Experiences related to signal or battery life? (FYI the JL2 modem comes up as UGJK4 in the ' about phone' section in settings)

GT-I9000. CM7.