yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] arefin:
Any Help??

since this thread has the best support so far (actually its greatly supportive) I hope someone will respond to my problem.

I cant see my ext partition in the settings menu, I have EXT3

I also have seen the internal memory to fill up stack by stack with time, I am sure it's NOT CACHE because I have cache remover application (not the free version) and cache is cleared. With uninstalling apps biggeer apps like toonwarz the memory is released but not exactly by the size of the removed app.

I hope this is only with me, coz I am great Fan of this ROM, I will not switch because of this but some sort of solution would be nice.

I can see the partition in other ROMs like in Fasttest 2.8 for example.

Cheers,
[G1 Android Development] :
do yo use an automatic wallpaper switcher? that's what caused my random reboots. 90% of the time is an app that runs in the background that causes this.
[G1 Android Development] olearyp:
`lucid -pi' will show you if the partition exists, `df' will show you if it's mounted and non-empty.

Installing apps will always use some amount of internal memory, since /data/data (application settings) is still on the phone. I'm not sure where you're looking in Settings, by the way.
[G1 Android Development] qwerty3656:
I did a wipe and re-partition. I then just flashed the asop base and 2.6.2 partiton and google maps appears on my homepage. This should not occur, right? I am trying to do a clean install because I can't download the google maps download.
[G1 Android Development] enomther:
My bad guys, I botched the update-script this go around ... suppose 2.6.3 is in order :rolleyes:

Till then ... if you're good with adb ... wipe, flash base, flash expansion 2.6.2 and while still in recovery (before booting up) ... through adb ...

rm /system/app/Maps.apk

That will fix you up. Otherwise, I'll try and get 2.6.3 out tomorrow sometime.

~enom~
[G1 Android Development] enomther:
preciate it man!

also, @ Ace42, much appreciated!

ALL ...

Fix a couple links in the themes post #3 ... and added AnderWeb's and Ace42's updated theme links.

:)

~enom~
[G1 Android Development] qwerty3656:
That worked thanks.
[G1 Android Development] Ace42:
Sorry it took so long, brought a N1 and had no phone to test with.
[G1 Android Development] matt tallant:
advanced launcher problems

So.... I have tried everything that normally works and probably some overzealous stuff =) so I was all excited about 2.6.1 and barted my phone downloaded all the new aosp updates including the enoch theme and started updating. Did the base and exp pack. Rebooted and it told me my sd card was corrupted. So no big deal (use at your own risk right?). So I reformatted my sd and tried to install enoch and was met with a status bar and black screen. I could use the status bar and through some creative use of hot keys most of my apps. But who wants a smart phone with no desktop right? So I downloaded the no sterricson lockscreen version of enoch and the aosp template neither gave better results. I changed gusto to not install advanced launcher and everything worked fine. But I would really like to have advanced launcher back. The extra stuff that I did was in the midst of having the black screen problem I erased my sdcard and went to just fat32. When that didn't work I flashed back to rc29 by way of dreaimg.nbh and rerooted my phone. So having said all that please don't just say just wipe your ext2/3/4 and reflash enoch. I promise that didn't work =) any other ideas? I tried searching the thread but bugtracking on here is really hard to follow. If I missed please link me to the relevant post.

SySfS
[G1 Android Development] olearyp:
I don't know if anyone's used AL much recently. Alright, I'll bite. Fresh install of AOSP 2.6.2, switched to AL, used theme template, works fine. Flashed over with enoch (w/lockscreen), also works fine.

You said you wiped sdcard, but never mentioned wiping /data. Since it works fine on a fresh install, I'm gonna have to say it's probably something to do with that.

While I was in there with the fresh copy, I also confirmed that my new build process for GUSTO does sign packages in such a way that they are upgradable separately from enomther's release process. That's good, as there are a few features I'd like to get in there soon.

(Man, it's nice to have nandroid working reliably again! myTouch users--get Amon-RA's 1.6.2G recovery!)
[G1 Android Development] bitter1:
Hmm, ok.

Cannot get Loccy's Better Browser to work or install. Gusto doesn't seem to change anything regardless of what I do.

Trying the ADwone Theme boots to a blank/black screen either regular upgrade or complete wipe.

