yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] enomther:
cyrus13,

Yes you would follow the steps on POST #4 to perform a fresh install of the AOSP ... since there really is not an upgrade path between the TMO and AOSP. It should be treated as a fresh install.

~enom~
[G1 Android Development] sardoid:
This rom with blur theme looks amazing:)
[G1 Android Development] Micah71381:
The reason I picked this set of ROMs to use was because I could get a rooted pure ADP image (no extras). However, with the change to only offering the language pack version, and now adding in a custom lock screen plus the reboot option from the menu it appears that you are going away from that model and starting to add "features" to the image... which makes me sad. :(

Would it be possible to get all these extras moved over to the expansion pack instead of in the base image so those of us interested in just a rooted ADP image can still get it?
[G1 Android Development] enomther:
Micah71381,

As far as an untouched ADP Version of the rooted base ROM. I will always produce/host that ... so no worries there. If you want the ADP rooted base only, it's not going anywhere. I was only referring to not updating the expansion packs for the ADP build.

As far as the reboot option and the lockscreen, these features are difficult to cleanly add to the expansion pack only, thus the most stable and uniform way to add these features was to the newer rooted base. These features are harmless if you really want to use the AOSP rooted base.

Finally, I'm probably going to reverse my decision to not continue to update the expansion packs for ADP. But I will also likely not port as many themes for it (we'll see). As you can imagine maintaining (4) ROM's that are extremely similar yet also different, is an experience worthy of driving most mad. At times, maintaining all (4) does get convoluted. I still haven't finalized one way or another regarding the expansion packs for the ADP. But if I remove the HERO transitions/animations from the expansion packs, there exists a strong likely hood I could consolidate the ADP and AOSP expansion packs into one. I'm still looking into this.

~enom~
[G1 Android Development] bubonik:
Im a bit confused why you keep managing the theme packs, it seems that with 2.2 all the work can be done on the server. Each file can be updated as necessary, and the end user couldnt tell the difference.

Maybe im missing a step though.
[G1 Android Development] Micah71381:
Ahh, I didn't realize that the ADP version was still updated, just not the expansion packs. Since that is all I am looking for I am back to happy with the builds you provide (specifically the ADP and the T-Mobile unmodified rooted base builds). Thanks for all the hard work you have done!
[G1 Android Development] Charbo:
I'm having a weird problem, I've been using your roms for a while with no problems but this morning I went to install DRD20. It seemed to install fine along with the expansion pack and I wiped phone and sd card before installing. But when its done it just stays on the G1 screen. I waited almost 30 mins and it wouldnt go past so I installed the adp DRC83 and its working fine, but I'd rather use the newest one... Is anyone else having this problem or just me and what can I do to try to fix it?
[G1 Android Development] enomther:
Did you make sure you reformatted (or at least completely) cleaned out your ext partition?

You should do this when switching between any buils (including mine, IE: ADP -> AOSP)

That's likely the issue.

~enom~
[G1 Android Development] javacody:
Hey Enom, please excuse me if this has been asked before, but when do you plan on uploading the new 10MB kernel hack?

Thanks again for this great ROM!
[G1 Android Development] Charbo:
Yup, I've formatted everything I even tried remaking my partitions and it still wont work.
[G1 Android Development] enomther:
I did not 100% follow you here .... are you saying why am I bothering re-posting the AOSP themes ... when in v2.2.x it will change ?

Also, there will not be a server involved in the theme-ing process, the phone will do all the work. ;)

~enom~
[G1 Android Development] Vlad83:
After reading this post, I realized that my PDFViewer disappeared to. Your solution fixed it though. Maybe something screws up in the upgrade... Are you using Maps3.2 or should I push manually?
[G1 Android Development] bigl34461:
I'm having a problem. My phone goes to a blank screen after thr android screen is done loading. Do I need to reformat my sdcard? Can I just reformat the ext3 partition?? If so how do I do it? Sorry for the noob questions
[G1 Android Development] BloodyWasHere:
hey i decided to give the blur theme a shot, n it looks cool, but outa curiosity, how do i go back to the default theme that came with the rom without relying on the nandroid? i thought installing the expansion pack again would do the trick, but the icons that changed from the theme didnt go back to normal.. so i assume theres a better way?
[G1 Android Development] BloodyWasHere:
yeah you'd have to reformat the card, but u can just format the extension using amon ra's latest recovery image... http://xdaforums.com/showthread.php?t=530492.
[G1 Android Development] dhaneshje:
Theme problem

