[Think Tank] Google Earth for 1.6 devices - G1 Android Development

In the market, google earth is out , search com.google.earth
But its for 2.1 devices, any way to get this on 1.6?
Direct download here http://bit.ly/9ArPbS

Apparently ppl have tried using edited build.prop. It crashes on load since its relying on 2.1 frameworks perhaps
Try changing ur title to something like [THINK TANK]

Daneshm90 said:
Apparently ppl have tried using edited build.prop. It crashes on load since its relying on 2.1 frameworks perhaps
Try changing ur title to something like [THINK TANK]
Click to expand...
Click to collapse
Dan is right the eclair framework is needed to get that app working and I played with the prop and it still isn't working. Upgrade to eclair or use earth on your compter .

Wouldn't the app run terribly slow on the G1/MT3G anyways? Especially with the 10mb RAM hack.. 2.1 devices generally have a faster CPU, so couldn't they be restricting this for this reason?

skyundersea said:
Wouldn't the app run terribly slow on the G1/MT3G anyways? Especially with the 10mb RAM hack.. 2.1 devices generally have a faster CPU, so couldn't they be restricting this for this reason?
Click to expand...
Click to collapse
I think that's what it comes down to. Obviously Google could make it work on 1.6 if they wanted to, but since most devices running it are slower with less memory and lower screen resolution, there's no point. Try running Google Earth for Windows on a Pentium II with 256MB RAM and see how it performs...not very well.

Yeah.... give it a week or two and it will be running on 1.6.... no problems.

blackvyper said:
Yeah.... give it a week or two and it will be running on 1.6.... no problems.
Click to expand...
Click to collapse
No problems running, except the issue of very stuttery framerates, and small resolutions.

tried this on my milestone 2.0.1 and it wont even open the apk file says it isnt able to. and i cant find it on the market *must be the all so cool USA ONLY* deal that google loves to do to everyone else.

EkostonS said:
tried this on my milestone 2.0.1 and it wont even open the apk file says it isnt able to. and i cant find it on the market *must be the all so cool USA ONLY* deal that google loves to do to everyone else.
Click to expand...
Click to collapse
No, it needs 2.1

I tried it on a Dream with OpenEclair and KiNgxKxlicK ROMs, it won't open because of the resolution, AFAIK earth is made for 800 x 480.

Works fine on my Vodafone 32b Magic with KiNgxKxlick's latest 1.6.1 Eclair ROM.

incredulous said:
Works fine on my Vodafone 32b Magic with KiNgxKxlick's latest 1.6.1 Eclair ROM.
Click to expand...
Click to collapse
I am using the same rom 1.6.1 and it dont work wonder why?

it wouldn't load at all on my 32A Magic with KiNgxKxlicK's 2.1 1.6.1 (ahmgsk port).
After installation, click on Google Earth and nothing happens. tried again after reboot and still the same. REMOVED.

katsuya82 said:
it wouldn't load at all on my 32A Magic with KiNgxKxlicK's 2.1 1.6.1 (ahmgsk port).
After installation, click on Google Earth and nothing happens. tried again after reboot and still the same. REMOVED.
Click to expand...
Click to collapse
The same for me over a dream.

Same here too.. runnin cannons 2.1 and this **** will just not load..

Doesn't work on xROM, either.

WOW... so its not just the android version, and the speed of the device but also screen res..... WTF.. why do they, never mind.

PJcastaldo said:
WOW... so its not just the android version, and the speed of the device but also screen res..... WTF.. why do they, never mind.
Click to expand...
Click to collapse
Wow quit complaining. Is google earth THAT important to you? I saw that it wouldn't work on the G1 and I thought "Oh, who cares." The G1 does so much that it isn't supposed to to that google earth is a minor detail. Are you pissed off that Office 07 doesn't work properly with windows 98?

Missing libs i think
On KiNgxKxlicK 1.6.1.
The error message that I get that seems to have meaning to me is this:
Code:
android.view.InflateException: Binary XML file line #24: Error inflating class <unknown>
.....
D/dalvikvm( 4457): Trying to load lib /data/data/com.google.earth/lib/libembeddedearth.so 0x43de4638
I/dalvikvm( 4457): Unable to dlopen(/data/data/com.google.earth/lib/libembeddedearth.so): Cannot load library: reloc_library[1245]: 2715 cannot locate ''...
W/dalvikvm( 4457): Exception Ljava/lang/UnsatisfiedLinkError; thrown during Lcom/google/earth/EarthActivity;.<clinit>
W/dalvikvm( 4457): Class init failed in newInstance call (Lcom/google/earth/EarthActivity;)