:-(

Using current AOSP and radio.
[G1 Android Development] matt tallant:
advanced launcher update

To update... i have gotten AL installed with all of the theme profile apps besides loccysBB. I dont know if it would have worked another way but what i did was go through theme profile one app at a time. I skipped loccy because mms was more important to me. Started with a fresh install as oleary had instructed. If i installed AL and anything else it wouldnt install but by itself it did. So i continued one by one. When i went back and tried to get loccy too (the same process as the others) it gave me the black screen with status bar. I dont get it, but frankly i usually use steel anyway so im not all that concerned. Just thought the powers that be be would like to know there is an issue in there somewhere. Im running amon 1.6.2, hard spl, aosp 2.6.2, enoch 2.6.1 w/ stericson on a dream. I just hope that i can get the uninstall for gmaps done without having to go through this headache again lol.

SySfS
[G1 Android Development] custommsp:
Hi,

Would like to report a problem;

- Using 2.6.2 AOSP with expansion pack

- Once on a phone call, the touch screen doesn't respond while trying to pull up the dial pad or input numbers once pulled up via menu botton.

- Youtube video playback is not stable, sometimes video shows, sometimes it doesn't and sometimes it freezes in the middle. Sound plays.

Thanks.
[G1 Android Development] AnderWeb:
More info would be great, please.

To use betterbrowser you mark it under GUSTO, then reboot to recovery and flash again your theme or theme template.

And for the ADWone theme, make sure you've completely booted the rom at least once before flashing the theme. And make sure too you are flashing the right version for your rom..

if it still doesn't work, post again so we can find the problem :-)
[G1 Android Development] olearyp:
It would help to know what you *did* do. You have to reboot to recovery (GUSTO will prompt on exit), then flash a theme (or the theme template if you want the stock appearance). If you did that, let us know which theme.

AnderWeb is apparently on it...
[G1 Android Development] bitter1:
GUSTO does not prompt for anything, much less reboot to recovery. It just does the "Working. . .starting process" then goes away annnnnd, done.

I'm not running any themes right now. I wiped everything and installed from scratch, just the base ROM and extension pack.

As for ADwone, yes it is the correct theme. Apparently a known issue.
[G1 Android Development] AnderWeb:
GUSTO doesn't have to make you read the posts... just read what i said previously about rebooting/reflashing.

For the ADWone, i'll make a deeper test tomorrow, but saying "it's a known problem" doesn't help too much...

As oleyarp said

"It would help to know what you *did* do" :)
[G1 Android Development] pezhore:
Blank Screen

Hello all,

I've tried wiping data/cache, doing a factory reset, and even repartitioning my SD card, but still I'm having troubles with installing the AOSP-1.6_r2 + ADP DRD36 v2.6.2 - Expansion-Pack.

ADB logcag shows activity, what can I look for that would be most helpful for troubleshooting my problem?

- pez

EDIT: It almost looks like it's looping while going through package manager steps. Maybe the first boot just takes its sweet time?
[G1 Android Development] MrMind10:
Hey Olearyp, Is it easy to update your radio? Do i even need it?
[G1 Android Development] AnderWeb:
First boot after install always stands a bit longer, take a beer :)

But, in case it isn't the problem, make sure you did these steps in this order:

Wipe data/cache, partition your card, etc

Flash the AOSP base

Flash the expansion pack

Reboot and wait.

done

After those steps, your rom should be working right. If not, try to catch a logcat and post here so experts can take a look :)
[G1 Android Development] olearyp:
It prompts when you exit (i.e., hit the "Back" button enough times). Here's the commit log where I added that feature. It was in v0.4; enomther included a modified v0.4-dev with 2.6.1, so I know it's in there.

If I prompted sooner, it would be very annoying, as you might wish to make several changes in a single boot cycle.
[G1 Android Development] pezhore:
About how long are we talking? 10 minutes? 20? I'm good with waiting, but at what point should I consider the flash to have gone wrong?
[G1 Android Development] bitter1:
Ahh, I just backed out once. It's a tad misleading to me on a UI level I have to back out all the way after the other popup window. I usually make changes and hit the reboot to recovery button instead of backing out all the way.

As for ADwone, saying:

Denotes a known issue, otherwise, what is "it"?
[G1 Android Development] olearyp:
I'll think on it. Maybe I can throw some sort of warning icon out? Perhaps a notification? Seems like overkill though (/me goes back to thinking).

