yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] uberingram:
Do the permissions fix outlined in the OP.

Only time will tell in my case. After a good and solid 24 hours I started to see a LOT of performance degradation on 3.4.1.
[G1 Android Development] driguez:
Complainers? Funny. Since you are not having any issues then the world its beautiful. Listen, its not about being complainers, if the phone is having major issues like constant freezes and force closes of course you are gonna be a little upset, if you are about to receive a call and it just freezes not showing who is coming from and cant answer, if you are replying to a txt and it just freezes, if you are browsing and freezes, you know the little things most ppl use the G! for, TRUST me you are not gonna be too excited. :rolleyes:
[G1 Android Development] fallinprince:
IF you were running a theme RELOAD the theme then attempt a full boot

I got the ACore crash when my Launcher.apk was different

(because i had icons on the 4th and 5th screen)
[G1 Android Development] driguez:
Thanx will try that.
[G1 Android Development] driguez:
That did it thanx.
[G1 Android Development] fallinprince:
Simply enough i believe that 3.4 is stable and you should always save ur previous rom

and yeah i would be pissed but i play with my phone ALOT and ive only froze it once
[G1 Android Development] Denkai:
If you want to back up to a previous version, read the thread, it's been covered at least 2 times. Cyanogen is smart and has his stuff backed up.

http://n0rp.chemlab.org/android/
[G1 Android Development] cyanogen:
Remember people.. Alot of the stuff thats going on in this thread is about improving Android performance which involves a bit of experimentation. I test these ROMs myself, but I obviously can't reproduce the same conditions as everyone else at all times.
[G1 Android Development] fallinprince:
The best way to replicate the crashes is to switch from application to application. its how i crashed mine i switched from msg to a (big) game to office to task manager to settings(applications) to and just staying in each long enough for them to load and maybe do a couple things..... with sms popup overlaying for each text received

it seems to be a memory leak where u don't recover memory
[G1 Android Development] driguez:
I understand and respect your work, its a bit frustrating when you are out and about, its all.

Was having issues with disappearing apps til i upgraded to 3.4.1 and now im having freezes. Just upgraded to 3.4.2, will see.
[G1 Android Development] fallinprince:
logcat

i just happened to have logcat running when i force locked up my phone

it could just be to much ram usage from what i was doing but i cannot get it to lock up any other way

3.4.2 is what im running

Ps.. is everyone who has lockups running class 6 sd cards

PSs....shortly after posting this it returned to the home screen (about 3-5 minutes)
[G1 Android Development] Binary100100:
I'm thinking narcolepsy.

To tell the truth, I've been keeping an eye on this rom but had some serious issues back in 3.4 with my apps dissappearing -> reboot -> bootloop. I've e-mailed, posted, searched and even posted my ddms log. Every answer I get to my question was "Are you using ext3?" (of course I already answered "yes" about 5 different times.) Very annoying. So I went back to ADP 1.51 and don't really have any issues. My phone does seem to sleep (or "coma) and takes some time waking up when I get a phone call (and at times I can't answer my phone) but every rom that I've tried has issues with that not just this one. So because of all the issues, I reverted back to ADP 1.51.

