yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] usmc2k:
yea u need to reboot
[G1 Android Development] shotad:
when i try to move with ASTRO it won't let me...would i need to do it in terminal? if so, what's teh command?
[G1 Android Development] lazaro17:
just switched back to 3.7.1 and got that good old cyanogen speed back.

me and my friend were having slow downs on both are g1's with 3.7.2.

not running compcache. hope 3.7.3 fixes this for me!

keep up the great work cyanogen!
[G1 Android Development] usmc2k:
Follow this tutorial....... just use the userinit.sh u have: http://xdaforums.com/showthread.php?t=537236
[G1 Android Development] shotad:
nvrmnd...i don't have busybox. :rolleyes:
[G1 Android Development] vikings1928:
Hakeem5, I also have this problem sometimes. What seems to work is after you start your download you need to sign in to your google talk, it is an app in the app drawer. Let me know if this works out for you
[G1 Android Development] bkmo:
After playing 20 questions you are not even running the proper rom? WTF
[G1 Android Development] o2ak:
I meant just the homescreen. I still want it to autorotate. Ah, not that big of a deal anyway...
[G1 Android Development] robpet2:
good job on the new release...

when i get sick of Hero rom again tomorrow, i will flash over to the 3.6.6

thank you for the new recovery img.. last backup was 3.6.5, so its easy as

nandroid restore, then flash 3.6.6 and Bammm... back in action !!!!
[G1 Android Development] ScottGood:
Cyan,

settings>sounds & display>ringer volume causes force close

This "pesky" F/C is not a real bit deal, SO take you time fix it when you get to it, we are just putting your newest version through it's paces.try to give us a weekend to find a few more issues befor updating please? I'm begging you.
[G1 Android Development] osho741:
Ok would it be possible for somone to post a new inituser.sh file that could be copied over to system/sd for people who have the autoswapper script running to make it simpler for us noobs and less tech saavy? With short instructions on how to disable swap before its copied over?
[G1 Android Development] cyanogen:
Settings bug.. Yeah, probably need to recompile some apps due to the resource ids changing. I'll fix it and upload a 3.6.7.1 I guess. Might wanna hold off on flashing 3.6.7 for now.
[G1 Android Development] revwillie:
FC here too, but I almost always use the volume rocker keys on the side for this function so I'd say it's a low priority.
[G1 Android Development] bkmo:
This is a pretty detailed explanation:

http://lwn.net/Articles/334649/
[G1 Android Development] bkmo:
Looks like a new theme template then too...right?
[G1 Android Development] ScottGood:
My userinit.sh

Download

Rename userinit.sh

create c:\shfile

create c:\shfile\backup

copy userinit.sh to c:\shfile

open CMD prompt

adb pull /system/sd/userinit.sh c:\shfile\backup

adb push c:\shfile\userinit.sh /system/sd

adb shell reboot

Done
[G1 Android Development] _Kyros_:
Could this be JF your talking about?, because that would be legendary. You guys should really consider teaming up since it's already being done in other ROMs like Hero and besides that would really take a load off of you Cyanogen.
[G1 Android Development] Ohsaka:
What we could all do that would help Cyan a ton is come up with a list of test cases for a new build. Many of us have found little issues here and there. We should compile a list of them all. Someone should start a new thread called "New Rom Community Test Case List". I would start it, but I wouldn't have the time to maintain the first post.

Examples:

-Start camera app and take a picture

-Start camcorder app and take a video

-Run Tether Wifi for Root users app

-Settings -> Sounds and Display -> Ringer Volume up and down

-Start Market, check My Downloads

Would probably be a long list, but after devs post a new ROM update, there will probably be at least one person in the community willing to perform all the tests and give the new ROM a "Community Tested Certification" seal. :)
[G1 Android Development] tekkitan:
Doh! Just flashed :)

I'll wait before setting up I suppose.
[G1 Android Development] osho741:
Ok thank you that's very helpful!
[G1 Android Development] cyanogen:
Most if not all of these problems have been because I ****ed up the resource ids in the framework. They are finally back to how they should be now, but I didn't copy the recompiled apps back into 3.6.7. Fix is on the way.
[G1 Android Development] dwang:
you need to delete the 1st couple of lines that enable the sdcard swap partition.

