yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] cyanogen:
Yeah, I think this is better than just showing you some huge number for "internal storage" that could be misleading.
[G1 Android Development] Amdathlonuk:
I propose all who haven't already done so, click on his link and donate him some beer money to support his development work..

Cyanogen, mine is on it's way, you deserve it.

:)
[G1 Android Development] dwang:
I'm noticing that "aufsd" is still running. Is that taking up any cpu or memory cycles?
[G1 Android Development] cyanogen:
It's just a sleeping kernel thread because I left AUFS support compiled in. I'll remove it for good in a future build. Shouldn't be taking up any resources.
[G1 Android Development] simms22:
ok , im running 3.4.3 . im not running apps2sd , and i show 6mb secondary memory . i never partitioned my sd card . how can i use this memory ?
[G1 Android Development] dubbeld00:
http://android.v-dh.nl/?m=Updates

For the last time promoting my script ;) select your version and then version 3.4.3 to update to version 3.4.3, it will do the same as the 44mb update of cyanogen, but it is only 4 mb (because it will only give you the files that are changed). So no SYSTEM wipe is done.

Hope someone likes it...

3.4.2 to 3.4.3 download link:

http://android.v-dh.nl/update/temp/3.4.2-3.4.3/update.zip (tested)
[G1 Android Development] short/y:
Backing up now and will flash in a flash. I'll report back in a while.
[G1 Android Development] jonbron:
the illest

flashing 3.4.3 at this very moment - i've never had a single problem with any of your builds, cyan, and i don't think i would enjoy my g1 nearly as much without your work. i hope other devs continue to build off of your.....

hold on it just finished booting up... damn this build is pretty crazy fast..

okay so it's showing 904mb secondary and 87mb internal - i'm guessing that means it's working correctly?
[G1 Android Development] cyanogen:
It's just using StatFs on the filesystem path, which is like using "du" in Linux. I should probably check if something is actually mounted there.

Going to add this to the OP if you don't mind.
[G1 Android Development] cyanogen:
Yep, the secondary storage is your ext partition.
[G1 Android Development] here.david:
I can say this is a fact on my G1...just updated to 3.4.3 with Hero 1.3.5 theme and forgot to clear the two end screens, which was pointed out previously, so had to update the hero twice as CM stated previously and this is the 1st time a 5 min update without any issues....:D...so far....

1. save hero 1.3.5 update as update_h.zip to root (fat32) sd card

2. save CM 3.4.3 update as update_cm.zip to root (fat32) sd card (for future)

3. save CM 3.4.3 update as update.zip to root (fat32) sd card

4. boot to recovery (three finger salute then home+end)

5. Alt-S

6. Alt-X

7. enter at prompt:

cd sdcard

ls (to see I am at the correct place, will see the updates listed if I am)

rm update.zip

cp update_h.zip to update.zip

8. reboot recovery

9. Alt-S

10. If I forgot to clear the left and right end screens, Alt-S again

11. Home+Back

12. Wait =< 5mins

So far - Perfectly update to current ROM and Hero 1.3.5, other than the block around the item clicked on...CM, new for me in 3.4.2...saw it listed and will live with it for now...as I have the Android as my wallpaper, which is green and might not have seen it previously...:)....
[G1 Android Development] dwang:
3.4.3 seems a bit slower than 3.4.2 to me, especially browser scrolling.

What were the changes you made to dalvik/bionic? I want to push those files from 3.4.2 to 3.4.3 and see if I get a performance increase.

Thanks,

Dave
[G1 Android Development] mikeyman77:
I wiped then installed 3.4.3. I installed power manager and IM+ and both of them are force closing. Does anyone else have this issue? This is the first time I have had a problem like this with cyanogen's rom.
[G1 Android Development] Crackbone:
I notice exactly the opposite. To me, the entire ROM is running faster, including all of the secondary functions, including the browser.

Much happier with this build, and no force close hangs...
[G1 Android Development] dwang:
Its faster to you because you were running aufs and now its switchedd to bind mounts.

