yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] amarkow2:
yeah i understand that now...where can i go to set it up...the guides i have searched for have not worked for me...
[G1 Android Development] sasa3791:
yes i have it,

it looks like when finished with download,

says that the download finished, but nothing in the folder it is empty

where's the problem?
[G1 Android Development] ceas909:
i get a force close when going home.. the advanced launcher home force closes... not my apps...when im in advance launcher home and switch to landscape view it gives me the advance launcher forclose...
[G1 Android Development] bmj1086:
Oh, then that issue is addressed in my first link in my signature.
[G1 Android Development] bmj1086:
Must be something with the downloading in the expsetup. I would try and get a direct link to the download so you can just do it on your own. I wouldn't know where to find it. I don't think its listed on the OP of the MOD. I'm sure enom knows.
[G1 Android Development] jonstanley2:
quick question

Im running off the htc 1.6 root base and the older expansion pack before the v2.0.1 expansion pack.

If I want to flash the newer 2.0.3 would I have to wipe and flash the the root base along with expansion pack or just flash the expansion pack on top of what I have with no wipe?

Thanks fer your helppp :D
[G1 Android Development] mikespy:
Just flash 2.0.3 right on top of 2.0.1. If you have a theme reflash on top of 2.0.3 just in case. ( sometimes themes can be touchy)... Enjoy.
[G1 Android Development] sasa3791:
direct link is somewhere on http://www.androidspin.com, but i cant find it

what is the name of file?
[G1 Android Development] jonstanley2:
thanks mikespy youre my hero :d
[G1 Android Development] mikespy:
If i won't do there is always a HERO theme you can use...:D
[G1 Android Development] jonstanley2:
actually I am using the hero theme too

Ill just put your picture as my background on it tooo!

haha jk

but i will reflash the the theme like ya said just in case it decides to fail

thanks for yer help again
[G1 Android Development] mikespy:
LOL......:)

I'm using the HERO theme also and noticed after installation of an expansion pack the LETTERING/FONT on the notification bar turned black making it hard to see(Should be white) so i just reflashed the theme and viola!!! Sucess.. Just do them back to back 2.0.3 then the V2 Hero theme and done....
[G1 Android Development] joshuas_79:
OK, I have installed this:

AOSP-1.6_r1.2 + ADP DRC92

-- Rooted-Base

----- v2.0.3- Expansion-Pack - , it worked fine.

then I downloaded this template

HTC-ADP-CRC1

I modified and signed, and then flashed it. But now, it stays in Vodafone logo screen. What did I do wrong?
[G1 Android Development] mikespy:
I believe those templates are for Cupcake builds only and you now have a Donut build... So i don't think they work...( i could be wrong tho)...
[G1 Android Development] amarkow2:
ok found a great script someone wrote and it did everything for me! http://xdaforums.com/editpost.php?do=editpost&postid=4750610 got apps2sd working now!
[G1 Android Development] cloverdale:
CRC1 is cupcake, you are correct on this one. You need the template for DRC92. (note that C=cupcake, D=donut on the release numbers)
[G1 Android Development] cloverdale:
Just download Amon Ra's recovery 1.2.3, and there is an option to partition your sd directly from the phone, with absolutely no work.
[G1 Android Development] mplspatch:
This guide is pretty good. Just download the sdparted file, and follow the instructions "to install from w/o computer." This way you can do it right from your phone. Just note, the example used for the executing command will create an ext4 partition, that many people are reporting problems with. It lists other commands at the end of the instructions. I'm using ext3 with no issues. Also, when it asks you if you are sure you want to erase the data, the Y/n must be a capital Y.

http://xdaforums.com/showthread.php?t=543985
[G1 Android Development] chowdarygm:
hi,

i followed the same way as mentioned above but all my work went waste, the app doesnt partition the card at all.....

