yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] marty22877:
i get bored easily, so i just switched over to the AOSP build, i decided to give it a whirl. I did a complete wipe, and flashed everything and it's workign like a charm
[G1 Android Development] Jdom58:
Marty I've been thinking of trying it also and I see you were on the TMO US 1.6 build before, how do you compare the two. Not sure if I'm just going to wait for the next update to try it.
[G1 Android Development] marty22877:
honestly i'm just getting down flashing everything now. i decided to partition my stock sd card to see what it was like, but it was really slow, so i had to reformat it and for safe measures i wiped and did a fresh install. i'll let you know how it goes.
[G1 Android Development] enomther:
Yea ... I'd hold off ... I'm redoing the AOSP ... upgrading to 1.6_r1.4-DRD20 sooo that's gonna post soon. Would at least wait for that.

~enom~
[G1 Android Development] bubonik:
Very cool, how soon is soon?
[G1 Android Development] Jdom58:
Enom, thanks for the heads up!! a little donation for your cause was just sent your way ;)
[G1 Android Development] Vlad83:
Enom, what changes are in DRD20?
[G1 Android Development] bitter1:
Oddly enough the install works now but I changed my partition sizes.

Funny how that is.
[G1 Android Development] marty22877:
enom,

i only run like 30 apps, do you think it's even worth it to get a new sd card and run apps2sd?
[G1 Android Development] mdavidf:
Thanks for the help Enom...I finally figured it out. The only thing I tried differently was to switch my Ext 4 to Ext 3...then everything flashed without a hitch...no kidding.
[G1 Android Development] Vlad83:
I am not speaking for Enom but I wouldn't use a2sd if I didn't have to. It'll just slow you down, even with a Class 6. If you want to use swap I think you can make 2 fat32 parts and 3rd linux swap (I havent tested but don't see why it wouldn't work) as swap is usually /blk0p3 unless Enom allows you to change it in the user.conf/sh. Then you can just make a second swap part and change it to /blk0p2 in the user.conf/sh
[G1 Android Development] enomther:
With only 30 apps and the 1.33.2005 SPL, it would probably be no problem to run w/out apps2sd.

Partition layout on the sdcard is auto-matic with expsetup/expinit ... so you can use linux-swap on any partition. Only requirement really is that FAT32 is always the 1st partition (this is an android thing).

Also, if you use a userinit/user.conf, you have to manually set it all up properly with the proper device pointers, etc.

~enom~
[G1 Android Development] enomther:
Truthfully ... minor revisions ... that will likely not be evident at all to the end user ... but for the sake of keeping pace. :)

But I am personally adding a few things that have been requested by others.

~enom~
[G1 Android Development] enomther:
Within a couple days tops, maybe sooner.

~enom~
[G1 Android Development] cloverdale:
Okay, I am now up and running again. I did a full wipe of everything, reflashed the base and the expansion. I did the 10MB hack, the better browser, and the mms app. I chose not to theme this time, or use the cytown phone app (never cared for it anyway), and no more lag when using the phone. Though I can not be sure as to what was the cause, I am very suspicious of the theme, as it did not happen prior to flashing it.
[G1 Android Development] xarope:
I briefly checked out CM 4.2.1, before flashing back to Enom's AOSP 1.6 r1.2 w/2.1.1, so I hope this is constructive feedback:

- CM 4.2.1 was super fast, and apps like handcent, k-9 mail etc were faster than on TheOfficial

- I didn't have the problems with having to press the menu or other buttons to wake up my G1, that I have with TheOfficial.

- However, stability was an issue; after a day, handcent couldn't send SMSs, and often calwidget would display "loading" on the home page for extended periods of time. Hence the switch back to TheOfficial (and to 2.1.1, I was previously on exp 2.0.2).

Not sure what contributed to the speed of CM 4.2.1, but I decided to change things around in TheOfficial to try to replicate, e.g. compcache off, swap on. But obviously I can't change the scheduler from BFS to CFS, since I'd need a new kernel (at least, easily; anybody know if linux schedulers are changeable via kernel modules now?)

