yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] rschenck:
Following my request for people to chime in with their views on what major issues still remain to be fixed on CM7, I got a whole range of response.

Many of them were of course of the "Nothing is wrong with CM7, EVERYTHING is perfect. Life is a bowl of WiFi enabled Cherries!" variety, which I ignored out of hand. There were also many people who repeated my own conclusion, which was basically that they do not use or care about the last few problematic features and feel that CM7 is as "ready for prime time" as any other ROM. However, after sober consideration of that viewpoint over the last few days, I decided it really isn't very practical or helpful.

After all, complacency and contentment are the enemies of growth. Even if CM7 (or any project, really) is 99 percent perfect, we STILL must discuss and strive and grind at that last one percent or instead of making CM7 the best, we are forcing it to settle at something a bit below the best. That would be doing a disservice to the OS, to the Devs hard work, and to ourselves.

Therefore, looked at from that angle, it seems clear the main quantifiable issue that is bothering most users are the problems with is....

720p video, by a wide margin. That seems to be the prevailing issue that bugs the most people and seems the most perplexing. The other major issues, including battery life (sigh) and various RIL issues come from the Cm7/Samsung mismatch and the Devs are doing their best about them.

Other issues that are bothering a number of people are...

Problems with headphone controls, which we all know Atinm is working on.

The Compass (or lack there of)

Video Out not working

Smaller issues include BLN and the FM radio, but there is a powerful consensus that says if BLN does cause battery and wake-up issues or the FM radio is the cause of the issues with headset controls and/or people being unable to hear us during phone calls at times...then kick them both to the curb and leave them there.

Most other issues that were mentioned appear to be for very niche groups of users, or very individual and likely due to that user's own phone/configuration/applications/screw-ups...and not CM7's problem at all.

Regarding the legitimate issues I mentioned earlier, I feel that while we may differ on how severe these issues are in terms of CM7 as a whole, we can all agree that they would be very very nice to see fixed in the near future. We should all continue giving our constructive feedback on these issues (and any new ones that appear) in order to speed that happy day.

However, trolls still need not apply.
[Galaxy S I9000 Android Development] Davith:
You can add phone not going into sleep if data is off and en Exchange account is set (maybe IMAP as well).

At least that's what a few people, including myself, are experiencing. I guess it's easy to reproduce.

Not a big deal for me anyway, I don't turn data off anymore.
[Galaxy S I9000 Android Development] rschenck:
We must all face it, True Believers....the nature of the Nightlies are changing.

Before CM7 went mainline we got used to each Nightly being a carefully crafted update by Codeworkx and Atinm, just for us. Now they are global updates that often wreck a small amount of temporary havok in our Galaxies.

Even SGSTEAM has admitted that they do not always know what will be appearing in each Nightly, and often are caught just as flatfooted as we are by the newest round of bootloops or strange behavior. We have outgrown the point where we should install every Nightly blindly. Now we take a little more care before flashing, but it is tough to be careful when we are in the dark.

The only weapon we have is sharing knowledge more before we flash a Nightly...therefore I have created a new Wiki...

http://sgscm7nightlies.pbworks.com

This Wiki is JUST for sharing direct, factual info on each Nightly. Tips, tricks, bugs and install advice for each build, added in real-time, for anyone to view in a simple, one-stop-shopping situation.

This is meant to be a collaborative effort, as I do not have the time usually to keep it perfectly up to date, and besides, soon I will be gone for a few weeks. Therefore, if you would like user access to the Nightly wiki so you can add info and make edits, please send me a private message on XDA with your email address and I will add you to the user list. Then you will just need to create an account with PBWorks and you will be golden. I urge as many as you as can to sign up as users so we can compile as much info as possible.

However remember that since this is a public wiki, I will be deleting any info that is not related to the Nightlies or otherwise off-topic pretty regularly....so be polite and watch your P's and Q's.
[Galaxy S I9000 Android Development] Laum:
Ehm, compass has been working just fine for a long time. What should be the problem with it? At least with maps its working ok with galaxysmtd. Just have to calibrate it by doing "number 8" in the air every once in a while.
[Galaxy S I9000 Android Development] rschenck:
That is one of the RIL issues that I mentioned as far as I know...some people have it, most don't...but it is related apparently to the way the Samsung modem and CM7 interact when putting the phone to sleep.
[Galaxy S I9000 Android Development] rschenck:
Several people mentioned the compass as an issue, fix or no fix...remember most all of these issues are not consistent. Some people have them, some don't. Really the only one which is experienced straight across the board (hence it's pride of place) is the 720p video bug.
[Galaxy S I9000 Android Development] funkateer2:
the transition from 31 to 32 is worry-free. no loss of su, the fm works quite well but could not adjust the volume.
[Galaxy S I9000 Android Development] FadeFx:
You didnt even have to reflash gapps?

