yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] ou812bkewl:
Ok. I don't mind long posts when they have great info like yours. Does anyone know what causes GB roms not to work on froyo bootloaders? I have honestly never tried to flash a GB rom over froyo bootloaders. Most devs that suggest it seem to do so in the interest of using the "safest practice".

Ok back to CM7: I had a problem last night with my launcher becoming sluggish so I figured I'd reboot. When my home screen was back up, the android phone service started to FC about every 5 seconds. I then checked the "About Phone" section of the settings menu and the Phone Number, IMEI and IMEI SV fields were blank. I have seen issues like this before and it is always caused by a corrupted EFS file. The only way to resolve this was to restore my /efs folder from backup. To everyone using any custom rom, I would like to reiterate the importance of backing up the /efs folder using the methods described in the thread dedicated to it. Just search for "backup nvdata.bin" and it should come up. I was on an uncustomized CM7 ROM nightly #104, CM7 original kernel, and KC1 modem. Has anyone else encountered this issue?
[Captivate Android Development] sixstringsg:
Did you use the 2g/3g toggle?
[Captivate Android Development] ou812bkewl:
HAHA! I sure did! Noob moment. I saw 2g/3g issue mentioned here so long ago I didn't remember until you told me. Well I can confirm that it is still an issue. :-)
[Captivate Android Development] sixstringsg:
A wipe data usually fixes it, as would a nandroid restore.
[Captivate Android Development] cfili:
I did the same yesterday, I fixed it by using adb and removing a value from provider settings DB.

Sent from my SGH-I897
[Captivate Android Development] nkrick:
Interesting. I had not heard of that fix before. If this can be fixed through adb, it seems like this fix should be scriptable and then usable as at least an "integrated workaround" implemented in the code...
[Captivate Android Development] prayii:
Anyone know how to make the Headphone Amplifier level stick in the Voodoo Control app? It resets all the time. Annoying.
[Captivate Android Development] nkrick:
If you don't get an answer here, you may want to look in or ask your questions in one of Supercurio's Project Voodoo threads. They are probably somewhere in the i9000 forums...
[Captivate Android Development] hauj0bb:
In Voodoo Control, select "Map Volume Keys hack", and then turn off "JACK plug-in safety". The headphone amp should now always stay where you left it.
[Captivate Android Development] cotr:
Nightly Builds?

Have nightly builds stopped? Im hoping for a fix on battery drain...
[Captivate Android Development] Smasher816:
Yes.

someone hacked kernel.org (hosts android source code), and they are doing maintence on it bow.

untill then cm7 cannot update, breaking the nughtly build bot
[Captivate Android Development] halfsoul:
Which app? I tried a few awhile back, all unsuccessfully.
[Captivate Android Development] Aztecbandit:
Ok so I've been having this problem constantly. And I dont know why, but its only CM7. Every time I flash a build ,starting from #16 up to #100 which is the latest build I've ran, after a few days or weeks I'll get a force close from normally Browser, XDA, or Amazon Appstore. Soon after that I get a force close from Google Service Frameworks. At that point anything I open force closes, and I'm forced to reflash the ROM. I have a 1007 model, any known reasons this happens and any way to fix it?
[Captivate Android Development] Smasher816:
type "df" in a terminal. check if /datadata is at a high %.

This has been none to cause lots of force closes.

But seriously search. This has been literally posted on almost every page, with the exact same problem as you...
[Captivate Android Development] Aztecbandit:
Weird cuz ive posted that question a few times and never get an answer, and when i do search its always slightly different then my problem
[Captivate Android Development] cfili:
com.android.phone force close loop 2g/3g toggle issue

Here's what I did using adb shell:

$ su

# sqlite3 /data/data/com.android.providers.settings/databases/settings.db

sqlite> delete from secure where name='preferred_network_mode';

sqlite> delete from system where name='expanded_widget_buttons';

sqlite> .quit

More details here for anyone who is interested:

http://code.google.com/p/cyanogenmod/issues/detail?id=2928
[Captivate Android Development] Smasher816:
Sorry to hear that. But here are some of the many i found on the first search page...
[Captivate Android Development] Jemack:
Ouch......that's got to hurt!
[Captivate Android Development] Smasher816:
:P

