yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] memphisraynz:
shell find command

Hey guys i can no longer seem to use the Shell Find command the way it used to work.

Anyone through any suggestions.

Below is what i run, it used to work but now when i run it i get the following message

adb shell find /system /data -name \*google\*maps.apk\* -o -name Maps.apk -delete

find: unrecognized: -delete

BusyBox v1.15.3android (2010-01-29 01:54:08 EST) multi-call binary

Usage: find [PATH...] [EXPRESSION]

Search for files. The default PATH is the current directory,

default EXPRESSION is '-print'
[G1 Android Development] jonze5:
nexus

does anyon know how i can put the nexus one boot anim in this rom??
[G1 Android Development] Jonathan062:
Black Screen Of Death

Running OpenEclair v1.0.1 STABLE and i unmounted the sd and the screen went black had to pull battery how do i report bugs? This rom is awesome cant wait till the bugs are worked out.
[G1 Android Development] evolarius:
hear hear!!!

A weekly release would be optimal IMHO, it give plenty of time for bugs to be found, and repaired. Sooner releases would be necessary if the bugs were major...
[G1 Android Development] ctso:
Issue Tracker is up at Google Code.

Please report all bugs here.

http://code.google.com/p/openeclair/issues/list
[G1 Android Development] :
Flashed from xROM straight to this without wipe, so far so good.

What's the recommended CompCache size, BTW?
[G1 Android Development] fiktion:
I wasn't saying to stop the updater support, by any means. It's just, every time I've used the updater, personally, I've had the md5 error. I've never got it to work, and prefer to not use, or have it. Even the CyanogenMod ROMs don't include it by default.
[G1 Android Development] Ace42:
You just tick the box in spare parts and compache isnt on the sd its the phone's ram.So you cant toggle the size of compache uses. Ctso sets a size for it to use.
[G1 Android Development] ultra spikey:
How does this not work on a Eng SPL or Hard SPL? This ROM file size is 51MB, the Eclair ROM I'm running now is 59MB. I was able to flash this bigger ROM onto my G1 with the EngSPL. Am I understanding this right? That since OpenEclair is smaller than my current ROM, I should be able to flash it?
[G1 Android Development] bkmo:
DDMS for screenshot of problem

I have some text issues in the app drawer with OpenEclair. I get some square boxes where there should be text under some of the icons. I was trying to do a DDMS screenshot, but DDMS crashes and closes down when I try it. Do I need a new version of DDMS with this rom to match the SDK?
[G1 Android Development] Ace42:
You should be using the 2.1 SDK not a older version for DDMS to work on this. I havent tried DDMS on this so i dont know if it works with the 2.1 SDK.
[G1 Android Development] bkmo:
I have the 1.6 SDK version now. I will download 2.1 to see if that fixes DDMS issues. DDMS works, but crashes on the sreen capture.
[G1 Android Development] Tomb77:
force close

I'm getting a force close when going into security & location in settings. can someone please confirm this? Thank you

edit: I had this issue with the darkstar theme. also could not select widgets.
[G1 Android Development] d750:
Lexx theme for OpenEclair download
[G1 Android Development] Stopsign002:
Am I lucky?

I've been following this ROM since it came about and have loved having it on my G1. I saw some talk of the Nexus Launcher and I was wondering if that is the new Home Screen that the Nexus has, with the dots and new app menu. I am really hoping so as I LOVE that menu compared to the normal one. So am I lucky enough to be getting what I want?

P.S. @ctso Im following your blog in hopes of learning how to code some of this stuff. Programming as always managed to escape my understand (I'm a computer system technology major)
[G1 Android Development] zeppelin481:
For those asking about compcache, you control it in SpareParts as Ace said. If you are asking which size is recommended, there isn't one. I know ctso prefers 16M and I personally use 24M. It doesn't hurt to try each size and settle on the one you feel works best for you.
[G1 Android Development] sfcdale:
Open Eclair I love it.

I updated from 1.4 using cm updater worked perfect :)

Great work.

I have a ? sense I am not a programmer but do like to contribute, from time to time I like to send a few beers (Pay-Pal) is there some way it could go to the open eclair project?

Dale
[G1 Android Development] TemporalShadows:
Has anyone else had a problem with embedded maps in apps? When I try to use such an app (Weatherbug, iMap Weather, Cellfinder, etc) it force closes. In the logcat for the Cellfinder force close it crashes because it can't find the superclass for "CellfinderMapActivity". I'd paste the entire logcat but I can't get to a PC for a while.