Dor me its a totally different story, i flashed 31->32 followed by su because i thaught itd be lost, and then gapps before i booted first time, however i found my phone bootlooping again, that could be solved with another flash... so there seems to be something different than cwm causing this bootloop. It looks like cwm trys to run some scripts that are not found or something...

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

tapatalked
[Galaxy S I9000 Android Development] blackdeath09:
Thanks it worked.

Edit: can you hear anything from fm-radio using latest build

And if you can, how you do it?
[Galaxy S I9000 Android Development] rover.prince:
Just came from #27 to #32.

1. First Install ended into Bootloop at CyanogenMod Main screen

2. Rebooted to system via 3 buttons combo. Wiped Dalvik Cache

3. Reinstalled #32 and system booted But Google apps were all gone

4. Flashed the Gapps and now rebooting let's see what happens

Oh one thing SU is still there in Rom
[Galaxy S I9000 Android Development] sugar 7:
for me rom manager flash de gabbs with the #32
[Galaxy S I9000 Android Development] dhurk:
i need odin flashable kernel!!!! about #23
[Galaxy S I9000 Android Development] Bonta768:
Same for me: First time I flashed I got a bootloop. I then went back to CWM and flashed the same again, and it worked fine.
[Galaxy S I9000 Android Development] gbohm:
good that codeworkx posted it isn't it
[Galaxy S I9000 Android Development] oaia:
I do not know what to say guys, I have never had a Bootloop with CM7 always update through rom manager, but before that I always go to recovery and Wiped Dalvik Cache and Cache Partition, today updated from 29 to 32 without problems.
[Galaxy S I9000 Android Development] gbohm:
could smb please try to move a huge amount of data(for example some nandroid backups) to the external sd

does it reboot for you too?
[Galaxy S I9000 Android Development] funkateer2:
Dis it with rm, gabbs ticked and no problemo ..i had the issues with 31before
[Galaxy S I9000 Android Development] FadeFx:
Hm, i did wipe dalvik cache on first install, just i installed from cwm...

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

tapatalked
[Galaxy S I9000 Android Development] FadeFx:
Working for me...

Oh, just moved only one backup, does it need more?

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

tapatalked
[Galaxy S I9000 Android Development] MuD-GMZ:
Great idea, very usefull!!

IMHO the tread here is getting cluttered with too much useless information, so thanx!

i9000MTD
[Galaxy S I9000 Android Development] zpon:
I just went from 31->32, it didn't help to wipe dalvik cache and the cache partition, still got bootloop.

I noticed something weird when flashing dalvik cache, I got an error saying "/sd-ext not mounted" (or something like that).

I also had to reinstall gapps.
[Galaxy S I9000 Android Development] gbohm:
jep i tried one it worked please try more (i did 7or 8 but 3 made a reboot too perhaps more than free ram? ! )
[Galaxy S I9000 Android Development] rschenck:
That is a common message, I get it every dalvik cache wipe. You can safely ignore it.