Thus I don't really don't see any purpose in this rom. With a2sd, dalvik2sd, cache2sd, and maybe even data2sd (don't use personally) I have 69 mbs left (which is plenty) and I don't have ANY issues with my phone locking up, freezing or anything posted in this thread for this ROM.

And yes, I've tried the 3.4.1 version to give it yet another chance and in the first 5 minutes it froze and rebooted on it's own (after I let it sit for a few minutes... about 5 or so). I let it sit on my phone for an hour to try it out and it did this 14 times! So... hell no. This isn't for me. But I will be keeping an eye on it because it definitly has potential but it is not yet worth the aggrivation.

Just some information about my past problem... it only happened with 3.4 (not with 3.8), I have an ADATA 16gb Class 6 card, 1gb ext3 partition, 1.2 Recovery Rom and a current total of 198 apps (to EXT3) and with GlossSuite theme (and yes... before I updated to the rom I wiped, flashed, wiped and tried it without a theme and had the same problems without it. Theme made no noticable difference)

I also notice a few people posting a couple pages back "This ROM is great" or "This ROM is fast" or "I don't have any issues at all" but they all ask in the same question "How do I get apps to sd?". :rolleyes:

example:

Maybe that's why they are not having any issues with the rom. ;)
[G1 Android Development] Binary100100:
back when I experienced these problems:

16gb AData, class 6.

14.2 fat/1 ext3
[G1 Android Development] JDMr2:
I've had the same problems w/ apps disappearing, reboots, force closes. . . so i always went back to 3.3.6 which was the last update that was stable (for me anyway). Didn't bother trying 3.4.1 since there wasn't much changed and ppl were still reporting issues. I just now went to 3.4.2 and so far so good. all my apps are there, no reboots, no force closing issues as of yet. If i start noticing anything goin wrong, it's back to 3.3.6 for me until another update comes up.

Thanks and props to cyanogen for being patient and constant dedication to try and help everyone.
[G1 Android Development] prash:
Just to put my two cents in this thread: I am running the .nounion (aka NO apps 2 sd) mod since when this rom first came out and I have never experienced a single 'coma' issue as others are beginging to call it. 3.2, 3.4, 3.4.1, and 3.4.2 all working great (amazingly great actually) so this may be a hint to what the cause of the coma/freeze problem may be.
[G1 Android Development] here.david:
Not able to understand this, however, I am slow...what was/is your base...

When I "just" use CM's roms I have had no issues, I started with JFv1.51_CM3.2-ADP.zip as a base...did the Radio Update 2.2.19.26I from HTC and when it came out did the Pimped Out Recovery Image v1.2. However, as I got brave (silly me) as CM's updates were SO VERY EASY and "COOL", no issues so I then started using others Themes and have had one issue after the next...now when I run into issues I go back to JF, then CM (as listed above) and then the current CM update without any issues..so far anyways...:D
[G1 Android Development] Binary100100:
So you used a theme, started having issues, went back to JF, now back to CM. Are you using a theme now?
[G1 Android Development] jsapp:
I'm on 3.4.1 with no issues. I had issues with the disappearing apps a couple roms back. Reformatted my card and went from 2GB ext to 1 GB. Haven't had that issues again. I was freezing quite a bit for a while too, to where I had to take the battery out (not coming back from a sleep though). Then I was running the hero theme and system tweaks. Wiped and reflashed, and staying away from the tweaks and theme. So far so good, all my issues have gone away. Sticking with just the rom for now, no themes or tweaks.
[G1 Android Development] JakobFriedrich:
ive noticed that alot of peoples phones are hanging and going into coma's with cyn's latest builds but here is waht you should do, it works for me and ya

first when using cynagen when you boot up just let it do its thing don't touch it at all like if you have jf updater on your phone let it tell you that you have 6 or 7 possible updates before messing with the phone at all, and once that is done hit menu twice to unlock your phone than put it in standby mode than unlock and since ive been doing this my phone has never hung or froze or not woken up
[G1 Android Development] kvizz:
how do you wipe your ext3 through cyan recovery image?
[G1 Android Development] JakobFriedrich:
hey quick question i'm running your 3.4.2 on my 1gig sd card partion 50/50

i just got my new 8 gig class 6 and i need to know how to move my apps from my 1 gig to my new 8 gig

should i just redownload all the apps and move them to my ext2 partion by alt+m in img 1.2 than hit up your alt x upgrade_fs so they are all on my ext3

please help
[G1 Android Development] here.david:
One G1 with and One G1 without...just purchased a new SDcard might try the 2nd one with Themes now...Gulp...what am I thinking, need to have one non-issue phone...

:D
[G1 Android Development] DavidChill:
Personally, I would just re-download the apps and start off with a fresh SD card/wipe/apps. You could always download the "AppManager" app from the market and make a backup to your original sd card. Then move the folder from old sd card to the new one, then reinstall from there.
[G1 Android Development] JakobFriedrich:
what do you mean a fresh sd card/wipe/apps and ya i'm doing it the app manager way haha

could you please tell me the easiest way to move em
[G1 Android Development] Erikbronx:
Thanks soo much for your work. :)
[G1 Android Development] kitsunisan:
I've read most of this thread, haven't run across any mention of this; is voice dialer an issue with this rom? I hold down the call button, then try and use a voice command and the phone locks up for about 10-30 seconds, then goes back to the home screen. Runs sluggish for about 10 seconds then back to normal.
[G1 Android Development] kvizz:
Why doesn't my market work?

I try opening it, but it just closes, it doesn't say anything either.
[G1 Android Development] JakobFriedrich:
alright so what you need to do is flash cynagen's pimped out recovery image 1.2 and hit alt+f to fix permissions if that dont work reflash rom
[G1 Android Development] kvizz:
oh okay!