Also, on Eclair ROMs no user-installed apps will run on the first attempt. Someone mentioned that it's due to the ROM optimizing the APK and the ROM then thinking that the APK has changed and reinstalling it on the fly, IIRC. Any chance of finding a workaround?

Great idea making this a team effort. This is currently the fastest Eclair ROM out there and I love it!
[G1 Android Development] ultra spikey:
anyone have any input? I would like to try this rom but dont want to flash the DangerSPL.
[G1 Android Development] 2dorr:
I had KiNgxKxOveR for 2 hours and the OpenEclair is much more faster, I must admit. It's still fast even with Live Wallpapers
[G1 Android Development] zeppelin481:
Danger SPL

Guys, the requirement for Danger SPL was from when Chris first released intension. For those who are opposed to flashing a modified SPL, OpenEclair v1.1 will not require Danger SPL. A beta is in the works now, so 1.1 is just around the corner. Hope this clears thing up a little.

Ryan
[G1 Android Development] digitallysick:
I had the same issue, the darkstar theme currently screws this rom all up, don't use it! Until its fixed
[G1 Android Development] zeppelin481:
It is based off of Intension which used to require Danger SPL. Wait for v1.1 which will not require Danger. Honestly, you should be able to flash v1 without a modified SPL as well, but the requirement will be removed after 1.1

Ryan
[G1 Android Development] techbeck:
http://code.google.com/p/openeclair/issues/list
[G1 Android Development] G Zero:
Ban

(10 char min)
[G1 Android Development] nduanetesh:
Exactly.

It blows my mind that people think this is an "issue" worth complaining about. There are definitely bigger problems to be tackled here.
[G1 Android Development] Jonathan062:
AppstoSD

can I manually configure apps to sd on mt3g ? or is it not supported
[G1 Android Development] techbeck:
it blows my mind how people make posts that in no way contribute to anything....

I know its not a big issue and I even stated that at one point. Wast just reporting an issue and it has to do with the duplicate keyboards, not the transparent background. One keyboard is fine, the other isnt. Also, there are minor issues with both KBs...something that they are working on.
[G1 Android Development] nduanetesh:
There's a problem with your math...

2.3MB per sec (could also be written as 2.3 MB/sec) for 2.3 seconds is still 2.3MB/sec. Not 1Mb/sec. It doesn't matter how long 2.3 MB/sec lasts, it's always that amount of info "per second". What you have written is akin to saying, "we went 60 Miles per hour for 60 hours, so that's 1 mile per hour!" No, it's not. It's still 60 miles per hour.

2.3MB per sec for four hours is still 2.3MB/sec.

Perhaps you meant--

2.3MB for 2.3 sec is 1 MB/sec? That would make more sense.

BTW, MB and Mb are not the same thing. MB = megabyte. Mb = megabit. 1 byte = 8 bits. So 2.3MB for 2.3 sec = 8 Mb/sec.
[G1 Android Development] nduanetesh:
Yeah, isn't that annoying? ;-)
[G1 Android Development] dmolition:
I have one question about swap.

So do i just go to spareparts and then mark swap and compache?

Do I need to do something else, for example repartion my SD card?

Also what do you recommend for the compache size?
[G1 Android Development] G Zero:
lol, true story. Id upload pictures of the keyboard with the Nexus wallpaper and Starfield wallpaper if I weren't so indifferent. I've seen techbeck contribute here so its all good in my book.

lol you're dead right bro. I reread that this morning and was like "....what??" That math was terrible, and I won't be doing intense calculations after 12 anymore lol. The principal was right though, OE is archetecturally a beast compared to some of the romms I've tested it against. Some point tomorrow ill ldyno' 1.0.1. Def wouldn't want to do it now at 13:71 in the morning.
[G1 Android Development] thenameismax:
http://xdaforums.com/showthread.php?t=625367

there you go man...next time try searching it...
[G1 Android Development] zimphishmonger:
As impressive as all the benchmark testing is using MFLOPS and system data throughput, all it is proving is that a lot of data is going along the system bus and the cpu is working much harder.

Like benchmarking a PC, you need to do a reproducible and comparible test, similar to Orthos or Prime95 in Windows, which calculate prime numbers yet already knows the answers, and compares the calculations w/ the known results and reports the time needed to process such calculations.

Hence why I still stand by BenchmarkPi as a the better utility to test out build speeds.....:)
[G1 Android Development] naguz:
Well, measuring Pi calculations etc. doesn't necessarily say anything about how usable the ROM is.