I've been running symlinks all this time so I didn't get a performance boost from that.
[G1 Android Development] MarcusMaximus04@gmail.com:
Well, one thing that was gained is that you can move apps to or from the sd card freely, and, with aufs, it can be configured to do so automatically if the ext2 partition starts getting full. Not mad at you for taking it out or trying to argue, just pointing out one gain from unionfs/aufs.
[G1 Android Development] cyanogen:
I really like the AUFS/UnionFS setup, it's superior to every other a2sd method in theory, but there is something bad happening with it when the system gets low on memory. I don't know what it is for sure, but with the bind mount setup, none of these issues occur. Maybe it's just extra memory that it uses that is not accounted for by the OOM killer. I am really not sure. I am going to send the AUFS developers an email about what we are discovering, though.
[G1 Android Development] cyanogen:
Ironically, it seems I never actually added the new libdvm.so to any build. Heh, whoops. The one thing that is changed that you might want to look into is the ioscheduler. 3.4.2 switched to anticipatory (to try and eliminate this as a cause of the crashes), and 3.4.1/3.4.3 uses CFQ. CFQ *should* be giving better performance, but I would suggest just flashing or fastbooting the boot.img from 3.4.2 and letting us know your results.
[G1 Android Development] here.david:
oops

U

CM- for your feedback...Went to take screen shot and it does not work ...forced closed....
[G1 Android Development] cyanogen:
Can you get an adb logcat of it?
[G1 Android Development] dwang:
Ok, thats easy enough to do.

The problem is there doesn't seem to be an objective way to measure performance, so everything is just perception.
[G1 Android Development] sir*mez:
why isnt my phone showing me this info??
[G1 Android Development] cyanogen:
Try running the "fix_permissions" script from Terminal as root and rebooting. The first exception from the HTC framework apk not having a classes.dex is normal, though.
[G1 Android Development] cyanogen:
You don't have a "SD Card Secondary" section under "SD & phone storage"? Sure you flashed the right build? :)

OH your theme.. It's probably nuking my custom Settings.apk
[G1 Android Development] dwang:
Fastbooted the boot.img from 3.4.2 and I could immediately feel the performance improvement. Swiping between screens is faster, scrolling in the browser is faster, scrolling the market is faster.

All I did was change the boot.img to 3.4.2, system is from 3.4.3, and I didn't wipe.

Anybody else want to confirm this? The boot.img is already in the update.zip so no need to nandroid to get it.
[G1 Android Development] short/y:
Did that right after flashing. Sequence:

1) flash 3.4.3

2) without rebooting, go into recovery console

3) run fix_permissions

4) enter "recovery" in console to get back to boot menu

5) reboot

Et voila!

This is pretty much the same set of failures I've been seeing all along. I can't say for sure that I've seen the problem with the framework before but I've seen the unknown permissions and java failures.
[G1 Android Development] sir*mez:
will reflash and port the settings.apk with yours on the ported theme and will report back.
[G1 Android Development] cyanogen:
Hah, that is really interesting. Maybe we will switch back to that scheduler if more people report good results.. Like you said, it's almost impossible to benchmark these kinds of things.
[G1 Android Development] cyanogen:
You actually need to run "fix_permissions" after booting up the first time and getting the failures. Try running it again :) Otherwise, you might want to consider a wipe.
[G1 Android Development] mikeyman77:
Ok I have done some testing. On 3.4.3, power manager and IM+ both force close. On 3.4.2 and 3.4.1, both work fine. I am about to reload 3.4.3 and do a adb logcat after the force closes.
[G1 Android Development] uberingram:
I would but I'm on a work computer with no ADB or fastboot. Damnit. :(
[G1 Android Development] kvizz:
oh my, I LOVE THIS.

makes everything so much easier.

THANKS!!!

i had to flashed over 5 times because i kept messing up on trying to get the hero htc theme to work haha.

i finally got it to work. i have to many apps. over 100mbs and still 800mb more!
[G1 Android Development] dwang:
There must have been a reason why google chose anticipatory iosched because by default doesn't the kernel ship with CFQ iosched?
[G1 Android Development] short/y:
I've done that, too, but not on 3.4.3. But the other thing that happens, which is probably related to the permissions issue, is that com.android.phone starts eating CPU and then is eventually killed. I tried a wipe on 3.4 or 3.4.1 and, believe it or not, it didn't address the problem with phone! Focusing on the permissions errors, I even tried to use an XML editor to compare the old and new packages.xml but the changes were just too great for me to make anything of it.

With 150+ apps, I'm really not inclined to wipe and reestablish all those apps and settings. And I think the problem I'm seeing is probably the root of why a lot of people aren't able to use these ROMs and may even be one of the reasons we have to wipe in the first place.
[G1 Android Development] tricky76:
I successfully upgraded from v 3.4 and Hero Theme 1.3.5 but I did have some issues.

I removed all the icons from the far left and far right home screens and deleted the analog clock widget from my center home screen. I then rebooted into recovery (Cyanogen 1.1) and flashed the v 3.4.3 rom. I rebooted the phone. My lock screen came up along with my info from the Contact Owner program. However, after unlocking the phone, I immediately received an error that android.process.acore had to be force closed. I waited a few more minutes and still had the same error. I could not access my app drawer.