Oh, I just meant he's answered and I don't have to say anything. I was originally going to have you PM him in case he wasn't watching the thread. So "it" would be "answering you". :) I don't have any out-of-band contact with AnderWeb.
[G1 Android Development] AnderWeb:
But i'm always open to out-of-band contact sir! :-P
[G1 Android Development] DKM119:
Question:Would it be ok to flash the new radio image 2.22.23.02 while using this Rom?
[G1 Android Development] RichieDaze:
It's not recommended by Enom...

But I have it on TheOfficial TMO rom as we speak...

And it's good money so far in NY...
[G1 Android Development] pezhore:
Well after letting it attempt to boot for about an hour - with no luck, I rebooted without the sd card - and it came up relatively quickly.

Does this sound familiar to anyone?

- pez
[G1 Android Development] jhaz420:
I was getting the same blank/black screen with Adwone's theme (with lockscreen). Download and flash the regular(without lockscreen), it worked for me.

By far the best android theme yet.
[G1 Android Development] olearyp:
Wipe the ext partition on the SD card. If no ext partition, then your SD card has probably bitten the dust (my condolences).
[G1 Android Development] AnderWeb:
I'll check that version again later. Were you using the theme profile on this or installed with default one?
[G1 Android Development] lordofsilence:
Before you throw the card away try this:

http://www.mediafire.com/file/mgwfmdztjn2/SDFormatter V2.0.exe
[G1 Android Development] JoelOFH:
I have a problem. I just flashed "HTC ADP 1.6 DRC83 - Rooted Base" and the screen wont auto-rotate.

I have checked the option in settings and have wiped the rotate settings with Amon's recovery image a few times. What could be the problem (FYI, I noticed someone else mentioned this 3-4 days ago).

I love this ROM, but I got to have my auto-rotate. :)

Please, help!

EDIT: Just read this

"Yea I likely will not create a "base" that makes MT3G work out-of-the-box ... I mean it boots with the current base ... it just can't auto-rotate, wifi is dead, etc."

Dang it. :( I loved this one, too.
[G1 Android Development] AnderWeb:
Why don't you install the AOSP instead?
[G1 Android Development] olearyp:
I don't believe that solves the problem--(accidentally) booting the base image on my phone still identified it as ADP1. The implication is that those drivers are missing.

If you're just looking for "plain stock" and "mT3G compatible", Amon-RA's ION or Dwang are probably your best bets.
[G1 Android Development] Jdom58:
Pat, I don't know call me thick but to install Loccy's from Gusto I'm not understading the part after I'm in recovery:

"then flash a theme (or the theme template if you want the stock appearance)"

I go into Gusto, select theme profile, check browser, allow su request, back, back select yes for reboot into recovery. The only choice left is to reboot phone, there is nothing to flash. Once rebooted I open browser and I don't see any changes, no MT, so where am I going wrong?

Thanks for the help
[G1 Android Development] jhaz420:
No I did not use theme profile. Thanks.
[G1 Android Development] pezhore:
I kind of doubt that... I can successfully flash cyanogen's rom and a few others with the same card. Are there older versions of the expansion packs? Maybe an older one would get farther.
[G1 Android Development] AnderWeb:
I realized the aosp+lockscreen theme wasn't working at all... i think is a compression fault, so i removed til i solve it... use the one without lockscreen instead for now.

Maybe if you people post the theme related problems inside theme's thread, this one would stay less cluttered... ;-)
[G1 Android Development] olearyp:
You'll have to download a theme or the theme template from Post 1 and put it on your SD card, then when you get to recovery, flash it just as you would a ROM, except you don't want to flash the ROM, just the theme file.

I think you *may* be able to reflash the expansion pack as well, if you don't want a separate download, but I haven't tested that and it's not the official line from enomther.

Doubt that it's dead or doubt that you need to wipe your ext partition? I'm with you on the first but the second is wrong. If you have an ext partition on your SD card, and you get a black screen on boot, you must wipe the partition. Differences in Dalvik between Cyanogen and AOSP and in A2SD between different ROMs cause no end of conflicts. Until you do this there is no other help we can give. Since you didn't mention whether you're partitioned or not, I'm assuming you are until you confirm or correct me.
[G1 Android Development] Jdom58:
Thanks for clearing that up, got it to work!

BTW, since all I had was the exp pack on my sd card I tried it that way and it worked like a charm :)
[G1 Android Development] bitter1:
I'll wait on the ANDwone theme, I'd like to try it. I saw it was pulled for now.