Hi guys,,

I have installed AOSP 1.6_r1.4(on my european T-Mobile G1) and the expansion pack v2.1.2.

When I install the appropriate Hero theme,, after the install I see no difference,, it doesn't work.:(

What's the problem here?:confused:

Thanks in advance

Grtz Dhanesh
[G1 Android Development] Vlad83:
Enom never mind, see that you are using Maps3.2.

Also, when I go into the market and try to disable the update notifications it FCs on me.

Can't wait for the 107mb boot image and the home replacement option in the next exp :)
[G1 Android Development] Charbo:
Noone else is having my problem? Ive wiped all the partitions on my sd card to make sure there was nothing there and it still wont work with DRD20... the AOSP versions have worked find for me before and the ADP version works for me just not DRD20.
[G1 Android Development] marty22877:
completely wipe all of the partitions off your sd card, reformat it to fat32, wipe your phone, apply the base rooted AOSP rom, then apply the expansion pack, then reboot the phone, does it load up? enom's roms always take a good bit for me to load up the first time.
[G1 Android Development] Charbo:
I have removed and remade all the partitions and wiped and it still doesnt work.
[G1 Android Development] dhaneshje:
Theme problem

Anyone?

Do I need a special SPL for the themes or something?

Btw, when I install the theme, the progress bar in the recoverymode(RA1.2.3)goes half way, it says copying files and then suddenly it's finished installing.

So it looks like the installer doesn't complete the install of the theme:confused:

grtz
[G1 Android Development] marty22877:
reformat it to just fat32, that's it, no ext2/3/4, just like stock phone, then wipe, then flash
[G1 Android Development] marty22877:
what happens when you boot it up? is the theme applied?
[G1 Android Development] Vlad83:
If you convert to Fat32 without repartitioning an ext, you will not have app2sd. Just wipe ext, install Base, let the phone load, reboot, then apply exp pack.
[G1 Android Development] dhaneshje:
Theme problem

When I boot up, there's nothing changed, the theme is not applied, nothing has happened,, reflashing of ROM's, and expansion packs always goes without trouble, but theming somehow doesn't work.

It's also strange that the updating progress(when flashing a theme) is sorta cutoff half way and says it is finished,, like I mentioned before.
[G1 Android Development] marty22877:
true, but he's got a stock card, if he formats to just fat32 he'd have to completely reformat the whole card, then we can eliminate the partitions as being the problem. if that works, then he can go back and repartition out
[G1 Android Development] cigar3tte:
Tried two approaches from my current AOSP 1.6 r1.2:

1. Flashed AOSP 1.6 r1.4 straight up, result is boot loop of the ANDROID splash screen.

2. Flashed AOSP 1.6 r1.4 followed by exp pack 2.1.2, no reboot in betwee, results in black screen.

Any ideas? I know a full wipe (data and ext) will probably fix this, but I'm coming from AOSP r1.2 and really don't want to do so for just two new features. I'm updating the same build.
[G1 Android Development] marty22877:
are you booting after the expansion pack? and then going back into recovery and flashing the theme?
[G1 Android Development] d3rrty1:
erm, I have used the search function for this thread as I have not experienced this before on any other ROM but I can't seem to find an answer.

I am having a slight annoyance really. I have recently switched from xROM and noticed that under any music application (I use the default music player, Meridian and Ringo Pro to test this), the Artist and Album sorting method does not work at all. I can search all music and type the artist or album name, but the individual selections themselves do not work.

I've tried to add more music but it still does not work.

any help or possible bug?

My music shows up, but the convenience is what I'm shooting for =|
[G1 Android Development] d3rrty1:
The problem is more than likely that the r1.4 and 2.1.2 exp pack are linked. And as stated in the first post i believe, if you install the exp pack on top of an ext2 partition and result in a black screen, then you need to wipe and possibly format.
[G1 Android Development] dhaneshje:
Theme problem

I have tried installing the theme after installing AOSP 1.6_r1.4 without the expansion,, doesn't work...with the expansion it also doesn't work..

But both times I have booted before theming..
[G1 Android Development] cigar3tte:
I'm not understanding the part about "install the exp pack on top of an ext2 partition". What other way is there (I'm on ext3 btw, but I don't think you meant ext2 specifically)?
[G1 Android Development] Charbo:
I just tried it like that too and it still doesnt work
[G1 Android Development] bubonik:
Sorry about that, let me try again.