infact found out the easiesttttt way to do this @ cyanogen mod wiki click HERE ,note:u need CM recovery to do this
[G1 Android Development] olearyp:
The quick read (if I'm parsing this log right) is that Dalvik is choking (actually, segfaulting) on /system/framework/core.odex. That shouldn't be happening as long as the VM running the odex matches the VM used to create the odex, which it should as long as you're using a matching set of ROM parts. Interesting. I don't think you said you were running the expansion pack, but if you are, make sure the expansion pack matches the ROM (AOSP, ADP, or TMO). That would be a possible cause for a VM mismatch.

EDIT: I also see libnativehelper in the stack--JNI gone wrong?

EDIT 2: Hopefully someone can solve this with experience, because without debug symbols it's really hard to figure out what's going on.
[G1 Android Development] keenerb:
THis was a freshly re-rooted device running just the TMO DRC83 rooted rom from page 1 of this thread.

I figured it must be a Dalvik VM problem when I compared log files from my functional nandroid backup.

Hope someone can help me make sense of all this...
[G1 Android Development] olearyp:
That's what I'd thought you'd said.

It's crazy that something this low-level (but still software-related) would go wrong for one in hundreds (thousands?) of installed devices, especially because it does work on OTA. Have you tried the AOSP build? A completely different ROM? And you (going back through your post history) are able to run TheOfficial TMO Cupcake?

I'm still wondering about /system/framework/core.odex--on AOSP that shouldn't be odex'ed so you shouldn't run into this problem. That might at least narrow things down. Sorry this isn't a hard answer. More fun for me (than dirty ext partitions and USB Debugging turned off) but worse for you, I'm sure.
[G1 Android Development] keenerb:
I've tried AOSP, TMO, and ADP builds from this site. I have avoided other roms since many require flashing radio/SPL and I'd like to avoid that if possible.

I've been able to flash the TMO DRC83 rooted at least three times, but when I tried to switch to AOSP all this started happening...

Re-flashing AOSP and I'll get a dump from it.
[G1 Android Development] enomther:
keenerb,

You keep saying that you are "freshly rooting" ... can you post a link to the process you are following to "freshly root" ... as this should be an unneeded step .... especially if a nandroid restore is funtioning.

~enom~
[G1 Android Development] enomther:
Minus Theme posted for AOSP

All,

david1171's Minus theme has been ported/posted for the AOSP-1.6_r1.2 build.

See post #7 ... if you like ... don't hesitate to show david1171 some love ... enjoy!

~enom~
[G1 Android Development] olearyp:
FYI, since you're on a myTouch, you already have the latest radio, and if you're rooted you do not need a new SPL. In fact, the "Danger SPL" is a port of the SPL from the Sapphire (myTouch) to the Dream (G1) for running larger ROMs. If you have a myTouch, you already have the ability to run those ROMs without further modification.
[G1 Android Development] nabzilla1990:
hey enom ur really good at this have u thought about porting some of the new roms specifically the blur one only needs a wifi fix i tried doing a logcat cant figure out why its not working
[G1 Android Development] keenerb:
I know it should be unnecessary, but I try it just to se eif it fixes anything.

Initially, I was running your TMO DRC83 Rooted base, with 2.0.2 update pack.

I wanted to try AOSP. I made a nandroid backup, and did a wipe of user data through the Cyanogen Recovery Loader interface, and applied the AOSP base pack via the recovery update.zip menu item.

After this, the phone would not boot unless I restored my nandroid backup. I wiped user data and re-applied TMO DRC83 rooted base and still nothing, even though I've had no problems the first two or three times I did this.

A few times I have gone back and re-flashed TMO 1.5 official, and re-rooted with one-click root and walked through the entire process again, but everything currently leads to a Mytouch3g green screen and nothing else.
[G1 Android Development] enomther:
keenerb,

OK ... here's what I need you todo for me ... nandroid restore to your functioning TMO build.

Go into Terminal ... (you'll need to download BetterTerminal for Magic from the Market) ...

su
expsetup

Option #8 ... this will gen a ep_log_XXXXXXXXXXXXXXXXXXXXx.log file to your sdcard. Send this to me ... at .... enomther at gmail dot com.

I'll have a look'sy and get to the bottom of this.

~enom~
[G1 Android Development] rattlesnake8:
between AOSP 1.6 and TMO 1.6 , which one is more fast

??
[G1 Android Development] AGunz82:
I must agree, this is way smoother than Cyanogens. Cheerz!
[G1 Android Development] keenerb:
The AOSP rom is doing something a little different.

It repeats the following piece of code:

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

D/AndroidRuntime( 116): CheckJNI is OFF

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

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

W/dalvikvm( 116): Size mismatch on inflated file (3585628 vs 3591576)

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

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

D/dalvikvm( 116): VM cleaning up

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

W/dalvikvm( 116): JNI_CreateJavaVM failed

E/AndroidRuntime( 116): JNI_CreateJavaVM failed

D/AndroidRuntime( 117):

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

D/AndroidRuntime( 117): CheckJNI is OFF

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

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

W/dalvikvm( 117): Size mismatch on inflated file (3585628 vs 3591576)

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

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

D/dalvikvm( 117): VM cleaning up

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

W/dalvikvm( 117): JNI_CreateJavaVM failed

E/AndroidRuntime( 117): JNI_CreateJavaVM failed

"Size mismatch on inflated file (3585628 vs 3591576)"?

I've downloaded this three times. Could it still be corrupt? Can someone throw up an MD5SUM of the file?
[G1 Android Development] olearyp:
Well, at least you're not the only one. No solution found so far, though. If you (or enom) does figure this out, he'd probably like to hear about it.

EDIT: alpha22 has asked this in a lot of threads with no ideas. The best guess so far is that the hardware is toast.
[G1 Android Development] enomther:
Hey guys ... I truly appreciate the kind words ...

Actually I'm sooooooooo swamped with what I've got goin on with my current ROM set and my "real life" (yes I have one of those too, lol) ...

I'm really hoping some1 else (a heavy hitter ... I won't name names out of extreme respect) ... but I'm hoping ... will take up that work ... and bring it full circle. I'd be happy to help that effort .. and also happy to sit idling by ....

All that said ... for now (cuz things do change) ... my plate is full ... for a solo operation on motoblur. ;) ... But I'm always there to help others.