I've attached my userinit.sh file
[G1 Android Development] usmc2k:
Or maybe Cyanogen has Been workn with JesusFreke this whole time : O !!!!!!! ; )
[G1 Android Development] bkmo:
Do you really want to enable the first swap device on the SD card? Looks to me that compcache should be handling it as a backup device on its own. I also think that the backup device is not needed as it is much slower than the ram cache. YMMV
[G1 Android Development] drpfenderson:
This would be amazing. Although, I don't mind flashing every day or two (gives me an excuse to tinker), easy updates through the system would be fantastic.

Especially the ability to choose upgrades based on a stable/unstable basis - selective upgrading. But that's fantasy.

In reality, flashed over to 3.6.7 and enabled Compcache.

This ROM is somehow snappier. *lesigh*

Confirmation on the Volume force-close as well. No biggie though.
[G1 Android Development] dwang:
yeah I removed the backing_swap from the original post.
[G1 Android Development] ScottGood:
Opps my bad, thanks for the edit,
[G1 Android Development] cyanogen:
Ok, 3.6.7.1 is up. This fixes the force closes that were reported. Flash away, this should be rock solid.
[G1 Android Development] G1-evolve:
Ever since3.6.5 updated I STILL can't download in the Market. Says "starting download" but won't download. I tried

SU

chown system.system /data/app

chown system.system /data/app-private

reboot

still nothing.
[G1 Android Development] vikings1928:
Try logging into google talk. i know it sounds wierd but it works for me
[G1 Android Development] shotad:
jeez that's why i just put busybx. i'll try later.
[G1 Android Development] clefster:
Since I moved to CyanogenMod from a Haykuro build, sometimes when I get a phone call the screen won't wake up until I answer (so I can't see who is calling). Similar thing happens sometimes for alarms. Any ideas?
[G1 Android Development] angelogiuffrida:
I know the answer.

It's 'debugging USB mode on' that causes the problem. I've got an Alpine headunit and it has the same problem.

Turn off the USB debugging mode and you'll lose the ability to get root. It's a lose-lose situation. :(
[G1 Android Development] shotad:
give up on userinit.sh...seems like it wont work after i did the busybox. oh well...i can deal with battery drain. :D:D:D
[G1 Android Development] Lollipop_Lawlipop:
I believe this is working.

Testing it some more to see if this fixes the heat problem.

4GB class 6 card

Edit: Definitely not as hot as before. Will check battery life
[G1 Android Development] oldsk00lz:
Just following up on this one since I said I would test this out.

Prior to this my phone was very slow to charge. I charged to 100% then unplugged and used wifi for email and browsing. The phone started draining. I charged back to 100% and th rerbooted. It has been 9.5+ hours and power is at about 33%. Maybe the battery meter gets all wacked when its rebooted and not fully charged.

Anyways, I'll do some followup tests to see if this really helps, or if its random luck. Thanks...

-oldsk00lz
[G1 Android Development] sputnik99:
I have this issue without coming from haykuro.

I am on 3.6.5.
[G1 Android Development] facelessuser:
I noticed on this build that my wifi never cuts off when sleeping. I don't recall this being the norm and probably contributing to my battery drain. Spare parts shows wifi has been running my battery down for 99% of the time.
[G1 Android Development] lukekirstein:
Change-able in your Wifi Settings by pressing Menu>Advanced in the "Wifi Settings" box.
[G1 Android Development] _Kyros_:
Everything is working great as usual including battery life, here's a another suggestion for people having battery life issues (some may already know this) first drain your battery all the way down till it turns off I mean by using everything that would drain the hell out of it and when it turns off plug in the charger and let it chill, check on it periodically so you know when it hits 100% exactly (or when led turns green) and when it does let it charge to 2 hours extra (exactly) then unplug your charger and turn off your phone (don't just reboot) and keep it off for about 10 secs. turn back on and use it as normally you would but I suggest doing the whole process again at least 2 times. It works great for me, I charged my phone about 2-1/2 hours ago full 100% and only lost 2% since then (normal activity).
[G1 Android Development] Binary100100:
Just wondering... but why do you have two fat32 partitions?

Do you have access to both partitions on your sdcard and if so, how? If not, then aren't you just wasting space on your sdcard?
[G1 Android Development] nxt:
Google Gears borked?

3.6.7.2 Google Gears seems to be broken. Google website no longer gets location or even asks to enable it. Google Mail (web) the link to "faster gmail" is there, but clicking it doesn't do anything, won't install google gears.

