yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] Grooby97:
I have encounter this. once last night with random shutdown. I think I can contribute this to my user.conf CPU throttling to too low speed. Second time was just an hour ago when the phone rebooted. Not sure what could cause this other than my phone was running in Edge mode and I've experience random reboots in EDGE mode using T-Mo's 1.6, and thus I am guess that could contribute to the reboot.
[G1 Android Development] ceas909:
question?? is it possible to push the Myfaves.apk file to this rom(4.1.9999)... if so does someone mind telling me how ive tried to look for how to, but im doing somthing wrong cuz its not working..and also would u need the MyFaves.odex file as well?? plz can someone help i would love to have MyFaves...
[G1 Android Development] xntx:
Is there some known problems with the compass on G1 in the last versions? Mine doesn't work correctly :(
[G1 Android Development] Robert916:
Well i got it fixed, I just got a new SD card then followed those steps and it worked.
[G1 Android Development] ufvj217:
quick question, can i install the recovery, then go straight to 4.1.9999 or do u have to start with 4.1.99 and then upgrade to .9999?
[G1 Android Development] lindellmm:
I notice some people having problem with music player starting up by itself. PBA that I have opened an Issue. It was logged as a Low Priority, but to me it is a High Priority, as I have to keep it muted all day while at work.

If you have this issue, please go to the Issue Log and add any helpful comments to Issue #620.
[G1 Android Development] bhilgeman:
You can go straight to .9999 as long as you have flashed the "recovery" image from the HTC website as instructed on the OP
[G1 Android Development] markimar:
So can't wait for this to go stable and get rid of compache!

My phone and sd card really don't get along well. It never has worked well for me, give me plain ole Linux swap please!
[G1 Android Development] buzzdroidx:
just a thought..or 2

i have a question for some of you who have been having compcache and swap issues etc. more of a suggestive nature as it helps you examine your situations. obviously there are so many issues questions etc i cant link to them all but it comes to mind, and its just error checking, no reflection on anyones intelligence, but when you load the rom are you running the commands in terminal to enable the cc or swap? or are you just expecting it to work? maybe i missed a class but afaik you have to apply the userinit and userconf commands manually once they are on your sdcard. just asking. im sure you have but its just error-checking ok? as i posted yesterday there have been so many sdcard and theme and individual widget issues that mess with so many builds its hard too nail down. since this is a "beta test" on the build why not approach it from a more methodic approach?

eliminate the complete package of stuff you have and start from a fresh build with nothing and work your way through till you find errors and report them its easier for devs to identify and deal with. sorry if this pissed anyone off fa fa but it seems like eliminating some of the variables will help things move faster and then we arent reading through 300 posts to gleen gems. i mean with nandroid so easily done there is a loss of merely minutes when testing this stuff anymore anyway my 2 sense
[G1 Android Development] shockd:
Hey quick question... I don't know if its because of this ROM or 1.6 or whatever, but where did the conditional call forwarding go? I'm trying to set up TrapCall on my phone and this is the instructions:

1. Go To Settings

2. Select Call Forwarding

3. Select Forward when Busy, Unanswered, and Unreachable. For each one you will need to type in +17608600220 as the forwarding number.

4. Save

When I go to settings I don't see the Call Forwarding option, all I see is Call Settings and there is no call forward option or anything.

Any help would be appreciated.. thanks!
[G1 Android Development] Fictionles:
Its under GSM call settings.
[G1 Android Development] metallicant:
I posted this back on page 180, 181 when I was using .999, same issue here with .9999 as well.
[G1 Android Development] shockd:
Oh wow can't believe I missed that lol. But now once I change the VM number to the TrapCall number, it says Unexpected response from network. This probably isnt a ROM issue so I'll try posting somewhere else. Thanks for your help though!
[G1 Android Development] heyyyitsjordan:
i had the same exact problem when i first flashed 4.1.999... most likely you flashed the wrong htc rom...
[G1 Android Development] jokersax11:
thank you i was starting to get tired of repeating it. you could try adb root then flash_image shell if you cant/dont know how to fastboot.
[G1 Android Development] lordyoda:
Quick question for the MT3G

Is there a difference between the following files?