I was annoyed from my homework and took some time to put that list together.

Sorry if it came off mean but I was just making the point that other have said: many have had this same problem (mass force closes due to full datadata).
[Captivate Android Development] halfsoul:
I wonder if the devs are considering changing the partition sizes so this doesn't happen. Kaik?
[Captivate Android Development] Kaik541:
I'm not a dev.

The partition is as large as it can be while staying on oneNAND, if were to move it back to moviNAND (on /data/data instead of /datadata) it would be back to like using a Samsung ROM again (including the slow). CyanogenMod is about lightweight, fast, and configurable.

If you want to go back to using /data/data instead of /datadata, all you *should* have to do is make a symlink or bind using the /data/local/userinit.sh script (a script that is run on boot and won't be wiped between installs--unless you factory reset) to set /data/data back to the moviNAND. you will likely see a decrease in speed and responsiveness, which is why the team has decided to keep the /datadata partition "solution".
[Captivate Android Development] littlewierdo:
The solution that the CM team came up with is not compatible with how the market works (regarding how partitions are setup).

Unfortunately, any apps over 30 MB simply cannot install (based on my understanding of how the market cache is setup). If this is all part of the reasoning behind the limited datadata solution, it is not a great solution.

Compatibility should be the first consideration. As it is, right now, I have to purchase apks and then side load them thru various, nefarious means to get them on my phone (I purchase the apks to make it pseudo legal and make sure the developers get paid).

Add to that, the number one issue since CM came to the Cappy has been the datadata partition filling with data.

Again, it is a problem that has been asked about on a regular basis and quite frankly, 'Im' even quite baffled as to how to fix it (and I consider myself to be somewhat 'tech-smart').

My current datadata partition is 98% full and no apps that are installed can be moved to the sd card (according to apps2sdcard). Deleting caches doesnt affect the datadata partition (tho I tried it for ****s and giggles). And yes, I have the option enabled under Cyanogenmod Settings>Applications>Enable Moving ENABLED.

A system needs to be derived that accomplishes two things.

1. The user should not need to 'manually' move anything. Android should be managing this (this is after all the reason I have 'let android choose where to install my apps' set to 'Automatic').

2. Provide maximum compatibility with apps downloaded from the market (including those over 30 MB). Perhaps the market cache can use the 13 GB internal partition for temporary storage for the market to store apks while it is downloading them to install. I dont care if this is slow, Im only installing an app, after which, the apk is removed.

Unfortunately, Im not familiar with how CM is setup on the phone, I just sort of expect things to work. And that is how CM should be, isnt it?

There are solutions to the laggy and slow issues that people have come up with.

Hell, how did Google setup the Nexus S? This is a very similar phone hardware wise, 'maybe', this might be something to look at as a model for how CM should function (that is, assuming this was not already looked at).
[Captivate Android Development] makelegs:
Have any of u guys tried the S2E app, from the market, to mitigate the app/data storage issue?? I personally use darktremor's script on N1, and it's been said that S2E is a bit more user friendly. Market description does not specify phone model requirement. If it were to work for cappy, it should allow you to move apps, cache, and data to an sd-ext partition. Data2sd can definitely "slow" ui performance modestly, but I rarely notice it on N1.

Maybe there is some obvious reason that I have overlooked why it would be incompatible for cappy. Just figured I'd pose the question.
[Captivate Android Development] Kaik541:
for one, the /datadata partition has nothing to do with /cache. second, we DEFINITELY aren't the only device with a /cache partition smaller than the largest downloadable size from the market (about 50 MB, we have a 30 MB partition). third, the Nexus S has full access to their oneNAND partitions, we have a lot of space wasted by the bootloaders, bml8 (aka unused recovery partition), and the space for the modem (you do like using your phone as a phone, right?). fourth, the "market compatibility issues" are related to /cache, which google, in their infinite wisdom, decided with newer versions of the marketplace to just assume is unlimited (which on many devices, it isn't). If anything, this is a complaint for google, not TeamHacksung.