Since you havent given us information about how the theming will actually take place. I am assuming that each component of the theme is downloaded, zipped, and flashed accordingly. Which allows you to manage files on the server level individually, thus allowing the end user total ease.

That is why I was a bit surprised that you released a revised theme pack.

Is there a reason you havent provided the lockscreen via expsetup in 2.2? Seems logical since its themeable.
[G1 Android Development] bubonik:
Redownload both the base and expansion pack. If it still fails, get another sd card. Although I havent tried 1.6 r1.4, I am using 2.1.2 on r1.3 without any issues.
[G1 Android Development] mailman1387:
Enom

Ok how do i install nandroid?Do i just flash it on the current rom im on right now and its intalled or is there something else?Also is the phone.APK V10 on the new ASOP rom yet?And will you eventually add in your exp pack the app that give you the option to disable apps that start up on boot?
[G1 Android Development] LucidREM:
NANDROID

nandroid is included in most every recovery.img i believe .. boot with HOME+POWER to get into it .. i use AmonRA's recovery myself .. very easy to use
[G1 Android Development] olearyp:
He's continuing to support existing users who "upgrade" to DRD20. I'd have held up on DRD20 myself, but it's his release process, it's just more work for him.

enom hit this a few pages ago--the lockscreen is tied into the framework, so apparently it's not trivial to make it an option. It might not be ready for 2.2.x but he's probably working on it.
[G1 Android Development] qwerty3656:
Charbo;

What method are you using to repartition your SD drive (UBUNTU?, AMON_RA?, Paragon?)?
[G1 Android Development] mailman1387:
I dont have the new rec img.I have the old jf img and its not included.im going to dl the one you mentioned but do i just flash it an if so can i just flash it on the current rom im using?
[G1 Android Development] bubonik:
You just have to put back the previous framework for it to function like it did without stericsons lock. I think the enoch themes made this work, with a fair amount of ease.
[G1 Android Development] jamerican413:
I had your problem. Stumped me for half the night. What I ended up doing (and it worked) was to wipe, reflash the base, reboot, check to see that it's working (which it did), then reflash the expansion pack. Everything has worked fine after that, except for wifi, which I'm still looking into...
[G1 Android Development] jamerican413:
I'm not getting the plastic theme after switching to aosp from T-Mo. The only thing I get is the lockscreen. I will try another theme to see if it works...

Just flashed the Hero theme; that's not working for me, either. So I don't have working themes nor wifi (with AOSP...)
[G1 Android Development] JackD3ath:
There are instructions for installing a new recovery image in the information thread. I believe also in the main thread for Amon RA recovery .
[G1 Android Development] Jdom58:
guys need some help pronto, I tried to use the lucid script:

lucid -rc -ra then lucid -u to upgrade my sons revovery to Amons and I'm stuck on the G1 screen when I reboot into recovery.

He is already on TMO1.6 with exp pack 2.1.2. and had cyanogens recovery

'If I pull the battery I can turn the phone on and it will go to launcher but I cant get to recovery, need help quickly or my rear is grass. I can't remember if I'm forgetting something
[G1 Android Development] blueheeler:
Have you tried this and have it work?

Enom sent me framework files last night to try, and unfortunately it wasn't successful.

If you did get this to work, can you please tell me exactly what files you used (filenames, from what theme and version of the theme)?

Thanks.
[G1 Android Development] Joe333x:
http://xdaforums.com/showthread.php?t=566669

instructions are in first post. You should be able to just flash it through terminal emu. Thats what i did anyway.
[G1 Android Development] enomther:
Goto Amon_RA's thread and manually download the recovery image.

Copy this to your son's sdcard and name it like amon_ra_rec_123.img.

Then open up the terminal app and perform the following ...

su
flash_image recovery /sdcard/amon_ra_rec_123.img
exit
exit

That should fixup your recovery. Do this asap.

~enom~
[G1 Android Development] bigl34461:
some more dumb questions

Is apps2sd automatic on this rom?? I had to wipe my ext3 partition to finally get this rom annd expansion pack working. How do I pullup my apps of my sdcard?? Or I don't have them anymore since I wiped ext??
[G1 Android Development] bubonik:
I personally had no need to, so sorry I cant help. http://xdaforums.com/showthread.php?t=548918 this guy got it to work with his themes. You might have to reflash a theme or something.
[G1 Android Development] LucidREM:
Recovery

i hope you did "lucid -u" first before "lucid -rc -ra" .. the "-u" option gets you the latest version of the script .. but go with enom's link to manually grab the image .. tho .. JF's recovery has the nandroid as well .. it should work
[G1 Android Development] Jdom58:
enom I get