Anyone else notice this?
[G1 Android Development] Binary100100:
Mine is alright. I wonder if you try resetting the defaults.
[G1 Android Development] Binary100100:
I also went back to swap (swappiness 20) and it runs lag free.

With compcache I would get lots of lag and a hell of a lot of force close/wait errors with programs that I wasn't even running. Example would be while I'm about to call someone the google maps app would popup forceclose or wait error. And a lot of home.acore forceclose/wait errors. Since I went back to swap... perfect.
[G1 Android Development] tep065:
from the accessory forum :

http://xdaforums.com/showthread.php?t=522146

Conditioning the Li-on battery by draining it to 0% and recharging and then draining to 0% is rather harmful to the battery. Lipo and Li-on cells do like going below 3.0-3.2V. The Nominal Voltage of the cell is 3.7V, a fully charged cell is at 4.2V-4.25V or so. Dropping it below 3.0V cause more harm to the battery then good. (Again this does not apply to G1)

Try to avoid draining the battery all the way if you are not able to charge it. Most phones have a cut off point, and my guess is for the G1 battery, it's 3.2V, or I hope it is (actually, it's 3.5V as you will read about it in post 11). But you use the phone to where it cuts of, and are not able to charge the batter for a few days, then that could drop the voltage to below 3.0 (over time). I've seen people do this when they use multiple batteries, and end up killing all of them because they let them sit while fully discharged. Big no no with Li-ons.

LI-on doesn't suffer from memory loss , charge them whenever possible. They do how ever become uncalibrated. Meaning if you constantly plug it in at random discharges (which is perfectly fine), the state of charge may differ from the actual charge gauge. Simple problem to resolve, Drain the battery too 3.2V ( I will post if draining the battery on the g1 to 0% is 3.2V or not) and fully recharge.

AND....

http://xdaforums.com/showthread.php?t=522146&page=2

Background on battery ratings: Batteries are rated in mAH aka Milliamp Hour, or how much power/charge a battery will hold. How is this measured? I won't go into details so will just give a run down version of it. Batteries are rated from their lower cutt-off voltage to the maximum voltage. The lower cut-off voltage for Li-ion and Li-po is 3.0-3.2V (3.2V being ideal).

The mAH rating is the amount of charge that it took to take the battery from 3.2V to 4.2V. In the Li-ion case, the lower cutt-off is 3.2V, the Nominal voltage is 3.7V and the maximum voltage is 4.2. Anything under 3.2V is over draining and anything over 4.2 is overcharging.

Why do I bring up the above? to give you an idea of how these batteries get rated.

Often companies will rate their batteries from a lower cut-off point to have HIGHER CAPACITY RATING. For example, if I Charge a li-ion cell from 3.0V to 4.2V, it will take in extra capacity as opposed to if I charge it from 3.2V to 4.2v, It just looks good on paper and spec sheet. This happens often. same with AA rechargeables, the lower cutt-off range is usually 1.0V but often companies will rate from .9V to achieve higher numbers. You will never see this disclosed on the battery, you'll just see the rating. (It will never say Capacity 1800mAH from .9v) etc.
[G1 Android Development] stellarman:
So, what is the change you are trying to test here? I looked at the file and it seems to me to be almost exactly what I have in my userinit.sh file now. The only thing different is that your file is not setting up the backing_swap on the linux-swap partition.

Am I missing something?

Or is this a test of the placebo effect? :rolleyes:
[G1 Android Development] stellarman:
I have used a similar "reset" method in the past and it has made a big difference for me.

I must say, however, that even after using this "reset" method, I am still not getting anywhere near the battery life I used to get on CM versions back around (I think) 3.4 (or so). I could go back through the old thread and see when the change occurred, as I commented on it in the forum at that time.

I really hope Cyanogen's theories and studies on this pan out. It would really be great to get back to being able to go almost two day (36 hours) on one charge.
[G1 Android Development] rob.turner:
Problem mounting SD card after flash

I'm having the same problem here. I'm fairly new to this, just got my G1 2 weeks ago, so it's entirely possible I've screwed something up somewhere.

