Related
It should fully work with G1!
Please report bugs etc...
WARNING: It's a T-Mobile US ROM! It send's SMS's to a short dial in the US..
To disable this, download terminal-emulator then do this:
su
mount -o rw,remount /dev/block/mtdblock3 /system
rm /system/app/MyFaves.apk
It's reported to be fast in the Magic-Forum.
Here's the thread: http://forum.xda-developers.com/showthread.php?t=533641
Features:
-JesusFreke 1.51 Kernel
-Root
-T-Mobile IM-App
-Amazon MP3
-MyFaves-App
-Pretty much a plain Google ROM, like ION
-Market working
-WiFi working!
CRB57!!
I found out, this is not the FINAL MyTouch ROM with all features. It's a pre-version for testing-purposes. I don't know when and if the final gets leaked.
http://www.megaupload.com/?d=DZILITTG
hotweiss said:
This is the fastest ROM that I have tried. Now if we could remove the T-Mobile customization and get the wifi working...
Click to expand...
Click to collapse
NOTICE: WiFi IS working in this build, this is a quote from the magic's-thread.
Whats so good about the Mytouch rom.
I see people over in the Magic forum talking about the T-Mobile app, Sherpa, being in this ROM. What's Sherpa, lol?
davidemartindale said:
I see people over in the Magic forum talking about the T-Mobile app, Sherpa, being in this ROM. What's Sherpa, lol?
Click to expand...
Click to collapse
The Sherpa application allows users of the phone to access locally relevant information right on their phone. Sherpa is a local discovery application that learns a user's favorite type of locations and other preferences over time.
Source: http://www.i4u.com/article25486.html
But I can't find such an app in the leaked ROM.
Can someone post the wallpapers from the rom?
Anyone checked if Bluetooth works OK on this?
Tks!
Hello. I flashed this rom. it seems no root in it. when i type su in terminal emulator.
it said: permission denied.
How can I get root. please help.
Oh, sorry.
Forgot this.
Go to recovery, press alt-x , enter, then:
Mount system
Cat /system/bin/sh > /system/bin/su
Chmod 04755 /system/bin/su
@maxisma,
Would love to test this ROM but, I'm one of those who can't stand one-handed phone-to-ear operating so,
is BT handsfree working?
Tks.
Sorry, i don't know if it works or not.
Just try, make a nandroid backup ;-)
it works, thank you very much.
isn't the MyTouch using the cupcake release? why would you want to go to that when there are other cupcake releases out there?
I thought there was something special about this rom, so i just ported it without really looking
at this rom.
It's comparable to ION, in ION there's nothing special except the dalvikvm.
This build is fast too, tmo has optimized it.
maxisma said:
I thought there was something special about this rom, so i just ported it without really looking
at this rom.
It's comparable to ION, in ION there's nothing special except the dalvikvm.
This build is fast too, tmo has optimized it.
Click to expand...
Click to collapse
ION dalvikvm is EXACTLY the same as jf 1.5 image. Exact same checksum. Zero difference.
i assume u get this from androinin.net. first leak was by us.
I got this from the Sapphire/Magic-Forum in xda-developers.. and just ported it to g1.
Sorry, will add credit!
I got this from the Sapphire/Magic-Forum in xda-developers.. and just ported it to g1.
Sorry, will add credit!
dwang said:
ION dalvikvm is EXACTLY the same as jf 1.5 image. Exact same checksum. Zero difference.
Click to expand...
Click to collapse
Yea i tried the ion and the jf they seem the same i did however wipe wipe load update wipe then updated had some boot loops from a theme. But yea i got the jf to run faster then i ever had before. I also got dalvik cache on sd i did that right after loading the rom.
So what is support to be so good about this rom?
wats da point
x140d4n said:
i assume u get this from androinin.net. first leak was by us.
Click to expand...
Click to collapse
might wanna type the site address correctly if your from there
MotoBlur 0.2 for HTC Magic 32a
Extremely experimental, try at your own risk, no support offered at all.
This was taken from Drizzy's earlier BetaBeta that I had a play with a few days ago and decided I might as well release it - he's added dream fixes, but not much of it applies to us so far from what I can see so haven't bothered updating it. Thanks should go to Drizzy for his work on getting this to start with tho!
It was a quick repack I made just to have a play with it and see what it was like - so I've added little to it.
Update: 0.2 now with a BFS303 kernel
If something's broken, don't expect me to fix it - my knowledge of the internals of it all is pretty small, but if you know HOW to fix it, feel free to let me know and if its' worthwhile I may even package it again
What's not working:
Wireless
Bluetooth
Laggy initially when the MotoBlur setup is running, but it speeds up once it's finished syncing.
Enjoy!
Downloads
MotoBlur 0.1 for 32a FULL INSTALL from:
http://www.megaupload.com/?d=DBJIDJAU
MotoBlur 0.2 for 32a UPDATE only!
(ie. you still need to install 0.1 first, then apply this!):
http://www.megaupload.com/?d=TFW1LR3Y
Enjoy!
I might try it just for checking it out. But wont just jump the wagon now that you don't seem to dedicated to make updates for it
Anyway thanks for sharing!
Just flashed it and it boots fine
Too bad that it looks like i cant connect to motoblur's servers. I get an error which is something like "blur service seems to be busy" and i'm not able to register:\
can someone port it for 32A the rom made by Drizzy at the dream forum. He seems to able to fix many things. http://forum.xda-developers.com/showthread.php?t=557982
It's not that I dont' want a working rom - I'm just new to this and don't know how to fix all of it without a lot of trial and error
As for Drizzy drake - his one hasn't really fixed the main problems much either - which are wifi/bt and speed.
I really rushed with 0.1 - hadn't realised this wasn't cupcake and was donut and that gives me a bit more incentive to fix it.
I've started on a 0.2 release with a BFS 303 kernel, working modules, xbin and if I can, wifi working - will let you know if/when I am successful.
Let me know if you see any easy fixes in here - I'm still learning my way around a rom like this and would appreciate any help.
Cheers,
Radix999
Thanks a lot for posting the rom! You made my day!
I really see a big potential in the MotoBlur OS, it just need speed and wifi
Hope you can get it fixed
Sorry i'm a bit confused here, maybe i missundestand something but in your first post you write:
And I don't even remember which kernel I put in.. think it was a 2.6.27 one as this is cupcake not donut.
Click to expand...
Click to collapse
but in 2nd post:
Hadn't realised this wasn't cupcake and was donut and that gives me a bit more incentive to fix it.
Click to expand...
Click to collapse
Can you please clear out my confusion
Radix999 said:
MotoBlur 0.1 for HTC Magic 32a
Extremely experimental, try at your own risk, no support offered at all.
It was a quick repack I made just to have a play with it and see what it was like - so I've added little to it.
I forget where I got this from, and I don't even remember which kernel I put in.. think it was a 2.6.27 one as this is cupcake not donut. I was asked to upload this just so other ppl could play.
If something's broken, don't expect me to fix it, but if you know HOW to fix it, feel free to let me know and if its' worthwhile I may even package it again
Enjoy!
Download 0.1 from:
http://www.megaupload.com/?d=DBJIDJAU
Click to expand...
Click to collapse
I cant open this url. a mirror please?
This is an update to the above rom - just updates the kernel to 2.6.29-6-BFS303.
It improves the experience a bit, but it's still very sluggish and I've not been able to get wifi/bt working:
Just download the update.zip below and apply on top of an existing motoblur 0.1 install:
MotoBlur 0.2 for 32a update:
http://www.megaupload.com/?d=TFW1LR3Y
If anyone can help me
a) mount the sqf files correctly,
b) work out what's wrong with wlan and BT
I'd appreciate the help!
nubcake said:
Just flashed it and it boots fine
Too bad that it looks like i cant connect to motoblur's servers. I get an error which is something like "blur service seems to be busy" and i'm not able to register:\
Click to expand...
Click to collapse
like you
Radix999 said:
MotoBlur 0.2 for HTC Magic 32a
Extremely experimental, try at your own risk, no support offered at all.
It was a quick repack I made just to have a play with it and see what it was like - so I've added little to it.
Update: 0.2 now with a BFS303 kernel
If something's broken, don't expect me to fix it - my knowledge of the internals of it all is pretty small, but if you know HOW to fix it, feel free to let me know and if its' worthwhile I may even package it again
What's not working:
Wireless
Bluetooth
Laggy initially when the MotoBlur setup is running, but it speeds up once it's finished syncing.
Enjoy!
Downloads
MotoBlur 0.1 for 32a FULL INSTALL from:
http://www.megaupload.com/?d=DBJIDJAU
MotoBlur 0.2 for 32a UPDATE only!
(ie. you still need to install 0.1 first, then apply this!):
http://www.megaupload.com/?d=TFW1LR3Y
Enjoy!
Click to expand...
Click to collapse
Please 32b!!!!
I'm just wondering - would wifi work if I flashed MotoBlur 0.2 and then flashed the newest kernel for CM ?
neojonax said:
Please 32b!!!!
Click to expand...
Click to collapse
Take a look at the one over at the Dream forum - http://forum.xda-developers.com/showthread.php?t=557982
Briix said:
Take a look at the one over at the Dream forum - http://forum.xda-developers.com/showthread.php?t=557982
Click to expand...
Click to collapse
Ok,THANKS!!!!!
Briix said:
I'm just wondering - would wifi work if I flashed MotoBlur 0.2 and then flashed the newest kernel for CM ?
Click to expand...
Click to collapse
They should be the same except for the ramdisk really.. I used the same kernel I compiled for CM 4.1.999 w/ BFS303
I guess you could always try it and if no luck then flash my 0.2 update afterwards
Thanks it's working
Thanks, it's working on my magic. (v0.1) I like to see how Motorola made it. I really enjoy.
BTW, how can I switch it off?
It does not respond to red Power switch. I saw Motorola's android phone had fewer switches.
I will "adb sync" few times, and pull out the battery...
and I will apply v0.2 after download.
Damm, i tried to flash it again.
I still get the following error whenever i try to register a MOTOBLUR account:
"The Blur service has indicated it is busy".
May it be that they are blocking my region or my mobile operator blocking any connection to their servers? These are the only things i can think about
setupr said:
BTW, how can I switch it off?
It does not respond to red Power switch. I saw Motorola's android phone had fewer switches.
Click to expand...
Click to collapse
Haha.. yeah, I did that too - I discovered that you can also use adb shell and 'toolbox reboot' to turn the phone off.
The Cliq has no end call button, hence why it's not assigned to do anything.
nubcake said:
Damm, i tried to flash it again.
I still get the following error whenever i try to register a MOTOBLUR account:
"The Blur service has indicated it is busy".
May it be that they are blocking my region or my mobile operator blocking any connection to their servers? These are the only things i can think about
Click to expand...
Click to collapse
I managed to sign up a couple of days ago when I first created this rom - but I think too many people have signed up and their phones aren't even out yet so they've blocked new users from signing up or something - I dunno.
Radix999 said:
Haha.. yeah, I did that too - I discovered that you can also use adb shell and 'toolbox reboot' to turn the phone off.
The Cliq has no end call button, hence why it's not assigned to do anything.
Click to expand...
Click to collapse
Haha. I was checking the Dream forum - http://forum.xda-developers.com/showthread.php?t=557982 . They are same situation.
Someone was writing about [Home]+[Menu]+[Power] switches. Is this "Reset" or "Shutdown"? If it is "Reset", it is same like "pull out the battery"....
Also, does "toolbox reboot" shutdown system properly? at least, I expect it does sync file system.
I did in adb shell "toolbox reboot", while pressing [Home] switch. It did not reboot but switched off.
How to switch off with Motorola Cliq ? There must be a proper way of shutting down the system.
Radix999 said:
I managed to sign up a couple of days ago when I first created this rom - but I think too many people have signed up and their phones aren't even out yet so they've blocked new users from signing up or something - I dunno.
Click to expand...
Click to collapse
In the Dream forum, there was a post http://forum.xda-developers.com/showthread.php?p=4677405#post4677405
jaygajay said:
> Is't it possible to jump over Blur account to Homescreen?
You have to delete Setup.apk
If you have adb installed on ur computer plug in your phone and do
Code:
adb root
adb remount
adb shell rm -r /data/app_s/Setup.apk
adb shell reboot
Click to expand...
Click to collapse
The end button issue I think has been resolved by Twisted over the dream forum as mentioned by Drake in Moto v0.5 change log, Can someone install that fix and confirm.
Not really sure what this does..
Its the kernel config file from the fender 1.6 dump. No other rom will use touch screen abilities with this phone except stock so Cursordroid concluded the kernel may be different.
If anyone can use this to make a kernel, or port roms it would be greatly appreciated. Sux having a rooted phone while having to use the stock rom lol
If I knew how to do it I would hop on it... but I is not as smarts as youu guyz
Remove .zip from end of file
EDIT- When the new Mytouch 1.2 comes out in the next couple months, this will be the same build included on it. so nothing like ahead start lol
crypysmoker said:
Not really sure what this does..
Its the kernel config file from the fender 1.6 dump. No other rom will use touch screen abilities with this phone except stock so Cursordroid concluded the kernel may be different.
If anyone can use this to make a kernel, or port roms it would be greatly appreciated. Sux having a rooted phone while having to use the stock rom lol
If I knew how to do it I would hop on it... but I is not as smarts as youu guyz
Remove .zip from end of file
EDIT- When the new Mytouch 1.2 comes out in the next couple months, this will be the same build included on it. so nothing like ahead start lol
Click to expand...
Click to collapse
Going to look at this - thanks
will be so happy if this is an easy fix. Thanks Wes. Didnt even occur to me the changes for the 3.5mm jack output would cause problems
wesgarner said:
Going to look at this - thanks
Click to expand...
Click to collapse
See a few things different in the config
Will have to port over the 3.5mm headphone drivers
Try this one out - should work on an WG-Kernel builds aka WG-Build and maybe a couple others, not sure
But should let you test real quick if you through my build on there then fastboot this boot.img
Oo it technically works on CM builds too - but nothing would really work lol (at least the touchscreen would)
I am betting this won't work but eh worth a try lol
crypysmoker said:
will be so happy if this is an easy fix. Thanks Wes. Didnt even occur to me the changes for the 3.5mm jack output would cause problems
Click to expand...
Click to collapse
lol yea requires new drivers to get it to work - they are on the MSM .32 git, I will have to backport them - no biggie for that I'm sure
wesgarner said:
Try this one out - should work on an WG-Kernel builds aka WG-Build and maybe a couple others, not sure
But should let you test real quick if you through my build on there then fastboot this boot.img
Oo it technically works on CM builds too - but nothing would really work lol (at least the touchscreen would)
I am betting this won't work but eh worth a try lol
Click to expand...
Click to collapse
lol Worth a shot.. I already got through the dangourus stuff. I use yours as it is on my spare G1 so no worries about it on here. Ill let you know the outcome.
wesgarner said:
Try this one out - should work on an WG-Kernel builds aka WG-Build and maybe a couple others, not sure
But should let you test real quick if you through my build on there then fastboot this boot.img
Oo it technically works on CM builds too - but nothing would really work lol (at least the touchscreen would)
I am betting this won't work but eh worth a try lol
Click to expand...
Click to collapse
Argh..
Flashed your newest build, then tried to flash the boot.img.zip file with verification failed. then onto remember that I have the perfected spl on when I tried to flash it lol. Without having a physical keyboard like the g1, and needing to flash the boot.img before boot... is there another way?
Also find that since we had to use a 32B recovery on a 32a phone... nandroid will not work in recovery. Guess ill try fastboot laster
crypysmoker said:
Argh..
Flashed your newest build, then tried to flash the boot.img.zip file with verification failed. then onto remember that I have the perfected spl on when I tried to flash it lol. Without having a physical keyboard like the g1, and needing to flash the boot.img before boot... is there another way?
Also find that since we had to use a 32B recovery on a 32a phone... nandroid will not work in recovery. Guess ill try fastboot laster
Click to expand...
Click to collapse
Try:
adb remount
adb shell
flash_image boot /sdcard/boot.img
reboot
EDIT: I tried that and this is what I got:
mtd: write error at 0x00140000 (Out of memory)
mtd: verification error at 0x00140000 (Out of memory)
mtd: wrote block after 1 retries
mtd: write error at 0x00160000 (Out of memory)
mtd: verification error at 0x00160000 (Out of memory)
mtd: wrote block after 1 retries
darn
Ok... would have just built a kernel for this that should (theoretically) work based off the nexusone kernel...
My battery just died on my laptop
Was a good idea! lol
Will compile in a little while and post
no rush at all guys and I thank those of you that hopped on this much quicker then I expected. eminds me of the old dreamcast homebrew days where everyone actualy worked together rather then who gets the most credit for what.
We got the hard part done.. now onto the fun part. And, at the same time if we dont get a full rom going by the OTA 2.1 update, at least we will have straight dumps off the phones lol
use the custom kernel, and post the dmesg
Compiling the new kernel now lol - sorry for the delay
Will build it into my current git beta build of y-2.7 lol
wesgarner said:
Compiling the new kernel now lol - sorry for the delay
Will build it into my current git beta build of y-2.7 lol
Click to expand...
Click to collapse
Awesome. If possible please let me know once finished for testing.
I cant belive at how many people start bugging you for stuff when your the first to find something. Honestly, My gtalk friends grew 10fold by 3am, of which 6 I had to explain what "stock rom" meant lol How many times can I hear "but whats the point if it doesnt look different" before I want to smackanoob lol
HTC has to release this Kernel source too.
maxisma said:
HTC has to release this Kernel source too.
Click to expand...
Click to collapse
Awwww. noo BOOOO dont tell me that lol. I mean, its fine now because im still using my g1 as to no hurt my wittle fender baby lol.
But once the new mytouch comes out there will be a flood of noobiness over this. But at least I got it out thier early so the good ones can have at it.
By the way, LOVE the quote in yoru sig. Kinda like question I used to get asked back in Xbox 1 modding days. "where is bios and can I take it out?" "I type FTP into my web browser and it wont see my xbox" "
maxisma said:
HTC has to release this Kernel source too.
Click to expand...
Click to collapse
Actually looks like the kernel source is active on the android-msm-2.6.29-nexusone
wesgarner said:
Actually looks like the kernel source is active on the android-msm-2.6.29-nexusone
Click to expand...
Click to collapse
Ouuuu. so if its running on same/similar kernel to Nexus one... 2.1 will run with ease.. at least the OTA version will lol.
But, at same time, lot of people going to be ad they grabbed up that nexus one.
wesgarner said:
Actually looks like the kernel source is active on the android-msm-2.6.29-nexusone
Click to expand...
Click to collapse
You could be right..
http://android.git.kernel.org/?p=ke...118;hb=refs/heads/android-msm-2.6.29-nexusone
-rwxr-xr-x
board-sapphire-gpio.c
blob | history | raw
-rwxr-xr-x
board-sapphire-h2w.c
blob | history | raw
-rwxr-xr-x
board-sapphire-keypad.c
blob | history | raw
-rwxr-xr-x
board-sapphire-mmc.c
blob | history | raw
-rwxr-xr-x
board-sapphire-panel.c
blob | history | raw
-rwxr-xr-x
board-sapphire-rfkill.c
blob | history | raw
-rwxr-xr-x
board-sapphire-wifi.c
blob | history | raw
-rwxr-xr-x
board-sapphire.c
blob | history | raw
-rwxr-xr-x
board-sapphire.h
blob | history | raw
Click to expand...
Click to collapse
crypysmoker,
If we are rocking the same kernel off of the nexus one, what does that mean for us in the future? Are we going to be able to do things quite similar?
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 )
Originally this was going to be something I would do for Kyorarom v0.2.0, but I will also let the general public in on my works.
I am currently going through every single file in CM6.2 and seeing if it will work on Froyo with little to no effort. Why? Well think of it as a poor mans alternative to a fully functioning CM6.2. I respect marcellusbes work 100% but there are so many people who are being impatient about the non-existant ETA of CM6.2 and CM7 (BECAUSE IT SAYS THERE IS NO ETA AND THERE SHOULD NOT NEED TO BE AN ETA), I decided to give the people half of what the want: the performance and open sourceness of CM6.2 while still retaining 100% functionality of the Samsung firmware.
Current Status
99% of the bins are working
A few CM apps are working
Some of the libs are working (but they are more just sitting in there)
--- CONSIDER THIS VERY MUCH IN BETA - THIS WILL HAVE A FEW BUGS HERE AND THERE SO PLEASE REPORT ALL OF THEM SO I CAN FIX THEM ---
Now remember, this is by no means an alternative to CM6.2, it is more of a stopgap for people who really want our phone to have CM6.2 on it.
I have been working on this all day today and haven't been able to actually test it properly, but it appears to be stable with the files I have added, and it also appears to be quicker. Not by much, but it feels a little smoother.
Why would I need this?
As I said, it's a poor mans CM6.2. It will give you 90% of the performance of CM6.2 while still giving you 100% functionality (provided I haven't broken anything) from Samsung firmware. Programs run quicker, the system responds faster, and the system just feels smoother in general. It's not like FuguTweaks or V6 Supercharger which gives you a tiny change, the goal of this is to give you a HUGE change.
What is noticably quicker?
Well I need people to tell me that, but what I have noticed is quicker is:
Screen rotate happens quicker
Scrolling through menus
Swiping around websites
System boot time
What do I need to use this?
Well I have only tested this on Kyorarom v0.2.0 alpha (unreleased), so I don't know how your results may go, but it SHOULD work on all JPS based SAMSUNG ROMS.
THIS IS NOT A PATCH FOR CM6.2! THIS IS A PATCH FOR SAMSUNG!
You will also need CWM with update.zip signing disabled. This is provided as an update.zip as there are SO MANY permissions that need to be set in the bins/xbins/libs that it would be ridiculous to tell people to run an ugly script which will probably not work on 99% of peoples computers, so an update.zip without signing is how I will do this. Why no signing? Because every guide I have followed to tell me how to sign a zip or an APK has done nothing useful. SOMEONE TELL ME HOW PLEASE!
How do I install this?
Just put this on your SD Card, go into CWM and tell it to update from an update.zip. Pretty simple. I highly recommend doing a system.img backup first though to be on the safe side in case something goes terribly wrong. Format your /system before restoring the system.img.
What should I do if I get a bug such as a force close or a random reboot
Get your phone right to just before the crash happens
Plug your phone into ADB
Go into ADB SHELL
Type logcat > /sdcard/crashlog.txt
Reproduce the crash
Wait until it has rebooted/force closed
Press Ctrl-C on ADB SHELL
Get the crashlog.txt off your SDcard and paste the last about 20-30 lines in a code box here telling me what you did to cause the crash.
Links
Patch 0.3.1 (requires Samsung firmware, recommended to be on JPS)
CMapps 0.3.0 (should work on Samsung firmware without CMbins)
CMbins Remover (will only replace the bins with the original Samsung bins)
Patch v0.2.0 (requires Samsung firmware, recommended to be on JPS)
Busybox Fix (for in case you installed any of the patches v0.0.3 and below - NOT AN UPDATE.ZIP: THIS IS A BUNCH OF FILES WITH A README)
Please note that this may play up with some custom themes, especially large ones such as MIUI as this replaces a lot of files which these themes may be using or rely upon.
Credits
marcellusbe for his incredibly hard work on CM6.2 and CM7 which sadly seems to not be appreciated as much as it should by some of this community. Please go over to both the CM6.2 and CM7 threads and thank him for his hard work, even if you have already done so.
Change Log
v0.3.1
Removed more pointless stuff such as the etc and libs as they won't provide a performance boost. They were more decoratio.
Fixed install script which removed TW apps but didn't replace them from v0.3.0.
v0.3.0
Removed pointless bins which don't provide any performance boost, such as ping and stuff.
Fixed force close lag bug.
v0.2.0
Added the last few bins that were missing. Only bins missing are the ones that cause the system to break.
Added a few more things from etc from CM. They shouldn't cause any difference.
v0.1.1
Fixed dalvik-cache building.
v0.1.0
Removed xbin. It was causing too many problems
Added a few libs (ones that aren't in Samsung)
Added a few items from etc
Replaced a few stock Samsung apps in order to clean the system up before I remove twframework.
v0.0.3
Fixed the missing meta-inf folder in the update.zip. Sorry guys!
v0.0.2
Fixed the busybox issue. the patch removed the old busybox and replaced it with a broken one. If this doesn't fix it then 'mount -o rw,remount /dev/block/stl6 /system' and 'chmod 755 /system/xbin/*'
I was doing something like this , cm framework on jps
But you did more
np
i didnt have the time to complete it fully(exams)
Best of luck!
cdesai said:
I was doing something like this , cm framework on jps
But you did more
np
i didnt have the time to complete it fully(exams)
Best of luck!
Click to expand...
Click to collapse
If you wish to help me then by all means I'll be grateful. I am nowhere near finished as there are a few files in /system/bin that still need checked to see if they cause issues. I just went through the alphabet and if a file such as 'dexopt' caused problems then I left out all of D. However that's just an example. Dexopt is left out, but I left in the rest of D as I found it causing problems later down the track. I know I am missing Q and S. I'm gonna go through them all tomorrow.
EDIT: Not to mention I want to go through frameworks and libs and the etc folder too.
I am not sure if this is helpfull or not... I instaled the update in my phone. At the moment, only issue is that busybox installer is not working after it get superuser permisions, and then i cannot open any other app. I need to reboot my system. If i find any other issue, i will let you know.
Sergiales said:
I am not sure if this is helpfull or not... I instaled the update in my phone. At the moment, only issue is that busybox installer is not working after it get superuser permisions, and then i cannot open any other app. I need to reboot my system. If i find any other issue, i will let you know.
Click to expand...
Click to collapse
Hmm, I might have done somethign weird with xbin. Try going into adb shell and run 'chmod 755 /system/xbin/*'. I might have to get it to set permissions in the update.zip for that folder.
EDIT: Try restore your system back to how it was prior the install of the update, and then try the other zip I just put in the first post. I think it'll be the xbin folder doing it.
@hillbeast
you also plan to port the framework of cm6?
ale_bot said:
@hillbeast
you also plan to port the framework of cm6?
Click to expand...
Click to collapse
I hope I can. The plan is to get everything that will work from CM6.2 in Samsung firmwares to work.
New version uploaded. See first post for details.
I fixed the busybox issue. I thought I fixed it earlier but aparently not. It was CM6.2s Busybox being in there that killed it. I put the Samsung one into v0.0.2 so it'll fix the grief it caused with version 0.0.1.
If it still causes issues then go into adb shell (or Terminal Emulator) and run this code:
Code:
mount -o rw,remount /dev/block/stl6 /system
chmod 755 /system/xbin/*
Donate and get rewarded
Good work, hillbeast.
I wish you would work more togother, i mean most of the main developers in g3.
you know the names.
And some more support from the community with donating and thanks or appriciation.
You (just caught you user reading this), could donate a little bit, so that your galaxy 3 is got tuned with great software, so it worth allmost double the price then you paid for it, because it expands with possibillities and powers.
Just click someones (dharamg3, marcelubes.. and some of all the other great programmers) donate button, type the number: 5 or 10 or 20 or 100 +++ etc, log in to paypal and DONATE!
(•.•) said:
Gut work, hillbeast.
I wish you would work more togother, i mean most of the main developers in g3.
you know the names.
And some more support from the community with donating and thanks or appriciation.
Yes You, could donate a little bit, so that your galaxy 3 is got tuned with great software, so it worth allmost double the price then you paid for it, because it expands with possibillities and powers.
Just click someones donate button, type the number: 5 or 10 or 20 or 100 +++ etc, log in to paypal and DONATE!
Click to expand...
Click to collapse
I actually work with dharamg3 on occasion and have given him ideas for G3Mod. I just don't take credit for anything because my contributions have been very minor at best and my credit isn't deserved considering how much more he and marcell have done for our phone.
hillbeast said:
I actually work with dharamg3 on occasion and have given him ideas for G3Mod. I just don't take credit for anything because my contributions have been very minor at best and my credit isn't deserved considering how much more he and marcell have done for our phone.
Click to expand...
Click to collapse
Yeah, i mean it for all developers, but you included of course. so why not.
Just for every user to remind if he reads my post.
(•.•) said:
Yeah, i mean it for all developers, but you included of course. so why not.
Just for every user to remind if he reads my post.
Click to expand...
Click to collapse
Yeah that is the entire point of the XDA: developers helping developers to make our phones incredible and help them reach their true potential.
People bash the Galaxy 3 but undreneith it's actually a really good phone with really good hardware. It's no dual-core Cortex-A9 with 1GB of DDR2 RAM or anything, but it's certainly a very good mid-range phone. It was just held back by Samsung not programming it right.
Nice vision man...best of luck
To make things easier i guess you can consult marcellusbe about what all stuff is not working in CM6.2...then u'll need to replace only those files instead of going through evry file !!
niteshtak said:
Nice vision man...best of luck
To make things easier i guess you can consult marcellusbe about what all stuff is not working in CM6.2...then u'll need to replace only those files instead of going through evry file !!
Click to expand...
Click to collapse
Yes however I also need to find what is compatible with the rest of Samsungs firmware.
hillbeast said:
Hmm, I might have done somethign weird with xbin. Try going into adb shell and run 'chmod 755 /system/xbin/*'. I might have to get it to set permissions in the update.zip for that folder.
EDIT: Try restore your system back to how it was prior the install of the update, and then try the other zip I just put in the first post. I think it'll be the xbin folder doing it.
Click to expand...
Click to collapse
I have just installed that 0.1 you told me and now is working good. I am gonna try the 0.2 and tell you if all is ok.
Guys I totally forgot the meta-inf folder in v0.0.2. You can just use the one from v0.0.1 as there is no signing or anything. I'll see if I can get the link on my phone for v1
Sent from my GT-I5800 using XDA App
But why using cyanogenmod files in samsung firmware ?
You know that CM 6.2 is the most awesome rom for froyo ! I've almost never had any lags and the rom is fast even after installing a tons of app's !
Darius_AWS said:
But why using cyanogenmod files in samsung firmware ?
You know that CM 6.2 is the most awesome rom for froyo ! I've almost never had any lags and the rom is fast even after installing a tons of app's !
Click to expand...
Click to collapse
Well its just a try to get the CM6.2 speed and smoothness on the samsung ROM..without having the bugs of CM6.2 which arent solved yet...
Sergiales said:
I have just installed that 0.1 you told me and now is working good. I am gonna try the 0.2 and tell you if all is ok.
Click to expand...
Click to collapse
Same problem in 0.2 with busybox installer, even trying to fix it with adb.
Darius_AWS said:
But why using cyanogenmod files in samsung firmware ?
You know that CM 6.2 is the most awesome rom for froyo ! I've almost never had any lags and the rom is fast even after installing a tons of app's !
Click to expand...
Click to collapse
As I stated in the OP, Cyanogenmod is incomplete and is buggy. The camera doesn't work, the FM radio doesn't work, no Bluetooth, and some things are buggy. By working in the opposite direction of moving to Cyanogenmod with small steps by using the working components from it, we get a balance.of speed and functionality which is what a lot of people have been moaning about all this time since CM went alpha.
Again, huge respect to marcell for getting it this far. This is a huge achievement from him.
Also here is the mediafire link for v1 so people can grab meta-inf and insert it into the v2. I will fix this in v3 later today.
Sent from my hybrid Kyorarom + Cyanogenmod Galaxy 3