Database Info

Android for Kaiser with Wifi [Beta][Package]

UPDATE 08/26/09
http://www.scarlet-arrow.com/index.php?page=08-26-09---wifi-dma
DISCLAIMER
WARNING: This is given to you with the understanding that I nor the developers will be held responsible for any damage done to your phone while using Android.
Thank you for downloading this pre-packaged Android setup.
This is offered for free and I claim no ownership or rights. I am simply making it easier for you. All credit goes to the hard workers of the Android Vogue(Vogue Linux) project and XDA-Developers forums.
All the developers of the Android Project
Reference sites:
http://code.google.com/p/vogue-android/
http://code.google.com/p/vogue-hero/
Click to expand...
Click to collapse
READ ME
http://scarlet-arrow.com
This package is provided by: Natalic
08/26/09
---------------------------------------------------------------
THIS IS A DMA WIFI HERO BUILD:
Thanks goto addisu and dzo for getting a working Wifi module and all the hard working developers who get Android ported to the various devices.
Thanks to JAC for making the base rom (JACHeroski1.6)
This pack was tested and worked before uploading!
Directions:
0) If you have a data.img delete it first!
1) Copy all files from "Required" to the root of your memory card. I recommend at-least a 512mb.
2) Launch haret and click "Run"
2.1) You will need to wait for the data.img (data store) to be created, this takes around 2 minutes. This stores your files.
3) It takes sometime to get to the setup screen. If the screen turns off, just turn it back on. It will come up.
4) Go through the intro of Android (you only do this once)
The first 3 steps get you into Android
The following gets you Wifi (Kaiser/Tilt only)
* In this build, you can now select your WiFi in the setup.
In side Android:
1) Bring the menu up
2) Goto settings
3) Go to Settings -> Wireless Controls then click "Wi-fi" wait until there is a check
4) Select your network under Wi-Fi Settings
6) Make sure you save your "calibration" file and keep a copy of it save so you can just move it to future builds.
House cleaning:
I did not develop any of this kit, I simply put the pieces together and made them available in an easy to use package.
If you need any help please leave a comment in the forum!
To setup APN you must configure it, this can be found on the Android Vogue Wiki( http://code.google.com/p/vogue-android/wikii/HowToInstall )
Click to expand...
Click to collapse

Reserved
This is reserved.

Do we really need another thread for this? Why can't we just get Newbie to clean up his first post in the other thread? Seems kinda redundant...

loserskater said:
Do we really need another thread for this? Why can't we just get Newbie to clean up his first post in the other thread? Seems kinda redundant...
Click to expand...
Click to collapse
Well, the previous one is not for strictly a build, its more for the wikis and stuff. This thread is strictly for downloading a complete package.

cool, I'll bite!
Trying to follow the steps when i type "su"
i get "uid 10027 not allowed to su" , I did a search for this phrase and the only hit i got was the same error, but person asking was ignored.
Any ideas on how to get around this?
I'm running on a Tilt.
Thanks !!

Excellent, any mirror not from rapid or mega?, my network has the storage web filter , a FTP mirror will be great!
Thanks in advance,

natalic said:
This is reserved.
Click to expand...
Click to collapse
So the hero zip file is a rom? and if so can you flash it to a kaiser ?

keep it up...
if its like HTC HERO, it would be nice

Thanks natalic, it works.
Some additional points:
1) Ensure you're getting the file from the rapidshare link. I tried the latest build from the project site (android-1.5-2009-08-04.zip) and I never managed to extract the calibration file
2) There's a hero build here (http://drop.io/calibrationfiles) but I would suggest to get the calibration file out 1st before trying the hero build. It seems that you wont be able to access the terminal easily from Hero builds... (Maybe it's just me)
What works and not in the Android build (non-hero):-
1) Browser works
2) Market works
3) Google Sync works
4) Google maps does not work

loserskater said:
Do we really need another thread for this? Why can't we just get Newbie to clean up his first post in the other thread? Seems kinda redundant...
Click to expand...
Click to collapse
yes it is, android is starting to need a forum all to itself, or you can look at it like this if the android threads are builds from diff "android chefs" then it would be no different than multiple rom threads for diff chefs or diff wm versions.

Heres my working repack. Enjoy
http://www.mediafire.com/?k13tnjton22

Wifi is working great, Tested on an AT&T tilt with no SIM card inserted. Was able to connect to the internet, download from the market, etc.

How do I get SIM to work and get the phone signal?