I rebooted into recovery and ran fix_permissions.sh and rebooted. Still the same error. I reflashed the 3.4.3 rom and rebooted, same error. I booted into recovery again and ran fix_permissions.sh.. still the same errors.

Finally, I rebooted again into recovery, but this time flashed the Hero 1.3.5 theme. The phone booted correctly without errors, however none of my icons were on the screen. I rebooted into recovery and rebooted the phone from there. My phone came back with all icons and apps in tact! So far so good... Note that I never performed a wipe.

Just a suggestion - if you look at the sigs in this thread, it seems that a lot of people are using the Hero Theme with this ROM. Would it be possible to maintain a separate "edition" of this ROM with the Hero Theme included? The Hero Theme compliments this ROM very well, especially because the ROM is so fast.
[G1 Android Development] geemboomba:
Tried it. I can certainly feel an improvement in overall speed.
[G1 Android Development] kvizz:
dope, just flashed 3.4.3.

works good so far.
[G1 Android Development] borodin1:
I second that.
[G1 Android Development] dwang:
Went back to 3.4.3 boot.img just to double check and its does feel slower than 3.4.2 boot.img.

Flashed back to 3.4.2 boot.img and its faster, at least to me. The icons in the market seem to load up quicker.
[G1 Android Development] P_Dub_S:
Im running Powermanager on 3.4.3 with no force closes. when I updated from 3.4.2 all I did was update with no wipe then ran fix_permissions. everything was working perfectly. Then flashed to the 1.3.5 hero theme and still no problems.
[G1 Android Development] mianosm:
2nd sd storage set disappears with themes.

My internal consistently seems to be decreasing...
[G1 Android Development] dwang:
Its because the themes overwrite the modified settings.apk from 3.4.3.
[G1 Android Development] Amdathlonuk:
Just downloaded the latest update and reformatted my class 6 with a 900mb Ext 3 partition.

I have now re-installed my 230+ apps and it is a HUGE improvement.

MUCH faster and totally reliable at present.

However the test will come as the caches ...etc start to build up I suppose.

Anyway I'll keep you posted but so far so good.

P.S. I have the Hero theme installed.
[G1 Android Development] P_Dub_S:
I think that's due to your theme overwriting the settings.apk as stated earlier in this thread.
[G1 Android Development] mikeyman77:
You using the free one or the full version?
[G1 Android Development] P_Dub_S:
Full version
[G1 Android Development] mikeyman77:
Ok, the wierd thing is that power manager works fine on 3.4.2 and 3.4.1, the only one that force closes on is 3.4.3. I even tried to put the 3.4.2 boot.img inside of 3.4.3. I have already ran the fix_permissions script as well. I also uninstalled the app and reinstall it. Doesn't work.

Perhaps it has something to do with the binded mounts.
[G1 Android Development] P_Dub_S:
I had a similar problem when i upgraded to 3.4.2 i had wiped before i upgraded and it made powermanager and weatherbug force close what i had to do was delete all the data in my EXT3 partition then reflash and reinstall which fixed it. Now when i upgraded this morning to 3.4.3 i skipped the wipe and it worked fine.
[G1 Android Development] mikeyman77:
I always removed everything that is on my ext3 partition before I update. Also another thing i notice is that the apps that I do install, do not show up in the app drawer.
[G1 Android Development] dwang:
But data isn't on ext3 flash. That's why u need to uninstall and reinstall to see if your problems are fixed.
[G1 Android Development] mikeyman77:
I normally wipe before I update and I make sure that /system/sd (ext3) is clean as well. I have never had this issue, this is the first build I have had problems with. Perhaps I should test w/o apps2sd.
[G1 Android Development] speoples20:
How do you delete whats on your ext3 partition?
[G1 Android Development] P_Dub_S:
I usually put my memory card in my laptop with ubuntu on it and delete the data in the EXT3 partition
[G1 Android Development] speoples20:
Is there a way to do it from the terminal or recovery?
[G1 Android Development] mikeyman77:
I use adb shell and goto the /system/sd directory and use "rm -r *" right before I issue a "adb shell reboot recovery" to boot in recovery to flash the rom.
[G1 Android Development] dwang:
Just tried installing power manager full myself and I can confirm the crash.