meh, its not a vital app, frankly I dont even care that it doesnt work, but i'm sure I'd download it if it did... as for resolution, these arent terribly low, its 320x480, same as the iPhone and ALOT of other phones.

Related

Have your Cupcake and Eat It Too (today's cupcake build)

As you may know, Google merged their internal branch with Cupcake today. I built the image for dream and published it on my site. Have fun:
http://www.koushikdutta.com/2009/04/have-you-cupcake-and-eat-it-too.html
How about some screenshots of the differences? I would like to see what is different from the sapphire builds.
I would guess that you've flashed this to an actual handset.
I won't have a chance to play with this for the next few days, so I'm curious to know how your "clean" cupcake build compares to Haykuro's Magic builds in terms of features (Exchange support, etc) and hardware support (WiFi/BT/radio/etc).
If I DO get a chance I may play around with this, I'm curious. Thanks for the info!
Yeah, I have flashed it. This is a build of the Android code that was only just committed upstream today. It is not in any Haykuro build yet AFAIK. It's not a "usable" build by any means (no Google apps), but it's fun to see what will be coming down to our phone in a matter of weeks.
I am just wondering what you meant by ui changes. Are we talking about a different notification bar or something?
Good work!
I will wait a bit before I put cupcake on my ADP1, but still cool that Google has made the merge.
Ive been playing around with the latest Cupcake build on my Touch Pro and indeed, the changes are significant.
The changes cupcake brings can be found here
You got Android working on your HTC Touch Pro???
What on earth makes you come to that conclusion
Erm, yeah.. We have been working on porting Android to the Touch Pro and Diamond for more than 5 months. Check htc-android.com, htc-linux.org/wiki or even the topic here at XDA (which isnt active anymore, here.
Neccesary files can be downloaded over at connect-utb.com
I have the master build running, I compiled the kernel and wifi, and took all the google apps from the 502h and every thing is working as expected, just lost the LED notification, even when charging I am not seeing the LED light, else every thing is working, Maps, YouTube, market[just not able to download app, its stuck and downloading], but its all working, gmail, contacts and calender sync[but have to deploy all the closed source into it]
Thanks,
Pramod
PS: Compiled the 2.6.29 kernel but not able to make the wifi compiled with it.
Wow sounds very interesting, might have to flash just to take a look.
Untouchab1e said:
Erm, yeah.. We have been working on porting Android to the Touch Pro and Diamond for more than 5 months. Check htc-android.com, htc-linux.org/wiki or even the topic here at XDA (which isnt active anymore, here.
Neccesary files can be downloaded over at connect-utb.com
Click to expand...
Click to collapse
lol ^ that's the reason i got the G1. my manager had android on his touch around the same time the G1 was releasing. he's had problems with running it on the diamond as of late. i'll give hime the links you provided
Nvm got it.
Everything looks the same as haykuros build 4.5 without google apps, only thing i see different is the dev tools is now spare parts with different options.
diaztradeinc said:
Everything looks the same as haykuros build 4.5 without google apps, only thing i see different is the dev tools is now spare parts with different options.
Click to expand...
Click to collapse
Nothing is special but I think this build can run more smooth than haykuro 4.5. because it doesn't include Google apps so I will not flash it
funbacon said:
Nothing is special but I think this build can run more smooth than haykuro 4.5. because it doesn't include Google apps so I will not flash it
Click to expand...
Click to collapse
What does can run more smooth mean?
Either its faster than haykuro 4.5 or its not.
Is it faster?
lol @ dwang..... maybe wiki the word "smooth" haha
When something runs smoothly vs something running sluggish and slow there's a differenece
Smooth means fast yes.....
Runs about the same to me, meaning if you add google apps it will surely run slower then haykuros build. Also many bugs browser gives error and wont load, camera and video recorder force-closes, auto rotate does not work blah blah list goes on lol...
pr0cl1v1ty said:
lol @ dwang..... maybe wiki the word "smooth" haha
When something runs smoothly vs something running sluggish and slow there's a differenece
Smooth means fast yes.....
Click to expand...
Click to collapse
I don't think that was lost on dwang. I think he was referring to the entire sentence, which seems to contradict itself. By saying it'll run smooth, but then saying he will not flash it.
Nifty. I wish I had a spare device to play around with it. I may just have to install the emulator so I can mess with this stuff, I find it very interesting.

[Browser] Getting Flash to work on non-hero builds?????

Title says it all... I'm trying to get Flash working on regular 1.5 builds (like JF builds). It's not working at the moment so I hope you guys can help me.
Files that are related to get flash working:
SYSTEM -- LIB
libfl.so (registered as com/htc/flash/FlashLiteLib)
libflashlite.so
libflashsnddec.so
libwebcore.so ???
libdrmdec.so ???
libdrmdec_jni.so ???
SYSTEM -- APP
Browser.apk (which is using com.htc.framework, com.htc.android.pimlib)
and needs the following provider: browser.htc.util.HTCBrowserProvider
Browser.apk uses assets/plugins/flashplugin.so for flash, so we might build this into the older browser...
HTMLViewer.apk ??? (probably not)
SYSTEM -- FRAMEWORK
com.htc.resources.apk (not sure)
com.htc.android.easopen.jar (not sure)
com.htc.android.pimlib.jar (needed for browser)
com.htc.framework.jar (needed for browser)
com.scalado.util.ScaladoUtil.jar (probably not)
SYSTEM - ETC - PERMISSIONS
platform.xml
com.htc.framework.xml
You can get those files from http://forum.xda-developers.com/showthread.php?t=521059 the Haykuro ROM (browser.apk and HTMLviewer are in the apps_s zip file, other files in the rom itselve).
After copying all these files... it simply won't work. (Browser is not visible and after reboot it won't boot (no it's not broken, you are able to get into recovery)).
(libfl.so, libflashlite.so or libflashsnddec.so are hanging during boot... when removing these files, your system will boot again).
HTC added some multitouch features into the core framework, so you need their version of the framework jars too. I dexdumped their version of the browser and it looks like the code to actually turn on the flash plugin is pretty minimal (just a couple of settings), it can probably be reverse engineered.
On the bright side, this is probably pre-release code from Adobe. Which means something official is right around the corner.
cyanogen said:
HTC added some multitouch features into the core framework, so you need their version of the framework jars too. I dexdumped their version of the browser and it looks like the code to actually turn on the flash plugin is pretty minimal (just a couple of settings), it can probably be reverse engineered.
On the bright side, this is probably pre-release code from Adobe. Which means something official is right around the corner.
Click to expand...
Click to collapse
Hmm true... but I don't know if Adobe will release it for the G1, just like Opera which is also only releasing for HTC WinMo phones...
I thought it might be easy to get flash to work, since the browser is "plugin based", but if you put the flashplugin.so in /asset/plugins/ the browser doesn't load the plugin... And plugins also aren't loaded by the AndroidManifest.xml... So I really don't know how to get the plugin itselve to work in the Android1.5 browser.
What I am trying to do is only get the libfl.so, libflashlite and libflashdec in /system/lib/, and create a modified Browser.apk... so you don't need the htc framework at all... but I guess it isn't going to work like this.
02c5b6: 6e20 d302 3200 |0091: invoke-virtual {v2, v3}, Landroid/webkit/WebSettings;.setFlashPlayerEnabledZ)V // [email protected]
Is really all the browser does.
Sadly this method is only in the HTC modified framework. And there is quite a lot of flash-related code in there too.
Multi-touch ? I see that Browser doesn't have zoom feature. Does Hero support multi-touch ?
Hi Fun,
Yes in Hero,
Double tap to zoom.
funbacon said:
Multi-touch ? I see that Browser doesn't have zoom feature. Does Hero support multi-touch ?
Click to expand...
Click to collapse
in the current branch of (cupcake) code, the browser has a setting to set the plugin path via the database. if you get that working, you should be able to drop plugins into a folder and have them work.
blackeyedbrian said:
in the current branch of (cupcake) code, the browser has a setting to set the plugin path via the database. if you get that working, you should be able to drop plugins into a folder and have them work.
Click to expand...
Click to collapse
It looks like they hard-coded a bunch of other stuff into android.webkit.WebView and WebViewCore do to the flash: URL handling, so it's not just a simple drop-in plugin.
I have a 1g card and can't afford a cars suitable for a2sd. So I won't be running Hero until after I find a damn job, so hopefully someone figures this out. I really want flash.
Makes me wonder if Adobe will release Flash for Android... since it's hardcoded in the HTC framework and Android I think it will be HTC (new ROM's) only.
So the only easy thing to do is strip the Hero build to a regular Android build but leave the browser alone? (Since I've no experience to reverse engineer this) But the ROM is far from clean then... (you will have the full HTC framework which you won't use).
I highly suggest that everyone not put framework.jar from the HTC Hero...I did and it caused a boot loop...
Get flash to work on hero first.. its subpar atm.
Does hero rom even support flash? i see the app but any site i have gone to with flash i just see a flash plugin error
pentace said:
Does hero rom even support flash? i see the app but any site i have gone to with flash i just see a flash plugin error
Click to expand...
Click to collapse
flash8 is supported, flash9 is not.
thelamacmdr said:
I highly suggest that everyone not put framework.jar from the HTC Hero...I did and it caused a boot loop...
Click to expand...
Click to collapse
Here's a thought. What rom did you attempt this on? Perhaps you will see better results if you try to bring the necessary hero framework/libs over to an HTC baised build such as 6.0H or Rogers.
That might be why.. I was using a Google Ion Rom which if I know what you're saying...has a different framework.jar file in it than HTC Roms..
Hmm, so is the flash currently on the phone even practical? I mean, I can't even get the full YouTube site to work and watch videos on it, it just opens up the Flash window and stays black.
I had tried this on google ion rom, but failed. I think we can get the FlashPlayer to work first. It need a HTC FilePicker. But I am not sure what FilePicker need for native lib(.so).
I tried to do this by adb logcat.
SolemnWishing said:
Hmm, so is the flash currently on the phone even practical? I mean, I can't even get the full YouTube site to work and watch videos on it, it just opens up the Flash window and stays black.
Click to expand...
Click to collapse
it is practical, not for youtube, for youtube external app is better, or it need big screen, I use opera 9.5 and flash lite 3.1 on my ipaq 214, it have big 4" vga screen so it look nice when playing youtube on youtube web site, it is more practical for sites which are using flash, for example flash galeries, flash menus, etc. I'm not sure that adobe will release flash for g1, unfortunatly android allowe only java apps and flash need deeper integration (on lib level) so it cant be in .apk it must be released as update for os, if google will decide to include in future updates like donut (android 2.0) then we will get it...
Flash ads work fine, especially the ones here at xda. Caught me by suprise when i was browsing from my phone lol.
I went to worldstarhiphop.com and clicked on one of the videos there. The player popped up with the lil flash smoke effect. I was able to click play but the vid never started. I thought maybe it was because i was on edge.

[ROM] Modded Super D with dwang's kernel

As I`ve posted before some code in most new kernels is causing some issues while using my car's handsfree set(vw) I get random disconnects.
So as I like Super D and I like latest dwang's rom. I mixed both of them and took the best of both roms. What you get with this rom is latest Super D with the best kernel that's working for me.
i don't take any credit from it, I'm sharing a good setup working for me. I just took all the work done by people involved in Super D and Dwang's rom. Apart from that I also included advanced launcher themed by eesel with cyanogen's tray shape.(thanks rogro82, cyanogen and eesel)
Link:
http://www.megaupload.com/?d=V5H2P9IE
Trying will report back
thanks for sharing friend!
Edit:
1. Speed is good
2. Sometimes launcher lags in sweeping
3. No MT anywhere, well thats the Kernel thing
4. sign-in page force-closed on me many times but got over with that
5. Killing all the apps gives 60 MB free, wwhile on SD default kernel we get around 45 MB, this is great!
6. application response is very very quick
7. wall-paper gallery is older
Thats all for now....hope it helps those wanting to try this ...
Cheers,
I am not having those issues. Have you wiped everything before flashing? I didn't have any force close in the whole friday.
I have to research how to solve multi touch issue, because dwangs rom supports it
Wow, superb work. I may test it asap.
Hows battery life compared to stock SuperD? That was the thing put me away from Dwangs (and the random reboots).
Thankyou!
sounds interesting.
xabierd said:
I am not having those issues. Have you wiped everything before flashing? I didn't have any force close in the whole friday.
I have to research how to solve multi touch issue, because dwangs rom supports it
Click to expand...
Click to collapse
-no idea then, coz mine asked for re-inputting log-in information again and again. although everythhing was setup (meaning, synching was running while it was still bugging for signing in to google after I did it once)
Coming to your question, ya I always do full wipe, no matter what.
Your Mod definitely runs fast, congrates, and the force close is only stopped once you ignore signing in request and press Home button - done!
MT is an issue fr me, not that I use it while browsing web or Gallery very often but I like to have it for the sense of completeness
Good Job, I am now back to SupD tho.
P.S. Battery was not checked since I only stayed on this rom for less than an hour, not enough time right?
cheers
Battery life *seems* good so far
Multitouch is working indeed BUT not in the browser nor the photo gallery, I still have to look for more info. If you want to try it run MT visualizer. I 'm sure it's something about multitouch being handled in different way by donut or eclair.
I just flashed it without a wipe.
It works fine for me so far, but it should be mentioned that it is the white version
But i like suprising graphical changes
arefin said:
thanks for sharing friend!
Edit:
1. Speed is good
2. Sometimes launcher lags in sweeping
3. No MT anywhere, well thats the Kernel thing
4. sign-in page force-closed on me many times but got over with that
5. Killing all the apps gives 60 MB free, wwhile on SD default kernel we get around 45 MB, this is great!
6. application response is very very quick
7. wall-paper gallery is older
Thats all for now....hope it helps those wanting to try this ...
Cheers,
Click to expand...
Click to collapse
60 MB free? "
It use ramhack, compcache and swap?
BTW.. seriously.. The kernel have ramhack, right?
Now I'm using the rom SuperCSDI V1, and with the SupSetup I can turn on or off APP2SD.
I think it's a great thing, because installing apps on NAND they run a lot faaaaaaaaaaster! So I install default apps in NAND, and other apps in ext partition.
If I found a way to do it in this rom, I'll try it
PS: If you don't use compcache or swap and it have 60mb free on killing.. ramhack can be removed to use 3D application
xabierd said:
As I`ve posted before some code in most new kernels kernel is causing some issues while using my car's handsfree set(vw) I get random disconnects.
Click to expand...
Click to collapse
OMG i have the same exact issue with the random disconnecting. its been prevalent in every rom since cyan's 4.2.6 (and dwangs, super D, etc). I've tried pushing the older working "bluetooth.apk" from 4.2.6 to the newer builds with no success at all. Did you recompile the ROM to make it work? The perfect ROM to me would be Super D 1.9.2 with no ram hack and working bluetooth.
good work though, im willing to sacrifice 3D games for working bluetooth though so i may give this a run... *subscribed!*
sounds good flashing
nice Rom, but it only has 3 screens, and i don't like the launcher. Despite those things its great, i did a few tests
benchmark
lowest - 625
highest - 1084
ram
after killing all of the tasks i had 50mb
zachattack052 said:
nice Rom, but it only has 3 screens,i dont like the launcher
Click to expand...
Click to collapse
You can have up to 10 screens: menu -> more
And there are enough themes for the advanced launcher
ID# said:
You can have up to 10 screens: menu -> more
And there are enough themes for the advanced launcher
Click to expand...
Click to collapse
O wish i knew that before. than that solves the things i didnt like about it.
After killing all apps I still have around 40-43 mb.
quierotacobell said:
After killing all apps I still have around 40-43 mb.
Click to expand...
Click to collapse
thats normal for a donut rom
zachattack052 said:
thats normal for a donut rom
Click to expand...
Click to collapse
Yeah but that one guy got it over 50 just curious thats all.
dzasta said:
OMG i have the same exact issue with the random disconnecting. its been prevalent in every rom since cyan's 4.2.6 (and dwangs, super D, etc). I've tried pushing the older working "bluetooth.apk" from 4.2.6 to the newer builds with no success at all. Did you recompile the ROM to make it work? The perfect ROM to me would be Super D 1.9.2 with no ram hack and working bluetooth.
good work though, im willing to sacrifice 3D games for working bluetooth though so i may give this a run... *subscribed!*
Click to expand...
Click to collapse
What hands free set do you use?
I've read that you can solve it by editing /etc/bluez/audio.conf as follow
enable=
Disable=Headset,Gateway,Source,Control,Sink
uncoment #Master=true and replace it by Master=False (mind the caps)
It's working for BMW sets, give it a try may be you can keep 3d.
xabierd said:
What hands free set do you use?
I've read that you can solve it by editing /etc/bluez/audio.conf as follow
enable=
Disable=Headset,Gateway,Source,Control,Sink
uncoment #Master=true and replace it by Master=False (mind the caps)
It's working for BMW sets, give it a try may be you can keep 3d.
Click to expand...
Click to collapse
I drive an audi A3, and the OP drives a VW which most likely uses the same BT system. I just finished pulling the audio.conf from the phone and will edit it like you said. *fingers crossed* will update tomorrow...
UPDATE: The bluetooth fix mentioned by xabierd seems to have fixed my random disconnecting issue. didn't drop the connection once during my 30min commute to work. i normally experience at least 2-3 random disconnects every time i drive to/from work. yay!~!!
I'm glad I helped you, I am the OP too

[Project] 2708 kernels for Legacy Builds (ezterry look, or anyone w/ 2708 experience)

Introduction:
Two questions.
1: should they be renamed to be 2825 kernels?
2: I need some help. I have realized that 1.5 hero roms provide an amazing experience with the extra ram; when swap and cc are disabled, while still leaving sense running, I can switch freely between clock, browser, messaging, and rosie (sense homescreen) without any of them quitting. App launch times are phenomenal, and I really would like to use a 1.5 hero as a daily rom.
Unfortunately, SD card, ringtones, and other features don't work. My only explanation for this is because historically, hero 1.5 roms always had a seperate modules.sqf in /system/modules/modules.sqf.
I think this is the reason, because when I try a 1.5 non-hero rom with a 2708 kernel, the result is all of these functions working perfectly.
Some comments:
I find it amazing that these newer kernels work so well with the older roms.
I will update this thread as progress occurs.
CURRENT PROGRESS
The only progress I know of is this:
ezterry has posted an "OLDBUILDS" kernel that enables only 8 of the available 14 megs so that camera works.
Download: http://sandbox.devnull.name/android/ezOldBuildsKernel-2708_S.zip
Please help. This can be an amazing project.
Beawtifull thread.
I love sense roms (1.5 is ok ) and also vanilla donut.
With some mb of ram more would be amazing !
I have used 1.6 vanilla with 14mb ram more, but camera don't works.
update:
I can't find any 1.5 sense roms for g1 that DONT have the modules.sqf, but rather have them somewhere else.
Could people please:
1. provide me with information about what modules.sqf is, and how it can be extracted/ combined/moved/ etc so that anykernel will pick up those modules.
2. find a 1.5 sense hero rom without the modules.sqf, but with the necessary files to allow SD access and ringtone selection to work.
known not to work
mightymax hero 1.9
maxisma sense 2.0.1
qteknology 3.05 cupcake sense
sensehero 1.4
3. These problems could also be caused by xbin.sqf, as in the proper xbins aren't able to be accessed that allow sd card and ringtone selection... but both of those are conrolled by mediaserver which is in bin (afaik).
Smart people please input.
nobody? at least post your thoughts here about what you think i'm doing, is it stupid, is it blatantly obvious, etc?
Essentially what i'm asking for is a 1.5 kernel that works with 2708.
jcarrz1 said:
3. These problems could also be caused by xbin.sqf, as in the proper xbins aren't able to be accessed that allow sd card and ringtone selection... but both of those are conrolled by mediaserver which is in bin (afaik).
Smart people please input.
Click to expand...
Click to collapse
Um. The sqf files are just squash fs disk images (mount them via loop).. there is no reason my kernel will have an issue with this.
If /system/xbin isn't mounted check logcat/dmesg.
Make sure losetup is finding the loop device.. you may need some shortcuts to be added in init.rc to adjust the loop device location.. that or pull losetup or toolbox from a newer build and see if it helps.
If the screen isn't black its mostly just updating the core version of linux to behave I think.
No news? I would really love sense 1.5 with 14mb ram hack, or vanilla 1.6 with more 14mb
bumpidibump
jcarrz:
did you try the zx 1.5 hero (zachattack xillius thing)? dont know how it is called correctly
id go for sensehero 1.4 with the extra ram!
still the most stable/usable sense rom i ever flashed.
nagash91 said:
No news? I would really love sense 1.5 with 14mb ram hack, or vanilla 1.6 with more 14mb
Click to expand...
Click to collapse
Both Amon_RA ION1.6 and the ZX_Donut (and more) will run with ezterry's 2708 kernel. you will need to set the camera's rez to 1mb to take pictures. An if i remember correctly the wlan.ko from a CM or CM builds such as the biffmod is needed to make the wifi work.
I ran donut with ezterry's kernel for a long time, and finally switched to CM 6.1 due lots of new apps i want to try are 2.1+ only.
sleepyfu said:
Both Amon_RA ION1.6 and the ZX_Donut (and more) will run with ezterry's 2708 kernel. you will need to set the camera's rez to 1mb to take pictures. An if i remember correctly the wlan.ko from a CM or CM builds such as the biffmod is needed to make the wifi work.
I ran donut with ezterry's kernel for a long time, and finally switched to CM 6.1 due lots of new apps i want to try are 2.1+ only.
Click to expand...
Click to collapse
Thanks!
"set camera's rez to 1mb" ? you mean 1mpx?
nagash91 said:
Thanks!
"set camera's rez to 1mb" ? you mean 1mpx?
Click to expand...
Click to collapse
If you use the kernel in the op you get 12 extra mb of ram and camera will likely work as usual..
nagash91 said:
Thanks!
"set camera's rez to 1mb" ? you mean 1mpx?
Click to expand...
Click to collapse
Oops, yup 1m pixel
ezterry said:
If you use the kernel in the op you get 12 extra mb of ram and camera will likely work as usual..
Click to expand...
Click to collapse
yup, IIRC i tried it awhile ago and camera worked in high rez.
phone pictures are generally for a quick share on social networking sites anyways, 1mp was the setting i've always used.
sleepyfu said:
Oops, yup 1m pixel
yup, IIRC i tried it awhile ago and camera worked in high rez.
phone pictures are generally for a quick share on social networking sites anyways, 1mp was the setting i've always used.
Click to expand...
Click to collapse
Glad to still see an interest in this. I've been fooling around, and made some progress.
first, Beav_35 has made a donut 2708 kernel that has had mixed results for me so far. He nor I are responsible for any damage to your phone. it is not guaranteed to work at all. use at your own risk.
http://www.multiupload.com/0YROAJ4IDY
Second, I am working on getting a nice 1.5 sense working 100% on the g1. I will update this thread periodically.
thanks jcarzz1! il watch this thread!
Are there any complete, stable , ready-made Donut ROMs that has a 2708 kernel? Preferably AOSP.

[ROM][HTC G1/Dream 32B/32A] Android 2.2.2 AOSP R6 (wifi Fixed!) [8/3/11]

DEAD
I will try it today and let you know
thank you for the ROM
Sorry for slow download guys! When I finish my build, I upload to ge.tt which allows end users to instantly download while I upload. R3 is also broken -_- ; will upload fixed again
Please stick with r2 atm until r4 is done uploading.
Why the mandatory 96MB Swap and 512MB Ext4?
Wow...this rom is so horribly slow. Amazing how Roms can still get worse.
Slow UI, no improvements over 2.2.1, Market doesn't download anything. No Superuser installed. No busybox installed either. Commands such as a simple "cp" doesn't work.
Horrible.
Honestly with EzTerry's odex'd Asop and Richies F4T 182 de-odex asop build you are a long long long way off lads, nice effort but there is a lot better available already. And as for it being Danger SPL or custom mtd patch needed for what 90% of people are using 2708 with 14mb extra ram then this is a massive home goal.
Sorry just speaking the truth.
No, thats allright, I haven't applied much stuff to it yet.. I just uploaded it the day I compiled.
i'm impressed, just needs a little work. Also, those figures you have for free ram is with or without swap??
do you include a 2708 kernel? is that the default one? that could be a little clearer.
Sorry for the bugs, it is my first native phone rom.. Those figures are for free ram (physical) with the stock system without google apps with 2708 kernel. I did not include 2708 kernel yet but I will very soon! With the google apps and without the 2708 spl/radio, i got around 30 mb of free ram.
The mandatory ext4 partition and swap is for the R5 (uploading now) with a2sd but su still does not want to work. The "su" file was not included in the aosp compile for some reason and it messes everything up..
I like the fact you have changed the OP now about it being fast or faster
Look forward to see where you go with this fella, maybe a look at EzTerry's Froyo Parts.apk if it can help you out. I ported it with Terry's permission to F4T 182 and may be a useful additional update for your rom in the future to add additional functionality.
shadowch31 said:
I like the fact you have changed the OP now about it being fast or faster
Look forward to see where you go with this fella, maybe a look at EzTerry's Froyo Parts.apk if it can help you out. I ported it with Terry's permission to F4T 182 and may be a useful additional update for your rom in the future to add additional functionality.
Click to expand...
Click to collapse
Yeah sorry I overestimated
35 MB of free physical ram with market, pinyin IME, and google messaging running DangerSPL and stock radio, no 2708.
Well, I'm curious to see Froyo 2.2.2 on my G1 anyway. I have it on my TP2 and the major difference I noticed is that 2.2.1 doesn't have wifi tethering in its Wireless and Networking settings but 2.2.2 does. (Not really a big deal I suppose, since I already have a tethering app.)
I'm kinda curious about why Lazlo or the others haven't merged 2.2.2 yet.
highlandsun said:
Well, I'm curious to see Froyo 2.2.2 on my G1 anyway. I have it on my TP2 and the major difference I noticed is that 2.2.1 doesn't have wifi tethering in its Wireless and Networking settings but 2.2.2 does. (Not really a big deal I suppose, since I already have a tethering app.)
I'm kinda curious about why Lazlo or the others haven't merged 2.2.2 yet.
Click to expand...
Click to collapse
Simple answer - Go ask them
My guess is nothing more than a reduction in memory footprint??? And Wireless tethering is so easy using the google code website (just for those that don't know) http://code.google.com/p/android-wifi-tether/ last time I remember wireless tether included in a rom was back in Donut days.
shadowch31 said:
Simple answer - Go ask them
My guess is nothing more than a reduction in memory footprint??? And Wireless tethering is so easy using the google code website (just for those that don't know) http://code.google.com/p/android-wifi-tether/ last time I remember wireless tether included in a rom was back in Donut days.
Click to expand...
Click to collapse
link is broken, tried chrome and IE thinking it was the site...
Link works for me... Using Google Chrome
Updating rom soon (this week) with EVERYTHING fixed. No more lags and bugs..
jcarrz1 said:
link is broken, tried chrome and IE thinking it was the site...
Click to expand...
Click to collapse
Nothing wrong with the link, works fine. I suggest taking a closer look at your pc
i was using an adblocking hosts file. who the hell doesn't? especially on xda... LOL i guess some people like ads
Ok, R5_Stable released. It is COMPLETELY STABLE with 97% bugs fixed. The UI is smooth and fast after all dalvik-cache has caught up on first boot. I have already messed with odexing and it works but will be in next release(s) because I still like my themes!
Note:
-DO NOT use QuickBoot application as it shuts down android incorrect (at least on this build), it works, but after you press "reboot" and android loads, up, android immediately crashes, and then reboots again and works fine..
-Now includes Live Wallpapers
-Launcher pro is default launcher
-seperate google apps for legal reasons (yeah again)
-On first boot, please wait until dalvik-cache has caught up (about 2 min) or until the phone has received radio signal for rom to run at full speed
-Pershoots .11 kernel added now
- 30+ MB of free physical ram with danger spl!! 60+ with 2708+ radio/spl/kernel.
-Requires Danger SPL now
- battery life is good but does not last 2 days
- setCPU recommended with ondemand at 122mhz-614mhz s (lower if you want to save battery but still runs fine @ 528mhz)
- usb tethering does not work unfortunately (the one built into rom)
jcarrz1 said:
i was using an adblocking hosts file. who the hell doesn't? especially on xda... LOL i guess some people like ads
Click to expand...
Click to collapse
Fella just because you use a host file please don't blame the links or assume no-one else is using them when links work for them. Not my fault you blindly use the host file and have no clue of how to configure it to allow certain things. The fault is the user because a computer works on a simply principle of it can only do what YOU tell it too.
smooth but on the mytouch wen using any other kernel it breaks wifi and the stock kernel doesnt support the new radio

Categories

Resources