shadowline said:
Wifi is working great, Tested on an AT&T tilt with no SIM card inserted. Was able to connect to the internet, download from the market, etc.
Click to expand...
Click to collapse
How did you download from market!? It just hangs on "Starting download" for me. Meh!
*Works. Just had to reboot *

TheParadox said:
How did you download from market!? It just hangs on "Starting download" for me. Meh!
*Works. Just had to reboot *
Click to expand...
Click to collapse
Same goes here.
I am now using HERO UI with a calibration file extracted from the standard build. Apps are not being downloaded... Google maps also not working... (Always Force Close)
Paradox: You forgot to mention about rebooting the phone after running getrom.txt as per your instruction in the zip file.

MOUSEY said:
Same goes here.
I am now using HERO UI with a calibration file extracted from the standard build. Apps are not being downloaded... Google maps also not working... (Always Force Close)
Paradox: You forgot to mention about rebooting the phone after running getrom.txt as per your instruction in the zip file.
Click to expand...
Click to collapse
Sorry mate.

MOUSEY said:
Same goes here.
I am now using HERO UI with a calibration file extracted from the standard build. Apps are not being downloaded... Google maps also not working... (Always Force Close)
Paradox: You forgot to mention about rebooting the phone after running getrom.txt as per your instruction in the zip file.
Click to expand...
Click to collapse
I thought the wifi was cooked into the system file? How do you do that?

MOUSEY said:
Same goes here.
I am now using HERO UI with a calibration file extracted from the standard build. Apps are not being downloaded... Google maps also not working... (Always Force Close)
Paradox: You forgot to mention about rebooting the phone after running getrom.txt as per your instruction in the zip file.
Click to expand...
Click to collapse
Is it reasonably responsive on your kaiser? I tried one build of it today, and it was awful. I mean all the features are cool, but no amount of features can replace responsivness...

MOUSEY said:
Same goes here.
I am now using HERO UI with a calibration file extracted from the standard build. Apps are not being downloaded... Google maps also not working... (Always Force Close)
Paradox: You forgot to mention about rebooting the phone after running getrom.txt as per your instruction in the zip file.
Click to expand...
Click to collapse
Can we see any screenshots of this or can you run such a screenshot program on android?

xxbabiboi228xx said:
Can we see any screenshots of this or can you run such a screenshot program on android?
Click to expand...
Click to collapse
The Hero UI works. Its just not that fast. I can vouch for that. I dont know how he has wifi working on it. I could have sworn the driver had to be cooked into the system.img

[ROM] myTouch 3G: Nothing but Netfilter 1.6 - Donut Update

Download link: MT3GV1.5_NBN1.5.zip
MD5:
1c962a4767659f86776fe6daf3052cf7 MT3GV1.5_NBN1.5.zip
This is the result of the work/messing around I did in this thread.
I started with the T-Mobile OTA stock ROM available here:
signed-opal-ota-150449.95700137.zip
I then:
1. Rebuilt the kernel with the same config as the ROM, except with the addition of the netfilter features required for tethering. (Kernel source is slightly newer than in the ROM as yesterday there were a few security related patches added to the repo.) The wlan.ko driver was rebuilt to match the new kernel as well.
2. Added the Superuser app and the Tethering app.
3. Removed the T-Mobile recovery and radio images. They are redundant at best, bricks waiting to happen at worst.
4. Re-packed and re-signed the ROM. (Only the ROM zip was signed so it would install via our recovery images. The internal apks were left alone.)
The result should be an experience identical to the stock software you had out of the box, but with the possibility of running apps that require root as well as tethering. Speed is the same, features are the same, apps are the same, etc.
There are plenty of great custom ROMs here if you're looking for more, but this will work if you're going for simple with no surprises.
UPDATE: Donut /1.6 update is on page 3.
UPDATE: Donut /1.6 DMD64 update is on page 4.

Is this for 32B or 32A?

This is for 32B.

awesome
hey man great job this is exactly what i want!!! great job!!!

atomtom, thank you for doing that. It's been working great the last 24 hours, no hidden gotchas or surprises from the updated kernel/wifi driver.

Thank you!!!...This is EXACTLY what I was looking for ..expecially for my friends who want root for wifi tether!!

Clean and Stock
Thanks for this ROM. I like clean and simple builts and this fullfill my tethering needs with my Viliv S5. I installed it today on MyTouch 3G.

Hi there
I installed this rom last night and by morning the phone was complaining about memory and had a bunch of processes force close.
Is there a mem leak or anything with this rom?