Did you fix the bootloop? Did a second install do it?
[Galaxy S I9000 Android Development] rschenck:
Well, the Dev thread has to play a lot of different roles, so Nightly install issues can get a bit swe[t away by both relevant and irrelevant issues.

So come join the Nightly Wiki as a user...we need more input!

http://sgscm7nightlies.pbworks.com
[Galaxy S I9000 Android Development] zpon:
Okay. Yeah, second flash did the trick.
[Galaxy S I9000 Android Development] rienkar:
Same to me, when I try to copy large amount of data to the external SD it reboots.

Edit: I've tried on nightlies from #29 to #31, don't know before that. I'll try on #32 now.
[Galaxy S I9000 Android Development] R34L2Pac:
Yes, this also happened to me few times when I tried to move/copy few backups from CWM directory to external SD. So I have to do that through my pc.
[Galaxy S I9000 Android Development] CaracalSef:
I had the bootloop issue too. Flashing second time #32 worked. This was the first time when happened to me and I had to reflash gapps too, but it's working now.

Coming from #29 to #32.
[Galaxy S I9000 Android Development] saszseb:
Why do you use 2 methods for an update?

It's unnecessary.
[Galaxy S I9000 Android Development] Joans:
It looks like at some point CWM moved up to 4.0.0.5, but I was still on 4.0.0.4 even though I was on the latest nightly. Looks like that might be why some people are having problems flashing the newer nightlies and some aren't?

I just flashed the latest Glitch kernel which put me back to CWM 4.0.0.2, then flashed nightly #32 over that and now I have 4.0.0.5, and it's booting first time. I did already try to flash #32 and couldn't get it to boot, so I'm assuming I'll have to reflash my gapps again.
[Galaxy S I9000 Android Development] gbohm:
could you please put your log on pastebin i want to know if it is the same with mine
[Galaxy S I9000 Android Development] R34L2Pac:
Well, here is my story:

Yesterday I flashed from #25 to #31 from ROM Manager.

I made an update queue from this packages: Lippol´s cleaning skript+nightly #31+gapps06132011+FadeFx´s update package (boot animation+gps fix). Everything went fine, booted on first time, so no problem.

Then I found out that su is missing so I downloaded from RM and manually flash it through recovery. But after that I found that backup from RM and recovery doesnt work, just stops backing up after boot.img and recovery.img. Looks like it is a problem with CWM 4.0.0.5, cause I tried custom kernels (FugoMod came with the same recovery and backup didnt work and Platypus came with 4.0.0.2 and backup works again).

Today I updated from #31 to #32.

I wiped cache/dalvik, format /system, flashed #32+gapps and rebooted. Everything went OK, didnt bootlooping or so. Than I went to recovery try backup, but again the version of CWM was 4.0.0.5 and process was interrupted on trying to backup system.img and CWM rebooted. so I flashed Platypus NEO 8 with CWM 4.0.0.2 and everything is fine now.

Yesterday just one other person told here that has also problems with backup from CWM 4.0.0.5, anyone else found out this issue?
[Galaxy S I9000 Android Development] oaia:
just to be sure, and it works, at least for me!! :))

in rom manager you don't have the option to wipe cache partition without wiping data
[Galaxy S I9000 Android Development] zpon:
Strange, I flashed #31 yesterday and got 4.0.0.5 then.
[Galaxy S I9000 Android Development] Joans:
What nightly were you on before that?
[Galaxy S I9000 Android Development] saszseb:
If you flash an update and the Glitch kernel simultaneously via Rom Manager and after reboot run "fix permissions" (via RM.), you won't get any problems.
[Galaxy S I9000 Android Development] R34L2Pac:
Well, I´d like to, but Zach´s NEO 8 kernel has disabled logcat so I can´t. Or if you know how to easy enable logcat than I can try to reproduce the move/copy problem.
[Galaxy S I9000 Android Development] oaia:
very strange, I'm on 32 and CWM is 4.0.0.4 ! it should be 4.0.0.5??

anyway backup works, just did one
[Galaxy S I9000 Android Development] zpon:
#24 if recall correctly
[Galaxy S I9000 Android Development] ericderace:
I've had bootloops before when I was flashing while the charger was connected. I since then flash using a charged battery only and didn't run into that issue again.
[Galaxy S I9000 Android Development] rschenck:
I tested this on Nightly 31, found that CWM4.0.0.5 does indeed have strange behavior. Normally as it backs up the larger directories luke system and data, it runs through the file names as it goes. This time, no file names....I just waited a few minutes and it moved onto the next directory. Eventually it said complete and did the whole MD5 thing, no problems.

At first I thought it may not have backed anything up, but I checked the folders and they are the right sizes.

It may be that the behavior of CWM has just been changed and it no longer shows progress by buzzing through the files it is backing up.

Has anyone tried to restore a backup that was taken like that? I admit, I lack the nerve at the moment.
[Galaxy S I9000 Android Development] Joans:
That probably explains it then, it looks like one of the recent nightlies (whichever one had 4.0.0.4) had a similar issue to #23, so CWM didn't get updated properly, even if you flashed another nightly with a later version.
[Galaxy S I9000 Android Development] sptorrent:
CWM depends on what kernel you use
[Galaxy S I9000 Android Development] R34L2Pac:
Looks like your backup process went well if you get the MD5 thing. In my case, it starts backup boot.img than recovery.img and when system.img starts everything just dissapear (only CWM logo on background stays) and than it shows the menu of recovery.