thanks.
[G1 Android Development] kizer:
Switched from 3.41 to 3.2 and doesn't seem so sluggish.

I'm by no means complaing I'm just guessing my biggest problem is the cache to the SD card.
[G1 Android Development] bittermormon:
Are you coming from a theme with 5 homescreens by chance? If so, reflash the theme and should be good to go.
[G1 Android Development] firestrife23:
Cyanogen I know you may not be looking forward to negatives comments but I hate to say this... unfortunately after I flashed to 3.4.2 and 12 hours later it went into comatose. Well don't let this stop you getting to bottom of this, I'm sure we all can figure it out somehow.

UPDATE: Full wiped, reformat fat32/ext3 and install CM-3.4.2 only without themes... so far so good however i notice HTC_IME, teeter and HTC QuickOffice didnt get install during flashing, had to use adb to fix this, no biggie tho. In next 24 hours I'll repost if comatose issues goes away, i have a hutch it's HTC Hero Theme, seem like that's what everybody been running with?
[G1 Android Development] SimonNWalker:
OK, So I've been reading as much of this thread as possible but cant find out if its still ok to run this build without APPS2SD.

Has anyone done this?

Is it possible or does automatically try to configure APPS2SD?

Thanks
[G1 Android Development] Amdathlonuk:
Here,here...........

Don't think of it as complaining but BETA testing.

If Cyanogen doesn't know about the issues he can't work on fixing them.

I think we need to remember he's doing this off his own back, he doesn't owe us anything, if he quit tomorrow we'd all be gutted.

Keep it up Cyanogen I'll help with the testing (As I have NO idea how to program :o )
[G1 Android Development] cojonesx:
I don't use APPS2SD, been using CyanogenMod since it came out.
[G1 Android Development] SimonNWalker:
I've been using CM builds also almost since day 1 but Im still at 3.2 and I just wanted to check with all the auto APPS2SD struff in the new version.

Thanks for the feedback.
[G1 Android Development] scotte9999:
I have been through all of the CM ROMs (okay, maybe missed a couple minor "unstable" point releases), and am using the ".nounion" method as well (just symlinks to get things to SD). I have not noticed any freezes, coma, or other weirdness either. I tried unionfs and aufs for a bit, but those quickly caused problems (very slow UI response, applications getting killed much too quickly due to OOM conditions, etc.).

My strong recommendation is to use ".nounion". Really, I see no downside other than (theoretically) not being able to use the phone with the SD card physically removed (big whoop).

(Aside: I do see a delay between the phone getting an incoming call, and the ringtone starting to play, but that's "always" happened, so I don't think it's CM-related issue.)

ScottE
[G1 Android Development] PageMaster500:
AppstoSD2 on Cyanogen

I posted this on the AppstoSD thread, but then I wasn't sure if this was a Cyanogen ROM specific issue on my part so I figured I'd ask here. I'm running the latest and greatest Cyanogen ROM and can't seem to get AppstoSD2 to work. The issue is the partitioning. I understand that this app will partition your SD Card for you, however when I run it and it says it has partitioned, it really hasn't. After a reboot and running AppstoSD again, it still says there aren't any partitions and lets me select partition sizes before running it and rebooting again.

Then I noticed at the beginning of the first post it mentioned

Apps2SD via AUFS (same as UnionFS) enabled by default! (3.3) and a warning not to run any other Apps2SD software because this ROM will do Apps2SD on it's own. Is this in any way related to why I can't partition using the AppstoSD2 application, or is that an unrelated issue?
[G1 Android Development] cyanogen:
These are immensely helpful. I think there are multiple things happening here, one of which is the dalvikvm changes I pulled from master.
[G1 Android Development] mianosm:
I'm using a class 6 sd card, apps2sd, and less than 30 apps on a custom theme.

I have never had a single problem...the roms have all been 100% for me so far.

If I run into any issues I'll be sure to run logcat though, if it helps. ; )
[G1 Android Development] dubbeld00:
To all the people over here... I've created a tool to get update packages only (not a FULL rom). You select your current version of a ROM, then select the version you want and it will automatically create an update.zip which you can flash.

Benefits of this solution are:

- You only have to download 2mb (or so) (you only download the changes)

- A much shorter flash process

- You only replace the files that are changed, so it won't write much to your phone memory (so it keeps your phone memory healthy)

I will also create an Android application which will Auto Update your device!

http://android.v-dh.nl/ Here you can get the update from 3.2.x to 3.4.x. Hope you all like it. I will add more ROM's if more people seems to like the idea.

Update from 3.4.1 to 3.4.2 (tested)

How does it work:

It will compare the version which you are currently using with the version you want. The files that have been changed or added, will be zipped to update.zip, if there are files deleted, they will be deleted from your device using the update-script. It will also set the permissions to the system files, and write boot img to your device, if this is changed. It will also auto-sign the package :)

