yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] rumsey:
Glad to hear it worked, I just recreated the issue and used recovery to move apps2sd and am booting now to see if it worked again.

Well, I'm not sure what causes the issue but its not exactly that. I think the recovery image just mounts the 2nd partition on the sdcard and moves the files there, it doesn't move them to "/system/sd" or anything like that. That's why it works for old and new apps2sd still.

edit: When I first posted that fix, I had restored a nandroid backup of CM5 and CM5 couldn't install apps either. The fix allowed CM5 too install to sd again. I recreated the issue by reflashing this ROM in the same order I did the first time (rom, wifipatch, theme, gapps, all without rebooting). This time I tried the fix from within CE and I'm happy to report it worked again and it can install apps2sd again.

Sorry it didn't work for you chunk, if you post some logcats of when you try to do an install, and when you try to move it to SD I can take a look and I'll be able to tell if you are having the same issue as me. If fixing it isn't a bigger deal to you than just having it working, you may be better off backing up all your apps/data/home screen/sms/mms/call logs with MyBackupPro, Titanium Backup, and Sprite Backup and starting off a completely fresh wipe of everything and just restoring. To me figuring out what is causing me this problem is actually a bigger issue than needing to use the ROM for any reason :)
[G1 Android Development] tsheeley:
What version of recovery are you using? Make sure you mention it in the full write-up once you have everything worked out.
[G1 Android Development] jsunkist146:
If you're still using the old recovery image it would also explain the backup/restore process not working correctly. Read the changelog on amon_ra's recovery (I believe 1.7.0).
[G1 Android Development] rumsey:
I was using amon ra 1.6.2, I'll post finer details as I close in more on the issue.

Thanks for the heads up I didn't know about the changes. The main change in 1.7 is to the restore features, however its also of note that amon ra removed the move apps to sd function in the newest recovery image so anyone who is going to try my workaround will need to flash 1.6.2 before doing so. Maybe chunk can let us know what recovery he was using and maybe try again with 1.6.2
[G1 Android Development] jsunkist146:
The workaround worked for me on 1.5.2. Also, the changes were made in version 1.7.0.
[G1 Android Development] motohip:
I think there might be a problem with the call volume for the other end. Everyone tells me they can't hear me. ???
[G1 Android Development] tsheeley:
Are you using a G1? Check the FAQ in my sig... at the bottom there is a fix.
[G1 Android Development] TheLaughingMan:
Hey guyz, do I need to wipe before flashing?

KTHXBAI :P lol :D

EDIT: by the way I'm totally kidding, READ THE FAQ PEOPLE!
[G1 Android Development] Argentum_90:
I think the coolest thing that you could do on this ROM is to make calls fast.

Since I rooted my Magic few months ago, I have never seen the Phone application working faster.

I mean, when I receive a call, Phone starts vibrating and 3 or 4 seconds later screen shows who's calling you and later the ringtone starts singing.

It's frustrating because you loose calls sometimes and it makes you to recall to the person.
[G1 Android Development] tsheeley:
I'm a little confused at the way this is worded... are you saying that the call speed has gotten better or worse with CE 2.2.1?
[G1 Android Development] T.C.:
Any Ideas?

Thanks,

T.C.
[G1 Android Development] chunkxzor:
Actually it was my fault that it didn't work, I didnt realize Amon_Ra's 1.7 didnt contain the apps2sd move and misunderstood what I was doing in the recovery. I just flashed 1.6.2 and used the apps2sd move and now everything works perfectly. Thanks for figuring this out rumsey. You and everyone else's help is very much appreciated.

EDIT: Hahaha I just saw what you posted after I left
[G1 Android Development] FatBoyExtraordinaire:
Yeah, it looks like I might have to take the plunge to Danger myself soon. I'll wait until 5.0.8 stable is released, than this will be updated, then I'll probably give it a go.
[G1 Android Development] TeeJay3800:
Right. When I posted that, those terminal instructions had not been posted.