As for the GUSTO, the idea is good, just might need a different way to make it a tad clearer. Maybe when backing out of the secondary screen it displays the message to reboot into recovery and flash a(ny) theme again instead of backing all the way out.

The little popup mislead me to think it had done what it needed to do with a reboot.

Since this thread is now Ginormous, it makes a bit more sense that releasing a tool might need to be packaged in a zip with a notepad with instructions, changelog, etc. That way just by downloading the package you get all the information you need instead of hunting for it. (Maybe a .rar so people won't automatically try and flash it, with the note inside and the actual .zip)
[G1 Android Development] olearyp:
That's fair. I'm reworking the whole system right now to be more asynchronous (using a Service to handle requests for su operations) and to use Notifications to indicate certain stateful things such as a reboot is required. Check the suserver_refactor branch (UPDATE: branch merged and deleted) for progress on that.

Fundamental Rule: People Don't Read Documentation. Otherwise everyone would have read how to use the theme profiles to configure their software while they were downloading, since it's described in the opening posts.
[G1 Android Development] pezhore:
Sorry, I wasn't specific enough. I doubt that my card is dead. I'll try again with repartitioning, but am I correct in assuming that using something like switchrom.sh won't allow me to bounce between CM and TheOfficial Donut roms?

Thanks for your patience...
[G1 Android Development] arefin:
Elegance theme for this ROM!

Can we expect Elegance Theme for this great ROM?

I am sure this will look excellent with Elegance.
[G1 Android Development] sirocyl:
I switched to this from Super D, and remembered that stock TmoG1 Donut didn't support ext4, which I used on every ROM previous.

So I got the black screen of death.

Users: I fixed it by reformatting to Ext2.

Super-users: I think it's a kernel issue. Try a compatible kernel with ext4 compiled in.

Developers: if the above kernel works, you should pull ext4 support into your kernel build if you wish, or point out that the ROM is incompatible with ext4. (I don't have an adb lolcat of the issue, sorry)

Nota Bene: I have not tried ext3 yet.

The command I used to fix it, I believe was:

mke2fs -L Android-System -T ext2 /dev/block/mmcblk0p2

This wipes your ext partition clean, so back up apps, files etc. :)
[G1 Android Development] pezhore:
This could be my problem... I was formatting ext4. TylTru, did you ever try ext3... or does anyone else know if by default Donut supports ext3?
[G1 Android Development] olearyp:
Ext4 is supposed to be supported here, but for whatever reason most people can't get it to work. I didn't think of that (but I can't guess your partition table :)). Ext3 works fine.
[G1 Android Development] AnderWeb:
Only the version with lockscreen was removed, the one without it is working.
[G1 Android Development] enomther:
Ya ... very nice theme there ... I'll see what I can swing.

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

Kudos on another fantastic job. I found Rogers was f'n with me on the Fido network and still removed my data after I put your HTC ADP EBI1 ROM on my Dream. I used my G1 for a day and though, what the heck, and put the SIM back in my Dream. I've had data since!

Thank you again, I look forward to your continued excellence in ROMs!

:cool: Rebellion :cool:
[G1 Android Development] olearyp:
For the impatient, GUSTO v0.5 has been released!

As always http://gusto-latest.greentaperacing.us/ is a direct link to the latest release of GUSTO which will replace the version that shipped with TheOfficial 2.6.2.

No more progress dialogs. Settings are updated fully in the background.

Notifications now warn you when reboots are needed. Select a reboot notification to carry out the reboot requested.

A warning now appears before creating an ep_log to explain what the option does and to give you the option to not do it.

The alert dialogs have titles, making them more attractive.

The first new feature represents the bulk of the new work, with big under-the-hood changes to how expansion pack settings are handled. This speeds up interaction significantly.

Barring major bugs, this is slated for inclusion in Expansion Pack 2.6.3.

----- BEGIN TECHNICAL JARGON -----​

Android coders might be interested in the implementation of SuServer, which now extends IntentService instead of AsyncTask. This is much more like what I originally intended for SuServer, and I'm quite happy with the way it's turned out (which I do understand is a death sentence for code.) I'm also playing some tricks with SharedPreferences to carry shared state between instances of SuServer, and using a BroadcastReceiver as part of the process of resetting that state.

----- END TECHNICAL JARGON -----​
[G1 Android Development] majoraccent:
Since flashing 2.6.1 and then 2.6.2, I've been having severe battery life issues, where when left alone the phone will drain completely within 7 or 8 hours. I've done much testing, and this is definitely not a battery meter calibration issue. I'm running Tmo, with RAM Hack. I've tried wiping and reflashing, picking out just about all third party apps, etc with no luck. I tried completely disabling location services via wifi/gps/cell, with no luck. Bluetooth/wifi are off, I tried both 2g and 3g only modes. The only hint I have is that under the battery usage screen, "Android OS" takes up anywhere from 60-80% so something is causing it to activate and not let the phone idle. Cyanogenized frequency scaling is on.

Running top -t shows "er.ServerThread" from process system_server usually leading the list, but the "top" process takes up the most CPU when I'm running it, so it appears to use 0% cpu. Any ideas?
[G1 Android Development] olearyp:
Have you tried a different ROM? I've had no problems with this on the current AOSP; you could also try one of the completely different ROMs (Dwang is a solid, simple one.) It would help to know if we can tie it to the specific ROM.

Also, try no or a fresh SD card. I had problems with mmcqd (the daemon that queues SD card transactions) frequently occupying the CPU, which had a pretty severe effect on battery life. A new SD card seems to have mitigated the problem. I believe that tasks like mmcqd qualify as "Android OS" in the battery usage screen.
[G1 Android Development] arefin:
Hi there, are u going to implement few stuffs for the CPU settings section in ur upcoming/future versions of GUSTO? I am referring to the 'setcpu' app where you get an advanced controls button allowing you to change few values like 'sampling rate', 'up threshold' and the likes?

Would be really great for those who really change them :-)

I tried to install setcpu and implement values over your GUSTO settings which simply doesnt work and are ignored/overruled by GUSTO settings at startup.

either you implement those settings or tell me some way to use setCPU complementarily to GUSTO setups.

Thanks, you guys rockzzzzZ still my best Donut ROM :D
[G1 Android Development] olearyp:
The CPU settings are handled in the init scripts, where my only options are "cyanogenized" and "normal". If you wish to override those modes, you'll have to enable the "User init script" option and implement an appropriate user.conf (there's more info in Post 1--enomther, I have the option labeled in GUSTO with "userinit.sh" which I think I got from expsetup; which one is right?) I don't have any hooks from enomther for changing the details and making them stick so I can only do the same thing as SetCPU--which as you've observed, won't work.
[G1 Android Development] arefin:
THANX MAN