Just flashed CM 3.6.7.2 from a clean wipe after trying the JesusFreke 1.5.1 ADP (had no problems with JF, other than it slowing down a bit after using Apps2SD 2). I've got the latest Radio and HardSPL 10.95.3000, and Cyanogen's Recovery 1.3.1. Followed THIS THREAD to partition my stock 1GB sdcard with 768mb fat32, 200 mb ext3, and 32mb swap, then flashed the ROM. Haven't set up swap yet. I got the "may need to update fstab" message mentioned in the post, but I don't know if I'm supposed to do anything about it. I did the partitioning in the recovery terminal, I'm still wrestling with ADB working correctly(device shows up where it's supposed to in my device manager, but won't mount in the command prompt).

When I plug in the USB cable it says "USB Connected" and when I press Mount, it flashes 3 notifications: "Turn Off USB Storage", then "Preparing SD Card", then back to "USB Connected". I'm able to put the updates onto the card via my laptop's card reader and then flash them in Recovery, and the recovery terminal can see the SD card to run Parted on it, and the Total and Available Space shows up in Settings, so I know the phone can see the card, but for some reason the card refuses to mount.

In Settings -> SD card and Phone Storage, under SD Card, it shows 730MB total, 730MB available, and the options for Unmounting and Formatting are grayed out. I have a new section for SD Card Secondary, which I haven't seen before, it shows 178MB total, 133MB available. The already used 45MB suggests to me that A2SD is enabled and has already moved the stock apps, as I have not yet installed any new apps for it to move. Then there's the Internal Storage section, showing 72MB available.

I think my problem lies somewhere in my card formatting technique, as everything else is pretty straight forward, but again, I'm relatively new to all this, so I'm not sure. If someone could point out what I did wrong that would be awesome. I'm sure it's a simple fix and I've just over analyzed it. For now I'm going to start over from scratch, to see if I can't stumble upon the answer. Sorry for the long winded post, just want to get all that info out there.
[G1 Android Development] :
anyone else encountered this "problem"?

When i recieve a call, it takes 3-4 sec to show up the caller info (but the phone is already ringing)

This is realy anoying when you have to wait, to see who is calling.

Does the Phone app take so long to come up?
[G1 Android Development] Molinari:
Market F/C

Just flashed to the latest 3.6.7.2 now the market force closes, I did clear the cache, same deal.

Any ideas or must I wipe and start from scratch??
[G1 Android Development] ZilverZurfarn:
Some pages back I reported/pleaded for help on my camera trouble. In short, I lose the camera app after every ROM update and have to manually install it after rebooting - sometimes Astro works, sometimes I have to use ADB.

I think I've got a lead on why. This is from the installation log:

E/PackageManager( 4145): Bad package setting: package com.android.camera has shared uid 10002 that is not defined
E/PackageManager( 4145): Bad package setting: package com.android.providers.media has shared uid 10002 that is not defined
E/PackageManager( 4145): Bad package setting: package com.android.providers.downloads has shared uid 10002 that is not defined
E/PackageManager( 4145): Bad package setting: package com.android.providers.drm has shared uid 10002 that is not defined
E/PackageManager( 4145): Bad package setting: package com.htc.album has shared uid 10002 that is not defined

and

W/PackageParser( 4145): Problem in package /system/app/Camera.apk:
W/PackageParser( 4145): Unknown element under <application>:
W/PackageManager( 4145): Package:com.android.camera has been updated. Ignoring the one from path:/system/app/Camera.apk

Now, what might be causing this? I'm sure a wipe will make it go away, but I'm the kind of guy who prefers precise surgery rather that fixing stuff with the sledge hammer.

Any bright ideas?

/Mats
[G1 Android Development] Binary100100:
CRC1

So CRC1 is supposed to be hitting our phones starting today. According to this thread many users are worried about losing root because it appears to be updating our recovery, boot, radio, many apps, (pretty much everything... even spl?) so I guess the question is... what can we expect for CyanogenMod ROM's and when?
[G1 Android Development] raukodur:
Have recently updated to Cyanogen ROM, and loving it, but having one problem. I cant capture any videos, I can start recording them, but when I try to end them, the app force closes.

I can take photos fine, just problem with the videos.

Any solutions?
[G1 Android Development] spinjason:
WTF... HELP!!

I just flashed the .7.2 update from.7.1 and now I am stuck at my hard SPL screen, I tried to reboot but no go. I didnt wipe before applying (I think this was where I went wrong.) I dont have ADB or know how to use it, Can anyone let me know what I sould do or point me to the correct thread please.