My SUper Pi score is better ein 1.1.1 than in 1.0, but 1.0 was noticably faster in use. 1.1.1 has in comloarison to 1.0 a noticable lag. The easiest way to see it is navigating in the settings menu or in folders in Astrid.
[G1 Android Development] sisterchick:
Good question. In the last instance, I didn't see caller ID and just assumed it was the lock screen. I slid the button to unlock, saw the caller ID and then was trying to slide to answer. By then, the call had gone to voicemail and my phone had locked up. Required reboot. It could have been a delay in showing caller ID. I'll verify if it happens again and perhaps wait and see what happens without my intervention. Thanks.
[G1 Android Development] :
Tried disabling CompCache...? It helped in my case.
[G1 Android Development] johaganism:
lock screen

i posted this following in another eclair thread. i havent tried this particular eclair yet but i thought the idea should be noted anyway.

the lock screen has some pointlessness to it on the g1. the lock button is just for looks since i personally just push menu twice all the time to turn on my phone anyway. altho the quick mute button/slider is a great idea.

so my question is will there be changes to the lockscreen for the g1 version?

maybe switch the functionality of the unlock slider to something useful... or have settings that change the function of any of those lockscreen sliders to other things like wifi/gps/bluetooth/etc.

(i am assuming all eclair roms have the same lock screen)
[G1 Android Development] sisterchick:
I'll do that. Thanks for the suggestion.:)
[G1 Android Development] G Zero:
Linpack Benchmark states its applying a dense linear N by N equasion of Ax = b, in effect doing what is described in the latter half of the second paragraph. Its also doing these equasions all at once, which is more representative of a live use scenario. I know benchmark pi gives us a flat number to compare but that number exists in a vacuum, akin to saying an apple this red in this situation translates to an orange that big in that situation.

this was the same inefficiency I felt abt Benchmark Pi. I noticed this when benchmarking Super D and JIT OE (aka 1.1) back to back. Super D was putting up 14s while JOE was putting up 9s, yet Super D was materially faster. The numbers were misleading.

The MFLOP test calculates a repeatable group of equasions at one time as opposed to one calculation at one time, more resembling a real life circumstance where your device is racing to calculate multiple tasks at a single time and show you all of them as fast as possible.

For the record, Super D and Open Eclaire 1.0.1 benchmark identical numbers, 2.3MFLOPS/s for 2.4s rounding off.
[G1 Android Development] thenameismax:
you guys confused the hell outta me with all this floppy bench stuff ha
[G1 Android Development] billquinn1:
111,111,111 x 111,111,111 = 12,345,678,987,654,321

I hope this clears it up.
[G1 Android Development] Temporarily:
I hate to say this, but with all of the great developers working on this ROM, why is it still not as fast and as stable as Hero_Over's effort? Everything Hero_Over ever released was pretty much crap, IMO, except his Eclair ROM. He got off on a better foot with that thing than anyone else did. C'mon guys, I know you're capable of some awesome things!
[G1 Android Development] sweetpunkined:
do the video player work on this rom...its not working on kingklick 1.4
[G1 Android Development] Temporarily:
You should probably be banned for asking this.
[G1 Android Development] jklong03:
Just so you understand sweetpunkined, that banning suggestion is due to the fact that posting your question simply showed a lack of effort on your part to search, or even, god forbid, read the OP! :eek:
[G1 Android Development] sweetpunkined:
WOW!!!! you have the power to do im sorry for my damn question..but when i try to play a video it plays the sound but the video do not move with the sound so if u can help......help.......if not dont try ban me if u dont have the power
[G1 Android Development] G Zero:
@thenameismax: lol

I'm gonna look into that. I DLed Kings newest and took it for a spin and I gotta tell ya, its VERY difficult to tell the diff between it and OE 1.0.1 on the surface. Kings Eclair is SLIGHTLY slower displaying graphical stuff (screen swipes, up and down in app tray, etc). Fired up my benchmark tools and they confirmed that King draws images slower (15 vs 16 for OE) and accesses file systems slower (greater time to read and write, as well as delete).

....but what really surprised me..... KINGS NEWEST ECLAIR IS ON JIT COMPILER. The same system that had Eclair 1.1 running like a squirrel with a 5hr energy. Kinda surprised me that OE jitless is actually slightly faster than Jit on Kings. Kings jit #s breakdown like OE did on jit as well, 3.5MFLOP/s for 1.5s. I hope 1.1 wasn't the last instance of Jit well see in OE........
[G1 Android Development] DeSim:
Do some reading befor you even get the roms. That is apparent you dont read to much in to the forums to deep. READ!!READ! READ! READ! READ! When your done doing that. READ READ READ READ some more then ask the questions.
[G1 Android Development] schwiz:
GenieWidget will not install I tried installing it directly with ADB but I get the error message