I'll hope to get the auto-update script working for the upcoming 3.4.3 release.
[G1 Android Development] dwang:
I deleted everything in my dalvik-cache and had it regenerate. Not seeing anymore browser crashes so far. Ill keep the thread updated if I see it again.
[G1 Android Development] cyanogen:
Ok guys I've been testing stuff all morning and I am quite pissed right now :mad:

I can cause the phone to crap out by playing iMeem and loading the main xda-developers forum page (the HUGE one). This is with AUFS enabled. If I disable AUFS and use symlinks or a bind mount, it DOES NOT HAPPEN. I also tried patching in the older UnionFS, and it has the same problem as AUFS. So something does not like this union-mount. When I see the problem occurring, the IO wait is insane on the device (> 80%) and the lowmem killer is going crazy.

We are seeing this happen more and more often now that people are running memory-hungry home replacement apps and widgets.

So, here is my proposed solution:

FORGET THE UNIONFS/AUFS FOR APPS2SD!

I keep thinking about it, and we aren't gaining anything (other than seeing a huge "internal memory" size in "Phone Storage") by using a union-mount. I think a well written startup script that sets up bind mounts on startup (probably copying anything off of internal memory app/app-private before) would work 1000x better.

So here is what 3.4.3 is going to do:

1. No more union mount. I will modify the scripts to set up bind mounts correctly. Apps2SD will still be automatic, and it will be better.

2. An extra row in "SD card & phone storage" that shows you how much space you have on your secondary SD partition.

3. Rollback the bionic/dalvikvm changes I pulled from master- I don't like that segfault that was posted earlier.

4. Don't **** with vfs_cache_pressure, it seems to cause problems in low memory situations no matter if I set it to 20 or 200 (200 is what I'm setting it to in 3.4.1+).

5. Re-enable the nice kernel optimizations that you all know and love because they aren't responsible for the problem.

Thanks for your patience everyone. I'm working hard on this stuff so our phones are as badass as they can be, sometimes it requires a little trial-and-error, though.
[G1 Android Development] dwang:
Sounds good. I was never a big fan of unionfs, especially when symlinks never gave me any issues.

As far as home replacements. I've switched back to the default one and noticed a huge improvement in performance.
[G1 Android Development] uberingram:
Wow...I never would have guessed. I was never lucky enough to have DDMS running when this happened, very good find.
[G1 Android Development] cyanogen:
Honestly, this kind of thing falls under the category of "unnecessary complexity", and that's something we definitely want to stay away from.
[G1 Android Development] Daemonjax:
I'm liking the changes for 3.43

I like the upcoming changes for 3.43... especially the focus on stability and performance -- what initially drew me to this mod.

Whatever you decide to do, I'm fine with because you seem to know what you're doing :cool:
[G1 Android Development] i1fang:
when people ask me how is my G1 doing during JK1.2, all I can say is: Its still in baby stage.

When I flashed Cyanogen 3.3, I'm so proud that I went around telling my friends that its in teenager stage.

Guess a fine young man is what we are seeing soon.

Keep the good job rolling!
[G1 Android Development] TheDudeOfLife:
Thanks for your work. I'm interested to see the results from the bind mounts vs the union mounts. I had some weird problems in the past when I did a straight union mount on /data and /system/sd but all those issues were resolved with permission fixes. I haven't had time to investigate app-private issues this weekend.
[G1 Android Development] question.com:
crap just updated to the last version. ohh well, def lookign forward to the new version.
[G1 Android Development] bkmo:
What is the downside of this? Phone won't boot without SD card? What if SD gets corrupted? Just asking cuz I don't know.

Thanks for the continued support.
[G1 Android Development] dan0zone:
i removed the sysctl.conf and seems to have helped so far ,, waiting for your next update