Nope, no RAM hack.
[G1 Android Development] jsunkist146:
Sorry, that might have been a misunderstanding on my part, I hadn't realized the 'move aps2sd' option was removed in 1.7.0. I'm not positive as i cant do testing at the moment as I'm not at home, but I'm pretty sure the 'workaround' is just that. I believe you could run into problems when backing up/restoring in 1.6.2 does not use the same apps2sd method. (Note: I'm not very up to date on what all is involved in the new apps2sd besides the new folder locations, but I think thats the problem.) So in the end i think you would be best off updating to the newest amon and doing a reformat or the ext partition and reinstalling your apps from backup apk's (or titanium/mybackup) or installing fresh from market.
[G1 Android Development] rumsey:
I think I'm going to consider this issue done since the fix seemed to work for everyone that had the problem and I'm no closer to finding the real culprit (though I can reproduce the issue).

Anything below 1.7 should work but I suggest flashing 1.6.2 to do the fix then switching back to 1.7. As far as backup and recovery go, even though changes have been made I think you can still make backups and recover fine with 1.6.2. A regular nandroid backup shouldn't touch any part of ext partition anyway, although you might have issues backing up nand+ext until you switch to 1.7 (though you can still do it from recovery console or adb manually).

To sum up:

Q: Coming from CM5 and are unable to install apps to SD after flashing?

A:

1- disable apps2sd in settings

2- install an app from market or sd that is not currently installed (no updates)

3- re-enable apps2sd in settings

3- flash amon_ra 1.6.2, reboot to recovery

4- select wipe -> dalvik cache. select other -> move apps to sd, reboot

5- flash amon_ra 1.7, make backup

6- apps should now install correctly to SD
[G1 Android Development] tsheeley:
Thanks for the write-up, I'll add it to the FAQ since it does seem to "fix" the issue.
[G1 Android Development] s1n3rgy:
done and thank you it worked.
[G1 Android Development] shawayne21:
What happens when you put a theme on your phone that is large in MBs? does it take up space on your phone if you flash it and remove from sd?
[G1 Android Development] mightyab:
Apps2SD

Yes I did the full wipe and did both checking and unchecking apps2sd and still my apps say internal and won't move to the sd card. Should I just reformat my whole sd card again and start fresh over again?
[G1 Android Development] tsheeley:
The theme modifies parts of the ROM that are on the internal memory of your phone... so yes, it will take up a little more space on your phone. You can remove the file from your SD card if you want, but it won't change anything about how the theme is on the internal memory itself.

At this point I'd say yes... reformat and partition your SD, then follow the flashing guide in my sig. Also, to try and avoid any issues ahead of time, make sure you have the current Amon-RA recovery flashed as well.
[G1 Android Development] IluvBread:
So... I suppose I need a full wipe to go from 2.1 to 2.2.1 ?
[G1 Android Development] FatBoyExtraordinaire:
Have you tried it yet to see if it works? Haven't gotten aroun dto it yet. Hopefully tonight.
[G1 Android Development] brianius:
a few guys did, but i would suggest a wipe ;)
[G1 Android Development] brianius:
I'm sorry if this is a known issue, but i think i don't really have multitasking actually. Often i listen to webradio with XiiaLive (Droidlive), but when i go to another app, the music/webstream stops - and xiialive isn't running anymore (even by using the widget).

So is there any chance to get only 2 apps at one time running? I want to be able to listen to music, while surfing the web or using my workout app.

Thanks in advance! ;)

PS: Besides my mentioned 3d problems, everything is running perfectly and really fast on mt3g! Awesome work! :)
[G1 Android Development] Gen00:
Just everyone to know running perfectly on both MT3G and G1..
[G1 Android Development] boostnek9:
I absolutely love this rom! it's so quick !

I only have 1 issue..I can't for the life of me get the black theme patch to work!..

I flash the rom, flash the black patch over it and my phone stays stuck at the boot animation...nothing else! and trust me I waited at least 25 minutes and nothing...

what's wrong?
[G1 Android Development] LucidREM:
Black Patch

do you have enough space in /system? i have not actually used it but i know any theme or patch made needs extra room on /system
[G1 Android Development] PSP_Hacker:
Thank you for putting the hashes, this saved me from flashing a bad WiFi patch :D

I wish all devs would put hashes for their work.
[G1 Android Development] boostnek9:
1.did a wipe

2.flashed the rom

3.flashed the black patch