Failure [INSTALL_PARSE_FAILED_UNEXPECTED_EXCEPTION]

I thought it may be a corrupt APK so I downloaded the APK from another source and still get the same error.

Also the smoke livewallpaper is broken, but other livewalllpapers from the market do work.
[G1 Android Development] G Zero:
So yeah ...this is a Hero Rom. Long story short, Hero 2.1 and Eclair 2.1 use totally different drivers to do the exact same things. Plus HTC gave the Qualcom drivers to developers. Google didn't. Biiiigg difference.
[G1 Android Development] doalittledanse:
He's talking about the person Hero_over, not the type of rom
[G1 Android Development] G Zero:
Genie widget comes included in 1.0.1 why are you trying to install it through ADB? *sigh*

I need a break.
[G1 Android Development] legend1222:
Email client bug?

I hesitate to add this to the bug tracker before making sure this isn't a known issue of some sort.

With my clients I maintain email addresses on their mail servers. What I've always done in the past is had the mail client hit my Exchange server for my personal stuff, and then check the clients servers via imap. All set to check every 10 minutes. This has worked on all other roms i've used, 1.5, 1.6, 2.0, whatever.

With this one, I just found out, it only actively checks my exchange server. The imap accounts are ignored until I switch into them. So I missed a days with of email from one of my clients because of this.

Anyone seen this or have a clue? This is OE1.0, On a Magic 32A. I know its not what this ROM is targeted for, but would think that for this situation the hardware wouldn't matter. I also realize that this isn't the most current stable rom, but based on the change log, I don't think upgrading would solve the issue.
[G1 Android Development] Temporarily:
So, yeah... what the hell are you even talking about? Did you even read my post before replying?
[G1 Android Development] schwiz:
It isn't installing correctly if you start with 1.1.1 I have reflashed and it is a no go....
[G1 Android Development] daveerickson:
This morning I switched from CM 4.2.14.1 with a full wipe and went to 1.1.1. I have the widget working just fine. I downloaded it from here:

http://xdaforums.com/showthread.php?t=600959

So, it wasn't included in 1.1.1, but no issues installing it here.
[G1 Android Development] schwiz:
It actually is included with 1.1.1 if you open the zip and look in the apps folder it is there but it will not properly install during the flash or when trying to manually install it with adb. I will try installing it from the source you linked.

Edit: installing from the source you linked worked fine. It appears that the apk included with 1.1.1 is corrupt.
[G1 Android Development] naguz:
Meh, I had two freezes today requiring a battery pull, right after each other. One was with spotifu playing, going to home screen and launching the sms app, the other was right after reobot on opening a message notification. Was changing rotation at the same time, so it COULD be related to Issue 108, but that seems different.

Min froze totally with the message app stuck on the screen.
[G1 Android Development] daveerickson:
Interesting, yeah I didn't see it so I just assumed it wasn't there. Glad the link worked for you.
[G1 Android Development] G Zero:
...are you kidding me?

A: How did I ever think you were talking about a ROM? :rolleyes:

B: I'm not gonna get into why you're 7 different types of retarded for comparing Hero 2.1 to Eclair 2.1, especially as you're an 8th type of retarded to not see that's exactly what you're doing.

C: You're comparing a dev who has aaaaaalllllll the drivers he needs provided for him, ...and admits to stealing from other devs, ......to devs that are basically using existing parts to build an OS from scratch?????

Riiiiiiggghhhhht...........
[G1 Android Development] jklong03:
Stop slapping each other!

Not necessarily taking sides here, but I totally understood Temporarily's OP on this subject because I follow most of the ROM devs threads and I was aware that Hero_over came out with an Eclair 2.0 ROM several weeks ago that was pretty decent for a first swing.

So, you are bashing him for comparing Hero to Eclair when in fact he wasn't! He was comparing the relative stability and functionality of Hero_over's Eclair ROM. You seem to be the one who got caught up with assuming because the dev's username is Hero_over, he had to be producing a Hero ROM exclusively.

