yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] charlus:
Update from 4.1.999 -> 4.1.9999 : phone does not boot

Hello all,

I've tried to upgrade my magic 32B ( French, SFR ) from 4.1.999 to 4.1.9999 by simply applying the latest update-cm-4.1.9999-signed.zip ( I did not reflash the 1.6 base from htc ).

When I reboot the phone I'm getting the following logs and the system crashes ( no boot, I'm not even getting the android logo , it stays on the 'SFR' logo ). Here's the start of a logcat ( full version attached ). I see processes SEGFAULTING :

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

I//system/xbin/busybox( 48): +++ Welcome to Android 1.6 / CyanogenMod-4.1.9999

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

I//system/xbin/busybox( 48): [: 1: unknown operand

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

I/logwrapper( 48): /system/xbin/busybox terminated by exit(0)

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

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

I/vold ( 79): New MMC card 'SU08G' (serial 2155648985) added @ /devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:aaaa

I/vold ( 79): Disk (blkdev 179:0), 15523840 secs (7580 MB) 1 partitions

I/vold ( 79): New blkdev 179.0 on media SU08G, media path /devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:aaaa, Dpp 1

I/vold ( 79): Partition (blkdev 179:1), 15515648 secs (7576 MB) type 0xb

I/vold ( 79): New blkdev 179.1 on media SU08G, media path /devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:aaaa, Dpp 0

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

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

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

D/vold ( 79): Bootstrapping complete

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

D/AKMD ( 88): akmd 1.6.6 START

D/AKMD ( 88): library version: 1.2.1.1129

E/RIL Acoustic( 81): Fail to open /system/etc/AudioPara_VODA-SFR.csv -1.

I/RIL Acoustic( 81): open /system/etc/AudioPara4.csv success.

I/RIL Acoustic( 81): acoustic table version: Dream_TMU_20090305

I/RIL Acoustic( 81): read_audio_para_from_file success.

D/AndroidRuntime( 82):

D/AndroidRuntime( 82): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<

D/AndroidRuntime( 82): CheckJNI is OFF

I/DEBUG ( 80): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

I/DEBUG ( 80): Build fingerprint: 'tmobile/opal/sapphire/sapphire:1.6/DRC92/15632:user/ota-rel-keys,release-keys'

I/DEBUG ( 80): pid: 83, tid: 83 >>> /system/bin/mediaserver <<<

I/DEBUG ( 80): signal 11 (SIGSEGV), fault addr f6149e57

I/DEBUG ( 80): r0 b0012e3c r1 00000000 r2 beb53ac4 r3 f6149e57

Is anyone else experiencing this ?
[G1 Android Development] oreoOozZz:
This thing is like LIGHTNING bro, amazing. Ive never seen the phone work this quick. If anybody wants to test it or doubts me, add a new wallpaper from the picture gallery and see how fast it applies compared to before. Its amazing, keep up the great work Cy, when i get a chance ill buy you a beer.
[G1 Android Development] Aglos:
32b 4.1.9999 not recognize mi fat32 partition in sd card
[G1 Android Development] Androidandy:
Just updated to .9999. Everything went as it should- no problems encountered :D
[G1 Android Development] skrki:
Thank you for sharing, and thank MikeTaylor00 for his awesome work on tweaking userinit, and helping everyone find best configurations for their devices.

The thread that's helped me out greatly is linked in my signature (CC+BSw). It contains great info from MikeTaylor00 and other significant members. My suggestion for everybody is to check it out!
[G1 Android Development] BlackElvis79:
apps

Will this have any residual effects on later flashes of different ROM's as far as the Google Apps.
[G1 Android Development] SxxxA:
Battery drain <=> Phone's activity

A few things to check:

0. Refresh your battery! This helps, trust me. You never know, especially if you switch ROMs often, sometimes leftovers can cause a huge mess. There are threads talking about the steps necessary to do this (I can't remember now, but search for "battery").

1. Is CPU overclocked for more than it needs to? (right, but what does that mean??? ;P)

2. Is the phone doing stuff while idle? Seen this happen, easilly can be figured out by monitoring the logcat while the phone is asleep.

3. Custom clocking through user.conf will ensure your CPU isn't set crazy fast when it doesn't need to be. For instance, people commonly think that setting CPU 384-512 will render the device blazingly fast. Yeah, but what about utilization? What about idle time it spends on high speeds?

4. Setting percentage of load at which the CPU goes up a speed step (also through user.conf) will help.

Basically, it's not the "ROM" that's eating battery, but the settings. Stock firmware is set up at a moderate level, balancing between the load and battery life to provide optimized performance for an average user.

CM builds, as stated by SK himself, are designed to "push the device even further"... hence the disclaimer about broken SD cards, thermonuclear war, etc... See the connection? :D

Luckily, using custom settings through userinit, allows us to modify these to our liking.

My experience w/CM is: Yes, it uses more battery by default, but I can tweak it and achieve, like 8% drop over 10 hours on idle, or maybe a 30% drop with 2-3 hours of WiFi/Data. I think that's pretty good....still have to charge it every day, but it was like that with stock, too :D

Hope this helps someone!

P.S. While I'm posting already... I had no probs w/install, even by doing crazy things that I do.. See, I had 4.1.999 on, but then I found out about MghtyMax Hero 1.9 and *just had to* try it! (it is AWESOME by the way) So when 9999 came out, I pulled out my SwitchROM of 999, restored it, and just flashed 9999 over it. Works perfectly!

So advice to all: use SwitchROM, and store stable setups. Recovering is as easy as typing a single command in the terminal! And no need to go through the procedure of installing ADP1.6, then reboot, watch your finger so it doesn't slip from Home button, blah blah...:P SwitchROM stores your nandroid, your apps, and your settings, and restores them correctly.

Hope this^ also helps someone...
[G1 Android Development] SxxxA:
IMO no.

Each ROM carries Google apps along, so how would that b affected?

There's a point to installing ADP1.6, as stated by PsychoI3oy earlier. It's nothing revolutionary, but has to be done to conform to Google's requirements.
[G1 Android Development] terence_oh:
I went the lazy route (i.e. no effort spent on tweaking) and bought this:

http://www.seidioonline.com/product-p/bacy26tmg1-bk.htm

I now average <50% utilization daily and charge every two days, even with heavy usage. At the cost of a thicker phone (less cool factor) and slightly more weight.
[G1 Android Development] coredalae:
same, just baught a 2nd battery i always carry around :) saves me the hassle of watching my batt lvl :P

.9999 runs great here btw, looking forward to the stable :)
[G1 Android Development] Sirus20x6:
ahahah that episode is epic win!
[G1 Android Development] nitefallz:
Are we just flashing the new file if we already have 4.1.999, or are we flashing both files?
[G1 Android Development] G1-evolve:
Just the new file.
[G1 Android Development] Shane2:
I have been looking through and can't find the info I need, so could someone help. I understand how to create the partitions, its just the other bits I am unsure about...

Firstly, is it true that you suffer detrimental performance if you have a linux swap larger than 32m

Secondly, once you have created the swap partition, how do you mount it and use it as your primary swap from within Android? thanks
[G1 Android Development] prash:
Both of those questions are not related to the rom specifically. It just clutters up this thread even more. You may want to try out the 'Dream Q&A' section made for asking just these sort of one-off non-related questions if you haven't found your answer by searching the various swap related threads in the forums. Search first, then try Dream Q&A.
[G1 Android Development] guinnes.s:
cannot uninstall using Astro,

i pushed with this comand

adb remount

adb push libt9.so /system/lib/libt9.so

adb push HTC_IME.apk /system/app/HTC_IME.apk

adb shell reboot

is that right?
[G1 Android Development] bluecluenj:
Ugh...

I installed and after the install it went perfectly, ran like a charm. Then I put my photos and sounds back on the card and rebooted, goes up to the cyanogen splash screen and black screens. Numerous reboots failed to fix the problem. I searched the thread but can't find a solution. Anyone can help? Thanks\

edit: I installed on a fat32 only card, no apps2sd.
[G1 Android Development] wesgarner:
Cm 4.1.9999 a2sd

(v4.1.9999 - almost-stable-beta version, updated 10/18):

Just upgraded from .11

I use my own a2sd, but where is the a2sd script (or what is it now) (it used to be located at /system/bin)
[G1 Android Development] wesgarner:
Cm 4.1.9999 a2sd

Scratch that found it, it's in init.d now
[G1 Android Development] nickp89:
I have a "CAMERA" problem.

Everytime i click on the camera icon, the phone crashes.

I use "Italian" Language.

Someone can help me?