power manager full is a protected app so it could be related to the bind mounting as its saved in app-private.
[G1 Android Development] sir*mez:
ported your settings.apk to the ported theme i have and it worked beautifully. Excellent work cyanogen!!
[G1 Android Development] cyanogen:
There really should be no reason to have to reformat your SD card to update.
[G1 Android Development] speoples20:
I'll try, one this is weird my app-private data is for some reason missing so non of my protected apps work. Is there a way to put that back? If not I was just going to erase everything and start over.
[G1 Android Development] mikeyman77:
I would just start over.
[G1 Android Development] cyanogen:
Looks like I made a typo in the new a2sd script, it could be the cause of the Powermanager problem.

Try this from terminal as root:

busybox chown 1000:1000 /data/app /data/app-private /data/dalvik-cache

busybox chmod 771 /data/app /data/app-private /data/dalvik-cache

Guess I'll need to do a 3.4.4 then :rolleyes:
[G1 Android Development] dwang:
didn't work..

doesn't look like protected apps get installed into app-private...

I also tried to install i tweet from the market and it forces close too. I think thats a protected app as well.
[G1 Android Development] cyanogen:
What about after reinstalling the app?
[G1 Android Development] sir*mez:
my power manager is working with no force closes. in matter of fact nothing is force closing... so idk, everything seems right here.
[G1 Android Development] mikeyman77:
Ok I loaded 3.4.3 w/o apps2sd and power manager and IM+ both work fine. I will reload 3.4.3 w/ apps2sd and use those commands and see if it helps.
[G1 Android Development] dwang:
Nope..

if you cd to /system/sd/app-private, the protected apps aren't there. Existing ones are there, but if you install new from market they aren't there.

Are they being installed on the internal flash /data/app-private and somehow the bind is screwing things up?
[G1 Android Development] mikeyman77:
It must have something to do with the bind mounts. Cause they work fine w/o apps2sd.
[G1 Android Development] speoples20:
I'm having the same issue. I tried downloading baseball superstars and it downloads and installs fine but will not open, just force close. I checked the app-private and there is nothing there.
[G1 Android Development] dwang:
powermanger is installed correctly in dalvik-cache, but its not there in app-private nor app

# cd /data/dalvik-cache

cd /data/dalvik-cache

# ls *power*

ls *power*

data@app-private@com.acme.android.powermanagerpro.apk@classes.dex

# cd /data/app-private

cd /data/app-private

# ls

ls

com.agilesoftresource.apk com.rerware.android.MyBackupPro.apk

com.leapwan.accudial.apk

# cd app

cd app

# ls *power*

ls *power*

ls: *power*: No such file or directory

#
[G1 Android Development] mikeyman77:
That would explain why some of the apps are not showing up in the apps drawer.
[G1 Android Development] cyanogen:
I might not be able to troubleshoot this until I get my new G1 tomorrow because a few things crash on my half-working device (unrelated to this ROM). Like Market and the dialer :eek:

I have a feeling that it has something to do with the is_valid_apk_path function in installd. Should be fixable, though.
[G1 Android Development] mikeyman77:
This what adb logcat says:

I/dalvikvm( 597): threadid=7: reacting to signal 3

W/asset ( 123): Asset path /data/app/com.acme.android.powermanagerpro.zip is

neither a directory nor file (type=1).

W/PackageManager( 123): Failure retrieving resources forcom.acme.android.powerm

anagerpro
[G1 Android Development] dwang:
when a protected app is installed, it has two files. a zip file in app and then the apk in app-private. Neither of them are there.

It should look something like this. These are my existing protected apps, which are intact in the app/app-private directories.

/system/sd/app

# ls *.zip

ls *.zip

com.agilesoftresource.zip com.rerware.android.MyBackupPro.zip

com.leapwan.accudial.zip

# cd ../app-private

cd ../app-private

# ls

ls

com.agilesoftresource.apk com.rerware.android.MyBackupPro.apk

com.leapwan.accudial.apk

#
[G1 Android Development] mikeyman77:
Wierd thing is that it works fine if you do not use apps2sd. So it has to have something to do with apps2sd. Perhaps the bind mounts?
[G1 Android Development] Nedlinin:
Just wanted to bring some feedback to 3.4.3 -- I had been using 3.4 for a bit and was receiving a few force closes every now and then. Also had a problem with the phone running slowly randomly. With 3.4.3, I get very few force closes(mainly the market still force closes) and the phone feels quite a bit snappier.