IMHO, you kinda owe him an apology (and perhaps assign yourself a degree of retard'ness for assuming incorrectly in the first place?)

My only comment on this subject, but thought perhaps an impartial 3rd party could put and end to this, since we don't seem to have anything else to talk about until the next release of OpenEclair. :)
[G1 Android Development] JAguirre1231:
For those of you not following them on Twitter, you really should ;) There may be a nice surprise there for you
[G1 Android Development] Temporarily:
Dude, you're a clown. Hero_Over's ROM wasn't a Hero ROM, it was Eclair. Plain and simple. Don't be an idiot.
[G1 Android Development] JAguirre1231:
Let's stop this fighting. This is a ROM thread, if you want to fight like this, pm each other and then post it somewhere for easy reading later on ;)
[G1 Android Development] Morrolan:
I think you're not understanding the post. Hero_Over released an Eclair 2.1 ROM a few weeks ago. I am using it now. It has the Nexus style drawer (Not launcher2) and supports all Live Wallpapers. It's stable and fast. And there is no video, just like on all Eclair ROMs, so the drivers aren't present. I'm currently using it now. I really think the OpenEclair devs should take a look at it. One big thing that keeps me from moving to OpenEclair is the Superuser.apk. On the Hero_Over Eclair ROM, I can get access to root through Superuser. On OpenEclair, I cannot. Hero_Over stopped development on it after the first release and said he would be working with KingKlick. I hope that clears up the confusion.
[G1 Android Development] Major_Skidmark:
1.1.3 still has the bug where apps open then close and dissappear from the apps menu.
[G1 Android Development] Quiketaz:
Testing the last version 1.1.3 crossing my fingers :D. Here is the link
[G1 Android Development] crypysmoker:
Theres a reason they released that on twitter only.

But you guys will be happy with 1.1.3, Its running much faster then others.
[G1 Android Development] Temporarily:
Just to let you all know, 1.1.3 is still unacceptably slow. :(

I'm sure they'll get us there soon. Fingers crossed.
[G1 Android Development] G Zero:
that's not true. Looking to try an eclair rom I Googled "Hero_Over Eclair" and found nothing. I found his name and searched for all threads created by hero_over, and found two RCs of hero and an 'im not devving anymore thread'. Don't take my word for it, search for your self. I did my due dilligence.

Now you said, 'Hey dude, its an eclair rom, and you should check it out'. Cool bro, link me! But when he comes in and says 'AH I'M TALKING ABOUT A PERSON NOT A ROM BLAH BLAH BLAH' trying to be a smartass, I not gonna appoligize for that.

....moving on.
[G1 Android Development] memphisraynz:
I have had it a lot where they will open and close once, but try it again and they will often work.

I think its something to do with having to build the dalvik cache for that app again. I dont think its a bug.
[G1 Android Development] cityeyes:
That's not a bug, it's a feature.

No seriously, I think they run something called a "zipalign" on install. That's why every time you open a program for the first time after an update, it does that.

I could be totally wrong about this, but I'm pretty sure I saw it somewhere on the tracker. This should be able to be solved by wiping before upgrade (you're supposed to with these and as far as I know any Eclair build).
[G1 Android Development] Temporarily:
LOL! You were disrespectful, insulting, attacked me, and were COMPLETELY WRONG about what you were saying, and now you refuse to apologize! LOL!! You're classic man. You should probably be banned. Think and read and pause for a moment before you go off like you did. Clown.
[G1 Android Development] JAguirre1231:
Again, this is why there are pm's. I'm all for a little flaming, but not in threads where I try and keep maintenance.
[G1 Android Development] pudgedaddy:
Stop all the bickering!

This is not a pissing match guys! Please be respectful of each other while on this forum. This is your warning.
[G1 Android Development] doalittledanse:
I think he was talking about this rom:

http://xdaforums.com/showthread.php?t=622099

Its an eclair rom by king klick and hero_over
[G1 Android Development] memphisraynz:
+1

All this bickering needs to stop. Its not helping development or teaching us anything. No one is perfect so we have to stop acting so superior
[G1 Android Development] here.david:
V1.1.3 works !!!!

I did both a non-wipe and then a full wipe (see attached)...runs FAST and great...non-wipe has issues, wipe does not unless using backup vs.. market to re-install apps, minor of double clicking on apps....More after a little testing...it is raining so maybe T-mobile is slow OR the 3G speed is a little less that v1.0.1 (15-20%) =< 1025kbps vs =< 800kbps ....
[G1 Android Development] doalittledanse:
How's the speed compared to 1.1? I haven't upgraded past that one because JIT seems to be way faster and i can handle the minor instability