"NO G1!.........AHHHH!!!!":eek::eek::eek:
[G1 Android Development] ID#:
@Cyanogen

It would be nice to see VPN in one of the next releases!

For example take a look at t4c's JF Mod.

The PDF-Reader in this mod is also helpfull ;)

But don't be scared, I'll stay with cyanogenmod ,)
[G1 Android Development] broncosfantx:
first off THANKS for all that you have done.

i keep getting an IM force close an suggestions.
[G1 Android Development] alritewhadeva:
pull out the battery. Boot into recovery. Fix filesystems, wipe and flash.
[G1 Android Development] spinjason:
Ok, I took the battery out for a couple of minutes. I got to Recoveryand fixed the file systems. Wiped then flashed and still took me back to my bootloader screen.... Any ideas?:eek:
[G1 Android Development] spinjason:
Just tried this also: Removed the battery, Recovery, Nandroid Restore, Reboot. I still Have the same issue...
[G1 Android Development] alritewhadeva:
repartiton your sdcard (remove ext and linux partitions if existent, and recreate them). Then wipe and reflash. Try that? :confused:
[G1 Android Development] spinjason:
(Ok,ok,ok...Breathing again)

I just removed the battery again after my last post, and Reinserted and it booted...

Any Ideas why this happened??:confused:
[G1 Android Development] alritewhadeva:
absolutely no idea...so this problem is solved i assume?
[G1 Android Development] spinjason:
Apparently, I will keep everyone updated if I notice anything wrong. Thanks for your help...
[G1 Android Development] :
Boot into recovery (home + Power), go into console and type:

cd sbin

fix_permissions

this only works with cyanogen recovery image
[G1 Android Development] alritewhadeva:
no problem :)
[G1 Android Development] Kwincy:
I'm having the same issues as you. It's not terrible, just annoying. I'm hoping that there is a quick fix for it though.
[G1 Android Development] spinjason:
Ok, it seems to be working but if I turn the phone off or reboot from Recovery I have to take the battery out to get it to boot up. This is just odd, never had the problem before. Its scary to thnk the system is missing something somewhere, I dont want it to crash. I am thinking of reflashing the HardSPL and Recovery to see if that fixes the problem. I think its a ROM issue though, so I think I will reflash that also. Thinking more about it makes me deduce there is a execution file missing or something.
[G1 Android Development] painrage:
@firefart @kwincy

are u guys both running themes?
[G1 Android Development] Kwincy:
Yep, I'm running Aero 1.7. It's probably the source of my problems. I'm also running Google Voice as well.
[G1 Android Development] kockroach:
Don't be so quick to blame the ROM. It could be the download itself. Did you do an md5sum check on the update file on your sdcard? The download could be corrupt. Also, don't forget, the first time you reboot after flashing this ROM, it will take a few minutes for the phone to get to the home screen. It has to build all of the files it needs.
[G1 Android Development] Christian S.:
I'm having the same problem without any theme. But: I noticed this on every build (Haykuro, Dude, etc.) I ever tried.
[G1 Android Development] :
no i'm running the "standard" rom

can this be caused by widgets on the home screen or too many installed apps?
[G1 Android Development] facelessuser:
I am aware of this. The problem is, it doesn't seem to be working. I tried unsetting it and resetting it back, and wifi appears to stay on without disconnecting during sleep; either that, or it is reconnecting just as fast as it wakes up which I think is highly unlikely. Anyone else noticing this?
[G1 Android Development] soulsponjah:
Another awesome update. Not experiencing any of the issues most are reporting. I can dl from the market, take pic/video, sms/mms works fine, bt and wifi always connect. Battery is acting like it did since it came out the box. Charged to 100% last night at 6pm and woke up this morning at 38%. This is with compcache swappiness set to 60. When I had swappiness set to 100 battery did run hotter as reported but phone was frickin quick.

Note: Originally came from JF1.5 apps2sd before switching to CM3.6. Went through all daily updates CM posted w/o wiping. Even tried Hero Themes w/o wipe. There are risks we take when flashing new ROMs...clearly noted in CM's DISCLAIMER.
[G1 Android Development] spinjason:
Good News

I flashed the HardSPL and my phone boots up fine now.... Still wondering what happened. If anyone knows Please inform us....

Thanks