4 no boot :(

I have the DangerSPL if that makes a difference..I think it does due to how it partitions..
[G1 Android Development] tsheeley:
Try following the flashing guide in my sig. There is a step in there about moving all but the default ringtone to your SD card. You probably ran out of space in /system on the internal memory.

Glad it was so helpful!
[G1 Android Development] tsheeley:
Haha!

I just saw the 2 faq tags for this thread. That's pretty funny. Many thanks to whomever did the "best faq" one. :D
[G1 Android Development] Nagoki:
CE 2.2.1 is very, very snappy, but is there a 633 mhz version of the multitasking kernel?
[G1 Android Development] tsheeley:
I didn't notice before that your sig says you have a Rogers phone... is that 32A or 32B?
[G1 Android Development] TeeJay3800:
Is anyone else noticing that even though by default CE2.2.1 has a "multi-tasking" kernel, that apps close on their own more than before? With all other ROMs I've used, including previous versions of CE, apps like the browser would generally remain open in the background until I manually killed it. Now, the browser closes almost immediately after pressing home. No, I'm not using swap, but that was never necessary before for simply keeping one app like the browser open all the time. Should I change kernels?
[G1 Android Development] eNNtOXX:
i have noticed this too but not with all apps (maps, settings, ...)
[G1 Android Development] TheLaughingMan:
lol, "read the faq" was my addition :P
[G1 Android Development] iamanalog:
I've noticed if its not a stock program it closes.. like the music player will stay in the background playing normally, but tunewiki will crash as soon as i hit home.
[G1 Android Development] motohip:
I have a MT3G. I think it was a fluke. I think I was in a low coverage area cause it seems to be fine now.
[G1 Android Development] TeeJay3800:
I was gonna say, I've never had any audio problems on my G1 since upgrading to 2.2.1. That's why I didn't think that audio fix zip was necessary anymore.
[G1 Android Development] Gen00:
Teejay did they come out with adw 0.7.8 replacement for the MT3G.. Becuz i remember u saying it was not out for this ROM	yet..

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

Sent via the XDA Tapatalk App
[G1 Android Development] Argentum_90:
Same as bad as always. A Magic with non oficial ROM is always slow calling.
[G1 Android Development] TeeJay3800:
It's actually been out since the 9th, but it was designed for CM5.0.8, so when flashed to a CM5.0.7 based ROM (like CE2.2.1), it didn't actually install. However, all you have to do is enter the following in Terminal...

su
mount -o rw,remount /system
rm /system/app/Launcher.apk
reboot recovery

...and then flash the zip.

Worked great for me. You're left with the only launcher on your system being ADW 0.7.8.
[G1 Android Development] nowusman:
I am desperate to have this ROM... can anyone help please????
[G1 Android Development] ukG1freak:
i think you need the patch for the 32A board dude
[G1 Android Development] tsheeley:
Try turning off vibrate, and if you are using non-stock ringtones, try moving them to /system/media/audio/ringtones. I've tested it with my home phone... the trackball lights up right away and the caller info pops up usually before the 2nd ring.

You need the 32A patch... there is a link to it in the FAQ in my sig.
[G1 Android Development] tsheeley:
I've noticed it too. Having swap on does make a difference... but it seems to be unstable for G1s. I'm not really sure what other kernels we could try.
[G1 Android Development] Gen00:
Thanks it worked perfectly..

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

Sent via the XDA Tapatalk App
[G1 Android Development] rumsey:
Yeah I have this same problem with sipdroid closing in the background all the time and not picking up my incoming voip calls. Its a problem in CM5 too, even with the multitasking kernel. I don't really have any other ideas, seems to be one of the few downsides of moving to 2.1 from 1.6 based roms.
[G1 Android Development] txspaderz:
After checking into this, this is definately coming out through my headset, instead of my speaker.

The same thing for my ringer.

HALP
[G1 Android Development] mr_deimos:
This fix did work for me, but i think i've found the cause of the problem and a faster solution.

When apps2sd is broken not only i couldn't install apps but also i wasn't able to uninstall them: OS claimed they were uninstalled properly but were back after a reboot. This led me to believe that this is simply a problem with directory access premissions. So i checked permissions before and after applying the fix via recovery, and here are the results before fixing (a2sd borken):

# cd /sd-ext
# ls -l
drwxr-xr-x 2 root root 3072 Jun 11 16:38 app
drwxr-xr-x 2 root root 1024 Jun 7 11:29 app-private
drwxr-xr-x 2 root root 12288 Jun 11 16:37 dalvik-cache
-rw-r--r-- 1 root root 14612 Aug 1 2008 fr-patch132.txt
drwxr-xr-x 2 root root 1024 Nov 18 2008 lost+found
drwxr-xr-x 2 root root 1024 Jun 11 16:37 userinit.d

And after (a2sd working):

# cd /sd-ext
# ls -l
drwxrwx--x 2 system system 4096 Jun 11 16:30 app
drwxrwx--x 2 system system 1024 Jun 11 16:27 app-private
drwxrwx--x 2 system system 5120 Jun 11 16:30 dalvik-cache
-rw-r--r-- 1 root root 14612 Aug 1 2008 fr-patch132.txt
drwxr-xr-x 2 root root 1024 Nov 18 2008 lost+found
drwxr-xr-x 2 root root 1024 Jun 11 12:29 userinit.d

Note that while a2sd is broken, the app, app-private and dalvik-cacke dirs belong to user root and group root, while they should belong to user and group system.

So, we just need to change the owner of these directories and we're set. Just execute these two commands in a root terminal (i used adb but recovery or terminal app will work as well):

#cd /sd-ext
#chown system:system app app-private dalvik-cache

You don't even need to reboot. I also noticed that access permissions are a bit different with a2sd broken and working. you can fix that by a third command:

#chmod 771 app app-private dalvik-cache

Note that even without this last step apps2SD will work and i'm not sure if it's really necessary.
[G1 Android Development] tsheeley:
Awesome write-up! I'll point the link in the FAQ to here instead.
[G1 Android Development] drklink:
I'm having issues with my camera!!!! O_o

It worked for like the first day, then it always force closes

HELP!!!

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

Sent via the XDA Tapatalk App
[G1 Android Development] mr_deimos:
Oh, and by the way, you mention in your faq that it is a no-wipe upgrade from CM5 that breaks apps2sd. For me it was actually a no-wipe update from openEclair 2.1 to 2.2.1 that seemed to have caused this problem. Or at least that's when i noticed it. Maybe using an ancient version of ammon ra recovery to backup/restore a few times also had a part in this trouble, but for me it definitely wasn't caused by cyanogenMOD rom.
[G1 Android Development] rumsey:
Good eye! It may be worth adding those permissions commands to a script that runs on the roms first boot to save time.
[G1 Android Development] tsheeley:
I'll change the wording and leave out mention of the transition from CM breaking apps2sd... just that not wiping can break it. Thanks for the tip on that.
[G1 Android Development] eNNtOXX:
this is brilliant thanks for the follow through
[G1 Android Development] qwerty3656:
rwsystem

When I type rwsystem in terminal it says: "rwsystem: not found"

I've run the firerat patch. When I try to run the patch again it says:

"looks like /system/bin/remount already exists I'm not going to replace it"

FWIW - I reflashed and started over. I get that "looks like /system/bin/remount already exists I'm not going to replace it" error even on the first run of the fr-patch132, so that means that /system/bin/remount is in the base canon ROM (and the fr-patch is not expecting it to be there).
[G1 Android Development] tsheeley:
Yeah, I noticed that too... not sure what the problem is with that. I literally just updated the flashing guide to have the full command to remount /system as rw. Sorry about the confusion.

Edit: For ****s and giggles, I just dropped into terminal and tried 'remount'... it gives some usage instructions... but following the usage guide doesn't produce any results either.
[G1 Android Development] tsheeley:
Thanks for the update on that. I took out the 'remount' part all together.
[G1 Android Development] txspaderz:
Bump, any suggestions? This was a wipe + flash also
[G1 Android Development] LucidREM:
AutoMod

did you try modifying the files as suggested?
[G1 Android Development] txspaderz:
I thought I replied to that, I'm sorry. I tried to do the changes, however his webserver hosting the csv files wasn't up.

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

Sent via the XDA Tapatalk App
[G1 Android Development] TeeJay3800:
This has been happening for me off and on ever since my first Eclair ROM (CE2.0). That means on both CM-based and non-CM-based ROMs. I'm not sure if the Louder Volume Hack is the best solution though. The reason for that is if the ringer is coming out of the headset speaker, that speaker is not meant to be very loud. Sound coming out of it is meant to be audible with your ear pressed directly against it. So it would seem that using LVH to artificially increase the volume could damage that speaker. The best solution is to fix the bug so sounds come out of the appropriate speaker.

Try running fix permissions.
[G1 Android Development] Gen00:
I dont understand why so many people r having so many problems with this ROM ive had it on my MT3G for about 2 weeks n on my G1 for about a week now n i haven't had any problems.. Everything working perfect.. Well i hope everyone gets there phone fixed with this ROM becuz its GREAT..
[G1 Android Development] sleepyfu:
thanks to you!

Could some of you with and without the wifi patch flashed post the kernel version. I've flash the ver7 non-over clock (cm-2.6.33.34-mt-v7-signed) from this thread by dumfuq. Even tho it's non-over clock, it's still scaled up to 576, I've since backed in down 245min/352max. it's running this ROM just fine.

FYI, MT3G's wifi worked just fine without the wifi-patch.

*edit mine= settings>about phone>kernel version> 2.6.33.4-cyanogenmod-jp@eddie #1
[G1 Android Development] TeeJay3800:
I'm just curious, why would you set the max to 352? The processor's non-OC'd max is 528, so it's perfectly safe to run there. I'm sure your battery life is better, but the Dream/Magic are none too fast, so normally people try to get everything from these phones that they can.
[G1 Android Development] asb123:
is anyone else noticing bad slowdowns after about a day of use? requiring a reboot to speed back up again
[G1 Android Development] TeeJay3800:
Yes, absolutely. Exactly as you described. That's somewhat normal with all ROMs, but it's especially true with CE2.1.1.

This ROM is very very good, but it definitely has some quirks that I haven't experienced with other ROMs.
[G1 Android Development] sleepyfu:
Well, I am actually testing to see how much battery the 352mhz setting is gonna save.

Normal usage, with compcache on and using home key as much as possible to keep apps in back ground, I found 352mhz to be "fine" during work hours where I need the phone for calls and emails what not, and stay charged. ( i don't work in a office)

You're right, 528mhz is proper for this CPU, and with that, this ROM flies.
[G1 Android Development] tsheeley:
The overclocked multi-tasking kernel that Cannon is shipping out with 2.2.1 can go to 633mhz.

I was bored at work today so I reved it up... it was speedy as hell, but twice my phone locked up while the screen was off and I had to yank the battery.

If you go slightly lower to 614mhz, it stays stable and hasn't locked up yet on me.
[G1 Android Development] drklink:
Try running fix permissions.[/QUOTE]

I'm sorry, but how do I that?

I'm still new at all of this....

Do I run the terminal app and type something in?

If so... then what? And do I need a "fix permissions" file in my sd card?

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

Sent via the XDA Tapatalk App
[G1 Android Development] tsheeley:
The OC'd kernel... 2.6.33.4-cyanogenmod jp@eddie #11 ... with wifi patch.
[G1 Android Development] sleepyfu:
I have not notice that, maybe even the other way around. I don't have swap/ext on, not sure if that helped.

Quick question, can you dismount SD at well when swap is on?
[G1 Android Development] sleepyfu:
Ok, so I am running on a different kernel. It's capped at 576mhz.

Maybe one day there will be kernel bible thread like the one for ROMs.

PS. kinda wish Firerat would be on this CE2.2.1, who knows what he's got up his sleeve.
[G1 Android Development] TeeJay3800:
I think you've confused kernels a little. The kernel that came with 2.2.1 can go up to 825 MHz.

So 614 is working well for you? Maybe I'll try that. For the last couple of days I've had the max at 576 and it's been running fine, but you can never have too much speed. :D

Simply open Terminal, enter 'su', and at the # promt type 'fix_permissions.sh' and press enter.
[G1 Android Development] boostnek9:
'

I don't want to correct you by all means but shouldn't it be

'su'

sh /sdcard/fix_permissions.sh

if I'm wrong this is a learning curve for me as I'm new to this!
[G1 Android Development] boostnek9:
I have a question for all you knowledge overloaded Android gurus out there lol

Is it normal that I flash this rom and it wont boot without flashing a kernel on top of it?

I tried just flashing the rom and it wont boot unless I flash pershoot's kernel or bcook's kernel.

Can I bring my Dream to 614Mhz? or is 576 the max due to undervoltage?

(I have 32A EBI1)
[G1 Android Development] TeeJay3800:
Nope. Just enter fix_permissions.sh at the root prompt.
[G1 Android Development] boostnek9:
Cool! well thanks for clearing that up!
[G1 Android Development] drklink:
Simply open Terminal, enter 'su', and at the # promt type 'fix_permissions.sh' and press enter.[/QUOTE]

Ok... I did that (didn't have to add .sh) and it "scanned"

But that didn't fix the camera problem....

When I try to open the camera, it says "process com.android.camera" idk if that helps

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

Sent via the XDA Tapatalk App
[G1 Android Development] tsheeley:
On this ROM, along with the main CM branch, you have to flash an EBI1/32A patch... which might actually just be a kernel. There is a q/a in my faq with a link.

Once you flash the patch, I'm not sure what range you'll have for overclocking. But, if you're able to OC it, I'll mention it in the faq.
[G1 Android Development] tsheeley:
Ok... I did that (didn't have to add .sh) and it "scanned"

But that didn't fix the camera problem....

When I try to open the camera, it says "process com.android.camera" idk if that helps

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

Sent via the XDA Tapatalk App[/QUOTE]

There is also an option to run fix permissions from RA's recovery, you could also try it there.
[G1 Android Development] tsheeley:
Nope, didn't confuse them at all. It's true, it physically can go up to 825, but per the kernels thread it won't boot unless you scale it down. I think 614 is pretty close to the highest it can go without becoming unstable.