Not that I know of, but I only tested it for a few hours and then went on to Cyanogen for my daily use. Considering how similar this is to the stock ROM I would be very surprised if there was a memory leak.
Standard debugging questions: What SPL and radio are you running? Did you do a wipe before installing? Do you have a log we could look at?
I'll put this ROM back on my phone and see how well it's doing tomorrow.

Noticed an issue. The SU you are using isn't ideal. With tethering it was fine but as soon as I typed Su in terminal emulator, it starts the superuser permissions app, but it comes up blank. If I go back, its stuck waiting for Su permission. Zenthought.org has/had one I used, its from the JF and cyanogen builds. If u decide to use it make sure u change the Su binary too.

atomtom said:
Not that I know of, but I only tested it for a few hours and then went on to Cyanogen for my daily use. Considering how similar this is to the stock ROM I would be very surprised if there was a memory leak.
Standard debugging questions: What SPL and radio are you running? Did you do a wipe before installing? Do you have a log we could look at?
I'll put this ROM back on my phone and see how well it's doing tomorrow.
Click to expand...
Click to collapse
Hi there
I am running SPL 2005 (aman_ra mytouch root guide)
32B radio from htc site for google ion 2.22.19.26I
recovery 1.2.0G (aman_ra)
I have been going back and forth trying to find the rom that works best for me so yes i have done the format/wipe. Also since i want to be sure i might even run the following ontop of the format/wipe
fastboot erase system -w
fastboot erase boot
I dont erase recovery since i dont think i need to.
Please let me know.
Also - I would LOVE it if you could provide the same rom but with HTC keyboard/dialer.

flamingblue8z said:
Noticed an issue. The SU you are using isn't ideal. With tethering it was fine but as soon as I typed Su in terminal emulator, it starts the superuser permissions app, but it comes up blank. If I go back, its stuck waiting for Su permission. Zenthought.org has/had one I used, its from the JF and cyanogen builds. If u decide to use it make sure u change the Su binary too.
Click to expand...
Click to collapse
Yeah, the one that is available stand-alone is older than the one that comes with other ROMs. When I tried installing the newer apk pulled from Cyanogen 4.0.1 it would fail due to the key used to sign the ROM internals.
adb install Superuser.apk:
Code:
159 KB/s (14979 bytes in 0.091s)
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE]
adb logcat:
Code:
E/PackageManager( 58): Package org.zenthought.android.su has no signatures that match those in shared user android.uid.system; ignoring!
W/PackageManager( 58): Package couldn't be installed in /data/app/org.zenthought.android.su.apk
If anyone knows how to sort this out let me know and I'll update it.
That said, su still worked perfectly when I installed Better Terminal Emulator. (Of course, Better Terminal Emulator doesn't work to begin with. Try typing in a number.)

hmm interesting. when I was using just the stock ROM, then used 1click root, went into CM-recovery, followed by your directions, adb mount -a, then adb push the SU in reference, zenthought's, I had no issue. I then pushed the wlan.ko you put up, and flashed boot.img, rebooted, and finally installed the Superuser.apk, and I had NO issues whatsoever. i've got a nandroid backup of that system setup, in case there is anything of interest in there. I would have to boot back into it and remove my txts/mms/contacts, but i'd gladly share it for analysis.
I noticed the myTouch NBH appeared earlier, im going to try downloading that on my WinMo Wing (it connects to the wifi at the college im at but my G1 and myTouch won't.) i'll try flashing the NBH then your ROM, see what happens... oh and yes, I obviously wiped before installing ur ROM.

ROM has Superuser Permissions and Superuser Whitelist? Whats the difference and are they both needed?

Superuser Whitelist is the name of the apk that manages which app gets root access, su is the command line tool that actually performs the actions requested as root.

speedyls91 said:
Hi there
I installed this rom last night and by morning the phone was complaining about memory and had a bunch of processes force close.
Is there a mem leak or anything with this rom?
Click to expand...
Click to collapse
After last night and today of normal use, and leaving it on overnight, I haven't seen any behavior out of the ordinary.

I spent the last hour or so playing around with the donut update, but there are problems.
I downloaded the COC10 to DRC92 update zip and looked through it. Appears to be a new boot.img, a handful of files, and a bunch of binary patches. I made the following changes:
1. New kernel with the netfilter features enabled, but otherwise same sources and config.
2. Replaced the wlan.ko patch with the full file that goes with the new kernel since the one we're upgrading isn't the original and the patch won't apply.
3. Changed the update script to not try to patch the wlan.ko and skip over the version/key checks.
The update (applied manually via the recovery image) went fine, but there are problems with one of or both of WiFi Tether and Superuser. When attempting to start tethering there is just a general failure error but nothing bad in the log screen. In addition the Superuser app no longer honors the "always yes" setting. There are newer versions of both apps so I'll check those out later tonight/tomorrow.

Wow, doesn't sound good. Maybe leave out Wifi tether? I have been using a better su whitelist app, I think u may want to use it. I am using stock Donut at the moment, runs GREAT, so if I can help this would be great. What I am going to do is load my nandroid backup, clear out some garbage, and if you want I can send u my system.img and u can pick it apart appropriately to take a look at the SU I have along with the whitelist app. Perhaps that will solve the problems.

Wifi Tether is kinda the whole point so leaving it out isn't an option (or rather, having the user install it manually won't help). I think getting the new Superuser app working is a higher priority though. Unfortunately a system image of a stock ROM won't do any good. The problem is that the Superuser app ties in to the system in a way that requires them to be signed with the same key (or a shared key, something I haven't looked in to yet.)
Code:
I/PackageManager( 78): /system/app/Superuser.apk changed; collecting certs
E/PackageManager( 78): Package org.zenthought.android.su has no signatures that match those in shared user android.uid.system; ignoring!
My guess that the system is signed with T-Mobile's production key but Superuser is signed with a test key that is used on the fully custom builds. So it works fine with stock Android, Cyanogen, etc., but not here since I only changed the kernel, not the keys.
Obviously I can't re-sign Superuser.apk with T-Mobile's key so I have to re-sign the system with the test key. Unfortunately I have no idea 1) which file this is specifically, or 2) how to do it even if I knew.
Any suggestions are of course appreciated.