And FWIW ... there are still several things not functioning on MotoBlur, Wifi is just one of the bigger issues.

~enom~
[G1 Android Development] keenerb:
This is moderately entertaining.

On one of my functional Nandroid backups I have Myfave, PDFViewer, and Quickoffice listed in my application drawer.

I'd be willing to bet I applied the wrong updatepack over a TMO base image at some point.

Doesn't explain what's wrong with flashing just the base rom, but it's interesting nonetheless.
[G1 Android Development] olearyp:
Possibly, but that shouldn't be permanent. I didn't know I wasn't the toppost anymore; read my edit above for less encouraging information :( (and/or :confused:)
[G1 Android Development] keenerb:
Email sent.
[G1 Android Development] keenerb:
Yeah, I found that one already.

Very strange.

I've got product replacement on my phone. I'll just run over it with my car or somesuch and get a new one if that's the case.

I had considered that perhaps the internal flash had gone bad, it would explain the problem!
[G1 Android Development] olearyp:
LOL, I'd say send pictures, but uh that might be evidence.

If it weren't for the fact that you'd lose root, and the ability to apply one-click root, I'd really like to know if 1.6 OTA would run. Obviously that would be grounds for replacement right there.
[G1 Android Development] keenerb:
I'll do that.

I can always re-flash 1.5 if I really want one-click root.

Another odd thing: 2.0.3 applied just fine.
[G1 Android Development] enomther:
keenerb,

K ... there is some interesting stuff in there regarding your sdcard partition layout. I don't know if it's related ... but your SPL, recovery and NAND appear to be in working order, so no need to continue re-rooting. That said ... please perform the following steps exactly ...

1) Redownload the AOSP rooted base from the OP. Ensure it's MD5 Checksum matches ... AOSP_ADP_1.6_r1.2_DRC92_rooted_base_v2.zip) = 7a067b6addd92345590a828b9288575a

LINK HERE!

2) Place the rooted base on your sdcard and name it "enom_test_update.zip".

3) Reboot into recovery.

4) Perform a DATA WIPE (factory default).

5) Flash w/ the anyzip flash option. Please note to look for the strange "enom_test_update.zip" name. If you don't see it ... stop and report back.

6) Once it's finished flashing ... pull the battery from your phone ... to power off.

7) Remove your sdcard.

8) Replace the battery and boot up the phone.

This should allow you to boot into the AOSP rooted base. Give this a try and let me know.