usage: flash_image partition file.img

any ideas
[G1 Android Development] enomther:
Make sure you don't have your phone mounted to your computer ... and then make sure the filename is correct.

~enom~
[G1 Android Development] Jdom58:
No that was it first time i tried it I did lucid -rc -ra first -u second. after I got stuck on g1 screen rebooting into recovery is when i realized it was the other way around. I tried it the right way afterwards but still no luck.

Enom it is a zip file I'm trying to flash here correct?

flash_image recovery /sdcard/amon_ra_rec_123.img

I get

error openning /sdcard/amon_ra_rec_123.img: no such file or directory

I've double check it is on sd card as zip file
[G1 Android Development] ohnoezmahfone:
thanks, I also had missing maps, etc. after flashing from ADP1.6r2/exp2.1.1 to ADP1.6r4/2.1.2, and that sorted me right out.
[G1 Android Development] bubonik:
Files are case sensitive in linux.
[G1 Android Development] Jdom58:
is there a way to go back to cyanogens recovery to at least have a functional recovery?

Ok never mind, got this done :-)
[G1 Android Development] mplspatch:
lockscreen?

Hey, probably a silly question, but what is the lockscreen? Is it just a theme that shows up instead of black when you lock the screen? Does that consume more power?? I saw some screen shots online, but cant figure out what it is. Was curious before I download the new updated ROM
[G1 Android Development] Jdom58:
Thanks bubo but I'm using terminal on this and renamed the zipfile all lower case
[G1 Android Development] Jdom58:
Hey everybody thanks for your input, finally got it going :-)

reflashed Cyanogen recovery "lucid -rc -cy" which worked and then started again in the right order this time with "lucid -u" and "lucid -rc -ra" and all is good now whew close one.

Installing AOSP now and QUICKLY returning the phone back to him.

Thanks Again
[G1 Android Development] olearyp:
This is the screen that appears whenever you wake the phone with any key other than "menu". The default one shows carrier, time/date, charging status if plugged in, and a short help. Stericson's also allows you to control music, always shows battery status, and does a few other things without unlocking first. Due to the deeper integration of the lockscreen (one of the few things that's not an app) it's hard for me to track down a good description.
[G1 Android Development] leiko49:
Could you suggest how I could do this?

Thanks

Dave
[G1 Android Development] enomther:
Terminal will likely not work either, right? no keyboard? (not sure myself)

Also,

after you got your prompt#, did you type

mount /data

??

~enom~
[G1 Android Development] leiko49:
I thought I did, but I didn't try that, but, same as before after

1. typing at # "mount /data" [without the quotes] I got another #

2. at the second # I typed in "rm /data/misc/akmd* /data/misc/rild" [without the qoutes.

3. the message was same as typing rm /data/misc/akmd* /data/misc/rild directly without the mount /data code, which was:

rm /data/misc/akmd* /data/misc/rild

rm: cannot remove ' /data/misc/akmd* :no such file or directory

rm: cannot remove ' /data/misc/rild* /data/misc/rild' : No such file or directory

DAve
[G1 Android Development] enomther:
Do you get any output when you

mount /data
ls /data

??

~enom~
[G1 Android Development] leiko49:
hmm, this time when I typed the code mount /data I got

mount: mounting /dev/block/mtdblock5 on /data failed: device or resource key busy. Before i just got another #.

When I typed ls data at the # I got

anr app-private data lost+found property

app dalvik-cache local misc system

Dave
[G1 Android Development] leiko49:
I did an "ls /data/misc" command at # and got

hcid rild_ril.chm.mids

rild_nitz_long_name_310260 rild_ril.chm.mode

rild_nitz_short_name_310260 rild_ril.clip

rild_ril.band.select-mode rild_ril.prefer.network.select-type

rild_ril.chm.dcss rild_ril.pscall.authentication

don't know if this helps

Dave

I just rebooted phone into recovery mode, and now when I type mount /data I get another # as before. just needed to be rebooted.
[G1 Android Development] enomther:
So yea it sounds like the 'rm' commands are failing b/c there's nothing to remove.

try

ls /data/misc/akmd*
ls /data/misc/rild*

let me know the output, but if it says no files found or something like that, then you've already delete the files properly. Try rebooting the phone and see if it's fixed.

~enom~
[G1 Android Development] leiko49:
When I type in ls /data/misc/akmd* I get no such file or directory