HTC ADP 1.6 DRC83 (http://www.androidspin.com/downloads...ooted_base.zip)

or the

HTC Magic/ION/MT3G: http://developer.htc.com/google-io-device.html

?
[G1 Android Development] zimphishmonger:
The 'rooted' version is already rooted, so if you do boot before flashing Cyan you wont lose root or your recovery
[G1 Android Development] jenol:
flawless works on mt3g
[G1 Android Development] jokersax11:
calender, gmail, talk??? those are synced with your account through the cloud. wipe wipe wipe. it will come back.
[G1 Android Development] AngryCookieMonster:
Use the Rooted version, and you wont have any problems, i found out the hardway trying to flash the non-rooted version<---silly me

HTC ADP 1.6 DRC83 ([url]http://www.androidspin.com/downloads...ooted_base.zip[/url])
[G1 Android Development] flak0:
Enough Already

I hope everyone that has contributed to the 35+ pages is aware that CYANOGEN might move away from XDA. To those that contributed you are so ungrateful for what CYANOGEN has done for all of us. He risked possible litigation for us. CYANOGEN is the savior for android like JC is the savior for Christians. No wonder JC ain't comming back yet. For what. Check out the latest update via twitter:

"Going to move development somewhere other than XDA I think, not a diss on XDA, but 34 pages of the same thing in a couple of hours is much."

http://www.twitter.com/cyanogen

This is probably why Jesus Freke and H left the scene, ungrateful people like you. Moderator please ban these fools....
[G1 Android Development] ivanmmj:
It worked beautifully. I'm very thankful that he made it as easy as he did. I personally was thinking of having to flash, boot up and set up the first ROM, use a tool to backup the google binaries and then having to flash the other ROM and then having to use the tool to restore those apps. This was WAY easier than that. ^_^

So far, stable! Much more stable than even the last build was.
[G1 Android Development] The_Omen:
thanks for the suprise. the slide me app manager is a nice bonus. good work as usual.
[G1 Android Development] eyesofibad:
Ditto with the widget troubles on the g1. Everything else is great! WB and thanks!
[G1 Android Development] pep1t0:
If it helps here's the logcat after flashing htcrecovery and cm4.1.99

* daemon not running. starting it now *

* daemon started successfully *

I//system/xbin/busybox( 49): +++ "This is your world, these are your people. You can live for yourself today, or help build tomorrow for everyone."

I//system/xbin/busybox( 49): +++ Welcome to Android 1.6 / CyanogenMod-4.1.99

I//system/xbin/busybox( 49): --- Loading kernel modules

I//system/xbin/busybox( 49): --- Checking filesystems

I//system/xbin/busybox( 49): e2fsck 1.41.9 (22-Aug-2009)

I//system/xbin/busybox( 49): /dev/block/mmcblk0p2: recovering journal

I//system/xbin/busybox( 49): Superblock last mount time (Mon Oct 5 06:02:45 2009,

I//system/xbin/busybox( 49): now = Mon Aug 24 21:04:29 2009) is in the future.

I//system/xbin/busybox( 49): Fix? yes

I//system/xbin/busybox( 49): /dev/block/mmcblk0p2: clean, 10/64384 files, 8463/257040 blocks

I//system/xbin/busybox( 49): cp: cannot stat '/data/app-private/*': No such file or directory

I//system/xbin/busybox( 49): cp: cannot stat '/data/dalvik-cache/*': No such file or directory

I//system/xbin/busybox( 49): +++ Apps-to-SD successfully enabled

I//system/xbin/busybox( 49): /system/etc/init.d/05userinit: 14: Syntax error: "fi" unexpected (expecting "then")

I//system/xbin/busybox( 49): run-parts: /system/etc/init.d/05userinit exited with code 2

I//system/xbin/busybox( 49): --- Enabling compcache

I/logwrapper( 49): /system/xbin/busybox terminated by exit(1)

I/DEBUG ( 141): debuggerd: Oct 3 2009 23:25:21

I/vold ( 140): Android Volume Daemon version 2.0

I/vold ( 140): New MMC card 'SU04G' (serial 276444197) added @ /devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:e0a9

I/vold ( 140): Disk (blkdev 179:0), 7959552 secs (3886 MB) 3 partitions

I/vold ( 140): New blkdev 179.0 on media SU04G, media path /devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:e0a9, Dpp 3

I/vold ( 140): Partition (blkdev 179:1), 5767272 secs (2816 MB) type 0xb

I/vold ( 140): New blkdev 179.1 on media SU04G, media path /devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:e0a9, Dpp 2

I/vold ( 140): Partition (blkdev 179:2), 2056320 secs (1004 MB) type 0x83

I/vold ( 140): New blkdev 179.2 on media SU04G, media path /devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:e0a9, Dpp 1

I/vold ( 140): Partition (blkdev 179:3), 128520 secs (62 MB) type 0x82

I/vold ( 140): New blkdev 179.3 on media SU04G, media path /devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:e0a9, Dpp 0

I/vold ( 140): Evaluating dev '/devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:e0a9/block/mmcblk0' for mountable filesystems for '/sdcard'

I/vold ( 140): Aborting start of /sdcard (bootstrap = 1)

I/vold ( 140): Volmgr not ready to handle device

D/vold ( 140): Bootstrapping complete

E/flash_image( 147): error opening /data/recovery.img: No such file or directory

D/AKMD ( 149): akmd 1.6.6 START

D/AKMD ( 149): library version: 1.2.1.1129
[G1 Android Development] ivanmmj:
This thread is an absolute mess. I'm temporarily closing it to clean it out. To those who are having problems flashing this, the instructions are simple enough. Many people have even answered it a few times. I'll keep those posts and remove any misinformation.
[G1 Android Development] ivanmmj:
For those waiting for the thread to be reopened:

Here are a few clarifications:

The recovery image is NOT a recovery in the meaning of the word we use.

It is NOT to be flashed over your current recovery. It's a ROM. If you flash it like you flash other recovery images, you will break your phone (although, you can probably fast boot everything back.)

I'm still working on cleaning the thread....

EDIT: My desktop BSOD'd.... so I'll have to reopen the thread... I need to fix my desktop first. Darn it....
[G1 Android Development] mwenyuan:
Bluetooth remote controller (AVRCP) seems still not working.
[G1 Android Development] hinlawrtai:
Bluetooth issue

Cyanogen, you're the best!! I have just installed your latest rom and it runs really smooth on my Dream!!

Here's my question, I can't seem to be able to connect my bluetooth headset with this latest ROM, is that a known issue? It will be great if there is a solution or something that I should do in order to make it work. I believe some people also experience this bluetooth issue? Thanks.
[G1 Android Development] rastacre:
Hi There,

there is a small error in /system/etc/init.d/05userinit:

the code is:

#!/system/bin/sh
# call a userinit.sh script if it's present on the sdcard
if [ -e /system/sd/userinit.sh ];
then
echo "--- Executing userinit.sh"
busybox chmod +x /system/sd/userinit.sh
/system/bin/sh /system/sd/userinit.sh;
setprop cm.userinit.active 1;
fi;

if [ -d /system/sd/userinit.d ];
busybox run-parts /system/sd/userinit.d;
setprop cm.userinit.active 1;
fi;

but should be:

#!/system/bin/sh
# call a userinit.sh script if it's present on the sdcard
if [ -e /system/sd/userinit.sh ];
then
echo "--- Executing userinit.sh"
busybox chmod +x /system/sd/userinit.sh
/system/bin/sh /system/sd/userinit.sh;
setprop cm.userinit.active 1;
fi;

if [ -d /system/sd/userinit.d ];
[B]then[/B]
busybox run-parts /system/sd/userinit.d;
setprop cm.userinit.active 1;
fi;

I get an error at 1st boot:

I//system/xbin/busybox( 49): +++ "This is your world, these are your people. You can live for yourself today, or help build tomorrow for everyone."
I//system/xbin/busybox( 49): +++ Welcome to Android 1.6 / CyanogenMod-4.1.99
I//system/xbin/busybox( 49): --- Loading kernel modules
I//system/xbin/busybox( 49): --- Checking filesystems
I//system/xbin/busybox( 49): e2fsck 1.41.9 (22-Aug-2009)
I//system/xbin/busybox( 49): G1SD2: recovering journal
I//system/xbin/busybox( 49): G1SD2: clean, 3828/128520 files, 239756/514080 blocks
I//system/xbin/busybox( 49): cp: cannot stat '/data/dalvik-cache/*': No such file or directory
I//system/xbin/busybox( 49): +++ Apps-to-SD successfully enabled
I//system/xbin/busybox( 49): --- Executing userinit.sh
I//system/xbin/busybox( 49): /system/etc/init.d/05userinit: 14: Syntax error: "fi" unexpected (expecting "then")
I//system/xbin/busybox( 49): run-parts: /system/etc/init.d/05userinit exited with code 2
I/logwrapper( 49): /system/xbin/busybox terminated by exit(1)

cheers
[G1 Android Development] FiFTYSiX:
Stereo Bluetooth is on the fritz with this build...

I get a connection to my car stereo (which connects with 1234 pass very easy even on my other g1 with old skool jf1.5) But there is no sound and the music app will play, but skip every 2-3 seconds, stream furious is fail as well...

would a log help out i dunno if this is a reoccurring prob with the builds r what, I have been using 2 JF1.5's since the beginning of the year never flashed until last week and today...
[G1 Android Development] IConrad01:
For those of you having bluetooth problems with this new version: Please post your logcat data at the following URL.

http://code.google.com/p/cyanogenmo...Priority Version Owner Summary Stars Modified
[G1 Android Development] innerspace:
Welcome back cyanogen!

My experience w/ 4.1.99:

Coming from a stable working build 4.1.11.1

Downloaded "1.6 recovery image" from htc website to sdcard

Downloaded cm4.1.99 to sdcard

rebooted to recovery

did a wipe

flashed "1.6 recovery image"

hit home + back to reboot when prompted

phone installed radio, rebooted, entered recovery image

I flashed cm4.1.99

hit home + back to reboot

at this point the G1 took approx. 10 minutes to boot, half on the G1 logo, half on the cyanogized Android logo. USB wasn't recognized, logcat/lolcat stuck at "waiting for device".

After phone finally booted I was presented with the initial "tap here to continue screen" and a ton of FC's.

Did 3 Finger salute and entered recovery, entered console, mounted sdcard, chmod'd fix_permissions_1.29.txt and ran it.

rebooted, lolcat worked this time, still a slow boot, lots of time on DexOpt but phone boots fine. I noticed the same behavior on 4.1.11.1

Got NO FC's this time. Signed in and synced and away we go!

I really appreciate all your time, effort etc. cyanogen. Thanks for taking one for the team and responding in such a rational and level-headed manner. And thanks for helping make Android what it should be for all of us who care. Really do appreciate all your hard work. I will report back with my experiences after the drive home.
[G1 Android Development] quakermaas:
All seems good so far, other than End Button Behavior, "Home, then sleep" still no worky.

I just installed over the top of 4.1.11.1, no wipe, Installed HTC 1.6, Installed 4.1.99, when booted had to install HTC_IME.apk to stop the force close.

Everything seems to be working great after that and fix_permissions, no lag to home screen, every thing is how it was, with the 4.1.11.1(wallpaper,setting,he-areo v1.5 theme) :)

Big Thanks to Cyanogen
[G1 Android Development] heyyyitsjordan:
flash the htc developer build before you flash cyan
[G1 Android Development] sino8r:
Just curious, has anyone else noticed CRAZY BATTERY DRAIN since 4.1.99? Before 4.1.99 (basically before donut or at least complete donut port (4.0.4 for instance)), I had a perfect, accurate battery reading. Now I can just watch the percents drain in literally 5 minutes. It'll go from the 90's to 70"s in less than 30 minutes. It might be my battery and purely coincidental. Just wondering if it's just me. Thanks for any input, folks. Besides that, I'm really loving the latest builds. My Touch Pro 2 and my other previous WM pocket pc's barely get any use anymore because Android is almost perfect now. WM, Apple, and Palm REALLY DO pale in comparison to Android these days! LONG LIVE THE BOT! lol...:D
[G1 Android Development] acidwashg1:
just reporting in: I am running 4.1.9999. I wiped and did the install routine for 4.1.999, and then I upgraded to .9999. I have compcache enabled at the moment, with a backing swap. I still have the random music playing issue. I am going to try to disable compcache and just use a linux-managed swap of 64mb. I'll see if the problem persists after I disable compcache.
[G1 Android Development] godofthesms:
i can not even get it running! i have 1.4 + JF when i follow the steps it just reboots and is still 1.4!

Anyone else had this issue? Or a fix?

i have a Rogers G1 =)
[G1 Android Development] markimar:
I noticed this on enoms rom and it followed me over to cyans rom. There is definitely a battery drain issue with doughnut builds atleast each build I've used so far.
[G1 Android Development] sino8r:
Thanks! Good to know it's not just me then. I still need a new battery I bet though. Mine is a year old. IMO, cell battery since lithium ion don't last more than a year with HEAVY use. I pretty much abuse my batterys anyways. Between bluetooth, 3g, and wi-fi; have had to keep 2 in rotation. It's a real shame that I lost my second one since donut:mad:

I may just get one of those giant, ugly-but-useful large capacity ones and be done with it. Oh well, thanks for the info!
[G1 Android Development] brownbomba:
I had a strange thing happen. I went from 4.1.11.1 and wiped and flashed everything per the instructions. But all my apps are still on the phone. I did not have to redownload any of my apps and I have not had one force close.....this is sweet!
[G1 Android Development] lotherius:
I have actually had the best luck now with a 64mb backing swap compcache setup. Have to set the size a couple meg under the partition size though, or it will default back to 32mb.
[G1 Android Development] lotherius:
Yes, I have had this happen. I was even able to put icons on the desktop from the drawer after this, but after reboot my original desktop icons and widgets came back. I had upgraded from .999 to .9999 and had previously had a theme installed. So I wiped and reflashed clean starting with the ADP ROM, and haven't had the problem again.
[G1 Android Development] Jaysn:
I've not had this happen to me, but I have heard of it. IIRC, they fixed it by running the battery completely down, to where it wouldn't even turn back on again, then doing a full charge with the device off. There was mention of the OS not having a correct reading on the battery's charge, so it just averaged out what it thought the correct level was. There might have been a file you can delete as well, unless that's the accelerometer / compass I'm thinking of.
[G1 Android Development] -vip3r-:
i dunno what's going on, the previous version didn't do this but, i've had atleast 5 reboots today!
[G1 Android Development] bkmo:
to clear the battery stats do this from terminal