~enom~
[G1 Android Development] keenerb:
OK. Verified download md5sum, copied to sd, verified sd md5sum.

Followed the rest of the instructions to the T.

And...

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

D/AndroidRuntime( 90): CheckJNI is OFF

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

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

W/dalvikvm( 90): Size mismatch on inflated file (3585640 vs 3591576)

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

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

D/dalvikvm( 90): VM cleaning up

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

W/dalvikvm( 90): JNI_CreateJavaVM failed

E/AndroidRuntime( 90): JNI_CreateJavaVM failed

D/AndroidRuntime( 94):
[G1 Android Development] dchiare:
Userinit.sh

Hi All,

First off, I have been searching for the answer to this question and I have not been very successful. Around page 170 of this thread there was a little discussion about using a userinit.sh file with this rom but as far as I can tell the discussion dropped off.

My want: To use a custom userinit.sh file in order to bypass using expsetup. More specifically, I want to use CompCache with backing swap rather than linux swap which is what expsetup allows for.

I read that using userinit.sh version 1.53 will not work because it only works with Cyanogen roms, so what userinit.sh file can I use with this rom and what steps do I need to take to use it other than enabling userinit.sh in expsetup?

Any help would be greatly appreciated.

Thanks!
[G1 Android Development] olearyp:
A linux-swap partition will be used as backing swap for compcache starting in the 2.x series. Here's the relevant changelog lines:
[G1 Android Development] dchiare:
Thanks for the response. I guess i now need to update my question as it appears compcache with cc_backingswap is the default.

My question now is: where is the script that sets those defaults. I know expsetup can change swappiness but i would also like to change the the compcache disk usage and the backing swap disk size as well.

Thanks for you help.
[G1 Android Development] olearyp:
I believe that stuff is handled in /system/bin/expinit, but Thar Be Dragons Here, since that's the script that makes the ROM go 'round. Mess with at your own risk, etc.
[G1 Android Development] ceas909:
ok but i have nothing on my advance launcher home screen but the message, internet, market and contacts icons....

well i jus gave in and re partitiond my fat32+ext3+swap and re flashed the whole rom... and then reinstalled my apps... and blah blah blah.... so its seems to be working ok now.... i jus wished i could of done somthing eaiser so i wouldnt of gone through all that... but ne ways i had to do wat i had too... thanks for ur help!!
[G1 Android Development] dchiare:
Thanks, I am looking through it now. I am keeping watch for dragons. I found the entry for the CompCache settings.

I find it kind of hard to believe that this would be the only way to change CompCache settings especially because it is so easy to do so using userinit.sh and a user.conf file.
[G1 Android Development] bmj1086:
Well, in that case we would need a logcat.

Do you have your SDK tools working?
[G1 Android Development] bmj1086:
I do the best I can with the time and knowledge I have. If I can't figure something out then I refer them to you or olearyp since you guys know a little more than me. Its hard because I leave for a few hours and come back on here and there are three or four more pages lol. As long as we can get people to read the first page of this thread then we could lower the amount of posts a lot.
[G1 Android Development] aneece98:
Black screen after expansion solution

I too flashes the root, thn the expansion and encountered black screen at boot. To fix this i simply reflashed the root and retained all features. If i missed this step sorry to repost, but I had to do this on almost every set i used
[G1 Android Development] ceas909:
well i jus gave in and re partitiond my fat32+ext3+swap and re flashed the whole rom... and then reinstalled my apps... and blah blah blah.... so its seems to be working ok now.... i jus wished i could of done somthing eaiser so i wouldnt of gone through all that... but ne ways i had to do wat i had too... thanks for ur help!!