When I look at that folder it shows me only 3files, boot.img and recovery.img has aprox. 7,5MB and system.img just 2KB. It´s not related to lack of space on sd, cause I have more than 1GB free.
[Galaxy S I9000 Android Development] rschenck:
OK, that is totally odd. No idea why it is doing that.
[Galaxy S I9000 Android Development] zpon:
That might be the problem for me, the last two nightlies I flashed resulted in bootloop (#31 and #32) and during both I had the usb cable plugged in to my computer for charging. But kinda weird if this only results in bootloop during the first flash and not the second.
[Galaxy S I9000 Android Development] mazroui:
hmmm strangely enough jumped from miui to cm7

started from #32 and all was smooth sailing... till i reached cyanogen settings

keeps F/C everytime even after a second/third flash

am i the only 1 ?
[Galaxy S I9000 Android Development] rschenck:
I think a data wipe is suggested for coming from Miui to CM7...I remember the instructions were posted on the Troubleshooting page I think.

EDIT: From the TS Post...

To install from MIUI (courtesy of runedrune)

- Reboot into recovery using 3-button-combo

- Choose "mounts & storage" and format system, data, cache, datadata

- Do not apply the initial-file. (not relevant anymore anyway)

- Apply the latest update

- Apply the latest gapps

- Done. Reboot
[Galaxy S I9000 Android Development] mazroui:
thanx for the fast reply ^_^ much appreciatted

guess i forgot the data and datadata part even tho i was pretty clean from yesterdays fresh flash, anyways will follow the guide ^_^ thanx again
[Galaxy S I9000 Android Development] sambwel:
Just flashed #32 and things seem mostly good. Still having problems with Breakfast.apk though. The "cook egg" function does work but only on hardboil setting. Every time I try to switch to softboil it FCs. Help please
[Galaxy S I9000 Android Development] aamirleo55:
i had installed this rom, when i open titanium backup it asks me to root. how to root my phone?
[Galaxy S I9000 Android Development] rschenck:
You need to install Superuser again. Do it from ROM Manager or there is a link around here somewhere to download it from, or get it from the Market.

And after that, next time...read back a few pages before posting in case you can get the answer to your question, likely the same question many others have already asked, more easily.
[Galaxy S I9000 Android Development] vorcigernix:
which radio?

Hi,

how can I say which radio is best for cm7? my original pda version was I9000XWJPF. There is link to compatible radios in first post, but there is nothing like JPF. I tried JP9 and it is working, but I want to understand it.

I have galaxy for week, cm from friday, so be kind if this is a retarded question please :)
[Galaxy S I9000 Android Development] zpon:
Which nightly did you install #31? or #32?
[Galaxy S I9000 Android Development] rschenck:
There is very little practical difference between radios. Some may work a bit better in some regions, or with some carriers, which will improve your battery life a bit. Beyond that, they are all pretty much the same.

They are also dead easy to flash, so read the forums to get some ideas on what modems you may want to try, download them, and flash 'em for a day or two to try them out.

In the end, no one can tell you which one will work best for you...you just need to experiment.
[Galaxy S I9000 Android Development] jeebspawnshop:
If you really wanna flash your own radios to CM7, you can do the following easy trick;

1 - Grab any radio CWM zip file from codeworkx site: codeworkx.de/download/cyanogenmod/

2 - Open it with WinZip

3 - Appropriate the modem.bin file from whichever firmware you wish

3 - Drag your chosen modem.bin file IN TO the opened zip

4 - Just hit Ok, Accept, or whatever

5 - Once done, copy the zip to your phone, and flash it via CWM

Enjoy your new radio ;)

I utilized this method to flash the latest Vodafone GB modem to my phone (JV3?) which actually helped the reception of 3G in my house. Yay :cool:
[Galaxy S I9000 Android Development] Bork84:
great idea!!

just used it to move from #27 to #32..

bootloops - second flashing did the work - gapps needed reinstalling...

all good now :)
[Galaxy S I9000 Android Development] frauhottelmann:
Well, that was a first for me :D Had a little boot loop after installing #32. So installed it again and bam: normal boot :) But alas I had to reinstall GApps... Never happened before, but what ever^^ So back to differential equations :D
[Galaxy S I9000 Android Development] codeworkx:
can someone check on which cwm version nandroid worked without problems?

some user are reporting problems on doing nandroid backups, bootloops and so on.

i think it's related to cwm.

if 4.0.0.3 works, then i know whats wrong.
[Galaxy S I9000 Android Development] frauhottelmann:
Trying 4.0.0.5 backup as I type... But I am not gonna try restore (I just updated...) :D