You mentioned that before. But even on the stock COC10 ROM, I pushed THAT su (from the last JF ROM,1.51) into /system/bin and then installed the apk into /data/app and it worked previously. If you wouldn't mind, plz send the new boot.img and I'll try flashing it through fastboot, as well as cm-recovery so I can use the root access adb to push the su into the stock donut. Which spl has fastboot enabled? I'll PM u my email.

[Addon] Multitouch Google Maps for CM 4.2.X[US/INT Nav SuperD, OpenEclair & others!]

[Addon] Multitouch Google Maps for CM 4.2.X[US/INT Nav SuperD, OpenEclair & others!]
Multitouch Google Maps 3.40 for CM 4.2.X (same as Nexus ota release) [US & INT NAV OPTIONS!!]
1: N1 Google Maps ported to 1.6 [US NAV ONLY]
http://www.mediafire.com/file/wngnq25bymy/mt-maps-cm-4.2-signed.zip
2: Opasha's version that removes the + and - zoom buttons [Same as above otherwise]
http://www.4shared.com/file/214300606/a98c0732/Maps340.html
3: Hacked International Nav with MT by Brut.all [once again amazing work!]
http://ul.to/308xt6/maps3.4.0-brut3-MT.apk
4: Brut.all's Hacked version for NON ROOTED Phones [Same as #3 otherwise]
http://ul.to/dxl2is/maps3.4.0-brut3-nonroot.apk
5: Dawitt1995's version with Brut.all's International Nav, and removed Zoom buttons [Same as #3 otherwise]
http://www.mediafire.com/file/onwvgwyd2ie/Maps-MT.zip
**************************************************
Instructions for options 1 & 2:
Flash via Amon_Ra 1.5.2 recovery (on top of current rom)
OR
unzip file
adb remount
adb push Maps.apk /system/app/Maps.apk
adb remount
adb push framework /system/framework
Instructions for option 3:
adb remount
adb shell find /system /data -name \*google\*maps.apk\* -o -name Maps.apk -delete
adb uninstall com.google.android.apps.maps
adb install maps3.4.0-brut3-MT.apk
OR in Recovery Console (must have the apk on the SD Card)
mount -o remount,rw /system
find /system /data -name \*google\*maps.apk\* -o -name Maps.apk -delete
pm uninstall com.google.android.apps.maps
pm install /sdcard/maps3.4.0-brut3-MT.apk
Instructions for option 4:
Install this as you would any new program (no commands necessary)
Instructions for option 5:
Flash via Amon_Ra 1.5.2 recovery (on top of current rom) [Dawitt reports you may have to flash #2 above first]
**************************************************
Nandroid is your friend
The running theory is that this will install fine on any Rom that has backported the Eclair graphics layer and or Multitouch framework.
Enjoy
Ps. Not my work, and I did nothing but flash it, whoever's it is gets full credit, just sharing I am not responsible for...anything

Will this work on Dwang-1.17.1 ??

Will work on any eclair ROM? Have KiNgxKxlicK AOSP 2.1 [1.4]
Thanks for sharing!

work on SuperD 1.8

Indeed! Works like a charm on SuperD's 1.8 Rom. Smoooooooth!
Only one minor detail: I would like for the + and - buttons to be removed, they're kinda redundant now

how about WG 2.6??

Pfeffernuss said:
Indeed! Works like a charm on SuperD's 1.8 Rom. Smoooooooth!
Only one minor detail: I would like for the + and - buttons to be removed, they're kinda redundant now
Click to expand...
Click to collapse
yea I agree! they need to be removed ... can any one do this?
thanks!

Can't flash it, I'm getting the following error: "Failure at line 5:
copy_dir PACKAGE:system7app SYSTEM:app"
Anything to do here?

I pushed the files from the update to JAC's xROM-Eclair 1.1.1 and it works great! Thanks for the post, ciwrl!

Navigation?
Does the file include Navigation outside the US?

works on OpenEclair 1.0. Thanx!

snellx said:
Does the file include Navigation outside the US?
Click to expand...
Click to collapse
just checking now...
nope

Installed without a problem on OpenEclair 1.1.1. Put the file on my sdcard, reboot in recovery and flash - simple as that. Multi-touch works better than on the web browser even it seems. Plus there's more stuff in the Labs (My Location button, Traffic with labels, etc). And if it's pulled from the N1 then is should work on most 2.x ROM's, no?

oh man I love you for posting this lol of course in a strictly platonic sort of way lol
works great in Super D 1.8, now if only we could get that new MT browser so that would be as smooth

I think its safe to say any 1.6 or newer roms this will work on.
btw KingKlick AOSP21 v1.4 Light or Dark + Custom = WORKS

Good looking out on posting this.

Alright, I'm having an issue. Tried to flash this over Wes Garner's WG Build and now whenever I touch the screen, it instantly force closes. How can I uninstall this version?

removed the annoying + and - zoom symbols
Pfeffernuss said:
Indeed! Works like a charm on SuperD's 1.8 Rom. Smoooooooth!
Only one minor detail: I would like for the + and - buttons to be removed, they're kinda redundant now
Click to expand...
Click to collapse
Dror520 said:
yea I agree! they need to be removed ... can any one do this?
thanks!
Click to expand...
Click to collapse
hey guys, i removed the annoying + and - zoom signs that are irrelevant. just flash in recovery- same directions as before. i've tested this on Super D 1.7 and it works like a charm and the zoom symbols are gone. the link is below
http://www.4shared.com/file/214300606/a98c0732/Maps340.html

Hmmm... do non-rooters have write access to system partition from recovery mode? If so, I might release "navi outside USA" hacks in form of update.zip and then will be no need for special "non-root" versions of GM.

opasha said:
hey guys, i removed the annoying + and - zoom signs that are irrelevant. just flash in recovery- same directions as before. i've tested this on Super D 1.7 and it works like a charm and the zoom symbols are gone. the link is below
http://www.4shared.com/file/214300606/a98c0732/Maps340.html
Click to expand...
Click to collapse
Hah, we should start a HackedGoogleMaps project, so we will have all fixes/hacks in one place

How to make MP4 work using Cyanogen eclair kernel on G1?

Hi Guys,
I compiled an eclair rom using the 2.9.26-eclair branch of Cyanogen kernel on github . And I ported the camera-related sources from donut branch to eclair branch. Now both 3d and camera can work on my G1. But I still canoot play mp4 on G1.
Would you please tell me how to make mp4 work on G1? I knew Kingklick had succeed to make mp4 work. Is his sources open?
Thanks.

loveheaven said:
Hi Guys,
I compiled an eclair rom using the 2.9.26-eclair branch of Cyanogen kernel on github . And I ported the camera-related sources from donut branch to eclair branch. Now both 3d and camera can work on my G1. But I still canoot play mp4 on G1.
Would you please tell me how to make mp4 work on G1? I knew Kingklick had succeed to make mp4 work. Is his sources open?
Thanks.
Click to expand...
Click to collapse
working dec libs come from the 2.1 drioderis dump which you can find in the eris dev forums.
you can also find them here
http://forum.xda-developers.com/showpost.php?p=5793964&postcount=667

Firerat said:
working dec libs come from the 2.1 drioderis dump which you can find in the eris dev forums.
you can also find them here
Click to expand...
Click to collapse
Would you please tell me which libs I should push into my 32B G1? I pushed libopencore_mp4*.so libOmxMpeg4.so from droid eris dump into my g1. But after that when I reboot my phone, my phone cannot be rebooted and stays at the first "G1 Tmobile" splash screen.

loveheaven said:
Would you please tell me which libs I should push into my 32B G1? I pushed libopencore_mp4*.so libOmxMpeg4.so from droid eris dump into my g1. But after that when I reboot my phone, my phone cannot be rebooted and stays at the first "G1 Tmobile" splash screen.
Click to expand...
Click to collapse
Code:
mkdir eris;mkdir Firerat3dvid
cd Firerat3dvid
unzip <fullpath to the update zip>
export SomeOtherDir=$PWD
cd ../eris
unzip <fullpath to dump zip>
cat > ~/bin/compmd5sum << "EOF"
#!/bin/sh
# md5sum a bunch of stuff
md5sum $1;md5sum $SomeOtherDir/$1;adb shell md5sum /$1
EOF
chmod 755 ~/bin/compmd5sum
find . |sed s/^/compmd5sum\ /|sh
now you can compare files in two dir on your linux box against the ones on your phone, tells you whats 'missing' what are the same and what are different
PS the files you need are in the zip files in the link I gave you
just thought that the above script might come in handy for someone wanting to compare files

Thank you very much!
I downloaded the CE-12-Patch_3D_vid_signed.zip you prodivded and pushed all the libraries in your zip (except the wlan.ko) into my G1. The kernel my G1 used is built from Cyanogen kernel eclair branch. After pushing the libraries, I reboot my G1.But the G1 got stucked in the first "T-mobile G1" splash screen and couldn't be reboot into the system.
Why did it happen? I should use your kernel?? The opencore library depends on the kernel?? I think the opencore is independent. Even if there is something wrong with opencore, G1 can always be reboot. Am I wrong?
Firerat said:
Code:
mkdir eris;mkdir Firerat3dvid
cd Firerat3dvid
unzip <fullpath to the update zip>
export SomeOtherDir=$PWD
cd ../eris
unzip <fullpath to dump zip>
cat > ~/bin/compmd5sum << "EOF"
#!/bin/sh
# md5sum a bunch of stuff
md5sum $1;md5sum $SomeOtherDir/$1;adb shell md5sum /$1
EOF
chmod 755 ~/bin/compmd5sum
find . |sed s/^/compmd5sum\ /|sh
now you can compare files in two dir on your linux box against the ones on your phone, tells you whats 'missing' what are the same and what are different
PS the files you need are in the zip files in the link I gave you
just thought that the above script might come in handy for someone wanting to compare files
Click to expand...
Click to collapse

loveheaven said:
Thank you very much!
I downloaded the CE-12-Patch_3D_vid_signed.zip you prodivded and pushed all the libraries in your zip (except the wlan.ko) into my G1. The kernel my G1 used is built from Cyanogen kernel eclair branch. After pushing the libraries, I reboot my G1.But the G1 got stucked in the first "T-mobile G1" splash screen and couldn't be reboot into the system.
Why did it happen? I should use your kernel?? The opencore library depends on the kernel?? I think the opencore is independent. Even if there is something wrong with opencore, G1 can always be reboot. Am I wrong?
Click to expand...
Click to collapse
your linux will be running fine, its the Android that isn't happy
the libs are not dependent on the kernel, but may be dependent on something which is already in CE
tbh I can't really help you , I have no idea what 'ROM' you are pushing these libs to.....
logcat is your friend, I have a whole bunch of them on one line
Code:
adb logcat;adb logcat;adb logcat;adb logcat;adb logcat;adb logcat;adb logcat;adb logcat;adb logcat
make sure your phone is connected the first time, and it will happily sit there when you unplug, 'waiting for device' till you plug it back in.
and in another console
adb shell busybox top
sometimes you can even shell in if you are not seeing anything on logcat
'busybox top' will give you an idea of what is running
and there is nothing stopping you from having a couple more terminals open
one with a shell for 'doing stuff' and another for pushing and pulling stuff
all while watching top and logcat
your loop is probably to do with drm, but the logcat will tell you

Firerat said:
your linux will be running fine, its the Android that isn't happy
the libs are not dependent on the kernel, but may be dependent on something which is already in CE
tbh I can't really help you , I have no idea what 'ROM' you are pushing these libs to.....
logcat is your friend, I have a whole bunch of them on one line
Code:
adb logcat;adb logcat;adb logcat;adb logcat;adb logcat;adb logcat;adb logcat;adb logcat;adb logcat
make sure your phone is connected the first time, and it will happily sit there when you unplug, 'waiting for device' till you plug it back in.
and in another console
adb shell busybox top
sometimes you can even shell in if you are not seeing anything on logcat
'busybox top' will give you an idea of what is running
and there is nothing stopping you from having a couple more terminals open
one with a shell for 'doing stuff' and another for pushing and pulling stuff
all while watching top and logcat
your loop is probably to do with drm, but the logcat will tell you
Click to expand...
Click to collapse
Thank you very much!
I used your method and found it is because my rom could not load the libwebcore.so in your zip. So I pushed my orignal libwebcore.zip back into G1, my G1 can boot now. But after that I still cannot watch Mp4 on my G1...
Would you please give me some advice? Thanks.

loveheaven said:
Thank you very much!
I used your method and found it is because my rom could not load the libwebcore.so in your zip. So I pushed my orignal libwebcore.zip back into G1, my G1 can boot now. But after that I still cannot watch Mp4 on my G1...
Would you please give me some advice? Thanks.
Click to expand...
Click to collapse
CE1.2 with my vid patch
wait for CE2
or Kings 1.8 AOSP
or
check the code in this
http://forum.xda-developers.com/showpost.php?p=5889900&postcount=4
with a bit of deduction, you could figure out what is missing/different
as I said in my last post, I can't help you as I have no idea what ROM you are trying to get mp4 to run on.........................................

Installing/Pushing CE-12-Patch_3D_Vid_signed.zip
Got a question... I recently downloaded the v4_1.zip, and was wondering if it's possible to incorporate the CE-12-Patch_3D_Vid_signed.zip in to it. I'm not new to the whole rooting thing, and have tried several variations of the Eclair and Donut roms floating around here. Unfortunately, I'm not to well versed in ADB. My main interest in pushing the above zip is to finally have an Eclair rom with working video. If anyone can help me out with this, it'd be greatly appreciated.

will4958 said:
Got a question... I recently downloaded the v4_1.zip, and was wondering if it's possible to incorporate the CE-12-Patch_3D_Vid_signed.zip in to it. I'm not new to the whole rooting thing, and have tried several variations of the Eclair and Donut roms floating around here. Unfortunately, I'm not to well versed in ADB. My main interest in pushing the above zip is to finally have an Eclair rom with working video. If anyone can help me out with this, it'd be greatly appreciated.
Click to expand...
Click to collapse
the v4 is a different beast
King's Eris has working video
King's Eris CachHacked has working video and is a lot faster

CE-12-Patch_3D_Vid_signed.zip
Thanks for the response. Actually, I was only using the v4 rom as an example. I have tried King's Eris rom, and I think I have the most recent version of it, but the last time I tried it the camcorder did it's I'm not gonna work for you thing. Is there a way to push the CE-12-Patch_3D_Vid_signed.zip to this rom instead, or did I misinterpret the description of this patch? At any rate, it is fun trying all these new and different roms. Can't wait for a fully working 2.0 pastry.
P.S: I just tried the FR-v4OL-CH-0-1_S.zip rom, and it does have video playback. Unfortunately, the camcorder is still non-funtional, of course, and data doesn't appear to be working.

will4958 said:
Thanks for the response. Actually, I was only using the v4 rom as an example. I have tried King's Eris rom, and I think I have the most recent version of it, but the last time I tried it the camcorder did it's I'm not gonna work for you thing. Is there a way to push the CE-12-Patch_3D_Vid_signed.zip to this rom instead, or did I misinterpret the description of this patch? At any rate, it is fun trying all these new and different roms. Can't wait for a fully working 2.0 pastry.
P.S: I just tried the FR-v4OL-CH-0-1_S.zip rom, and it does have video playback. Unfortunately, the camcorder is still non-funtional, of course, and data doesn't appear to be working.
Click to expand...
Click to collapse
/data not working?
if data wasn't working it wouldn't boot past the bootanimation splashscreen
if data is 'full' reboot, it will correct itself

Unfortunately, when I try to do something that requires a data connection, it suggests using wifi. During setup, I did select the first connection option, which I think was data and wifi or something like that. When I try to go into Market to sign in that way, I can't connect. Is there a step I'm missing, or has this happened to anyone else? Also, is there a way to push the CE-12-Patch_3D_Vid_signed.zip into the FR-v4OL-CH-0-1_S.zip rom, or can I just flash like a normal zip? Thanks in advance.

will4958 said:
Unfortunately, when I try to do something that requires a data connection, it suggests using wifi. During setup, I did select the first connection option, which I think was data and wifi or something like that. When I try to go into Market to sign in that way, I can't connect. Is there a step I'm missing, or has this happened to anyone else? Also, is there a way to push the CE-12-Patch_3D_Vid_signed.zip into the FR-v4OL-CH-0-1_S.zip rom, or can I just flash like a normal zip? Thanks in advance.
Click to expand...
Click to collapse
ahh, sorry I'm getting all mixed up, because everyone is stressed out over FR-a2sd using /data for something useful instead of leaving it as an empty,wasted space.
yes, data connection is not working, tbh I don't know why the Market doesn't work even if wifi is working..
The CE-12-Patch_3D_Vid_signed.zip isn't going to do anything for FR-v4OL-CH-0-1_S.zip
its just a 3D kernel , and libs I took from the eris dump which got video working.
infact , the libs are 'mostly' the same as the ones already in v4OL
( which means I'm totally not understanding why video is dark, got to be a framework thing, maybe, I don't really know, just guessing )
Flashing / pushing CE-12-Patch is just going to kill v4OL
I did CE-12-Patch a long time ago, shortly after re-visiting xda after initially rooting my g1 way back in Feb '09.. kinda wished I'd stuck around then.
anyway, CE-12-Patch WILL break v4OL, is it doesn't mount mtdblock4 in the right place.
the v4OL is beta , lots of things don't work
if you get your kicks trying to fix broken things, or making yourself understand things you don't understand ( i.e. you self teach )
then it is for you.
if you want things to work 'out of the box' ,
King's Eris mostly works
ce12 cachehack works
ce2.0 works ( with a 'lil' fixup, facebook fix is in the thread FR*S.zip coming soon.. )
OE1.3.0.1 has things working ( anyone flashed ce12-patch over oe1.3 ? )
and good ol' SuperD works very well.
personally I think your best root is the CE12 CacheHack
It's fully functional, and best of all, CE2.0 is a *no wipe* update
You can flash CE2.0 , just a couple of fixes that need to be consolidated
they are in the thread , minor fix is at post #1401 ( which I will update to a "no hassle,flash straight after CE2.0" soon )

[ICON] Replace the stock Android browser icon with Chrome

Ive always found it interesting that Android’s stock browser does not have the Chrome browser icon, seeing as it technically is a mobile version of Chrome. So, I did some quick reversing and took the stock 2.2 browser and replaced the icon. The result is a new Browser.apk, identical to the original stock one except for the changed icon.
To install this, just read on for the full instructions. Note that we will be backing up your stock Browser.apk so you can easily revert the changes. Also note that this requires root.
Firstly, you need the Android SDK, available for Windows, Linux and OSX here
The following instructions are for Linux, but given you have set up the SDK correctly, the instructions are the same regardless of which operating system you use.
Firstly, connect your rooted phone running Android 2.2 to your computer. Then download the new Browser.apk and save it. Note that for some reason, the file name gets changed from Browser.apk to browser.apk when you download, so be sure to rename it.
Open up a terminal and navigate to the directory in which you saved your Browser.apk and then type in the following..
Code:
adb remount
Then we will take a backup of your current Browser.apk.
Code:
adb pull /system/app/Browser.apk Browser.apk.original
Then we will push over the new Browser.apk
Code:
adb push Browser.apk /system/app/Browser.apk
Lastly, we reboot the phone
Code:
adb reboot
After the phone boots back up, you will notice the new icon in your launcher menu. Enjoy!
This was tested and confirmed working on my rooted Nexus One running Modaco's rooted Android 2.2 ROM.

Think whoever moved this misunderstood what this is.. its an app basically..

theres something in market called fake chrome that does just this

Sure, but that wont replace the stock browser icon.. it will just add another one.. so then you have two..

Icon looks great; however, FC's on enom 2.11.3

lengz said:
Icon looks great; however, FC's on enom 2.11.3
Click to expand...
Click to collapse
Ah, Im sorry. I can only confirm that it works on Modaco's rooted stock Android 2.2 ROM. If you want I can fix it for you if you give me your original Browser.apk though..

Very cool. I don't have an N1, but liking the concept!

Untouchab1e said:
Ah, Im sorry. I can only confirm that it works on Modaco's rooted stock Android 2.2 ROM. If you want I can fix it for you if you give me your original Browser.apk though..
Click to expand...
Click to collapse
You don't need to do it, but here's the apk for ref.

Should work on any android phone running 2.2.. But apparently not on all ROMs
Sent from my Nexus One using Tapatalk