Also, in spare parts, there was that option to lock home in memory; anybody know how this is accomplished? I'd like to lock e.g. home and superdial in memory, since those are the most often used.
[G1 Android Development] chowdarygm:
will that be a Non-Wipe update:) or Fresh install :( :confused:
[G1 Android Development] nmw407:
I've been running base + expansion 2.0.3 + official HERO theme 2.0 for the last few days. Then today, I flashed expansion 2.1.1 + official Hero theme 2.1 and although everything looks good and runs fine, the notification bar turned back to white (looks like the generic notification bar). On Hero 2.0 this used to be black with the letter H instead of 3G on the connection icon.

Now this maybe my phone but I'd like to go back to Hero 2.0 for now. Can someone post the zip file for this again since it's now gone from page 1? Thanks.
[G1 Android Development] Jrbourque:
So which one are people liking better on this?
[G1 Android Development] koolmick:
I just wanted to say what you guys do with these Roms are amazing and an incredible service to the G1/android phones. I used this Rom, in particular, before I got a new Cliq this week and I had to unroot my G1 and ran stock for a few days and I don't know how people survive with non rooted G1s. ...great work and keep it up...
[G1 Android Development] oMszKikiIzWavyo:
Yes My Phone Was Acting Crazy, When People Call Me, The Call Will Not Show Up Until Three Seconds Later And While That Person Is Calling Me, I Would Get Phone Force Closures.

I Reinstalled, And The Rom Is Working Great Now But I Still Have This Problem. Enom Do You Think You Can Fix This In Your Next Update?
[G1 Android Development] enomther:
cloverdale,

I've been running un-themed w/Zero issues (at least to the extent you were stating) ... could you tell me which theme so that I may scrutinize my work please?

~enom~
[G1 Android Development] enomther:
Should be non-wipe update, only difference will be a base & expansion pack update. But no wiping should be necessary.

~enom~
[G1 Android Development] enomther:
1) This ROM does not use BFS (never has) ... so this has and will continue to be (unless we see a change in the android git main stream) CFS scheduler.

2) Some of the features you describe are specific features Cyanogen has poured into the his version of either kernel and/or the his android git repository. These are his personal hardwork and contributions. When I can I do evaluate what he's done, his work is always top-notch! ;) These features include the keeping a memory resident launcher in spareparts and some custom kernel tweaks. Most of the speed can be accounted for by the elimination of compcache and swap altogether PLUS his reversion to a CFS scheduler.

3) I take it as constructive criticism, of course, and am fully aware of where the ROM's stand. Rest assured, I'm constantly evaluating as many facets of speed that I can. We will see improvements hopefully soon.

~enom~
[G1 Android Development] enomther:
Have you tried re-applying the theme ? ... if you accidently applied the theme and then the expansion pack ... you would get the result you currently have.

I would encourage you to try and flash the theme one more time.

~enom~
[G1 Android Development] enomther:
I haven't seen anything that harsh ... are you themed and/or running cytown's phone MOD ?

~enom~
[G1 Android Development] Vlad83:
Correct me if I am wrong but I don't believe this ROM uses BFS. I think we use Noop on this one. I have hero theme and seemed to increase snappiness with Linux swap...
[G1 Android Development] JonInAtl:
Your ROMs provide something lacking in may others, stability, and that's worth more to me than perceived speed increases (real or imagined).
[G1 Android Development] olearyp:
Enom half-addressed this on the previous page, but to clarify, noop is an I/O scheduler, not a task scheduler. The I/O scheduler used by enom's kernel is, by default, "anticipatory", though "noop" is also built and available in the kernel (a benchmark found elsewhere on this forum shows that there is no practical difference in the two with either the SD card or NAND flash on our hardware). The task scheduler is "CFS", the default Completely Fair Scheduler used in mainline Linux.
[G1 Android Development] nmw407:
I reapplied the theme and the same thing is happening. I'm still getting the white notification bar.

It's the weirdest thing. Everything looks like Hero, except for the notification bar.

I even reflashed the base, expansion pack, and then the 2.1 theme and nada... still the same result. It's not a deal breaker, but just doesn't look pretty, ya know.
[G1 Android Development] Vlad83:
Cool thanks, must have missed it. Good to know, I was pretty sure Enom wasn't using BFS though.

I am going to run Linux Swap for a few days, see if I get any slow downs down the road, that was my problem with it before. Otherwise, I like it better so far.
[G1 Android Development] L0rdDash:
latest build of the Tmo rom is running great so far for me. seems alot faster but maybe thats just my imagination but iv had no FC at all sense flashingthe other day and the call lag is alot less now. thanx for the great work and Enom i droped you a PM with a question i didnt think fit in the thread ;D
[G1 Android Development] cloverdale:
I still have zero issues un-themed :), and in all reality, un-themed looks pretty good.