(I've Cyanogen 4.1.9999 version)
[G1 Android Development] nitefallz:
Thanks, worked flawlessly.
[G1 Android Development] ddaanet:
Bootloop with both 4.1.999 and 4.1.9999

4.1.99 boots here, but when I follow the same install procedure with 4.1.999 or 4.1.9999 I get a bootloop.

Running on a white G1 from Orange with HardSPL and recovery-RA-dream-v1.2.3.

ADB gives the following repeat message on bootloop with 4.1.999.

I/dalvikvm( 137): DexOpt: source file mod time mismatch (3b43bcf2 vs 3b46411a)

D/dalvikvm( 137): Stale deps in cache file; removing and retrying

W/dalvikvm( 137): Size mismatch on inflated file (975643 vs 974440)

E/dalvikvm( 137): Unable to extract+optimize DEX from '/system/framework/services.jar'

D/dalvikvm( 137): Failed on '/system/framework/services.jar' (boot=1)

D/dalvikvm( 137): VM cleaning up

D/dalvikvm( 137): LinearAlloc 0x0 used 4100 of 4194304 (0%)

W/dalvikvm( 137): JNI_CreateJavaVM failed

E/AndroidRuntime( 137): JNI_CreateJavaVM failed

D/AndroidRuntime( 154):

D/AndroidRuntime( 154): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<

D/AndroidRuntime( 154): CheckJNI is OFF

D/dalvikvm( 154): DexOpt: incorrect opt magic number (0xff ff ff ff)

D/dalvikvm( 154): Stale deps in cache file; removing and retrying

W/dalvikvm( 154): Size mismatch on inflated file (975643 vs 974440)

E/dalvikvm( 154): Unable to extract+optimize DEX from '/system/framework/services.jar'

etc.

And with 4.1.9999:

D/dalvikvm( 130): DexOpt: incorrect opt magic number (0xff ff ff ff)

D/dalvikvm( 130): Stale deps in cache file; removing and retrying

W/dalvikvm( 130): Size mismatch on inflated file (5504137 vs 5502156)

E/dalvikvm( 130): Unable to extract+optimize DEX from '/system/framework/framework.jar'

D/dalvikvm( 130): Failed on '/system/framework/framework.jar' (boot=1)

D/dalvikvm( 130): VM cleaning up

D/dalvikvm( 130): LinearAlloc 0x0 used 4100 of 4194304 (0%)

W/dalvikvm( 130): JNI_CreateJavaVM failed

E/AndroidRuntime( 130): JNI_CreateJavaVM failed

D/AndroidRuntime( 147):

D/AndroidRuntime( 147): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<

D/AndroidRuntime( 147): CheckJNI is OFF

D/dalvikvm( 147): DexOpt: incorrect opt magic number (0xff ff ff ff)

D/dalvikvm( 147): Stale deps in cache file; removing and retrying

W/dalvikvm( 147): Size mismatch on inflated file (5504137 vs 5502156)

E/dalvikvm( 147): Unable to extract+optimize DEX from '/system/framework/framework.jar'

etc.

Yes, I did wipe data and the ext partition, it makes no difference.

I can provide more complete logs on demand, I have them saved on disk.
[G1 Android Development] Morpheo17:
mmmm

The new build works perfect for me but, the market doesn't show all aplications. For example, Spotify doesn't appear. Any idea?
[G1 Android Development] alapapa:
I don't see an app called Spotify on cyrket

http://www.cyrket.com/search?q=spotify

is it called something else?
[G1 Android Development] TrOjAnUK:
Spotify SHOWS and is installed from Market, just done it to test.

TrOjAn
[G1 Android Development] Morpheo17:
Ok, Spotify is only in the european Market xDDD

http://es.androlib.com/android.application.com-spotify-mobile-android-ui-qiqj.aspx

Ok, another app (a simple widget made by me):

http://www.cyrket.com/package/com.giu.batterywidget

That app doesn't appears in the market :S
[G1 Android Development] tman7510:
Cyan I love your ROMs but need pdf support. How about porting kpdf or kghostview? 90% of attachments are sent in pdf format. I'm not complaining, I know you do this on your spare time for free. I'm just making a suggestion because I like your roms better then the hero roms but I haven't had a choice since google sent you the C&A letter :D
[G1 Android Development] coredalae:
Try going from .99 to .9999 without without using the steps from the first post, so just flash .9999 over .99 the old way..
[G1 Android Development] AustinKnight45:
I didn't get a chance to try it that way, it should work adb though did it not or what? Did you go to astro and find wherever HTC_IME.apk is then open it, there should be a uninstall tab and a launch tab.Uninstall it then reinstall HTC_IME.apk.
[G1 Android Development] AustinKnight45:
Double sorry
[G1 Android Development] fabolous50:
Market Force Close

I keep getting a market force close..won't even open. (Process com.android.vending) that's wat it says
[G1 Android Development] djengizz:
I had the same error on all of the '9-releases' complaining about different jars for each release (framework, ext and core). Also after starting from scratch and wiping everything.

I solved it by extracting the jar from the downloaded zip file and manually pushing it to /system/framework using adb. You can even do it while in the bootloop and it should pick it up right away and continue booting.

edit: make sure you do adb remount before pushing the jar.
[G1 Android Development] ddaanet:
Bootloop resolved. Bad internal flash?

It still bootloops, but it produces a slightly different error:

W/dalvikvm( 3017): Size mismatch on inflated file (5504129 vs 5502156)

In doubt, I used "adb shell" to rename the framework.jar to framework.jar.0, and I copied in the framework.jar from the zip through the sdcard.

And behold, it boots!

That really sucks, apparently something in the chain causes a silent data corruption... My best guess is bad NAND. Is there a way to diagnose and repair the internal flash?
[G1 Android Development] jiffyj:
the random music playing issue still exists for me, just happened a sec ago. Otherwise, i'm all good.
[G1 Android Development] djengizz:
I'm not sure. All my nandroid backups restore fine. It just when I flash using recovery (i even tried different recovery consoles, still the same error).
[G1 Android Development] anangphatak:
Request to include Wallpaper Lake in ROM

I love your roms..always keep coming back to them...currently running 4.1.999 and wanted to express my gratitude, first off !!

Now to my request:

On 4.1.999 rom, on selecting the wallpaper_lake, it asks me crop the image (to a much smaller size)...it never did that on your previous ROM (4.0.4)

Can you include the lake wallpapers in your roms ? (see attached ?)

Thanks in advance,

AAP
[G1 Android Development] tjt486:
For some reason I had a scare flashing from .999 to .9999 last night. I had already done the htc recovery image so I just flashed as normal. The t-mobile boot screen seemed to be taking longer than normal so I left it and went to sleep. I woke up this morning and still had the t-mobile boot screen. I pulled the battery, reflashed the htc image, then flashed .9999 and it works fine now.
[G1 Android Development] Pikkuhannu:
Why dont`s you use wallpaper set&save app?

Just choose pic and save.
[G1 Android Development] cb7tuner93:
Ok so the "no audio" problem is 99% hardware problem not a ROM problem or anything like that.
[G1 Android Development] charlus:
Update from 4.1.999 -> 4.1.9999 : phone does not boot

Hello all,

I've tried to upgrade my magic 32B ( French, SFR ) from 4.1.999 to 4.1.9999 by simply applying the latest update-cm-4.1.9999-signed.zip ( I did not reflash the 1.6 base from htc ).

When I reboot the phone I'm getting the following logs and the system crashes ( no boot, I'm not even getting the android logo , it stays on the 'SFR' logo ). Here's the start of a logcat ( full version attached ). I see processes SEGFAULTING ( cf log exerpt, full log attachted ).

I tried to reflash the image a second time, same result.

Has anyone seen this ? Any idea ?

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

I//system/xbin/busybox( 48): +++ Welcome to Android 1.6 / CyanogenMod-4.1.9999

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

I//system/xbin/busybox( 48): [: 1: unknown operand

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

I/logwrapper( 48): /system/xbin/busybox terminated by exit(0)

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

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

I/vold ( 79): New MMC card 'SU08G' (serial 2155648985) added @ /devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:aaaa

I/vold ( 79): Disk (blkdev 179:0), 15523840 secs (7580 MB) 1 partitions

I/vold ( 79): New blkdev 179.0 on media SU08G, media path /devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:aaaa, Dpp 1

I/vold ( 79): Partition (blkdev 179:1), 15515648 secs (7576 MB) type 0xb

I/vold ( 79): New blkdev 179.1 on media SU08G, media path /devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:aaaa, Dpp 0

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

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

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

D/vold ( 79): Bootstrapping complete

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

D/AKMD ( 88): akmd 1.6.6 START

D/AKMD ( 88): library version: 1.2.1.1129

E/RIL Acoustic( 81): Fail to open /system/etc/AudioPara_VODA-SFR.csv -1.

I/RIL Acoustic( 81): open /system/etc/AudioPara4.csv success.

I/RIL Acoustic( 81): acoustic table version: Dream_TMU_20090305

I/RIL Acoustic( 81): read_audio_para_from_file success.

D/AndroidRuntime( 82):

D/AndroidRuntime( 82): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<

D/AndroidRuntime( 82): CheckJNI is OFF

I/DEBUG ( 80): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

I/DEBUG ( 80): Build fingerprint: 'tmobile/opal/sapphire/sapphire:1.6/DRC92/15632:user/ota-rel-keys,release-keys'

I/DEBUG ( 80): pid: 83, tid: 83 >>> /system/bin/mediaserver <<<

I/DEBUG ( 80): signal 11 (SIGSEGV), fault addr f6149e57

I/DEBUG ( 80): r0 b0012e3c r1 00000000 r2 beb53ac4 r3 f6149e57
[G1 Android Development] ddaanet:
Silent data corruption in flashing process

That's funny. I did the "copy over jar from the zip" thing without even reading your previous message.

And same for me: nandroid restores fine, it's only when flashing zips or img from another source that I get problems.

I compared the original framework.jar (renamed framework.jar.0) and the one I installed by hand:

/system/framework# md5sum framework.jar.0 framework.jar

03e0122ee6c5425c765f155a9734be12 framework.jar.0

d00f4d27e7ef8fd4643ea5e9cd04aefc framework.jar

No read error. Just silent data corruption. That's really scary. Is there a way to audit the entire system post-flash to detect other corrupted files? I guess someone could provide md5sums for all the files in the system partition. But how to audit the boot partition?

The thing with an Android dev reporting a similar problem and solving it by using a different recovery console is puzzling. Do you have more details?
[G1 Android Development] ministersin:
Dialer won't let me press 1 for English :)

when I make a call I am unable to make the number pad come up by pressing Dialpad. I have to hit the menu button and then choose the dial pad scroller at the top of that.

even then I am unable to press numbers or double tab to wake up after it sleeps.

So calling anything with a prompt for a "Press #" is not an option for me under this ROM (.9999).

Anybody else having this? any suggestions if it is not the ROM (worked fine before flashing .9999)
[G1 Android Development] mahd-leb:
thnx for the info bro... just to confirm something iam not using ext parition i thought i dnt need it so i guess it doesnt work widout it but if i recreated my ext partition and put my apps on it if i backup and then restore the apps will be automatically installed on the new rom i flashed ....they wont be apks tht i have to install is that correct?
[G1 Android Development] ddaanet:
Hey charlus. I think you might have the same issue as me and djengizz.

Apparently, silent data corruption occurs in the flashing process on some phones. Both of us had the problem in jar files that we could identify thanks to logcat, so we ended up extracting them from the zip and copying them onto the internal flash by hand (either adb push or cp in adb shell).

See if you can get a dump of the md5 sums of all the files in your system partition. I'll do the same here and we'll find which files are different.
[G1 Android Development] djengizz:
Yes, scary.

I searched for that post again but couldn't find it anymore, sorry. I believe it was in one of the Google groups about Android development.

The weird thing is once it happened after flashing .99 I am not able to flash any ROM anymore without these kind of errors (also tried non-cyanogen ROMs). Most of them I got working anyway by manually pushing the files but it's still a scary thought and I haven't found a solution or cause yet. I think it's also strange that it's always a jar in the framework folder and always only one corrupted file. It's also reproducible on my phone, meaning the same file gets corrupted (depending on the ROM). This leads me to believe it's not corrupted NAND but i'm not sure.

The only thing I can think of is the fact that I have a perfected SPL (1.33.0006) but I don't see how this can cause data corruption...
[G1 Android Development] shaithis01:
I get a black screen after every other restart.
[G1 Android Development] pureimagination:
Link to HTC recovery image

When you go to http://developer.htc.com/adp.html#s3 there are still place holders for the Android 1.6 Recovery Image but once clicked on and then agree to the TOS it takes you to http://www.htc.com/www/support.aspx. Is there a direct link to this or did HTC take it down?
[G1 Android Development] bkmo:
You are not giving any info of your setup before/after to help with your problem. We are not psychics.
[G1 Android Development] ZilverZurfarn:
Beg to differ! The less media and other non functional stuff that the end users easily can add themselves, the better. I never use stock backgrounds or ringtones - and would hate having to download them (and then removing them) for every update.

/Mats
[G1 Android Development] ddaanet:
Silent data corruption in flashing process, md5sums from CM 4.1.9999.

To further the investigation, here are the md5sums of my /system. This listing was produced with the following procedure (assuming linux on the computer).

Make a nandroid backup

Copy the system.img from sdcard to the computer.

mkdir system; cd system ; unyaffs ../system.img

Remove any specific files you might have (I removed my framework.jar.0 file).

find . -type f | sort | xargs md5sum > ../system-md5s.txt

You can get the unyaffs binary from the project's download page on Google Code.

The system's life was "htc donut" -> CM-4.1.99 + french keyboard layout -> CM-4.1.9999

Send in your md5sums, and let's see if we have other differences.