GREAT work man ,, keep it up
[G1 Android Development] simms22:
I can't wait to try this new version . I don't do appstosd , so I have never had any problems with your roms . They are the best ! and keep getting better :) Anyways , than you for doing this for us :)
[G1 Android Development] Biodome:
Final Testing :o
[G1 Android Development] cyanogen:
3.4.3 is up, includes all the changes I mentioned earlier. See the first post for info. This ROM is indeed growing up :)
[G1 Android Development] Biodome:
Thanks dude. Flashing it now, and thanks for being on top of this so fast. Never seen someone patch a rom so quickly.
[G1 Android Development] P_Dub_S:
Thankyou for all the hard work you have put into making these Roms. Flashing now
[G1 Android Development] cyanogen:
Please let me know if crashes are still happening with this ROM. I am feeling pretty confident about it being fixed, though :cool:

The output of "mount" should now look something like this:

rootfs on / type rootfs (ro)

tmpfs on /dev type tmpfs (rw,mode=755)

devpts on /dev/pts type devpts (rw,mode=600)

proc on /proc type proc (rw)

sysfs on /sys type sysfs (rw)

tmpfs on /sqlite_stmt_journals type tmpfs (rw,size=4096k)

/dev/block/mtdblock3 on /system type yaffs2 (ro)

/dev/block/loop0 on /system/modules type cramfs (ro)

/dev/block/loop1 on /system/xbin type cramfs (ro)

/dev/block/mtdblock5 on /data type yaffs2 (rw,nodev)

/dev/block/mtdblock4 on /cache type yaffs2 (rw,nosuid,nodev)

/dev/block/mmcblk0p2 on /system/sd type ext3 (rw,noatime,nodiratime,errors=continue,data=ordered)

/dev/block/mmcblk0p2 on /data/app type ext3 (rw,noatime,nodiratime,errors=continue,data=ordered)

/dev/block/mmcblk0p2 on /data/app-private type ext3 (rw,noatime,nodiratime,errors=continue,data=ordered)

/dev/block/mmcblk0p2 on /data/dalvik-cache type ext3 (rw,noatime,nodiratime,errors=continue,data=ordered)

/dev/block//vold/179:1 on /sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1000,fmask=0711,dmask=0700,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8)
[G1 Android Development] dwang:
How do the bind mounts work? When I goto /data, I don't see symlinks to /system/sd/.
[G1 Android Development] sir*mez:
flashing 3.4.3 as i type... will report back...
[G1 Android Development] cyanogen:
I made the a2sd script clean up any symlinks. A bind mount just takes a path from an existing mounted filesystem, and makes it visible on another path. The command to create a bind mount is something like "mount -o bind /system/sd/app /data/app". I chose this over symlinks because I've had problems with app-private acting strangely that shouldn't be an issue with this method.
[G1 Android Development] simms22:
up and running on 3.4.3 ......

wow .... the roms TRULY keep getting better !

no wipe , clean install . ran the permission fixer just in case .

and its SUPER FAST !!! :D
[G1 Android Development] short/y:
I've been having problems with this and all of cyanogen's previous builds I've tried. I don't lose apps nor do I get into a reboot loop -- my phone never comes out of the android screen. I've gone in and looked at what's taking up all the CPU and it's always been the phone app (com.android.phone is the process, I believe). I've repeatedly rebooted and run fix_permissions and nothing clears it up. I've got an 8GB class 6 with a 7G FAT and a 1G EXT3 with app, app-private and dalvik-cache on it. A wipe used to address the issue but, with the switch to AUFS, it doesn't anymore. I know I can manually remove all the necessary directories and get it to work but I'm not a fan of reloading my 150 apps and all their settings. Since I have no real issues on JF's US 1.51, I've decided to just stick with it BUT, like you, I'm keeping my eye on this build. I'm particularly fond of what cyan's done with shutdown -- flushing the filesystem's cache and remounting everything readonly makes for a much healthier filesystem.
[G1 Android Development] dwang:
Cool!

I've had problems with app-private as well with symlinks.
[G1 Android Development] The Spirit:
one quick question.

i have only one available ringtone and one available alarm sound left.

is this normal, or have i done something wrong?
[G1 Android Development] cyanogen:
Read the first post- you need to download the audio resources and unzip the file to your sdcard.
[G1 Android Development] uberingram:
Normal. Read the OP.

Edit: I just noticed the SD Card Secondary Storage section in the Phone Storage section of Settings. That's god damn cool.
[G1 Android Development] cyanogen:
All of these issues should be addressed in the latest version now. Also if you get force-closes after installing and had a theme with more than 3 home screens (like the Hero theme), you need to reflash the theme afterwards.