Edit: Well, backup worked :)
[Galaxy S I9000 Android Development] sugar 7:
then I'm CWM 4.0.0.5 I can do a nandroid backup

thanks
[Galaxy S I9000 Android Development] mystombox:
Same thing for me.

I had to flash from 27 to 32 -> bootloop

Then 3 button recovery, and flash 32 again.

Got to bootup animation.
[Galaxy S I9000 Android Development] saszseb:
Yes, you need to tick "wipe dalvik". I have been updating via RM for a month.
[Galaxy S I9000 Android Development] Bork84:
just did a backup and restored it

cwm 4.0.0.5 (nightly #32)

no problems here...
[Galaxy S I9000 Android Development] commandozzz:
That actually sounds like the backup settings were changed in RM. Ive been using those settings lately, if you go into advanced settings in RM, you can choose to disable progress tracking of backup, and therefore make it go faster.

The problem with 4.0.0.5, I also experienced it when flashing from 25 to 31. Backup and restore would both stop as soon as it got to system, thus resulting in an incomplete backup and incomplete restore.

Sent. Period.
[Galaxy S I9000 Android Development] worly:
When does the Wifi policy gets fixed finally? I always have to download bigger files with screen on :/
[Galaxy S I9000 Android Development] Herman76:
just set the policy to "never"?
[Galaxy S I9000 Android Development] xero2002:
#32 using CWM 4.0.0.5 with newest RM and no problems. :)
[Galaxy S I9000 Android Development] Zatta:
Wich build has had version 4.0.0.3, can someone tell me that and I will try

Tapatalked u see
[Galaxy S I9000 Android Development] kris713:
Getting rid of the Call end bleep

Any one knows how to get rid of the loud call end/disconnect bleep please? I'm using build 32, my first experience with CM7 (have previously tried MIUI) and loving it.
[Galaxy S I9000 Android Development] DROCSID:
Well, with #30 ur still on 4.0.0.2, you guess yourself ;-)
[Galaxy S I9000 Android Development] R34L2Pac:
+1

Also will test it, if someone tells in which nightly was 4.0.0.3. I was on #25 (i think it had CWM 4.0.0.2) and than I flashed #31 and #32 (both 4.0.0.5 and I had problems in both with backup). So the 4.0.0.3 might be in #26 or #27 but I dont want to blindly flash to find out.
[Galaxy S I9000 Android Development] montrealcityboy:
well i had done the format system like codeworkx suggest we do and when i flashed to #32 it still did the bootloop,reflashing the nightly fixed to problem as we all know. but one thing i noticed with the recent nightlies that have the bootloop issue,is when i go to "fix permissions" right after i flash the nightly,it "fixes permissions" instantly and does not take a few seconds as it normally does. that's when i know it will bootloop.so after reflashing when i go do "fix permissions" it takes a few seconds and that's when i know it will boot up properly.

just trying to help out the devs so they can accurately pinpoint the issue and maybe what i noticed could help.
[Galaxy S I9000 Android Development] zolah:
Can anyone help me...

I tried to update to number 32 but it gave me orientation issues where you had to tip the phone upside down to get potrait mode etc etc.

I flashed back to ezbase and factory reset and wipe cache partition and flashed again but i still had the same problem...

I had nightly number 30 on my sd card so i flashed ezbase yet again and started from scratch...

Problem with that was that i couldnt install gapps through rom manager because it said i needed the latest version of rom manager and then just forced closed the app...

Could anyone help me out please
[Galaxy S I9000 Android Development] IINexusII:
does anyone have a working link to the nightly #19 for me? the official nightlies page dosent exist anymore and im feeling to go back to that and test the battery, beacuse im getting very high android OS usage on mine at the moment, even with no apps installed...
[Galaxy S I9000 Android Development] xan:
What he said :)
[Galaxy S I9000 Android Development] Draco32:
tested with google talk i can see both parts of the video on my phone but i am unable to see the phone video on my PC. The FFC is working. Audio both ways is also working.
[Galaxy S I9000 Android Development] jetpackjeff:
Can someone upload or link to the latest gapps with the new Google talk again for the new thread?
[Galaxy S I9000 Android Development] got_milk:
https://dl.dropbox.com/u/11741385/gapps-gb-20110503-signed.zip
[Galaxy S I9000 Android Development] got_milk:
Works for me, both PC and SGS are doing video + audio. It's not perfect by any means - video coming from the SGS is a bit laggy - but it's not bad.
[Galaxy S I9000 Android Development] Jason123420:
Is this "for everyday use now"????