update.. after doing this no more forcecloses.. but now apps2sd not working...:(.. so i started all over again... but installed exp pack 2.0.1 the updated to 2.0.2 and then finally to 2.0.3.... and now i think its working great... no force closes and apps2sd working...
[G1 Android Development] tantrix:
Tried it.. installed the base + expansion pack. Had a newly created ext4 partition. Don't think the apps2sd is working. Any way I can confirm?
[G1 Android Development] zimphishmonger:
Somewhat rough, but you could go to terminal and type the code below. If anything comes up (besides no such folder), it means the system is using the ext2/3/4 partition on your sd, aka Apps2SD.

su
ls /system/sd
[G1 Android Development] joshuas_79:
Thanks, I was sure it was something lilke this...

Can somebody post a donut theme template or help me to get one?
[G1 Android Development] Pfeffernuss:
Nice, way to go man! Any chance of porting the Plastic theme as well? :rolleyes:
[G1 Android Development] enomther:
Pfeffernuss,

Don't roll your eyes at me! lol

Not my fault. ... I had it fully ported (v1.5) ... and then I went to his thread for some screenshots ... and he has v1.6!!!! (which looks wayyy nicer) ... So I starting porting that ... only to find that his theme breaks the music widget.

So as soon as he fixes that ... I will post it.

~enom~
[G1 Android Development] enomther:
joshuas_79,

I will try to post theme templates today ... I'm currently working on a v1.9.x for my Rogers ... I gotta show some love and get that pumped out ASAP.

Anyhow ... theme templates soon.

~enom~
[G1 Android Development] enomther:
dumbestcrayon,

You cloverdale, olearyp and mikespy's efforts are gr8ly appreciated!!! :)

I can actually take breaks now . ... periodically .... lol

TY

~enom~
[G1 Android Development] enomther:
Yeeew ... yea sorry I didn't get to you last night ... fell asleep ...

But if you are still getting that after following my instructions exactly ... you must have some form of a hardware issue. It's the only thing that makes sense at this point if you truly followed the steps.

~enom~
[G1 Android Development] enomther:
userinit.sh/user.conf combinations came on the scene shortly after I had exploded into the use of my exp script set ...

Unfortunately ... the userinit.sh/user.conf script available have ALL been highly talored to cyangoen's kernels and modules ...

That said ... I'll attempt to port one to be compat with my builds ... and I'll post when possible, allowing users to use such a script when necessary.

~enom~
[G1 Android Development] keenerb:
Yeah, that's what I'm figuring.

Reflashed back to stock firmware, waiting for OTA update at this point. If it fails, I'll try to get a warranty replacement.

Would it be possible to get the core.jar and push it to the device somehow by itself?
[G1 Android Development] keenerb:
Strangely enough the OTA 1.6 upgrade worked flawlessly.

No clue what's up with this thing!
[G1 Android Development] olearyp:
Gah! And you can't just walk into the T-Mobile store and say "hey, I want a new phone, rooted ROMs just won't work" :)

You need some way to stress (and break) the phone that doesn't violate the TOS. I just don't know what that would be--I was hoping that it was endemic to Donut builds and the OTA update would still trigger it. Fresh out of ideas again.
[G1 Android Development] qwerty3656:
Camera?

I just noticed there is no zoom on the camera? Why not load a better camera?
[G1 Android Development] korami:
Numbers stored in international format - contact info not displayed

Hi enomther,

I am a happy user of your cupcake rom, but wanted to taste the donut. Flashing the rom (tried once the ADP and once the AOSP one) went ok, but came with the following issue: all my contacts' numbers are stored in international format, and when I receive a call from within my country (so without the international prefix), the caller id isn't recognized (some conversion missing). This occurs both before and after installing the ExpansionPack.

This defect was reported in cyanogen's rom a few months ago (see bug report here: http://code.google.com/p/cyanogenmod/issues/detail?id=4), which was fixed and appeared again in the donut rom and needed the same fix.

Do you know about this issue?

I'm back with my backed up Cupcake for now...
[G1 Android Development] torpex505:
apps on sd not showing in menu

I had the AOSP 1.6 "Extended" ROM installed, I decided that I needed Apps to SD. I re-partitioned the SD card and put it back in my G1. It took a while to boot up(I figured that was the auto-apps-to-sd working) When it finished booting, I found that none of my installed apps are displayed in the pull-up menu, or list of apps when creating a shortcut on the desktop. I ran "ls /system/sd" in the term and have lost+found, expstick, app, app-private, and dalvik-cache. Do I just need to reinstall? If so, do I need to wipe?
[G1 Android Development] olearyp:
"We know. Sit down." (with apologies)
[G1 Android Development] mgorman:
If we installed the 10mb patch can we increase compcache to get more speed out of the phone or is what its set at the best setting?