su <enter>

rm /data/system/batterystats.bin <enter>
[G1 Android Development] kilaclwnjuggalo:
can u flash this just like motoclic blur
[G1 Android Development] FrEsHaZzBuRu:
I'm still getting notification issues with this ROM.

Once I get a text message or some other notification, the notification bar is not responsive. Also, after this occurs, the display timeout starts to tweak. Even during usage, the display will time out after only a couple seconds. This only occurs after the notification bar becomes unresponsive.

If anyone has any similar experiences, please help me out.

note: I wiped, re-partitioned, wiped again, then flashed both this ROM and the merged version in the other thread in separate instances, and finally restarted twice.
[G1 Android Development] rakjer:
Wow. been a while since i've been here. Strange how some phones run perfectly(like mine), and others have sooo many problems. Weird huh?. I just went from CM v4.1.11.1 to 4.1.9999 and my phone has not skipped a single beat. This rom has been

super fast

(fastest

i've

used so far) and

stable

for me since install(10/18). Had the "touch input" problem at initial install, but did as the instructions said, and all is good. No lagging or FC's whatsoever. All of my progs run fine(i have around 85 installed, why, I don't know?, cause I can ;)) As far as I am concerned, this rom version should be stable.

Thank you Cyanogen.
[G1 Android Development] turboyo:
I lost root some how flashing this or maybe a previous rom but havnt noticed till now, i was on the first akira before but flashed to newer versions then did nandroid backup to akira 1 .. i flashed to this and i realize theres no root.. even when i run my back up no root. I have root like in the recovery and console .. but when the actual phone is running and not in recovery i just keep getting $ instead of # in terminal.. no message or anything SOMEONE HELP PLEASE! apps 2 sd and all my root apps seem to work .. im so stumpedd
[G1 Android Development] Silence66:
i got a huge problem here too:( i noticed that when my phone is in standby mode for a long time (for exmaple over night for 6h), i cannot send sms anymore or do any calls. also i don't get any notifications about incoming messages, missed calls and also incoming calls!!:/ everythng else works perfect (home screen, ...). i use a sapphire phone and updated from 4.1.999 to 4.1.9999 without a wipe. i hadn't this problems with the old 4.199 version (but there i got the problem that i was sometimes not able to wake up the phone)
[G1 Android Development] ZilverZurfarn:
Why wait? Use userinit.sh/user.conf (http://xdaforums.com/showthread.php?t=542899&highlight=userinit.sh) to set your phone to use whatever (if any) virtual memory system you want.

Read the first post in this thread (and/or the wiki @ www.cyanogenmod.com) for instructions.

/Mats
[G1 Android Development] ddaanet:
Debugging a bootloop

Try running "adb logcat" while booting (you might need to reflash from a working backup to enable USB debugging) and identify the repeating error that's causing the bootloop.

For at least two of us the flashing process (with either CM-1.4 or RA-1.2.3) installs a corrupted jar in the /system/framework folder that caused an early bootloop. The problem always affect the same file on a given phone for a given ROM, and it's not specific to CM ROMs.

Extracting a good replacement jar from the CM zip and copying it in place with "adb push" or cp from the sdcard fixes the problem.

I speculate that the corruption could sometimes affect other files that do not cause a helpful error message in logcat. To be sure, you can generate the md5sums from all the files in your system (see one of my earlier posts for that) and compare it to the md5sums that were posted here.

If you indeed have this problem, please report the precise phone model you have, the repetitive portion of the the logcat output, the installation procedure you followed (esp. on what base you install CM), and the md5sum listing. I suspect it might be the cause of a lot of bootloops and crashes around and we need to collect more data about this issue.
[G1 Android Development] Krypt:
I had a problem with this. When I flashed the HTC rom and then 4.1.9999 directly I couldn't enable bluetooth.

I reflashed the HTC and then 4.1.9999 again; I still couldn't enable bluetooth.

When I reflashed HTC, then 4.1.999 and then 4.1.9999 all was fine.