There's a reason why we've always agreed CM isn't for everyone, there's a reason we don't say you should install it on your mom or sister's phones. If you're a technical user and know what you're doing (no, CM shouldn't *just work*), the /datadata partition isn't an issue (especially if you know how to use the "symlink" or "bind" commands). And if you aren't a technical user who enjoys tinkering with your phone, why are you on CM?

As for saying this has always been the "number 1 problem", I find that hilarious because it must clearly be a joke. Saying this has higher importance than say, the 2G/3G toggle or just the Samsung RIL being plain sloppy and sucking our battery lives away is just so damn funny.
[Captivate Android Development] cfili:
So I see many posts here about how to check if datadata is full but not a lot on how to fix it.

Does moving apps to the SD card really fix the issue? What is the best work around?

Sent from my SGH-I897
[Captivate Android Development] nimper:
Moving apps is the easiest work around. I ran into this problem recently myself.
[Captivate Android Development] halfsoul:
You can quickly see which apps are hogging the most space with "du -sk /datadata/* | sort -rn | head" in a shell

In my experience moving the app(s) didn't reduce the datadata size. I ended up just deleting the App that was hogging so much space.
[Captivate Android Development] cfili:
Yeah moving to sd does nothing for this problem for me either. That command is handy, the bad news is that my top apps are ones I actually use. Netflix client being the biggest offender.

Sent from my SGH-I897
[Captivate Android Development] littlewierdo:
Sorry, but I disagree, CM should just work. This is NOT a tinkering problem. (Please inform me what setting to change that will address this).

I would agree 'if' we were talking about a setting to change that would resolve this problem, but it is NOT. This is a problem with the rom (or the lack of documentation if you prefer).

And with regards to the 'number 1 problem', I didnt mean by order of importance, I meant by number of posts regarding this problem. NEARLY EVERY PAGE on this 1100 page thread has a mention of it, yet, no real solutions have been presented. I mean, you really expect a user to have to move their apps every 20-40 MB they install worth in apps?

I will be fiddling with my phone this weekend, time is a resource that is limited for me. FOR THE MOST PART, CM is fantastic. But there are areas where I simply disagree with the dev teams thinking.

To expect a user to use adb and know how to use all the command lines to change and modify their phone is ludicrous.

And of course, no solutions were given in your post, just vague mentions of 'symlink' and 'bind'. Of course, I will do the work, google these and figure out what you mean by mentioning them, their use, and their function and if they provide a viable solution, I will direct users on how to use them to the best of my ability.

My goal is for everyone to have an awesome experience with their phone (and specifically CM). I believe CM is the best rom out there for the Cappy and if there is something that can make that experience less troublesome, I am all for it.

If you look at the majority of my posts, you will see most of them are in an attempt to help a user or letting a developer know that I have found a problem with their rom.

While I dont mean to insult, the elitist attitude from the Linux community is pretty obnoxious. Unfortunately, it appears it has leaked into the Android community as well, which is a sad thing (see "you do like using your phone as a phone, right?" which is a pretty snarky, elitist statement, made in YOUR post. There are more statements I could pull but that one works fine for making my point).

I have donated to a number of Android rom developers (and I have been meaning to for Android as well, I just need to figure out a way that will work for me - this is a personal preference for how I am dealing with my finances - not something I need help figuring out how to do) because I respect their time and efforts, particularly when they do all the hard work and I simply download and install with relative ease.

Again, I am happy with CM overall. This isnt to say that it is perfect, it is to say I believe it is the best rom out there for the Cappy.

Im happy to continue this in a PM, I dont want to cluster f**k the CM thread anymore with a potential flame war.

And my apologies for this being a bit scatter brained and lengthy, Im on my way out the door to work another long 12 hour shift. Didnt have time to read and edit this.
[Captivate Android Development] ThisWasATriumph:
Really easy way to check datadata and see whats apps are taking up: Install the app Diskusage (unless you cant install anything then uninstall something first but it only takes 16kb of datadata) Diskusage will give you a graphical representation of the Datadata directory (under the root option) and all its sub directories and free space. I had only 9 megs after uninstalling a bunch of apps.
[Captivate Android Development] Kaik541:
I didn't list the actual commands because I have never need to set up this solution as I have every app I need installed (about 70 apps) and am nowhere near pressing the limits of my /datadata partion (97 MB used). I've talked to several people who have used it come through the #CMSGS IRC channel though. Quite simply, there is an init.d script (20userinit) that is included by default in every installation that searches various places on the phone for a script called "userinit.sh" including /data/local and /sdcard. This will be run on every boot of your device and will not be wiped (unless you choose to wipe it). If you symlink or bind (not sure which is the better option, but probably bind) /data/data to /datadata, the application data will be written onto the moviNAND /data/data. Heck, theoretically, you could bind it anywhere, including an external SD if you really wanted.

Also, if you go through the posts, you'll notice the "/datadata issue" wasn't even common knowledge until about two months ago. What I expect is that someone using CM know what they're doing. I don't expect them to know "every trick", but to not know adb? Get out. We don't want your kind here if that's how you're gonna play, we don't need ignorant users since they contribute nothing beyond occasionally popping up and going "I get FC's!" with no logcats or additional information, and without that, then we honestly do not give even the smallest of damns.

Lastly, the "elitist attitude" you speak of isn't unique to Linux. It exists in windows (how often do you see people asked if they've installed proper drivers and if someone isn't sure, they just laugh at them?) and elsewhere. Again, this is more of a "if you can't help yourself, why should we do it for you?" thing. To us, it's the same as when one of our friends comes up and goes "you're good with computers right? I've royally ****ed mine with viruses, can you fix it?" and is angry when we suggest performing a full wipe. It's the exact same headache you feel in that situation that I feel hearing a user complain while providing no information to their issues (and /data/data vs. /datadata isn't really an issue if you know how to use bind)

To sum everything up, simply googling could have taught you this much:

busybox mount -o bind /data/data /datadata

The /data/data part could be anywhere you want, the /datadata partition is what's being remapped
[Captivate Android Development] jopet216:
No Market

Sorry for the noob question, but I just flashed this rom and for some reason I cant find the Market App..bad flash or bad luck???
[Captivate Android Development] EnemyOfGlaDOS:
Did you read the CM7 Q&A sticky? Or the OP for that matter:rolleyes:.. you need to flash gapps. That contains the market!
[Captivate Android Development] halfsoul:
Battery drain on microcell

Anybody else experience rapid battery drain while on a Microcell?
[Captivate Android Development] joeybear23:
did you choose to add gapps?
[Captivate Android Development] staplebox:
Less typing on xda, more fiddling with yourself = better resource management. We all win.
[Captivate Android Development] Aztecbandit:
Double post
[Captivate Android Development] Aztecbandit:
It's all good bro
[Captivate Android Development] mnjm9b:
Microcell works fine Here....
[Captivate Android Development] dabels1961:
Thanks for this, it is VERY helpful.
[Captivate Android Development] littlewierdo:
I think you made my point regarding the elitist attitude.

We all started not knowing anything.

Feed a man a fish and he will eat for a day. Teach a man to fish and he will eat for a lifetime.

While I originally had a longer post, it not only is not applicable to the CM thread, others arent interested in this rather pointless discussion, and quite frankly, well, Ill just stop here before I say something that I shouldnt.

Stick to coding, I think it suits you better than explaining how things work for us lowly peons.
[Captivate Android Development] david717:
Littleweirdo, if you want something so bad, do it yourself. The devs do this for free, and I'm sure this SD problem isn't a high priority since it is very easily remedied by the end user, and not the dev. So until you can find a solution to the problem, stop complaining. Some of us enjoy the progress made on CM7. I prefer it over any samsung rom.

I'm tired of people expecting this project to be perfect over night... don't bite the hand that feeds our flashing addiction.
[Captivate Android Development] littlewierdo:
What I more had a problem with is the general elitist attitude. Knowing more doesnt give anyone the right to be an ass (and yes, that includes developers).

And why this common problem is not addressed in the original post with instructions on how to diagnose and fix said problem is beyond me. Of course, there is no fix for 30+ MB apps which again, no mention of anywhere regarding this limitation. People are just expected to know this stuff I guess...

Sorry but, you cant get pissed off at users if your own developer documentation doesnt address known issues/limitations.

Useless trivia for the win...

*shrugs*
[Captivate Android Development] techmik67:
I have 147 apps on my phone, including netflix, and i have never had a problem...... perhaps, as has been stated *numerous* times, it can just be accepted that ** CM7 is NOT for all users **..... if you want/need more space than can be accomplished by moving apps to SD, either accept the several workarounds which have been posted, or USE ANOTHER ROM!!!

Also, afaik, there is a wiki

editable by anyone

, in which you can feel free to post a/the workarounds....
[Captivate Android Development] littlewierdo:
Less typing on xda, more fiddling with yourself = music

Or the more obvious, 'a mess'.
[Captivate Android Development] singlebeam:
I haven't noticed but I will be using one today - I'll pay closer attention and let ya know.
[Captivate Android Development] Kaik541:
as techmik already said, there's a reason I moved the FAQ from the forums to the cyanogenmod wiki and I even have the link to the FAQ in my signature so anyone can find the link very easily as well as edit it. The wiki is community edited and community driven, I had kept it up to date with the majority of important issues over the past several months, and almost NO ONE else has contributed to it, but I can't spend my time adding every single little inconvenience to it. It's up to you guys to actually *give back* instead of just "take take take".

it's not my job to fix your issues. I am very happy with the way the phone is right now, if you aren't, it's up to you to fix it. it's the same reason http://review.cyanogenmod.com exists... so ANYONE can provide improvements and changes to the CM source code and make it a better experience for yourself as well as, potentially, others.
[Captivate Android Development] littlewierdo:
If you have a personal issue with me, please PM me.

The time many users here have posted to help others with problems, the time I have spent to help others here, the time others here have spent to help me personally with problems I have had, apparently means nothing.

Apparently, the only way to contribute is via a wiki or submitting code?

It is beyond me at this point, there is not much else I can say. If all we do is 'take take take', well ****, we dont have much of a community here and its nice to know that some of the CM developers think of the people that use their creation and often times, donate money for their hard work, as such.

The recent post regarding the 16kb app 'DiskUsage' is brilliant! I was going to suggest something like this might be a good idea for CM.

(posted by ThisWasATriumph)

http://xdaforums.com/showpost.php?p=17560148&postcount=10877

But apparently, all we do is "take take take"

All of this makes me sad...

:(

Well, if my statements regarding CM have been taken personally, I apologize for those statements. I dont know what else I can say or do.
[Captivate Android Development] singlebeam:
Well said.

Thanks for the DiskUsage tip!
[Captivate Android Development] joeybear23:
Now, on to the subject at hand.

CM7 is some major android goodness!
[Captivate Android Development] Kaik541:
I don't have an issue with you personally, I'm just tired of seeing almost every fifth post a complaint by a user who has never done anything more than complain. I've been with the team on this project over the past year, heck I'm part of the reason atinm, Unhelpful, codeworkx, coolya, and jt1134 were even able to get in the same room and start hashing things out together back in the froyo days (when we were briefly hijacking #project-voodoo). The "diskusage" app is so unnecessary as it's just a front-end for the "df" and "du" commands, and there's no real *need* to implement it considering the ROM ships with terminal emulator.

If you aren't happy with the ROM, fix it.

If you can't fix it, give back to the community through other means. (Look at the i9000 guys, they run their own wiki that they keep updated regularly with known issues, workarounds, and alternatives... they've even asked captivate users to contribute to this as well, a thing that also hasn't happened)

If you can't give back, then why are you even a part of the community other than to complain?
[Captivate Android Development] joeybear23:
I have made a small contribution to it now... is any of it subject to peer review? Does somebody get an email when it is updated?
[Captivate Android Development] nkrick:
I have never used a microcell, but I have had a very similar experience when using a cell repeater. When on the repeater, cell standby seems to eat up a lot of juice and the phone does not seem to sleep quite right. I have had similar issues on stock though, so I don't think the issue is CM related.