Related
Hello all,
I started this thread as I was testing myhero v1.0.0 and my BT doesn't plays music and on the myhero v0.1.0 it plays...
I've found on the folder root/system/lib 2 OS files for the A2DP, the liba2dp.so (53.14 K) and the libA2DP.so (9.12K) on the version that works!!! An the one that was missing on the version who doesn't work was the smaller one!!! In all you can also find the file libbluetooth.so and the liba2dp.so that they are mandatory for the your ROM starting...
Always use the Astro Explorer, Root Explorer or any other explorer and check the file system of your device to check what is the file missing.
Code:
adb remount
adb push libA2DP.so /system/lib/
-- or/and --
adb push liba2dp2.so /system/lib/
It was informed that the media by Bluetooth was working on Hero ROM's (32A and 32B too)!!
ATTENTION: In some ROM's the libA2DP.so is already there, as the liba2dp2.so too, like the myhero v.1.1.2 based on a Modaco's ROM, in this one, the files were there but the libA2DP.so had a different size. On this ROM the A2DP issue was fixed substituting the files. This also MAY be what is happening on other ROM's!
Thanks to all from making everything possible!
TOGETHER WE CAN EVERYTHING!!.
My best regards to all community..
Last update on 09/19/2009
worked for me! I will add the the ROM thread too
edit: I lied, you added it there already.
edit2: just push the small file to the device and music will work again (if you haven't already)
adb remount
adb push libA2DP.so /system/lib/
did you also try to rename libA2DP.so to liba2dp.so?
No renaming,
linux is case sensitive (as far as I know) and both files (liba2dp.so and libA2DP.so) were in the MyHero v0.1.0 ROM and BT was working.
I just pushed the missing file to MyHero v1.0.0 and bt was working again.
Completely possible that liba2dp.so is unrequired, I will pull it and see what happens.
EDIT: Ugh... I deleted liba2dp.so and rebooted, got stuck on initial splash screen... push the file back via the recovery mode, and I am STILL getting stuck at the initial screen...wtf... SIGH
does this fix the BT phone functions or just the Stereo Headset?
Phone function doesn't work for me when I do this. Just the music.
ryoojin83 said:
worked for me! I will add the the ROM thread too
edit: I lied, you added it there already.
edit2: just push the small file to the device and music will work again (if you haven't already)
adb remount
adb push libA2DP.so /system/lib/
Click to expand...
Click to collapse
Hi..
Great news than, I just wake up I'll flash it right now (hmm.. this flash thing remind me the film with the music from Queen hahahaha )
.. so Flash oh ohhhhh Thanks for the code my friend, adb on mine yesterday said to me it was read-only, I didn't do the remount...
Who knows knows.. Thanks ryoojin83
ricardomega said:
Hi..
Great news than, I just wake up I'll flash it right now (hmm.. this flash thing remind me the film with the music from Queen hahahaha )
.. so Flash oh ohhhhh Thanks for the code my friend, adb on mine yesterday said to me it was read-only, I didn't do the remount...
Who knows knows.. Thanks ryoojin83
Click to expand...
Click to collapse
^-- this man is abnormal just awaken xD
Done and working yuppppiii
Great find! OMG it was so simple after all
Could you include both files on first post please?
L10nH34Rt said:
Great find! OMG it was so simple after all
Could you include both files on first post please?
Click to expand...
Click to collapse
Sure He's here my friend!! You'll test on your ROM's?
"My" roms I just port them
I can't test (no BT headset), but I sure as hell can include them
Greatt
Ported or not, is a hard work and someone has to do it
Hope it works on yours as well!
Best Regards!!
Hello, someone already connected the headphone bluetooth Nokia BH101 ?
If yes, working well and which rom ?
Thanks for feedback.
linux92 said:
Hello, someone already connected the headphone bluetooth Nokia BH101 ?
If yes, working well and which rom ?
Thanks for feedback.
Click to expand...
Click to collapse
I just google search your headset and it seems that it is A2dp tech compatible... so in other works, it seems that you are able to ear music on it but don't expect to place calls with it...
GOOGLE KNOW EVERYTHING
good news we are waiting, im ready to flash new rom with bluetooth support...
at314 said:
good news we are waiting, im ready to flash new rom with bluetooth support...
Click to expand...
Click to collapse
Is still not full BT support.. it just music (media) on the Bluetooth..
Some people answered that this features were placed on other ROM's, not only on myhero from redglasses.. but, I think this can be a plug to people compile a library that works on full, since there's so many others in other languages.. I'm not a programmer, but who is and read this mini-tread, understanding how this works maybe just be enough to start working on that.. If Bluex can do it as a app, why we can incl this as a normal process, or something..
Anyway, just ideas... I don't know really what I'm talking about...
Great found, I did this way and the music play on my SE HBH-DS200 work fine...
Simple much?
I'm sure this is way-over-simplified, but if this works, shouldn't there be a file in /system/lib from the previous builds that deals with phone audio that could be ported over and added/replaced? Just have to find it...
idenncsu said:
I'm sure this is way-over-simplified, but if this works, shouldn't there be a file in /system/lib from the previous builds that deals with phone audio that could be ported over and added/replaced? Just have to find it...
Click to expand...
Click to collapse
Although is not mentioned, in some ROM's that had before this issues, this was already done
***I have recently switched to the Nexus One but I will continue to do these Magic ports as long as there is a desire (and I have time).***
This is a thread for the port files required to use the 32B Cyanogenmod ROM on 32a/EBI1 phones. Please see the following link for details on the ROM:
http://forum.xda-developers.com/showthread.php?t=567610
Note: Rogers users - if you find yourself without data upon flashing this ROM, use the settings found here to restore your APN.
Credit Radix for the following instructions - they are copy/pasted from his thread. Also thanks to all of devs who have contributed to the ROM scene - impossible to mention all of you, specifically Amon_RA, stericson, prash, cyanogen, riku, Radix, koush, TigerTael, haykuro, pershoot, zinx and more I am forgetting I am sure.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
***Please note that the following steps require that you have a recovery with the option to flash any .zip file. I recommend Amon_RAs recovery, Clockwork Recovery, or ROM Manager
***
NOTE: All new ports will be based on Koush's Universal update.zip. This lets you flash just a kernel and matching libs to a phone without the need for a ramdisk. Basically, it takes the ramdisk currently installed and repacks with it the new kernel.
Basically, the port packages provided from now on will port ANY ROM from 32B --> 32A/EBI1.
CM5.x (Eclair base)
Upgrade from 4.2.x Cyanogenmod ROM
http://wiki.cyanogenmod.com/index.p...or_other_rooted_ROMS_to_5.0.x(Dream/Sapphire))
Gapps Mirror: http://briancrook.ca/android/gapps/gapps-ds-ERE36B-signed.zip
CM4.2.x (Donut Base)
NEW INSTALL (ie. never installed CM 4.1.99 or greater before):
Magic Users
Rogers Dream EBI1 Users
UPGRADE INSTALL (ie. already installed 4.1.99 or greater):
Cyanogenmod Wiki
ROM Manager
1. Download ROM Manager from the market
2. Flash the ClockWork Recovery
3. Go to Download ROM > CyanogenMOD > Choose the version you want to flash.
4. Select Gapps addon (if you want Google Apps)
5. This will reboot to recovery, make a backup if requested, flash all the components and reboot.
6. Win.
Theme Support
Themes CAN be applied overtop of this ROM/Port combo. Just make sure to reboot in between the Defanged Base/update-cm-/port file step and pick a theme that corresponds to the Cyanogenmod version you are running. Keep in mind that some themes include a boot.img (no idea why...), so just keep an eye out. If you apply a theme with a 32B boot.img, just reapply the port file afterwards. If you apply a theme with a 32B boot.img, the phone will not boot past your carrier lockscreen...you can easily restart and reflash the port file. Always backup before flashing anything!!
==================================================================================================
If you would like to donate, please use the following link. Any donations are greatly appreciated
==================================================================================================
Port Files:
CM-6.1.0
Download: http://briancrook.ca/android/cm-ports/bc-6.1.0-ebi1-signed.zip
md5sum
CM-6.1.0-RC1
Download: http://briancrook.ca/android/cm-ports/bc-6.1.0-RC1-ebi1-signed.zip
md5sum
ROM Manager Web Connect
For older -test versions of ports, go to: www.briancrook.ca/android/cm-ports/old
CM-6.0.0-RC1
Download: http://briancrook.ca/android/cm-ports/bc-6.0.0-RC1-ebi1-signed.zip
md5sum
For older -test versions of ports, go to: www.briancrook.ca/android/cm-ports/old
==============================================================================
CM-5.0.8
Download: http://briancrook.ca/android/cm-ports/bc-5.0.8-ebi1-signed.zip
md5sum
For older -test versions of ports, go to: www.briancrook.ca/android/cm-ports/old
==============================================================================
CM-4.2.15.1
Download: http://briancrook.ca/android/cm-ports/bc-4.2.15.1-ebi1-signed.zip
md5sum
Iptables was left out by mistake. Tether issues should be gone.
For other port versions, go to: www.briancrook.ca/android/cm-ports/old
Thank you
cheer
Worked great, thanks a ton!
Does anyone else have signal problems with this rom?
I have had lost signal, many many times today
bunny0007 said:
Does anyone else have signal problems with this rom?
I have had lost signal, many many times today
Click to expand...
Click to collapse
no problem
very niceļ¼
i like this rom, but now i cant have Google navigation
elite_is3 said:
i like this rom, but now i cant have Google navigation
Click to expand...
Click to collapse
did you have it before you did the new rom? i had to go to a like 4.2.4 or 4.2.3.1 and then download the gmaps off the market and then took it back to the 4.2.5. I havent did the 4.2.6
can this be installed using the one click method from the unlockr.com
i have the amon ra recovery
also im on a perfect spl - do i need to change that- rookie questions i know-
Anyone else not able to access the dialer while in a phone call... or is just me?
1.33.2005
3.22.20.17
KeeganX said:
Anyone else not able to access the dialer while in a phone call... or is just me?
1.33.2005
3.22.20.17
Click to expand...
Click to collapse
Do you mean the dialpad, that you drag up while on a call? it works for me.
KeeganX said:
Anyone else not able to access the dialer while in a phone call... or is just me?
1.33.2005
3.22.20.17
Click to expand...
Click to collapse
I can access it just fine. Have you tried doing a wipe?
Moving the bug I'm having from another thread to this new one, here it is:
Can somebody confirm if this is just my problem or a ROM bug?
Steps to reproduce:
1) While listening to music using bluetooth
2) Answer an incoming call
3) use the bluetooth headset to pickup phone call
4) Cannot hear any audio nor can the caller hear you talk
I loaded back an android 2.0 rom (jd02 with x3rom 32A patch) and can confirm this is NOT a problem.
I also tried loading back 4.2.5 cyanogen and its a problem there as well.
Anybody can verify with there ROM or have a clue whats going on?
httpftp123 said:
Moving the bug I'm having from another thread to this new one, here it is:
Can somebody confirm if this is just my problem or a ROM bug?
Steps to reproduce:
1) While listening to music using bluetooth
2) Answer an incoming call
3) use the bluetooth headset to pickup phone call
4) Cannot hear any audio nor can the caller hear you talk
I loaded back an android 2.0 rom (jd02 with x3rom 32A patch) and can confirm this is NOT a problem.
I also tried loading back 4.2.5 cyanogen and its a problem there as well.
Anybody can verify with there ROM or have a clue whats going on?
Click to expand...
Click to collapse
I cant confirm, I dont have the proper bluetooth stuff. have you checked the cyanogen bugtracker?
I have a few issues after updating from 4.2.5 without wiping.
1. GPS kept losing signal during navigation.
2. Lost three 888 xxxxxxx call receptions today.
3. My wife complained she heard horrible static noises each time when I changed locations. For example, when I moved from outside to inside my building or I stepped out of my truck.
4. I couldn't listen to my voicemail through GV. FC every time.
The rest work great. The rebooting time is super fast.
Thank you so much, guys.
httpftp123 said:
Moving the bug I'm having from another thread to this new one, here it is:
Can somebody confirm if this is just my problem or a ROM bug?
Steps to reproduce:
1) While listening to music using bluetooth
2) Answer an incoming call
3) use the bluetooth headset to pickup phone call
4) Cannot hear any audio nor can the caller hear you talk
I loaded back an android 2.0 rom (jd02 with x3rom 32A patch) and can confirm this is NOT a problem.
I also tried loading back 4.2.5 cyanogen and its a problem there as well.
Anybody can verify with there ROM or have a clue whats going on?
Click to expand...
Click to collapse
I believe I suffer from this issue as well, or at least something related. This was also happening on 4.2.5, but was perfect on my previous ROM, MyHero.
In my case I use a mini USB Y-Splitter adapter in the car: one end goes to the mini-USB cigarette lighter charger, the other to a 3.5mm jack for the AUX-IN in my car stereo. This way I can listen to Pandora or whatever over the stereo. If I answer a call in this setup the other party cannot hear me. Similarly I cannot speak any Google searches, or use Shazam, or anything that requires my microphone to work. I was hoping this release would fix it. Evidently not.
As stated, worked great with MyHero. *sigh*
No one else could confirm this as an issue before, so I thought I was alone... maybe still am...
Newbie here
I'm confused as to what the differences are between the kernel port files and why it matters which one you choose?
Thanks
httpftp123 said:
Moving the bug I'm having from another thread to this new one, here it is:
Can somebody confirm if this is just my problem or a ROM bug?
Steps to reproduce:
1) While listening to music using bluetooth
2) Answer an incoming call
3) use the bluetooth headset to pickup phone call
4) Cannot hear any audio nor can the caller hear you talk
I loaded back an android 2.0 rom (jd02 with x3rom 32A patch) and can confirm this is NOT a problem.
I also tried loading back 4.2.5 cyanogen and its a problem there as well.
Anybody can verify with there ROM or have a clue whats going on?
Click to expand...
Click to collapse
I listen to music in my car audio which is connected to my phone via BT (music from my phone). When someone calls i just pick up call and talk through built in car system. After the call, music just continues playing.
sleepymatt said:
Newbie here
I'm confused as to what the differences are between the kernel port files and why it matters which one you choose?
Thanks
Click to expand...
Click to collapse
they 'adapt' to the roms for which they are written, allowing 32a owners to flash 32b roms on their devices.
you dont really have a choice on which port file to install. there is only one (generally) for each version of a rom.
sleepymatt said:
Newbie here
I'm confused as to what the differences are between the kernel port files and why it matters which one you choose?
Thanks
Click to expand...
Click to collapse
Pick the one that corresponds to the version of CM you are running. Assuming you want to use the newest cm (version 4.2.6), use the 4.2.6 port file
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 )
This post is now irrelevant, Alex put these commands into the main program. See second post for links.
I figured out how to get it fully working. Big thank you to tonyb486 and canteenboy for figuring out that you need to disable adb and usb mass storage for tethering to work. That only left the problem of disk mounting not working after you are tethering. Here are two scripts to get the whole thing running smoothly and without a problem.
First, if you haven't already, install android-wired-tether. Next install GScript Lite (on the Market) which will let us automate toggling the USB function switch.
Create a new script with SU enabled and use this as the code.
Code:
echo 0 > /sys/devices/platform/msm_hsusb/usb_function_switch
That command shuts off usb_mass_storage and adb so everything is disabled and ready for Wired Tether to come in and do its job. Your usb_function_switch will look like this after running the command.
usb_mass_storage:disable
adb:disable
diag:disable
serial:disable
ether:disable
modem:disable
nmea:disable
When you are done tethering, use this command to re-enable adb and usb_mass_storage:
Code:
echo 3 > /sys/devices/platform/msm_hsusb/usb_function_switch
If for some reason you don't use USB debugging (adb), you can use this command to turn on usb_mass_storage by itself.
Code:
echo 1 > /sys/devices/platform/msm_hsusb/usb_function_switch
For those of you new to GScript, you can place shortcuts to scripts on your home screen. To simplify my life, I put them in a folder with Wired Tether so I have everything in one place. It's not an elegant solution, but you won't need to reboot your phone to get SD card mounting to work again. Perhaps someone with more knowledge of GScript can write some code that will automate running the first script, starting Wired Tether, and then running the last script after it notices that tethering has stopped. (Or better yet, get these commands into the actual program itself.)
(Optional)
For completeness, if you use any of the other usb functions listed above, you can use other 'echo #' commands to find the right combination. They don't toggle individual settings, but rather represent entire combinations of settings. I think around 32-33 it cycles back to 0 (everything off), I didn't have time to figure out if there is a pattern. You can find out what each number does by using another script to read out the switches.
Code:
cat /sys/devices/platform/msm_hsusb/usb_function_switch
Huge thank you to Alex C. Hofbauer. He implemented these commands into the program. Now the program works flawlessly (or I assume, I haven't tested it yet).
Attached to this post:
http://forum.xda-developers.com/showthread.php?t=706602
http://code.google.com/p/android-wired-tether/issues/detail?id=21
Thanks! I'd like to add that the scripts and the patched app are both working great on my Incredible.
O Whoa, Wired Tether works on my stock Eris now Thank You
Saturn2K said:
Huge thank you to Alex C. Hofbauer. He implemented these commands into the program. Now the program works flawlessly (or I assume, I haven't tested it yet).
Attached to this post:
http://forum.xda-developers.com/showthread.php?t=706602
http://code.google.com/p/android-wired-tether/issues/detail?id=21
Click to expand...
Click to collapse
Do you have the link to the exact program that has the commands built in? Perused both links and couldn't find the link to the fixed one for the Evo.
jerdog said:
Do you have the link to the exact program that has the commands built in? Perused both links and couldn't find the link to the fixed one for the Evo.
Click to expand...
Click to collapse
Same. I was going to try the app on the Eris because the same manual fix works :\
jerdog said:
Do you have the link to the exact program that has the commands built in? Perused both links and couldn't find the link to the fixed one for the Evo.
Click to expand...
Click to collapse
yeah me too cant find it
Wow, I thought nobody gave a **** about this. Here it is, all compiled and ready to go.
Thanks duder, works like a charm...
Sent from my phone.
THANKS!!!!
Has anyone figured out how to get this to work on Froyo? I get a kernel unsupported error when trying to run it.
dalstrs said:
Has anyone figured out how to get this to work on Froyo? I get a kernel unsupported error when trying to run it.
Click to expand...
Click to collapse
Same here, I'm using netarchy's 4.0.3a kernel and SteelH's stock Froyo RevE.1 ROM.
I have stock froyo on my evo and use easythether, it works perfect, all you have to do is set it to debug mode in the settings, install the app on your computer and when connected set it to charge only.
Sent from my Evo using XDA App
striker012 said:
I have stock froyo on my evo and use easythether, it works perfect, all you have to do is set it to debug mode in the settings, install the app on your computer and when connected set it to charge only.
Sent from my Evo using XDA App
Click to expand...
Click to collapse
The problem with that is having to install stuff on the computer. With wired tether you don't have to install anything on the computer.
XevoX said:
Same here, I'm using netarchy's 4.0.3a kernel and SteelH's stock Froyo RevE.1 ROM.
Click to expand...
Click to collapse
I'm running the same kernel on evio rom and it's working fine for me...
Sent from my phone.
I've been able to make this work on my stock kernel, rooted FroYo Evo, so this is indeed possible and I've narrowed it down to what is necessary. Please star/follow issue 23 in the Google Code tracker for updates.
Unsupported Kernel message...
Hello, all. I'm running Fresh Evo 3.1.0.1 and King's latest kernel and I get the unsupported kernel message. When I try to ignore as is suggested in post 24 on the Google code page for the wired tether, I get a FC once I click to start tethering. Any ideas? Thanks in advance. -E
Hello, all. I'm running Fresh Evo 3.1.0.1 and King's latest kernel and I get the unsupported kernel message. When I try to ignore as is suggested in post 24 on the Google code page for the wired tether, I get a FC once I click to start tethering. Any ideas? Thanks in advance. -E
Click to expand...
Click to collapse
Hi EindhovenOne, I responded to you on the issue tracker for Wired Tether, but I'll respond here just for some others to know the situation.
I found a fix that worked for me on my stock, rooted FroYo Evo and I coded the change and sent Harald a patch. He incorporated the patch and did the build for Wired Tether for me to test, which I have done (and it does indeed work for me, but does currently have the unsupported kernel dialog*). At the same time, though, it is listed in the downloads (you have to select all and then search), but this is in beta state for the changes (hence the deprecated tag I believe).
* I have fixed the unsupported kernel message and sent Harald a patch on this as well, so when he finds time to build it, that should be corrected, too.
So back to the "it's not working" portion, since I'm not running anything but stock (ROM and kernel), my system won't be the same as everyone's. I have no problem with other variations of ROMs and kernels (Evo's and non-Evo's) trying the 1.3 APK, giving feedback, and I'll try to do what I can (and someone else can step in if more suited than me even).
If you do run into issues, you can tag them in the issue tracker, which I try to follow frequently right now. Also, most importantly, if you can provide as much information as possible (what ROM and kernel you're using, a LogCat run just after the error occurs, any other pertinent information we can use to diagnose the problem, etc.), that helps tremendously in tracking down the problem and identifying a fix.
Saturn2K said:
Huge thank you to Alex C. Hofbauer. He implemented these commands into the program. Now the program works flawlessly (or I assume, I haven't tested it yet).
Attached to this post:
http://forum.xda-developers.com/showthread.php?t=706602
http://code.google.com/p/android-wired-tether/issues/detail?id=21
Click to expand...
Click to collapse
Is there a way we can find this patched version of android-tether? It is no longer attached to the first post. Also, the version I download from google still says incompatible kernel. It would be awesome to get wired tether working for the EVO
superevilllama said:
Is there a way we can find this patched version of android-tether? It is no longer attached to the first post. Also, the version I download from google still says incompatible kernel. It would be awesome to get wired tether working for the EVO
Click to expand...
Click to collapse
The beta-in-progress version 1.3 is located here. It still warns about the kernel currently but you can ignore it (simple lapse in patching that as well at the time). It works perfectly for me (starting and stopping), but there are a couple of issues outstanding right now that I'm working through with the users.
If you do run into a problem, though, just let me/us know through the issue tracker preferably, but you can also contact me directly (here, or my email via the issue tracker).
PS: I have patched the kernel message already, but I don't have write access to the project yet and I don't have the build system in place to handle the native code just yet, so I have been handing builds off to Harald who graciously has done the 1.3 so far for me. When he has time to do the one including the kernel warning fix, I'll post again with an update on that.
Hello, since there seems to be some confusion I decided to start this thread for the 32A port.
The G1 / Magic 32B thread is here: http://forum.xda-developers.com/showthread.php?t=776922
Note that all the work on PSFreedom was done by KaKaRoTo, and he was helped by DrMon in the MSM72K port, i merely compiled their work and put it in a simple package for everyone to enjoy.
I created 2 packages, an enabler and a disabler, that you have to flash over your working CM 6.0 Final installation.
Flashing the enabler will install the modded kernel and PSFreedom module. You will lose usb functionality completely (no adb, no mass storage etc.) until you flash the disabler.
After flashing the enabler the module will always start upon boot, you have to enter no commands on the terminal emulator.
[SIZE=+2]HOW TO:[/SIZE]
Preliminary: Make sure you are on CyanogenMod 6.0 Final and everything is working correctly. It has been reported that it works also with older CM6 versions and CM5 too, you may try if it works and report it in this thread. If it's the first time, do a Nandroid backup before testing!
Download these files: http://www.multiupload.com/MY1LOGZ6YP (32A-Enabler), www.megaupload.com/?d=3UU2L0UX (32A-Disabler)
Put them on your SD card
Reboot into recovery and Flash Enable_PSFreedom_32A.zip
Reboot
Now psfreedom should be loaded as a module, you will see no difference, except for the loss of normal usb functions.
To run the exploit:
Make sure you are on 3.41 (DO NOT UPDATE OVER THE NETWORK!)
Connect the phone to the PS3 using usb
Turn it off completely (unplug power cable or turn off back switch on Fat models)
Plug it back in (turn on back switch)
Turn it on and immediately press the eject button (you should hear 3 quick beeps)
Booting should take a bit longer (5-10 seconds)
If you see two new options under the games tab, the exploit worked. You can now unplug the phone. Mind that you will have to do this procedure every time you boot your PS3. Try using another USB cable if it doesn't work with a few tries.
To uninstall:
Boot back into recovery
Flash Disable_PSFreedom_G1.zip
Reboot
You should have usb functions back to normal.
Payloads:
This version of PSFreedom contains the new PSGroove 1.1 payload (peek & poke)and is enabled for backups, but backup manager talk should not be done on this thread, there are other boards for that.
If you want to try other payloads (F.I. the new AerialX's apploader), you just have to load it into /proc/psfreedom/payload . You can do it by typing:
Code:
cat payload > /proc/psfreedom/payload
The payload can be wherever you want and has to be in the classic binary format. (just remember to substitute "payload" with the correct path).
Even better, if you put the new payload in the /data/local directory, named "payload" (no quotes), it will be automatically loaded upon startup, thus becoming the default payload.
Mirrors:
Code:
Enabler: http://depositfiles.com/en/files/o1qpcbkeo
http://www.zshare.net/download/80630364707ab8fe/
http://rapidshare.com/files/420315547/Enable_PSFreedom_32A_v3.zip
Disabler: http://www.zshare.net/download/801637791c6185b2/
Versions:
Code:
v0: initial release
v1: +module loaded on startup
+created disabler
v2: updated payload (peek & poke)
v3: resolved bootloop bug, updated PSFreedom, dynamic payload loading.
reserved (10 characters long)
Thanks for yours work!
What about an application to enable/disable psfreedom? Will it be possible in the future?
My Magic (32A) does just reboot over and over after flashing the enabler.......also after flashing the disabler........so now restoring (i ALWAYS back-up befor flashing anything!)
But thanks for trying!
radio version for cm6
one question, CM6 can be for New Radio, or just Old radio?
H3llSp4wN said:
one question, CM6 can be for New Radio, or just Old radio?
Click to expand...
Click to collapse
there's a port also for new radio showthread.php?t=723520
But there are some issues (like broken camera)
Old Radio, new radio requires a different kernel.
For the app, for now psfreedom requires a modded kernel, and it is not possible to switch them on the fly using an app. I know they're working on using a different driver, to avoid having to recompile the kernel. Still don't know if it can be done though.
Can anyone provide a mirror please?
cm6
i'm just a bit confused about what cm6 rom should be better and should i use, because there are severeal releases (minimou, redux etc).
can u give me a tip about this?
best regards
I always use the vanilla one, straight from the cyanogenMod forums. I think it should work with any of those versions though. Just make sure you're on old radio and you make a nandroid backup before trying.
got everything right now.
thanks for the mirror.
Got a question? Does the mt3gs use the msm72k also and why is it not on the port list? Sorry I'm probably in the wrong area but thought I would try
Hi , just have a question , looked arround with google , couldn't find my answer, maybe someone here knows,
Before trying this out, I would like to know if I can revert my ps3 to original state,
or to how it was before running psgroove?
yes as the exploit must be ran on every boot so simply reboot and delete bxxm
H3llSp4wN said:
i'm just a bit confused about what cm6 rom should be better and should i use, because there are severeal releases (minimou, redux etc).
can u give me a tip about this?
best regards
Click to expand...
Click to collapse
i use redux and it works for me (i still use the release that u have to do thru the terminal)
focus400hp said:
Got a question? Does the mt3gs use the msm72k also and why is it not on the port list? Sorry I'm probably in the wrong area but thought I would try
Click to expand...
Click to collapse
MT3G is 32B, so head off to the Dream section and get that one instead.
with cm6 my g1 go in loop... why?
Hey guys, I'm running into a little trouble after installing the PSFreedom enabler. My htc magic 32a (3.5mm jacket) just sits on the "HTC Magic" screen for eternity after flashing PSfreedom. I do have CM 6.0 installed, I believe its from Cyanogenmod 6.0 S/D version, I don't know what ebi I am nor if need to do something with kernel, but I just know I go into recovery, flash PSfreedom enabler, reboot, the "htc magic" logo shows up and then it sits there forever...Is there something I'm doing wrong?
@ repukken, rock187. You should use the 32B port. The link is in the first post.
Lollipop_Lawlipop said:
MT3G is 32B, so head off to the Dream section and get that one instead.
Click to expand...
Click to collapse
its mt3g slide i believe its different though i did use the precompiled for the dream 32b on a g1 yesterday and works very well and with no probs at all still want to see something for the slide. i asked in the slide forums and everyone just had s*** to talk really