I was running the Minus theme.
[G1 Android Development] cloverdale:
I had the same thing happen with 2.0.2. I was forced to wipe, the reflash the base and expansion.
[G1 Android Development] cloverdale:
I completely agree.
[G1 Android Development] cloverdale:
This was also happening to me with each call.
[G1 Android Development] nmw407:
Found my copy of Hero 2.0 and flashed the zip, and voila... black notification bar.

Then tested again... wiped, flashed base, flashed expansion 2.1.1, flashed Hero 2.1 - grrr.... white notification bar. So, next step, I wiped again, flashed base, expansion 2.1.1, and Hero 2.0. Lookee there... black notification bar.

I truly don't get it. Since 2.0 seems to be working ok, I'll just keep it on for now to test. I guess 2.1 just doesn't like me.
[G1 Android Development] enomther:
I musta messed up the theme then ... I will check it out.

~enom~
[G1 Android Development] enomther:
I completely believe you! :) ... I'm able to replicate various things surrounding the call issue ... too agreesive compcache is mostly the cuplrit at this point. I will be posting a revision update ... once I find the right combo ;)

~enom~
[G1 Android Development] xarope:
Enom, as always, thanks for the clarifications.

FYI and for others, my handcent problem still existed after re-flashing TheOfficial, but running fix_permissions (rebooting into recovery and using the console) fixed it (strangely; still don't understand the root cause as I had sent at least a dozen messages whilst on CM 4.2.1 before the problem turned up).
[G1 Android Development] nmw407:
thanks, enom! I really like this ROM. Once I got the whole expsetup figured out, I haven't had any problems with it and it's definitely fast for me.
[G1 Android Development] cloverdale:
Thank you. In my opinion this ROM is almost perfect, the people on the thread are friendly and helpful, and I plan on staying with your work.

I hope you do not mind, but on another forum, on which I am an admin, I have started a thread to promote, and offer support for you work (I can't imagine why, but many noobs are afraid to ask questions on XDA :) ). Let me know and I will take it down.
[G1 Android Development] DOHCtor:
Start lurking around more often and you will see why lol
[G1 Android Development] cloverdale:
As a long time cyanogen user (2.* to 4.1.11.1), I assure you I was only joking. One of the things that brought me over here is how helpful everyone is (I am 5 months away from a PhD in probability theory, but would often question if I was intelligent enough to ask questions on many threads here).
[G1 Android Development] agent321:
I asked earlier and got no response....

Any reason why multi touch would not be working in this rom?

I have the expansions loaded fine and have no other issues.

Thanks in advance for the help!
[G1 Android Development] olearyp:
Terminal:

$ su
# expsetup

<list of options>

Choose an operation: 14

<list of options>

Choose: 2

Follow remaining directions.
[G1 Android Development] maxkid86:
themes

Okay, so i've been switching back and forth between TMO and AOSP and I'm not sure which to keep. for some reason AOSP volume is super low, but I'm wondering if I jump to TMO and grab the chrome theme will there be any problems with it.... has any one tried that mix yet?
[G1 Android Development] zimphishmonger:
Apply meltus's latest audio hack for any audio level issues, the newest versions work quite well. I personally use v2r2
[G1 Android Development] agent321:
YOU ROCK!!!!!!!
[G1 Android Development] rockodeville13:
Theres no need to be afraid! Questions are Questions and will eventually be answered, or might have already on previous posts, but I also dont agree with flaming the noobs...everyone was there at some point. So far as much as i look around this forum, there is no Dev that helps out the pub as much as Enom.

Thats the way it should be, thats why there arent a lot of noobish questions posted up as he explaings everything in his OP.

Thanks Enom!
[G1 Android Development] DarkMerc:
I love this rom. I agree though, on my HTC G1 from T-mobile, ADP did seem to run alot slower for some reason then the TMO version. On my phone however, HQ/HD youtube video on my phone work great. I don't have any problems with that. I'm running a 512 mb ext2 apps2sd (I wish I had a class 6 card instead of 4 though). I haven't had any problems with most apps, just some high intensity ones seem cranky and I'm pretty sure that's just because they haven't been ported to donut yet (Totemo won't work at all - keeps slowing down and freezing). I also have no problems with the Market, except when I'm connected via WIFI (it gets spotty at best), I think that's a problem with the new market and not the phone though. Also whoever said that overclocking widget is better than the expsetup clocking options is crazy. I thought that too, at first, but after setting the options in the expsetup to enable Cyanogenized CPU freq sampling and min 245760 and max 528000 my phone is working amazingly quick most of the time. I still can't get debian with X11 working great though - but getting there. I have a 64mb linux swap space on my sd card but I'm thinking about upgrading that to 128mb or 256mb and getting a class 6 8gb microsd card and running debian off an ext4 partition on the sd card rather than an img of a fat32 partition and I think xwindows through debian will work excellent. Well that's my two cents ;).

Other quick thoughts:

Did anyone else notice that vi is in the terminal? Great for text editing because nano sucks.

My google maps actually works pretty good. The only thing I've seen with GPS problems is where I'm at. Sometimes it takes longer to get a perfect center of me on the map than usual based on my physical location.
[G1 Android Development] Vlad83:
Yeah, don't mean to offend anyone but this is the most unfriendly forum I've been a part of. Everyone hates when people don't search/read the rules/etc (I've been guilty of a few times my self) but this aura of fear that encompasses XDA is pretty noticeable...

Sorry, back to topic. Has anyone experimented with the user.conf yet?

p.s. Enom, can you list your default settings that are adjustable, most curious of VM... or do you have it disabled by default? I played around a lot with user.conf in CM4.04 and 4.11.xx had good results.
[G1 Android Development] DarkMerc:
Hey vlad did you check out the link on the first page? user.conf.example. It pretty much looks like most of the settings that are in the expsetup script. You can add your own custom commands to the end (adds it to the boot up of the phone) which is pretty nifty though. So if you had a debian build you could start your bootup script automatically on boot of the phone for example. That's what I added to mine.
[G1 Android Development] Vlad83:
Yeah but the example script is a generic script that was initially written for CM builds. I want to know which settings this particular ROM used by default with no script. I checked expinit and couldn't find the VM settings, userinit I believe is only active if .../sd/user.conf is present.
[G1 Android Development] cloverdale:
I quite like nano, what do you feel are the advantages to using vi?
[G1 Android Development] oMszKikiIzWavyo:
Yes Im Themed, Using Official Hero Theme 2.1 And No Im Not Using Cytown's Phone Mod

By The Way When I Try Cytown's Phone Mod, My Service Never Comes Back
[G1 Android Development] Tito2007:
Hey, i was trying to setup my email using the email app on the phone but when i enter my infromation i get a dialog box saying that "

username or password incorrect". Does anybody have any info on why or how i can fix this. Also before i had an onscreen keyboard i think it was something like "input touch" but now i only have the defalut one. Thanks
[G1 Android Development] fisio:
oh no, google maps 3.2 removed Latitude?
[G1 Android Development] Vlad83:
It's in Layers. But after I tried disabling it, I got a bunch of FCs...
[G1 Android Development] chowdarygm:
Did you by chance trying to login to Yahoo account?? , i guess it wont work with yahoo for some reason unknown to me....

to get the touch input, just longpress the number symbol key in your defualt screen which will show you the available keyboards

and also DID any one notice, the gmail app is FC when i try to open a PDF document attachment......??? any idea???
[G1 Android Development] lyric911:
I have a different adapter (http://www.amazon.com/gp/product/B0011WDLES/ref=ox_ya_oh_product) but am experiencing the same problem. If it helps in any way, I didn't have this problem on CM, so perhaps he can point you in the right direction?
[G1 Android Development] LucidREM:
MOD Version

so i was just "tinkering" around and noticed the "getprop ro.modversion" no longer pulls up information about the current build .. this was the way JF had set for people to know what ROM they were using .. i have a script that makes a call to that

# lucid -v

but is there a way to add this back or look somewhere else for the version?
[G1 Android Development] cyberrobin:
Hey enomther,

Are you going to work on the 2.0 Eclair for the G1 (Dream)? :D

Can't wait to install it.. ;)
[G1 Android Development] Jrbourque:
Im not sure if anyone else is having this problem, but I cant set my alarm with the aosp build. It goes to change it and then when i click okay it wont change it nor will it set my alarm even if i dont try to change the time. I did fresh install. cleared sd card.
[G1 Android Development] enomther:
This is 100% fine with me ... so long as it's understood I lack the time to actively participate anywhere in regards to this work other than my settled home here on XDA. So feel free to do so!

~enom~
[G1 Android Development] enomther:
Ooops. I didn't even consider your script -v when I removed this ... as I'm basically moved this information to the ro.displayid property.

I will consider re-adding it in the next revision ... I'll let you know.

Thanks for pointing it out.

~enom~
[G1 Android Development] enomther:
Of course I do plan on working with and producing an Eclair ROM ... but not until it officially hits the AOSP.

Staying true to my form, I will likely not produce anything in relation to eclair till it's reached "release" status in the AOSP.

But if you mean to ask will I rip it from the SDK emulator and support/port it that way ... then no I won't. I have no interest in spinning my wheels to produce a ROM that Google themselves has not released publicly yet.

Also, we will be waiting for a little while on this ... as according to what I know ... we have to wait for the Verizon devices to hit the shelves before we'll see any of the eclair code hit the AOSP.

~enom~
[G1 Android Development] enomther:
Just FYI.

I've determined that the PID prioritization was causing some issues with the GPS location services when a weaker signal was being received.

I'm releasing a new revision to v2.1.x (today likely) that will bring the GPS back to where it outta be in terms of it's ability to function in low-signal-strength situations.

~enom~
[G1 Android Development] Jrbourque:
Hey enomther, Im running your aosp build and i cant set or change my alarms. wiped, cleared sdcard before flash. would you have any ideas?
[G1 Android Development] bittermormon:
New modified Dialer

are you planning on including the newer v11 of the Modified Phone app in the update?

v11 @ 1028:
add vibrate on call waiting function and a switch for that.
add larger avatar
fix bug for show avatar when outgoing call not answered
improve performance for vibrate notification
[G1 Android Development] mdavidf:
I was having a similar issue...I'd completely wipe everything and then flash all of the AOSP files (root, extension, and hero theme). I tried it several times thinking I missed a step, but every time I'd either get what you're describing OR the Hero Theme would kill my Advanced Launcher and not apply any of the Hero theme.

The only thing I did to fix it was, believe it or not, change my Ext 4 partition to an Ext 3...the next time I wiped and flashed, everything applied as it should, even the notification bar.

EDIT: I know it sounds ridiculous and I don't understand why it worked, but I swear it is the only thing I did differently.
[G1 Android Development] nmw407:
The thing is I'm using Ext3, so I don't think that's the issue. I don't use Advanced Launcher either. I think enom was going to look at the theme to see if it was the 2.1 theme that's causing the problem.
[G1 Android Development] mdavidf:
Yeah, I read that after I already posted.

When I was having this issue...the AOSP Root and Expansion flashed flawlessly each time. It was only after flashing the Hero Theme that I ran into problems.
[G1 Android Development] nblakqori:
hey enom, just wanted to say thanks for aosp, cuz this is the only donut i have tried that copilot live works.

regards,
[G1 Android Development] cloverdale:
Careful what you say, it is not unknown that the only copilot issues were a result of KFC's crack, and thus threads which discuss this are being locked by mods.
[G1 Android Development] cloverdale:
Enom,

Though a fresh wipe helped with lag, I began noticing quite a bit of lag when running more than one concurrent app in the foreground. Remembering your comment regarding compcache issues, I disabed compcache and enabled a linux swap with swappiness 60. All lag is gone, and this is easily as fast as cm4.2.2.
[G1 Android Development] enomther:
Yup,

Compcache is the culprit ... I have several variations of the next release in testing to combat the problem.

But if appears cc + backing store is simply not a good idea altogether (per my testing) ... so far the winning results are pure_cc w/ swappiness 30 or less (and really less just sux, so 30).... OR ... linux-swap swappiness 30-60.

Final tweaks are getting ironed out now ... this revision should see a return to the speeds 2.0.1 and prior had. :)

~enom~
[G1 Android Development] marty22877:
hopefully that log i sent you yesterday helped out.
[G1 Android Development] enomther:
Not sure about this man ... this has been thoroughly tested and is confirmed to work w/ no hassles.

Make the alarm settings fail, etc ... again .. then ..

Send me a log ... option #8 in expsetup ... enomther at gmail dot com

I'll have a look.

~enom~
[G1 Android Development] enomther:
Yes, I am evaluating it.

~enom~
[G1 Android Development] enomther:
It did ... the 10mb MOD will now only sport 32MB (no more 64MB ... it's simply too much) Compcache w/30 swappiness ;) ... so you're log and others definitely did help quite a bit.

~enom~