Great release - Thanks cyan
[G1 Android Development] mikeyman77:
Are you use apps2sd?
[G1 Android Development] short/y:
Hmmm ... I think I'll try removing /data/data/com.android.phone and see if that gets me past my current hang. It may be that the hangs people like me experience when they cross ROMs (e.g a 1.51 US-based ROM to a 1.51 ADP-based ROM) is because the settings are incompatible from one ROM base to the next. I think I recall this being discussed elsewhere but I don't think anyone's come up with a solution other than just wiping.
[G1 Android Development] jinx10000:
I still have not experienced many freezes or force closes like others are reporting.

I have wondered if it is because I installed the Hero theme and maybe it overwrote a problem file. I saw where someone earlier had mentioned that they had the Hero theme and they were not having problems either. Probably a crackbrained theory.

I can confirm with 3.43 that I can no longer install protected apps from the market.
[G1 Android Development] mikeyman77:
Loading 3.4.4 now and will test.
[G1 Android Development] cyanogen:
I think I know why this is giving us an issue with bind mounts. It's because installd uses the rename() function in move_dex, and is silently swallowing a "cross-device link" error. Let me see if I can't implement something a little less braindead. Open-source is awesome :)
[G1 Android Development] mr_notorious:
Is it just me, or is anybody having issue with street view not loading? It seems like the street.apk is missing from this rom (3.4.3)...
[G1 Android Development] simms22:
Street view is not loading for me either ....
[G1 Android Development] uberingram:
Can you uninstall Maps and redownload it from the Market? It might fail if streets.apk is protected.
[G1 Android Development] mr_notorious:
Thanks for the confirmation. When I run "fix_permissions", an error comes up stating "chown: /system/app/Street.apk: No such file or directory"

First thing I did, but still no go.
[G1 Android Development] cidica:
wake up and 3.4.3 is out. just updated to 3.4.2 lastnight think I'll be waiting on this one.
[G1 Android Development] mikeyman77:
Yea 3.4.3 has an issue with protected apps if you are using apps2sd.
[G1 Android Development] uberingram:
Looks like it's protected then.
[G1 Android Development] firestrife23:
according to adb logcat, AudioPara_TMUS.csv failed to load, because it's missing. It's need for bluetooth. Other than that... 3.4.3 is one of a helluva stable build! Thanks for patching up ROM in timely fashion!
[G1 Android Development] short/y:
Well, removing the contents of /data/data/com.android.phone after flashing 3.4.3 didn't change anything -- phone still ate up all the CPU and then died. I'll have to get back to this later when I have more time.
[G1 Android Development] Amdathlonuk:
I'll agree with this, at present this ROM is bullet proof. Just a few protected app issues, but fix that and I think it's there.

I have been trying to get my phone to lock up for 3 hours or so now with no luck! :)
[G1 Android Development] g1201:
bro where you got the hero theme from and how do u install it
[G1 Android Development] Thats BS:
http://xdaforums.com/showthread.php?t=520629

Install like a rom- rename to update, boot in recovery, apply update.
[G1 Android Development] jinx10000:
http://xdaforums.com/showthread.php?t=520629&highlight=cyanogen

Flash it from recovery. If you have an analog clock on a home screen, remove it before flashing. You can readd after flashing.
[G1 Android Development] uberingram:
y0 br0s3ph, get it from the mad tight Theme forum: http://xdaforums.com/forumdisplay.php?f=450
[G1 Android Development] dwang:
I can confirm that stereo BT isn't working correctly. It pairs, but output is going to the speakers and not the BT headset.

Using BT for phone calls work, but for stereo it doesn't.
[G1 Android Development] simms22:
its the first thing i did .....

didnt work :(
[G1 Android Development] jinx10000:
Strange, bluetooth stereo is working fine for me. Listening to it through bluetooth headset right now.
[G1 Android Development] simms22:
i have a sharper image bluetooth speaker . it works , sound goes through it . BUT , sound quality is terrible . it seems like sometings missing.....
[G1 Android Development] dwang:
Ok, I unpaired and then re-paired and both phone calls and stereo are working now.

Sorry about that.
[G1 Android Development] jinx10000:
I have an Insignia headset. And the funny thing is I think my sound quality sounds a little better than normal. Probably just imagination.
[G1 Android Development] simms22:
it was .....

i had a cr@py quality song playing . my bluetooth works just fine , quality is good ! just missing the streetview :cool:
[G1 Android Development] Nedlinin:
I am using Apps2SD -- Ext3 partition formatted to 700mb on a Class 6 Sandisk card

I also noticed that the TTS Service force closes anytime it is called upon (AndNav2, Chomp for Speak Text, etc.)
[G1 Android Development] jinx10000:
I had same problem on an earlier build. Reinstall TTS library and it should work unless it is a protected app. There seems to be an issue with protected apps on 3.4.3.

TTS is working for me.