thanks indeed....will b wating
[G1 Android Development] cgrunner:
I've noticed the same problem with TMO 2.6.2 since the upgrade from the previous version. I don't have this issue with ASOP or other ROMs.
[G1 Android Development] majoraccent:
I tried unmounting and leaving out the sd card, same issue. I wiped and flashed Dwang's latest ROM and within 30 minutes of unplugging it, I could again see the battery draining, with "Android OS" as the culprit again. This sounds like a hardware issue now. Since we're discussing this anyway, is there any way to apply the stock T-Mobile firmware (without root) and retain the engineering SPL and RAv recovery? In the meantime, I will try the AOSP version from enomther.
[G1 Android Development] olearyp:
You can keep the SPL, but IIRC recovery will be reflashed when you boot the stock firmware if it detects that it's different than stock.

The biggest thing you lose (in my opinion) with AOSP over TMO is you lose the option to bill your TMO account for paid Market apps. As badly as I want to be able to do that, I switched to AOSP when I upgraded to Donut and haven't looked back.
[G1 Android Development] qwerty3656:
did some more searching and answered my own question
[G1 Android Development] jerry214:
Ace42's CommunityTheme - Expresso V0.1 - sorry How to download I really like this ROM and Theme thank you !!!
[G1 Android Development] enomther:
http://www.4shared.com/file/235823091/44755ee/Espresso-Enom-Latest-AOSP.html

here ya go.

~enom~
[G1 Android Development] olearyp:
Looks like Ace42 hasn't updated it yet. That thread will be best for further discussion about his theme (as Ace42 will be paying more attention there, I'd bet.)

EDIT: Well there's the S33KR37 link enomther gave above you could use. :)
[G1 Android Development] jerry214:
I do not know what went wrong and still can not open a Web page might be because I am in China
[G1 Android Development] jerry214:
I agree with you OLEARYP I hope that is true

so looking forward to