when i type in ls /data/misc/rild* I get

/data/misc/rild_nitz_long_name_310260

/data/misc/rild_nitz_short_name_310260

/data/misc/rild_ril.band.select-mode

/data/misc/rild_ril.chm.dcss

/data/misc/hcid rild_ril.chm.mids

/data/misc/rild_ril.chm.mode

/data/misc/rild_ril.clip

/data/misc/rild_ril.prefer.network.select-type

/data/misc/rild_ril.pscall.authentication

should i try: rm /data/misc/rild*

Dave
[G1 Android Development] enomther:
yes ... do run

rm /data/misc/rild*

reboot and let me know.

~enom~
[G1 Android Development] leiko49:
the command effectively removed the rild files. I did a ls /data/misc and the directory was indeed empty.

unfortunately, when rebooted, the auto rotate did not work (orientation is checked in settings)

:mad:
[G1 Android Development] enomther:
yeah, and still no word from anyone more informed as of yet.

Here's what I'd try, if I were you.

Download and Flash cyanogen's latest build 3.9.11.2 as a test. If auto-rotate doesn't work with his build, then it's likely hardware ... if it does then we know it's my OTA build.

Give this a show, it's your best bet to quickly determine if it's HW or SW.

Just what I'd do, while awaiting more answers.

~enom~
[G1 Android Development] leiko49:
wouldn't you know it, the one rom I didn't try yet. If this don't work, and we don't here the word from those above, then I'm gonna wanna unroot. Before we go with that I'll try to "one rom to rule them all" cyanogen deal.

I sent a minor donation for your efforts to assist. More later when I have been liberated from my cellular problem.

Dave
[G1 Android Development] enomther:
lol ... much appreciated Dave. I really hope Cyanogen's ROM rules you well!! ;)

Please let me know the output of that and thanks for the donation. I'm sure things will get sorted out, one way or another.

~enom~
[G1 Android Development] enomther:
Hey Dave,

So since I was bugged by this MyTouch issue (and I haven't heard back from people) ;;.. I went ahead and reverse engineered the latest cm-3.9.11.2. And there is indeed several differences in terms of sensor libs, etc. So I'm sure this is a software issue with my OTA build. After all this was pulled and built for the G1, not the sapphire/magic/G2, whatever ;).

I'm sure in short time I can get these sapphire components incorporated into the OTA expansion. Till then, I'm almost certain cyanogen's will work for you.

~enom~
[G1 Android Development] leiko49:
Enom,

the one rom that rules them all indeed. rotation up and running. all and all the programs are a bit slower then yours, yours was similar to Haykuro's (which also did not support the sensor). way way light speed faster then dizzy drake's, which also did not support the sensor.

I would likely swear allegiance with your speedy rom once you apply the knowledge we have gained from your efforts to assist me in turning the perfect dreaded spl into the perfect rooted state of art mytouch.

another donation is on its way.

Cheers

Dave
[G1 Android Development] enomther:
Hey Dave,

I'm gonna break ground on this move towards MyTouch support. After all this is TheOfficial, so there outta be a version for MyTouch users. I move this into the v1.6 line. Can I count on you to help me do a PREBETA-test? Once I have it ready, my ETA would be roughly 1 week.

Till then cyanogen's will hold you tight.

Let me know!
[G1 Android Development] leiko49:
No doubt, be happy to.

yesterday someone posted on cyanogen's thread exactly what we were looking at, again referring to the failed method we found was only good for g1 (I let them know).

http://xdaforums.com/showthread.php?t=539744&page=424

second post down by cracker tc. apparently cyanogen's is somewhat unstable with the auto rotate as well.
[G1 Android Development] enomther:
Awesome, greatly appreciate the donations. Like I said, give me a week and something should like be ready. I'll PM you with a prebeta-link once ready.

Thanks again!

~enom~
[G1 Android Development] enomther:
CIFS & FUSE Kernel Modules

Hi BeRo1985,

As promised, I've attached the fuse & cifs kernel modules (kmods.zip), place em and use em as needed.

I'll likely throw these into the v1.6, since someone has a need. I've tested these over Wifi and mounting SMBFS (cifs), all is well.

Again, unionfs support is built into the kernel, so you've already got that!

Let me know if you need anything else BeRo1985, definitely want to support other devs.

~enom~
[G1 Android Development] dta1974:
This might be off topic but I have to say it.....you are great man,you keep helping people,replying,taking care of everything etc....Like a said you are great.

Thank you so much,I really appreciate it. ;);)